XNET Fire Network Operating Troubleshooting
This section contains troubleshooting information for XNET fire control panels (FireFinder XLS/MXL, Desigo Fire Safety Modular, and Cerberus Pro Modular).
Handle Event Problems in Operating Mode
Problem | Situation | Do the following... |
Cannot silence events from Desigo CC stations. In the Event List, the silence command icon is missing. | The silence inhibit has been configured on the panel and is currently active. The silence command is only allowed after a predefined delay. |
|
All control commands have no effects. | Network connection is down: all object properties show #COM state and object symbols in graphics display a yellow grid. |
|
Cannot silence the active sound on a fire panel from the Desigo CC Event List. No event displays that can provide the silence command. | On the fire panel, the sound was generated by a condition that did not create an event. The silence command is only available from System Manager. |
To create e specific event for unsilenced fire panels, see Configuring Unsilenced Panel Event. |
Cannot silence events from Desigo CC stations. The silence command has no effect. | When both MNS and Fire events are pending, the silence commands must be performed in order, according to the event priority in Event List. |
|
Cannot reset fire events after an out-of-queue event occurs. | As on the PMIs in the field, out-of-queue events do not appear in the Desigo CC Event List, and, if not acknowledged, prevent older events from being reset. |
|
Missing events on management station. Event List misalignment with fire panels. | In the Zeus configuration, with the Proprietary NFPA System Type setting, the Self Restoring options are not supported and may result in event misalignments. |
|
After an error during the network configuration, for example when saving an NCC station object or importing the NET configuration, you cannot treat and remove events concerning that XNET. | Due to the problem in modifying the internal configuration, Desigo CC is no longer aligned with the XNET configuration and false events may occur. |
|
The | An event overflow occurred due to an avalanche of messages to the XNET driver. Based on the event sorting criteria, some less important events do not appear in the Event List on the screen. |
|