Radar Product Echo vs False Echo: Field Interpretation Guide

The strongest radar echo is not always the product surface. Nozzles, walls, coils, ladders, agitators and vessel bottoms can create fixed returns, while foam, dust, interfaces and changing solids surfaces can create moving or intermittent peaks. Correct interpretation combines physical geometry, known process level and time-based movement with the raw echo curve. Suppression should follow diagnosis, not replace it. The objective is to prove which peak represents the intended level and how tracking behaves when signals compete, weaken or enter the near range.

Build a distance map

Measure antenna reference plane, nozzle, adapters, walls, internals, inlet, bottom and moving equipment. Convert each target to expected radar distance. Record alignment and beam width. A fixed peak can only be identified confidently when its distance matches an as-built feature rather than an assumed drawing.

Capture known-level curves

Save raw curves at verified low, middle and high levels with product, temperature, pressure, foam, dust, agitation and fill state. Use consistent scales. Mark the selected distance and signal quality. A screenshot without process context cannot prove whether a peak is product, foam, structure or bottom.

Use movement as evidence

Track how peaks move as the real surface changes. A product return should normally follow level direction, while a rigid structure stays at a fixed distance. However, multiple surfaces and solids geometry can complicate movement, so compare with independent references and process events rather than relying on one rule.

Recognize process-created echoes

Foam may produce its own interface or attenuate the liquid echo; low dielectric product can allow bottom reflection; dust and turbulence can broaden or interrupt returns. Guided or bypass arrangements add transitions. Define which interface the application needs and evaluate representative conditions before labelling alternative peaks false.

Review tracking behavior

Check expected rate, search window, damping, confidence and lost-echo response. Observe whether the selected peak switches, freezes or recovers after filling. A stable output can result from holding the last value, so inspect status and raw distance. Carry low confidence and stale quality to the control system.

Apply suppression carefully

Correct avoidable nozzle, aiming or obstruction problems first. Create false-echo mapping at a documented level and preserve the before-and-after curves. Do not suppress a region that a valid high surface must enter. Test high-level detection and fault response after every mapping change.

Verify downstream meaning

Compare selected distance, calculated level, output current or register, PLC tag, HMI and alarms. A correct echo can still be displayed incorrectly through range, unit or tank-table errors. Test invalid and lost-echo states so the system does not convert uncertainty into a healthy zero or full value.

Retain a diagnostic baseline

Store geometry, curves, process states, model, firmware, configuration and accepted suppression. Capture new evidence before cleaning, reset or mechanical work. Compare with the baseline using the same scales. Define investigation triggers such as new fixed peaks, reduced margin or recurrent switching.

Engineering checklist

• Map every physical target by distance.
• Capture curves at known levels.
• Use peak movement and process context.
• Treat foam and interfaces as possible real surfaces.
• Test suppression at high level.
• Preserve quality through the output chain.

Frequently asked questions

Is the strongest peak always product?

No. Structures or another interface may reflect more strongly.

What suggests a false echo?

A repeatable peak at a fixed distance matching a physical structure is strong evidence.

When can suppression be accepted?

After geometry is understood and valid product detection, faults and alarms are retested.

Decision record

Keep a concise approval record that states the operating case, assumptions, accepted limits, responsible owner and evidence reviewed. Attach the relevant drawing, configuration, test results and unresolved deviations. Define what process, mechanical, electrical or software change requires reassessment. This record prevents a technically sound decision from becoming an unsupported setting after staff, equipment or operating conditions change.

Related measurement solutions

80 GHz radar level meters · Guided-wave radar level meters