Manual Festo

CPX Terminal
Manual
Electronics
CPX bus node
Type CPXFB33
Type CPXMFB34
Type CPXMFB35
Network protocol
PROFINET IO
Manual
548 760
en 1008b
[752 465]
Contents and general instructions
Original . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . de
Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . en 1008b
Designation . . . . . . . . . . . . . . . . . . . . . . . P.BECPXPNIOEN
Order no. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 760
(Festo AG & Co. KG, D73726 Esslingen, Germany, 2010)

Internet: http://www.festo.com
EMail:
service_international@festo.com
The reproduction of this document and disclosure to third
parties and the utilisation or communication of its contents
without explicit authorization is prohibited. Offenders will
be held liable for compensation of damages. All rights
reserved, in particular the right to carry out patent, utility
model or ornamental design registrations.
Festo P.BECPXPN IOEN en 1008b
PROFINET IO, PROFIBUS, SIMATIC, TORX, TV and VDE

are registered trademarks of the respective trademark owners in certain countries.
II
Contents
Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Instructions on this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Important user instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VII
VIII
VIII
IX
XI
1.
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
1.1
1.2
1.3
1.4
13
14
15
17
1.7
1.8
General instructions on installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Electrical connection and display components . . . . . . . . . . . . . . . . . . . . . . .
Dismantling and mounting of the bus node . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the DIL switches, use of the memory card . . . . . . . . . . . . . . . . . . . . .
1.4.1
Removing and attaching the cover for the DIL switches
and memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2
Settingthe DIL switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.3
Use of the memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of the bus node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1
General information about PROFINET networks . . . . . . . . . . . . . . .
1.6.2
Overview of connections, network connectors and cables . . . . . . .
1.6.3
Network interface of the CPXFB33 . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.4
Network interface of the CPXMFB34 . . . . . . . . . . . . . . . . . . . . . . .
1.6.5
You will then comply with protection class IP65/IP67 . . . . . . . . . . . . . . . . . .
Pin assignment of power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
18
114
115
117
117
119
123
124
125
126
127
2.
Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
2.1
2.2
2.3
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
2.3.1
Basic rules for addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
2.3.2
Address assignment and addressing after expansion
or conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
1.5
1.6
III
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
IV
Instructions for commissioning with Siemens SIMATIC STEP 7 . . . . . . . . . . .

Preparing for commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.1
Import device master file (GSDML) and symbol files . . . . . . . . . . .
2.5.2
Select GSDML file (compatibility table) . . . . . . . . . . . . . . . . . . . . . .
2.5.3
Setting up an automation project . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.4
Setting up the controller system (PLC/Master) . . . . . . . . . . . . . . . .
2.5.5
Installing GSDML file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.1
Localise and identify CPX terminal in the network . . . . . . . . . . . . . .
2.6.2
Select CPX terminal (station selection) . . . . . . . . . . . . . . . . . . . . . .
2.6.3
Assign device name" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.4
Set up Prioritized Startup (Fast Startup") . . . . . . . . . . . . . . . . . .
2.6.5
Assigning or changing IP address . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.6
Use MAC addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.7
Determine port addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPX terminal configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.1
Allocate configuration table (insert bus nodes and modules) . . . .
2.7.2
Modifying the I/O address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.3
Modifying the diagnostics address . . . . . . . . . . . . . . . . . . . . . . . . .
Parametrisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8.1
Start parametrisation while switching on (system start) . . . . . . . .
2.8.2
Parametrisation of the CPX terminal with Siemens STEP 7 . . . . . . .
2.8.3
Parametrisation with the handheld . . . . . . . . . . . . . . . . . . . . . . . . .
2.8.4
Parametrisation via the Festo Maintenance Tool . . . . . . . . . . . . . . .
2.8.5
Bus node parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8.6
Application example for parametrisation . . . . . . . . . . . . . . . . . . . . .
Identification & Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration in the Remote Controller operating mode . . . . . . . . . . . . . . . .
Checklist for starting up the CPX terminal . . . . . . . . . . . . . . . . . . . . . . . . . . .
219
221
221
222
224
225
227
228
228
230
233
235
239
242
243
244
244
249
249
251
253
254
260
260
261
263
264
267
268
3.
Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
3.1
3.2
Overview of Diagnostic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Diagnostics via LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1
Network status LED NF / connection status LEDs TP1, TP2 . . . . .
3.2.2
CPX system/terminal status LEDs PS, PL, SF, M . . . . . . . . . . . . . .
Diagnostics via status bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics via the I/O diagnostic interface (STI) . . . . . . . . . . . . . . . . . . . . .
Diagnostics via PROFINET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1
Basic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2
Online diagnostics with Siemens STEP 7 . . . . . . . . . . . . . . . . . . . . .
3.5.3
Userspecific diagnostics with Siemens STEP 7 . . . . . . . . . . . . . . .
33
35
37
38
311
312
313
313
316
318
A.
Technical appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A1
A.1
A.2
A.3
A.4
Technical data of bus node CPXFB33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical data of bus node CPXMFB34 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Networkspecific technical data
Bus node CPXFB33, CPXMFB34 and CPXMFB35 . . . . . . . . . . . . . . . . . . .
A3
A4
A5
B.
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B1
B.1
Bus node operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.1
Remote I/O Explanation of the operating mode . . . . . . . . . . . . . .
B.1.2
Remote controller explanation of the operating mode . . . . . . . . .
B.1.3
Fast Startup" explanation of the additional function . . . . . . . . .
B3
B3
B4
B5
C.
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C1
3.3
3.4
3.5
A6
VI
Intended use
The CPXFB33, CPXMFB34 and CPXMFB35 bus nodes
documented in this manual are intended only for use as
stations (I/O device) on the industrial Ethernet system
PROFINET IO.
The bus nodes can be used in three different operating
modes:
Remote I/O
Remote controller
Remote I/O with additional function Prioritized Startup,

also designated "Fast Startup" (FSU)
The FSU operating mode ensures a faster startup of the CPX

system.
But this operating mode has restrictions regarding
commissioning and parametrisation. Detailed information can
be found in the corresponding chapters.
The CPX terminal must only be used as follows:
As intended in an industrial environment
In original condition without modification (only the

conversions or modifications described in the
documentation supplied with the product are permitted)
In faultless technical condition
The limit values specified for pressures, temperatures,

electrical data, torques etc. should be observed.
If conventional accessory components such as sensors and
actuators are connected, the specified limits for pressures,
temperatures, electrical data, torques etc. should be
observed.
VII
Comply with the legal rules and regulations and standards,

rules of the testing organisations and insurance companies
and national specifications applicable for the location.
Warning
Use only PELV circuits as per IEC/DIN EN 602041 for the
electric power supply (protective extralow voltage,
PELV).
Observe also the general requirements for PELV power
circuits as per IEC/DIN EN 602041.

Use only power packswhich guarantee reliable electrical
isolation of the operating voltage as per IEC/DIN EN

602041.
Due to the use of PELV power units, protection against
electric shock (protection against direct and indirect contact)
is guaranteed in accordance with IEC/DIN EN 602041
(Electrical Equipment of Machines, General Requirements).
Observe the measures in sections 2.11 and 3.1 when
implementing an emergency stop function.
Target group
This manual is intended exclusively for technicians trained in
control and automation technology who have experience in
installing, commissioning, programming and diagnosing
programmable logic controllers (PLC) and field bus systems.
Service
Please consult your local Festo Service agent if you have any
technical problems.
VIII
Instructions on this manual

This manual includes information
about the following modules:
CPX bus node
Type
designation
Description
Connection technology
CPXFB33
Ethernetbased CPX bus node

for PROFINET IO
2 x M12 socket,
Dcoded, female, 4pin,
corresponding to IEC 610762
The PROFINET fieldbus

technology uses the Ethernet
standards and TCP/IP protocol
for realtime communication in
an industrial environment.
Data transmission:
CPXMFB34
CPXMFB35
PROFINET, based on
industrial Ethernet,
based on the Ethernet
protocol (IEEE 802.3),
realtime capable
Switched Fast Ethernet,
100 Mbit/s
Selection of directives,
standards and norms
regarding PROFINET:
PROFINET Installation Guide

IEC 61158
IEC 61784
IEC 61918
2 x RJ45 sockets, pushpull,

copper, conforms to AIDA,
corresponding to IEC 60603,
IEC 610763
2 x SCRJ sockets, pushpull,

650 nm wavelength, suitable
for POF fibreoptic cable,
AIDAconforming,
Further information:
http://www.profinet.com
Tab. 0/1:
Overview of CPX bus node for PROFINET
IX
This manual includes information about installation and

configuration of the CPX bus node for PROFINET as well as
PROFINETspecific information regarding parametrisation,
commissioning, programming and diagnosis of a CPX terminal
in a PROFINET network.
Further information about PROFINET can be obtained in the
Internet:
www.profinet.com
Also observe the following PROFINETspecific document:
General basic information on the mode of operation,

mounting, installing and commissioning CPX terminals can be
found in the CPX system description (P.BECPXSYS...).
Information about further CPX modules can be found in the
description for the respective module.
An overview of the structure of the CPXterminal user
documentation is contained in the CPX system description
(P.BECPXSYS...).
Product specific information about the control system (IPC,
PLC or I/O controller) can be found in the manufacturers
product documentation accompanying the product.
Important user instructions

Danger categories
This manual contains instructions on the possible dangers
which may occur if the product is not used correctly. These
instructions are marked (Warning, Caution, etc.), printed on a
shaded background and marked additionally with a picto
gram. A distinction is made between the following danger
warnings:
Warning
This means that failure to observe this instruction may
result in serious personal injury or damage to property.
Caution
result in personal injury or damage to property.
Note
result in damage to property.
The following pictogram marks passages in the text which

describe activities with electrostatically sensitive
components.
Electrostatically sensitive components may be damaged if
they are not handled correctly.
XI
Marking special information

The following pictograms mark passages in the text
containing special information.
Pictograms
Information:
Recommendations, tips and references to other sources of
information.
Accessories:
Information on necessary or sensible accessories for the
Festo product.
Environment:
Information on environmentfriendly use of Festo products.
Text markings
The bullet indicates activities which may be carried out in

any order.
1. Figures denote activities which must be carried out in the

numerical order specified.
XII
Hyphens indicate general activities.
The following productspecific terms and abbreviations are

used in this description:
Term/abbreviation
Meaning
A0h
Hexadecimal numbers are marked by a subscript h".
AIDA
Automation Initiative of German Automobile Manufacturers
AutoMDI
AutoMDI designates the capability of automatically recognising the

circuitry of the transmitting and receiving lines or of the connected
device and to adjust to it (also designated Crossover detection" or
Auto crossover")
Bus node
Create the connection to certain networks or fieldbusses; pass on

control signals to the connected modules and monitor their functioning
CEC
CoDeSys controller, e.g. CPXCEC/CPXCEC..., applicable for

configuration, commissioning and programming of various components
and equipment from Festo
CoDeSys
Controller Development System
CP
Compact Performance
CPX modules
Common term for the various modules which can be incorporated in a

CPX terminal
CPX Terminal
Complete system consisting of CPX modules with or without

pneumatics
DIL switch
Miniature switch; dualinline switches consist of several switch

elements with which settings can be made
FEC
Front End Controller, e.g. CPXFEC, applicable as:

standalone system controller(PLC, stand alone operating mode)
System controller (PLC, remote controller operating mode)
Fieldbus slave (Remote I/O operating mode)
FMT
Festo Maintenance Tool (CPXFMT); configuration and programming

software for CPX modules for startup and service purposes
FO
Fibreoptic cable (FOC, fibre optics)
FOC
Fibreoptic cables
Tab. 0/2:
Specific terms and abbreviations part 1
XIII
Term/abbreviation
Meaning
FSU
Fast Startup", also designated Prioritized Startup"; further informa

tion can be found in section B.1.3
Handheld (MMI)
Handheld terminal (handheld, CPXMMI) for CPX modules for commis

sioning and service purposes (ManMachine Interface, MMI)
Digital input
IB
Input byte
I/O modules
Collective term for the CPX modules which provide digital inputs and
outputs
I/Os
Digital inputs and outputs
IPC
Industrial PC
MAC address
Permanently assigned hardware address (physical address") for

Ethernet network equipment or network adapters for unique identifi
cation in the worldwide computer network (media access control ad
dress)
MDI
Mediumdependent interface
Digital output
OB
Output byte
Octet
Number of address words assigned by the CPX terminal
PLC
Programmable Logic Controller, same meaning as SPS
POF
Polymeric optical fibre (POF: also designated plastic optical fibre)
Pneumatic interface
The pneumatic interface is the interface between the modular electrical

periphery and the pneumatics
Prioritized Startup
Prioritized Startup is also designated Fast Startup" (FSU);

Further information can be found in section B.1.3
PROFINET IO
Fieldbus system based on Industrial Ethernet for data exchange be

tween system controller (PLC/IPC), plant controller (e.g. CPXFEC) and
field devices (I/O devices) or drives and valve terminals; for further
information: http://www.profinet.com
Tab. 0/3:
XIV
Term/abbreviation
Meaning
PROFINET IO RT
Profinet IO in the version with realtime protocol

(typical cycle time: 10 ms; typical application: production control)
PROFINET IO IRT
PROFINET IO in the version with isochronous realtime protocol

(typical cycle time: < 1 ms; typical application: drive controller)
SPS
Programmable logic controller, also designated system controller or

controller for short (see also PLC)
STI
I/O diagnostic interface (System Table Interface)
Tab. 0/4:
XV
XVI
Installation
Chapter 1
11
1. Installation
Contents
1.
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
1.1
1.2
1.3
1.4
General instructions on installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Electrical connection and display components . . . . . . . . . . . . . . . . . . . . . . .
Dismantling and mounting of the bus node . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the DIL switches, use of the memory card . . . . . . . . . . . . . . . . . . . . .
1.4.1
and memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2
Settingthe DIL switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.3
Use of the memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of the bus node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1
General information about PROFINET networks . . . . . . . . . . . . . . .
1.6.2
Overview of connections, network connectors and cables . . . . . . .
1.6.3
Network interface of the CPXFB33 . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.4
1.6.5
You will then comply with protection class IP65/IP67 . . . . . . . . . . . . . . . . . .
Pin assignment of power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
14
15
17
1.5
1.6
1.7
1.8
12
17
18
114
115
117
117
119
123
124
125
126
127
1. Installation
1.1
General instructions on installation

Warning
Before carrying out installation and maintenance work,
switch off the following:
compressed air supply
operating voltage supply for the electronics/sensors
load voltage supply for the outputs/valves
In this way, you can avoid:
uncontrolled movements of loose tubing
unexpected movements of the connected actuators
undefined switching states of the electronics
Caution
The CPX bus node contains electrostatically sensitive
components.
Therefore, do not touch any components.
Observe the handling specifications for electrostatically
sensitive devices.
You avoid malfunctions of and damage to the electronics by
doing so.
Information about fitting the CPX terminal can be found in the
CPX system manual (P.BECPXSYS...).
13
1. Installation
1.2
Electrical connection and display components

You will find the following connection and display elements
on the CPX bus node for PROFINET:
3
2
2
2
CPXFB33
CPXMFB34
CPXMFB35
1 PROFINETspecific network/bus status 3 Cover for DIL switch and memory card
LEDs and CPXspecific LEDs
2 Network connection
CPXFB33:
2 x M12, Dcoded,
female, 4pin
CPXMFB34: 2 x RJ45, pushpull,
copper
CPXMFB35: 2 x SCRJ, pushpull,
4 Service interface
for handheld (CPXMMI; V.24 interface)
and USB adapter (for CPXFMT)
5 Name plate with MACID and CPX

revision code (Rev ...")
Fig. 1/1: Connection and display components on the CPX bus node
Note
Use protective caps or blanking plugs to seal unused
connections. You will then comply with protection class
IP65/IP67 (see section 1.7).
14
1. Installation
1.3
Dismantling and mounting of the bus node

When installed, the bus node is located in an interlinking
block of the CPX terminal (see Fig. 1/2).
Dismantling
Dismantle the bus node as follows:

1. Loosen the four screws of the bus node with a size T10
Torx screwdriver.
2. Pull the bus node carefully and without tilting away from
the contact rails of the interlinking block.
1 CPX bus node

(Example CPXFB33)
2 Interlinking block
1
3 Contact rails
4 Torx T10 screws,
tightening torque:
0.9 ... 1.1 Nm
3
2
Fig. 1/2: Dismantling/mounting the bus node
15
1. Installation
Note
Always use appropriate screws for the interlocking block,
which depend on the blocks material (metal or plastic).
For plastic interlinking blocks:
threadcutting tapping screws
For metal interlinking blocks:
screws with metric thread.
Both types of screws are enclosed respectively when ordering
the bus node as a single part.
Mounting
Mount the bus node as follows:

1. Check seal and seal surfaces
2. Place the bus node in the interlinking block without
tilting.
3. Carefully push the bus node into the interlinking block up
to the stop.
4. Place the screws so that the selfcutting threads can be
used.
5. Tighten the screws with a size T10 Torx screwdriver with
0.9 ... 1.1 Nm of torque.
16
1. Installation
1.4
Setting the DIL switches, use of the memory card

In order to make the settings for the CPX bus node and to
change the memory card, you must first remove the cover for
the DIL switches.
Caution
The CPX bus node contains electrostatically sensitive
components.
Therefore, do not touch any components.
Observe the handling specifications for electrostatically
sensitive devices.
You avoid malfunctions of and damage to the electronics
by doing so.
1.4.1

and memory card
You need a screwdriver in order to remove or attach the
cover.
Note
Observe the following instructions when removing or
attaching the cover:
Disconnect the power supply before removing the cover.
Make sure that the seal is seated correctly when
attaching the cover.

Tighten the two fastening screws at first by hand and
then with max. 0.4 Nm.
17
1. Installation
1.4.2
Settingthe DIL switches

You can set the following parameters with the DIL switches
under the cover (see Fig. 1/3):
Bus node operating mode
Diagnostics mode (remote I/O operating mode only)
Datafield size (only in remote controller operating mode)
Procedure:
1. Switch off the power supply.
2. Remove the cover.
(see section 1.4.1).
3. Make the required settings
(see Tab. 1/1, Tab. 1/2 and Tab. 1/4).
4. Reattach the cover
Note
Make sure that the seal is seated correctly.
1 DIL switches 1.1 + 1.2:

Bus node operating mode
2 DIL switches 2.1 + 2.2:

Diagnostics mode
(remote I/O operating mode only);
Datafield size
(only in remote controller operating mode)
2
3
3 Memory card
(see section 1.4.3, 1.5 as well as 2.6.3 and 2.8.1)
Fig. 1/3: Settings of the DIL switches on the bus node
18
1. Installation
Setting the operating mode with DIL switch 1

You can set the operating mode of the bus node with switch
element 1.1 of DIL switch 1 (see Tab. 1/1):
DIL switch 1
Remote I/O operating mode

Remote controller operating mode
Function:
Set bus node operating mode
DIL 1.1: OFF

DIL 1.2: OFF
(factory setting)
Remote I/O operating mode

All functions of the CPX terminal are controlled directly by the
PROFINETIO controller or a higherlevel PLC.
The bus node undertakes the required connection to PROFINET,
ifrequired.
DIL 1.1:
DIL 1.2:
ON
OFF
Operating mode remote controller

Requirement:
A CPXFEC or CPXCEC is a component of the CPX terminal.
The CPXFEC or CPXCEC integrated into the terminal controls all
functions of the CPX terminal, i.e. the FEC or CEC takes on the
I/Ocontrol.
The bus node undertakes the additional connection to PROFINET,
ifrequired.
Tab. 1/1:
Setting the bus node operating mode with DIL switch 1

Further explanations of the bus node operating mode can be
found in section B.1:
Remote controller operating mode section B.1.2
Remote I/O operating mode section B.1.1
Additional function Fast Startup" (FSU) section B.1.3
19
1. Installation
In remote I/O operating mode:

Setting the diagnostics mode with DIL switch 2
The function of the DIL switch 2 depends on the setting of
the DIL switch 1 or the set operating mode of the CPX
terminal (see Tab. 1/1):
The diagnostics mode is set with DIL switch 2 in the remote
I/O operating mode (see Tab. 1/2).
DIL switch 2
Function:
Setting diagnostics mode
(in remote I/O operating mode)
DIL 2.1: OFF

DIL 2.2: OFF
(factory setting)
DIL 2.1:
DIL 2.2:
OFF
ON
The status bits are switched on

(+ 1 byte I / 0 byte O) 1)
DIL 2.1:
DIL 2.2:
ON
OFF
The I/O diagnostic interface is switched on

(+ 2 bytes I / 2 bytes O) 2)
DIL 2.1:
DIL 2.2:
1)
2)
The I/O diagnostics interface and status bits are switched off
(+ 0 byte I / 0 byte O)
ON
ON
Reserved for future extensions
Diagnostics mode status bits occupy 1 byte of address space (8 I bits)

