Any specific read/write/directory listing is blocking -- it returns a value after the appropriate 1-wire communication. So you can perform as tight a loop as you want.
If you have more than one process accessing owfs, you wil either get data from the cache,or wait until the bus is free. The 1-wire bus is locked during each query, but each 1-wire bus is locked independently. I don't know if owfs can hit the theoretical maximum throughput of the 1-wire bus. We don't poll the line to see when conversions are done, for example, but wait the theoretical maximum time given in the datasheet. Still, there is no limitation on trying. Paul Alfille On Sun, Dec 28, 2008 at 8:34 AM, Jaap Struyk <[email protected]> wrote: > Hello, > > I was wondering what the max. polling time of owfs itself is. > If I recall correctly the shortest interval to poll 1-wire sensors is > 10ms. to 50ms. depending on the type is that correct? > Currently I am trying to write a C interface to collect data and writing > it into mysql and are wondering what theoretically the maximum is. > If the above is correct it would mean 20-100 polls per second for every > available 9097, can owfs handle this? (or is the serial port a limit here?) > > > > ------------------------------------------------------------------------------ > _______________________________________________ > 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
