FESTO CPX-FB36 - EthernetIP-ModbusTCPIP

CPX-FB36
Bus node
Description | Commis-
sioning
8024075
8024075
2019-07b
[8090481]
Translation of the original instructions
ALLEN-BRADLEY®, CODESYS®, EtherNet/IP®, HART®, MODBUS®, ODVA CONFORMANT®, ODVA®,

ROCKWELL AUTOMATION®, SPEEDCON®, STUDIO 5000® are registered trademarks of the respective
trademark owners in certain countries.
2 Festo — CPX-FB36 — 2019-07b

Table of contents
1 Safety........................................................................................................................... 7
1.1 Intended Use................................................................................................................ 7
1.2 Safety Instructions....................................................................................................... 7
1.3 Qualifications of specialised personnel (target group).................................................. 8
1.4 Service...........................................................................................................................8
1.5 Information regarding this description......................................................................... 8
1.6 Terms and abbreviations.............................................................................................. 8
1.7 Data types.................................................................................................................... 11
2 Installation.................................................................................................................. 12
2.1 General information about installation......................................................................... 12
2.1.1 Connection and display components...................................................................... 12
2.1.2 Dismantling and mounting......................................................................................13
2.2 Settings of the DIL switches.......................................................................................... 13
2.2.1 Removing and attaching cover................................................................................14
2.2.2 Arrangement of the DIL switches............................................................................ 14
2.2.3 Setting DIL switches................................................................................................14
2.2.4 Setting operating mode and network protocol........................................................15
2.2.5 Setting diagnostic mode or data field size.............................................................. 15
2.2.6 Setting IP addressing.............................................................................................. 16
2.3 Connecting to the network............................................................................................ 17
2.3.1 General information................................................................................................ 17
2.3.2 Overview of connection technology and network plug connectors..........................18
2.3.3 Cable specification..................................................................................................18
2.3.4 Network connections.............................................................................................. 19
2.3.5 Setting IP addressing.............................................................................................. 20
2.3.6 Extended network settings..................................................................................... 22
2.4 Ensuring the degree of protection................................................................................ 22
2.5 Power supply of the CPX terminal................................................................................. 22
3 Preparing for commissioning...................................................................................... 23
3.1 EtherNet/IP protocol.................................................................................................... 23
3.1.1 IP-Multicast telegram..............................................................................................23
3.1.2 "QuickConnect"......................................................................................................24
3.1.3 Device-Level-Ring protocol (DLR)............................................................................26
3.2 Modbus TCP protocol................................................................................................... 26
3.3 Notes on commissioning the CPX-FB36........................................................................ 27
3.3.1 Requirements for commissioning............................................................................27
3.3.2 Switching on the power supply............................................................................... 28
3.3.3 Normal operating status......................................................................................... 28
3.4 Stations in the network................................................................................................ 30
3.4.1 Station properties (Electronic Data Sheet, EDS file)................................................30
Festo — CPX-FB36 — 2019-07b 3

4 Commissioning.............................................................................................................31
4.1 Configuration.................................................................................................................31
4.1.1 Configuration with EDS file.................................................................................... 31
4.1.2 Configuration with "Generic Ethernet Module"..................................................... 37
4.1.3 Configuration with CPX-FMT................................................................................... 42
4.1.4 Configuration in Remote Controller operating mode.............................................. 45
4.1.5 "Listen-only" Set up connection............................................................................ 46
4.2 Parameterisation........................................................................................................... 46
4.2.1 Parameterisation during switch-on [system start].................................................. 47
4.2.2 Methods of parameterisation................................................................................. 48
4.2.3 Parameterisation via configuration data................................................................ 49
4.2.4 Parameterisation with the CPX-MMI operator unit................................................. 50
4.2.5 Parameterisation in the PLC user program............................................................. 50
4.2.6 Parameterisation using CPX-FMT and system start with saved parameters............ 50
4.3 Behaviour of the outputs in the "Fail safe mode" or " "Idle mode" mode.................... 50
4.4 Web server.................................................................................................................... 50
4.5 Check list for commissioning a CPX terminal................................................................. 51
4.6 Replacing bus node....................................................................................................... 51
5 Diagnostics...................................................................................................................52
5.1 Diagnostics options.......................................................................................................52
5.2 Diagnostics via LED displays......................................................................................... 53
5.2.1 CPX-specific LED displays...................................................................................... 54
5.2.2 Network-specific LED displays............................................................................... 56
5.3 Diagnostics via status bits.............................................................................................58
5.4 Diagnostics via the I/O diagnostics interface.................................................................59
5.5 Diagnostics via EtherNet/IP...........................................................................................60
5.6 Diagnostics via Modbus TCP......................................................................................... 61
5.7 Error handling ("Fail safe")............................................................................................61
6 Technical appendix...................................................................................................... 62
6.1 Technical Data............................................................................................................... 62
6.2 Address assignment of the CPX terminal....................................................................... 63
6.2.1 Address assignment.............................................................................................. 63
6.2.1.1 Bus node................................................................................................................ 64
6.2.1.2 Digital modules...................................................................................................... 64
6.2.1.3 Analogue modules................................................................................................. 66
6.2.1.4 Technology modules.............................................................................................. 68
6.2.2 Addressing............................................................................................................. 69
6.2.2.1 Basic rules for addressing...................................................................................... 69
6.2.2.2 Data formats.......................................................................................................... 70
6.2.2.3 Examples of addressing......................................................................................... 71
4 Festo — CPX-FB36 — 2019-07b

6.2.3 Address assignment after extension/conversion.................................................... 74
6.3 EtherNet/IP-Objects of the CPX-FB36........................................................................... 76
6.3.1 Overview of EtherNet/IP objects............................................................................. 76
6.3.2 Objects for network settings................................................................................... 79
6.3.2.1 "Device Level Ring Object"..................................................................................... 79
6.3.2.2 "QoS Object"..........................................................................................................80
6.3.2.3 "TCP/IP Interface Object"...................................................................................... 80
6.3.2.4 "Ethernet Link Object"............................................................................................82
6.3.3 Objects for the I/O connection................................................................................ 82
6.3.3.1 "Assembly Object"................................................................................................. 82
6.3.4 Objects for system data and diagnostics................................................................ 85
6.3.4.1 "Identity Object".................................................................................................... 85
6.3.4.2 "Global System Object" for operating mode Remote I/O........................................86
6.3.4.3 "Status and Diagnosis Object"............................................................................... 89
6.3.4.4 "Diagnosis Trace Object"....................................................................................... 89
6.3.4.5 "Diagnosis Trace Status Object"............................................................................ 90
6.3.4.6 "Generic Parameter Object"................................................................................... 92
6.3.4.7 "Force Parameter"..................................................................................................94
6.3.4.8 Fail safe and Idle parameters.................................................................................. 97
6.3.4.9 "Configuration Array Object"..................................................................................100
6.3.4.10 “Slave Size Object” for “Remote Controller” operating mode.................................101
6.3.4.11 "Condition Counter Object"....................................................................................101
6.3.4.12 "HART Access Object"............................................................................................ 102
6.3.4.13 "ISDU Access Object"............................................................................................. 108
6.3.5 Examples................................................................................................................ 109
6.3.5.1 Forcing inputs......................................................................................................... 109
6.3.5.2 Parameterisation with “Generic Parameter Object”................................................ 111
6.4 Modbus TCP-Objects of the CPX-FB36.......................................................................... 112
6.4.1 Overview of Modbus TCP objects........................................................................... 112
6.4.2 Commands and addresses...................................................................................... 112
6.4.3 CPX status information (Group A)........................................................................... 113
6.4.4 Process data (Group B and D)................................................................................. 114
6.4.4.1 Bus node CPX-M-FB36............................................................................................ 115
6.4.4.2 Electric modules..................................................................................................... 115
6.4.4.3 Pneumatic modules................................................................................................ 117
6.4.4.4 Electrical interface (CP interface) CPX-CP-4-FB........................................................119
6.4.4.5 Structure of diagnostic data (diagnostic word)....................................................... 122
6.4.4.6 Structure of the data of the I/O diagnostics interface............................................. 122
6.4.5 Diagnostic memory (Groups C and E)......................................................................123
6.4.6 Modbus TCP-Objects (Group F)...............................................................................124
Festo — CPX-FB36 — 2019-07b 5

6.4.6.1 Examples of addressing for Modbus TCP............................................................... 125
6 Festo — CPX-FB36 — 2019-07b

Safety
1 Safety
1.1 Intended Use
The bus node described in this description is intended exclusively for use in Festo CPX terminals for
installation in a machine or automation system.
In conjunction with a CPX terminal, the bus node is used for communication as a station in networks
with the EtherNet/IP or Modbus TCP protocols.
The CPX terminal may only be used as follows:
– as intended in industrial environments; outside industrial environments, e.g. in commercial and
mixed-residential areas, actions to suppress interference may be required
– in its original state without unauthorised modifications; only the conversions or modifications
described in the documentation supplied with the product are permitted.
– In perfect technical condition
– Only in combination with approved components
– Observe the specified limit values.
– Take into consideration the applicable regulations for the intended destination as well as instruc-
tions and standards, regulations of the inspection organisations, insurance companies and
national regulations.
1.2 Safety Instructions

– Before assembly or installation work, switch off the power supply, switch off the compressed air
supply, exhaust any pneumatic components.
– Use exclusively PELV circuits in accordance with IEC 60204-1/EN 60204-1 for the electrical power
supply.
– Observe the notes on installation and power supply as well as on equipotential bonding (earthing
measures) in the CPX system description (CPX-SYS).
– Observe the handling specifications for electrostatically sensitive devices.
– Seal unused connections with cover caps to achieve the required degree of protection.
– Use connection hardware with the required degree of protection.
– Observe the specifications in the CPX system description, in the descriptions of the valve terminal
used as well as in the assembly instructions for the individual components.
– Observe the instructions for correctly mounting the CPX terminal.
– Place only a completely mounted and wired CPX terminal into operation.
– Only switch on the compressed air and load voltage if the system has been professionally
installed, configured and parameterised.
– Make sure that nobody enters the positioning range of the actuators.
Switching off the compressed air or load voltage is not a suitable interlocking mechanism. Uninten-
tional movement of actuators may occur in the event of a malfunction.
Festo — CPX-FB36 — 2019-07b 7

Safety
1.3 Qualifications of specialised personnel (target group)

The product may only be commissioned by trained, qualified control and automation technology tech-
nicians who are familiar with:
– mounting, installation, operation and diagnostics of control systems, networks and fieldbus sys-
tems
– the applicable regulations for accident prevention and occupational safety
– the documentation for the product
1.4 Service
If you have technical problems contact your local Festo service è www.festo.com.
1.5 Information regarding this description

This description contains specific information about installation, configuration, parameterisation,
commissioning, programming and diagnostics with the bus node CPX-FB36 for EtherNet/IP and Mod-
bus TCP.
An overview of the user documentation structure for the CPX terminal can be found in the CPX system
description (CPX-SYS).
Further information on EtherNet/IP can be found here:

è www.odva.org
Further information on Modbus TCP can be found here:
è www.modbus.org
The bus node was certified by Open Device Vendor Association(ODVA):
ODVA CONFORMANT
EtherNet/IP
Modbus TCP
Tab. 1 ODVA certifications

General basic information about mode of operation, assembling, installing and commissioning CPX
terminals can be found in the CPX system description (CPX-SYS).
Information about additional CPX modules can be found in the description for the specific module.
All available documents for the product è www.festo.com/pk.
1.6 Terms and abbreviations

The following product-specific terms and abbreviations are used in this description:
Term/abbreviation Meaning
160d Decimal numbers are marked in part by a subscript "d".
8 Festo — CPX-FB36 — 2019-07b

Safety
A0h Hexadecimal numbers are marked by a subscript "h".

O digital output
AO analogue output
AI analogue input
BOOTP Dynamic protocol for the automatic allocation of IP addresses (Bootstrap
Protocol, predecessor of DHCP).
Bus node Establishes the connection to specific fieldbuses. It transmits control sig-
nals to the connected modules and monitors their ability to function.
CEC CODESYS Embedded Controller, e.g. CPX-CEC, can be used for control, con-
figuration and commissioning of CPX terminals.
CODESYS Controller Development System
CP Compact Performance
CP module Collective term for the various modules that can be integrated into the CP
system (decentralised installation system).
CPX-CP interface Interface for connecting decentrally arranged CP modules to a CPX termin-
al.
CPX-FMT Festo Maintenance Tool for configuration and parameterisation of CPX ter-
minals.
CPX modules Collective term for electric modules that can be incorporated into a CPX ter-
minal: bus nodes, I/O modules and function modules (technology mod-
ules).
CPX modules provide, among other things, electrical inputs and outputs for
connecting sensors and actuators.
CPX modules form the electrical side of the CPX terminal.
CPX terminal Complete system consisting of various CPX modules with or without pneu-
matics modules.
DO digital output
DI digital input
DHCP Dynamic protocol for automatic allocation of IP addresses (Dynamic Host
Configuration Protocol).
DIL switch Dual-In-Line switch with several switch elements with which settings can
be made.
I digital input
I/O diagnostics inter- Network-independent diagnostic interface at I/O level that enables access
face to internal data of the CPX terminal.
Festo — CPX-FB36 — 2019-07b 9

Safety
I/O modules Collective term for the CPX modules that provide digital or analogue inputs
and outputs.
I/O signal Input/output signal of an I/O module; also referred to as a process signal.
I/Os Analogue or digital inputs and outputs.
EtherNet/IP Communication protocol for connecting various devices in a network.
FEC Control block, e.g. CPX-FEC, can be used as:
– stand-alone system controller (SPS, Stand Alone operating mode)
– system controller (SPS, Remote Controller operating mode)
– fieldbus Slave (Remote I/O operating mode)
Function module Collective term for modules with additional functions, e.g. CPX-CP inter-
face, control block CPX-CEC or CPX-FEC. Function modules are also referred
to as technology modules.
CPX-MMI Operator unit for commissioning and service purposes.
Modbus TCP Communication protocol via TCP/IP in automation technology.
Pneumatic interface Interface between CPX modules and pneumatic modules within a CPX ter-
minal.
The pneumatic interface is functionally on the electrical side of the CPX ter-
minal.
Pneumatic modules Collective term for the pneumatics modules that can be integrated into a
CPX terminal.
They provide outputs (working ports) for connecting actuators, e.g. cylin-
ders. They form the pneumatic side of the CPX terminal.
Status bits Internal inputs that supply coded common diagnostic messages.
Technology module è Function module
Tab. 2 Terms and abbreviations
10 Festo — CPX-FB36 — 2019-07b

Safety
1.7 Data types

Data type Size Value range Description
ARRAY –1) – Structure with identical

data types
BOOL 1 bit 0 “false” and 1 “true” Logical data type
BYTE 8 bit 00h … FFh Bit field
DWORD 32 bit 00000000h … FFFFFFFFh Bit field
DINT 32 bit –2147483648 … Signed Double Integer
2147483647
INT 16 bit –32,768 … 32,767 Signed Integer
Padded EPATH max. 12 bytes Logical segments of a
path specification
SINT 8 bit –128 … 127 Signed Short Integer
STRING 8 bit/character – String
SHORT_STRING 8 bit/character + – String with
8 bit length spe- max. 255 characters
cification
STRUCT – Structure of any data
–1)
types
UDINT 32 bit 0 … 4294967296 Unsigned Double Integer
UINT 16 bit 0 … 65,536 Unsigned Integer
USINT 8 bit 0 … 256 Unsigned Short Integer
WORD 16 bit 0000h … FFFFh Bit field
1) depends on the data types in use
Tab. 3 Data types
Festo — CPX-FB36 — 2019-07b 11

Installation
2 Installation
2.1 General information about installation
WARNING!
Uncontrolled movements of the actuators and loose tubing lines, undefined switching states of the
electronics
Injury caused by moving parts, damage to machine and to system
Before mounting and installation work:
• Switch off the power supply
• Switch off the compressed air supply
• Exhaust pneumatics.
NOTICE!
Electrostatically sensitive devices
• Do not touch any components.
• Observe the handling specifications for electrostatically sensitive devices.
NOTICE!
Ensuring the required degree of protection
• Use cover caps to seal unused connections è 2.4 Ensuring the degree of protection.
Information about mounting of the CPX terminal can be found in the CPX system description (CPX-
SYS).
2.1.1 Connection and display components
1 Network-specific and CPX-specific LED displays

2 Network connections [X1], [X2]
(2 x socket, M12, D-coded, 4-pin)
3 DIL switch
4 Service interface for operator unit CPX-MMI or Festo
Maintenance Tool CPX-FMT
(socket, M12, A-coded, 5-pin)
Fig. 1 Connection and display components
12 Festo — CPX-FB36 — 2019-07b

Installation
2.1.2 Dismantling and mounting

The bus node is installed in an interlinking block of the CPX terminal è Fig.2.
1 Screws
2 Interlinking block
3 Bus node CPX-M-FB36
Fig. 2 Dismantling/mounting
Dismantling bus node

1. Unscrew screws.
2. Pull the bus node out of the interlinking block without tilting it.
Mounting bus node
NOTICE!
Material damage due to incorrect mounting
• Select screws that are suitable for the material of the interlinking block:
– Polymer: thread-grooving screws
– Metal: screws with metric thread.
1. Check seal and sealing surface. Replace damaged parts.

2. Push the bus node carefully and without tilting into the interlinking block up to the stop.
3. Screw the screws into the existing thread.
4. Tighten the screws in diagonally opposite sequence.
Tightening torque: 1 Nm ± 10%.
2.2 Settings of the DIL switches

The following settings can be made with the DIL switches:
– Operating mode and network protocol
– Diagnostic mode or data field size
– IP addressing
The settings of the DIL switches become effective only after the power supply is switched on.
Festo — CPX-FB36 — 2019-07b 13

Installation
2.2.1 Removing and attaching cover

The cover must be removed to set the DIL switches at the bus node.
Removing the DIL switch cover
1. Switch off power supply.
2. Unscrew screws.
3. Remove the DIL switch cover.
Attaching the DIL switch cover
1. Attach the DIL switch cover. Make sure that the seal is seated correctly.
2. Tighten screws. Tightening torque: max. 0.4 Nm.
2.2.2 Arrangement of the DIL switches
1 DIL switch 1:
Operating mode and network protocol
2 DIL switch 2:
Diagnostic mode or data field size
(depending on the set operating mode)
3 DIL switch 3:
IP addressing
Fig. 3 DIL switch
2.2.3 Setting DIL switches

Procedure
1. Switch off power supply.
2. Remove the DIL switch cover è 2.2.1 Removing and attaching cover.
3. Make the settings for the DIL switches è 2.2.4 Setting operating mode and network protocol …
è 2.2.6 Setting IP addressing.
4. Replace the cover of the DIL switches è 2.2.1 Removing and attaching cover.
14 Festo — CPX-FB36 — 2019-07b

Installation
2.2.4 Setting operating mode and network protocol
DIL switch 1.1 Mode of operation
DIL 1.1: OFF Remote I/O

(factory setting) All functions of the CPX terminal are controlled directly by
the higher-order controller (SPS). A control block integrated
into the CPX terminal (e.g. CPX-CEC or CPX-FEC) works as a
passive function module without controller.
DIL 1.1: ON Remote Controller
A control block integrated into the CPX terminal (e.g. CPX-
CEC or CPX-FEC) controls the I/O controller. This operating
mode is only useful if a control block is integrated into the
CPX terminal.
Tab. 4 Setting operating mode
DIL switch 1.2 Network protocol
DIL 1.2: OFF EtherNet/IP

(factory setting) The CPX terminal uses the EtherNet/IP network protocol.
DIL 1.2: ON Modbus TCP

The CPX terminal uses the EtherNet/IP network protocol.
Tab. 5 Setting network protocol
2.2.5 Setting diagnostic mode or data field size
The function of DIL switch 2 is dependent on the set operating mode of the CPX terminal
è Tab. 4 Setting operating mode.
DIL switch 2 Diagnostics mode Data field size

