HART Communication FAQ

This HART communication FAQ answers the questions instrument and automation technicians ask most: how HART works, what a HART communicator does, how HART rides on a 4-20 mA loop, and how HART calibration and HART-IP fit together. HART is the most widely deployed smart-instrument protocol in process automation, and every answer below is written answer-first so you get the short version in the first sentence, then the detail. For term-by-term definitions see the HART glossary, or start with what is HART.

HART basics

What is HART communication?

HART communication is a digital protocol that lets a smart field instrument and a host exchange data over the same two wires that carry a standard 4-20 mA analog signal. HART stands for Highway Addressable Remote Transducer, and it is an open, published industry standard managed by the FieldComm Group. It works by layering a small digital signal on top of the analog current loop, so you keep the proven 4-20 mA measurement while also reading configuration, diagnostics, and extra variables digitally. That dual nature is why HART has stayed dominant for decades.

How does HART work over a 4-20 mA loop?

HART works by superimposing a digital frequency-shift-keying (FSK) signal on top of the 4-20 mA analog current, using the Bell 202 standard. It encodes digital bits as two audio-range tones (1200 Hz for a "1" and 2200 Hz for a "0") whose average current contribution is zero, so the underlying 4-20 mA measurement is not disturbed. The analog value still represents the primary variable, while the FSK layer carries digital commands and replies at 1200 bits per second. In short, one pair of wires does two jobs at once: analog measurement and digital communication.

What is the difference between HART and 4-20 mA?

The difference is that 4-20 mA is a single analog signal, while HART adds a two-way digital conversation on top of that same signal. A plain 4-20 mA loop can only report one process value as a current level, with no identity, no diagnostics, and no remote configuration. HART keeps that analog current but layers digital data over it, so the same wires also carry the device tag, multiple variables, status, and the ability to write settings. Think of 4-20 mA as the speedometer and HART as the full dashboard plus a service port, all on one cable.

Is HART still used in 2026?

Yes, HART is still very widely used in 2026 and remains one of the most installed field protocols in process industries. The vast majority of smart 4-20 mA transmitters in oil and gas, chemical, water, and power facilities are HART-capable, and the installed base continues to grow each year. Newer variants like HART-IP and WirelessHART have extended the protocol to Ethernet and wireless mesh networks rather than replacing it. Because HART rides on the 4-20 mA wiring that plants already have, it stays the practical default for connecting and diagnosing smart instruments.

HART communicators and tools

What is a HART communicator?

A HART communicator is a handheld tool that connects to a HART instrument and lets you read and write its settings, view diagnostics, and verify its output. You clip it across the loop, and it talks to the device using HART commands to do things like change the range, set the tag, adjust damping, and trim the output. Technicians use one to commission, troubleshoot, and calibrate smart transmitters in the field. Traditional handhelds are often tied to specific vendors, while vendor-neutral tools like OmniBus aim to work across manufacturers.

Do I need a HART communicator for every brand?

Not necessarily, because most HART instruments respond to the same set of universal and common-practice commands regardless of brand. The HART standard defines universal commands (identity, primary variable, status) and common-practice commands (range, damping, units, loop test) that any compliant device supports, so a single communicator can do core work on instruments from many manufacturers. Brand-specific or device-specific features may require that vendor's device descriptor to fully expose every parameter. A vendor-neutral approach focuses on this shared, common-practice HART layer so one tool covers the whole bus instead of one handheld per manufacturer.

What is a HART device descriptor (DD)?

A HART device descriptor, or DD, is a standardized file that tells a host how to talk to a specific instrument model, including its menus, parameters, and special commands. Each manufacturer publishes a DD (and newer EDD variants) so any compliant host can present that device's full feature set without custom programming. The DD essentially describes what the device can do and how its data is organized, beyond the universal commands every HART device already supports. Hosts use DDs to show vendor-specific configuration screens for a given model.

Can OmniBus replace a traditional HART communicator?

