Festo CPX-E-EP User manual

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
2Festo – 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
4Festo – CPX-E-EP-EN – 2017-07 – English
A Technical Data 47..........................................................................
B Terminology 48............................................................................
Index 49......................................................................................

1 About this document
Festo – CPX-E-EP-EN – 2017-07 – English 5
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 About this document
6Festo – CPX-E-EP-EN – 2017-07 – English
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.
1Designation
2Part number/serial number
3Revision status
4MAC ID
5Data Matrix Code
6Product Key
7Certifications/warning symbols
8Terminal 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
Festo – CPX-E-EP-EN – 2017-07 – English 7
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
8Festo – CPX-E-EP-EN – 2017-07 – English
2.1.5 Product design
1LED indicators
2Rotary and DIL switches
3Power supply terminal block UEL/SEN [XD]
4Terminal block lock
5Network connection [XF2]
6Linking
7Network connection [XF1]
1
2
34
5
6
7
Fig. 2.1
2.1.6 Display components
1Network-specific LED indicators:
– Module status [MS] (green, red, orange)
– Network status [NS] (green, red, orange)
– Connection/data traffic [XF1]/[XF2] (green)
2System-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
Festo – CPX-E-EP-EN – 2017-07 – English 9
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
10 Festo – CPX-E-EP-EN – 2017-07 – English
2.1.8 Connecting components
Port [XF1], [XF2] Signal Designation
1 TD+ Transmitted data +
2 TD– Transmitted data –
3RD+ Received data +
4 n.c. –
5 n.c. –
6RD– 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
20 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
Festo – CPX-E-EP-EN – 2017-07 – English 11
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
1Bus module CPX-E-EP (with status bits)
– Status bits activated
– I/O diagnostic interface deactivated
2Digital input module CPX-E-16DI
3Digital output module CPX-E-8DO
4Digital output module CPX-E-8DO
5Analogue input module CPX-E-4AI-U-I
6Analogue output module CPX-E-4AO-U-I
Module no.: 0 1 2 3 4 5
123456
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
0Bus module CPX-E-EP (with status bits) I0 … I7 –
1Digital input module CPX-E-16DI I72 … I87 –
2Digital output module CPX-E-8DO –O64 … O71
3Digital output module CPX-E-8DO –O72 … O79
4Analogue input module CPX-E-4AI-U-I I8 … I71 –
5Analogue output module CPX-E-4AO-U-I –O0 … O63
Tab. 2.5

2 Function
12 Festo – CPX-E-EP-EN – 2017-07 – English
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
èDescription of system CPX-E
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
èDescription of system CPX-E
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
Festo – CPX-E-EP-EN – 2017-07 – English 13
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
14 Festo – CPX-E-EP-EN – 2017-07 – English
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”
è1.1 Further applicable documents.

2 Function
Festo – CPX-E-EP-EN – 2017-07 – English 15
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
101dGeneric Module Parameter Object – Error number of module
– Faulty channel type
– Number of the faulty channel
133dStatus and Diagnostics Object – Diagnostic status1)
– Number of the module in which an error has occurred
– System error number
134dDiagnostics Trace Object – Long-term memory (maximum of 40 entries)
– Detailed diagnostics + relative time stamp per error event
135dDiagnostics 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
16 Festo – CPX-E-EP-EN – 2017-07 – English
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 –
4100 … 102
110 … 111
Assembly Object èTab. 3.7 …
Tab. 3.11
61 … 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
Festo – CPX-E-EP-EN – 2017-07 – English 17
Object type Detailed
information
NameInstances1) Object
class1)
CPX-E-specific objects
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
CPX-E-specific objects
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
CPX-E-specific objects
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
18 Festo – CPX-E-EP-EN – 2017-07 – English
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
4Set (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
Festo – CPX-E-EP-EN – 2017-07 – English 19
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
Reserved, shall be 0
Supervisor capable
Reserved, shall be 0
Flush_table frame capable
Reserved, shall be 0
1) Bit 0 and bit 1 are mutually exclusive
Tab. 3.3
QoS Object
– Object class: 72d
– 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.
Attribute no. Access Description Type
1Set (NV) 802.1Q Tag enable
0 = Tagged frames disabled (default)
1 = Tagged frames enabled
USINT
2Set (NV) DSCP PTP event (default = 59) USINT
3Set (NV) DSCP PTP general (default = 47) USINT
4Set (NV) DSCP urgent1) (default = 55) USINT
5Set (NV) DSCP scheduled1) (default = 47) USINT
6Set (NV) DSCP high1) (default = 43) USINT
7Set (NV) DSCP low (default =31) USINT
8Set (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
20 Festo – CPX-E-EP-EN – 2017-07 – English
TCP/IP Interface Object
– Object class: 245d
– Instances: 1
Configuration of TCP/IP network interface.
Attribute no. Access Description Type
1 Get Interface status DWORD
2Get (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)
3Set (NV) Configuration control DWORD
4Get (NV) Physical link object
Path size; path
STRUCT of UINT +
Padded EPATH
5Set (NV) Interface configuration:
– IP address
– Netmask
– Gateway address
– Name server
– Name server 2
– Domain name
STRUCT of
– UDINT
– UDINT
– UDINT
– UDINT
– UDINT
– STRING
6Set (NV) HostName (max. 64 chars) STRING
8Set (NV) TTL value – 1 … 255 (default = 1) USINT
9Get (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