/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.

No idea why you loose also the first adapter, but before starting to debug the 
problem I would try to implement correct udev rules and see if you get a more 
stable environment.

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.

Finally you have a chain adapters "usb-to-serial => serial-to-1wire": I would 
consider a usb-to1wire solution, since you will eliminate one point of failure.

Stefano



> On 14 Oct 2016, at 17:07, samuix <sam...@gmx.de <mailto:sam...@gmx.de>> wrote:
> 
> Hello,
> i had a look at dmesg –e and saw the error message:
> ftdi_sio ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
> After the disconnection the USB device was connected to USB2 instead of USB1. 
> It looks like that the owserver had the problem after the USB1 was 
> disconnected, missing.
>  
> Why the values from the still connected USB0 are not available anylonger?
> How can we recognize that the owserver has a problem ?
>  
> Thanks
> Br
>  
> Gesendet: Freitag, 14. Oktober 2016 um 15:54 Uhr
> Von: "Jan Kandziora" <j...@gmx.de <mailto:j...@gmx.de>>
> An: "OWFS (One-wire file system) discussion and help" 
> <owfs-developers@lists.sourceforge.net 
> <mailto:owfs-developers@lists.sourceforge.net>>
> Betreff: Re: [Owfs-developers] owserver is not working correctly
> Am 14.10.2016 um 14:42 schrieb samuix:
> > Hello,
> > we are using since one week two ds9097u bus adapter at the same time. It 
> > works
> > fine until this morning the owserver don't response any request, openhab or
> > owdir, the process was still running. After restart its work fine again
> > Start command: owserver -d /dev/ttyUSB0 -d /dev/ttyUSB1 -p4304
> > Where is the problem? How we can findout if it is running normally or not to
> > maybe auto restart?
> >
> Most likely these are USB problems. Check
> 
> # dmesg
> 
> for error messages first, should this happen again.
> 
> 
> Kind regards
> 
> Jan
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org <http://slashdot.org/>! 
> http://sdm.link/slashdot <http://sdm.link/slashdot>
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net 
> <mailto:Owfs-developers@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/owfs-developers 
> <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://slashdot.org/>! 
> http://sdm.link/slashdot_______________________________________________ 
> <http://sdm.link/slashdot_______________________________________________>
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net 
> <mailto: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

Reply via email to