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 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.
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.
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.
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.
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.
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.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.