Diagnostics mode I/O diagnostics interface occupies 4 bytes of address space (16 I and 16 O bits)
Tab. 1/2:
110
Setting the diagnostics mode with DIL switch 2 (in remote I/O operating mode)
1. Installation
Note
(1) Diagnostics mode reduces the available address space
Use of the diagnostics mode (status bits or I/O diagnostic
interface) occupies 8 I or 16 I/O bits and thus reduces the
number of I/O bits which are available for module
communication. In this way, the number of addressable
modules is reduced in favour of additional status or
diagnostic information.
Take account of this fact for the planning of your
CPXterminal.
(2) Subsequent activation changes configuration
During subsequent activation of the diagnostics module
(status bits or I/O diagnostics interface), the CPXinternal
I/O image can be displaced.
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.
Assignment of the I/O addresses and diagnostics
addresses can be changed as needed.
To do this, repeat the hardware and network configuration
in your configuration and programming software
(e.g. Siemens SIMATIC STEP 7), especially assignment
ofthe inputs and outputs (see section 2.7.1 and
section 2.7.2).
111
1. Installation
Note
The DIL switch settings for operating mode and
diagnostics mode must match the bus node selection in
the context of a PLC hardware and network configuration
(see Tab. 1/3 and section 2.6.2).
1
2
3
Operating mode Diagnostics mode
Additional function Field device group
of the bus node
Fast Startup (FSU)
[mode identification]
(station symbol)
FB33, FB34 FB35
CPX 1)
CPXFO
Yes, with FSU
CPX FSU 2)
CPXFO FSU 2)
No
CPX 1)
CPXFO
Yes, with FSU
CPX FSU 2)
CPXFO FSU 2)
I/O diagnostics interface

[STI] 3
No
CPX 1)
CPXFO
Yes, with FSU
CPX FSU 2)
CPXFO FSU 2)
n/a
n/a
CPX RC
CPXRCFO
Without
diagnostics 1
Remote controller
1)
2)
No
Status bits
[Status] 2
Remote I/O
CPX Rev 11 for bus node up to CPX revision code Rev 11

Prioritized Startup, from GSDML file V. 2.2 + Rev 12
Tab. 1/3:
112
Bus node selection (station symbol or field device group) dependent on

operating mode, diagnostics mode and additional function FSU
1. Installation
In remote controller operating mode:

Setting the datafield size with DIL switch 2
The function of the DIL switch 2 depends on the setting
ofthe DIL switch 1 or the set operating mode of the
CPXterminal (see Tab. 1/1):
The datafield size is set with DIL switch 2 in the remote
controller operating mode (see Tab. 1/4).
Further explanations on the remote controller" operating
mode can be found in section B.1.2.
DIL switch 2
Function:
Setting datafield size
(in remote controller operating mode)
DIL 2.1: OFF

DIL 2.2: OFF
(factory setting)
DIL 2.1:
DIL 2.2:
OFF
ON
Datafield size:
16 bytes I/16 bytes O
DIL 2.1:
DIL 2.2:
ON
OFF
DIL 2.1:
DIL 2.2:
Tab. 1/4:
Datafield size:
8 bytes I/8 bytes O
ON
ON
Setting the datafield size with DIL switch 2

(in remote controller operating mode)
113
1. Installation
1.4.3
Use of the memory card

The memory card is used as a carrier of configuration data,
e.g. of the fieldbus device name (PROFINET IO device name),
and thus simplifies bus node replacement.
Note
Data stored on the card have priority over other
configuration data which are stored, e.g. in the bus node
memory or in the controller system (see also section 2.8.1,
sequence of the start parametrisation with memory card).
Caution
Risk of malfunctions or damage.
Inserting or removing the memory card while the power
supply is switched on can result in malfunctions of or
damage to the memory card.
Disconnect the power supply before you insert or
remove the memory card.
Replacement
of the memory card
114
The memory card is located under a cover (see Fig. 1/1).

You need a screwdriver in order to remove or attach this
cover.
1. Installation
1.5
Replacement of the bus node

Easy replacement using memory card
The memory card is used as a carrier of configuration data,
e.g. of the fieldbus device name, i.e. of the PROFINET IO
device name. Thus, a bus node can be conveniently replaced.
Note
Check the startup behaviour of the CPX terminal before
replacing the bus node.
If the Modify LED (M) lights up or flashes permanently
after the system start, System start with saved
parametrisation and saved CPX expansion" is set or
Force" is active.
For CPX terminals with a permanently lit or flashing MLED,
the parametrisation at replacement of the bus node or
CPX terminal during servicing is not automatically created
by the higherlevel system.
In this case, verify which settings are required before
replacement, and restore these settings after replacement.
Caution
Risk of malfunctions or damage.
Inserting or removing the memory card while the power
supply is switched on can result in malfunctions of or
damage to the memory card.
Disconnect the power supply before you insert or
remove the memory card.
115
1. Installation
Bus node replacement with memory card:

2. Remove the cover.
(Observe section 1.4.1).
3. Remove the memory card from the bus node.
4. Replace the bus node (mounting/dismantling:
see section 1.1).
5. Insert the memory card in the new bus node.
6. Reattach the cover (observe section 1.4.1).
7. Switch the power supply back on.
8. Start the automation program if necessary.
9. The controller recognises the bus node using the device
name on the memory card and loads all required data.
Bus node replacement without memory card:
2. Replace the bus node (mounting/dismantling:
see section 1.1).
3. Switch the power supply back on.
4. Start your configuration and programming software
(e.g. Siemens STEP 7).
5. Perform a new configuration (hardware configuration,
inSTEP 7 using HW Config).
6. The controller loads all required data into the bus node.
116
1. Installation
1.6
1.6.1
Connecting to the network

General information about PROFINET networks
Note
Subassemblies with PROFINET interfaces must not be
operated in networks where all connected network
components are supplied with PELV power supplies or
integrated power supplies with similar protection.
Installation guidelines
The installation guidelines can be obtained via the PROFINET
User Organisation:
Internet: http://www.profinet.com
Internet: http://www.profibus.com/downloads
Observe the instructions there.
117
1. Installation
Use of switches and routers

The switch integrated in the bus node permits division of the
network into several segments.
With use of additional switches and routers, the network can
be divided into additional segments. Thus, it is possible to
structure the PROFINET network and realize greater network
expansions.
independent of the network structure, the expansion of a
PROFINET segment must not exceed certain connection
lengths:
Copper connection line

(Ethernet twistedpair wire, 22 AWG):
max. 100 m between network stations
(PROFINET endtoend link)
Optical connecting cable

(POF fibreoptic cable, max. 12.5 dB signal attenuation
over the entire connection length):
max. 50 m PROFINET endtoend link
Switches and routers for Industrial Ethernet are available on

the market from various companies. There are many IP20,
IP65 or IP67 components.
Unmanaged switches:
for small Ethernet solutions with a low network load or
minimal requirements for deterministics.
Managed switches:
for comprehensive network solutions, with diagnostics
and control functions
Note
Make sure that any intermediate switches and routers
support the PROFINET function Fast Startup" (FSU) when
you use this additional function. Further information on
FSU can be found in section B.1.3.
118
1. Installation
Note
PROFINET devices (I/O devices) that are connected over
Industrial Wireless LAN (IWLAN access points) do not
support the FSU function.
1.6.2
Overview of connections, network connectors and cables

Note
Faulty installation or high transmission rates may cause
data transmission errors as a result of signal reflections
and attenuations.
Causes of transmission faults may be:
faulty screened connection
branches
transmission over distances that are too long
inappropriate cables
Observe the cable specification!
Refer to the manual of your controller for information
about the required type of line or cable.
Bus node
Connection technology
Network connectors
CPXFB33
2x M12 socket, Dcoded, female, 4pin,

Plug from Festo,

Type NECUMSD12G4C2ET
CPXMFB34
2 x RJ45 socket, pushpull connection,

copper, AIDAcompliant, corresponding
toIEC 60603, IEC 610763
Plug from Festo,

Type FBSRJ45PPGS
CPXMFB35
2 x SCRJ sockets, pushpull connection,

650 nm wavelength, suitable for POF
fibreoptic cable, AIDAcompliant,
Plug from Festo,

Type FBSSCRJPPGS
Internet: www.festo.com/catalogue/
Tab. 1/5:
Overview of connection technology and network plugs
119
1. Installation
RJ45 to M12 converter

For PROFINET installations, it may be necessary to change
between RJ45 and M12 connection technology.
Application example: Connections between devices in the
switch cabinet with RJ45 connection and IP65/IP67 devices
with M12 connection.
Cable specification
Use shielded Industrial Ethernet lines of category
Cat 5/Cat 5e or higher. You can find details regarding cable
specification in Tab. 1/6.
Crossover detection
The CPX bus nodes for PROFINET support crossover

detection (AutoMDI"). You can optionally use patch cables
or crossover cables for connecting your bus node to a
network or PC.
Make sure that the function Autonegotiation/Autocrossover"
is activated in your controller software if you use patch and
crossover cables in the same system. You will find additional
instructions on this function in section 2.6.4.
Crossover detection is not available in the Prioritized
Startup" operating mode (FSU):
Use only suitable lines.

Choose the network line (patch cable or crossover cable)
depending on the circuitry (pin allocation) of the
connected devices (I/O devices, see Fig. 1/4):
Crossover cable with the same assignment of the ports
Patch cable with different assignment of the ports
120
Observe the following note regarding pin allocation of

port TP2.
1. Installation
Note pin allocation TP2

Deactivation of the crossover detection changes the pin
allocation of the outgoing port TP2 to crossover".
Choose the network line (patch cable or crossover cable)
depending on the circuitry of the connected devices
(I/O devices).
Make sure that the function

Autonegotiation/Autocrossover" is deactivated in your
control software before placing the system in operation
If necessary, the function Autonegotiation/Autocrossover"

must also be deactivated on the hardwareside, in the
basic setting of your controller (PLC) or switches or
routers in between: Check this with the port settings.
PLC or switch
TP1
I/O device
TP2
TP1
1 Switch port, e.g. of the PLC
I/O device
TP2
TP1
TP2
3 Patch cable
(crossover" pin allocation)
2 Terminal port of an I/O device

Fig. 1/4: Wiring of the I/O devices for Fast Startup" with deactivated crossover"
detection or autonegotiation" (configuration example)
121
1. Installation
Bus node
Line specification 1)
+ network plug
CPXFB33
+ ...D12G4...
Cable type:
Transmission class
(link class):
Cable diameter:
Wire cross section:
Connection length:
CPXMFB34
+ ...RJ45...
Cable type:
Transmission class
(link class):
Cable diameter:
Wire cross section:
Wire/conductor
configuration:
Connection length:
CPXMFB35
+ ...SCRJ...
Cable type:
Cable composition
(core/sheath
diameter):
Cable diameter:
Connection length:
Signal attenuation:
1)
Ethernet twisted pair cable, screened

(Shielded twisted pair, STP)
category Cat 5/Cat 5e
6 ... 8 mm
0.14 ... 0.75 mm2);
22 AWG required for max. connection length
between network stations (PROFINET endtoend link)
Ethernet twisted pair cable, screened
(Shielded twisted pair, STP)
category Cat 5/Cat 5e
5 ... 8 mm
0.13 ... 0.36 mm2 (Z approx. 26 ... 22 AWG);
22 AWG required for max. connection length
between network stations (PROFINET endtoend link)
1wire or 7wire
fibreoptic cable, polymeroptic fibre
(polymeric/plastic optical fibre, POF)
980/1000 m
6.5 ... 9.5 mm
12.5 dB
(over the entire connection length)
Length corresponding to specification for PROFINET networks (PROFINET Installation Guide)

based on ISO/IEC 11801, ANSI/TIA/EIA568 (see also section 1.6.1)
Internet: www.profinet.com, www.profibus.com/downloads
Tab. 1/6:
122
Overview of line specification (in combination with Festo bus node and
Festonetwork plug)
1. Installation
Note strain relief

If the CPX terminal is fitted onto the moving part of a
machine, the network cable on the moving part must be
provided with strain relief. Please also observe the relevant
regulations in EN60204 part 1.
1.6.3
Network interface of the CPXFB33

