CPX terminal - Festo · CPX terminal Manual 541 305 en 0605NH ... B.4.7 Force parameter B−26 ......

Electronics Manual

CPX field bus node

Type CPX−FB32

Field bus protocol EtherNet/IP

CPX terminal

Manual541 305en 0605NH[693 135]

Contents and general instructions

IFesto P.BE−CPX−FB32−EN en 0605NH

Original de. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Edition en 0605NH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Designation P.BE−CPX−FB32−EN. . . . . . . . . . . . . . . . . . . . . . .

Order no. 541 305. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

© (Festo AG�&�Co. KG, D�73726 Esslingen, Federal Republic ofGermany, 2006)Internet: http://www.festo.comE−Mail: [email protected]

The reproduction, distribution and utilization of this documentas well as the communicaton of its contents to others withoutexpress authorization is prohibited. Offenders will be heldliable for the payment of damages. All rights reserved in theevent of the grant of a patent, utility module or design.


II Festo P.BE−CPX−FB32−EN en 0605NH

EtherNet/IP�® is a registered trade name of ControlNet International Ltd.and the Open DeviceNet Vendor Association. Inc. (ODVA)

RSLogix is a registered trade name of Rockwell Automation

SPEEDCON�® is a registered trade name of PHOENIX CONTACT GmbH &Co. KG, 32825 Blomberg, Germany

TORX�® is a registered trade name of CAMCAR TEXTRON INC.,Rockford, Ill., USA


IIIFesto P.BE−CPX−FB32−EN en 0605NH

Contents

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

Target group� VII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Service VII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Notes on the use of this manual VIII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Important user instructions IX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Installation 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

1.2 Settings of the DIL switches on the field bus node 1−6 . . . . . . . . . . . . . . . . . . . .

1.2.1 Removing and fitting the cover over the DIL switches 1−6 . . . . . . . . . . .

1.2.2 Settingthe DIL switches 1−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Connecting the Ethernet field bus 1−12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.1 Ethernet cable 1−12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.2 Field businterface of the CPX−FB32 1−13 . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.3 Setting the IP address 1−14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.4 Extended Ethernet settings 1−16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.5 Use the Webserver functions of the CPX−FB32 1−16 . . . . . . . . . . . . . . . .

1.4 Pin assignment of power supply 1−17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


IV Festo P.BE−CPX−FB32−EN en 0605NH

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−9 . . . . . . . . . . . . . . . . . . . . .

2.1.3 Address assignment after extension/conversion 2−16 . . . . . . . . . . . . . .

2.2 Bus configuration 2−19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.1 Registering slave properties in the configuration program 2−19 . . . . . .

2.2.2 Overview of configuration on the EtherNet/IP 2−22 . . . . . . . . . . . . . . . . .

2.2.3 Configuration with RSLogix 5000 2−23 . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Parametrizing 2−26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Methods of parametrizing 2−28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Parametrizing via Configuration Assembly (method 1) 2−29 . . . . . . . . . .

2.3.3 Parametrizing via software (method 2a) 2−29 . . . . . . . . . . . . . . . . . . . . .

2.3.4 Parametrizing with the Handheld (method 2b) 2−29 . . . . . . . . . . . . . . . .

2.3.5 Parametrizing via the PLC user program (method 3) 2−30 . . . . . . . . . . . .

2.3.6 Parametrizing with EDS files (method 4) 2−31 . . . . . . . . . . . . . . . . . . . . .

2.4 Notes on parameters for Idle mode and Fault mode 2−32 . . . . . . . . . . . . . . . . . . .

2.5 Check list for commissioning the CPX terminal with FB32 2−33 . . . . . . . . . . . . . . .

3. Diagnosis 3−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Overview of diagnostic possibilities 3−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Diagnosis via LEDs 3−4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.1 CPX−specific LEDs 3−6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Diagnosis via status bits 3−13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4 Diagnosis via I/O diagnostic interface 3−14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Diagnosis via EtherNet/IP 3−15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6 Fault treatment 3−17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


VFesto P.BE−CPX−FB32−EN en 0605NH

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

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

A.2 Accessories A−4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B. Ethernet/IP Objects of the CPX−FB32 B−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1 Overview of Ethernet/IP Objects of the CPX−FB32 B−3 . . . . . . . . . . . . . . . . . . . . .

B.2 Objects for network settings B−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.1 Port Object B−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.2 TCP/IP Interface Object B−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.3 Ethernet Link Object B−9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3 Objects for the I/O connection B−10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3.1 Assembly Object B−10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4 Objects for system data and diagnosis B−15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.1 Identity Object B−15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.2 System Object (for operating mode Remote I/O) B−16 . . . . . . . . . . . . . .

B.4.3 Status and Diagnostic Object B−19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.4 Diagnostic Trace Object B−20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.5 Diagnostic Trace Status Object B−21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.6 General Module Parameter Object B−23 . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.7 Force parameter B−26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.8 Fail safe and Idle parameters B−31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.9 Configuration Array Object B−36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.10 Slave Size Object (for operating mode Remote Controller) B−36 . . . . . .

B.5 Examples B−37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.5.1 Example: Forcing inputs B−37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.5.2 Example: Parametrizing with the general Modul Parameter Object B−39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C. Index C−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


VI Festo P.BE−CPX−FB32−EN en 0605NH


VIIFesto P.BE−CPX−FB32−EN en 0605NH

Designated use

The field bus node type CPX−FB32 described in this manualhas been designed exclusively for use as a slave on theEtherNet/IP.

The CPX terminal may only be used as follows:

� as designated in industrial applications

� without any modifications by the user. Only the conver�sions or modifications described in the documentationsupplied with the product are permitted.

� in faultless technical condition.

The maximum values specified for pressures, temperatures,electrical data, torques etc. must be observed.

If additional commercially−available components such assensors and actuators are connected, the specified limits forpressures, temperatures, electrical data, torques, etc. mustnot be exceeded.

Please comply with national and local safety laws andregulations.

Target group�

This manual is intended exclusively for technicians trained incontrol and automation technology who have experience ininstalling, commissioning, programming and diagnosingslaves on the EtherNet.

Service

Please consult your local Festo repair service if you have anytechnical problems.


VIII Festo P.BE−CPX−FB32−EN en 0605NH

Notes on the use of this manual

Further information on the EtherNet/IP can be found in:

� www.odva.org

Information on master manufacturers can be found in:

� www.rockwellautomation.com

General basic information on the method of operation, onfitting, installing and commissioning CPX terminals can befound in the CPX system manual.


IXFesto P.BE−CPX−FB32−EN en 0605NH

Important user instructions

Danger categories

This manual contains instructions on the possible dangerswhich may occur if the product is not used correctly. Theseinstructions are marked (Warning, Caution, etc.), printed on ashaded background and marked additionally with a picto�gram. A distinction is made between the following dangerwarnings:

WarningThis means that failure to observe this instruction mayresult in serious personal injury or damage to property.

CautionThis means that failure to observe this instruction mayresult in personal injury or damage to property.

Please noteThis means that failure to observe this instruction mayresult in damage to property.

The following pictogram marks passages in the text whichdescribe activities with electrostatically sensitive compo�nents.

Electrostatically sensitive components may be damaged ifthey are not handled correctly.


X Festo P.BE−CPX−FB32−EN en 0605NH

Marking special information

The following pictograms mark passages in the textcontaining special information.

Pictograms

Information:Recommendations, tips and references to other sources ofinformation.

Accessories:Information on necessary or sensible accessories for theFesto product.

Environment:Information on environment−friendly use of Festo products.

Text markings

· The bullet indicates activities which may be carried out inany order.

1. Figures denote activities which must be carried out in thenumerical order specified.

� Hyphens indicate general activities.


XIFesto P.BE−CPX−FB32−EN en 0605NH

Design Title Manual

ElectronicsManual

�System manual"type P.BE−CPX−SYS−...

Overview of structure, components and methodof operation of CPX terminals;installation and commissioning instructions aswell as basic principles of parametrizing

�CPX field bus node"type P.BE−CPX−FB...

Instructions on fitting, installing, commissioningand diagnosing the relevant field bus node

�CPX I/O modules"type P.BE−CPX−EA−...

Notes on connection types and instructions onfitting, installing and commissioning input andoutput modules of type CPX−..., the MPApneumatic modules, as well as MPA, CPA andMidi/Maxi pneumatic interfaces

�CPX analogue I/Omodules"type P.BE−CPX−AX−...

Notes on connection types and instructions onfitting, installing and commissioning CPXanalogue I/O modules

�CPX−CP interface"type P.BE−CPX−CP−...

Instructions on fitting, installing, commissioningand diagnosing CP systems with the CP interfacetype CPX−CP−4−FB

�Handheld"type P.BE−CPX−MMI−1−...

Instructions on commissioning and diagnosingCPX terminals with the Handheldtype�CPX−MMI−1

�CPX−FEC"type P.BE−CPX−FEC−...

Instructions on fitting, installing, commissioningand diagnosing the CPX Front End Controller.

Softwarepackage

�FST" Programming in Statement List and LadderDiagram for the FEC

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


XII Festo P.BE−CPX−FB32−EN en 0605NH

Design Title Manual

PneumaticsManual

�Valve terminals withMPA�pneumatics"type P.BE−MPA−...

Instructions on fitting, installing, commission�ing, maintaining and converting the MPA pneu�matics (type 32)

�Valve terminals withCPA�pneumatics"type P.BE−CPA−...

Instructions on fitting, installing, commission�ing, maintaining and converting the CPA pneu�matics (type 12)

�Valve terminals withMidi/Maxi pneumatics"type P.BE−MIDI/MAXI−03−...

Instructions on fitting, installing, commission�ing, maintaining and converting the Midi/Maxipneumatics (type 03)

�Valve terminal withVTSA/ISO pneumatics"type P.BE−VTSA−44−...

Instructions on fitting, installing, commission�ing, maintaining and converting the VTSA/ISOpneumatics (type 44)

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


XIIIFesto P.BE−CPX−FB32−EN en 0605NH

The following product−specific terms and abbreviations areused in this manual:

Term/abbreviation Meaning

A0h Hexadecimal numbers are marked by a low−set �h"

AI Analogue input

AO Analogue output

CP modules Common term for the various modules which can be incorporated in aCPX�terminal.

CPX terminal Complete system consisting of CPX modules with or without pneumatics.

DI Digital input

DIL switch Dual−in−line switches consist of several switch elements with whichsettings can be made.

DO Digital output

FEC Front End Controller

Field bus node Provides the connection to specific field buses. Transmits control signals tothe connected modules and monitors their ability to function.

Handheld / MMI Handheld programmer for commissioning and service purposes

IB, IW Input byte, input word

I/O modules Common term for the CPX modules which provide digital inputs andoutputs.

I/Os Digital inputs and outputs

OB, OW Output byte, output word

Pneumatic interface The pneumatic interface is the interface between the modular electricalperiphery and the pneumatics.

Tab.�0/3: CPX−specific terms and abbreviations


XIV Festo P.BE−CPX−FB32−EN en 0605NH

Installation

1−1Festo P.BE−CPX−FB32−EN en 0605NH

Chapter 1

1. Installation

1−2 Festo P.BE−CPX−FB32−EN en 0605NH

Contents

1. Installation 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

1.2 Settings of the DIL switches on the field bus node 1−6 . . . . . . . . . . . . . . . . . . . .

1.2.1 Removing and fitting the cover over the DIL switches 1−6 . . . . . . . . . . .

1.2.2 Settingthe DIL switches 1−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Connecting the Ethernet field bus 1−12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.1 Ethernet cable 1−12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.2 Field businterface of the CPX−FB32 1−13 . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.3 Setting the IP address 1−14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.4 Extended Ethernet settings 1−16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.5 Use the Webserver functions of the CPX−FB32 1−16 . . . . . . . . . . . . . . . .

1.4 Pin assignment of power supply 1−17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Installation


1.1 General instructions on installation

WarningBefore carrying out installation and maintenance work,switch off the following:

� the compressed air supply

� the operating voltage supply for the electronics/sensors

� the load voltage supply for the outputs/valves.

You can thereby avoid:

� uncontrolled movements of loose tubing.

� unexpected movements of the connected actuators

� non−defined switching states of the electroniccomponents.

CautionThe CPX field bus node contains electrostatically sensitivecomponents.

· Do not therefore touch any contacts.

· Observe the regulations for handling electrostaticallysensitive components.

You will then prevent the electronics from being damaged.

Please noteUse a protective cap or blanking plug to seal unusedconnections. You will then comply with protection classIP65/IP67.

Information on fitting the CPX terminal can be found in theCPX system manual (P.BE−CPX−SYS−...).

1. Installation


Electrical connecting and display elements

The following connecting and display elements can be foundon field bus node CPX−FB32:

1

23

4

1 Bus status−specific and CPX−specificLEDs

2 Field bus interface: Ethernetconnection (4−pin M12 socket,D−coded)

3 Transparent cover for the DIL switches

4 Service interface for the Handheld(V24)

Fig.�1/1: Connecting and display elements on the CPX field bus node

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 Torxscrewdriver size T10.

2. Pull the field bus node carefully and without tilting awayfrom the contact rails of the manifold base.

1 Field bus nodeCPX−FB32

2 Manifold basewith contact rails

3 Torx T10 screws

3

1

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 surethat the grooves with the power contact terminals on thebottom of the field bus node lie above the contact rails.

2. Push the field bus node carefully and without tilting as faras possible into the manifold base.

3. Tighten the screws at first only by hand. Place the screwsso that the self−cutting threads can be used.

4. Tighten the screws with a Torx screwdriver size T10 withtorque 0.9 ... 1.1 Nm.

1. Installation


1.2 Settings of the DIL switches on the field bus node

In order to set the CPX field bus node you must first removethe cover over the DIL switches.

CautionThe CPX field bus node contains electrostatically sensitivecomponents.

· Do not therefore touch any contacts.

· Observe the regulations for handling electrostaticallysensitive components.

You will then prevent the electronics in the node from beingdamaged.

1.2.1 Removing and fitting the cover over the DIL switches

In order to set the CPX field bus node you must first removethe 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.

Fitting 1. Place the cover carefully on the node.

Please note· Make sure that the seal is seated correctly.

2. Tighten the two fastening screws at first by hand and thenwith torque 0.4 Nm.

1. Installation


1.2.2 Settingthe DIL switches

You can set the following parameters with the DIL switchesunder the cover (see Fig.�1/3):

� Operating mode

� Diagnostic mode or number of I/O bytes

� IP addressing

Procedure

1. Switch off the power supply.

2. Remove the cover over the DIL switches (section 1.2.1).

3. Carry out the setting as described on the following pages.

4. Fit the cover again (section 1.2.1).

1 DIL switch 1: Operating mode

2 DIL switch 2: Diagnostic modeor number of I/Obytes for RemoteController

3 DIL switch 3: IP addressing

1 2

3

Fig.�1/3: DIL switches in the field bus node

1. Installation


Setting the operating mode with DIL switch 1

You can set the operating mode of the field bus node withswitch element 1 of DIL switch 1:

Operating mode Setting DIL switch 1

Operating mode Remote I/OAll functions of the CPX terminal are controlleddirectly by the master. An FEC integrated in theCPX terminal works as a passive function modulewithout controller.

DIL 1.1: OFFDIL 1.2: OFF(factory setting)

Operating mode Remote ControllerAn FEC integrated in the CPX terminal takescontrol of the I/Os. This operating mode is onlyuseful if an FEC is integrated in the CPX terminal.

DIL 1.1: ONDIL 1.2: OFF

Tab.�1/1: Setting the operating mode with DIL switch 1

1. Installation


Setting the diagnostic mode or the data size for Remote

Controller with DIL switch 2

The function of this DIL switch depends on the set operatingmode of the CPX terminal (see also Tab.�1/1): In the operatingmode Remote I/O the diagnostic mode is set; in the operatingmode Remote Controller the number of I/O bytes is set.

Diagnostic mode (operating mode Remote I/O)

SettingDIL switch 2

The I/O diagnostic interface and thestatus bits are switched off(+ 0 I/O bits)

2.1: OFF2.2: OFF(default)

The I/O diagnostic interface is switchedon 1)

(+ 16 I/O bits)

2.1: ON2.2: OFF

The status bits are switched on(+ 16 I−bits (8 used))

2.1: OFF2.2: ON

Reserved for future extensions 2.1: ON2.2: ON

1) The I/O diagnostic interface occupies an additional 16 I/O bits.

Tab.�1/2: Setting the diagnostic mode with DIL switch 2(operating mode Remote I/O)

1. Installation


Number of I/O bytes (operating mode Remote Controller)

SettingDIL switch 2

8 bytes I / 8 bytes O for communication ofthe field bus node with the CPX−FEC

2.1: OFF2.2: OFF(default)

Reserved 2.1: ON2.2: OFF

16 bytes I / 16 bytes I for communicationof the field bus node with the CPX−FEC

2.1: OFF2.2: ON

Reserved 2.1: ON2.2: ON

Tab.�1/3: Setting the number of I/O bytes with DIL switch 2(operating mode Remote Controller)

1. Installation


Setting the IP addressing with DIL switch 3

With DIL switch 3 you can set the type of addressing or theIP�address of the field bus node.

Dynamic addressing viaBOOTP/DHCP or savedaddressing

Fixed addressing viaDIL�switch

12

34

56

78

Setting: All switches OFF (factory setting) 1

23

45

67

8

Setting: Host ID of the IP address

Tab.�1/4: Settings of DIL switch 3 for different types ofaddressing

The factory setting is the dynamic addressing. Note the detailed information on addressing in section 1.3.3.

1. Installation


1.3 Connecting the Ethernet field bus

1.3.1 Ethernet cable

Please noteIf installation has not been carried out correctly and if highbaud rates are used, data transmission errors may occuras a result of signal reflections and attenuations.Causes of the transmission faults may be:

� incorrect screening/shield connection

� branches

� transmission over long distances

� unsuitable cables.

Observe the cable specifications. Refer to your controllermanual for information on the type of cable to be used.

Cable specification Screened flexible Ethernet round cable of category 5Max. outer diameter: 5.4 mmCore diameter: 0.89 ... 1.0 mm AWG24−26User−made: plug screwed on,

type NECU−M−S−D12G4−C2−ET,part no. 543�109

Please noteIf the CPX terminal is fitted onto the moving part of amachine, the field bus cable on the moving part must beprovided with strain relief. Please observe also the relevantregulations in EN�60204 part 1.

The specifications for Ethernet networks as per ANSI/TIA/EIA−568−B.1 apply for the field bus length.

1. Installation


1.3.2 Field businterface of the CPX−FB32

There is a 4−pin M12 socket with D−code on the field bus nodefor connecting the valve terminal to the field bus. The socketis compatible with SPEEDCON® plugs.

M12 socket EtherNet/IP

Pin assignment Explanation Pin equivalent withRJ45 plug

1. TX+2. RX+3. TX�4. RX�Housing: Screening/shield

Transmitted data +Received data +Send data �Receive data �

1326

Tab.�1/5: Pin assignment of the field bus interface of the CPX−FB32 (M12 4−pin)

Connection with field bus plugs from Festo

You can connect the CPX terminal to the field bus with thefield bus plug from Festo (type NECU−M−S−D12G4−C2−ET,part�no. 543�109).

1. Installation


1.3.3 Setting the IP address

There are three possibilities of setting the IP address of theCPX−FB32.

Please noteIf the network settings of the CPX−FB32 are modified, theModify LED �M" will flash yellow:

· Start the CPX−FB32 again in this case with PowerOFF/ON.

Dynamic addressing via BOOTP/DHCP

Factory setting In the factory setting all switch elements of DIL switch 3 areset to OFF and BOOTP/DHCP is activated in the CPX−FB32.The dynamic addressing via BOOTP/DHCP is then set(see�Tab.�1/4).For the dynamic addressing there must be a BOOTP/DHCPserver in the network.

If you wish to change from another type of addressing back todynamic addressing:

1. Set all switch elements of DIL switch 3 to OFF(see�Tab.�1/4).

2. Activate DHCP with the Handheld (CPX−MMI) or with theprogram �BOOTP−DHCP Server" from Rockwell Automa�tion.

Use the network setting saved in the CPX−FB32

The CPX−FB32 offers the possibility of saving the networksettings in a non−volatile memory. DHCP/BOOTP is therebydeactivated.

1. Set all switch elements of DIL switch 3 to OFF(see�Tab.�1/4).

1. Installation


2. Set the network settings with the Handheld (CPX−MMI) orwith the program �BOOTP−DHCP Server" from RockwellAutomation. The saving of the network settings is thenactivated.

Fixed addressing via DIL switch

Tip The fixed setting of the IP address is to be recommended fortest purposes during commissioning or for small networks.

Setting If a (binary coded) number not equal to 0 or 255 is set withthe switch elements of DIL switch 3, the IP address is as�signed fixed. The set number specifies the host ID of theaddress �192.168.1.xxx" (see Fig.�1/4).

Example: set IP address:192.168.1.005

Example: set IP address:192.168.1.038

12

34

56

78

20 + 22 =1 + 4 =5 1

23

45

67

8

21 + 22 + 25 =2 + 4 + 32 =38

Fig.�1/4: Examples of set IP addresses (binary coded) withfixed addressing

The settings of the network mask and the Gateway are setwith fixed addressing as follows and cannot be modified: Network mask: 255.255.255.0Gateway: 0.0.0.0

1. Installation


1.3.4 Extended Ethernet settings

Via the �Ethernet Link Object" (see appendix B.2.3) you canundertake further settings for the Ethernet connection. Confi�gure the Ethernet Link Object via your Ethernet/IP master orscanner. The extended Ethernet settings are described below.

Automatic setting (factory setting)

The field bus baud rate and the Duplex mode are recognizedas standard by the CPX−FB32.

Baud rate

The field bus baud rate can be switched via EtherNet/IP andis set via Attribute no. 6 (Interface Speed) of the Ethernet LinkObject. The following settings are possible:

� 10 MBd

� 100 MBd

Duplex mode

The full Duplex mode can be activated/deactivated.

1.3.5 Use the Webserver functions of the CPX−FB32

A Webserver is incorporated in the CPX−FB32. The Webservercan be used freely. You can copy files onto the Webserver viaFTP. Information on using the FTP can be found in the appen�dix A.1.

Use the �CPX Web Monitor" software (part number 545�413),in order to use all the functions of the Webserver optimallyand user−friendly.With the CPX Web Monitor you can load a visualization pack�age on an HTLM basis into the Webserver of the FB32. User−friendly diagnostic possibilities are then available via theEthernet network.

1. Installation


1.4 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 forPELV circuits as per IEC/DIN EN 60204−1.

· Use only power packs which guarantee reliable electri�cal isolation of the operating voltage as per IEC/DINEN�60204−1.

By the use of PELV power units, protection against electricshock (protection against direct and indirect contact) is guar�anteed in accordance with IEC/DIN EN 60204−1 (electricalequipment of machines, general requirements).

The current consumption of a CPX terminal depends on thenumber and type of integrated modules and components.

Read the information on power supply as well as on theearthing measures to be carried out in the CPX systemmanual.

1. Installation


System supply, additionalsupply and valve supply

The CPX terminal is supplied with operating and load volt�ages via the manifold bases with system supply, additionalsupply and valve supply types CPX−GE−EV−S, CPX−GE−EV−Z orCPX−GE−EV−V.

Plug Pin assignment of manifold base with ...

system supply moduletype CPX−GE−EV−S...

additional supplymodule typeCPX−GE−EV−Z...

valve supply moduletype CPX−GE−EV−V...

2

3

4

1

M18

1: 24 VEL/SEN2: 24 VVAL / 24 VOUT3: 0 VEL/SEN /

0 VVAL / 0 VOUT4: Earth connection

1: not connected2: 24 VOUT3: 0 VOUT4: Earth connection

1: not connected2: 24 VVAL3: 0 VVAL4: Earth connection

D

C

B

A: 24 VEL/SENB: 24 VVAL / 24 VOUTC: Earth connectionD:0 VEL/SEN /

0 VVAL / 0 VOUT (incoming)

A: not connectedB: 24 VOUTC: Earth connectionD:0 VOUT (incoming)

A: not connectedB: 24 VVALC: Earth connectionD:0 VVAL (incoming)

7/8"−4POLA Pin assignment: Note the specifications on the plug.

7/8"−5POL

1

2

3

4

5

1: 0 VVAL / 0 VOUT2: 0 VEL/SEN3: Earth connection

(incoming)4: 24 VEL/SEN5: 24 VVAL / 24 VOUT

1: 0 VOUT2: not connected3: Earth connection

(incoming)4: not connected5: 24 VOUT

�

VEL/SEN: Operating voltage for electronics/sensorsVOUT: Load voltage for outputsVVAL: Load voltage for valves

Tab.�1/6: Pin assignment for system supply, additional supply and valve supply

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−9 . . . . . . . . . . . . . . . . . . . . .

2.1.3 Address assignment after extension/conversion 2−16 . . . . . . . . . . . . . .

2.2 Bus configuration 2−19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.1 Registering slave properties in the configuration program 2−19 . . . . . .

2.2.2 Overview of configuration on the EtherNet/IP 2−22 . . . . . . . . . . . . . . . . .

