You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to read and write registers on a specific serial device. I started with a basic synchronous client, but found the read/writes to be too slow. I expected the asynchronous client to vastly increase performance, but it seems like the execute method is blocking until timeout (default 3s), even though the device has replied.
I saw this behaviour on version 3.8.3 and then built the latest development version to see if it has been fixed in the pre-release (it hasn't).
If I adjust the timeout, the reads are much faster, but I don't think this is intended. If the device has replied, the async code should not block.
Async do return as soon as a valid response is received, but for some reason your device did not respond to the first request, and when resending it responded 2 times, The problem might be in your rs485 converter.
Versions
Pymodbus Specific
Description
I am attempting to read and write registers on a specific serial device. I started with a basic synchronous client, but found the read/writes to be too slow. I expected the asynchronous client to vastly increase performance, but it seems like the execute method is blocking until timeout (default 3s), even though the device has replied.
I saw this behaviour on version 3.8.3 and then built the latest development version to see if it has been fixed in the pre-release (it hasn't).
If I adjust the timeout, the reads are much faster, but I don't think this is intended. If the device has replied, the async code should not block.
Code and Logs
code is based on https://github.com/pymodbus-dev/pymodbus/blob/901a87d885af009b4f272999877bccb155ff064b/examples/client_performance.py, but adapted to read registers on my known devic.
Note in the logs below the 3s delay between reads
The text was updated successfully, but these errors were encountered: