Reconfiguring FS20

Scenario: You want to reconfigure an existing FS20 system, fully configured in Desigo CC, to a new FS20 node that reuses the same detection lines.
This can be necessary when:
- The BACnet configuration was changed and new BACnet IDs must be used for the FS20
- The FS20 was moved from one BACnet network to another, for example after a network split or merge.
- The FS20 connection was moved from a server to a FEP or vice versa

The migration procedure can automatically arrange the fire object references in the Desigo CC configuration.

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

Reference: For background information, see the reference section.

Workflow diagram:

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.
• The FS20 you want to reconfigure is fully configured in Desigo CC.
• The new FS20 panel has been configured to support the same fire objects as the old FS20.
  NOTE: Keep track of the BACnet IDs of old and new panels that you can use to match the correct pairs during the procedure.
• 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 (maps, macros, reactions, and so on, see FS20 Reconfiguration Limits and Compatibility).

Steps:

2 – Run the Reconfiguration Procedure

1. To speed configuration, set the transaction mode to simple.

2. 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.

• 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.

10. When finished, to resume normal operational monitoring, set the transaction mode back to logging.