There are two 4pin, Dcoded M12 sockets on the CPXFB33
for the network connection.
Socket
Pin
Signal
Explanation
1
2
3
4
Housing
TD+
RD+
TD
RD
Shield/FE
Transmitted data +
Received data +
Transmitted data
Received data
Shield/functional earth
M12, Dcoded
2
1
3
4
Tab. 1/7:
Pin allocation of the network interfaces of the CPXFB33 (M12)
Connection with plug from Festo

Connect the CPX terminal to the network with Festo plugs
type NECUMSD12G4C2ET. The plug is designed for
Ethernet cable with cable diameters of 6 ... 8 mm.
To achieve protection class IP65/IP67:
Use Festo plugs.

Seal unused interfaces (see section 1.7).
123
1. Installation
1.6.4
Network interface of the CPXMFB34

There are two RJ45 pushpull sockets (AIDAcompliant) on the
CPXMFB34 for the network connection:
Socket
Pin
Signal
Explanation
1
2
3
4
5
6
7
8
Housing
TD+
TD
RD+
n.c.
n.c.
RD
n.c.
n.c.
Shield/FE
Transmitted data +
Transmitted data
Received data +
Not connected
Not connected
Received data
Not connected
Not connected
Shield/functional earth
8
7
6
5
4
3
2
1
RJ45, pushpull
Tab. 1/8:
Pin allocation of the network interfaces of the CPXMFB34 (RJ45)

Connect the CPX terminal to the network with Festo plugs,
type FBSRJ45PPGS. The plug is designed for Ethernet cable
with cable diameters of 5 ... 8 mm.
124
Use Festo plugs.

1. Installation
1.6.5
Network interface of the CPXMFB35

There are two SCRJ pushpull sockets (AIDAcompliant) on the
CPXMFB35 for the network connection:
Socket
Port
Signal
Explanation
1
2
TX
RX
Transmitted data
Received data
SCRJ, pushpull
Tab. 1/9:
Pin allocation of the network interfaces of the CPXMFB35 (SCRJ)

Connect the CPX terminal to the network with Festo plugs,
type FBSSCRJPPGS. The plug is designed for POF fibreoptic
cable with cable diameter of 6.5 ... 9.5 mm.
Use Festo plugs.

125
1. Installation
1.7
You will then comply with protection class IP65/IP67

In order to comply with protection class IP65/IP67, seal
unused sockets with the appropriate plugs or protection
caps.
Port
Port IP65/IP67
Cover IP65/IP67 1)
CPXFB33:
TP1, TP2 (M12)
Plug from Festo,

Type NECUMSD12G4C2ET
Cover cap from Festo,

Type ISKM12
CPXMFB34:
TP1, TP2 (RJ45)
Plug from Festo,

Type FBSRJ45PPGS
CPXMFB35:
TP1, TP2 (SCRJ)
Plug from Festo,

Type FBSSCRJPPGS
Service interface (M12) for

CPXMMI + CPXFMT
Connecting cable and plugs

of the CPXMMIs or CPXFMTs
1)
2)

Type CPXMAKC

Type ISKM12 2)
if connection is not used

included in scope of supply, always cover unused connection
Tab. 1/10:
126
Connections and covers for protection class IP65/IP67
1. Installation
1.8
Pin assignment of power supply

Warning
Use only PELV circuits as per IEC/DIN EN 602041 for
the electric power supply (protective extralow voltage,
PELV).
Observe also the general requirements for PELV power
circuits as per IEC/DIN EN 602041.

Use only power packswhich guarantee reliable
electrical isolation of the operating voltage as per

IEC/DIN EN 602041.
Due to the use of PELV power units, protection against
electric shock (protection against direct and indirect contact)
is guaranteed in accordance with IEC/DIN EN 602041
(Electrical Equipment of Machines, General Requirements).
Observe the measures in sections 2.11 and 3.1 when
implementing an emergency stop function.
The current consumption of a CPX terminal depends on the
number and type of integrated modules and components.
Observe the information on power supply and the required
earthing measures in the CPX system description.
127
1. Installation
System power supply,

additional power supply
and valve power supply
Plugs
The CPX terminal is supplied with operating and load power

via the interlinking block with system, additional and valve
supply.
Interlinking block with

System supply
Additional power supply
Valve supply
Type CPX(M)GEEVS... Type CPX(M)GEEVZ...
7/8"5PIN
2
3
4
1
5
M18
1
4
2
3
Pushpull 2)
VEL/SEN:
VOUT/VAL:
FE:
n.c.:
1)
2)
A: n.c.
B: 24 VOUT
C: FE
D: 0 VOUT
A: n.c.
B: 24 VVAL
C: FE
D: 0 VVAL
1: 0 VOUT
2: n.c.
3: FE
4: n.c.
5: 24 VOUT
1: 24 VEL/SEN
2: 24 VVAL / 24 VOUT
3: 0 VEL/SEN /
0 VVAL / 0 VOUT
4: FE
1: n.c.
2: 24 VOUT
3: 0 VOUT
4: FE
1: n.c.
2: 24 VVAL
3: 0 VVAL
4: FE
1: 24 VEL/SEN
2: 0 VEL/SEN
4: 0 VVAL / 0 VOUT
5: FE
A: 24 VEL/SEN
B: 24 VVAL / 24 VOUT
C: FE
D: 0 VEL/SEN /
0 VVAL / 0 VOUT
1: 0 VVAL / 0 VOUT
2: 0 VEL/SEN
3: FE
4: 24 VEL/SEN
7/8"4PIN 1)
Type CPXGEEVV...
1: n.c.
2: n.c.
3: 24 VOUT
4: 0 VOUT
5: FE
Operating voltage for electronics/sensors

Load voltage for outputs/valves
Earth terminal (functional earth)
free (not connected)
Pay attention to the information on the plug (regarding allocation of the connection pins A, B, C, D).
Interlinking blocks with pushpull connection and with forwarding function or with system supply
are identically constructed.
Tab. 1/11:
128
Pin assignment for system supply, additional supply and valve supply
Commissioning
Chapter 2
21
2. Commissioning
Contents
2.
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
22
Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1
Basic rules for addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2
Address assignment and addressing after expansion
or conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Instructions for commissioning with Siemens SIMATIC STEP 7 . . . . . . . . . . .
Preparing for commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.1
Import device master file (GSDML) and symbol files . . . . . . . . . . .
2.5.2
Select GSDML file (compatibility table) . . . . . . . . . . . . . . . . . . . . . .
2.5.3
Setting up an automation project . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.4
Setting up the controller system (PLC/Master) . . . . . . . . . . . . . . . .
2.5.5
Installing GSDML file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.1
Localise and identify CPX terminal in the network . . . . . . . . . . . . . .
2.6.2
Select CPX terminal (station selection) . . . . . . . . . . . . . . . . . . . . . .
2.6.3
Assign device name" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.4
Set up Prioritized Startup (Fast Startup") . . . . . . . . . . . . . . . . . .
2.6.5
Assigning or changing IP address . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.6
Use MAC addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.7
Determine port addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPX terminal configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.1
Allocate configuration table (insert bus nodes and modules) . . . .
2.7.2
Modifying the I/O address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.3
Modifying the diagnostics address . . . . . . . . . . . . . . . . . . . . . . . . .
Parametrisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8.1
Start parametrisation while switching on (system start) . . . . . . . .
2.8.2
Parametrisation of the CPX terminal with Siemens STEP 7 . . . . . . .
2.8.3
Parametrisation with the handheld . . . . . . . . . . . . . . . . . . . . . . . . .
2.8.4
Parametrisation via the Festo Maintenance Tool . . . . . . . . . . . . . . .
2.8.5
Bus node parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8.6
Application example for parametrisation . . . . . . . . . . . . . . . . . . . . .
Identification & Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration in the Remote Controller operating mode . . . . . . . . . . . . . . . .
Checklist for starting up the CPX terminal . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
23
25
216
216
218
219
221
221
222
224
225
227
228
228
230
233
235
239
242
243
244
244
249
249
251
253
254
260
260
261
263
264
267
268
2. Commissioning
2.1
General information
The configuration of the CPX bus nodes for PROFINET
depends on the control system used.
The basic procedure and the required configuration data are
presented in the following pages.
Switching on the power supply

Caution
Danger of malfunctions, damage or injuries to people
Before commissioning, ensure that the connected
elements (e.g. actuators) do not perform any undesired or
uncontrollable movements.
If the safety concept of your machine/system permits,
commission the CPX terminal with both operating voltages
but without compressed air. You can then test the CPX
terminal without triggering undesired reactions.
Note
Please observe the switchingon instructions in the manual
of your control system (PLC/IPC).
Separatesupply
If the control system and the field bus slaves have separate
power supplies, the devices must be switched on in the
following sequence:
1. Switch on the operating voltage supply of all bus
subscribers (I/O devices).
2. Switch on the operating voltage supply for the controller.
23
2. Commissioning
Addressing, configuration and parametrisation

Addressing
The address space of a CPX terminal in the PROFINET network

is limited. Determine the number of assigned inputs and
outputs before commissioning or configuring the CPX
terminal (see section 2.2 regarding address assignment and
section 2.3 regarding addressing).
Addressing the individual modules requires the higherorder
controller: PROFINET uses moduleoriented addressing,
i.e.each module is addressed separately (in contrast to
blockoriented addressing of other fieldbus systems).
The controller uses the following for addressing:
IP addresses and MACIDs
Fieldbus device names, in short device names.
Configuration
Configuration of a CPX terminal and the related CPX bus node

depends on the control system used. The fundamental
procedure, PROFINETspecific preparations and the main
configuration steps are depicted on the following pages
(seesection 2.6).
Parametrisation
A CPX terminal in the PROFINET network can be parametrised

through the control system (PLC/IPC), a handheld control unit
(CPXMMI) or the Festo Maintenance Tool (CPX FMT)
(seesection 2.8).
24
2. Commissioning
2.2
Address assignment
Note
The address space of a CPX terminal in the PROFINET
network is limited.
The CPX bus node for PROFINET provides the CPX terminal
with an address space of up to 64 bytes for inputs (I) and
64 bytes for outputs (O).
Each module of the CPX terminal occupies a certain
number of I/O bits, bytes or words in the context of
module communication.
Please refer to the following tables (Tab. 2/2 to Tab. 2/7)
for the number of I/O bytes occupied (of the respective
module).
Also, certain functions, e.g. the I/O diagnostics interface
(STI), reduce the number of available I/O bytes (in favour
of status or diagnostics functions).
Take account of this fact for the planning of your CPX
terminal.
Before starting up or configuring the CPX terminal, determine
the number of assigned inputs and outputs. Tab. 2/8 assists
you with this.
Use the configuration documents, the handheld control unit
(CPXMMI) or the Festo Maintenance Tool (CPXFMT) to
determine address assignment or terminal configuration.
In the handheld display, the individual modules of the CPX
terminal are displayed with the respective module identifiers.
Using the module identifier and the following tables, you can
determine the module type and, with it, the number of inputs
and outputs occupied by the module.
25
2. Commissioning
Module identifiers
Each module, including the bus node, has its own identifier,
the socalled module identifier. It serves to determine and
localise the module type, for example as part of
configuration. Apply the module identifiers from left to
right corresponding to the physical order as installed in the
CPX terminal in your configuration program (e.g. Siemens
SIMATIC STEP 7, see section 2.7).
In graphically oriented configuration programs, the module
identifiers are typically found in a separate listing of all
available hardware modules or field devices, e.g. in a module
directory or module catalogue.
Electric modules
Tab. 2/1 shows the assigned address space of the bus node
in the Remote Controller operating mode.
Tab. 2/2 to Tab. 2/4 give an overview of the assigned address
spaces of different electrical modules and of the bus node in
the remote I/O operating mode.
The address assignment within the individual CPX I/O
modules can be found in the manual for the I/O module
(P.BECPXEA ...).
Details on the CP interface can be found in the manual for the
CP interface (P.BECPXCP...).
Configuration
of the bus node
In the remote controller (RC) operating mode, only the

identifier of the bus node will be configured (see Tab. 2/1).
In the remote I/O (RIO) operating mode, the identifiers of
the bus node (including diagnostics mode), the CPX
modules and, if present, the pneumatics modules are
configured (see Tab. 2/2).
26
2. Commissioning
Electric modules bus node
Module type Module

identifier 1)
Allocated address
space
(Designation)
(Name)
inputs
outputs
Bus node for PROFINET IO

in remote controller operating mode
with setting of datafield size
8 byte I / 8 byte O (see Tab. 1/4)
CPXFB33
CPXMFB34
CPXMFB35
e.g. FB33RC
ProfiNet I/O
bus node 1)
8 byte/
32 I
8 byte/
32 O

in remote controller operating mode
with setting of datafield size
16 byte I / 16 byte O (see Tab. 1/4)
CPXFB33
CPXMFB34
CPXMFB35
e.g. FB33RC
ProfiNet I/O
bus node 1)
16 byte/
64 I
16 byte/
64 O
1)
Module identifier in the handheld unit or in the hardware configuration of the programming software
Note: In the handheld, the bus node is designated with FB33RC ProfiNet I/O bus node" or
FB34RC ProfiNet RJ45 bus node" or FB35RC ProfiNet FOC bus node"
Tab. 2/1:
Address assignment of the bus node in the remote controller operating mode
Electric modules bus node
Module
type
(Designation)
(Name)

In Remote I/O operating mode:
without diagnostics access
CPXFB33
CPXMFB34
CPXMFB35

with status bits [Status]

with I/O diagnostic interface
[System Table Interface, STI]
Module
identifier 1)
Allocated address
space
inputs
outputs
e.g. FB33RIO
ProfiNet
remote I/O 1)
CPXFB33
CPXMFB34
CPXMFB35
e.g. FB33RIO
ProfiNet re
mote I/O 1)
[Status]
2 byte/
8 (16) I 2)
(8 bit
used)
CPXFB33
CPXMFB34
CPXMFB35
e.g. FB33RIO
ProfiNet
remote I/O 1)
[STI]
2 byte/
16 I
2 byte/
16 O
1)
Note: In the handheld, the bus node is designated with FB33RIO ProfiNet Remote I/O"
or FB34RIO ProfiNet RJ45 Remote I/O" or FB35RIO ProfiNet FOC Remote I/O"
(independent of the diagnostics mode)
2) Diagnostics mode status bits assigned 16 I or 2 bytes of address space (8 I or 8 bits remain unused)
Tab. 2/2:
Address allocation of the bus nodes for the remote I/O operating mode
27
2. Commissioning
Electric modules
Module
type
(Designation)
(Name)
Digital 4input module
CPX4DE
Module
identifier 1)
Allocated address
space
inputs
outputs
4DI
Input modules
1 byte/
4 (8) I 3)
CPX8DE
8DI
Input modules
1 byte/
8I

with channel diagnosis
CPX8DED
8DID
Input modules
1 byte/
8I
Digital 8input module, nswitching:
CPX8NDE
8NDI
Input modules
1 byte/
8I
CPX16DE
16DI
Input modules
2 byte/
16 I

with channel diagnosis
CPX
M16DED
16DID
Input modules
2 byte/
16 I
Digital 4way output module
CPX4DA
4DO
Output modules
1 byte/
4 (8) O 2)
Digital 8output module
CPX8DA
8DO
Output modules
1 byte/
8O
Digital 8output high current output

module
CPX8DAH
8DOH
Output modules
1 byte/
8O
Digital multi I/O module
CPX8DE8DA
8DI/8DO
Multi I/O mod
ules
1 byte/
8I
1 byte/
8O
Analogue 2input module
CPX2AEUI
2AI
Analogue Input
2 words/
32 I
Analogue 2way output module
CPX2AAUI
2AO
Analogue
output
2 words/
32 O
1)
2)
4way modules (CPX4DE and CPX4DA) occupy 8 I or 8 O or 1 byte of address space (4 I/O or 8 bits of
address space remain unused)
Tab. 2/3:
28
Address assignment of electric CPX modules (overview; bus node in remote

I/O operating mode) part 1
2. Commissioning
Electric modules
Module
type
(Designation)
(Name)
Analogue 4way input module 2)
CPX4AEI

(Temperature module for RTD sensors)
Module
identifier 1)
Allocated address
space
inputs
outputs
4AII
Analogue Input
4 words/
64 I
CPX4AET
4AIT
Analogue Input
Temp.
2 words
or
4 words/
32/64 I 3)

(Temperature module for TC sensors)
CPX4AETC
4AITC
Analogue Input
Temp.
4 words/
64 I
Analogue 4way input module

with pressure sensor 2)
(Measuring range 1 ... +1 bar)
CPX4AE
PB2
4AIPB2
Analogue Input
Press.
4 words/
64 I
Analogue 4way input module

