Hi Jan, It turns out the sensors are parasite powered. :/ We bought them from iButtonLink already packaged that way. We don't need to update our readings that often so it's okay. Every 2-5 minutes is fine.
On 10/5/2015 6:54 AM, Jan Kandziora wrote: > Am 05.10.2015 um 14:23 schrieb Alex R. Gibbs: >> >> However, other clients will have to wait if they happen >> to query owserver during the conversion/read. >> > No. That can only happen if you use parasite powered sensors. Because > parasite power occupies the bus during temperature conversion for > powering. That's a limitation of the hardware, you cannot do anything > about that. I was hoping the owfs cache would buffer clients against that. Here is a test case with 1 sensor. I do: owwrite -s localhost:4304 /settings/timeout/volatile 30 I confirm it with an owread. One script triggers a conversion and read every 15 seconds using: owread /uncached/###/temperature Every 100ms another script does: owread /###/temperature The response is 2-3 ms unless the fist script is doing the uncached read, in which case it takes about a second. Owserver waits for the uncached read to finish instead of returning the still-valid cached value. If this is the expected behavior and there isn't an alternative then I need to do external caching. By the way, thanks for writing owfs! Alex ------------------------------------------------------------------------------ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
