Radar Echo Curve Commissioning: Acceptance and Baseline Records

An echo curve is useful only when it is connected to real geometry and a known process condition. A clean-looking graph does not by itself prove that the radar tracks the intended surface or will remain reliable during filling, foam, dust or maximum level. Commissioning should identify major returns by distance, verify the selected echo, record margin and tracking, control any suppression and preserve comparable files. The result becomes a baseline for acceptance and later troubleshooting rather than a screenshot without context.

Prepare the geometry map

Before interpreting diagnostics, record antenna reference plane, empty distance, tank zero, nozzle, walls, ladders, coils, agitators, inlets, bottom and moving structures. Include tolerances and every adapter. Convert their locations to expected radar distances. This map allows fixed peaks to be explained physically and exposes discrepancies between drawings and the installed vessel.

Capture known process states

Save curves at documented levels and process conditions, ideally including low, intermediate and high states plus representative filling or agitation. Record product, temperature, pressure, foam, dust and antenna condition. Use consistent display scales and export formats. A curve without time and process reference cannot support comparison or root-cause analysis.

Identify the intended echo

Compare selected distance with an independent reference and the geometry map. Check whether the radar tracks liquid, foam, solids cone, interface or a fixed target. Review competing peaks and noise. The strongest echo is not automatically correct, especially with reflective internals or low dielectric products. State which surface the control system expects.

Assess signal margin and continuity

Evaluate the desired return relative to noise and competing echoes through the operating range. Observe quality, confidence and transitions rather than a single amplitude at one level. Correlate temporary loss or switching with filling, agitator position, foam or dust. Define acceptable continuity and response from the operational consequence.

Control false-echo suppression

Investigate and correct avoidable mechanical targets before creating a suppression map. Build the map at a known level that does not hide valid process surfaces. Record the exact settings and before-and-after curves. Prove high-level detection after mapping. Aggressive suppression can make a trend stable while removing the echo needed for an alarm.

Review tracking and lost-echo behavior

Set expected rate, damping, search window and hold or fault response from the process. Test what happens when the selected echo weakens, moves rapidly or disappears. Confirm that the PLC or DCS receives bad quality or fault status rather than an apparently healthy held value. Avoid using slow damping to disguise incorrect echo selection.

Link diagnostics to functional tests

At each acceptance point, record raw distance, calculated level, output current or digital variable, system value, quality and alarm state. Test power and communication recovery. The echo curve supports the measurement layer, while loop and logic tests prove the downstream path; neither should be substituted for the other.

Maintain the baseline

Store curves, geometry, model, firmware, configuration, process state and approver under the equipment tag. Capture new evidence before cleaning, reset, firmware update or mechanical change. Compare with the baseline using the same scales. Define triggers such as reduced margin, new fixed peaks or repeated lost echo that require investigation.

Engineering checklist

Map physical targets by radar distance.
Capture curves at known process states.
Prove the selected echo is the intended surface.
Assess margin and tracking continuity.
Control and test false-echo suppression.
Link diagnostics to output and alarm tests.

Frequently asked questions

Is a strong product echo enough for acceptance?

No. Tracking, competing echoes, output scaling and failure behavior also require verification.

When should a false-echo map be created?

After geometry is understood and avoidable physical causes are corrected.

What makes two echo curves comparable?

Known process state, consistent scale, same configuration and recorded model and firmware provide context.

Need a project-specific review? Send process data, drawings, photographs and acceptance criteria through our contact page.