HART Protocol for Level Instruments: What the PLC and Maintenance Tool Can Read

The HART protocol adds bidirectional digital communication to compatible field instruments. In a conventional point-to-point 4-20 mA/HART installation, the current carries the configured process value while a suitable host can exchange digital information with the transmitter. An ordinary analogue input can read the current, but it does not automatically acquire HART diagnostics.

What the HART protocol adds to a current loop

Classic wired HART uses frequency-shift keying based on Bell 202, with 1200 Hz and 2200 Hz signals. Its conventional FSK communication operates at 1200 bit/s. The digital signal is superimposed on the loop so that, in a correctly designed installation, it coexists with the DC current measurement.

This is useful when a plant wants to retain its analogue control signal while giving maintenance access to instrument identification, configuration and supported diagnostics. It does not mean every instrument publishes the same secondary variables or exposes every advanced setting through every host.

Basic communication and full device support are different

A host may identify a transmitter and read a primary variable using common functions while lacking a device-specific menu. More specialised access can depend on the correct device description or integration package and compatible software versions. Record the instrument revision and the actual host tool when requesting support.

Do not treat the availability of a generic HART driver as proof that a radar echo display, mapping command or configuration export is supported. Ask for a demonstration or documented function list for the particular combination. Likewise, a product stating HART compatibility does not by itself establish registration status in a third-party product registry.

For METRAVON MV-RD12, the published two-wire 24 V DC option combines 4-20 mA with HART. Specify the corresponding electronics when that is the intended interface. The separately offered RS485 configuration is a different communication route; it should not be wired or commissioned as a HART loop.

Why current can work while HART communication fails

Trace the digital path through the whole loop. An isolator or input can pass DC current without providing the required HART path. Check the documented impedance, available terminal voltage, cable and connection point before adding components. Noise and an unsuitable host connection can also prevent reliable communication.

A 250-ohm resistor is commonly seen in test arrangements, but it is not an instruction to add one to every installed loop. The existing input or other equipment may already supply the required load. Additional resistance also consumes voltage; verify the transmitter's operating margin at the required current using the actual loop documentation.

For a hypothetical 250-ohm resistor carrying 20 mA, Ohm's law gives a 5 V drop. That calculation describes the resistor only. It does not establish the minimum supply for an MV-RD12 or account for cables, barriers and the transmitter's own voltage requirement.

Do not change topology just to reach more devices

Point-to-point operation normally uses a separate current loop for each process value. Multidrop arrangements rely on addressed digital communication and can change the meaning of the loop current. Compatibility, address range, power and update behaviour depend on the supported revisions and devices.

Confirm an approved multidrop design before using it. Moving an instrument from normal analogue service into a digital arrangement can leave the PLC with a plausible but non-measuring fixed current. Do not infer a universal device count or an update interval from the word HART.

Q1. Will adding a HART modem change the PLC range?

An approved read-only connection does not require a range change, but the communication path and loop operating margin still need to be correct. Confirm the tool's mode and permitted connection point before attaching it. Write commands that change the transmitter's variable, range or output behaviour can affect the PLC signal; restrict those functions and record any authorised configuration change.

Q2. Can a good current reading prove the digital value is correct?

Check the variable assignment, units and scaling on both paths. A plausible current can represent a configured process value while the host reads a different available digital quantity or interprets its units incorrectly. Compare both values at the same operating condition and record their definitions. Do not adjust the analogue range merely to make two differently assigned quantities display the same number.

Q3. Can HART replace the need for measurement verification?

Remote access to settings and diagnostics is useful evidence, but it does not demonstrate that the radar is observing the required surface. Keep an appropriate physical reference comparison and trace the result through the local value and receiving system. If only communication was tested, record that limit instead of reporting the whole measurement as accepted.

Q4. What should a purchase request say about software?

Identify the transmitter model and revision, interface hardware, host software and the exact maintenance functions required. Ask which device description or integration package supports that combination and whether the requested functions have been demonstrated. Basic identification or a readable process variable does not prove that echo views, mapping or configuration export are supported. Confirm availability rather than listing every package type as an included deliverable.

Summary

Specify the current input, digital host and maintenance functions as separate requirements. Ask METRAVON to confirm the MV-RD12 electrical option and tool support before purchasing interface hardware.