Reconfiguring FS20

Scenario

You want to reconfigure one or more fire panels of an existing FS20 system without losing the fire object references configured in the Desigo CC applications.
The reconfiguration may be necessary when:
- The fire panel configuration was changed to modify the previous BACnet IDs.
- The fire panel was moved from one BACnet network to another, for example after a network split or merge.
- The fire network connection was moved from a Desigo CC server to a FEP or vice versa.

In all such cases, you need to change the Desigo CC configuration, but you may want to save the fire object references in Desigo CC applications such as graphics, user-defined views and more.
The re-configuration described in this section is a migration process that you can start from the main BACnet network node.
This migration can automatically arrange the fire object references from the existing fire panel node to your new fire panel node.

NOTE 1: In case of a site merge, the procedure also applies to panels whose BACnet ID has not changed.

NOTE 2: In the main BACnet network node, the Fire System Migration tab is available when at least two fire panels have been imported in one or more FS20 BACnet networks.

For background information, see the reference section.

Prerequisites

• The appropriate panel extension is installed and included in the active project.
• The Danger Management Common extension is installed and included in the active project.
• In Desigo CC, the fire panel you want to reconfigure is fully configured.
• In the FS20 tool, you have modified the fire panel configuration as necessary, and exported the SiB-X file.
  NOTE: In the new fire panel configuration, you can set a new BACnet ID or reuse the same BACnet ID.
  In the first case, keep track of the old and new BACnet IDs that you can use to match the correct pairs during the migration procedure.
  The second scenario, reusing the same BACnet ID, is only supported if you create a new BACnet network in Desigo CC AND associate a new BACnet driver to the network.
• System Manager is in Engineering mode.
• System Browser is in Management View.
• You have full scope visibility of all fire objects in both the Source and Target panel.
• You have full scope visibility of all objects involved in the reconfiguration (see FS20 Reconfiguration Limits and Compatibility).

2 – Run the Reconfiguration Procedure

• To speed configuration, make sure the Desigo CC Transaction Mode is set to Simple or the Automatic Switch of Transaction Mode is set to True.
  The automatic switch setting is recommended. Without it, to re-enable the logs, you need to set the Transaction Mode to Logging at the end of the configuration procedure.

1. In System Browser, select Project > Field Networks > [BACnet Network].
   NOTE: In case the two FS20 are on different networks, select the BACnet network where the new FS20 is connected.

2. Select the Fire System Migration tab.

• Page 1 of 2 displays: Select the migration type.

3. In Migration Types, select FS20 reconfiguration.

4. Click to proceed to the next page.

• Page 2 of 2 displays: Select the panels involved in the migration.

5. In Source Item, select the Network where the old FS20 is located, then the Panel itself.

6. In Target Item, select the Network where the new FS20 is located, then the Panel itself.

7. Click Start.

8. The System Manager dialog box appears, click Yes to confirm the start of the migration process.

• The migration procedure replaces old FS20 objects with new FS20 objects in all applicable cases (see FS20 Reconfiguration Limits and Compatibility).
  NOTE: In case of object mismatch during the search a System Manager dialog box appears, click Yes to proceed anyway.

• The Migration Log button become available.

9. Click Migration Log to show the import log.
   For information about the log files, see the reference section.