Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
Two nearby tanks can have similar levels, allowing crossed inputs or copied display links to escape a visual check. PLC level tag verification must establish identity through the complete signal path. Matching numbers do not prove that the operator is looking at the intended tank.
Build a one-to-one identity record
Start at the physical instrument tag and record the cable, junction terminals, input channel, controller variable, display object and historian point. For a digital network, include device address and the relevant data mapping. Compare the installed record with the drawing rather than carrying over a previous project's channel list.
The METRAVON MV-RD12 can be ordered with an analogue/HART or RS485 interface. Use the actual configuration to decide what identifies the signal. A printed tank name on the display is editable text; it is not proof of the address or physical channel supplying the value.
PLC level tag verification needs a distinguishable event
Under an approved test arrangement, introduce or observe a change that can be associated unambiguously with one instrument. Check the expected tag and neighbouring tags at the same time. The purpose is to detect an unintended response elsewhere, not just confirm that one screen moves.
For signal simulation, identify where the test is injected. Simulation at a PLC software variable can validate display mapping but bypasses the field cable and input channel. A field-side test covers more of the electrical path, but still does not prove physical radar measurement. Keep those claims separate in the record.
| Checkpoint | Evidence of correct identity |
|---|---|
| Field assembly | Installed tag and model identification agree with the tank location. |
| Input channel | The intended physical or network input responds to the authorised test. |
| Operator display | The correct object follows that input; neighbouring tank objects do not. |
| Stored record | The historian stores the event under the correct asset and timestamp. |
Do not repair crossed signals by renaming screens alone
If the wiring or channel assignment differs from the approved design, resolve the discrepancy through the change procedure. A display rename can leave alarms, reports and control logic attached to the wrong tank. Review every consumer of the affected variable before accepting the correction.
After the test, restore the live signal and verify its identity again. Remove only the authorised temporary changes associated with this work. Record who witnessed the field location and who checked the receiving system so later maintenance can trace the test.
Q1. Is a correct 4-20 mA scale enough to approve the tag?
No. A perfectly scaled channel can still belong to another tank. Identity and scaling are independent acceptance checks.
Q2. Can a live tank be filled solely to create a test event?
Only within an approved operating test. Use an appropriate authorised method that does not compromise process limits or protection; do not improvise a level excursion for convenience.
Summary
Verify the asset behind the value before relying on it. Include the MV-RD12 interface, channel schedule and observed mismatch when requesting assistance with signal identification.