with pressure sensor 2)
(Measuring range 0 ... 10 bar)
CPX4AE
PD10
4AIPD10
Analogue Input
Press.
4 words/
64 I
CPInterface 2)
CPXCP4FB
CPI
CP interface
max.
8 words/
128 I4)
max.
8 words/
128 A4)
1)
2)
No support of the FSU function (Module can be used in the FSU mode;
but the fast startup of the CPX system is not guaranteed; the shorter startup times might not be
reached)
3) number of inputs which can be switched between 2 and 4
4) Address space assignment dependent on the string allocation (4 bytes I or 4 bytes O per string)
Tab. 2/4:
Address assignment of electric CPX modules (overview; bus node in remote

I/O operating mode) part 2
29
2. Commissioning
Pneumatic interfaces and pneumatic modules

Tab. 2/5 ... Tab. 2/7 give an overview of the assigned address
spaces of various pneumatic interfaces and modules.
Configuration of the
pneumatics (valves)
The valves are configured according to the pneumatic

interface used:
Valves of type 03 (Midi/Maxi), type 12 (CPA) and

type 44/45 (VTSA/VTSA F or ISO):
When extensions are added to the valve side, only one
configuration is required for the pneumatic interface. In
the pneumatic interface, the number of valve coils is set
using a DIL switch.
Valves of type 32 and 33 (MPA, MPAF, MPAP and

MPAFP or VPPM pneumatic modules):
From the technical point of view, the individual MPA
pneumatic modules each represent an electric module for
controlling the attached valves.
A configuration is required for each pneumatic module of
type MPA... or VPPM:
} Pneumatic modules of type MPA1 each occupy 1 byte
O or 8 outputs regardless of how many valves are
attached to the pneumatic module.
} Pneumatic modules of type MPA2 each occupy 1 byte
of O or 8 outputs, but only 4 bits are used.
} Pneumatic modules of type MPAP or MPAFP each
occupy 2 bytes of I or 16 inputs.
} Pneumatic modules of type VPPM each occupy 4
bytes of address space, i.e. 2 bytes of I / 2 bytes of O or
16 inputs and 16 outputs.
210
2. Commissioning
Pneumatic modules of type MPAP or MPAFP and VPPM

are analogue modules. Observe the order of the modules
in addressing or I/O mapping (see Tab. 2/9).
Additional information on the pneumatics can be found in the
corresponding Pneumatics descriptions (see document
overview Descriptions of the CPX terminal" in the CPX
system description P.BECPXSYS...).
The descriptions for the pneumatic valve terminal (Midi/Maxi,
CPA, MPA and VTSA/VTSAF or ISO) contain the address
assignment within the pneumatic modules.
For further information on MPA pneumatic modules
and the pneumatic interfaces: see manual for the CPX I/O
modules (P.BECPXEA...).
211
2. Commissioning
Pneumatic interface for

MPA/MPAF and related
modules
Module type
Pneumatic interface for MPA or

MPAF valves (type 32/33)
VMPAFBEPL...
MPA1 pneumatic module

(Type 32/33: 18V...)
without electrical isolation
(Designation of the
electronic module)
Module
identifier1)
Allocated address
space
inputs
outputs
VMPA1FBEMS8
[8DO]
MPA1S
Valve module
1 byte/
8O

(Type 32/33: 18V...)
with electrical isolation
VMPA1FBEMG8
[8DO]
MPA1G
Valve module
1 byte/
8O

(Type 32/33: 14V...)
without electrical isolation
VMPA2FBEMS4
[4DO]
MPA2S
Valve module
1 byte/
4 (8) O 2)

(Type 32/33: 14V...)
with electrical isolation
VMPA2FBEMG4
[4DO]
MPA2G
Valve module
1 byte/
4 (8) O 2)

(Type 32/33: 18V...)
without electrical isolation,
with diagnostic function D2
VMPA1FBEMS
D28
[8DO]
MPA1SD
Valve module
1 byte/
8O

(Type 32/33: 18V...)
with electrical isolation,
VMPA1FBEMG
D28
[8DO]
MPA1GD
Valve module
1 byte/
8O

(Type 32/33: 14V...)
without electrical isolation,
VMPA2FBEMS
D24
[4DO]
MPA2SD
Valve module
1 byte/
4 (8) O 2)

(Type 32/33: 14V...)
with electrical isolation,
VMPA2FBEMG
D24
[4DO]
MPA2GD
Valve module
1 byte/
4 (8) O 2)
1)
2)
4way modules MPA2 always occupy 8 I (1 byte) of address space (4 I or 8 bits remain unused)
Tab. 2/5:
212
Overview of CPX pneumatic interfaces and pneumatic modules (part 1)
2. Commissioning
Pneumatic interface for

MPA/MPAF and related
modules
Module type
Module
identifier1)
(Name)
Allocated address
space
inputs
outputs
VPPM proportionalpressure regu

VPPM6...1...
lator (type 32; 2 bar, 6 bar, 10 bar,
[2AI/2AO]
not equipped" or vacant position) 2) 3)
VPPM
Proportional
valve ...
1 word/
16 I
1 word/
16 O
MPAP pressure sensor module 2) 3)

VMPA...FBPS...
[2AIP]
MPAP
Analogue
input press.
1 word/
16 I
MPAFP pneumatic interface with

pressure sensor 2) 3) 4)
VMPAFFBEPLPS
[1AIP]
MPAFP
Analogue
input press.
1 word/
16 I
1)
2)
No support of the FSU function (Module can be used in the FSU mode; but the fast startup of the
CPXsystem is not guaranteed; the shorter startup times might not be reached)
3) Pneumatic modules of type MPAP or MPAFP and VPPM are analogue modules.
Observe the order of the modules in addressing or I/O mapping (see Tab. 2/9).
4) MPAFP is also called end plate" with pressure sensor or pressure sensor plate
Tab. 2/6:
213
2. Commissioning
Pneumatic interfaces for

Midi/Maxi, CPA, VTSA/VTSAF
(ISO)
Module type
Pneumatic interface for Midi/Maxi

valves (type 03: 1......)
with setting: 2)
1...8 valve coils
1...16 valve coils
1...24 valve coils
1...32 valve coils (26 can be used)
CPXGP034.0
Pneumatic interface for CPA valves

(type 12: 1......)
with setting: 2)
1...8 valve coils
1...16 valve coils
1...24 valve coils (22 can be used)
CPXGPCPA10
CPXGPCPA14
Pneumatic interface for VTSA or

VTSAF pneumatic (ISO, type 44/45:
1......) with adjustment: 2)
1...0.8 valve coils
1...16 valve coils
1..0.24 valve coils
1...0.32 valve coils
VABA10S6x1
1)
2)
3)
Module
identifier1)
(Name)
Allocated address
space
inputs
TYPE 3
Pneumatic
interface
CPA 10/14
Pneumatic
interface
VTSA
Pneumatic
interface,
ISOplugin or
type 44 or
type 45 3)
outputs
1 byte/8 O
2 bytes/16 O
3 bytes/24 O
4 bytes/32 O
1 byte/8 O
2 bytes/16 O
3 bytes/24 O
1 byte/8 O
2 bytes/16 O
3 bytes/24 O
4 bytes/32 O
Setting with DIL switch in the pneumatic interface
Display text (module identifier) dependent on the version of the handheld unit
Tab. 2/7:
214
2. Commissioning
Calculation of the address allocation

Use Tab. 2/8 to calculate the address assignment or number
of inputs and outputs of your CPX terminal.
Input/output modules and system diagnosis
inputs
outputs
1. Status bits or I/O diagnostic interface1)
_____ I
_____ O
2. Number of input modules CPX4DE
+ __ x 8I2)
_____ I
3. Number of input modules CPX8DE, 8DED,8NDE
+ __ x 8 I
_____ I
4. Number of input modules CPX16DE, (M)16DED
+ __ x 16I
_____ I
5. Number of output modules CPX4DA
+ __ x 8O2)
_____ O
6. Number of output modules CPX8DA, 8DAH
+ __ x 8 O
_____ O
7. Number of multiI/O modules CPX8DE8DA
+ __ x 8 IO
_____ I
_____ O
8. Number of analogue input modules CPX2AEUI
+ __ x 32 I
_____ I
9. Number of analogue input modules CPX4AEI
+ __ x 64 I
_____ I
+
_____ O
_____ O
_____ O
_____ O
10.Number of analogue output modules CPX2AAUI + __ x 32 O

11.Number of analogue input modules CPX4AET + __ x 32 I/ x 64 I
_____ I
12.Number of analogue input modules CPX4AETC
+ __ x 64 I
_____ I
13.Number of analogue input modules CPX4AEP...
+ __ x 64 I
_____ I
_____ I
14.Number of inputs and outputs of other modules

+ __ IO
(e.g. CP interface, VPPM/MPAP/MPAFP pneumatic module)
15.Midi/Maxi, CPA and VTSA/VTSAF pneumatic interface:
Number of configured valve magnet coils (+ 8 O ... 32 O; 32 O (Midi/
Maxi, VTSA/VTSAF) or 24 O (CPA) are configured at the factory)
16.Number of MPA1 or MPA2 pneumatic modules
Total sum of inputs/outputs to be configured
Total from 1 to 15 (max. 512 I and 512 O)
1)
2)
+ __ x 8 O2)
= _____ I
= _____ O
Number of occupied inputs/outputs: see Tab. 2/2

4way modules CPX4DE and CPX4DA as well as MPA2 pneumatic modules always occupy 8 inputs or
outputs (1 byte; available address space remains partially unused)
Tab. 2/8:
Identifying the assigned address space (total of inputs and outputs)
215
2. Commissioning
2.3
2.3.1
Addressing
Basic rules for addressing
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.
Observe the instructions regarding address assignment in

section 2.2.
The address assignment of the inputs does not depend

on the address assignment of the outputs.
Counting moduleoriented, from left to right

(corresponding to the physical sequence)
Addressing bytebybyte: Modules with less than 8 bits

occupy 8 bits or 1 byte of address space, but do not use
all this space.
The I/Os of different module types are assigned

separately from each other. Observe the sequence of
addressing: see Tab. 2/9.
Note
If necessary, status bits or the I/O diagnostic interface can
be activated by DIL switch (see Tab. 1/2):
If the 8 status bits are activated, they will occupy the
first 16 inputs in the address range (8 used).
If the I/O diagnostic interface is activated, it will occupy
the first 16 inputs and 16 outputs in the address range.
216
2. Commissioning
Sequence of addressing
Description
1.
Status bits or I/O diagnostic

interface 1)
Delivers status and diagnostic information; activate through

DIL switches; occupies the first 16 inputs or inputs and
outputs 2)
2.
Analogue modules
Modules with analogue inputs/outputs
3.
Technology modules
e.g. CP interface, front end controller (CPXFEC),

CoDeSysController (CPXCEC, CPXCEC...)
4.
Digital modules
Modules with digital inputs/outputs
1)
2)
See also note above as well as Tab. 1/2 and Tab. 2/2.
Depending on the setting, you can also occupy this address space with modules
(see also following information).
Tab. 2/9:
Sequence of addressing
If the status bits or I/O diagnostic interface are activated
later, that is, after initial commissioning, the module
configuration for the first 16 inputs and outputs must be
adjusted.
Move the modules originally configured in this address
space into another area. Configuration of these modules
must be repeated, if necessary (see also section 2.7
regarding configuration with PROFINET configuration and
programming software, e.g. Siemens SIMATIC STEP 7).
217
2. Commissioning
2.3.2
Address assignment and addressing after expansion or conversion

A speciality of the CPX terminal is its flexibility. If the demands
placed on the machine/system change, the equipment fitted
on the CPX terminal can also be modified.
Caution
If the CPX terminal is extended or converted at a later
stage, the input/output addresses may be shifted. This
applies in the following cases:
if additional modules are inserted between existing
modules.
if existing modules are removed or replaced by other
modules which have more or fewer input/output
addresses.
Interlinking blocks (CPA) or pneumatic manifold blocks
(midi/maxi) for singlesolenoid valves are replaced by
interlinking blocks/manifold blocks for doublesolenoid
valves or vice versa (see Pneumatics description).
if additional manifold subbases (CPA) or subbases
(Midi/Maxi) are inserted between existing subbases.
The diagnostic mode (status bits or the I/O diagnostic
interface) is activated/deactivated.
218
2. Commissioning
2.4
Instructions for commissioning with Siemens SIMATIC STEP 7

Commissioning of a CPX terminal requires an exact
procedure, since, possibly for each station, i.e. for each I/O
device in the PROFINET network, different configuration
specifications are required due to the modular structure.
The following sections describe the basic configuration steps
with the SIEMENS PLC SIMATIC S7 and the Siemens SIMATIC
STEP 7 configuration and programming software.
Operation of the STEP 7 software is assumed to be known in
the following.
Other controller systems may require other settings or a
different procedure.
Note
Please observe the configuration instructions in the
manual of your control system (PLC/IPC).
The illustrations and specifications in this description refer to

the following variants:
for the remote I/O and remote controller operating

modes:
Controller (PLC/CPU) Siemens SIMATIC S7317

with FW V. 2.5.x
GSDML/PNIO specification V. 2.1
Control software Siemens STEP 7 V. 5.4
for the Prioritized Startup" operating mode

(Fast Startup):
GSDML/PNIO specification V. 2.2

Controller (PLC/CPU) Siemens SIMATIC S7319
with FW V. 2.7.x
219
2. Commissioning
PROFINETStack V. 3.0.x (FSU version)
Control software Siemens STEP 7 V. 5.4

with Service Pack SP 4
Please take information on other variants from the documents

on your controller and control software.
In case of technical problems, please first contact the
respective manufacturer. In cases of doubt, your local Festo
Service is happy to help you further.
Note
There are different configuration programs available for a
Siemens PLC. Observe the corresponding procedure for
your configuration program.
Caution
Danger of malfunctions, damage or injuries to people
A valve terminal with defective configuration will also be
put into operation. However, only the modules which have
been correctly configured for type and position will be
activated.
Before commissioning, ensure that the connected
elements (e.g. actuators) do not perform any undesired or
uncontrollable movements.
If necessary, disconnect the load power supply and
compressed air supply.
See also section 2.11: Checklist for commissioning the
CPXterminal.
220
2. Commissioning
2.5
Preparing for commissioning

The following sections describe the PROFINETspecific
preparation of commissioning with the SIEMENS PLC
SIMATICS7 and the Siemens SIMATIC STEP 7 configuration
and programming software.
2.5.1
Import device master file (GSDML) and symbol files

A device master file (GSD) in XML format (GSDML) is needed
for configuration and programming of the CPX terminal.
TheGSDML includes all the required information for the
configuration and adjustment of the CPX terminal using
configuration and programming software, e.g. STEP 7.
Source
The current GSDML file for CPX terminals can be found on the
Festo website at:
www.festo.com/fieldbus: Section PROFINET (GSDML)"
File download
Upload the current GSDML file to your controller system:
Click on the download arrow in the section PROFINET

(GSDML)", and save the file FestoGSDML.exe".
Double click on the saved file FestoGSDML.exe" to

unpack the contents (selfunpacking ZIP file):
one or more GSDML files:

GSDMLV...FestoCPX.. .xml
(bilingual, English/German, see Tab. 2/2)
Several symbol files for Festo CPX terminals:
Pb_cpx_...bmp
(bitmaps, see Tab. 2/1)
221
2. Commissioning
If applicable, a Read Me" file with notes

on the current GSDML versions:
Readme GSDML Versions.txt
Observe the notes in the Read Me" file as well as the

instructions in section 2.5.2 before installing the GSDML file.
Installation of the GSDML file is explained in section 2.5.5.
Symbol files
The symbol files serve to depict Festo CPX terminals in your

configuration software. Normally, the control system
automatically includes the symbol files (during installation of
the GSDML file, see section 2.5.5).
Normal operating
status
Diagnostic case
Special operating
status
File: Pb_cpx_n.bmp
File: Pb_cpx_d.bmp
File: Pb_cpx_s.bmp
Tab. 2/1:
2.5.2
Symbol files for representation of CPX terminals

in the configuration and programming software
Select GSDML file (compatibility table)

Using the following compatibility table, select the required
GSDML file for your system and application purpose.
222
2. Commissioning
GSDML file
Bus node
Controller software
Functional range
(Version)
(CPX revision code;

see name plate) 4)
(PLC software status)
(Extract)
GSDML file
V. 1.0 1)
Rev 07
Siemens STEP 7:
V. 5.3, Service Pack SP 3
PROFINETRT basic
logicfunction,
CPXconfiguration and
diagnostics over PLC
GSDML file
V. 2.1 2)
Rev 07 Rev 11 5)
Siemens STEP 7:
up to Version 5.4,
Service Pack SP 2,
Hotfix 2 or SP 3.1
LLDP, access via SNMP,