(Remote I/O)1) (Remote Controller)2)
2.1: OFF I/O diagnostics interface and 8 byte I/8 byte O for communic-
2.2: OFF status bits switched off ation of the bus node with a
(factory setting) control block (e.g. CPX-CEC)
2.1: ON I/O diagnostics interface is 32 Byte I/32 Byte O for commu-
2.2: OFF switched on nication of the bus node with a
control block (e.g. CPX-CEC)3)
2.1: OFF Status bits switched on 16 byte I/16 byte O for commu-
2.2: ON nication of the bus node with a
control block (e.g. CPX-CEC)
Festo — CPX-FB36 — 2019-07b 15

Installation
DIL switch 2 Diagnostics mode Data field size

(Remote I/O)1) (Remote Controller)2)
2.1: ON reserved 64 byte I/64 byte O for commu-

2.2: ON nication of the bus node with a
control block (e.g. CPX-CEC)4)
1) The diagnostic mode can only be set in the remote I/O operating mode.
2) The data field size can only be set in the remote controller operating mode.
3) as of revision 12
4) from revision 13
Tab. 6 Setting diagnostic mode or data field size
The CPX-internal I/O illustration or address allocation can be shifted during a subsequent activation of
the diagnostics mode (status bits or I/O diagnostics interface). The system controller carries out this
adjustment automatically. Manual manipulation, e.g. a reconfiguration of the CPX terminal or manual
adaptation of the hardware and network configuration, are not required.
2.2.6 Setting IP addressing
DIL switch 3 IP addressing
DIL 3.8: 27 = 128 The type of addressing or the Host-ID of the IP address of
DIL 3.7: 26 = 64 the bus node is set via the DIL switch elements 3.1 … 3.8.
DIL 3.6: 25 = 32
DIL 3.5: 24 = 16 Possible settings:
DIL 3.4: 23 = 8 0 = dynamic addressing via DHCP/BOOTP
DIL 3.3: 22 = 4 1 … 254 = permissible address range
DIL 3.2: 21 = 2 255 = reset all IP parameters to factory setting
DIL 3.1: 20 = 1
Factory setting: 0
Tab. 7 Setting IP addressing
Dynamic addressing is set in the factory via DHCP/BOOTP.

If all of the switch elements of the DIL switch 3 are set to the ON position when the bus node is
switched on, all IP parameters will be reset to factory settings.
Example – setting IP address of the bus node
DIL 3.8: OFF Example:

DIL 3.7: OFF 21 + 22 + 25 = 2 + 4 + 32 = 38 (Host-ID)
DIL 3.6: ON 25 = 32
DIL 3.5: OFF Set IP address: 192.168.1.038
DIL 3.4: OFF
16 Festo — CPX-FB36 — 2019-07b

Installation
Example – setting IP address of the bus node
DIL 3.3: ON 22 = 4
DIL 3.2: ON 21 = 2
DIL 3.1: OFF
Tab. 8 Example – IP addressing
2.3 Connecting to the network

2.3.1 General information
NOTICE!
Unauthorised access to the device can cause damage or malfunctions.

When connecting the device to a network, protect the network from unauthorised access.
Measures to protect the network include:
• Firewall
• Intrusion Prevention System (IPS)
• Network segmentation
• Virtual LAN (VLAN)
• Virtual Private Network (VPN)
• Security at physical access level (Port Security)
An access password only protects against unintentional modification.

For additional information è Guidelines and standards for security in information technology, e. g.
IEC 62443, ISO/IEC 27001.
NOTICE!
Modules with Ethernet interfaces should only be operated in networks if all connected network com-
ponents are supplied by PELV circuits or integrated power circuits with equivalent protection.
Installation guidelines
Installation guidelines can be sourced from the ODVA user organisation è www.odva.org.
Use of switches and routers

The switch integrated in the bus node enables division of the network into several segments.
Festo — CPX-FB36 — 2019-07b 17

Installation
The network can be divided into additional segments with the use of additional switches and routers.
This makes it possible to structure the network and achieve greater network expansion.
Regardless of the network structure, the expansion of a network segment must not exceed certain
connection lengths.
– Copper connecting cable
(Ethernet cable, Twisted Pair, 22 AWG):
max. 100 m between network stations
Switches and routers for Industrial Ethernet are available in the market from various manufacturers
and in a variety of components in IP20, IP65 or IP67.
– Unmanaged Switches:
For small networks with low network load or minimum deterministic requirements
– Managed Switches:
For complex networks with diagnostic and monitoring functions
2.3.2 Overview of connection technology and network plug connectors

NOTICE!
If installation has not been carried out correctly and high transmission rates are used, data transmis-
sion errors may occur due to signal reflection and attenuation.
• Note cable specifications è Tab. 10 Cable specification.
Transmission errors can be caused by:
• incorrectly screened connection
• branches
• transmission over distances that are too long
• unsuitable cables.
Connection technology Network connectors
2× socket M12, D-coded, 4-pin, according to Plug NECU-M-S-D12G4-C2-ET

IEC 61076-2, SPEEDCON-compatible
Tab. 9 Overview of connection technology and network plug connectors
RJ45 to M12 converter
For EtherNet/IP installations it may be necessary to switch between RJ45 and M12 connection techno-
logy.
Example: connections between devices in a control cabinet and IP65/IP67 devices.
2.3.3 Cable specification

– Use sheathed Industrial Ethernet wiring of Cat 5/Cat 5e category or better
è Tab. 10 Cable specification.
The CPX bus node supports the "Crossover detection" (Auto-MDI/MDI-X) function. Either Patch cables
or Crossover cables can be used for connecting the bus node with the network or a PC. The circuitry of
the network connections X1 and X2 is adjusted automatically.
18 Festo — CPX-FB36 — 2019-07b

Installation
Cable specification
Cable type Ethernet cable, Twisted Pair, shielded

Transmission class Category Cat 5/Cat 5e
Cable diameter1) 6 … 8 mm
Wire cross section 0.14 … 0.75 mm2; 22 AWG2)
Connection length 3) maximum 100 m ("End-to-End Link")
1) when using NECU-M-S-D12G4-C2-ET plug
2) required for maximum connection length between the network stations
3) according to the specification for EtherNet/IP networks, following ISO/IEC 11801, ANSI/TIA/EIA-568
Tab. 10 Cable specification
NOTICE!
When mounting the CPX terminal on a moving part of a machine:
• Use network cables with strain relief.
• Observe corresponding instructions of IEC 60204/EN 60204.
2.3.4 Network connections

There are two 4-pin, D-coded M12 sockets on the bus node for the network connection. The sockets
are compatible with SPEEDCON plugs.
Both connections have Auto-Negotiation and Crossover detection (factory setting).
When Crossover detection is activated, the bus node automatically sets the pins for transmitted and
received data. If Crossover detection is deactivated, assignment of the pins for transmitted and
received data at the X2 connection is crossed. As a result, several bus nodes in a row can each be con-
nected with a Patch cable.
Socket1) Pin Connection [X1]2) Connection [X2]2)

M12, Signal Explanation Signal Explanation
4-pin
1 TD+ Transmitted data + RD+ Received data +

2 RD+ Received data + TD+ Transmitted data +
3 TD– Transmitted data – RD– Received data –
4 RD– Received data – TD– Transmitted data –
Housing Shield Functional earth Shield Functional earth
1) The functional earth is implemented via the housing
2) Pin allocation with deactivated crossover detection
Tab. 11 Pin allocation of network connections [X1] and [X2]
Festo — CPX-FB36 — 2019-07b 19

Installation
If the "QuickConnect" function has been activated, Crossover detection is not available.
Further information on cabling with deactivated Crossover detection can be found in chapter
è 3.1.2 "QuickConnect".
Connection with Festo plug

The CPX terminal is connected to the network using NECU-M-S-D12G4-C2-ET plugs.
The plugs are designed for network lines with cable diameters of 6 … 8 mm.
To comply with degree of protection IP65/IP67:
– Use Festo plugs.
– Use cover caps to seal unused connections è 2.4 Ensuring the degree of protection.
2.3.5 Setting IP addressing

Alternatively the IP address for the bus node can be set via:
– dynamic addressing via DHCP/BOOTP (factory setting)
– saved addressing
– static addressing using DIL switches
NOTICE!
When the network settings are changed with DIL switches, the "Modify" LED (M) flashes yellow.
• Restart the bus node to activate the modified network settings.
Dynamic addressing via DHCP/BOOTP

– Make sure there is a DHCP/BOOTP server in the network.
To set the dynamic addressing:
1. Set all switch elements of DIL switch 3 to the OFF position è Tab. 7 Setting IP addressing.
2. Dynamic addressing via DHCP/BOOTP alternatively activate via:
– Operator unit (CPX-MMI)
– Software "Festo Maintenance Tool" (CPX-FMT)
– Software "BOOTP-DHCP Server" by ROCKWELL AUTOMATION
Saved network settings
The bus node offers the option of storing the network settings in a non-volatile memory. This will
deactivate DHCP/BOOTP.
1. Set all switch elements of DIL switch 3 to the OFF position è Tab. 7 Setting IP addressing.
2. Alternatively change network settings via:
– Software "BOOTP-DHCP Server" by ROCKWELL AUTOMATION
Use this setting to activate the storage of network settings in the non-volatile memory of the bus
node.
20 Festo — CPX-FB36 — 2019-07b

Installation
Addressing via DIL switches

When addressing via DIL switches, the bus node receives a fixed IP address. This setting is recommen-
ded for test purposes during commissioning or for small networks.
The IP address of the bus node consists of 4 octets:
– Octets 1 … 3: saved in the bus node
– Octet 4: setting via DIL switch 3
– Set a binary number between 1 and 254 with DIL switch element 3.1 … 3.8.
This number is then used as the 4th octet of the IP address when the bus node is switched on.
Example with IP address: Example with IP address:

192.168.001.005 192.168.001.038
20 + 22 = 21 + 22 + 25 =
1+4= 2 + 4 + 32 =
5 38
Tab. 12 Examples of fixed values for the 4th octet of the IP address (binary coded)
If all of the switch elements of DIL switch 3 are set to the ON position when the bus node is switched
on, all network parameters will be reset to the factory setting.
Factory settings of the CPX-FB36
IP address – octet 1 … 3 192.168.1

IP address – octet 4 01)
Network mask (Subnet Mask) 255.255.255.0
Gateway 0.0.0.0
1) dynamic addressing via DHCP/BOOTP
Tab. 13 Factory settings
– Alternatively, change the first 3 octets of the IP address with:
– Software "Festo Field Device Tool" (FFT)
– Access via EtherNet/IP-objects è 6.3.1 Overview of EtherNet/IP objects
Festo — CPX-FB36 — 2019-07b 21

Installation
The network mask and Gateway are set by using the corresponding CPX parameters.
2.3.6 Extended network settings

The following settings for the network connection can be made via the Ethernet link object 0xF6 (246d)
è 6.3.2.4 "Ethernet Link Object".
In the factory setting, the bus node automatically detects the baud rate and duplex mode.
Baud rate
Setting via attribute 6 (Forced Interface Speed) of the Ethernet link object:
– 10 Mbit/s
– 100 Mbit/s
Duplex mode
Setting via attribute 6 (Control Bits, bit 1) of the Ethernet link object:
– Half duplex
– Full duplex
2.4 Ensuring the degree of protection

– Use connection hardware with the required degree of protection è www.festo.com/catalogue;
examples
è Tab. 14 Connection technology and cover caps for degree of protection IP65/IP67 (examples).
– Use cover caps to seal unused connections.
Connection Connecting hardware Cover cap
Network connection (M12) Plug NECU-M-S-D12G4-C2-ET ISK-M12

Service interface (M12) Connection cable KV-M12-M12-... 1) ISK-M12
1) Connection cable for the operator unit (CPX-MMI)
Tab. 14 Connection technology and cover caps for degree of protection IP65/IP67 (examples)
2.5 Power supply of the CPX terminal

CPX terminals are supplied with operating and load voltage via interlinking blocks or end plates.
WARNING!
Risk of injury due to electric shock.

• For the electric power supply, use PELV circuits that guarantee a reliable electric disconnection
from the mains network.
• Observe IEC 60204-1/EN 60204-1.
• Connect all circuits for the operating and load voltage supply.
The power consumption of a CPX terminal depends on the number and type of integrated modules and
components.
22 Festo — CPX-FB36 — 2019-07b

Preparing for commissioning
Observe the information on power supply (è electrical connection) as well as on the earthing meas-
ures to be carried out (è equipotential bonding) contained in the CPX system description.
3 Preparing for commissioning

3.1 EtherNet/IP protocol
EtherNet/IP is an industrial Ethernet protocol, which is predominantly used in automation technology.
The EtherNet/IP protocol is activated via DIL switch 1.2 in the OFF position
è Tab. 5 Setting network protocol.
The bus node then identifies itself with the designation "FB36 - EtherNet IP Remote‑IO".
After switching the protocol, the following unmodified parameters are available:
– IP address
– Diagnostics mode
– System parameters
The DIL switch function remains unchanged.
Retentive bus-specific parameters are only active if the relevant protocol is selected
è 2.2.4 Setting operating mode and network protocol.
Parameterisation examples can be found in the appendix è 6.3.5 Examples.
3.1.1 IP-Multicast telegram

EtherNet/IP uses IP-Multicast telegrams by default for process data transmission. The advantage of
"Multicast" over "Unicast" is that a telegram can be received by multiple stations.
However, simple switches cannot differentiate the stations to which a "Multicast" telegram is to be
forwarded. Therefore these switches send the "Multicast" telegrams to all stations in the network.
This results in a EtherNet/IP station receiving many unnecessary telegrams, which must then be dis-
carded in the device. This may reduce the reaction times of the participants. It also increases the net-
work bandwidth requirements.
This does not pose a problem for smaller networks; however, the performance for larger networks can
be improved with the following functions and/or protocols.
– Use of switches with "IGMP snooping"
– Segmentation of the network
Switches with "IGMP Snooping"
With the help of the Internet Group Management Protocol (IGMP) switches can decide to which
devices the various Multicast telegrams are forwarded. This avoids unnecessary data traffic through
Multicast.
– Activate this function in all switches/routers.
– Configure at least one switch so that cyclic "IGMP Queries" are sent. Without these "IGMP Quer-
ies" the "IGMP Snooping" function cannot work correctly.
Festo — CPX-FB36 — 2019-07b 23

Segmentation of the network

– Split the machine into smaller network segments. For example, this can be implemented with the
aid of VLANs without having to modify the network wiring.
3.1.2 "QuickConnect"
The EtherNet/IP "QuickConnect" function enables the CPX terminal to be started more quickly and the
connection to the EtherNet/IP master to be established more quickly.
"QuickConnect" is commonly used for applications with a tool change, for which the downtime should
be minimised by the disconnection and connection of devices.
NOTICE!
"QuickConnect" only works if this function is supported by all participating devices.
• Make sure that intermediate switches and routers in your network support this function.
The "QuickConnect" function is deactivated in the bus node when delivered from the factory.
For the use of "QuickConnect":
1. "QuickConnect" via attribute 12 of the TCP/IP interface object
è 6.3.2.3 "TCP/IP Interface Object". This deactivates the "Crossover" detection in the bus node.
2. Restart the bus node to activate the modified network settings.
3. Use the same settings for baud rate and duplex mode at the counterpart station (e.g. switch) and
at the PLC as in the bus node.
For fast connection set-up:
– 100 Mbit/s
– Full duplex
4. "QuickConnect" in the PLC or in the control program.
Simplified configuration of "QuickConnect" at the bus node CPX-FB36:

• Set CPX parameter "IP configuration" to "with stored parameters and QuickConnect".
If "QuickConnect" is activated, "Crossover" detection is deactivated for both network connections.

This will operate terminal X1 in MDI mode and terminal X2 in MDI-X mode.
This allows a line topology to be constructed with patch cables:
1 SPS or Switch 3 I/O-Device (e.g. CPX-FB36)

2 Patch cable
Fig. 4 "QuickConnect" line topology with patch cables
24 Festo — CPX-FB36 — 2019-07b

According to EtherNet/IP specification the bus node corresponds to a "Class A Device". When
switched on, the bus node requires less than 350 ms to accept a TCP connection. Due to the fast
establishment of the TCP connection, the detection of IP addresses already in use ("IP Address Con-
flict Detection", ACD) is not fully executed. Multiple assigned IP addresses are only detected late. This
may cause interference in the network.
• If IP addresses are assigned correctly in the network, deactivate the ACD with attribute 10 of the
TCP/IP interface object è 6.3.2.3 "TCP/IP Interface Object".
"QuickConnect" is available for the following modules:
CPX modules Order code
Bus node CPX-FB36

Digital 4x input module CPX-4DE
Digital 8x input module with channel diagnostics CPX-8DE-D
Digital 8x input module, n-switching: CPX-8NDE
Digital 16x input module with channel diagnostics CPX-M-16DE-D
Digital 16x input module with terminal strip CPX-L-16DE-16-KL-3POL
Digital 4x output module CPX-4DO
Digital 8x output module CPX-8DO
Digital 8x output module, high-current variant CPX-8DA-H
Digital 8x input/output module CPX-8DI-8DO
Digital 16x input/output module, with terminal strip CPX-L-8DE-8DA-16-KL-3POL
Analogue 2-gang input module (voltage/current) CPX-2AE-U-I
Analogue 2x output module (voltage/current) CPX-2AA-U-I
Analogue 4x input module (current) CPX-4AE-I
Tab. 15 CPX modules that support "QuickConnect"
"QuickConnect" is available for the following pneumatic modules and pneumatic interfaces:
Pneumatic modules Type
MPA1 pneumatic module VMPA1-FB-EM...-8

MPA2 pneumatic module VMPA2-FB-EM...-4
MPA1 pneumatic module with diagnostic function VMPA1-FB-EM...-D2-8
MPA2 pneumatic module with diagnostic function VMPA2-FB-EM...-D2-8
Tab. 16 Pneumatic modules that "QuickConnect" support
Festo — CPX-FB36 — 2019-07b 25

Pneumatic interfaces Type

(pneumatic interfaces)
for VTSA or VTSA-F pneumatics VABA-10S6-X1

for MPA-S valves VMPA-FB-EPL-…
for MPA-F valves VMPAF-FB-EPL-...
for MPA-L valves VMPAL-FB-EPL-...
VMPAL-EPL-CPX
Tab. 17 Pneumatic interfaces that support "QuickConnect"
3.1.3 Device-Level-Ring protocol (DLR)

The Device-Level-Ring protocol (DLR) allows multiple devices to be operated in a ring topology.
Requirement
All DLR devices feature an integrated Ethernet switch with at least 2 external ports and they support
the DLR protocol.
Fig. 5 Device-Level-Ring topology, example

The availability of the network can be increased with the ring topology, as there are redundant com-
munication paths between two devices. A cable or communication error between two devices will
therefore not result in communication failure. Only two errors in a ring will lead to a malfunction.
A ring always consists of at least one Ring Supervisor and any number of Ring Nodes.
– Use only DLR-capable devices in a ring. Otherwise, the time required for automatic correction of
an error may be adversely affected.
– Operate the bus node as Ring Node either "Beacon-based" or "Announce-based".
Operation as Ring Supervisor is not possible. This function is usually performed by a EtherNet/IP
scanner.
The DLR protocol is configured via the DLR object (Class Code 47h).
3.2 Modbus TCP protocol

Modbus TCP is an open communication protocol based on the MasterSlave architecture. It is a stand-
ard for communication via TCP/IP in automation technology.
26 Festo — CPX-FB36 — 2019-07b

The Modbus TCP protocol is activated via the DIL switch 1.2 in the ON position
è Tab. 5 Setting network protocol.
The bus node then identifies itself with the designation "FB36‑MB - Modbus TCP Remote‑IO".
Parameterisation
After switching the protocol, the following unmodified parameters are available:
– IP address
– Diagnostics mode
– System parameters
The DIL switch function remains unchanged.
Retentive bus-specific parameters are only active if the relevant protocol is selected
è 2.2.4 Setting operating mode and network protocol.
The configuration options via Modbus TCP TCP correspond to those via EtherNet/IP.
Exception: Modbus TCP cannot be used to access EtherNet/IP objects.
To configure the CPX terminal for Modbus TCP, the Modbus addresses of the data and the inputs and
outputs of the CPX terminal are required è 6.4 Modbus TCP-Objects of the CPX-FB36.
Addressing examples can be found in the appendix

è 6.4.6.1 Examples of addressing for Modbus TCP.
3.3 Notes on commissioning the CPX-FB36

Configuration of the CPX terminal requires an exact procedure, because different configuration spe-
cifications are sometimes necessary for each station in the network, due to the modular structure.
Detailed instructions and further information can be found in the documentation or the online help for
the controller or control program.
NOTICE!
The bus node CPX-FB36 can always be used on all EtherNet/IP or Modbus TCPcontrollers.
In the following, the configuration and commissioning of a ALLEN-BRADLEY controller using the "Stu-
dio 5000" software from ROCKWELL AUTOMATION is described as an example.
3.3.1 Requirements for commissioning

– Installation of the bus node is complete.
– The DIL switches of the bus node are set correctly.
– All connecting cables are connected and tested.
Festo — CPX-FB36 — 2019-07b 27

3.3.2 Switching on the power supply

WARNING!
Uncontrolled movements of the actuators, undefined switching statuses.
Injury to people, damage to the machine and system.
Before switching on:
• Make sure that the requirements for commissioning are met.
• Check settings of the DIL switches.
During operation:
• Leave switch elements of the DIL switches unchanged during operation.
NOTICE!
• Observe the instructions for switching on in the controller manual.
3.3.3 Normal operating status

After the CPX terminal is switched on, the status LEDs (è Fig.22) indicate the operating status and
correct function of the bus node and network communications dependent on the configuration.
– Bus node not configured (è Tab. 18 Status LEDs after switch-on – bus node not configured)
– Bus node configured and higher-order controller (PLC) is in stop mode
(è Tab. 19 Status LEDs after switch-on – bus node configured, PLC in the Stop mode)
– Bus node configured and higher-order controller (PLC) is in run mode
(è Tab. 20 Status LEDs after switch-on – bus node configured, PLC in the run mode)
Information on diagnostics using the LED displays can be found in section

è 5.2 Diagnostics via LED displays.
Bus node not configured
LED display Status and meaning
[MS] – Device ready for operation
lights up green
[PS] – Power supply (Power System, PS) OK
– Operating voltage applied
(in the approved range)
lights up green
[NS] – Network communication available, but not configured (operating
status "online"). This state is correct in this case because the bus
node is not configured.
flashes green
28 Festo — CPX-FB36 — 2019-07b

[PL] – Load voltage (Power Load, PL) is applied

(in the approved range)1)
lights up green
[TP1], – Device correctly connected to the bus node
[TP2] – internal communication between bus node and device 1 and/or
device 2 is error-free
– Operating voltage and load voltage present
lights up green
1) Display depends on monitoring and message by the connected device.
Tab. 18 Status LEDs after switch-on – bus node not configured
Bus node configured – PLC in the stop mode
[MS] – Module status (Module Status, MS) error-free
lights up green
lights up green
[NS] – Network status (Network Status, NS) error-free (operating status
"online")
– Communication with the network and PLC OK
lights up green
lights up green
Festo — CPX-FB36 — 2019-07b 29

