System CPX-E Bus module CPX-E-EP - Festo

System CPX-E

Bus module CPX-E-EP

Description

Protocol

EtherNet/IP

Modbus TCP

Industrial Ethernet

2-Port

Function

Parameterisation

8071171

2017-07

[8071173]

Bus module CPX-E-EP

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

Original instructions

CPX-E-EP-EN

EtherNet/IP®, IO-Link®, Modbus® and RSLogix® 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-EP

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

Table of Contents

1 About this document 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Further applicable documents 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Target group 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Product version 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Product labelling 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 Specified standards 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Function 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 General remarks 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.1 Web server 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.2 Device description file 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

2.1.4 QuickConnect 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.5 Product design 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.6 Display components 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.7 Control components 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.8 Connecting components 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

2.3 Addressing 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Basic rules for addressing 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Addressing example 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 Diagnostics options 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.1 LED indicators 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

2.5 Diagnostics via EtherNet/IP 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.1 Overview of diagnostic data with Explicit Messaging 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.2 Diagnostic steps 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6 Diagnostics via Modbus TCP 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Parameterisation 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 EtherNet/IP objects 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.1 Object overview 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.2 Objects for network settings 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.3 Objects for I/O connection 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.4 CPX-E-specific objects for IO-Link 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.5 Objects for system data and diagnostics 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.6 Force Parameter 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.7 Fail safe and Idle parameters 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Modbus TCP objects 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.1 Commands and addresses 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.2 Status information (Group A) 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.3 Process data (Group B and D) 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.4 Diagnostic memory (Groups C and E) 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.5 Modbus TCP Objects (Group F) 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bus module CPX-E-EP

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

A Technical Data 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B Terminology 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 About this document



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 Content

Description of system CPX-E (CPX-E-SYS) Detailed description of the 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

a�system CPX-E

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

usage of the product

Documentation for the components in a 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 of an EtherNet/IP or Modbus TCP network

is required in order to understand this documentation.

1.3 Product version

This document refers to the following product versions:

Product Version

CPX-E-EP Bus module CPX-E-EP, 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 labelling

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

appropriate device opens the Festo Support Portal with the relevant documents for the product. Alternatively, the

Product Key (11-character alphanumeric code on the product label) can be entered in the Support Portal search box.

1 Designation2 Part number/serial number3 Revision status4 MAC ID5 Data Matrix Code6 Product Key7 Certifications/warning symbols8 Terminal allocation

1

2

3

4

5

7

6

8

Fig. 1.1

1.5 Specified standards

Version

EN 60529:2013-10 IEC 60204-1:2014-10

EN 61000-6-2:2009-04 IEEE 802.3:2014-00

EN 61000-6-4:2011-09 NE 21:2012-05

Tab. 1.3

2 Function


2 Function

2.1 General remarks

The product is intended for the operation of a system CPX-E in an Ethernet network using either the EtherNet/IP or

the Modbus TCP protocol. Data is transmitted on the basis of Industrial Ethernet following the IEEE 802.3 protocol.

The product has two equivalent Ethernet interfaces (RJ45) with integrated switch, and therefore supports both star

and line topology. The integrated switch enables the division of the network into different segments. With the use of

additional switches and routers, the network can be divided into additional segments. This makes it possible to

structure the network and achieve networks of greater extent.

2.1.1 Web server

The integrated web server provides read access to the key parameters and diagnostic functions of the

system�CPX-E.

The web server can be accessed by entering the IP address in the address bar of a web browser.

Factory settings of the bus module:

IP address: 192.168.1.1, subnet mask: 255.255.255.0 (DHCP = active)

2.1.2 Device description file

The bus module is configured in the control software for the higher-order controller using a device description file

(EDS file). This contains all the information required to parameterise the system CPX-E via control software

(e.g.�RSLogix 5000).

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.

When using the “Priority start-up” function (QuickConnect), crossover detection (auto MDI/MDI-X)

must�be deactivated.

2.1.4 QuickConnect

The “QuickConnect” function ensures rapid start-up of the system CPX-E.

When using the “QuickConnect” function, crossover detection (auto MDI/MDI-X) must be deactivated,

and the transmission rate and duplex mode of the network connections to the bus module and to the

higher-order controller must be set to be identical.

The IO-Link master module CPX-E-4IOL-... does not support the “QuickConnect” function.

2 Function


2.1.5 Product design

1 LED indicators2 Rotary and DIL switches3 Power supply terminal block UEL/SEN [XD]4 Terminal block lock5 Network connection [XF2]6 Linking7 Network connection [XF1]

1

2

34

5

6

7

Fig. 2.1

2.1.6 Display components

1 Network-specific LED indicators:– Module status [MS] (green, red, orange)

– Network status [NS] (green, red, orange)

– Connection/data traffic [XF1]/[XF2] (green)

2 System-specific LED indicators:– Power supply UEL/SEN [PS] (green)

– Load power 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

The 3 rotary switches are used to set the 4th octet of the IP address (192.168.1.XXX).

Possible settings:

0 = Dynamic addressing via DHCP/BOOTP

1 … 255 = Permissible address range

Valid values:

EtherNet/IP: 300 … 555 (IP address = value – 300)

Modbus TCP: 600 … 855 (IP address = value – 600)

Factory setting: 900

The diagnostic mode is set using the DIL switches � Tab. 2.2.

Tab. 2.1

In the case of invalid values, the IP parameters are reset to dynamic addressing (DHCP).

For switch settings 0 ... 255, the EtherNet/IP and Modbus TCP protocols can be used in parallel.

The�rights to control the outputs are assigned to the protocol that sends outputs first.

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

Reserved

1) Factory setting

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 [XF1], [XF2] 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

Port [XD]1) Signal

0 +24 V DC power supply UEL/SEN

1

2 0 V DC power supply UEL/SEN

3

1) Ports XD.0 and XD.1 and ports XD.2 and XD.3, respectively, are connected to each other in the terminal block.

Tab. 2.4

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 Function


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 8 inputs.

– 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 following sequence applies:

1. Bus module with status bits or I/O diagnostic interface (if activated via DIL switch)

2. Analogue modules

3. Technology modules

4. Digital modules

2.3.2 Addressing example

1 Bus module CPX-E-EP (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-EP (with status bits) I0 … I7 –

1 Digital input module CPX-E-16DI I72 … I87 –

2 Digital output module CPX-E-8DO – O64 … O71

3 Digital output module CPX-E-8DO – O72 … O79

4 Analogue input module CPX-E-4AI-U-I I8 … I71 –

5 Analogue output module CPX-E-4AO-U-I – O0 … O63

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-EP

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

EtherNet/IP Diagnostics as part of the EtherNet/IP

function via the network.

Detailed module- and channel-related

error detection by means of control

software.

� 2.5

Modbus TCP Diagnostics as part of the Modbus TCP

function via the network.

Detailed module- and channel-related

error detection by means of control

software.

� 2.6

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.

Data traffic [XF1], [XF2]

LED (green) Meaning Remedy

lights up

Network connection OK –

flashes1)

