What Is HART Protocol, and How Does It Work for Industrial Instrumentation?

Detailed Explanation

HART was developed in the 1980s specifically to add digital communication to the 4-20mA current loop that already dominated process instrumentation, without requiring plants to rip out and rewire their existing analog infrastructure. That backward compatibility is still the reason HART remains the most widely deployed field-instrument protocol in industrial plants today, even though purpose-built digital fieldbuses have existed for decades. The FieldComm Group (formed from the merger of the HART Communication Foundation and the Fieldbus Foundation) now maintains the HART specification.

FSK over the current loop

A standard 4-20mA loop represents a process variable, such as pressure, flow, or temperature, as a current proportional to the measured range: 4 mA corresponds to 0% of range, 20 mA to 100%. HART adds a small AC signal on top of that DC current, using frequency-shift keying (FSK) based on the Bell 202 modem standard. According to FieldComm Group documentation, a logic 1 is represented by a 1200 Hz tone and a logic 0 by a 2200 Hz tone, transmitted at 1200 bit/s.

Because the two tones are symmetric around the DC current and the transitions between them are phase-continuous, the average value of the FSK signal over a bit period is zero. The 4-20mA analog reading passes through unaffected, and the digital signal rides on top of it as a small ripple, approximately 1 mA peak-to-peak according to Analog Devices' HART interface application notes, that an ordinary analog meter simply doesn't resolve.

This is the core design idea that distinguishes HART from every other protocol covered elsewhere on this site. RS-485 and CAN bus are digital-only physical layers built for new installations; HART deliberately shares a wire with an existing analog signal so a plant can adopt digital diagnostics and configuration without discarding decades of installed 4-20mA wiring, terminal blocks, and marshalling cabinets.

Point-to-point mode

In point-to-point mode, a single HART field device shares its loop with a single host (a control system analog input, a handheld communicator, or both). The 4-20mA current still represents the primary process variable exactly as it would on a non-HART loop, and the FSK channel carries additional data alongside it: device diagnostics, secondary variables, tag names, and configuration commands. This is the mode used when a plant wants to keep its existing analog control strategy but gain digital access to a transmitter for commissioning, calibration checks, and predictive-maintenance diagnostics, typically through a handheld HART communicator or a HART modem connected to a laptop.

A control system input that only reads the 4-20mA analog value, using a plain shunt resistor and ADC as described in sensor signal conditioning basics, still works correctly on a HART loop; it simply never sees the digital data riding on top of it.

Multidrop mode

In multidrop mode, several HART devices share the same two-wire loop, addressed individually rather than distinguished by current level. To make this possible, every device on a multidrop loop is configured to a fixed current, typically 4 mA, so the analog value carries no information; all process data, for every device on the loop, moves entirely over the digital FSK channel instead. The HART addressing scheme reserves address 0 for point-to-point (single-device) operation and typically supports addresses 1 through 15 for multidrop devices sharing one pair of wires, though practical installations are usually kept well below that ceiling because of loop current budget and polling-time constraints.

Multidrop trades the immediacy of a live analog signal for wiring economy: a single twisted pair and one set of intrinsic-safety barriers can serve multiple transmitters, which matters in remote or hazardous-area installations where every additional cable run and barrier adds material and certification cost.

Why HART persists in brownfield instrumentation

Foundation Fieldbus and PROFIBUS PA were both designed as clean digital replacements for the 4-20mA loop, and where an installation is being built from scratch, either can offer higher data rates and richer device models than HART provides. In practice, most industrial plants are not built from scratch; they are extended and retrofitted around instrumentation, cabling, and control systems that were installed years or decades earlier. HART's defining advantage is that it does not force a choice between the two: a HART transmitter can be dropped into a loop that a legacy analog controller still reads as a plain 4-20mA signal, while a HART-aware host, on the same wires, extracts diagnostics and configuration data the analog-only equipment simply ignores.

That coexistence is why HART transmitters remain the default choice for routine replacement and expansion work in plants that were never migrated to a full digital fieldbus, and why HART is functionally distinct from the multidrop digital buses already covered on this site, such as RS-485-based Modbus RTU or CAN bus: those protocols were never designed to share a wire with a legacy analog signal in the first place.

Practical Examples

A process engineer replacing a failed pressure transmitter on an existing 4-20mA loop installs a modern HART-capable transmitter in point-to-point mode. The control system continues reading the 4-20mA analog signal exactly as before, no configuration change required on the control system side. Separately, a technician connects a handheld HART communicator across the loop's terminal resistor to read the transmitter's diagnostics, adjust its damping and range, and confirm its serial number, all without interrupting the analog reading the control system depends on.

