RS485 Modbus RTU: Wiring, Register Checks and Commissioning

RS485 Modbus RTU connects many industrial instruments to a PLC, RTU or data logger, but the label alone does not guarantee communication. RS485 describes the electrical interface; Modbus RTU defines the serial message exchange. A working installation needs compatible wiring, matching serial settings, a valid request and the correct interpretation of the returned data. Test those layers separately so a register-format problem is not mistaken for a damaged sensor.

Specify the RS485 Modbus RTU equipment pair

For a water-level station, an RS485 configuration of the METRAVON MV-RD12T radar water level meter can be assessed with a compatible PLC or the TG501 RTU listed in the METRAVON catalogue. Obtain the radar's ordered electrical version, terminal drawing and register map, plus the controller's supported polling and decoding functions. An analog-output version must not be assumed to include the same serial connection.

Before delivery, ask for one documented read example using the selected firmware: device address, serial format, function code, starting register, register count, returned value and engineering unit. This small acceptance item is more useful than a general statement that both devices support Modbus. Keep the example with the instrument's serial number and configuration backup.

Prove the bus before adding all instruments

Begin with one powered instrument and one polling controller. Ordinary Modbus RTU serial operation uses one active requester at a time, with a unique address for each responding device. Match baud rate, parity, data bits and stop bits, then allow the documented response timeout and frame timing. A service laptop issuing requests alongside the PLC can create collisions.

Check whether the interfaces are two-wire or four-wire. Trace terminals from the manufacturers' drawings: A/B names are not sufficient evidence that two suppliers use identical polarity labels. Signal common, cable shield and protective earth serve different purposes; connect them according to the isolation and grounding design, not by joining every terminal marked ground.

For the usual two-wire bus, use a trunk with short device connections rather than an arbitrary star. Where termination is required, place it at the physical ends and match it to the cable and interface design; 120 ohms is common, not a reason to install a resistor at every device. Check for built-in termination before adding external parts. Bias networks also load the bus. Cable length, data rate, electrical loading and noise determine the viable installation; a quoted maximum distance is not a site guarantee. For the electrical trade-offs, see the RS485 termination guidance.

For long outdoor runs, include surge protection, cable routing, bonding and any required galvanic isolation in the electrical design. A bench link that works with a short USB adapter does not validate a field cable beside motor wiring. Power down under the site procedure before changing wiring, and never apply an insulation tester across connected instrument electronics.

Read the intended value, not just any successful response

A Modbus register holds 16 bits. The device map determines whether a measurement occupies one register or several, whether it is signed, and how it becomes an engineering value. Function 03 reads holding registers; function 04 reads input registers. A controller's displayed register notation may differ from the zero-based address in a request. Confirm the convention rather than subtracting one from every address automatically.

For multi-register values, confirm the documented word order separately from the byte order within a register. Then apply the specified scale and unit. As a hypothetical example, an unsigned raw value of 2468 with a documented scale of 0.001 m per count represents 2.468 m. That example is not an MV-RD12T register definition. The Modbus Application Protocol Specification V1.1b3 and Serial Line Protocol and Implementation Guide V1.02 define protocol behaviour; the instrument manual defines its measurements.

Compare the decoded result with the instrument's local or configuration display and a suitable independent reference. For radar, establish whether the variable is sensor-to-surface distance or level relative to a configured zero. Correct bytes with the wrong variable can invert the meaning of a rising water surface. Save the raw response alongside the interpreted value during commissioning.

Commission the operating sequence, including failure

1. Read a documented, non-command register from one instrument. Verify the expected value without changing its calibration or output settings.
2. Add instruments individually, maintaining an address list and a record of the termination positions. Recheck operation after each addition.
3. Choose a polling interval that the complete request-response cycle can sustain, including slow or absent devices. Bound retries so one failure does not block every other measurement.
4. Under an approved test plan, interrupt communication and verify that stale data is identified. A retained last value must not continue to appear as a fresh successful measurement.
5. Restore the link and test controller and instrument restarts. Confirm configuration retention, recovery time and the final display's units and sign.

A valid CRC checks message integrity; it does not prove that the register, units or sensor reading are correct. Similarly, communicating once is not an endurance test. Record successful polls, errors and data age over the site's relevant operating cycle, including switching loads or network transitions where applicable.

Questions about controllers and gateways

Q1. Can an Ethernet adapter replace a Modbus gateway?

Only if it performs the function the system needs. A serial tunnel carries bytes; a Modbus RTU-to-TCP gateway translates the transaction framing and manages serial requests. Confirm the controller mode, device-address mapping and timeout handling. The TG501 product documentation lists Modbus RTU and Modbus TCP among its protocol options. That list alone does not establish the required gateway mode. Confirm the supplied firmware and its supported transaction routing with the actual instrument before accepting the configuration.

Q2. Why does the same address work in one software tool but not another?

The tools may expect different register notation or apply an offset internally. Compare their transmitted requests, not only the number shown in the setup window. Check function code and register count too. Use the device's documented read example to establish the correct convention before commissioning the remaining tags.

Q3. What should I send when requesting integration support?

Provide both model and firmware versions, the electrical option, terminal drawing, cable layout, serial settings, register-map revision and a short request-response log. Include the expected physical value and the value displayed by the PLC. Send these details to METRAVON for an interface review; they help distinguish an unsupported function from a wiring or decoding error.

Summary

Commission from the physical link to a verified engineering value: one instrument first, then the complete bus, then restart and failure behaviour. An RS485 label is not a register map, and a successful response is not proof of a correct level reading. Preserve the tested configuration and show communication quality alongside the measurement.