Le vendredi 21 juillet 2017 à 10:47 +0200, Martin Patzak (GMX) a écrit : > I am trying to start owserver with a LinkUSB V 1.7 as bus master > using > the option /--link/. > I am able to start owserver with the LinkUSB V 1.7 and V 1.4 using > the > option "d" for device without any problems.
I can confirm the same behaviour here. I just upgraded my Raspberry Pi to Raspbian stretch with owfs 3.1p5 (from squeeze with owfs 2.8). The serial LINK is not recognised with the --link option, but OK with -- device. I didn't change anything else, juste upgraded the system. Here are the logs : root@raspberry:~# owserver -V owserver version: 3.1p5 libow version: 3.1p5 root@raspberry:~# owserver --link=/dev/owlink --foreground --error_level=9 DEBUG: ow_daemon.c:(170) main thread id = 3069931600 DEBUG: ow_inotify.c:(80) No configuration files to monitor CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library isn't found CALL: ow_parsename.c:(104) path=[] DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock adapters) DEBUG: ow_com.c:(47) Auto initialization of /dev/owlink DEBUG: ow_link.c:(328) Detecting serial LINK using 9600 bps DEBUG: ow_link.c:(360) Slurp in initial bytes DEBUG: ow_link.c:(431) Checking LINK version DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.000000 seconds DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1 DEBUG: ow_link.c:(199) Link version Found 1.0 CONNECT: owlib.c:(216) Cannot open LINK bus master at /dev/owlink DEBUG: ow_serial_free.c:(40) COM_close: flush DEBUG: ow_serial_free.c:(42) COM_close: restore DEFAULT: owlib.c:(52) No valid 1-wire buses found DEBUG: ow_exit.c:(17) Exit code = 1 ... root@raspberry:~# ls -l /dev/owlink lrwxrwxrwx 1 root root 7 sept. 10 21:39 /dev/owlink -> ttyUSB2 > What seams to be the problem? Anybody seen this before? I've never seen that before. owfs and my serial LINK have both been very reliable since at least 2003... -- Nicolas Huillard ------------------------------------------------------------------------------ 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