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

Max 125 for FC03/04.

From end of request to start of response.

Setting in the master software.

Optional.

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

  1. Choose serial settings (baud, data bits, parity, stop bits) and function code.
  2. Enter registers per request, number of devices and requests per device.
  3. 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

InputValue
Baud rate9600
Data bits8
ParityNone (N)
Stop bits1
Function code03 Read holding registers
Registers/bits per request10
Devices10
Requests per device1
Device response delay20
Extra wait between devices0
Target cycle time1000

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

InputValue
Baud rate115200
Data bits8
ParityEven (E)
Stop bits1
Function code03 Read holding registers
Registers/bits per request50
Devices30
Requests per device2
Device response delay5
Extra wait between devices0
Target cycle time500

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

Related service: PLC–PLC and PLC–Server Integration

Industrial online tools · See all online tools