System CPX-E Bus module CPX-E-EC module CPX-E-EC Festo – CPX-E-EC-EN – 2017-07 – English 3 Table of Contents 1 About this document 4 1.1 Further applicable documents 4 1.2 Target

System CPX-E

Bus module CPX-E-EC

Description

Protocol

EtherCAT

Function

Parameterisation

8071155

2017-07

[8071157]

Bus module CPX-E-EC

2 Festo – CPX-E-EC-EN – 2017-07 –

Original instructions

CPX-E-EC-E N

EtherCAT®, TwinCAT® are registered trademarks of the respective trademark owners in certain countries.

Symbols used:

Note

Material damage or loss of function

Recommendations, tips, references to other documentation

Bus module CPX-E-EC

Festo – CPX-E-EC-EN – 2017-07 – English 3

Table of Contents

1 About this document 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Further applicable documents 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Target group 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Product version 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Product label 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 Specified standards 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Function 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 General remarks 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.1 Web server 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.2 Device description file 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.3 Crossover detection (auto MDI/MDI-X) 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.4 Distributed Clocks 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.5 Product design 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.6 Display components 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.7 Control components 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.8 Connecting components 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Address assignment 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Addressing 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Basic rules for addressing 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Addressing example 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 Diagnostics options 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.1 LED indicators 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.2 Status bits 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.3 I/O diagnostic interface 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5 Diagnostics via EtherCAT 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.1 Diagnostics via SDO access 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.2 Diagnostics via diagnostics history 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.3 Emergency message 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Parameterisation 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Object directory (Modular Device Profile) 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A Technical Data 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B Terminology 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 About this document

4 Festo – CPX-E-EC-EN – 2017-07 – English


This document describes the function and parameterisation of the product stated in the title. Safe use of the

product is described in a separate document � 1.1 Further applicable documents.

1.1 Further applicable documents

Document Contents

Description of system CPX-E (CPX-E-SYS) Detailed description of system CPX-E

Instructions for use of system CPX-E (CPX-E-SYS) Instructions and important notes on mounting,

electrical installation and maintenance tasks for

system�CPX-E

Instructions for use of bus module CPX-E-EC (CPX-E-EC) Instructions and important notes on the use and safe

usage of the product

Documentation for the components in system CPE-X

and the connected peripherals

Information on use of the components

Documentation for the higher-order controller and the

additional participants in the network

Information on commissioning and parameterisation

of�the components

Tab. 1.1

For all available product documentation � www.festo.com/pk.

1.2 Target group

This document is intended for qualified specialised personnel. Experience in EtherCAT networks is required in order

to understand this documentation.

1.3 Product version

This document refers to the following product versions:

Product Version number

CPX-E-EC Bus module CPX-E-EC, revision 1 onward

Tab. 1.2

The product version can be identified from the product label or with the help of appropriate software from Festo.

Appropriate software for identifying the product version can be found in the Festo Support Portal

� www.festo.com/sp.

Information on using the software can be found in the integrated Help function.

There may be an updated version of this document for these or later product versions.

� Check whether a corresponding version of this document is available � www.festo.com/sp.



1.4 Product label

The product label is located on the left-hand side of the module. Scanning the printed Data Matrix Code with an

appropriate device calls up the Festo Support Portal, with information appropriate for the product. Alternatively, the

Product Key (11-digit alphanumeric code or product label) can be entered in the search field of the Support Portal.

1 Designation2 Part number/serial number3 Revision status4 Data Matrix Code5 Product Key6 Approvals/warning symbols7 Pin assignment

1

2

3

4

5

7

6

Fig. 1.1

1.5 Specified standards

Version status

EN 60529:2013-10 IEC 61784:2014-08

EN 61000-6-2:2009-04 IEC 61918:2013-08

EN 61000-6-4:2011-09 IEEE 802.3:2014-00

IEC 60204-1:2014-10 ISO/IEC 8802-3:2000-10

IEC 61158:2014-07 NE 21:2015-05

Tab. 1.3

2 Function


