Configuration
EK9300
40
Version: 3.2.6
5.4
EK9300 – Configuration example
PDO Mapping
The process data on the EtherCAT side are described via the PDO Mapping. The individual terminals bring
along a pre-defined PDO mapping, i.e. a practical combination of individual PDOs, via the ESI file (EtherCAT
description file).
Fig. 30: EK9300 - Predefined PDO selection dialog
These combinations are described in turn on the Profinet side using different submodules and thus process
data; i.e. each pre-defined PDO mapping has an associated submodule.
Fig. 31: EK9300 Sub-modules
Such modular terminals always have a fixed submodule plugged into subslot 1 on the EK9300. This is the
placeholder for the terminal itself; i.e. the generally valid diagnosis for the terminal is operated via this. The
actual process data are plugged into subslot 2 and the PDO mapping on the EC-master is generated on their
basis.
SDO Mapping
Each of the plugged-in subslots can bring along parameterization data. The Service Data Objects (SDOs)
are transmitted via these data, i.e. the SDOs are mapped to record data sets. The objects 0x8xxx and
0xF8xx are always mapped. Since the indices on the PROFINET side are only vendor-specific from 0 -
0x7FFF, the EtherCAT objects 0x8xxx correspond to the PROFINET record indices 0x3xxx and the EC
objects 0xF8xx to the PROFINET index range 0x48xx. In PROFINET the records are always written during
the controller start-up phase; they are transferred internally to the EtherCAT master as start-up SDOs. This
means that the internal EC master is also restarted during a PROFINET restart.
