Set Up an EtherCAT Network (Scenarios)

When setting up a network, various settings are necessary in order to connect devices to each other and exchange data. The steps necessary for configuration depend on the application, and, thus on the devices used and their roles as master or slave.

The following applications will be considered:

Note

Using the Term “Controller”

In this description, devices that can be programmed in CODESYS V3 or e!COCKPIT are referred to as “controllers” (most PFCs, for example). The scenarios described for “controller (master)” devices also apply to Touch Panels 600 and Edge controllers if they act as control panels, i.e., if they have a corresponding license (provided by the vendor or added subsequently).
Controllers cannot be operated as EtherCAT slaves.

The procedure described below for the individual applications represent the general process for performing the configuration.
The order may vary. Depending on the communicating device selected, individual steps may be largely or entirely omitted.

  1. Select Devices
    For devices to be used in e!COCKPIT, they must be known within e!COCKPIT, i.e. they must be available in the product catalog. The installation of e!COCKPIT automatically makes WAGO devices available in the product catalog. Third-party devices are added to the product catalog by importing a device description file.
  2. Place Devices in the Topology View
    Devices are dragged from the product catalog into the Topology view.
  3. Disconnect Ethernet Ports and Enable the EtherCAT Port
    The master Ethernet ports are separated and port X2 is enabled for the EtherCAT master function.
  4. Disable Broadcast Protection Function
    Since EtherCAT devices only communicate via broadcast, the broadcast protection function must be disabled in the controller.
  5. Connect Devices
    Devices are first connected in the Topology view and then in the Communication view via EtherCAT connectors.
  6. Make the Device Settings on the “Settings” Panel
    The device settings on the “Settings” panel are displayed in a context-sensitive way for the specific selected device and its communication interfaces and can be modified as needed.
  7. Program Application
    In the Device Detail view, the I/O map is created between the local bus and application variables, and the applications are programmed
    Note: This step is only relevant for controllers.
  8. Configure Slave
    Connections and slave data points can be created and configured in the data point configurator. These are published and can be used by the master (see also Slave Settings in the Data Point Configurator).
  9. Configure Connection between Master and Slave
    In the fieldbus configurator, you can set the communication relation on the data point level. It is determined which data points of the slave are to be available in which form for the master (see also Master and Connection Settings in the Fieldbus Configurator).
  10. Access Data Points
    Slave data points that have been created can be accessed from the master’s application.