Hi Paul, I am currently working on upgrading from 2.8p1 to 2.8p8. I have been running fine on 2.8p1 for several months (since July or last year). I had to patch 2.8p1 to force hardware flow control because otherwise owserver would not be able to talk to my LinkUSB in emulation mode.
I remember that back when I originally reported this problem you changed things so hardware flow control would be used if a first attempt using no flow control failed. That seems to be working. However, it takes a long time for the detection to succeed: May 3 14:22:38 altamira OWFS[21715]: CALL: ow_parsename.c:FS_ParsedName_anywhere(95) path=[] May 3 14:22:38 altamira OWFS[21715]: DEBUG: owlib.c:SetupTemperatureLimits(79) Globals temp limits 0C 100C (for sim ulated adapters) May 3 14:22:38 altamira OWFS[21715]: DEBUG: ow_link.c:LINK_detect_serial(237) Slurp in initial bytes May 3 14:22:38 altamira OWFS[21715]: DEBUG: ow_link.c:LINK_version(298) Checking LINK version May 3 14:22:38 altamira OWFS[21715]: DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds May 3 14:22:43 altamira OWFS[21715]: CONNECT: ow_tcp_read.c:tcp_read(110) TIMEOUT after 0 bytes May 3 14:22:43 altamira OWFS[21715]: DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds May 3 14:22:48 altamira OWFS[21715]: CONNECT: ow_tcp_read.c:tcp_read(110) TIMEOUT after 0 bytes <lots of TCP connect errors> [...] May 3 14:24:58 altamira OWFS[21715]: DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds May 3 14:25:03 altamira OWFS[21715]: CONNECT: ow_tcp_read.c:tcp_read(110) TIMEOUT after 0 bytes May 3 14:25:38 altamira OWFS[21715]: DEFAULT: ow_link.c:LINK_version(349) LINK version string too long. <> greater than 36 chars May 3 14:25:38 altamira OWFS[21715]: DEFAULT: ow_link.c:LINK_detect_serial(243) LINK detection error May 3 14:25:38 altamira OWFS[21715]: DEBUG: ow_link.c:LINK_detect(211) Second attempt at serial LINK setup <second attempt will finally succeed, but after many of the following TCP connection errors> May 3 14:25:38 altamira OWFS[21715]: DEBUG: ow_link.c:LINK_detect_serial(237) Slurp in initial bytes May 3 14:25:38 altamira OWFS[21715]: DEBUG: ow_link.c:LINK_version(298) Checking LINK version May 3 14:25:38 altamira OWFS[21715]: DEBUG: ow_tcp_read.c:tcp_read(64) attempt 1 bytes Time: 5.000000 seconds May 3 14:25:38 altamira OWFS[21715]: DEBUG: ow_tcp_read.c:tcp_read(114) read: 1 - 0 = 1 May 3 14:25:38 altamira OWFS[21715]: DEBUG: ow_link.c:LinkVersion_knownstring(133) Link version Found 1.4 I am starting owserver like this: /opt/owfs/bin/owserver --link /dev/1wire-master0 -C --error_print 0 --error_level 5 --nozero The TCP errors seem to be causing a long delay, but as far as I can see there is no need for any TCP connections since owserver is only talking to a serial device. Any ideas why TCP connections are being attempted? Cheers, Eloy Paris.- ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