Yes, OmniBus is built to replace a traditional single-vendor HART communicator with one vendor-neutral handheld that also records the work. According to the OmniBus product brochure, it communicates with HART field instruments regardless of manufacturer, organizes commands by device family (Temperature, Level, Pressure, PID Control), and runs guided Configure, Calibrate, Loop Test, and Record workflows. Beyond a communicator, it captures As-Found and As-Left calibration as an append-only audit trail and measures real loop current with an onboard 4-20 mA circuit, so a HART device's reported milliamp value can be verified independently. In the brochure's framing it combines a communicator, a documenting calibrator, and the compliance record in one device. See the OmniBus overview for the full picture.

HART networking variants

What is HART-IP?

HART-IP is a version of the HART protocol that carries HART messages over standard Ethernet and IP networks instead of (or in addition to) the 4-20 mA loop. It lets hosts reach HART instruments and gateways across a network, which is how data from many field devices gets aggregated and moved into control and asset-management systems. HART-IP is commonly used to talk to WirelessHART gateways and to high-density instrument networks. It keeps the same HART command structure, just delivered over a faster, routable transport.

What is WirelessHART?

WirelessHART is the wireless version of HART that lets instruments communicate over a secure, self-organizing radio mesh network instead of wires. It operates in the 2.4 GHz band and forms a mesh where each device can relay messages for others, improving reliability and coverage. Field devices report to a gateway, which typically connects upstream using HART-IP. WirelessHART is designed for monitoring points where running wire is impractical, while keeping the same HART data model technicians already know.

What is HART multidrop and burst mode?

HART multidrop is a wiring scheme where several HART devices share one pair of wires and are addressed digitally, while burst mode lets a device send updates on its own without being polled. In multidrop, each instrument is given a unique polling address and its analog current is parked at a fixed low value (commonly around 4 mA), so the loop carries digital data only and many devices coexist on the same pair. Burst mode (also called publish mode) has the device automatically transmit its values at a set interval, which speeds up data collection compared to one request-and-reply at a time. Both are optional features defined by the HART standard.

HART calibration

How do you calibrate a HART transmitter?

You calibrate a HART transmitter by applying a known reference input at several points across its range and comparing the device's output to what it should be, then trimming if it is out of tolerance. A typical procedure applies the process variable at points such as 0, 25, 50, 75, and 100 percent of span, reads the output (and the real loop current), and computes the error against the tolerance. If a point fails, you perform the appropriate trim, for example a sensor (PV) zero trim or an output (DAC) zero and gain trim, then re-verify. Good practice records the condition before and after as As-Found and As-Left results.

What is As-Found and As-Left calibration?

As-Found is the instrument's condition before you adjust it, and As-Left is its condition after any adjustment, captured as a before-and-after pair of calibration results. As-Found proves how the device was actually performing when you arrived, which is what auditors and QA/QC care about. If the As-Found data shows the device was out of tolerance, you trim it and then record As-Left to prove it now passes. Capturing both is the heart of a defensible calibration record, and the OmniBus brochure describes making As-Found and As-Left capture the path of least resistance, turning each session into a finished certificate. Learn more on the OmniBus product page.

What is NAMUR NE43?

NAMUR NE43 is a recommendation that defines how 4-20 mA transmitters use out-of-range current levels to signal a fault, so a sensor failure is not mistaken for a valid reading. It reserves the normal measuring range to roughly 3.8 to 20.5 mA and treats currents below about 3.6 mA or above about 21 mA as fault indications rather than process values. This lets a control system distinguish a real low or high reading from a broken sensor or wiring problem. NE43 is widely adopted on smart HART transmitters and is why a downscale or upscale failure current is meaningful.

Related HART resources

For plain-language definitions of every term used here, see the HART glossary. For a deeper introduction to the protocol, read what is HART communication. To see how a vendor-neutral communicator captures these calibrations as an audit trail, visit the OmniBus homepage.