Modify the Navigation display to trigger the Critical Condition Summary window
- Last UpdatedApr 24, 2025
- 1 minute read
For the Critical Condition Summary window to be displayed automatically, the Navigation display (or any display that is always open on the easy eXtended Operator Station [ezXOS] computer) needs to be modified to subscribe to the criticalAlarm topic. The standard NAVMENU.XEM can be used as a reference for modifications that would need to be added to a custom Navigation display. The eXtended Editor (XE) can be used to view the display and modify a custom display.
There are two key areas that need to be added, or modified, to a custom Navigation display:
-
A Publish/Subscribe (PubSub) Subscriptions object needs to be added to the display. In the sample display, this object is named pubCriticalAlm. The PubSub object needs to have a SubscriptionValueChanged event that will be used to trigger the display. In the sample display, refer to the function pubCriticalAlm_SubscriptionValueChanged() for details on how to code this event.
-
Verify that the ezXOS computer has DNA Permission - Critical_Alarms set. If this is not set, then the Critical Condition Summary window should not be displayed. In the sample display, refer to the function sqlPermCheck_StopEvent() for details on how to code the display for this permission.