CPX-FB11 Manual

CPX terminal
Manual
Electronics
CPX field bus node
Type CPX−FB11
Field bus protocol

DeviceNet
Manual
526 422
en 0503b
[689 002]
Contents and general instructions
Original . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . de
Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . en 0503b
Designation . . . . . . . . . . . . . . . . . . . . . . . P.BE−CPX−FB11−EN
Order no. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 422
© (Festo AG&Co. KG, D73726 Esslingen, Federal Republic of

Germany, 2005)
Internet: http://www.festo.com
E−Mail: service_international@festo.com
The reproduction, distribution and utilization of this document

as well as the communicaton of its contents to others without
express authorization is prohibited. Offenders will be held
liable for the payment of damages. All rights reserved in the
event of the grant of a patent, utility module or design.
Festo P.BE−CPX−FB11−EN en 0503b I

DeviceNet® is a registered trademark of Open DeviceNet Vendor

Association. Inc. (ODVA)
RSLinx, RSLogix,
RSNetWorx for
DeviceNet® are registered trademarks of Rockwell Software Inc.
TORX® is a registered trade mark of CAMCAR TEXTRON INC.,

Rockford, Ill., USA
II Festo P.BE−CPX−FB11−EN en 0503b

Contents
Designated use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VII

Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VIII
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VIII
Important user instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IX
Notes on the use of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XI
1. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−1
1.1 General instructions on installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−3

1.2 Setting the CPX field bus node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−6
1.2.1 Removing and fitting the cover over the DIL switches . . . . . . . . . . . 1−6
1.2.2 Setting the DIL switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−7
1.3 Connecting to the field bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−16
1.3.1 Field bus cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−16
1.3.2 Field bus baud rate and field bus length . . . . . . . . . . . . . . . . . . . . . 1−17
1.3.3 Connection instructions for DeviceNet . . . . . . . . . . . . . . . . . . . . . . . 1−18
1.3.4 Micro Style connection (2xM12) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−20
1.3.5 Open Style connection (screw terminals, IP20) . . . . . . . . . . . . . . . . 1−21
1.3.6 Example of connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−22
1.3.7 Further connection possibility via the Sub−D connection . . . . . . . . 1−23
1.4 Bus termination with terminating resistors . . . . . . . . . . . . . . . . . . . . . . . . . . 1−27
1.5 Pin assignment of power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−28
Festo P.BE−CPX−FB11−EN en 0503b III

2. Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−1
2.1 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−3

2.1.1 Ascertaining the address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−4
2.1.2 Address assignment of the CPX terminal . . . . . . . . . . . . . . . . . . . . . 2−8
2.1.3 Address assignment after extension/conversion . . . . . . . . . . . . . . 2−15
2.2 Bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−18
2.2.1 Switching on the power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−19
2.2.2 Configuring DeviceNet slave features (EDS) . . . . . . . . . . . . . . . . . . 2−20
2.2.3 Remarks on configuration on the DeviceNet . . . . . . . . . . . . . . . . . . 2−24
2.2.4 Configuration with RSNetWorx for DeviceNet
with standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−25
with modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−33
2.3 Parameterisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−41
2.3.1 Methods of parameterisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−43
2.3.2 Parameterisation with RSNetWorx with standard EDS . . . . . . . . . . 2−45
2.3.3 Parameterisation with RSNetWorx with modular EDS . . . . . . . . . . . 2−48
2.3.4 Notes on specific parameters of the DeviceNet . . . . . . . . . . . . . . . . 2−51
2.3.5 Parameterisation via the PLC user program . . . . . . . . . . . . . . . . . . . 2−54
2.3.6 Parameterisation with the handheld . . . . . . . . . . . . . . . . . . . . . . . . 2−56
2.4 Commissioning the CPX terminal on the DeviceNet . . . . . . . . . . . . . . . . . . . . 2−57
3. Diagnosis and error treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−1
3.1 Overview of diagnostic options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−3

3.2 Diagnosis via LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−4
3.2.1 CPX−specific LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−6
3.3 Diagnosis via status bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−12
3.4 Diagnosis via I/O diagnostic interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−13
3.5 Diagnosis via DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−14
3.5.1 Diagnosis via software configurator with standard EDS . . . . . . . . . 3−14
3.5.2 Diagnosis via software configurator with modular EDS . . . . . . . . . 3−18
3.5.3 Diagnosis via the user program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−20
3.6 Fault treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−23
IV Festo P.BE−CPX−FB11−EN en 0503b

A. Technical appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A−1
A.1 Technical specifications of field bus node type CPX−FB11 . . . . . . . . . . . . . . . A−3

A.2 Accessories for field bus connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A−4
A.3 EDS files of the CPX terminal for standard EDS . . . . . . . . . . . . . . . . . . . . . . . A−5
A.4 Structure of the standard EDS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A−6
A.4.1 Numbering the modules in the standard EDS file . . . . . . . . . . . . . . A−8
A.4.2 Channel assignment for Force, Fail safe
and Idle parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A−10
B. DeviceNet objects with Standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−1
B.1 DeviceNet objects with Standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−3

B.1.1 DeviceNet object model CPX terminal . . . . . . . . . . . . . . . . . . . . . . . B−3
B.1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−4
B.1.3 Module−parameter object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−6
B.1.4 Assembly object instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−11
B.1.5 Channel assignment for Force, Fail safe
and Idle parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−14
B.1.6 Object, modification digital outputs . . . . . . . . . . . . . . . . . . . . . . . . . B−15
B.1.7 Object, modification digital inputs . . . . . . . . . . . . . . . . . . . . . . . . . . B−16
B.1.8 Object, modification analogue outputs . . . . . . . . . . . . . . . . . . . . . . B−17
B.1.9 Object, modification analogue inputs . . . . . . . . . . . . . . . . . . . . . . . B−18
B.1.10 Object, modification output words function module . . . . . . . . . . . B−19
B.1.11 Object, modification input words function module . . . . . . . . . . . . . B−20
B.1.12 Module−independent system object . . . . . . . . . . . . . . . . . . . . . . . . . B−21
B.1.13 Status and diagnostic object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−25
B.1.14 Diagnostic trace object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−26
B.1.15 Diagnostic trace status object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−27
Festo P.BE−CPX−FB11−EN en 0503b V

C. DeviceNet objects with Modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−1
C.1 DeviceNet Objects with Modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−3

C.1.1 DeviceNet object model CPX terminal . . . . . . . . . . . . . . . . . . . . . . . C−3
C.1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−4
C.1.3 Assembly object instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−6
C.1.4 Status and diagnostic object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−9
C.1.5 Module−independent system object . . . . . . . . . . . . . . . . . . . . . . . . . C−10
C.1.6 Parameter Object Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−14
C.1.7 General object module parameters . . . . . . . . . . . . . . . . . . . . . . . . . C−19
C.1.8 Channel assignment for Force, Fail safe and Idle parameters . . . . . C−24
C.1.9 Object: Forcing inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−25
C.1.10 Object: Forcing outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−27
C.1.11 Object: Fault mode and Fault state of the outputs . . . . . . . . . . . . . C−28
C.1.12 Object: Idle mode and Idle state of the outputs . . . . . . . . . . . . . . . C−29
C.1.13 Diagnostic trace object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−30
C.1.14 Diagnostic trace status object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−31
D. Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D−1
VI Festo P.BE−CPX−FB11−EN en 0503b

Designated use
The field bus node type CPX−FB11 described in this manual

has been designed exclusively for use as a slave on the
DeviceNet.
The CPX terminal may only be used as follows:
only in industrial applications
in accordance with designated use
without any modifications by the user. Only the conver

sions or modifications described in the documentation
supplied with the product are permitted.
in faultless technical condition.
the maximum values specified for pressures, tempera

tures, electrical data, torques etc. must be observed.
Please comply with national and local safety laws and

regulations.
Festo P.BE−CPX−FB11−EN en 0503b VII

Target group
This manual is intended exclusively for technicians trained in

control and automation technology, who have experience in
installing, commissioning, programming and diagnosing
slaves on the DeviceNet field bus.
Service
Please consult your local Festo repair service if you have any
technical problems.
VIII Festo P.BE−CPX−FB11−EN en 0503b

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.
Please note
result in damage to property.
The following pictogram marks passages in the text which

describe activities with electrostatically sensitive compo
nents.
Electrostatically sensitive components may be damaged if

they are not handled correctly.
Festo P.BE−CPX−FB11−EN en 0503b IX

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 environment−friendly 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.
Hyphens indicate general activities.
X Festo P.BE−CPX−FB11−EN en 0503b

Notes on the use of this manual
Please note
This manual refers to the following versions:
Support of Field bus node CPX−FB11 1) EDS file
MPA1 pneumatic and handheld as from software status 26.05.03 (R09) as from Rev. 1.3
type CPX−MMI−1
MPA2 pneumatics as from software status 26.05.03 (R09) as from Rev. 1.3
CPX−CP interface as from software status 12.10.05 (R16) as from Rev. 2.1
(Modular EDS)
CPX−FB11 as from Rev. 2.1

As Remote Controller as from software status 25.04.05 (R14)
(e.g. with CPX−FEC)
Modular EDS as from software status 12.10.05 (R16)
1) Software status (SW) or revision no. (R) see type plate
Tab.0/1: Support of features and software status
This manual contains specific information on installation,

commissioning, programming and diagnosis with the CPX
field bus node for DeviceNet.
General basic information on the method of operation, on

fitting, installing and commissioning CPX terminals can be
found in the CPX system manual.
Information on further CPX modules can be found in the

manual for the relevant module.
Festo P.BE−CPX−FB11−EN en 0503b XI

Version Title Description
Manual System manual" Overview of structure, components and method

Electronics type P.BE−CPX−SYS−... of operation of CPX terminals;
installation and commissioning instructions as
well as basic principles of parameterisation
CPX field bus node" Instructions on fitting, installing, commissioning

type P.BE−CPX−FB... and diagnosing the relevant field bus node
CPX I/O modules" Notes on connection types and instructions on

type P.BE−CPX−EA−... fitting, installing and commissioning input and
output modules of type CPX−..., the MPA pneu
matic modules, as well as MPA, CPA and Midi/
Maxi pneumatic interfaces
CPX analogue I/O Notes on connection types and instructions on
modules" fitting, installing and commissioning CPX
type P.BE−CPX−AX−... analogue I/O modules
CPX−CP interface" Instructions on fitting, installing, commissioning
type P.BE−CPX−CP−... and diagnosing CP systems with the CP interface
type CPX−CP−4−FB
Handheld" Instructions on commissioning and diagnosing
type P.BE−CPX−MMI−1−... CPX terminals with the Handheld
typeCPX−MMI−1
CPX−FEC" Instructions on fitting, installing, commissioning
type P.BE−CPX−FEC−... and diagnosing the CPX Front End Controller
Software FST" Programming in Statement List and Ladder

package Diagram for the FEC
Tab.0/2: Manuals on the CPX terminal part 1
XII Festo P.BE−CPX−FB11−EN en 0503b

Version Title Description
Manual Valve terminals with MPA Instructions on fitting, installing, commis

Pneumatic pneumatics" sioning, maintaining and converting the MPA
components type P.BE−MPA−... pneumatics (type 32)
Valve terminals with CPA Instructions on fitting, installing, commis

pneumatics" sioning, maintaining and converting the CPA
type P.BE−CPA−... pneumatics (type 12)
Valve terminals with Midi/ Instructions on fitting, installing, commis
Maxi pneumatics" sioning, maintaining and converting the
type P.BE−MIDI/MAXI−03−... Midi/Maxi pneumatics (type 03)
Valve terminal with VTSA/ Instructions on fitting, installing, commis
ISO pneumatics" sioning, maintaining and converting the
type P.BE−VTSA−44−... VTSA/ISO pneumatics (type 44)
Tab.0/3: Manuals on the CPX terminal part 2
Festo P.BE−CPX−FB11−EN en 0503b XIII

The following product−specific terms and abbreviations are

used in this manual:
Term/abbreviation Meaning
CP Compact Performance
CPA Pneumatic modules/valve terminal type 12
CPX bus Data bus via which the CPX modules communicate with each other and
are supplied with the necessary operating voltage.
CPX modules Common term for the various modules which can be incorporated in a
CPXterminal
CPX terminal Modular, electric terminal type 50
EDS library The features of the various field bus slaves are managed in the EDS library
(Electronic data sheets).
Field bus nodes Provide the connection to specific field buses. Transmit control signals to
the connected modules and monitor their ability to function.
I Digital input
I/O diagnostic interface The I/O diagnostic interface is a bus−independent diagnostic interface at
I/O level, permitting access to internal data of the CPX terminal.
I/O modules Common term for the CPX modules which provide digital inputs and
outputs (CPX input modules and CPX output modules).
I/Os Digital inputs and outputs
O Digital output
PLC/IPC Programmable logic controller/industrial PC
Pneumatic interface The pneumatic interface is the interface between the modular electrical
periphery and the pneumatics.
Midi/Maxi Pneumatic modules/valve terminal type 03
RSNetWorx Parameterisation, commissioning and diagnostic software
Status bits Internal inputs which supply coded common diagnostic messages.
Tab.0/4: CPX−specific terms and abbreviations
XIV Festo P.BE−CPX−FB11−EN en 0503b

Installation
Chapter 1
Festo P.BE−CPX−FB11−EN en 0503b 1−1

1. Installation
Contents
1. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−1
1.1 General instructions on installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−3

1.2 Setting the CPX field bus node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−6
1.2.1 Removing and fitting the cover over the DIL switches . . . . . . . . . . . 1−6
1.2.2 Setting the DIL switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−7
1.3 Connecting to the field bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−16
1.3.1 Field bus cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−16
1.3.2 Field bus baud rate and field bus length . . . . . . . . . . . . . . . . . . . . . 1−17
1.3.3 Connection instructions for DeviceNet . . . . . . . . . . . . . . . . . . . . . . . 1−18
1.3.4 Micro Style connection (2xM12) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−20
1.3.5 Open Style connection (screw terminals, IP20) . . . . . . . . . . . . . . . . 1−21
1.3.6 Example of connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−22
1.3.7 Further connection possibility via the Sub−D connection . . . . . . . . 1−23
1.4 Bus termination with terminating resistors . . . . . . . . . . . . . . . . . . . . . . . . . . 1−27
1.5 Pin assignment of power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−28
1−2 Festo P.BE−CPX−FB11−EN en 0503b

1. Installation
1.1 General instructions on installation
Warning
Sudden unexpected movement of the connected actuators
and uncontrolled movements of loose tubing can cause
injury to human beings or damage to property.
Before carrying out installation and maintenance work,
switch off the following:
the compressed air supply
the operating and load voltage supplies.
Caution
The CPX field bus node may be damaged if it is not
handled correctly.
· Observe the regulations for handling electrostatically
sensitive components.
· Discharge yourself electrostatically before fitting or re
moving components in order to protect the components
against discharges of static electricity.

1. Installation
Electrical connecting and display elements

You will find the following connecting and display elements
on the CPX field bus node for DeviceNet:
1 Bus status−
specific and 4 1
CPX−specific LEDs
2 Exchangeable
field bus
connection
(here Micro Style 3 2
connection)
3 Transparent
cover for the DIL
switches
4 Service interface
for handheld
Fig.1/1: Connecting and display elements on the CPX field bus node
The field bus connection is exchangeable. The following

connection possibilities are available:
Micro Style connection type FBA−2−M12−5POL (2xM12)
Open Style connection type FBA−1−SL−5POL with terminal

strip type FBSD−KL−2x5POL
9−pin sub−D plug

1. Installation
Dismantling and fitting

The field bus node is fitted in a manifold base of the
CPXterminal (see Fig.1/2).
Dismantling Dismantle the field bus node as follows:
1. Loosen the 4 screws in the field bus node with a Torx

screwdriver size T10.
2. Pull the field bus node carefully and without tilting away
from the contact rails of the manifold base.
1 Field bus node 4

CPX−FB11
2 Manifold block
3 Contact rails 1
4 Screws
3
2
Fig.1/2: Dismantling/fitting the field bus node
Fitting Fit the field bus node as follows:
1. Place the field bus node in the manifold base. Make sure
that the grooves with the power contact terminals on the
bottom of the field bus node lie above the contact rails.
Press the field bus node carefully and without tilting as
far as possible into the manifold sub−base.
2. Tighten the screws at first only by hand. Place the screws

so that the self−cutting threads can be used.
Tighten the screws with a Torx screwdriver size T10 with
0.9 ... 1.1 Nm.

1. Installation
1.2 Setting the CPX field bus node
In order to set the CPX field bus node, you must first remove
the cover over the DIL switches.
Caution
The CPX field bus node contains electrostatically sensitive
components.
· Do not therefore touch any contacts.
· Observe the regulations for handling electrostatically
sensitive components.
You will then prevent the electronics in the node from being
damaged.
1.2.1 Removing and fitting the cover over the DIL switches
Removing 1. Switch off the power supply.
2. Unscrew the two fastening screws in the switch cover.
3. Lift up the cover.
Assembly 1. Place the cover carefully on the node.
Please note
Make sure that the seal is seated correctly.
2. Tighten both fastening screws at first by hand and then

with torque 0.5 ... 0.8 Nm.

1. Installation
1.2.2 Setting the DIL switches
When you have removed the cover for the DIL switches, you
will see five DIL switches in the field bus node (see Fig.1/3).
DIL switch 2 is reserved for later extensions. With the other

four DIL switches you can set the following:
Operating mode and EDS mode (firmware)
Baud rate
Diagnosis mode or number of I/O bytes
Station number
Procedure:
1. Switch off the power supply.
Modifications to the DIL switch settings will not become

effective until the operating voltage is switched on again.
2. Remove the cover over the DIL switches (chapter 1.2.1).
3. Set the baud rate (lower left 2−position DIL switch).
4. Set the diagnostic mode (lower right 2−position DIL

switch).
5. Assign an unused station number to the CPX terminal.

Set the desired station number (8−position DIL switch,
elements 1...6).
6. Fit the cover again (chapter 1.2.1).

1. Installation
1 DIL switch 1:
Operating mode
and EDS mode
1 ON ON
2
2 DIL switch 2:
1 2 1 2
Reserved
3 DIL switch 3:
Diagnosis mode
7 8
or number of 5
5 6
I/Obytes
1 2 3 4
4 DIL switch 4: ON
Baud rate
5 DIL switch 5: 4
ON ON
3
Station number
1 2 1 2
Fig.1/3: DIL switches in the field bus node (further information on 1...5 on the
following pages)

1. Installation
Setting the operating mode with DIL switch 1

You can set the operating mode of the CPX terminal with
switch element 1 of DIL switch 1:
Operating mode Setting DIL switch 1.1
Remote I/O operating mode DIL 1.1: OFF

All functions of the CPX terminal are controlled directly by the (factory setting)
higher−order PLC/IPC. An FEC integrated in the CPX terminal
functions as a passive function module without controller.
Remote Controller operating mode DIL 1.1: ON

An FEC integrated in the CPX terminal takes control of the I/Os.
This operating mode is only useful if an FEC is integrated in the
CPX terminal.
Tab.1/1: DIL switch 1 (operating mode)
Setting the EDS mode with DIL switch 1

You can set the EDS mode of the CPX terminal with switch
element 2 of DIL switch 1:
EDS mode Setting DIL switch 1.2
Standard EDS DIL 1.2: OFF

The CPX terminal is configured with standard EDS (factory setting)
(one EDS file for the entire configuration)
Modular EDS (starting with software version R16) DIL 1.2: ON

The CPX terminal is configured with modular EDS
(one EDS file for each module type)
Tab.1/2: DIL switch 1 (EDS mode)
Please note
If you configure the CPX terminal with modular EDS, the
field bus node must be installed as module 0 on the first
place.

1. Installation
Setting the diagnosis mode or number of I/O bytes with

DILswitch 3
The function of this DIL switch depends on the set operating
mode of the CPX terminal (see also Tab.1/1).
Remote I/O operating mode Remote Controller Setting

operating mode DIL switch 3
Diagnostic mode Number of I/O bytes
The I/O diagnostic interface and the status Not permitted 3.1: OFF
bits are switched off 3.2: OFF
(+ 0 I/O bits) (default)
Recommended setting 1)
The I/O diagnostic interface is switched on 2) 3.1: ON

(+ 16 I/O bits, beginning with the first free 3.2: OFF
process data word)
The status bits are switched on 3) 3.1: OFF

(+ 16 input bits, beginning with the first free 3.2: ON
process data word)
This setting is used for exceptional situations
in which controllers do not easily support the
Strobed I/O" connections.
Reserved for future extensions 8−byte I/8 byte O for 3.1: ON

communication of the 3.2: ON
field bus node with the
CPX−FEC.
1) Irrespective of the DIL switch setting, the 8 status bits are always available via a Strobed I/O"
connection. In addition the diagnosis can take place via the DeviceNet objects (see appendix B.1).
Starting with software version R16, the Strobed I/O" connection can be deactivated with DIL 2.2.
2) The I/O diagnostic interface occupies an additional 16 I/O bits.
3) With this setting the status bits occupy an additional 16 input bits and can be transmitted via a
Polled" connection or a Change of State" connection. The 8 status bits lie in the lower−value
8bits. The higher−value 8 bits remain unused.
Tab.1/3: DIL switch 3 (diagnosis mode or number of I/O bytes with remote controller)

