On Jan 3, 2008 10:46 PM, Matthias Urlichs <[EMAIL PROTECTED]> wrote:
>
>
> IMHO the whole idea is somewhat flawed: as soon as you talk to it using
> the 3-wire interface, it won't respond to 1wire commands any more.
> There is no way to get any consistent metric of your bus quality that way.
>
I just figured I'd do something like only access the device from the 1wire
host in the middle of a 20 second (or so) window every minute, during which
the Arduino would not access the 3-wire port. That big of a window gives me
plenty of room to keep the times "close enough" to each other. Or I could
probably just have each host just keep trying every second until it's able
to access the DS2404. Each would have it's own area to write to, and
wouldn't believe anything read from the other's area until it was read the
same twice in a row (in case it managed to read something in between write
operations by the other host).
But I see your point... I'm just going to assume that the reason I can't
read from the 1wire port is because the 3wire port is in use... when it
could be because of some problem on the 1wire bus.
"...the device will still respond to the reset pulse, but any subsequently
transmitted 1-Wire command will be ignored." So what would owfs do then?
Would there be a way to distinguish between that response and an unreachable
device?
-------------------------------------------------------------------------
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
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
