How to Detect Wire Breaks in a 4-20mA Loop: Understanding the Live Zero in OLLA Lab

In a healthy 4-20mA loop, 4mA is the “live zero,” not a fault. A reading near 0mA usually indicates an electrical failure such as a wire break or loss of transmitter power. PLC logic should detect that condition before scaling or PID control interprets it as a valid low process value.

A 0mA reading is not simply a very low level. In a standard 4-20mA loop, it is generally an electrical abnormality unless the loop is intentionally being driven into a diagnostic state. That distinction is small on paper and expensive in service.

In a recent review of 500 beginner analog-fault validation exercises inside OLLA Lab, 82% of users initially scaled the input directly to engineering units without a low-signal fault rung, causing the simulated control logic to treat a forced wire break as a valid 0% process value. Methodology: n=500 first-attempt lab submissions for a defined analog tank-level fault-handling task; baseline comparator = presence or absence of an explicit low-limit fault-intercept rung before scaling/control use; time window = Q1 2026. This supports a narrow point: omission of analog fault handling is common in early commissioning practice. It does not support any claim about the broader industry error rate.

A simulation-ready engineer, operationally defined, is not merely someone who can scale 4-20mA to 0-100%. It is someone who can prove, observe, diagnose, and harden the logic when the signal stops being trustworthy. Syntax is easy; deterministic fault behavior is the part that causes trouble.

The “live zero” is the use of 4mA to represent the minimum valid process value in a 4-20mA analog loop. Historically, this convention is associated with process instrumentation standards such as ISA-50.1 and IEC 60381-1.

The engineering reason is practical. A two-wire loop-powered transmitter needs baseline current to operate, so the loop cannot use 0mA as its normal zero measurement. That reserved gap between 0mA and 4mA becomes diagnostically useful because it can indicate abnormal electrical conditions rather than a legitimate process minimum.

In other words:

• 4mA = lowest valid measured value
• 20mA = highest valid measured value
• 0mA to below a configured fault threshold = likely electrical failure, not process data

This is one reason 4-20mA remains widely used in process industries. It carries measurement and a basic form of fault discrimination in the same loop.

Why not use 0-10V for the same purpose?

A 0-10V signal can represent a valid zero value at 0V, but that creates ambiguity because 0V can also result from power loss, wiring failure, or device fault. A 4-20mA loop is not immune to failure, but it is generally better at making failure states distinguishable from valid low-end measurement.

That distinction matters in plants where the control system must decide whether to keep running, alarm, trip, or inhibit a sequence.

A 0mA reading causes trouble when the PLC logic treats it as a valid process minimum instead of an instrument fault. The classic mistake is blind scaling.

Consider a level transmitter scaled so that:

• 4mA = 0% tank level
• 20mA = 100% tank level

If the signal wire breaks and the analog input falls to 0mA, poorly defended logic may convert that to 0% level or some under-ranged value that still feeds downstream control. A fill valve or pump permissive may then respond as if the vessel is empty. The result can be:

• tank overflow,
• pump dry-run,
• false permissives,
• nuisance trips,
• or a PID loop driving hard in the wrong direction.

NAMUR NE 43 fault thresholds

Modern plants often apply NAMUR NE 43 conventions to distinguish valid measurement from fault signaling. Exact implementation depends on transmitter and control-system configuration, but commonly used thresholds are:

- less than 3.6mA: under-range fault indication, often associated with wire break, power loss, or transmitter failure - 3.8mA to 20.5mA: normal operating measurement range - greater than 21.0mA: over-range fault indication, often associated with device fault or configured failure upscale

A practical note matters here: exactly 4.0mA is not the same thing as “fault low.” In a correctly configured loop, 4mA is the valid low endpoint. Fault handling should usually be based on a threshold such as 3.6mA or 3.8mA, not on “anything near zero.”

Why junior logic often misses this

Early PLC exercises often teach scaling before they teach fault semantics. That produces programmers who can convert counts to percentages but do not yet intercept invalid measurements before those values reach alarming, permissives, or PID blocks.