2.2.3 Configuration with RSLogix 5000 2−23 . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Parametrizing 2−26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Methods of parametrizing 2−28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Parametrizing via Configuration Assembly (method 1) 2−29 . . . . . . . . . .

2.3.3 Parametrizing via software (method 2a) 2−29 . . . . . . . . . . . . . . . . . . . . .

2.3.4 Parametrizing with the Handheld (method 2b) 2−29 . . . . . . . . . . . . . . . .

2.3.5 Parametrizing via the PLC user program (method 3) 2−30 . . . . . . . . . . . .

2.3.6 Parametrizing with EDS files (method 4) 2−31 . . . . . . . . . . . . . . . . . . . . .

2.4 Notes on parameters for Idle mode and Fault mode 2−32 . . . . . . . . . . . . . . . . . . .

2.5 Check list for commissioning the CPX terminal with FB32 2−33 . . . . . . . . . . . . . . .

2. Commissioning


2.1 Addressing

Before configuring, ascertain the exact number of availableinputs/outputs. A CPX terminal consists of a different numberof I/Os, depending on what you have ordered and on the con�figuration of the field bus node. The I/Os will be assignedautomatically within the CPX terminal.

Please note� Maximum 10 electric modules including the field busnode plus a pneumatic interface or MPA pneumaticmodules are permitted on a CPX terminal.

� If you configure the CPX terminal with an EDS file, thefield bus node in the first location must be installed asmodule 0.

� The CPX terminal has an address range of up to 64 bytesof inputs and 64 bytes of outputs.

2. Commissioning


2.1.1 Ascertaining the address range

Address assignment of the modules

Electric modules

The individual modules are displayed with their identifier onthe handheld. In the case of the I/O modules, the identifier isalso shown in the LED viewing window. With the aid of thisidentifier, you can read the type of module and therefore thenumber of inputs and outputs occupied by the module.

Electric modules Type Moduleid tifi 1)

Assigned addressesidentifier 1) Inputs Outputs

Field bus node FB32 CPX−FB32 FB32−... � �

Digital 4−input module CPX−4DE 4 DI 4 I 2) �

Digital 8−input module CPX−8DE 8 DI 8 I �

Digital 8−input module with channeldiagnosis

CPX−8DE−D 8 DI−D 8 I �

Digital 16−input module CPX−16DE 16 DI 16 I �

Digital 8−input module n−switching CPX−8NDE 8 NDI 8 I �

Digital 4−output module CPX−4DA 4 DO � 4 O 2)

Digital 8−output module CPX−8DA 8 DO � 8 O

Digital multi I/O module CPX−8DE−8DA 8 DI / 8 DO 8 I 8 O

1) Module identifier in the handheld2) 8 bits are always assigned

Tab.�2/1: Overview of electric CPX modules (part 1)

2. Commissioning


Electric modules 1) Type Moduleid tifi

Assigned addressesidentifier Inputs Outputs

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 (temperature module)

CPX−4AE−T 4AI−T 32/64 I�2) �

Analogue 2−output module CPX−2AA−U−I 2AO � 32 O

CP interface CPX−CP−4−FB CPI 128 I 3) 128 O 3)

Front End Controller CPX−FEC FEC 64/128 I 4) 64/128 O 4)

1) Further modules in preparation2) Number of inputs which can be switched between 2 and 43) Maximum number (actual assignment depends on the string assignment)4) With the CPX−FB32 can be set via DIL switch (see section 1.2.2)

Tab.�2/2: Overview of electric CPX modules (part 2)

The address assignment within the individual I/O modulescan be found in the manual for the I/O modules. Details onthe CP interface can be found in the manual for the CP inter�face.

2. Commissioning


Pneumatic modules and pneumatic interfaces

The following table shows the number of output addressesoccupied by the pneumatic modules:

Pneumatic modules andpneumatic interfaces 1)

Type Moduleidentifier 2)

Assignedaddresses

Inputs Outputs

Pneumatic interface for MPA valves(type 32)

VMPA−FB−EPL−... � � �

MPA1 pneumatic module (type 32)without electrical isolation

VMPA1−FB−EMS−8 3) MPA1S � 8 O

MPA1 pneumatic module (type 32)with electrical isolation

VMPA1−FB−EMG−8 3) MPA1G � 8 O

MPA2 pneumatic module (type 32)without electrical isolation

VMPA2−FB−EMS−4 3) MPA2S � 4 O 4)

MPA2 pneumatic module (type 32)with electrical isolation

VMPA2−FB−EMG−4 3) MPA2G � 4 O 4)

MPA1 pneumatic module (type 32)without electrical isolationwith diagnostic function D2

VMPA1−FB−EMS−D2−8 3) MPA1S−D � 8 O

MPA1 pneumatic module (type 32)with electrical isolationwith diagnostic function D2

VMPA1−FB−EMG−D2−8 3) MPA1G−D � 8 O

MPA2 pneumatic module (type 32)without electrical isolationwith diagnostic function D2

VMPA2−FB−EMS−D2−4 3) MPA2S−D � 4 O 4)

MPA2 pneumatic module (type 32)with electrical isolationwith diagnostic function D2

VMPA2−FB−EMG−D2−4 3) MPA2G−D � 4 O 4)

1) Further modules in preparation2) Module identifier in the handheld3) Type of electronic module used4) 8 bits are always assigned

Tab.�2/3: Summary of pneumatic modules and pneumatic interfaces (part 1)

2. Commissioning


Pneumatic modules andpneumatic interfaces

Type Moduleidentifier 1)

Assignedaddresses

Inputs Outputs

Pneumatic interface for CPA valves(type 12) with setting: 3)

� 1...8 valve coils� 1...16 valve coils� 1...24 valve coils (22 can be used)

CPX−GP−CPA−10CPX−GP−CPA−14

CPA10/14 �

8 O16 O24 O

Pneumatic interface for Midi/Maxivalves (type 03) with setting:�2)

� 1...8 valve coils� 1...16 valve coils� 1...24 valve coils� 1...32 valve coils (26 can be used)

CPX−GP−03−4.0 TYPE3 �

8 O16 O24 O32 O

Pneumatic interface for VTSApneumatics (ISO, type 44) 2)

� 1...8 valve coils� 1...16 valve coils� 1...24 valve coils� 1...32 valve coils

VABA−10S6−x1 ISO PlugIn ortype�44 3)

�

8 O16 O24 O32 O

1) Module identifier in the Handheld2) Setting with DIL switch in the pneumatic interface (see manual for CPX I/O modules)3) 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 canbe found in the manual for the valve terminal pneumatics.Further information on MPA pneumatic modules can be foundin the manual for the CPX I/O modules (P.BE−CPX−EA−...).

2. Commissioning


Calculating the number of inputs/outputs

Use the following table for calculating the number of inputsand outputs on your CPX terminal.

Input/output modules and system diagnosis Inputs Outputs

1. I/O diagnostic interface, if set + 16 I/O + _____ I + _____ O

2. Number of input modules CPX−4DE + __ x 8 I 1) + _____ I

3. Number of input modules CPX−8DE, −8NDE, 8DE−D + __ x 8 I + _____ I

4. Number of input modules CPX−16DE + __ x 16 I + _____ I

5. Number of output modules CPX−4DA + __ x 8 O 1) + _____ O

6. Number of output modules CPX−8DA + __ x 8 O + _____ O

7. Nnumber of multi−I/O modules CPX−8DE−8DA + __ x 8 I/O + _____ I + _____ O

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

9. Number of analogue input modules CPX−4AE−I + __ x 64 I/ x 32 I + _____ I

10.Number of analogue input modules CPX−4AE−T + __ x 64 I + _____ I

11.Number of analogue output modules CPX−2AA−U−I + __ x 32 O + _____ O

12.Number of inputs and outputs of other modules + __ I/O(e.g. CP interface)

+ _____ I + _____ O

13.Midi/Maxi, CPA or VTSA pneumatic interface:Number of configured valve solenoid coils (+8 O, 16 O, 24 O, 32 O)32 O (Midi/Maxi) or 24 O (CPA) are configured at the factory.

+ _____ O

14.Number of MPA1 or MPA2 pneumatic modules + __ x 8 O 1) + _____ O

15.Total sum of inputs/outputs to be configuredSum of 1 to 14: = � _____ I = � _____ O

1) 8 bits are always assigned (4 remain unused).

Tab.�2/5: Ascertaining the number of inputs and outputs

2. Commissioning


2.1.2 Address assignment of the CPX terminal

Please noteIf necessary, status bits or an I/O diagnostic interface canbe activated by DIL switch (see Tab.�1/2):

� If the 8 status bits are activated, they will occupy thefirst 16 inputs in the address range (8 used).

� If the I/O diagnostic interface is activated, it will occupythe first 16 inputs and outputs in the address range.

If you configure the CPX terminal with an EDS file, the fieldbus node must be installed in the first location asmodule�0.

Basic rules for addressing

� The address assignment of the inputs does not depend onthe address assignment of the outputs.

� Counting is from left to right, addressing in bytes: Modules with less than 8 bits occupy 8 bits addressspace, but do not use all this space.

� The field bus node counts as a module with 0�inputs and0 outputs when the status bits and the I/O diagnosticinterface are deactivated.

� The I/Os of different module types are assignedseparately from each other. The sequence in the following table then applies:

2. Commissioning


Sequence of addressing Description

1. I/O diagnostic interface 1) Can be activated by DIL switch. If the interface is activated, itwill occupy the first 16 inputs and outputs in the address range.

2. Analogue modules Modules with analogue inputs/outputs

3. Technology modules e.g. CP interface, Front End Controller CPX−FEC

4. Digital modules Modules with digital inputs/outputs

1) Depending on the setting, this address range can also be occupied by status bits (see note above and Tab.�1/2).

Tab.�2/6: Sequence of addressing

Configuration examples

Example 1: CPX terminal with MPA1 and MPA2 pneumatics

The following diagram shows as an example a CPX terminalwith MPA pneumatics and the following setting:

� Status bits and I/O diagnostic interface deactivated

Module no.: 0

1 2

8DI 4DO 8DI

8 O

3

8DO

8 O

1 2 3 4 5 6

4 O 4 O

4

1 Field bus node CPX−FB32

2 MPA pneumatic interface

3 MPA1 pneumatic modules (8 DO each)

4 MPA2 pneumatic modules (4 DO each)

Fig.�2/1: Example terminal 1 (with MPA1 and MPA2 pneumatics)

2. Commissioning


The following table shows the address assignment for theCPX terminal in Fig.�2/1:

Module no. Module Input address Output address

0 Field bus node CPX−FB32 � �

1 Digital 8−input module CPX−8DE I0 ... I7 �

2 Digital 4−output module CPX−4DA � O0 ... O7 *)

3 MPA1 pneumatic module (8 DO) � O8 ... O15


5 MPA2 pneumatic module (4 DO) � O24 ... O31 *)

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

*) 8 bits occupied, 4 bits used

Tab.�2/7: Addressing the example terminal 1 (see Fig.�2/1)

If modular EDS is used, the addresses will be assigned inbytes. In the example above, the output addresses thereforechange as from modules 2, 5 and 6.

2. Commissioning


Example 2: CPX terminal with CP interface

The address assignment for this CPX terminal can be foundon the next page in Tab.�2/8. The settings are:

� Status bits and /I/O diagnostic interface deactivated

1 2 3 4 5 6Module no.: 0

8 O 8 O

1

2

3

4

5

6

8DI 4DO 8DI 8DO

1 Field bus node CPX−FB32

2 CPV valve terminal (16 DO) on theCP�interface (string�1)

3 CP input module (16 DI)

4 Sensor

5 Cylinder

6 CP output module (16 DO) on theCP�interface (string 4)

Fig.�2/2: Example terminal 2 (with CP interface)

2. Commissioning



0 Field bus node CPX−FB32 � �


2 Digital 4−output module CPX−4DA � O128 ... O135 *)

3 CP interface CP−I, here: 4 bytes I, 16 bytes O

I0 ... I32 O0 ... O127

4 Digital multi−I/O moduleCPX−8DE−8DA

I40 ... I47 O136 ... O143



*) 8 bits occupied, 4 bits used


2. Commissioning


Example 3: CPX valve terminal with analogue module and VTSA pneumatics

The address assignment for this CPX terminal can be foundon the next page in Tab.�2/9. The settings are:

� Status bits activated and /I/O diagnostic interfacedeactivated

� On the pneumatic interface set with DIL switch to1...8�valve coils (8 DO).

1 2

8DI 8DI 4DO 8DI 2AO

3

8DO

8 O

Module no.: 0 1 2 3 4 5 6

1 Field bus node CPX−FB32 (with DIL 3.2 to ON for status bits)

2 Pneumatic interface (set with DIL switch to 1...8 valve coils)

3 VTSA pneumatics (type 44)

