Why Ultrasonic Sensor Returns 0 Suddenly and Keeps 0: The Complete Troubleshooting Guide

In this guide: Why an ultrasonic level sensor can suddenly read 0 (empty) and stay at 0 - the difference between a 0 mA loop fault and a 0% level reading, the two real failure paths (power/loop loss and lost echo with fail-safe latched to 0%), a step-by-step diagnosis, and how to fix and prevent it.

Why Ultrasonic Sensor Returns 0 Suddenly and Keeps 0: Quick Answer

An ultrasonic sensor that suddenly reads 0 and stays at 0 is almost always one of two things: (1) it has lost power or its 4–20 mA loop has dropped to 0 mA (a wire break, lost 24 V DC supply, reversed polarity, or short), which the controller shows as 0; or (2) it has lost its echo - foam, heavy vapor, condensation on the face, an obstruction in the beam, the surface falling into the dead band, or a failed transducer - and its no-measurement fail-safe is configured to drive to 0% (4 mA), which is why it "keeps" 0 instead of recovering. "Suddenly and keeps" is the tell: a gradual true emptying would fall smoothly, but a persistent 0 means the sensor stopped getting a valid echo (or stopped being powered) and latched to its configured fail-safe. The fastest check is to look at the loop current - 0 mA points to power/wiring, while 4 mA (or a steady 0% on a healthy loop) points to a lost echo with fail-safe-at-0. This guide walks the diagnosis.

First: What Does "0" Actually Mean

0 mA vs. 0%

"0" can mean two different faults:

Read the current, not just the number: A 4–20 mA sensor at true empty sits at 4 mA (not 0 mA). If the loop is actually at 0 mA, the sensor is not powered or the loop is broken - that is a wiring/power fault, not a level fault. If the loop holds ~4 mA but the displayed level is 0%, the sensor is powered and deliberately reporting empty (fail-safe or real). Telling these apart is step one.

Path 1 - Power or Loop Loss (0 mA)

The Sensor Is Dark

If the loop current is 0 mA, the sensor has no working signal path:

Why "suddenly": A breaker trip, a disconnected quick-connect, a cable chewed by equipment, or water in a junction box can drop the loop to 0 mA with no warning. The sensor is simply unpowered, so it reports nothing and the controller shows 0 (or a fault). This is the most common "sudden 0" and the easiest to confirm with a multimeter at the sensor terminals.

Path 2 - Lost Echo with Fail-Safe Latched to 0%

The Sensor Is Powered but Blind

If the loop is ~4 mA (powered) but level reads 0%, the echo is gone and fail-safe = 0%:

Why it "keeps" 0: Most ultrasonic sensors have a configurable no-echo fail-safe - on losing a valid echo they can hold last value, drive to 3.6 mA (under-range fault), drive to 21 mA (over-range fault), or drive to 0% (4 mA) / 100% (20 mA). If the installer set fail-safe to 0%, then the moment the echo disappears (foam event, condensation, transducer death), the sensor outputs 4 mA = 0% and stays there until an echo returns. If the root cause is permanent (dead transducer, blocked beam), it stays 0 forever. That is exactly the reported symptom.

Diagnosis: A 6-Step Flow

From Symptom to Cause

Trust the sensor's own diagnostics: Many ultrasonic transmitters show a "no echo," "echo lost," or signal-strength indicator. A steady "no echo" with a healthy loop current is the signature of Path 2. A 0 mA reading is the signature of Path 1. The meter at the terminal settles it in minutes.

Lost-Echo Causes in Detail

What Specifically Killed the Echo

Foam is the top suspect: In process tanks, aeration, boiling, or agitation creates foam that absorbs the ultrasonic pulse - the echo vanishes and, with fail-safe at 0%, the sensor pins to empty. Condensation is the quiet second: on a cool tank the face beads up and the return is lost. Both are environment, not electronics, and both produce the exact "sudden 0, stays 0" behavior.

Fail-Safe Configuration: Why It "Keeps"

The Latch That Holds 0

What the sensor does on lost echo:

Change the latch: If a lost echo keeps pinning the reading to 0, the fix is twofold - restore the echo (clear foam/condensation/obstruction) and, optionally, change the fail-safe to hold last value or a fault current (3.6/21 mA) so a lost echo is obvious instead of silently reading empty. A silent 0% on lost echo is dangerous for pump/overflow protection, because the system "thinks" the tank is empty.

Not This: Things That Look Similar

Rule Out False Cousins

0 vs 100 vs noise: A sensor that pins to 100% has a different fail-safe or the surface above the sensor; one that fluctuates has a weak but present echo (turbulence); one that drifts has a calibration/temperature issue. "Suddenly and stays 0" specifically points to lost power/loop or lost echo with 0% fail-safe - not calibration or drift.

Fix and Prevent

Stop the 0, Keep It From Returning

Prevention pays: The recurring "0 and stays 0" is preventable by (a) a sound power/loop install (fused, dry, strain-relieved cable), (b) a clear beam path and condensation control, and © a fail-safe set to hold or a fault current rather than silent 0%. For chronically foamy or steamy tanks, moving to radar eliminates the lost-echo failure entirely.

Frequently Asked Questions

Q1: Why does my ultrasonic level sensor show 0% all of a sudden and never recover?

