Radar Echo Diagnostics: Installation Requirements and Acceptance

Echo diagnostics are not an optional screen for specialists; they are evidence that a radar level meter is tracking the intended surface. A purchase specification should require access to a raw or sufficiently detailed echo curve, selected target distance, signal strength or confidence, and diagnostic status. Installation quality determines whether those tools reveal a clear product echo or a collection of avoidable nozzle and structure reflections. Acceptance should therefore link vessel geometry, measured distances and operating states to labelled diagnostic records, rather than approving a device from one plausible displayed level.

Specify useful diagnostic access

Confirm how the exact model exposes echo curves, selected target, confidence, temperature and fault history: local display, service software, HART, fieldbus or another interface. Include any cable, modem, license and access rights in the supply scope.

Require configuration export in a retrievable format. A screenshot without tag, date, level and process state is weak evidence and cannot support later comparison after a fault.

Map physical echo sources

Measure the antenna reference plane and distances to nozzle steps, roof beams, ladders, coils, agitators, walls and vessel bottom. Mark fill and discharge streams and moving internals.

Use the geometry to label fixed targets on the curve. Do not suppress an unexplained reflection simply because the display becomes stable; it may overlap the real product at another level.

Establish representative curves

Capture curves at empty or low level, normal operation and the highest safe level. For solids, include filling and discharge profiles; for liquids, include agitation, foam, steam or condensation where relevant.

Record the independently known level and operating mode with every curve. Compare echo amplitude and target selection across states to identify weak margins before they become intermittent failures.

Control false-echo suppression

Map only verified fixed echoes outside the valid product region. Review the suppression envelope against minimum and maximum levels and preserve the original curve before changing it.

Automatic mapping can be useful but still requires engineering review. A map created while product is present may classify the real surface as an obstruction and cause lost or incorrect tracking later.

Define control-system diagnostics

Transmit low confidence, lost echo, device fault and stale-data status where the interface supports it. The PLC should not treat a held last value as a healthy measurement.

Set damping, recovery and fault delays from process dynamics. Verify that alarm action remains fast enough for the credible fill rate and remaining freeboard.

Accept and hand over

Compare radar distance, local level, output and control-system value at known points. Test fixed-target conditions, lost echo and recovery without bypassing independent protection.

Store approved curves, geometry, parameters, firmware and test results by tag. Train maintenance personnel to compare evidence before retuning sensitivity, suppression or damping.

Create a diagnostic decision rule

Define when an echo curve requires action: target movement inconsistent with process rate, reduced signal margin, repeated selection of a fixed echo, excessive antenna temperature or lost-echo events. Link each trigger to an inspection, process check or controlled configuration review. Do not permit a remote tuning change without saving the before state and identifying the physical reason. The rule helps operations distinguish a temporary process disturbance from deterioration that could make the level unreliable at a critical condition.

Engineering checklist

Require accessible echo diagnostics and backups.
Measure and label fixed targets.
Capture curves across representative states.
Control false-echo mapping against the real range.
Expose invalid and low-confidence status.
Store an as-left diagnostic baseline.

Frequently asked questions

Is a stable displayed level proof of the correct echo?

No. The radar may be tracking a fixed structure or another interface.

Should every fixed echo be suppressed?

Only verified fixed targets outside the valid product zone should be mapped.

What makes an echo curve useful later?

Tag, date, configuration, known level and process state must be recorded with it.

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