2 Function

2.1 General remarks

The product is intended for the operation of system CPX-E in an EtherCAT network. Data is transmitted on the basis

of Industrial Ethernet following the IEEE 802.3 protocol.

The product has two Ethernet interfaces (RJ45) and support any topologies.

The EtherCAT address (0 … 4095) can be set manually using DIL switches, which means that the “Hot Connect”

function (for coupling and decoupling devices during operation) can be used.

2.1.1 Web server

The integrated web server provides read access to the key parameters and diagnostic functions of system CPX-E.

The web server can be reached through the “Ethernet over EtherCAT (EoE)” protocol and must be

configured accordingly in the controller.

The IP address and subnet mask must be assigned individually.

To access the web server, the following settings must be made:

– IP address on PC (e.g. 192.168.2.100)

– IP address on the higher-order controller for the connection to the PC (e.g. 192.168.2.10)

– IP address and subnet mask on the higher-order controller for the connection to the bus module

(e.g. 172.16.1.1; 255.255.0.0).

– Activation of “Ethernet over EtherCAT (EoE)” and “IP Routing” on the higher-order controller

– An IP address and subnet mask must be assigned to the bus module

(e.g. 172.16.1.100; 255.255.0.0)

The subnet mask of the bus module must correspond with the subnet mask for the connection to the

bus�module on the higher-order controller.

– In the Windows program “cmd.exe,” the following routing setting must be entered:

“route add 172.16.0.0 mask 255.255.0.0 192.168.2.10”

2.1.2 Device description file

The project planning for the bus module in the controller software of the higher-order controller is implemented by

a�device description file (ESI file). This contains all the information required to parameterise system CPX-E via

controller software (e.g. Beckhoff TwinCAT).

The device description file is available on the Festo Support Portal

� www.festo.com/sp.

2.1.3 Crossover detection (auto MDI/MDI-X)

The product supports crossover detection (auto MDI/MDI-X), so both patch cables and crossover cables can

optionally be used.

When using patch cables and crossover cables in the same network, crossover detection must be

activated in the higher-order controller.

2.1.4 Distributed Clocks

The product supports the “Distributed Clocks” for the precise synchronisation of participants in an EtherCAT

network. Applications can therefore be implemented that required simultaneously coordinated actions.

The following CPX-E modules allow synchronized operation when “Distributed Clocks” is used:

– Digital input module CPX-E-16DI(-P)

– Digital output module CPX-E-8DO(-P)

– Counter module CPX-E-1CI

2 Function


2.1.5 Product design

1 LED indicators2 Rotary and DIL switches3 Terminal strip for operating voltage supply UEL/SEN

[XD]4 Terminal block interlock5 Network connection [OUT]6 Linking7 Network connection [IN]

1

2

34

7

6

5

Fig. 2.1

2.1.6 Display components

1 Network-specific LED indicators:– EtherCAT operating status [Run]

(green,�orange)

– EtherCAT error [Error] (red, orange)

– Connection status [LA IN]/[LA OUT] (green)

2 System-specific LED indicators:– Operating voltage supply UEL/SEN [PS]

(green)

– Load voltage supply UOUT [PL] (green)

– System fault [SF] (red)

– Force mode [M] (yellow)

1

2

Fig. 2.2

2 Function


2.1.7 Control components

Rotary/DIL

switches

Function

Using the 3 rotary switch, EtherCAT “Explicit Device ID” of the bus module is set with

hexadecimal coding.

Possible settings:

0 = saved EtherCAT address, no “Explicit Device ID” assigned

1 … 4095 (1h … fffh) = permissible address range

In case of a setting of 0, the address of the bus module is automatically assigned by the

EtherCAT master (auto increment).

Factory setting: 0

The internal system diagnosis or bootloader is set by the DIL switch � Tab. 2.2.

Tab. 2.1

DIL switches Function

DIL 1: OFF

DIL 2: OFF

No diagnostics1)

DIL 1: OFF

DIL 2: ON

Status bits activated

DIL 1: ON

