XNET Fire Network Troubleshooting

This section contains troubleshooting information for XNET fire control panels (FireFinder XLS/MXL, Desigo Fire Safety Modular, and Cerberus Pro Modular).

Handle Import Errors

Message	Situation	Do the following...
The specified file is invalid.	The selected file to import is not a valid configuration file or it is not suitable to the Desigo CC sales channel.	Retry using a new file. Check that the file is generated by a tool belonging to the same Desigo CC sales channel.
There are warnings or errors, look at the log file.	The selected file to import is valid, but some data is not supported.	Open the analysis log (Analysis Log button) to check the pre-import log.

Import cannot be performed. Import would exceed the system load.

Based on the hardware category of the installation, there is a limit to the number of objects a project can have.

The system prevents you from performing imports that would exceed this limit.

The system warns you if an import would approach this limit (90% or more of allowed objects). You can then choose whether to proceed.

If the installation allows for it, you can change the hardware category in the server properties to increase the system objects limit.

Handle Misalignments with Control Panels

Desigo CC can detect a misalignment with the panel configuration. The information provided in Event List helps you to identify the misalignment.

Message

Situation

Do the following...

Configuration outdated (Re-Import required).

An Unidentified Event occurred.

You created a new project and imported an old panel configuration file.

The panel configuration was changed after a first import, and you did not import the new configuration.

An Unidentified event is generated when a message is received with no corresponding data point.

Obtain the updated panel configuration file and re-import it into Desigo CC.

Field configuration outdated (Download required).

You imported an updated configuration file into Desigo CC, but the new configuration was not loaded into the panel.

Download the updated configuration to the panel.

Configuration outdated event

The Desigo CC configuration is not aligned with the XNET panel.

Import the latest panel configuration into Desigo CC. See Import XNET Fire Panel Configurations.

Unidentified node event, for example:
XNET Unidentified Node

Event with Unspecified node in the message text.

An XNET panel is missing in the Desigo CC configuration.

Import the latest XNET configuration into Desigo CC. See Import XNET Fire Panel Configurations.

Unidentified object event, for example:
XNET_Network 001-255 Module [Unidentified object]

Cannot identify the object of a message from an XNET panel. The device configuration in the panel is not correct (wrong addressing or missing entry).

In Event List, select the unidentified object event to identify the panel.
In the panel tool, check the panel configuration and fix the device settings. If necessary, download the revised configuration to the panel.
Export the revised configuration from the panel tool and import it again into Desigo CC.

Handle Communication Problems

Source Event

Situation

Do the following...

Communication problems with a fire panel.

A Trouble Event occurred.

The panel is not properly configured. In the Zeus tool, the management station node is missing.

In Zeus, add the management station node.

Problem	Situation	Do the following...
Enable/Disable commands from the management station do not work for some XLS/MXL sub-modules.	Unsupported Enable/Disable commands are erroneously presented for the ZAC-40 sub-modules.	Do not use these commands, they have no effect.

Problem	Situation	Do the following...
Communication problems on a MOSA-based XNET link after rebooting the MOSA Adapter (XND). The driver cannot re-establish the connection with the adapter.	After rebooting the external MOSA adapter (XND), you need to stop for at least 30 seconds and then restart the Desigo CC project from SMC. If the XND device in the MOSA adapter was replaced, you also need to configure the new XND adapter.	From SMC, stop and restart the Desigo CC project. If required, from the XNET driver page in programming mode, configure the new XND adapter. See Configure XNET Driver for XNET Card.
Communication problems on a MOSA-NRC based XNET link after rebooting the MOSA adapter (e.g. power failure).	When power is restored to the external MOSA adapter (XND) without powering off the panel, the NRC bridge is reset, causing one-way communication.	Reset the NRC-NIC bridge (both modules).
Cannot arm/disarm or activate/deactivate PAD-5 I/Os with panels connected via Local or Global FSI.	XNET Networks do not support commands on I/O when connected to a WAN driver.	Send commands from the geographical tree on the PMI.

Handle Event Problems

Problem	Situation	Do the following...
Cannot silence events from Desigo CC stations. In the Event List, the silence command icon is missing. You cannot silence events from the panel PMI either.	The silence inhibit has been configured on the panel and is currently active. The silence command is only allowed after a predefined delay.	Wait for the delay configured in the fire panel tool.
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.	Get the network connection re-established.

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.	In System Browser, select the fire panel. In Extended Operation, select Silence. 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. Instead, you can silence events from the panel PMI.	When both MNS and Fire events are pending, the silence commands must be performed in order, according to the event priority in Event List.	Silence events one after the other in the order they appear in Event List OR Silence events from the panel PMI
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. Note that the queue capacity is 150 events for the 9-queue setting (9Q) and 300 events for the 4-queue setting (4Q).	From the affected panel node, use the global Acknowledge command of the Panel Unacknowledged property in Extended Operation. After acknowledging the panel, you can reset the individual events as necessary.
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.	Check the Zeus setting in Desigo Fire Safety Modular System Limits and Compatibility.

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.	In Engineering mode, you can force a configuration alignment by creating an NCC station on the affected XNET. See the step-by-step procedure. You can then remove the NCC.
The `Event List Incomplete` status event displays for an XNET driver.	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. Note that all events are always logged in the History database and, if a printer is installed, included in the Journaling printout. See also XNET Fire Events.	To prevent event overflows, you can adjust the XNET driver configuration: In Engineering mode, in System Browser, select the XNET driver. In the XNET tab, in the Control Settings expander, modify the Max number of events property. Default value is 1500. We recommend an overall maximum of 6000 events for all fire drivers. If you have less than 4 drivers, you can increase the default limit and try to prevent overflows.