Fig.�2/3: Example terminal 3 (with analogue module and VTSA pneumatics)

2. Commissioning



0 Field bus node CPX−FB32 with status bits I0 ... I15 1) �



3 Digital 4−output module CPX−4DA � O32 ... O39 2)

4 Digital multi−I/O module CPX−8DE−8DA I32 ... I39 O40 ... O47

5 Analogue 2−output module CPX−2AA � O0 ... O31

6 VTSA pneumatic interface set with DILswitch to 1�...8 valve coils

� O48 ... O55

1) 16 bits occupied, 8 bits used2) 8 bits occupied, 4 bits used


2. Commissioning


2.1.3 Address assignment after extension/conversion

A speciality of the CPX terminal is its flexibility. If the demandsplaced on the machine change, the equipment fitted on theCPX terminal can also be modified.

CautionIf the CPX terminal is extended or converted at a laterstage, the input/output addresses may be shifted. Thisapplies in the following cases:

� if additional modules are inserted between existingmodules.

� if existing modules are removed or replaced by othermodules which have more or fewer input/output ad�dresses.

� if manifold sub−bases (CPA) or pneumatic sub−bases(Midi/Maxi) for single−solenoid valves are replaced bymanifold bases for double−solenoid valves or vice versa(see pneumatics manual).

� if additional manifold sub−bases (CPA) or sub−bases(Midi/Maxi) are inserted between existing sub−bases

� if status bits or the I/O diagnostic interface is activated/deactivated.

2. Commissioning


Example terminal3�modified

The next diagram shows with terminal 3 as an example(see�Fig.�2/3) the effects of modifications to the addressassignment.

The following has been changed:

� The status bits have been deactivated.

� In the case of module no. 1 an 8−input module has beenreplaced by a 16−input module.

� The pneumatic interface has been set to 16 O, in order toreserve addresses for an extension to the pneumatics.

1 2

16DI 8DI 4DO 8DI 2AO

3

8DO

16 O

Module no.: 0 1 2 3 4 5 6

1 Modified: Status bits deactivated

2 Modified: 8 DI module replaced by16�DI module

3 Modified: Pneumatic interface (now setwith DIL switch to 1...16 valve coils)

Fig.�2/4: Example terminal 3 after extension/conversion (compare with Fig.�2/3)

2. Commissioning



0 Field bus node CPX−FB32 withdeactivated status bits

Depends on DIL switch settings (see Tab.�1/2)



3 Digital 4−output module CPX−4DA � O32 ... O39 1)

4 Digital multi−I/O module CPX−8DE−8DA I24 ... I31 O40 ... O47

5 Analogue 2−output module CPX−2AA � O0 ... O31

6 VTSA pneumatic interface withDIL�switch set to �1...16 valve coils

� O48 ... O63

heavy type = modified module1) 8 bits occupied, 4 bits used

Tab.�2/10: Addressing the example terminal 3 after extension/conversion (see Fig.�2/4)

2. Commissioning


2.2 Bus configuration

General instructions on commissioning

Configuration of the CPX terminal demands a very accurateprocedure, as different configuration specifications are some�times necessary for each slave on the EtherNet/IP due to themodular structure. Note here the specifications in the sec�tions which follow.

2.2.1 Registering slave properties in the configuration program

When you commission a new EtherNet/IP slave the first time,you must inform your configuration program about certainproperties of the slave.

The properties of the various slaves are usually administeredby the configuration program in a list or library e.g. EDS li�brary (EDS for electronic data sheets).

The following possibilities are available for extending an EDSlibrary:

� Installing EDS files The EDS file serves simply for identify�ing the CPX−FB32 in the network.

� Enter slave properties manually (only by using theparameter settings set at the factory).

Reference soure for EDS files

Reference source Current EDS files, icon files and information on the EDS filescan be found under the following address in Internet:

� www.festo.com/fieldbus

2. Commissioning


Installing EDS files

You will require the following files for the CPX terminal:

File type File name Language Description

EDS cpx_fb32.eds English Provides the communication adapter in theconfiguration program.

ICO cpx_fb32.ico � Icon file for representing the CPX terminal ormode in the configuration program.

Tab.�2/11: Configuration files (EDS) for CPX terminal for EtherNet/IP

Installing EDS files · Install the files with your configuration program.

Iconlfiles Depending on the configuration program used, you canassign icon files (format .ico) to the CPX terminal or the CPXmodules. The CPX terminal or the modules will then berepresented accordingly in the configuration program.

Notes on installing the EDS files and the icon files can befound in the documentation for your configuration program.

2. Commissioning


Enter slave properties manually

When an EDS file is installed, the following information aboutthe EtherNet/IP slave is added to the EDS library. This informa�tion can also be entered manually if the CPX terminal is to beoperated with the parameter settings preset at the factory.

Information Description

Vendor name Festo Corporation

Vendor ID 26D 1AH

Device type 12D CH

Product code (depends on operating mode)� Remote I/O� Remote Controller

13002D 32CAH13003D 32CBH

Major revision / Minor revision 1.2

Input size / Output size Depends on CPXequipment

Product name CPX−FB32

Catalogue number 541302

Extended Ethernet / IP slave properties

Request Packet Interval (RPI) � 10 ms

Connections:� Exclusive Owner� Input only� Listen only

max. 1max. 16max. 16

Tab.�2/12: Slave properties

Please noteIf the slave properties are entered manually, individualparametrizing of the CPX terminal is not possible.

2. Commissioning


When the EDS library has been extended, the CPX terminal isentered in the slave list as a possible EtherNet/IP slave. It cannow be added to a network.

2.2.2 Overview of configuration on the EtherNet/IP

When the slave properties have been configured (e.g. byinstallation of the EDS file), the following steps are requiredfor parametrizing (depending on the configuration program):

1. Install your CPX terminal and set the network addressingaccording to section 1.3.3.

2. Create a connection to an EtherNet/IP slave. In order todo this, use with RSLogix the profile �Generic EthernetDevice".

3. Assign the Instances of the Assembly Object: Instance 101: InputsInstance 100: OutputsInstance 102: Configuration data, if used

(Configuration Assembly)

4. Select the data format SINT.

5. Enter the IP address, if necessary.

2. Commissioning


2.2.3 Configuration with RSLogix 5000

1. Click in RSLogix 5000 in the �I/O Configuration" on theright on the Ethernet/IP bridge and select �New Module":

1

1 Insert CPX−FB32 as new module in Ethernet/IP

Fig.�2/5: Configuration with RSLogix 5000

2. Commissioning


2. Select the �ETHERNET MODULE � Generic EthernetModule" in the window �Select Module Type" and confirmwith OK.

Fig.�2/6: Insert CPX−FB32 as Generic Module

3. Enter the following in the window �Module Properties"(Fig.�2/7):

� the name for the field bus node (as desired)

� the Instances for inputs: 101outputs: 100

� the Instance for Configuration Assembly: 102The standard setting is �0" (Configuration Assemblynot used).Operating mode Remote I/O: If you undertakeparametrizing via the Configuration Assembly: Enterthe sum of the assigned bytes (see section 2.3.1). Operating mode Remote Controller: Leave the stan�dard setting �0".

2. Commissioning


� Data format SINT

� IP address

Confirm the entry.

1 Name (freelyselectable)

2 AssemblyInstances

3 Size of the�ConfigurationAssembly" (seeexplanation in thetext)

4 IP address

5 Data format

1 2

345

Fig.�2/7: Enter values for �Module Properties"

Please noteFor the configuration with RSLogix 5000 at least one inputmust be assigned:

· for the Instances for inputs (��2 in Fig.�2/7) enter atleast�1 or

· if your CPX terminal does not contain any input modules,activate the status bits with the DIL switches(see�Tab.�1/2).

2. Commissioning


2.3 Parametrizing

CautionA different parametrizing will result in a different reaction.Check especially when replacing CPX terminals to seewhich settings are necessary and make sure that these arerestored (e.g. in the start−up phase by the higher−orderPLC/IPC).

The CPX terminal is supplied from the factory with presetparameters.

The system reaction of the CPX terminal can be adapted tothe relevant application. You can set the reaction of the CPXterminal as well as the reaction of individual modules andchannels by parametrizing. A distinction is made between thefollowing parametrizings:

� System parametrizing, e.g.: Switching out fault messages,setting reaction times, etc.

� Module parametrizing (module and channel−specific),e.g.: Monitoring, settings in the event of faults, settingsfor Forcing.

� Parametizing the diagnostic memory.

A detailed description of the individual parameters as well asbasic information on application can be found in the CPX sys�tem manual (P.BE−CPX−SYS−...).The module parameters which are available for the variousmodules 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 parametrizing

With the system parameter �System start" you can influencethe starting reaction. If possible select the setting �Systemstart with default parametrizing and current CPX systemequipment". The desired parametrizing can then be carriedout in the initialisation phase or user−controlled (dependingon the field bus used).

Please noteThe CPX terminal can only be parametrized if the systemparameter �System start" has the setting �System startwith default parametrizing and current CPX systemequipment".

If the M LED lights up permanently after the system start,then �System start with saved parametrizing and saved CPXsystem equipment" is set. In this case, no other parametriz�ing can be carried out.

CautionIn the case of CPX terminals on which the M LED lights uppermanently, the parametrizing will not be restored auto�matically by the higher−order system if the CPX terminal isreplaced during servicing. In these cases, check beforereplacement to see which settings are required and carryout these settings.

2. Commissioning


2.3.1 Methods of parametrizing

The CPX terminal with CPX−FB32 can be parametrized invarious ways. The following table and the following sectionsprovide an overview of the methods.

Methods and description Advantages Disadvantages

1. Parametrizing via configurationdata (Configuration Assembly)

Depending on the control software,parameters can be entered user−friendly via the menus.

� Parameters are loadedautomatically after PowerOn and are thereforeretained if the CPX terminalis replaced.

� Parameters be enteredindividually.

2a. Parametrizing via software2b. Parametrizing with the

HandheldParametrizing is carried out withentries via the menus.

� User−friendly parametrizingvia the menus (clear text).

� Parametrizing is savedlocally in the CPX terminaland is lost if the terminal isreplaced. 1)

3. Parametrizing via the PLC user program

Parameterisation is carried outwithin the user program in the PLC/IPC via �Explicit Message".

� Parametrizing is saved inthe PLC

� Parameters are loadedautomatically after PowerOn and are therefore re�tained if the CPX terminal isreplaced.

� Explicit Message program�ming required

4. Parametrizing with EDS files via the configuration program

The parameters are set via the con�figuration program and transmitteddirectly to the EtherNet/IP slave.

� Fast, simple parametrizingduring commissioning fortesting the parameters

� Not available with allEthernet/IP masters (at present e.g. not inRSLogix or RSNetWorx)

� Parametrizing is savedlocally in the CPX terminaland is lost if the terminal isreplaced. 1)

1) It is possible to copy the current parameter settings with the aid of the Handheld.

Tab.�2/13: Methods of parametrizing

2. Commissioning


2.3.2 Parametrizing via Configuration Assembly (method 1)

With parametrizing via the Configuration Assembly the para�meters must be entered individually in the control program orgenerated via software.

Parametrizing via the Configuration Assembly is availableonly as from revision status later than Rev. 1.10. Further information on creating the Configuration Assemblycan be found under www.festo.com/fieldbus.

2.3.3 Parametrizing via software (method 2a)

With the CPX Maintenance Tool (CPX−MT) you can parametrizethe CPX terminal via Ethernet with a PC.

The CPX−MT is available in Internet under:

� www.festo.com/fieldbus

2.3.4 Parametrizing with the Handheld (method 2b)

The Handheld offers menu−orientated access to parametrizingwithout configuration software.

Information on operating the Handheld can be found in therelevant manual.

Please noteThe last parametrizing received in the CPX terminal isalways valid.

The CPX terminal can only be parametrized if the systemparameter �System start" has the setting �System start withdefault parametrizing and current CPX system equipment".In this case, the standard parameter settings are valid in theCPX terminal after Power On.

2. Commissioning


Please noteIf the system parameter �System start" has the setting�System start with saved parametrizing and saved CPXsystem equipment," modified parameter settings in theCPX terminal will become valid immediately after Power On.

2.3.5 Parametrizing via the PLC user program (method 3)

Program−controlled access to parameters is made via the�Explicit message" programming. The addresses of theEtherNet/IP Object Model required for this can be found inappendix B. Information on programming this data trans�mission can be found in the manual for your controller.

In order to address the CPX terminal with FB32 you willrequire the following Object descriptions:

Detailed Object descriptions can be found in appendix B.1.

Objectclasses

Instances(dec.)

Attrib.(dec.)

Name

4d 100 ... 102 � Assembly Object

102d 1 ... 48 1, 2 Modification digital inputs, Object