expansion of module
support
GSDML file
V. 2.2 3)
Rev 12 Rev 18 6) 7)
Siemens STEP 7:
from Version 5.4,
Service Pack SP4
Fast Startup" (FSU),

expansion of module
support and diagnostic
function, in particular
regarding FOC
diagnostics
1)
2)
3)
4)
5)
6)
7)
GSDML file V. 1.0 is no longer available for download:

please use GSDML file V. 2.1 (or possibly 2.2)
For example, GSDML file GSDMLV2.1FestoCPX20090702.xml";
Please observe: Version 2.1 is not officially approved and published; Festo therefore
accepts no responsibility for malfunctions and effects connected to them
For example, GSDML file GSDMLV2.2FestoCPX20100517.xml";
required for the Prioritized Startup" operating mode (Fast Startup", FSU):
The CPX revision code is located on the name plate (see section 1.2).
The GSDML file V. 2.1 also supports bus nodes with Rev 12 to Rev 14:
But the FSU function is supported only by version 2.2 (and bus nodes from Rev 12).
The GSDML file V. 2.2 also supports bus nodes with Rev 07 to Rev 11:
The FSU function is not supported by these bus nodes (with Rev 07 to Rev 11).
Individual bus nodes with Rev 13 do not have the required hardware for
support of the FSU function (HW revision > 8): Check the hardware revision status
using FMT or contact your local Festo service.
Tab. 2/2:
Compatibility of GSDML file, bus nodes and controller

The current GSDML file for CPX terminals can be found on the
Festo website at:
www.festo.com/fieldbus
If you have questions or technical problems, please contact
your local Festo service or the Festo telephone hotline.
223
2. Commissioning
2.5.3
Setting up an automation project

1. Start the Siemens SIMATIC controller: Start > Programs >
SIMATIC > SIMATIC Manager.
(The program path of your SIMATIC controller can be
different from the example shown here).
Note
These instructions refer to the English language version of
the Siemens SIMATIC controller and the STEP 7
configuration and programming software.
Other language versions usually use other designations for
the program and function calls and menu items mentioned
here.
2. Create a new project in the SIMATIC Manager: File > New >
New...
3. Enter a project name (e.g. CPX_FB33) and confirm the
input with OK.
4. Select the controller used (PLC/Master): Insert >

Station > ... (e.g. SIMATIC 300 Station).
5. Open the project by clicking on the plus symbol (on the

left next to the project symbol and the project name).
224
2. Commissioning
2.5.4
Setting up the controller system (PLC/Master)

1. Click once on the station symbol (on the left next to the
station name) and afterwards double click on the
hardware symbol in the Object name" column.
The hardware configuration window HW Config
(station configuration) is displayed.
2. Open the Hardware Catalogue (Catalogue View, 1 in the
adjacent screenshot).
1
3. Select your controller system (PLC/Master) in the
Hardware Catalogue (e.g. SIMATIC 300, 1 in Fig. 2/5):
Click on the plus symbol in order to expand the selection.
4. Open the rack directory (e.g. RACK300, 2 in Fig. 2/5).
5. Double click on the rack rail symbol (e.g. RAIL, 2 in
Fig. 2/5).
A child window (with rack rail symbol in the header)
opens in the lefthand area of the HW Config window
( 3 or 4 in Fig. 2/5).
The child window symbolises the rack rail (profile rail) of
your controller system. You compile the individual
elements of your controller in this child window and thus
form the basis for your PROFINET automation system.
225
2. Commissioning
3
1
4
2
1 Select controller system

2 Insert rack rail
3 Set up controller system in the rack rail window
Fig. 2/5: Setting up the controller system (PLC/Master)
inserting rack rail (rail)
6. Add your CPU and a PROFINET IO system to the hardware
configuration: Drag the corresponding catalogue elements
(symbols) into the Rack Rail window ( 3 or 4 in Fig. 2/5).
226
Alternatively, you can also double click on the catalogue

element: Select the next free row (insert position, slot) in
the rack rail window before you make the double click.
Row 1 (Slot 1) is reserved and cannot be used for the
configuration.
2. Commissioning
2.5.5
Installing GSDML file

You install the GSDML file in the course of the following steps:
GSDMLV...FestoCPX...xml
Source and remarks for the selection:

see section 2.5.1.
1. Start the installation function from the STEP7 menu:
Options > Install GSD File ...
2. Update the hardware catalogue from the STEP7 menu:
Options > Update Catalogue.
All available CPX modules in the hardware catalogue are
displayed under PROFINET IO > Additional Field Devices >
Valves > Festo CPX Terminal.
You can start the selection and configuration of your
modules (see section 2.6).
227
2. Commissioning
2.6
Basic hardware configuration

The following sections describe hardware configuration with
the SIEMENS PLC SIMATIC S7 and the Siemens SIMATIC
STEP 7 configuration and programming software.
2.6.1
Localise and identify CPX terminal in the network

Use the function Node flashing test" (flashing) to localise
your CPX terminal in the network: The LEDs TP1 and TP2 flash
simultaneously. This function helps you with the allocation of
the device name. You can also use this function to test
whether there is a logical data connection to the CPX
terminal.
1. Start the PROFINET hardware configuration in your
configuration and programming software (e.g. HW Config
in Siemens STEP 7).
2. Start the Assign Device Name" function from the STEP7
menu: PLC > Ethernet > Assign Device Name.
The Assign Device Name" window is displayed.
3. If the CPX terminal is not displayed, start the refresh of
the display: To do this, click on Update".
The network is searched and the network participants
found are listed (under Available devices").
4. Mark your searchedfor CPX terminal in the list
(recognisable e.g. from the MACID) and click on
Flashingon".
The LEDs TP1 and TP2 of the bus node at the found
CPXterminal flash for clear identification.
228
2. Commissioning
You can assign a device name to the CPX terminal in the

next step. This device name is also stored on the memory
card (provided it is inserted) of the bus node.
5. Enter a device name in the Device name" field
(e.g. CPX or CPX01) and confirm the entry by clicking on
Assign name".
229
2. Commissioning
2.6.2
Select CPX terminal (station selection)

configuration and programming software (e. g. HW Config
in Siemens STEP 7).
3
Fig. 2/6: Station selection using Siemens STEP 7 HW Config
2. If the Hardware Catalogue has not been opened:
Click on the catalogue symbol ( 1 in Fig. 2/6) or use the
keyboard combination [Ctrl] + [K].
The hardware catalogue is displayed.
230
2. Commissioning
Select station"
(station symbol)
3. In the Hardware Catalogue (HW Config), open the folder:
\PROFINETIO\Additional Field Devices\Valves\Festo

CPXTerminal" (English language version of the software)
PROFINETIO\Weitere Feldgerte\Ventile\Festo
CPXTerminal (German language version of the software)
Note
If the directory ValvesFesto CPXTerminal" is not
displayed (see Fig. 2/7), repeat installation of the device
master file (GSDML, see section 2.5.5).
Fig. 2/7: Station selection selection of the station symbol

(Festo CPX terminals)
4. Choose the station symbol corresponding to your
application using the following Tab. 2/3 dependent on:
Operating mode of the bus node

(see section 1.4.2 or Tab. 1/1)
Additional function Fast Startup"

(for short FSU, see section B.1.3)
CPX revision code of the bus node

Connection technology (M12 or RJ45 or SCRJ)
231
2. Commissioning
Example: With use of a bus node CPXFB33 with Rev 14

in the remote I/O operating mode, without the
additional function Fast Startup", open the station
symbol CPX ( 1 in Tab. 2/3).
CPX revision code
Operating mode Additional function
Station symbol 1
of the bus node
of the bus node
(Field device group)
Fast Startup (FSU)
FB33 (M12),
FB34 (RJ45)
FB35 (SCRJ)
Rev 09 Rev 11
Remote I/O
n/a
CPX Rev 11 1)
n/a
Rev 12 Rev 18
Remote I/O
No
CPX
CPXFO
Yes, with FSU
CPX FSU 2)
CPXFO FSU 2)
Rev 09 Rev 11
Remote controller
n/a
CPX RC
n/a
Rev 12 Rev 18
Remote controller
n/a
CPX RC
CPXRCFO
1)
2)

Tab. 2/3:
Station symbol selection as part of CPX terminal configuration

with Siemens SIMATIC STEP 7
5. Drag the selected station symbol 1 onto the bus line of
the PROFINET IO system ( 2 in Tab. 2/3).
The CPX terminal is displayed as a symbol ( 3 see also
Tab. 2/1) and connected to the bus of the PROFINET IO
system.
232
2. Commissioning
2.6.3
Assign device name"

The following steps and related illustrations differ by
controller, firmware and software used.
Use of the device name
You can assign or change a device name for the CPX

terminal in the next step. This device name is also stored on
the memory card (provided it is inserted) of the bus node.
Using this device name, you can also directly address" the
CPX terminal, e.g. in your automation programs. Alternatively,
you can also use the IP address or the MACID for addressing
(information about IP addressing can be found in the sections
2.6.5 and 2.6.6).
If you have allocated a device name in the course of localising
and identifying the CPX terminal (see section 2.6.1), you can
skip the steps 6. and 7..
Assign device name
6. Double click on the symbol of the CPX terminal 3.

The Properties CPX" window is displayed (see Fig. 2/8).
233
2. Commissioning
Fig. 2/8: CPX terminal characteristics device name

7. In the Device Name" field ( 1 in Fig. 2/8) or Name"
( 1 in Fig. 2/9), enter a unique device name for the CPX
terminal: e.g. CPX01, Stationxy or an applicationspecific
designation.
234
2. Commissioning
Fig. 2/9: CPX terminal properties device name and activation of the Prioritized
Startup" (Fast Startup)
2.6.4
Set up Prioritized Startup (Fast Startup")

In the next steps, you can set up the Prioritized Startup"
function. This operating mode allows faster system startup
times.
Prioritized Startup" is also designated Fast Startup"
(abbreviated FSU).
If you do not want to use Fast Startup", you can omit steps
8. to 20.
235
2. Commissioning
Note
The Fast Startup" operating mode has restrictions
regarding commissioning and parametrisation. Detailed
information can be found in the corresponding chapters.
Also observe the instructions in section 2.8 and
section B.1.3 regarding Fast Startup".
Activate Fast Startup"
8. Place a check in front of Prioritized Startup" 2 in the

window Properties CPX" (see Fig. 2/9).
9. Choose the tab IO Cycle" ( 1 in Fig. 2/10).
1
2
Fig. 2/10: FastStartup" settings adaptation of the I/O cycle time (Update time)
236
2. Commissioning
10. Make sure that the following values are set for IO Cycle":
Update time 2:
Mode:
Update time:
Fixed
update
time
1,000 ms
Response monitoring time 3:

Number of update cycles:
Response monitoring time:
3
3,000 ms
11. Confirm your entries by clicking on OK".

12. Click on the symbol of the CPX terminal to be configured
in the PROFINET Hardware Configuration (HW Config,
3 in Fig. 2/6).
13. The configuration table is displayed:
You will find the configuration table below the schematic
representation of the PROFINET IO system. If necessary,
increase the size of this area of the HW Config window
(see Fig. 2/6 or 2 in Fig. 2/17).
14. Double click in the configuration line of the connection

(port) X1 TP1".
The window Properties CPX FSU Port 1" is displayed
(see Fig. 2/11).
15. Choose the Options" tab (1 in Fig. 2/11).
237
2. Commissioning
1
2
3
Fig. 2/11: FastStartup" settings Deactivation of the crossover detection

(Disable Autonegotiation)
16. Make sure that the following Transmission medium" for
Connection" 2 is set:
TP / ITP with 100 Mbps full duplex"
17. Deactivate the crossover detection 3:

Place a check in front of Disable Autonegotiation".
238
2. Commissioning
18. Also deactivate crossover detection in the counterpart

station, e.g. in the control system (PLC/Master).
Deactivation of crossover detection is required for a startup
of the CPX system.
Fast Startup" or Prioritized Startup" is possible only with
crossover detection deactivated.
19. Use a suitable network line for this connection, in this
case a crossed line, for example (if the crossover
detection is deactivated on both sides of the connection
and a connection between PLC or master and slave is
created).
20. Repeat the steps 14. to 19. for port X2 TP2.
2.6.5
Assigning or changing IP address

You can manually assign or change the IP address of the CPX
terminal in the next steps. The controller usually takes over
the allocation of an IP address (automatic addressing using
the DHCP server integrated in the controller).
If you would like to accept the specified IP address, you can
skip the steps 21. to 23..
Assigning or changing
IPaddress
21. Depending on the PROFINET environment, a different

procedure is required for entry or change of the IP
address:
Click on the Ethernet..." button for IP addressing

( 1 in Fig. 2/12).
For IP addressing, choose the tab Addresses"

( 1 in Fig. 2/13).
The Addresses" tab or the window Properties Ethernet
interface CPX" window is displayed (see Fig. 2/14 or
Fig. 2/15).
239
2. Commissioning
Fig. 2/12: CPX terminal characteristics addressing (part 1)

22. Manual addressing (if required):
Enter the IP address of the bus node
( 1 in Fig. 2/14 or Fig. 2/15).
240
2. Commissioning
241
2. Commissioning
23. Confirm your entries by clicking on OK" twice if

necessary.
Observe the basic addressing rules for the allocation of the
IPaddress, e.g. with respect to the use of private or public
address ranges. Also check that the IP address can be used in
your automation network (no duplicate address assignment
etc.).
The following IP address variants are available for addressing
the bus node or CPX terminal:
Factoryspecified (remanent") IP address (192.168.10.2)
Host system IP address
Dynamic IP address, assigned through DHCP
Static, customerspecific or userchangeable IP address
The dynamic IP address assigned through DCHP can be fixed,

if needed, and so becomes a customerspecific static IP
address.
2.6.6
Use MAC addressing
Use MAC addressing
Besides the IP addresses, the MACID of the bus node is

also available for addressing purposes (see 1 in Fig. 2/16).
The MACID is located on the name plate.
Fig. 2/16: CPX terminal characteristics MAC addressing
242
2. Commissioning
The MACID is a uniform worldwide identification of each

individual Ethernet device. The identification consists of a
Manufacturer ID" and a consecutive identification of the
Ethernet device, e.g. 000EF0123ABC. The highlighted
identification represents the Manufacturer ID", here Festo.
2.6.7
Determine port addresses
Determine port addresses Addresses of the input and output ports TP1 and TP2 can be
determined through the configuration table of the HW
Config window, for example.
243
2. Commissioning
2.7
2.7.1
CPX terminal configuration

Allocate configuration table (insert bus nodes and modules)
In the following steps, you take the bus node and individual
modules of your CPX terminal ( 1 in Fig. 2/17) from the
hardware catalogue into the configuration table ( 2 ).
The CPX modules are divided into fielddevice groups within
the Hardware Catalogue ( 4 in Fig. 2/17): analogue modules,
digital modules, pneumatic interfaces, pneumatic modules
and technology modules. In this environment, the CPX bus
nodes FB33, FB34 and FB35 form their own group (Bus
nodes").
The field device groups or Bus node and module folder" are
located under the station symbols ( 3 ).
in Siemens STEP 7).
2. If the Hardware Catalogue has not been opened:
Click on the catalogue symbol or use the keyboard
combination [Ctrl] + [K].
The hardware catalogue is displayed.
3. In the Hardware Catalogue, open the folder:
\PROFINETIO\Additional Field Devices\Valves\Festo

CPXTerminal" (English language version of the
software)
or
244
\PROFINETIO\Weitere Feldgerte\Ventile\Festo
CPXTerminal
2. Commissioning
If the folder ValvesFesto CPXTerminal"

is not displayed, repeat the installation of the device
master file (GSDML, see section 2.5.5).
2
Fig. 2/17: CPX terminal configuration with Siemens STEP 7 HW Config
4. Click on the symbol of the CPX terminal to be configured
in the PROFINET Hardware Configuration (HW Config, 1
in Fig. 2/17).
The configuration table ( 2 in Fig. 2/17) is displayed
(below the schematic representation of the PROFINET IO
system). If necessary, increase the size of this area of the
HW Config window.
245
2. Commissioning
The configuration table represents your CPX terminal.

This area of the HW Config window as well as the higherlevel
graphic representation is also designated as the Rack Rail
window. In the documentation for your control system, the
designation profile rail, mounting rack, or rail may be found
instead of rack rail".
Open station symbol
5. In the hardware catalogue, open the station symbol

