Tilman,
I presume your output from 12/15/2006 is still accurate:
./owhttpd -d /dev/tty0 -p 3001 --foreground -msec_read=700 --error_level=9
CALL: PARSENAME path=[]
CONNECT: Cannot detect DS2480 or LINK interface on /dev/tty0.
DEBUG: COM_close: flush
DEBUG: COM_close: restore
DEBUG: COM_close: close
CALL: PARSENAME path=[]
DEFAULT: Cannot detect DS9097 (passive) interface on /dev/tty0.
DEBUG: COM_close: flush
DEBUG: COM_close: restore
DEBUG: COM_close: close
DEBUG: ServerProcessOut = 3084725152
DEBUG: ServerProcessAccept 3001[3084725152] try lock 0
DEBUG: ServerProcessAccept 3001[3084725152] locked 0
DEBUG: ServerProcess: break signo=2
DEBUG: ow_net.c:ServerProcess() shutdown initiated
DEBUG: Shutting down 0 of 1 thread -1210242144
DEBUG: ow_net.c:ServerProcess() shutdown done
DEBUG: ow_exit 0
CALL: Starting Library cleanup
CALL: Closing Cache
CALL: Closing input devices
DEBUG: FreeIn: busmode=2
CALL: Closing outout devices
CALL: Finished Library cleanup
When I try the same thing, this is what I get:
amd64:/home/paul # owhttpd -d /dev/ttyS0 -p 3001 --foreground
--error_level=9
CALL: PARSENAME path=[]
DEBUG: ServerProcessOut = 1082132800
DEBUG: OW_Announce: 1
DEBUG: OW_Announce: end
DEBUG: ServerProcessAccept 3001[1082132800] try lock 0
DEBUG: ServerProcessAccept 3001[1082132800] locked 0
DEBUG: Announce: 1
DEBUG: Announce: 2
DETAIL: RegisterBack ref=5274160 flags=0 error=0 name=OWFS (1-wire) Web
type=_http._tcp. domain=local.
DEBUG: RegisterBack: done
DEBUG: Announce: 3
DETAIL: RegisterBack ref=5274304 flags=0 error=0 name=OWFS (1-wire) Web
type=_owhttpd._tcp. domain=local.
DEBUG: RegisterBack: done
DEBUG: Announce: end
And, indeed, it works from there.
That is because the MAX232 has a inverter stage build in and negates the
> signal (Please refer to page 25 figure 11b in
> http://datasheets.maxim-ic.com/en/ds/DS2480B.pdf)
>
Ok, just offering a suggestion.
>
> I tried again using an oscilloscope. I see some signal changes on the tx
> line.
> a) I wonder what to expect however. A screenshot of an oscilloscope or an
> equivalent description of the detection sequence would be really helpful :-)
>
Looking at the code, we set the speed, then send a "break", then "C1" to set
timing.
> b) Looking through the code in DS2480_detect ( ow_ds9097U.c) suggest that
> there should be some activity on the RX line as well during the detection
> sequence. Is this correct ?
>
Yes, after that timing byte, 4 bytes of configuration are sent, and echoed
back.
> c) Is there some activity to be expected on the OW bus during the detect
> sequence ?
>
After those configuration byte, a 1-wire reset is done.
d) Any suggestions how to narrow this done ? Would it for instance help to
instrument the detect sequence and see where it bails out ?
Yes, that's exactly what I would do. You can put a printf after every branch
point in DS2480_detect (in modules/owlib/src/c/ow_ds9097U.c) Since you are
running in foreground, the lines will appear on the console. Remember to add
a "\n" after each debugging line to flush the buffer.
Paul Alfille
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