DIL 2: OFF

I/O diagnostic interface activated

DIL 1: ON

DIL 2: ON

Bootloader activated2)

1) Factory setting

2) For recovery after a failed firmware update using the Festo Field Device Tool (FFT).

Tab. 2.2

Changes to the rotary and DIL switches only take effect following a restart of the bus module.

2 Function


2.1.8 Connecting components

Port [IN], [OUT] Signal Designation

1 TD+ Transmitted data +

2 TD– Transmitted data –

3 RD+ Received data +

4 n.c. –

5 n.c. –

6 RD– Received data –

7 n.c. –

8 n.c. –1) Shield Functional earth

1) Housing

Tab. 2.3

Connection [XD]1) Signal

0 +24 V DC operating voltage supply UEL/SEN

1

2 0 V DC operating voltage supply UEL/SEN

3

1) The connections XD.0 and XD.1 and also XD.2 and XD.3 are interconnected in the terminal strip.

Tab. 2.4

2 Function


2.2 Address assignment

The system CPX-E is composed of a different number of inputs and outputs, depending on the number and type of

modules CPX-E used and the parameterisation of the bus module. The inputs and outputs are assigned

automatically within the system CPX-E.

The address assignment (number of allocated inputs and outputs) on the system CPX-E must be determined prior

to�commissioning.

– A maximum of 10 I/O modules + bus module is permitted in one system CPX-E.

– The address space of a system CPX-E is limited. The bus module provides the system CPX-E with

a�maximum address space of 64 bytes for inputs and 64 bytes for outputs.

– Activated diagnostic functions as well as status bits or the I/O diagnostic interface reduce the size

of�the available address space.

2.3 Addressing

2.3.1 Basic rules for addressing

– The address assignment of the inputs does not depend on the address assignment of the outputs.

– The numbering goes from left to right.

– The bus module counts as a module with 0 inputs and 0 outputs when the status bits and the I/O diagnostic

interface are deactivated.

– Activated status bits occupy 16 inputs (only 8 inputs are used).

– An activated I/O diagnostic interface occupies 16 inputs and 16 outputs.

– The inputs and outputs of different module types are assigned separately from each other.

– The I/O addresses are assigned in ascending order according to the module number.

2.3.2 Addressing example

1 Bus module CPX-E-EC (with status bits)– Status bits activated

– I/O diagnostic interface deactivated

2 Digital input module CPX-E-16DI3 Digital output module CPX-E-8DO4 Digital output module CPX-E-8DO5 Analogue input module CPX-E-4AI-U-I6 Analogue output module CPX-E-4AO-U-I

Module

no.:

0 1 2 3 4 5

1 2 3 4 5 6

Fig. 2.3

The address assignment for the system CPX-E presented is shown in Tab. 2.5.

Module no. Module Input address Output address

0 Bus module CPX-E-EC (with status bits) I0 … I15 –

1 Digital input module CPX-E-16DI I16 … I31 –

2 Digital output module CPX-E-8DO – O0 … O7

3 Digital output module CPX-E-8DO – O8 … O15

4 Analogue input module CPX-E-4AI-U-I I32 … I95 –

5 Analogue output module CPX-E-4AO-U-I – O16 … O79

Tab. 2.5

2 Function


2.4 Diagnostics options

The module supports various diagnostics options, depending on the configuration and parameterisation of the

system CPX-E.

Diagnostics option Description Detailed information

LED display components

System-specific System status and errors are displayed

directly on the module via LED indicators.

� Instructions for use of system CPX-E

� Description of system CPX-E

Network-specific Network status and errors are displayed

directly on the module via LED indicators.

� 2.4.1

� Instructions for use of CPX-E-EC

Status bits Common diagnostic messages are

transmitted cyclically to the interface as

internal inputs. Access is via the control

software, independently of the interface

and master.

� 2.4.2


I/O diagnostic interface Network-independent diagnostic interface

with read access to the internal data of

the system CPX-E at the I/O level.

� 2.4.3


Festo Software Malfunctions or errors are displayed

