AXL E EC DI16 M12 6P
8541_en_03 PHOENIX CONTACT 22
16 Synchronization
There are two modes for synchronizing the application which can be selected in the engineering system.
- SM Synchronous (process data update when an SM event occurs)
- DM Synchronous (process data update when a SYNC0 event occurs)
16.1 SM Synchronous
In this mode, the EtherCAT
®
communication system and the I/Os operate asynchronously. The I/Os are in Auto-Run mode
and run with the minimum cycle time possible for the current device configuration. This mode is set by default in the device.
16.2 DC Synchronous
In this mode, the I/Os are synchronized with the EtherCAT
®
cycle.
The implemented Distributed Clocks unit is used for the time synchronization of processes.
In synchronous operation, the time points for outputting and reading the process data of the individual I/Os are synchronized
with the higher-level network. EtherCAT
®
Distributed Clocks (DC) are used for this synchronization.
Figure 11 Synchronization model
The figure shows the synchronization model of the EtherCAT
®
device. The “DC Sync0 event” is used for synchronization.
After the “Sync0 event” has occurred and a fixed delay time (output delay time) has elapsed, the process data is output.
The inputs are likewise read after a fixed delay (input delay time).
In order to activate DC Synchronous mode in TwinCAT
®
, it must be selected in the DC tab under Operation
Mode and the slave must be started up again by means of the EtherCAT
®
master.
TwinCAT
®
should be operated in Run mode.
AXL E EC DI16 M12 6P
8541_en_03 23
PHOENIX CONTACT GmbH & Co. KG • 32823 Blomberg • Germany
phoenixcontact.com
17 Restoring the default settings
The following option is available for restoring the default set-
tings:
Write the value “1” to CoE object 2F00
hex
. After power-
ing on again, the device is in the default settings.
18 Firmware started
Once you have connected the power, the firmware is
started.
After completion of the boot process of the firmware, the
RDY LED lights up green or flashes depending on the bus
status.
19 Firmware update
It is possible to carry out a firmware update via EtherCAT
®
.
The File Access over EtherCAT
®
(FoE) mechanism is used
for this, which is provided via your engineering system.
For detailed instructions for the firmware update with
TwinCAT
®
, please refer to
AH EN FIRMWARE UPDATE AXL E EC.
The application note can be downloaded at
phoenixcontact.net/products.
20 Device description file (ESI)
In the case of EtherCAT
®
, a device description file is re-
quired for various configuration tools.
This file is called EtherCAT
®
Slave Information (ESI).
A single ESI file is provided for all Axioline E EtherCAT
®
de-
vices.
21 Endianness
EtherCAT
®
uses Little Endian format. All variables, param-
eters, and data in this document are in Little Endian format
(Intel), i.e., LSB/MSB.

2701521

Mfr. #:
Manufacturer:
Phoenix Contact
Description:
Terminal Block Interface Modules AXL E EC DI16 M12 6P
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union

Products related to this Datasheet