FS20 Sinteso Fire Troubleshooting

This section contains FS20 Sinteso troubleshooting information.

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.

The misalignment condition indicated by the Unidentified Event does not disappear after importing the latest panel configuration.

This occurs when the BDV applies by default the Direct activation of the base sounder by zone or channel to detectors with a base sounder.

You need to change the default base sounder setting for all affected detectors.
To do that, you temporarily add a base sounder. Apply the following procedure:

1) In the fire panel engineering tool:
- Open and expand the Hardware tree.
- Select the detector device with a base sounder.
- Right-click and select New > Base sounder.
- In the Overview pane of the detector, make sure that Direct activation of base sounder is set to No direct activation (default).
- In the tree, select the Base sounder you added.
- Right-click and select Delete.
- Repeat the previous steps for all detectors with a base sounder.
- Export the SiB-X file.

2) In Desigo CC :
- Reimport the SiB-X file

Handle Communication Errors

Message

Situation

Do the following...

In large configurations, occasional fault events due to communication errors with fire panels.

Some BACnet communication parameters need to be adjusted in case of large configurations (for example more than 50 panels).

In the BACnet Device node of all fire panels, open the Timing and status Info expander of the BACnet tab and modify the following parameters as indicated:

- Use auto ADPU timeout unchecked
- ADPU timeout = 20
- Device ping rate = 10
- ADPU retries = 3
- Allowed failed ping = 3

In the fire panel configuration tool, make sure to set the following parameters:
- ADPU timeout = 20
- ADPU segment timeout = 10

Handle Alarm-Handling Countdown Problems

Condition	Situation	Do the following...
Fire alarm-handling countdown timers do not display or are stuck at 00:00.	T1/T2 timers display must be enabled. In addition, management stations and the fire panels must be set to the same local time zone.	Check the fire network configuration. Check the time zone configuration on the management stations (Date and Time Settings in Windows) and on the fire panels (in the configuration tool, see Global System Configuration > Country Settings).

Handle Alarm-Handling Problems

Condition	Situation	Do the following...
In the event treatment, operators cannot send out all or some of the event-control commands such as Acknowledge, Reset, or Silence/Unsilence.	Users must be enabled to event commanding in the Security settings of the group they belong to (Command Groups of the Scope Rights). In addition, the security for BACnet Reset and Silence/Unsilence commands requires the Write capability on the status and configuration of properties (Property Groups of the Scope Rights).	In Engineering mode, select Management View and then System Settings > Security. In the Security tab, select the security [group] of the operator. In the Scope Rights expander: - In Property groups, set Write (W) for Sta. (Status) and Con. (Configuration). - In Command Groups, make sure to select Eve. (Events). Instead, Sta.(Standard) is not required for event handling as it concerns commands such as enable/disable.
Silence / Unsilence command cannot be sent, or incorrectly handled	In case of multiple Silence / Unsilence commands, sent for example by: Block commands Multiple selection in Event List Multiple selection in System Browser The command either cannot be sent or does not appear to succeed.	This is a known issue for panel firmware versions prior to 81.17.70.
Incorrect Device Failure event of the FG2004 X300 gateway.	The FG2004 gateway is part of the imported configuration, but not supported by the communication protocol.	Disable the incorrect event. Select the FG2004 object in System Browser and do one of the following: In Extended Operation, select Alarm Suppression > Enable. In the Property expander of the Object Configurator tab, select Alarm.Fault. Then, in the Alarm Configuration expander, click Valid and select Alarm Configuration > None. Finally, click Save .
In the Panel Configuration Tool > Fire Control > Details tab, you have selected ‘Activation’ event hidden checkbox but the Activation events are still displayed on Operating terminal, stored in event memory and printed.	The default value for ‘Activation’ event hidden is false. This option is deliberately not considered in Desigo CC and consequently the two events are displayed regardless of the ‘Activation’ event hidden value.	Repeat the following customization for each control and control effect: In the Property expander of the Object Configurator tab, select Alarm.OffNormal. Then, in the Alarm Configuration expander, click Valid and select Alarm Configuration > None. Finally, click Save .