Data traffic ongoing –

off

No network connection � Check network connection.

1) Flashing frequency is dependent on the traffic.

Tab. 2.7

Module status [MS]

LED

(green, red,

orange)

Meaning Remedy

lights up

green

Normal operating status –

flashes

green

Configuration of system CPX-E not complete or

not correct.

� Complete or correct configuration of the

system CPX-E.

lights up

red

Error cannot be rectified � Contact Festo service

� www.festo.com.

flashes red

Error can be rectified � Check configuration of system CPX-E.

flashes

alternately

red/green

The system CPX-E is in self-test mode. –

lights up

orange

Bootloader –

off

No logic supply to the network interface. � Check logic supply.

Tab. 2.8

2 Function


Network status [NS]1)

LED

(green, red,

orange)

Meaning Remedy

lights up

green

Normal operating status.

The system CPX-E is online and has a network

connection.

–

flashes

green

The system CPX-E is online and has received

an�IP address but does not have a configured

network connection.

� Check configuration of the system CPX-E;

it�is possible that the system CPX-E is not

assigned to a master/scanner.

lights up

red

Communication has failed.

Non-permitted IP address set that is already

used in the network.

� Correct IP address.

flashes red

One or more “I/O connections” are in the

“time-out status”.

� Check the physical connection to the

master/scanner.

flashes

alternately

red/green

The system CPX-E is in self-test mode. –

lights up

orange

Modbus TCP has control over the output data.

Bootloader if the LED [MS] is also lit up orange

� Tab. 2.8.

–

off

The system CPX-E is offline.

No IP address assigned or no IP address received

from DHCP server.

� Check network connection.

� Check IP addressing settings.

1) The behaviour of the LED indicator is dependent on the network protocol used.

Tab. 2.9

2.4.2 Status bits

The 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”


2 Function


2.5 Diagnostics via EtherNet/IP

The system CPX-E supports the following diagnostic options via the EtherNet/IP protocol.

The following diagnostics options are supported here:

– Explicit-Messaging via EtherNet/IP master

– Diagnostics via PLC user program. The I/O diagnostic interface can also be read out here.

2.5.1 Overview of diagnostic data with Explicit Messaging

Object

class

Name Diagnostic data

101d Generic Module Parameter Object – Error number of module

– Faulty channel type

– Number of the faulty channel

133d Status and Diagnostics Object – Diagnostic status1)

– Number of the module in which an error has occurred

– System error number

134d Diagnostics Trace Object – Long-term memory (maximum of 40 entries)

– Detailed diagnostics + relative time stamp per error event

135d Diagnostics Trace Status Object – Number of entries in the diagnostic memory

– Trace status

1) Indicates whether diagnostic data are present

Tab. 2.10

2.5.2 Diagnostic steps

The necessary steps for performing diagnostics on the system CPX-E are explained below.

1. Check whether diagnostic data are present � Status and Diagnostics Object 133d.

2. Determine the number of the module in which an error has occurred � Status and Diagnostics Object 133d.

3. Determine associated diagnostic data for the module � Generic Module Parameter Object 101d.

2.6 Diagnostics via Modbus TCP

The system CPX-E enables diagnostics via the Modbus TCP protocol:

– Status register � 3.2.2 Status information (Group A)

– I/O diagnostic interface � 3.2.3 Process data (Group B and D)

– Diagnostic memory � 3.2.4 Diagnostic memory (Groups C and E)

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 can find a detailed description of the individual parameters in the “Description of system CPX-E” and

in the descriptions of the corresponding modules � 1.1 Further applicable documents.

The parameters of the individual modules are available as objects.

3.1 EtherNet/IP objects

The following sections describe the representation of the system CPX-E within the EtherNet/IP object

model. Many of the terms shown are the original English terms of the protocol specification, and are used

for clarity in any language.

3.1.1 Object overview

EtherNet/IP class services

The system CPX-E supports various services, depending on the object:

Service code Service name

05 (05h) Reset

01 (01h) Get Attribute All

14 (0Eh) Get Attribute Single

16 (10h) Set Attribute Single

Tab. 3.1

EtherNet/IP object classes

The following objects are supported:

Object type Object

class1)

Instances1) Name Detailed

information

General CIP objects 1 1 Identity Object � Tab. 3.16

2 1 Message Router Object –

4 100 … 102

110 … 111

Assembly Object � Tab. 3.7 …

Tab. 3.11

6 1 … 10 Connection Manager Object –

244 1 Port Object –

EtherNet/IP-specific

objects

245 1 TCP/IP Interface Object � Tab. 3.5

246 3 Ethernet Link Object � Tab. 3.6

71 1 Device Level Ring Object � Tab. 3.3

72 1 QoS Object � Tab. 3.4

CPX-E-specific objects

for�IO-Link

140 1 … 48 IO-Link Port Configuration Object � Tab. 3.12

300 ISDU Access Object � Tab. 3.13

1) Decimal

3 Parameterisation


Object type Detailed

information

NameInstances1)Object

class1)


for�parameterisation and

diagnostics

132 1 Global System Object � Tab. 3.17

133 Status and Diagnosis Object � Tab. 3.18

134 1 … 40 Diagnosis Trace Object � Tab. 3.19

135 1 Diagnosis Trace Status Object � Tab. 3.20

199 Configuration Array Object � Tab. 3.33

108 … 111

116 … 119

124 … 127

1 … 48 Force Parameter � 3.1.6

112 … 113

120 … 121

128 … 129

1 … 48 Fail safe Parameter � 3.1.7

114 … 115

122 … 123

130 … 131

1 … 48 Idle Parameter

101 1 … 48 Generic Module Parameter Object � Tab. 3.21,

Tab. 3.22


for�parameterisation of

inputs and outputs

102 1 … 48 Discrete Input Object –

103 Discrete Output Object

104 Analog Input Object

105 Analog Output Object

106 Function Input Object

107 Function Output Object


for�parameterisation of

Force, Fail� safe and Idle

mode

108 1 … 48 Discrete Input Force State Object � 3.1.6

109 Discrete Input Force Mode Object

110 Discrete Output Force State Object

111 Discrete Output Force Mode Object

112 Discrete Output Fail safe State Object � 3.1.7

113 Discrete Output Fail safe Mode Object

114 Discrete Output Idle State Object

115 Discrete Output Idle Mode Object

116 Analog Input Force State Object � 3.1.6

117 Analog Input Force Mode Object

118 Analog Output Force State Object

119 Analog Output Force Mode Object

120 Analog Output Fail safe State Object � 3.1.7

121 Analog Output Fail safe Mode Object

122 Analog Output Idle State Object

123 Analog Output Idle Mode Object

124 Function Input Force State Object � 3.1.6

125 Function Input Force Mode Object

126 Function Output Force State Object

127 Function Output Force Mode Object

128 Function Output Fail safe State Object � 3.1.7

