We have a feature that isn't fully implemented or tested called --one_device.
The idea is that only one device is on that bus, so after the initial discovery, much faster techniques can be used to access the slave. UIsing that an a dedicated bus master for each rpm sensor could get you near your goal. Paul Alfille On Mon, Dec 29, 2008 at 3:02 AM, Jaap Struyk <[email protected]> wrote: > Matthias Urlichs schreef: > > > You'll need to put the RPM sensors onto a different bus. > > > >> So I like to poll those 2 sensors (counters DS2423) every 10ms. > >> > > 10ms is very ambitious. > > That is why I bought a HUB at first instance, unfortunately it was > broken on arrival, the plan was to use one bus for temps. and both > counters on separate ones so every counter had it's own bus. (even then > 10ms. is tricky, I know) > I have no clue if 10ms. should be fast enough to prevent damage, maybe > it's way to slow but maybe 100ms. is also fast enough as response time. > Time will learn... > > There are a lot of things I am not certain about, but whatever happens > owfs is very capable of logging my temps. so that is my primary goal, > the fun part of the 1-wire stuff is that it is extendible so I start > with temps. only and work my way up until I am satisfied or until I > reach the limits. > > Whatever happens it would be fun to stand aside the track with a laptop, > login into our own (moving) wlan-ap on the tractor and read the temp. > stuff online, so every step above this will only add extra fun! > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Owfs-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/owfs-developers >
------------------------------------------------------------------------------
_______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
