AXL E EC DI8 DO8 M12 6P
8540_en_03 PHOENIX CONTACT 22
14 Process data
14.1 TxPDO Mapping Digital Inputs
Key:
14.2 RxPDO Mapping Digital Outputs
Key:
14.3 TxPDO Mapping IO Status
Input process data
Byte Byte 0
Bit 76543210
IN 07 06 05 04 03 02 01 00
Connection X04 X03 X02 X01
Pin 24242424
DI 87654321
Bit: Process data assignment
IN: LED marking
DI: Input of the device
Output process data
Byte Byte 0
Bit 76543210
OUT 0706050403020100
Connection X08 X07 X06 X05
Pin 24242424
DO 87654321
Bit: Process data assignment
OUT: LED marking
DO: Output of the device
Bit 31... bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Reserved Supply of the module electronics and
sensors (U
S
)
Supply of the actuators (U
A
)Outputs
Reserved Undervoltage Overload Undervoltage Short-circuit Overload Short-circuit
AXL E EC DI8 DO8 M12 6P
8540_en_03 PHOENIX CONTACT 23
15 Emergency messages
Emergency messages are messages that are actively sent from the device to the EtherCAT® master if certain events/prob-
lems occur. They are an unverified service which is based on CoE. In this way, all errors can be indicated to the master by
the slave. This takes the form of messages which are specified in ETG.1000.6.
An emergency message is structured as follows:
The following emergency messages are supported by the device:
CoE emergency message
2 bytes 1 byte 5 bytes
Error code Error register Diagnostic data
Error code (hex) Error register Diagnostic data (hex) Localization Meaning
3001 Bit 2 set 00, 01, 00, 00 Device level Supply voltage overcurrent
3002 Bit 2 set 00, 02, 00, 00 Device level Supply surge voltage
3003 Bit 2 set 00, 03, 00, 00 Device level Supply undervoltage
3004 Bit 2 set 00, 04, 00, 00 Device level Surge voltage of actuator supply
3005 Bit 2 set 00, 05, 00, 00 Device level Undervoltage of actuator supply
4001 Bit 4 set 00, 06, 00, 00 Device level Overtemperature
The device sends emergency messages for an incoming and outgoing error. Once the problem has been
solved, an emergency message with the error code 0000
hex
(reset error) is sent by the slave.
The value of the corresponding bit in the error register is then 0. The diagnostic data value does not change.
AXL E EC DI8 DO8 M12 6P
8540_en_03 PHOENIX CONTACT 24
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.

2701520

Mfr. #:
Manufacturer:
Phoenix Contact
Description:
Terminal Block Interface Modules AXL E EC DI8 DO8 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