1. Installation
In the Remote I/O operating mode, you set with the DIL
switch 3 whether diagnostic information is to be transmitted
on a Polled" or Change of State" connection. Irrespective of
this setting, in this operating mode the 8 status bits are
always available via a Ptrobed I/O" connection.
In the Remote Controller operating mode, both switch el

ements of the DIL switch 3 must be set to ON. Communication
of the field bus node with an integrated CPX−FEC runs over
8input bytes and 8 output bytes.
Setting the baud rate with DIL switch 4

You can set the baud rate with switch element 2 of the DIL
switch 4:
Description Setting the DIL switches 4
Baud rate 125 kBd 4.1: OFF

4.2: OFF
(default)
Baud rate 250 kBd 4.1: ON

4.2: OFF
Baud rate 500 kBd 4.1: OFF

4.2: ON
Automatic baud rate recognition 4.1: ON

in the switch−on phase of the 4.2: ON
CPX terminal when connected to
a bus system which is running. 1)
1) If no baud rate is recognised in the switch−on phase, 125 KBd will
be set automatically. First connect the CPX terminal to the running
DeviceNet network. Then switch on the power supply for the CPX
terminal.
Tab.1/4: DIL switch 4 (baud rate)

1. Installation
Setting the station number with DIL switch 5

You can set the field bus station number (binary coded) with
the 8−element DIL switch.
7 8
5 6
3 4
1
2
1
1 Setting the station number
(8−element DIL switch, switch elements 1−6)
Fig.1/4: Setting the station number (8−element DIL switch)
Switch elements 7 and 8 are reserved for future extensions

and must be set to OFF.
Please note
Station numbers may only be assigned once per field bus
line.
The following station numbers are permitted:
Protocol Address designation Permitted station

numbers
DeviceNet Station number 0...63
Tab.1/5: Permitted station numbers
Recommendation:
Assign the station numbers in ascending order. Assign the
station numbers to suit the machine structure of your system.

1. Installation
Example
Station number 05 Station number 38
20 + 22 = 21 + 22 + 25 =
8
1+4=5 2 + 4 + 32 = 38
7
25 25
6
6
5
24 24
5
23 23
4
4
22 22
3
3
21 21
2
2
20 20
1
1
Tab.1/6: Examples of set station numbers
The following pages contain a summary of the settings for the

station numbers.

1. Installation
Sta 1 2 3 4 5 6 7 8 Sta 1 2 3 4 5 6 7 8
tion tion
no. no.
0 16 ON
OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF
1 ON 17 ON ON
OFF OFF OFF OFF OFF OFF OFF OFF OFF
2 ON 18 ON ON
3 ON ON 19 ON ON ON
OFF OFF OFF OFF OFF OFF OFF
4 ON 20 ON ON
5 ON ON 21 ON ON ON
6 ON ON 22 ON ON ON
7 ON ON ON 23 ON ON ON ON
OFF OFF OFF OFF OFF
8 ON 24 ON ON
9 ON ON 25 ON ON ON
10 ON ON 26 ON ON ON
OFF OFF OFF OFF OFF
OFF OFF OFF OFF OFF
OFF OFF OFF OFF OFF
15 ON ON ON ON 31 ON ON ON ON ON
OFF OFF OFF
Tab.1/7: Setting station numbers 0...31: Position of the DIL switch elements

1. Installation
Sta 1 2 3 4 5 6 7 8 Sta 1 2 3 4 5 6 7 8
tion tion
no. no.
32 ON 48 ON ON
OFF OFF OFF OFF OFF
OFF OFF OFF OFF OFF
OFF OFF OFF OFF OFF
OFF OFF OFF
OFF OFF OFF OFF OFF
OFF OFF OFF OFF OFF
OFF OFF OFF
OFF OFF OFF OFF OFF
OFF OFF OFF
OFF OFF OFF
47 ON ON ON ON ON 63 ON ON ON ON ON ON
OFF
Tab.1/8: Setting station numbers 32...63: Position of the DIL switch elements

1. Installation
1.3 Connecting to the field bus
1.3.1 Field bus cable
Please note
If installation has not been carried out correctly and if high
baud rates are used, data transmission errors may occur
as a result of signal reflections and attenuations. Causes of
transmission faults may be:
missing or incorrect terminating resistor
incorrect screening/shield connection
branch lines too long
transmission over long distances
unsuitable cables.
Observe the cable specifications. Refer to your controller
manual for information on the type of cable to be used.
Use a twisted, screened 5−core cable for connecting the field

bus. The bus interface is supplied with power via the field bus
cable.
Alternatively, you can use bus cables of other manufacturers

(see also appendix A.2, Accessories).
Please note
If the CPX terminal is fitted onto the moving part of a
machine, the field bus cable on the moving part must be
provided with strain relief. Please observe also the relevant
regulations in EN60204 part 1.

1. Installation
1.3.2 Field bus baud rate and field bus length
The maximum permitted field bus length depends on the

baud rate used. Tab.1/9 shows the nominal values. Detailed
specifications can be found in the manuals for the your con
trol system or scanner.
The maximum permitted length of the branch line depends on

the total length of the branch lines and the baud rate.
Please note
· Refer to the manuals for your control system or bus in
terface for information on the T−adapter and the maxi
mum branch line length which is permitted for your
controller.
· Take into account also the sum of the branch line lengths
when calculating the maximum permitted length of the
field bus cable.
Baud rate Maximum main Branch line length

b length
bus l th Maximum Cumulative
125 kBaud 500 m 156 m

6m
250 kBaud 250 m 78 m
500 kBaud 100 m 39 m
Tab.1/9: Maximum field bus and branch line lengths

depending on the baud rate (as per ODVA
specification V2.0)
Information on setting the baud rate can be found in

chapter1.2.2.

1. Installation
1.3.3 Connection instructions for DeviceNet
Bus supply
Avoid long distances between the bus interfaces/logic supply
and the CPX terminal.
Caution
· Make sure the polarity is correct when you connect the
field bus interface and the power supply for the bus
interface/internal logics.
· Connect the screening/shield.
Please note
Bus slaves have different tolerances in respect to the inter
face supply, depending on the manufacturer. Note this
when planning the bus length and placing the power unit.
The following tolerance of the bus interface supply applies to

the CPX terminal (pin 2 with the Micro Style connection or
pin5 with the Open Style connection):
Vmax = 30.0 V DC
Vmin = 11.0 V DC
Recommendation:
Place the power unit approximately in the centre of the bus.

1. Installation
Connection diagram for DeviceNet
Please note
You must check the pin assignment of your scanner with
the relevant documentation.
The field bus node can be connected in a variety of ways.

The following table shows the relationship between the core
colour, signal and pin assignment of the various connecting
possibilities.
Signal−related Designation Micro Style Open Style Sub−D plug

core colour *) connection connection (integrated)
(optional) (optional)
red 24 V DC bus Pin 2 Pin 5 Pin 9

white CAN_H Pin 4 Pin 4 Pin 7
bare Screen Pin 1 Pin 3 Pin 5
blue CAN_L Pin 5 Pin 2 Pin 2
black 0 V bus Pin 3 Pin 1 Pin 3
*) Typical for Bus connection
DeviceNet cables variants: 1 5
6 9
1 2 3 4 5
Tab.1/10: Connection diagram for DeviceNet
Connect the field bus cable of your control system to the field
bus interface of the CPX terminal as described in the follow
ing sections.

1. Installation
1.3.4 Micro Style connection (2xM12)
The Micro Style connection (type FBA−2−M12−5POL) offers a

5−pin M12 plug and a 5−pin M12 socket with PG9 screw con
nector. The M12 plug serves for connecting the incoming field
bus cable. The M12 plug serves for connecting the continuing
field bus cable.
Accessories from Festo for the Micro Style connection:

M12 plug type FBS−M12−5GS−PG9
M12 socket type FBSD−GD−9−5POL
Please note
Use blanking plugs to seal unused connections. You will
then comply with protection class IP65.
Micro Style connection Pin no.
2 2 1. Screen
2. 24 V DC bus (max. 4A)
3. 0 V bus
3 1 1 3
5 5
4. CAN_H
5. CAN_L
4 4
Bus out
Bus in Blanking plug for
unused connection
Tab.1/11: Pin assignment of the field bus interface

(Micro Style connection, type FBA−2−M12−5POL)
With the M12 connections, you can implement a T−tap

(seeFig.1/5). Bus in and bus out are connected together in
the Micro Style connection.

1. Installation
1.3.5 Open Style connection (screw terminals, IP20)
The Open Style connection (type FBA−1−SL−5POL) enables the

2x5−pin terminal strip (type FBSD−KL−2x5POL) to be inserted.
The first row of connections serves to connect the incoming
field bus cable. The second row of connections serves to
connect the continuing field bus cable.
The maximum permitted current at the terminals is 4 A.

Use cables with a minimum cross−sectional area of 0.34 mm2.
Open Style connection Pin no.
1. 0 V bus
2. CAN_L
1 2 3 4 5 3. Screen
4. CAN_H
5. 24 V DC bus (max. 4 A)
2x5−pin terminal strip
Tab.1/12: Pin assignment of the field bus interface

(Open Style connection, 5−pin)
If you connect the field bus via the terminal strip type
FBSD−KL−2x5POL from Festo, you can implement a T−tap
function (double row of screw terminals).

1. Installation
1.3.6 Example of connection
4 5 6
2
1 2 3 4 5
1 Micro Style connection with T−tap 3 Branch line

function (if the Micro Style connection
is removed completely with the plugs) 4 Field bus
2 T−adapter 5 Power supply
6 Screen
Fig.1/5: Structure of the bus interface and example of connection

1. Installation
1.3.7 Further connection possibility via the Sub−D connection
After removing the Micro Style or Open Style connection, you

will find a 9−pin Sub−D plug on the top of the field bus node.
This plug offers a further connection possibility to the field
bus (supply and continuation).
Pin DeviceNet Designation Field bus plug

from Festo (IP65)
1 n.c. Not connected

2 CAN_L CAN Low A/L
3 0 V bus Power supply to the bus interface GND
5 BUS screening Capacitive connection to housing Cable clip/SLD
6 GND optional
7 CAN_H CAN high B/H
9 24 V bus Power supply to the bus interface V+
1 5
6 9
(View of the Sub−D plug of the CPX−FB11)
Tab.1/13: Pin assignment of the field bus interfaceof the CPX−FB11
Please note
The screening connection at pin 5 of the Sub−D plug is
capacitively connected to the housing within the CPX
terminal. This prevents equalising currents from flowing
via the screening of the field bus cable (see Fig.1/6).

1. Installation
1 Capacitive 1 5
connection
6 9
2 Housing
1
Fig.1/6: Screening connection within the CPX terminal
Use a field bus plug from Festo for the connection:
type FBS−SUB−9−BU−2x4POL or
type FBS−SUB−9−BU−2x5POL−B
Please note
Note that only the Festo field bus plugs guarantee
compliance with protection class IP65.
Before using field bus plugs from other manufacturers:
· replace the two flat screws with bolts
(type UNC 4−40/M3x6).
Field bus plug from Festo

Screening connection A floating screening connection is intended with the field bus
plugs from Festo.
Please note
The cable clip in the Festo field bus plug is connected inter
nally only capacitively with the metal housing of the sub−D
plug. This is to prevent equalising currents flowing through
the screening of the field bus cable (Fig.1/8).
Please also follow the mounting instructions for the respect

ive field bus plug.

1. Installation
FBS−SUB−9−BU−2x5POL−B
· Fasten the shield of the field bus cable under the clamp
strap of the Festo sub−D socket (see Fig.1/7).
With this field bus plug, you can use the screening core of a
5−core cable: Connect the screening core to the SLD" con
nection in the field bus plug.
1 2 3
SLD
0Vbus
24Vbus
7
CAN_H
CAN_L
4 5 6
1 Hinged cover with display window 5 Field bus incoming

2 Screening connection under clamp 6 Field bus continuing
strap
7 Pin assignment in the field bus plug
3 Blanking plug if connection is not used
4 Only connected capacitively
Fig.1/7: Field bus plug from Festo type FBS−SUB−9−BU−2x5POL−B, pin assignment and
screening connection

1. Installation
FBS−SUB−9−BU−2x4POL
· Clamp the screening of the field bus cable under the cable
clip of the field bus plug (see Fig.1/8).
With this field bus plug, contact to the screening conductor is

only through the cable clip. This connects the incoming and
outgoing cable screening. With a 5−core cable, you can there
fore cut off the screening cores.
1 Screening
24Vbus
0Vbus
connection,
cableclip
1
2 Only connected
capacitively
4
3 CPX field bus
node 2 X
4 Pin assignment in
the field bus plug
CAN_H
CAN_L
BF PS
PL
SF
M
Fig.1/8: Field bus plug from Festo type FBS−SUB−9−BU−2x4POL, pin assignment and
screening connection

1. Installation
1.4 Bus termination with terminating resistors
Please note
Fit a bus termination to both ends of a bus segment. This
also applies if the bus circuit or bus interface is at the
beginning of the bus cable.
If the CPX terminal is at the end of the field bus system, a bus
termination will be required.
If you use T−adapters, we recommend that you install the

terminating resistor at the unused output of the T−adapter.
Recommendation:
Fit a resistor (121, 0.25 W) for the bus termination between
the connections for CAN_L and CAN_H. Fig.1/9 shows this as
an example with the Open Style connection.
1 Resistor for bus

termination 1
(121 ±1 %,
0.25W)
1 2 3 4 5
Fig.1/9: Bus termination with resistor on the Open Style connection

1. Installation
1.5 Pin assignment of power supply
Warning
· For the power supply, use only PELV circuits as per
IEC/DIN EN 60204−1 (Protective Extra−Low Voltage,
PELV).
Take into account also the general requirements for
PELV circuits as per IEC/DIN EN 60204−1.
· Use only power sources which guarantee reliable electri
cal isolation of the operating voltage as per IEC/DIN
EN60204−1.
By the use of PELV power units, protection against electric

shock (protection against direct and indirect contact) is guar
anteed in accordance with IEC/DIN EN 60204−1 (electrical
equipment of machines, general requirements).
The current consumption of a CPX terminal depends on the

number and type of integrated modules and components.
Read the information on power supply as well as on the

earthing measures to be carried out in the CPX system
manual.
1−28 Festo P.BE−CPX−FB11−E N en 0503b

1. Installation
System supply, The CPX terminal is supplied with operating and load volt
additional power supply ages via the manifold bases with system supply, additional
and valve supply supply and valve supply types CPX−GE−EV−S..., CPX−GE−EV−Z...
or CPX−GE−EV−V...
Plug Pin assignment of manifold base with

System supply Additional supply Valve supply
type CPX−GE−EV−S... type CPX−GE−EV−Z... type CPX−GE−EV−V...
1 1: 24 V EL/SEN 1: not connected 1: not connected

2: 24 VVAL / 24 VOUT 2: 24 VOUT 2: 24 VVAL
3: 0 VEL/SEN / 3: 0 VOUT 3: 0 VVAL
2 0 VVAL / 0 VOUT
4: Earth terminal 4: Earth terminal 4: Earth terminal
4
M18 3
C A: 24 VEL/SEN A: not connected A: not connected
B: 24 VVAL / 24 VOUT B: 24 VOUT B: 24 VVAL
D C: Earth terminal C: Earth terminal C: Earth terminal
D: 0 VEL/SEN / D: 0 VOUT (leading) D: 0 VVAL (leading)
0 VVAL / 0 VOUT
B (leading)
Pin designation Pin designation Pin designation
7/8"−4PIN
A Pay attention to the in Pay attention to the in Pay attention to the in
formation on the plug. formation on the plug. formation on the plug.
2 1: 0 VVAL / 0 VOUT 1: 0 VOUT

2: 0 VEL/SEN 2: not connected
3: Earth terminal 3: Earth terminal
1
(leading) (leading)
3
4: 24 VEL/SEN 4: not connected
4 5: 24 VVAL / 24 VOUT 5: 24 VOUT
7/8"−5PIN 5
VEL/SEN: Operating voltage for electronics/sensors
VOUT: Load voltage outputs
VVAL: Load voltage valves
Tab.1/14: Pin assignment for system supply, additional supply and valve supply
Festo P.BE−CPX−FB11−E N en 0503b 1−29

1. Installation

Commissioning
Chapter 2

2. Commissioning
Contents
2. Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−1
2.1 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−3

2.1.1 Ascertaining the address range . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−4
2.1.2 Address assignment of the CPX terminal . . . . . . . . . . . . . . . . . . . . . 2−8
2.1.3 Address assignment after extension/conversion . . . . . . . . . . . . . . 2−15
2.2 Bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−18
2.2.1 Switching on the power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−19
2.2.2 Configuring DeviceNet slave features (EDS) . . . . . . . . . . . . . . . . . . 2−20
2.2.3 Remarks on configuration on the DeviceNet . . . . . . . . . . . . . . . . . . 2−24
with standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−25
with modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−33
2.3 Parameterisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−41
2.3.1 Methods of parameterisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−43
2.3.2 Parameterisation with RSNetWorx with standard EDS . . . . . . . . . . 2−45
2.3.3 Parameterisation with RSNetWorx with modular EDS . . . . . . . . . . . 2−48
2.3.4 Notes on specific parameters of the DeviceNet . . . . . . . . . . . . . . . . 2−51
2.3.5 Parameterisation via the PLC user program . . . . . . . . . . . . . . . . . . . 2−54
2.3.6 Parameterisation with the handheld . . . . . . . . . . . . . . . . . . . . . . . . 2−56
2.4 Commissioning the CPX terminal on the DeviceNet . . . . . . . . . . . . . . . . . . . . 2−57

2. Commissioning
2.1 Addressing
Before configuring, ascertain the exact number of available

inputs/outputs. A CPX terminal consists of a different number
of I/Os, depending on what you have ordered and on the con
figuration of the field bus node. The I/Os will be assigned
automatically within the CPX terminal.
Please note
A maximum of 10 electric modules including the field
bus node plus a pneumatic interface or MPA pneumatic
module are permitted in a CPX terminal.
place.
The CPX terminal has an address range of up to 64 bytes
of inputs and 64 bytes of outputs.
Modular EDS
Starting with the software version of 12 Oct. 2005 (R16), the
CPX−FB11 supports the configuration with modular EDS.
The main features of modular EDS are:
With modular EDS, each module type has its own EDS
files (see section 2.2.2).
Configuration of technology modules, such as the

CPinterface, is supported only with modular EDS.
The modules’ address assignment is made bytewise and

may have a different order than with standard EDS
(seesection 2.1.2).
Setting modular EDS If you wish to use modular EDS, set the EDS mode to
modular EDS with the DIL switch 1 (see section 1.2.2).

2. Commissioning
2.1.1 Ascertaining the address range
Address assignment of the modules
Electric modules
The individual modules are displayed with their identifier on
the handheld. In the case of the I/O modules, the identifier is
also shown in the LED viewing window. With the aid of this
identifier, you can read the type of module and therefore the
number of inputs and outputs occupied by the module.
Electric modules 1) Type Module Assigned addresses

id tifi 2)
identifier Inputs Outputs
Field bus node FB11 CPX−FB11 FB11−...
Digital 4−input module CPX−4DE 4DI 4 I 4)
Digital 8−input module CPX−8DE 8DI 8I
Digital 8−input module with channel CPX−8DE−D 8DI−D 8I

diagnosis
Digital 4−output module CPX−4DA 4DO 4 O 4)
Digital 8−output module CPX−8DA 8DO 8O
Digital multi I/O module CPX−8DE−8DA 8DI/8DO 8I 8O
Analogue 2−input module CPX−2AE−U−I 2AI 32 I
Analogue 4−input module CPX−4AE−I 4AI−I 64 I
Analogue 4−input module CPX−4AE−T 4AI−T 32/64 I 3)

(temperature module)
Analogue 2−output module CPX−2AA−U−I 2AO 32 O

1) Some modules are in preparation
3) Number of inputs can be switched between 2 and 4
2) Module identifier in the handheld
4) With modular EDS, 8 bit always assigned
Tab.2/1: Overview of electric CPX modules (part 1)

2. Commissioning
Electric modules Type Module Assigned addresses

id tifi
CP interface CPX−CP−4−FB CPI 128 I 1) 128 O 1)
Front End Controller CPX−FEC FEC 64 I 64 O

1) Maximum number (actual assignment depends on branch assignment)
Tab.2/2: Overview of electric CPX modules (part 2)
The address assignment within the individual I/O modules

can be found in the manual for the I/O modules. Details on
the CP interface can be found in the manual for the CP inter
face.
Pneumatic modules and pneumatic interfaces

The following table shows the number of the output
addresses occupied by the pneumatic modules:
Pneumatic modules and Type Module Assigned addresses

pneumatic
ti interfaces
i t f 1) id tifi 2)
Pneumatic interface for MPA valves VMPA−FB−EPL−...

(type 32)
MPA1 pneumatic module (type 32) VMPA1−FB−EMS−8 3) MPA1S 8O

without electrical isolation
MPA1 pneumatic module (type 32) VMPA1−FB−EMG−8 3) MPA1G 8O

with electrical isolation
MPA2 pneumatic module (type 32) VMPA2−FB−EMS−4 3) MPA2S 4O

without electrical isolation
MPA2 pneumatic module (type 32) VMPA2−FB−EMG−4 3) MPA2G 4O

with electrical isolation
3) Type of electronic module used
Tab.2/3: Overview of pneumatic modules and pneumatic interfaces (part 1)

2. Commissioning
Pneumatic modules and Type Module Assigned addresses

pneumatic
ti iinterfaces
t f 1) id tifi 2)
Pneumatic interface for CPA valves CPX−GP−CPA−10 CPA10/14

(type 12) with adjustment: 3) CPX−GP−CPA−14
1...8 valve coils 8O
1...16 valve coils 16 O
1...24 valve coils (22 can be used) 24 O
Pneumatic interface for Midi/Maxi CPX−GP−03−4.0 TYPE3

valves (type 03) with setting:3)
1...32 valve coils (26 can be used) 32 O
Pneumatic interface for VTSA VABA−10S6−x1 ISO PlugIn or

pneumatics (ISO, type 44): 3) type44 4)
3) Setting with DIL switch in the pneumatic interface (see CPX−EA modules manual)
4) Depending on the version of the handheld
Tab.2/4: Overview of pneumatic modules and pneumatic interfaces (part 2)
The address assignment within the pneumatic modules can

be found in the manual for the valve terminal pneumatics.
Further information on MPA pneumatic modules can be found
in the manual for the CPX−EA modules (P.BE−CPX−EA−...).

2. Commissioning
Calculating the number of inputs/outputs

Use the following table to calculate the inputs and outputs of
your CPX terminal.
Input/output modules and system diagnosis Inputs Outputs
1. I/O diagnostic interface, if set + 16 IO + _____ I + _____ O
2. Number of input modules type CPX−4DE + __ x 4 I 1) + _____ I
3. Number of input modules CPX−8DE (−D) + __ x 8 I + _____ I
4. Number of output modules CPX−4DA + __ x 4 O 1) + _____ O
5. Number of output modules CPX−8DA + __ x 8 O + _____ O
6. Number of multi I/O modules CPX−8DE−8DA + __ x 8 IO + _____ I + _____ O
7. Number of analogue input

modules CPX−2AE−U−I + __ x 32 I + _____ I
8. Number of analogue input

modules CPX−4AE−I + __ x 64 I/ x 32 I + _____ I
9. Number of analogue input modules CPX−4AE−T + __ x 64 I + _____ I
10.Number of analogue output modules CPX−2AA−U−I + __ x 32 O + _____ O
11.Number of inputs and outputs of other modules + __ IO + _____ I + _____ O

(e.g. CP interface)
12.Midi/Maxi, CPA or VTSA pneumatic interface: + _____ O

Number of configured valve solenoid coils
(+ 8 O, 16 O, 24 O, 32 O)
Configured at the factory are 32 O (Midi/Maxi, VTSA)
or 24 O (CPA).
13.Number of MPA1 pneumatic modules + __ x 8 O + _____ O
14.Number of MPA2 pneumatic modules + __ x 4 O 1) + _____ O
15.Total sum of inputs/outputs to be configured

Sum of 1 to 14: = _____ I = _____ O
1) Only for configuration with classical EDS file. For modular EDS, these modules occupy 8 I or O
(4 are unused).
Tab.2/5: Calculating the number of inputs/outputs

2. Commissioning
2.1.2 Address assignment of the CPX terminal
Please note
A CPX terminal with field bus node FB11 makes 8 status
bits available. These 8 status bits must be transmitted
separately via a Strobed I/O" connection.
If necessary, an I/O diagnostic interface can be activated
by a DIL switch. If the interface is active, it will occupy
the first 16 inputs and outputs in the address range.
place!
Basic rules for addressing

The address assignment of the inputs does not depend on
the address assignment of the outputs.
Counting mode:
with standard EDS: from left to right in ascending

order without gaps, depending on the module type
and independent of the position of the field bus node.
with modular EDS: from left to right, addressing byte

wise: Modules with less than 8 bits occupy 8 bits of
address space but do not use it completely. The field
bus node must be installed as module 0.
The field bus node counts as a module with 0inputs and

0 outputs if the status bits and the I/O diagnostic inter
face are deactivated.
The I/Os of various module types are assigned separately

from each other.
The following order applies:

2. Commissioning
Sequence of addressing Description
1. I/O diagnostic interface 1) Can be activated by DIL switch. When activated, it will occupy
the first 16 inputs and outputs in the address range.
2. Analogue modules Modules with analogue inputs/outputs
3. Technology module e.g. CP interface, front−end controller CPX−FEC
4. Digital modules Modules with digital inputs/outputs

1) In exceptional cases this address range can also be occupied by status bits (see Tab.1/3).
Tab.2/6: Sequence of addressing
Configuration examples
Example 1: CPX terminal with MPA1 and MPA2 pneumatics

The following illustration shows a CPX terminal with MPA
pneumatics and the following setting:
Status bits and /I/O diagnostic interface deactivated
Module no.: 0 1 2 3 4 5 6
8DI 4DO 8DI 8DO
8O 8O 4O 4O
1 2 3 4
1 Field bus node CPX−FB11 3 MPA1 pneumatic modules (each 8DO)

2 MPA pneumatic interface 4 MPA2 pneumatic modules (each 4DO)
Fig.2/1: Example terminal 1 (with MPA1 and MPA2 pneumatics)

2. Commissioning
The following table shows address assignments for the CPX

terminal in Fig.2/1:
Module Module Standard EDS addressing Modular EDS addressing

no.
Input Output Input Output
address address address address
0 Field bus node

CPX−FB11
1 Digital 8−input I0 ... I7 I0 ... I7

moduleCPX−8DE
2 Digital 4−output O0 ... O3 O0 ... O7 *)

module CPX−4DA
3 MPA1 pneumatic O4 ... O11 O8 ... O15

modules (8DO)

module (8DO)
5 MPA2 pneumatic O20 ... O23 O24 ... O31 *)

module (4DO)
6 MPA2 pneumatic O24 ... O27 O32 ... O39 *)

module (4DO)
*) 8 bits occupied 4 bits used
Tab.2/7: Addressing the example terminal 1 (see Fig.2/1)
When modular EDS is used, the addresses are assigned

bytewise. In the above example, the output addresses change
starting with modules 2, 5 and 6.

2. Commissioning
Example 2: CPX terminal with CP interface

The address assignments for this CPX terminal are shown in
the next page in Tab.2/8. The settings are:
Status bits and /I/O diagnostic interface deactivated
Module no.: 0 1 2 3 4 5 6
8DI 4DO 8DI 8DO
8O 8O
2
4
1 Field bus node CPX−FB11 4 Sensor

2 CPV valve island (16DO) on the 5 Cylinder
CPinterface (branch1)
6 CP output module (16DO) on the
3 CP input module (16DI) CPinterface (branch 4)
Fig.2/2: Example terminal 2 (with CP interface)

2. Commissioning

no.
0 Field bus node

CPX−FB11

module CPX−8DE

module CPX−4DA
3 CP interface I0 ... I31 O0 ... O127 I0 ... I31 O0 ... O127

CP I, here: 4 bytes I,
16 bytes O
4 Digital multi I/O I40 ... I47 O132 ... O139 I40 ... I47 O136 ... O143
module
CPX−8DE−8DA

module (8DO)

module (8DO)

2. Commissioning
Example 3: CPX terminal with analogue module and

CPApneumatics
The address assignments for this CPX terminal are shown in
the next page in Tab.2/9. The settings are:
Status bits activated and I/O diagnostic interface

deactivated
Pneumatic interface set with DIL switch to 1...8 valve coils

(8DO).
Module no.: 0 1 2 3 4 5 6
ÓÓ ÓÓ
ÓÓ ÓÓ
8DI 8DI 4DO 8DI 8DO 2AO
ÓÓ
ÓÓ ÓÓ
ÓÓ
8O
ÓÓ ÓÓ
1 2 3
1 Field bus node CPX−FB11 3 CPA pneumatics

(with DIL 3.2 to ON for status bits)
2 Pneumatic interface
(set with DIL switch to 1...8 valve coils)
Fig.2/3: Example terminal 3 (with analogue module and CPA pneumatics)

2. Commissioning

no.
0 Field bus node I0 ... I7 I0 ... I7

CPX−FB11

module CPX−8DE

module CPX−8DE

module CPX−4DA
module
CPX−8DE−8DA
5 Analogue 2−output O0 ... O31 O0 ... O31

module CPX−2AA
6 CPA pneumatic O44 ... O51 O48 ... O55

interface set with
DIL switch to
1...8valve coils

2. Commissioning
2.1.3 Address assignment after extension/conversion
A special feature of the CPX terminal is its flexibility. If the

demands placed on the machine 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:
Additional modules are inserted between existing
modules.
Existing modules are removed or replaced by other mod
ules which have more or fewer input/output addresses.
Manifold bases (CPA) or pneumatic connection bases
(Midi/Maxi) for single−solenoid valves are replaced by
manifold bases/connection bases for double−solenoid
valves or vice versa (see pneumatics manual).
Additional manifold bases (CPA) or connection bases
(Midi/Maxi) are inserted between existing bases.
Status bits or the I/O diagnostic interface are activated/
deactivated.

2. Commissioning
Example terminal 3 Using example terminal 3 (see Fig.2/3), the next illustration
changed shows the effects of addressing changes.
The following has been changed:
The I/O diagnostic interface has been activated.
For module no. 1, an 8−input module has been replaced

by a 4−input module.
In the CPA pneumatics, a valve disc was added (not

shown in the illustration) and the pneumatic interface was
set to 16 O.
Module no.: 0 1 2 3 4 5 6
ÓÓ ÓÓ
ÓÓ ÓÓ
ÓÓ
ÓÓ ÓÓ
ÓÓ
16 O
ÓÓ ÓÓ
1 2 3
1 Changed: Field bus node CPX−FB11 3 Changed: Pneumatic interface (now set
now with activated I/O diagnosis with DIL switch to 1...16 valve coils)
interface
2 Changed: 8DI module replaced by

4DImodule
Fig.2/4: Example terminal 3 after expansion/conversion (compare with Fig.2/3)

2. Commissioning

no.
0 Field bus node I0 ... I15 O0 ... O15 I0 ... I15 O0 ... O15
CPX−FB11 with
activated I/O
diagnosis interface
1 Digital 4−input I16 ... I19 I16 ... I23*)

module CPX−4DE

module CPX−8DE

module CPX−4DA
module
CPX−8DE−8DA
5 Analogue 2−output O16 ... O47 O16 ... O47

module CPX−2AA
6 CPA pneumatic O60 ... O75 O64 ... O79

interface set with
DIL switch to
1...16valve coils
*) 8 bits occupied 4 bits used, bold = changed module
Tab.2/10: Addressing the example terminal 3 after expansion/conversion (see Fig.2/4)

2. Commissioning
2.2 Bus configuration
General instructions on commissioning

Before commissioning or programming, compile a configur
ation list of all connected field bus slaves. On the basis of this
list you can:
carry out a comparison between the NOMINAL and the

ACTUAL configurations to ascertain if there are any
connection faults.
recognise a faulty device after a service replacement.
Configuration of the CPX terminal requires a very accurate

procedure, as different configuration specifications may be
necessary for each slave on the DeviceNet, due to the modu
lar structure. Note here the specifications in the sections
which follow.

2. Commissioning
2.2.1 Switching on the power supply
Please note
Observe here also the instructions in the manual for your
controller with DeviceNet module.
When a controller with DeviceNet module is switched on, it

automatically carries out a comparison between the
NOMINAL and the ACTUAL configurations. It is important for
this configuration run that:
the configuration specifications are complete and correct
the bus interface is supplied with power
the field bus slaves are supplied with power, in order that
they can be recognised when the ACTUAL configuration is
ascertained.
Therefore after switching on the power supply for the bus

interface, switch on the power supply for all the field bus
slaves simultaneously, e.g. by means of a central switch.
Or switch on the power supply in the following sequence:
1. the power supply for the bus interface
2. the power supply for all the field bus slaves
3. the power supply for the controller.

2. Commissioning
2.2.2 Configuring DeviceNet slave features (EDS)
When you commission a new DeviceNet slave the first time,

you must inform your configuration program about certain
features of the slave.
The features of the various slaves are usually administered by

the configuration program in a list or library, e.g. EDS library
(EDS for electronic data sheets).
The following possibilities are available for extending an EDS

library:
Install an EDS file: standard EDS or modular EDS. Para

meterisation of technology modules, such as the CP inter
face, is supported only with modular EDS.
Enter slave features manually (only by using the para

meter settings set at the factory).
Sources for EDS files

Source Current EDS files, icons and information on the EDS files can
be found under the following address in Internet:
www.festo.com/fieldbus
The EDS files are available at first in packed format.
1. Download the packed file from the Internet.
2. Unpack the EDS and icon files contained in the file into a
directory of your choice.
3. Install the files with your configuration program

(seebelow).

2. Commissioning
Installing a standard EDS file
You will find information on the installation of EDS files and

symbol files in your configuration program’s documentation.
You will require the following information for the CPX terminal:
File type File name Language Description
EDS DNIO..CPX−DE.EDS German (de) EDS files for CPX terminals fitted with different
types of equipment 1)
DNIO..CPX−EN.EDS English (en)
ICO DNIOXCPX.ICO Icon file
BMP DNIOXCPX.BMP Bitmap file

1) EDS files which support different combinations of digital and analogue modules within a
CPX terminal are available (see also Tab.A/2).
Tab.2/11: Configuration files for the CPX field bus node for DeviceNet
For the CPX terminal in the Remote Controller operating mode

(e.g. with a CPX−FEC), you need the following files:
EDS CPX−FB11−RC.EDS English (en) EDS files for CPX terminals in the Remote
Controller operating mode
ICO CPX−FB11−RC.ICO Icon file
BMP CPX−FB11−RC.BMP Bitmap file
Tab.2/12: Configuration files for the CPX field bus node for DeviceNet
EDS file The EDS file contains all the necessary features of the CPX
terminal.
Symbol files Depending on the configuration program used, you can as
sign symbol files (format .ico or .bmp) to the CPX terminal.
The CPX terminal will then be represented accordingly in the
configuration program.

2. Commissioning
Installing a modular EDS file

You will require the following information for the CPX terminal:
EDS cpx_chassis.eds English Base file for modular EDS.
EDS cpx_fb11...eds English Provides the communication adapter in the

configuration program.
EDS cpx_...eds English There is an EDS file for every module type. It
contains the information needed for
configuration and parameterisation.
ICO cpx_...ico Icon file for depicting the CPX terminal or

module in the configuration program.
Tab.2/13: Configuration files (modular EDS) for the CPX terminal for DeviceNet
Installing modular · Install the files with your configuration program.

EDSfiles
You must install at least the Chassis EDS and the EDS files of
the required modules.
Recommendation: Install all EDS files.
Symbol files Depending on the configuration program used, you can

assign symbol files (format .ico) to the CPX terminal or CPX
modules. The CPX terminal or the modules will then be
represented accordingly in the configuration program.
You will find information on the installation of EDS files and

symbol files in your configuration program’s documentation.

2. Commissioning
Entering slave features manually

When an EDS file is installed, the following information about
the DeviceNet slave is added to the EDS library. This informa
tion can also be entered manually, if the CPX terminal is to be
operated with the parameter settings preset at the factory.
Information Description Description

Standard EDS Modular EDS
Vendor name Festo Corporation
Vendor ID 26D 1AH
Device Type / Product Type 12D CH
Product code (depends on operating mode)

Remote I/O without diagnosis 4554D 11CAH 4556D 11CCH
Remote I/O with status bits 4557D 11CDH
Remote I/O with I/O diagnosis interface 4558D 11CEH
Remote Controller 4555D 11CBH
Major revision / Minor revision All versions From V 2.14

(RemoteController)
from V 2.16 (Remote I/O)
Input size / Output size Depends on CPX equipment
Product name CPX−FB11
Catalogue number 526172
Tab.2/14: Slave features
Please note
If the slave features are entered manually, individual para
meterisation of the CPX terminal is not possible.
When the EDS library has been extended, the CPX terminal is
entered in the slave list as a possible DeviceNet slave. It can
now be added to a network.

2. Commissioning
2.2.3 Remarks on configuration on the DeviceNet
When the slave features have been configured (e.g. by in

stallation of the EDS file), the following steps are required for
parameterisation, depending on the configuration program.
1. Insert the slave into the project/network (online or

offline). If the slave is inserted offline, it will be selected
from the slave list and added to the network.
2. Assign the slave to a scanner. A network can contain

several scanners. The slave must be assigned to a
scanner.
3. Define the I/O parameters of the slave. The following

entries are required here:
· Number of I/O bytes to be transferred. The following

applies to the CPX terminal: The value depends on the
equipment fitted on the CPX terminal. It can be calcu
lated manually or be read out online by means of the
device features.
· Specification of the communication type. The follow

ing communication types are permitted with the CPX
terminal:
Polled Communication"
or
Change of State / Cyclic"
In addition to these communication connections, a

Strobed I/O" connection must be used in each case
for transmitting the status bits.

2. Commissioning
Please note
The following applies to an SLC 500 with an Allen−Bradley
scanner type 1747−SDN:
Change of State / Cyclic" can be used in combination
with the diagnosis via Strobed I/O" only starting with
software version V4.015 of the scanner.
Polled I/O" with Strobed I/O" is also supported by
earlier versions.
· Assign the I/O addresses of the slave to the

PLCoperands.
· 1. Assign one diagnostic byte to the PLC operands.
4. Load the configuration into the scanner.
2.2.4 Configuration with RSNetWorx for DeviceNet with standard EDS
This section gives instructions on configuring with RSNetWorx

for DeviceNet version 4.01.00 from Rockwell.
Please note
All steps listed refer to the Allen−Bradley scanner
1747−SDN as example. They apply accordingly to other
masters.
Insert the slave into the project/network

RSNetWorx for DeviceNet contains an assistant (EDS Wizard)
which will support you in installing the EDS file. After instal
ling the EDS−file, you will find the CPX terminal in the Hard
ware" list. By shifting the mouse, you can insert slaves in the
network on the right−hand side.

2. Commissioning
1 CPX terminal with field bus node CPX−FB11 (standard EDS)

Fig.2/5: Hardware list and network in RSNetWorx for DeviceNet with standard EDS

2. Commissioning
Assign the slave to a scanner

1. Double−click the desired scanner in the network.
A dialogue box will open.
2. Select the Scanlist" register and assign the existing

slaves to the scanner.
1 Button for assigning the slave

Fig.2/6: Scanlist" register (example)

2. Commissioning
Set the I/O parameters of the slave

1. Double−click a slave in the Scanlist" (Fig.2/6).
The dialogue box Edit I/O Parameters" will open.
2. Determine the I/O parameters of the slave and confirm

with OK.
In online mode you can read out the number of available in
puts and outputs via the system data Rx size" and Tx size"
(see also section 2.3).
Fig.2/7: Determining the I/O parameters of the slave

(example)
As an example, the CPX terminal’s I/O parameter from

example 3 are set:
Communication type Strobed" for diagnosis information
Status bits (1 input byte)
Communication type Polled" for I/O data:

4 input bytes for status bits and CPX input modules,
7 output bytes for CPX output modules and the pneu
matic interface.

2. Commissioning
Assign the I/O addresses of the slave

With the registers Input" and Output", you can assign the
I/O addresses of the CPX terminal to the PLC operands.
Fig.2/8: Address assignment of the input (example)
The CPX terminal appears in the input data with two separate
communication connections:
A Strobed" connection for transmitting the 8 status bits

(diagnostic information).
A Polled" or Change of State" connection for transmit

ting the physical input data.

2. Commissioning
The physical output data are transmitted with the communi

cation connection Polled" or Change of State." In this
example Polled":
Fig.2/9: Address assignment of the output (example)
Load the configuration into the scanner

Finally, load the configuration data into the scanner. Further
information can be found in the documentation for the
scanner.

2. Commissioning
Example: scanner 1747−SDN (SLC 500 series)

Addressing for example terminal 3 with:
2 input bytes for status bits (strobed data)

The status bits are switched on via the DIL switch 3
(see Tab.1/3)
3 input bytes, input address as from I1.1.8
7 output bytes, output address as from O1.1.0
Module no.: 0 1 2 3 4 5 6
ÓÓ ÓÓ
ÓÓ ÓÓ
ÓÓ
ÓÓ ÓÓ
ÓÓ
8O
ÓÓ ÓÓ
1 2 3
1 Field bus node CPX−FB11 3 CPA pneumatics

(with DIL 3.2 to ON for status bits)
2 Pneumatic interface
(set with DIL switch to 1...8 valve coils)
Fig.2/10: CPX example terminal 3

(address example for scanner 1747−SDN, see following table)

