What Is a HART Communicator (and How to Choose One)
What is a HART communicator?
A HART communicator is a master device that talks the HART protocol to field instruments so a technician can configure, range, trim, calibrate, diagnose, and read them. HART stands for Highway Addressable Remote Transducer, an open digital communication standard maintained by the FieldComm Group. The communicator is the tool that puts a human in the loop with a smart transmitter, valve positioner, or analyzer.
In practical terms, a HART communicator is how you change a transmitter's tag, set its 4 mA and 20 mA range points, perform a sensor or output trim, read the primary variable, and pull device diagnostics, all without removing the instrument from service in most cases. It speaks to the instrument over the same two wires that carry the 4 to 20 mA loop signal, by riding a low-amplitude digital signal on top of the analog current.
Anyone who works smart instruments needs one. A HART field communicator is standard kit for instrument and automation technicians, calibration shops, and reliability teams.
How HART communication actually works
HART layers a digital signal on top of a standard 4 to 20 mA analog current loop, so one pair of wires carries both the live process value and two-way digital messaging at the same time. The digital signal uses frequency-shift keying (FSK), which the analog reading ignores, so configuring or polling a device does not disturb the 4 to 20 mA the control system is reading.
Communication is a master/slave exchange: the master (your communicator) asks, and the field device (the slave) answers. Commands fall into three groups: universal commands that every HART device supports (identity, primary variable, basic status), common-practice commands that most devices share (range, damping, loop test, trims), and device-specific commands unique to a given model. This three-tier command model is what makes a vendor-neutral communicator possible: universal and common-practice commands behave consistently across manufacturers.
Primary master vs secondary master
HART allows two masters on a loop at once: a primary master and a secondary master. They use different addresses so they do not collide, which means a handheld communicator can join a loop that a control system or asset-management host is already using.
The distinction matters in the field. A permanently wired host (a DCS interface card, a multiplexer, or an asset-management server) is typically configured as the primary master. A portable handheld HART communicator that a technician clips on temporarily usually takes the secondary master role, so it can talk to the device without bumping the host off the loop. Knowing which role each tool holds avoids communication conflicts when more than one master is present.
- Primary master
- Usually the fixed host: DCS, PLC interface, HART multiplexer, or asset-management system that owns the loop full time.
- Secondary master
- Usually the portable tool: a handheld or PC-based communicator that joins the loop temporarily for service work.
The three form factors of a HART communicator
HART communicators come in three form factors: a self-contained handheld field communicator, PC or tablet software paired with a HART modem, and HART communication built into an asset-management host. Each solves part of the job; they trade off portability, cost, and depth of integration.
| Form factor | What it is | Best for |
|---|---|---|
| Handheld field communicator | A self-contained, battery-powered, rugged device you carry to the instrument. Talks HART on its own, no laptop required. | Day-to-day field work, calibration rounds, troubleshooting in the field. |
| PC/tablet + HART modem (software) | HART communicator software on a computer, paired with a USB or Bluetooth HART modem that bridges to the loop. | Bench work, deep configuration, environments where a laptop is already in hand. |
| Built into an asset-management host | HART communication integrated into a plant asset-management system or DCS, reaching devices over wired HART or a multiplexer. | Remote configuration and diagnostics from the control room, fleet oversight. |
A handheld HART communicator wins on portability and ruggedness. A software-plus-modem setup wins on screen size and bench convenience. A host-integrated approach wins on reach and centralization but ties you to that host. Many shops end up owning more than one because no single traditional tool covers every situation.
What a HART communicator does
A HART communicator lets a technician configure, range, trim and calibrate, diagnose, and read live variables from a smart field instrument. These are the core jobs it exists to perform.
- Configure. Write the settings that define the instrument: tag, descriptor and message, engineering units, damping, transfer function (linear or square-root), and polling address.
- Range. Set the lower and upper range values (LRV and URV) that map the process span to the 4 to 20 mA output, including setting the range points from an applied process value.
- Trim and calibrate. Perform sensor and output trims (such as PV zero, DAC zero, and DAC gain) so the instrument's reported value and its analog output match a known reference.
- Diagnose. Read device status, alarms, and self-test results to find a fault before it becomes a callout.
- Read variables. Pull the primary variable (PV) and any secondary, tertiary, and quaternary variables, plus the loop current the device reports.
- Loop test. Force the output to a fixed current (for example 4, 12, or 20 mA) to verify wiring and the receiving system, then release it back to live tracking.
One important caveat on diagnostics: a HART device's reported milliamp value is only what the device thinks it is outputting, not proof of the actual loop current. Verifying the real current requires a separate measurement, which is why documenting calibrators and the OmniBus communicator measure loop milliamps independently.
How a HART communicator connects to the loop
A HART communicator connects across the 4 to 20 mA loop, either by tapping a loop that is already powered or by supplying the loop power itself, with a USB HART modem doing the bridging for software-based tools. The key requirement is that there be enough loop resistance (commonly a 250 ohm load) for the HART FSK signal to develop across.
- USB HART modem on the loop. For PC or tablet software, a HART modem connects to the computer over USB (or Bluetooth) and clips across the loop, translating between the software and the FSK signal on the wires.
- On a powered loop. When the loop is already energized by the control system or a power supply, the communicator simply taps across the leads to read and write HART, sourcing nothing.
- On a dead bench loop. When there is no loop power, a communicator that can source 24 V loop power energizes the device itself, then reads the current and talks HART at the same time.
Networked instruments add a fourth path: HART-IP over Ethernet or Wi-Fi reaches instruments and wireless gateways across the plant network instead of over a clip-on pair of wires.
The vendor lock-in problem: device descriptors
The biggest pain in traditional HART communicators is vendor lock-in driven by per-device descriptor files. To unlock every device-specific feature of a given instrument, a communicator typically needs that instrument's device descriptor (a DD, or its richer successor, an EDD), a file the manufacturer publishes per device type and revision.
That creates real friction in the field:
- You may have to keep DD/EDD libraries current and licensed across many manufacturers and device revisions.
- A brand-new or uncommon device can show up as "device not supported" until its descriptor is loaded.
- Some communicators are effectively tied to one manufacturer's ecosystem, so a multi-vendor plant means more than one handheld in the truck.
There is a way around the worst of it. Because HART's universal and common-practice commands behave the same across manufacturers, a communicator built on those standard commands can configure, range, trim, loop-test, and read the vast majority of devices without a per-vendor descriptor at all. That is the basis of a universal HART communicator.
How to choose a HART communicator
Choose a HART communicator by matching form factor to where you work, then weighing vendor coverage, loop-current measurement, and record-keeping. The right tool depends on whether you live in the field or at a bench, how many manufacturers you touch, and whether your work has to be documented.
| Question to ask | Why it matters |
|---|---|
| Field or bench? | Field work favors a rugged handheld; bench work can use PC software plus a modem. |
| How many manufacturers? | A multi-vendor plant pushes you toward a vendor-neutral tool to avoid descriptor lock-in and multiple handhelds. |
| Do you measure real mA? | If you certify calibrations, you need independent loop-current measurement, not just the device's reported value. |
| Do you need a record? | If audits or QA/QC matter, As-Found / As-Left capture and certificates should come from the tool, not a separate clipboard. |
| Wired, wireless, or both? | Networked plants need HART-IP and gateway support, not just a clip-on loop. |
For background on the protocol itself, see what is HART, and the HART glossary for terms like LRV, URV, DD/EDD, and master roles.
OmniBus: a universal, vendor-neutral HART communicator and calibration recorder
OmniBus is a universal, vendor-neutral handheld HART communicator and calibration recorder built by PragOptics (Fortiview Holdings). It combines the communicator, the documenting calibrator, and the audit record in one rugged, battery-powered, touchscreen field node, and it is designed to sidestep the descriptor lock-in described above.
Per the OmniBus brochure, it is vendor-neutral by design: instead of locking to one manufacturer's device descriptors, it speaks universal, common-practice HART and organizes commands by device family (Temperature, Level, Pressure, PID Control), so the screen shows only what the connected instrument can actually do. No per-vendor handheld, no descriptor licensing.
- Every form factor in one. It works as a self-contained handheld over its on-board two-wire loop, as a USB HART modem path, and across the network over HART-IP, all feeding the same workflow.
- Multi-modal HART-IP. Point it at a networked address and it works out what it is connected to before drawing a screen: it auto-detects whether the endpoint is a wireless gateway host fronting a whole mesh or a single direct instrument, and adapts the interface to match.
- It measures real loop current. An on-board, galvanically isolated 4 to 20 mA circuit measures the actual loop current independently, so the trusted value (not just what the device reports) lands in the record. On a dead loop it can also source 24 V loop power, reading current and talking HART at once.
- The record is the product. Guided Configure, Calibrate, Loop Test, and Record workflows capture As-Found / As-Left results and produce print-ready calibration certificates, written to an append-only historian that answers who did what, when, where, and why.
In short, OmniBus is positioned as a universal HART communicator that replaces a vendor-locked handheld, a separate documenting calibrator, and a stack of paperwork with one device, on any HART instrument, with the record already done. See more HART questions answered or explore the full HART resource hub.