SAFEX FSoE communication between two ctrlX CORES

1 Introduction

This How-to describes how FSoE communication between FSoE devices in different EtherCAT networks can be implemented. The SAFEX #1 is the only EtherCAT device below the ctrlX CORE #1 and is configured as the FSoE master.

SAFEX #2 is the only EtherCAT device below the ctrlX CORE #2 and is configured as an FSoE slave.

The mapping of the FSoE data between the CORE #1 and CORE #2 is implemented via Network Variable Lists (NVL). The configuration of the NVL is very simple and can therefore be recommended.

The How-to basically describes the configuration of the NVL in the PLC programs of the CORE #1 and CORE #2. All programs of the CORE #1 and CORE #2 as well as the programs of the SAFEX #1 and SAFEX #2 are available for download.

1.1 Configuration PLC-program CORE #2

The SAFEX #2 is configured as FSoE-Slave. In preparation for mapping the FSoE data, a byte array is declared at the output address %QB0.

The configuration of NVL always starts on the sender side. A name (NVL_Core2toCore1) is defined there and the IP address (192.168.1.1) to which data is to be sent is also specified.

Image 1 3: CORE #2 NVL configuration as Sender

In preparation for mapping the FSoE data, a byte array is declared at the input address %IB0. That means this Input Array of CORE #2 should be send to CORE #1.