From 5e87f7e16fcaea7132b2776afc743f923373d896 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Sun, 31 May 2026 10:12:47 -0400 Subject: [PATCH] docs(alarms): record 2026-05-31 live re-confirmation of native alarm feed Independently re-ran the D.1 alarm-source smoke against the live gateway (10.100.0.48:5120) to back the native MxAccess alarm-event claim with a fresh empirical run, not just the original 2026-05-29 capture. --- docs/plans/alarms-d1-smoke-artifact.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/plans/alarms-d1-smoke-artifact.md b/docs/plans/alarms-d1-smoke-artifact.md index b85e1955..75fb2e4f 100644 --- a/docs/plans/alarms-d1-smoke-artifact.md +++ b/docs/plans/alarms-d1-smoke-artifact.md @@ -3,6 +3,12 @@ > **Status (2026-05-29): alarm-source leg VERIFIED. Historian-write leg still > pending the Windows sidecar + live AVEVA Historian.** > +> **Re-confirmed 2026-05-31** against the same gateway (`http://10.100.0.48:5120`): +> the Skip-gated live test passed again, pulling a native `Raise` transition +> (`Galaxy!TestArea.TestMachine_001.TestAlarm001`, raw sev 500 → OPC UA 750/High, +> category `TestArea`, operator comment `Test alarm #1`) through the production +> consumer. Independent re-run, not the original capture. +> > This is the D.1 deliverable called for by `docs/plans/alarms-worker-wiring-plan.md` > — captured evidence that a live Galaxy alarm reaches lmxopcua through the native > gateway path (not the sub-attribute fallback). It supersedes the "A.2 blocked"