jan iversen comments

Results 123 comments of


jan iversen

updated time.sleep to 0.02s in _wait_for_data() under sync.py

But because it works for you, does not mean it is a general solution at least you have not convinced me (e.g. for lower BPS it surely needs to be...

updated time.sleep to 0.02s in _wait_for_data() under sync.py

For example read the documentation. As you can see the stack trace is not initiated by the while loop, so are you sure the while loop is actually run multiple...

updated time.sleep to 0.02s in _wait_for_data() under sync.py

Right now both @dhoomakethu and myself believes this PR is not correct even though it works in your case.

updated time.sleep to 0.02s in _wait_for_data() under sync.py

@balaARR I Think you are forgetting a couple of Modbus restriccions. 0.01 is too fast for your setup running, and 0.02 is just perfect. But you are using 19.200Bps what...

updated time.sleep to 0.02s in _wait_for_data() under sync.py

Are you still working on a generic solution ?

updated time.sleep to 0.02s in _wait_for_data() under sync.py

closing

Previous response from modbus device returned as current response when using sync TCP over network with lag

Previous response are no longer returned on current dev.

Doesn't construct payload if unit is greater than 0x9, unit=0x9

This works in my test setup, can you please provide debug logs, so we can see why it is not working for you (maybe you do slave unit id =...

Doesn't construct payload if unit is greater than 0x9, unit=0x9

Closing as no longer actual.

Slow read operation when sync serial client and servers are running at the same time

We now have a test that among others addresses this issue test/test_examples.py, furthermore I did some testing: examples/server_sync + examples/client_sync using 2 USB rs-485 adapters, no delay, limiting factor were...