lights up green
Tab. 19 Status LEDs after switch-on – bus node configured, PLC in the Stop mode
Bus node configured – PLC in the run mode
[MS] – Module status (Module Status, MS) error-free
lights up green
lights up green
[NS] – Network status (Network Status, NS) error-free (operating status
"online")
– Communication with the network and PLC OK
lights up green
lights up green
lights up green
Tab. 20 Status LEDs after switch-on – bus node configured, PLC in the run mode
3.4 Stations in the network

When using the CPX terminal as a new network station for the first time, the configuration program
must be informed of certain network properties.
These network properties are integrated into the station properties.
3.4.1 Station properties (Electronic Data Sheet, EDS file)

The station properties are managed by the configuration program in a list or library, e.g. in an EDS file.
The following options are available for extending an EDS library:
30 Festo — CPX-FB36 — 2019-07b

Commissioning
– Install EDS files

– Enter station properties manually
– Import import properties
As soon as the CPX terminal has been registered as a potential network station, it can be added to a
network.
4 Commissioning
4.1 Configuration
A CPX terminal with bus node CPX-FB36 can be configured using various methods.
Method Description Advantages Disadvantages
Configuration Installation of station With the exception of the I/O Not available with all Ether-
with EDS file properties for the CPX data length, the entire config- Net/IP masters. Paramet-
terminal in the "Stu- uration is taken over from the erisation is saved locally in
dio 5000" configura- EDS file. the CPX terminal and is lost if
tion program. the terminal is replaced.
è 4.1.1 Configuration with EDS file
Configuration Creation of a new sta- Works with all versions All settings must be entered
with "Generic tion and manual con- manually.
Ethernet figuration in the "Stu-
Module" dio 5000" configura-
tion program.
è 4.1.2 Configuration with "Generic Ethernet Module"
Configuration Export of the settings Transfer of the existing con-
with CPX-FMT of the CPX terminal figuration of the station and
CPX-FMT and import parameterisation of the CPX
of the settings in the terminal.
configuration pro-
gram "Studio 5000".
è 4.1.3 Configuration with CPX-FMT
Tab. 21 Configuration methods
4.1.1 Configuration with EDS file

This section describes the configuration of the bus node as a station in an ALLEN-BRADLEY controller
with the aid of the "Studio 5000" software (V 26.01.00) from ROCKWELL AUTOMATION using an
equipment description file (EDS file) from Festo.
The fundamental aspects of this description also apply for other control systems.
Festo — CPX-FB36 — 2019-07b 31

Commissioning
Obtaining EDS files

– Use one of the following EDS files for the CPX terminal with CPX-FB36.
File type File name Language Description
EDS cpx_FB36.eds English Provides the communication adapter in

the configuration program.
cpx_FB36RC.eds English File with information for the operating
mode Remote Controller.
ICO cpx_FB36.ico - Symbol file for representing the CPX ter-
minal or module in the configuration pro-
gram.
Tab. 22 Device description files for CPX-FB36
The device description file is available from the Festo support portal è www.festo.com/sp.
Registering the EDS file

1. Start "Studio 5000" software.
2. Start EDS wizard:
["Tools"] > ["EDS Hardware Installation Tool"]
Fig. 6 Start EDS wizard

3. In the ""ROCKWELL AUTOMATION's EDS Wizard"" dialogue box select the ""Register an EDS
file(s)"" option and confirm the selection with the ""Next >"" button.
32 Festo — CPX-FB36 — 2019-07b

Commissioning
Fig. 7 EDS wizard – options

4. Select one of the following options:
– ""Register a single file""
– ""Register a directory of EDS files""
5. Press the ""Browse…"" button and select the EDS file from the corresponding directory.
Fig. 8 EDS wizard with selected EDS file

6. Confirm selection with the ""Next >"" button.
Ä The procedure for registering the bus node is complete.
Festo — CPX-FB36 — 2019-07b 33

Commissioning
Integrate and configure stations in the project
Configuration of the bus node can only take place if there is no online connection to the controller.
1. Abort an existing online connection to the higher-level controller:

["Communications"] > "Go Offline"
2. Open the ""Select Module Type"" dialogue:
In the ""Controller Organizer"" window in the ""I/O Configuration"" directory right click on
""Ethernet"" and select ""New Module…"" from the context menu.
Fig. 9 Context menu for “New Module…”

3. In the register ""Catalog"" select from the table the module with the description "CPX‑FB36 Eth-
erNet/IP 2‑Port Remote I/O".
34 Festo — CPX-FB36 — 2019-07b

Commissioning
Fig. 10 Integrating bus node in the project as a station

4. Confirm selection with the ""Create"" button.
Ä This opens the ""New Module"" dialogue for configuring the new stationè Fig.11.
Fig. 11 Configuring station

5. Enter a name for the bus node.
6. Enter IP address of the bus node.
7. Open the ""Module Definition"" dialogue:
Click on the ""Change"" button.
Festo — CPX-FB36 — 2019-07b 35

Commissioning
Fig. 12 Enter I/O data length

8. Enter the I/O data length (number of inputs and outputs) of the CPX terminal.
This value can either be calculated or read out with the aid of CPX-FMT or web server.
9. Confirm inputs with the ""OK"" button.

10. Exit ""Module Definition"" dialogue.
Ä The bus node appears as a newly integrated station in the ""Controller Organizer"" window
in the ""I/O Configuration/Ethernet"" directory.
36 Festo — CPX-FB36 — 2019-07b

Commissioning
Changing configuration of the station

["Communications"] > ["Go Offline"]
2. Open the ""Module Properties"" dialogue:
In the ""Controller Organizer"" window in the ""I/O Configuration/Ethernet"" directory right-
click on the corresponding module and select ""Properties"" from the context menu.
Fig. 13 Context menu for “Properties”

3. Change configuration of the station with the input fields and confirm with the “"OK"” button.
4.1.2 Configuration with "Generic Ethernet Module"

In this section, the manual configuration of the bus node as a station in a ALLEN-BRADLEY controller
described using the "Studio 5000" software (V 26.01.00) from ROCKWELL AUTOMATION.
Integrate and configure stations in the project
Festo — CPX-FB36 — 2019-07b 37

Commissioning

2. Open the ""Select Module Type"" dialogue:
In the ""Controller Organizer"" window in the ""I/O Configuration"" directory right click on
""Ethernet"" and select "New Module…" from the context menu è Fig.9.
3. In the register ""Catalog"" select from the table the module with the description ""Generic Ether-
net-Module"".
Fig. 14 Integrate bus node as Generic Ethernet Module

4. Confirm selection with the ""Create"" button.
Ä This opens the ""Module Properties"" dialogue for configuring the module as a
participantè Fig.15.
38 Festo — CPX-FB36 — 2019-07b

Commissioning
Fig. 15 Configuring station

5. Enter a name for the bus node.
6. Select the (Data - SINT or Data - INT) data format in the ""Comm Format"" list box.
8. Enter values for ""Assembly Instance"" depending on the selected data format
è Tab. 23 Input values for ""Assembly Instance"
".
Data format Data – SINT Data – INT
""Input"" 101 111

""Output"" 100 110
""Configuration"" 102 102
Tab. 23 Input values for ""Assembly Instance""
Festo — CPX-FB36 — 2019-07b 39

Commissioning
9. Input values for ""Size"" depending on the selected operating mode

è Tab. 24 Input values for ""Size"
".
Mode of operation Values
Remote I/O ""Input"" and ""Output"":

Number of assigned inputs and outputs of the CPX terminal:
– for data format SINT: in bytes
– for data format INT: in words
The input ""Size"" = 0 for inputs and outputs is not permitted in the
Remote I/O operating mode.
""Configuration"":
– Number of memory slots occupied by CPX parameters
or
– 0 (default setting)1)
Remote Controller ""Input"" and ""Output"":
Set data field size
(è Tab. 6 Setting diagnostic mode or data field size):
– for data format SINT: in bytes
– for data format INT: in words
""Configuration"":
– 0 (default setting)1)
1) "Configuration Assembly" not used
Tab. 24 Input values for ""Size""
When using a CPX terminal without inputs:

• Activate status bits via DIL switch 2 è Tab. 6 Setting diagnostic mode or data field size.
The following settings then apply for the input data (""Input""):
• for format SINT: "Size" = 2
• for format INT: "Size" = 1
10. Confirm inputs with the ""OK"" button.

11. Exit ""Module Properties"" dialogue.
Ä The bus node appears as a newly integrated station in the ""Controller Organizer"" window
in the ""I/O Configuration/Ethernet"" directory.
40 Festo — CPX-FB36 — 2019-07b

Commissioning
Using station properties

– Use the following data in the higher-order controller è Tab. 25 Station features.
Characteristic Description
"Vendor Name" Festo Corporation

"Vendor ID" 26 = 1Ah
"Device Type" 12 = 0Ch
"Product Code"
(depending on the operating mode)
– "Remote I/O" 14026 = 36CAh
– "Remote Controller" 14027 = 36CBh
"Major Revision" 1
"Input size"/"Output size" depending on the CPX configuration
"Assembly Instance" SINT format INT format
– "Input" 101 111
– "Output" 100 110
– "Configuration" 102 102
– "Diagnosis" 103 103
"Product Name" CPX-FB36 Remote IO
CPX-FB36 Remote Controller
Advanced EtherNet/IP station features
Min. bus cycle time ("Request Packet 1 ms
Interval", RPI)
Connections
– Total of all connections max. 32
– "Exclusive Owner" max. 1
– "Input only" max. 32
– "Listen only" max. 311)
1) only with simultaneous "Exclusive Owner" or "Input only" connection
Tab. 25 Station features
Changing configuration of the station

In the ""Controller Organizer"" window in the ""I/O Configuration/Ethernet"" directory right-
click on the corresponding module and select ""Properties"" from the context menu.
Festo — CPX-FB36 — 2019-07b 41

Commissioning
Fig. 16 Context menu for ""Properties"" (Generic)

3. Change configuration of the station with the input fields and confirm with the “"OK"” button.
4.1.3 Configuration with CPX-FMT

It is possible to export the configuration and complete parameterisation of a CPX terminal to a file and
then import the file into the controller as a project with the “Festo Maintenance Tool” software
(CPX-FMT).
This section describes the transfer of the configuration file to a controller from ALLEN-BRADLEY with
the help of the software "Studio 5000" (V 26.01.00) from ROCKWELL AUTOMATION.
Exporting a configuration from CPX-FMT
The "Festo Maintenance Tool" software (CPX-FMT) is available on the Festo support portal
è www.festo.com/sp.
1. Start CPX-FMT software.

2. Make sure that there is an Ethernet connection between CPX-FMT and the CPX terminal.
3. Activate the online function to transfer the current configuration of the bus node to the PC.
4. Change the configuration and parameterisation for the CPX terminal with CPX-FB36, if necessary.
The CPX terminal can also be configured offline. Changes can also be made after importing the
project in the "Studio 5000" software.
5. Open the dialogue for exporting the configuration:

["File"] > ["Export"] > ["RSLogix (.L5K)"].
42 Festo — CPX-FB36 — 2019-07b

Commissioning
Fig. 17 Configuration for "Studio 5000" export

6. Select and save a directory and name to save the L5K file.
Importing configuration
1. Start "Studio 5000" software.
2. Open saved L5K file:
["File"] > ["Open"] and select the saved L5K file.
3. Confirm selection with the ""Open"" button.
4. Select the directory and name for the imported file.
5. Confirm selection with the ""Import"" button.
Ä The L5K file is imported into a new project (.ACD) as an Ethernet module.
Festo — CPX-FB36 — 2019-07b 43

Commissioning
Integrating the CPX terminal into an existing project

The CPX terminal configured and parameterised with the Festo Maintenance Tool software appears in
the "Studio 5000" software as an Ethernet module.
To integrate this module into an existing project:
1. In the window ""Controller Organizer"" in the directory ""I/O Configuration"" right click on the
Ethernet module and select ""Copy"" in the context menu.
Fig. 18 Copying Ethernet module

2. Open the project to which the imported Ethernet module is to be added.
3. In the ""Controller Organizer"" window in the ""I/O Configuration"" directory right-click on
""Ethernet"" and select ""Paste"" from the context menu.
44 Festo — CPX-FB36 — 2019-07b

Commissioning
Fig. 19 Inserting Ethernet module

The project has now imported all required settings of the CPX terminal. This includes,
among other things, I/O data lengths, the IP configuration and all module and system parameters.
Configuration and parameterisation are hereby completed. Changes to the parameterisation of the
modules and valve terminals used in the CPX terminal are made with the “Studio 5000” software.
4.1.4 Configuration in Remote Controller operating mode

When using a control block CPX-FEC or CPX-CEC in the CPX terminal, the bus node must be used in the
Remote Controller operating mode.
In principle, the bus node is configured in the same manner as in the Remote I/O operating mode, but
with different I/O data lengths.
The bus node then occupies 8 or 16 byte inputs and 8 or 16 byte outputs depending on the setting of
DIL switch 2.2 è Tab. 6 Setting diagnostic mode or data field size. These inputs and outputs are avail-
able to the control program of the control block.
To use the Remote Controller operating mode:
1. Set Remote Controller operating mode with DIL switch 1.1 è Tab. 4 Setting operating mode.
2. Set the network protocol with DIL switch 1.2 è Tab. 5 Setting network protocol.
3. Set the required data field size with DIL switch 2.1
è Tab. 6 Setting diagnostic mode or data field size.
The bus node is now configured in the Remote Controller operating mode.
Festo — CPX-FB36 — 2019-07b 45

Commissioning
4.1.5 "Listen-only" Set up connection

When the station properties have been configured (e.g. by installation of an EDS file), the following
steps are required for configuration.
1. Install CPX terminal and set IP addressing è 2.3.5 Setting IP addressing.
2. Establish connection to bus node.
To do this, in the "Studio 5000" software use the ""Generic Ethernet Device"" profile
è 4.1.2 Configuration with "Generic Ethernet Module".
3. Open the ""Module Properties"" dialogue.
4. Select "Data ‑ SINT" data format from the ""Comm Format"" list field è Fig.15.
5. Enter the following values in the ""Connection Parameters"" area:
"Connection Parameters" "Assembly Instance" "Size"
"Input" 101 Number of inputs set

on the bus node
"Output" 254 0
"Configuration" 102 ("Configuration Assembly") 0
Tab. 26 Properties for “Connection parameters”
4.2 Parameterisation
WARNING!
Uncontrolled movement of the actuators, undefined switching statuses
Injury to people, damage to the machine and system
• During the parameterisation process, make sure that nobody is within the danger zone of moving
parts of your system.
The CPX terminal is supplied from the factory with preset parameters. These parameters are saved in
the bus node.
These parameters can be used to generally adapt the behaviour of the CPX terminal to the relevant
application.
A distinction is made between the following variants:
– System parameters, e.g. setting reaction times, switching off error messages
– Module parameters (module- and channel-specific), e.g. diagnostic settings, settings for error
handling, settings for debounce times of inputs, settings for forcing
– Parameters of the diagnostic memory
A detailed description of the individual parameters as well as basic principles of application can be
found in the CPX system description (CPX-SYS).
46 Festo — CPX-FB36 — 2019-07b

Commissioning
The module parameters can be found in the descriptions for the modules, e.g. description of the CPX
pneumatic interfaces and CPX I/O modules (CPX-EA).
4.2.1 Parameterisation during switch-on [system start]

The parameterisation of the CPX terminal is initially dependent on the setting of the [system start]
parameter. This parameter establishes whether the default parameters or the parameters saved by
the user in the bus node are used when switching on the CPX terminal.
The parameterisation is loaded again after every interruption of the power supply or the network con-
nection. For example, this enables exchange of individual CPX modules without the need for re-para-
meterisation.
Sequence of parameterisation when the CPX terminal is switched on

System start with default parameters ("Default parameters")
1. The controller transmits the parameterisation that is saved in the controller to the bus node.
2. The bus node distributes this parameterisation to the individual modules.
System start with stored parameters ("Saved parameters")
• The bus node distributes the parameterisation that is saved in the bus node to the individual
modules.
The parameterisation saved in the bus node can be overwritten accidentally by the controller.
• Prevent unintentional overwriting of the stored parameterisation by changing the "Configura-
tion" connection parameter using the "Studio 5000" software.
To change the "Configuration" connection parameter with the "Studio 5000" software:
In the window ""Controller Organizer"" in the directory ""I/O Configuration"" double click on
""Ethernet"".
Festo — CPX-FB36 — 2019-07b 47

Commissioning
1 ""Assembly Instance"" connection paramet-

er for ""Configuration""
Fig. 20 Dialogue ""Module Properties""
3. In the ""Connection Parameters"" range for ""Configuration"" enter the value ""Assembly
Instance"" = 0.
4. Close dialogue ""Module Properties"" with the ""Finish" >>" button.
If the Modifiy (M) LED on the bus node is on permanently after system start-up, [System start with
saved parameters] is set.
4.2.2 Methods of parameterisation
Parameterisation Export of CPX ter- Convenient transfer of the –
via configuration minal parameterisa- complete configuration for

data (Configuration tion by using CPX- a CPX terminal.
Assembly) FMT.
Import of the set-
tings in the "Stu-
dio 5000" software.
è 4.2.3 Parameterisation via configuration data
48 Festo — CPX-FB36 — 2019-07b

