see inline
Gesendet: Freitag, 14. Oktober 2016 um 18:06 Uhr
Von: "Jan Kandziora" <j...@gmx.de>
An: "OWFS (One-wire file system) discussion and help" <owfs-developers@lists.sourceforge.net>
Betreff: Re: [Owfs-developers] owserver is not working correctly
Von: "Jan Kandziora" <j...@gmx.de>
An: "OWFS (One-wire file system) discussion and help" <owfs-developers@lists.sourceforge.net>
Betreff: Re: [Owfs-developers] owserver is not working correctly
Am 14.10.2016 um 17:36 schrieb Stefano Miccoli:
> /dev/ttyUSBx names are NOT persistent, and typically when you unplug
> an USB-to-serial adapter and reconnect it you get a new /dev/ttyUSBy
> device.
>
> On the contrary owserver needs a persistent device name to work
> properly: try googling "udev rules ttyusb” for some recipes on how
> to write a udev rule which creates a persistent symlink to the
> current serial adapter, and configure owserver to connect to the
> persistent name.
>
While this is correct, it can be incredibly hard to write such a rule
when you have two or more otherwise identical adapters.
It works, they have different serial numbers
>
> From the spec the DS9097U-009 includes a DS2502 Identification Chip:
> if this is your case you can use the ‘owpresent’ command to check if
> the adapter is still connected.
>
You can use Johan Ström's owusbprobe for this. It's in the owshell
directory from recent owfs installations.
It shows only the difference of the USB adapters. My problem is during owserver is running and nobody knows when the USB adapter do not answer
Kind regards
Jan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
> /dev/ttyUSBx names are NOT persistent, and typically when you unplug
> an USB-to-serial adapter and reconnect it you get a new /dev/ttyUSBy
> device.
>
> On the contrary owserver needs a persistent device name to work
> properly: try googling "udev rules ttyusb” for some recipes on how
> to write a udev rule which creates a persistent symlink to the
> current serial adapter, and configure owserver to connect to the
> persistent name.
>
While this is correct, it can be incredibly hard to write such a rule
when you have two or more otherwise identical adapters.
It works, they have different serial numbers
>
> From the spec the DS9097U-009 includes a DS2502 Identification Chip:
> if this is your case you can use the ‘owpresent’ command to check if
> the adapter is still connected.
>
You can use Johan Ström's owusbprobe for this. It's in the owshell
directory from recent owfs installations.
It shows only the difference of the USB adapters. My problem is during owserver is running and nobody knows when the USB adapter do not answer
Kind regards
Jan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
