Modbus RTU Radar Level Integration: Register and Fault Testing

Modbus RTU integration fails most often at the boundaries between documents, wiring and software: an address interpreted as zero-based instead of one-based, swapped 32-bit words, incompatible parity, missing biasing or a status register that the PLC ignores. A displayed number can still be wrong by a factor, unit or timestamp. The commissioning plan should define the exact physical layer, serial settings, register map, data types, scaling and failure response for the offered radar firmware, then test each layer from the device to the operator screen.

Confirm the physical RS485 network

Record two-wire or four-wire arrangement, polarity, shield connection, grounding, isolation, cable type, route and total length. Use one controlled grounding method and avoid parallel high-noise power routes.

Place termination at the physical ends of the trunk and apply biasing according to the master or gateway design. Unplanned star branches and excessive stubs can create intermittent errors that appear only at full traffic.

Control serial settings and addresses

Set baud rate, data bits, parity, stop bits and slave address from an approved schedule. Confirm that every device address is unique before connecting the full segment.

Record whether the gateway changes unit identifiers or encapsulates Modbus TCP. Configuration tools and PLC code must refer to the same final network architecture.

Verify the exact register map

Use the manual for the delivered model and firmware. Document function code, register number, zero- or one-based notation, data type, word order, byte order, scale and engineering unit.

Map distance, level, signal quality and device status separately. Do not infer register meaning from a related transmitter or a screenshot without revision identification.

Design polling and error handling

Set polling intervals within device and network capacity. Monitor timeout, CRC error, exception response and consecutive failure count rather than retrying indefinitely at maximum speed.

The PLC should mark data invalid or stale after a defined age and execute the documented safe response. It must not convert a communication failure into zero level.

Protect write functions

Use read-only polling for routine supervision unless remote configuration is justified. Restrict write access, document permitted registers and prevent broadcast writes to operational settings.

Back up radar and PLC configurations before changes. Record who changed an address, range or damping value and verify the measurement after every authorized write.

Run an end-to-end acceptance test

Compare known radar distance and level with raw register values, engineering conversion, PLC tag, HMI and historian. Test negative, boundary and decimal cases where the data type permits them.

Disconnect one device, reverse a test lead under controlled conditions and interrupt the trunk to verify diagnostics and recovery. Store packet or register evidence with the final address schedule and code revision.

Baseline network performance

Before adding the radar segment to normal operation, record response time, timeout count, CRC errors, scan utilization and gateway diagnostics with all planned devices online. Repeat the observation during expected electrical noise and peak polling. Define alert thresholds and the person responsible for investigating deterioration. This baseline distinguishes a future sensor fault from a shared RS485 network problem and helps prevent technicians from changing an otherwise correct slave address, register or instrument configuration to compensate for wiring or traffic defects.

Engineering checklist

Document RS485 topology and grounding.
Freeze serial settings and unique addresses.
Verify register base, type and byte order.
Carry value age and status to the PLC.
Restrict and audit write access.
Test normal data, faults and recovery end to end.

Frequently asked questions

Why is the value exactly wrong by a large factor?

Check data type, byte order, word order, scale and engineering units.

Can every device have termination enabled?

No. Termination normally belongs only at the two physical ends of the RS485 trunk.

What should the PLC do on timeout?

Mark the value stale or invalid and apply the approved process response rather than showing zero as a measurement.

Need a project-specific review? Send process data, drawings, photographs and acceptance criteria through our contact page.