103d 1 ... 48 1 ... 6 Modification digital outputs, Object

104d 1 ... 48 1, 2 Modification analogue inputs, Object

105d 1 ... 48 1 ... 6 Modification analogue outputs, Object

106d 1 ... 48 1, 2 Modification input words of technology module, Object

107d 1 ... 48 1 ... 6 Modification output words of technology module, Object

132d 1 1 ... 37 System Object (Global System Object)

133d 1 1 ... 3 Status and Diagnostic Object

134d 1 ... 40 1 ... 12 Diagnostic Trace Object

135d 1 1 ... 13 Diagnostic Trace Status Object

Tab.�2/14: Overview of Object classes for EtherNet/IP (operating mode Remote I/O)

2. Commissioning


Objectclasses

Instances(dec.)

Attrib.(dec.)

Name Type

136d 1 1, 2 Slave Size Object (only Remote Controller)

SINT

Tab.�2/15: Object class for EtherNet/IP in operating mode Remote Controller

2.3.6 Parametrizing with EDS files (method 4)

This method of parametrizing is only possible if your configur�ation program supports parametrizing via EDS (at present notpossible with RSLogix or RSNetWorx). The EDS files of theCPX terminal must be contained in the EDS library. The CPX−EDS version 1.2 simply serves for identifying theCPX−FB32 in the network.

2. Commissioning


2.4 Notes on parameters for Idle mode and Fault mode

Reaction of the outputs in Idle mode or Fault mode

The Idle mode is assumed by the slaves after request by themaster. The Fault mode defines the status the relevant channel is toassume in the event of field bus communication faults. Thefollowing applies in this state:

� Inputs are transferred

� Output channels of the slaves are no longer updated.

In the Idle mode or Fault mode outputs can assume one ofthe following states:

Digital outputs/valves Analogue outputs

Freeze current status Freeze current status

Reset the output Desired analogue value

Set the output

Tab.�2/16: Possible states in the Idle or Fault mode

You can determine the status to be assumed for each outputchannel (output or solenoid coil) separately. The standardsetting is �Reset output channel".

Further information can be found in the CPX system manual.

2. Commissioning


2.5 Check list for commissioning the CPX terminal with FB32

· Please observe the general commissioning instructions inthe CPX system manual.

· Check the DIL switch settings and the network configur�ation before using and replacing CPX terminals.

· Check the configured address range. If necessary, test theI/Os.

· Check the address assignment of the I/Os on the CPXterminal. For this purpose you can, if necessary, force theI/Os (see CPX system manual).

· Make sure that the desired parametrizing of the CPX ter�minal in the start−up phase or after field bus interruptionsis restored by the plug−in module. This is to ensure that ifthe CPX terminal is replaced, the new terminal will also beoperated with the desired parameter settings.

· Use spot checks if necessary to check the parametrizing,e.g. with the configuration program or with the Handheld.

2. Commissioning


Diagnosis


Chapter 3

3. Diagnosis


Contents

3. Diagnosis 3−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Overview of diagnostic possibilities 3−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Diagnosis via LEDs 3−4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.1 CPX−specific LEDs 3−6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Diagnosis via status bits 3−13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4 Diagnosis via I/O diagnostic interface 3−14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Diagnosis via EtherNet/IP 3−15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6 Fault treatment 3−17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3. Diagnosis

3−3Festo P.BE−CPX−FB32−E N en 0605NH

3.1 Overview of diagnostic possibilities

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:

Diagnosticpossibility

Brief description Advantages Detaileddescription

LED display The LEDs show directly con�figuration faults, hardwarefaults, bus faults, etc.

Fast �on−the−spot"recognition of faults

Section 3.2

Status bits Internal inputs which supplycoded common diagnosticmessages.

Fast access to faultmessages, irrespective of themodule and master.

Section 3.3 andCPX systemmanual

I/O diagnosticinterface

The I/O diagnostic interface isa bus−independent diagnosticinterface at I/O level whichpermits access to internaldata of the CPX terminal(16�inputs and 16 outputs).

Detailed fault recognitionirrespective of the field bustype used.

Section 3.4 andCPX systemmanual

Diagnosis viaEtherNet/IP

Access to all system data ofthe CPX terminal via the fieldbus.

Detailed module−related andchannel−related faultrecognition as well as accessto the diagnostic memory inthe online mode of theprogramming/configurationsoftware and in the PLC userprogram.

Appendix B(Ethernet/IPObjects)

Diagnosis viathe Handheld

Diagnostic information can beshown on the CPX Handheldin a user−friendly manner bymeans of menus.

Fast �on−the−spot"recognition of faults

Manual for theHandheld

Tab.�3/1: Diagnostic possibilities

Please noteNote that the diagnostic information displayed depends onthe parameterization of the CPX terminal.

3. Diagnosis

3−4 Festo P.BE−CPX−FB32−E N en 0605NH

3.2 Diagnosis via LEDs

LEDs for diagnosing the CPX terminal are available on thefield bus node as well as on the individual modules.

The meaning of the LEDs on the electric modules can befound in the manual for the relevant module.

LEDs on field bus node CPX−FB32

The LEDs on the cover indicate the operating status of theCPX field bus node.

1 CPX−specific LEDs

PS: Power system

PL: Power load

SF: System fault

M: Modify

2 EtherNet/IPspecific LEDs

MS:Module status

NS: Network status

IO: I/O status

TP: Link/Traffic

PS

PL

SF

MS

NS

IO

M

1

2PS

PL

SF

MS

NS

IO

M

TP

TP

Fig.�3/1: LEDs on the CPX field bus node

3. Diagnosis


The LEDs are represented in their various states as follows:

� lights up; flashes; 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 withthe setting �System start with saved parameterization andCPX extension" (see function number 4402).

LED display Operatingstatus

PS

PL

SF

MS

NS

IO

MTP

The following LEDslight up green:� PS� PL� MS� NS� IO 1)

� TP 2)

The SF LED does notlight up.

� SFM LED see functionnumber 4402

Standard

1) Lights up only when inputs/outputs are controlled via EtherNet/IP.

2) Continuous lighting: Ready for data transmission Flashes: Date transmission runs

Tab.�3/2: Normal operating status

3. Diagnosis


3.2.1 CPX−specific LEDs

PS (power system) � power sensor/logic supply

LED (green) Sequence Status Meaning/fault treatment

LED lights up

ON

OFF

No fault. Operating volt�age/sensor supply applied

�

LED flashes

ON

OFF

Operating voltage/sensorsupply outside the toler�ance range

Eliminate undervoltage

LED flashes

ON

OFF

Internal fuse for the oper�ating voltage/sensor sup�ply has responded.

1. Eliminate short circuit/overload onmodule side.

2. Depends on the parametrization ofthe module (module parameter):· The sensor supply voltage will be

switched on again automaticallywhen the short circuit has beeneliminated (default)

· Power Off/On is necessary

LED is out

ON

OFF

The operating voltage/sen�sor supply is not applied

Check the operating voltageconnection of the electronics

PL (Power Load) � power load supply (outputs/valves)

LED (green) Sequence Status Meaning/fault treatment

LED lights up

ON

OFF

No fault. Load voltageapplied

None

LED flashes

ON

OFF

Load voltage at the systemsupply or additional supplyoutside the tolerancerange

Eliminate undervoltage

3. Diagnosis


SF (system failure) � system fault

LED (red) Sequence 1) Status Meaning/fault treatment

LED is out

ON

OFF

No fault. �

LED flashes

ON

OFF

Simple fault/information(fault class 1)

See description of fault numbers inthe CPX system manual

LED flashes

ON

OFF

Fault(fault class 2)

LED flashes

ON

OFF

Serious fault(fault class 3)

1) The system fault LED flashes depending on the class of fault which has occurred.Fault class 1 (simple fault): 1 * flash, pauseFault class 2 (fault): 2 * flash twice, pauseFault class 3 (serious fault): 3 * flash three times, pause

3. Diagnosis


M (modify) � parametrizing modified or Force active

LED (yellow) Sequence Status Meaning/fault treatment

LED is out

ON

OFF

System start with defaultparametrizing (factorysetting) and current CPXequipment status is set;external parametrizing ispossible (pre−setting).

none

LED lights up

ON

OFF

System start with savedparametrizing and savedCPX equipment status isset;parameters and CPXequipment status aresaved remanently; externalparametrizing is blocked 1)

Be careful when replacing CPX valveterminals with saved parametrizing.With these CPX valve terminals,parametrizing is not carried out auto�matically by the higher−order PLC/IPCwhen the terminal is replaced. Inthese cases check before replacing tosee which settings are required and, ifnecessary, carry out these settings.

LED flashes

ON

OFF

� Force is active 1)

� Network settings havebeen modified

� The Force function is enabled (seesystem parameter Force mode;function no. 4402).

� Start CPX−FB32 again (PowerOFF/ON), see also section 1.3.3

1) The display of the Force function (LED flashes) has precedence over the display of the setting for System start (LED lights up).

3. Diagnosis


EtherNet/IP specific LEDs

MS � module status

LED Sequence Status Meaning/fault treatment

is out

ON

OFF

Logic supply for businterface not applied

· Check logic supply

lights upgreen

ON

OFF

Operating status normal None

flashes green

ON

OFF

The CPX terminal must becommissioned because itis not yet configured, is notcomplete or is not correct.

Carry out the configuration, completeor correct

flashes red

ON

OFF

Fault can be rectified Complete or correct the configuration

lights up red

ON

OFF

Fault cannot be rectified Check equipment on CPX as well asother LEDs and, if necessary, requestservice

flashesred−green

ON

OFF

CPX terminal is in self−test None

3. Diagnosis


NS � network status


is out

ON

OFF

The CPX terminal is notonline� Logic supply for bus

interface not applied· Check logic supply

flashes green

ON

OFF

CPX terminal is online andhas received an IP address,but the CPX terminal doesnot have a configuredconnection.

· Check the configuration, perhapsthe CPX terminal is not assigned toa scanner/master.or

· Check the status of the master, itis possible that the master is not inthe RUN mode.

lights upgreen

ON

OFF

The CPX terminal is onlineand has a connection tothe field bus.

None (normal operating status)

flashes red

ON

OFF

One or several �I/O con�nections" is/are in thetime−out status

Check the physical connection to themaster/scanner (EtherNet cable).

lights up red

ON

OFF

Communication has failed.� Non−permitted IP

address set and alreadyused in the network

· Correct IP address

flashesred/green

ON

OFF


*) Test algorithm which ensures that station numbers on the network are not assigned twice. The testis usually carried out automatically when the network connection is set up.

3. Diagnosis


I/O (I/O status)


is out

ON

OFF

� Logic supply for businterface not applied

� Inputs/outputs areinactive

· Check logic supply

lights up

ON

OFF

One or more inputs/out�puts is/are controlled viaEtherNet/IP.None of the inputs/outputshas a fault.

None

flashes green

ON

OFF

One or more outputs is/arein the idle state and noneof the outputs is active orfaulty.

I/O control via EtherNet/IP, but deviceis allocated by the master and themaster is in idle mode, e.g. program�ming mode.

flashes red

ON

OFF

One or more inputs/out�puts is/are faulty, perhapsin fault status.

Check the inputs/outputs and thecommunication connection to themaster.

lights up red

ON

OFF

One or several outputs areforcibly switched off (per�haps a fault which cannotbe corrected); one or moreinputs have a fault whichcannot be corrected.

Check the other LEDs, if necessaryrequest servicing

flashesred/green

ON

OFF


3. Diagnosis


TP (Link/Traffic)

LED (green) Sequence Status Fault treatment

LED is out

ON

OFF

No Ethernet connection orEthernet cable notconnected

If necessary check Ethernetconnection

LED lights up

ON

OFF

Network connection OK(Link)

�

LED flashes

ON

OFF

Data traffic (Traffic)The light intensity dependson data traffic.

�

3. Diagnosis


3.3 Diagnosis via status bits

Status bits are internal inputs (1 input byte) which serve fordisplaying common diagnostic messages (global faultmessages).

Please noteIf status bits are to be transmitted via a �Polled" or�Change of State" connection, you must set the DILswitches on the field bus node accordingly (see Tab.�1/2).

If all status bits supply a 0−signal, no fault will be registered.The following table shows the diagnostic information whenthere is a 1−signal:

Bit Diagnostic informationwith 1−signal

Description

0 Fault at valve Module type on which afault has occurred

1 Fault at outputfault has occurred.

2 Fault at input

3 Fault on analogue module/technology 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 ofmodules, these faults cannot be assigned via the status bits.Faults can be clearly defined via the I/O diagnostic interfaceof by diagnosis via EtherNet/IP access.

Further instructions on the function and content of the statusbits can be found in the CPX system manual.

3. Diagnosis


3.4 Diagnosis via I/O diagnostic interface