That is the gap between classroom correctness and commissioning correctness.

You program analog fault handling by checking the raw input against defined fault thresholds before using the signal for scaling, alarming, sequencing, or control. The key is order of operations.

The safe sequence is usually:

1. Read raw analog input
2. Compare against low and high fault thresholds
3. Set fault bits and safe-state actions
4. Only then scale and use the signal if it is valid

If you scale first and diagnose later, you have already allowed bad data into the logic.

### Example: low-signal wire-break detection in ladder logic

Below is a representative ladder pattern using a low comparator on the raw input value. The exact raw threshold depends on the analog card resolution and scaling.

Ladder example:

- Source A: `Local:1:I.Ch0Data` - Source B: `3277` - Output: `ALM_Tank_Level_WireBreak`

• LES (Less Than)

In this example:

- `Local:1:I.Ch0Data` is the raw analog input count

• `3277` is shown as the low threshold in the example logic
• `ALM_Tank_Level_WireBreak` becomes true when the signal falls below the configured threshold

That alarm bit should not sit alone as a decorative lamp. It should drive a defined response.

What should the fault response do?

A wire-break alarm is only useful if it changes system behavior safely. Typical responses include:

• inhibiting automatic control,
• forcing the PID loop to manual,
• clamping a valve or VFD command to a safe value,
• removing start permissives,
• generating operator alarm text,
• latching a fault until reset or signal restoration criteria are met,
• and recording the event for troubleshooting.

The exact response depends on process hazard. A failed level transmitter on a neutral water tank is not the same problem as a failed pressure transmitter on a reactive chemical skid.

A compact logic structure that holds up better

A robust analog-input pattern usually includes:

• raw input tag,
• low fault comparator,
• high fault comparator,
• signal-valid bit,
• scaled engineering-unit value enabled only when valid,
• and fallback or safe-state logic when invalid.

A simple operational definition of correct analog handling is useful here: correct analog handling means the control system does not treat an invalid signal as trustworthy process measurement.

You convert milliamp thresholds into raw counts using the analog card’s configured range and resolution. A common example is a card scaled from 0 to 32767 counts for 0 to 20mA.

For that case:

• 4.0mA ≈ 6553 counts
• 3.8mA ≈ 6225 counts
• 3.6mA ≈ 5898 counts

Some systems use different raw ranges, signed values, or engineering-unit pre-scaling in the module configuration. So the principle is stable, but the exact number is platform-specific.

If your logic uses 3277 as the threshold, that corresponds more closely to about 2.0mA on a 0-20mA, 0-32767 mapping, not 3.6mA. That is why engineers should verify the card scaling before copying comparator constants into production logic.

Practical rule

Always document:

• the analog card raw range,
• the current range,
• the engineering-unit range,
• and the fault thresholds in both mA and counts.

A comparator without context becomes a troubleshooting puzzle later.

Fault handling should isolate invalid analog data before it can influence closed-loop control or sequence decisions. A PID loop should not continue acting on a broken measurement as though it were a real process upset.

For analog signals feeding PID or sequence logic, common protective actions are:

• switch PID from Auto to Manual,
• freeze or clamp output to a defined safe value,
• inhibit sequence advancement,
• force a hold state,
• alarm the operator with a specific diagnostic,
• require operator acknowledgement or maintenance intervention.

For example, if a tank level input fails low:

• the level PV should be marked invalid,
• the fill-control PID should not continue opening the valve based on that invalid PV,
• and any sequence dependent on “tank empty” should be blocked unless separately confirmed.

This is where control philosophy matters more than syntax.

OLLA Lab simulates wire-break handling by giving the user a controlled environment to force analog values, observe tag behavior, and verify that ladder logic responds safely before any live deployment. That is the bounded product value here.

Operationally, OLLA Lab is useful because it lets an engineer:

• build the ladder logic in the web-based editor,
• run the logic in simulation mode,
• monitor raw and interpreted values in the Variables Panel,
• force abnormal analog conditions,
• and compare ladder state against simulated equipment behavior.

