Profinet configuration

General

The EP9300-0022 is always implemented in the Profinet controller (Master) with the help of a GSDML file. The GSDML file contains all the parameterization data required for the operation of the EP9300-0022 on the Profinet controller. The configuration tool reads this file and then provides the data to the user.

The EtherCAT devices that can be operated on the EP9300-0022 are also specified in the GSDML file. Not all EtherCAT devices are supported. Therefore, inform yourself first whether the EtherCAT devices that you wish to use are also supported by the EP9300-0022.

Data in the DAP (Device Access Point)

2 x 2 bytes of data are located in the DAP of the GSDML file:

• ECCycleCounter (2 bytes). This is incremented with each EtherCAT cycle (1 ms), provided the EtherCAT Master is in the "OP" state.
• Status (2 bytes). This indicates individual status information bit by bit. These are occupied as follows:
• Bit 0 - IsSynchron – is set when the EP9300-0022 is operated as a PTP Slave or an IRT device and is synchronous.
• Bit 1 - IsPTPMaster – is set when the EP9300-0022 is operated as a PTP Master.
• Bit 2 - ECFrameError – is set when a problem is determined at the EtherCAT output. The Profinet diagnostics or the alarms must be read in order to obtain further information.

Parameters in the DAP

Activate PN Fallback Value
Off -> EtherCAT data are written to zero.
On -> there is a possibility to use another default value with outputs. With digital outputs, for example, the current output process value can be frozen or set to 0 or 1 in case of a Profinet communication error.

Data Presentation
Intel Format -> data are represented in Intel format.
Motorola Format -> data are represented in Motorola format. In Word variables, for example, the high and low bytes are exchanged.

EBus error behaviour
Set IOs to 0 -> input and output data are set to zero in case of an EtherCAT error.
Legacy -> input data retain their last state, but are no longer updated; output data can still be set (depending on the position of the terminal).

Mapping

The EP9300-0022 is typically used in a group with EtherCAT devices that are connected to the EtherCAT output. The EtherCAT devices are a component of the GSDML; the EtherCAT devices are parameterized from the Profinet controller.

You must enter the EtherCAT devices in the hardware configurator exactly as they are physically connected. If EtherCAT star hubs and/or EtherCAT junctions are used, it is important to know the order in which the other EtherCAT devices were entered in the process image (see EtherCAT configuration).

Behavior when starting the EP9300-0022 All EtherCAT devices must be present when starting or resetting the EP9300-0022. This means that all connected EtherCAT devices must be supplied with voltage at the same time before the start so that the EP9300-0022 also starts up properly on the Profinet. A solution can be constructed more flexibly with the CX8093.

Configuration of the EtherCAT devices

There are 4 types of EtherCAT devices:

• EtherCAT devices without process data
• EtherCAT devices with "simple" process data without parameterization
  (as a rule, simple EtherCAT devices with digital inputs or outputs)
• EtherCAT devices with "simple" process data with parameters
  (as a rule, EtherCAT devices with analog inputs or outputs)
• EtherCAT devices with different process data and parameters
  (for example incremental encoders)

The rule for all of them is: they must be entered in the configuration.

Grouping digital inputs and outputs (pack terminals)

The digital input and output terminals can also be grouped according to their process data. This option can be used with 2 or 4-channel terminals. To do this a 2 or 4-channel pack terminal (without asterisk) must be appended to the GSDML file. In order to fill the byte, a 2 or 4-channel pack terminal (with asterisk) must be appended next. The terminals must be physically and systematically plugged in one behind the other or logically. The byte limit must not be exceeded.

Example

2-channel pack (without asterisk), after that 3 modules from 2-channel pack terminals (with asterisk) may be appended.
Not permitted:
2-channel pack (without asterisk), then 2 modules from 4-channel pack terminals (with asterisk). This exceeds the byte limit.

EtherCAT devices with different mapping options

Some EtherCAT devices offer the option to represent different process data. These are represented differently on the basis of the parameters. In the Profinet controller such an EtherCAT device is represented by submodules. The standard mapping is always integrated. If you want to use a different mapping that deviates from the standard, then delete the standard submodule and insert the one that you wish to use. It may be the case that, contradictory to the documentation for the EtherCAT device, not all mappings can be used under EP9300-0022.

Example of an EL5101

EtherCAT gateways

EtherCAT gateways support several submodules; the first or basic module is loaded immediately, then the modules for the process data must be created. These must then also be parameterized on the master side of the corresponding gateway. Not all features of an EtherCAT gateway can be used on EP9300-0022.

EL6631-0010

The PROFINET device terminal enables two different PROFINET networks to be connected; only one device interface is supported on the EK. A default station name can be assigned and IP settings made via parameterization data (GSDML). Note that the complete maximum data length of the EL6631-0010 cannot be used. The length is dependent on the other EtherCAT devices attached to the EP9300.

EL6731-0010

The PROFIBUS slave terminal enables communication with a PROFIBUS master. The PROFIBUS address is specified via the parameter settings (in the GSDML) in the terminal. Only pure process data can be exchanged.

EL6692

The EtherCAT slave terminal enables communication with an EtherCAT master. Only pure process data can be exchanged.

EL6652-0010

The EtherNet/IP slave terminal enables communication with an EtherNet/IP master; only one slave interface is supported on the EK. The IP address and subnet mask are specified via the parameter settings (in the GSDML) of the terminal. Only pure process data can be exchanged. The terminal on the EK supports only one slave interface.