Commissioning
Parameterisation Parameterisation Convenient parameterisa- Parameterisation of the

with the CPX-MMI via menu-driven tion via the menu naviga- CPX terminal is saved loc-
operator unit entries. tion (plain text). ally in the bus node and is
lost if the node is
replaced.1)
è 4.2.4 Parameterisation with the CPX-MMI operator unit
Parameterisation in Parameterisation Parameters are reloaded User program required
the PLC user pro- via Explicit Mes- after every restart and are
gram saging. Parameters therefore also retained if
are saved in the the device is replaced.
PLC.
è 4.2.5 Parameterisation in the PLC user program
Parameterisation Parameterisation Fast, simple parameterisa- Parameterisation of the
using CPX-FMT and via menu-driven tion during commissioning CPX terminal is saved loc-
system start with entries. for testing the parameters. ally in the bus node and is
saved parameters Parameters are lost when replaced.1)
saved directly in the
bus node.
Start with saved
parameters neces-
sary.
è 4.2.6 Parameterisation using CPX-FMT and system start with saved parameters
1) The current parameterisation can be copied with the CPX-MMI operator unit.
Tab. 27 Methods of parameterisation
Further information about parameterisation can be found in the CPX system description (CPX-SYS).
NOTICE!
The last parameterisation transferred in the CPX terminal is always valid.
4.2.3 Parameterisation via configuration data

The parameterisation via configuration data (Configuration Assembly) corresponds to the method for
configuration with CPX-FMT and transfer of all parameters to the "Studio 5000" software
è 4.1.3 Configuration with CPX-FMT.
Festo — CPX-FB36 — 2019-07b 49

Commissioning
4.2.4 Parameterisation with the CPX-MMI operator unit

The CPX-MMI operator unit offers menu-driven access to the parameterisation. It does not require any
additional configuration software.
Information about using the operator unit can be found in the corresponding description.
4.2.5 Parameterisation in the PLC user program

Program-controlled access to parameters is via Explicit Messaging. The addresses of the EtherNet/IP
object model required for this can be found in the appendix è 6.3.1 Overview of EtherNet/IP objects.
Further information on programming this data data transfer can be found in the manual for the control-
ler.
4.2.6 Parameterisation using CPX-FMT and system start with saved parameters
The parameterisation corresponds to the method for configuration with CPX-FMT and transfer of all
parameters to the "Studio 5000" software è 4.1.3 Configuration with CPX-FMT.
The parameterisation of the CPX terminal is saved directly in the bus node. To use this parameterisa-
tion, the “System start” parameter needs to be set to “Saved parameters”
è 4.2.1 Parameterisation during switch-on [system start].
4.3 Behaviour of the outputs in the "Fail safe mode" or " "Idle mode" mode
“Idle mode” ("Idle mode") is assumed by the participants after a request by the master.
The error state ("Fail safe mode", also called "Fault mode") defines the state of the respective chan-
nel in case of network communication errors.
This applies for this status:
– Inputs are transmitted
– Output channels of the stations are no longer updated
In the "Fail safe mode" or "Idle mode" outputs can have one of the following states:
Digital outputs/valves Analogue outputs
Freeze current status Freeze current status

Reset the output Desired analogue value
Setting the output
Tab. 28 Possible states in the "Fail safe mode"/"Idle mode"
The status to be assumed for each output channel (output or solenoid coil) can be determined separ-
ately. The standard setting is "Reset of the output channel".
Additional information can be found in the CPX system description (CPX-SYS).
4.4 Web server

A web server is integrated in the CPX-FB36 bus node. The web server provides the most important
parameters and diagnostic functions.
50 Festo — CPX-FB36 — 2019-07b

Commissioning
Fig. 21 Web server of the CPX-FB36
Procedure
– Enter the IP address of the bus node in the address line of an internet browser as follows :
http://192.168.1.xxx
4.5 Check list for commissioning a CPX terminal

– Observe the general instructions for commissioning in the CPX system description (CPX-SYS).
– Check the DIL switch settings and network configuration before using and replacing the CPX ter-
minal.
– Check the configured address range and test the inputs and outputs, if necessary.
– Check the address assignment of the inputs and outputs on the CPX terminal, e.g. with the
"Force" function.
– Make sure that the desired parameterisation of the CPX terminal in the start-up phase or after net-
work interruptions is restored by the interface module.
This ensures that, if the CPX terminal is replaced, the new terminal will also be operated with the
desired parameter settings.
– If necessary, check parameterisation with configuration software (e.g. "Studio 5000") or an oper-
ator unit (e.g. CPX-MMI).
4.6 Replacing bus node

CAUTION!
For CPX terminals with a steady or flashing "Modify" LED (M), the parameterisation is not automatic-
ally created by the higher-level system when the CPX terminal is replaced during servicing.
• Make a note of the settings required before replacement and restore them after replacement.
Festo — CPX-FB36 — 2019-07b 51

Diagnostics
When replacing a bus node with the setting [System start with saved parameters], the CPX terminal is
not automatically parameterised by the higher-order controller.
The CPX-FB36 bus node is compatible with the CPX-FB32 bus node:
In existing applications, a CPX-FB32 bus node can be replaced by a CPX-FB36 bus node (from Revision
13) without changing the configuration of the host system.
Exchange with the Festo Maintenance Tool (CPX-FMT):

1. Before replacing the bus node, save the parameterisation of the CPX terminal in a CPX-FMT file.
2. After replacing the bus node, transfer the parameterisation to the new bus node.
["CPX"] > ["Download Settings..."]
3. Activate all settings to be loaded in the dialogue ""Download"".
4. Start the transfer to the bus node by pressing the ""OK"" button.
5 Diagnostics
5.1 Diagnostics options
Diagnostics option Brief description Advantages
LED display Display of configuration, hardware, Fast error detection "on-site"

network errors, etc. directly at the
bus node.
è 5.2 Diagnostics via LED displays
Status bits Internal inputs that supply coded Fast access to error messages, inde-
common diagnostic messages. pendent of the interface and higher-
order controller.
è 5.3 Diagnostics via status bits and CPX system description (CPX-SYS)
I/O diagnostics inter- Bus-independent diagnostic inter- Detailed error detection and further
face face at I/O level, which enables processing of diagnostic data, e.g.
access to the internal data of the by a PLC user program.
CPX terminal
(16 inputs and 16 outputs)
è 5.4 Diagnostics via the I/O diagnostics interface and CPX system description (CPX-SYS)
Operator unit CPX-MMI Menu-driven display of diagnostic Fast error detection "on site"
information on the operator unit. without programming in plain text.
è Description of operator unit (CPX-MMI)
52 Festo — CPX-FB36 — 2019-07b

Diagnostics
Diagnostics option Brief description Advantages
Diagnostics via Ether- Access to all system data of the CPX Detailed error detection as well as
Net/IP terminal over the network. access to the diagnostic memory in
the online mode of the controller
software and in the PLC user pro-
gram.
è 6.3.1 Overview of EtherNet/IP objects
Tab. 29 Diagnostics options
The available diagnostic information is dependent on the DIL switch settings on the bus node and the
parameterisation of the CPX terminal.
5.2 Diagnostics via LED displays

The following LED displays for diagnosis of errors are available on the bus node:
1 CPX-specific LED displays:

– PS: Power System (green)
– PL: Power Load (green)
– SF: System Failure (red)
– M: Modifiy (yellow)
2 Network-specific LED displays
- MS: Module Status (green, red)
- NS: (greenNetwork Status, red)
– TP1: Link/Traffic Port 1 (green)
– TP2: Link/Traffic Port 2 (green)
Fig. 22 LED displays
In the following sections, the different statuses of the LED displays are shown as follows:
lights up
flashing
off
Tab. 30 Status of the LED displays
Festo — CPX-FB36 — 2019-07b 53

Diagnostics
Normal operating status

In the normal operating status the following LEDs are green è Tab. 31 Normal operating status.
The SF-LED is not on. The M-LED is only on with the "System start with stored parameterisation and
stored CPX extension" setting (function number 4402
è Tab. 73 Attributes of the system object for Remote I/O operating mode).
LED display Operating status
These LEDs are green: normal

– MS
– NS
– TP1/TP21)
– PS
– PL
The red LED (SF) is not on.
The yellow LED (M) is on.2)
1) Steady light: ready for data transfer; flashing: data being transmitted
2) On only if "System start with stored parameterisation and stored CPX extension" is activated.
Tab. 31 Normal operating status
5.2.1 CPX-specific LED displays
PS (Power System) – power supply

LED status Meaning Error handling
No error. Operating voltage –
applied.
lights up green
Operating voltage outside the – Rectify undervoltage.
tolerance range.
flashes green
(fast flashing)
Internal fuse has tripped. 1. Rectify short circuit/overload.
2. Depending on the parameterisation:
– The power supply will be switched
flashes green
on again automatically after the
short circuit has been eliminated
(factory setting).
– Switch the power supply off and
then on again.
54 Festo — CPX-FB36 — 2019-07b

Diagnostics
PS (Power System) – power supply

Operating voltage not present. – Check connection of the operating

voltage.
off
Tab. 32 LED display PS (power supply)
PL (Power Load) – load voltage supply

No error. Load voltage present. –
lights up green
Load voltage outside the toler- – Rectify undervoltage.
ance range.
flashes green
Tab. 33 LED display PL (load voltage supply)
SF (System Failure) – system error

LED status1) Meaning Error handling
minor error/information è CPX system description (CPX-SYS)

(fault class 1) 2)
flashes red 1x
Error
(fault class 2) 3)
flashes red 2x
serious error
(fault class 3) 4)
flashes red 3x
No error. –
off
1) The LED display SF flashes depending on the error class that has occurred.
2) Fault class 1 (minor faults): 1x flashing, pause time
3) Fault class 2 (faults): 2x flashing, pause time
4) Fault class 3 (serious faults): 3x flashing, pause time
Tab. 34 LED display SF (system error)
Festo — CPX-FB36 — 2019-07b 55

Diagnostics
M (Modify) – parameterisation modified or forcing active

LED status Meaning
System start with saved parameterisation and saved CPX expansion has
been set:
– Parameters and CPX configuration are stored retentively
on yellow
– external parameterisation is blocked1)
Caution when replacing CPX valve terminals with saved parameterisation.
For these CPX terminals, parameterisation is not carried out automatically
by the higher-order controller when the terminal is replaced.
– Before replacing, determine the necessary settings and restore them if
necessary.
Forcing active1)
The Force function is enabled or the IP address was changed via the DIL
switch (restart required).
flashing yellow
System start with default parameterisation and current CPX structure (fact-
ory setting)
– external parameterisation is possible
off
1) The display of the Force function (LED flashes) has priority over the display of the system start setting (LED on).
Tab. 35 LED display M (parameterisation modified or forcing active)
5.2.2 Network-specific LED displays
MS (Module Status) – Module status1)

Network protocol EtherNet/IP

normal operating status -
lights up green
Configuration of the CPX terminal – Complete or correct configura-
not complete or not correct. tion of the CPX terminal.
flashes green
error cannot be rectified – Contact Festo Service
(è www.festo.com).
lights red
error can be rectified – Check configuration of the CPX
terminal.
flashes red
56 Festo — CPX-FB36 — 2019-07b

Diagnostics
MS (Module Status) – Module status1)

The CPX terminal is in self-test. –
flashes red/green
No logic power supply to the net- – Check logic power supply.
work interface.
off
Network protocol Modbus TCP
Ready for Modbus connections –
lights up green
Not ready for Modbus connections –
off
1) The behaviour of the LED display depends on the network protocol used.
Tab. 36 LED display MS (Module Status)
NS (Network Status) – Network Status1)

Network protocol EtherNet/IP

Normal operating status. The CPX –
terminal is online and has a net-

work connection.
lights up green
The CPX terminal is online and has – Check configuration of the CPX
received an IP address but does terminal; it is possible that the
not have a configured network con- CPX terminal has not been
flashes green
nection. allocated to a Master/Scanner.
Communication has failed. Non- – Correct IP address.
permitted IP address set that is
already used in the network.
lights red
One or more "I/O Connections" – Check physical connection to
are in the "Time-out status". the Master/Scanner.
flashes red
Festo — CPX-FB36 — 2019-07b 57

Diagnostics
NS (Network Status) – Network Status1)

The CPX terminal is in self-test. –
flashes red/green
The CPX terminal is offline. – Check network connection.
off
Network protocol Modbus TCP
At least one Modbus connection –
active.
lights up green
No Modbus connection active. –
off
1) The behaviour of the LED display depends on the network protocol used.
Tab. 37 LED display NS (Network Status)
TP1, TP2 (Link/Traffic) – connection/data traffic

Network connection OK –
lights up
Data traffic activity (Traffic) –
Flashing frequency depends on the

traffic.
flashing
No network connection – Check network connection.
off
Tab. 38 LED display TP1, TP2 (connection/data traffic)
5.3 Diagnostics via status bits

Status bits are internal inputs that serve to display common diagnostic messages (global error mes-
sages). If all status bits return a logic 0, no error is reported. If at least one status bit returns a logic 1,
there is a fault è Tab. 39 Overview of status bits.
58 Festo — CPX-FB36 — 2019-07b

Diagnostics
If the status bits are to be transmitted via a "Polled" or "Change of state" connection, the DIL
switches on the bus node must be set accordingly è Tab. 6 Setting diagnostic mode or data field size.
Bit Diagnostic information with logic 1 Description
0 Error at valve Module type in which an error has

1 Error at output occurred
2 Error at input
3 Error at analogue module/technology module Module type in which an error has
occurred
4 Undervoltage Type of error
5 Short circuit/overload Type of error
6 Cable break Type of error
7 Other error Type of error
Tab. 39 Overview of status bits
Detailed information on the status bits can be found in the CPX system description (CPX-SYS ).
5.4 Diagnostics via the I/O diagnostics interface

Detailed diagnostic information about the CPX terminal can be accessed via the I/O diagnostic inter-
face. As a result, it can be determined exactly on which module and channel an error has occurred, for
example. Available to access this information are 16 input bits and 16 output bits, through which all
diagnostic data can be read.
To use the I/O diagnostics interface, it must be activated via DIL switches on the bus node
è Tab. 6 Setting diagnostic mode or data field size. When the I/O diagnostic interface is activated, the
first 16 inputs and outputs in the address range are occupied è Tab. 50 Sequence of addressing.
Diagnostic data Description
Global diagnostic data General overview of errors

Module diagnostic data Detailed diagnostics per module
Status of diagnostic memory Number of entries in the diagnostic memory and operating
mode
Diagnostic memory data Long-term memory, detailed diagnostics and relative time
stamp per error event
Tab. 40 Diagnostic data
Festo — CPX-FB36 — 2019-07b 59

Diagnostics
Detailed information on the I/O diagnostic interface and the available diagnostic information and the
corresponding function numbers can be found in the CPX system description (CPX-SYS).
Accessing EtherNet/IP objects via Explicit-Messaging programming is more useful for the CPX-FB36
bus node than using the I/O diagnostics interface è 6.3.1 Overview of EtherNet/IP objects.
5.5 Diagnostics via EtherNet/IP

The CPX system permits diagnostics through the network. The following options are supported here:
– Explicit Messaging via EtherNet/IP-Master
– Diagnostics via user program The I/O diagnostic interface can also be read out here.
Overview of diagnostic data for Explicit Messaging
The following EtherNet/IP objects offer detailed diagnostic information:
Object classes Name Diagnostic data
101d Generic Module Parameter – Faulty channel type

Object – Number of the faulty channel
– Module error number
133d Status and Diagnostics Object – Number of the module in which an error has
occurred
– Diagnostic status (specifies whether dia-
gnostic data are present)
– System error number
134d Diagnostics Trace Object – Long-term memory
(max. 40 entries)
– Detailed diagnostics and relative time stamp
per error event
135d Diagnostics Trace Status Object – Number of entries in the diagnostic memory
– Trace status
Tab. 41 Diagnostic data with Explicit Messaging
Possible sequence of diagnostics
Possible sequence of dia- Diagnostic data Object that supplies the dia-
gnostics gnostic data
1. Check whether diagnostic Diagnostic status Status and Diagnostics Object

data are present (133d)
60 Festo — CPX-FB36 — 2019-07b

Diagnostics
Possible sequence of dia- Diagnostic data Object that supplies the dia-
gnostics gnostic data
2. Determine the number of the Number of the module Status and Diagnostics Object
module in which an error has (133d)
occurred
3. Determine relevant module Error number, channel type and Generic Module Parameter
diagnostic data number of the faulty channel Object (101d)
Tab. 42 Possible sequence of diagnostics
5.6 Diagnostics via Modbus TCP

The CPX system enables diagnostics via the protocol Modbus TCP è Description CPX-CEC/CPX-FEC:
– Diagnostics via CPX status register, CPX diagnostic memory and I/O diagnostics interface
5.7 Error handling ("Fail safe")

The behaviour of the CPX terminal with the following malfunctions is dependent on the parameterisa-
tion of the higher-order controller and the setting of the "Fail safe" parameter:
– Telegram failure
– Stop the higher-order controller
– Break in the network cable.
Depending on the parameterisation, the outputs (valves and electric outputs) will be switched off
(factory setting), switched on or retain their status.
“Reset outputs” means the following:

• Monostable valves move to the initial position.
• Bistable valves remain in the current position.
• Mid-position valves go into mid-position (pressurised, exhausted or blocked, depending on valve
type).
WARNING!
Undesired status of valves and outputs with communication errors
Injury to people, damage to the machine and system
An incorrect status of valves and outputs can lead to dangerous situations.
• Ensure that valves and outputs relating to the aforementioned malfunctions are placed in a safe
condition.
The Modbus connection for the controller is monitored by default with a timeout of 10 seconds. This
time can be adjusted via Modbus address 46100 è Tab. 118 Modbus connection timeout.
If no telegrams are received by the controller during the set time, the outputs are set to the set values
of the "Fail safe" parameter.
Festo — CPX-FB36 — 2019-07b 61

Technical appendix
6 Technical appendix
6.1 Technical Data
General technical data
Technical data of the CPX terminal è CPX system description (CPX-SYS)

Degree of protection through housing IP65/IP671)
in accordance with IEC 60529, completely moun-
ted, plug connector in plugged-in status or
equipped with cover caps
Protection against electric shock by the use of PELV-circuits
Protection against direct and indirect contact in
accordance with IEC 60204-1/EN 60204-1
Module code (CPX-specific)
Remote I/O 224
Remote Controller 171
Module identifier (operator unit)
EtherNet/IP
Remote I/O FB36 EtherNet/IP Remote‑IO V2
Remote Controller FB36‑RC EtherNet/IP Node
Modbus TCP
Remote I/O FB36‑MB Modbus TCP Remote‑IO
Remote Controller FB36‑MB‑RC Modbus TCP Node
1) Connected products may only satisfy a lower degree of protection.
Tab. 43 Technical data – general
Power supply
Operating power supply UEL/SEN [V DC] 24 ± 25 %

Intrinsic current consumption [mA] Typ. 100 (internal electronics)
at nominal operating voltage 24 V from
operating voltage supply UEL/SEN
Network interface separation Galvanic
Operating power supply UEL/SEN
Load voltage supplyVAL/OUT [V DC] 24 ± 10 %
Mains buffering time [ms] 10
Tab. 44 Technical data – power supply
62 Festo — CPX-FB36 — 2019-07b

Technical appendix
Network-specific technical data
Connection technology 2× socket, M12, D-coded, 4-pin

Protocol EtherNet/IP or Modbus TCP1)
Specification IEEE 802.3u (100Base-TX)
Transmission rate [Mbit/s] 10/100 (full duplex/half duplex)
Minimum cycle time (RPI) [ms] 1
Maximum data field size (Input/Output Size)
Remote I/O [Bytes] 64 I/64 O
Remote Controller [Bytes] 8 I/8 O, 16 I/16 O, 32 I/32 O or 64 I/64 O2)
Crossover detection Auto MDI/MDI-X
Cable type Ethernet-TwistedPair cable, shielded
Transmission class Category Cat 5/Cat 5e
Max. cable length [m] 100
1) based on the Ethernet protocol IEEE 802.3
2) depending on the setting of DIL switch 2 and the revision of the bus node
Tab. 45 Technical data – network-specific
6.2 Address assignment of the CPX terminal

