XNET Fire Events
This section describes the different types of fire events, and briefly presents how to handle the three main types: Alarms, Troubles, and Supervisories.
NOTICE
MAXIMUM LIMITS IN THE NUMBER OF EVENTS:
Driver Events Overflow
Desigo CC limits the amount of XNET events that are presented in Event List. The limit is necessary to ensure the system integrity in critical conditions and it is set to a value configurable.
See Configure XNET Driver for XNET Card. See also XNET Fire Network Operating Troubleshooting.
If the driver overflow condition is reached, Desigo CC prints and logs but does not show the most recent and less important events. In addition, a Status event displays to signal the driver overflow condition (Event List Incomplete).
Panel Events Overflow
Desigo CC keeps Event List aligned with the XNET control panels, which have a limited event buffer. The size of the buffer depends on the control panel type and version:
- MXL and XLS V11: 300 events per event category.
- XLS V12 and later, Modular: 300 events per event category when the legacy queues are configured (Alarm, Supervisory, Security, Trouble) or 150 events per event category when the extended queues are configured (MNS1, Alarm, MNS2, Gas/Emergency, Supervisory, Security/Building Safety, Trouble, MNS Trouble, Other).
In case of a queue overflow, Desigo CC behaves as the control panel and does not show the events that do not fit in the panel queues. Note that all events are anyway printed to journaling printers and logged in the history database. In addition, a Trouble (or MNS Trouble) event displays to signal the queue overflow condition.
Recommended Actions
In case of an event overflow, proceed as follows:
- Since the event report is incomplete, make sure to have a local check on the danger situations in the affected areas/buildings.
- To make Desigo CC receive the missing events, fully process all events in Event List (Acknowledged, Reset, and Close). Note that abnormal conditions still active will trigger new events. The overflow event disappears when the overflow condition is no longer present.
- See if a configuration adjustment is possible in the engineering troubleshooting.
- More in general, study and try to remove the causes of the avalanche of events. Contact the technical support to get assistance.
Journaling and Archiving
All disregarded events are printed on the journaling devices and stored in the history database.
Fire Alarms
Fire alarms—as well as Fire Building/Securities, CO/Emergency, and Mass Notification (MNS) alarms—appear in the user interface with maximum priority, by the most relevant positions on the screen. Event List provides the event information including cause, source, location, date/time, suggested actions, and so on.
Station operators are expected to treat fire alarms immediately to prevent fire from spreading.
Basic control commands become available in Event List as icon buttons. These include acknowledge, silence/unsilence, and reset.
Acting on the event buttons on the left allows operators to launch more advanced treatment procedures that can vary depending on the specific configuration.
Fire Troubles
Troubles in the fire system may delay the recognition of a fire event and have very serious consequences. Therefore, operators are expected to treat the fire troubles as soon as possible.
As for fire alarms, Event List provides all the available event information.
Fire Supervisories
No direct danger is caused by Fire Supervisories events, but they can negatively influence the fire system functionality. As for fire alarms and troubles, Event List provides all the available event information.
NOTE:
Audio alert: Desigo CC has no control over subsequent alarm notification signals.