On Sat, Aug 9, 2008 at 6:23 AM, Matthias Urlichs <[EMAIL PROTECTED]>wrote:
> Sometimes the bus is blocked for too long to share it.
>
> Polling e.g. a motion sensor or a door contact a couple of times per
> second doesn't work when there's e.g. a temperature sensor on the same
> bus, as reading that thing takes >1 second.
>
Good point.
Some suggestions:
1. The DS2482-800 lines have some cross-contention (only one can be read at
a time), but the 1 second conversion delay with the bus powered high should
be ok.
2. OWFS spawns a separate thread for each request, so queries on different
busses should be fine. The only time a request ties up all the busses is
when OWFS is finding the location of a device, and when simultaneous
conversion is requested.
a. You can specify the exact location of a device by /bus.1/10.1231231231
although it's a little fragile.
b. The locations are cached. If the design is fairly static, increasing
that timeout would be more efficient.
Paul Alfille
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