129 Function Output Fail safe Mode Object

130 Function Output Idle State Object

131 Function Output Idle Mode Object

1) Decimal

Tab. 3.2

3 Parameterisation


Counting mode

For the module-orientated objects, the following applies: Instance number = Module number + 1

– The modules are counted starting at 0 for the bus module

– The instances are counted starting at 1 for the bus module.

An overview of the available data and parameters, their function numbers as well as their assignment

to�the objects can be found in the following sections.

You can find a description and the functions of the individual parameters and data as well as fundament

als on parameterisation in the “Description of system CPX-E” � 1.1 Further applicable documents.

3.1.2 Objects for network settings

Device Level Ring Object

– Object class: 71d

– Instances: 1

Status information for the Device Level Ring protocol (DLR protocol).

Attribute no. Access Description Type

1 Get Network topology

0 = Linear

1 = Ring

USINT

2 Get Network status

0 = Normal

1 = Ring fault

2 = Unexpected loop detected

3 = Partial network fault

4 = Rapid fault/restore cycle

USINT

3 Get Ring supervisor active status flag

0 = Backup supervisor

1 = Active ring supervisor

2 = Normal ring node

3 = Non DLR topo

4 = Cannot support current ring parameters

(beacon interval/timeout)

USINT

4 Set (NV) Ring supervisor config

– Ring supervisor enable

– Ring supervisor precedence

– Beacon interval

– Beacon timeout

– DLR VLAN ID

STRUCT of

– BOOL

– USINT

– UDINT

– UDINT

– UINT

5 Set Ring faults count (reset by writing 0) UINT

6 Get Last active node on port 1

Last active node at the end of chain through port 1 of active

ring supervisor during ring fault

STRUCT of

UDINT (IP)

USINT [6] (MAC)

7 Get Last active node on port 2

Last active node at the end of chain through port 2 of active

ring supervisor during ring fault

STRUCT of

UDINT (IP)

USINT [6] (MAC)

8 Get Ring protocol participants count

Number of devices in ring protocol participants list

UINT

9 Get Ring protocol participants list

List of devices participating in ring protocol

ARRAY of:

STRUCT of

UDINT (IP)

USINT [6] (MAC)

1) Bit 0 and bit 1 are mutually exclusive

3 Parameterisation


Attribute no. TypeDescriptionAccess

10 Get Active supervisor address:

– Supervisor IP address

– Supervisor MAC address

STRUCT of

– UDINT (IP)

– USINT [6]

(MAC)

11 Get Active supervisor precedence:

Precedence value of active ring supervisor

USINT

12 Get Capability flags DWORD

Bit 0

Bit 1

Bit 2 … 4

Bit 5

Bit 6

Bit 7

Bit 8 … 31

Reserved, shall be 0

Beacon-based ring node


Supervisor capable


Flush_table frame capable


1) Bit 0 and bit 1 are mutually exclusive

Tab. 3.3

QoS Object


– Instances: 1

Classification and prioritisation of data packets for EtherNet/IP communication.

IEEE 802.1D/Q describes Ethernet frames that contain an additional 32-bit header. This header contains, among

other things, a VLAN ID and a prioritisation field.


1 Set (NV) 802.1Q Tag enable

0 = Tagged frames disabled (default)

1 = Tagged frames enabled

USINT

2 Set (NV) DSCP PTP event (default = 59) USINT

3 Set (NV) DSCP PTP general (default = 47) USINT

4 Set (NV) DSCP urgent1) (default = 55) USINT

5 Set (NV) DSCP scheduled1) (default = 47) USINT

6 Set (NV) DSCP high1) (default = 43) USINT

7 Set (NV) DSCP low (default =31) USINT

8 Set (NV) DSCP explicit (default = 27) USINT

1) This attribute describes the IP header priority of various EtherNet/IP frames:

urgent = CIP motion

scheduled = CIP safety

high = I/O

Tab. 3.4

3 Parameterisation


TCP/IP Interface Object


– Instances: 1

Configuration of TCP/IP network interface.


1 Get Interface status DWORD

2 Get (NV) Configuration capability DWORD

Bit 0

Bit 1

Bit 2

Bit 3

Bit 4

Bit 5

Bit 6

Bit 7

BOOTP client (false)

DNS client (true)

DHCP client (true)

DHCP-DNS update (false)

Configuration settable (true)

Hardware configurable (true)

Interface configuration – change requires reset

(false)

AcdCapable (true)

3 Set (NV) Configuration control DWORD

4 Get (NV) Physical link object

Path size; path

STRUCT of UINT +

Padded EPATH

5 Set (NV) Interface configuration:

– IP address

– Netmask

– Gateway address

– Name server

– Name server 2

– Domain name

STRUCT of

– UDINT

– UDINT

– UDINT

– UDINT

– UDINT

– STRING

6 Set (NV) HostName (max. 64 chars) STRING

8 Set (NV) TTL value – 1 … 255 (default = 1) USINT

9 Get (NV) Mcast config (IP multicast address configuration):

– Alloc control

– Reserved

– Num Mcast

– Mcast start addr

STRUCT of

– USINT

– USINT

– UINT

– UDINT

10 Set (NV) SelectAcd

0 = Enable ACD

1 = Disable ACD

BOOL

11 Set (NV) LastConflictDetected:

– ACDactivity

– RemoteMAC

– ArpPDU

STRUCT of

– USINT

– ARRAY of

USINT [6]

– ARRAY of

USINT [28]

12 Set (NV) QuickConnect

0 = Disable

1 = Enable

BOOL

13 Set (NV) Encapsulation inactivity timeout

0 = Disable

1 … 3600 = Timeout in seconds (default = 120)

UINT

Tab. 3.5

3 Parameterisation


Ethernet Link Object


– Instances: 3

General information and status information as well as advanced settings for the Ethernet interfaces.

Instance 1 corresponds to Ethernet port X1 and instance 2 corresponds to Ethernet port X2.


1 Get Interface speed (in Mbps) UDINT

2 Get Interface flags DWORD

Bit 0

Bit 1

Bit 2 … 4

Bit 5

Bit 6

Link status

0 = Inactive link

1 = Active link

Half duplex/Full duplex

0 = Half duplex

1 = Full duplex

Negotiation status:

0 = Autonegotiation in progress

1 = Autonegotiation and speed detection failed

2 = Autonegotiation failed but detected speed

3 = Successfully negotiated speed and duplex

4 = Autonegotiation not attempted

Manual setting requires reset

Local hardware fault

0 = No local hardware fault

1 = Local hardware fault detected

3 Get Physical address (MAC layer address) ARRAY of UINT [6]

4 Get Interface counters

– In octets

– In Ucast packets

– In NUcast packets

– In discards

– In errors

– In unknown protos

– Out octets

– Out Ucast packets

– Out NUcast packets

– Out discards

– Out errors

STRUCT of UDINT

5 Get Media counters

– Alignment errors

– FCS errors

