Shopfloor

HART protocol explained: smart instruments on 4-20 mA wiring

How the HART protocol overlays digital diagnostics on analog current loops, what DD files do, and when to migrate to HART-IP or Ethernet-APL.

The Highway Addressable Remote Transducer (HART) protocol is the process industry's answer to a hard constraint: millions of installed 4–20 mA loops that work, are paid for, and cannot be rewired without shutdowns nobody wants. HART overlays a digital signal on the same two wires using frequency-shift keying — 1,200 Hz and 2,200 Hz tones representing bits — at 1,200 baud, without disturbing the analog measurement the control system reads. The loop keeps controlling exactly as before, while asset-management software can now interrogate each instrument for its identity, range, diagnostics, and secondary measurements.

What the digital channel carries

Every HART device exposes a digital dataset alongside its analog primary variable: device tag, manufacturer and model, range and damping configuration, device status and extended diagnostics, and often secondary variables (a temperature transmitter may report sensor-2 value or electronics temperature). A handheld communicator or a multiplexer in the cabinet reads and writes this data, so technicians can re-range a transmitter, check for sensor drift, or read "replace sensor soon" warnings without breaking the loop.

Device descriptions (DD files) define how host software interprets each instrument's parameters. In practice, this means keeping the DD library current in your asset-management tooling is a real maintenance task — an unknown DD revision turns a smart instrument back into a dumb one from the host's perspective. Standardize on one asset-management package per site and update its library on a schedule, not when someone notices a gap.

HART-IP and the Ethernet migration

Classic HART's 1,200-baud multidrop mode is too slow for anything resembling real-time data collection, so modern architectures concentrate HART through multiplexers,WirelessHART gateways, or I/O cards with built-in HART modems, then carry the data upstream over Ethernet — increasingly as HART-IP. The instrument stays wired exactly as it is; only the backhaul modernizes.

For greenfield process units, the question is whether to lay 4–20 mA plus HART at all. Single-pair Ethernet with APL now carries power and 10 Mbit/s Ethernet to field instruments in hazardous areas, which makes native Ethernet instruments with richer data models (and OPC UA companion specs) the forward-looking choice. The pragmatic rule: keep HART where loops already exist and work, since a HART-enabled brownfield instrument delivers 80% of the diagnostic value at zero wiring cost; specify Ethernet instruments for new units where the infrastructure can be built once.

Getting value from HART you already own

Most plants with HART instruments capture a fraction of the available value. The usual gaps: HART-capable I/O cards installed but never licensed or wired for digital pass-through, no asset-management software connected, or DD libraries years out of date. An audit of one process unit — which instruments are HART-capable, which channels pass digital data, what the host can actually read — typically uncovers quick wins: re-ranging without work permits for loop breaking, early warning of sensor degradation, and verified as-built instrument databases. Pair it with a brownfield OT asset inventory effort and the instrument data populates itself.

Cite this page: HART protocol explained: smart instruments on 4-20 mA wiring, Shopfloor, 2026-10-04. https://shopfloor.space/articles/hart-protocol-explained/

Related