For the field bus node CPX−FB32, access to the EtherNet/IPObjects va Explicit Message programming is always more suit�able than via the I/O diagnostic interface (see appendix B.1).

Detailed diagnostic information can be accessed via the I/Odiagnostic interface. You can ascertain exactly, e.g. on whichmodule and on which channel a fault has occurred. 16 inputbits and 16 output bits, via which all diagnostic data can beread, are available for accessing the system diagnosis.

Please noteIn order to use the I/O diagnostic interface, this must beactivated with the DIL switch on the field bus node(see�Tab.�1/2).

If the I/O diagnostic interface is active, it will occupy the first16 inputs and outputs in the address range (see Tab.�2/6).

Information on the I/O diagnostic interface (diagnostic in�formation, function numbers) can be found in the CPX systemmanual.

Overview of diagnostic data

Diagnostic data Contents / description

Global diagnostic data � General overview of faults

Module diagnostic data � Detail diagnosis per module

Status of diagnosticmemory

� Number of entries in the diagnosticmemory

� Operating mode

Diagnostic memorydata

� Long−term memory� Detail diagnosis + relative time stamp

per fault event

Tab.�3/4: Diagnostic data

3. Diagnosis


3.5 Diagnosis via EtherNet/IP

The CPX system enables diagnosis via EtherNet/IP. The following diagnostic possibilities are supported here:

� Explicit Messaging via Ethernet/IP master

� Diagnosis via user program The I/O diagnostic interfacecan also be read out here.

Overview of diagnostic data with Explicit Messaging

The following EtherNet/IP Objects offer detailed diagnosticinformation:

Objectclasses

Name Diagnostic data

101d General Module ParameterObject

� Faulty channel type� Number of the faulty channel� Module fault number

133d Status and Diagnostic Object � Number of the module in which a fault has occurred.� Diagnostic status (specifies whether there are

diagnostic data)� System fault number

134d Diagnostic Trace Object � Long−term memory (max. 40 entries)� Detail diagnosis + relative time stamp per fault event

135d Diagnostic Trace Status Object � Number of entries in the diagnostic memory� Trace status

Tab.�3/5: Diagnostic data with Explicit Messaging

3. Diagnosis


Possible sequence of diagnosis

Possible sequence of diagnosis Diagnostic data Object whichsupplies thediagnostic data

1. Check to see if there are diagnostic data Diagnostic status Status and DiagnosticObject (133d)

2. Ascertain the number of the module in which afault has occurred.

Number of the module Status and DiagnosticObject (133d)

3. Ascertain relevant module diagnostic data Fault number, channeltype and number ofthe faulty channel

General ParameterObject Module (101d)

Tab.�3/6: Possible sequence of diagnosis

3. Diagnosis


3.6 Fault treatment

With the following faults, the reaction of the CPX terminaldepends on the configured reaction of the master moduleand on the parameterised Fail safe setting:

� telegram failure

� master has stopped

� interruption in the bus cable.

Depending on the parametrizing, the outputs (valves andelectric outputs) will be switched off (factory setting),switched on or retain their status (see CPX system manual).

Warning· Make sure that valves and outputs are put into a safestate if the faults named occur.

An incorrect status of the valves and outputs can lead todangerous situations.

Please notePlease note the following if the outputs are reset after PLCstop, 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: pressurized, exhausted or blocked).

3. Diagnosis


Technical appendix

A−1Festo P.BE−CPX−FB32−EN en 0605NH

Appendix A

A. Technical appendix

A−2 Festo P.BE−CPX−FB32−EN en 0605NH

Contents

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

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

A.2 Accessories A−4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


A−3Festo P.BE−CPX−FB32−EN en 0605NH

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

General

General technical data See CPX system manual P.BE−CPX−SYS−...

Protection class as per EN 60529, CPX−FB32 fittedcompletely, plug connector as per Accessoriesplugged in or fitted with protective cap.

IP65 / IP67

Protection against electric shock(protection against direct and indirect contact as perIEC/DIN EN 60204−1)

By means of PELV power circuit(Protected Extra−Low Voltage)

Current consumption of field bus node CPX−FB32Internal current consumption at 24 V (internalelectronics):� Of operating voltage supply for electronics/

sensors (VEL/SEN)Typ. 65 mA

Electrical isolation� Ethernet/IP interface Electrically isolated (optocoupler)

Module code (CPX−specific) Remote I/O: 212Remote Controller: 160

Module identification (Handheld) Remote I/O:� �CPX−FB32 Remote/IO"Remote Controller:� �CPX−FB32 Remote Controller"


A−4 Festo P.BE−CPX−FB32−EN en 0605NH

Field bus

Protocols � IEEE 802.3 (Ethernet) as per RFC 894� Internet Protocol (RFC 791)� User Datagram Protocol (UDP) (RFC 768)� Transmission Control Protocol (TCP) (RFC 793)� Address Resolution Protocol (ARP) (RFC 826)� Internet Control Messaging Protocol (ICMP) (RFC 792)� Internet Group Management Protocol (IGMP) (RFC 1112 & 2236)� HTTP� FTP� DHCP

Baud rate 10/100 MBd, full/half duplex

Cable type and length See Ethernet specification as per IEEE 802.3

Webserver of the CPX−FB32

Memory space for own Web pages 384 kB

FTP access for saving own Web pages FTP−URL: IP address of the CPX−FB32FTP Port: 21FTP user name: RootFTP password: Festo

Address of the Web pages in the Webserver http://"myURL"/FS/www/"Filename"

A.2 Accessories

Accessories Type Part no.

M12 plug for connection to the field bus NECU−M−S−D12G4−C2−ET 543109

Software for using the integrated Webserver CPX−WEB−MONITOR 545413

Tab.�A/1: Accessories

Ethernet/IP Objects of the CPX−FB32

B−1Festo P.BE−CPX−FB32−EN en 0605NH

Appendix B

B. Ethernet/IP Objects of the CPX−FB32

B−2 Festo P.BE−CPX−FB32−EN en 0605NH

Contents

B. Ethernet/IP Objects of the CPX−FB32 B−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1 Overview of Ethernet/IP Objects of the CPX−FB32 B−3 . . . . . . . . . . . . . . . . . . . . .

B.2 Objects for network settings B−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.1 Port Object B−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.2 TCP/IP Interface Object B−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.3 Ethernet Link Object B−9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3 Objects for the I/O connection B−10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3.1 Assembly Object B−10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4 Objects for system data and diagnosis B−15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.1 Identity Object B−15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.2 System Object (for operating mode Remote I/O) B−16 . . . . . . . . . . . . . .

B.4.3 Status and Diagnostic Object B−19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.4 Diagnostic Trace Object B−20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.5 Diagnostic Trace Status Object B−21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.6 General Module Parameter Object B−23 . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.7 Force parameter B−26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.8 Fail safe and Idle parameters B−31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.9 Configuration Array Object B−36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.10 Slave Size Object (for operating mode Remote Controller) B−36 . . . . . .

B.5 Examples B−37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.5.1 Example: Forcing inputs B−37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.5.2 Example: Parametrizing with the general Modul Parameter Object B−39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



B.1 Overview of Ethernet/IP Objects of the CPX−FB32

This chapter describes the representation of the CPX terminalwithin the DeviceNet Object model. The information is in Eng�lish in order that the original terms of the Ethernet/IP specifi�cation can be used clearly.

Ethernet/IP Class Services

The CPX terminal supports various services depending on theObject:

Service Code Service Name

05d (05h) Reset

01d (01h) Get Attribute All

14d (0Eh) Get Attribute Single

16d (10h) Set Attribute Single

Tab.�B/1: Class services and Instance services



Ethernet/IP Object classes

The following Objects are supported:

Object class Instances Name Type

1d 1 Identity Object CIP general

2d 1 Message Router Object

4d 100...102 Assembly Object

6d 1...10 Connection Manager Object

244d 1 Port Object

245d 1 TCP/IP Interface Object Ethernet/IP specific

246d 1 Ethernet Link Object

132d 1 System Object (Global System Object) CPX specific

133d 1 Status and Diagnostic Object

134d 1...40 Diagnostic Trace Object

135d 1 Diagnostic Trace Status Object

199d 1 Configuration Array Object

Tab.�B/2: Overview of EtherNet/IP Objects of the CPX−FB32 � part 1




101d 1...48 General Module Parameter Object (Generic Parameter Object)

CPX specific:Parameters

102d 1...48 Discrete Input Object CPX specific:Inputs/outputs

103d 1...48 Discrete Output ObjectInputs/outputs

104d 1...48 Analogue Input Object

105d 1...48 Analogue Output Object

106d 1...48 Function Input Object

107d 1...48 Function Output Object

108d 1...48 Discrete Input Force State Object CPX specific:Force Fault

109d 1...48 Discrete Input Force Mode ObjectForce, Fault,Idle�mode

110d 1...48 Discrete Output Force State Object

111d 1...48 Discrete Output Force Mode Object

112d 1...48 Discrete Output Fault State Object

113d 1...48 Discrete Output Fault Mode Object

114d 1...48 Discrete Output Idle State Object

115d 1...48 Discrete Output Idle Mode Object





116d 1...48 Analogue Input Force State Object CPX specific:Force Fault

117d 1...48 Analogue Input Force Mode ObjectForce, Fault,Idle�mode

118d 1...48 Analogue Output Force State Object

119d 1...48 Analogue Output Force Mode Object

120d 1...48 Analogue Output Fault State Object

121d 1...48 Analogue Output Fault Mode Object

122d 1...48 Analogue Output Idle State Object

123d 1...48 Analogue Output Idle Mode Object

124d 1...48 Function Input Force State Object

125d 1...48 Function Input Force Mode Object

126d 1...48 Function Output Force State Object

127d 1...48 Function Output Force Mode Object

128d 1...48 Function Output Fault State Object

129d 1...48 Function Output Fault Mode Object

130d 1...48 Function Output Idle State Object

131d 1...48 Function Output Idle Mode Object



136d 1 Slave Size Object CPX specific

Tab.�B/5: Special EtherNet/IP Object for the operating mode Remote Controller



Counting mode With the module−orientated Objects in Tab.�B/3 andTab.�B/4 the following applies: Instance number = modulenumber + 1Explanation: The counting of the modules begins with 0 onthe field bus node; the counting of the instances begins with1 on the field bus node.

An overview of the available data and parameters, their func�tion numbers as well as their assignment to the objects canbe found in the following sections.

A description of the functions of the individual parametersand data as well as basic information on parametrizing can befound in the CPX system manual.

B.2 Objects for network settings

B.2.1 Port Object

Object class: 244Instances: 1

The Port Object lists the CIP ports available on the device.The Port Object of the CPX−FB32 supports an instance withthe ID 2.

Attr.no.

Access Description Type

1 Get Revision WORD

2 Get Max Instances WORD

3 Get Number of Instances Array

8 Get Entry Port Array

9 Get All Ports Array



B.2.2 TCP/IP Interface Object


With the TCP/IP Interface Object you can configure thenetwork settings of a device.

Attr.no.


1 Get Status DOUBLE

2 Get Configuration Capability DOUBLE

3 Get/Set Configuration Control DOUBLE

4 Get Physical Link ObjectPath SizePath

Array

5 Get/Set Interface Configuration IP Address Network Mask Gateway Address Name Server Name Server 2 Domain Name

Array

6 Get/Set Host Name Array



B.2.3 Ethernet Link Object


Via the Ethernet Link Object you can undertake extendedsettings for the Ethernet connection (see also section 1.3.4):

Attr.no.


1 Get Interface Speed DOUBLE

2 Get Interface Flags DOUBLE

3 Get Physical MAC address Array

6 Get/Set Interface Control DOUBLE

Control Bits DOUBLE

Forced Interface Speed DOUBLE

Further details can be found in the Ethernet/IP specification.



B.3 Objects for the I/O connection

B.3.1 Assembly Object


The Assembly Object bundles together Attributes of variousObjects, so that the exchange of data with the Objects cantake place via one connection.

The following Object instances are saved in the AssemblyObject:

Instances Description

101 Input data

100 Output data

102 Configuration data



Operating mode Remote I/O

Each data range begins on the LSB (least significant bit) of aword.

Instance 101: Input

Within the instance �Input Assembly Object" all inputs of theCPX system are transmitted cyclically over the network bymeans of a communication connection. The followingsequence applies during transmission:

Sequence of transmission

1. I/O diagnostic interface, if active (16−bit orientated)

2. Object instances of the analogue channels (16−bit orientated)

3. Instances of the technology modules (16 or 8−bit orientated)

4. Object instances of the digital inputs (8−bit orientated)

Instance 101 (input) possesses the following member list inthe operating mode Remote I/O:

Obj. Instances (= module no. + 1)

Attributes(channel)

Entries in member list Type

