4–20 mA Loop Troubleshooting for PLC and Transmitter Faults

A symptom-to-boundary fault tree for authorised UK maintenance technicians investigating an abnormal 4–20 mA loop.

By SEESII Technical Editorial Published 19 July 2026 Evidence checked 19 July 2026

Direct answer: For 4-20mA loop troubleshooting, first make the process safe and identify the exact loop, power source, input type, configured range and every interface. Compare four separate observations: the process or transmitter value, independently established physical current, PLC raw input and final engineering-unit display. A real 0 mA sends the search towards missing power, an open path, polarity or topology. Fixed 4 mA or 20 mA may be a valid endpoint, a forced state or a configured limit. Current that rises but caps points towards voltage headroom or burden. Correct current with a wrong display points towards input configuration, raw conversion or scaling. Divide the loop only at an authorised test boundary and state what each result includes and excludes.

Safety boundary: This guide is for authorised work on a positively identified process-signal loop. Before opening, lifting or connecting anything, agree the safe control state with operations, apply the site’s risk assessment, permit, isolation, proving-dead and authorised testing procedures, and use the current loop drawing plus the exact equipment instructions. Testing exposed energised conductors is controlled work. Use a competent person, protect alarms, interlocks and final elements, and plan restoration before the first test.

Stop immediately if the tag or circuit cannot be identified; drawings and installed wiring disagree; the power owner, polarity or source/sink relationship is uncertain; the circuit may include mains or an unsupported voltage; safe process consequences have not been agreed; the signal could move equipment or trigger a trip outside the plan; a safety function lacks its approved procedure; a hazardous-area boundary or barrier requirement is unclear; the connection point or instrument limits are unknown; or any reading, movement, heating, smell or instability is unexpected.

Start with the symptom, not the transmitter

A reported “loop fault” may exist in the process, field device, current path, input module or display logic. Do not disturb the field wiring until the observation has been placed in the correct layer:

  1. Process and transmitter value: the actual pressure, temperature, level, flow or other condition, plus the local or digital value reported by the field device.
  2. Physical loop current: current established by a suitable independent method at a named point and time, not a value merely labelled “mA” on a host or HMI.
  3. PLC or DCS raw input: the channel’s actual counts, current value, quality and diagnostics before engineering scaling.
  4. Scaled display: the engineering value after range conversion, clamping, substitution, filtering, tag mapping and HMI logic.

An HMI value of zero is not proof of 0 mA. It could mean zero engineering units, an underrange code translated to zero, substituted bad-quality data or a software clamp. Conversely, a local transmitter display that looks correct does not establish that the physical current, cable path and receiver agree. Capture all four observations at the same process condition before selecting a fault branch.

Evidence rule: record where the observation was made, what path was included, what the result supports and what remains untested. Use “points towards” rather than “proves” until the fault boundary has been narrowed by independent evidence.

Fast 4–20 mA symptom matrix

Reported symptomEstablish firstNext boundaryDo not conclude yet
HMI shows 0Is it 0 mA, 0%, zero engineering units or substituted data?PLC raw value, status, tag and scalingOpen circuit
Genuine physical 0 mADocumented loop power and return pathSupply, fuse or link, conductor, polarity, interface and input pathFailed transmitter
Below 4 mAExact configured alarm and receiver thresholdsDevice diagnostics, loaded voltage and input handlingUniversal fault code
Fixed at 4 mAIs the process genuinely at its lower endpoint?Local value, fixed-output state, range, limit and network modeDead transmitter
Fixed at 20 mAIs the process genuinely at its upper endpoint?Local value, overrange, output state, clamp and diagnosticsHigh alarm from 20 mA alone
Correct current, wrong HMIDoes the raw input correspond to the physical current?Channel range, raw conversion, engineering scale, tag and display logicField wiring fault
Rises but cannot reach 20 mAIs the upper endpoint actually requested, and does current cap?Loaded supply, terminal voltage, cable, receiver and interface burdenScaling fault before current is established
Noisy or driftingDoes the process or local value move on the same timeline?Physical current, raw input, shared supply or common, interference and softwareGround loop
Known substitution gives no responseWho supplies voltage and where was the boundary opened?Mode, polarity, open load, input common, fuse and included pathFailed input card

Symptom-to-boundary fault tree

