Industrial Networks and OT · #87
Online Modbus RTU Polling Time Calculator
Calculates how many milliseconds it takes to read every device on an RS-485 line once.
- Data is processed in your browser and not sent to a server
Tool
What does this tool do?
As devices are added to an RS-485 line, each device's data updates less often. Reading 10 registers at 9600 baud takes over 60 ms with the device's response delay; on a 30-device line a value may take several seconds to update. The tool adds frame sizes, Modbus's 3.5-character silent interval and device delay.
How to use it
- Choose serial settings (baud, data bits, parity, stop bits) and function code.
- Enter registers per request, number of devices and requests per device.
- Enter device response delay, extra wait between polls and target cycle time; press Run.
Fields
- Baud rate
- Data bits
- Parity
- Stop bits
- Function code
- Registers/bits per request
- Max 125 for FC03/04.
- Devices
- Requests per device
- Device response delay
- From end of request to start of response.
- Extra wait between devices
- Setting in the master software.
- Target cycle time
- Optional.
Worked example
| Input | Value |
|---|---|
| Baud rate | 9600 |
| Data bits | 8 |
| Parity | None (N) |
| Stop bits | 1 |
| Function code | 03 Read holding registers |
| Registers/bits per request | 10 |
| Devices | 10 |
| Requests per device | 1 |
| Device response delay | 20 |
| Extra wait between devices | 0 |
| Target cycle time | 1000 |
Expected result: At 9600 8N1 a character takes 1.042 ms; a 10-register request is 8 + 25 bytes, 61.7 ms with silence and 20 ms delay; a 10-device scan 617 ms.
Within the 1 s target. Device response delay is a third of the total; lower it if devices allow. Moving to 19200 baud halves transmission time but not delay.
Second scenario
| Input | Value |
|---|---|
| Baud rate | 115200 |
| Data bits | 8 |
| Parity | Even (E) |
| Stop bits | 1 |
| Function code | 03 Read holding registers |
| Registers/bits per request | 50 |
| Devices | 30 |
| Requests per device | 2 |
| Device response delay | 5 |
| Extra wait between devices | 0 |
| Target cycle time | 500 |
Expected result: 115200 8E1, 30 devices × 2 requests × 50 registers: 19.3 ms per request, cycle 1,157 ms; the 500 ms target is exceeded.
Method and assumptions
Character time = (1 start + data + parity + stop) / baud. Request frame 8 bytes; response 5 + 2 × registers (5 + bits/8 for FC01/02). Silent interval 3.5 characters (fixed 1.75 ms above 19200 baud).
Request time = (request + response) × character + 2 × silence + device delay. Cycle = devices × requests × request time + devices × extra wait.
Using the result and troubleshooting
If the cycle target is exceeded: read consecutive registers in one request, raise baud, split the line or use a Modbus TCP gateway. Set the timeout to 2–3 × request time.
Limits and common mistakes
- Error, retry and timeout times, master processing time and write operations are not included.
Frequently asked questions
Is 8N1 compliant with Modbus?
The Modbus RTU specification recommends 2 stop bits (11 bits) without parity, but 8N1 is common in the field and usually accepted. All devices must use the same settings.
Related tools and service
- Modbus Register Address ConverterConverts the register number in a device manual to the address your SCADA/PLC driver expects.
- PLC Data Buffer SizingCalculates how large the on-site buffer must be so data is not lost when the central link drops.
Related service: PLC–PLC and PLC–Server Integration