6.2.1 Address assignment
A CPX terminal consists of a different number of inputs and outputs, depending on the order and the
configuration of the bus node.
The inputs and outputs are assigned automatically within the CPX terminal.
– Determine the address assignment (number of allocated inputs and outputs) on the CPX terminal
prior to commissioning.
NOTICE!
• The address space of a CPX terminal is limited. The bus node provides the CPX terminal a maxim-
um address space of 64 bytes for inputs and 64 bytes for outputs.
• An activated diagnostic mode reduces the number of available I/O bytes.
The number of assigned inputs and outputs for modules can be found in the following tables:
• Bus node è Tab. 46 Address assignment of bus nodes
• Digital modules è Tab. 47 Address assignment for digital modules
• Analogue modules è Tab. 48 Address assignment of analogue modules
• Technology modules è Tab. 49 Address assignment for technology modules
Festo — CPX-FB36 — 2019-07b 63

Technical appendix
6.2.1.1 Bus node
Bus node CPX-M-FB36 Module identi- Allocated address space

in operating mode fier1) Inputs Outputs
Remote I/O
Without diagnostics mode FB-36-RIO... - -
With status bits FB-36-RIO... 1x 16 Bit2) -
with I/O diagnostics interface FB-36-RIO... 1x 16 bits 1x 16 bits
Remote Controller
FB-36-RC... 8x 8 bit … 8x 8 bit …
64x 8 bit3) 64x 8 bit3)
1) In the operator unit or in the hardware configuration of the programming software.
2) Diagnostics mode status bits assigned 2 bytes of address space (8 bits remain unused).
3) depending on the setting of DIL switch 2 and the revision of the bus node
Tab. 46 Address assignment of bus nodes
6.2.1.2 Digital modules
Module designation Module identi- Allocated address space

fier1) Inputs Outputs
Input module
CPX-4DE 4DI 4x 1 bit2) -
CPX-4DE 8DI 8x 1 bits -
CPX-8NDE (n-switching) 8NDI 8x 1 bits -
CPX-8DE-D (with channel diagnostics) 8DI-D 8x 1 bits -
CPX-16DE 16DI 16x 1 bits -
CPX-M-16DE-D (with channel diagnostics) 16DI-D 16x 1 bits -
CPX-L-16DE-16-KL-… (with terminal strip) L-16DI-PI 16x 1 bits -
CPX-P-8DE-N P8-DI-N 2x 8 bits 1x 8 bits
CPX-P-8DE-N-X P8-DI-N-X 10x 8 bits 2x 8 bits
CPX-P-8DE-N-IS (intrinsically safe inputs) P8-DI-N-IS 2x 8 bits 1x 8 bits
CPX-P-8DE-N-IS-X (intrinsically safe inputs) P8-DI-N-IS-X 10x 8 bits 2x 8 bits
Output module
CPX-4DO 4DO - 4x 1 bits
CPX-8DO 8DO - 8x 1 bits
CPX-8DO-H (high current) 8DO-H - 8x 1 bits
64 Festo — CPX-FB36 — 2019-07b

Technical appendix

Input/output module
CPX-8DI-8DO 8DI/8DO 8x 1 bits 8x 1 bits
CPX-L-8DI-8DO-16-KL- … (with terminal strip) L-8DI8DO-PI 8x 1 bits 8x 1 bits
Electronics module
VMPA1-FB-EMS-8 for pneumatic module MPA1 MPA1S - 8x 1 bit3)
(1 … 8 valves)
VMPA2-FB-EMS-4 for pneumatic module MPA2 MPA2S - 8x 1 bit4)
(1 … 4 valves)
Electronics module (electrically isolated)
VMPA1-FB-EMG-8 for pneumatic module MPA1 MPA1G - 8x 1 bits
(1 … 8 valves)
VMPA2-FB-EMG-4 for pneumatic module MPA2 MPA2G - 8x 1 bits
(1 … 4 valves)
Electrical module with diagnostic function
VMPA1-FB-EMS-D2-8 for pneumatic module MPA1S-D - 8x 1 bits
MPA1 (1 … 8 valves)
VMPA2-FB-EMS-D2-4 for pneumatic module MPA2S-D - 8x 1 bits
Electrical module with diagnostic function (electrically isolated)
VMPA1-FB-EMG-D2-8 for pneumatic module MPA1G-D - 8x 1 bits
VMPA2-FB-EMG-D2-4 for pneumatic module MPA2G-D - 8x 1 bits
Electrical manifold module VMPAL-EVAP-10-... (for pneumatic module MPA-L)
VMPAL-EVAP-10-1 (1 valve, 1 coil) MPAL - 1 bit
VMPAL-EVAP-10-2 (1 valve, 2 coils) MPAL - 2 bit
VMPAL-EVAP-10-1-4 (4 valves, 4 coils) MPAL - 4 bit
VMPAL-EVAP-10-2-8 (4 valves, 8 coils) MPAL - 8 bit
End plate (pneumatic interface) VMPA…
VMPA-FB-EPL-… for valve terminal MPA-S - - -
VMPAF-FB-EPL-… for valve terminal MPA-F - - -
VMPAL-FB-EPL-… for valve terminal MPA-L
Festo — CPX-FB36 — 2019-07b 65

Technical appendix

1 … 4 valve coils - - 8x 1 bits

Pneumatic interface
VABA-... for valve terminal VTSA-/VTSA-F with VTSA or
setting:5) Type44/456)
1 … 8 valve coils - 8x 1 bits
2) Digital 4x modules (CPX-4DE and CPX-4DA) always occupy 8 inputs or 8 outputs.
3) VMPA1 modules always occupy 8 outputs regardless of the number of valves attached.
4) VMPA2 modules always occupy 8 outputs although only 4 bits are used.
5) Setting via DIL switch of the pneumatic interface (pneumatic interface).
6) depending on the version of the operator unit
Tab. 47 Address assignment for digital modules
Additional information:
• The address assignment in the CPX digital I/O modules can be found in the CPX-EA-... and
CPX-4AE-4AA-H descriptions (analogue I/O modules with HART communication).
• Information on CPX I/O modules with intrinsically safe inputs can be found in the description CPX-
P-EA-...
• Information on pneumatic interfaces and pneumatic modules can be found in the corresponding
descriptions of pneumatics.
• From the technical point of view, the individual pneumatic modules each represent an electric
module for controlling the attached valves.
• An overview of the “Descriptions of the CPX terminal” documentation can be found in the CPX sys-
tem description (CPX-SYS).
6.2.1.3 Analogue modules

Pressure sensor VMPA-FB-PS-... MPA-P 1x 16 bits -
66 Festo — CPX-FB36 — 2019-07b

Technical appendix

Proportional pressure regulator VPPM-...TA- VPPM 1x 16 bits 1x 16 bits

L-1-F...
Analogue module
CPX-2AE-U-I 2AI 2x 16 bits -
CPX-4AE-U-I 4AI 4x 16 bits -
CPX-4AE-I 4AI-I 4x 16 bits -
CPX-4AE-T (temperature module for RTD sensors) 4AI-T 2x 16 bits -
or
4x 16 bit2)
CPX-4AE-TC (temperature module for TC sensors) 4AI-TC 4x 16 bits -
CPX-4AE-P-D10 (pressure sensor module 0 … 10 4AI-P-D10 4x 16 bits -
bar)
CPX-4AE-P-B2 (pressure sensor module -1 … 1 4AI-P-B2 4x 16 bits -
bar)
CPX-2AA-U-I 2AA - 2x 16 bits
Analogue module CPX-4AE-4AA-H (with HART communication, HART variables in process image3)
4AI (HART) + 4 HART variables 4AI-H 4HV 12x 16 bits -
3AI, 1AO (HART) + 4 HARTvariables 3AI1AO-H 4HV 11x 16 bits 1x 16 bits
4AO (HART) + 4 HART variables 4AO-H 4HV 8x 16 bits 4x 16 bits
Analogue module CPX-4AE-4AA-H (with HART communication)3)
4AI (HART) 4AI-H 4x 16 bits -
3AI, 1AO (HART) 3AI1AO-H 3x 16 bits 1x 16 bits
4AO (HART) 4AO-H - 4x 16 bits
2) depending on the configuration
3) HART = Highway Addressable Remote Transducer)
Tab. 48 Address assignment of analogue modules
Festo — CPX-FB36 — 2019-07b 67

Technical appendix
The address assignment in the CPX analogue I/O modules can be found in the CPX-EA-... and
CPX-4AE-4AA-H descriptions (analogue I/O modules with HART communication).
6.2.1.4 Technology modules

Electrical interface connection CPX-CP-4-FB (CP CPI maximum maximum

interface) 16x 8 bit2) 16x 8 bits2)
Axis controller CPX-CMAX-C1-1 CMAX-C1-1 8x 8 bits 8x 8 bits
Control block CPX-CMXX (multi-axis interface) CMXX 8x 16 bits 8x 16 bits
End-position controller CPX-CMPX-C-1-H1 CMPX-C-1 6x 8 bits 6x 8 bits
Control block CPX-CM-HPP (FHPP interface) CM-HPP 32x 8 bits 32x 8 bits
Measuring module CPX-CMIX-M1-1 CMIX 3x 16 bits 3x 16 bits
Input/output module CPX-2ZE2DA (counter mod- 2CI2DO 3x 32 bits 3x 32 bits
ule)
Control block CPX-CEC (CODESYS embedded CEC 16x 8 bits 16x 8 bits
Controller)
Control block CPX-FEC (front-end controller) FEC 8x 8 bits 8x 8 bits
Electrical interface CPX-CTEL-4-M12-5POL CTEL
with setting
0E/0A - -
0E/8A - 8x 8 bits
0E/16A - 16x 8 bits
0E/24A - 24x 8 bits
0E/32A - 32x 8 bits
8E/0A 8x 8 bits -
16E/0A 16x 8 bits -
24E/0A 24x 8 bits -
32E/0A 32x 8 bits -
8E/8A 8x 8 bits 8x 8 bits
68 Festo — CPX-FB36 — 2019-07b

Technical appendix

Electrical interface CPX-CTEL-2-M12-5POL-LK CTEL-2-LK

with setting I-Port LK Master

2) Maximum assigned address space depends on the string allocation.
Tab. 49 Address assignment for technology modules
Details on the technology modules can be found in the corresponding descriptions è CPX-...
6.2.2 Addressing
6.2.2.1 Basic rules for addressing

– The address assignment of the inputs does not depend on the address assignment of the outputs.
– Counting from left to right, addressing byte by byte:
Modules with fewer than 8 bits occupy 8 bits of address space, but do not make full use of it.
– The bus node counts as a module with 0 inputs and 0 outputs when the status bits and the I/O
diagnostic interface are deactivated.
– The inputs/outputs of different module types are occupied separately from one other.
The sequence in the following table applies:
Sequence of addressing Description
1. I/O diagnostics interface The I/O diagnostic interface can be activated via the
DIL switch. If it is activated, it will occupy the first 16
inputs and outputs in the address range.
Depending on the setting, this address range can also
be occupied by status
bitsè Tab. 6 Setting diagnostic mode or data field
size.
2. Analogue modules Modules with analogue inputs/outputs
3. Technology modules e.g. CP interface, control block CPX-CEC or CPX-FEC
4. Digital modules Modules with digital I/O
Tab. 50 Sequence of addressing
Festo — CPX-FB36 — 2019-07b 69

Technical appendix
6.2.2.2 Data formats

In the "Studio 5000" software the inputs and outputs of the bus node are configured in the SINT or
INT formats.
Using the SINT format
If the SINT format is used, the data length of the Assembly Instances corresponds to the precise byte
of the current CPX terminal configuration.
The following Assembly instances are used for the SINT format.
– Inputs: Assembly instance 101
– Outputs: Assembly instance 100
Using the INT format
If the INT format is to be used, then the size of the process data must be a multiple of 16 bits.
If the total size of process data for the CPX terminal is not a multiple of 16 bits, the process data will
be rounded to the nearest 16-bit limit at the end with dummy I/Os.
Depending on the configuration of the CPX terminal, two CPX modules share a 16 bit-Tag in the "Stu-
dio 5000" software.
The following Assembly instances are used for the INT format:
– Inputs: Assembly instance 111
– Outputs: Assembly instance 110
NOTICE!
• Ensure that the outputs (100 and 110) are not accessed simultaneously on the Assembly
instances.
70 Festo — CPX-FB36 — 2019-07b

Technical appendix
6.2.2.3 Examples of addressing

Example 1: CPX terminal with MPA pneumatics
The following diagram shows as an example a CPX terminal with MPA pneumatics and the following
setting:
– Status bits and I/O diagnostics interface deactivated
1 Bus node CPX-M-FB36 3 MPA1 pneumatic modules (8 DO)

2 MPA: pneumatic interface 4 MPA2 pneumatic modules (4 DO)
Fig. 23 Example 1 – CPX terminal with MPA pneumatics
The following table shows the address assignment for the CPX terminal shown in example 1:
Module Module type I address O address

number
0 Bus node CPX-M-FB36 - -

1 Digital input module CPX-8DI E0 … E7 -
2 Digital output module CPX-4DO - A0 … A71)
3 Pneumatic module MPA1 (8 DO) - A8 … A15
4 Pneumatic module MPA1 (8 DO) - A16 … A23
5 Pneumatic module MPA2 (4DA) - A24 … A311)
6 Pneumatic module MPA2 (4DA) - A32 … A391)
1) 8 bits occupied, 4 bits used.
Tab. 51 Address assignment example 1
Festo — CPX-FB36 — 2019-07b 71

Technical appendix
Example 2: CPX terminal with electrical interface

The following graphic shows a CPX terminal with electrical interface and the following setting:
– Status bits and I/O diagnostics interface deactivated
1 Bus node CPX-M-FB36 4 Sensor

2 CPV valve terminal (16 DO) on string 1 of the 5 Cylinder
electrical interface 6 CP output module (16 DO) on string 4 of the
3 CP input module (16 DI) electrical interface
Fig. 24 Example 2 – CPX terminal with electrical interface (CP interface)
The following table shows the address assignment for the CPX terminal shown in Example 2:

number
0 Bus node CPX-M-FB36 - -

1 Digital input module CPX-8DI I32 … I39 -
2 Digital output module CPX-4DO - I128 … I1351)
3 Electrical interface (CP interface) CPX-CP-4-FB I0 … I31 O0 … O127
(4 bytes I, 16 bytes O)
72 Festo — CPX-FB36 — 2019-07b

Technical appendix

number
4 Digital input/output module CPX-8DI-8DO I40 … I47 O136 … O143

5 Pneumatic module MPA1 (8 DO) - O144 … O151
6 Pneumatic module MPA1 (8 DO) - O152 … O159
1) 8 bits occupied, 4 bits used
Festo — CPX-FB36 — 2019-07b 73

Technical appendix
Example 3: CPX terminal with analogue module and VTSA pneumatics

The address assignment for this CPX terminal can be found in the following table
è Tab. 53 Address assignment example 3. The settings are:
– Status bits activated
– I/O diagnostic interface deactivated
– Pneumatic interface set with DIL switch to 1 … 8 solenoid coils
1 Bus node CPX-FB36 (status bits activated) 3 VTSA pneumatics

2 Pneumatic interface VABA set with DIL
switch to 1 ... 8 solenoid coils
Fig. 25 Example 3 – CPX terminal with analogue module and VTSA pneumatics

number
0 Bus node CPX-FB36 (status bits activated) I0 … I151) -

5 Analogue output module CPX-2AA - O0 … O31
6 Pneumatic interface VABA set with DIL switch to - O48 … O55
1 … 8 solenoid coils
6.2.3 Address assignment after extension/conversion

A special feature of the CPX terminal is its flexibility. If the requirements of the machine are changed,
the equipment of the CPX terminal can also be changed.
74 Festo — CPX-FB36 — 2019-07b

Technical appendix
CAUTION!
If the CPX terminal is extended or converted at a later stage, input/output addresses may be shifted.
This applies in the following cases:
• Additional modules are inserted between existing modules.
• Existing modules are removed or replaced by other modules with fewer or more input/output
addresses.
• Interlinking blocks (VTSA) or pneumatic connection blocks (MPA-L) for monostable valves are
replaced by interlinking blocks/connection blocks for bistable valves – or vice versa (è Pneumat-
ics description).
• Additional interlinking blocks (VTSA) or connection blocks (MPA-L) are inserted between existing
ones.
• Status bits or the I/O diagnostics interface are activated/deactivated.
Addressing example 3 after extension/conversion

The following diagram shows the effects of changes on the address assignment based on addressing
example 3 (è Fig.25).
The following has been changed:
– The status bits were deactivated.
– The digital input module CPX-8DI (module no. 1) has been replaced by a digital input module
CPX-16DI.
– The pneumatic interface VABA has been set to 1 … 16 solenoid coils in order to reserve addresses
for an extension to the pneumatics.
1 Changed: status bits deactivated 3 Changed: pneumatic interface (pneumatic

2 Changed: digital input module CPX-8DI interface) VABA now set to 1 ... 16 valve coils
replaced by digital input module CPX-16DI via DIL switch
Fig. 26 Addressing example 3 after extension/conversion
Festo — CPX-FB36 — 2019-07b 75

Technical appendix
Module Module I address O address

number
0 Bus node CPX-FB36 (status bits deactivated) - -

5 Analogue output module CPX-2AA - O0 … O31
6 Pneumatic interface VABA set with DIL switch to - O48 … O63
1 … 16 solenoid coils
bold = changes
Tab. 54 Addressing example 3 after extension/conversion
6.3 EtherNet/IP-Objects of the CPX-FB36

6.3.1 Overview of EtherNet/IP objects
This chapter describes the representation of the CPX terminal within the EtherNet/IP object model.
Some information is in English so that the original terms of the EtherNet/IP specification can be used
unambiguously.
"EtherNet/IP Class Services"
The CPX terminal 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. 55 Class Services and Instance Services
76 Festo — CPX-FB36 — 2019-07b

Technical appendix
EtherNet/IP object classes

The following objects are supported:
Object class Instances Name Comments

(dec.)
1d 1 Identity Object General CIP objects

2d 1 Message Router Object
4d 100 … 102, Assembly Object
110, 111
6d 1 … 10 Connection Manager Object
244d 1 Port Object
245d 1 TCP/IP Interface Object EtherNet/IP-specific
71d 1 Device Level Ring Object objects
72d 1 QoS Object

132d 1 Global System Object CPX-specific objects for
133d 1 Status and Diagnosis Object parameterisation and dia-
gnostics
134d 1 … 40 Diagnosis Trace Object
135d 1 Diagnosis Trace Status Object
199d 1 Configuration Array Object
108d … 111d, 1 … 48 Force Parameter
116d … 119d,
124d … 127d
112d, 113d, 1 … 48 Fail safe Parameter
120d, 121d,
128d, 129d
114d … 115d 1 … 48 Idle Parameter CPX-specific objects for
122d, 123d parameterisation
130d, 131d
101d 1 … 48 Generic Parameter Object
102d 1 … 48 Discrete Input Object CPX-specific objects for
104d 1 … 48 Analog Input Object parameterisation of inputs
and outputs
105d 1 … 48 Analog Output Object
106d 1 … 48 Function Input Object
107d 1 … 48 Function Output Object
Festo — CPX-FB36 — 2019-07b 77

Technical appendix

(dec.)
108d 1 … 48 Discrete Input Force State Object CPX-specific objects for

109d 1 … 48 Discrete Input Force Mode Object the parameterisation of
Force, Fail safe and Idle
110d 1 … 48 Discrete Output Force State Object
Mode
111d 1 … 48 Discrete Output Force Mode Object
112d 1 … 48 Discrete Output Fail safe State Object
113d 1 … 48 Discrete Output Fail safe Mode Object
114d 1 … 48 Discrete Output Idle State Object
115d 1 … 48 Discrete Output Idle Mode Object
116d 1 … 48 Analog Input Force State Object CPX-specific objects for
117d 1 … 48 Analog Input Force Mode Object parameterisation of Force,
Fail safe and Idle mode
118d 1 … 48 Analog Output Force State Object
119d 1 … 48 Analog Output Force Mode Object
120d 1 … 48 Analog Output Fail safe State Object
121d 1 … 48 Analog Output Fail safe Mode Object
122d 1 … 48 Analog Output Idle State Object
123d 1 … 48 Analog Output Idle Mode Object
124d 1 … 48 Function Input Force State Object
125d 1 … 48 Function Input Force Mode Object
126d 1 … 48 Function Output Force State Object
127d 1 … 48 Function Output Force Mode Object
128d 1 … 48 Function Output Fail safe State Object
129d 1 … 48 Function Output Fail safe Mode Object
130d 1 … 48 Function Output Idle State Object
131d 1 … 48 Function Output Idle Mode Object
Tab. 56 Overview of EtherNet/IP objects