directly on a PC, meaning that diagnostics

is also possible from a higher automation

level.

� Online help for software

EtherCAT Diagnostics as part of the EtherCAT

function via the network.

Detailed module- and channel-related

error detection by means of control

software.

� 2.5

Tab. 2.6

2 Function


2.4.1 LED indicators

This document describes the network-specific LED indicators. The system-specific LED indicators are

described in the documentation for the system CPX-E � 1.1 Further applicable documents.

Connection status [LA IN], [LA OUT]

LED (green) Significance Remedy

Lights up

Network connection OK –

Flickers1)

Data traffic ongoing –

Off

No network connection � Check network connection.

1) Fast flickering acts as lamp; the light intensity depends on the data traffic.

Tab. 2.7

EtherCAT operating status [Run]

LED (green,

orange)

Function Remedy

Lights up green

Operational

Normal operating status

–

Flashes green

Pre-operational

Configuration of the EtherCAT network.

–

Flashes green1)

Safe-operational

Only the input signals (e.g. sensor data) are

updated. Outputs retain the current status.

–

Flickers green

Bootstrap

The bus module receives a firmware update.

–

Lights up orange

Bootloader or firmware update active –

Off

Init

Normal status after activation or after a restart.

–

1) Single flash: One-time, brief flashing (1x flashing, pause, 1x flashing, etc.)

Tab. 2.8

2 Function


EtherCAT error [Error]

LED (red,

orange)

Function Remedy

Lights up red

Severe communication error (application

controller failure)

Possible causes:

– Application controller does not answer

– Watchdog timeout by ESC

� Contact Festo service

� www.festo.com.

Flashes red

Configuration error (invalid configuration)

No network connection.

Possible causes:

– Line/connection interrupted

– No connection to master

– Master is not active

� Check the network connections.

� Check the configuration and addressing of

the bus module.

Flashes red1)

EtherCAT status change (unsolicited state

change)

Status change from “Operational” to

“Safe-operational” based on a synchronisation

error.

–

Flashes red2)

Application watchdog timeout

Watchdog timeout by the Sync Manager

–

Flashes red3)

Reserved –

Flickers red

Booting error

Error (checksum) in application controller flash

memory

–

Lights up orange

Bootloader or firmware update active –

Off

No error –

1) Single flash: One-time, brief flashing (1x flashing, pause, 1x flashing, etc.)

2) Double flash: two-time, brief flashing (2x flashing, pause, 2x flashing, etc.)

3) Triple flash: three-time, brief flashing (3x flashing, pause, 3x flashing, etc.)

Tab. 2.9

2 Function


2.4.2 Status bits

System CPX-E provides 8 status bits for displaying global common diagnostic messages.

The status bits are configured like inputs and supply coded diagnostic information in the form of 0 or 1 signals. If all

status bits are supplying a 0 signal, there is no error. If, in contrast, a status bit supplies a 1 signal, there is a fault. In

order to make use of the status bits function, the bus module of the system CPX-E must be configured accordingly.

If different errors occur simultaneously on different types of modules, errors cannot be distinguished.

The�I/O diagnostic interface can be used to distinguish errors clearly � 2.4.3 I/O diagnostic interface.

You can find detailed information about status bits in the “Description of system CPX-E”

� 1.1 Further applicable documents.

2.4.3 I/O diagnostic interface

The system CPX-E provides an I/O diagnostic interface in the form of 16 input bits and 16 output bits for reading

detailed diagnostic information. The I/O diagnostic interface can be used, for example, to precisely determine the

module and channel on which an error has occurred. In order to make use of the I/O diagnostic interface, the bus

module of the system CPX-E must be configured accordingly.

You can find detailed information about the I/O diagnostics interface in the “Description of system CPX-E”

� 1.1 Further applicable documents.

2 Function


2.5 Diagnostics via EtherCAT

The availability of diagnostic information depends on the settings of the DIL switch and parameterisation.

To guarantee that error messages of system CPX-E are automatically displayed in the controller software,

