dohertj2/lmxopcua
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

Native alarm conditions stay inactive after a rebuild when the alarm-tag set is unchanged #641

New Issue
Closed
opened 2026-10-08 16:33:37 -04:00 by dohertj2 · 1 comment
dohertj2 commented 2026-10-08 16:33:37 -04:00
Owner
Copy Link
Copy Source

A full address-space rebuild recreates native alarm conditions inactive.
The host does not re-subscribe alarms when the subscribed alarm set is unchanged.
Result: an active native alarm (any source) shows inactive until its next transition.
Found during MTConnect CONDITION work (#626).

A full address-space rebuild recreates native alarm conditions inactive. The host does not re-subscribe alarms when the subscribed alarm set is unchanged. Result: an active native alarm (any source) shows inactive until its next transition. Found during MTConnect CONDITION work (#626).
dohertj2 commented 2026-10-08 18:51:52 -04:00
Author
Owner
Copy Link
Copy Source

Landed on master (merge 5af9aae2, ddd76782..bd23f557): native alarm conditions are carried across a rebuild when the alarm-tag set is unchanged, so they no longer stay inactive; unclaimed captures are discarded. Verified: unit suites + live docker-dev gate: UNS-reference deploy rebuild=True 'carried 2', Xtravel stays Active sev800 with original timestamp. Related split-off: #647 (FOCAS native alarms unroutable). Closing.

Landed on master (merge 5af9aae2, ddd76782..bd23f557): native alarm conditions are carried across a rebuild when the alarm-tag set is unchanged, so they no longer stay inactive; unclaimed captures are discarded. Verified: unit suites + live docker-dev gate: UNS-reference deploy rebuild=True 'carried 2', Xtravel stays Active sev800 with original timestamp. Related split-off: #647 (FOCAS native alarms unroutable). Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto-managed
queue management
 cross-driver
queue management
 driver/abcip
queue management
 driver/ablegacy
queue management
 driver/focas
queue management
 driver/mqtt
MQTT / Sparkplug B broker-subscribe driver
 driver/opcuaclient
queue management
 driver/s7
queue management
 driver/twincat
queue management
 phase/1
queue management
 phase/2
queue management
 phase/3
queue management
 phase/4
queue management
 phase/5
queue management
 phase/6
queue management
 queue/blocked
queue management
 queue/done
queue management
 queue/failed
queue management
 queue/in-progress
queue management
 queue/queued
queue management
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#641
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?