2. Commissioning
The sequence in Tab.2/6 applies for addressing.
Module Module Addressing

no.
Input address Output address
0 Field bus node CPX−FB11 I1.1.0 ... I1.1.15

(DIL 3.2 to ON for
status bits)
1 Digital 8−input module CPX−8DE I1.2.0 ... I1.2.7
3 Digital 4−output module CPX−4DA O1.3.0 ... O1.3.3
4 Digital multi I/O module I1.3.0 ... 1.3.7 O1.3.4 ... O1.3.11
CPX−8DE−8DA
5 Analogue 2−output module O1.1.0 ... O1.1.15

CPX−2AA O1.2.0 ... O1.2.15
6 CPA pneumatic interface set with O1.3.12 ... O1.3.15

DIL switch to 1...8 valve coils O1.4.0 ... O1.4.3
Tab.2/15: Addressing example for scanner 1747−SDN with CPX example terminal 3 and
standard EDS

2. Commissioning
2.2.5 Configuration with RSNetWorx for DeviceNet with modular EDS
This section gives instructions on configuring with RSNetWorx

for DeviceNet version 4.01.00 from Rockwell.
Please note
All steps listed refer to the Allen−Bradley scanner
1747−SDN as an example. They apply accordingly to other
masters.
Insert the slave into the project/network

RSNetWorx for DeviceNet contains an assistant (EDS Wizard)
which will support you in installing the EDS files. After instal
ling the modular EDS files, you will find three entries for the
CPX terminal in the Hardware" list for configuration with
modular EDS.
CPX−FB11 Modular RIO"

CPX terminal without status bits and without I/O
diagnosis interface
CPX−FB11 Modular RIO Diag. Interface"

CPX terminal with activated I/O diagnosis interface
CPX−FB11 Modular RIO Status bits"

CPX terminal with status bits
With the mouse, pull the corresponding entry into the

network on the right−hand side. This configuration must
correspond to the setting of the DIL switch 3 (see Tab.1/3).

2. Commissioning
1 CPX terminal with field bus node CPX−FB11 for modular EDS
2 CPX terminal in the network
Fig.2/11: Hardware list and network in RSNetWorx for DeviceNet (modular EDS)

2. Commissioning
Assign the slave to a scanner (modular EDS)

1. Double−click the desired scanner in the network.
A dialogue box will open.
2. Select the Scanlist" register and assign the existing

slaves to the scanner.
1 Button for assigning the slave

Fig.2/12: Scanlist" register (example)

2. Commissioning
Configure CPX modules (modular EDS)

1. Double−click the CPX terminal in the network
(seeFig.2/11). A dialogue box will open.
2. Select the Module Configuration" register.

To use modular EDS, the field bus node must be installed
on place 0. In the dialogue box, the field bus node is
already entered in place 0.
3. Pull the CPX module in accordance with your CPX ter

minal’s equipment into the configuration table on the
right−hand side. The illustration shows the configuration
for the example terminal 2 from Fig.2/2:
Fig.2/13: Module configuration with modular EDS

(example terminal 2)

2. Commissioning
With the I/O Summary" register, you can show the number
of occupied bytes of the inputs and outputs.
The I/O parameters of the CPX terminal from example 2 are

(see Fig.2/3):
Communication type Polled" for I/O data:

6 input bytes for CPX input modules and the CP interface.
20 output bytes for CPX output modules, the CP interface
and the MPA pneumatic modules.
Fig.2/14: Display of the occupied I/O bytes

(example 2, mod. EDS)
The above illustration shows the position of the modules in

the CPX terminal, but not the real I/O mapping!

2. Commissioning
Assign the I/O addresses of the slave (mod. EDS)

1. Double−click on the scanner in the network. A dialogue
box will open.
2. With the registers Input" and Output", you can assign

the I/O addresses of the CPX terminal to the PLC
operands.
Fig.2/15: Address assignment of the input


2. Commissioning
The physical output data are transmitted with the communi

cation connection Polled" or Change of State". In this
example Polled":
Fig.2/16: Address assignment of the output

Load the configuration into the scanner

Finally, load the configuration data into the scanner. Further
information can be found in the documentation for the
scanner.
Example: scanner 1747−SDN (SLC 500 series)

Addressing for example terminal 2 (CPX terminal with
CPInterface, see Fig.2/2) with:
6 input bytes, input address as from I1.1.0
20 output bytes, output address as from O1.1.0

2. Commissioning
The sequence in Tab.2/6 applies for addressing.
Module Module Addressing

no.
Input address Output address
0 Field bus node CPX−FB11
2 Digital 4−output module CPX−4DA O1.9.0 ... O1.9.7 *)
3 CP interface I1.1.0 ... I1.1.7 O1.1.0 ... O1.1.7

CP I, here: 4 bytes I, 16 bytes O I1.1.8 ... I1.1.15 O1.1.8 ... O1.1.15
I1.2.0 ... I1.2.7 O1.2.0 ... O1.2.7
I1.2.8 ... I1.2.15 O1.2.8 ... O1.2.15
O1.3.0 ... O1.3.7
O1.3.8 ... O1.3.15
O1.4.0 ... O1.4.7
O1.4.8 ... O1.4.15
O1.5.0 ... O1.5.7
O1.5.8 ... O1.5.15
O1.6.0 ... O1.6.7
O1.6.8 ... O1.6.15
O1.7.0 ... O1.7.7
O1.7.8 ... O1.7.15
O1.8.0 ... O1.8.7
O1.8.8 ... O1.8.15
4 Digital multi I/O module I1.3.7 ... 1.3.15 O1.9.8 ... O1.9.15
CPX−8DE−8DA
5 MPA1 pneumatic module (8DO) O1.10.0 ... O1.10.7
6 MPA1 pneumatic module (8DO) O1.10.8 ... O1.10.15

*) 8 bits occupied, 4 bits used
Tab.2/16: Addressing for scanner 1747−SDN with CPX example terminal 2 (seeFig.2/2)
with modular EDS

2. Commissioning
2.3 Parameterisation
Caution
A different parameterisation will result in a different reac
tion. Check especially when replacing CPX terminals to see
which settings are necessary and make sure that these
settings, where applicable, are carried out (e.g. in the
start−up phase by the higher−order PLC/IPC).
The CPX terminal is supplied with preset parameters.
The system reaction of the CPX terminal can usually be

adapted to the relevant application. You can set the reaction
of the CPX terminal as well as the reaction of individual mod
ules and channels by parameterisation. A distinction is made
between the following parameterisations:
system parameterisation, e.g.: switching out fault

messages, setting reaction times, etc.
module parameterisation (module and channel−specific),

e.g.: monitoring, settings in the event of faults, settings
for forcing
parameterisation of the diagnostic memory.
A detailed description of the individual parameters as well as

basic information on application can be found in the CPX sys
tem manual (P.BE−CPX−SYS−...).
The module parameters which are available for the various
modules can be found in the manual for the relevant module
(e.g. manual for CPX pneumatic interfaces and CPX I/O mod
ules (P.BE−CPX−EA−...).

2. Commissioning
Prerequisites for parameterisation

With the system parameter System start", you can influence
the starting reaction. If possible, select the setting System
start with default parameterisation and current CPX system
equipment". The desired parameterisation can then be car
ried out in the initialisation phase or controlled by the user
(depending on the field bus used).
Please note
The CPX terminal can only be parameterised if the system
parameter System start" has the setting System start
with default parameterisation and current CPX system
equipment".
If the M LED lights up permanently after the system start,

then System start with saved parameterisation and CPX
equipment" is set. In this case, no other parameterisation can
be carried out.
Caution
In the case of CPX terminals on which the M LED lights up
permanently, parameterisation will not be restored auto
matically by the higher−order system if the CPX terminal is
replaced during servicing. In these cases, check before
replacement to see which settings are required and carry
out these settings.

2. Commissioning
2.3.1 Methods of parameterisation
The CPX terminal with field bus node CPX−FB11 can be para
meterised in various ways. The following table provides an
overview of the methods.
Method Description Advantages Disadvantages
Parameterisation via The parameters are set Fast, simple para Parameterisation is
the configuration via the configuration meterisation during saved locally in the
program (e.g. program and trans commissioning for CPX terminal and is
RSNetWorx) mitted directly to the testing the para lost when the ter
DeviceNet slave. meters minal is replaced. 1)
Parameterisation via The parameters are set Parameters are The scanner must
the scanner auto via the configuration loaded again support ADR
matically after Power program and trans automatically after (automatic device
On (configuration mitted to the scanner. Power On and are replacement).
recovery via ADR) The parameters are therefore retained if
transmitted by the the CPX terminal is
scanner after Power On. replaced.
Parameterisation via Parameterisation is Parameterisation is Explicit message

the PLC user program carried out within the saved in the PLC programming
user program in the required
PLC/IPC via Explicit
Message".
Parameterisation Parameterisation is Very user−friendly Parameterisation is

with the handheld 1) carried out via menu− parameterisation via saved locally in the
listed entries with the menu−guiding (plain CPX terminal and is
handheld. text). lost if the CPX ter
minal is replaced. 1)
1) It is possible to copy the current parameter settings with the aid of the handheld.
Tab.2/17: Methods of parameterisation

2. Commissioning
Recommendation:
Use the ADR function (automatic device replacement) or the
explicit message programming. If the parameters are trans
mitted to the CPX terminal after Power On, the settings will be
retained even if a CPX terminal is replaced.
Please note
The last parameterisation received in the CPX terminal is
always valid.
The CPX terminal can only be parameterised if the system

parameter System start" has the setting System start with
default parameterisation and current CPX system equipment".
In this case, the standard parameter settings are valid in the
CPX terminal after Power On.
Please note
If the system parameter System start" has the setting
System start with saved parameterisation and saved CPX
system equipment", modified parameter settings in the
CPX terminal will become valid immediately after Power
On.

2. Commissioning
2.3.2 Parameterisation with RSNetWorx with standard EDS
With RSNetWorx, you can carry out parameterisation with the

aid of the Parameters" register card of the relevant DeviceNet
slave.
The prerequisite is that the EDS file of the relevant DeviceNet

slave is contained in the EDS library (see section 2.2.2).
The following diagram shows the Parameters" register of the

CPX terminal:
Fig.2/17: Parameterisation with standard EDS
The settings saved in the project are displayed in offline

mode.

2. Commissioning
With the Groups" check box, you can display the parameters
and data grouped in folders.
1 4
3
2
1 Groups" check box

2 Parameters and data grouped in folders
3 Set parameters with list field
4 Buttons for online display (monitor), upload and
download parameters
Fig.2/18: Selection of parameters and data with standard

EDS

2. Commissioning
Changing parameters Click on a value (Current Value) and change it in the list field
or in a separately opening window.
Transfer parameters In online mode you can transfer parameters and display
them online with the appropriate buttons (see 3in
Fig.2/18).
Note the following in online mode:
In online mode the settings of the CPX terminal will be

transmitted and displayed when accessed. Transmission
of the values requires a certain amount of time.
Current values are continuously displayed only in monitor

mode. However, there is no detail representation.

You can find notes on specific parameters of the DeviceNet in
section 2.3.4.

2. Commissioning
2.3.3 Parameterisation with RSNetWorx with modular EDS
When modular EDS is used, you can set the parameters by

module with RSNetWorx.
The prerequisite is that the modular EDS files of the CPX

terminal are contained in the EDS library (see section 2.2.2).
The following diagram shows the Module Configuration"

register of the CPX terminal. Double clicking on the module in
the configuration table brings you to the window for setting
the parameters.
1 Buttons for upload and download of 2 System parameters and data

the parameters
3 Module parameters
Fig.2/19: Parameterisation with modular EDS

2. Commissioning
Double clicking on the module in the configuration table

brings you to the windows for setting the parameters
(seeFig.2/20 and Fig.2/21).
The settings saved in the project are displayed in offline

mode.
System parameters · Double−click on the field bus node in the configuration

table. Set the system parameters in the displayed
window in the Configuration Settings" register.
Confirm twice with OK.
1 Set parameters with list field

Fig.2/20: System parameters and data with modular EDS

2. Commissioning
Module parameters · Double−click on the CPX modules in the configuration

table. Set the module parameters in the displayed
window in the Advanced Parameters" register.
Confirm twice with OK.
1 Set parameters with list field or via detail

representation
Fig.2/21: Module parameters and data with modular EDS
Transfer parameters In online mode you can transfer parameters with the
appropriate buttons (see 1in Fig.2/19).
Note the following in online mode:
In online mode the settings of the CPX terminal will be

transmitted and displayed when accessed. Transmission
of the values requires a certain amount of time.
Current values are continuously displayed only in monitor

mode. However, there is no detail representation.

2. Commissioning

You can find notes on specific parameters of the DeviceNet in
section 2.3.4.
2.3.4 Notes on specific parameters of the DeviceNet
Reaction of the outputs in theIdle mode

The Idle mode is assumed by the slaves upon request by the
master or scanner. The following applies in this example:
Inputs are transferred
Output channels of the slaves are no longer updated.
In the Idle mode, outputs can assume one of the following

states:
Digital outputs/valves Analogue outputs
Freeze current status Freeze current status
Reset the output Desired analogue value
Set the output
Tab.2/18: Possible states in the Idle mode
You can determine the status to be assumed for each output

channel (output or solenoid coil) separately. The standard
setting is Reset output channel".
Further information can be found in the CPX system manual.

2. Commissioning
Automatic parameterisation via the scanner
For modular EDS, you need RSNetWorx version 5 or later for

automatic parameterisation.
In order to force automatic parameterisation when a

CPXterminal is replaced or after Power on:
1. Make sure that the system parameter System start" of

the CPX terminal is set to System start with default
parameterisation and current CPX equipment status"
(presetting).
Otherwise the parameters of the CPX terminal are
write−protected. Automatic parameterisation is then not
possible.
2. Double−click on the scanner in the network.
3. In the ADR" (Automatic Device Replacement) register

under Available Devices", mark the CPX terminal.
4. Under ADR Settings", choose the setting Configuration

Recovery".
The scanner then automatically loads the set parameters into

the CPX terminal before it exchanges I/O data with the CPX
terminal.

2. Commissioning
1 Setting [Configuration Recovery]

Fig.2/22: Setting for automatic parameterisation after
Poweron

2. Commissioning
2.3.5 Parameterisation via the PLC user program
Program−controlled access to parameters is made via the

Explicit Message" programming. The addresses of the
DeviceNet object model necessary for this can be found in
appendix B.1 and C.1. Refer to your controller manual for
information on programming this data transfer.
In order to address the CPX terminal with standard EDS, you

will require the following object descriptions:
Object Instances Attributes Name Type

classes (dez.) (dez.)
100d 1 ... 78 75 Parameter Object Module (various)
4d 100 ... 102 Assembly object instances (various)
107d 1 ... 32 1 ... 6 Modification of digital outputs, object WORD
109d 1 ... 32 1, 2 Modification of digital inputs, object WORD
110d 1 ... 32 1 ... 6 Modification of analogue outputs, object (various)
111d 1 ... 32 1, 2 Modification analogue inputs, object (various)
112d 1 ... 32 1 ... 6 Modification of output words function WORD

module, object
113d 1 ... 32 1, 2 Modification of input words function WORD

module, object
114d 1 1 ... 37 Module−independent system object SINT
115d 1 1 ... 3 Status and diagnostic object (various)
116d 1 ... 40 1 ... 12 Diagnostic trace object SINT
117d 1 1 ... 13 Diagnosis of trace status object (various)
Tab.2/19: Object classes for standard EDS (overview)
Detailed object descriptions for standard EDS can be found in

appendix B.1.

2. Commissioning
In order to address the CPX terminal with modular EDS, you

will require the following object descriptions:
Object Instances Attributes Name Type

classes (dez.) (dez.)
115d 1 100 ... 102 Status and diagnostic object (various)
114d 1 1 ... 37 Module−independent system object USINT/BYTE
102d 1 ... 32 99 ... 134 Parameter Object Module (various)
120d 1 ... 32 1 ... 188 General object module parameters (various)
104d 1 ... 32 100 ... 172 Modification of digital inputs, object WORD
125d 1 ... 32 100 ... 172 Modification of digital outputs, object WORD
126d 1 ... 32 100 ... 172 Modification of analogue outputs, object (various)
127d 1 ... 32 100 ... 172 Modification of analogue inputs, object (various)
116d 1 ... 40 1 ... 12 Diagnosis of trace object USINT/BYTE
117d 1 1 ... 13 Diagnosis of trace status object (various)
Tab.2/20: Object classes for modular EDS (overview)
Detailed object descriptions for modular EDS can be found in

appendix C.1.

2. Commissioning
2.3.6 Parameterisation with the handheld
The CPX handheld offers menu−orientated access to para

meterise the CPX terminal without configuration software.
Information on operating the handheld can be found in the

relevant manual.

2. Commissioning
2.4 Commissioning the CPX terminal on the DeviceNet
In order to avoid faults (e.g. configuration and parameterisa

tion faults) during commissioning:
· Observe the general commissioning instructions in the

CPX system manual.
· Check the DIL switch settings before using and replacing

CPX terminals.
· Note the instructions on switching on the power supply in

section 2.2.1.
· Check the configured address range (process data and

assigned input and output bytes). If necessary, test the
I/Os.
· Check the address assignment of the I/Os on the CPX

terminal. For this purpose, you can force the I/Os (see
CPX system manual).
· Make sure that the desired parameterisation of the CPX

terminal in the start−up phase or after field bus interrup
tions is carried out by the module. This is to ensure that if
the CPX terminal is replaced, the new terminal will also be
operated with the desired parameter settings.
· Use spot checks if necessary to check the parameterisa

tion, e.g. with the configuration program or with the hand
held.

2. Commissioning

Diagnosis and error treatment
Chapter 3

3. Diagnosis and error treatment
Contents
3. Diagnosis and error treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−1
3.1 Overview of diagnostic options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−3

3.2 Diagnosis via LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−4
3.2.1 CPX−specific LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−6
3.3 Diagnosis via status bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−12
3.4 Diagnosis via I/O diagnostic interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−13
3.5 Diagnosis via DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−14
3.5.1 Diagnosis via software configurator with standard EDS . . . . . . . . . 3−14
3.5.2 Diagnosis via software configurator with modular EDS . . . . . . . . . 3−18
3.5.3 Diagnosis via the user program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−20
3.6 Fault treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−23

3.1 Overview of diagnostic options
The CPX terminal offers extensive and user−friendly possibi

lities of diagnosis and fault treatment. The following possibi
lities are available, depending on the configuration:
Diagnostic Brief description Advantages Detailed

possibility description
LED display The LEDs directly show con Fast on−the−spot" Section 3.2
figuration faults, hardware recognition of faults
faults, bus faults, etc.
Status bits Internal inputs which supply Fast access to fault Section 3.3 and
coded common diagnostic messages, irrespective of CPX system manual
messages. the module and master.
I/O diagnostic The I/O diagnostic interface Detailed fault recognition Section 3.4 and
interface is a bus−independent diag irrespective of the field bus CPX system manual
nostic interface at I/O level type used.
which permits access to in
ternal data of the CPX ter
minal (16inputs and 16 out
puts).
Diagnosis via Access to all system data of Detailed module−related and Appendix B.1
DeviceNet the CPX terminal via the field channel−related fault rec EDS file
bus. ognition as well as access to
the diagnostic memory in the
online mode of the program
ming/configuration software
and in the PLC user program.
Diagnosis via Diagnostic information can Fast on−the−spot" Manual for the
the handheld be shown on the CPX hand recognition of faults handheld
held in a user−friendly
manner by means of menus.
Tab.3/1: Diagnostic possibilities
Please note
Note that the diagnostic information displayed depends on
the parameterisation of the CPX terminal.

3.2 Diagnosis via LEDs
LEDs for diagnosing the CPX terminal are available on the

field bus node as well as on the individual modules.
You will find the meaning of the LEDs for the I/O modules,
pneumatic interfaces or pneumatics in the corresponding
manuals.
LEDs on field bus node CPX−FB11

The LEDs on the cover indicate the operating status of the
CPX field bus node.
1 CPX−specific LEDs
PS: power system MS PS
NS PL 1
PL: power load
IO SF
SF: system fault M
M: modify
2 DeviceNet−specific MS PS
LEDs
NS PL 2
MS: module status IO SF
M
NS: network status
IO: I/O status
Fig.3/1: LEDs on the CPX field bus node CPX−FB11

The LEDs are represented in their various states as follows:
lights up blinks dark
Normal operating status

In normal operating status the following LEDs light up green:
The SF LED does not light up. The M LED lights up only with
the setting System start with saved parameterisation and
saved CPX equipment" (see function number 4402).
LED display Operating

status
The following LEDs Standard

light up green:
PS
MS PS PL
MS
NS PL NS
IO 1)
IO SF The SF LED does not
light up.
M SF
M LED see function
number 4402
1) Lights up only when inputs/outputs are controlled via DeviceNet.
Tab.3/2: Normal operating status

3.2.1 CPX−specific LEDs
PS (power system) power sensor/logic supply