That is what “simulation-ready” means in practice: not admiration for the diagram, but evidence that the logic survives bad inputs.

A practical OLLA Lab test workflow

To simulate a wire break in OLLA Lab:

Verify that:

• the wire-break alarm bit turns on,
• the signal-valid bit turns off,
• the PID loop enters manual or hold state if applicable,
• and the final control element command is clamped or inhibited safely.

1. Build or open an analog-input scenario. Use a tank level, pump, or process skid exercise where an analog transmitter drives control logic.
2. Identify the raw analog tag in the Variables Panel. Confirm whether the panel is showing raw counts, engineering units, or both.
3. Add explicit low-fault logic in ladder. Use a comparator to detect under-range current or equivalent raw counts.
4. Force the signal to an abnormal low state. Deliberately drive the analog input to 0mA-equivalent behavior or below the configured valid threshold.
5. Observe the logic response.
6. Compare ladder state to equipment state. Check whether the simulated valve, pump, or tank behavior matches the intended control philosophy.
7. Revise and retest. If the process still reacts as though the signal were valid, the logic is incomplete.

This is where OLLA Lab becomes operationally useful. It lets users rehearse abnormal-state behavior that employers generally do not want discovered for the first time on a commissioned system.

A useful validation record is not a screenshot gallery. It is a compact body of engineering evidence that shows what was tested, what failed, what changed, and why.

Use this structure:

1. System Description Define the process unit, the analog instrument, the control objective, and the relevant outputs.
2. Operational definition of correct State what the system must do when the signal is healthy and what it must do when the signal is invalid.
3. Ladder logic and simulated equipment state Show the fault-detection rung, signal-valid logic, and the resulting simulated equipment behavior.
4. The injected fault case Record the exact abnormal condition introduced, such as forced 0mA, under-range current, or transmitter power loss equivalent.
5. The revision made Document the logic change after the first failed test or unsafe response.
6. Lessons learned Capture what the fault revealed about scaling order, permissives, PID behavior, alarm design, or sequence assumptions.

That format is harder to fake and easier to review.

Analog scaling converts a signal into engineering units. Analog validation determines whether the signal should be trusted at all.

That distinction is foundational:

- Scaling asks: “What value does this current represent?” - Validation asks: “Is this current a valid measurement or a fault condition?”

A great deal of weak PLC logic answers the first question and skips the second.

Digital twin validation is appropriate when the control logic must be checked against realistic equipment behavior, sequence interaction, and abnormal-state consequences before deployment. In bounded terms, it is valuable when the question is no longer “does the rung compile?” but “does the system behave safely when the measurement fails?”

For analog fault handling, digital twin validation helps engineers test:

• whether alarms occur at the intended threshold,
• whether interlocks trigger in the right order,
• whether simulated equipment enters a safe state,
• whether sequence logic stalls, resets, or bypasses incorrectly,
• and whether operator-facing behavior is understandable.

OLLA Lab’s role here is not to certify safety integrity or replace site commissioning. It is to provide a risk-contained rehearsal environment where engineers can observe and correct logic under realistic fault conditions before live exposure.

The shortest correct version is this:

• 4mA is the valid low end of a 4-20mA loop, not a fault
• 0mA or under-range current usually indicates an electrical problem
• fault detection must occur before scaling and control use
• NAMUR NE 43 thresholds provide a widely used basis for fault discrimination
• PID loops and sequences should enter a defined safe response when the signal is invalid
• OLLA Lab is useful as a validation environment for forcing these faults and observing the logic response safely

If the control system cannot distinguish an empty tank from a broken wire, it is not ready.

- Up (Pillar Hub): Explore Pillar guidance - Across: Related article 1 - Across: Related article 2 - Down (Commercial/CTA): Build your next project in OLLA Lab

- IEC 60381-1 Analogue signals for process control systems - NAMUR NE 43 failure signaling for analog transmitters - ISA-50.1 analog signal compatibility standard information - IEC 61508 Functional Safety standard family