RS-485 and Modbus RTU: Practical Wiring Guide

Separate the electrical interface from the protocol

RS-485 defines an electrical interface; Modbus RTU defines messages carried over it. Matching terminals do not guarantee compatible communication. Record baud rate, parity, stop bits, device address, function codes and the register map before connecting equipment. Keep these settings in one commissioning table.

Record how the manual expresses register addresses. A human-readable label such as 40001 may differ from the starting address transmitted in the request. Signed values, decimal scaling and the word order of values occupying two registers must also be explicit. A valid CRC proves that a message passed its integrity check; it does not prove that the application has interpreted a pressure or temperature correctly.

Document the trunk, termination and idle behavior

An understandable starting point is a trunk passing through the devices with short branches to each transceiver. Termination requirements depend on propagation delay, driver edge speed and network geometry. Where termination is needed, place it at the physical ends of the trunk and select it for the cable impedance. Enabling a termination switch on every device can overload an otherwise workable network.

Check the transceiver data sheet for its behavior with an idle or disconnected input. If external bias is necessary, calculate it together with termination and receiver loading rather than copying one resistor pair onto every board. Show which node provides bias and which locations terminate the cable. This installation drawing becomes essential when a maintenance team replaces a device with a different model.

Plan the signal reference and protection paths

Differential signaling does not give the receiver an unlimited common-mode range. Devices powered from separate cabinets may sit at different potentials. Distinguish the signal reference, cable shield and protective earth instead of treating them as interchangeable wires. Decide whether isolation is appropriate after reviewing the grounding arrangement, cable route and expected disturbances of the actual installation.

On the PCB, draw transient-current paths before selecting protection. For an isolated port, check the power barrier, board clearances and debug connectors that might bridge it. Define immunity tests for the product environment; an industrial connector alone does not establish protection performance.

Tie direction control to actual transmission completion

A half-duplex driver must stop driving at the right instant. Writing the final byte into a UART buffer does not mean its final stop bit has left the pin. Use the peripheral transmission-complete indication when controlling DE. A late switch back to reception may lose the beginning of a fast response; switching too early can damage the final byte of your own request.

Implement RTU frame separation and character timing using the speed-dependent rules in the official serial-line guide. A general task delay may become inconsistent under processor load. Keep separate counters for timeouts, CRC failures, protocol exception responses and application conversion errors. These are different observations and lead to different investigations. Logging them separately avoids treating an unsupported register as if it were an intermittent cable fault.

Example: Commission a three-device measurement bus

Consider a controller reading two temperature devices and an energy meter. Start with one device and a short cable. Add the real cable, remaining devices and switching cabinet loads in separate steps. Run the same number of queries at each step, recording latency, retries and error categories. This makes the effect of each installation change visible instead of relying on a vague impression that communication improved.

Build the polling schedule around response time as well as baud rate. An unavailable energy meter can delay both temperature readings if its long timeout is repeated on every cycle. A limited retry policy followed by a slower retry interval for a failing node can protect the freshness of other readings. Define the maximum acceptable data age for the application, then test it with one device deliberately disconnected.

Collect evidence before changing components

Do not assume that A and B labels are used identically by every manufacturer. Compare each product document with the transceiver polarity definition. Resistance checks on an unpowered bus and waveform checks on an operating bus answer different questions. Plan the measurement reference too: an earth-referenced oscilloscope probe can create an unintended connection. Use a suitable safe measurement method for the installation.

Include cable type, routing, addresses, termination locations, firmware versions and initial diagnostic counters in the commissioning record. Observe normal machine activity, reconnects and power cycles. Avoid universal distance or device-count guarantees; validate the selected equipment and the complete network together.

• Verify unique addresses and matching serial-port settings.
• Mark the trunk, branches and termination positions on the installation drawing.
• Test a disconnected node, power restoration and normal cabinet switching activity.

Conclusion and next step

A dependable Modbus installation combines documented wiring with explicit data interpretation and repeatable tests. Verify the physical link and the application values separately so each diagnostic result has a clear meaning.