Alarms
Rules
| # | On | Name | Watches | Condition | Deadband | Delay | Relay | Notify | Value | State | Count |
|---|
Add / edit a rule
Address is the image address — the same number the SCADA reads and the TCP offset shown on the Poll Map, not the PLC’s own address.
On-delay must hold before the alarm raises; deadband is how far the value must come back before it clears. Both exist because a value sitting on its limit will otherwise chatter the alarm, the relay and the webhook several times a second.
R1 and R2 already signal bus-healthy and block-fault; an alarm claiming one overrides that while it is active. R3 and R4 are free.
On-delay must hold before the alarm raises; deadband is how far the value must come back before it clears. Both exist because a value sitting on its limit will otherwise chatter the alarm, the relay and the webhook several times a second.
R1 and R2 already signal bus-healthy and block-fault; an alarm claiming one overrides that while it is active. R3 and R4 are free.
Notification
POSTs a small JSON body on every raise and clear: unit, alarm name, state, address and value. Point it at Node-RED, Home Assistant, or the Mini SCADA’s own webhook channel.
Plain HTTP only, deliberately. TLS on this chip costs tens of kilobytes of flash this build cannot spare, and buys little when the target is a box on the same LAN. For phone notifications, let the SCADA do it — it already has push, history and acknowledgement.
Plain HTTP only, deliberately. TLS on this chip costs tens of kilobytes of flash this build cannot spare, and buys little when the target is a box on the same LAN. For phone notifications, let the SCADA do it — it already has push, history and acknowledgement.