133 1...48 0/1 I/O diagnostic interface data,if�active

WORD

104 1...48 1...32 Analogue channel data WORD

106 1...48 1...64 /65...96

Technology module BYTE/WORD

102 1...48 1...64 Digital data BOOL



Instance 100: Output

Within the instance Output in the Assembly Object all outputsof the CPX system will be transmitted over the network bymeans of one communication connection. The followingsequence 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 technology modules (16 or 8−bit orientated)

4. Object instances of the digital outputs (8−bit orientated)

Instance 100 (Output) possesses the following member list inthe operating mode Remote I/O:

Obj. Instances(= module no. + 1)

Attributes(channel)

Entries in member list Type

133 1...48 0/1 I/O diagnostic interface data, if active

WORD

105 1...48 1...32 Analogue channel data WORD

107 1...48 1...64 /65...96


103 1...48 1...64 Digital data BOOL



Instance 102: Configuration

Instance 102 (Configuration) possesses the following memberlist:

Obj. Number of Entries in member list Type

199 1 Configuration Array data Array

The I/O Objects 102...107 also possess the following at�tributes:

Attribute Entries ... Type

100 Number of data of the modulein BYTE or WORD

BYTE

101 Data type:� D1h: BYTE� D2h: WORD

BYTE

102 All data values Array



Operating mode Remote Controller

Each data range begins on the LSB (least significant bit) of aword.

Instance 100: Output

Instance 100 (Output) possesses the following member list inthe operating mode Remote Controller:


107 1...64 /65...96


Instance 101: Input

Instance 101 (input) possesses the following member list:


106 1...64 / 65...96


Transmission by communication types Polled I/O or COS/Cyclic.

Instance 102: Configuration

Instance 102 (Configuration) must have the value �0" in theoperating mode Remote Controller.



B.4 Objects for system data and diagnosis

B.4.1 Identity Object


The Identity Object contains the identification and generalinformation on the CPX−FB32.

Attr.no.


1 Get Vendor ID WORD

2 Get Device type WORD

3 Get Product code WORD

4 Get Revision (major/minor) WORD

5 Get Status WORD

6 Get Serial number DOUBLE

7 Get Product name Array

14 Get/Set Semaphore Array

100 Get Operating Mode BOOL

101 Get External Module Identifiers Array



B.4.2 System Object (for operating mode Remote I/O)


This Object is only available in the operating mode RemoteI/O.

Attr.no.

Access Description Type Functionno.

1 Get CPX operating mode (bit 0...3)0: Remote I/O without FEC1: Remote I/O with FEC2: Remote Controller without bus node3: Remote Controller with bus node

BYTE 0 (bit 0...3)

CPX equipment status (bit 4)Specifies whether the current equipment fitted to theCPX corresponds to the saved CPX equipment status.0: equal1: not equal

0 (bit 4)

Handheld (bit 5)Specifies whether or not a handheld is connected.0: Handheld not connected1: Handheld connected

0 (bit 5)

Force mode (bit 6)Specifies whether Force is blocked or enabled.0: blocked1: enabled

0 (bit 6)

Bit 7: Reserved 0 (bit 7)

2 Get Fail safeSpecifies whether Fail safe is active or inactive.0: inactive1: active

BYTE 1 (bit 0, 1)

System Idle modeSpecifies whether Idle mode is active or inactive.0: inactive1: active

1 (bit 2, 3)



Attr.no.

Functionno.

TypeDescriptionAccess

3 Get Monitoring CPX terminal (bit 0...7)Specifies whether the monitoring of short circuit/over�load and undervoltage is active or inactive.Bit 0: Monitoring short circuit/overload in the

sensor supplyBit 1: Monitoring short circuit at the outputs

Short circuit/overload at the outputsBit 2: Monitoring Vout

Undervoltage at the outputsBit 3: Monitoring Vval

Undervoltage at valvesBit 4: Monitoring SCV (short circuit at valves)Bit 5...7: Reserved0: inactive1: active

BYTE 2 (bit 0...7)

4 Get Number of input bytes (Rx size)Specifies the number of input bytes of the CPX terminal.

BYTE �

5 Get Number of output bytes (Tx size)Specif. the number of output bytes of the CPX terminal.

BYTE �

9 Get/Set Monitoring (bit 0...7)Bit 0: Monitoring short circuit/overload in the

sensor supplyBit 1: Monitoring short circuit/overload at the

outputsBit 2: Monitoring Vout (undervoltage at outputs)Bit 3: Monitoring Vval (undervoltage at valves)Bit 4: Monitoring SCV (short circuit at the valves)Bit 5...7: Reserved1: active (presetting)0: inactive

BYTE 4401 (bit 0...7)

10 Get/Set Fail safe0: Reset all outputs (presetting)1: Hold last state (retain signal status)2: Assume fault mode

BYTE 4402 (bit 0, 1)

11 Get/Set Force mode0: blocked1: enabled

BYTE 4402 (bit 2, 3)



Attr.no.

Functionno.

TypeDescriptionAccess

12 Get/Set System Idle mode0: Reset all outputs (presetting)1: Hold last state (retain signal status)2: Assume Idle mode

BYTE 4402 (bit 4, 5)

13 Get/Set System start0: System start with default parameterisation (factory

setting) and current CPX equipment status; external parameterisation is possible (presetting)

1: System start with saved parameterisation and savedCPX equipment status; parameters and CPX equip�ment status are saved remanently; external para�meterisation is blocked; the M−LED on the field busnode lights up.

BYTE 4402 (bit 6)



B.4.3 Status and Diagnostic Object


The status bits and the I/O diagnostic interface are mappedhere.

Attr.no.


1 Get Status bits (8 bit)Fault source: Bit 0: valve

Bit 1: outputBit 2: inputBit 3: analogue/technology module

Fault type: Bit 4: undervoltageBit 5: short circuit/overloadBit 6: wire fractureBit 7: other faults

BYTE 1936

2 Get Number of the first module in which a fault has occurred. BYTE 1937

3 Get Diagnostic status BYTE

4 Get Fault number BYTE 1938

5 Get/Set Address of the I/O diagnostic interface16 output bits (task data) of the I/O diagnostic interface

WORD

6 Get Data of the I/O diagnostic interface16 input bits (reply data) of the I/O diagnosic interface

WORD



B.4.4 Diagnostic Trace Object

Object class: 134Instances: 1...40

An instance is created for each diagnostic entry.

Attr.no.

Access Designation Description Type Function no.3488 + n 1)

1 Get Marking the first entry afterPower onSupplies 1 if it is the firstentry after Power on.

BYTE n = 10 * d + 4(bit 7)

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

3 Get Hours Number of hours 2) BYTE n = 10 * d + 1

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

5 Get Seconds Number of seconds 2) BYTE n = 10 * d + 3

6 Get Milliseconds Number of 10 msec 2) BYTE n = 10 * d + 4(bit 0...6)

7 Get Module code �3) Module code of the modulewhich registered the fault.

BYTE n = 10 * d + 5

8 Get Module number Module position of themodule which registered thefault; 63 = fault notmodule−related

BYTE n = 10 * d + 6(bits 6, 7)

9 Get Channelnumber �3)

Number of the first faultychannel

BYTE n = 10 * d + 7(bit 0...5)

10 Get Fault number Possible fault messages seeSystem Manual chapter 5.

BYTE n = 10 * d + 8

11 Get Subsequentchannels 3)

Number of subsequentchannels with the same fault

BYTE n = 10 * d + 9

1) d (diagnostic event) = 0...39; most current diagnostic event = 02) Measured from the moment the power supply is switched on3) 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).



B.4.5 Diagnostic Trace Status Object


Attr.no.

Access Name Type Functionno.

1 Get Number of Trace entries in the diagnostic memory BYTE 3482(bit 0...7)

2 Get Status of diagnostic memory0: Registering active1: Registering inactive

BYTE 3483(bits 0, 1)

3 Get/Set Clear_trace1, access via EDS BYTE �

4 Get/Set Clear_trace2, access via explicit messaging;Confirms activity carried out by resetting (0) theattribute value

BYTE �

5 Get/Set Entries remanent with Power on0: active (presetting)1: inactive

BYTE 3480(bit 0)

6 Get/Set Run/Stop filter 10: Stop after 40 entries (save the first 40 entries)1: Overwrite old entries (save the last 40 entries),

presetting)

BYTE 3480(bit 1)

7 Get/Set Run/Stop filter 20: Run/stop filter 2 inactive (presetting)1: Register up to the defined FN2: Register up to the defined FN + MN3: Register up to the defined FN + MN + CN4: Register as from the defined FN5: Register as from the defined FN + MN6: Register as from the defined FN + MN + CN7: Reserved

MN = module numberCN = channel numberFN = fault number

BYTE 3484(bit 0...2)



Attr.no.

Functionno.

TypeNameAccess

8 Get/Set Fault end filter0: Register running faults (end of fault)

(filter inactive, presetting)1: Do not register running faults (end of fault)

(filter active)

BYTE 3484(bit 3)

9 Get/Set Fault number filterFN = fault number0: Fault number filter inactive (presetting)1: Register only defined FN2: Do not register defined FN3: Reserved


10 Get/Set Module/channel filterWith this diagnostic memory filter, the registering offaults of other modules or channels can be suppres�sed in order that faults in a particular module orchannel can be analysed.FN = fault number0: Module/channel filter inactive (presetting)1: Register only the FN of a module2: Register only the FN of a channel3: reserved


11 Get/Set Module numberModule number for the diagnostic memory filter

BYTE 3485(bit 0...7)

12 Get/Set Channel numberChannel number for the diagnostic memory filter

BYTE 3486(bit 0...7)

13 Get/Set Fault numberFault number for the diagnostic memory filter

BYTE 3487(bit 0...7)



B.4.6 General Module Parameter Object

Object class: 101Instances: 1...48

Note: Instance number = module number + 1

This Object enables general access to the module parametersof all existing and future CPX modules.

Use the general parameter Module Object for parametrizingmodules with word or double−word parameters. Examples ofmodules with word or double−word parameters: the analogue4−input module CPX−4AE−I, the temperature module CPX−4AE−Tor the CPX−CP interface.

You can access three types of parameters via the Attributes ofthe general Module Parameter Object:

� byte parameters via Attributes 1...64� word parameters via Attributes 65...127� double−word parameters via Attributes 129...189

Procedure forparametrizing

1. Refer to the module manual for the function number ofthe parameter which you wish to set.

2. Search for this function number in the last column ofTab.�B/6 (byte and word parameter) or Tab.�B/7(double−word parameter)

3. Read the appropriate Attribute number from the table.

Examples for parametrizing with the general ModuleParameter Object can be found in section B.5.2.



Attribute no. Parameter Function no.

Byte Word Word

165

� See relevant module manual for the parameter 4828 + m * 64 + 0

265

664828 + m * 64 + 1

367

664828 + m * 64 + 2

467

684828 + m * 64 + 3

569

684828 + m * 64 + 4

669

704828 + m * 64 + 5

771

704828 + m * 64 + 6

871

724828 + m * 64 + 7

973

724828 + m * 64 + 8

1073

744828 + m * 64 + 9

1175

744828 + m * 64 + 10

1275

764828 + m * 64 + 11

...76

4828 + m * 64 + ...

......

4828 + m * 64 + ...

......

4828 + m * 64 + ...

......

1244828 + m * 64 + 59

61125

1244828 + m * 64 + 60

62125

1264828 + m * 64 + 61

63127

1264828 + m * 64 + 62

64127

� 4828 + m * 64 + 63

Tab.�B/6: General Module Parameter Object: Assignment of the Attributes for wordparameters to the function numbers



Attribute no. Parameter Function no.

Byte DWord DWord DWord DWord

1 � � � See relevant modulemanual for the

4828 + m * 64 + 0

2manual for theparameter 4828 + m * 64 + 1

3129

p

4828 + m * 64 + 2

4130

4828 + m * 64 + 3

5131

4828 + m * 64 + 4

6132

4828 + m * 64 + 5

7133

4828 + m * 64 + 6

8134

4828 + m * 64 + 7

9135

6

4828 + m * 64 + 8

10136

4828 + m * 64 + 9

11...

4828 + m * 64 + 10

12...

4828 + m * 64 + 11

......

4828 + m * 64 + ...

......

4828 + m * 64 + ...

...185

6

4828 + m * 64 + ...

...186

4828 + m * 64 + 59

61187

4828 + m * 64 + 60

62 �188

4828 + m * 64 + 61

63189

� 4828 + m * 64 + 62

64 � 4828 + m * 64 + 63

Tab.�B/7: General Module Parameter Object: Assignment of the Attributes fordouble−word parameters to the function numbers



B.4.7 Force parameter

The first word receives the lowest instance number of therelevant Object. The second word receives the second lowestinstance number, etc.