( 3 ) corresponding to your application and the related
field device groups (bus node and module folder",
4 in Fig. 2/17).
Note
Open the same station symbol as with the station selection
in section 2.6.2.
Select and insert bus node 6. Pull the required catalogue elements, i.e. first the bus
node and then the modules of your CPX terminal
corresponding to the physical" sequence (as mounted,
from left to right) into the configuration table.
Note
Various catalogue elements are available for linking the
bus node: Observe the following sections.
Choose the required bus node catalogue element based
on the following Tab. 2/4 dependent on:
246
Operating mode of the bus node

Diagnostics mode of the bus node
2. Commissioning
Additional function Fast Startup"

(FSU, see Appendix B.1.3)
Connection technology (M12 or RJ45 or SCRJ)
1
2
3
Operating mode
Diagnostics mode
Additional function Field device group
of the bus node
[mode identification]
Fast Startup (FSU)
(station symbol)
FB33,
FB34
FB35
CPXFO
Without
diagnostics 1
1)
2)
CPX 1)
Yes, with FSU
CPX FSU 2) CPXFO FSU 2)
No
CPX 1)
CPXFO
Yes, with FSU
CPX FSU 2)
CPXFO FSU 2)
I/O diagnostics interface

[STI] 3
Remote controller
No
Status bits
[Status] 2
Remote I/O
No
CPX 1)
CPXFO
Yes, with FSU
CPX FSU 2)
CPXFO FSU 2)
n/a
n/a
CPX RC
CPXRCFO

Tab. 2/4:
Bus node selection as part of CPX terminal configuration

(PLC hardware configuration)
247
2. Commissioning
Example: When using the bus node from the previous

example (CPXFB33 with Rev 14) in the operating mode
remote I/O with diagnostics mode status bits but
without the additional function Fast Startup", choose
the bus node module FB33 with mode identification
Status (from the field device group Bus nodes"
underneath the CPX station symbol): FB33 PNIO module
[Status] ( 2 in Tab. 2/4).
Then pull the first (left) module of your CPX terminal

from the field device group onto line 2 in the
configuration table.
248
Check the setting of the DIL switches for operating

mode and diagnostics mode (see section 1.4.2):
Ensure that the setting for operating mode and
diagnostics mode selected through DIL switches at
the bus node matches the function of the catalogue
element.
Inserting modules
First pull the bus node onto the first line of the
configuration table (Slot" 1, 2 in Tab. 2/4, also
designated as function card position 1 or card slot 1).
Drag the next module to the respective next free row

of the configuration table.
Alternatively, you can also double click on the catalogue

element: Select the next free row in the rack rail window
before you make the double click.
2. Commissioning
2.7.2
Modifying the I/O address

1. Double click on the module name in the configuration
table.
The Properties ..." window is displayed.
2. Select the Addresses" tab.
3. Change the start address (Start") of the inputs or
outputs.
4. Confirm the entry with OK".
The modified address is displayed in the configuration
table.
2.7.3
Modifying the diagnostics address

The diagnostics address is automatically assigned by the
Siemens STEP 7 configuration and programming software
HW Config. A change is rarely required.
1. Doubleclick on Slot 0" in the configuration table.
The Properties CPX" window is displayed (see Fig. 2/18).
Fig. 2/18: Changing the diagnostics address with Siemens

STEP 7 HW Config
2. Select the Addresses" tab.
249
2. Commissioning
3. Enter the desired Diagnostic Address".

(The available address range depends on the controller
used see manufacturers documentation).
4. Confirm the entry with OK".
The modified address is displayed in the configuration
table.
Further information about diagnostics:
Summary of diagnostics options"
250
Section 3.1,
Section 3.5,
Diagnostics via PROFINET"
2. Commissioning
2.8
Parametrisation
You can individually set the behaviour of the CPX terminal
through parametrisation. We distinguish between the
following parametrisation variants:
System parametrisation, e.g. deactivating error messages

etc.
Module parametrisation (modulespecific and

channelspecific), e.g. module monitoring, settings for
errors, adjustment of debouncing times for the inputs,
etc.
Parametrisation of the diagnostics memory
A detailed description of the individual parameters as well as

basic information about application can be found in the CPX
system description (P.BECPXSYS...).
Parameter lists for the various CPX modules can be found in
the corresponding descriptions for the modules
(P.BECPXEA..., P.BECPXAX..., P.BECPXCP... etc.).
Note Module parameter in the operating mode FSU

In the Fast Startup" (FSU) operating mode, the module
parameters cannot be set through the control software
(exception: VTSAD pneumatics interface).
Use the Festo Maintenance Tool (FMT) or the handheld
(MMI) to make the required settings.
System parameters can be set in all operating modes, also
in the FSU operating mode, using the control software.
251
2. Commissioning
Note System start in the operating mode FSU

For the system start, the function System Start with Saved
Parameters" (Saved" or Stored Parameters") must be
activated to ensure that the parameters entered using FMT
or MMI are used.
This setting must be made at two positions:
in the bus node system parameters (using FMT or MMI)
in the system parameters of the control software
(e.g. Siemens STEP 7, see 1 in Fig. 2/19)
1
Fig. 2/19: System start in the operating mode FSU System
Start with Saved Parameters" (Saved" or Stored
Parameters")
252
2. Commissioning
2.8.1
Start parametrisation while switching on (system start)

The parametrisation at system start of the CPX terminal
is initially dependent on the setting of the system start
parameter. This parameter specifies whether the start
parametrisation will be loaded from the PROFINET I/O
Controller or from the CPX bus node.
Note
The start parameter set is loaded again (according to the
rules described above) after every interruption of the
network connection or of the power supply.
An exchange of individual CPX modules is therefore possible
without the need for new manual parametrisation.
Sequence of the start parametrisation when

switching on the CPX terminal
Sequence with system start parameter Default
Parameters":
The PROFINET I/O controller loads the start parameter set

into the CPX bus node.
The bus node then distributes the parameter set to the

modules.
It does not matter whether there is a memory card in the
bus node or not.
Sequence with system start parameter Saved

Parameters":
The CPX bus node distributes the saved (in the bus node)
start parameter set to the modules.
253
2. Commissioning
2.8.2
Parametrisation of the CPX terminal with Siemens STEP 7

Setting system parameters
in Siemens STEP 7).
Fig. 2/20: Setting system parameters with Siemens STEP 7
254
2. Commissioning
2. Mark the symbol of the CPX terminal on the PROFINET IO

system (see 1 Fig. 2/20). The configuration table now
shows the configuration of the CPX terminal.
3. Double click on line 0 of the configuration table 2. The
Properties CPX" dialogue window is displayed.
4. Select the Parameters" tab 3.
The list with the parameters and the currently active
values will be shown.
5. Click on the value (Value") of the parameter that you
would like to change.
A list with the possible values will be opened 4.
6. Change the parameter by clicking on the desired value
(Value").
7. Then confirm the change.
Note
System parameters monitoring KZS/KSA/KZV, UOUT/VAL
The shortcircuit/overload and undervoltage diagnostics
messages for the complete CPX terminal can be
suppressed using the monitoring system parameter
(function no. 4401).
The settings made separately for each module with the
CPX module parameter monitoring are not affected by the
setting of the system parameter monitoring.
Additional information on parametrisation can be found
inthe CPX system description (P.BECPXSYS...) in
Appendix B.
255
2. Commissioning
Setting module parameters

in Siemens STEP 7).
Fig. 2/21: Setting module parameters with Siemens STEP 7

2. Double click in the configuration table on the designation
of the module you would like to parametrise
( 1 in Fig. 2/21). The Properties ..." dialogue window is
displayed.
3. Click on the value (Value") of the parameter that you
would like to change. A list with the possible values will
be opened 2.
256
2. Commissioning
4. Change the parameter by clicking on the desired value

(Value").
5. Then confirm the change.
Note
Module parameters can refer to:
Properties of the complete module
Properties of an individual channel of a module
257
2. Commissioning
Parametrisation of the diagnostic memory

A maximum of 40 diagnostic messages can be saved in the
diagnostic memory. Using the handheld (CPXMMI) or the
Festo Maintenance Tool (CPXFMT), you can parametrise,
among other things, which messages are saved and how the
messages are saved.
Choose, for example, the memory duration or the diagnostic
memory mode (Entries remanent at Power ON") or
the memory procedure (Run/Stop" setting).
A short explanation of the major settings can be found in the
following sections. You can obtain further information in the
description for the CPXMMI or FMT.
Memory duration or diagnostic memory mode
(Trace parameters" > Entries remanent at Power ON" or
Diag.Buffer Mode"):
Active" or remanent":
The diagnostic messages remain saved when the
operating voltage is switched off or after a power failure.
Inactive" or not remanent":

The diagnostic messages are lost after the operating
voltage is switched off or after a power failure.
Memory procedure
(Trace parameters" > Run/Stop 1" or
Diag.Buffer Mode"):
Save first 40 entries" or Stop after 40 records..."

(Stop after 40 entries...):
The bus node saves the first forty diagnostic messages.
Additional, subsequent messages are not saved.
258
2. Commissioning
Save last 40 entries" or Record continually...":

Continuous saving of the diagnostic messages.
After the 40th message, the oldest message will be
overwritten.
Fault end filter

(Trace parameters" > Fault end filter" or
Diag.Buffer Error end")
Select whether a rectified fault (Outgoing fault") is to be
recorded in the diagnostic memory:
Record outgoing faults" or Record coming/going"

(Record incoming/outgoing faults):
When a fault occurs and is eliminated, the error number
and the time of the event are recorded.
Do not record outgoing faults" or Record coming only"

(Only record coming faults):
Only when a fault occurs are the error number and the
time of the event recorded. If the fault is eliminated, the
time of the event will not be recorded.
259
2. Commissioning
2.8.3
Parametrisation with the handheld

The handheld (CPXMMI) offers menudriven access to
parametrise the CPX terminal without configuration software.
If the handheld has write access to the parameters, you
cannot parametrise the following parameters via the bus:
System parameters
Module parameters
Information about operating the handheld can be found in the

description for the handheld P.BECPXMMI...
2.8.4
Parametrisation via the Festo Maintenance Tool

With the PC software Festo Maintenance Tool (CPXFMT), you
can conveniently parametrise the CPX terminal over a USB
connection.
You receive the necessary USB adapter with the CPXFMT
software.
Note
The last parametrisation set or received is always valid
until the restart of the bus node or CPX terminal.
After a restart, settings chosen through MMI or FMT must
be recreated, if necessary. See also section 2.8.1 (Start
parametrisation) and the instructions on system start in
the operating mode FSU (Fig. 2/19). Instructions on
parametrisation after replacement of a bus node can be
found in section 1.5.
260
2. Commissioning
2.8.5
Bus node parameter
Devicespecific parameters
Description/setting possibilities
Standard CPX parameter more detailed information:

see CPX system description (P.BECPXSYS...)
Monitoring SCS
Monitoring SCS
Monitoring Uout (VOUT)
Monitoring UVen (VVAL)
Monitoring SCS
Fail safe
Force mode
System start with external
parameters or default parameters
or with saved parameters
(Saved Parameters")
Note
The parameters of the diagnostic memory can only be set via
the CPXMMI or CPXFMT.
Filter diagnostic message

UOff/UVen
(Undervoltage, VOUT/VVAL)
Special bus node parameter setting options:

Inactive:
Undervoltage is reported over the network
Active:
Undervoltage messages are filtered and not reported over
the network; the undervoltage is displayed only through
flashing of the SF LED on the bus node.
Analogue process value

representation
(Intel/Motorola format)
Special bus node parameter defines the representation of

process values of the analogue modules setting options:
INTEL byte sequence (LSBMSB, Little Endian"; factory
setting):
Process values are depicted in the Intel format (least
significant bit to the left, most significant bit to the right)
MOTOROLA byte sequence (MSBLSB, Big Endian"):
Process values are displayed in the Motorola format
(highest value bit on the left, lowest value bit on the right)
This parameter can also be set via the I/O diagnostic interface
with the function number 4402 bit 7.
Value 0": Intel (LSBMSB; factory setting)
Value 1": Motorola (MSBLSB)
The settings of the byte sequence or of the process value
representation is dependent on your control system and the
related user programs: Choose the byte sequence used in
your control system.
Tab. 2/5:
Devicespecific parameters of the bus node
261
2. Commissioning
Note
Take into account the set bus node parameters in your
user programs also, in particular the analogue process
value representation" (byte sequence).
Note
Observe that the parameter Filter diagnostic message
UOUT/UVAL" is only available from Revision 14 (Rev 14")
ofthe PROFINET bus node.
If you use a bus node with an earlier revision, although the
parameters are displayed in Siemens STEP 7, they have no
effect.
262
2. Commissioning
2.8.6
Application example for parametrisation
1 Input for
1st sensor
(with default
parametrisation)
2 Parametrised
input for
2nd sensor
(see text)
1st sensor
2nd sensor
Fig. 2/22: Application example for parametrisation of input debouncing time and signal
extension time on the 2nd sensor
In the above application, packets are transported on a
fastmoving conveyor belt.
The input for the 2nd sensor is parametrised as follows for
improvement of the signal recording and processing:
Reduction of the input debouncing time from 3 ms

(factory setting) to 0.1 ms: Recording of shorter signals is
possible. This parameter is set for the complete module.
Signal extension time set to 50 ms: Reliable recording of
the signals by the controller.
The value of this parameter is set for the complete
module, but must be activated/deactivated separately for
each input channel.
263
2. Commissioning
2.9
Identification & Maintenance
The Identification and Maintenance" (I&M) function serves

as an electronic nameplate of the bus node and offers
uniform, nonproprietary access to devicespecific online
information via the internet.
Note
To use the I&M function, at least revision status 14
(Rev 14") is required (see name plate of the bus node).
Ifa bus node with an earlier version is used, the following
error message is displayed.
Fig. 2/23: I&M error message for bus nodes with revision
status (CPX revisions code) earlier than Rev 14"
264
2. Commissioning
Load identification properties in the field bus node

1. Click on Download Module Identification..." in the
PLC"menu (Target system > Load module identification).
The window Download Module Identification" is
displayed.
2. Enter your new identification properties in the fields
under Offline" (examples: see Fig. 2/24).
3. Make sure that, a check is entered in the check boxes under
Include" only if you want to load new I&M data into the bus
node.
Note
Remove the check under Include" if correct data are
already in the ONLINE" field; otherwise, these data will
be overwritten!
4. Confirm the entries with OK.
1 Deactivate checks, if applicable, so that correctly filledin ONLINE fields are not
overwritten.
Fig. 2/24: Selection of the I&M identification data for transfer to the bus node
265
2. Commissioning
Look at identification properties

1. Click on Module Information..." in the PLC" menu
(Target system > Module status).
The window Module Information" (module status)
isdisplayed.
2. In the General" tab, you will find the hardware revision
and the software/firmware status of the bus node.
Note
The detailed and possibly updated I&M specifications for
the hardware revision and for the firmware and software
status of the bus node might not be identical to the
higherlevel CPX revision code (Rev xy") located on the
name plate.
3. You will find further information, such as manufacturers
specifications, in the Identification" tab.
266
2. Commissioning
2.10 Configuration in the Remote Controller operating mode

If there is an FEC or CEC in your CPX terminal, you must
operate the bus node in the Remote Controller operating
mode. The bus node then occupies 8 or 16 input bytes and 8
or 16 output bytes (dependent on the switch position DIL 2.2:
see Tab. 1/4). These are available to the control program in
the FEC or CEC and to the PROFINET Master.
Configuration of the bus
node Remote Controller
operating mode
1. Ensure that DIL switch 1 of the bus node is in the

Remote Controller position (see section 1.4.2, Tab. 1/1).
DIL 1.1: ON
DIL 1.2: OFF
2. With DIL switch 2, set the required datafield size

(seeTab. 1/4).
3. Start your configuration and programming software,
e.g.Siemens STEP 7.
4. Open the hardware configuration, here: HW Config.
5. If you change an existing configuration: If necessary,
remove the existing bus nodes and all other (subordinate)
modules from this CPX terminal configuration.
6. Carry out the bus node selection (station selection) with
the station type CPX RC or CPXRCFO (see section 2.7.1).
The bus node is thus configured as Remote Controller.
Additional settings, such as change of the PROFINET device
name or IP address, can be made just as in the Remote I/O
operating mode.
267
2. Commissioning
2.11 Checklist for starting up the CPX terminal

If the safety concept of your machine/system permits, start
up the CPX terminal first with both operating voltages but
without compressed air. You can then test the CPX terminal
without triggering undesired reactions.
Note
Observe the general commissioning instructions in the
CPX system description and in the manual of your
controller.
Caution
The CPX terminal with bus node for PROFINET also starts
with incomplete configuration.
Check the configuration and address assignment of the
I/Os on the CPX terminal. In order to do this, you can,

ifnecessary, force the I/Os (see CPX system manual
P.BECPXSYS...).
An incomplete configuration will normally be displayed
with the diagnostics LED of the controller and in the

online diagnostics of your configuration software.
Procedure:
268
Check the DIL switch settings and the network

configuration before using and replacing CPX terminals.
Ensure that the desired start parametrisation of the
CPXterminal will be recreated after a network
interruption.
2. Commissioning
Make sure that, after replacement of individual modules

or of the entire CPX terminal, the new terminal is also
operated with the required parameter settings.
(See also section 2.8.1 for the start parametrisation and
the note on parametrisation using CPXMMI or CPXFMT in
section 2.8.4.)
If necessary, check the parametrisation on a random

basis, e.g. with the MMI, FMT or configuration program.
Errorfree commissioning, normal operating status

After an errorfree commissioning (normal operating status),
the following LEDs light green: "Power System" (PS) and
"Power Load" (PL), possibly also "Link/Traffic 1" (TP 1) and
TP2 (if connection is used).
LED display
NF
Operating
status
PS
PL
TP1
SF
TP2
1)
Normal,
no error
Only if connection is used:

Constant light: connection active
Flashing/blinking: Data transmission is running
Tab. 2/6:
The following LEDs

light green:
PS
PL
TP1 1)
TP2 1)
The following LEDs
do not light:
SF
NF
The M LED lights
orflashes if
parametrisation is
changed or force
mode is active
Normal operating status of the CPX terminal or

bus node
269
2. Commissioning
The LEDs "System Failure" (SF) and "Network Failure" (NF) do

not light.
The "Modify" (M) LED only lights or flashes for the "changed
parametrisation" setting (system start with saved
parametrisation and saved CPX expansion) or "force active"
(force mode, function no. 4402; see CPX system description
P.BECPXSYS..., on the spot diagnostics).
Detailed information about the meaning of the individual
LEDs and information on diagnostics and error handling can
be found in section 3.2 of this description and in the CPX
system description (P.BECPXSYS...).
270
Diagnosis
Chapter 3
31
3. Diagnosis
Contents
3.
Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
3.1
3.2
Overview of Diagnostic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Diagnostics via LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1
Network status LED NF / connection status LEDs TP1, TP2 . . . . .
3.2.2
CPX system/terminal status LEDs PS, PL, SF, M . . . . . . . . . . . . . .
Diagnostics via status bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics via the I/O diagnostic interface (STI) . . . . . . . . . . . . . . . . . . . . .
Diagnostics via PROFINET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1
Basic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2
Online diagnostics with Siemens STEP 7 . . . . . . . . . . . . . . . . . . . . .
3.5.3
Userspecific diagnostics with Siemens STEP 7 . . . . . . . . . . . . . . .
33
35
37
38
311
312
313
313
316
318
3.3
3.4
3.5
32
3. Diagnosis
3.1
Overview of Diagnostic Functions

The CPX terminal provides extensive and userfriendly
possibilities for diagnostics and error handling. Depending on
the configuration, the following functions are available as part
of PROFINET:
Diagnostic
function
Brief description
Advantages
Detailed
description
LED display
Status LEDs, for display of

hardware errors,
configuration errors, bus
errors, etc.
Fast onthespot"
recognition of faults
Section 3.2
Status bits
Internal inputs which supply

coded common diagnostic
messages: 8 status bits are
transmitted to the interface as
Inputs" cyclically with all
other inputs
Fast access to fault

messages in the PLC user
program, irrespective
ofthe module and
IOController
Section 3.3
I/O diagnostics
interface
Busindependent diagnostic
interface at I/O level which
enables access to the internal
data of the CPX terminal
(16 inputs and 16 outputs)
Read access to internal

parameters and data at
I/O level
CPX System
Manual, section
Diagnostics and
fault clearance
(P.BECPXSYS...),
Instructions in
section 3.4
(P.BECPXPNIO...)
Tab. 3/1:
Overview of the diagnostic options of the CPX terminal Part 1
33
3. Diagnosis
Diagnostic
function
Brief description
Advantages
Detailed
description
Diagnostics via
CPXMMI
Handheld MMI, for

menudriven, convenient
display of diagnostic
information
Fast onthespot" error

detection, without
programming, in clear text
Description for
the handheld unit
(P.BECPXMMI...)
Diagnostics via
CPXFMT
Festo Maintenance Tool (FMT),

for PCbased diagnostic
functions
Graphic representation
ofthe CPX terminal,
additional functions,
e.g.status display,
parametrisation
Online
documentation for
the CPXFMT
Diagnostics via
PROFINET
Diagnostics as part of the

PROFINET function
Diagnostics via the

network:
Detailed modulerelated
and channelrelated error
detection in the online
mode of the configuration
software and in the PLC
user program
Section 3.5
Tab. 3/2:
Overview of the diagnostic options of the CPX terminal Part 2
Note
Note that the diagnostic information shown can depend on
the settings (see section 1.4.2) as well as on the
parametrisation (see section 2.8) of the CPX terminal.
34
3. Diagnosis
3.2
Diagnostics via LEDs

LEDs for diagnosing the CPX terminal are available on the bus
node as well as on the individual modules.
The meaning of the LEDs on the electric modules can be
found in the manual for the relevant module.
LEDs on the CPX bus node for PROFINET

The light emitting diodes on the cover indicate the operating
status of the CPX bus node.
1 CPXspecific LEDs
NF
PS: Power system
PS
TP1
SF
TP2
PL: Power load
PM
NF
PS
SF: System Failure

M: Modify
2 PROFINET
specific LEDs
NF: Network Failure
TP1: Link/Traffic 1
PM
TP1
SF
TP2
TP2: Link/Traffic 2
Fig. 3/1: LEDs at the CPX bus node (here CPXFB33)
35
3. Diagnosis
The LEDs are shown in their various states as follows:

lights;
flashes;
dark;
Normal operating status

In normal operating status, the following LEDs light green:
PS, PL and possibly also TP1, TP2 (if connection is used).
The SF and NF LEDs do not light up.
The M LED only lights or flashes for the changed
parametrisation" setting (system start with saved
parametrisation and saved CPX expansion) or force active"
(force mode, function no. 4402; see CPX system description
P.BECPXSYS..., on the spot diagnostics).
LED display
NF
Operating
status
PS
PM
TP1
SF
TP2
1)
Normal,
no error
Only if connection is used:

Constant light: connection active
Flashing/blinking: Data transmission is running
Tab. 3/3:
36
The following LEDs

light green:
PS
PM
TP1 1)
TP2 1)
The following LEDs
do not light:
SF
NF
The M LED lights
orflashes if
parametrisation is
changed or force
mode is active
Normal operating status LED display
3. Diagnosis
3.2.1
Network status LED NF / connection status LEDs TP1, TP2
NF Network status/network failure

LED (red)
Procedure
Installation
Error handling
ON
No error
(if the green PS LED
lights up)
Network connection
not OK possible causes:
Only before initial
commissioning:
Configuration defective,
e.g. MACID not
configured
Device name or device
number not correct
IO controller defective
Network connection
interrupted, short
circuited or disturbed
Check:
OFF
LED is off
ON
OFF
LED flashes
Configuration
Device name
Device number
IO controller
Network connection
TP1, TP2 connection status (link/traffic 1, 2)

LED (green)
Procedure
Installation
Error handling
ON
No physical network
connection
Check network connection /

network cable
Network connection OK
Flickering: Data
transmission is running
Flashing, both LEDs at
the same rate:
Module location
OFF
LED is off
ON
OFF
LED lights up
ON
OFF
LED flickers or
flashes 1)
1)
ON
OFF
Module location: e.g. for fault

diagnostics or during configuration
(section 2.6.1)
Rapid flickering seems to be lighting; the light intensity depends on the data traffic
Tab. 3/4:
Network status LED NF / connection status LEDs TP1, TP2
37
3. Diagnosis
3.2.2
CPX system/terminal status LEDs PS, PL, SF, M
PS Operating voltage supply (power system)

LED (green)
Procedure
ON
OFF
LED lights up
ON
OFF
LED flashes
ON
OFF
LED is off
Installation
Error handling
No error, operating voltage

for electronics and sensors
is present
Operating voltage for

electronics and sensors
outside the tolerance
range
1. Eliminate short circuit/overload

2. Dependent on the parametrisation:
The sensor supply voltage will be
switched on again automatically
when the short circuit has been
eliminated (default)
Power off/on necessary
Operating voltage for

electronics and sensors not
applied
Check the operating voltage

connection of the electronics
PL Load voltage supply for outputs and valves (power load)

LED (green)
Procedure
Installation
Error handling
ON
No fault, load voltage

applied
None
Load voltage outside

tolerance range
1. Eliminate undervoltage
2. Dependent on the parametrisation:
the load voltage supply will be
switched on again automatically
after the undervoltage has been
eliminated (default)
Power off/on necessary
OFF
LED lights up
ON
OFF
LED flashes
Tab. 3/5:
38
CPX system/terminal status (part 1) LEDs PS and PL
3. Diagnosis
SF system failure
Procedure
Status 1)
Meaning/error handling
ON
No error
OFF
Information or
minor error
(error class 1)
See description of the error numbers

in the CPX system manual
(P.BECPXSYS...)
ON
LED (red)
Error (error class 2)
OFF
LED is off
ON
LED flashes
once
OFF
LED flashes
twice
ON
OFF
LED flashes
three times
1
Serious error
(error class 3)
See description of the error numbers

in the CPX system manual
(P.BECPXSYS...)
The system error LED flashes depending on the class of error which has occurred:
Error class 1 (minor error):
1x flash, pause
Error class 2 (error):
2x flash, pause
Error class 3 (serious error): 3x flash, pause
Tab. 3/6:
CPX system/terminal status (part 2) LED SF
39
3. Diagnosis
M parametrisation modified or forcing active (modify)

LED (yellow)
Procedure
Installation
Meaning/error handling
ON
System start with

factory settings (default
parametrisation) and
current CPX expansion
External parametrisation
possible (default)
None
System start with saved

parametrisation and
saved CPX expansion
Parameters and CPX
expansion are
retentively saved;
external parametrisation
is blocked 1)
Caution when replacing a CPX terminal

