Things I would try, in random order.

- Try an ‘owdir /uncached ’ command before writing to simultaneous, just to 
refresh the owserver view of the devices on the bus. Maybe a single owdir 
command is faster that querying the sensors one at a time.
- Do not use owserver aliases, use only bus addresses (this is just my personal 
dislike, and some troubles in having a stable working setup with aliases in the 
past)
- Nuclear option: enable the owserver verbose output and try to pinpoint what’s 
going on when the loop slows down.

Just for reference, here are some stats form my tiny home owserver, with a 
LinkUSB host adapter and two Link multi sensors.
(I’m using walk.py, which you can find here: 
https://github.com/miccoli/pyownet/blob/dev/examples/walk.py 
<https://github.com/miccoli/pyownet/blob/dev/examples/walk.py>
)

$ python walk.py /statistics/read/
/statistics/read/bytes                   b'     2442834'
/statistics/read/cachebytes              b'           0'
/statistics/read/cachesuccess            b'           0'
/statistics/read/calls                   b'       99461'
/statistics/read/success                 b'      198136'
/statistics/read/tries.ALL               b'       99464,           0,           
0'
/statistics/read/tries.0                 b'       99465'
/statistics/read/tries.1                 b'           0'
/statistics/read/tries.2                 b'           0'

$ walk.py /statistics/errors/
/statistics/errors/BUS_bit_errors        b'           0'
/statistics/errors/BUS_byte_errors       b'           0'
/statistics/errors/BUS_detect_errors     b'           0'
/statistics/errors/BUS_echo_errors       b'           0'
/statistics/errors/BUS_level_errors      b'           0'
/statistics/errors/BUS_next_alarm_errors b'           0'
/statistics/errors/BUS_next_errors       b'           0'
/statistics/errors/BUS_readin_data_errors b'           0'
/statistics/errors/BUS_status_errors     b'           0'
/statistics/errors/BUS_tcsetattr_errors  b'           0'
/statistics/errors/CRC16_errors          b'           0'
/statistics/errors/CRC16_tries           b'           0'
/statistics/errors/CRC8_errors           b'           0'
/statistics/errors/CRC8_tries            b'      197398'
/statistics/errors/DS2480_level_docheck_errors b'           0'
/statistics/errors/DS2480_read_fd_isset  b'           0'
/statistics/errors/DS2480_read_null      b'           0'
/statistics/errors/DS2480_read_read      b'           0'
/statistics/errors/NET_accept_errors     b'           0'
/statistics/errors/NET_connection_errors b'           0'
/statistics/errors/NET_read_errors       b'           1'
/statistics/errors/max_delay             b'           0'



> On 9 Aug 2020, at 11:38, Martin Patzak <martin.pat...@gmx.de> wrote:
> 
> 
> 
> On 09.08.20 11:34, Mick Sulley wrote:
>> 
>> CRC16_tries        11768
>> CRC16_errors        11768
>> 
> you should not have near that amount of CRC errors
> read the errors after every module reading or writing to find out what
> causes those errors
>> 
>> Time to do some reading of the docs.......
>> 
> yeah, enjoy and good luck :-)
> 
> 
> 
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to