A 4-20 mA input on a gas alarm controller reads a single analog variable, the loop current, mapped 4 mA = 0% range and 20 mA = 100% range, with a live-zero offset so 0 mA reads as a broken wire rather than a clean-air zero [S3].
A HART input on a gas alarm controller reads that same 4-20 mA current for safety signaling and additionally decodes a 1200 bps Bell 202 FSK signal superimposed on the loop, exposing device tag, range, calibration date, and sensor-health flags over the identical two-wire pair [S2][S4]. About 95% of fixed gas detection systems in industrial plants still ride a 4-20 mA field segment, even as digital buses and HART-capable instruments gain ground on new builds [S3].
What Each Input Actually Does on the Terminal Block
A 4-20 mA input card samples loop current through a sense resistor, converts it with an ADC, and scales the count against the configured range, for example 0-100% LEL combustible or 0-100 ppm toxic [S3][S5]. The card typically sources 24 VDC loop supply, supports a 2-wire or 4-wire detector, and raises a fault when current drops below ~3.8 mA or rises above ~20.5 mA, treating both as hardware failure rather than process data [S3].
A HART input card adds an FSK modem in parallel with the analog sense path: the 4-20 mA current continues to drive alarm setpoints and trip logic, while the modem exchanges burst-mode or polled-mode messages with the detector on the same pair [S2][S4]. Because the FSK average is zero, the overlay does not bias the 4-20 mA reading; the analog safety function remains valid even if the digital channel fails, which is the reason HART is accepted as a non-interfering addition to safety loops [S4].
Selection Criteria: 4-20 mA vs HART Input
Pick a 4-20 mA input card when the project has under ~30 detector points, cable runs exceed 300 m, the controller already has spare analog channels, and there is no per-detector calibration log requirement, because pure analog needs no DD files, no HART multiplexer, and no asset-management host [S3].
Pick a HART input card when the point count exceeds ~30 detectors, the engineering team needs calibration-due dates and sensor-life data per point, or the same controller must serve as the gateway into an Emerson AMS, Honeywell FDM, or Yokogawa PRM asset-management database [S3][S4]. HART also pays off when hot-swap replacement is expected, since the handheld or controller can auto-poll the replacement detector's tag and range without manual reconfiguration [S4].
Concrete trade-off table, drawn from the same sources:
4-20 mA input: one variable per channel (concentration), no configuration software required, immune to DD-file version mismatches, lowest controller cost per channel, no remote diagnostics beyond the analog reading.
HART input: analog concentration plus tag, range, calibration date, sensor-health flags, and fault diagnostics overlaid on the same 4-20 mA pair; requires DD files and a HART-aware input module; uses the same wiring as a 4-20 mA detector, allowing legacy heads to continue operating on the loop [S2][S3][S4].
Who Each Input Is For, and Who Should Skip It
A 4-20 mA input gas alarm controller is the right call for skid-mounted small systems, remote wellhead panels with under 10 points, and any plant where the only decision to make is "trip or do not trip" at a fixed setpoint [S3]. It is also the right call for explosion-proof installations where the controller must accept loop-powered 2-wire detectors and the loop budget is tight; 2-wire loop-powered devices typically cap at roughly 3.5 mA of sensor supply current on a 24 VDC rail after the 4 mA live-zero baseline is taken [S3].
A HART input gas alarm controller is the right call for refinery and petrochemical units running IEC 60079-29-1 detector populations, where the fixed gas detector fleet must demonstrate periodic bump-test logs to a third-party auditor, and where calibration-due-date tracking replaces paper logbooks [S7]. It is the right call for any greenfield where the spec already calls for a gas alarm controller with NAMUR NE107 diagnostic categories, since HART carries the status bits that NE107 maps to its four-condition model.
Skip HART inputs when the detector population is purely catalytic-bead or purely electrochemical with no digital overlay in the head, when the existing analog I/O rack is full and the HART-enabling I/O card is a long lead-time item, or when the project standard is locked to Modbus RTU daisy-chain polling, in which case the HART modem adds cost without benefit [S3][S6].
Real Use Cases from the Source Material
A Riken Keiki fixed gas detector specified for combustible-gas monitoring on a petrochemical skid typically outputs 4-20 mA DC proportional to 0-100% LEL and exposes the same loop to a HART modem inside the head, so the choice is made at the gas alarm controller input card, not at the detector [S5].
A Det-Tronics flame or combustible-gas detector with HART protocol support ships with a registered Device Description (DD) at the HART Communication Foundation, allowing the same detector to plug into any HART-aware input on a third-party controller while keeping diagnostic flags such as dirty-optics, calibration-due, and sensor-failure visible to the host [S4].
A Modbus/RTU or HART multidrop wiring scheme, where a single RS-485 trunk carries 32 detectors with unique addresses 1-247 at 9600-19200 baud over stub-free runs near 1200 m, reduces home-run cable count by roughly the inverse of the multidrop factor, which is why refinery retrofits above ~30 points gravitate to digital buses plus HART for the per-point diagnostics that pure Modbus cannot carry natively [S3][S6].
Limitations, Constraints, and Failure Modes
4-20 mA input has no per-detector identity: if two combustible heads are wired to two channels, the controller cannot tell which detector is which beyond the channel number, and a hot-swap requires manual re-entry of range and tag on the controller [S3][S4].
HART input requires the controller to maintain DD-file libraries matching each detector's firmware revision; a mismatched DD will display the analog reading but block access to diagnostic variables, and the controller must support burst mode if the field device is configured for it [S2][S4]. HART multidrop is rarely used in safety loops because it disables the analog current as a process variable (each slave locks its loop at a fixed 4 mA), so HART in fixed gas detection stays in point-to-point mode, which preserves the 4-20 mA safety signal but caps the multidrop cable saving that pure Modbus delivers [S2][S3][S4].
Loop budget remains the same on either input: at 24 VDC supply, the controller must still budget for the worst-case 500 m run, the worst-case detector burden, and a 4 mA live-zero floor, otherwise the analog channel reads low at full scale even when the HART channel reports a healthy 20.0 mA [S3].
Standards, Sourcing, and the Wire Behind the Input
IEC 60079-29-1 governs the performance demonstration of flammable-gas detectors, including accuracy, repeatability, and drift behaviour, which is the documentation layer that the HART diagnostic channel is built to expose to a host [S7]. HART itself is maintained by the FieldComm Group and registered as a trademark, with HART, WirelessHART, and HART-IP as distinct protocol variants on the same data model [S2].
For a typical fire alarm control panel room integration, a HART-aware input card is wired to a gas cabinet area detector, while 4-20 mA-only inputs are reserved for low-purity or single-gas skids where the extra DD-library maintenance would not pay back. The perimeter-alarm category sits outside this scope because its detection principle is different and its inputs are typically dry-contact or digital, not analog current loops.
Track the following two signals over the next planning cycle: detector vendors' continued support for HART Device Description revisions aligned to NAMUR NE107 status categories, and the lead time differential between pure analog input cards and HART-capable input cards on the same controller platform. Both numbers swing project economics more than any incremental per-channel price quote.
Background reading: 90-Minute vs 3-Hour Emergency Lighting: Code Triggers, Test Method, and Spec Pick.