(dec.)
136d 1 Slave Size Object CPX-specific object

Tab. 57 Special EtherNet/IP object for operating mode Remote Controller
78 Festo — CPX-FB36 — 2019-07b

Technical appendix
Counting mode
The following applies to module-oriented objects:
– Instance number = module number + 1
Explanation:
– The counting of the modules starts with 0 at the bus node.
– The counting of instances starts with 1 at the bus node.
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.
The description and mode of operation of the individual parameters and data as well as fundamentals
on parameterisation can be found in the CPX system description (CPX-SYS).
6.3.2 Objects for network settings
6.3.2.1 "Device Level Ring Object"

Object class: 71d
Instances: 1
Attr. No. Access Description Type
1 Get Current Network Topology Mode USINT

0: Linear
1: Ring
2 Get Current Status of Network USINT
0: Normal
1: Ring fault
2: Unexpected loop detected
3: Partial network fault
4: Rapid fault / restore cycle
10 Get Active Supervisor Address STRUCT of
– Supervisor IP address UDINT
– Supervisor MAC address ARRAY of 6
USINT
12 Get Capability Flags DWORD
Bit 0:
Announce-based ring node1)
Bit 1: Beacon-based ring node1)
Bit 2 … 4: Reserved, shall be set to zero
Bit 5: Supervisor capable
Bit 6 … 31: Reserved, shall be set to zero
Bits 0 and 1 are mutually exclusive
1) è EtherNet/IP specification, chapter 9.5.4
Tab. 58 Network settings with Device-Level-Ring object
Festo — CPX-FB36 — 2019-07b 79

Technical appendix
6.3.2.2 "QoS Object"

Object class: 72d
Instances: 1
The 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 802.1Q Tag Enable USINT

Enables or disables sending 802.1Q frames on
CIP and IEEE 1588 messages
Default = 0
4 Set DSCP Urgent1) USINT
Default = 55
5 Set DSCP Scheduled1) USINT
Default = 47
6 Set DSCP High1) USINT
Default = 43
7 Set DSCP Low USINT
Default = 31
8 Set DSCP Explicit USINT
Default = 27
1) These attributes describe the IP header priority of various EtherNet/IP frames: Urgent = CIP Motion; Scheduled = CIP Safety;
High = I/O
Tab. 59 Network settings with QoS object
6.3.2.3 "TCP/IP Interface Object"

Object class: 245d
Instances: 1
The TCP/IP-Interface object is used to configure the network settings of a device.
1 Get Status (Interface Status) DWORD

2 Get Configuration Capability DWORD
Bit 5: hardware configurable
Bit 6: interface configuration change requires
reset
Bit 7: ACD capable
3 Get/Set Configuration Control DWORD
80 Festo — CPX-FB36 — 2019-07b

Technical appendix
4 Get Physical Link Object STRUCT of

– Path Size UINT +
– Path Padded
EPATH
5 Get/Set Interface Configuration STRUCT of
– Interface Configuration UDINT
– Network Mask UDINT
– Gateway Addres UDINT
– Name Server UDINT
– Name Server 2 UDINT
– Domain Name STRING
6 Get/Set Host Name STRING
8 Get/Set TTL Value USINT
for EtherNet/IP Multicast Packets
9 Get/Set IP Multicast Address Configuration STRUCT of
– Alloc Control
– Reserved USINT
– Num Mcast USINT
– Mcast Start Addr UINT
UDINT
10 Set Select ACD BOOL
0: Disable
1: Enable (default)
11 Get/Set Last Conflict Detected: STRUCT of
– ACD activity USINT
– Remote MAC ARRAY of 6
USINT
– Address Resolution Protocol Protocol Data ARRAY of 28
Unit (ARP PDU) USINT
12 Set QuickConnect BOOL
0: Disable (default)
1: Enable
13 Get/Set Encapsulation Inactivity Timeout UINT
0: Disable
1 … 3600: Timeout in seconds
16 Get Active TCP Connection UINT
17 Get Non-CIP Encapsulation Messages per Second UDINT
Tab. 60 Network settings with TCP/IP Interface object
Festo — CPX-FB36 — 2019-07b 81

Technical appendix
6.3.2.4 "Ethernet Link Object"

Object class: 246d
Instances: 2
One instance per Ethernet port:
– Instance 1 corresponds to Ethernet port X1
– Instance 2 corresponds to Ethernet port X2
– Instance 3 corresponds to the internal port
Via the Ethernet Link object extended settings for the Ethernet connection can be made
è 2.3.6 Extended network settings.
1 Get Interface Speed UDINT

2 Get Interface Status Flags DWORD
3 Get Physical MAC address ARRAY of 6
USINT
6 Get/Set Interface Control STRUCT of
– Control Bits WORD,
– Forced Interface Speed UINT
Tab. 61 Network settings with Ethernet-Link object
Examples:
To permanently set port X1 to 100 Mbit/s, full duplex (Auto-Negotiation off), the following values
must be written in attribute 6, instance 1: [0002h][0064h].
To activate Auto-Negotiation, the following values must be written in attribute 6, instance 1:
[0001h][0000h].
Further details can be found in the EtherNet/IP specification.
6.3.3 Objects for the I/O connection
6.3.3.1 "Assembly Object"

Object class: 4d
Instances: 6
The Assembly object bundles attributes of various objects to enable exchange of data with the objects
via one connection.
The following instances are created in the Assembly object:
Instance Description
100 Output data (Output Data)

101 Input data (Input Data)
102 Configuration data (Configuration Data)
103 Diagnostic data (Diagnosis Data)
82 Festo — CPX-FB36 — 2019-07b

Technical appendix
Instance Description
110 Output data in the INT format (Output Data with Padding)
111 Input data in the INT format (Input Data with Padding)
254 HeartBeat
255 ListenOnly
Tab. 62 Instances for Assembly object
Mode of operation Remote I/O
Each data area begins at the least significant bit (Least Significant Bit, LSB) of a word.
Instance 101: Input
Within the instance "Input" of the Assembly object, all inputs of the CPX system are transmitted cyclic-
ally over the network by means of a communication connection.
The following sequence applies:
Sequence of transmission
1. I/O diagnostic interface, if active (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)
Tab. 63 Sequence of transmission for Instance 101
Instance 101 (Input) has the following member list in the Remote I/O operating mode:
Obj. Instances (= Attributes Entries in member list Type

module no. (channel)
+ 1)
102 1 … 48 1 … 64 Digital data BOOL

104 1 … 48 1 … 32 Analogue data WORD
106 1 … 48 1 … 64/ Technology module BYTE/
65 … 96 WORD
133 1 0/1 I/O diagnostic interface data, if active WORD
Tab. 64 Member list of instance 101 in the Remote I/O operating mode
Instance 100: Output
Within the "Output" instance in the Assembly object all outputs of the CPX system will be transmitted
over the network by one communication connection.
The following sequence applies:
Festo — CPX-FB36 — 2019-07b 83

Technical appendix
Sequence of transmission
1. I/O diagnostic interface/status byte, if active (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)
Tab. 65 Sequence of transmission for Instance 100
Instance 100 (Output) has the following member list in Remote I/O operating mode:
Obj. Instances Attributes Entries in member list Type

(= module (channel)
no. + 1)
103 1 … 48 1 … 64 Digital data BOOL

105 1 … 48 1 … 32 Analogue data WORD
107 1 … 48 1 … 64/ Technology module BYTE/
65 … 96 WORD
133 1 … 48 0/1 I/O diagnostic interface data, if active WORD
Tab. 66 Member list of instance 100 in operation mode Remote I/O
Instance 102: Configuration
Instance 102 (Configuration) has the following member list:
Obj. Number Entries in member list Type
199 1 Configuration-Array data ARRAY

Tab. 67 Instance 102 member list
The I/O objects 102 … 107 also have the following attributes:
Attribute Entries Type
100 Number of data of the module in BYTE

BYTE or WORD
101 Data type: BYTE
– D1h : BYTE
– D2h : WORD
102 All data values ARRAY
Tab. 68 Attributes of the I/O objects 102 … 107
84 Festo — CPX-FB36 — 2019-07b

Technical appendix
Instance 103: Diagnosis Data

Instance 103 (Diagnosis Data) consists of the following data:
Byte Description Type
0 ST status byte è 5.3 Diagnostics via status bits USINT

1 Number of the first module in which an error has occurred USINT
2 Channel USINT
3 Error number USINT
Tab. 69 Data of the instance 103
Operating mode Remote Controller
Each data area begins at the least significant bit (Least Significant Bit, LSB) of a word.
Instance 100: Output
Instance 100 (Output) has the following member list in Remote Controller operating mode:
Obj. Attributes Entries in member list Type
107 1 … 64/ Technology module BYTE/

65 … 96 WORD
Instance 101: Input
Instance 101 (Input) has the following member list:
Obj. Attributes Entries in member list Type
106 1 … 64/ Technology module BYTE/

65 … 96 WORD
Transmission through the communication types "Polled Communication" or "Change of State/Cyclic
Communication".
Instance 102: Configuration
Instance 102 (Configuration) must have the value "0" in the operating modeRemote Controller.
6.3.4 Objects for system data and diagnostics
6.3.4.1 "Identity Object"

Object class: 1d
Instances: 1
The Identity object contains the identification and general information about the bus node CPX-FB36.
Service code 5d:
Reset
– Parameter 0 emulates a Power Cycle
– Parameter 1 resets the device to factory settings and then emulates a Power Cycle.
Festo — CPX-FB36 — 2019-07b 85

Technical appendix
1 Get Vendor ID: 1Ah UINT

2 Get Device Type: 0Ch UINT
3 Get Product Code UINT
– Remote I/O36CAh
– Remote Controller36CBh
6 Get Revision STRUCT
5 Get Status WORD
Bit 0: Owned
Bit 1: Reserved, shall be 0
Bit 2: Configured
Bit 3: Reserved, shall be 0
Bit 4-7: Extended device status
Bit 8: Minor recoverable fault
Bit 9: Minor unrecoverable fault
Bit 10: Major recoverable fault
Bit 11: Major unrecoverable fault
Bit 12-15: Reserved, shall be 0
6 Get Serial Number UDINT
7 Get Product Name SHORT_S
– CPX-FB36 Remote-I/O TRING
– CPX-FB36 Remote Controller
14 Get/Set Semaphore STRUCT
100 Get Operating Mode BOOL
– Remote Controller: TRUE
– Remote I/O: FALSE
101 Get External Module Identifiers ARRAY
Tab. 72 Attributes of the Identity object
6.3.4.2 "Global System Object" for operating mode Remote I/O

Object class: 132d
Instances: 1
This object is only available in the operating mode Remote I/O.
86 Festo — CPX-FB36 — 2019-07b

Technical appendix
Attr. Access Description Type Function no.

No.
1 Get CPX operating mode (Bit 0 … 3) BYTE 0 (bit 0 … 3)

0: Remote I/Owithout FEC or CEC
1: Remote I/Owith FEC or CEC
2: Remote Controllerwithout bus node
3: Remote Controllerwith bus node
CPX expansion (bit 4) 0 (bit 4)
Specifies whether the current CPX expansion cor-
responds to the saved CPX expansion.
0: equal
1: unequal
Operator unit (bit 5) 0 (bit 5)
Specifies whether or not an operator unit is con-
nected.
0: operator unit not connected
1: operator unit connected
Force Mode (bit 6) 0 (bit 6)
Specifies whether Force is blocked or enabled.
0: blocked
1: enabled
Bit 7: reserved 0 (bit 7)
2 Get Fail safe Mode BYTE 1 (bit 0, 1)
Indicates whether Fail safe Mode is active or
inactive.
0: inactive
1: active
System Idle Mode 1 (bit 2, 3)
Indicates whether Idle Mode is active or inactive.
0: inactive
1: active
3 Get Monitoring CPX terminal (bit 0 … 7) BYTE 2 (bit 0 … 7)
Specifies whether the monitoring of short cir-
cuit/overload and undervoltage is active or inact-
ive.
Bit 0: monitoring KZS (short circuit/overload
sensor supply)
Bit 1: monitoring KZA (short circuit/overload out-
puts)
Bit 2: monitoring UOUT (undervoltage outputs)
Festo — CPX-FB36 — 2019-07b 87

Technical appendix

No.
Bit 3: monitoring UVAL (undervoltage of valves)

Bit 4: monitoring KZV (short circuit valves)
Bit 5 … 7: reserved
0: inactive
1: active
4 Get Number of input bytes (Rx Size) BYTE -
Specifies the number of input bytes of the CPX
terminal.
5 Get Number of output bytes (Tx Size) BYTE -
Specifies the number of output bytes of the CPX
terminal.
9 Get/Set Monitoring (bit 0 … 7) BYTE 4401 (bit
Bit 0: monitoring KZS (short circuit/overload 0 … 7)
sensor supply)
Bit 1: monitoring KZA (short circuit/overload out-
puts)
Bit 2: monitoring UOUT (undervoltage outputs)
Bit 3: monitoring UVAL (undervoltage of valves)
Bit 4: monitoring KZV (short circuit valves)
Bit 5 … 7: reserved
1 = active (default)
0: inactive
10 Get/Set Fail safe Mode BYTE 4402 (bit 0, 1)
0: reset all outputs (default)
1: retain signal status (Hold last state)
2: assume Fail safe Mode
11 Get/Set Force Mode BYTE 4402 (bit 2, 3)
0: blocked
1: enabled
12 Get/Set System Idle Mode BYTE 4402 (bit 4, 5)
0: reset all outputs (default)
1: hold last state (retain signal status)
2: assume idle mode
13 Get/Set System start BYTE 4402 (bit 6)
0: system start with standard parameters (factory
setting) and current CPX expansion; external
parameterisation possible (presetting)
88 Festo — CPX-FB36 — 2019-07b

Technical appendix

No.
1: system start with saved parameters and saved

CPX expansion; parameters and CPX expansion
are saved retentively; external parameterisation
is blocked; the "Modify" LED on the bus node is
on
Tab. 73 Attributes of the system object for Remote I/O operating mode
6.3.4.3 "Status and Diagnosis Object"

Object class: 133d
Instances: 1
The status bits and the I/O diagnostic interface are mapped here.

No.
1 Get Status bits (8 bit) BYTE 1936

Source of error:
Bit 0: valve
Bit 1: output
Bit 2: input
Bit 3: analogue/technology module
Type of error:
Bit 4: undervoltage
Bit 5: short circuit/overload
Bit 6: wire break
Bit 7: other error
2 Get Number of the first module in which an error BYTE 1937
has occurred
3 Get Diagnostic status BYTE
4 Get Error number BYTE 1938
5 Get/Set Address of I/O diagnostic interface WORD
16 output bits (order data) of the I/O dia-
gnostic interface
6 Get Data for I/O diagnostic interface WORD
16 input bits (response data) of the I/O dia-
gnostic interface
Tab. 74 Attributes of the status and diagnostics object
6.3.4.4 "Diagnosis Trace Object"

Object class: 134d
Festo — CPX-FB36 — 2019-07b 89

Technical appendix
Instances: 1 … 40
An instance is created for every diagnostic entry.
Attr. Access Designation Description Type Function no.

No. 3488 + n1)
1 Get Mark first entry after Power BYTE n = 10 × d + 4

On Returns 1 if it is the first (Bit 7)
entry after a Power ON.
2 Get Days Number of days2) BYTE n = 10 × d + 0
3 Get Hours Number of hours2) BYTE n = 10 × d + 1
4 Get Minutes Number of minutes2) BYTE n = 10 × d + 2
5 Get Seconds Number of seconds2) BYTE n = 10 × d + 3
6 Get Milliseconds Number of 10 ms2) BYTE n = 10 × d + 4
(Bit 0 … 6)
7 Get Module code3) Module code of the module BYTE n = 10 × d + 5
that reported the error
8 Get Module num- Module position of the mod- BYTE n = 10 × d + 6
ber ule that reported the error; (Bit 6, 7)
63 = error not module-
related
9 Get Channel num- Number of the first faulty BYTE n = 10 × d + 7
ber3) channel (Bit 0 … 5)
10 Get Error number Possible fault messages BYTE n = 10 × d + 8
è CPX system description
11 Get Subsequent Number of subsequent BYTE n = 10 × d + 9

channels channels with the same
error
1) d (diagnostic event) = 0 … 39; current diagnostic event = 0;
2) measured from the moment the power supply is switched on
3) It is the error number = 0, if the content is also 0. If the error number is between 128 … 199 (error class 3), the content is not relevant
(service required).
Tab. 75 Attributes of the Diagnosis Trace Object
6.3.4.5 "Diagnosis Trace Status Object"

Object class: 135d
Instances: 1
Attr. Access Name Type Function no.

No.
1 Get Number of trace entries in the diagnostic memory BYTE 3482

(Bit 0 … 7)
90 Festo — CPX-FB36 — 2019-07b

Technical appendix

No.
2 Get Status of diagnostic memory BYTE 3483

0: recording active (Bit 0, 1)
1: recording inactive
3 Get/Set Clear_trace1, access via EDS BYTE -
4 Get/Set Clear_trace2, access via explicit messaging; BYTE -
Confirmation of execution by reset (0) of the
attribute value
5 Get/Set Entries saved retentively with Power On BYTE 3480
0 = active (default) (Bit 0)
1: inactive
6 Get/Set Run/stop filter 1 BYTE 3480
0: stop after 40 entries (save the first 40 entries) (Bit 1)
1: overwrite old entries (save the last 40 entries),
(default)
7 Get/Set Run/stop filter 2 BYTE 3484
0: run/stop filter 2 inactive (default) (Bit 0 … 2)
1: record to defined FN
2: record to defined FN + MN
3: record to defined FN + MN + KN
4: record from defined FN
5: record from defined FN + MN
6: record from defined FN + MN + KN
7: reserved
8 Get/Set Error end filter BYTE 3484
0: record outgoing errors (end of error); (filter (Bit 3)
inactive, default)
1: do not record outgoing errors (end of error);
(filter active)
9 Get/Set Error number filter BYTE 3484
FN = error number (Bit 4, 5)
0: error number filter inactive (default)
1: record only defined FN
2: do not record defined FN
3: reserved
Festo — CPX-FB36 — 2019-07b 91

Technical appendix

No.
10 Get/Set Module/channel filter BYTE 3484

With this diagnostic memory filter, the recording (Bit 6, 7)
of errors of other modules or channels can be
suppressed so that errors in a particular module
or channel can be analysed.
FN = error number
0: module/channel filter inactive (default)
1: record only FN of one module
2: record only FN of one channel
3: reserved
11 Get/Set Module number BYTE 3485
Module number for diagnostic memory filter (Bit 0 … 7)
12 Get/Set Channel number BYTE 3486
Channel number for diagnostic memory filter (Bit 0 … 7)
13 Get/Set Error number BYTE 3487
Error number for diagnostic memory filter (Bit 0 … 7)
Tab. 76 Attributes of the diagnostics trace status object
6.3.4.6 "Generic Parameter Object"

Object class: 101d
Instances: 1 … 48
The rule is: instance number = module number + 1
This object enables general access to the module parameters of all existing and future CPX modules.
– Use this object to parameterise modules with word or double word parameters.
Examples of modules with word or double-word parameters:
– Analogue input module CPX-E-4AE-I
– Temperature module CPX-4AE-T
– CPX-CP interface
Three parameter types can be accessed via the attributes of the general module parameter object:
– to byte parameters:
via attributes 1 … 64
– to word parameters:
using the attributes 65 … 127
– to double word parameters:
via the attributes 129 … 189
Procedure for parameterisation
1. Take the function number of the parameter to be set from the description for the module.
92 Festo — CPX-FB36 — 2019-07b

