docs(#420): final reconciliation — alarms-over-gateway feature complete; C.1 superseded #467

2026-07-15T15:23:52-04:00

dohertj2 commented

2026-07-15 15:23:52 -04:00

Advances/closes #420. The issue (filed 2026-05-01 as "4 inert scaffolds + D.1 smoke") is stale — current master + the mxaccessgw sibling repo show the feature landed on both sides, and its central premise (the WM_APP-pump design) was ruled out by the 2026-05-01 probes and reimplemented via the wnwrap consumer.

Current state per acceptance item:

A.2/A.4 (mxaccessgw): native alarms served via WnWrapAlarmConsumer (over WNWRAPCONSUMERLib.wwAlarmConsumerClass) + FailoverAlarmConsumer + AlarmDispatcher; StreamAlarms active-alarm snapshot (20 alarms verified live 2026-05-29/05-31).
A.3 (mxaccessgw): NotWiredAlarmRpcDispatcher gone (only in generated proto); ack routes MxGatewayClient.AcknowledgeAlarmAsync → AlarmClient.AlarmAckByGUID.
lmxopcua: GalaxyDriver : IAlarmSource wires GatewayGalaxyAlarmFeed (→ OnAlarmEvent, native metadata incl. operator-comment) + inbound ack via GatewayGalaxyAlarmAcknowledger; native feed live-proven by GatewayGalaxyAlarmFeedLiveTests.
C.1 (SdkAlarmHistorianWriteBackend/aahClientManaged): SUPERSEDED. The whole Wonderware sidecar was retired; alarm-history writes cut over to the HistorianGateway (GatewayAlarmHistorianWriter, SendEvent path), live-verified 2026-07-15 (R2-06/R2-08, 6/6). The target no longer exists in the tree.
D.1 smoke + banner: captured (alarms-d1-smoke-artifact.md); banner reconciled to ✅ historical here.

Sole residual: a full running-server → OPC UA A&C round-trip on the Windows parity rig (Part 9 Acknowledge → gateway → AVEVA, real Galaxy alarm via the System Platform IDE) — needs live Galaxy + human IDE interaction; any final mxaccessgw integration-test polish is tracked in that repo.

Docs-only: alarms-over-gateway.md final-reconciliation banner + alarms-d1-smoke-artifact.md status note.

Advances/closes #420. The issue (filed 2026-05-01 as "4 inert scaffolds + D.1 smoke") is **stale** — current master + the mxaccessgw sibling repo show the feature landed on both sides, and its central premise (the WM_APP-pump design) was ruled out by the 2026-05-01 probes and reimplemented via the wnwrap consumer. **Current state per acceptance item:** - **A.2/A.4 (mxaccessgw):** native alarms served via `WnWrapAlarmConsumer` (over `WNWRAPCONSUMERLib.wwAlarmConsumerClass`) + `FailoverAlarmConsumer` + `AlarmDispatcher`; `StreamAlarms` active-alarm snapshot (20 alarms verified live 2026-05-29/05-31). - **A.3 (mxaccessgw):** `NotWiredAlarmRpcDispatcher` gone (only in generated proto); ack routes `MxGatewayClient.AcknowledgeAlarmAsync` → `AlarmClient.AlarmAckByGUID`. - **lmxopcua:** `GalaxyDriver : IAlarmSource` wires `GatewayGalaxyAlarmFeed` (→ `OnAlarmEvent`, native metadata incl. operator-comment) + inbound ack via `GatewayGalaxyAlarmAcknowledger`; native feed live-proven by `GatewayGalaxyAlarmFeedLiveTests`. - **C.1 (`SdkAlarmHistorianWriteBackend`/`aahClientManaged`): SUPERSEDED.** The whole Wonderware sidecar was retired; alarm-history writes cut over to the **HistorianGateway** (`GatewayAlarmHistorianWriter`, `SendEvent` path), live-verified 2026-07-15 (R2-06/R2-08, 6/6). The target no longer exists in the tree. - **D.1 smoke + banner:** captured (`alarms-d1-smoke-artifact.md`); banner reconciled to ✅ historical here. **Sole residual:** a full running-server → OPC UA A&C round-trip on the Windows parity rig (Part 9 Acknowledge → gateway → AVEVA, real Galaxy alarm via the System Platform IDE) — needs live Galaxy + human IDE interaction; any final mxaccessgw integration-test polish is tracked in that repo. Docs-only: `alarms-over-gateway.md` final-reconciliation banner + `alarms-d1-smoke-artifact.md` status note.

dohertj2 added 1 commit 2026-07-15 15:23:53 -04:00

docs(#420 ): final reconciliation — alarms-over-gateway feature complete; C.1 superseded

v2-ci / build (pull_request) Successful in 4m15s

Details

v2-ci / unit-tests (pull_request) Failing after 10m50s

Details

2791ab5810

#420 (filed 2026-05-01 as '4 inert scaffolds + D.1 smoke') is stale. Current
master + the mxaccessgw sibling repo show the feature landed on both sides:

- mxaccessgw A.2/A.4: native alarms served via the wnwrap consumer
  (WnWrapAlarmConsumer over WNWRAPCONSUMERLib.wwAlarmConsumerClass) +
  FailoverAlarmConsumer + AlarmDispatcher; StreamAlarms active-alarm snapshot
  (20 alarms verified live). The WM_APP-pump premise this issue was written
  against was ruled out by the 2026-05-01 probes; the design pivoted to wnwrap.
- mxaccessgw A.3: NotWiredAlarmRpcDispatcher gone (only in generated proto);
  ack routes MxGatewayClient.AcknowledgeAlarmAsync -> AlarmClient.AlarmAckByGUID.
- lmxopcua: GalaxyDriver : IAlarmSource wires GatewayGalaxyAlarmFeed
  (-> OnAlarmEvent, native metadata incl. operator-comment) + inbound ack via
  GatewayGalaxyAlarmAcknowledger; native feed live-proven by
  GatewayGalaxyAlarmFeedLiveTests.
- C.1 (SdkAlarmHistorianWriteBackend / aahClientManaged): SUPERSEDED. The whole
  Wonderware sidecar was retired; alarm-history writes cut over to the
  HistorianGateway (GatewayAlarmHistorianWriter, SendEvent path), live-verified
  2026-07-15 (R2-06/R2-08, 6/6). The target no longer exists in the tree.

Updated the alarms-over-gateway.md banner (final reconciliation) + the
alarms-d1-smoke-artifact.md status note. Sole residual = a Windows-parity-rig
running-server OPC UA A&C round-trip (needs live Galaxy + human IDE).

dohertj2 merged commit 97e06b4747 into master

2026-07-15 15:24:07 -04:00

dohertj2 referenced this pull request

2026-07-15 15:24:29 -04:00

alarms-over-gateway: wire worker AlarmClient + pin SDK call site (4 inert scaffolds + D.1 smoke) #420

dohertj2 referenced this pull request

2026-07-15 15:35:27 -04:00

docs: reconcile alarms-over-gateway banner with audited source #419

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#467