Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
Silencing a high-level alarm does not lower the liquid, repair a failed measurement or prove that a filling valve has stopped. Radar level alarm reset needs a clear meaning at the operator screen and in the control logic. Otherwise one button can appear to restore normal operation while an unsafe or unresolved condition remains.
Write the state changes before choosing screen buttons
Describe acknowledgement as the operator's response to an annunciation. Describe the active process condition separately. If the design includes a latched trip, define when that memory may be cleared and whether a further command is needed to resume operation. The approved cause-and-effect design determines these behaviours; they are not universal radar settings.
| Action or state | What must remain distinguishable |
|---|---|
| Acknowledged | The operator has seen the alarm; the initiating condition may still exist. |
| Condition cleared | The measured condition has returned within the defined limits, with valid measurement. |
| Trip reset | The approved reset requirements have been satisfied; this need not start equipment. |
| Restart permitted | All required permissions and operating checks are satisfied, not merely the level alarm. |
Include invalid measurement in the radar level alarm reset review
A missing or stale level must not be mistaken for a confirmed return to normal. Define how the logic treats loss of signal, communication interruption, a held value and instrument recovery. A newly received number also needs the validity and freshness checks specified for the system.
For a hazardous process, the responsible safety designer must establish the required independence, integrity and response. A normal control transmitter, an operator alarm and an independent protective function are different duties. This article does not establish a safety integrity level or a permitted reset arrangement for a particular tank.
The METRAVON MV-RD12 can be specified with different output electronics. Confirm the signal and fault information available from the ordered version before writing the receiving logic. Its ordinary product specification is not evidence that the complete instrument-to-valve protective function is certified.
Test the transitions, not just one high-level indication
Under an authorised test plan, check what happens when the condition remains active after acknowledgement, returns to normal, becomes invalid and subsequently recovers. Where a latch is specified, test the permitted and denied reset cases. Record the displayed state, logic state and actual equipment response separately.
Plan any simulation with operations because it can cause real valve or pump movement. State which part of the chain each test covers. Forcing a PLC input does not demonstrate the sensor's detection of liquid. At completion, account for every temporary override and test value before releasing the system.
Q1. Should acknowledgement automatically restart filling?
Do not use acknowledgement as an undocumented restart command. The operating and safety design must explicitly define the permissions and actions required after an alarm or trip.
Q2. Is a quiet alarm screen evidence that the condition cleared?
No. The display may be acknowledged, shelved or disconnected from fresh data. Check the active condition and measurement quality rather than sound alone.
Q3. What belongs in the instrument enquiry?
Identify the required measured variable, receiving input and fault indication. Provide the approved control requirements for interface review without assuming the transmitter itself implements the plant's reset logic.
Summary
Keep operator acknowledgement, valid level recovery and restart permission explicit. Submit the MV-RD12 output and fault-signal requirements alongside the control-system specification.