the I/O diagnostic interface must be activated.

2.5.1 Diagnostics via SDO access

Diagnostic information can be requested from the higher-order controller through SDO access.

The corresponding objects are listed in the appendix � 3.1 Object directory (Modular Device Profile).

2.5.2 Diagnostics via diagnostics history

The last 63 diagnostic messages of the bus module can be displayed via diagnostic object 0x10F3. An error message

referenced with a code is displayed for every event (warning, error, information).

The diagnostic messages are translated using the ESI file and can be read from the controller software in this way.

Structure of diagnostics object 0x10F3

Index (hex) Subindex Description Data type Values Access1)

0x10F3 0 Diagnostics history U8 RO

1 Maximum messages U8 64 RO

2 Newest message U8 RO

3 Newest acknowledged message U8 RW

4 New message available BOOL RO P

5 Flags U16 0x0000 RW

6 … 70 Subindex 006 … 070 BYTE [23] RO

1) RO = read only; RW = read/write; RO P = read only (PDO mappable)

Tab. 2.10

The diagnostic messages of the bus module are saved in the diagnostics history.

02 00 00 E1 02 02 02 37 1F C5 9D 61 31 00 00 00 05 00 02 05 00 80

Sample diagnostic message:

1 2 3 4 5 6 7 8

The individual values of the diagnostic message are explained below.

Values of diagnostic message

Name1) Value from example (hex) Explanation

1 Diag Code 02 00 00 E1 CPX-E error number (2 = short circuit)2)

E1 = CPX-E error number

E8 = Error code to DS401

2 Flags 02 02 Number of parameters in the diagnostic message (2)

and diagnostics type 2 (error message)

3 Text-ID 02 37 Reference to ESI file with the clear text of the dia

gnostic message (<TextId>#x3702)

4 Time stamp 1F C5 9D 61 31 00 00 00 Local time stamp and/or CD time stamp

(Time since the start of the bus module)

5 Flag parameter 1 05 00 Type of parameter 1 (UNSIGNED8)

6 Parameter 1 02 CPX module number

7 Flag parameter 2 05 00 Type of parameter 2 (UNSIGNED8)

8 Parameter 2 80 Channel 80h (Channel 128d)

1) According to ETG.1020

2) � Description of the CPX-E system

Tab. 2.11

2 Function


The Text IDs 3700h … 37FFh correspond with the CPX error numbers (0 … 255). Additional information can

be found in the “Description of system CPX-E” � 1.1 Further applicable documents.

In addition to the CPX-specific text-IDs, the ESI file also includes EtherCAT-specific text-IDs.

EtherCAT-specific text-IDs from ESI file

Text-ID (hex) Clear text (English) Clear text (English)

3800 Identification check failed for configured

module

Identification check failed for configured

module

3801 Identification check skipped – PLC has not

written to Object 0xF030

Identification check skipped – PLC has not

written to Object 0xF030

000F Calculate bus cycle time failed (local timer

too�slow)

Calculate bus cycle time failed (local timer

too�slow)

0011 Sync Manager invalid address Sync Manager invalid address

0012 Sync Manager invalid size Sync Manager invalid size

0013 Sync Manager invalid settings Sync Manager invalid settings

Tab. 2.12

The diagnostic message are written to a buffer (80 bytes).

2 operating modes are available for processing diagnostic messages:

– Overwrite mode:

When the number of diagnostic messages reaches 64, old diagnostic messages are overwritten.

– Acknowledge mode:

A diagnostic message must first be acknowledged before it can be overwritten with a new diagnostic message.

When the number of unacknowledged diagnostic messages reaches 64, new diagnostic messages will not be

saved and will be lost.

Specifying operating mode for diagnostic message

The operating mode for diagnostic messages can be read and written using diagnostics object 0x10F3

(Subindex 5,�Bit 4).

Operating mode Value of bit 4

Overwrite mode 0

Acknowledge mode 1

Tab. 2.13

Mapping of “New message available” message

For the simplification of the diagnostic evaluation, the module offers the possibility to signal the existence of a new

