ctrlX SAFETY with Fortress amGard proNet FSoE

Introduction

In this article we show to you how to connect a Fortress amGard proNet interlock via Safety over EtherCAT (FSoE) with a SAFEX-C1x SAFETY controller.

General Information

All functions and screen shots are based on:

• ctrlX SAFETY Engineering version >= 1.7.3.9558
• SAFEX Runtime / Firmware version >= 1.0.1.45
• ctrlX WORKS version >= 1.20.5

Fortress amGard proNet

The Fortress amGard proNet is available with the solenoid controlled by either the safety controller or standard controller. This is depicted in the model number:

• “NM” indicates the solenoid is controlled by the standard controller.
• “NR” indicates the solenoid is controlled by the safety controller.

In this example a unit with the solenoid controlled by the standard controller was used with the following ESI file:

• HL1S6SKV11SVRALY0000NNMLGLRP7EINPF09
• ESI_Fortress_amGard_proNet 1.xml

Further details including the ESI file are available from Fortress. 

Prerequisites

• A connection to the SAFEX-C1x SAFETY control and ctrlX CORE have been successfully established.
• The devices are correctly wired and have been powered on with 24V.
• Engineering tools ctrlX SAFETY and ctrlX WORKS have been started.
• ctrlX CORE has EtherCAT Master, PLC app and licenses for each app installed.

ctrlX I/O Engineering

Open ctrlX I/O Engineering from ctrlX WORKS:

Open Tools\Device Repository:

Click “Install..”:

Select Fortress ESI file, click “Open”:

The Fortress amGard proNet device is added, click “Close”:

If needed repeat the process for SAFEX-C1x ESI file installation.

Select File\New Project:

Select ctrlX CORE I/O, enter name and location of project then click “OK”:

A new project was created, right click on “ethercatmaster (EtherCAT Master)” then “Scan for Devices…”:

The SAFEX-C12 and amGard proNet are found. Click “Insert all newly scanned devices” then OK:

The devices are added to the project:

Expand SAFEX_C12 (SAFEX-C12) then right click on FSoE Connection_1\Plug Device…:

The Fortress interlock requires 4 bytes in/4 bytes out, select this data length then click “Plug Device”:

The FSoE connection is added to the project:

This step is required for the module used in this example. It may or may not be required for your module. Expand amGard_proNet (amGard proNet) then right click on Interlock_IO (Deactivated)\Plug Device.:

Select “Interlock Standard IO then click “Plug Device”:

The control for the solenoid from the standard I/O has been added:

Double click on “ethercatmaster (EtherCAT Master)” then “Slave to slave” tab to add the FSoE connections between the SAFEX-C12 SAFETY controller and amGard proNet interlock:

First the SAFEX-C12 FSoE outputs to the amGard proNet interlock inputs will be added. On the “Source” side expand SAFEX_C12 [SAFEX-C12]\FSoE_Connection1 [FSoE Master Connection 4 Bytes In/4 Bytes out 0 bye safety parameter 620D] then select 0x1A00 FSoE SafetySlaveMessage 04 Bytes In [88 Bits]:

On the “Destination” side expand amGard_proNet [amGard proNet]\Safety_Module [Safety Module] then select 0x1600 RxSPDU [88 bits] then click “Add connection”:

The connection is added to the project:

Now the amGard proNet interlock outputs to SAFEX-C12 FSoE inputs will be added. On the “Source” side expand amGard_proNet [amGard proNet]\Safety_Module [Safety Module] then select 0xA00 TxSPDU [88 bits]:

On the “Destination” side expand SAFEX_C12 [SAFEX-C12]\FSoE_Connection1 [FSoE Master Connection 4 Bytes In/4 Bytes out 0 bye safety parameter 620D] then select 0x1600 FSoE SafetyMasterMessage 04 Bytes Out [88 Bits] then click “Add connection”:

The connection is added to the project:

The I/O configuration is completed and can be downloaded to the CORE. Click on the “Download” icon from the tool bar and ensure the project downloads successfully:

ctrlX PLC Engineering

Open ctrlX PLC Engineering from ctrlX WORKS:

Select File\New Project:

Select ctrlX CORE hardware type, enter name and location of project then click “OK”:

A new project was created, right click on “DataLayer_Realtime\Select realtime data\Selectively from ctrlX CORE…”:

Use the pull-down menu to Select Source: Control ethercat_master_instance_ethercatmaster, check the boxes for all devices then click “Applies all currently selected control data to the PLC project.” Click close:

The SAFEX-C12 and amGard proNet interlock devices are added to the PLC project:

Here is an overview of the Fortress amGard proNet I/O from the documentation. Please see the Fortress website for the latest documentation and additional information:

The following PLC program was created only as a functional example for demonstration purposes of the communications. It is not written to meet any specific PL or SIL rating nor any specific risk assessment. Programming methods must be used to meet your specific application requirements:

ctrlX SAFETY Engineering

Open ctrlX SAFETY Engineering then select “Slave Device Editor” from the Main Menu:

Click “Import Slave Device” icon:

Select Fortress ESI file, click “Open”:

Click amGard proNet checkbox, click “Import”:

Click “OK” to close the Slave Device Editor and finish the import process:

If needed expand Master\ctrlX SAFETY in the Library window then drag and drop the control type you have in the workspace area:

In this case a SAFEX-C12 has been added:

Expand Slave Device\Fortress Interlocks\Network Interlocks then drag and drop an amGard proNet to the workspace area:

In the properties window for the amGard proNet select the Profile type using the pulldown menu:

The Slave Address must match the address on the unit set with the DIP switches. Please see the Fortress website for the latest documentation and additional information on setting the FSoE Slave Address:

• For this example the DIP switches were set to Slave Address 1.
• The Connection ID must match the Connection ID used in ctrlX I/O Engineering. In this example the Connection ID used was 1.
• The ECat Address must match the address assigned by the EtherCAT master in ctrlX I/O Engineering. In this example the ECat Address assigned was 1002. These values will be used in the properties along with changing the Name:

The Safety Module profile was added to the configuration and can now be used in the Functional Scheme:

Since the module used for this example is configured to use the standard controller for control of the solenoid. Programming can be added to monitor the bits. The following ctrlX SAFETY program was created only as a functional example for demonstration purposes of the communications. It is not written to meet any specific PL or SIL rating nor any specific risk assessment. Programming methods must be used to meet your specific application requirements:

ctrlX Example Projects

The following example projects are included in the SAFEX-C1x - Fortress Example Projects.zip available for download below:

• ctrlX I/O Engineering
• ctrlX PLC Engineering
• ctrlX SAFETY Engineering

Additional  Resources

• How-to All about ctrlX AUTOMATION
• Quick Start Guide ctrlX CORE
• Quick Start Guide Licensing
• Create safety PLC project with ctrlX SAFETY Engineering
• Set up a ctrlX CORE and PLC Programming

Downloads