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.00 seconds
CONNECT: ow_tcp_read.c:(110) TIMEOUT afte
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.
On Sun, Nov 10, 2013 at 1:24 PM, Willard Korfhage wrote:
Using picocom to interact directly with the LinkUSB with the f and n
commands, I find 2 devices:
770245762028
431473A90D01
Odd that owlib says there are no valid 1-wire buses. I tried slowing
down the baud rate to 19200, but the results are no different. I don't
see any way of forcing
I found at least part of the problem. Playing with picocom, I determined
that the baud rate was 57600. Applying that to the command line removes
the link detection errors, although it still says it cannot find a valid
1-wire bus
On 11/10/2013 12:24 PM, Willard Korfhage wrote:
I already checked
I already checked that before, and it looks fine. This is from today. I
have 2 LinkUSBi's and I tried them both (not at the same time) with
identical results.
[68001.548041] usb 5-1: new full-speed USB device number 3 using uhci_hcd
[68001.770796] usbcore: registered new interface driver usbser