– Single collisions

– Multiple collisions

– SQE test errors

– Deferred transmissions

– Late collisions

– Excessive collisions

– MAC transmit errors

– Carrier sense errors

– Frame too long

– MAC receive errors

STRUCT of UDINT

3 Parameterisation



6 Set (NV) Interface control

Control bits STRUCT of WORD

Bit 0

Bit 1

Bit 2 … 15

Autonegotiate

0 = Autonegotiation disabled

1 = Autonegotiation enabled

Forced duplex mode

0 = The interface duplex should be half duplex

1 = The interface duplex should be full duplex


Forced interface speed (in Mbps) STRUCT of UINT

7 Get Interface type

0 = Unknown interface type

1 = The interface is internal to the device

2 = Twisted-pair

3 = Optical fiber

USINT

8 Get Interface state

0 = Unknown interface state

1 = The interface is enabled and ready to send/receive data

2 = The interface is disabled

3 = The interface is testing

USINT

9 Set (NV) Admin state

1 = Enable

2 = Disable

USINT

10 Get Interface label SHORT_STRING

11 Get Interface capability

Capability bits STRUCT of DWORD

Bit 0

Bit 1

Bit 2

Bit 3

Bit 4 … 31

Manual setting requires reset

Autonegotiate

Auto MDIX

Manual speed/duplex


Speed/duplex options

– Speed/duplex array count STRUCT of USINT

– Speed/duplex array

– Interface speed (in Mbps)

– Interface duplex mode

� (0 = half duplex, 1 = full duplex)

ARRAY of

STRUCT of

– UINT

– USINT

12 Get HC interface counters (high capacity interface counters)

– HCInOctets

– HCInUcastPkts

– HCInMulticastPkts

– HCInBroadcastPkts

– HCOutOctets

– HCOutUcastPkts

– HCOutMulticastPkts

– HCOutBroadcastPkts

STRUCT of ULINT

3 Parameterisation



13 Get HC media counters (high capacity media counters)

– HCStatsAlignment

– HCStatsFCSErrors

– HCStatsInternalMacTransmitErrors

– HCStatsFrameTooLongs

– HCStatsInternalMacReceiveErrors

– HCStatsSymbolErrors

STRUCT of ULINT

Tab. 3.6

Examples:

– To set port X1 to 100 Mbps (full duplex) and deactivated auto-negotiation, the values [0002h] [0064h] must be

written in attribute 6, instance 1.

– To activate auto-negotiation, the values [0001h] [0000h] must be written in attribute 6, instance 1.

3.1.3 Objects for I/O connection

Assembly Object


– Instances: 5

Bundling of attributes of different objects for data exchange of the objects over one connection.

Each data range begins on the LSB (least significant bit; low-order bit) of a word.

The following object instances are saved in the Assembly Object:

Instance Description

100 Output data (in format SINT)

101 Input data (in format SINT)

102 Configuration data

110 Output data with padding (in format INT)

111 Input data with padding (in format INT)

Tab. 3.7

Instance 101: (Input data)

Within instance 101, all inputs of the system CPX-E are transmitted cyclically over the network.

The following sequence applies during transmission:

1. I/O diagnostic interface, if activated (16-bit oriented)

2. Object instances of the analogue channels (16-bit oriented)

3. Instances of the technology modules (16- or 8-bit oriented)

4. Object instances of the digital inputs (8-bit oriented)

Instance 101 (input) has the following member list:

Object Instances1) Attributes (channel) Entry in member list Type

102 1 … 48 1 … 64 Digital data BOOL

104 1 … 32 Analogue channel data WORD

106 1 … 64/65 … 96 Technology module BYTE/WORD

133 1 0/1 I/O diagnostic interface data, if activated WORD

1) Instances = Module number + 1

Tab. 3.8

3 Parameterisation


Instance 100 (Output data)

Within instance 100, all outputs of the system CPX-E are transmitted cyclically over the network.

The following sequence applies during transmission:

1. I/O diagnostic interface or status bits, if activated (16-bit oriented)

2. Object instances of the analogue channels (16-bit oriented)

3. Instances of the technology modules (16- or 8-bit oriented)

4. Object instances of the digital outputs (8-bit oriented)

Instance 100 (output) has the following member list:

Object Instances1) Attributes (channel) Entry in member list Type

103 1 … 48 1 … 64 Digital data BOOL

105 1 … 32 Analogue channel data WORD

107 1 … 64/65 … 96 Technology module BYTE/WORD

133 1 0/1 I/O diagnostic interface data, if activated WORD

1) Instances = Module number + 1

Tab. 3.9

Instance 102 (Configuration data)

Instance 102 has the following member list:

Object Quantity Entry in member list Type

199 1 Configuration array data ARRAY

Tab. 3.10

The I/O objects 102 ... 107 also have the following attributes:

Attribute Entries Type

100 Number of data of the module in BYTE or WORD BYTE

101 Data type:

– D1h: BYTE

– D2h: WORD

BYTE

102 All data values ARRAY

Tab. 3.11

3 Parameterisation


3.1.4 CPX-E-specific objects for IO-Link

IO-Link Port Configuration Object


– Instances: 1 ... 48


1 Get/Set Port 1 configuration STRUCT of

Master Cycle Time in 100 μs (Default 0) UINT

Inspection Level (Default 0)

0 = No Check

1 = Type compatible (Check Vendor and Device ID)

2 = Identical (Check Serial, Vendor and Device ID)

USINT

Expected Vendor ID (Default 0) UINT

Expected Device ID (Default 0) UDINT

Expected Serial STRING

… … … …

4 Get/Set Port 4 configuration STRUCT of

Master Cycle Time in 100 μs (Default 0) UINT

Inspection Level (Default 0)

0 = No Check

1 = Type compatible (Check Vendor and Device ID)

2 = Identical (Check Serial, Vendor and Device ID)

USINT

Expected Vendor ID (Default 0) UINT

Expected Device ID (Default 0) UDINT

Expected Serial STRING

Tab. 3.12

ISDU Access Object

Request Service code Instance Attribute Data [0 … 1] Data [2] Data [3 … n]

Read 0x32 Channel1) Module Index Subindex –

Write 0x33 Channel1) Module Index Sunindex Data To Write

1) Values: 1 = Port 1; 2 = Port 2; etc.

Tab. 3.13

Read response data Write response data

Data [0] Data [1 … n] Data [0]

Response status

� Tab. 3.15

Data from ISDU Response status � Tab. 3.15

Tab. 3.14

Response

status

Description Response

status

Description

0

0x00 Success 0xE6 Read Answer Too Long

0xE1 Write Data Length Too Long 0xE7 State Unknown

0xE2 Port Unknown 0xE8 Port On Master Not Support

0xE3 Device Busy 0xE9 Port In Invalid State

0xE4 Write Failed 0xFF Timeout

0xE5 Read Failed

Tab. 3.15

3 Parameterisation


3.1.5 Objects for system data and diagnostics