A sudden, persistent 0% reading on an ultrasonic level sensor is almost always either a loss of power/loop or a lost echo with fail-safe set to 0%. First check the 4–20 mA loop current at the sensor: if it is 0 mA, the sensor has lost its 24 V DC supply, the loop wire is broken or shorted, polarity is reversed, or a fuse/breaker has tripped - the sensor is simply unpowered and the controller shows 0. If the loop holds ~4 mA but the level reads 0%, the sensor is powered but has lost its echo (foam, vapor, condensation on the face, an obstruction in the beam, the surface in the dead band, or a dead transducer) and its no-measurement fail-safe is configured to drive to 0% (4 mA), which is why it stays at 0 instead of recovering. The meter at the terminal tells you which path within minutes.

Q2: Is a 0 reading the same as a 0 mA loop fault?

No - a 0% level reading and a 0 mA loop current are different faults. A healthy 4–20 mA ultrasonic sensor at true empty sits at 4 mA, not 0 mA. If the loop current is actually 0 mA, the sensor is unpowered or the loop is broken (wire break, lost supply, short, reversed polarity) - that is a wiring/power fault. If the loop current is ~4 mA but the displayed level is 0%, the sensor is powered and is deliberately reporting empty, either because it truly sees an empty tank or because it lost its echo and fail-safe is set to 0%. So the first diagnostic step is always to measure the loop current: 0 mA points to power/wiring, while a steady 4 mA with a 0% reading points to a lost echo with fail-safe-at-0.

Q3: Why does the sensor stay at 0 instead of recovering when the tank has liquid?

The sensor stays at 0 because its no-echo fail-safe is configured to drive to 0% (4 mA). On losing a valid echo, an ultrasonic transmitter does not guess - it follows its programmed fail-safe: it can hold the last good value, drive to a fault current (3.6 mA under-range or 21 mA over-range), or drive to 0% (4 mA) or 100% (20 mA). If the installer chose 0%, then the instant the echo disappears - say a foam event, condensation on the face, or a failed transducer - the output drops to 4 mA and reads 0%. It stays there until a valid echo returns. If the root cause is permanent (a dead transducer or a blocked beam), it never recovers. Changing the fail-safe to "hold last value" or a fault current makes a lost echo obvious instead of silently reading empty.

Q4: What specifically causes an ultrasonic sensor to lose its echo?

An ultrasonic sensor loses its echo when something stops the sound pulse from reaching the surface and returning cleanly. The common causes are foam on the liquid surface (which absorbs or scatters the pulse - typical in aerated, boiling, or agitated tanks), heavy vapor or steam above the liquid (which slows and distorts the sound path), condensation beading on the transducer face (which scrambles the return - common on cool tanks), an obstruction such as a pipe, ladder, or agitator inside the beam cone, the liquid surface rising into the dead band directly below the sensor (the ring-down zone where no echo can be received), a tilted or off-center mount (the beam misses the surface), or a failed transducer (the piezo element is dead and emits nothing). Foam and condensation are the two most frequent, and both produce exactly the "sudden 0, stays 0" symptom when fail-safe is set to 0%.

Q5: How do I fix and prevent an ultrasonic sensor stuck at 0?

To fix an ultrasonic sensor stuck at 0, first measure the loop current at the sensor: if it is 0 mA, restore the 24 V DC supply, repair the broken or shorted loop wire, correct reversed polarity, or reset the tripped breaker. If the loop is ~4 mA, inspect for a lost echo - clear foam or vent steam, clean or heat the transducer face to remove condensation, remove any obstruction in the beam, remount vertically if tilted, or replace the sensor if the transducer is dead. To prevent recurrence, install the power/loop soundly (fused, dry, strain-relieved cable), keep a clear beam path with condensation control, and set the fail-safe to "hold last value" or a fault current (3.6/21 mA) rather than silent 0%. For tanks that are chronically foamy or steamy, replace the ultrasonic sensor with a radar transmitter, which is immune to those conditions and eliminates the lost-echo failure entirely.

The Bottom Line

An ultrasonic sensor that suddenly reads 0 and stays at 0 is not usually "broken math" - it is either unpowered (the 4–20 mA loop has dropped to 0 mA from a lost 24 V DC supply, broken/short/reversed loop wire, or tripped breaker) or it has lost its echo and latched to a 0% fail-safe. The decisive test is the loop current at the sensor: 0 mA means power/wiring (Path 1) and the fix is in the panel and cable; ~4 mA with a 0% reading means the sensor is powered but blind (Path 2), with foam, vapor, condensation on the face, a beam obstruction, the surface in the dead band, or a dead transducer killing the echo, and a fail-safe set to 0% keeping it pinned. "Suddenly and keeps" rules out calibration drift (which is slow) and points to an event - a power drop or an echo loss - and the latch explains the persistence. Diagnose in six steps (read mA → check supply → check wiring → check echo → inspect face/beam → test transducer), restore power or clear the echo, then set fail-safe to hold or a fault current so a future lost echo is loud, not silent. For chronically foamy or steamy tanks, move to radar and the lost-echo failure disappears for good.

Last updated: August 2026

Disclaimer: This guide is a general troubleshooting reference for ultrasonic level sensors showing a persistent 0 reading. Exact fail-safe options, loop behavior, dead-band size, and diagnostic displays vary by manufacturer and model; always consult the device's manual and follow electrical safety before working on live 24 V DC loops. This guide is not affiliated with, endorsed by, or sponsored by any sensor manufacturer.