diagnostic message through the process data. To do this, the object “New message available” can optionally be

mapped to the process data.

Deactivating/activating emergency message

The emergency message (� 2.5.3 Emergency message) can be deactivated and activated by the diagnostic object

0x10F3 (Subindex 5, Bit 0).

Emergency message Value of bit 0

Deactivate 0

Activate 1

Tab. 2.14

2 Function


2.5.3 Emergency message

If there is an error, system CPX-E will transmit an emergency message which consists of the following:

Structure of emergency message

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Error code1) Error register Status bits CPX-E mod

ule number

CPX-E error

number

Reserved Additional error

information2)

Index 1001 Index 1002 (Manufacturer status register)2)

1) In accordance with DS301/DS401

2) Device-typical error messages

Tab. 2.15

Structure of emergency message – Error code (byte 1, byte 0)

Byte 1 Byte 0 Explanation

00 00 No error

10 00 General error

23 20 Short circuit at the outputs

23 30 Load dump (wire break)

31 20 Input voltage too low

33 20 Output voltage too low

50 00 Hardware error (all error, 128)

Tab. 2.16

Structure of emergency message – Error register (byte 2)

Bit Meaning Explanation

0 Generic error Bit is set for each error

1 Current Short circuit/overload in sensor supply (SCS)

Short circuit/overload at outputs (SCO)

2 Voltage Undervoltage of outputs (UOUT)

Load voltage failure at output module or input module

3 – –

4 Communication error Node guard, heart beat, fieldbus-specific only

5 … 6 – –

7 Manufacturer specific Wire break, other error

Tab. 2.17

Structure of emergency message – Status bits (byte 3)


0 Error at valve Module type in which an error has occurred

1 Error at output

2 Error at input

3 Error at analogue or

function module

4 Undervoltage Error type

5 Short circuit/overload

6 Wire break

7 Other error

Tab. 2.18

Structure of emergency message – CPX-E module number (byte 4)


0 … 7 CPX-E module number Number of the module with diagnostic message

Tab. 2.19

2 Function


Structure of emergency message – CPX-E error number (byte 5)


0 … 7 CPX-E error number CPX-E error number1)

1) � Description of the CPX-E system

Tab. 2.20

Structure of emergency message – Additional error information (byte 7)


0 … 7 Additional error

information

For example:

– Node ID with heartbeat error (which participant has caused the timeout?)

– Channel number of the first channel with error

Tab. 2.21

3 Parameterisation


3 Parameterisation

The behaviour of the system CPX-E can be parameterised with the aid of suitable software from Festo or using

a�higher-order controller. Here, a distinction is made between the following variants:

– System parameters

– Module parameters (module and channel-specific)

– Parameterisation of the diagnostic memory

You will find a detailed description of the individual parameters in the “Description of system CPX-E,”

as�well as the descriptions of the corresponding modules � 1.1 Further applicable documents.

The parameters of the individual modules are available as objects

� 3.1 Object directory (Modular Device Profile).

3.1 Object directory (Modular Device Profile)

Object directory (Modular Device Profile)

Index (hex) Subindex Description Data type Values Access1)

0x1000 0 Device Type U32 0x04561389 RO

0x1001 0 Error Register U8 RO

0x1008 0 Device Name String CPX-E-EC RO

0x1009 0 Hardware Version String RO

0x100A 0 Software Version String RO

0x1018 0 Identify U8 4 RO

1 Vendor ID U32 0x0000001D RO

2 Product Code U32 RO

3 Revision U32 RO

4 Serial Number U32 RO

0x10F1 0 Error Settings U8 2 RO

1 Local Error Reaction U32 RO

2 Sync Error Counter Limit U32 RO

0x10F3 0 Diagnostics History U8 RO

1 Maximum Messages U8 64 RO

2 Newest Message U8 RO

3 Newest Acknowledged Message U8 RW

4 New Message Available BOOL RO P

5 Flags U16 0x0000 RW