Identity Object


– Instances: 1

Identification and general information on the bus module CPX-E-EP.

Service Code 5d: Reset

– Parameter 0 emulates a power cycle

– Parameter 1 resets the device to the factory settings and then emulates a power cycle


1 Get VendorID: 1Ah UINT

2 Get Device type: 0Ch UINT

3 Get Product code: 36D8h UINT

4 Get Revision (major/minor) STRUCT

5 Get Status WORD

Bit 0

Bit 1

Bit 2

Bit 3

Bit 4 … 7

Bit 8

Bit 9

Bit 10

Bit 11

Bit 12 … 15

Owned


Configured


Extended device status

Minor recoverable fault

Minor unrecoverable fault

Major recoverable fault

Major unrecoverable fault


6 Get Serial number UDINT

7 Get Product name (CPX-E-EP Remote I/O) SHORT_STRING

8 Get State

0 = Nonexistent

1 = Device self testing

2 = Standby

3 = Operational

4 = Major recoverable fault

5 = Major unrecoverable fault

255 = Default value

USINT

14 Get/Set Semaphore STRUCT

15 Get/Set

(NV)

User assigned name STRING

16 Get/Set

(NV)

User assigned description STRING

17 Get/Set

(NV)

User assigned location STRING

100 Get Operating mode BOOL

101 Get External module identifiers ARRAY

Tab. 3.16

3 Parameterisation


Global System Object


– Instances: 1

Attribute no. Access Description Type Function number

1 Get Operating mode (bit 0, 1) USINT 0 (bit 0, 1)

0 = Without control

1 = With control

CPX-E expansion1) (bit 4) 0 (bit 4)

0 = Uniform expansion

1 = Nonuniform expansion

Force mode (bit 6) 0 (bit 6)

0 = Force blocked

1 = Force enabled

2 Get Fail safe mode (bit 0, 1) USINT 1 (bit 0, 1)

0 = Fail safe mode inactive

1 = Fail safe mode active

System Idle mode (bit 2, 3) 1 (bit 2, 3)

0 = Idle mode inactive

1 = Idle mode active

3 Get Monitoring of system CPX-E USINT 2 (bit 0 … 7)

Bit 0 0 = SCS2) monitoring inactive

1 = SCS2) monitoring active

Bit 1 0 = SCO3) monitoring inactive

1 = SCO3) monitoring active

Bit 2 0 = UOUT monitoring inactive

1 = UOUT monitoring active

Bit 3 0 = UVAL monitoring inactive

1 = UVAL monitoring active

Bit 4 0 = SCV4) monitoring inactive

1 = SCV4) monitoring active

Bit 5 … 7 Reserved

4 Get Number of input bytes (Rx size) UINT –

5 Get Number of output bytes (Tx size) USINT –

9 Get/Set Monitoring (presetting: active) USINT 4401 (bit 0 … 7)

Bit 0 0 = SCS2) monitoring inactive

1 = SCS2) monitoring active

Bit 1 0 = SCO3) monitoring inactive

1 = SCO3) monitoring active

Bit 2 0 = UOUT monitoring inactive

1 = UOUT monitoring active

Bit 3 0 = UVAL monitoring inactive

1 = UVAL monitoring active

Bit 4 0 = SCV4) monitoring inactive

1 = SCV4) monitoring active

Bit 5 … 7 Reserved

1) Indicates whether the current expansion of the system CPX-E corresponds to the saved expansion.

2) SCS = Short circuit/overload in sensor supply

3) SCO = Short circuit/overload at the outputs

4) SCV = Short circuit at valves

5) Presetting

3 Parameterisation


Attribute no. Function numberTypeDescriptionAccess

10 Get/Set Fail safe mode (bit 0, 1) USINT 4402 (bit 0, 1)

0 = Reset all outputs5)

1 = Retain signal status

2 = Assume Fail safe mode

11 Get/Set Force mode (bit 2, 3) USINT 4402 (bit 2, 3)

0 = Force mode blocked

1 = Force mode enabled

12 Get/Set System Idle mode (bit 4, 5) USINT 4402 (bit 4, 5)

0 = Reset all outputs5)

1 = Retain signal status

2 = Assume Idle mode

13 Get/Set System start (bit 6) USINT 4402 (bit 6)

0 = System start with standard parameters

(factory setting) and current expansion; external

parameterisation possible (presetting)

1 = System start with saved parameters and

saved expansion; parameters and expansion are

saved to retentive memory; external

parameterisation is blocked; the “M” LED on the

bus module is lit up

1) Indicates whether the current expansion of the system CPX-E corresponds to the saved expansion.

2) SCS = Short circuit/overload in sensor supply

3) SCO = Short circuit/overload at the outputs

4) SCV = Short circuit at valves

5) Presetting

Tab. 3.17

Status and Diagnostics Object


– Instances: 1

Mapping of status bits and of I/O diagnostic interface.


1 Get Status bits1) USINT 1936

Bit 0

Bit 1

Bit 2

Bit 3

Valve

Outlet

Input

Analogue/technology module

Bit 4

Bit 5

Bit 6

Bit 7

Undervoltage

Short circuit/overload

Wire break

Other error

2 Get Number of the first module in which an error has

occurred

USINT 1937

3 Get Diagnostic status USINT

4 Get Error number UINT 1938

5 Get/Set Address of I/O diagnostic interface

16 output bits (order data)

WORD –

6 Get Data for I/O diagnostic interface

16 input bits (reply data)

WORD –

1) Source of error = Bit 0 ... 3; type of error = Bit 4 ... 7

Tab. 3.18

3 Parameterisation


Diagnostics Trace Object



An instance is created for each entry of a diagnostic message.


3488 + n1)

1 Get Marking the first entry after Power On2) BYTE n = 10 * d + 4 (bit 7)

2 Get Number of days3) BYTE n = 10 * d + 0

3 Get Number of hours3) BYTE n = 10 * d + 1

4 Get Number of minutes3) BYTE n = 10 * d + 2

5 Get Number of seconds3) BYTE n = 10 * d + 3

6 Get Number of 10 milliseconds3) BYTE n = 10 * d + 4

(bit 0 … 6)

7 Get Module code of the module which registered

the�error

BYTE n = 10 * d + 5

8 Get Module number of the module which registered

the error (63 = error not module-related)

BYTE n = 10 * d + 6

(bit 6 … 7)

9 Get Channel number of the first faulty channel4) BYTE n = 10 * d + 7

(bit 0 … 5)

10 Get Error number BYTE n = 10 * d + 8

11 Get Number of subsequent channels with the

same�error4)

BYTE n = 10 * d + 9

1) d = Diagnostic event (0 … 39); 0 = Current diagnostic event

2) Supplies a 1 signal if it is the first entry after Power On.

3) Measured from the moment the power supply is switched on.

4) If the error number = 0, the content also = 0. If the error number lies between 128 ... 199 (error class 3), the content is not relevant

(servicing�required).