with saved parametrisation
(LED M lights up):
In case of servicing, such as with
replacement of the CPX terminal,
parametrisation is not created
automatically by the PLC or the
higherorder system. In this case,
check which settings are required
before replacement and make these
settings if necessary.
Forcing active 1)
The Force function has been activated

(Force mode; Function No. 4402, see
CPX System Manual P.BECPXSYS...).
OFF
LED is off
ON
OFF
LED lights up
ON
OFF
LED flashes
1
The display of the Force function (LED flashes) has priority over the display of the setting for the
system start (LED lights).
Tab. 3/7:
310
CPX system/terminal status (part 3) LED M
3. Diagnosis
3.3
Diagnostics via status bits

The CPX terminal provides 8 status bits if you activate this
function using DIL switches (see section 1.4.2) assuming
the corresponding PLC hardware configuration (see Tab. 1/3).
Also observe the continued explanations for configuration in
section 2.6.2.
The status bits are used for displaying common diagnostics
messages (global error messages). The status bits are
configured like inputs; you can select the address freely
during the configuration.
If all status bits supply a 0signal, no error will be reported.
Bit
Diagnostic information
with 1signal
Description
Error in valve
Module type in which an

error has occurred
Error at output
Error at input
Error on analogue module/

technology module
Undervoltage
Short circuit/overload
Wire break
Other error
Tab. 3/8:
Type of error
Status bits of the CPX bus node (optional)
311
3. Diagnosis
3.4
Diagnostics via the I/O diagnostic interface (STI)

The CPX terminal provides a 16bit I/O diagnostics interface
(system table interface, STI) if you activate this function using
DIL switches (see section 1.4.2) assuming the
corresponding PLC hardware configuration (see Tab. 1/3).
Observe also the continued explanations for configuration in
section 2.6.2.
Further information can be found in the CPX system
description (P.BECPXSYS...) in the diagnostics and error
handling section.
312
3. Diagnosis
3.5
3.5.1
Diagnostics via PROFINET

Basic information
PROFINET forms the basis for comprehensive diagnostics

functions and information over your automation network,
e.g.detailed modulerelated and channelrelated status
information and error recognition in the online mode of the
configuration software and in the PLC user program.
The following sections provide an initial view of the use of the
online diagnostics using the configuration and programming
software (see section 3.5.2) and the userspecific diagnostics
using function modules (see section 3.5.3).
Error characteristics
The behaviour of the CPX terminal for the following errors is
dependent on the configured behaviour of the controller
(ofthe Master), i.e. of the PLC or IPC and the parametrised
failsafe setting:
telegram failure
stop of the controller (of the master)
network interruption.
Depending on the parametrisation, the outputs (valves and

electric outputs) will be switched off (factory setting),
switched on or retain their status.
Further information about the failsafe setting can be found in
the CPX system description P.BECPXSYS...
313
3. Diagnosis
You can set two types of controller error characteristics:
Hard error characteristics: the controller switches to the

operating mode STOP" when an error occurs.
Soft error characteristics: the controller remains in the

operating mode RUN" when an error occurs.
Warning
Ensure that valves and outputs are put into a safe state
if the faults named occur.
An incorrect status of the valves and outputs can lead to
dangerous situations!
Note
Please note the following if the outputs are reset after
PLCstop, network interruption or fault:
Singlesolenoid valves move to the basic position.
Doublesolenoid valves remain in the current position.
Midposition valves move to the mid position (depending
on the valve type: pressurised, exhausted or blocked).
314
3. Diagnosis
Fault types
The following table shows a list of all error types which
provided further diagnostics information. The sections 3.5.2
and 3.5.3 describe the access to these error types (based on
Siemens STEP 7).
Value
Fault type (standard)
Value Error type (CPXspecific)
Reserved
1016
Incorrect valve setting
Short circuit
1017
Valve: Switching counter,

limit value exceeded
Undervoltage
1018
Reserved
Overvoltage
1019
Reserved
Overload
1020
Parametrisation error (configurable)
Overtemperature
1021
Parametrisation error (data format)
Cable break
1022
Parametrisation error (linear scaling)
Upper limit value exceeded
1023
Parametrisation error (digital filter)
Lower limit value exceeded
1024
Parametrisation error
(lower limit value)
Reserved
1025
Parametrisation error
(upper limit value)
10
Reserved
1026
Defective actuator supply
11
Reserved
1027
CP module failure
12
Reserved
1028
Defective CP configuration
13
Reserved
1029
Short circuit in the CP string (CP line)
14
Reserved
1030
Slave has no bus connection
15
Reserved
1031
Channel failed
bold = relevant for CPXFB33, CPXMFB34, CPXMFB35
Tab. 3/9:
Error types for the diagnostics via PROFINET
315
3. Diagnosis
3.5.2
Online diagnostics with Siemens STEP 7

configuration and programming software
(e. g. HW Config in Siemens STEP 7).
Fig. 3/2: Online diagnostics with Siemens STEP 7
316
3. Diagnosis
2. Switch from offline to online (see Fig. 3/2 1 ).

3. Click with the righthand mouse button on the CPU
in rack 2.
4. Click on Module information ..." in the displayed
context menu (Module status).
The window Module Information" (module status)
will be displayed 3.
5. Click on the IO device diagnostics" tab
(IO device diagnostics) 4.
6. Click on the event and then on Display"
(Displays) 5.
Diagnostics details are displayed in a new window 6.
These provide more precise information for further
processing. The information is independent of the
controller used.
317
3. Diagnosis
3.5.3
Userspecific diagnostics with Siemens STEP 7

The diagnostics for PROFINET are supported in STEP 7 by
Organisation Modules (OMs) and Function Modules (FMs).
OMs and FMs consist of individual function instructions and
thus form special program modules, socalled Instruction
Lists (AWL) which can be integrated in userspecific
programs.
Organisation Modules start in response to an error or a
devicerelated diagnosis and are used thereby for localisation
of the source of the error while Function Modules read the
diagnostics of the CPX bus node and write to a data area of
the user program (see example in Fig. 3/3).
In this way, the systemspecific diagnostics are individually
integrated in comprehensive, higherorder diagnostics
systems.
The following OMs and FMs can typically be used for
diagnostics purposes: OM 82, OM 86 and SFM 54
(see Tab. 3/10).
Control
system
Module
Meaning
Detail information
STEP 7
Siemens
OB 82
Starts as reaction to a devicerelated

diagnosis
OB 86
Starts as reaction to failure of an IO device

or the network
SFB 54
RALRM
Starts as reaction to failure of an IO device

or the network
Siemens
Reference manual
System and standard
functions for S7300/400"
/
PROFIBUS/PROFINET
Guidelines with respect to
G id li
ih
Function Blocks
Tab. 3/10:
318
Intended use (meaning) of the Organisation Modules OM 82 and OM 86 and