Technical appendix
2. Search for function number:

– byte/word parameters
è Tab. 77 General module parameter object: assignment of the attributes for word
parameters to the function numbers
– double word parameter
è Tab. 78 General module parameter object: assignment of the attributes for double-word
parameters to the function numbers
3. Read the corresponding attribute number from the relevant table.
Examples for parameterisation with the general module parameter object

è 6.3.5.2 Parameterisation with “Generic Parameter Object”
Attribute no. Parameter Function no.

Byte Word Word
1 65 - è Description of the module 4828 + m × 64 + 0

2 66 4828 + m × 64 + 1
3 67 4828 + m × 64 + 2
4 68 4828 + m × 64 + 3
5 69 4828 + m × 64 + 4
6 70 4828 + m × 64 + 5
7 71 4828 + m × 64 + 6
8 72 4828 + m × 64 + 7
9 73 4828 + m × 64 + 8
10 74 4828 + m × 64 + 9
11 75 4828 + m × 64 + 10
12 76 4828 + m × 64 + 11
… … 4828 + m × 64 + …
… … 4828 + m × 64 + …
… … 4828 + m × 64 + …
… 124 4828 + m × 64 + 59
61 125 4828 + m × 64 + 60
62 126 4828 + m × 64 + 61
63 127 4828 + m × 64 + 62
64 - 4828 + m × 64 + 63
Tab. 77 General module parameter object: assignment of the attributes for word parameters to the
function numbers
Festo — CPX-FB36 — 2019-07b 93

Technical appendix
Attribute no. Parameter Function no.

Byte DWor- DWor- DWor- DWor-
d d d d
1 129 - - - è Description of the 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. 78 General module parameter object: assignment of the attributes for double-word parameters to
the function numbers
6.3.4.7 "Force Parameter"

The first word receives the lowest instance number of the relevant object. The second word receives
the second lowest instance number, etc.
94 Festo — CPX-FB36 — 2019-07b

Technical appendix
Object Description
108 Force state digital inputs

109 Force mode digital inputs
110 Force state digital outputs
111 Force mode digital outputs
Tab. 79 Objects for force parameter of digital I/O modules
Object Description
116 Force state analogue inputs

117 Force mode analogue inputs
118 Force state analogue outputs
119 Force mode analogue outputs
Tab. 80 Objects for force parameter of analogue I/O modules
Object Description
124 Force state inputs technology module

125 Force mode inputs technology module
126 Force state outputs technology module
127 Force mode outputs technology module
Tab. 81 Objects for force parameter for technology modules
Structure of the objects for “Force mode”
Objects Force mode: 109d, 111d, 117d, 119d, 125d, 127d
è Tab. 79 Objects for force parameter of digital I/O modules …
è Tab. 81 Objects for force parameter for technology modules
Instances: 1 … 48
1 Get/Set Value for Force mode: BOOL

Channel 0:
0: force blocked
1: force enabled
2 Get/Set Channel 1: BOOL
0: force blocked
1: force enabled
… … … …
Festo — CPX-FB36 — 2019-07b 95

Technical appendix

0: force blocked
1: force enabled
100 Get Number of channels BYTE
101 Get All channels: values for Force mode ARRAY
Tab. 82 Basic Structure of the objects for Force mode
Structure of the objects for “Force state” for digital I/O modules
Objects Force state: 108d, 110d è Tab. 79 Objects for force parameter of digital I/O modules
Instances: 1 … 48
1 Get/Set Value for Force state: BOOL

Channel 0:
0: reset signal
1: set signal
0: reset signal
1: set signal
… … … …
0: reset signal
1: set signal
101 Get All channels: values for Force state ARRAY
Tab. 83 Structure of the objects for “Force state” for digital I/O modules
Structure of the Objects for “Force state” for analogue I/O modules
Objects Force state: 116d, 118d è Tab. 80 Objects for force parameter of analogue I/O modules
Instances: 1 … 48
1 Get/Set Channel 0: WORD

Value for Force
Value for Force
… … … …
96 Festo — CPX-FB36 — 2019-07b

Technical appendix

Value for Force
Tab. 84 Structure of the Objects for “Force state” for analogue I/O modules
Structure of the objects for “Force state” for technology modules
Objects Force state: 124d, 126d è Tab. 81 Objects for force parameter for technology modules
Instances: 1 … 48
1 Get/Set Channel 0: BYTE

Value for Force
Value for Force
… … … …
Value for Force
Value for Force
... ... ... ...
Value for Force
101 Get Data type: BYTE
– D1h : BYTE
– D2h : WORD
102 Get/Set All channels: values for Force state ARRAY
Tab. 85 Structure of the objects for Force state technology modules
6.3.4.8 Fail safe and Idle parameters

The first word receives the lowest instance number of the relevant object. The second word receives
the second lowest instance number, etc.
Object Description
112 Fail safe state digital outputs

113 Fail safe mode digital outputs
114 Idle state digital outputs
Festo — CPX-FB36 — 2019-07b 97

Technical appendix
Object Description
115 Idle mode digital outputs

Tab. 86 Objects for Fail safe and Idle parameters of digital output modules
Object Description
120 Fail safe state analogue outputs

121 Fail safe mode analogue outputs
122 Idle state analogue outputs
123 Idle mode analogue outputs
Tab. 87 Objects for Fail safe and Idle parameters of analogue output modules
Object Description
128 Fail safe state outputs technology module

129 Fail safe mode outputs technology module
130 Idle state outputs technology module
131 Idle mode outputs technology module
Tab. 88 Objects for the Fail safe and Idle parameters for technology modules
Structure of the objects for Fail safe mode and Idle mode
Objects "Fail safe mode": 113d, 121d, 129d
Objects "Idle mode": 115d, 123d, 131d
è Tab. 86 Objects for Fail safe and Idle parameters of digital output modules …
è Tab. 88 Objects for the Fail safe and Idle parameters for technology modules
Instances: 1 … 48

0: Hold last state
1: Fail safe/"Idle state"
0: Hold last state
… … … …
0: Hold last state
98 Festo — CPX-FB36 — 2019-07b

Technical appendix
101 Get All channels: values for Fail safe mode and Idle ARRAY
mode
Tab. 89 Structure of the objects for Fail safe mode and Idle mode
Structure of the objects for “Fail safe state” and “Idle state” for digital output modules
Object "Fail safe state": 112d
Object "Idle state": 114d
è Tab. 86 Objects for Fail safe and Idle parameters of digital output modules
Instances: 1 … 48

0: Hold last state
0: Hold last state
… … … …
0: Hold last state
101 Get All channels: values for Fail safe state and Idle ARRAY
state
Tab. 90 Structure of the objects for “Fail safe state” and “Idle state” for digital output modules
Structure of the objects for “Fail safe state” and “Idle state” for analogue output modules
è Tab. 87 Objects for Fail safe and Idle parameters of analogue output modules
Instances: 1 … 48

Value for Fail safe state and Idle state
… … … …
Festo — CPX-FB36 — 2019-07b 99

Technical appendix

Tab. 91 Structure of the objects for “Fail safe state” and “Idle state” for analogue output modules and
technology modules
Structure of the Objects for “Fail safe state” and “Idle state” for technology modules
è Tab. 88 Objects for the Fail safe and Idle parameters for technology modules
Instances: 1 … 48
1 Get/Set Channel 0: value for "Fail safe state" and "Idle BYTE
state"
state"
… … … …
state"
65 Get/Set Channel 0: value for "Fail safe state" and "Idle WORD
state"
... ... … …
96 Get/Set Channel 31: value for "Fail safe state" and "Idle WORD
state"
101 Get Data type: BYTE
– D1h : BYTE
– D2h : WORD
102 Get/Set All channels: values for Fail safe state and Idle ARRAY
state
Tab. 92 Structure of the objects for “Fail safe state” and “Idle state” for analogue output modules and
technology modules
6.3.4.9 "Configuration Array Object"
The Configuration Array Object is available only for revision statuses later than Rev. 1.2. Further
information about this object can be found at www.festo.com/sp.
Object class: 199d
100 Festo — CPX-FB36 — 2019-07b

Technical appendix
Attr. Access Description Type Function

No. no.
1 Get/Set Data field with all system and module parameters. ARRAY -
Tab. 93 "Configuration Array Object"
6.3.4.10 “Slave Size Object” for “Remote Controller” operating mode

Object class: 136d
Instances: 1
This object is only available in the Remote Controller operating mode.
The slave size object contains the number of I/O bytes for communication of the bus node CPX-FB36
with a control block (e.g. CPX-FEC). The setting is made via DIL switches on the bus node CPX-FB36
è Tab. 6 Setting diagnostic mode or data field size.
Attr. Access Description Type

No.
1 Get Number of input bytes for the Remote Controller operating SINT
mode
2 Get Number of output bytes for the Remote Controller operating SINT
mode
Tab. 94 “Slave Size Object” for “Remote Controller” operating mode
6.3.4.11 "Condition Counter Object"

Object class: 141d
Instances: 1
Attribute no. Access Name Type Description Value
Class Attributes
1 Get Revision UINT Revision of the 1
object
2 Get Max instances UINT Maximum 48
number of
instances of
the CIP object
3 Get Num instances UINT Number of ≤ 48
instances that
are currently
generated by
the CIP object
6 Get Max Class UINT 7
Attribute
Festo — CPX-FB36 — 2019-07b 101

Technical appendix
7 Get Max Instance UINT Channel of

Attribute Modules + 1
Instance Attributes
1 Get Channel count USINT
2 … + Channel Get/Set Condition UDINT
Count Counter of
Channel1)
1) Reset of the "Counter of Channel" counter: set value to 0.
Tab. 95 "Condition Counter Object"
6.3.4.12 "HART Access Object"

Object class: 861d
Instances: 1
Class Attributes
1 Get Revision UINT Revision of the 1
object
2 Get Max instances UINT Maximum 48
number of
instances of
the CIP object
3 Get Num instances UINT Number of ≤ 48
instances that
are currently
generated by
the CIP object
6 Get Max Class UINT 100
Attribute
7 Get Max Instance UINT Channel of
Attribute Modules + 1
100 Get/Set HART Status UINT 120
Polling Interval
in Seconds
Instance Attributes
No Instance Attributes
Tab. 96 "HART Access Object"
102 Festo — CPX-FB36 — 2019-07b

Technical appendix
"Read Additional Device Status"
Request Service Code Instance Attribute
Read Additional Device 0x4C Channel Module

Status Request1) (76d)
1) Repeat for all modules and channels: set the Channel instance to 0.
Tab. 97 Query (Request) "Read Additional Device Status"
Offset Field Description
Request not successful (Request failed)

0 Status 34: Running
Device handles requests, fur-
ther requests not possible
35: Dead
Device not connected or com-
munication not possible
1 Padding 0
Request successful (Request successful)
0 Status 0: Success
1 Number of Status Bytes 0 … 25 bytes
2 … 26 Additional Status Bytes Response data of HART com-
mand 48 ("CMD#48")1))
27 Padding 02)
1) Within instance 0 the offset bytes are filled with zeros if not in use.
2) This offset byte is only available if all 25 bytes are in use or the corresponding instance is set to zero.
Tab. 98 "Read Additional Device Status"
"Get HART Device Information"
Request Service Code Instance Attribute
Get HART Device 0x4D Channel Module

Information Request (77d)
Tab. 99 Query (Request) "Get HART Device Information"
Festo — CPX-FB36 — 2019-07b 103

Technical appendix
Offset Field Size Description
Request not successful (Request failed)

0 Status 1 byte 34: Running
Device handles
requests, further
requests not possible
35: Dead
Device not connected
or communication not
possible
1 Padding 1 byte 0
Request successful (Request successful)
0 Status 1 byte 0: Success
1 Manufacture ID 1 byte CMD#0, Byte 1
2 Device Type 1 byte CMD#0, Byte 2
3 HART preamble 1 byte CMD#0, Byte 3
4 HART Univ Cmd Code 1 byte CMD#0, Byte 4
5 HART Trans Spec Rev 1 byte CMD#0, Byte 5
6 Software Revision 1 byte CMD#0, Byte 6
7 Hardware Revision 1 byte CMD#0, Byte 7
8 HART flags 1 byte CMD#0, byte 8
9 Pad_1 for 32 bit align- 1 byte
ment
10 … 11 HART Manufacturer ID 16 bit CMD#0, byte 1, if HART
revision < 7
CMD#0, bytes 17 … 18
if HART revision ≥ 7
12 … 15 HART Device ID UINT CMD#0, Bytes 9 … 111)
Number1)
16 … 19 Day Size 8 4 bytes
20 … 27 Tag String 8 bytes unpacked ASCII CMD#13, Bytes 0 … 5
28 … 31 Descriptor size 4 bytes
32 … 47 Descriptor String 16 bytes unpacked CMD#13, Bytes 6 … 17
ASCII
48 Date Day 1 byte CMD#13, Byte 18
104 Festo — CPX-FB36 — 2019-07b

Technical appendix
49 Date Month 1 byte CMD#13, Byte 19

50 … 51 Date Year 2 bytes CMD#13, Byte 20
(+ 1900)
52 … 55 Final Assembly 4 bytes UDINT CMD#16, Bytes 0 … 21)
Number1)
56 … 59 message size 4 bytes
60 … 91 Message String 32 bytes unpacked CMD#12, Bytes 0 … 23
ASCII
92 PVCode 1 byte CMD#50, byte 02)
93 SVCode 1 byte CMD#50, Byte 12)
94 TVCode 1 byte CMD#50, Byte 22)
95 FVCode 1 byte CMD#50, Byte 32)
96 PV units 1 byte CMD#3, Byte 4
97 SVUnits 1 byte CMD#3, byte 93)
98 TVUnits 1 byte CMD#3, Byte 143)
99 FVUnits 1 byte CMD#3, Byte 193)
100 Transfer function 1 byte CMD#15, Byte 1
101 Range units 1 byte CMD#15, Byte 2
102 … 103 Expanded Device Type 2 bytes CMD#0, Byte 2, if
Code HART-Revision < 7
CMD#0, bytes 1 … 2, if
HART-revision ≥ 7
104 … 107 HART PV Lower Range 4 Bytes Floating Point CMD#15, bytes 3 … 6
Value
108 … 111 HART PV Upper Range 4 bytes – Floating Point CMD#15, bytes 7 … 10
Value
112 … 115 Damping Value 4 bytes – Floating Point CMD#15,
Value bytes 11 … 14
116 Write Protect Code 1 byte CMD#15, byte 15
117 Pad_2 for alignment 1 byte
Festo — CPX-FB36 — 2019-07b 105

Technical appendix
118 … 119 Private Label Mfg 16 bits (2 bytes) CMD#0, byte 1, if HART
revision < 7
CMD#0, bytes 19 … 20,
if HART revision ≥ 7
1) The data is displayed in Intel format: LSB in first position. In HART format the MSB is in first position.
2) "0xFF", if the command is not supported.
3) "0", if the stated devices ("Units") are not available.
Tab. 100 "Get HART Device Information"
"Pass Through Init"
Request Service Instance Attribute Data [0] Data [1] Data [2 … 2-

Code 56]
Pass 0x4E Channel Module HART com- HART data HART

Through Init (78d) mand size data [0 … 2-
Request 55]
Tab. 101 Query (Request) "Pass Through Init"
Offset Field Value Description
0 Status 32: Busy

Query queue full, fur-
ther queries not pos-
sible
33: Initiated
Queue request accep-
ted successfully, pro-
cessing follows
35: Dead
possible
1 HART command Response ("Echo") of
the HART command
(CMD…)
2 Handle 1 … 255 (1 byte) Data Handle used in
the queue request
3 Queue Space Remain- 1 byte Number of query
ing queues still available
Error Reason Code, if for this channel.
status = 35
106 Festo — CPX-FB36 — 2019-07b

Technical appendix
Diagnostic information
(Error Reason Code) if a
queue request is not
successful
(Status = 35)
Tab. 102 "Pass Through Init"
"Pass Through Query"
Request Service Code Instance Attributes Data[0]
Pass Through 0x4F Channel Module Data Handle that

Query Request (79d) was returned in
the Initiate
Request
Tab. 103 Query (Request) "Pass Through Query"
0 Status 0: Success
Queue request suc-
cessfully executed
34: Busy
Queue request still in
progress
35: Dead
possible
1 HART command Response ("Echo") of
the HART command
(CMD…)
2 HART CommStatus HART response status
regarding byte 1
3 HART FieldDeviceStatus HART response status
regarding byte 2
or
Error Reason Code, if
status = 35
Festo — CPX-FB36 — 2019-07b 107

Technical appendix
4 Data size 1 byte Number of data bytes

(data size) in the
response to the HART
command
5 … 257 Data Data bytes in the data
field of the response to
the HART command
Tab. 104 "Pass Through Query"
"Pass Through Error Reason Codes"
Code Description
0x81 No response from device

0x82 Invalid, too long Frame address
0x83 Invalid HART-Message check sum
0x84 HART command (CMD … ) not allowed
0x85 Invalid channel (Channel)
0x86 Channel (Channel) not enabled for HART
0x87 No device connected
0x89 Invalid size of the CIP Message (too small)
0x8A Invalid data Handle
0x8B Invalid delimiter/field separator (Delimiter)
0x8F Invalid data volume (too large)
Tab. 105 Pass Through Error Reason Codes
6.3.4.13 "ISDU Access Object"

Object class: 768d
Instances: 1
Attr. Access Description Type Function

No. no.
1 Get List with instance numbers of CBUS modules with ARRAY OF -

ISDU function (ISDU = Indexed Service Data Unit) SINT
Tab. 106 "ISDU Access Object"
The object also offers the following services:
108 Festo — CPX-FB36 — 2019-07b

Technical appendix
Request Service Instance1) Attribute2) Data [0 … 1] Data [2] Data [3 … n]

Code
Read 0x32 Channel CBUS mod- Index Subindex -

(50d) ule number
Write 0x33 Channel CBUS mod- Index Subindex Data to write
(51d) ule number
1) The instance can have the following values: 1= Port 1; 2 = Port 2
2) The attribute contains the CBUS module number starting with 0
Tab. 107 Services of the object “ISDU Access Object”
The answer for the services 0x32 and 0x33 is:
Data [0] Data [1 … n]
Response Status è Tab. 109 Response Status Data from ISDU

(only for service 0x32 = Read)
Tab. 108 Answer for the services 0x32 and 0x33
Response Status Description
0 Success
E1h Write data length too long
E2h Port unknown
E3h Device busy
E4h Write failed
E5h Read failed
E6h Read answer too long
E7h State unknown
E8h Port on master not support
E9h Port in invalid state
FFh Timeout
Tab. 109 Response Status
6.3.5 Examples
6.3.5.1 Forcing inputs

In this example, the Force mode of an analogue input module is parameterised.
Festo — CPX-FB36 — 2019-07b 109

Technical appendix
1 Parameterisation: module CPX-4AE-I,

Force mode setting for channel 2:
Object class 117
(è Tab. 80 Objects for force parameter of
analogue I/O modules),
Instance 3 (= module number + 1),
Attribute 3 (for channel 2
è Tab. 82 Basic Structure of the objects for
Force mode,
è Tab. 110 Example: set Force state for
module no. 2)
Fig. 27 Example of Forcing (sequence: see text)
1. Enable Force mode
Enable the Force mode for the CPX terminal with system object 132
è Tab. 56 Overview of EtherNet/IP objects,
è 6.3.4.2 "Global System Object" for operating mode Remote I/O:
System object: 132
Instance: 1
Attribute 11 (Force mode)
2. Define value for Force state for channel 2:
Objects Force state: 116
(è Tab. 84 Structure of the Objects for “Force state” for analogue I/O modules)
Instance: 3
Attr. No. Access Parameter Type
... ... ... ...

Value for Force
... ... ... ...
Tab. 110 Example: set Force state for module no. 2
110 Festo — CPX-FB36 — 2019-07b

Technical appendix
3. Define Force mode for channel

Objects Force state: 117 (è Tab. 82 Basic Structure of the objects for Force mode)
Instance: 3
Attr. No. Access Parameter Type
... ... ... ...

3 Get/Set Value for Force mode, channel 2: BOOL
0 = force blocked
1 = force enabled
... ... ... ...
Tab. 111 Example: set Force state for module no. 2
6.3.5.2 Parameterisation with “Generic Parameter Object”

