Skip to main content
Call Eric:863-698-8266
CURRYCONTROLS.COMControls & Automation Knowledge Hub
TroubleshootingTroubleshootingInstrumentation4-20 mASignalsAnalog

Signal Pegged High or Low

A 4-20 mA signal stuck at a rail or a fault current: a transmitter in fault, a process truly out of range, an open or shorted loop, a wrong range, a wiring error, an input channel fault, or a scaling clamp. How the current itself tells you which.

8 min readUpdated Sep 5, 2026Published Sep 5, 2026By Eric Sullivan

Symptom

A process value shows exactly its minimum or maximum, or a value beyond range, and does not move; the controller input reports under-range, over-range, or open wire; a related alarm or interlock has acted; the loop current reads at a rail or at a fault value.

The short answer

Signal Pegged High or Low

A loop signal that is stuck at an end of its range is reporting one of three things: the process is genuinely at or beyond the range limit, the transmitter has detected a fault and driven the loop to its configured alarm current, or the loop itself is broken or miswired so that the receiver sees no current or full current. Measuring the loop current with a meter separates them: a fault current below 3.8 or above 20.5 milliamps is the transmitter announcing a diagnostic, exactly 0 milliamps is an open loop or a dead supply, a current at the supply limit is a short, and a clean 4.0 or 20.0 is a process value at the limit or a range that no longer fits the process. The receiver display alone cannot tell these apart, which is why the meter comes first.

Key points

  • Measure the current: a fault current is a diagnostic, 0 is an open loop, the supply limit is a short, 4.0 or 20.0 is a limit or a range problem.
  • Transmitters signal faults with currents outside the live range, and the fault code on the transmitter says what they found.
  • A process can really be out of range; check the field before condemning the instrument.
  • A range that does not fit the process pegs the signal at full scale whenever the process exceeds it.
  • An input channel that is clamped, scaled wrong, or faulted looks pegged when the loop is fine.

Possible causes and what to check

Possible causeWhat to check
Transmitter fault currentThe loop reads below 3.8 or above 20.5 milliamps at a value fixed by the alarm setting; the transmitter display or a handheld communicator shows the fault: sensor open, electronics, over-range, or a configuration error.
Process truly at or beyond rangeThe loop reads a clean 4.0 or 20.0 and a field indicator or a portable instrument confirms the process is at the limit; the range is too narrow or the process is abnormal.
Open loopZero current: a broken wire, a loose terminal, a blown loop fuse, a dead loop supply, or a transmitter with no power. Check the supply voltage at the transmitter terminals.
Short or ground on the loopCurrent at the supply limit or a high, unstable value; a wire shorted to ground or to another conductor, or water in a junction box. Isolate segments.
Reversed polarityZero current with the supply present; the transmitter connected backwards after a replacement. Check the terminal marking.
Range set wrong in the transmitterThe transmitter range narrower than the process; the signal pegs at 20 whenever the process exceeds the upper range value. Compare the transmitter range with the design range and the controller scaling.
Sensor failureA pressure element ruptured, a level probe fouled, a flow tube empty, an electrode broken; the transmitter may report a fault or a plausible-looking rail. Inspect the sensor.
Input channel fault or clampThe loop current is normal at the terminals but the controller shows a rail; the channel is faulted, its range set wrong, or its scaling clamps at a limit. Check the module diagnostics and scaling.
Loop supply overloadedSeveral transmitters on one supply and not enough voltage for the loop resistance; signals peg or sag together. Measure the supply under load.
Isolator or signal conditioner failedA device in the loop passing full or zero output; measure on both sides of it.

What the current says

Measured loop currentMeaningNext step
0.0 mAOpen loop, no supply, or reversed transmitterSupply voltage at the transmitter; continuity; polarity
About 3.6 mA or below 3.8Transmitter low fault alarmRead the transmitter fault code
Exactly 4.0 mA, steadyProcess at or below lower range valueConfirm in the field; check the range
Between 4 and 20, but the controller shows a railInput channel, scaling, or a clampModule diagnostics and scaling
Exactly 20.0 mA, steadyProcess at or above upper range valueConfirm in the field; check the range
21 to 22.5 mATransmitter high fault alarm or over-rangeRead the transmitter fault code
At the supply limit or wandering highShort or ground fault on the loopIsolate segments; check junction boxes

Working it

  1. 1

    Look at the process

    Before anything else: could the process actually be there. A wet well at the top of its range or a pressure at zero during a shutdown is real. Field indicators, a portable instrument, or the operators know.

  2. 2

    Measure the current

    A meter in series at the receiver terminals, or a clamp meter for milliamps. Compare with the table.

  3. 3

    Read the transmitter

    The local display or a handheld communicator: the measured value, the output current it thinks it is sending, any fault code, and the range.

  4. 4

    Compare transmitter output with the measured current

    If the transmitter says 12 milliamps and the meter says 0, the loop is open between them. If both say 20, the transmitter is driving the rail and the reason is in the transmitter or the process.

  5. 5

    Check the range

    Transmitter lower and upper range values against the design and the controller scaling. A range changed during calibration or a replacement with factory defaults is common.

  6. 6

    Check the input

    Module channel diagnostics, channel range setting, raw counts, scaling, and any clamp in the logic.

  7. 7

    Fix and verify

    Sweep the transmitter output through the range with a simulator and confirm the controller value follows.

When the process is really there

A signal that pegs because the process exceeds the range is a design finding rather than an instrument fault. A range that fit the process at design has been outgrown by a new pump, a new setpoint, or a changed operation, and the fix is a new range in the transmitter and in every place that scales it, with the change documented. A signal that pegs briefly during an upset and returns is doing its job; the alarm on the rail is what the design intends.

Frequently asked questions

The transmitter says 20.0 and the process is nowhere near full scale.
The transmitter has either the wrong range, a sensor that has failed toward full scale, or a fault that it reports as full scale rather than as a fault current. The transmitter configuration and diagnostics say which; a sensor fault is confirmed by applying a known input.
Why does my controller show 3.6 mA as a valid low reading instead of a fault?
Because the input scaling extends below 4 milliamps and nothing in the logic checks for under-range. The input module under-range flag, or a comparison against 3.8 milliamps, should drive a bad-quality flag and an alarm rather than a value.
The signal pegs high when a nearby motor starts.
That is noise or a supply sag rather than a rail: a common-mode surge on the loop, a supply that dips under the start, or a ground path that shifts. Measure the loop current during the start with a meter that records minimum and maximum.
Can a bad loop supply make a signal peg?
A supply without enough voltage for the loop resistance cannot drive 20 milliamps and the signal saturates below full scale; a supply that fails leaves the loop at 0. Measure the supply at the transmitter with the loop at 20 milliamps.

Direct contact

Have a controls question?

Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.