6 … 26 Subindex 006 … 026 BYTE[23] RO

0x16xx 0 Module xx – RxPDO U8 yy RO

yy Output Mapping yy U32 0x70xx:yy,s RW

0x1Axx 0 Module xx – TxPDO U8 yy RO

yy Input Mapping yy U32 0x60xx:yy,s RW

0x1A40 0 Diag History – TxPDO U8 1 RO

1 Input Mapping 01 U32 0x10F3:00,1 RW

0x20xx 0 Module Parameter – Module xx U8 xy RO

yy Parameter yy ? 2)

0x21xx 0 Fail-Safe Values – Module xx U8 xy RO

yy Channel yy ? RW

1) RO = read only; RO P = read only (PDO mappable); RW = read/write; RW P = read/write (PDO mappable)

2) Depending on parameter

3) Only valid for the IO-Link master module CPX-E-4IOL-…

3 Parameterisation


Object directory (Modular Device Profile)

Index (hex) Access1)ValuesData typeDescriptionSubindex

0x22xx3) 0 ISDU Access – Module xx U8 7 RO

1 Direction (0 = Read; 1 = Write) U8 RW

2 Channel (Start at 0) U8 RW

3 ISDU Index from IO-Link Device U16 RW

4 ISDU Subindex from IO-Link Device U8 RW

5 ISDU Error U16 RW

6 Length of Data U8 RW

7 Data ARRAY OF

BYTE

RW

0x2400 0 Global CPX Settings U8 8 RO

1 Filter Alarm VOUT/VSEN U8 0x00 RW

2 Monitor SCS BOOL TRUE RW

3 Monitor SCO BOOL TRUE RW

4 Monitor VOUT BOOL TRUE RW

5 Monitor VVEN BOOL TRUE RW

6 Monitor SCV BOOL TRUE RW

7 Fail-Safe U8 0x00 RW

8 System Start U8 0x00 RW

0x2401 0 Diagnosis History – Filter No Error U8 RW

0x5000 0 Generic Terminal Information U8 3 RO

1 Modules Count U8 xx RO

2 Input Length U8 xx RO

3 Output Length U8 xx RO

0x5001 0 Build Hash STRING RO

0x5002 0 Unique ID STRING RO

0x60xx 0 Module Inputs U8 xx RO

yy Input yy ? RO P

0x70xx 0 Module Outputs U8 xx RO

yy Output yy ? RW P

0xF000 0 Modular Device Profile U8 2 RO

1 Index Distance U8 1 RO

2 Maximum Number of Modules U16 48 RO

0xF050 0 Detected module list U16 0 … 48 RO

1 Subindex 001 U32 RO

… … U32 RO

48 Subindex 048 U32 RO

1) RO = read only; RO P = read only (PDO mappable); RW = read/write; RW P = read/write (PDO mappable)

2) Depending on parameter

3) Only valid for the IO-Link master module CPX-E-4IOL-…

Tab. 3.1

A Technical Data


A Technical Data

General remarks

Key feature Specification/value

General technical data of CPX-E system Description of CPX-E system

� 1.1 Further applicable documents

Dimensions (Length x Width x Height) [mm] 125.8 x 37.8 x 76.5

Product weight1) [g] 145

Mounting position Vertical/horizontal

Ambient temperature [°C] –5 … +60 (–5 … +50)2)

Storage temperature [°C] –20 … +70

Air humidity (non-condensing) [%] 0 … 95

Assigned address space (inputs/outputs)

Without diagnostics [bit] –/–

With status bits [bit] 163)/–

With I/O diagnostic interface [bit] 16/16

Module code/submodule code (CPX-E-specific) 222/37

Module identification E-EC

Degree of protection in accordance with EN 60529 IP20

Protection against electric shock (protection against

direct and indirect contact to IEC 60204-1)

Through the use of PELV circuits

(Protected extra-low voltage)

Electromagnetic compatibility To EN 61000-6-2/-4 and NE 21

1) Including linking

2) With horizontal mounting position

