-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Long wait time between receiving a reply and sending the next request #67
Comments
Hi! |
Thanks, that's a useful feature but it's not what I'm talking about - the round trip is quick as the MCU on the other end of the bus responds quickly, the issue is the wait time between the PC receiving data and sending the next packet. Is this a Python or OS limitation? I am not particularly familiar with high level languages or programming for OSes. |
I am having the same issue. In my case the delay is in the range of 10-25ms. I have not been able to isolate the problem. However, continuous writing directly to the serial port does not behave like this. I am using MinimalModbus (2.0.1) |
Can you please specify
|
Python version: 3.8.10 |
Python version: 3.7.3 Please find my initialization code below:Create devicemotor = minimalmodbus.Instrument( '/dev/serial0', 1) # port name, slave address (in decimal) Setup Modbus communication propertiesmotor.serial.close() |
Just for reference, I tested using PyModbus 2.5.3 and that did not show the same delay. |
I have a short script that requests some registers from two clients on the same serial adapter. Functionally I have data transferring with no issues, but looking at the bus on an oscilloscope the bus utilisation is very low. Requests are only being sent every 17ms, despite my client responding to the request within 5ms. This leaves ~10ms of dead time between receiving a packet and sending the next request, regardless of baud rate (assuming it's fast enough to do all the comms within that 17ms period).
Is this something that is configurable?
Thanks!
The text was updated successfully, but these errors were encountered: