I have just run it again, sleep for 3 seconds after the
simultaneous/temperature write and sleep 25 seconds at the end of the
loop. Presence is at 120 and I see a delay every 130 seconds or so.
The delay is on reading whichever parameter is first, so if I read
present first then that is the 0.7 scan, the other parameters are < 0.1,
but If I read type first then that is 0.7 sec, etc
I am also reading CR16_errors and CR16_tries, these are the same and
both increase by 8 each loop. Is that normal? Is there any
documentation on this stuff, I can't find anything.
Mick
On 08/08/2020 08:46, Martin Patzak wrote:
Thanks Mick, great summary.
Let me add to 4), that you only see the 0.7 sec delay, because you
read in a busy loop.
I read only every 30 seconds and I never see a delay.
But timing your reads is a good practice because this way you catch
retries and maybe bus or sensor problems.
Additionally you can have a look in /statistics for retries and errors
On 08.08.20 01:04, Mick Sulley wrote:
Update on test findings. Test setup was 19 - DS18B20 temperature, 2
- DS2413 IO and 1 - DS2437 Voltage, Raspberry Pi4 with Sheepwalk RPi3
Adapter
1) /simultaneous/temperature does work, best to read latesttemp.
2) /settings/timeout/presence cannot be set or read via the owhttpd
web page, you must use owwrite & owread
3) Reading values (after setting simultaneous) normally takes < 0.1
seconds
4) After the /settings/timeout/presence interval the next read for
every device will take around 0.7 seconds. Note if you read multiple
fields it is only the first one which takes the increased time.
5) The increased time after /settings/timeout/presence interval
applies to all devices, not just temperature
Mick
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