Tab. 3.19

3 Parameterisation


Diagnostics Trace Status Object


– Instances: 1


1 Get Number of trace entries in the diagnostic

memory

BYTE 3482 (bit 0 … 7)

2 Get Status of diagnostic memory (bit 0, 1) BYTE 3483 (bit 0, 1)0 = Registering active

1 = Registering inactive

3 Get/Set Clear_trace1, access via EDS BYTE –4 Get/Set Clear_trace2, access via Explicit Messaging;

Confirms activity carried out by resetting (0)

the�attribute value

BYTE –

5 Get/Set Entries saved retentively with Power On (bit 0) BYTE 3480 (bit 0)0 = Active (presetting)

1 = Inactive

6 Get/Set Run/stop filter 1 (bit 1) BYTE 3480 (bit 1)0 = Save the first 40 entries, stop after 40 entries

1 = Save the last 40 entries, overwrite existing

entries (presetting)

7 Get/Set Run/stop filter 2 (bit 0 ... 2) BYTE 3484 (bit 0 … 2)0 = Run/stop filter 2 inactive (presetting)

1 = Record up to the defined error number (FN)

2 = Record up to the defined FN + module

number (MN)

3 = Record up to the defined FN + MN + channel

number (KN)

4 = Record from the defined FN

5 = Record from the defined FN + MN

6 = Record from the defined FN + MN + KN

7 = Reserved

8 Get/Set Error end filter (bit 3) BYTE 3484 (bit 3)0 =Filter inactive, record running errors

(end�of�error) (presetting)

1 = Filter active, do not record running errors

(end of error)

9 Get/Set Error number filter (bit 4, 5) BYTE 3484 (bit 4, 5)0 = Filter inactive (presetting)

1 = Record only defined error numbers

2 = Do not record defined error numbers

3 = Reserved

10 Get/Set Module/channel filter (bit 6, 7)

With this diagnostic memory filter, the recording

of errors of other modules or channels can be

suppressed so that errors in a particular module

or channel can be analysed.

BYTE 3484 (bit 6, 7)

0 = Filter inactive (presetting)

1 = Record only the error numbers of a module

2 = Record only the error numbers of a channel

3 = Reserved

11 Get/Set Module number for the diagnostic memory filter BYTE 3485 (bit 0 … 7)12 Get/Set Channel number for the diagnostic memory filter BYTE 3486 (bit 0 … 7)13 Get/Set Error number for the diagnostic memory filter BYTE 3487 (bit 0 … 7)

Tab. 3.20

3 Parameterisation


Generic Module Parameter Object



This object enables general access to the module parameters of all modules.

For this object, the following applies: Instance number = Module number + 1

The module parameters are accessed in 3 different ways:

– Byte parameters via the attributes 1 ... 64 � Tab. 3.21, Tab. 3.22

– Word parameters via the attributes 65 ... 127 � Tab. 3.21

– Double-word parameters via the attributes 129 ... 189 � Tab. 3.22

Assignment of the attributes for word parameters to the function numbers

Attribute no. Parameter Function number

Byte Word Word

1 65 – � Description of the respective module 4827 + m * 64 + 0

2 66 4827 + m * 64 + 1

3 67 4827 + m * 64 + 2

4 68 4827 + m * 64 + 3

5 69 4827 + m * 64 + 4

6 70 4827 + m * 64 + 5

… … 4827 + m * 64 + …

… … 4827 + m * 64 + …

… … 4827 + m * 64 + …

… 124 4827 + m * 64 + 59

61 125 4827 + m * 64 + 60

62 126 4827 + m * 64 + 61

63 127 4827 + m * 64 + 62

64 – 4827 + m * 64 + 63

Tab. 3.21

Assignment of the attributes for double-word parameters to the function numbers

Attribute no. Parameter Function number

Byte DWord DWord DWord DWord

1 129 – – – � Description of the respective module 4828 + m * 64 + 0

2 130 4828 + m * 64 + 1

3 131 4828 + m * 64 + 2

4 132 4828 + m * 64 + 3

5 133 4828 + m * 64 + 4

6 134 4828 + m * 64 + 5

7 135 4828 + m * 64 + 6

8 136 4828 + m * 64 + 7

9 … 4828 + m * 64 + 8

10 … 4828 + m * 64 + 9

11 … 4828 + m * 64 + 10

12 … 4828 + m * 64 + 11

… 185 4828 + m * 64 + …

… 186 4828 + m * 64 + …

… 187 4828 + m * 64 + …

… 188 4828 + m * 64 + 59

61 189 4828 + m * 64 + 60

62 – 4828 + m * 64 + 61

63 – 4828 + m * 64 + 62

64 – 4828 + m * 64 + 63

Tab. 3.22

3 Parameterisation


3.1.6 Force Parameter

Assigning the instance numbers for the relevant object:

– The first word receives the lowest instance number

– The second word receives the second lowest instance number

– …

Overview

Object Description Module type

108 Force state digital inputs Digital I/O modules

109 Force mode digital inputs

110 Force state digital outputs

111 Force mode digital outputs

116 Force state analogue inputs Analogue I/O modules

117 Force mode analogue inputs

118 Force state analogue outputs

119 Force mode analogue outputs

124 Force state inputs, technology modules Technology modules

125 Force mode inputs, technology modules

126 Force state outputs, technology modules

127 Force mode outputs, technology modules

Tab. 3.23

Force mode objects

– Object classes: 109d, 111d, 117d, 119d, 125d, 127d



1 Get/Set Duct 0

0 = Force blocked

1 = Force enabled

BOOL

2 Get/Set Channel 1

0 = Force blocked

1 = Force enabled

BOOL

… … … …

64 Get/Set Duct 63

0 = Force blocked

1 = Force enabled

BOOL

100 Get Number of channels BYTE

101 Get All channels: values for Force mode ARRAY

Tab. 3.24

3 Parameterisation


Force state objects for digital I/O modules

– Object classes: 108d, 110d



1 Get/Set Duct 0

0 = Reset signal

1 = Set signal

BOOL

2 Get/Set Channel 1

0 = Reset signal

1 = Set signal

BOOL

… … … …

64 Get/Set Duct 63

0 = Reset signal

1 = Set signal

BOOL


101 Get All channels: values for Force state ARRAY

Tab. 3.25

Force state objects for analogue I/O modules




1 Get/Set Duct 0

Value for Force

WORD

2 Get/Set Channel 1

Value for Force

WORD

… … … …

32 Get/Set Duct 31

Value for Force

WORD

Tab. 3.26

Force state objects for technology modules




1 Get/Set Duct 0

Value for Force

BYTE

2 Get/Set Channel 1

Value for Force

BYTE

… … … …

64 Get/Set Duct 63

Value for Force

BYTE

65 Get/Set Duct 0

Value for Force

WORD

… … … …

96 Get/Set Duct 31

Value for Force

WORD


101 Get Data type: D1h = BYTE; D2h = WORD BYTE

