Radar Level Integration with DCS and PLC: Signal-to-Alarm Testing

DCS or PLC integration must preserve the meaning and health of the radar measurement from antenna to operator. A correct field value can become wrong through duplicated scaling, mismatched units, reversed range, discarded status or stale communication. A reliable design defines where conversions occur, how faults are represented, which alarms and final actions use the value, and how changes are controlled. Acceptance should test physical levels and failure states through the complete signal chain instead of checking only the transmitter or one software tag.

Define the signal contract

Document raw distance, calculated level, volume if used, engineering units, range, update interval, resolution, quality and alarm states. Assign one location for each conversion and one owner for the tank table. The radar, input card and software should not independently apply offsets or linearization without a controlled architecture.

Engineer the physical interface

For 4–20 mA, calculate loop voltage, resistance, barriers, isolation, fault current, shielding and grounding. For HART or digital networks, define topology, addresses, register or object revisions, data type and byte order. Record cable and channel identity so field and control drawings remain traceable.

Map faults and quality

Carry lost echo, device fault, over-range, under-range, maintenance mode and communication loss into explicit DCS or PLC status. Define stale-data age and held-value behaviour. Never convert an invalid signal to a normal zero level, and ensure operators can distinguish a real stable process from a frozen measurement.

Design alarms and interlocks

Set alarm points, hysteresis, delay, priority and acknowledgement from process consequence and rate of change. Verify whether high, low or diagnostic alarms initiate pumps, valves, gates or conveyors. Independent protective devices should remain logically and physically separate where the risk assessment requires them.

Control changes and access

Restrict range, damping, tank-table and alarm changes to authorized roles. Back up transmitter and control configurations and record revision, reason, approver and effective time. Remote write access requires deliberate cybersecurity controls; routine monitoring should not create an undocumented path to alter field parameters.

Test end to end

Use known or simulated values at low, middle and upper range and compare radar display, signal or register, input, engineering tag, HMI, historian and reports. Test power loss, open circuit, lost echo and network interruption separately. Confirm final actions, timestamps, quality, recovery and removal of all temporary forces.

Validate response timing

Measure the time from a real or simulated level change to transmitter output, PLC or DCS tag, alarm annunciation and final equipment action. Include radar damping, analog filtering, network polling, logic delays and actuator stopping. Compare the total with the maximum credible process rate and remaining margin. Record tested conditions and distinguish a software force from a full physical-path test. Repeat timing after changes to filters, scan rates, gateways or alarm logic. A correct final value can still be operationally unsafe if it arrives too late for the control or protection decision.

End-to-end test record

The signed test sheet should identify the simulated or physical level, transmitter distance, loop current or digital value, controller engineering value, alarm state and final action at each point. Test normal rise and fall, sensor fault, stale communication and power recovery. Record bypasses and restore them under independent check. This evidence separates a successful display test from a complete control-path test and gives future fault investigations a known-good reference for every boundary between the instrument, network and control system.

Engineering checklist

• Define values, units, quality and owners.
• Verify analog or digital physical interfaces.
• Expose invalid and stale measurements.
• Test alarms through final equipment.
• Restrict and audit configuration changes.
• Prove normal and failure states end to end.

Frequently asked questions

Should the PLC use radar distance or level?

Either can work, but conversion location, reference and ownership must be explicit.

What is the most dangerous integration error?

A failed or stale value that still appears healthy to control logic and operators.

Does a software simulation prove the field loop?

No. Combine simulation with physical or electrical checks appropriate to each layer.

Related measurement solutions

80 GHz radar level meters · Industrial IoT gateways