LED (green) Sequence Status Meaning/fault treatment
ON
No fault. Operating volt
OFF
age/sensor supply applied
LED lights up
ON Operating voltage/sensor Eliminate undervoltage

OFF supply outside the toler
ance range
LED flashes
ON Internal fuse for the 1. Eliminate short circuit/overload on
OFF
operating voltage/sensor module side.
supply has responded. 2. Depending on the parameterisation
of the module (module parameter):
· The sensor supply voltage will be
switched on again automatically
when the short circuit has been
eliminated (default)
· Power Off/On is necessary
ON The operating voltage/ Check the operating voltage connec

OFF
sensor supply is not tion of the electronics
LED is out applied
PL (Power Load) power load supply (outputs/valves)

LED (green) Sequence Status Meaning/fault treatment
ON
No fault. Load voltage None
OFF
applied
LED lights up
ON Load voltage at the system Eliminate undervoltage
OFF
supply or additional supply
outside the tolerance
LED flashes range

SF (system failure) system fault

LED (red) Sequence 1) Status Meaning/fault treatment
ON No fault.
OFF
LED is out
ON
Simple fault/information See description of fault numbers in
OFF
(fault class 1) the CPX system manual
LED flashes
ON Fault
OFF (fault class 2)
LED flashes
ON Serious fault
OFF
(fault class 3)
LED flashes
1) The system fault LED flashes depending on the class of fault which has occurred.
Fault class 1 (simple fault): flash once, pause
Fault class 2 (fault): flash twice, pause
Fault class 3 (serious fault): flash three times, pause

M (modify) parameterisation modified or Force active

LED (yellow) Sequence Status Meaning/fault treatment
ON System start with default None

OFF
parameterisation (factory
LED is out setting) and current CPX
equipment status is set;
external parameterisation
is possible (pre−setting).
ON
System start with saved Be careful when replacing CPX valve
OFF
parameterisation and terminals with saved parameterisation.
LED lights up saved CPX equipment With these CPX valve terminals, para
status is set; meterisation is not carried out auto
parameters and CPX equip matically by the higher−order PLC/IPC
ment status are saved when the terminal is replaced. In
remanently; external para these cases check before replacing to
meterisation is blocked 1) see which settings are required and, if
necessary, carry out these settings.
ON Force is active 1) The Force function is enabled
OFF
(see system parameter Force mode",
function no. 4402).
LED flashes
1) The display of the Force function (LED flashes) has precedence over the display of the setting for
System start (LED lights up).

DeviceNet−specific LEDs
MS (module status) module status

LED Sequence Status Meaning/fault treatment
ON Logic supply for bus inter · Check logic supply

OFF
face not applied
is out
ON
Operating status normal None
OFF
lights up
green
ON The CPX terminal must be Carry out the configuration, complete

OFF commissioned because it or correct it
is not yet configured, is not
flashes green complete or is not correct.
ON Fault can be rectified Complete or correct the configuration
OFF
flashes red
ON Fault cannot be rectified Check equipment on CPX as well as

OFF other LEDs and, if necessary, request
service
lights up red
ON CPX terminal is in self−test None
OFF
flashes
red−green

NS (network status) network status

ON The CPX terminal is not

OFF
online
Dup_MAC_ID test *) · Wait for the end of the test. If the
is out is not yet concluded LED remains out: Station number
possibly assigned twice; correct
station numbers
Logic supply for bus · See module status LED
interface not applied
ON CPX terminal is online, the · Check the configuration; perhaps

OFF Dup_MAC_ID test is the CPX terminal is not assigned to
concluded, but the CPX a scanner/master.
flashes green terminal does not have a or
configured connection to a · Check the status of the master; it
scanner. is possible that the master is not in
the RUN mode.
ON
The CPX terminal is online None (normal operating status)
OFF
and has a connection to
lights up the field bus.
green
ON One or several I/O con Check the physical connection to the
OFF nections" are in the scanner (bus cable).
time−out status
flashes red
ON Communication has failed.

OFF Non−permitted station · Correct station address
address set
Bus off · Check set baud rate, check bus
lights up red cable, Power OFF/ON
ON The CPX terminal has a net LED self−test or device can no longer
OFF work access fault and is in communicate; check scanner; evalu
the status Communication ate fault message from scanner.
Flashes failed".
red/green
*) Test algorithm which ensures that station numbers on the network are not assigned twice.
The test is usually carried out automatically when the network connection is set up.

I/O (I/O status) I/O status

ON Logic supply for bus inter I/O control via DeviceNet, device is
OFF
face not applied not allocated by a scanner
is out
ON
One or more inputs/out None
OFF
puts is/are controlled via
lights up DeviceNet.
None of the inputs/outputs
has a fault.
ON One or more outputs is/are I/O control via DeviceNet, but device
OFF in the idle state and none is allocated by the scanner and the
of the outputs is active or scanner is in idle mode, e.g. program
flashes green faulty. ming mode.
ON One or more inputs/out Check the inputs/outputs and the
OFF puts is/are faulty, perhaps communication connection to the
in fault status. scanner.
flashes red
ON One or several outputs are Check the other LEDs, if necessary

OFF forcibly switched off (per request servicing
haps a fault which cannot
be corrected); one or more
lights up red inputs have a fault which
cannot be corrected.

3.3 Diagnosis via status bits
Status bits are internal inputs (1 input byte) which serve to

display common diagnostic messages (global fault mess
ages). The status bits are transmitted via the communication
type Strobed I/O".
Please note
If status bits are to be transmitted via a Polled" or
Change of State" connection, you must set the DIL
switches on the field bus node accordingly (see Tab.1/3).
If all status bits supply a 0−signal, no fault will be registered.

The following table shows the diagnostic information when
there is a 1−signal:
Bit Diagnostic information Description

with 1−signal
0 Fault at valve Module type on which a

fault has occurred
occurred.
1 Fault at output
2 Fault at input
3 Fault on analogue module/

function module
4 Undervoltage Type of fault
5 Short circuit/overload
6 Cable fracture
7 Other faults
Tab.3/3: Overview of status bits
If various faults occur simultaneously on various types of

modules, these faults cannot be assigned via the status bits.
Faults can be clearly defined via the I/O diagnostic interface
of by diagnosis via DeviceNet access.

Further instructions on the function and content of the status

bits can be found in the CPX system manual.
3.4 Diagnosis via I/O diagnostic interface
Detailed diagnostic information can be accessed via the I/O

diagnostic interface. You can ascertain exactly, e.g. on which
module and on which channel a fault has occurred. The sys
tem diagnosis can be called up by 16 input bits and 16 out
put bits, via which all diagnostic data can be read out.
For the field bus node CPX−FB11, access to the DeviceNet

objects with Explicit Message programming is always more
suitable than via the I/O diagnostic interface (see appendix
B.1).
Information on the available diagnostic information and its

function numbers can be found in the CPX system manual.
Please note
In order to use the I/O diagnostic interface, you must
activate it with the DIL switch on the field bus node.
If the I/O diagnostic interface is active, it will occupy the first

16 inputs and outputs in the address range.
Instructions on diagnosis with the I/O diagnostic interface

can be found in the CPX system manual.

Overview of diagnostic data
Diagnostic data Contents / description
Global diagnostic data General overview of faults
Diagnostic data module Detail diagnosis per module
Status of diagnostic Number of entries in the diagnostic

memory memory
Operating mode
Diagnostic memory data Long−term memory

Detail diagnosis + relative time
stamp per fault event
Tab.3/4: Diagnostic data
3.5 Diagnosis via DeviceNet
The CPX system permits diagnosis via DeviceNet.

The following diagnostic possibilities are supported here:
diagnosis via the configuration program

(e.g. RSNetworx, see section 3.5.3)
diagnosis via DeviceNet Scanner
diagnosis via the user program (see section 3.5.3).
3.5.1 Diagnosis via software configurator with standard EDS
1. Make sure that the field bus node is online on the

DeviceNet.
2. Double click on the symbol of the CPX terminal in the

software configurator (e.g. RSNetWorx).
3. Click on the Parameters" register.

With the Groups" check box, you can display parameters

and data grouped in folders.
Group Description
SysDiag. Data System diagnostic data
Dat/ParDig.Mod... Module diagnostic data of the relevant

modules
Dat/ParAna.Mod...
Dat/Par PI Mod
Dat/Par Fct.Mod
Dat/Par MPA...
DiagMemData Diagnostic memory data
DiagMem.Entr. Entries in the diagnostic memory
Tab.3/5: Groups with diagnostic data
Detailed information on parameters and data can be found in

appendix A.3 and in the CPX system manual.
The following diagram shows as an example the system

diagnostic data in the group SysDiag.Data.

1 Group
SysDiag.Data
Fig.3/2: Display system diagnostic data
The diagnostic status specifies whether there is diagnostic

information. Fault location/Module position" specifies the
position of the faulty module in the CPX system (irrespective
of the module type). The equipment fitted on the CPX ter
minal must be known before the relevant module diagnostic
data can be ascertained (see following example).

Example
In Fig.3/2 a fault is shown at module position 3. If the CPX
terminal were equipped as shown in the following diagram,
there would be a digital output module (4DO) in this position.
The relevant module diagnostic data would therefore be in
the group Dat/ParDig.Mod2.
1 2 3
Module
position: 0 1 2 3 4 5 6 7
ÓÓÓÓ
4DI 8DI 4DO 2AO 8DI 8DO 2AO
ÓÓÓÓ
ÓÓÓÓ
16 O
ÓÓÓÓ
1 First digital module 3 Third digital module
(digital module 0) (digital module 2)
2 Second digital module

(digital module 1)
Fig.3/3: Numbering the modules (example)

3.5.2 Diagnosis via software configurator with modular EDS
1. Make sure that the field bus node is online on the

DeviceNet.
2. Double click on the symbol of the valve island in the

software configurator (e.g. RSNetWorx).
3. Click on the Module Configuration" register.
4. Double−click in the configuration table on the field bus

node (module 0, see also Fig.2/13).
5. In the window now appearing, double click on the

Configuration Settings" tab (Fig.3/4):
1 Diagnosis information (double click for detailed display)

Fig.3/4: Online diagnosis via the software configurator
(modular EDS)

6. For detailed diagnosis information, double−click on the

appropriate line (1 in Fig.3/4).
Fig.3/5: Detailed diagnosis information

3.5.3 Diagnosis via the user program
If the separate communication connection Strobed I/O" is

configured for the CPX system (see Fig.2/8), the diagnostic
information of the status bits is then available for the user
program. The data from the Strobed I/O" connection can be
placed in the input file or in the M1 file of the controller.
Possible sequence of diagnosis Diagnostic data Object which

supplies the
diagnostic data
1. Check to see if there are diagnostic data Diagnostic status Module−independent

system object (114d)
2. Ascertain the number of the module in which Number of the module Module−independent
a fault has occurred. system object (114d)
3. Ascertain relevant module diagnostic data Fault number, channel Parameter Object
type and number of Module (100d or 102d)
the faulty channel
Tab.3/6: Possible sequence of diagnosis
A description of the possible fault numbers can be found in

chapter 5 of the system manual.

Overview of diagnosis data with standard EDS

The following DeviceNet objects offer detailed diagnostic
information:
Object Name Diagnostic data

classes
100d Parameter Object Faulty channel type

Module Number of the faulty channel
Module fault number
114d Module−indepen Number of the module in which a fault has occurred.

dent system object Diagnostic status (specifies whether there are diagnostic data)
System fault number
117d Diagnostic trace Number of entries in the diagnostic memory

status object Trace status
116d Diagnostic trace Long−term memory (max. 40 entries)

object Detail diagnosis + relative time stamp per fault event
Tab.3/7: Diagnosis data standard EDS

Overview of diagnosis data with modular EDS

The following DeviceNet objects offer detailed diagnostic
information:
Object Name Diagnosis data

classes
102d Parameter Object Faulty channel type

Module Number of the faulty channel
Module fault number
114d Module−indepen Number of the module in which a fault has occurred.

dent system object Diagnostic status (specifies whether there are diagnostic data)
System fault number
117d Diagnostic trace Number of entries in the diagnostic memory

status object Trace status
116d Diagnostic trace Long−term memory (max. 40 entries)

object Detail diagnosis + relative time stamp per fault event
Tab.3/8: Diagnosis data modular EDS

3.6 Fault treatment
With the following faults, the reaction of the CPX terminal

depends on the configured reaction of the master module
and on the parameterised Fail safe setting:
telegram failure
the master has stopped
interruption in the bus cable.
Depending on the parameterisation, the outputs (valves and

electric outputs) will be switched off (factory setting) or retain
their status (see CPX system manual).
Warning
· Make sure that valves and outputs are put into a safe
state if the named faults occur.
An incorrect status of the valves and outputs can lead to
dangerous situations.
Please note
Please note the following if the outputs are reset after PLC
stop, field bus interruption or fault:
Single−solenoid valves move to the basic position.
Double−solenoid valves remain in the current position.
Mid−position valves move to the mid−position (depend
ing on valve type: pressurised, exhausted or blocked).


Technical appendix
Appendix A
Festo P.BE−CPX−FB11−EN en 0503b A−1

A. Technical appendix
Contents
A. Technical appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A−1
A.1 Technical specifications of field bus node type CPX−FB11 . . . . . . . . . . . . . . . A−3

A.2 Accessories for field bus connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A−4
A.3 EDS files of the CPX terminal for standard EDS . . . . . . . . . . . . . . . . . . . . . . . A−5
A.4 Structure of the standard EDS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A−6
A.4.1 Numbering the modules in the standard EDS file . . . . . . . . . . . . . . A−8
A.4.2 Channel assignment for Force, Fail safe and Idle parameters . . . . . A−10
A−2 Festo P.BE−CPX−FB11−EN en 0503b

A.1 Technical specifications of field bus node type CPX−FB11
General information
General technical data See CPX system manual P.BE−CPX−SYS−...
Protection class as per EN 60529, CPX−FB11 fitted IP65/IP67

completely, plug connector as per Accessories,
plugged in or fitted with protective cap.
Protection against electric shock By means of PELV power circuit

(Protection against direct and indirect contact as per (Protective Extra−Low Voltage)
IEC/DIN EN 60204−1)
Current consumption of field bus node CPX−FB11

Internal current consumption at 24 V
(internal electronics):
from operating voltage supply for electronics/ Typ. 65 mA
sensors (VEL/SEN)
Electrical isolation
DeviceNet interface Electrically isolated (optocoupler)
Module code (CPX−specific) Remote I/O: 204

Remote Controller: 155
Module identification (handheld) Remote I/O:

FB11−RIO DeviceNet Remote I/O
Remote Controller:
FB11−RC DeviceNet bus node
Field bus
Protocol DeviceNet according to ODVA specification V 2.0
Baud rate 125kBaud, 250kBaud, 500kBaud
Cable type See DeviceNet specification part 1, appendix B and

installation guidelines for your controller
Cable length
(depends on baud rate and cable type) Max. 500 m

A.2 Accessories for field bus connection
This chapter gives you an overview of necessary and useful

accessories for the field bus connection.
Connection Type Part no.
Micro Style connection FBA−2−M12−5POL 525 632
M12 socket for Micro FBSD−GD−9−5POL 18 324

Style connection
M12 plug for Micro FBS−M12−5GS−PG9 175 380

Style connection
Open Style connection FBA−1−SL−5POL 525 634
Terminal strip for Open FBSD−KL−2x5POL 525 635

Style connection
Sub−D sockets 9−pin FBS−SUB−9−BU−2x4POL 197 960

(IP65/IP67)
FBS−SUB−9−BU−2x5POL−B 532 219
Tab.A/1: Accessories for field bus connection
If you wish to use 9−pin Sub−D plugs of other manufacturers,

you must replace the two flat screws on the plug with
threaded sockets (part no. 340 960).

A.3 EDS files of the CPX terminal for standard EDS
This section only describes standard EDS files. If you use

modular EDS, each CPX module has its own EDS file with
corresponding entries.
EDS files which support different combinations of digital and

analogue modules within a CPX terminal are available for CPX
terminals.
If you are using CPX terminals, each with different combina

tions of digital and analogue modules on a DeviceNet, you
will require an EDS file which supports all the combinations
used.
The greater the number of possible module combinations

that an EDS file supports, the greater is the number of para
meters contained in an EDS file.
Please note
Please note that the greater the number of parameters
contained in an EDS file, the longer is the time required for
transmission of the parameters.
This section describes the following standard EDS files.
File name 1) Supports the following module combinations Number of

(Standard EDS) parameters
DNIO1CPX−EN.EDS Exclusively digital modules Approx. 730

DNIO1CPX−DE.EDS
DNIO2CPX−EN.EDS Combinations consist of up to: Approx. 1027

DNIO2CPX−DE.EDS 9 digital modules, 9 analogue modules 2)
1) In the file names DE stands for German, EN for English.
2) This EDS file supports all possible module combinations.
Tab.A/2: EDS files for the CPX terminal (standard EDS)

A.4 Structure of the standard EDS files
In order to simplify access to parameters and data of the CPX

terminal, the parameters and data in the EDS file have been
grouped as follows:
Group Description
All parameters All parameters 1)
SysDiag. Data System diagnostic data
SysData System data
SysParameter System parameters
Dat/Par Dig.Mod Data and parameters of the digital I/O modules 2)

Dat/Par Dig.Mod1 Separate counting of the digital modules from left to right
Dat/Par Dig.Mod...
Dat/Par PI Mod Data and parameters of the pneumatic interface
Dat/Par Ana.Mod Data and parameters of the analogue I/O modules 2) 3)

Dat/Par Ana.Mod1 Separate counting of the analogue modules from left to right
Dat/Par Ana.Mod...
Dat/Par Fct.Mod Data and parameters of function module
Dat/Par MPA Data and parameters of the MPA electronics module

Dat/Par MPA1
Dat/Par MPA...
Force Param DO Force parameter digital output modules
Force Param DI Force parameter digital input modules
FailSafe Param DO Fail safe parameter digital output modules
Idle Param DO Idle parameter digital output modules
Force Param AO Force parameter analogue output module 3)
FailSafe Param AO Fail safe parameter analogue output module 3)
Idle Param AO Idle parameter analogue output module 3)
Force Param AI Force parameter analogue input module 3)

Group Description
DiagMem.Param Diagnostic memory parameters
SysPar Systemstart System parameter system start
DiagMemData Diagnostic memory data
DiagMem.Entr. Diagnostic memory data entry 0...39

DiagMem.Entr1
DiagMem.Entr...
DiagMem.Entr39
1) This group shows all the parameters of the CPX terminal.
2) The number of modules listed depends on the EDS file used.
3) These data and parameters are not supported by all EDS files.
Tab.A/3: Parameter groups in the EDS file

The module parameters which are available for the various
modules can be found in the manual for the relevant module
(e.g. manual for CPX pneumatic interfaces and CPX I/O mod
ules (P.BE−CPX−EA−...).

A.4.1 Numbering the modules in the standard EDS file
The data and parameters for the digital and analogue

modules are each grouped together as follows:
Group Group name Description
Digital module Dat/Par Dig.Mod Data and parameters of digital module 0

Dat/Par Dig.Mod1 Data and parameters of digital module 1
Dat/Par Dig.Mod... Data and parameters of digital module ...
Analogue module Dat/Par Ana.Mod Data and parameters of analogue module 0

Dat/Par Ana.Mod1 Data and parameters of analogue module 1
Dat/Par Ana.Mod... Data and parameters of analogue module ...
MPA pneumatics 1) Dat/Par MPA Data and parameters of the MPA pneumatics module 0
Dat/Par MPA1 Data and parameters of the MPA pneumatics module 1
Dat/Par MPA... Data and parameters of the MPA pneumatics module ...
Pneumatic interface 2) Dat/Par PI Mod Data and parameters of the pneumatic interfaces
1) Only relevant for CPX terminals with MPA pneumatics
2) Only relevant for CPX terminals with CPA or Midi/Maxi pneumatics
Tab.A/4: Numbering the modules
The number at the end of the group name specifies the

number of the relevant module type within the CPX terminal.
It is not identical to the module position number (see also
Fig.A/1).
The digital modules and the analogue modules are counted

separately in each case from left to right, beginning with zero.

Module 1 2 3 4 5
position: 0 1 2 3 4 5 6 7
4DI 8DI 2AO 8DI 8DO 2AO
16 O
6 7
1 First digital module (digital module 0) 5 Second MPA electronic module (MPA 1)
2 Second digital module (digital mod. 1) 6 First analogue module (ana. module 0)
3 Third digital module (digital module 2) 7 Second analogue module (analogue
module 1)
4 First MPA electronic module (MPA 0)
Fig.A/1: Numbering the modules (example with MPA pneumatics)
Module 1 2 3 4
position: 0 1 2 3 4 5 6

ÓÓ ÓÓ
ÓÓ
ÓÓ ÓÓ
ÓÓ
ÓÓÓÓ
16 O
5 6
1 First digital module (digital module 0) 4 Pneumatic interface (PI Mod)

2 Second digital module (digital mod. 1) 5 First analogue module (analog mod. 0)
3 Third digital module (digital module 2) 6 Second analogue module (ana. mod. 1)
Fig.A/2: Numbering the modules (example with CPA pneumatics)