3) Status bits occupy 2 bytes of the address space even though only 8 bits are in use (8 bits remain unused).

Tab. A.1

Power supply

Key feature Specification/value

Operating voltage supply of electronics/sensors

(UEL/SEN)

[V DC] 24 ± 25 %

Intrinsic current consumption at nominal operating

voltage 24 V from UEL/SEN

[mA] 50

Reverse polarity protection 24 V UEL/SEN against 0 V

UEL/SEN

Yes

Mains buffering time [ms] 20

Tab. A.2

Network-specific

Feature Specification/value

Protocol EtherCAT1)

Specification2) IEC 61158, IEC 61784, IEC 61918, ISO/IEC 8802-3

Transmission rate [Mbps] 100

Crossover detection Auto-MDI/MDI-X

Maximum cable length per segment [m] 100

Cable specification

Cable type Ethernet twisted pair cable, screened

Transmission class Category 5 or higher

Cable diameter [mm] 6 … 8

Wire cross section [mm²] 0.14 … 0.75; 22 AWG3)

1) Based on Ethernet protocol IEEE 802.3, optimised for process data, calibratable

2) Standards with reference to EtherCAT

3) Required for maximum connection length between network participants

Tab. A.3

B Terminology


B Terminology

Term/abbreviation Description

Bus module Connects a system CPX-E to the network; transmits control signals to the

connected modules CPX-E and monitors their functionality.

Device description file Protocol-specific file for configuring the bus module in the control software

for�the higher-order controller. This contains all the information required to

parameterise the system CPX-E via control software.

DIL switch Switches consisting of several switch elements with which settings can be made

(dual in-line).

ESI file Device description file for (EtherCAT slave information)

Ethernet Protocol by means of which the higher-order controller communicates with the

system CPX-E or other devices in the network.

I/O Input and output

I/O diagnostic interface Network-independent diagnostic interface at I/O level, which enables access to

the internal data of the system CPX-E.

In/out (I/O) module Collective term for modules that provide analogue or digital inputs and/or

outputs.

Modules CPX-E Collective term for modules that can be integrated in a CPX-E system.

Status bits Internal status information (common diagnostic messages) of the system CPX-E,

provided as input signals via the network.

System CPX-E Complete system consisting of modules CPX-E.

Tab. B.1

Bus module CPX-E-EC


Index

A

Abbreviations, 22

Address assignment, 10

Addressing, 10

– Basic rules, 10

– Example, 10

C

Connection status, 12

Crossover detection (auto MDI/MDI-X), 6

D

Device description file, 6

Diagnostics history, 15

Diagnostics options, 11

– I/O diagnostics interface, 14

– LED indicators, 12

– Status bits, 14

– Via EtherCAT, 15

Diagnostics via EtherCAT, 15

– Diagnostics history, 15

– Emergency message, 17

– SDO access, 15

Distributed Clocks, 6

E

Emergency message, 17

ESI file, 6

EtherCAT error, 13

EtherCAT operating status, 12

F

Further applicable documents, 4

I

I/O diagnostic interface, 14

L

LED indicators, 12

– Connection status, 12

– EtherCAT error, 13

– EtherCAT operating status, 12

M

Modular Device Profile, 19

O

Object directory, 19

P

Product labelling, 5

Product version, 4

S

SDO access, 15

Status bits, 14

T

Target group, 4

Technical data, 21

Terminology, 22

W

Web servers, 6

Reproduction, distribution or sale of this document or communication ofits contents to others without express authorization is prohibited. Offenders will be liable for damages. All rights reserved in the event that a patent, utility model or design patent is registered.

Copyright:Festo AG & Co. KGRuiter Straße 8273734 EsslingenGermany

Phone:+49 711 347-0

Fax:+49 711 347-2144

e-mail:[email protected]

Internet:www.festo.com

Documents

System CPX-E Bus module CPX-E-EC module CPX-E-EC Festo – CPX-E-EC-EN – 2017-07 – English 3 Table of Contents 1 About this document 4 1.1 Further applicable documents 4 1.2 Target