Object Description

108 Force state digital inputs

109 Force mode digital inputs

110 Force state digital outputs

111 Force mode digital outputs

Tab.�B/8: Objects for Force Parameter digital I/O modules

Object Description

116 Force state analogue inputs

117 Force mode analogue inputs

118 Force state analogue outputs

119 Force mode analogue outputs

Tab.�B/9: Objects for Force Parameter analogue I/Omodules

Object Description

124 Force state inputs technology module

125 Force mode inputs technology module

126 Force state outputs technology module

127 Force mode outputs technology module

Tab.�B/10: Objects for Force Parameter for technologymodule



Composition of the Objects for Force mode

Objects for Force mode: 109, 111, 117, 119, 125, 127(see Tab.�B/8...Tab.�B/10)

Instances: 1...64, 100, 101

Attr.no.


1 Get/Set Value for Force mode:Channel 0:0 = Force blocked1 = Force enabled

BOOL

2 Get/Set Channel 1:0 = Force blocked1 = Force enabled

BOOL

... ... ... ...

64 Get/Set Channel 63:0 = Force blocked1 = Force enabled

BOOL

100 Get Number of channels BYTE

101 Get All channels: Values for Force mode

Array

Tab.�B/11: Basic composition of the Objects for Force mode



Composition of the Objects for Force statefor�digital�I/O modules

Objects for Force state: 108, 110 (see Tab.�B/8)Instances: 1...64, 100, 101

Attr.no.


1 Get/Set Value for Force state:Channel 0:0 = Reset signal1 = Set signal

BOOL

2 Get/Set Channel 1:0 = Reset signal1 = Set signal

BOOL

... ... ... ...

64 Get/Set Channel 63:0 = Reset signal1 = Set signal

BOOL


101 Get All channels: Values for Force state

Array

Tab.�B/12: Composition of the Objects for Force state fordigital I/O modules



Composition of the Objects for Force statefor�analogue I/O modules

Objects for Force state: 116, 118 (see Tab.�B/9)Instances: 1...32, 100, 101

Attr.no.


1 Get/Set Channel 0:Value for Forcing

WORD


WORD

... ... ... ...


WORD

Tab.�B/13: Composition of the Objects for Force state foranalogue I/O modules



Composition of the Objects for Force statefor�technology modules

Objects for Force state: 124, 126(see Tab.�B/10)

Instances: 1...64, 100, 101

Attr.no.



BYTE


BYTE

... ... ... ...


BYTE


WORD

... ... ... ...


WORD


101 Get Data type:� D1h: BYTE� D2h: WORD

BYTE

102 Get/Set All channels: Values for Force state Array

Tab.�B/14: Composition of the Objects for Force statetechnology modules



B.4.8 Fail safe and Idle parameters

The first word receives the lowest instance number of therelevant Object. The second word receives the second lowestinstance number, etc.

Object Description

112 Fault state digital outputs

113 Fault mode digital outputs

114 Idle state digital outputs

115 Idle mode digital outputs

Tab.�B/15: Objects for Fail safe and Idle parameters ofdigital output modules

Object Description

120 Fault state analogue outputs

121 Fault mode analogue outputs

122 Idle state analogue outputs

123 Idle mode analogue outputs

Tab.�B/16: Objects for Fail safe and Idle parameters of ana�logue output modules

Object Description

128 Fault state outputs technology module

129 Fault mode outputs technology module

130 Idle state outputs technology module

131 Idle mode outputs technology module

Tab.�B/17: Objects for the Fail safe and Idle parameters fortechnology modules



Composition of the Objects for Fault/Idle mode

Objects for Fault state: 112, 120, 128Objects for Fault mode: 113, 121, 119

(see Tab.�B/15 ... Tab.�B/17)Instances: 1...64, 100, 101

Attr.no.


1 Get/Set Values for Fault/Idle mode:Channel 0:0 = Hold last state1 = Fault/Idle state

BOOL

2 Get/Set Channel 1:0 = Hold last state1 = Fault/Idle state

BOOL

... ... ... ...


BOOL


101 Get All channels: Values for Fault/Idle mode

Array

Tab.�B/18: Composition of the Objects for Fault/Idle mode



Composition of the Objects for Fault/Idle statefor�digital output modules

Object Fault state: 112Object Idle state: 114

(see Tab.�B/15)Instances: 1...64, 100, 101

Attr.no.



BOOL


BOOL

... ... ... ...


BOOL


101 Get All channels: Values for Fault/Idle state

Array

Tab.�B/19: Composition of the Objects for Fault/Idle statefor digital output modules



Composition of the Objects for Fault/Idle statefor�analogue output modules



Attr.no.


1 Get/Set Channel 0:Value for Fault/Idle state

WORD


WORD

... ... ... ...


WORD

Tab.�B/20: Composition of the Objects for Fault/Idle statefor analogue output modules and technologymodules



Composition of the Objects for Fault/Idle statefor�technology modules



Attr.no.



BYTE


BYTE

... ... ... ...


BYTE


WORD

... ... ... ...


WORD


101 Get Data type:� D1h: BYTE� D2h: WORD

BYTE

102 Get/Set All channels: Values for Fault/Idle state

Array

Tab.�B/21: Composition of the Objects for Fault/Idle statefor analogue output modules and technologymodules



B.4.9 Configuration Array Object

The Configuration Array Object is available only as from arevision status later than 1.2. Further information on this Ob�ject can be found under www.festo.com/fieldbus.

Instances: 1Object class: 199

Attr.no.


1 Get/Set Data field with all system and module parameters. Array �

B.4.10 Slave Size Object (for operating mode Remote Controller)


This Object is only available in the operating mode RemoteController. It contains the number of I/O bytes for communi�cation of the CPX−FB32 with the CPX−FEC. The setting is madevia the DIL switch on the CPX−FB32 (see Tab.�1/3).

Attr.no.


1 Get Number of input bytes for the operating mode Remote Controller BYTE

2 Get Number of output bytes for the operating mode Remote Controller BYTE



B.5 Examples

B.5.1 Example: Forcing inputs

In this example the Force mode of an analogue input moduleis parametrized.

1 2

3

4 5 6

Instance no.: 1

8 O 8 O

1

8DI4AI−I 8DI 8DO

0Module no.:

22

3

4 5 6 7

1 Parametrizing: Module CPX−4AE−I: Setting Force Mode for channel 2Object class 117 (see Tab.�B/9)Instance 3 (= module number + 1)Attribute 3 (for channel 2, see Tab.�B/11 and Tab.�B/22)

Fig.�B/1: EXample of Forcing (sequence see text)

1. Enable Force mode

Enable the Force mode for the CPX terminal with the SystemObject 132 (see Tab.�B/2 and section B.4.2):

System Object: 132Instance: 1Attribute 11 (Force mode)



2. Define value for Force state for channel 2:

Objects for Force state: 116 (see Tab.�B/13)Instance: 3

Attr.no.

Access Parameter Type

... ... ... ...


WORD

... ... ... ...


101 Get All channels: Values for Force mode Array

Tab.�B/22: Example: Set Force state for module no. 2

3. Define Force mode for channel

Objects for Force state: 117 (see Tab.�B/11)Instance: 3

Attr.no.

Access Parameter Type

... ... ... ...

3 Get/Set Value for Force mode, channel 2:0 = Force blocked1 = Force enabled

BOOL

... ... ... ...


101 Get All channels: Values for Force mode Array

Tab.�B/23: Example: Set Force mode for module no. 2



B.5.2 Example: Parametrizing with the general Modul Parameter Object

In this example a signal extension time with a digital inputmodule and a lower limit value with an analogue input mod�ule are parametrized.

1 2

3

4 5 6

Instance no.: 1

8 O 8 O

1

8DI4AI−I 8DI 8DO

0Module no.:

22

3

4 5 6 7

2

1 Parametrizing module CPX−8DE: Enable signal extension channel 5Object class 101 (see B.4.6)Instance 1 (= module number)Attribute 7 (see Tab.�B/24)

2 Parametrizing module CPX−4AE−I: Lower limit channel 2Object class 101Instance 2 (= module number)Attribute 82 (see Tab.�B/25)

Fig.�B/2: Examples of parametrizing with the general Module Parameter Object

The following tables show you how to ascertain the Attributesfor the parametrizing. The parameters of the relevant mod�ules are entered in the tables.

Information on the parameters can be found in the manual forthe relevant module.



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

Byte Word Word

165

� Monitoring the CPX module 4828 + m * 64 + 0

265

66

Bit 0: Reaction after short circuit/overloadBit 4, 5: Input debounce timeBit 6, 7: Signal extension time

4828 + m * 64 + 1

367

� 4828 + m * 64 + 2

467

68� 4828 + m * 64 + 3

569

68� 4828 + m * 64 + 4

669

70� 4828 + m * 64 + 5

771

70Signal extension channel x 4828 + m * 64 + 6

871

... � 4828 + m * 64 + 7

Tab.�B/24: Example: Parametrizing the signal extension for module no. 1

Attribute no. Parameter (module no. 2 in Fig.�B/2) Function no.

Byte Word Word

165

� Monitoring the CPX module 4828 + m * 64 + 0

265

66Bit 0: Reaction after short circuit/overload 4828 + m * 64 + 1

...66

... 4828 + m * 64 + ...

......

... 4828 + m * 64 + ...

1580

...Lower limit channel 1 4828 + m * 64 + 14

1680

81Lower limit channel 1 4828 + m * 64 + 15

1782


1882


... ...83

... 4828 + m * 64 + ...

Tab.�B/25: Example: Parametrizing the lower limit value (module no. 2, channel 2)

Index

C−1Festo P.BE−CPX−FB32−EN en 0605NH

Appendix C

B. Index

C−2 Festo P.BE−CPX−FB32−EN en 0605NH

Contents

C. Index C−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B. Index


A

Abbreviations, product−specific XIII . . . . . . . . . . . . . . . . . . . .

Accessories A−4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Additional power supply 1−18 . . . . . . . . . . . . . . . . . . . . . . . . .

Address assignment 2−9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

B

Baud rate 1−16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bus configuration 2−19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C

ConnectingField bus 1−12, 1−13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply 1−17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CP interface 2−12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CPX−FEC 1−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D

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

Diagnosis via I/O diagnostic interface 3−14 . . . . . . . . . . . . . .

Diagnosis via LEDs 3−4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Diagnosis via status bits 3−13 . . . . . . . . . . . . . . . . . . . . . . . . .

Diagnostic data 3−14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Diagnostic possibilities 3−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DIL switch 1−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cover 1−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dismantling 1−5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B. Index


E

Electrical connecting and display elements 1−4 . . . . . . . . . . .

Ethernet cable 1−12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Ethernet/IP Objects B−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

F

Fault mode 2−32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FEC 1−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Field bus plug 1−13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fitting 1−5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I

I/O diagnostic interface 3−14 . . . . . . . . . . . . . . . . . . . . . . . . . .

ICO/BMP file 2−20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Idle mode 2−32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Important user instructions IX . . . . . . . . . . . . . . . . . . . . . . . . . .

InputsCalculate 2−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IP addressSet 1−14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L

LEDs 3−4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N

Notes on the use of this manual VIII . . . . . . . . . . . . . . . . . . . .

B. Index


O

ObjectsFor network settings B−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . For system data and diagnosis B−15 . . . . . . . . . . . . . . . . . . For the I/O connection B−10 . . . . . . . . . . . . . . . . . . . . . . . . . Overview B−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operating mode 1−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OutputsCalculate 2−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

P

ParametrizingExamples B−37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods 2−28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites 2−27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Via Configuration Assembly 2−29 . . . . . . . . . . . . . . . . . . . . . Via software 2−29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Via the PLC user program 2−30 . . . . . . . . . . . . . . . . . . . . . . With EDS files 2−31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . With the Handheld 2−29 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PELV (Protected Extra−Low Voltage) 1−17 . . . . . . . . . . . . . . . .

Pictograms X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pin assignmentField bus interface 1−13 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Power supply 1−17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

R

Remote Controller 1−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RSNetWorxStandard EDS 2−23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B. Index


S

Service VII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SetData size 1−9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic mode 1−9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIL switch 1−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP addressing 1−11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating mode 1−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Status bits 3−13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Strain relief 1−12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Switch coverRemoving and fitting 1−6 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System supply module 1−18 . . . . . . . . . . . . . . . . . . . . . . . . . .

T

Target group VII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical specifications A−3 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Text markings X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

V

Valve supply 1−18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CPX terminal - Festo · CPX terminal Manual 541 305 en 0605NH ... B.4.7 Force parameter B−26 ......

Documents

Transcript of CPX terminal - Festo · CPX terminal Manual 541 305 en 0605NH ... B.4.7 Force parameter B−26 ......