Handle FCC Symbols Problems

Problem	Situation	Do the following...
Graphic symbols that represent FCC objects do not provide any blinking for unacknowledged events. They do not support control commands either.	Neither event blinking in graphics nor control commands are provided by FCC objects.	In the graphics, replace the FCC objects with the corresponding XLS objects.

Handle Problems with NCC Graphic Map Import

Message / Condition	Situation	Do the following...
Icon file [file name including the path]not found	The icon file was not found.	Check if the icon file exists and if the required path is correct.
Error creating the background image for the graphic map [graphic map name	The file extension of the background image is not supported.	Save the background image with a supported file extension. List of supported file extensions: DWG, DXF, BMP, GIF, PCX.
Error creating the background image for the graphic map [graphic map name]from CAD file	The CAD file is corrupted.	Use a valid file.
Error retrieving symbol linked to the data point [data point ID]	The symbol linked to the data point was not found in Desigo CC.	Contact technical support.
Error reading CSV file [file name] at line [line number]	The line [line number] of the CSV file cannot be read.	Check the CSV file in SqlExport folder at line [line number] for errors.
Error creating bitmap from the icon file [file name]	Desigo CC needs to create a temporary bitmap copy of the icon images to read the image dimensions. This step may fail if the icon file is corrupted.	Check if the icon file is corrupted in the NCC icons folder by opening the file with an image editing software. If the file is corrupted, use a valid file, otherwise contact technical support.
Error creating new Depth for graphic map	A Depth is an image representing a detail of the graphic map. Some error prevented Desigo CC from creating a Depth for the graphic map.	Contact technical support.
Error retrieving icon dimensions from bitmap [file name] for the graphic map[graphic map name]	Desigo CC needs to read the dimensions of a temporary bitmap copy of the icon images to set the correct dimensions of the symbols. This step may fail if the icon file is corrupted.	Check if the bitmap file is corrupted by opening the file with an image editing software. If the file is corrupted, use a valid file, otherwise contact technical support.
Failed to initialize the graphic library	The graphic library cannot be initialized.	Contact technical support.
Failed to compile the list of graphic maps linked to data points	The list of graphic maps linked to a data point is shown in the Related Items tab. Some error prevented Desigo CC from compiling the list.	Contact technical support.
Unable to read CSV file [file name]	One of the database (CSV) files cannot be read.	Check the CSV file in the SqlExport folder for errors.
Save operation failed for symbols linked to the graphic map [graphic name]	The symbols linked to the graphic map cannot be saved.	Contact technical support.
Save operation failed for the graphic map [graphic name]	The graphic map cannot be saved.	Contact technical support.
Save operation failed for all symbols and graphic maps	Desigo CC makes a final save operation for all the symbols and graphic maps. Some error prevented Desigo CC from making the final save.	Contact technical support.
No symbol available in the management station for the imported data point [data point ID]	No symbol is available in Desigo CC for the imported data point.	Contact technical support.
Unable to save symbols linked to the graphic map [graphic map name]	The symbols linked to the graphic map cannot be saved.	Contact technical support.
Unable to find NCC data point [point name]	The NCC data point is not present in the Desigo CC configuration.	Check that the Desigo CC configuration matches the NCC configuration.
NFPA symbols are not visible in maps with black background	The black color of lines is not visible on black map background (symbols have a transparent background).	Do one of the following: - Change the background color of symbols (press CTRL+A to select all the symbols) in the Graphics Editor. - Change the background color of the DWG/DXF files in the Graphics Editor. - Modify the DWG files before importing.

Handle Problems with MM8000 Graphic Map Import

Problem	Situation	Do the following...
In MM8000 configuration with stand-alone XLS panels, the migration procedure was performed but the points configured on the MM8000 maps are not present in the graphics, nor in the geographical tree.	The algorithm cannot uniquely identify XLS panels on separate networks; it cannot migrate the configured point into MM8000 maps or populate the geographical tree. Desigo CC only supports MM8000 projects with XLS panels that are in the same XNET network.	Manually configure everything that is missing, you cannot use the migration tool.

Handle Antivirus Problems with XNET Programs

Problem	Situation	Do the following...
NCCGMS.exe (XNET), WANGMS.exe (Fire WAN), TruePort.exe (when using MOSA) programs are detected as a possible threat by the antivirus.	These programs require a special setting.	In the antivirus configuration, set NCCGMS.exe, WANGMS.exe, TruePort.exe as trusted programs/applications.

Handle Problems Removing FireFinder X-Net Extension Module

Problem

Situation

Do the following...

In SMC, even after deleting all XNET networks and drivers, cannot remove the FireFinder X-Net extension module. An error occurs that says:

XNET cannot be removed from project.

A special procedure is required, which involves the FireFinder XLS MXL extension module.

From SMC, if never done before, add the FireFinder XLS MXL extension module to the project.
At this point, remove the FireFinder X-Net extension module from the project, and this also removes FireFinder XLS MXL.

Handle Ownership and Control Issues

Problem	Situation	Do the following...
A station set for full control does not re-gain control after logging off and then logging back on.	The Ownership script provided by the template projects should not be used with stations in full control.	In Engineering mode, set the Ownership script to manual and stop it, or delete it.
User has ownership of only one panel but commands reach other panels not owned by the user.	In the Block Command Scope, the Network level was selected.	In Engineering mode, open the XNET network settings and, from the drop-down list of the Block command scope, select Panel level.