It appears that the supplied version is not compiled with the ftdi option. I had not tried restarting owserver or unplugging the linkUSB. Unfortunately it has so far always failed at a inconvenient time when the priority has been to get the heating running again before the house freezes :)
Next time hopefully I will be able to try one or other of those. Colin On 2 March 2017 at 12:03, Johan Ström <jo...@stromnet.se> wrote: > Hi, > > no suggestion on what it could be, but it looks like you are using the > serial device layer, not the libftdi layer. > > I'm not sure it will make a difference, or behave more reliable, but you > could try to use direct ftdi access, make sure to compile with libftdi > support (or if if that is on by default on jessie?) and check the man > pages (use something like --device ftdi:xxx:yyyy). > > Besides that, have you tried pulling the LinkUSB out and re-inserting it > (both on USB side and 1W side, if 1W net is externally powered)? And > also restarting owserver. > > Johan > > > On 02/03/17 10:21, Colin Law wrote: >> Running a LinkUSB on a pi zero (Raspbian Jessie), with owserver >> 3.1p4-1 from jessie testing, I very occasionally (every few weeks) see >> in syslog >> >> Mar 1 22:10:50 pi004 kernel: [194834.694657] ftdi_sio ttyUSB0: failed >> to get modem status: -110 >> Mar 1 22:11:00 pi004 kernel: [194844.694679] ftdi_sio ttyUSB0: failed >> to get modem status: -110 >> Mar 1 22:11:06 pi004 kernel: [194850.694734] ftdi_sio ttyUSB0: >> ftdi_set_termios FAILED to set databits/stopbits/parity >> Mar 1 22:11:07 pi004 kernel: [194851.694724] ftdi_sio ttyUSB0: >> ftdi_set_termios urb failed to set baudrate >> Mar 1 22:11:12 pi004 kernel: [194856.694771] ftdi_sio ttyUSB0: urb >> failed to clear flow control >> Mar 1 22:11:22 pi004 kernel: [194866.694810] ftdi_sio ttyUSB0: failed >> to get modem status: -110 >> Mar 1 22:11:27 pi004 kernel: [194871.694819] ftdi_sio ttyUSB0: urb >> failed to clear flow control >> >> and thereafter owserver returns >> Errno::ECONNRESET: Connection reset by peer >> There is nothing else abnormal in syslog around the above ftdi messages. >> >> After a reboot everything works ok for another few weeks. >> >> Has anyone any suggestions what might be causing it? >> >> Colin >> >> ------------------------------------------------------------------------------ >> 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 ------------------------------------------------------------------------------ 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