A.4.2 Channel assignment for Force, Fail safe and Idle parameters
The Force, Fail safe and Idle parameters for the various
channel types are respectively combined into groups
(standard EDS).
Identifier *) Description
DO Digital outputs/valves
DI Digital inputs
AO Analogue outputs
AI Analogue inputs
*) Channel type identifier in group names
Tab.A/5: Channel type identifier in group names
The following pictures show as an example the assignment of

the digital force outputs.
The digital modules and the analogue modules are counted

separately in each case from left to right.

8O
4 8
8 8
0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
2 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
1 2
1 Number of the output word 2 Bit number

Fig.A/3: Assignment of the digital force outputs (example MPA pneumatics)

ÓÓ ÓÓ
8O ÓÓ
ÓÓ ÓÓ
ÓÓ
4 8 8 ÓÓ ÓÓ
0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
2 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
1 2
1 Number of the output word 2 Bit number

Fig.A/4: Assignment of the digital force outputs (example CPA pneumatics)
The diagram below shows as an example the assignment of

the analogue force outputs.

ÓÓÓÓ
8O ÓÓ
ÓÓÓÓ
ÓÓ
ÓÓÓÓ
1 2
1 Analogue channel 0 + 1 2 Analogue channel 2 + 3

Fig.A/5: Assignment of the analogue force outputs (example)


DeviceNet objects with Standard EDS
Appendix B
Festo P.BE−CPX−FB11−EN en 0503b B−1

B. DeviceNet objects with Standard EDS
Contents
B. DeviceNet objects with Standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−1
B.1 DeviceNet objects with Standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−3

B.1.1 DeviceNet object model CPX terminal . . . . . . . . . . . . . . . . . . . . . . . B−3
B.1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−4
B.1.3 Module−parameter object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−6
B.1.4 Assembly object instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−11
B.1.5 Channel assignment for Force, Fail safe and Idle parameters . . . . . B−14
B.1.6 Object, modification digital outputs . . . . . . . . . . . . . . . . . . . . . . . . . B−15
B.1.7 Object, modification digital inputs . . . . . . . . . . . . . . . . . . . . . . . . . . B−16
B.1.8 Object, modification analogue outputs . . . . . . . . . . . . . . . . . . . . . . B−17
B.1.9 Object, modification analogue inputs . . . . . . . . . . . . . . . . . . . . . . . B−18
B.1.10 Object, modification output words function module . . . . . . . . . . . B−19
B.1.11 Object, modification input words function module . . . . . . . . . . . . . B−20
B.1.12 Module−independent system object . . . . . . . . . . . . . . . . . . . . . . . . . B−21
B.1.13 Status and diagnostic object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−25
B.1.14 Diagnostic trace object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−26
B.1.15 Diagnostic trace status object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−27
B−2 Festo P.BE−CPX−FB11−EN en 0503b

B.1 DeviceNet objects with Standard EDS
This chapter describes the representation of the CPX terminal

within the DeviceNet object model when standard EDS is
used. Some information is in English in order that the original
terms of the DeviceNet specification can be used clearly.
B.1.1 DeviceNet object model CPX terminal
ÓÓ ÓÓ
ÓÓ
ÓÓÓÓ
ÓÓ Modification
Digital output
Modification
Digital input
Status/Diag. Modification Modification

object Analogue output Analogue input
Modification Modification
Function output Function input
16−bit input data
16−bit output
data
8−bit output data
System object
8−bit input data
General
parameters
Object
Message
Assembly Assembly
Router
Assembly Inputs Diagnostic byte outputs
Diagnostic trace
object
I/O Explicit
I/O Connection
Connection Message Diagnostic trace
status object
Fig.B/1: DeviceNet object model of the CPX terminal

B.1.2 Overview
Types of communication for the I/O connection:

Change of State / Cyclic
I/O Polling
I/O Bit Strobe
DeviceNet Class Services

As a slave device of group 2, the CPX terminal supports the
following class services and instance services:
Service Code Service Name
05 (0x05) Reset
14 (0x0E) Get Attribute Single
16 (0x10) Set Attribute Single
75 (0x4B) Allocate Group 2 Identifier Set
76 (0x4C) Release Group 2 Identifier Set

DeviceNet object classes (standard EDS)

The following DeviceNet object classes are supported:
Object Instances Name Type

classes
100d 1 ... 78 Module−parameter object (various)
107d 1 ... 32 Modification of digital outputs, object WORD
109d 1 ... 32 Modification of digital inputs, object WORD
110d 1 ... 32 Modification of analogue outputs, object (various)
111d 1 ... 32 Modification of analogue inputs, object (various)
112d 1 ... 32 Modification of output words function module, object WORD
113d 1 ... 32 Modification of input words function module, object WORD
114d 1 Module−independent system object USINT/BYTE
115d 1 Status and diagnostic object (various)
116d 1 ... 40 Diagnosis of trace object USINT/BYTE
117d 1 Diagnosis of trace status object (various)
An overview of the available data and parameters, their func

tion numbers as well as their assignment to the objects can
be found in the following sections.
The description of the functions of the individual parameters

and data as well as the fundamentals of parameterisation can
be found in the CPX system manual.

B.1.3 Module−parameter object
Object classes: 100

Instances: 1 ... 78
The module parameters of the modules, which exist at the

time, are mapped in this object. An instance of this object is
assigned to each module. A range of instances is therefore
firmly assigned to the various module types.
Module type Instances
Digital modules 1 ... 15 1)
Pneumatic interface 16
Analogue modules 17 ... 31
Function modules 32 ... 46
Pneumatic modules 47 ... 78 2)

1) Instances 11 ... 15 are reserved for extensions
2) Pneumatic interface for Midi/Maxi or CPA: Instance 47
MPA pneumatic modules Instances 47... 54
Instances 55 ... 78 are reserved for extensions
The instance which is assigned to a module also depends on

the position of the module within the CPX terminal. The as
signment of the instances within a range is made from left to
right with ascending instance numbers. For example, in
stance17 is assigned to the first analogue module. Instance
18 is assigned to the second analogue module etc.
The first module of a type therefore receives the lowest in

stance number of the relevant range. The second module
receives the second lowest instance number etc.
Not all the attributes of this object exist as parameters in all

module types. Information on the parameters, and thereby on
the attributes which a module supports, can be found in the

Attr. no. Access Description Type Function no.
100 Get Module code USINT 16 + 16 m + 0

Specifies the module code of the module. (bit 0 ... 7)
Module code Module type
1 Input module CPX−4DE
3 Output module CPX−4DA
4 Multi I/O module CPX−8DE−8DA
7 Input module CPX−8DE−D
66 Pneumatic interface CPX−GP−CPA−...
67 Pneumatic interface CPX−GP−03−4.0
80 MPA electronic mod. VMPA1−FB−EMG−8
82 MPA electronic mod. VMPA1−FB−EMS−8
128 Input module CPX−2AE−U−I
129 Output module CPX−2AA−U−I
130 Input module CPX−4AE−I
132 Input module CPX−4AE−T
153 Bus node CPX−FB13; remote controller
15... Bus node CPX−FB13...; remote controller
202 Bus node CPX−FB13; remote I/O
20... Bus node CPX−FB...; remote I/O
101 Get Revision code USINT 16 + 16 m + 13

Specifies the output status of the module. (bit 0 ... 7)
102 Get Channel type/module fault USINT 2008 + m * 4 + 0

Specifies the type of the faulty channel. (bits 6, 7)
0: Output channel
1: Module fault
2: Input channel
103 Get Number of the faulty channel USINT 2008 + m * 4 + 0

0: Channel 0 (bit 0 ... 5)
...
63: Channel 63
104 Get Module fault number (see System manual USINT 2008 + m * 4 + 1
chapter 5 Possible fault numbers") (bit 0 ... 7)

105 Get Info 2 USINT 2008 + m * 4 + 2

(Reserved) (bit 0 ... 7)
106 Get Info 3 USINT 2008 + m * 4 + 2

107 Get/Set Monitoring the CPX module (module−related BYTE 4828 + m * 64 + 0

parameter 0) (bit 0 ... 7)
Monitoring of the possible faults can be
activated or deactivated (suppressed) for each
module independently.
Bit 0: Monitoring short circuit/overload in
the sensor supply
Bit 1: Monitoring short circuit/overload at
the outputs
Bit 2: Monitoring VOUT/VAL (undervoltage at
outputs/valves)
Bit 3: Monitoring short circuit at the valves
Bit 4: Reserved
Bit 5: Reserved
Bit 6: Reserved
Bit 7: Monitoring parameterisation faults
(internal faults)
1: active (presetting)
0: inactive
108 Get/Set Reaction after short circuit/overload BYTE 4828 + m * 64 + 1

(module−related parameter 1) (bit 0 ... 1)
the sensor supply
the outputs
Bit 3: Behaviour after short circuit/overload
at analogue output
0: VSEN/VOUT remains switched off
109 Get/Set Input debouncing time (value range 0 ... 3) USINT 4828 + m * 64 + 1
0: 0.1 ms (bits 4, 5)
1: 3 ms (typical presetting)
2: 10 ms
3: 20 ms

110 Get/Set Signal extension time (value range 0 ... 3) USINT 4828 + m * 64 + 1
0: 0.5 ms (bits 6, 7)
2: 50 ms
3: 100 ms
111 Reserved
112 Reserved
113 Get/Set Data format analogue value inputs USINT 4828 + m * 64 + 3

(bits 0, 1)
114 Get/Set Data format analogue value outputs USINT 4828 + m * 64 + 3

(bits 4, 5)
115 Reserved
...
118
119 Get/Set 1. Byte parameter of the module SINT

... ... ... ...
150 Get/Set 32. Byte parameter of the module SINT
151 Get/Set 1. Word parameter of the module INT

... ... ... ...
166 Get/Set 16. Word parameter of the module INT
167 Get/Set 1. Double word parameter DINT

... ... ... ...
174 Get/Set 8. Double word parameter DINT

Attributes 119 ... 174 of object 100

Attributes 119 ... 174 are also available for future module
types.
Module−specific data and parameters are stored in attributes

119 ... 174, depending on data type (size) and sequence. A
description of these parameters can be found in the manual
for the relevant module.
The following module−specific parameters are fixed:
Digital input modules

1st parameter (1 byte):
Enabling the individual channels for signal extension;
placing in the 1st. byte parameter of object 100
(attribute 119).
Pneumatic interface
1st parameter (32 bits):
Activate monitoring wire fracture channel−by−channel;
placing in the 1st./2nd./3rd./4th. byte parameter of
object 100 (attributes 119, 120, 121 and 122).

B.1.4 Assembly object instances
Object class: 04
Instances: 100 ... 102
The following instances are saved in the Assembly object

(04h):
Description Instances
OUTPUT (consume data from network) 100
INPUT (produce data to network) 101
SYSTEM STATUS (produce data to network) 102
Within the instance Output in assembly object" all outputs

of the CPX system are transmitted over the network by means
of a communication connection. The following sequence
applies during transmission:
Sequence of transmission
1 I/O diagnostic interface/status byte, if active (16−bit orientated)
2 Object instances of the analogue channels (16−bit orientated)
3 Instances of the function modules (16−bit orientated)
4 Object instances of the digital outputs (8−bit orientated)
Each new data range begins on the LSB (least significant bit)
of a word.

Instance 100 (output) possesses the following member list:
No. Entries in member list Orient. Obj.
0/1 I/O diagnostic interface, 16 bits 104

if active
0 ... 32 Analogue channel data 16 bits 104
0 ... 32 Function module data 16 bits 104
0 ... 64 Digital data 8 bits 103
Transmission by communication types Polled I/O or

COS/Cyclic.
Instance 101: INPUT
Within the instance Input assembly object" all entries in the

CPX system are transmitted cyclically over the network by
means of a communication connection. The following se
quence applies during transmission:
1 I/O diagnostic interface, if active (16−bit orientated)
4 Object instances of the digital inputs (8−bit orientated)
of a word.

Instance 101 (input) possesses the following member list:
0/1 I/O diagnostic interface data, 16 bits 102

if active
0 ... 32 Function module 16 bits 102

COS/Cyclic.
Instance 102: SYSTEM STATUS
Instance 102 (system status) possesses the following

member list:
1 Status byte 8 bits 101

B.1.5 Channel assignment for Force, Fail safe and Idle parameters
The Force, Fail safe and Idle parameters for the various chan
nel types are each grouped together in objects.
Object Description
109 Digital inputs
107 Digital outputs
110 Analogue outputs
111 Analogue inputs
112 Output words function module
113 Input words function module
Tab.B/1: Objects for the Force, Fail safe and Idle

parameters
The assignment of the channels with the Force, Fail safe and
Idle parameters is identical to the assignment of the para
meters of the EDS file.
The first word receives the lowest instance number of the

relevant object. The second word receives the second lowest
instance number etc.
Further instructions on assigning the Force, Fail safe and Idle

parameters can be found in section A.4.2.

B.1.6 Object, modification digital outputs
Object class: 107

Instances: 1 ... 32
The Force, Fail safe and Idle parameters of the digital outputs
are split into words (16 bits) and distributed among the max.
32 instances of this object. There is no module orientation.
The existing digital outputs are assigned in blocks of 16 bits
in ascending order without gaps.
The first output word of the digital outputs is administered in

instance 1. The second in instance 2 etc.
Information on the assignment can be found in section B.1.5

and section A.4.2.
100 Get/Set Force mode parameter for output word n 1) WORD
101 Get/Set Force state parameter for output word n 1) WORD
102 Get/Set Fault mode parameter for output word n 1) WORD
103 Get/Set Fault state parameter for output word n 1) WORD
104 Get/Set Idle mode parameter for output word n 1) WORD
105 Get/Set Idle state parameter for output word n 1) WORD

1) Identical with the assignment of the data block of the digital outputs

B.1.7 Object, modification digital inputs
Object class: 109

Instances: 1 ... 32
The Force, Fail safe and Idle parameters of the digital inputs
are also split into words (16 bits) like those of the digital out
puts and distributed among the max. 32 instances of this
object. There is no module orientation. The existing digital
inputs are assigned in blocks of 16 bits in ascending order
without gaps.
The first input word of the digital inputs is administered in

instance 1. The second in instance 2 etc.

and section A.4.2.
100 Get/Set Force mode parameter for input word n 1) WORD
101 Get/Set Force state parameter for input word n 1) WORD

1) Identical with the assignment of the data block of the digital inputs

B.1.8 Object, modification analogue outputs
Object class: 110

Instances: 1 ... 32
The Force, Fail safe and Idle parameters for the analogue out
puts are administered in this object. The first analogue out
put (channel 0) is administered in instance 1. The second
analogue output (channel 1) in instance 2 etc.
The relevant mode for the analogue output of this instance is

enabled or blocked in attributes 100, 102 and 104. This en
able function is subordinate to the system function which
affects all channels (placed in System object 114, attributes
121, 122 and 123).

and section A.4.2.
100 Get/Set Force mode of the relevant channel USINT
101 Get/Set Force state of the relevant channel 1) INT
102 Get/Set Fault mode of the relevant channel USINT
103 Get/Set Fault state of the relevant channel 1) INT
104 Get/Set Idle mode of the relevant channel USINT
105 Get/Set Idle state of the relevant channel 1) INT

1) Identical with the distribution of the data block of the analogue output data. The value is
congruent with the value of the analogue output channel.

B.1.9 Object, modification analogue inputs
Object class: 111

Instances: 1 ... 32
The Force, Fail safe and Idle parameters for the analogue in
puts are administered in this object. The first analogue input
(channel 0) is administered in instance 1. The second ana
logue input (channel 1) in instance 2 etc.
The force mode for the analogue input of this instance is

enabled or blocked in attribute 100. This enable function is
switched after the system function which affects all channels
(placed in System object 114, attribute 121).

and section A.4.2.
Attr. no. Access Data source Type Function no.
100 Get/Set Force mode of the relevant channel USINT
101 Get/Set Force state of the relevant channel 1) INT

1) Identical with the distribution of the data block of analogue input data. The value is congruent
with the value of the analogue input channel.

B.1.10 Object, modification output words function module
Object class: 112

Instances: 1 ... 32
The Force, Fail safe and Idle parameters of the outputs of the
function modules are split into words (16 bits) and distrib
uted among the max. 32 instances of this object. There is no
module orientation. The existing outputs are assigned in
blocks of 16 bits in ascending order without gaps.
The first output word of the outputs is administered in in

stance 1. The second output word in instance 2 etc.

and section A.4.2.
100 Get/Set Force mode parameter for output word n 1) WORD
101 Get/Set Force state parameter for output word n 1) WORD
102 Get/Set Fault mode parameter for output word n 1) WORD
103 Get/Set Fault state parameter for output word n 1) WORD
104 Get/Set Idle mode parameter for output word n 1) WORD
105 Get/Set Idle state parameter for output word n 1) WORD

1) Identical with the distribution of the data block of the function output data.

B.1.11 Object, modification input words function module
Object class: 113

Instances: 1 ... 32
The Force, Fail safe and Idle parameters of the inputs of the
function modules are split into words (16 bits) and distrib
uted among the max. 32 instances of this object. There is no
module orientation. The existing inputs are assigned in
blocks of 16 bits in ascending order without gaps.
The first output word of the outputs is administered in

instance 1. The second output word in instance 2 etc.

and section A.4.2.
100 Get/Set Force mode parameter for input word n 1) WORD
101 Get/Set Force state parameter for input word n 1) WORD

1) Identical with the distribution of the data block of the function input data.

B.1.12 Module−independent system object
Object class: 114

Instances: 1
100 Get CPX operating mode (bit 0 ... 3) BYTE 0 (bit 0 ... 3)
0: Remote I/O without FEC
1: Remote I/O with FEC
2: Remote controller without bus node
3: Remote controller with bus node
CPX equipment status (bit 4) 0 (bit 4)

Specifies whether the current equipment fitted
to the CPX corresponds to the saved CPX
equipment status.
0: Equal
1: Not equal
Handheld (bit 5) 0 (bit 5)

Specifies whether a handheld is connected or
not.
0: Handheld not connected
1: Handheld connected
Force mode (bit 6) 0 (bit 6)

Specifies whether Force is blocked or enabled.
0: Blocked
1: Enabled
System start (bit 7) 0 (bit 7)

Specifies how the system start of the CPX
terminal is to be carried out
0: System start with default parameterisation
(factory setting) and current CPX equip
ment status
1: System start with saved parameterisation
and saved CPX equipment status

101 Get Fail safe BYTE 1 (bit 0, 1)

Specifies whether Fail safe is active or inactive.
0: Inactive
1: Active
System Idle mode 1 (bit 2, 3)

Specifies whether Idle mode is active or
inactive.
0: Inactive
1: Active
102 Get Monitoring CPX terminal (bit 0 ... 7) BYTE 2 (bit 0 ... 7)
Specifies whether the monitoring of short
circuit/overload and undervoltage is active or
inactive.
the sensor supply
Bit 1: Monitoring short circuit at the outputs
Short circuit/overload at the outputs
Bit 2: Monitoring VOUT
Undervoltage at the outputs
Undervoltage at valves
Bit 4: Monitoring SCV (short circuit at valves)
Bit 5 ... 7: Reserved
0: Inactive
1: Active
103 Reserved
104 Reserved
105 Get Reserved USINT
108 Get Module number USINT 1937 (bit 0 ... 5)

Contains, where applicable, the number of the
first module on which a fault has occurred.
From the module number you can ascertain the
instance no. of object 100 via the relevant
module type. With the aid of this instance num
ber, further diagnostic data can be ascertained
(e.g. the number of the faulty channel).

109 Get Diagnostic status BYTE 1937 (bit 6)

