Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
A radar may communicate reliably alone and become intermittent when several units are connected. Radar RS485 commissioning should introduce devices in controlled stages. This makes an address conflict or a wiring change easier to locate than repeatedly adjusting all instruments on a complete network.
Prepare a physical and logical device schedule
List each instrument's tag, serial identity, configured address and serial settings. Show its position on the actual cable route. A drawing of PLC tag names alone cannot reveal duplicated addresses or an unintended branch in the physical network.
Use the electrical and serial-line guidance applicable to the installation. Identify the trunk ends and approved termination and biasing arrangement. Do not add resistors to every device or change grounding from memory; follow the reviewed network design and equipment instructions.
A staged radar RS485 commissioning sequence
- Verify one identified radar on the intended interface using read-only requests.
- Set and record its approved address and communication parameters.
- Add the next verified unit and check both identities before expanding further.
- Test the completed segment at its intended polling load and record errors and recovery.
| Result | Useful next investigation |
|---|---|
| Fails alone | Unit power, interface version, wiring and serial settings. |
| Fails after addition | New wiring, duplicated address and interaction with the segment arrangement. |
| Fails under load | Polling schedule, response timing and physical signal quality. |
| Wrong identity | Address schedule, gateway routing and the actual device answering the request. |
Preserve the last working configuration and the exact change that preceded a fault. Avoid a sequence of undocumented baud-rate, timeout and wiring changes that leaves no reproducible starting point.
Confirm the output version in the purchase order
The METRAVON MV-RD12 requires the appropriate electronics for RS485/Modbus communication. Do not assume a HART unit provides an additional RS485 connection. State the desired supply and interface together when ordering.
Once communication is stable, use the register-mapping checks to verify what each returned value means. Physical connectivity and correct level interpretation are separate acceptance steps.
Q1. Does a changing number prove that the requested radar answered?
No. Establish device identity through supported readback or controlled isolation. Two instruments with a shared address can make an apparent response misleading.
Q2. Can repeated retries be used to hide intermittent failures?
Retries may be part of the designed protocol handling, but persistent errors still need investigation. Define data age and invalid-state behaviour so repeated retries do not present stale level as current.
Summary
Expand the segment from known working devices and preserve the address schedule. Send the network drawing and required MV-RD12 interface before finalising the order.
