How to Diagnose a 4-20 mA Input Pegged at Saturation
An analog input parked at the top of its range is telling you something, but not yet what. The process may genuinely be beyond the calibrated range, the transmitter may be saturated or deliberately signaling a fault, the range configuration may be wrong at either end of the wire, or the input card may be clipping. Each cause has a different fix, and the fastest way through is to read the actual loop current and let the milliamp value name the condition. This page is that diagnosis, in order.
Diagnose a Saturated 4-20 mA Input in one line: To diagnose a 4-20 mA input pegged at saturation, measure the real loop current and interpret it against NAMUR NE 43 conventions: a current just above 20 mA, around the 20.5 mA saturation limit, means the transmitter is alive but the measurement is beyond its configured range, while a current at or above 21 mA is a deliberate failure signal from the device's diagnostics. A value exactly at 20 mA with the process plausibly below range points at scaling or range mismatch between transmitter and input card. The current tells you which of three very different problems you have.
First Checks: Read the Actual Current
Do not diagnose from the HMI number, which has been through scaling, clamping, and quality logic that can all hide the truth. Measure the loop current itself: with a clamp meter made for milliamp loops without breaking the circuit, across the input's test points where the panel provides them, or with a meter in series per site practice. Also pull the raw counts or milliamp value the input card itself reports, because the card's raw view versus the HMI's scaled view localizes whether the pegging happens in the field or in the software.
While you are at the panel, note the process context: is it plausible the measurement is genuinely at or beyond the top of the range right now? A separator riding high, a flow above design during an upset, a summer temperature exceeding a winter-chosen span - the most common cause of a pegged input is a process outside a range that was configured too optimistically. If the process explanation fits, the instrument is honest and the range is the problem.
Saturation or Failure Signal: The Current Names It
Smart transmitters follow the NAMUR NE 43 recommendation, which divides the current scale into meanings. Normal measurement lives between 3.8 and 20.5 mA, with the region just beyond 20 mA up to about 20.5 mA meaning saturation: the device is healthy but the process has left its configured range, so the output parks at the limit. At or above 21 mA - or at or below 3.6 mA on the low side - the transmitter is not measuring at all; its diagnostics have detected a fault and it is deliberately driving the current out of the measurement band as a failure signal.
This is why the exact milliamp value matters more than "it reads high". A loop sitting near 20.5 mA calls for a process and range conversation; a loop at 21.75 mA or wherever the vendor's high-alarm current sits calls for a transmitter diagnostic session, because the device is announcing an internal or sensor fault - a burned-out element, a plugged and overranged cell, a configuration corruption. Treating a failure current as a range problem, or vice versa, sends the whole effort down the wrong path.
Causes on the Field Side
If the current shows genuine saturation, work the physical explanations: the process is really beyond range; the transmitter range or lower and upper range values were set wrong or changed; a plugged impulse line has trapped pressure that keeps the cell pinned; a valve lineup is applying static pressure the range never anticipated. A transmitter that saturates during identifiable operating states - transfers, startups, hot afternoons - is usually reporting the truth about an undersized range rather than failing.
If the current is a failure signal, go to the device: read its diagnostics with a communicator, check the sensor - a burned-out RTD or thermocouple drives the configured burnout direction, which on upscale burnout looks exactly like a pegged input - and check the configured alarm direction against what the control system assumes. A swap-in transmitter with a different alarm direction than its predecessor is a classic way a familiar point starts pegging after maintenance.
Causes on the System Side, Verifying, and Common Mistakes
When the measured current is normal but the displayed value pegs, the problem is between the terminals and the screen: input card range or filtering configured differently than the transmitter's calibration, scaling that maps the current to the wrong engineering-unit span, or a clamp in the SCADA tag configuration sitting inside the real operating range. Comparing the card's raw milliamp reading against your meter, and then against the HMI value, corners the discrepancy in minutes.
The fix is verified when the current, the card's raw value, and the displayed value all agree and the point tracks the process again through its full range. The recurring mistakes: diagnosing from the HMI instead of the current; widening the range to make the pegging go away without asking whether the process or a plugged line changed; ignoring quality flags that the system was raising all along; and forgetting that a pegged input on an alarm or shutdown point deserves priority handling, since a point parked at a rail is a point that has stopped protecting anything. Where trends are recorded in a monitoring platform such as Merobix, the moment the pegging began, and what the process was doing then, is usually sitting in the history waiting to be read.
Frequently Asked Questions
What does a loop current of about 20.5 mA mean versus 21 mA or more?
Around 20.5 mA is the NAMUR NE 43 saturation region: the transmitter is healthy but the measurement has gone beyond its configured upper range, so the output parks at the limit. At or above 21 mA the transmitter is deliberately signaling a detected fault - it is not measuring at all. The two call for different responses: saturation starts a range and process investigation, while a failure current starts a device diagnostic session with a communicator.
Can SCADA tell the difference between saturation and a transmitter failure signal?
Only if the analog input hardware measures beyond the 4-20 mA band and the configuration maps those regions to distinct states or quality flags. Many systems simply clamp anything above range to full scale, which erases the distinction and shows a believable maximum value in both cases. It is worth configuring out-of-band detection where the card supports it, so a failure current raises a device alarm instead of masquerading as a very high process reading.
Why does my input peg only during certain conditions, like transfers or hot weather?
Condition-dependent pegging is usually honest saturation: the process genuinely exceeds the configured range during those states - a flow above design during transfers, a temperature above a span chosen in cooler conditions. The instrument is fine; the range was sized for normal operation rather than the extremes. The fix is a deliberate re-range with updated documentation and alarm limits, not a trim, and the recorded trend around each event will confirm the pattern.
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.