102 Get/Set All channels: values for Force state ARRAYh

Tab. 3.27

3 Parameterisation


3.1.7 Fail safe and Idle parameters

Assigning the instance numbers for the relevant object:

– The first word receives the lowest instance number

– The second word receives the second lowest instance number

– …

Overview

Module type Object Description

Digital output modules 112 Fail safe state digital outputs

113 Fail safe mode digital outputs

114 Idle state digital outputs

115 Idle mode digital outputs

Analogue output modules 120 Fail safe state analogue outputs

121 Fail safe mode analogue outputs

122 Idle state analogue outputs

123 Idle mode analogue outputs

Technology modules 128 Fail safe state inputs, technology modules

129 Fail safe mode inputs, technology modules

130 Idle state outputs, technology modules

131 Idle mode outputs, technology modules

Tab. 3.28

Fail safe mode and Idle mode objects

– Object classes:

– Fail safe mode: 113d, 121d, 129d

– Idle mode: 115d, 123d, 131d



1 Get/Set Duct 0

0 = Hold last state

1 = Fail safe/Idle state

BOOL

2 Get/Set Channel 1

0 = Hold last state


BOOL

… … … …

64 Get/Set Duct 63

0 = Hold last state


BOOL


101 Get All channels: values for Fail safe mode and Idle mode ARRAY

Tab. 3.29

3 Parameterisation


Fail safe state and Idle state objects for digital output modules

– Object classes:

– Fail safe state: 112d

– Idle state: 114d



1 Get/Set Duct 0

0 = Hold last state


BOOL

2 Get/Set Channel 1

0 = Hold last state


BOOL

… … … …

64 Get/Set Duct 63

0 = Hold last state


BOOL


101 Get All channels: values for Fail safe state and Idle state ARRAY

Tab. 3.30

Fail safe state and Idle state objects for analogue output modules






1 Get/Set Duct 0

Value for Fail safe state/Idle state

WORD

2 Get/Set Channel 1


WORD

… … … …

32 Get/Set Duct 31


WORD

Tab. 3.31

3 Parameterisation


Fail safe state and Idle state objects of technology modules






1 Get/Set Duct 0


BYTE

2 Get/Set Channel 1


BYTE

… … … …

64 Get/Set Duct 63


BYTE

65 Get/Set Duct 0


WORD

… … … …

96 Get/Set Duct 31


WORD


101 Get Data type: D1h = BYTE; D2h = WORD BYTE

102 Get/Set All channels: values for Fail safe state and Idle state ARRAY

Tab. 3.32

Configuration Array Object


– Instances: 1


1 Get/Set Data field with all system and module parameters ARRAY

Tab. 3.33

3 Parameterisation


3.2 Modbus TCP objects

The following sections describe the representation of the system CPX-E within the Modbus TCP object

model. Many of the terms shown are the original English terms of the protocol specification, and are used

for clarity in any language.

3.2.1 Commands and addresses

The table below shows the connection between the Modbus address and data/parameters of the system CPX-E.

The�data are assigned to various groups.

Command Function code Modbus address Significance Access Group

read

4 x registers

3 45357 … 45391

45392 … 45647

45648 … 45655

45656 … 46055

Status information

Process data inputs

Diagnostic memory parameters

Diagnostic memory data

read A

B

C

C

write

4 x registers

6, 16 40001 … 40256

40257 … 40264

Process data outputs


write D

E

read/write

4 x registers

23 45357 … 45391

45392 … 45647

45648 … 45655

45656 … 46055

Status information

Process data inputs


Diagnostic memory data

read A

B

C

C

40001 … 40256

40257 … 40264

Process data outputs


write D

E

read device

identification

43 Objects Objects IDO 1, 2, 3, 4, 5 read F

Tab. 3.34

3 Parameterisation


3.2.2 Status information (Group A)

The status information provides information on the configuration and the error status of the system CPX-E.

Configuration of the system CPX-E

Modbus

address

Process data inputs Bit1)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

45367 Module 0 … 15 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

45368 Module 16 … 31 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

45369 Module 32 … 47 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

1) 0 = Module not present; 1 = Module present

Tab. 3.35

Error detection

Modbus

address

Process data inputs Bit1)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

45383 Module 0 … 15 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

45384 Module 16 … 31 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

45385 Module 32 … 47 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

1) 0 = No error; 1 = error in module n

Tab. 3.36

Status register

Modbus

address

Process data inputs Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

45391 Status register entry1)2) 01

01

1) Bit 11: 0 = Parameter not write-protected; 1 = Parameter write-protected

2) Bit 15: 0 = Force inactive; 1 = Force active

Tab. 3.37

3 Parameterisation


3.2.3 Process data (Group B and D)

The process image of the input data (Group B) and of the output data (Group D) is composed without gaps from the

data of the modules as mounted from left to right in the system CPX-E.

The Modbus addresses also depend accordingly on the arrangement of the modules of the system CPX-E. The

Modbus addresses are arranged in ascending order without gaps i.e. n, n +1, n +2..., where n corresponds to the first

Modbus address of the module.

Bus module CPX-E-EP

Inputs

Modbus

address1)

Process data inputs (Group B) Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Result of access to the I/O

diagnostic interface

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 Data from the system table

(read�access)

Waiting 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Request successful (8000h) 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Error (, 8000h)

Write protection (8001h) 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1

Writing not permitted,

reserved range (8002h)

1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0

Internal error (8003h) 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1

n + 2 Module diagnostics data

Error number (0 … 255) 01

01

01

01

01

01

01

01

Channel number (0 … 63) 01

01

01

01

01

01

Number of first faulty output

channel

0 0

Number of first faulty input

channel

1 0

There is a module error 0 1

Reserved 1 1

1) n = First Modbus address of the module

Tab. 3.38

Outputs

Modbus

address1)

Process data outputs (Group D) Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Access to the I/O diagnostic

interface

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 Data for the system table

(write�access)

Function number 01

01

01

01

01

01

01

01

01

01

01

01

01

Read request 0

Write request 1

Byte value 0

Word value 1

Control bit: Write access to the

I/O diagnostic interface2)

01


2) Write access occurs with a rising edge (from 0 to 1).

Tab. 3.39

3 Parameterisation


Digital input modules CPX-E-16DI-...

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Inputs 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 Module diagnostics data 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.40

Digital output modules CPX-E-8DO-...

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Echo outputs 01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.41

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Outputs 01

01

01

01

01

01

01

01


Tab. 3.42

Analogue input modules CPX-E-4AI-U-I

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Analogue inputs, channel 0 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 Analogue inputs, channel 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.43

Analogue output modules CPX-E-4AO-U-I

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Echo analogue outputs, channel 0 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 Echo analogue outputs, channel 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.44

3 Parameterisation


Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Analogue outputs, channel 0 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 Analogue outputs, channel 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.45

IO-Link master module CPX-E-4IOL-...

The process image for the input and output data on the IO-Link master module CPX-E-4IOL-... is

