Configuring SecuriFire Modbus Commands Macros
Scenario: You want the acknowledgment command to work also from Event List for zone events. For this purpose, you have to create a specific macro for the management station.
Reference: For background information, see SecuriFire Modbus Commands.
Workflow diagram:
Prerequisites:
- Desigo CC is configured to integrate the SecuriFire system. For instructions, see Integrating SecuriFire Modbus System.
- System Manager is in Engineering Mode.
Steps:
1 – Create a Scope Rule for the Network
- In System Browser, select Management View.
- Select Project > System Settings > Scopes.
- In the Scopes tab, click New
and select New Definition.
- In the Scopes tab, drag the Modbus network (in this case, SecuriFire) that you want to include from System Browser into the Scopes field of the Scope Rules section.
- The Scopes field is automatically set based on the linked objects.
- Click Save
.
- Enter a name and description for the new scope. For example, SecuriFire Network Scope.
2 – Create a Macro Folder for the Event Commands Macros
- In System Browser, select Application View.
- Select Applications > Logics > Macros.
- in the Macro tab, click New .
- In the New object dialog box, enter a name and description.
- Click OK.
- The newly-created folder is added to System Browser.
3 – Create the Event Commands Macros
- In System Browser, select the Manual Navigation check box to retain the Macro tab.
- Drag the target scope object (in this case, SecuriFire Network Scope) from System Browser to the empty area inside the Macro tab.
- A new row is created.
- Configure the other fields as follows:
- Property: Aggregate Alarm [Command]
- Command: Ack [Ack]
- Click Save As
.
- In the Save Object As dialog box, enter the following name and description:
- BLOCK_ACK_ManagementView_FieldNetworks_[SecuriFireNetworkName]
- Click OK.
- The new macro is added to System Browser under the specified macros folder.
NOTICE
Abiding by Naming Conventions is Essential
Since the name of the macro is strictly connected to the name of the network in the specific project, this action must be performed after the creation of the network itself, and must be performed manually, project by project.
Abiding by the above-mentioned naming convention is mandatory for the acknowledgement command to work for zone events.