In a simple intact series loop, current is the same around the path at the same instant. Different current readings can therefore indicate different timing or methods, an unintended parallel or leakage path, or an interface that creates two separate loops. An isolator’s input and output sides are separate boundaries: a correct value on one side does not guarantee the other side follows.

4–20 mA loop troubleshooting sequence

  1. Freeze the as-found evidence. Record the process condition, operator report, local field indication, physical current if already available safely, input raw value and status, final display, active alarms, temporary forces or substitutions, and recent maintenance or power changes. Time-align the observations. A test that disturbs the loop can remove the transient clue.
  2. Identify the complete topology from controlled documents. Establish the field-device wiring type, loop-voltage owner, active or passive receiver arrangement, polarity, every fuse, link and test terminal, and every barrier, isolator, repeater, indicator or recorder. Record the configured current range, direction, lower and upper range values, receiver input type and raw range. Do not infer this from wire colour or a remembered nominal supply.
  3. Read diagnostics and inspect before moving conductors. Check permitted accessible points for loose, lifted, duplicated or corroded terminations, displaced links, open fuses, damaged cable, moisture, unpowered interfaces and changed range selection. Read field-device and input-channel diagnostics. Do not tighten, swap or move an energised conductor because it looks suspect.
  4. Decide whether the electrical current is actually abnormal. Prefer existing channel diagnostics or an approved non-intrusive observation where they answer the question. A conventional series current measurement interrupts the path while it is connected; treat that as a process-affecting intervention. Verify the correct function, terminals, leads and limits, and never connect by trial. Compare readings at the same process condition.
  5. Check loaded power and polarity at meaningful points. For a genuine dead or low-current loop, compare the documented supply at its source and the field-device terminal voltage under the authorised test method. Voltage across an open point can exist while no current path is available; an unloaded source reading does not prove adequate voltage under load. Correct polarity only under the approved isolation.
  6. Calculate voltage headroom when current clips. Include the minimum supply under load, field-device minimum terminal voltage, both cable conductors, receiver burden, interfaces and any other series drops. Use the highest current the approved design must pass. A loop that works near mid-span can still run out of voltage at the top.
  7. Move the test boundary deliberately. If documentary and non-intrusive checks do not localise the fault, use only an approved cabinet or field substitution point. State who supplies loop voltage, which element regulates current, and which path is disconnected. Never oppose two sources. The full connection and normal-use method remains outside this fault tree.
  8. Interpret only the included path. A cabinet input that responds to planned values supports the input, raw conversion and downstream display at those conditions; it normally says nothing about the disconnected field device or field cable. A field-end substitution can include the cable, supply, interfaces and receiver while excluding the original field device. Record both inclusions and exclusions.
  9. Investigate the field device after the downstream path is bounded. Compare the actual process or suitable reference condition with the local process value, configured range, transfer function, damping, output limits and diagnostics. Do not change range or adjustment merely to make two disagreeing displays match; first resolve wiring, voltage, input and software branches.
  10. Restore and hand back. Remove temporary sources and leads, restore conductors, links, fuses, covers and screen terminations, clear fixed outputs and temporary forces, reinstate controller modes, alarms, interlocks and safety functions through the authorised process, and confirm local, current, raw and display values plus quality. Obtain operations acceptance.

What 0 mA, 4 mA and 20 mA actually mean

Genuine 0 mA: current cannot complete the intended path

In a conventional 4–20 mA range, 4 mA is the live zero. A genuine physical 0 mA observation is therefore outside the normal process band and usually points towards missing power or an incomplete current path. Branches include an open conductor, fuse or link; wrong polarity; an unpowered interface; the wrong input or instrument mode; an open receiver path; or a device fault.

First prove that “0” is physical current, not an HMI representation. Then use the drawing to check supply and return as one path. For resistance or continuity work, isolate all relevant sources, secure the isolation, prove dead at the point of work and follow the equipment instructions before disconnecting sensitive electronics.

Fixed 4 mA: valid lower endpoint or held output

Ask whether the process is genuinely at the lower range value. If the local process value changes while current remains fixed, check the documented output state, configured range, output limit and diagnostics. A compatible digital network can also be configured so current remains at a minimum value while process data is carried digitally. That is a narrow communication branch, not a reason to change an address by trial; follow it only when the loop documentation identifies the protocol and mode.

Fixed 20 mA: valid upper endpoint, limit or diagnostic branch