In this example, a signal extension time with a digital input module and a lower limit value with an
analogue input module are parameterised.
1 Parameterisation module CPX-8DE: 2 Parameterisation module CPX-4AE-I:

Enable signal extension channel 5: Lower limit value of channel 2:
Object class 101 Object class 101
(è 6.3.4.6 "Generic Parameter Object"), (è 6.3.4.6 "Generic Parameter Object"),
Instance 1 (= module number), Instance 2 (= module number),
Attribute 7 Attribute 82
(è Tab. 112 Example: parameterisation of (è Tab. 113 Example: parameterisation of
signal extension for module no. 1) the lower limit value (module no. 2, channel
2))
Fig. 28 Examples for parameterisation with the general Module Parameter Object
The following tables show you how to determine the attributes for the parameterisation. The paramet-
ers of the relevant modules are entered in the tables.
Festo — CPX-FB36 — 2019-07b 111

Technical appendix
Information on the parameters can be found in the description for the relevant module.
Attribute no. Parameter (module no. 1 è Fig.28) Function no.

Byte Word Word
1 65 - Monitoring CPX module 4828 + m * 64 + 0

2 66 Bit 0: behaviour after short circuit/overload 4828 + m * 64 + 1
Bit 4, 5: input debounce time
Bit 6, 7: signal extension time
3 67 - 4828 + m * 64 + 2
4 68 - 4828 + m * 64 + 3
5 69 - 4828 + m * 64 + 4
6 70 - 4828 + m * 64 + 5
7 71 Signal extension channel x 4828 + m * 64 + 6
8 ... - 4828 + m * 64 + 7
Tab. 112 Example: parameterisation of signal extension for module no. 1
Attribute no. Parameter (module no. 2 è Fig.28) Function no.

Byte Word Word
1 65 - Monitoring CPX module 4828 + m * 64 + 0

2 66 Bit 0: behaviour after short circuit/overload 4828 + m * 64 + 1
... ... ... 4828 + m * 64 + ...
... ... ... 4828 + m * 64 + ...
15 80 Lower limit value of channel 1 4828 + m * 64 + 14
... ... ... 4828 + m * 64 + ...
Tab. 113 Example: parameterisation of the lower limit value (module no. 2, channel 2)
6.4 Modbus TCP-Objects of the CPX-FB36

6.4.1 Overview of Modbus TCP objects
This chapter describes the representation of the CPX terminal within the Modbus TCP object model.
Some information is in English so that the original terms of the protocol specification can be used
unambiguously.
112 Festo — CPX-FB36 — 2019-07b

Technical appendix
6.4.2 Commands and addresses

The table below shows the connection between the Modbus address and data or parameters of the
CPX terminal. The data are assigned to various groups.
Modbus command Func- Modbus address Meaning Remote- Group

tion I/O
code 16-bit
access
read 3 45357 … 45391 CPX status information read O

4x registers 45392 … 45647 Process data inputs read B
45648 … 45655 Diagnostic memory paramet- read C
45656 … 46055 ers read C
46100 Diagnostic memory data read O
Modbus connection timeout
write 6, 16 40001 … 40256 Process data outputs write D
4x registers 40257 … 40264 Diagnostic memory paramet- write I
46100 ers write O
Modbus connection timeout
read/write 23 45357 … 45391 CPX status information read O
4x registers 45392 … 45647 Process data inputs read B
45648 … 45655 Diagnostic memory paramet- read C
45656 … 46055 ers read C
40001 … 40256 Diagnostic memory data write D
40257 … 40264 Process data outputs write I
Diagnostic memory paramet-
ers
read device identi- 43 Objects Objects ID0, 1, 2, 3, 4, 5 read F
fication
Tab. 114 Overview of the Modbus function codes for the bus node CPX-FB36 in operating mode
Remote I/O
6.4.3 CPX status information (Group A)

The status information provides information on the configuration and the fault status of the CPX ter-
minal. It is in the Modbus address range 45367 … 45391.
Modbus CPX terminal configuration

address
Process data inputs

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
45367 Module 0 … 15
45368 Module 16 … 31
Festo — CPX-FB36 — 2019-07b 113

Technical appendix
Modbus CPX terminal configuration

address
45369 Module 32 … 47
Bit n = 0: module does not exist
Bit n = 1: module exists
Tab. 115 Configuration information on the modules of the CPX terminal
Modbus Fault detection

address
Process data inputs

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
45383 Module 0 … 15
45384 Module 16 … 31
45385 Module 32 … 47
Bit n = 0: no error
Bit n = 1: error in module n
Tab. 116 Detection of which module reports a fault
Modbus Status register

address
Process data inputs

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
45391 Bit 4 = 1: operator unit connected; 0: not connected
Bit 11 = 1: parameter write-protected; 0: no write protection
Bit 15 = 1: force active; 0: force inactive
Tab. 117 Further status information (extracts from the system data)
Modbus Modbus connection timeout

address
Monitoring of the Modbus connection in milliseconds [ms]

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
46100 0 = deactivated
Value range: 10 … 65535
Default setting: 10000 (10 s)
Tab. 118 Modbus connection timeout
114 Festo — CPX-FB36 — 2019-07b

Technical appendix
6.4.4 Process data (Group B and D)

The process image of the input data (Group B) and of the output data (Group D) is composed seam-
lessly of the data of the modules as mounted from left to right in the CPX terminal.
The Modbus addresses depend accordingly on the modules mounted on the CPX terminal. They are
arranged seamlessly in ascending order (n, n +1, n +2, ... ; n corresponds to the first Modbus address
of the module).
Examples of addressing è Fig.29
6.4.4.1 Bus node CPX-M-FB36
Modbus Bus node CPX-FB36 Remote I/O

address1)
Process data inputs Process data outputs

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n Result of access to the I/O diagnostic Access to the I/O diagnostic interface 2)
interface1)
n+1 Data from the system table (read access) Data for the system table
è Tab. 141 I/O diagnostics interface – è Tab. 140 I/O diagnostics interface –
read access write access2)
(write access )
n+2 Module diagnostic data -
è Tab. 139 Module diagnostic data
1) n corresponds to the first Modbus address of the module.

2) Structure of the I/O diagnostic interface
Tab. 119 Bus node CPX-FB36 Remote I/O
6.4.4.2 Electric modules
Modbus Digital input module (CPX-4DI)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n 0 Inputs -
Tab. 120 Digital input module (CPX-4DI)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
Festo — CPX-FB36 — 2019-07b 115

Technical appendix

address1)
n 0 Inputs -
Tab. 121 Digital input module (CPX-8DI)
Modbus Digital output module (CPX-4DO)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n x Echo x Outputs
outputs
Tab. 122 Digital output module (CPX-4DO)
Modbus Digital input/output module (CPX-8DI-8DO)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n 0 Inputs x Outputs
n+1 x Echo outputs -
Tab. 123 Digital input/output module (CPX-8DI-8DO)
Modbus Analogue input module (CPX-2OI)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n Analogue inputs channel 0 -
n+1 Analogue inputs channel 1 -
Tab. 124 Analogue input module (CPX-2OI)
116 Festo — CPX-FB36 — 2019-07b

Technical appendix
Modbus Analogue output module (CPX-2AO)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n Echo analogue outputs channel 0 Analogue outputs channel 0
n+1 Echo analogue outputs channel 1 Analogue outputs channel 1
Tab. 125 Analogue output module (CPX-2AO)
6.4.4.3 Pneumatic modules
Modbus MPA1 pneumatic module (1 … 8 valves)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n x Echo outputs x Outputs
Tab. 126 MPA1 pneumatic module
Modbus MPA2 pneumatic module (1 … 4 valves)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n x Echo x Outputs
outputs
Tab. 127 MPA2 pneumatic module
Modbus Pneumatic interface for CPA pneumatic set to 1 … 8 valves

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n x Echo outputs x Echo outputs
Festo — CPX-FB36 — 2019-07b 117

Technical appendix

address1)
n+1 Diagnostic data -

Tab. 128 Pneumatic interface for CPA pneumatic (1 ... 8 valves)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n Echo outputs Outputs

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n Echo outputs 0 … 15 Outputs 0 … 15
n+1 x Echo outputs x Outputs 16 … 22
16 … 22
Modbus Pneumatic interface for midi/maxi pneumatic set to 1 … 8 valves

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n x Echo outputs x Outputs
Tab. 131 Pneumatic interface for midi/maxi pneumatic (1 ... 8 valves)
118 Festo — CPX-FB36 — 2019-07b

Technical appendix

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n Echo outputs Outputs

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n Echo outputs 0 … 15 Outputs 0 … 15
16 … 24
Modbus Pneumatic interface for pneumatic Midi/Maxi set to 1 … 32 valves2)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n+1 Echo outputs 0 … 15 Outputs 0 … 15
16 … 26
2) Only 26 valves usable.
6.4.4.4 Electrical interface (CP interface) CPX-CP-4-FB

The electrical interface (CP interface) CPX-CP-4-FB has connections for 4 strings to each of which max-
imum 4 CP modules can be connected.
The last used string is decisive for the number of assigned bytes, even if numerically lower strings are
not assigned physically.
Festo — CPX-FB36 — 2019-07b 119

Technical appendix
Modbus Electrical interface (CP interface) CPX-CP-4-FB used string: 1 (line 1)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n Data byte 1 Data byte 0 Data byte 1 Data byte 0
n+1 Data byte 3 Data byte 2 Data byte 3 Data byte 2
n+2 Echo Echo -
Output data 1 Output data 0
n+3 Echo Echo -
Tab. 135 Electrical interface (CP interface) CPX-CP-4-FB - used string 1
Modbus Electrical interface (CP interface) CPX-CP-4-FB Used strings: 1, 2 (line 1 … 2)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n+3 Data byte 7 Data byte 6 Data byte 7
n+4 Echo Echo -
n+5 Echo Echo -
n+6 Echo Echo -
n+7 Echo Echo -
Tab. 136 Electrical interface (CP interface) CPX-CP-4-FB - used strings 1, 2
120 Festo — CPX-FB36 — 2019-07b

Technical appendix
Modbus Electrical interface (CP interface) CPX-CP-4-FB Used strings: 1, 2, 3 (line 1 … 3)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
n+6 Echo Echo -
n+7 Echo Echo -
n+8 Echo Echo -
n+9 Echo Echo -
n+10 Echo Echo -
n+11 Echo Echo -
Tab. 137 Electrical interface (CP interface) CPX-CP-4-FB - used strings 1, 2, 3
Modbus Electrical interface (CP interface) CPX-CP-4-FB Used strings 1, 2, 3, 4 (line 1 … 4)

address1)

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0
Festo — CPX-FB36 — 2019-07b 121

Technical appendix
Modbus Electrical interface (CP interface) CPX-CP-4-FB Used strings 1, 2, 3, 4 (line 1 … 4)

address1)

n+8 Echo Echo -
n+9 Echo output data 3 Echo output data 2 -
n+13 Echo output data Echo output data -
11 10
13 12
15 14
Tab. 138 Electrical interface (CP interface) CPX-CP-4-FB - used strings 1, 2, 3, 4
6.4.4.5 Structure of diagnostic data (diagnostic word)
Module diagnostic data
Input data
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0/1 0/1 Channel number (0 … 63) Error number (0 … 255)
Bit 15 and 14:
0 0: number of the first faulty O-channel
1 0: number of the first faulty I-channel
0 1: there is a module fault
1 1: reserved
Tab. 139 Module diagnostic data
122 Festo — CPX-FB36 — 2019-07b

Technical appendix
6.4.4.6 Structure of the data of the I/O diagnostics interface
I/O diagnostics interface

Write access
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
x x x CPX function number
Data from the system table
Bit 15 (control bit): write access to the I/O diagnostics interface takes place with positive edge (0
è 1)
Bit 14 = 0: byte value, 1: word value
Bit 13 = 0: read request, 1: write request
Tab. 140 I/O diagnostics interface – write access
I/O diagnostics interface

Read access
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Result of last request
Data from the system table
Result of last request:
= 0: waiting
= 8000h: request successful
> 8000h: error
8001h: write protection or operator unit has write access
8002h: write not allowed, reserved range
8003h: internal error
Tab. 141 I/O diagnostics interface – read access
Information on the I/O diagnostics interface and examples of its use can be found in the CPX system
description (CPX-SYS).
6.4.5 Diagnostic memory (Groups C and E)
Modbus Diagnostic memory parameters and data

address Read access
Input data
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
45648 Run/stop filter 1 (CPX function number 3480)
Festo — CPX-FB36 — 2019-07b 123

Technical appendix
Modbus Diagnostic memory parameters and data

address Read access
45652 Error end filter (CPX function number 3484)

45652 Error number filter (CPX function number 3484)
45652 Module/channel filter (CPX function number 3484)
45653 Module number MN (CPX function number 3485)
45654 Channel number CN (CPX function number 3486)
45655 Fault number FN (CPX function number 3487)
45650 Diagnostic memory data – number of entries (CPX function number 3482)
45651 Diagnostic memory data – overflow (CPX function number 3483)
45651 Diagnostic memory data – status (CPX function number 3483)
45656 Diagnostic memory data (CPX function number 3488 + n1))
… …
1) è CPX system description (CPX-SYS)
Tab. 142 Read access to diagnostic memory parameters and data
Modbus Diagnostic memory parameters

address Write access
Output data – write and modify

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
40261 Error end filter (CPX function number 3484)
40261 Error number filter (CPX function number 3484)
40261 Module/channel filter (CPX function number 3484)
40262 Module number MN (CPX function number 3485)
40263 Channel number CN (CPX function number 3486)
40264 Fault number FN (CPX function number 3487)
Tab. 143 Write access to diagnostic memory parameters
Information about the diagnostic memory can be found in the CPX system description (CPX-SYS).
124 Festo — CPX-FB36 — 2019-07b

Technical appendix
6.4.6 Modbus TCP-Objects (Group F)
Object ID Object name Contents
0 Vendor name "Festo SE & Co. KG"

1 Product code "CPX-FB36"
2 MajorMinorRevision "x.y"1)
3 VendorURL "http://www.festo.com"
4 Product name "Modbus TCP"
5 Model name "CPX terminal"
1) x: version Modbus driver, y: revision code CPX terminal
Tab. 144 Modbus TCP objects
6.4.6.1 Examples of addressing for Modbus TCP

CPX terminal with digital I/O modules and MPA pneumatics
1 CPX-FB36 3 MPA pneumatics

2 Digital I/O modules
Fig. 29 Example 1: CPX terminal with digital I/O modules and MPA pneumatics
Module Loca- Modbus Input data

tion address
Bit 15 8 7 4 3 0
CPX-FB36 0 45392 Result of access to the I/O diagnostic interface
Remote I/O 45393
45394 Diagnostic data
Digital input module 1 45395 0 Input data
(CPX-8DI) 45396 Diagnostic data
Festo — CPX-FB36 — 2019-07b 125

Technical appendix

tion address
Digital output module 2 45397 x Echo output

(CPX-4DO) data
MPA pneumatic module 3 45399 x Echo output data
with diagnostic func- 45400 Diagnostic data
tion
tion
tion
tion
Tab. 145 Input data Addressing example 1

tion address
Bit 15 8 7 4 3 0
Remote I/O 40002 Data for the system table (write access)
Digital output module 2 40003 x Output data
(CPX-4DO)
MPA pneumatic module 3 40004 x Output data
with diagnostic func-
tion
tion
tion
126 Festo — CPX-FB36 — 2019-07b

Technical appendix

tion address

tion
Tab. 146 Output data Addressing example 1
CPX terminal with digital and analogue I/O modules and also MPA pneumatics
1 CPX-FB36 4 MPA pneumatics

2 Digital I/O modules 3 Analogue I/O modules
Fig. 30 Example 2: CPX terminal with digital and analogue I/O modules and also MPA pneumatics

tion address
Bit 15 8 7 4 3 0
Remote I/O 45393 Data from the system table (read access)
Digital input module 1 45395 0 Input data
(CPX-8DI) 45396 Module diagnostic data
Analogue input module 2 45397 Analogue inputs channel 0
(CPX-2OI) 45398 Analogue inputs channel 1
45399 Module diagnostic data
Analogue output mod- 3 45400 Echo analogue outputs channel 0
ule (CPX-2AO) 45401 Echo analogue outputs channel 1
45402 Module diagnostic data
Festo — CPX-FB36 — 2019-07b 127

Technical appendix

tion address

with diagnostic func- 45404 Module diagnostic data
tion
tion
tion
Tab. 147 Input data Addressing example 2

tion address
Bit 15 8 7 4 3 0
Remote I/O 40002 Data for the system table (write access)
Analogue output mod- 3 40003 Analogue outputs channel 0
ule (2AO) 40004 Analogue outputs channel 1
tion
tion
tion
Tab. 148 Output data Addressing example 2
128 Festo — CPX-FB36 — 2019-07b

Copyright:
Festo SE & Co. KG
Ruiter Straße 82
73734 Esslingen
Germany
Phone:
+49 711 347-0
Internet:
© 2019 all rights reserved to Festo SE & Co. KG www.festo.com

FESTO CPX-FB36 - EthernetIP-ModbusTCPIP

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FESTO CPX-FB36 - EthernetIP-ModbusTCPIP

Uploaded by

Copyright:

Available Formats

CPX-FB36

ALLEN-BRADLEY®, CODESYS®, EtherNet/IP®, HART®, MODBUS®, ODVA CONFORMANT®, ODVA®,

2 Festo — CPX-FB36 — 2019-07b

Festo — CPX-FB36 — 2019-07b 3

4 Festo — CPX-FB36 — 2019-07b

Festo — CPX-FB36 — 2019-07b 5

6 Festo — CPX-FB36 — 2019-07b

1.2 Safety Instructions

Festo — CPX-FB36 — 2019-07b 7

1.3 Qualifications of specialised personnel (target group)

1.5 Information regarding this description

Further information on EtherNet/IP can be found here:

Tab. 1 ODVA certifications

All available documents for the product è www.festo.com/pk.

1.6 Terms and abbreviations

160d Decimal numbers are marked in part by a subscript "d".

8 Festo — CPX-FB36 — 2019-07b

A0h Hexadecimal numbers are marked by a subscript "h".

Festo — CPX-FB36 — 2019-07b 9

10 Festo — CPX-FB36 — 2019-07b

1.7 Data types

ARRAY –1) – Structure with identical

Festo — CPX-FB36 — 2019-07b 11

2.1.1 Connection and display components

1 Network-specific and CPX-specific LED displays

Fig. 1 Connection and display components

12 Festo — CPX-FB36 — 2019-07b

2.1.2 Dismantling and mounting

Dismantling bus node

1. Check seal and sealing surface. Replace damaged parts.

2.2 Settings of the DIL switches

Festo — CPX-FB36 — 2019-07b 13

2.2.1 Removing and attaching cover

2.2.2 Arrangement of the DIL switches

Fig. 3 DIL switch

2.2.3 Setting DIL switches

14 Festo — CPX-FB36 — 2019-07b

2.2.4 Setting operating mode and network protocol

DIL switch 1.1 Mode of operation

DIL 1.1: OFF Remote I/O

DIL switch 1.2 Network protocol

DIL 1.2: OFF EtherNet/IP

DIL 1.2: ON Modbus TCP

Tab. 5 Setting network protocol

2.2.5 Setting diagnostic mode or data field size

DIL switch 2 Diagnostics mode Data field size

Festo — CPX-FB36 — 2019-07b 15

DIL switch 2 Diagnostics mode Data field size

2.1: ON reserved 64 byte I/64 byte O for commu-

2.2.6 Setting IP addressing

DIL switch 3 IP addressing

Dynamic addressing is set in the factory via DHCP/BOOTP.

Example – setting IP address of the bus node

DIL 3.8: OFF Example:

16 Festo — CPX-FB36 — 2019-07b

Example – setting IP address of the bus node

Tab. 8 Example – IP addressing

2.3 Connecting to the network

Unauthorised access to the device can cause damage or malfunctions.

An access password only protects against unintentional modification.

Use of switches and routers

Festo — CPX-FB36 — 2019-07b 17

2.3.2 Overview of connection technology and network plug connectors