dependent on the available address space set on the module.

E-1IOL

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Inputs 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 15 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 16 Echo outputs 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 31 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.46

E-1IOL

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Outputs 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 15 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.47

3 Parameterisation


E-2IOL

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Inputs, channel 0 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 7 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 8 Inputs, channel 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 15 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 16 Echo outputs, channel 0 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 23 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 31 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.48

E-2IOL

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Outputs, channel 0 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 7 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 8 Outputs, channel 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 15 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.49

E-4IOL (8 bytes)

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.50

3 Parameterisation


E-4IOL (8 bytes)

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.51

E-4IOL (16 bytes)

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 3 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 5 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 7 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 9 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 11 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 13 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 15 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.52

E-4IOL (16 bytes)

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 3 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 5 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 7 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.53

3 Parameterisation


E-4IOL (32 bytes)

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 3 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 7 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 11 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 15 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 19 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 23 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 27 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 31 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.54

E-4IOL (32 bytes)

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 3 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 7 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 11 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 15 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.55

3 Parameterisation


Counter module CPX-E-1CI

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Inputs 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 1 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… …

n + 4 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

n + 5 Reserved

n + 6 Echo outputs 01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Tab. 3.56

Modbus

address1)


15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

n Outputs 01

01

01

01

01

01

01

01


Tab. 3.57

3 Parameterisation


3.2.4 Diagnostic memory (Groups C and E)

Diagnostic memory – Parameters and data (read access)

Modbus

address

Input data Function

number

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

45648 Run/stop filter 1 3480 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

Error end filter 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

Error numbers filter 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

Module/channel filter 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

45653 Module number 3485 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

45654 Channel number 3486 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

45655 Error number 3487 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

45650 Diagnostic memory

Number of entries

3482 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


Overflow

3483 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

Diagnostic memory

Status

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


data

3488 + n1) 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

… … … 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

1) You can find detailed information in the “Description of system CPX-E” � 1.1 Further applicable documents.

Tab. 3.58

Diagnostic memory – Parameters and data (write access)

Modbus

address

Output data Function

number

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01


01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

Error end filter 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

Error numbers filter 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

Module/channel filter 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

40262 Module number 3485 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

40263 Channel number 3486 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

40264 Error number 3487 01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

01

Tab. 3.59

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


3.2.5 Modbus TCP Objects (Group F)

Object ID Object name Contents

0 Manufacturer name Festo AG & Co. KG

1 Product code CPX-E-EP

2 MajorMinorRevision x.y1)

3 VendorURL http://www.festo.com

4 Product name Modbus TCP

5 Model name System CPX-E

1) x: Version Modbus driver, y: Revision code system CPX-E

Tab. 3.60

A Technical Data


A Technical Data

General

Feature Specification/value

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

� 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] 8/–

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

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

Module identification E-EP

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

Tab. A.1

Power supply


Power supply for electronics/sensors (UEL/SEN) [V DC] 24 ± 25 %

Intrinsic current consumption at nominal operating

voltage 24 V from UEL/SEN

[mA] 70

Reverse polarity protection 24 V UEL/SEN against 0 V

UEL/SEN

Yes

Mains buffering time [ms] 20

Tab. A.2

Network-specific


Protocol EtherNet/IP and Modbus TCP1)

Specification EtherNet/IP

Transmission rate [Mbps] 10/100 (full duplex/half duplex)

Crossover detection Auto-MDI/MDI-X

Maximum cable length per segment [m] 1002)

Cable specification

Cable type Ethernet twisted pair cable, screened

Transmission class Category Cat 5/Cat 5e (link class)

Cable diameter [mm] 6 … 8

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

1) Based on the Ethernet protocol IEEE 802.3

2) At a transmission rate of 100 Mbps

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).

EDS file Device description file for EtherNet/IP (electronic data sheet)

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.

I/O module Collective term for the modules that provide analogue or digital inputs/outputs.

Modules CPX-E Collective term for the various modules which can be incorporated in a system

CPX-E.

PLC Programmable logic controller

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-EP


Index

A

Abbreviations, 48

Address assignment, 10

Addressing, 11

– Basic rules, 11

– Example, 11

Assembly Object, 23

– Instance 100 (Output data), 24

– Instance 101 (Input data), 23

– Instance 102 (Configuration data), 24

C

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

D

Data traffic, 13

Device description file , 7

Device Level Ring Object, 18

Diagnostic memory, 46

Diagnostics options, 12

– I/O diagnostic interface, 14

– LED indicators, 13

– Status bits, 14

– via EtherNet/IP, 15

– via Modbus TCP, 15

Diagnostics Trace Object, 29

Diagnostics Trace Status Object, 30

Diagnostics via EtherNet/IP, 15

– Diagnostic steps, 15

– Fail safe parameters, 34

Fail safe mode objects, 34

Fail safe state objects, 35

– Force parameters, 32

Force mode objects, 32

Force state objects, 33

– Idle parameters, 34

Idle mode objects, 34

Idle state objects, 35

– Object overview, 16

– Objects for I/O connection, 23

Assembly Object, 23

– Objects for network settings, 18

Device Level Ring Object, 18

Ethernet Link Object, 21

QoS Object, 19

TCP/IP Interface Object, 20

– Objects for system data and diagnostics, 26

Diagnostics Trace Object, 29

Diagnostics Trace Status Object, 30

Generic Module Parameter Object, 31

Global System Object, 27

Identity Object, 26

Status and Diagnostics Object, 28

Diagnostics via Modbus TCP, 15

– Commands and addresses, 37

– Diagnostic memory, 46

– Modbus TCP objects, 46

– Process Data, 39

– Status information, 38

E

EDS file, 7

Ethernet Link Object, 21

F

Fail safe mode objects, 34

Fail safe state objects, 35

Force mode objects, 32

Force state objects, 33

Further applicable documents, 5

G

Generic Module Parameter Object, 31

Global System Object, 27

I

I/O diagnostic interface, 14

Identity Object, 26

Idle mode objects, 34

Idle state objects, 35

IO-Link Port Configuration Object, 25

ISDU Access Object, 25

L

LED indicators, 13

– Data traffic, 13

– Module status, 13

– Network status, 14

M

Modbus TCP objects, 46

Module status, 13

Bus module CPX-E-EP


N

Network status, 14

P

Process Data, 39

Product labelling, 6

Product version, 5

Q

QoS Object, 19

QuickConnect, 7

S

Status and Diagnostics Object, 28

Status bits, 14

Status information, 38

T

Target group, 5

TCP/IP Interface Object, 20

Technical data, 47

Terminology, 48

W

Web servers, 7

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 SE & Co. KGRuiter Straße 8273734 EsslingenGermany

Phone:+49 711 347-0

Fax:+49 711 347-2144

e-mail:[email protected]

Internet:www.festo.com

System CPX-E Bus module CPX-E-EP - Festo

Documents

Transcript of System CPX-E Bus module CPX-E-EP - Festo