Modbus Modes and Timing Workbench
Compare RTU, TCP, and ASCII timing with character gaps, frame expansion, and polling throughput.
Modbus Modes and Timing Workbench
Compare the same read request in RTU, ASCII, and TCP. The timeline shows which part of the cycle is bytes on the wire, required silence, device turnaround, or network latency.
Stage 1: select the transport mode
RTU and ASCII use serial character timing. TCP uses an MBAP header and depends more on network latency than byte time.
RTU
Binary serial Compact frames with CRC-16 and strict silent intervals for frame boundaries.TCP
Ethernet/IP MBAP header replaces serial timing and CRC; throughput is usually latency-limited.ASCII
Hex text serial Human-readable colon and CR/LF frame, but each binary byte becomes two hex characters.What to notice
Core idea
RTU frame boundaries are timed silence, not bytes. ASCII frame boundaries are visible delimiter characters. TCP frame boundaries come from MBAP length over a stream.
Common trap
Raising baud rate helps serial byte time, but slow device turnaround and required gaps can still dominate small polls.
Planning use
Multiply one poll cycle by the number of devices to estimate scan time before tuning timeout values or polling rates.
Quick reference and technical notes
Numbers are planning estimates for a read-holding-registers transaction. Real systems also need timeout margins, retries, gateway delay, and device-specific processing time.