Have you tried to disconnect the 1-wire network and connect only to the
LinkUSB itself?
Sometimes wiring-problems, defective sensors and other hardware related
problems (like humidity) can cause weird behavior.
On 11/11/2013 07:04 AM, Willard Korfhage wrote:
Doesn't help, I'm afraid. Here's the debug info
DEBUG: ow_ds9097U.c:(287) Attempt 0 of 3 to initialize the DS9097U
DEBUG: ow_ds9097U.c:(381) Send the initial reset to the bus master.
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_ds9097U.c:(476) Failed first attempt at resetting baud rate
of bus master /dev/ttyUSB0
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_ds9097U.c:(481) Failed second attempt at resetting baud
rate of bus master /dev/ttyUSB0
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_ds9097U.c:(476) Failed first attempt at resetting baud rate
of bus master /dev/ttyUSB0
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_ds9097U.c:(481) Failed second attempt at resetting baud
rate of bus master /dev/ttyUSB0
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_serial_open.c:(174) Cannot power cycle a closed serial port
DEBUG: ow_ds9097U.c:(381) Send the initial reset to the bus master.
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_ds9097U.c:(476) Failed first attempt at resetting baud rate
of bus master /dev/ttyUSB0
DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT after 0 bytes
DEBUG: ow_ds9097U.c:(481) Failed second attempt at resetting baud
rate of bus master /dev/ttyUSB0
... [keeps going]
I tried to use socat so I could monitor the serial connection:
sudo socat -v -d -d pty,raw,echo=0 file:/dev/ttyUSB0,raw,echo=0,b57600
That creates a pty and a bidirectional passthrough to /dev/ttyUSB0,
echoing the traffic to the screen. I ran owfs with -d /dev/pts/2, for
that is the PTY that socat printed out. Somehow, that ended up resetting
the LinkUSB to 9600 baud, which seems to have been key to getting better
behavior.
By the way, when using socat, I couldn't run owfs with
"--link=/dev/pts/2" because I got a "cannot access device" message even
though I was running as root.
Anyway, now that the LinkUSB is 9600 baud, running
sudo /opt/owfs/bin/owfs --baud=9600 --link=/dev/ttyUSB0 -m /var/lib/1wire
works, partially. The directory shows the structure I expect to see, but
I don't see any devices:
# ls /var/lib/1wire
bus.0 settings statistics structure system uncached
There is a temperature sensor on it, so I would expect to see something.
On 11/10/2013 12:54 PM, Don Veino wrote:
What happens if you try -d vs --link, as in following?
sudo /opt/owfs/bin/owfs -d /dev/ttyUSB0 -m /var/lib/1wire
I have a LinkUSB (non-i) and use that device nomenclature with
owserver and it works fine with 2.9p0-1 on Arch Linux ARM.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
