docs: alarms-over-gateway plan banner — record A.2 dev-rig finding #418

dohertj2 · 2026-04-30T21:31:36-04:00

dohertj2 commented

2026-04-30 21:31:36 -04:00

Summary

Replaces the "ships as a follow-up gated on dev-rig validation" banner with the actual finding from the dev-rig inspection.

The MXAccess COM Toolkit at C:\Program Files (x86)\ArchestrA\Framework\Bin\ArchestrA.MXAccess.dll exposes no alarm-event family — only OnDataChange, OnWriteComplete, OperationComplete, OnBufferedDataChange. AVEVA's alarm-subscription managed assemblies (aaAlarmManagedClient, ArchestrAAlarmsAndEvents.SDK) are x64-only and incompatible with the worker's x86 bitness.

Two operator-facing paths forward documented inline:

Stay on the value-driven sub-attribute path (current production behaviour). Operator-comment fidelity is the only v1 regression.
Add an x64 alarm-helper sub-process alongside the worker that loads aaAlarmManagedClient and forwards transitions over a named-pipe IPC. Recovers full v1 fidelity but adds operational complexity.

Full architectural notes live in the mxaccessgw repo at src/MxGateway.Worker/MxAccess/MxAccessAlarmEventSink.cs.

## Summary Replaces the "ships as a follow-up gated on dev-rig validation" banner with the actual finding from the dev-rig inspection. The MXAccess COM Toolkit at `C:\Program Files (x86)\ArchestrA\Framework\Bin\ArchestrA.MXAccess.dll` exposes no alarm-event family — only `OnDataChange`, `OnWriteComplete`, `OperationComplete`, `OnBufferedDataChange`. AVEVA's alarm-subscription managed assemblies (`aaAlarmManagedClient`, `ArchestrAAlarmsAndEvents.SDK`) are x64-only and incompatible with the worker's x86 bitness. Two operator-facing paths forward documented inline: 1. **Stay on the value-driven sub-attribute path** (current production behaviour). Operator-comment fidelity is the only v1 regression. 2. **Add an x64 alarm-helper sub-process** alongside the worker that loads `aaAlarmManagedClient` and forwards transitions over a named-pipe IPC. Recovers full v1 fidelity but adds operational complexity. Full architectural notes live in the mxaccessgw repo at `src/MxGateway.Worker/MxAccess/MxAccessAlarmEventSink.cs`.

dohertj2 added 1 commit 2026-04-30 21:31:38 -04:00

docs: alarms-over-gateway plan banner — record A.2 dev-rig finding 5ed26d2ec6

Replaces the "ships as a follow-up gated on dev-rig validation"
banner with the actual finding from the dev-rig inspection: the
MXAccess COM Toolkit on this AVEVA install does not expose any
alarm-event family, and the AVEVA alarm-subscription managed
assemblies (aaAlarmManagedClient, ArchestrAAlarmsAndEvents.SDK)
are x64-only and incompatible with the worker's x86 bitness.

Two operator-facing paths forward documented inline:

1. Stay on the value-driven sub-attribute path (current production
   behaviour). Operator-comment fidelity is the only v1 regression.

2. Add an x64 alarm-helper sub-process alongside the worker that
   loads aaAlarmManagedClient and forwards transitions over a
   named-pipe IPC. Recovers full v1 fidelity but adds operational
   complexity.

The full architectural notes live in the mxaccessgw repo at
src/MxGateway.Worker/MxAccess/MxAccessAlarmEventSink.cs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

dohertj2 merged commit 69f02fed7f into master

2026-04-30 21:31:42 -04:00

dohertj2 deleted branch track-d1-followup-plan-banner

2026-04-30 21:31:42 -04:00

dohertj2 referenced this issue from a commit

2026-04-30 21:31:44 -04:00

Merge pull request 'docs: alarms-over-gateway plan banner — record A.2 dev-rig finding' (#418) from track-d1-followup-plan-banner into master

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#418