Specifies whether there are diagnostic data
1: There are diagnostic data
0: There are no diagnostic data
110 Get Fault number (bit 0 ... 7) (see System manual USINT 1938 (bit 0 ... 7)
chapter 5 Possible fault numbers")
111 Get Reserved SINT
116 Reserved
117 Reserved
118 Reserved
119 Reserved
120 Get/Set Monitoring (bit 0 ... 7) BYTE 4401 (bit 0 ... 7)

the sensor supply
the outputs
Bit 2: Monitor. VOUT (undervoltage at outputs)
Bit 3: Monitor. VVAL (undervoltage at valves)
Bit 4: Monitor. SCV (short circuit at the valves)
0: inactive
121 Get/Set Force mode USINT 4402 (bit 2, 3)

0: Blocked
1: Enabled
122 Get/Set Fail safe USINT 4402 (bit 0, 1)

0: Reset all outputs (presetting)
1: Hold last State (retain signal status)
2: Assume fault mode

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

2: Assume Idle mode
124 Get/Set System start USINT 4402 (bit 6)

(factory setting) and current CPX equip
ment status; external parameterisation is
possible (presetting)
and saved CPX equipment status; para
meters and CPX equipment status are
saved remanently; external parameterisa
tion is blocked; the M−LED on the field bus
node lights up.
125 Reserved
126 Reserved
127 Reserved
128 Reserved
129 Reserved
130 Reserved
131 Reserved
132 Reserved
133 Get Number of input bytes (Rx size) USINT

Specifies the number of input bytes of the CPX
terminal.
134 Get Number of output bytes (Tx size) USINT

Specifies the number of output bytes of the
CPX terminal.
135 Get/Set Reserved USINT

B.1.13 Status and diagnostic object
Object class: 115

Instances: 1
The 16−bit wide I/O diagnostic interface and the status bits
are mapped here.
100 Get Status bits (8 bit) BYTE 1936

Fault source: Bit 0: valve
Bit 1: output
Bit 2: input
Bit 3: analogue/function module
Fault type: Bit 4: undervoltage

Bit 5: short circuit/overload
Bit 6: wire fracture
Bit 7: other faults
101 Get/Set 16 output bits (order data) of the I/O diagnostic UINT
interface
102 Get 16 input bits (reply data) of the I/O diagnostic UINT
interface

B.1.14 Diagnostic trace object
Object class: 116

Instances: 1 ... 40
An instance is created for each diagnostic entry.
Attr. Access Designation Description Type Function no.

no. 3488 + n
100 Get Marking the first entry after SINT n = 10 * d + 4

Power on (bit 7)
Supplies 1 if it is the first entry
after Power on.
101 Get Days Number of days 2) USINT n = 10 * d + 0
102 Get Hours Number of hours 2) USINT n = 10 * d + 1
103 Get Minutes Number of minutes 2) USINT n = 10 * d + 2
104 Get Seconds Number of seconds 2) USINT n = 10 * d + 3
105 Get Milliseconds Number of 10 msec 2) USINT n = 10 * d + 4

(bit 0 ... 6)
106 Get Module code 3) Module code of the module USINT n = 10 * d + 5

which registered the fault.
107 Get Channel type + Specifies the type of fault or USINT

fault type the faulty channel type.
0: Output channel
1: Module fault
2: Input channel
108 Get Module position Module position of the module USINT n = 10 * d + 6

(module number) which registered the fault; (bits 6, 7)
63 = fault not module−related
109 Get Channel Number of the faulty channel USINT n = 10 * d + 7

number 3) (bits 0 ... 5)
1) d (diagnostic event) = 0 ... 39; most current diagnostic event = 0
2) Measured from the moment the power supply is switched on
3) If the fault number = 0, the contents are also 0. If the fault number lies between 128 ... 199
(fault class 3), the contents are not relevant (servicing required).


no. 3488 + n
110 Get Fault number See System manual chapter 5, USINT n = 10 * d + 8

Possible fault messages"
111 Get Subsequent Number of subsequent USINT n = 10 * d + 9

channels 3) channels with the same fault
B.1.15 Diagnostic trace status object
Object class: 117

Instances: 1
Attr. no. Access Name Type Function no.
100 Get Number of Trace entries in the diagnostic memory USINT 3482
(bit 0 ... 7)
101 Get Status of diagnostic memory BYTE 3483

0: Registering active (bits 0, 1)
1: Registering inactive
102 Get/Set Clear_trace1, access via EDS USINT
103 Get/Set Clear_trace1, access via explicit messaging; USINT

Confirms activity carried out by resetting (0) the
attribute value
104 Get/Set Entries remanent with Power on USINT 3480

1: inactive (bit 0)
105 Get/Set Run/stop filter 1 USINT 3480

0: Stop after 40 entries (save the first 40 entries) (bit 1)
1: Overwrite old entries (save the last 40 entries,
presetting)


0: Run/stop filter 2 inactive (presetting) (bits 0 ... 2)
1: Register up to the defined FN
2: Register up to the defined FN + MN
3: Register up to the defined FN + MN + CN
4: Register as from the defined FN
5: Register as from the defined FN + MN
6: Register as from the defined FN + MN + CN
7: Reserved
107 Get/Set Fault end filter USINT 3484

0: Register running faults (end of fault) (bit 3)
(filter inactive, presetting)
1: Do not register running faults (end of fault)
(filter active)
108 Get/Set Fault number filter USINT 3484

FN = fault number (bits 4, 5)
0: Fault number filter inactive (presetting)
1: Register only defined FN
2: Do not register defined FN
3: Reserved
109 Get/Set Module/channel filter USINT 3484

With this diagnostic memory filter, the registering (bits 6, 7)
of faults of other modules or channels can be
suppressed in order that faults in a particular
module or channel can be analysed.
FN = fault number
0: Module/channel filter inactive (presetting)
1: Register only the FN of a module
2: Register only the FN of a channel
3: Reserved
110 Get/Set Module number USINT 3485

Module number for the diagnostic memory filter (bits 0 ... 7)
111 Get/Set Channel number USINT 3486

Channel number for the diagnostic memory filter (bits 0 ... 7)
112 Get/Set Fault number USINT 3487

Fault number for the diagnostic memory filter (bits 0 ... 7)

DeviceNet objects with Modular EDS
Appendix C
Festo P.BE−CPX−FB11−EN en 0503b C−1

C. DeviceNet objects with Modular EDS
Contents
C. DeviceNet objects with Modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−1
C.1 DeviceNet Objects with Modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−3

C.1.1 DeviceNet object model CPX terminal . . . . . . . . . . . . . . . . . . . . . . . C−3
C.1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−4
C.1.3 Assembly object instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−6
C.1.4 Status and diagnostic object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−9
C.1.5 Module−independent system object . . . . . . . . . . . . . . . . . . . . . . . . . C−10
C.1.6 Parameter Object Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−14
C.1.7 General object module parameters . . . . . . . . . . . . . . . . . . . . . . . . . C−19
C.1.8 Channel assignment for Force, Fail safe and Idle parameters . . . . . C−24
C.1.9 Object: Forcing inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−25
C.1.10 Object: Forcing outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−27
C.1.11 Object: Fault mode and Fault state of the outputs . . . . . . . . . . . . . C−28
C.1.12 Object: Idle mode and Idle state of the outputs . . . . . . . . . . . . . . . C−29
C.1.13 Diagnostic trace object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−30
C.1.14 Diagnostic trace status object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−31
C−2 Festo P.BE−CPX−FB11−EN en 0503b

C.1 DeviceNet Objects with Modular EDS
This chapter describes the representation of the CPX terminal

within the DeviceNet object model when modular EDS is
used. Some information is in English in order that the original
terms of the DeviceNet specification can be used clearly.
Software version R16 is necessary to use modular EDS
(seeTab.0/1).
C.1.1 DeviceNet object model CPX terminal
ÓÓ ÓÓ
ÓÓ ÓÓ
ÓÓÓÓ Force Output Fault Output
Object Object
Status/Diag. Force Input Idle Output

object Object Object
16−bit input data Module−

16−bit output data parameter object
8−bit output data
8−bit input data System object

General
parameters
Object
Message
Assembly Assembly
Assembly Router
Diagnostic byte outputs
Inputs
Diagnostic trace
object
I/O Explicit
I/O Connection
Connection Message Diagnostic trace
status object
Fig.C/1: DeviceNet object model of the CPX terminal for modular EDS

C.1.2 Overview
Types of communication for the I/O connection

Change of State / Cyclic
I/O Polling
I/O Bit Strobe
DeviceNet Class Services

As a slave device of group 2, the CPX terminal supports the
following class services and instance services:
Service Code Service Name
05 (0x05) Reset
14 (0x0E) Get Attribute Single
16 (0x10) Set Attribute Single
75 (0x4B) Allocate Group 2 Identifier Set
76 (0x4C) Release Group 2 Identifier Set

DeviceNet object classes (modular EDS)

The following DeviceNet object classes are supported:
Object Instances Name Type

classes
115d 1 Status and diagnostic object (various)
114d 1 Module−independent system object USINT/BYTE
102d 1 ... 32 Parameter Object Module (various)
120d 1 ... 32 General object module parameters (various)
104d 1 ... 32 Force Input, Object (various)
125d 1 ... 32 Force Output, Object (various)
126d 1 ... 32 Fault Output, Object (various)
127d 1 ... 32 Fault Input, Object (various)
116d 1 ... 40 Diagnosis of trace object USINT/BYTE
117d 1 Diagnosis of trace status object (various)
Counting mode Note: Instance = module number

The modules are counted starting at 0 for the field bus
node. The instances are counted starting at 1 for the first
module.
An overview of the available data and parameters, their func

tion numbers as well as their assignment to the objects can
be found in the following sections.
The description of the functions of the individual parameters

and data as well as the fundamentals of parameterisation can
be found in the CPX system manual.

C.1.3 Assembly object instances
Object class: 04
Instances: 101 ... 103
The following instances are saved in the Assembly object

(04h):
Description Instances
OUTPUT (consume data from network) 101
INPUT (produce data to network) 102
SYSTEM STATUS (produce data to network) 103
Within the instance Output in assembly object" all outputs

of the CPX system are transmitted over the network by means
of a communication connection. The following sequence
applies during transmission:
1 I/O diagnostic interface/status byte, if active (16−bit orientated)
4 Object instances of the digital outputs (8−bit orientated)
of a word.

Instance 101 (output) possesses the following member list:
0/1 I/O diagnostic interface, 16 bits 104

if active
0 ... 32 Function module data 16 bits 104

COS/Cyclic.
Instance 102: INPUT
Within the instance Input assembly object" all entries in the

CPX system are transmitted cyclically over the network by
means of a communication connection. The following se
quence applies during transmission:
1 I/O diagnostic interface, if active (16−bit orientated)
4 Object instances of the digital inputs (8−bit orientated)
of a word.

Instance 102 (input) possesses the following member list:
0/1 I/O diagnostic interface data, 16 bits 102

if active
0 ... 32 Function module 16 bits 102

COS/Cyclic.
Instance 103: SYSTEM STATUS
Instance 103 (system status) possesses the following

member list:
1 Status byte 8 bits 101

C.1.4 Status and diagnostic object
Object class: 115

Instances: 1
The 16−bit wide I/O diagnostic interface and the status bits
are mapped here.
100 Get Status bits (8 bit) BYTE 1936

Fault source: Bit 0: valve
Bit 1: output
Bit 2: input
Bit 3: analogue/function module
Fault type: Bit 4: undervoltage

Bit 5: short circuit/overload
Bit 6: wire fracture
Bit 7: other faults
101 Get/Set 16 output bits (order data) of the I/O diagnostic UINT
interface
102 Get 16 input bits (reply data) of the I/O diagnostic UINT
interface

C.1.5 Module−independent system object
Object class: 114

Instances: 1
100 Get CPX operating mode (bit 0 ... 3) BYTE 0 (bit 0 ... 3)
0: Remote I/O without FEC
1: Remote I/O with FEC
2: Remote controller without bus node
3: Remote controller with bus node
CPX equipment status (bit 4) 0 (bit 4)

Specifies whether the current equipment fitted
to the CPX corresponds to the saved CPX equip
ment status.
0: Equal
1: Not equal
Handheld (bit 5) 0 (bit 5)

Specifies whether a handheld is connected or
not.
0: Handheld not connected
1: Handheld connected
Force mode (bit 6) 0 (bit 6)

Specifies whether Force is blocked or enabled.
0: Blocked
1: Enabled
System start (bit 7) 0 (bit 7)

Specifies how the system start of the CPX ter
minal is to be carried out,
(factory setting) and current CPX equipment
status
and saved CPX equipment status

101 Get Fail safe BYTE 1 (bit 0, 1)

Specifies whether Fail safe is active or inactive.
0: Inactive
1: Active
System Idle mode 1 (bit 2, 3)

Specifies whether Idle mode is active or inactive.
0: Inactive
1: Active
102 Get Monitoring CPX terminal (bit 0 ... 7) BYTE 2 (bit 0 ... 7)
Specifies whether the monitoring of short
circuit/overload and undervoltage is active or
inactive.
Bit 0: Monitoring short circuit/overload in the
sensor supply
Bit 1: Monitoring short circuit at the outputs
Short circuit/overload at the outputs
Undervoltage at the outputs
Undervoltage at valves
Bit 4: Monitoring SCV (short circuit at valves)
0: Inactive
1: Active
103 Reserved
104 Reserved
108 Get Module number USINT 1937 (bit 0 ... 5)

Contains, where applicable, the number of the
first module on which a fault has occurred. From
the module number you can ascertain the in
stance no. of object 100 via the relevant module
type. With the aid of this instance number,
further diagnostic data can be ascertained (e.g.
the number of the faulty channel).

109 Get Diagnostic status BYTE 1937 (bit 6)

Specifies whether there are diagnostic data
1: There are diagnostic data
0: There are no diagnostic data
110 Get Fault number (bit 0 ... 7) (see System manual USINT 1938 (bit 0 ... 7)
chapter 5 Possible fault numbers")
116 Reserved
117 Reserved
118 Reserved
119 Reserved
120 Get/Set Monitoring (bit 0 ... 7) BYTE 4401 (bit 0 ... 7)

sensor supply
Bit 1: Monitoring short circuit/overload at the
outputs
Bit 2: Monitor. Vout (undervoltage at outputs)
Bit 3: Monitor. Vval (undervoltage at valves)
Bit 4: Monitor. SCV (short circuit at the valves)
1: Active (presetting)
0: Inactive
121 Get/Set Force mode USINT 4402 (bit 2, 3)

0: Blocked
1: Enabled
122 Get/Set Fail safe USINT 4402 (bit 0, 1)

2: Assume fault mode

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

2: Assume Idle mode
124 Get/Set System start USINT 4402 (bit 6)

(factory setting) and current CPX equipment
status; external parameterisation is possible
(presetting).
and saved CPX equipment status; para
meters and CPX equipment status are saved
remanently; external parameterisation is
blocked; the M−LED on the field bus node
lights up.
125 Reserved
126 Reserved
127 Reserved
128 Reserved
129 Reserved
130 Reserved
131 Reserved
132 Reserved
133 Get Number of input bytes (Rx size) USINT

Specifies the number of input bytes of the CPX
terminal.
134 Get Number of output bytes (Tx size) USINT

Specifies the number of output bytes of the CPX
terminal.

C.1.6 Parameter Object Module
Object class: 102

Instances: 1 ... 32
Note: Instance number = module number
The module parameters of the modules created until the

middle of 2005 are mapped in this object. An instance of this
object is assigned to each module.
Not all the attributes of this object exist as parameters in all

module types. Information on the parameters, and thereby on
the attributes which a module supports, can be found in the
Newer modules from Use the general module−parameter object (see section C.1.7)
mid−2005 onward to parameterise modules with word or double−word para
meters.

100 Get Module code USINT 16 + 16 m + 0

Specifies the module code of the module. (bit 0 ... 7)
Module code Module type
7 Input module CPX−8DE−D
14 Multi I/O module CPX−8DE−8DA
66 Pneumatic interface CPX−GP−CPA−...
67 Pneumatic interface CPX−GP−03−4.0
80 MPA electronic module VMPA1−FB−EMG−8
82 MPA electronic module VMPA1−FB−EMS−8
128 Input module CPX−2AE−U−I
129 Output module CPX−2AA−U−I
130 Input module CPX−4AE−I
132 Input module CPX−4AE−T
15... Bus node CPX−FB13...; remote controller
20... Bus node CPX−FB...; remote I/O
101 Get Revision code USINT 16 + 16 m + 13

Specifies the output status of the module. (bit 0 ... 7)
102 Get Channel type/module fault USINT 2008 + m * 4 + 0

Specifies the type of the faulty channel. (bits 6, 7)
0: Output channel
1: Module fault
2: Input channel
103 Get Number of the faulty channel USINT 2008 + m * 4 + 0

0: Channel 0 (bit 0 ... 5)
...
63: Channel 63
104 Get Module fault number (see System manual USINT 2008 + m * 4 + 1
chapter 5 Possible fault numbers") (bit 0 ... 7)

105 Get Info 2 USINT 2008 + m * 4 + 2

106 Get Info 3 USINT 2008 + m * 4 + 2

107 Get/Set Monitoring the CPX module (module−related BYTE 4828 + m * 64 + 0

parameter 0) (bit 0 ... 7)
Monitoring of the possible faults can be
activated or deactivated (suppressed) for each
module independently.
Bit 0: Monitoring short circuit/overload
in the sensor supply
outputs
Bit 2: Monitoring VOUT/VAL (undervoltage at
outputs/valves)
Bit 3: Monitoring short circuit at the valves
Bit 4: Reserved
Bit 5: Reserved
Bit 6: Reserved
Bit 7: Monitoring parameterisation faults
(internal faults)
0: Inactive
108 Get/Set Reaction after short circuit/overload BYTE 4828 + m * 64 + 1

(module−related parameter 1) (bit 0 ... 1)
sensor supply
outputs
Bit 3: Behaviour after short circuit/overload
at analogue output
1: VSEN/VOUT switched back on
109 Get/Set Input debouncing time (value range 0 ... 3) USINT 4828 + m * 64 + 1
0: 0.1 ms (bits 4, 5)
2: 10 ms
3: 20 ms

110 Get/Set Signal extension time (value range 0 ... 3) USINT 4828 + m * 64 + 1
0: 0.5 ms (bits 6, 7)
2: 50 ms
3: 100 ms
111 Reserved
112 Reserved
113 Get/Set Data format analogue value inputs USINT 4828 + m * 64 + 3

(bits 0, 1)
114 Get/Set Data format analogue value outputs USINT 4828 + m * 64 + 3

(bits 4, 5)
115 Reserved
...
118
119 Get/Set Monitoring wire fracture CPA channel 0...7 SINT 4828 + m * 64 + 6
119 Get/Set Monitoring channel0 for analogue input/output SINT 4828 + m * 64 + 6

module
120 Get/Set Wire fracture monitoring for CPA 8...15 SINT 4828 + m * 64 + 7
120 Get/Set Monitoring channel1 for analogue input/output SINT 4828 + m * 64 + 7

module
121 Get/Set Monitoring wire fracture for CPA 16...23 SINT 4828 + m * 64 + 8
122 Get/Set Monitoring wire fracture for CPA 24...31 SINT 4828 + m * 64 + 9
123 Get/Set Signal range channel 0 with AO, AI USINT 4828 + m * 64 + 8
124 Get/Set Signal range channel 1 with AO, AI USINT 4828 + m * 64 + 8
125 Get/Set Measurem. value smoothing channel 0 with AI USINT 4828 + m * 64 + 9
126 Get/Set Measurem. value smoothing channel 1 with AI USINT 4828 + m * 64 + 9
127 Get/Set Lower limit channel 0 with AI INT 4828 + m * 64 +

10...11
128 Get/Set Lower limit channel 1 with AI INT 4828 + m * 64 +

12...13

129 Get/Set Upper limit channel 0 with AI INT 4828 + m * 64 +

14...15
130 Get/Set Upper limit channel 1 with AI INT 4828 + m * 64 +

16...17
131 Get/Set Lower limit channel 0 with AO INT 4828 + m * 64 +

9...10
132 Get/Set Lower limit channel 1 with AO INT 4828 + m * 64 +

11...12
133 Get/Set Upper limit channel 0 with AO INT 4828 + m * 64 +

13...14
134 Get/Set Upper limit channel 1 with AO INT 4828 + m * 64 +

15...16

C.1.7 General object module parameters
Object classes: 120

Instances: 1 ... 32
Note: Instance number = module number
This object permits general access to the module parameters

of all existing and future CPX modules. For this object, a soft
ware status of at least R16 is required (see Tab.0/1).
Newer modules from Use the general parameter module object to parameterise
mid−2005 onward modules with word or double−word parameters. Examples
for modules with word or double−word parameters are: the
analogue 4−input module CPX−4AE−I, the temperature mod
ule CPX−4AE−T or the CPX−CP interface.
You can access 3 kinds of parameters via the attributes of the

general module parameter object:
byte parameters via the attributes 1...64

word parameters via the attributes 65...127
double−word parameters via the attributes 129...189
Procedure for 1. Take the function no. of the parameter that you would
parameterisation like to set from the manual for the module.
2. Look for this function no. in the last column of Tab.C/1

(byte and word parameters) or Tab.C/2 (double−word
parameters).
3. Read the corresponding attribute no. from the table.
You will find examples for parameterisation after the table.

Attribute no. Parameter Function no.

Byte Word Word
1 For parameters, see the manual for the respective 4828 + m * 64 + 0

65 module
2 4828 + m * 64 + 1
66
3 4828 + m * 64 + 2
67
4 4828 + m * 64 + 3
68
5 4828 + m * 64 + 4
69
6 4828 + m * 64 + 5
70
7 4828 + m * 64 + 6
71
8 4828 + m * 64 + 7
72
9 4828 + m * 64 + 8
73
10 4828 + m * 64 + 9
74
11 4828 + m * 64 + 10
75
12 4828 + m * 64 + 11
76
... 4828 + m * 64 + ...
...
... 4828 + m * 64 + ...
...
... 4828 + m * 64 + ...
...
... 4828 + m * 64 + 59
124
61 4828 + m * 64 + 60
125
62 4828 + m * 64 + 61
126
63 4828 + m * 64 + 62
127
64 4828 + m * 64 + 63
Tab.C/1: General module−parameter object: assignment of attributes for word

parameters to the function numbers

Attribute no. Parameter Function no.

Byte DWord DWord DWord DWord
1 For parameters, see the 4828 + m * 64 + 0

manual for the
2 respective
p module 4828 + m * 64 + 1
129
3 4828 + m * 64 + 2
130
4 4828 + m * 64 + 3
131
5 4828 + m * 64 + 4
132
6 4828 + m * 64 + 5
133
7 4828 + m * 64 + 6
134
8 4828 + m * 64 + 7
135
9 4828 + m * 64 + 8
136
6
10 4828 + m * 64 + 9
...
11 4828 + m * 64 + 10
...
12 4828 + m * 64 + 11
...
... 4828 + m * 64 + ...
...
... 4828 + m * 64 + ...
185
... 4828 + m * 64 + ...
186
6
... 4828 + m * 64 + 59
187
61 4828 + m * 64 + 60
188
62 4828 + m * 64 + 61
189
63 4828 + m * 64 + 62
64 4828 + m * 64 + 63
Tab.C/2: General module−parameter object: assignment of attributes for double−word

parameters to the function numbers

Module no./
Instance no.: (0) 1 2 3 4 5 6
4
8DI AI−I 8DI 8DO
8O 8O
1 2
1 Parameterisation module CPX−8DE: Release signal extension channel 5:

Object class 120, instance 1, attribute 7 (see Tab.C/3)
2 Parameterisation module CPX−4AE−I: Lower limit channel 2:

Fig.C/2: Examples for parameterisation with the general module parameter object
The following tables show how to determine the attributes for

parameterisation. The parameters of the respective modules
are entered into the tables.
Information on the parameters can be found in the manual for

the relevant module.

Attribute no. Parameter (module no. 1 in Fig.C/2) Function no.

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

65
2 Bit 0: Reaction after short circuit/overload 4828 + m * 64 + 1
Bit 4, 5: Switch−on debounce time
66 Bit 6, 7: Signal stretching time
3 4828 + m * 64 + 2
67
4 4828 + m * 64 + 3
68
5 4828 + m * 64 + 4
69
6 4828 + m * 64 + 5
70
7 Signal extension channel x 4828 + m * 64 + 6
71
8 ... 4828 + m * 64 + 7
Tab.C/3: Example: Parameterisation of the signal extension for module no. 1
Attribute no. Parameter (module no. 2 in Fig.C/2) Function no.

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

65
2 Bit 0: Reaction after short circuit/overload 4828 + m * 64 + 1
66
... ... 4828 + m * 64 + ...
...
... ... 4828 + m * 64 + ...
...
15 Lower limit channel 1 4828 + m * 64 + 14
80
81
82
83
... ... ... 4828 + m * 64 + ...
Tab.C/4: Example: Parameterisation of the lower limit (module no. 2, channel 2)

Please note
For parameterisation with the general module parameter
object, a software status of at least R16 is required
(see Tab.0/1).
C.1.8 Channel assignment for Force, Fail safe and Idle parameters
The Force, Fail safe and Idle parameters for the various
channel types are each grouped together in objects.
Object Description
104 Forcing inputs
125 Forcing outputs
126 Fault mode and Fault state of the outputs
127 Idle mode and Idle state of the outputs
Tab.C/5: Objects for the Force, Fail safe and Idle

parameters
The assignment of the channels with the Force, Fail safe and
Idle parameters is identical to the assignment of the para
meters of the EDS file.
The first word receives the lowest instance number of the

relevant object. The second word receives the second lowest
instance number etc.
Further instructions on assigning the Force, Fail safe and Idle

parameters can be found in section A.4.2.

C.1.9 Object: Forcing inputs
Object class: 104

Instances: 1 ... 32
The instance number corresponds to the module number

(see section C.1.2).
100 ... 115 Get/Set Force mode parameter byte 0 ... 15 BYTE
(Digital input modules)
116 ... 131 Get/Set Force state parameter byte 0 ... 15 BYTE
(Digital input modules)
132 ... 147 Get/Set Force mode parameter word 0 ... 15 WORD
(Technology modules, e.g. CP interface)
148 ... 163 Get/Set Force state parameter word 0 ... 15 WORD
164 ... 167 Get/Set Force mode parameter analogue inputs WORD
channel 0 ... 3
168 ... 172 Get/Set Force state parameter analogue inputs WORD
channel 0 ... 3
Tab.C/6: Objects for forcing inputs (grey: example for forcing from Fig.C/3)

Module no./
Instance no.: (0) 1 2 3 4 5 6
4
8DI AI−I 8DI 8DO
8O 8O
1 2
1 Field bus node CPX−FB11

2 Parameterisation: Module CPX−4AE−I, setting force mode for channel 2:
Fig.C/3: Example for forcing

C.1.10 Object: Forcing outputs
Object class: 125

Instances: 1 ... 32

100 ... 115 Get/Set Force mode parameter (byte 0 ... 15 BYTE
(Digital output modules)
116 ... 131 Get/Set Force state parameter byte 0 ... 15 BYTE
132 ... 147 Get/Set Force mode parameter word 0 ... 15 WORD
148 ... 163 Get/Set Force state parameter word 0 ... 15 WORD
164 ... 167 Get/Set Force mode parameter analogue outputs WORD
channel 0 ... 3
168 ... 172 Get/Set Force state parameter analogue outputs WORD
channel 0 ... 3
Tab.C/7: Objects for forcing outputs

C.1.11 Object: Fault mode and Fault state of the outputs
Object class: 126

Instances: 1 ... 32

100 ... 115 Get/Set Fault mode parameter byte 0 ... 15 BYTE
116 ... 131 Get/Set Fault state parameter byte 0 ... 15 BYTE
132 ... 147 Get/Set Fault mode parameter word 0 ... 15 WORD
148 ... 163 Get/Set Fault state parameter word 0 ... 15 WORD
164 ... 167 Get/Set Fault mode parameter analogue outputs WORD
channel 0 ... 3
168 ... 172 Get/Set Fault state parameter analogue outputs WORD
channel 0 ... 3
Tab.C/8: Objects for Fault mode and Fault state of the outputs

C.1.12 Object: Idle mode and Idle state of the outputs
Object class: 127

Instances: 1 ... 32

100 ... 115 Get/Set Idle mode parameter byte 0 ... 15 BYTE
116 ... 131 Get/Set Idle state parameter byte 0 ... 15 BYTE
132 ... 147 Get/Set Idle mode parameter word 0 ... 15 WORD
148 ... 163 Get/Set Idle state parameter word 0 ... 15 WORD
164 ... 167 Get/Set Idle mode parameter analogue outputs WORD
channel 0 ... 3
168 ... 172 Get/Set Idle state parameter analogue outputs WORD
channel 0 ... 3
Tab.C/9: Objects for Idle mode and Idle state of the outputs

C.1.13 Diagnostic trace object
Object class: 116

Instances: 1 ... 40
An instance is created for each diagnostic entry.

no. 3488 + n
100 Get Marking the first entry after SINT n = 10 * d + 4

Power on (bit 7)
Supplies 1 if it is the first
entry after Power on.
101 Get Days Number of days 2) USINT n = 10 * d + 0
102 Get Hours Number of hours 2) USINT n = 10 * d + 1
103 Get Minutes Number of minutes 2) USINT n = 10 * d + 2
104 Get Seconds Number of seconds 2) USINT n = 10 * d + 3
105 Get Milliseconds Number of 10 msec 2) USINT n = 10 * d + 4

