Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
Level data integration fails when different systems attach different meanings to the same reading. A METRAVON radar can report a correct value while the PLC applies the wrong span, the historian stores the wrong unit or a dashboard presents an old value as current. Define the measurement and its status at each interface before connecting more systems.
Choose one place for each conversion
Draw the actual chain from transmitter to receiver and from receiver to each consumer. For example, an MV-RD14G with the selected 4-20 mA/HART electronics can feed a compatible PLC input; the PLC can then provide approved data to a historian or monitoring system. A separately specified RS485/Modbus RTU version needs a compatible receiver and its own communication setup.
Decide whether the transmitter provides distance, level, percentage or another supported variable. Record the reference and units. If the PLC calculates volume, it needs the correct tank table; if another system calculates volume again from that result, the calculation can be applied twice. Keep the original measured variable available where practical so that later conversions can be audited.
| Record | Meaning to agree |
|---|---|
| Measurement tag | Which physical vessel and instrument supply the value, including the analog channel or digital device address. |
| Variable and unit | Distance from the antenna reference is different from height above a tank datum; metres, millimetres and percent cannot be interchanged without conversion. |
| Transformation | Where scaling, offsets, tank tables or density calculations occur, with the active revision identified. |
| Validity and age | How a device fault, communication failure or old reading is represented and which system supplies the timestamp. |
Level data integration through a current input
The transmitter's analog span and the receiver's engineering span must describe the same variable. As an illustrative linear mapping, consider 4-20 mA assigned to a level of 0-8 m. The conversion is level = (current - 4 mA) / 16 mA x 8 m. A current of 10 mA corresponds to 3 m. This example is a scaling calculation, not a required span for a METRAVON model.
| Test current | Expected result for this example |
|---|---|
| 4 mA | 0 m level. Verify that the receiver does not instead display the empty distance. |
| 12 mA | 4 m level. This intermediate point helps reveal an incorrect span or an extra conversion. |
| 20 mA | 8 m level. Check the units and displayed result in each dependent system. |
Known-current tests check the electrical and software mapping from the injection point onwards. They do not prove that the radar is measuring the product surface correctly. Keep the process measurement check separate, and use signal simulation only through an approved commissioning procedure.
An ordinary analog input may read current without obtaining HART diagnostics. If remote status or configuration is required through HART, confirm the interface, compatible tools and variables. Do not assume that the presence of a HART-capable transmitter makes every connected system HART-capable.
Modbus requires the delivered device map
For RS485/Modbus RTU, agree on address, serial settings, function and register interpretation using the supplied documentation. Modbus registers are 16-bit quantities; a multi-register value needs the specified representation and ordering. Do not copy a floating-point format or address offset from a different instrument simply because both communicate over RS485.
Check the value and status definitions together. A successful reply proves that a message was received, not that the value represents a valid echo or the intended engineering unit. If the device does not provide a desired diagnostic through that interface, document the limitation instead of creating an apparently healthy status in the gateway.
A recent message can contain an old measurement
Distinguish sensor validity from communication freshness. A transmitter may hold its previous value after losing the echo while continuing to reply to requests. Conversely, a healthy sensor may be unreachable because the network has failed. A single communication flag cannot fully describe both conditions.
Define when each consumer considers a reading stale, based on the expected update pattern and process need. Show the last valid value only with its age and condition made clear. Replacing invalid data with zero can falsely suggest an empty vessel; leaving a retained number marked healthy can be equally misleading.
Record where time is assigned. If the sensor has no measurement timestamp, a logger's acquisition time must not be described as a timestamp originating inside the instrument. Where the system buffers data, distinguish the original acquisition time from the later upload time. Test delayed records and clock settings before relying on event order.
Test a change across every consumer
A range change at the transmitter can affect PLC display, alarms, trends and reports. Keep a list of those consumers and compare them at known points after changes to units, span, variable assignment or a tank table. Document which results were calculated and which came from an independent physical reference.
For an MV-RD21S silo measurement, label a converted inventory estimate distinctly from the local surface level. The integration software must not turn a level tag into an apparently direct mass measurement. Preserve assumptions about material profile and density with any calculation.
Keep configuration writes separate from routine monitoring. Identify which authorised system may change instrument settings and retain a recoverable configuration. An added dashboard should not introduce an undocumented route for changing a control measurement.
Questions about shared level data
Q1. Can several systems read the same analog loop independently?
Do not add receivers without checking the electrical design. Input types, isolation and total loop burden matter. Use an appropriate distribution or system interface where required, and verify that the extra connection does not disrupt the original measurement or HART communication.
Q2. Is it enough to test only the PLC screen?
No. A historian, gateway or report can apply a separate unit conversion, filter or timestamp. Compare each required consumer using the same identified source condition. Include loss and recovery of communication so that retained values are not mistaken for new measurements.
Q3. What information is needed to quote the transmitter interface?
Specify the instrument model, required variable, receiving hardware, power arrangement and whether diagnostics must be read remotely. For Modbus, request the applicable register document; for HART, identify the intended host or service tool. List any required accessories instead of assuming they are included with the sensor.
Summary
A reliable shared value retains its identity, unit, validity and time as it moves between systems. For an interface review, send the proposed signal path and receiving-device details. Resolve scaling and status handling before adding another dashboard or report to the same measurement.