Exactly 20 mA may be a legitimate full-scale value or a deliberate fixed output. It is not enough to label the signal as overrange or a fault. Compare actual process condition, local or digital process value, physical current, fixed-output state, configured clamp and diagnostics. Values near but not equal to the nominal endpoints also require the exact transmitter and input documentation: alarm, saturation, underrange and wire-break thresholds are model- and configuration-dependent, not universal codes.

Why a loop rises but cannot reach 20 mA

First establish that the process or authorised test state is requesting the upper endpoint. Then prove that physical current rises normally and caps. If it does, calculate the remaining voltage at the greatest current the design must pass:

voltage margin = minimum loaded supply − minimum field-device terminal voltage − fixed interface drops − (maximum current × total series resistance)

Total series resistance includes both cable conductors, the PLC or DCS input burden and any permitted series device. Fixed drops include interfaces whose documentation specifies an insertion voltage rather than a simple resistance. Use current minimum and maximum values from the exact design documents. Do not assume a universal receiver resistance, field-device voltage or alarm current.

A negative margin means the requested current cannot be guaranteed. A small positive result is a fragile design calculation, not proof that the installed circuit is healthy. If the supply droops as demand rises, investigate source capacity and distribution. If field-device terminal voltage remains adequate but current still caps, follow the configured range, output-limit, diagnostic and device branches. Never bypass an interface to make the arithmetic pass.

When physical current is right but the PLC value is wrong

Work from the electrical input towards the display. Compare the physical current at the named point with the input channel’s raw value and quality. If raw input is wrong, check the selected channel, current versus voltage range, terminals, common, input status and exact raw-data format. If raw input is right but engineering units are wrong, check lower and upper range values, direction, units, duplicate scaling, software clamps, substitution and tag mapping.

For a linear 4–20 mA range, the engineering relationship is:

engineering value = LRV + ((current − 4 mA) ÷ 16 mA) × (URV − LRV)

Do not apply that formula directly to arbitrary PLC counts. Use the exact module’s documented raw values and data type. Also check whether the channel is configured for 0–20 mA, a reverse-acting range, a non-linear transfer function or filtering. If physical current and raw value agree but the HMI differs, keep the field loop intact and follow the software path.

Separate process movement, interference and shared faults

“Noisy loop” is a symptom, not a mechanism. Trend the process or suitable reference, local field value, physical current, input raw value and final display on the same timeline. Add the operating state of nearby drives, motors, heaters, solenoids or contactors only when the site plan permits observation. Then follow the pattern:

  • Local value and current move together: investigate the real process, sensor and field-device branch.
  • Current is steady while raw input moves: investigate the receiver, common, reference, interface and interference branch.
  • Raw input is steady while the HMI moves: investigate software, communications, tag and display logic.
  • Several channels move together: investigate a shared supply, common, module, reference or environmental change.
  • Disturbance correlates with another asset: treat correlation as evidence for a coupling hypothesis, not proof of the route.

Different reference potentials can drive unwanted current, but loose terminations, moisture, coupling, common-mode limits and real process oscillation can produce similar symptoms. Follow the complete earthing and screen design in the exact system documents. There is no universal screen-termination fix. Never lift protective conductors or use a screen as the signal return. Filtering may make a display look calmer while leaving the underlying fault present.

Use substitution to test a boundary, not to declare the whole loop healthy

Diagnostic boundaryUsually includedUsually excludedBounded conclusion
PLC raw value compared with HMIRaw conversion, engineering scale, logic and displayField electrical path if it is not disturbedPoints towards input conversion or software depending on where disagreement starts
Cabinet-side known-current substitution into a disconnected compatible inputInput terminals, channel conversion, controller logic and displayField device and usually field cableThe downstream receiving path responded at the stated values and conditions
Field-end simulation replacing an externally powered two-wire field deviceField cable, loop supply, interfaces, receiver and downstream displayOriginal sensor and field deviceThe downstream path from that field boundary responded at the stated values
Comparison across an isolator or signal conditionerOne side at a time unless both sides are observedThe unobserved side and its separate power pathPoints towards the interface or one adjoining loop; does not imply equal current across separate loops

Source and simulate are not interchangeable labels. A source supplies the drive for a compatible passive receiver. A simulator or sink regulates current provided by an external loop. This page uses those concepts only to explain fault boundaries; connection logic, planned points, load checks and normal operation remain with the mapped operating owner and the exact instrument and receiver instructions.

Restore the loop and record the result