(bit 0 ... 6)
106 Get Module code 3) Module code of the module USINT n = 10 * d + 5

which registered the fault.
107 Get Channel type + Specifies the type of fault or USINT

fault type the faulty channel type.
0: Output channel
1: Module fault
2: Input channel
108 Get Module position Module position of the mod USINT n = 10 * d + 6

(module number) ule which registered the fault; (bits 6, 7)
63 = fault not module−related
109 Get Channel number 3) Number of the faulty channel USINT n = 10 * d + 7

(bits 0 ... 5)


no. 3488 + n
110 Get Fault number See System manual chap. 5, USINT n = 10 * d + 8

Possible fault messages"
111 Get Subsequent Number of subsequent USINT n = 10 * d + 9

channels 3) channels with the same fault
C.1.14 Diagnostic trace status object
Object class: 117

Instances: 1
100 Get Number of Trace entries in the diagnostic memory USINT 3482
(bit 0 ... 7)
101 Get Status of diagnostic memory BYTE 3483

0: Registering active (bits 0, 1)
1: Registering inactive
102 Get/Set Clear_trace1, access via EDS USINT
103 Get/Set Clear_trace2, access via explicit messaging; USINT

Confirms activity carried out by resetting (0) the
attribute value
104 Get/Set Entries remanent with Power on USINT 3480

1: Inactive (bit 0)

0: Stop after 40 entries (save the first 40 entries) (bit 1)
1: Overwrite old entries (save the last 40 entries,
presetting)


0: Run/stop filter 2 inactive (presetting) (bits 0 ... 2)
1: Register up to the defined FN
2: Register up to the defined FN + MN
3: Register up to the defined FN + MN + CN
4: Register as from the defined FN
5: Register as from the defined FN + MN
6: Register as from the defined FN + MN + CN
7: Reserved
107 Get/Set Fault end filter USINT 3484

0: Register running faults (end of fault) (bit 3)
(filter inactive, presetting)
1: Do not register running faults (end of fault)
(filter active)
108 Get/Set Fault number filter USINT 3484

FN = fault number (bits 4, 5)
0: Fault number filter inactive (presetting)
1: Register only defined FN
2: Do not register defined FN
3: Reserved
109 Get/Set Module/channel filter USINT 3484

With this diagnostic memory filter, the registering (bits 6, 7)
of faults of other modules or channels can be
suppressed in order that faults in a particular
module or channel can be analysed.
FN = fault number
0: Module/channel filter inactive (presetting)
1: Register only the FN of a module
2: Register only the FN of a channel
3: Reserved
110 Get/Set Module number USINT 3485

Module number for the diagnostic memory filter (bits 0 ... 7)
111 Get/Set Channel number USINT 3486

Channel number for the diagnostic memory filter (bits 0 ... 7)
112 Get/Set Fault number USINT 3487

Fault number for the diagnostic memory filter (bits 0 ... 7)

Index
Appendix D
Festo P.BE−CPX−FB11−EN en 0503b D−1

D. Index
Contents
D. Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D−1
D−2 Festo P.BE−CPX−FB11−EN en 0503b

D. Index
A
Abbreviations, product−specific . . . . . . . . . . . . . . . . . . . . XIV
Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A−4
Additional power supply . . . . . . . . . . . . . . . . . . . . . . . . . 1−29
Address assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−8
Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−3
B
Baud rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−11, 1−17
Branch line lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−17
Bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−18
Bus termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−27
C
Cable
Field bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−16
Connecting
Field bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−16
Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−28
Connection diagram for DeviceNet . . . . . . . . . . . . . . . . . 1−19
CP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−11
D
Designated use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VII
DeviceNet Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−3, C−3
Diagnosis
Via I/O diagnostic interface . . . . . . . . . . . . . . . . . . . . . 3−13
Via LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−4
Via status bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−12

D. Index
Diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−14

Diagnostic mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−10
Diagnostic possibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−3
DIL switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−8
Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−7
Dismantling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−5
E
EDS file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−21
EDS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−21, A−5
EDS mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−9
Electrical connecting and display elements . . . . . . . . . . . 1−4
F
Field bus baud rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−17
Field bus cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−16
Field bus length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−17
Fitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−5
I
I/O diagnostic interface . . . . . . . . . . . . . . . . . . . . . . . . . . 3−13
ICO/BMP file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−21, 2−22
Idle mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−51
Important user instructions . . . . . . . . . . . . . . . . . . . . . . . . . . IX
Inputs
Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−7
L
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−4

D. Index
M
Micro Style connection . . . . . . . . . . . . . . . . . . . . . . . . . . 1−20
Modular EDS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−22
N
Notes on the use of this manual . . . . . . . . . . . . . . . . . . . . . . XI
O
Object model
Modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−3
Standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−3
Open Style connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−21
Operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−9
Outputs
Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−7
P
Parameterisation
Automatically after Power On . . . . . . . . . . . . . . . . . . . 2−52
Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−43
On the DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−24
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−42
Via the PLC user program . . . . . . . . . . . . . . . . . . . . . . 2−54
With RSNetWorx . . . . . . . . . . . . . . . . . . . . . . . . . . 2−45, 2−48
PELV (Protected Extra−Low Voltage) . . . . . . . . . . . . . . . . 1−28
Pictograms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X
Pin allocation
Field bus interface . . . . . . . . . . . . . . . . . . . 1−20, 1−21, 1−23
Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−28
Switching on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−19

D. Index
R
RSNetWorx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−14
Modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−33
Standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−25
S
Screened connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−24
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VIII
Setting
Baud rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−11
Diagnostic mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−10
EDS mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−9
Operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−9
Station number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−12
Software status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XI
Station numbers
Permitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−12
Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−13
Status bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−12
Strain relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−16
Sub−D plug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−23
Switch cover
Removing and fitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−6
System supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−29
T
Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VIII
Technical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . A−3
Text markings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X
V
Valve supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−29

Conditions of use for "Electronic documentation"
I. Protection rights and scope of use 3. Transferring the authorization of tion provided in Internet/Intranet, is
The file of your choice is subject to use limited exclusively to proper duplica
safeguarding provisions. Festo or The user can transfer his authorization tion of the software, whereby Festo
third parties have protection rights for of use in the scope of and with the li guarantees that in each case the rel
this electronic documentation which mitations of the conditions in accord evant portable data storage device or
Festo provides on portable data stor ance with items 1 and 2 completely to software contains the latest status of
age devices (diskettes, CD ROM, car a third party. The third party must be the documentation. In respect of the
tridge discs), as well as in Internet made explicitly aware of these condi electronic documentation in Internet/
and/or Intranet, always referred to in tions of use. Intranet it is not guaranteed that this
the following as electronic documen has the same version status as the
tation". In so far as third parties have last printed edition.
whole or partial right of access to this II. Exporting the electronic docu 2. Furthermore, Festo cannot be held
electronic documentation, Festo has mentation liable for the lack of economic success
the appropriate rights of use. Festo When exporting the electronic docu or for damage or claims by third
permits the user the use under the fol mentation, the licence holder must parties resulting from the use of the
lowing conditions: observe the export regulations of the documentation by the user, with the
exporting country and those of the exception of claims arising from in
1. Scope of use purchasing country. fringement of the protection rights of
a) The user of the electronic documen third parties concerning the use of the
tation is allowed to use this documen electronic documentation.
tation for his own, exclusively com III. Guarantee 3. The limitations of liability as per
pany−internal purposes on any 1. Festo products are being further paragraphs 1 and 2 do not apply if, in
number of machines within his busi developed with regard to hardware cases of intent or wanton negligence
ness premises (location). This right of and software. The hardware status or the lack of warranted quality, liabil
use includes exclusively the right to and, where applicable, the software ity is absolutely necessary. In such a
save the electronic documentation on status of the product can be found on case, the liability of Festo is limited to
the central processors (machines) the type plate of the product. If the the damage recognizable by Festo
used at the location. electronic documentation, in whatever when the concrete circumstances are
b) The electronic documentation may form, is not supplied with the product, made known.
be printed out on a printer at the loca i.e. is not supplied on a data storage
tion of the user as often as desired, device (diskette, CD ROM, cartridge
providing this printout is printed with disc) as a delivery unit with the rel VI. Safety guidelines/documentation
or kept in a safe place together with evant product, Festo does not guaran Guarantee and liability claims in con
these conditions of use and other user tee that the electronic documentation formity with the regulations men
instructions. corresponds to every hardware and tioned above (items III. and IV) can
c) With the exception of the Festo software status of the product. In this only be made if the user has observed
Logo, the user has the right to use pic case, the printed documentation from the safety guidelines of the documen
tures and texts from the electronic do Festo accompanying the product is tation in conjunction with the use of
cumentation for creating his own ma alone decisive for ensuring that the the machine and its safety guidelines.
chine and system documentation. The hardware and software status of the The user himself is responsible for en
use of the Festo logo requires written product matches that of the electronic suring that the electronic documenta
consent from Festo. The user himself documentation. tion, which is not supplied with the
is responsible for ensuring that the 2. The information contained in this product, matches the product actually
pictures and texts used match the ma electronic documentation can be used by the user.
chine/system or the relevant product. amended by Festo without prior notice
d) Further uses are permitted within and does not commit Festo in any way.
the following framework:
Copying exclusively for use within the
framework of machine and system do IV. Liability/limitations of liability
cumentation from electronic docu 1. Festo provides this electronic docu
ments of all documented supplier mentation in order to assist the user in
components. creating his machine and system do
Demonstrating to third parties exclus cumentation. In the case of electronic
ively under guarantee that no data documentation which in the form of
material is stored wholly or partly in portable data storage devices (disk
other networks or other data storage ettes, CD ROM, cartridge discs) does
devices or can be reproduced there. not accompany a product, i.e. which
Passing on printouts to third parties are not supplied together with that
not covered by the regulation in item product, Festo does not guarantee
3, as well as any processing or other that the electronic documentation
use, is not permitted. separately available / supplied
matches the product actually used by
2. Copyright note the user. The latter applies particu
Every "Electronic document" receives larly to extracts of the documents for
a copyright note. This note must be the user’s own documentation.
included in every copy and in every The guarantee and liability for separ
printout. ately available / supplied portable
Example: © 2003, Festo AG & Co. KG, data storage devices, i.e. with the ex
D−73726 Esslingen, Germany ception of the electronic documenta−
0310d

CPX-FB11 Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CPX-FB11 Manual

Uploaded by

Copyright:

Available Formats

CPX terminal

CPX field bus node

Field bus protocol

Order no. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 422

© (Festo AG&Co. KG, D73726 Esslingen, Federal Republic of

The reproduction, distribution and utilization of this document

Festo P.BE−CPX−FB11−EN en 0503b I

DeviceNet® is a registered trademark of Open DeviceNet Vendor

TORX® is a registered trade mark of CAMCAR TEXTRON INC.,

II Festo P.BE−CPX−FB11−EN en 0503b

Designated use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VII

1.1 General instructions on installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−3

Festo P.BE−CPX−FB11−EN en 0503b III

2.1 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−3

3. Diagnosis and error treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−1

3.1 Overview of diagnostic options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−3

IV Festo P.BE−CPX−FB11−EN en 0503b

A. Technical appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A−1

A.1 Technical specifications of field bus node type CPX−FB11 . . . . . . . . . . . . . . . A−3

B. DeviceNet objects with Standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−1

B.1 DeviceNet objects with Standard EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−3

Festo P.BE−CPX−FB11−EN en 0503b V

C. DeviceNet objects with Modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−1

C.1 DeviceNet Objects with Modular EDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C−3

VI Festo P.BE−CPX−FB11−EN en 0503b

The field bus node type CPX−FB11 described in this manual

The CPX terminal may only be used as follows:

 only in industrial applications

 in accordance with designated use

 without any modifications by the user. Only the conver

 in faultless technical condition.

 the maximum values specified for pressures, tempera

Please comply with national and local safety laws and

Festo P.BE−CPX−FB11−EN en 0503b VII

This manual is intended exclusively for technicians trained in

VIII Festo P.BE−CPX−FB11−EN en 0503b

Important user instructions

The following pictogram marks passages in the text which

Electrostatically sensitive components may be damaged if

Festo P.BE−CPX−FB11−EN en 0503b IX

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.

X Festo P.BE−CPX−FB11−EN en 0503b

Notes on the use of this manual

Support of Field bus node CPX−FB11 1) EDS file

CPX−FB11 as from Rev. 2.1

Tab.0/1: Support of features and software status

This manual contains specific information on installation,

General basic information on the method of operation, on

Information on further CPX modules can be found in the

Festo P.BE−CPX−FB11−EN en 0503b XI

Version Title Description

Manual System manual" Overview of structure, components and method

CPX field bus node" Instructions on fitting, installing, commissioning

CPX I/O modules" Notes on connection types and instructions on

Software FST" Programming in Statement List and Ladder

Tab.0/2: Manuals on the CPX terminal  part 1

XII Festo P.BE−CPX−FB11−EN en 0503b

Version Title Description

Manual Valve terminals with MPA Instructions on fitting, installing, commis

Valve terminals with CPA Instructions on fitting, installing, commis

only in industrial applications

in accordance with designated use

without any modifications by the user. Only the conver

in faultless technical condition.

the maximum values specified for pressures, tempera

Hyphens indicate general activities.

Manual System manual" Overview of structure, components and method

CPX field bus node" Instructions on fitting, installing, commissioning

CPX I/O modules" Notes on connection types and instructions on

Software FST" Programming in Statement List and Ladder

Tab.0/2: Manuals on the CPX terminal part 1

Manual Valve terminals with MPA Instructions on fitting, installing, commis

Valve terminals with CPA Instructions on fitting, installing, commis

Tab.0/3: Manuals on the CPX terminal part 2

Micro Style connection type FBA−2−M12−5POL (2xM12)

Open Style connection type FBA−1−SL−5POL with terminal

9−pin sub−D plug

Operating mode and EDS mode (firmware)

Diagnosis mode or number of I/O bytes