Why PLC Alarm Logic Should Use SET/RST Instead of Simple OUT Instructions - PLC Provider Industrial Automation Supplier PLC HMI Drives

Table of Contents

Introduction

In industrial automation, alarm handling is not just about turning on a warning light — it is about capturing, preserving, and diagnosing abnormal events.

Many beginners in PLC programming tend to implement alarms using simple output logic:

If fault condition = TRUE → Alarm ON
If fault condition = FALSE → Alarm OFF

At first glance, this seems logical. However, in real industrial environments, this approach can lead to missed faults, unsafe operations, and difficult troubleshooting.

This is why experienced engineers almost always follow one rule:

Use latching logic (SET/RST), not direct output (OUT), for alarms.

Direct Output vs Latching Logic: What’s the Difference?

Direct Output (OUT)

Alarm follows real-time signal
No memory
Signal disappears → alarm disappears

👉 This is suitable for control, but not for alarm management

Latching Logic (SET/RST)

Alarm is stored (latched) once triggered
Remains active even if signal disappears
Requires manual reset (RST)

👉 This is suitable for fault tracking and safety

The Real Problem: Transient Faults in Industrial Systems

In real factory environments, many faults are not continuous — they are momentary.

Typical examples:

Emergency stop pressed briefly
Motor overload triggers for 0.2 seconds
Sensor blocked by dust for a short moment
Communication loss between PLC and drive (tens of milliseconds)

If you use OUT logic, these faults may:

Appear for 0.1–0.5 seconds
Disappear instantly
Leave no trace

Operators will see:

“The machine stopped for a moment… but no alarm?”

This is extremely dangerous.

Real Case: Conveyor Jam Detection Failure

Imagine a packaging line with a photoelectric sensor detecting material flow.

Logic used by inexperienced programmer:

If sensor = no material → Alarm ON (OUT)

What happened on site:

A small gap appears between materials
Sensor briefly detects “no material” (~0.1s)
Alarm turns ON… then OFF immediately
Operator sees nothing
Machine intermittently stops without explanation

After several occurrences, production is affected — but no clear alarm history exists.

Why SET/RST Solves This Problem

Using SET (latch) fundamentally changes the behavior:

Logic:

Fault detected → SET alarm bit
Alarm stays ON regardless of signal disappearance
Only cleared by RST (manual reset)

What happens now:

Even if the fault lasts only 0.1 seconds:

Alarm is triggered
Alarm remains visible
Operator is aware
Maintenance can investigate

👉 The PLC now has memory

Standard Structure of a Reliable PLC Alarm Program

A well-designed alarm system typically includes three essential steps:

1. Fault Trigger (SET)

When abnormal condition occurs:

IF Fault Condition = TRUE

→ SET Alarm_Bit

✔ Capture the event immediately
✔ Do not depend on signal duration

2. Alarm Hold & Output

Use the latched alarm bit to drive:

Alarm light
Buzzer
HMI alarm display

Alarm_Output = Alarm_Bit

✔ Ensures alarm remains visible
✔ Supports alarm history logging

3. Reset Condition (RST)

This is the most critical part.

Correct logic:

IF Reset_Button = TRUE

AND Fault Condition = FALSE

→ RST Alarm_Bit

Why this matters:

If you allow reset without checking fault status:

Operator may clear alarm while fault still exists
Equipment continues running in unsafe condition

👉 Reset ≠ Silence
👉 Reset = Confirm issue is resolved

Why Alarm Reset Must Be Controlled

Let’s say:

Temperature is still above limit
Operator presses reset

If your logic allows reset immediately:

Alarm disappears
Fault still exists
System runs blindly

This is a serious design flaw.

Correct approach:

✔ Fault must disappear first
✔ Then operator confirms reset

Alarm Logic Is About Safety and Traceability

Using SET/RST is not just a programming habit — it reflects industrial safety philosophy.

1. Responsibility for Safety

Even a 0.1-second abnormal signal could mean:

Mechanical collision
Overload stress
Electrical instability

Alarms must record events, not just display them.

2. Responsibility for Equipment

Short-term faults may indicate:

Early-stage equipment damage
Intermittent issues

Without alarm memory:

👉 Problems are ignored until failure becomes severe

3. Responsibility for Maintenance & Management

Modern factories rely on:

Alarm history
Fault statistics
Root cause analysis

Latched alarms allow:

Tracking how often faults occur
Identifying weak points
Improving system reliability

Best Practices for PLC Alarm Design

To build a professional alarm system, follow these guidelines:

✔ Always use SET/RST (or latch equivalent) for alarms
✔ Separate alarm logic from control logic
✔ Ensure reset requires fault cleared + operator confirmation
✔ Log alarms in HMI or SCADA system
✔ Avoid direct signal-driven alarm outputs
✔ Classify alarms (warning / critical / trip)
✔ Use timestamps for diagnostics

Practical Considerations for Maintenance Engineers

🔧 Recommended PLC and HMI Components for Reliable Alarm Systems

In real-world projects, reliable alarm logic also depends on stable hardware performance.
Using well-proven PLC and HMI platforms can significantly improve system reliability and fault traceability.

For example:

Siemens SIMATIC S7-1200 / S7-1500 PLC
- Common models:
  - 6ES7214-1AG40-0XB0
  - 6ES7511-1AK02-0AB0
- Widely used in factory automation with strong diagnostic capabilities
Allen-Bradley CompactLogix / ControlLogix
- Common models:
  - 1769-L24ER-QB1B
  - 1756-L71
- Suitable for high-reliability industrial applications with advanced alarm handling
Siemens HMI Panels
- Example:
  - 6AV2124-0MC01-0AX0 (TP1200 Comfort)
- Supports alarm history, acknowledgment, and event logging
Allen-Bradley PanelView Plus
- Example:
  - 2711P-T12W22D9P
- Ideal for integrating alarm visualization and operator interaction