Fault-finding is not complete when the display recovers. Record the as-found symptom, every observation point, included and excluded path, temporary change, result and remaining uncertainty. Restore and check:

  • temporary current sources, simulators, meters and leads removed and accounted for;
  • every conductor, link, fuse, interface, cover and screen termination returned to the documented state;
  • fixed outputs, simulations, forces, substitutions and temporary filters cleared;
  • controller modes, alarms, interlocks and safety functions reinstated through the approved procedure;
  • local process value, physical current where required, raw input, quality and HMI indication reconciled;
  • normal final-element behaviour and process condition confirmed by operations; and
  • as-left evidence, unresolved follow-up and operations acceptance recorded.

Handback test: another authorised technician should be able to read the record and identify the exact symptom, test boundary, evidence, excluded components, restoration checks and any work still outstanding. A normal-looking HMI alone is not sufficient.

Frequently asked questions

What does 0 mA mean in a 4–20 mA loop?

A genuine physical 0 mA reading is outside the normal process band and usually means current cannot flow. Possible branches include missing loop power, an open conductor, link or fuse, wrong polarity, an open input path or a failed device. First establish that “0” is measured current rather than zero engineering units, a bad-quality substitute or a clamped PLC value.

Why is a transmitter stuck at 4 mA?

It may be correctly reporting the lower range value. If the process or local value changes but physical current does not, check the documented fixed-output state, range, output limit and diagnostics. A documented multidrop arrangement can also hold current at a minimum value while process data is digital, so confirm the configured mode before treating 4 mA as a fault.

Why is a 4–20 mA signal stuck at 20 mA?

Exactly 20 mA can be a valid upper-range value or a deliberate fixed output. Compare the actual process condition, local or digital process value, physical current, output state and documented limits. Process overrange, a configured clamp or a diagnostic state are separate branches; the exact transmitter documentation and configuration determine which applies.

Is 3.6 mA always a transmitter fault code?

No. Transmitter alarm and saturation values, and PLC underrange or wire-break thresholds, vary by device and configuration. Read the transmitter diagnostics, the configured alarm direction and the exact receiver thresholds. Do not assign a universal meaning to one current value or assume the field device and input card classify it in the same way.

Why does the loop reach 12 mA but not 20 mA?

The available voltage may cover the loop’s drops at mid-span but not near maximum current. First prove that the process or authorised test state is requesting the upper endpoint and that physical current really caps. Then check the minimum loaded supply, transmitter terminal-voltage requirement, receiver burden, both cable conductors, interfaces and any configured output limit.

Where should I inject a 4–20 mA test signal?

Choose the documented boundary that answers the fault question. A cabinet-side substitution can test the input, raw conversion and display while excluding the field transmitter and usually the field cable. A field-end substitution can include the cable, loop supply, interfaces and receiver while excluding the original transmitter. Record the location, included path and excluded components.

Can a ground loop affect a 4–20 mA signal?

Yes, different reference potentials can drive unwanted current and create offset or instability. However, a fluctuating indication can also come from real process movement, a loose connection, interference, common-mode limits, moisture or software filtering. Time-align the process value, physical current, PLC raw value and display before changing screens, earthing or isolation.

Sources and evidence boundary

This is a documentary, model-neutral troubleshooting guide based on the sources below and the exact-manual evidence hierarchy in the site’s engineering review. It reports no hands-on loop test. The Siemens input-module and Endress+Hauser transmitter manuals are cited as first-party examples that burden, polarity, diagnostics and thresholds are model-specific; they are not specifications for the reader’s installation. Exact equipment instructions, approved drawings and site procedures control the work. Sources were checked for the evidence brief on 19 July 2026.

  1. Health and Safety Executive — Safety in electrical testing at work (INDG354)
  2. Health and Safety Executive — The Electricity at Work Regulations 1989: guidance on regulations (HSR25)
  3. Health and Safety Executive — Electricity at work: safe working practices (HSG85)
  4. Health and Safety Executive — Permit-to-work systems
  5. Health and Safety Executive — Electrical equipment in potentially explosive atmospheres
  6. FieldComm Group / HART Communication Foundation — HART Application Guide, revision 7.1
  7. Fluke — How to measure a 4–20 mA loop signal
  8. Siemens — ET 200SP AI 4xU/I two-wire input-module manual
  9. Endress+Hauser — Cerabar PMP43 operating instructions
  10. Phoenix Contact — Analogue signal transmission in MCR technology