What Is Wire Break Detection?
Wire break detection is the ability of an instrument loop to reveal when its own wiring has failed, rather than silently reporting a plausible but false value. A cut cable that reads as a comfortable mid-range number is far more dangerous than one that trips an obvious fault. This guide explains how wire break detection works across 4-20 mA, RTD, and thermocouple circuits, and why oil and gas facilities rely on it.
Wire Break Detection in one line: Wire break detection is a feature of instrument loops and I/O that identifies an open circuit - a broken or disconnected wire - and flags it as a fault rather than a valid reading. It exploits the live-zero of 4-20 mA loops and open-circuit behavior in RTD and thermocouple inputs.
The Live-Zero Advantage
The 4-20 mA standard is built for this. Because a healthy loop never drops below 4 mA - the live-zero - a reading of 0 mA can only mean the loop is broken or dead. An input card watching for current below about 3.6 mA can therefore declare a wire-break fault with confidence, something impossible with a 0-20 mA or 0-10 V signal where zero is a legitimate value indistinguishable from a broken wire.
This is one of the core reasons 4-20 mA became the field standard. The same margin lets the top of the range flag an over-scale fault above 20 mA. Instruments deliberately drive to a defined out-of-range value on internal failure so the fault is unmistakable downstream.
RTD and Thermocouple Open-Circuit Detection
Temperature inputs detect breaks differently because they read resistance or millivolts rather than a loop current. An RTD input can pass a tiny sense current and watch for the open-circuit condition a broken lead produces, flagging it as a fault. A thermocouple input uses burnout detection: it monitors for the effectively infinite resistance of a broken thermocouple and forces the reading to a defined upscale or downscale value so the failure is obvious.
Whether the input drives upscale or downscale on burnout is a configured choice tied to the safe direction for that measurement - a heater control might fail upscale so the loss of sensing looks like over-temperature and shuts the burner rather than driving it hotter.
Why It Matters in Oil and Gas
In safety and control loops, an undetected wire break is a silent failure that can leave an operator watching a frozen or fabricated value while the real process drifts. Wire break detection turns that silent failure into a visible alarm, and it is a required diagnostic in many safety-instrumented functions because it improves the loop's ability to reveal its own faults.
Detection happens at the field instrument and controller I/O. A cloud SCADA such as Merobix reads the fault or out-of-range value the controller reports and can alarm on it - so a broken sensor wire in the field surfaces as a clear bad-quality or fault indication on the dashboard, rather than a misleading normal reading. The controller detects; the SCADA surfaces and alarms.
NAMUR NE43 and the Fault Bands
NAMUR recommendation NE43 formalizes what a smart transmitter should do with the space around the 4-20 mA range. It reserves the region between 3.8 mA and 20.5 mA for measurement information, including saturation, and defines everything at or below 3.6 mA or at or above 21 mA as a deliberate failure signal. A transmitter that detects an internal fault drives its output into one of those failure bands - configurable low or high - so the receiving card sees a current that no valid measurement can produce.
The practical work is making both ends agree. If the transmitter is set to signal faults downscale but the input card only alarms above 21 mA, a detected fault sails through as a saturated-low reading. During configuration, record each loop's fault direction and the card's detection thresholds together, and take the exact fault currents from the manufacturer's datasheet rather than assuming them - implementations differ.
Supervised Discrete Circuits
Discrete inputs have the same silent-failure problem in a worse form: a broken wire on a plain dry contact is indistinguishable from the contact simply being open. Where the circuit matters - fire and gas detection, shutdown pushbuttons, ESD interlocks - the fix is line supervision. An end-of-line resistor network at the field device gives the healthy circuit a defined resistance, and the input measures that resistance instead of merely sensing open or closed.
With the right network the input can tell four states apart: normal, active, open circuit, and short circuit - so a cut cable or a crushed one raises a distinct circuit-fault alarm rather than masquerading as a healthy, quiet detector. The resistor values and wiring arrangement are specific to the input card, so fit exactly what the manufacturer's documentation calls for, and fit it at the far end of the circuit so it supervises the whole run.
Proving It at Commissioning
Wire break detection is a claim until you have tested it end to end. A workable sequence:
- Get authorization first: permits in place, operations notified, and any executive actions inhibited per site procedure by qualified personnel.
- Lift one conductor at the field end of the loop, not at the marshalling cabinet, so the test covers the entire cable run.
- Confirm the input declares a fault or out-of-range condition, not a plausible process value.
- Confirm the bad quality and the alarm propagate all the way to the HMI and the historian.
- Confirm any control or interlock response moves in the designed fail-safe direction.
- Reland the conductor, verify a healthy reading, and remove inhibits per procedure.
This folds naturally into loop checkout - a few extra minutes on top of a standard 4-20 mA loop check buys certainty that the diagnostic actually reaches an operator.
What the System Should Do Once a Break Is Detected
Detection is only half the design; the response is the other half. A PID loop reading a failed input must not keep controlling on a frozen or fault value - the loop should shed to manual or drive a defined safe output, per the loop's design. Totalizers should stop accumulating rather than integrate a fault current into a volume. Historians should store the quality flag, not a fabricated number that poisons later analysis.
On the operator side, a bad-quality tag should look visibly different from a live value, and I/O fault alarms should be distinguishable from process alarms so the operator knows immediately that the problem is the measurement, not the process. Nothing erodes trust in a system faster than a broken sensor presented as a calm, healthy reading.
Frequently Asked Questions
How does a 4-20 mA loop detect a wire break?
A healthy loop never falls below 4 mA, so a reading near 0 mA can only mean the wiring is broken or the transmitter is dead. An input card watching for current below about 3.6 mA flags a wire-break fault, which a 0-based signal could not distinguish from a real zero.
What is thermocouple burnout detection?
It is open-circuit detection for a thermocouple. The input monitors for the very high resistance of a broken thermocouple and forces the reading to a defined upscale or downscale value, so the failure is obvious rather than being mistaken for a valid temperature.
Why is wire break detection important for safety?
An undetected broken wire can leave a control system reading a false but plausible value while the process drifts unmonitored. Wire break detection converts that silent failure into a visible alarm, which is why it is a required diagnostic in many safety-instrumented functions.
Can a 0-10 V or 0-20 mA signal detect a wire break?
Not inherently - zero is a legitimate measurement value in those ranges, so a broken wire reads exactly like a real zero. Workarounds exist: use a live-zero scaling such as 2-10 V or 4-20 mA so a zero signal becomes impossible, add supervised wiring, or rely on a digital layer such as HART or a fieldbus that carries device status alongside the value. This ambiguity is a strong argument for live-zero signals on anything that matters.
Does wire break detection catch every wiring fault?
No. It catches the clean open circuit. A corroded, high-resistance termination can still pass a plausible but wrong current, and a partial short or a miswired loop can also read believably. Those faults only surface through periodic testing - loop checks, insulation resistance tests, and bench work such as when you bench test an RTD - so wire break detection reduces, but does not eliminate, the need for scheduled instrument maintenance.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.