In a tank farm with eight temperature transmitters sharing a single conduit run back to a remote I/O cabinet, an engineer configures all eight transmitters for multidrop mode, each with a fixed current and a unique HART address from 1 to 8. A HART multiplexer at the cabinet polls each device in turn over the shared pair, and forwards temperature readings to the plant historian over Modbus TCP. This avoids running eight separate twisted pairs and eight sets of intrinsically safe barriers into a hazardous-area tank farm.

Design Considerations

• Loop resistance: a HART modem needs enough voltage developed across the loop's resistive load to read the superimposed FSK signal reliably. HART documentation commonly cites a minimum loop resistance of approximately 230 Ω between the transmitter and the power supply, with a 250 Ω resistor commonly used in practice since it is a standard value that gives 1-5 VDC across the resistor at 4-20mA. Loops with too little resistance, for example a control system input configured for a very low burden voltage, can attenuate the HART signal below what a communicator can decode even though the 4-20mA analog reading looks perfectly normal.
• Cable and capacitance limits: HART communication is more sensitive to cable capacitance and length than the underlying 4-20mA analog signal is. Long cable runs, especially with multiple devices in multidrop mode, can attenuate the FSK signal enough that the analog value still reads correctly while HART communication becomes unreliable or fails outright. Follow the cable length and capacitance guidance in the transmitter's own installation documentation rather than assuming any 4-20mA-rated cable is automatically suitable for HART.
• Power supply filtering: switching power supplies and some analog input cards inject noise near the HART FSK band or present a low AC impedance that attenuates the signal. A HART-rated power supply and appropriate loop filtering avoid this; a supply that was never validated for HART use can pass a functional 4-20mA test while still corrupting HART communication.
• Host and PLC input card compatibility: not every analog input card that reads 4-20mA correctly is HART-transparent. Some cards filter or clamp the signal in a way that attenuates the FSK tones enough to prevent communication, even though the 4-20mA value is read correctly. Confirm HART pass-through compatibility on the specific input card model before relying on HART diagnostics through a PLC or DCS analog input.
• Primary vs secondary master conflicts: the HART specification allows two masters on a loop simultaneously, conventionally a control system as the primary master and a handheld communicator as the secondary master. Both can poll and, in principle, write to the device. Leaving a handheld communicator connected and issuing commands while the control system is also actively polling the same loop can create write conflicts or intermittent communication; disconnect handhelds once configuration work is done.
• Zeus Design builds firmware for HART-capable field instruments and PLC/DCS integration layers, including HART command set implementation and the host-side handling required to pull diagnostic and configuration data into a plant network. Zeus Design's embedded firmware team supports both new instrument development and retrofit integration work.

Common Mistakes

• Assuming a working 4-20mA reading means HART is working: because HART's digital signal averages to zero, a loop can pass a completely normal analog reading while HART communication is degraded or absent, due to low loop resistance, excessive cable capacitance, or a non-HART-transparent input card. Verify HART communication independently with a handheld communicator or modem rather than inferring it from the analog value.
• Under-sizing loop resistance: configuring a control system input for very low burden voltage, or omitting the loop resistor entirely on a bench setup, starves the HART modem of the signal amplitude it needs. If a handheld communicator cannot see a device that is otherwise reading correctly, loop resistance is one of the first things to check.
• Mixing multidrop addressing carelessly: assigning a duplicate HART address to two devices on the same multidrop loop, or leaving a device at address 0 (point-to-point) while wiring it into a multidrop loop, produces address collisions or a device stuck outputting a live analog current onto a loop meant to be entirely digital. Every device on a multidrop loop needs both a unique nonzero address and its current fixed for multidrop operation.
• Leaving a handheld communicator connected as an unintended second master: a forgotten handheld communicator left connected in secondary-master mode can intermittently interfere with polling from the primary host, producing communication errors that look like a wiring or device fault rather than a master conflict.
• Treating WirelessHART as a drop-in wired HART replacement: WirelessHART shares HART's command set but runs over an IEEE 802.15.4-based mesh network rather than a current loop, and a wired-only transmitter needs a WirelessHART adapter to join a mesh network. Planning a wireless retrofit without accounting for adapter cost, mesh network commissioning, and battery or loop-power budgeting for the adapter is a common scoping mistake.