the Function Module SFB 54
3. Diagnosis
Basic procedures diagnostics with user program

Always call the Function Module SFB 54 RALRM from the
Error Organisation Module which has been started by the
controller, e.g. OM 82 or OM 86. A program example can be
found in Fig. 3/3.
1. Call up SFB 54 initially with the operating mode
MODE = 0 in order to determine the address of the
IO device triggering the diagnostics.
2. For determining the diagnostics details:
Call SFB 54 with the operating mode MODE = 2.
Enter the diagnostics address of the CPX bus node in

the parameter F_ID (apply diagnostics address from
step 1).
3. SFB 54 writes the diagnostics information to the AINFO

output parameter.
AWL
Explanation
CALL RALRM , DB54

MODE :=2
F_ID :=DW#16#7F3
MLEN :=255
NEW :=M54.0
STATUS:=DB_ALARM.STATUS
ID :=DB_ALARM.ID
LEN :=DB_ALARM.LEN
TINFO:=DB_ALARM.TINFO
AINFO:=DB_ALARM.AINFO
Call up of SFB 54
Operating mode check of the IO device with address in F_ID
Logical address of the PNIO bus node
Max. length in bytes
New alarm received
Error code of the SFB
Starting address of the module with alarm
Length of alarm information
Target range OB start information (Task information)
Target range header/additional information
(alarm information)
Fig. 3/3: Program example in AWL for reading diagnostics information
319
3. Diagnosis
320
Technical appendix
Appendix A
A1
A. Technical appendix
Contents
A.
Technical appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A1
A.1
A.2
A.3
A.4
Technical data of bus node CPXFB33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bus node CPXFB33, CPXMFB34 and CPXMFB35 . . . . . . . . . . . . . . . . . . .
A3
A4
A5
A2
A6
A.1
Technical data of bus node CPXFB33
General properties of CPXFB33

General technical data
See CPX System Description P.BECPXSYS...
Protection class through housing

according to EN 60529, completely mounted,
plug connector inserted or provided with
protective cap
IP65/IP67
Protection against electric shock

Protection against direct and indirect contact as
per IEC/DIN EN 602041
By means of PELV power circuit

(Protected ExtraLow Voltage)
Module code (CPXspecific)

Remote I/O
Remote controller
215
164
Module code (in the PLC, in the CPXFMT or

CPXMMI handheld)
Remote I/O
Remote controller
FB33RIO ProfiNet Remote I/O

FB33RC ProfiNet I/O bus node
Power supply CPXFB33

Operating voltage /load voltage
Intrinsic current consumption of bus node at 24 V

from operating voltage supply for electronics/
sensors (VEL/SEN)
typ. 120 mA
(internal electronics)
Galvanic isolation
PROFINET interfaces for VEL/SEN
Through a transformer (up to 1500 V)
Power failure bridging time
10 ms
A3
A.2
Technical data of bus node CPXMFB34
General properties of CPXMFB34


protective cap
IP65/IP67



Remote I/O
Remote controller
216
165

CPXMMI handheld)
Remote I/O
Remote controller
FB34RIO ProfiNet RJ45 Remote I/O

FB34RC ProfiNet RJ45 bus node
Power supply CPXMFB34


from operating voltage supply for electronics/
sensors (VEL/SEN)
typ. 120 mA
Galvanic isolation
Through a transformer (up to 1500 V)
10 ms
A4
A.3
Technical data of bus node CPXMFB35
General properties of CPXMFB35


protective cap
IP65/IP67



Remote I/O
Remote controller
217
166

CPXMMI handheld)
Remote I/O
Remote controller
FB35RIO ProfiNet FOC remote I/O

FB35RC ProfiNet FOC bus node
Power supply CPXMFB35


from operating voltage supply for
electronics/sensors (VEL/SEN)
typ. 150 mA
Galvanic isolation
Through fibreoptic cable
10 ms
A5
A.4

Bus node CPXFB33, CPXMFB34 and CPXMFB35
Networkspecific characteristics
Fieldbus protocol
PROFINET IO RT (PNIO RT):

based on industrial Ethernet
based on the Ethernet protocol
(IEEE 802.3)
Realtimecapable
supports LLDP
Specification
Selection of directives, standards and norms

with reference to PROFINET:
(PROFINET Installationsrichtlinie)
IEC 61158
IEC 61784
IEC 61918
Further information:
http://www.profinet.com
http://www.profibus.com/downloads
Transmission technology
Switched Fast Ethernet;

design 100BaseTX according to IEEE 802.3
Baud rate
100 Mbit/s
Wavelength
(only CPXMFB35)
650 nm
(suitable for POF fibreoptic cable)
Interfaces
(detailed information in section 1.6)
CPXFB33
CPXMFB34
CPXMFB35
2 x M12, Dcoded, female, 4pin

2 x RJ45, pushpull, copper, AIDAconforming
2 x SCRJ, pushpull, AIDAconforming
Crossover recognition
(only CPXFB33 + CPXMFB34)
AutoMDI
PROFINET input/output size
64 bytes I/64 bytes O,

independent of operating mode
A6
Glossary
Appendix B
B1
B. Glossary
Contents
B.
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B1
B.1
Bus node operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.1
Remote I/O Explanation of the operating mode . . . . . . . . . . . . . .
B.1.2
Remote controller explanation of the operating mode . . . . . . . . .
B.1.3
Fast Startup" explanation of the additional function . . . . . . . . .
B3
B3
B4
B5
B2
B. Glossary
B.1
Bus node operating modes
B.1.1 Remote I/O Explanation of the operating mode

All functions of the CPX terminal are controlled directly by the
PROFINETIO controller or a higherlevel PLC.
Control of the CPX terminal (or of the CPX valve terminal;

also designated as IO controller)
Data exchange between controller and modules
Parametrisation of the modules
Diagnostics
Controller and CPX terminal communicate via PROFINET.

In doing so, the bus node takes over the connection to
PROFINET and processing of the data exchange:
Protocol implementation
Forwarding of incoming and outgoing data
PROFINET RT
The PROFINET RealTime Protocol (RT) is used here.
(in both operating modes)
An FEC,possibly integrated in the CPX terminal, works as a
passive module, i.e. without controller. In this case, the FEC
can be used for connection to other networks, for example:
The FEC takes over the forwarding of incoming and outgoing
data and thus behaves like an I/O module.
B3
B. Glossary
B.1.2 Remote controller explanation of the operating mode

A CPXFEC of CPXCEC integrated into the CPX terminal takes
over control of the terminal (also described as IO controller)
as the local controller of a larger system, for example.
Requirements for this operating mode:
A CPXFEC or CPXCEC is a component of the CPX terminal.
Make sure that the DIL switches of bus nodes and

CPXFEC or CPXCEC are set corresponding to the
operating mode (see Tab. 1/4 and description of
P.BECPXFEC or P.BECPXCEC).
If necessary, settings must also be adapted to the

software level, such as in the programside hardware
configuration.
The bus node takes over the additional connection to

PROFINET, if applicable; that means, connection to the
higherorder network is not required in this configuration to
operate the CPX terminal. In this case, connection to
PROFINET provides supplementary functions:
B4
The FEC or CEC can communicate at the fieldbus level

over a datafield of 8 or 16 IObytes in size, such as with a
PROFINET IO controller or a higherlevel controller.
A higherlevel PLC can, for example, call up status
information of the valve terminal using this interface and
adjust or optimise the controller correspondingly with
other system parts.
B. Glossary
B.1.3 Fast Startup" explanation of the additional function

The remote I/O operating mode can be combined with the
additional function Prioritized Startup.
The additional function Prioritized Startup, also designated
Fast Startup" (FSU), ensures a faster startup of the
CPXsystem.
The following sections summarise the specific information
from the previous chapters to provide a comprehensive
overview of this function.
The summary also simplifies conversion of an existing
CPXsystem to Fast Startup".
Requirements
The additional function Fast Startup" requires certain

hardware, firmware and software versions as well as the
current GSDML file, which must be installed as part of
commissioning.
Hardware, firmware and software requirements can be

found in Tab. 2/2 (in section 2.5.2).
Tab. 2/2 also includes information about the

required GSDML file: For Fast Startup" you need
version 2.2 (orpossibly a higher version),
e.g. GSDMLV2.2FestoCPX20100517.xml.
Observe the wiring information regarding FSU

in section1.6.2.
Installation of the GSDML file is described in section 2.5.5.
B5
B. Glossary
Restrictions
Crossover detection is not available in remote I/O operating

mode with additional function Prioritized Startup" (FSU):
Use an appropriate cable (see section 1.6.2).
Make sure that the function Autonegotiation/

Autocrossover" is deactivated in your control software
before placing the system in operation (see section 2.6.4).
If necessary, the function Autonegotiation/

Autocrossover" must also be deactivated on the
hardwareside, in the basic setting of your controller (PLC)
or switches or routers in between: Check this with the
port settings.
The additional function FSU has restrictions in

parametrisation:
Module parameters cannot be set over the controller

software and must therefore be entered using CPXFMT or
CPXMMI.
For the system start, the function System Start with

Saved Parameters" (Saved" or Stored Parameters")
must be activated to ensure that the parameters entered
using FMT or MMI are used.
Additional information on parametrisation can be found in the

corresponding sections, especially section 2.8.
B6
B. Glossary
Activation/change
The change of operating mode to Fast Startup" is

performed in the control software, e.g. Siemens STEP 7:
Observe the following note!
Note
Activation of the additional function Fast Startup" (FSU)
Observe that the change to Fast Startup" in the control
software must be made at two configuration levels:
Basic hardware configuration
CPXterminal properties } section 2.6.4,
Set up Prioritized Startup (FSU)"
CPXterminal configuration
Allocate configuration table } section 2.7.1,
Open station symbol" and Select bus node"
with additional function FSU
Additional information on the FSU function can be found in
the Siemens PROFINET system description, section
Prioritized Startup".
B7
B. Glossary
B8
Index
Appendix C
C1
C. Index
Contents
C.
C2
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C1
C. Index
A
Abbreviations, productspecific . . . . . . . . . . . . . . . . . . . . XIII
Additional power supply . . . . . . . . . . . . . . . . . . . . . . . . . 128
Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24, 216
Address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Address space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Calculate address allocation . . . . . . . . . . . . . . . . . . . . 215
C
Cables, Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Commissioning
Address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24, 216
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Parametrisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Pneumatics (valves) . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
with Siemens Master . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Connecting
CPXFB33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPXMFB34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPXMFB35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
123
124
125
117
127
Connection technology . . . . . . . . . . . . . . . . . . . . . . . . . . 119

CP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
CPA pneumatics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
CPX revision code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
CPXFEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19, 267, B3
C3
C. Index
D
Device master file (GSDML) . . . . . . . . . . . . . . . . . . . 221, B5
DIL switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Dismantling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
E
Electric modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Electrical connection and display elements . . . . . . . . . . . 14
F
FEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19, 267, B3
Festo Maintenance Tool (CPXFMT) . . . . . . . . . . . . . . . . . . 25
FSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VII
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120, 121
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Crossover detection (AutoMDI) . . . . . . . . . . . . . . . . . 120
Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XIV, B5
Module support . . . . . . . . . . . . . . . . . . . . . . . . . . 29, 213
Operating mode . . . . . . . . . . . . . . . . . . 19, 246, 247, B5
Parametrisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
PROFINETStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Selecting bus node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Setting up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Station selection . . . . . . . . . . . . . . . . . . . . . . . . . 231, 232
System start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
WLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
G
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
H
Handheld (CPXMMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
C4
C. Index
I
I/O diagnostics interface . . . . . . . . . . . . . . . . . . . . . . . . . 312
Important user instructions . . . . . . . . . . . . . . . . . . . . . . . . . XI
Inputs, Calculate address allocation . . . . . . . . . . . . . . . . 215
Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VII
Interfaces, Pneumatics . . . . . . . . . . . . . . . . . . . . . . . . . . 210
IP65/IP67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
ISO pneumatics (VTSA) . . . . . . . . . . . . . . . . . . . . . . . . . . 210
L
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269, 35
M
Memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114, 115
Midi/Maxi pneumatics . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Module identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . 25, 26
Module parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Modules, Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
N
Network
Connection technology . . . . . . . . . . . . . . . . . . . . . . . . 119
Network cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Network connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
NFLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Notes on the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IX
C5
C. Index
O
Operating mode . . . . . . . . . . . . . . . . . . . . . . . . 19, 246, 267
Operating voltage, power supply . . . . . . . . . . . . . . . . . . . 23
Outputs, Calculate address allocation . . . . . . . . . . . . . . 215
P
Parametrisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Application example . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Diagnostic memory . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Module parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Start parametrisation . . . . . . . . . . . . . . . . . . . . . . . . . . 253
System parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
through software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
with the handheld unit . . . . . . . . . . . . . . . . . . . . . . . . . 260
Pictograms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XII
Pin allocation
Network interface CPXFB33 . . . . . . . . . . . . . . . . . . . . 123
Network interface CPXMFB34 . . . . . . . . . . . . . . . . . . 124
Network interface CPXMFB35 . . . . . . . . . . . . . . . . . . 125
Plug . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119, 123, 124, 125
Pneumatic interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Switching on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Protection class IP65/IP67 . . . . . . . . . . . . . . . . . . . . . . . 126
R
Remote controller . . . . . . . . . . . . . . . . . . . . . . . . . . 19, 267
C6
C. Index
S
Selecting bus node . . . . . . . . . . . . . . . . . . . 112, 246, 247
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
CPX revision code . . . . . . . . . . . . . . . . . . . . . . . . 112, 223
Diagnostics mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
DIL switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Fast Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112, 247
HW Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112, 246
Operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Station symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VIII
Setting
Diagnostics mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
DIL switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Siemens Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Start parametrisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Status bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
STEP 7
Automation project . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Hardware configurator (HW Config) . . . . 225, 231, 246
Online diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Station selection . . . . . . . . . . . . . . . . . . . . . . . . . 231, 232
Station symbol . . . . . . . . . . . . . . . . . . . . . . . . . . 232, 246
Strain relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Switch cover, Removing and mounting . . . . . . . . . . . . . . . 17
Symbol files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
System supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
C7
C. Index
T
Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VIII
Technical data
CPXFB33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A3
CPXMFB34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A4
CPXMFB35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A5
Text markings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XII
TP LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
V
Valve supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
VTSA pneumatics (ISO) . . . . . . . . . . . . . . . . . . . . . . . . . . 210
C8

Manual Festo

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Manual Festo

Enviado por

Direitos autorais:

Formatos disponíveis

CPX Terminal

Contents and general instructions

(Festo AG & Co. KG, D73726 Esslingen, Germany, 2010)

Contents and general instructions

PROFINET IO, PROFIBUS, SIMATIC, TORX, TV and VDE

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

General instructions on installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

Instructions for commissioning with Siemens SIMATIC STEP 7 . . . . . . . . . . .

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

Overview of Diagnostic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical data of bus node CPXFB33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bus node operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

Remote I/O with additional function Prioritized Startup,

The FSU operating mode ensures a faster startup of the CPX

As intended in an industrial environment

In original condition without modification (only the

In faultless technical condition

The limit values specified for pressures, temperatures,

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

Comply with the legal rules and regulations and standards,

circuits as per IEC/DIN EN 602041.

isolation of the operating voltage as per IEC/DIN EN

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

Instructions on this manual

Ethernetbased CPX bus node

The PROFINET fieldbus

PROFINET Installation Guide

2 x RJ45 sockets, pushpull,

2 x SCRJ sockets, pushpull,

Overview of CPX bus node for PROFINET

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

This manual includes information about installation and

PROFINET Installation Guide

General basic information on the mode of operation,

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

Important user instructions

The following pictogram marks passages in the text which

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

Marking special information

The bullet indicates activities which may be carried out in

1. Figures denote activities which must be carried out in the

Hyphens indicate general activities.

Festo P.BECPXPN IOEN en 1008b

Contents and general instructions

The following productspecific terms and abbreviations are

Hexadecimal numbers are marked by a subscript h".

Automation Initiative of German Automobile Manufacturers

AutoMDI designates the capability of automatically recognising the

Create the connection to certain networks or fieldbusses; pass on

CoDeSys controller, e.g. CPXCEC/CPXCEC..., applicable for

Controller Development System

Hexadecimal numbers are marked by a subscript h".

Fast Startup", also designated Prioritized Startup"; further informa

Permanently assigned hardware address (physical address") for

Prioritized Startup is also designated Fast Startup" (FSU);

Additional function Fast Startup" (FSU) section B.1.3