terminal cpx bus node cpxfb36 - festo usa€¦ · d.6.1 addressing examples for modbus® tcp d-24...

Description

Network protocolEtherNet/IPModbus TCP

Industrial Ethernet2-Port

8024075en 1611a[8067476]

Terminal CPX

Bus node CPXFB36

Contents and general instructions

IFesto CPX-FB36-EN en 1611a English

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

Version en 1611a. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Designation CPX-FB36-EN. . . . . . . . . . . . . . . . . . . . . . . . . . .

Order no. 8024075. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� (Festo AG & Co. KG, D‐73726 Esslingen, 2016)Internet: �http://www.festo.comE-mail: �[email protected]

Reproduction, distribution or sale of this document or communication of its contents to others withoutexpress authorization is prohibited. Offenders will be heldliable for damages. All rights are reserved, in particular theright to file patent, utility model or registered design applications.


II Festo CPX-FB36-EN en 1611a English

EtherNet/IP®, Modbus®, ROCKWELL AUTOMATION®, SPEEDCON® are registered trademarks of the respective trademark owners in certain countries.


IIIFesto CPX-FB36-EN en 1611a English

Contents

Intended use VIII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Safety instructions IX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Qualification of specialized personnel (target group) X. . . . . . . . . . . . . . . . . . . . . . . . .

Service X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Notes regarding this description XI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Important user information XII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Installation 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 General instructions for installation 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.1 Connection and display components 1-4. . . . . . . . . . . . . . . . . . . . . . . .

1.1.2 Dismantling and mounting 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Settings of the DIL switches 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.1 Removing and attaching cover 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.2 Arrangement of the DIL switches 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.3 Setting the DIL switches 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.4 Setting the operating mode and network protocol 1-8. . . . . . . . . . . . .

1.2.5 Setting diagnostic mode or data field size 1-9. . . . . . . . . . . . . . . . . . . .

1.2.6 Setting IP addressing 1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Connecting to the network 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.1 General instructions 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.2 Overview of connection technology and network plug connectors 1-13

1.3.3 Cable specification 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.4 Network connections 1-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.5 Setting the IP addressing 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.6 Extended network settings 1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Ensuring the degree of protection 1-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 Power supply of the CPX terminal 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


IV Festo CPX-FB36-EN en 1611a English

2. Preparing for commissioning 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 EtherNet/IP protocol 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.1 “Multicast” telegram 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.2 “QuickConnect” 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.3 “Device Level Ring” protocol (DLR) 2-8. . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Modbus® TCP protocol 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Notes on commissioning of the CPX-FB36 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Requirements for commissioning 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Switching on the power supply 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.3 Normal operating status 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 Participants in the network 2-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.1 Participant properties (EDS file) 2-16. . . . . . . . . . . . . . . . . . . . . . . . . . . .

3. Commissioning 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Configuration 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.1 Configuration with EDS file 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.2 Configuration with “Generic Ethernet Module” 3-11. . . . . . . . . . . . . . . .

3.1.3 Configuration with CPX-FMT 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.4 Configuration in the “Remote Controller” operating mode 3-20. . . . . . .

3.1.5 Setting up a “Listen only” connection 3-21. . . . . . . . . . . . . . . . . . . . . . .

3.2 Parameterisation 3-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.1 Parameterisation during switch-on [system start] 3-23. . . . . . . . . . . . . .

3.2.2 Methods of parameterisation 3-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.3 Parameterisation via configuration data 3-26. . . . . . . . . . . . . . . . . . . . .

3.2.4 Parameterisation with the control device CPX-MMI 3-26. . . . . . . . . . . .

3.2.5 Parameterisation in the PLC user program 3-26. . . . . . . . . . . . . . . . . . .

3.2.6 Parameterisation using CPX-FMT and system start with saved parameters3-27

3.3 Behaviour of the outputs in the “Fail safe mode” or “Idle mode” 3-28. . . . . . . . .

3.4 Web server 3-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Checklist for commissioning a CPX terminal 3-30. . . . . . . . . . . . . . . . . . . . . . . . . .

3.6 Replacing the bus node 3-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


VFesto CPX-FB36-EN en 1611a English

4. Diagnostics 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Diagnostics options 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Diagnostics via LED displays 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 CPX-specific LED displays 4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2 Network-specific LED indicators 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 Diagnostics via status bits 4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4 Diagnostics via the I/O diagnostics interface 4-13. . . . . . . . . . . . . . . . . . . . . . . . .

4.5 Diagnostics via EtherNet/IP 4-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.6 Diagnostics via Modbus®�TCP 4-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7 Error handling (“Fail safe”) 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A. Technical appendix A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.1 Technical data A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B. Address assignment of the CPX terminal B-1. . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1 Address assignment B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.1 Bus node B-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.2 Digital modules B-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.3 Analogue modules B-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.4 Technology modules B-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2 Addressing B-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.1 Basic rules for addressing B-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.2 Data formats B-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.3 Examples of addressing B-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3 Address assignment after extension/conversion B-20. . . . . . . . . . . . . . . . . . . . . .


VI Festo CPX-FB36-EN en 1611a English

C. EtherNet/IP Objects of the CPX-FB36 C-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.1 Overview of Ethernet/IP objects C-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2 Objects for network settings C-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2.1 “Device Level Ring Object” C-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2.2 “QoS Object” C-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2.3 “TCP/IP Interface Object” C-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2.4 “Ethernet Link Object” C-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.3 Objects for the I/O connection C-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.3.1 “Assembly Object” C-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4 Objects for system data and diagnostics C-18. . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.1 “Identity Object” C-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.2 “Global System Object” for operating mode “Remote I/O” C-20. . . . . .

C.4.3 “Status and Diagnosis Object” C-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.4 “Diagnosis Trace Object” C-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.5 “Diagnosis Trace Status Object” C-26. . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.6 “Generic Parameter Object” C-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.7 “Force Parameter” C-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.8 “Fail safe” and “Idle” parameters C-36. . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.9 “Configuration Array Object” C-42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.10 “Slave Size Object” for “Remote Controller” operating mode C-42. . . .

C.4.11 “ISDU Access Object” C-43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5 Examples C-45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5.1 Forcing inputs C-45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5.2 Parameterisation with “Generic Parameter Object” C-47. . . . . . . . . . . .


VIIFesto CPX-FB36-EN en 1611a English

D. Modbus® TCP objects of the CPX-FB36 D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.1 Overview of Modbus® TCP objects D-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.2 Commands and addresses D-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.3 CPX status information (Group A) D-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4 Process data (Group B and D) D-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.1 Bus node CPX-FB36 D-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.2 Electric modules D-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.3 Pneumatic modules D-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.4 Electrical interface (CP interface) CPX-CP-4-FB D-15. . . . . . . . . . . . . . . .

D.4.5 Composition of diagnostic data (diagnostic word) D-19. . . . . . . . . . . . .

D.4.6 Composition of the data of the I/O diagnostics interface D-20. . . . . . . .

D.5 Diagnostic memory (Groups C and E) D-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.6 Modbus TCP Objects (Group F) D-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.6.1 Addressing examples for Modbus® TCP D-24. . . . . . . . . . . . . . . . . . . . .

E. Index E-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


VIII Festo CPX-FB36-EN en 1611a English

Intended use

The bus node described in this description is intended exclusively for use in CPX terminals from Festo for installation in amachine or automated system.

In combination with a CPX terminal, the bus node is used forcommunication as a participant in networks with the protocols EtherNet/IP or Modbus�TCP.

The CPX terminal may only be used as follows:

– as intended in industrial environments; outside of industrial environments, e.g. in commercial and mixed-residential areas, actions to suppress radio interference mayhave to be taken

– in its original state without unauthorised modifications;only the conversions or modifications described in thedocumentation supplied with the product are permitted.

– in perfect technical condition

– only in combination with approved components

� Observe the specified limit values.

� Take into consideration the applicable regulations for thedestination as well as directives and standards, regulations of the inspection organisations, insurance companies and national regulations.


IXFesto CPX-FB36-EN en 1611a English

Safety instructions

� Before assembly or installation work, switch off the powersupply, switch off the compressed air supply, exhaust anypneumatic components.

� For the electrical power supply, only use PELV circuits inaccordance with IEC 60204-1/EN 60204-1.

� Note the information on installation and power supply aswell as on potential equalisation (earthing measures) inthe CPX system description (� P.BE-CPX-SYS-…).

� Observe the handling specifications for electrostaticallysensitive devices.

� Seal unused connections with cover caps to achieve therequired degree of protection.

� Use connection technology with the required degree ofprotection.

� Observe the specifications in the CPX system description,in the descriptions of the valve terminal used as well as inthe assembly instructions of the individual components.

� Observe the instructions for correctly mounting the CPXterminal.

� Place only a completely mounted and wired CPX terminalinto operation.

� Only switch on the compressed air and load voltage if thesystem has been professionally installed, configured andparameterised.

� Make sure that nobody enters the positioning range ofthe actuators.

Switching off the compressed air or load voltage is not a suitable locking mechanism. Unintentional movement of actuators may occur in the event of a malfunction.


X Festo CPX-FB36-EN en 1611a English

Qualification of specialized personnel (target group)

The product must only be commissioned by trained experts incontrol and automation technology who are familiar with:

– mounting, installation, operation and diagnostics of control systems, networks and fieldbus systems

– the applicable regulations for accident prevention andoccupational safety

– the documentation for the product.

Service

Consult your local Festo repair service if you have any technical problems.


XIFesto CPX-FB36-EN en 1611a English

Notes regarding this description

This description contains specific information on the installation, configuration, parameterisation, commissioning, programming and diagnostics with the CPX-FB36 bus node forEtherNet/IP and Modbus® TCP.

An overview of the structure of user documentation for theCPX terminal can be found in the CPX system description(� P.BE.CPX-SYS-…).

Additional information regarding EtherNet/IP can be foundhere:

� www.odva.org

Additional information regarding Modbus® TCP can be foundhere:

� www.modbus.org

The bus node has been certified by the Open Device VendorAssociation (ODVA):

General basic information about the mode of operation, mounting, installation and commissioning of CPX terminals can befound in the CPX system description (� P.BE-CPX-SYS-…).

Information about additional CPX modules can be found inthe description for the respective module.


XII Festo CPX-FB36-EN en 1611a English

Important user information

Danger categories

This description includes instructions on the possible dangersthat can occur if the product is used incorrectly. These dangerwarnings are marked with a signal word (warning, caution,etc.), placed on a grey background and additionally markedwith a pictogram. A distinction is made between the followingdanger warnings:

Warning... means that non-observance can result in serious personal injury or damage to property.

Caution... means that injury to people and damage to property canoccur if this warning is not observed.

Note... means that damage to property can occur if this warningis not observed.

In addition, the following pictogram marks passages in thetext that describe activities involving electrostatic sensitivedevices:

Electrostatically sensitive devices: Incorrect handling cancause damage to devices.


XIIIFesto CPX-FB36-EN en 1611a English

Marking of special information

The following pictograms mark passages in the text that contain special information.

Pictograms

Information:Recommendations, tips and references to other informationsources.

Accessories:Information about necessary or useful accessories for theproduct.

Environment:Information on the environmentally friendly use of theproduct.

Text designations

� Bullet points denote activities that can be carried out inany order.

1. Numerals label activities that must be carried out in thesequence specified.

– Arrowheads indicate general lists.


XIV Festo CPX-FB36-EN en 1611a English

The following product-specific terms and abbreviations areused in this description:

Term/abbreviation Significance

160d Decimal numbers are marked in part by a low-set “d”.

A0h Hexadecimal numbers are marked by a low-set “h”.

AO Analogue output

AI Analogue input

BOOTP Dynamic protocol for automatic assignment of IP addresses (Boot protocol, predecessor of DHCP).

Bus node Provides the connection to specific fieldbuses. It transmits control signalsto the connected modules and monitors their ability to function.

CEC CoDeSys Controller, e.g. CPX-CEC, usable for control, configuration andcommissioning of CPX terminals.

CoDeSys Controller Development System

CP Compact Performance

CP module Collective term for the various modules which can be integrated into the CPsystem (decentralised installation system).

CPX-CP interface Interface for connecting decentrally arranged CP modules to a CPX terminal.

CPX-FMT Festo Maintenance Tool for configuration and parameterisation of CPXterminals.

CPX-MMI Operator unit for commissioning and service purposes.

CPX modules Collective term for electric modules which can be incorporated into a CPXterminal: bus nodes, I/O modules and function modules (technology modules).CPX modules provide, among other things, electrical inputs and outputs forconnecting sensors and actuators.CPX modules form the electrical side of the CPX terminal.

Tab. 0/1: CPX-specific terms and abbreviations - part 1


XVFesto CPX-FB36-EN en 1611a English


CPX terminal Complete system consisting of various CPX modules with or withoutpneumatics modules.

DHCP Dynamic protocol for automatic assignment of IP addresses (DynamicHost Configuration Protocol).

DI Digital input

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

DO Digital output

EtherNet/IP Communication protocol for connecting various devices in a network.

FEC Control block, e.g. CPX-FEC, usable as:– stand-alone system controller (PLC, Stand Alone operating mode)– system controller (PLC, Remote Controller operating mode)– fieldbus slave (Remote I/O operating mode)

Function module Collective term for modules with additional functions, e.g. CPX-CP interface, control block (CPX-FEC) and CoDeSys controller (CPX-CEC); function modules are also known as technology modules.

I Digital input

I/O diagnostics interface Network-independent diagnostic interface at I/O level, which enablesaccess to the internal data of the CPX terminal.

I/O modules Collective term for the CPX modules that provide digital or analogueinputs and/or outputs.

I/O signal Input/output signal of an I/O module; also referred to as a processsignal.

I/Os Analogue or digital inputs and outputs.

Modbus�TCP Communication protocol via TCP/IP in automation technology.

O Digital output



XVI Festo CPX-FB36-EN en 1611a English


Pneumatic interface Interface between CPX modules and pneumatic modules within a CPXterminal.The pneumatic interface counts functionally as part of the electricalside of the CPX terminal.

Pneumatic modules Collective term for the pneumatics modules which can be integratedinto a CPX terminal.They provide outputs (working ports) for connecting actuators, e.g.cylinders. They form the pneumatic side of the CPX terminal.

Status bits Internal inputs that supply coded common diagnostic messages

Technology module � Function module



XVIIFesto CPX-FB36-EN en 1611a English

Data type Size Range of values Description

ARRAY —1) — Structure with identicaldata types

BOOL 1 bit 0 “false” and 1 “true” Logical data type

BYTE 8 bit 00h … FFh Bit field

DWORD 32 bit 00000000h … FFFFFFFFh Bit field

DINT 32 bit –2.147.483.648 …2.147.483.647

Signed Double Integer

INT 16 bit –32,768 … 32,767 Signed Integer

Padded EPATH Max. 12 bytes Logical segments of apath specification

SINT 8 bit –128 … 127 Signed Short Integer

STRING 8 bit/character — String

SHORT_STRING 8 bit/character +8 bit length specification

— String with max. 255 characters

STRUCT —1) — Structure of any datatypes

UDINT 32 bit 0 … 4,294,967,296 Unsigned Double Integer

UINT 16 bit 0 … 65,536 Unsigned integer

USINT 8 bit 0 … 256 Unsigned Short Integer

WORD 16 bit 0000h … FFFFh Bit field

1) Dependent on the data types used

Tab. 0/4: Data types used


XVIII Festo CPX-FB36-EN en 1611a English

Installation

1-1Festo CPX-FB36-EN en 1611a English

Chapter 1

Installation

1. Installation

1-2 Festo CPX-FB36-EN en 1611a English

Contents

1. Installation 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 General instructions for installation 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.1 Connection and display components 1-4. . . . . . . . . . . . . . . . . . . . . . . .

1.1.2 Dismantling and mounting 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Settings of the DIL switches 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.1 Removing and attaching cover 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.2 Arrangement of the DIL switches 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.3 Setting the DIL switches 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.4 Setting the operating mode and network protocol 1-8. . . . . . . . . . . . .

1.2.5 Setting diagnostic mode or data field size 1-9. . . . . . . . . . . . . . . . . . . .

1.2.6 Setting IP addressing 1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Connecting to the network 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.1 General instructions 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.2 Overview of connection technology and network plug connectors 1-13

1.3.3 Cable specification 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.4 Network connections 1-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.5 Setting the IP addressing 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.6 Extended network settings 1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Ensuring the degree of protection 1-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 Power supply of the CPX terminal 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Installation


1.1 General instructions for installation

WarningUncontrolled movements of the actuators and loosetubing, undefined switching states of the electronic components

Injury caused by moving parts, damage to machine and tosystem

Before mounting and installation work:

� Switch off the power supplies

� Switch off the compressed air supply

� Exhaust any pneumatic components.

NoteElectrostatically sensitive devices

� Do not touch any components.

� Observe the handling specifications for electrostaticallysensitive devices.

NoteEnsuring the required degree of protection

� Use cover caps to seal unused connections(� 1.4 Ensuring the degree of protection).

Information about mounting of the CPX terminal can be foundin the CPX system description (� P.BE-CPX-SYS-...).

1. Installation


1.1.1 Connection and display components

1 Network-specificand CPX-specificLED indicators

2 Network connections [X1], [X2]

3 DIL switches

4 Service interface

1

2

3

4

1) 2× socket, M12, D-coded, 4-pin2) Socket, M12, A-coded, 5-pin; for the control device CPX-MMI or Festo Maintenance Tool CPX-FMT

Fig. 1/1: Connection and display components

1.1.2 Dismantling and mounting

The bus node is installed in an interlinking block of the CPXterminal (� Fig. 1/2).

1 Screws

2 Interlinking block

3 Bus node CPX-FB36

3 1

2

1

Fig. 1/2: Dismantling/mounting

1. Installation


Dismantling the bus node

1. Unscrew the screws.

2. Pull the bus node without tilting out of the interlinkingblock.

Mounting the bus node

NoteMaterial damage due to incorrect mounting

� Select screws that are suitable for the material of theinterlinking block:

� plastic: thread-cutting tapping screws

� metal: screws with metric thread.

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

2. Push the bus node carefully and without tilting into theinterlinking block up to the stop.

3. Turn the screws into the existing thread.

4. Tighten the screws in diagonally opposite sequence.Tightening torque:�1 �Nm ± 10 %.

1. Installation


1.2 Settings of the DIL switches

The following settings can be made through the DIL switches:

– Operating mode and network protocol

– Diagnostic mode or data field size

– IP addressing

The settings of the DIL switches become effective only afterthe power supply is switched on.

1.2.1 Removing and attaching cover

To set the DIL switches at the bus node, the cover must beremoved.

Removing the DIL switch cover

1. Switch off power supply.

2. Unscrew the screws.

3. Remove the DIL switch cover.

Attaching the DIL switch cover

1. Put the DIL switch cover in place. Make sure that the sealis seated correctly.

2. Tighten the screws. Tightening torque: max. 0.4 Nm.

1. Installation


1.2.2 Arrangement of the DIL switches

1 DIL switch 1: operating modeand networkprotocol

2 DIL switch 2 diagnostic modeor data fieldsize1)

3 DIL switch 3:IP addressing

1 2

3

1) Depending on the set operating mode

Fig. 1/3: DIL switches

1.2.3 Setting the DIL switches

Procedure

1. Switch off power supply.

2. Remove the DIL switch cover (� 1.2.1).

3. Make the settings for the DIL switches (� 1.2.4 … 1.2.6).

4. Re-attach the DIL switch cover (� 1.2.1).

1. Installation


1.2.4 Setting the operating mode and network protocol

DIL switch1.1 Operating mode

DIL 1.1: OFF(Factory setting)

Remote I/OAll functions of the CPX terminal are controlled directly by thehigher-order controller (PLC). A control block integrated intothe CPX terminal (e.g. CPX-CEC or CPX-FEC) works as a passivefunction module without controller.

DIL 1.1: ON Remote controllerA control block integrated into the CPX terminal (e.g. CPX-CEC orCPX-FEC) takes over I/O control. This operating mode is onlyuseful if a control block is integrated into the CPX terminal.

Tab. 1/1: Setting the operating mode

DIL switch1.2 Network protocol

DIL 1.2: OFF(Factory setting)

EtherNet/IPThe CPX terminal uses the EtherNet/IP network protocol.

DIL 1.2: ON Modbus®TCPThe CPX terminal uses the Modbus® TCP network protocol.

Tab. 1/2: Setting the network protocol

1. Installation


1.2.5 Setting diagnostic mode or data field size

The function of DIL switch 2 is dependent on the set operating mode of the CPX terminal (� Tab. 1/1).

DIL switch2 Diagnostics mode(Remote I/O)1)

Data field size(Remote Controller)2)

2.1: OFF2.2: OFF(Factory setting)

I/O diagnostics interface andstatus bits switched off

8 byte I/8 byte O for communication of the bus node witha control block (e.g. B. CPX-FEC)

2.1: ON2.2: OFF

I/O diagnostics interface isswitched on

32 byte I/32 byte O for communication of the bus nodewith a control block(e.g. B. CPX-FEC)3)

2.1: OFF2.2: ON

Status bits switched on 16 byte I/16 byte O for communication of the bus nodewith a control block(e.g. B. CPX-FEC)

2.1: ON2.2: ON

Reserved 64 byte I/64 byte O for communication of the bus nodewith a control block(e.g. B. CPX-FEC)4)

1) Setting of the diagnostic mode is available only in the remote I/O operating mode.2) Setting of the data field size is available only in the remote controller operating mode.3) From Revision 124) From Revision 13

Tab. 1/3: Setting diagnostic mode or data field size

During subsequent activation of the diagnostics mode (statusbits or I/O diagnostics interface), the CPX-internal I/O illustration or address allocation can be shifted. The system controller carries out this adjustment automatically. Manual manipulation, e.g. a reconfiguration of the CPX terminal or manualadaptation of the hardware and network configuration, arenot required.

1. Installation


1.2.6 Setting IP addressing

DIL switch3 IP addressing

12

34

56

78 DIL 3.8:

DIL 3.7:DIL 3.6:DIL 3.5:DIL 3.4:DIL 3.3:DIL 3.2:DIL 3.1:

27 =26 =25 =24 =23 =22 =21 =20 =

1286432168421

The type of addressing or the host ID of the IP address of thebus node is set via DIL switch elements 3.1 ... 3.8.

Possible settings:0 = Dynamic addressing via DHCP/BOOTP1 … 254 = Permissible address range255 = Reset all IP parameters to factory setting

Factory setting: 0

Tab. 1/4: Setting IP addressing

Dynamic addressing is set via DHCP/BOOTP by default. If all of the switch elements of DIL switch3 are set to ON whenthe bus node is switched on, all IP parameters will be reset tothe factory setting.

Example – Setting IP address of the bus node

12

34

56

78 DIL 3.8:

DIL 3.7:DIL 3.6:DIL 3.5:DIL 3.4:DIL 3.3:DIL 3.2:DIL 3.1:

OFFOffONOffOffONONOff

25 = 32

22 = 421 = 2

Example:21 + 22 + 25 = 2 + 4 + 32 = 38 (Host-ID)

Set IP address: 192.168.1.038

Tab. 1/5: Example – IP addressing

1. Installation


1.3 Connecting to the network

1.3.1 General instructions

NoteUnauthorised access to the device can cause damage ormalfunctions.

When connecting the device to a network:

� Protect the network from unauthorised access.

Measures to protect the network include:

� firewall

� “Intrusion Prevention System” (IPS)

� network segmentation

� virtual LAN (VLAN)

� “Virtual Private Network” (VPN)

� security at physical access level (“Port Security”).

For further notes, please refer to the guidelines and standards for security in information technology, e.g. IEC 62443,ISO/IEC 27001.

An access password protects only against accidentalchanges.

NoteAssemblies with Ethernet interfaces should only be operated in networks if all connected network components aresupplied by PELV circuits or integrated circuits with equivalent protection.

1. Installation


Installation guidelines

Installation guidelines can be sourced from the ODVA userorganization (� www.odva.org).

Use of switches and routers

The switch integrated in the bus node permits division of thenetwork into several segments.

With use of additional switches and routers, the network canbe divided into additional segments. Thus, it is possible tostructure the network and realise a greater network expansion.

Independent of the network structure, the expansion of anetwork segment must not exceed certain connectionlengths.

– Copper connecting cable:(Ethernet twisted pair cable, 22 AWG): max. 100 m between network participants

Switches and routers for Industrial EtherCat are available inthe market from various companies and in a variety of components in IP20, IP65 or IP67.

– Unmanaged Switches: For small networks with a low network load or minimalrequirements for determinism

– Managed Switches: For comprehensive networks with diagnostics and monitoring functions

1. Installation


1.3.2 Overview of connection technology and network plug connectors

NoteFaulty installation and high transmission rates may causedata transmission errors as a result of signal reflectionsand attenuations.

� Observe cable specification (� Tab. 1/7).

Transmission errors can be caused by:

� faulty screened connection

� branches

� transmission over distances which are too long

� unsuitable cables.

Connection technology Network connectors

2 x socket M12, D-coded, 4-pin, in accordancewith IEC 61076-2, SPEEDCON compatible

Plug connector NECU-M-S-D12G4-C2-ET

Tab. 1/6: Overview of connection technology and network plug connectors

RJ45 to M12 converter

For EtherNet/IP installations, it may be necessary to changebetween RJ45- and M12 connection technology.

Example: Connections between devices in a control cabinetand IP65/IP67 devices.

1. Installation


1.3.3 Cable specification

� Use sheathed Industrial Ethernet wiring of categoryCat 5/Cat 5e or higher (� Tab. 1/7).

The CPX bus node supports the “crossover detection” function (Auto-MDI/MDI-X). To connect the bus node to the network or to a PC, this means you can choose between patchcables or crossover cables. The circuitry of the network connections X1 and X2 is adjusted automatically.

Cable specification

Cable type Ethernet twisted pair cable, screened

Transmission class Category Cat� 5/Cat �5e

Cable diameter1) 6 … 8 mm

Wire cross section 0.14 … 0.75�mm2; 22 AWG2)

Connection length3) Maximum 100 m (“end-to-end link”)

1) When using plug NECUMSD12G4C2ET2) Required for maximum connection length between network participants3) Corresponding to specification for EtherNet/IP networks, based on ISO/IEC 11801, ANSI/TIA/EIA-568

(� 1.3.1 General instructions)

Tab. 1/7: Cable specification

NoteWhen mounting the CPX terminal on a moving part of amachine:

� Use network wiring with tension relief.

� Observe corresponding stipulations ofIEC 60204/EN 60204.

1. Installation


1.3.4 Network connections

There are two 4-pin, D-coded M12 sockets on the bus nodefor the network connection. The sockets are compatible withSPEEDCON plugs.Both connections have “Auto-Negotiation” and “Crossover”detection (factory setting).

When crossover detection is activated, the bus node automatically exchanges the transmitted and received data.If crossover detection is deactivated, assignment of the pinsfor transmitted and received data at the XP2 connection iscrossed. As a result, several bus nodes in a row can each beconnected with a patch cable.

Socket1) Pin Connection�[X1]2) Connection�[X2]2)

M12, 4-pin Signal Explanation Signal Explanation

1234Housing

TD+RD+TD–RD–Shield

Transmitted data +Received data +Transmitted data –Received data –Functional earth

RD+TD+RD–TD–Shield

Received data +Transmitted data +Received data –Transmitted data –Functional earth

1) Functional earth is accomplished via the housing2) Pin activation with deactivated crossover detection

Tab. 1/8: Pin allocation of the network connections [X1] and [X2]

If the QuickConnect function has been activated, the crossover detection function is not available. Further notes on wiring with deactivated crossover detectioncan be found in chapter �2.1.2.

1. Installation


Connection with plug connector by Festo

The CPX terminal is connected to the network with plugsNECU-M-S-D12G4-C2-ET. The plugs are designed for network lines with cable diameters of 6 ... 8 mm.

To comply with degree of protection IP65/IP67:

� Use Festo plugs.

� Use cover caps to seal unused connections(� 1.4 Ensuring the degree of protection).

1.3.5 Setting the IP addressing

Alternatively the IP address for the bus node can be set via:

– Dynamic addressing via DHCP/BOOTP (factory setting)

– Saved addressing

– Static addressing via DIL switches

NoteIf changes are made to the network settings through theDIL switches, the “Modify” LED (M) flashes yellow.

� Restart the bus node so that the revised network settings can be taken over.

1. Installation


Dynamic addressing via DHCP/BOOTP

� Make sure there is a DHCP/BOOTP server in the network.

To set the dynamic addressing:

1. Switch all switch elements of the DIL switch 3 into the OFFposition (� Tab. 1/4).

2. Alternatively, activate dynamic addressing via DHCP/BOOTP using:

– Operator unit (CPX-MMI)

– Festo Maintenance Tool (CPX-FMT) software

– “BOOTP-DHCP Server” software from Rockwell Automation

Saved network settings

The bus node offers the option of saving network settings in anon-volatile memory unit in the bus node. DHCP/BOOTP isthereby deactivated.

1. Switch all switch elements of the DIL switch 3 into the OFFposition (� Tab. 1/4).

2. Alternatively change the network settings via:

– Operator unit CPX-MMI

– “Festo Maintenance Tool” (CPX-FMT) program

– “BOOTP-DHCP Server” program from “Rockwell Automation”

Use this setting to activate the storage of network settings ina non-volatile memory of the bus node.

1. Installation


Addressing via DIL switches

When addressing via DIL switches, the bus node obtains afixed IP address. This setting is recommended for test purposes during commissioning or for small networks.

The IP address of the bus node consists of 4 octets:

– Octets 1 … 3: stored in the bus node

– Octet 4: setting via DIL switch�3

� Set a binary number between 1 and 254 over the DILswitch elements 3.1 … 3.8.

This number is then used as the 4th octet of the IP address when the bus node is switched on.

Example with IP address:192.168.001.005

Example with IP address:192.168.001.038

12

34

56

78 20 + 22 =

1 + 4 =5

12

34

56

78 21 + 22 + 25 =

2 + 4 + 32 =38

Tab. 1/9: Examples of fixed values for the 4th octet of theIP address (binary coded)

If all of the switch elements of DIL switch3 are set to ON whenthe bus node is switched on, all network parameters will bereset to the factory setting.

1. Installation


Factory settings of the CPX-FB36

IP address – octet 1 … 3 192.168.1

IP address – octet 4 01)

Network mask 255.255.255.0

Gateway 0.0.0.0

1) Dynamic addressing via DHCP/BOOTP

Tab. 1/10: Factory settings

� Alternatively, change the first 3 octets of the IP address with:

– Operator unit CPX-MMI

– Festo Maintenance Tool CPX-FMT

– Festo Field Device Tool FFT

– Access via EtherNet/IP objects (� C.1)

The network mask and gateway are set by using the corresponding CPX parameters.

1. Installation


1.3.6 Extended network settings

The following settings for the network connection can bemade through the Ethernet link object 0xF6 (246d) (��C.2.4).

In the factory setting, the bus node automatically detects thebaud rate and duplex mode.

Baud rate

Setting via attribute 6 (Forced Interface Speed) of the Ethernet link object:

– 10 Mbit/s

– 100 Mbit/s

Duplex mode

Setting via attribute 6 (control bits, bit 1) of the Ethernet linkobject:

– Half duplex

– Full duplex

1. Installation


1.4 Ensuring the degree of protection

� Use connection technology with the required degree ofprotection (� www.festo.com/catalogue, examples inTab. 1/11).

� Use cover caps to seal unused connections.

Compressed air Connection technology Cover cap

Network connection (M12) Plug connector NECU-M-S-D12G4-C2-ET ISK-M12

Service interface (M12) Connecting cable KV-M12-M12-...1) ISK-M12

1) Connecting cable for the operator unit (CPX-MMI)

Tab. 1/11: Connection technology and cover caps for degree of protection IP65/IP67(examples)

1. Installation


1.5 Power supply of the CPX terminal

CPX terminals are supplied with operating and load voltagethrough interlinking blocks or end plates.

WarningElectric voltage

Injury caused by electric shock, damage to machine and tosystem

� For the electrical power supply, use only PELV circuits inaccordance with IEC/EN�60204-1 (Protective Extra-LowVoltage, PELV).

� Observe the general requirements in accordance withIEC/EN�60204-1 for PELV circuits.

� Use only voltage sources that ensure a reliable electricseparation from the mains network in accordance withIEC/EN�60204-1.

� Always connect all of the power circuits for operatingand load voltage supplies UEL/SEN and UVAL/OUT.

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

Observe the information on power supply (� electrical connection) as well as on the earthing measures to be carried out(� potential equalisation) contained in the CPX system description.

Preparing for commissioning


Chapter 2

Preparing for commissioning

2. Preparing for commissioning


Contents

2. Preparing for commissioning 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 EtherNet/IP protocol 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.1 “Multicast” telegram 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.2 “QuickConnect” 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.3 “Device Level Ring” protocol (DLR) 2-8. . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Modbus® TCP protocol 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Notes on commissioning of the CPX-FB36 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Requirements for commissioning 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Switching on the power supply 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.3 Normal operating status 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 Participants in the network 2-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.1 Participant properties (EDS file) 2-16. . . . . . . . . . . . . . . . . . . . . . . . . . . .



2.1 EtherNet/IP protocol

EtherNet/IP is an industrial Ethernet protocol, which is predominantly used in automation technology.

The EtherNet/IP protocol is activated with DIL switch 1.2 inthe OFF position (� Tab. 1/2).The bus node is then identified with the designation “FB36 - EtherNet IP Remote-IO”.

After switching the protocol, the following unmodified parameters are available:

– IP address

– Diagnostics mode

– System parameters

The DIL switch function remains unchanged.

Retentive bus-specific parameters are only active if the relevant protocol is selected (� section 1.2.4).

Parameterisation examples can be found in the appendix(� C.5).

2.1.1 “Multicast” telegram

EtherNet/IP uses “IP Multicast” telegrams as standard fortransferring process data. The advantage of “Multicast” compared to “Unicast” is that a telegram can be received by multiple participants.

Simple switches, however, cannot distinguish to which participant a “Multicast” telegram is to be transferred. Therefore,these switches send the “Multicast” telegrams to all devicesin the network.

This results in an EtherNet/IP participant receiving numerousunnecessary telegrams, which must then be discarded from



the device. This can reduce the response times of the participants. The demand on the network bandwidth increases.

This does not pose a problem for smaller networks; the performance for larger networks, however, can be improved withthe following functions and/or protocols.

– Use of switches with “IGMP snooping”

– Segmentation of the network

Switches with “IGMP snooping”

By using an IGMP (Internet Group Management Protocol), theswitches are able to decide to which devices the various Multicast telegrams are transferred. As a result, unnecessarydata traffic is avoided through Multicast.

� Activate this function in all switches/routers used.

� Configure at least one switch so that cyclical “IGMP queries” are sent. The “IGMP snooping” function cannot workproperly without these “IGMP queries”.

Segmentation of the network

� Split the machine into smaller network segments. This canbe realised without changing the network cabling, forexample, by using VLANs.



2.1.2 “QuickConnect”

The EtherNet/IP “QuickConnect” function enables a quickerinitialisation of the CPX terminal and a fast connection set-upto the EtherNet/IP master.

“QuickConnect” is commonly used for applications with a toolchange, for which the downtime should be minimised by thedisconnection and connection of devices.

Note“QuickConnect” only works if this function is supported byall participating devices.

� Make sure that intermediate switches and routers inyour network support this function.

The “QuickConnect” function in the bus node is in a deactivated state when delivered.

Using “QuickConnect”:

1. Activate “QuickConnect” via attribute 12 of the TCP/IPinterface object (� C.2.3). This automatically deactivates“Crossover” detection in the bus node.

2. Restart the bus node so that the revised network settingscan be taken over.

3. Use the same settings for baud rate and duplex mode atthe counterpart station (e.g. switch) and at the PLC as inthe bus node.

For fast connection set-up:

– 100 �MBit/s

– Full duplex

4. Activate “QuickConnect” in the PLC or the control program.



Simplified configuration of “QuickConnect” at the bus nodeCPX-FB36:

� Set the CPX parameter “IP configuration” to “with savedparameters and QuickConnect”.

With activation of “QuickConnect”, the “Crossover” detectionis deactivated for both network connections. As a result, connection X1 runs in the MDI-mode and connection X2 runs inthe MDI-X mode.

This allows a line topology to be constructed with patchcables:

MDI MDIX MDI MDIX MDI MDIXX1 X2 X1 X2 X1 X2TP1 TP2

1 2 3

1 PLC or switch

2 Patch cable

3 I/O device (e.g. B.�CPX-FB36)

Fig. 2/1: QuickConnect line topology with patch cables

The bus node corresponds to a “Class A device” in accordance with the EtherNet/IP specification. When switched on,the bus node requires less than 350 ms to accept a TCP connection. Due to the rapid establishment of the TCP connection, the detection of already used IP addresses (ACD, “IP�Address Conflict Detection”) is not executed completely.Multiple assigned IP addresses are only detected late. As aresult, the network can be disturbed.

� If IP addresses are correctly assigned in the network, deactivate the ACD via attribute 10 of the TCP/IP interfaceobject (� C.2.3).



“QuickConnect” is available for the following modules:

CPX modules Order code

Bus node CPX-FB36

Digital 4-off input module CPX-4DE


Digital 8-off input module with channel diagnostics

CPX-8DE-D

Digital 8-off input module, n-switching

CPX-8NDE


Digital 16-off input module with channel diagnostics

CPX-M-16DE-D

Digital 16-off input module, with terminal strip

CPXL16DE16KL3POL

Digital 4-off output module CPX-4DA

Digital 8-off output module CPX-8DA

Digital 8-off output module, high-current variant

CPX-8DA-H

Digital 8-off input/output module CPX-8DE-8DA

Digital 16-off input/output module, with terminal strip

CPXL8DE8DA16KL3POL

Analogue 2-off input module (voltage/current)

CPX2AEUI

Analogue 2-off output module (voltage/current)

CPX2AAUI

Analogue 4-off input module (current) CPX4AEI

Tab. 2/1: CPX modules, which support “QuickConnect”



“QuickConnect” is available for the following pneumatic modules and pneumatic interfaces:

Pneumatic modules Type

MPA1 pneumatic module VMPA1-FB-EM...-8

MPA2 pneumatic module VMPA2-FB-EM...-4

MPA1 pneumatic module with diagnosticfunction

VMPA1-FB-EM...-D2-8

MPA2 pneumatic module with diagnosticfunction

VMPA2-FB-EM...-D2-8

Tab. 2/2: Pneumatic modules that support “QuickConnect”

Pneumatic interfaces Type

for VTSA or VTSAF pneumatics VABA10S6X1

for MPAS valves VMPAFBEPL…

for MPAF valves VMPAFFBEPL...

for MPAL valves VMPALFBEPL...VMPALEPLCPX

Tab. 2/3: Pneumatic interfaces that support “QuickConnect”

2.1.3 “Device Level Ring” protocol (DLR)

The Device Level Ring protocol (DLR) allows multiple devicesto be operated in a ring topology.

Requirements

All DLR devices feature an integrated Ethernet switch with atleast 2 external ports and support the DLR Protocol.



Ring

Supervisor

Ring

Node 1

Ring

Node 2

Ring

Node 3

Ring

Node 4

Fig. 2/2: Device Level Ring topology, example

The availability of the network can be increased through the ringtopology, as there are redundant communication paths betweentwo devices. A cable or communication error between twodevices will therefore not result in communication failure. Onlytwo errors in a ring will lead to a malfunction.

A ring always consists of at least one ring supervisor and anynumber of ring nodes.

� Only use DLR-capable devices in a ring. Otherwise, the time required for automatic elimination ofan error may be adversely affected.

� Operate the bus node as a ring node either in a “beacon-based” or “announce-based” configuration. Operation as a ring supervisor is not possible. This function is normally executed by an EtherNet/IP scanner.

The DLR protocol is configured via the DLR object (class code 47h).



2.2 Modbus® TCP protocol

Modbus® is an open communication protocol based on themaster-slave architecture. It is a standard for communicationvia TCP/IP in automation technology.

The Modbus® TCP protocol is activated with DIL switch 1.2 inthe ON position (� Tab. 1/2).The bus node is then identified with the designation“FB36-MB - Modbus® TCP Remote-IO”.

After switching the protocol, the following unmodified parameters are available:

– IP address

– Diagnostics mode

– System parameters

The DIL switch function remains unchanged.

Retentive bus-specific parameters are only active if the relevant protocol is selected (� section 1.2.4).

The configuration options via Modbus® TCP correspond tothose via EtherNet/IP. Exception: EtherNet/IP objects cannot be accessed via Modbus® TCP.

In order to configure the CPX terminal for Modbus® TCP, theModbus® addresses of the data and of the inputs and outputs of the CPX terminal are required. (� D).

Addressing examples can be found in the appendix (� D.6.1).



2.3 Notes on commissioning of the CPX-FB36

Configuration of the CPX terminal requires an exact procedure, as different configuration specifications are sometimesnecessary for each station in the network, due to the modularstructure.

Detailed instructions and further information can be found inthe documentation or the online help for the controller orcontrol program.

NoteThe bus node CPX-FB36 can be used on all EtherNet/IP orModbus® TCP controllers.

The following section describes the configuration and commissioning procedure using the example of a controllerfrom Allen-Bradley with the help of the “Studio 5000” software from Rockwell Automation.

2.3.1 Requirements for commissioning

– Installation of the bus node is complete.

– The DIL switches of the bus node are set correctly.

– All connecting cables are connected and checked.



2.3.2 Switching on the power supply

WarningUncontrolled movement of the actuators, undefinedswitching statuses.

Injury to people, damage to the machine and system.

Before switching on:

� Make sure that the requirements for commissioning aremet.

� Check settings of the DIL switches.

During operation:

� Leave switch elements of the DIL switches unchangedduring operation.

Note� Observe the switching-on instructions in the controller

manual.

2.3.3 Normal operating status

After the CPX terminal is switched on, the status LEDs(� Fig. 4/1) indicate the operating status and correct function of the bus node as well as of the network communicationdependent on the configuration.

– Bus node not configured (� Tab. 2/4)

– Bus node configured and higher-order controller (PLC) isin stop mode (� Tab. 2/5)

– Bus node configured and higher-order controller (PLC) isin the Run stop mode (� Tab. 2/6)

Information on diagnostics using the LED displays can befound in section 4.2.



Bus node not configured

LED indicator Status and significance

Lights up green

[MS] – Device ready for operation

Lights up green

[PS] – Power supply (Power System, PS) is OK– Operating voltage present

(in the approved range)

Flashes green

[NS] – Network communication present but not configured (operating status “online”), In this case, this is correct, because the busnode is not configured.

Lights up green

[PL] – Load voltage present (in the approved range)1)

Lights up green

[TP1], [TP2] – Device is correctly connected to the bus node– Internal communication between bus node and

device 1 or device 2 is error free– Operating and load voltage present

(in the approved range)1)

1) Display dependent on monitoring and signal from the connecteddevice.

Tab. 2/4: Status LEDs after switch-on – bus node not configured



Bus node configured – PLC in the stop mode


Lights up green

[MS] – Module status (MS) error free

Lights up green



Lights up green

[NS] – Network status (NS) error free (“online” operating status)

– Communication with the network and PLC OK

Lights up green


Lights up green





Tab. 2/5: Status LEDs after switch-on – bus node configured, PLC in the Stop mode



Bus node configured – PLC in the Run mode


Lights up green

[MS] – Module status (MS) error free

Lights up green



Lights up green

[NS] – Network status (NS) error free (“online” operating status)

– Communication with the network and PLC OK

Lights up green


Lights up green





Tab. 2/6: Status LEDs after switch-on – bus node configured, PLC in the Run mode



2.4 Participants in the network

When using the CPX terminal as a new network participant forthe first time, the configuration program is to be informed ofcertain network properties.

These network properties are integrated into the participantproperties.

2.4.1 Participant properties (EDS file)

The participant properties are predominantly managed by theconfiguration program in a list or library, e.g. EDS file (Electronic Data Sheet).

The following options are available for expanding an EDS library:

– Install EDS files

– Enter participant properties manually

– Import participant properties

As soon as the CPX terminal has been registered as a potential network participant, it can be added to a network.

Commissioning


Chapter 3

Commissioning

3. Commissioning


Contents

3. Commissioning 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Configuration 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.1 Configuration with EDS file 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.2 Configuration with “Generic Ethernet Module” 3-11. . . . . . . . . . . . . . . .

3.1.3 Configuration with CPX-FMT 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.4 Configuration in the “Remote Controller” operating mode 3-20. . . . . . .

3.1.5 Setting up a “Listen only” connection 3-21. . . . . . . . . . . . . . . . . . . . . . .

3.2 Parameterisation 3-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.1 Parameterisation during switch-on [system start] 3-23. . . . . . . . . . . . . .

3.2.2 Methods of parameterisation 3-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.3 Parameterisation via configuration data 3-26. . . . . . . . . . . . . . . . . . . . .

3.2.4 Parameterisation with the control device CPX-MMI 3-26. . . . . . . . . . . .

3.2.5 Parameterisation in the PLC user program 3-26. . . . . . . . . . . . . . . . . . .

3.2.6 Parameterisation using CPX-FMT and system start with saved parameters3-27

3.3 Behaviour of the outputs in the “Fail safe mode” or “Idle mode” 3-28. . . . . . . . .

3.4 Web server 3-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Checklist for commissioning a CPX terminal 3-30. . . . . . . . . . . . . . . . . . . . . . . . . .

3.6 Replacing the bus node 3-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3. Commissioning


3.1 Configuration

A CPX terminal with bus node CPX-FB36 can be configuredusing various methods.

Method Description Advantages Disadvantages

Configuration withEDS file (� 3.1.1)

Installation of participant properties for theCPX terminal in the “Studio 5000” configurationprogram.

With the exception ofthe I/O data length, theentire configuration istransferred from the EDSfile.

Not available with allEtherNet/IP masters.Parameterisation issaved locally in the CPXterminal and is lost if theterminal is replaced.1)

Configuration with“Generic EthernetModule”(� 3.1.2)

Creation of a new participant and manual configuration in the “Studio5000” configurationprogram.

Works with all versions All settings must beentered manually.

Configuration withCPX-FMT(� 3.1.3)

Export of the CPX terminal settings by CPX-FMT and import of thesettings to the “Studio5000” configuration program.

Transfer of the existingconfiguration of the participant and parameterisation of the CPX terminal.

Tab. 3/1: Configuration methods

3. Commissioning


3.1.1 Configuration with EDS file

This section describes the configuration of the bus node asparticipant in a controller from Allen-Bradley with the help ofthe “Studio 5000” software (V 26.01.00) from Rockwell Automation using an equipment description file (EDS file) fromFesto.

The fundamental aspects of this description also apply forother control systems.

Obtaining EDS files

� Use one of the following EDS files for the CPX terminalwith CPX-FB36.

File type File name Language Description

EDS cpx_FB36.eds English Provides the communication adapter in the configuration program.

cpx_FB36RC.eds English File with information for the “Remote Controller” operating mode.

ICO cpx_FB36.ico – Icon file for representing the CPX terminal ormode in the configuration program.

Tab. 3/2: Device description files for CPX-FB36

The current device description file is available on the FestoSupport Portal (� www.festo.com/sp).

3. Commissioning


Registering the EDS file

1. Start “Studio 5000” software.

2. Start EDS Wizard: [Tools] , [EDS Hardware Installation Tool]

Fig. 3/1: Starting EDS Wizard

3. In the “Rockwell Automation's EDS Wizard” dialogue,select the option “Register an EDS file(s)” and confirm itwith the “Next >” button.

Fig. 3/2: EDS Wizard – Options

3. Commissioning


4. Select one of the following options:

– “Register a single file”

– “Register a directory of EDS files”

5. Actuate “Browse…” button and select EDS file from thecorresponsing directory.

Fig. 3/3: EDS Wizard with selected EDS file

6. Confirm selection with the “Next >” button.

The procedure for registering the bus node is complete.

3. Commissioning


Integrate participants into the project and configurethem

Configuration of the bus node can only take place if there isno online connection to the controller.

1. Terminate an existing online connection to the higher-order controller: [Communications] , [Go Offline]

2. Open “Select Module Type” dialogue: In the “Controller Organizer” window in the “I/O Configuration” directory, click on “Ethernet” with the right mousebutton and select “New Module” in the context menu.

Fig. 3/4: Context menu for “New Module…”

3. Commissioning


3. In the “Catalogue” tab, select the module with the description “CPX-FB36 Ethernet/IP 2-Port Remote I/O” fromthe table.

Fig. 3/5: Integrating bus node in the project as a participant

4. Confirm selection with the “Create” button.

This opens the dialogue “New Module” for configuration ofthe new participant (� Fig. 3/6).

Fig. 3/6: Configuring a participant

3. Commissioning


5. Enter a name for the bus node.

6. Enter IP address of the bus node.

7. Open the “Module Definition” dialogue and click on the“Change” button.

Add screenshot of the dialogue “Module Definition”

Fig. 3/7: Enter I/O data length

8. Enter I/O data length (number of inputs and outputs) ofthe CPX terminal.

This value can either be calculated or retrieved usingCPXFMT or a web server.

9. Confirm entries with the “OK” button.

10. Close the “Module Definition” dialogue.

The bus node appears as a newly integrated participant in the“Controller Organizer” window in the “I/O Configuration/Ethernet” directory.

3. Commissioning


Changing configuration of the participant



2. Open “Select Module Type” dialogue: In the “Controller Organizer” window in the “I/O Configuration/Ethernet” directory, click on the correspondingmodule with the right mouse button and select “Properties” in the context menu.

Fig. 3/8: Context menu for “Properties”

3. Change configuration of the participant through the inputfields and confirm with the “OK” button.

3. Commissioning


3.1.2 Configuration with “Generic Ethernet Module”

This section describes the manual configuration of the busnode as participant in a a controller from Allen-Bradley withthe help of the “Studio 5000” software (V 26.01.00) fromRockwell Automation.


Integrate participants into the project and configurethem



2. Open “Select Module Type” dialogue: In the “Controller Organizer” window in the “I/O Configuration” directory, click on “Ethernet” with the right mousebutton and select “New Module” in the context menu(� Fig. 3/4).

3. In the “Catalogue” tab, select the module with the description “Generic Ethernet Module” from the table.

Fig. 3/9: Integrating a bus node as a Generic Ethernet Module

3. Commissioning


4. Confirm selection with the “Create” button.

This opens the dialogue “Module Properties” for configuration of the module as participant (� Fig. 3/10).

Fig. 3/10: Configuring a participant

5. Enter a name for the bus node.

6. Select data format (Data - SINT or Data - INT) in the“Comm Format” list field.


8. Enter values for “Assembly Instance” dependent on theselected data format (� Tab. 3/3).

Data format Data – SINT Data – INT

“Input” 101 111

“Output” 100 110

“Configuration” 102 102

Tab. 3/3: Input values for “Assembly Instance”

9. Enter values for “Size” dependent on the selected operating mode (� Tab. 3/4).

3. Commissioning


Operatingmode

Values

Remote I/O “Input” and “output”:Number of assigned inputs and outputs of the CPXterminal:– for data format SINT: in bytes– for data format INT: in wordsThe entry “Size” = 0 for inputs and outputs is notpermissible in the Remote I/O operating mode.

“Configuration”– Number of memory slots occupied by CPX para

metersor– 0 (standard setting)1)

Remote controller

“Input” and “output”:Set data field size (� Tab. 1/3):– for data format SINT: in bytes– for data format INT: in words

“Configuration”– 0 (standard setting)1)

1) “Configuration Assembly” not used

Tab. 3/4: Input values for “Size”

When using a CPX terminal without inputs:

� Activate status bits via DIL switch�2 (� Tab. 1/3).

The following settings then apply for the input data (“Input”):

– for SINT format: “Size” = 2

– for INT format: “Size” = 1

10. Confirm entries with the “OK” button.

11. Close the “Module Properties” dialogue.

The bus node appears as a newly integrated participant in the“Controller Organizer” window in the “I/O Configuration/Ethernet” directory.

3. Commissioning


Using participant properties

� Use the following data in the higher-order controller(� Tab. 3/5).

Characteristic Description

“Vendor Name” Festo Corporation

“Vendor ID” 26 = 1Ah

“Device Type” 12 = 0Ch

“Product code” (dependent on the operating mode)– “Remote�I/O”– “Remote controller”

14026 = 36CAh

14027 = 36CBh

“Major revision” 1

“Input size”/“Output size” Dependent on CPX expansion

“Assembly instance”– “Input”– “Output”– “Configuration”

SINT format101100102

INT format111110102

“Product Name” CPX-FB36 Remote IO

CPX-FB36 Remote controller

Extended EtherNet/IP participant properties

Min. bus cycle time (RPI) “Request Packet Interval” 1 ms

Connections– Total of all connections– “Exclusive owner”– “Input only”– “Listen only”

Max. 32Max. 1Max. 32Max. 311)

1) Only with simultaneous connection “Exclusive Owner” or “Input only”

Tab. 3/5: Participant features

3. Commissioning


Changing configuration of the participant



2. Open “Select Module Type” dialogue: In the “Controller Organizer” window in the “I/O Configuration/Ethernet” directory, click on the correspondingmodule with the right mouse button and select “Properties” in the context menu.

Fig. 3/11: Context menu for “Properties” (Generic)

3. Change configuration of the participant through the inputfields and confirm with the “OK” button.

3. Commissioning


3.1.3 Configuration with CPX-FMT

With the “Festo Maintenance Tool” software (CPX-FMT), it ispossible to export the configuration and complete parameterisation of a CPX terminal to a file and then import the fileinto the controller as a project.

This section describes the transmission of the configuration fileto a controller from Allen-Bradley with the help of the “Studio 5000” software (V 26.01.00) from Rockwell Automation.


Exporting a configuration from CPX-FMT

The Festo Maintenance Tool (CPX-FMT) software is available inthe Festo Support Portal (� www.festo.com/sp).

1. Start CPX-FMT software.

2. Make sure that an Ethernet connection exists betweenCPX-FMT and the CPX terminal.

3. Activate the online function to transfer the current configuration of the bus node to the PC.

4. Change the configuration and parameterisation for theCPX terminal with CPX-FB36, if necessary.

The CPX terminal can also be configured offline. Changes arealso possible after importing the project in the “Studio5000”software.

3. Commissioning


5. Open dialogue for export of the configuration:[File] , [Export] , [RSLogix�(.L5K)].

Fig. 3/12: Exporting a configuration for “Studio�5000”

6. Select and save a directory and name to save the L5K file.

Importing configuration

1. Start “Studio 5000” software.

2. Open saved L5K file:[File] , [Open] and select the saved L5K file.

3. Confirm selection with the “Open” button.

4. Select the directory and name for the file to be imported.

5. Confirm selection with the “Import” button.

The L5K file is imported into a new project (.ACD) as an Ethernet module.

3. Commissioning


Integrating the CPX terminal into an existing project

The CPX terminal configured and parameterised with theFesto Maintenance Tool software appears in the “Studio�5000” software as an Ethernet module.

To integrate this module into an existing project:

1. In the “Controller Organizer” window in the “I/O Configuration” directory, right click on the Ethernet module andselect “Copy” in the context menu.

Fig. 3/13: Copying the Ethernet module

3. Commissioning


2. Open the project in which the imported Ethernet moduleis to be added.

3. In the “Controller Organizer” window in the “I/O Configuration” directory, right click on “Ethernet” and select“Paste” in the context menu.

Fig. 3/14: Inserting an Ethernet module

The project has now take over all required settings of the CPXterminal. This includes, among other things, I/O data lengths,the IP configuration, as well as all module and system parameters.

Configuration and parameterisation are hereby completed.Changes to the parameterisation of the modules and valveterminals used in the CPX terminal are made through the“Studio�5000” software.

3. Commissioning


3.1.4 Configuration in the “Remote Controller” operating mode

When a control block CPX-FEC or CPX-CEC is used in the CPXterminal, the bus node must be used in the Remote Controlleroperating mode.

In principle, the bus node is configured in the same manneras in the Remote I/O operating mode, but with different I/Odata lengths.

The bus node then occupies 8 or 16� input bytes and 8� or16�output bytes, dependent on the setting of the DILswitch 2.2 (� Tab. 1/3). These inputs and outputs are available to the control program of the control block.

To use the Remote Controller operating mode:

1. Set Remote Controller operating mode through the DILswitch�1.1 (� Tab. 1/1).

2. Set the network protocol through the DIL switch 1.2(� Tab. 1/2).

3. Set the required data field size through the DIL switch2.1(� Tab. 1/3).

The bus node is thus configured in the Remote Controlleroperating mode.

3. Commissioning


3.1.5 Setting up a “Listen only” connection

When the participant properties have been configured (e.g.by installation of an EDS file), the following steps are requiredfor configuration.

1. Install CPX terminal and set IP addressing (� 1.3.5).

2. Make connection to the bus node.In the “Studio 5000” software, use the “Generic EthernetDevice” profile for this purpose (� 3.1.2).

3. Open the “Module Properties” dialogue.

4. Select the data format DATA - SINT from the “CommFormat” list field (� Fig. 3/10).

5. Enter the following values in the “Connection Parameters”field:

“ConnectionParameters”

“AssemblyInstance”

“Size”

“Input” 101 Number of inputsset on the busnode

“Output” 1 0

“Configuration” 102 (“Configuration Assembly”)

0

Tab. 3/6: Properties for “Connection parameters”


3. Commissioning


3.2 Parameterisation

WarningUncontrolled movements of the actuators, undefinedswitching statesInjury to people, damage to the machine and system

� During the parameterisation process, make sure thatnobody is within the sphere of influence of moving partsof your system.

The CPX terminal is supplied from the factory with presetparameters. These parameters are saved in the bus node.

These parameters can be used to largely adapt the behaviourof the CPX terminal to the relevant application.

A distinction is made between the following variants:

– System parameters, e.g. setting reaction times, switchingoff error messages

– Module parameters (module- and channel-specific), e.g.diagnostic settings, settings for error handling, settingsfor debounce times of inputs, settings for forcing

– Parameters of the diagnostic memory

A detailed description of the individual parameters as well asbasic principles of application can be found in the CPX systemdescription (� P.BE-CPX-SYS-...).

The module parameters can be found in the descriptions forthe modules, e.g. description of the CPX pneumatic interfacesand CPX I/O modules (� P.BE-CPX-EA-...).

3. Commissioning


3.2.1 Parameterisation during switch-on [system start]

Parameterisation during system start of the CPX terminal isinitially dependent on the setting of the parameter [systemstart]. This parameter establishes whether the default parameters or the parameters saved by the user in the bus nodeare used when switching on the CPX terminal.

The parameterisation is loaded again after every interruptionof the power supply or the network connection. An exchangeof individual CPX modules is therefore possible, for example,without the need for re-parameterisation.

Sequence of parameterisation when the CPX terminal is switched on

System start with standard parameters(“default parameters”)

1. The controller transmits the parameterisation that issaved in the controller to the bus node.

2. The bus node distributes this parameterisation to theindividual modules.

System start with saved parameters

1. The bus node distributes the parameterisation that issaved in the bus node to the individual modules.

The parameterisation saved in the bus node can be overwritten accidentally by the controller.

� Prevent accidental overwriting of the saved parameterisation by changing the “Configuration” connection parameter using the “Studio 5000” software.

3. Commissioning


To change the “Configuration” connection parameter with the“Studio 5000” software:


2. Open “Module Properties” dialogue: Double-click on “Ethernet” in the “Controller Organizer”window in the “I/O Configuration” directory.

1 “Assembly-lnstance” connection parameterfor “Configuration”

1

Fig. 3/15: “Module Properties” dialogue

3. Enter the value “Assembly Instance” = 0 for “Configuration” in the “Connection Parameters” area.

4. Close the “Module Properties” dialogue with the “Finish >>” button.

If the “Modify” (M) LED on the bus node lights up permanently after system start-up, [System start with saved parameters] is set.

3. Commissioning


3.2.2 Methods of parameterisation

Method Description Advantages Disadvantages

Parameterisation viaconfiguration data(Configuration Assembly) (� 3.2.3)

Export of CPX terminalparameterisation byusing CPX-FMT.Import of the settingsin the “Studio 5000”software.

Convenient transfer ofthe complete configuration for a CPX terminal.

–

Parameterisation withthe CPX-MMI operatorunit (� 3.2.4)

Parameterisation viamenu-driven entries.

Convenient parameterisation via the menunavigation (clear text).

Parameterisation ofthe CPX terminal issaved locally in the busnode and is lost whenreplaced.1)

Parameterisation in thePLC user program(� 3.2.5)

Parameterisation viaExplicit Messaging.Parameters are savedin the PLC.

Parameters are reloaded after every restart and are thereforealso retained if thedevice is replaced.

User program required

Parameterisation usingCPX-FMT and systemstart with saved parameters (� 3.2.6)

Parameterisation viamenu-driven entries.Parameters are saveddirectly in the busnode.Start with saved parameters necessary.

Fast, simple parameterisation during commissioning for testingthe parameters.

Parameterisation ofthe CPX terminal issaved locally in the busnode and is lost whenreplaced.1)

1) It is possible to copy the current parameterisation with the help of the CPX-MMI operator unit.

Tab. 3/7: Methods of parameterisation

Further information about parameterisation can be found inthe CPX system description (� P.BE-CPX-SYS-...).

3. Commissioning


NoteThe last parameterisation transferred in the CPX terminal isalways valid.

3.2.3 Parameterisation via configuration data

Parameterisation via configuration data (Configuration Assembly) corresponds to the method for configuration withCPX-FMT and transfer of all parameters to the “Studio 5000”software (� section 3.1.3 Configuration with CPX-FMT).

3.2.4 Parameterisation with the control device CPX-MMI

The operator unit CPX-MMI offers menu-driven access to theparameterisation. It does not require any additional configuration software.

Information about using the operator unit can be found in thecorresponding description.

3.2.5 Parameterisation in the PLC user program

The program-controlled access to parameters is effected viaExplicit Messaging. The addresses of the EtherNet/IP objectmodel that are required for this can be found in the appendix(� C.1 Overview of Ethernet/IP objects).

Further information on programming this data transmissioncan be found in the manual for the controller.

3. Commissioning


3.2.6 Parameterisation using CPX-FMT and system start with saved parameters

Parameterisation corresponds to the method for configuration with CPX-FMT and transfer of all parameters to the “Studio 5000” software (� 3.1.3).

The parameterisation of the CPX terminal is saved directly inthe bus node. To use this parameterisation, the “Systemstart” parameter needs to be set to “Saved parameters”(� section 3.2.1).

3. Commissioning


3.3 Behaviour of the outputs in the “Fail safe mode” or “Idle mode”

“Idle mode” is assumed by the participants after a request bythe master.

The error status (“Fail safe mode”, also referred to as “Faultmode”) defines the status the relevant channel is to assumein the event of fieldbus communication errors.

In this status, the following applies:

– Inputs are transmitted

– Output channels of the participants are no longer updated

In the “Fail safe mode” or “Idle mode”, outputs can assumeone of the following states:

Digital outputs/valves Analogue outputs

Freeze current status Freeze current status

Reset the output Desired analogue value

Setting the output

Tab. 3/8: Possible states in the “Fail safe mode”/“Idle mode”

The status to be assumed for each output channel (output orsolenoid coil) can be determined separately. The standardsetting is “Reset of the output channel”.

Additional information can be found in the CPX system description (� P.BE-CPX-SYS-...).

3. Commissioning


3.4 Web server

A web server is integrated in the bus node CPX-FB36. Theweb server makes available the most important parametersand diagnostic functions.

Fig. 3/16: Web server of the CPX-FB36

Procedure

� In the address bar of the Internet browser, enter the IPaddress of the bus node as follows: http://192.168.1.xxx

3. Commissioning


3.5 Checklist for commissioning a CPX terminal

� Observe the general instructions for commissioning in theCPX system description (� P.BE-CPX-SYS-…).

� Check the DIL switch settings and network configurationbefore use and replacement of the CPX terminal.

� Check the configured address range and test the inputsand outputs, if necessary.

� Check the address assignment of the inputs and outputson the CPX terminal, e.g. with the “Force” function.

� Make sure that the desired parameterisation of the CPXterminal in the start-up phase or after network interruptions is restored by the interface module. This ensures that, if the CPX terminal is replaced, the newterminal will also be operated with the desired parametersettings.

� If necessary, check parameterisation with configurationsoftware (e.g. “Studio 5000”) or an operator unit (e.g.CPX-MMI).

3. Commissioning


3.6 Replacing the bus node

CautionFor CPX terminals with a continuously illuminated or flashing “Modify” LED (M), parameterisation is not automatically created by the higher-level system when the CPX terminal is replaced during servicing.

� Before replacement, note required settings and makethem again after replacement.

When replacing a bus node with the setting [System start withsaved parameters], the CPX terminal is not parameterisedautomatically by the higher-order controller.

The bus node CPX-FB36 is compatible with the bus node CPX-FB32: A bus node CPX-FB32 can be replaced in existing applicationsby a bus node CPX-FB36 (Revision 13 or higher) withoutchanging the configuration of the host system.

With the Festo Maintenance Tool (CPXFMT):

1. Before replacing the bus node, save the parameterisationof the CPX terminal in a CPX-FMT file.

2. After replacing the bus node, transfer the parameterisation to the new bus node. [CPX] , [Download Settings…]

3. Activate all settings to be loaded in the “Download” dialogue.

4. Start the transfer to the bus node by pressing “OK”.

3. Commissioning


Diagnostics


Chapter 4

Diagnostics

4. Diagnostics


Contents

4. Diagnostics 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Diagnostics options 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Diagnostics via LED displays 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 CPX-specific LED displays 4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2 Network-specific LED indicators 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 Diagnostics via status bits 4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4 Diagnostics via the I/O diagnostics interface 4-13. . . . . . . . . . . . . . . . . . . . . . . . .

4.5 Diagnostics via EtherNet/IP 4-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.6 Diagnostics via Modbus®�TCP 4-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7 Error handling (“Fail safe”) 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4. Diagnostics


4.1 Diagnostics options

Diagnosticsoptions

Brief description Advantages Detailedinformation

LED indicator Display of configuration,hardware, network errors,etc. directly at the bus node.

Fast “on-the-spot” errordetection

� 4.2

Status bits Internal inputs that supply coded common diagnostic messages.

Fast access to error messages, independent of theinterface and higher-ordercontroller.

��4.3 and CPXsystem descriptionP.BE-CPX-SYS-…

I/O diagnosticsinterface

Bus-independent diagnosticinterface at I/O level, whichenables access to the internaldata of the CPX terminal(16 inputs and 16 outputs)

Detailed error detectionand further processing ofdiagnostic data, e.g.through a PLC user program.

� �4.4 and CPXsystem descriptionP.BE-CPX-SYS-…

Operator unitCPX-MMI

Menu-driven display of diagnostic information on theoperator unit.

Fast “on-site” error detection without programming,in plain text.

� Description forthe operator unitP.BE-CPX-MMI-1-…

Diagnostics viaEtherNet/IP

Access to all system data ofthe CPX terminal over the network.

Detailed error detection aswell as access to the diagnostic memory in the online mode of the controllersoftware and in the PLCuser program.

� C.1

Tab. 4/1: Diagnostics options

The available diagnostic information is dependent on the DILswitch settings on the bus node and the parameterisation ofthe CPX terminal.

4. Diagnostics


4.2 Diagnostics via LED displays

The following LED displays for diagnosis of errors are available on the bus node:

PS

PM

SF

MS

NS

M

1

2PS

PM

SF

MS

NS

TP1

M

TP2

TP2

TP1

1 CPX-specific LED indicators: – PS: Power System (green)– PL: Power Load (green)– SF: System Failure (red)– M: Modify (yellow)

2 Network-specific LED indicators: – MS: Module Status (green, red)– NS: Network Status (green, red)– TP1: Link/Traffic 1 (green)– TP2: Link/Traffic 2 (green)

Fig. 4/1: LED indicators

4. Diagnostics


In the following sections, the statuses of the LED displays arerepresented as follows:

lit; flashing; off;

Normal operating status

During normal operation, the following LEDs light up green.The SF LED does not illuminate. The M-LED only illuminateswith the setting “System start with stored parameterisationand stored CPX expansion” (� function number 4402).

LED indicator operatingstatus

PS

PM

SF

MS

NS

MTP2

TP1

These LEDs light upgreen:– MS– NS– TP1/21)

– PS– PLThe red LED (SF) doesnot illuminate.The yellow LED (M) islit.2)

Normal

1) Steady light: Ready for data transmission Flashing: Data transmission ongoing

2) Lights up only if system start is activated with saved parameterisation and saved CPX expansion.

Tab. 4/2: Normal operating status

4. Diagnostics


4.2.1 CPX-specific LED displays

PS (Power System) – operating voltage supply

LED (green) Sequence Significance Error handling

lights up

ON

Off

No error. Operating voltageapplied.

–

flashes

ON

OFF

Operating voltage outside thetolerance range.

� Eliminate undervoltage.

ON

OFF

Internal fuse has responded. 1. Eliminate short circuit/overload.

2. Depending on the parameterisation:� The power supply will be

switched on again automatically after the short circuithas been eliminated (factory setting).

� Switch the power supply offand then on again.

Off

ON

OFF

Operating voltage not present. � Check connection of the operating voltage.

Tab. 4/3: LED indicator PS (power supply)

PL (power load) – load voltage supply


lights up

ON

Off

No error. Load voltage present. –

flashes

ON

OFF

Load voltage outside the tolerance range.

� Eliminate undervoltage.

Tab. 4/4: LED indicator PL (load voltage supply)

4. Diagnostics


SF (System Failure) – system failure

LED (red) Sequence1) Significance Error handling

flashes 1x

ON

Off

simple error/information(Error class 1)

� CPX system description P.BE-CPX-SYS-…

flashes 2x

ON

Off

Error (error class 2)

flashes 3x

ON

Off

serious error(Error class 3)

Off

ON

OFF

No error. –

1) The SF LED indicator flashes depending on the error class.Error class 1 (simple error): 1x flash, pauseError class 2 (error) 2x flash, pauseError class 3 (serious error): 3x flash, pause

Tab. 4/5: LED indicator SF (system error)

4. Diagnostics


M (modify) – parameterisation modified or Forcing active

LED (yellow) Sequence Significance

lights up

ON

Off

System start with saved parameterisation and saved CPX expansionset; parameters and CPX expansion are saved remanently; externalparameterisation is blocked1)

Caution when replacing CPX valve terminals with saved parameterisation. For these CPX terminals, parameterisation is not carried outautomatically by the higher-order controller when the terminal isreplaced.� Before replacement, note required settings and restore them

after replacement, if required.

flashes

ON

OFF

Forcing active1)

The Forcing function is released or the IP address has been changedvia DIP switches (restart required)

Off

ON

OFF

System start with default parameterisation (factory setting) andcurrent CPX expansion set; external parameterisation is possible(presetting)

1) Indication of the Forcing function (LED flashing) has priority over indication of the setting for thesystem start (LED lights up).

Tab. 4/6: LED indicator M (Parameterisation modified or Forcing active)

4. Diagnostics


4.2.2 Network-specific LED indicators

MS (Module Status) – module status1)

LED (green, red)

Sequence Significance Error handling

EtherNet/IP network protocol

lights up green

ON

OFF

Normal operating status –

flashes green

ON

OFF

Configuration of the CPX terminal not complete or not correct.

� Complete or correct configuration of the CPX terminal.

lights up red

ON

OFF

Error cannot be rectified � Contact Festo Service (� www.festo.com).

flashes red

ON

OFF

Error can be rectified � Check configuration of theCPX terminal.

flashes red/green

ON

OFF

The CPX terminal is in self-test. –

Off

ON

OFF

No logic power supply of the network interface.

� Check logic supply.

Modbus® TCP network protocol

lights up green

ON

OFF

Ready for Modbus connections –

Off

ON

OFF

Not ready for Modbus® connections

–

1) The behaviour of the LED indicator is dependent on the network protocol used.

Tab. 4/7: LED indicator MS (Module Status)

4. Diagnostics


NS (Network Status) – Network status1)

LED (green, red)

Sequence Significance Error handling

EtherNet/IP network protocol

lights up green

ON

OFF

Normal operating status.The CPX terminal is online andhas a network connection.

–

flashes green

ON

OFF

The CPX terminal is online andhas received an IP address butdoes not have a configured network connection.

� Check configuration of theCPX terminal; it is possiblethat the CPX terminal is notassigned to any master/scanner.

lights up red

ON

Off

Communication has failed.Non-permitted IP address that isalready used in the network is set.

� Correct IP address.

flashes red

ON

OFF

One or more “I/O connections”are in the “time-out status”.

� Check the physical connectionto the master/scanner.

flashes red/green

ON

OFF

The CPX terminal is in self-test. –

Off

ON

OFF

The CPX terminal is offline. � Check network connection.

Modbus® TCP network protocol

lights up green

ON

OFF

At least one Modbus® connection active.

–

Off

ON

OFF

No Modbus® connection active. –

1) The behaviour of the LED indicator is dependent on the network protocol used.

Tab. 4/8: LED indicator NS (Network Status)

4. Diagnostics


TP1, TP2 (link/traffic) – connection/data traffic


lights up

ON

Off

Network connection OK –

flashes

ON

OFF

Data traffic ongoing (Traffic)Flashing frequency is dependenton the traffic.

–

Off

ON

OFF

No network connection � Check network connection.

Tab. 4/9: LED indicator TP1, TP2 (connection/data traffic)

4. Diagnostics


4.3 Diagnostics via status bits

Status bits are internal inputs that serve to display commondiagnostic messages (global error messages). If all status bitssupply a 0-signal, no error is reported. If at least one statusbit delivers a 1-signal, there is an error (� Tab. 4/10).

If the status bits are to be transmitted via a “polled” or“change of state” connection, you must set the DIL switcheson the bus node accordingly (� Tab. 1/3).

Bit Diagnostic informationwith logic 1

Description

0 Error at valve Module type in which the error has occurred

1 Error at output

2 Error at input

3 Error at analogue module/technology module

Module type in which theerror has occurred

4 Undervoltage Error type

5 Short circuit/overload Error type

6 Wire break Error type

7 other error Error type

Tab. 4/10: Overview of status bits

Detailed information on the status bits can be found in theCPX system description (� P.BE-CPX-SYS-…).

4. Diagnostics


4.4 Diagnostics via the I/O diagnostics interface

Detailed diagnostic information about the CPX terminal canbe accessed via the I/O diagnostic interface. As a result, itcan be determined exactly on which module and channel anerror has occurred, for example. Available to access this information are 16 input bits and 16 output bits, through whichall diagnostic data can be read.

To use the I/O diagnostics interface, it must be activated viaDIL switches on the bus node (� Tab. 1/3). If the I/O diagnostic interface is activated, it will occupy the first 16 inputsand outputs in the address range (� Tab. B/8).

Diagnostic data Description

Global diagnostic data General overview of errors

Diagnostic data module Detailed diagnostics per module

Status of diagnostic memory Number of entries in the diagnosticmemory and operating mode

Diagnostic memory data Long-term memory, detailed diagnostics and relative time stamp pererror event

Tab. 4/11: Diagnostic data

Detailed information on the I/O diagnostic information andthe available diagnostic information and the correspondingfunction numbers can be found in the CPX system description(� P.BE-CPX-SYS-…).

Access to EtherNet/IP objects via Explicit Messaging programming makes more sense with the bus node CPX-FB36than use of the I/O diagnostics interface (� C.1).

4. Diagnostics


4.5 Diagnostics via EtherNet/IP

The CPX system permits diagnostics through the network.The following options are supported here:

– Explicit Messaging via EtherNet/IP Master

– Diagnostics via user program The I/O diagnostic interface can also be read out here.

Overview of diagnostic data 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 error number

133d Status and diagnostic object – Number of the module in which an error hasoccurred

– Diagnostic status (specifies whether diagnosticdata are present)

– System error number

134d Diagnostic trace object – Long-term memory (max. 40 entries)– Detailed diagnostics and relative time stamp per

error event

135d Diagnostic trace status object – Number of entries in the diagnostic memory– Trace status

Tab. 4/12: Diagnostic data with Explicit Messaging

4. Diagnostics


Possible sequence of diagnostics

Possible sequence of diagnostics Diagnostic data Object that supplies the diagnosticdata

1. Check whether diagnostic data are present Diagnostic status Status and diagnosticobject (133d)

2. Determine the number of the module in whichan error has occurred

Number of the module Status and diagnosticobject (133d)

3. Determine relevant module diagnostic data Error number, channeltype and number of thefaulty channel

General module parameter object (101d)

Tab. 4/13: Possible sequence of diagnostics

4.6 Diagnostics via Modbus®�TCP

The CPX system enables diagnostics via the Modbus® TCPprotocol.

– Diagnostics are implemented via the CPX status register(� description P.BE.CPXFEC-..., chapter 6.2.2)

– CPX diagnostic memory and I/O description (� description P.BE.CPXFEC-..., chapter 6.2.4)

4. Diagnostics


4.7 Error handling (“Fail safe”)

The behaviour of the CPX terminal with the following errors isdependent on the parameterisation of the higher-order controller and the setting of the “Fail safe” parameter:

– Telegram failure

– Stop the higher-order controller

– Break in the network cable.

Depending on the parameterisation, the outputs (valves andelectric outputs) will be switched off (factory setting),switched on or retain their status.

“Reset outputs” means the following:– Monostable valves move to the initial position.– Double solenoid valves remain in the current position.– Mid-position valves go into mid-position

(pressurised, exhausted or closed, depending on valvetype).

WarningUndesired status of valves and outputs with communication errors

Injury to persons, damage to the machine and system

An incorrect status of valves and outputs can lead to dangerous situations.

� Ensure that valves and outputs relating to the aforementioned problems are placed in a safe condition.

The Modbus® connection for the controller is monitored bydefault with a timeout of 10 seconds. This time can be adapted through the Modbus® address 46100 (� Tab. D/5). If notelegrams are received by the controller during the set time,the outputs are set to the set values of the “Fail safe” parameter.

Technical appendix

A-1Festo CPX-FB36-EN en 1611a English

Appendix A

Technical appendix

A. Technical appendix

A-2 Festo CPX-FB36-EN en 1611a English

Contents

A. Technical appendix A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.1 Technical data A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


A-3Festo CPX-FB36-EN en 1611a English

A.1 Technical data

General

General technical data � CPX system description P.BE-CPX-SYS-…

Degree of protection through housing in accordance with IEC 60529, completely mounted, plugconnector in plugged-in status or equipped with cover caps.

IP65/IP671)

Protection against electric shockProtection against direct and indirect contact in accordancewith IEC 60204-1/EN 60204-1

Through the use of PELV circuits(Protected Extra-Low Voltage)

Module code (CPX-specific)

Remote I/O 224

Remote controller 171

Module identifier (operator unit)

EtherNet/IP

Remote I/O FB36 EtherNet/IP Remote-IO V2

Remote controller FB36-RC EtherNet/IP Node

Modbus TCP

Remote I/O FB36-MB Modbus TCP Remote-IO

Remote controller FB36-MB-RC Modbus TCP Node

1) Connected products may only satisfy a lower degree of protection.

Tab. A/1: Technical data – general


A-4 Festo CPX-FB36-EN en 1611a English

Power supply

Operating voltage supply UEL/SEN [V DC] 24 _ 25 %

Intrinsic current consumption at nominal operatingvoltage 24 V from operating voltage supply UEL/SEN

[mA] Typ. 100 (internal electronics)

Separation of network interface from operatingvoltage supply UEL/SEN

Galvanic

Load voltage supply UVAL/OUT [V DC] 24 _ 10 %

Mains buffering time [ms] 10

Tab. A/2: Technical data – power supply

Network-specific

Connection technology 2× socket, M12, D-coded, 4-pin

Protocol EtherNet/IP or Modbus TCP1)

Specification IEEE 802.3u (100Base-TX)

Transmission rate [Mbit/s] 10/100 (full duplex/half duplex)

Minimum cycle time (RPI) [ms] 1

Maximum data field size (input/output size)

Remote I/O [byte] 64 I/64 O

Remote controller [byte] 8 I/8 O, 16 I/16 O, 32 I/32 O or64 I/64 O2)

Crossover detection Auto-MDI/MDI-X

Cable type Ethernet twisted pair cable,screened

Transmission class Category Cat� 5/Cat �5e

Maximum cable length [m] 100

1) Based on the Ethernet protocol IEEE 802.32) Dependent on the setting of the DIL switch 2 and the revision of the bus node

Tab. A/3: Technical data – network-specific

Address assignment of the CPX terminal

B-1Festo CPX-FB36-EN en 1611a English

Appendix B

Address assignment of the CPX terminal

B. Address assignment of the CPX terminal

B-2 Festo CPX-FB36-EN en 1611a English

Contents

B. Address assignment of the CPX terminal B-1. . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1 Address assignment B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.1 Bus node B-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.2 Digital modules B-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.3 Analogue modules B-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.4 Technology modules B-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2 Addressing B-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.1 Basic rules for addressing B-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.2 Data formats B-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.3 Examples of addressing B-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3 Address assignment after extension/conversion B-20. . . . . . . . . . . . . . . . . . . . . .



B.1 Address assignment

A CPX terminal consists of a different number of inputs andoutputs, depending on the order and the configuration of thebus node.

The inputs and outputs are assigned automatically within theCPX terminal.

� Determine the address assignment (number of allocatedinputs and outputs) on the CPX terminal prior to commissioning.

Note� The address space of a CPX terminal is limited. The bus

node provides the CPX terminal a maximum addressspace of 64 bytes for inputs and 64 bytes for outputs.

� An activated diagnostic mode reduces the number ofavailable I/O bytes.

The number of assigned inputs and outputs for modules canbe found in the following tables:

– Bus nodes (� Tab. B/1)

– Digital modules (� Tab. B/2 … Tab. B/4)

– Analogue modules (� Tab. B/5)

– Technology modules (� Tab. B/6 and Tab. B/7).



B.1.1 Bus node

Bus node CPX-FB36 in operating mode Moduleindicator1)

Assigned addressspace

Inputs Outputs

Remote I/O

Without diagnostics mode FB-36-RIO… – –

With status bits FB-36-RIO… 1x 16 bit2) –

With I/O diagnostics interface FB-36-RIO… 1x 16 bit 1x 16 bit

Remote controller FB-36-RC… 8x 8 bit8x 16 bit3)

8x 8 Bit8x 16 bit3)

1) In the operator unit or in the hardware configuration of the programming software.2) Diagnostics mode status bits assigned 2 bytes of address space (8 bits remain unused).3) Dependent on the setting of the DIL switches

Tab. B/1: Address assignment of bus nodes



B.1.2 Digital modules

Module designation Moduleindicator1)


Inputs Outputs

Input module

CPX-4DE 4DI 4x 1 bit2) –

CPX-8DE 8DI 8x 1 bit –

CPX-8NDE (n-switching) 8NDI 8x 1 bit –

CPX-8DE-D (with channel diagnostics) 8DI-D 8x 1 bit –

CPX-16DE 16DI 16x 1 bit –

CPX-M-16DE-D (with channel diagnostics) 16DI-D 16x 1 bit –

CPX-L-16DE-16-KL-3POL (with terminal strip) L-16DI-PI 16x 1 bit –

Output module

CPX-4DA 4DO – 4x 1 bit2)

CPX-8DA 8DO – 8x 1 bit

CPX-8DA-H (high current) 8DO-H – 8x 1 bit

Input/output module

CPX-8DE-8DA 8DI/8DO 8x 1 bit 8x 1 Bit

CPX-L-8DE-8DA-16-KL-3POL (with terminal strip) L-8DI8DO-PI 8x 1 bit 8x 1 Bit

1) In the operator unit or in the hardware configuration of the programming software.2) Digital 4-fold modules (CPX-4DE and CPX-4DA) always occupy 8 inputs or 8 outputs.

Tab. B/2: Address assignment of digital modules (part 1)





Inputs Outputs

Electronics module

VMPA1-FB-EMS-8 for pneumatic module MPA1(1 … 8 valves)

MPA1S – 8x 1 bit2)

VMPA2-FB-EMS-4 for pneumatic module MPA2(1 … 4 valves)

MPA2S – 8x 1 bit3)

Electronics module (electrically isolated)

VMPA1-FB-EMG-8 for pneumatic module MPA1(1 … 8 valves)

MPA1G – 8x 1 bit2)

VMPA2-FB-EMG-4 for pneumatic module MPA2(1 … 4 valves)

MPA2G – 8x 1 bit3)

Electrical module with diagnostic function

VMPA1-FB-EMS-D2-8 for pneumatic module MPA1(1 … 8 valves)

MPA1S-D – 8x 1 bit2)

VMPA2-FB-EMS-D2-4 for pneumatic module MPA2(1 … 4 valves)

MPA2S-D – 8x 1 bit3)

Electrical module with diagnostic function (electrically isolated)

VMPA1-FB-EMG-D2-8 for pneumatic module MPA1(1 … 8 valves)

MPA1G-D – 8x 1 bit2)

VMPA2-FB-EMG-D2-4 for pneumatic module MPA2(1 … 4 valves)

MPA2G-D – 8x 1 bit3)

1) In the operator unit or in the hardware configuration of the programming software.2) VMPA1 modules always occupy 8 outputs regardless of the number of valves attached.3) VMPA2 modules always occupy 8 outputs, although only 4 bits are used.






Inputs Outputs

Electrical interlinking VMPAL-EVAP-10-... (for pneumatic module MPA-L)

VMPAL-EVAP-10-1 (1 valve, 1 coil) MPAL – 1 bit

VMPAL-EVAP-10-2 (1 valve, 2 coils) MPAL – 2 bit

VMPAL-EVAP-10-1-4 (4 valves, 4 coils) MPAL – 4 bit

VMPAL-EVAP-10-2-8 (4 valves, 8 coils) MPAL – 8 bit

End plate (pneumatic interface) VMPA…

VMPA-FB-EPL-… for valve terminal MPA-S – – –

VMPAF-FB-EPL-… for valve terminal MPA-F – – –

VMPAL-FB-EPL-… for valve terminal MPA-L

1 … 4 solenoid coils – – 8x 1 bit





Pneumatic interface

VABA-… for valve terminal VTSA-/VTSA-F with setting:2)

VTSA orTyp44/453)

1 … 8 solenoid coils – 8x 1 bit




1) In the operator unit or in the hardware configuration of the programming software.2) Setting via DIL switches of the pneumatic interface.3) Dependent on the version of the operator unit




Additional information:

– The address assignment within the individual CPX I/Omodules can be found in the description for the I/O modules (� P.BE-CPX-EA-…).

– Information about pneumatic interfaces and pneumaticmodules can be found in the corresponding descriptionsof pneumatics.

– An overview of the “Descriptions of the CPX terminal”documentation can be found in the CPX system description (� P.BE-CPX-SYS-…).

– From the technical point of view, the individual pneumaticmodules each represent an electric module for controllingthe attached valves.



B.1.3 Analogue modules



Inputs Outputs

VMPA-FB-PS-… (pressure sensor) MPA-P 1x 16 bit –

VPPM-…TA-L-1-F… (Proportional pressure regulator valve) VPPM 1x 16 bit 1x 16 bit

Analogue module

CPX-2AE-U-I 2AI 2x 16 bit –

CPX-4AE-U-I 4AI 4x 16 bit –

CPX-4AE-I 4AI-I 4x 16 bit –

CPX-4AE-T (Temperature module for RTD sensors) 4AI-T 2x 16 bitor4x 16 bit2)

–

CPX-4AE-TC (Temperature module for TC sensors) 4AI-TC 4x 16 bit –

CPX-4AE-P-D10 (Pressure sensor module 0 … 10 bar) 4AI-P-D10 4x 16 bit –

CPX-4AE-P-B2 (Pressure sensor module –1 … 1 bar) 4AI-P-B2 4x 16 bit –

CPX-2AA-U-I 2AO – 2x 16 bit

1) In the operator unit or in the hardware configuration of the programming software.2) Depending on the configuration

Tab. B/5: Address assignment of the analogue module

The address assignment within the individual CPX analogueI/O modules can be found in the description for the analogueI/O modules (� P.BE-CPX-AX-…).



B.1.4 Technology modules



Inputs Outputs

CPX-CP-4-FB Electrical interface (CP interface) CPI Maximum16x 8 bit2)

Maximum16x 8 bit2)

CPX-CMAX-C1-1 Axis controller CMAX-C1-1 8x 8 bit 8x 8 Bit

CPX-CMXX control block (multi-axis interface) CMXX 8x 16 bit 8x 16 bit

CPX-CMPX-C-1-H1 End-position controller CMPX-C-1 6x 8 bit 6x 8 Bit

CPX-CM-HPP control block (FHPP interface) CM-HPP 32x 8 bit 32x 8 bit

CPX-CMIX-M1-1 Measuring module CMIX 3x 16 bit 3x 16 Bit

CPX-2ZE2DA Input/output module (counter module) 2CI2DO 3x 32 bit 3x 32 Bit

CPX-FEC control block (front end controller) FEC 8x 8 bit 8x 8 Bit

1) In the operator unit or in the hardware configuration of the programming software.2) Maximum assigned address space is dependent on the string allocation.

Tab. B/6: Address assignment for technology modules (part 1)





Inputs Outputs

CPX-CTEL-4-M12-5POLElectrical interface with setting:

CTEL

0I/0O – –

0I/8O – 8x 8 bit

0I/16O – 16x 8 bit

0I/24O – 24x 8 bit

0I/32O – 32x 8 bit

8I/0O 8x 8 bit –

16I/0O 16x 8 bit –

24I/0O 24x 8 bit –

32I/0O 32x 8 bit –

8I/8O 8x 8 bit 8x 8 bit

16I/16O 16x 8 bit 16x 8 bit

24I/24O 24x 8 bit 24x 8 bit

32I/32O 32x 8 bit 32x 8 Bit

CPX-CTEL-2-M12-5POL-LKElectrical interface with setting:

CTEL-2-LK I-port LK master

8I/8O 8x 8 bit 8x 8 bit

16I/16O 16x 8 bit 16x 8 bit

24I/24O 24x 8 bit 24x 8 Bit

1) In the operator unit or in the hardware configuration of the programming software.

Tab. B/7: Address assignment for technology modules (part 2)

Details on the technology modules can be found in the corresponding descriptions (� P.BE-CPX-…).



B.2 Addressing

B.2.1 Basic rules for addressing

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

– Counting from left to right, addressing bytewise: Moduleswith less than 8 bits occupy an 8-bit address space, butdo not use it completely.

– The bus node counts as a module with 0 inputs and 0 outputs when the status bits and the I/O diagnostic interfaceare deactivated.

– The I/Os of different module types are assigned separately from each other.The sequence in the following table applies:

Sequence of addressing Description

1. I/O diagnostics interface1) Can be activated by DIL switch. If it is activated, it will occupythe first 16 inputs and outputs in the address range.

2. Analogue modules Modules with analogue inputs/outputs

3. Technology modules e.g. CP interface, control block 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 (� note aboveand Tab. 1/3).

Tab. B/8: Sequence of addressing



B.2.2 Data formats

In the “Studio 5000” software, the inputs and outputs of thebus node are configured in the SINT or INT formats.

Using the SINT format

If the SINT format is used, the data length of the AssemblyInstances corresponds to the precise byte of the current CPXterminal configuration.

The following Assembly Instances are used for the SINTformat.

– Inputs: Assembly Instance 101

– Outputs: Assembly Instance 100

Using the INT format

If the INT format is to be used, then the size of the processdata must be a multiple of 16 bits.

If the total size of process data for the CPX terminal is not amultiple of 16 bits, the process data will be rounded to thenearest 16-bit limit at the end with dummy I/Os.

Two CPX modules share a 16-bit tag in the “Studion 5000”software, depending on the configuration of the CPX terminal.

The following Assembly Instances are used for the INTformat:

– Inputs: Assembly Instance 111

– Outputs: Assembly Instance 110

Note� Ensure that the outputs (100 and 110) are not accessed

simultaneously on the Assembly Instances.



B.2.3 Examples of addressing

Example 1: CPX terminal with MPA pneumatics

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

– Status bits and I/O diagnostics interface deactivated

Module no.: 0

1 2

8DI 4DO

3

1 2 3 4 5 6

4

1 Bus node CPX-FB36

2 MPA pneumatic interface

3 MPA1 pneumatic modules (8 DO)

4 MPA2 pneumatic modules (4 DO)

Fig. B/1: Example 1 – CPX terminal with MPA pneumatics



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

Modulenumber

Module type I address O address

0 Bus node CPX-FB36 – –

1 Digital input module CPX-8DE E0 … E7 –

2 Digital output module CPX-4DA – A0 … A71)

3 MPA1 pneumatic module (8 DO) – O8 … O15


5 MPA2 pneumatic module (4DO) – O24 … O311)

6 MPA2 pneumatic module (4DO) – O32 … O391)

1) 8 bits assigned, 4 bits used.

Tab. B/9: Address assignment example 1 (� Fig. B/1)



Example 2: CPX terminal with electrical interface

The following graphic shows a CPX terminal with electricalinterface and the following setting:

– Status bits and I/O diagnostics interface deactivated

1 2 3 4 5 6Module no.: 0

1

2

3

4

5

6

8DI 4DO 8DI 8DO

1 Bus node CPX-FB36

2 CPV valve terminal (16 DO) on string 1of the electrical interface

3 CP input module (16 DI)

4 Sensor

5 Cylinder

6 CP output module (16 DO) on string 4of the electrical interface

Fig. B/2: Example 2 – CPX terminal with electrical interface (CP interface)



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

Modulenumber


0 Bus node CPX-FB36 – –

1 Digital input module CPX-8DE I32 … I39 –

2 Digital output module CPX-4DA – O128 … O1351)

3 Electrical interface (CP interface) CPX-CP-4-FB(4 byte I, 16 byte O)

I0 … I31 O0 … O127

4 Digital input/output module CPX-8DE-8DA I40 … I47 O136 … O143



1) 8 bits assigned, 4 bits used




Example 3: CPX terminal with analogue module andVTSA pneumatics

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

– Status bits activated

– I/O diagnostics interface deactivated

– Pneumatic interface set with DIL switch to 1 ... 8 solenoidcoils

1 2

8DI 8DI 4DO 8DI 2AO

3

8DO

Module no.: 0 1 2 3 4 5 6

1 Bus node CPX-FB36 (status bits activated)

2 Pneumatic interface VABA set with DILswitch to 1 ... 8 solenoid coils

3 VTSA pneumatics

Fig. B/3: Example 3 – CPX terminal with analogue module and VTSA pneumatics



Modulenumber


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





5 Analogue output module CPX-2AA – O0 … O31

6 Pneumatic interface VABA set with DIL switch to1 ... 8 solenoid coils

– O48 … O55

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




B.3 Address assignment after extension/conversion

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

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

� Additional modules are inserted between existingmodules.

� Existing modules are removed or replaced by other modules, which have fewer or more input/output addresses.

� Interlinking blocks (VTSA) or pneumatic connectionblocks (MPA-L) for monostable valves are replaced byinterlinking blocks/connection blocks for bistable valves– or vice versa (�� Pneumatics description).

� Additional interlinking blocks (VTSA) or connectionblocks (MPA-L) are inserted between existing ones.

� Status bits or the I/O diagnostic interface are activated/deactivated.



Addressing example 3 after extension/conversion

The following depiction shows the effects of changes on theaddress assignment using the addressing example 3(� Fig. B/3).

The following has been changed:

– The status bits have been deactivated.

– The digital input module CPX-8DE (Module no. 1) hasbeen replaced by a digital input module CPX-16DE.

– The pneumatic interface VABA has been set to 1 ... 16solenoid coils in order to reserve addresses for an extension to the pneumatics.

1 2

16DI 8DI 4DO 8DI 2AO

3

8DO

Module no.: 0 1 2 3 4 5 6

1 Changed: status bits deactivated

2 Changed: digital input moduleCPX-8DE replaced by digital inputmodule CPX-16DE

3 Changed: Pneumatic interface VABAnow set with DIL switch to 1 ... 16solenoid coils

Fig. B/4: Addressing example 3 after extension/conversion (see Fig. B/3)



Modulenumber

Module I address O address

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





5 Analogue output module CPX-2AA – O0 … O31

6 Pneumatic interface VABA set with DIL switch to1 ... 16 solenoid coils

– O48 … O63

bold = changes1) 8 bits assigned, 4 bits used

Tab. B/12: Addressing example 3 after extension/conversion (� Fig. B/4)

EtherNet/IP Objects of the CPX-FB36

C-1Festo CPX-FB36-EN en 1611a English

Appendix C

EtherNet/IP Objects of the CPX-FB36

C. EtherNet/IP Objects of the CPX-FB36

C-2 Festo CPX-FB36-EN en 1611a English

Contents

C. EtherNet/IP Objects of the CPX-FB36 C-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.1 Overview of Ethernet/IP objects C-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2 Objects for network settings C-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2.1 “Device Level Ring Object” C-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2.2 “QoS Object” C-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2.3 “TCP/IP Interface Object” C-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.2.4 “Ethernet Link Object” C-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.3 Objects for the I/O connection C-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.3.1 “Assembly Object” C-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4 Objects for system data and diagnostics C-18. . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.1 “Identity Object” C-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.2 “Global System Object” for operating mode “Remote I/O” C-20. . . . . .

C.4.3 “Status and Diagnosis Object” C-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.4 “Diagnosis Trace Object” C-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.5 “Diagnosis Trace Status Object” C-26. . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.6 “Generic Parameter Object” C-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.7 “Force Parameter” C-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.8 “Fail safe” and “Idle” parameters C-36. . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.9 “Configuration Array Object” C-42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.10 “Slave Size Object” for “Remote Controller” operating mode C-42. . . .

C.4.11 “ISDU Access Object” C-43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5 Examples C-45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5.1 Forcing inputs C-45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5.2 Parameterisation with “Generic Parameter Object” C-47. . . . . . . . . . . .



C.1 Overview of Ethernet/IP objects

This chapter describes the representation of the CPX terminalwithin the Ethernet/IP object model.

Some of the information is in English, even in the documentation in other languages, so that the original terms of theEthernet/IP specification can be used uniquely.

“EtherNet/IP Class Services”

The CPX terminal supports various services, depending onthe Object:

Service Code Service Name

05 (05h) Reset

01 (01h) Get Attribute All

14 (0Eh) Get Attribute Single

16 (10h) Set Attribute Single

Tab. C/1: Class services and Instance services



EtherNet/IP object classes

The following objects are supported:

Object class Instances(dec.)

Name Comments

1d 1 Identity Object General CIP Objects

2d 1 Message Router Object

4d 100 … 102,110, 111

Assembly Object

6d 1 … 10 Connection Manager Object

244d 1 Port Object

245d 1 TCP/IP Interface Object EtherNet/IP-specificObjects

246d 2 Ethernet Link Object

71d 1 Device Level Ring Object

72d 1 QoS Object

132d 1 Global System Object CPX-specific objects forparameterisation anddiagnostics133d 1 Status and Diagnosis Object

134d 1 … 40 Diagnosis Trace Object

135d 1 Diagnosis Trace Status Object

199d 1 Configuration Array Object

108d … 111d,116d … 119d,124d … 127d

1 … 48 Force Parameter

112d, 113d,120d, 121d,128d, 129d

1 … 48 Fail safe Parameter

Tab. C/2: Overview – EtherNet/IP objects - part 1




Name Comments

114d … 115d122d, 123d130d, 131d

1 … 48 Idle Parameter CPX-specific objects forparameterisation

101d 1 … 48 Generic Parameter Object

102d 1 … 48 Discrete Input Object CPX-specific objects forparameterisation of theinputs and outputs103d 1 … 48 Discrete Output Object

104d 1 … 48 Analog Input Object

105d 1 … 48 Analog Output Object

106d 1 … 48 Function Input Object

107d 1 … 48 Function Output Object

108d 1 … 48 Discrete Input Force State Object CPX-specific objects forparameterisation ofForce, Fail�safe and Idlemode

109d 1 … 48 Discrete Input Force Mode Object

110d 1 … 48 Discrete Output Force State Object

111d 1 … 48 Discrete Output Force Mode Object

112d 1 … 48 Discrete Output Failsafe State Object

113d 1 … 48 Discrete Output Failsafe Mode Object

114d 1 … 48 Discrete Output Idle State Object

115d 1 … 48 Discrete Output Idle Mode Object





Name Comments

116d 1 … 48 Analogue Input Force State Object CPX-specific objects forparameterisation ofForce, Fail�safe and Idlemode

117d 1 … 48 Analog Input Force Mode Object

118d 1 … 48 Analog Output Force State Object

119d 1 … 48 Analog Output Force Mode Object

120d 1 … 48 Analog Output Failsafe State Object

121d 1 … 48 Analog Output Failsafe Mode Object

122d 1 … 48 Analog Output Idle State Object

123d 1 … 48 Analog Output Idle Mode Object

124d 1 … 48 Function Input Force State Object

125d 1 … 48 Function Input Force Mode Object

126d 1 … 48 Function Output Force State Object

127d 1 … 48 Function Output Force Mode Object

128d 1 … 48 Function Output Failsafe State Object

129d 1 … 48 Function Output Failsafe Mode Object

130d 1 … 48 Function Output Idle State Object

131d 1 … 48 Function Output Idle Mode Object



Name Comments

136d 1 Slave Size Object CPX-specific Object

Tab. C/5: Special EtherNet/IP object for the Remote Controller operating mode



Counting mode For the module-oriented objectsInstance number = Module number + 1Explanation:- counting of the modules begins with 0 for the bus node - counting of the instances begins with 1 for the bus node.

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

The description of the functions of the individual parametersand data as well as fundamentals on parameterisation can befound in the CPX system description (� P.BE-CPX-SYS-…).



C.2 Objects for network settings

C.2.1 “Device Level Ring Object”

Object class: 71d

Instances: 1

Attr.no.

Access Description Type

1 Get Current network topology mode0: Linear1: Ring

USINT

2 Get Current status of network0: Normal1: Ring Fault2: Unexpected loop detected3: Partial network fault4: Rapid fault / restore cycle

USINT

10 Get Active Supervisor Address– Supervisor IP address– Supervisor MAC address

STRUCT ofUDINTARRAY of6 USINT

12 Get Capability FlagsBit 0: Announce-based

RingNode1)

Bit 1: Beacon-basedRingNode1)

Bit 2 … 4: Reserved. Shall be setto zero

Bit 5: Supervisor CapableBit 6 … 31: Reserved. Shall be set

to zeroBits 0 and 1 are mutually exclusive

DWORD

1) � EtherNet/IP specification, chapter 9-5.4

Tab. C/6: Network settings with Device Level Ring Object



C.2.2 “QoS Object”

Object class: 72d

Instances: 1

The IEEE 802.1D/Q describes Ethernet Frames that contain anadditional 32-bit header. This header contains, among otherthings, a VLAN ID and a prioritisation field.

Attr.no.


1 Set 802.1Q Tag enableEnables or disables sending 802.1Qframes on CIP and IEEE 1588 messagesDefault = 0

USINT

4 Set DSCP Urgent1)

Default = 55USINT

5 Set DSCP Scheduled1)

Default = 47USINT

6 Set DSCP High1)

Default = 43USINT

7 Set DSCP LowDefault = 31

USINT

8 Set DSCP ExplicitDefault = 27

USINT

1) These attributes describe the IP header priority of variousEtherNet/IP Frames:Urgent = CIP MotionScheduled = CIP SafetyHigh = I/O

Tab. C/7: Network settings with QoS Object



C.2.3 “TCP/IP Interface Object”

Object class: 245d

Instances: 1

The network settings of a device are configured with the TCP/IP Interface Object.

Attr.no.


1 Get Status (Interface Status) DWORD

2 Get Configuration CapabilityBit 5: Hardware configurableBit 6: Interface configuration

change requires resetBit 7: AcdCapable

DWORD

3 Get/Set Configuration Control DWORD

4 Get Physical Link Object– Path Size– Path

STRUCT ofUINT +PaddedEPATH

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

STRUCT ofUDINTUDINTUDINTUDINTUDINTSTRING

6 Get/Set HostName STRING

Tab. C/8: Network settings with TCP/IP Interface Object -part 1



Attr.no.


8 Get/Set TTL Valuefor EtherNet/IP multicast packets

USINT

9 Get/Set Mcast configIP multicast address configuration– Alloc Control– Reserved– Num Mcast– Mcast Start Addr

STRUCT of

USINTUSINTUINTUDINT

10 Set SelectAcd0: Disable1: Enable (default)

BOOL

11 Get/Set LastConflictDetected:– ACDactivity– RemoteMAC

– ArpPDU

STRUCT ofUSINTARRAY of6 USINTARRAY of28 USINT

12 Set QuickConnect0: Disable (default)1: Enable

BOOL

Tab. C/9: Network settings with TCP/IP Interface Object -part 2



C.2.4 “Ethernet Link Object”

Object class: 246d

Instances: 2

One instance per Ethernet port:

– Instance 1 corresponds to Ethernet port X1

– Instance 2 corresponds to Ethernet port X2

Via the Ethernet Link Object, you can undertake extendedsettings for the Ethernet connection (� section 1.3.6).

Attr.no.


1 Get Interface Speed UDINT

2 Get Interface Status Flags DWORD

3 Get Physical MAC address ARRAY of6 USINT

6 Get/Set Interface Control– Control Bits– Forced Interface Speed

STRUCT ofWORD,UINT

Tab. C/10: Network settings with Ethernet Link Object

Examples:

To set Port X1 permanently to 100 Mbit/s, full duplex (Auto-Negotiation off ), the following values must be written inAttribute 6, Instance 1: [0002h][0064h].

To activate Auto-Negotiation, the following values must bewritten in Attribute 6, Instance 1: [0001h][0000h].

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



C.3 Objects for the I/O connection

C.3.1 “Assembly Object”

Object class: 4d

Instances: 5

The Assembly Object bundles together attributes of variousobjects, so that exchange of data with the objects can takeplace over one connection.

The following instances are saved in the Assembly Object:

Instance Description

100 Output data

101 Input data

102 Configuration data

110 Output data with padding(Output data in the INT format)

111 Input data with padding(Input data in the INT format)

Tab. C/11: Instances for Assembly Object



Operating mode “Remote I/O”

Each data range begins on the LSB (least significant bit; low-order bit) of a word.

Instance 101: Input

Within the instance “Input of the Assembly Object”, all inputsof the CPX system are transmitted cyclically over the networkby means of a communication connection.

The following sequence applies:

Sequence of transmission

1. I/O diagnostic interface, if active (16-bit oriented)

2. Object instances of the analogue channels (16-bit oriented)

3. Instances of the technology modules (16- or 8-bit oriented)

4. Object instances of the digital inputs (8-bit oriented)

Tab. C/12: Sequence of transmission for Instance 101

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

102 1 … 48 1 … 64 Digital Data BOOL

104 1 … 48 1 … 32 Analogue channel data WORD

106 1 … 48 1 … 64/65 … 96

Technology module BYTE/WORD

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

Tab. C/13: Instance 101 member list in the Remote I/O operating mode



Instance 100: Output

Within the Instance Output in the Assembly Object, all outputs of the CPX system will be transmitted over the networkby means of one communication connection.

The following sequence applies:

Sequence of transmission

1. I/O diagnostic interface/status byte, if active (16-bit oriented)

2. Object instances of the analogue channels (16-bit oriented)

3. Instances of the technology modules (16- or 8-bit oriented)

4. Object instances of the digital outputs (8-bit oriented)

Tab. C/14: Sequence of transmission for Instance 100

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

103 1 … 48 1 … 64 Digital Data BOOL

105 1 … 48 1 … 32 Analogue channel data WORD

107 1 … 48 1 … 64/65 … 96


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

Tab. C/15: Instance 100 member list in the Remote I/O operating mode



Instance 102: Configuration

Instance 102 (Configuration) possesses the following memberlist:

Obj. Number of Entries in member list Type

199 1 Configuration Array data ARRAY

Tab. C/16: Instance 102 member list

The I/O objects 102 ... 107 also possess the following attributes:

Attribute Entries Type

100 Number of data of themodule in BYTE orWORD

BYTE

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

BYTE

102 All data values ARRAY

Tab. C/17: Attributes of I/O Objects 102 ... 107



“Remote Controller” operating mode

Each data range begins on the LSB (least significant bit; low-order bit) of a word.

Instance 100: Output

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

Obj. Attribute Entries in member list Type

107 1 … 64/65 … 96



Instance 101: Input

Instance 101 (input) possesses the following member list:

Obj. Attribute Entries in member list Type

106 1 … 64/65 … 96



Transmission through the communication types “Polled communication” or “Change of state/Cyclic communication”.

Instance 102: Configuration

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



C.4 Objects for system data and diagnostics

C.4.1 “Identity Object”

Object class: 1d

Instances: 1

The Identity Object contains the identification and generalinformation on the bus node CPX-FB36.

Service Code 5d:

Reset

– Parameter 0 emulates a power cycle

– Parameter 1 resets the device to the factory settings andthen emulates a power cycle.

Attr.no.


1 Get VendorID: 1Ah UINT

2 Get Device Type: 0Ch UINT

3 Get Product Code:– Remote I/O: 36CAh

– Remote Controller: 36CBh

UINT

4 Get Revision STRUCT

Tab. C/20: Attributes of the Identity Object - part 1



Attr.no.


5 Get StatusBit 0: OwnedBit 1: reserved, shall be 0Bit 2: ConfiguredBit 3: reserved, shall be 0Bit 4-7: Extended Device StatusBit 8: Minor Recoverable FaultBit 9: Minor UnrecoverableFaultBit 10: Major Recoverable FaultBit 11: Major Unrecoverable FaultBit 12-15: reserved, shall be 0

WORD

6 Get Serial Number UDINT

7 Get Product name

– CPX-FB36 Remote I/O

– CPX-FB36 Remote controller

SHORT_STRING

14 Get/Set Semaphore STRUCT

100 Get Operating Mode– Remote Controller: TRUE– Remote I/O: FALSE

BOOL

101 Get External Module Identifiers ARRAY

Tab. C/21: Attributes of the Identity Object - part 2



C.4.2 “Global System Object” for operating mode “Remote I/O”

Object class: 132d

Instances: 1

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

Attr.no.

Access Description Type Function no.

1 Get CPX operating mode (bit 0 … 3)0: Remote I/O without FEC/CEC1: Remote I/O with FEC or CEC2: Remote controller without bus node3: Remote controller with bus node

BYTE 0 (bit 0 … 3)

CPX expansion (bit 4)Specifies whether the current CPX expansioncorresponds to the saved CPX expansion.0: equal1: unequal

0 (bit 4)

Operator unit (bit 5)Specifies whether or not an operator unit isconnected.0: No operator unit is connected1: Operator unit connected

0 (bit 5)

Force mode (bit 6)Specifies whether Force is disabled or enabled.0: disabled1: enabled

0 (bit 6)

Bit 7: reserved 0 (bit 7)

Tab. C/22: Attributes of the System Object for operating mode Remote�I/O (part 1)



Attr.no.


2 Get Failsafe modeSpecifies whether Failsafe mode 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)

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

load sensor supply)Bit 1: Monitoring SCO

(short circuit/overload outputs)Bit 2: Monitoring UOUT

(undervoltage outputs)Bit 3: Monitoring UVAL

(undervoltage valves)Bit 4: Monitoring SCV

(short circuit 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 CPXterminal.

BYTE –

5 Get Number of output bytes (Tx size)Specifies the number of output bytes of the CPXterminal.

BYTE –

Tab. C/23: Attributes of the System Object for operating mode Remote�I/O - part 2



Attr.no.


9 Get/Set Monitoring (bit 0 ... 7)Bit 0: Monitoring SCS (short circuit/over

load sensor supply)Bit 1: Monitoring SCO (short circuit/over

load outputs)Bit 2: Monitoring UOUT (undervoltage out

puts)Bit 3: Monitoring UVAL (undervoltage val

ves)Bit 4: Monitoring SCV (short circuit valves)Bit 5 … 7: reserved1: active (presetting)0: inactive

BYTE 4401 (bit 0 … 7)

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

BYTE 4402 (bit 0, 1)

11 Get/Set Force mode0: disabled1: enabled

BYTE 4402 (bit 2, 3)

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 standard parameters (fac

tory setting) and current CPX expansion;external parameterisation possible(presetting)

1: System start with saved parameters and saved CPX expansion; parameters and CPXexpansion are saved remanently; externalparameterisation is blocked; the “Modify”LED on the bus node illuminates

BYTE 4402 (bit 6)

Tab. C/24: Attributes of the System Object for operating mode Remote�I/O (part 3)



C.4.3 “Status and Diagnosis Object”

Object class: 133d

Instances: 1

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

Attr.no.

Access Description Type Functionno.

1 Get Status bits (8 bit)Source of error: Bit 0: Valve

Bit 1: OutputBit 2: InputBit 3: Analogue/technology module

Error type: Bit 4: UndervoltageBit 5: Short circuit/overloadBit 6: Wire breakBit 7: Other error

BYTE 1936

2 Get Number of the first module in which a fault hasoccurred

BYTE 1937

3 Get Diagnostic status BYTE

4 Get Error number BYTE 1938

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

WORD

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

WORD

Tab. C/25: Attributes of the status and diagnostics object



C.4.4 “Diagnosis Trace Object”

Object class: 134d

Instances: 1 … 40

An instance is created for each diagnostic entry.

Attr.no.

Access Description Description Type Function no.3488 + n1)

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 days2) BYTE n = 10 × d + 0

3 Get Hours Number of hours2) BYTE n = 10 × d + 1

4 Get Minutes Number of minutes2) BYTE n = 10 × d + 2

5 Get Seconds Number of seconds2) BYTE n = 10 × d + 3

6 Get Milliseconds Number of 10 ms2) BYTE n = 10 × d + 4(Bit 0 … 6)

7 Get Module code3) Module code of the modulewhich registered the error

BYTE n = 10 × d + 5

8 Get Modulenumber

Module position of the module that signaled the error;63 = Error not module-related

BYTE n = 10 × d + 6(Bit 6, 7)

9 Get Channelnumber3)

Number of the first faultychannel

BYTE n = 10 × d + 7(Bit 0 … 5)

1) d (Diagnostic event) = 0 … 39; current diagnostic event = 0;2) Measured from the moment the power supply is switched on3) If the error number = 0, the content of this byte is also 0.

If the error number lies between 128 ... 199 (error class 3), the content of this byte is not relevant (servicing required).

Tab. C/26: Attributes of the diagnostics trace object - part 1



Attr.no.

Access Description Description Type Function no.3488 + n1)

10 Get Error number Possible fault messages see

� CPX system description

BYTE n = 10 × d + 8

11 Get Followingchannels1)

Number of subsequent channels with the same error

BYTE n = 10 × d + 9

1) If the error number = 0, the content of this byte is also 0. If the error number lies between 128 ... 199 (error class 3), the content of this byte is not relevant (servicing required).




C.4.5 “Diagnosis Trace Status Object”

Object class: 135d

Instances: 1

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: Recording active1: Recording inactive

BYTE 3483(Bit 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 at 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: Record up to the defined fault number (FN)2: Record up to the defined FN + module number

(MN)3: Record up to the defined FN + MN + channel

number (CN)4: Record from the defined FN5 = Record from the defined FN + MN6: Record from the defined FN + MN + CN7: Reserved

BYTE 3484(Bit 0 … 2)




Attr.no.

Access Name Type Functionno.

8 Get/Set End of error filter0: Record running errors (end of error)

(filter inactive, presetting)1: Do not record running errors (end of error)

(filter active)

BYTE 3484(Bit 3)

9 Get/Set Error number filterFN = Error (fault) number0: Error number filter inactive (presetting)1: Record only defined FN2: Do not record defined FN3: Reserved

BYTE 3484(Bit 4, 5)

10 Get/Set Module/channel filterWith this diagnostic memory filter, the recording oferrors of other modules or channels can be suppressed in order that errors in a particular module orchannel can be analysed.FN = Error (fault) number0: Module/channel filter inactive (presetting)1: Record only the FN of a module2: Record only the FN of a channel3: Reserved

BYTE 3484(Bit 6, 7)

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 Error numberFault number for the diagnostic memory filter

BYTE 3487(Bit 0 … 7)




C.4.6 “Generic Parameter Object”

Object class: 101d

Instances: 1 … 48

The rule is: Instance number = Module number + 1

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

� Use this object for parameterising modules with word ordouble-word parameters.

Examples of modules with word or double-word parameters:

– Analogue input module CPX-4AE-I

– Temperature module CPX-4AE-T

– CPX-CP interface

Three parameter types can be accessed via the attributes ofthe general module parameter object:

– byte parameters through the attributes 1 ... 64

– word parameters through the attributes 65 … 127

– double-word parameters through the attributes 129 … 189

Procedure for parameterisation

1. Take the function number of the parameter to be setfrom the description for the module.

2. Search for the function number in the Tab. C/30 (byte/word parameter) or Tab. C/31 (double-word parameter).

3. Read the corresponding attribute number from the respective table.

Examples for parameterisation with the general module parameter object can be found in chapter C.5.2.



Attribute no. Parameters Function no.

Byte Word Word

165

– � Description of the respective module 4828 + m × 64 + 0

266

4828 + m × 64 + 1

367

4828 + m × 64 + 2

468

4828 + m × 64 + 3

569

4828 + m × 64 + 4

670

4828 + m × 64 + 5

771

4828 + m × 64 + 6

872

4828 + m × 64 + 7

973

4828 + m × 64 + 8

1074

4828 + m × 64 + 9

1175

4828 + m × 64 + 10

1276

4828 + m × 64 + 11

……

4828 + m × 64 + …

……

4828 + m × 64 + …

……

4828 + m × 64 + …

…124

4828 + m × 64 + 59

61125

4828 + m × 64 + 60

62126

4828 + m × 64 + 61

63127

4828 + m × 64 + 62

64 – 4828 + m × 64 + 63

Tab. C/30: General module parameter object: Assignment of the attributes for word parameters to the function numbers



Attribute no. Parameters Function no.

Byte DWord DWord DWord DWord

1

129

– – – � Description of therespective module

4828 + m × 64 + 0

2

130

4828 + m × 64 + 1

3

131

4828 + m × 64 + 2

4

132

4828 + m × 64 + 3

5

133

4828 + m × 64 + 4

6

134

4828 + m × 64 + 5

7

135

4828 + m × 64 + 6

8

136

4828 + m × 64 + 7

9

…

4828 + m × 64 + 8

10

…

4828 + m × 64 + 9

11

…

4828 + m × 64 + 10

12

…

4828 + m × 64 + 11

…

185

4828 + m × 64 + …

…

186

4828 + m × 64 + …

…

187

4828 + m × 64 + …

…

188

4828 + m × 64 + 59

61

189

4828 + m × 64 + 60

62 – 4828 + m × 64 + 61

63 – 4828 + m × 64 + 62

64 – 4828 + m × 64 + 63

Tab. C/31: General module parameter object: Assignment of the attributes for double-word parameters to the functionnumbers



C.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. C/32: Objects for force parameter of digital I/O modules

Object Description

116 Force state analogue inputs

117 Force mode analogue inputs

118 Force state analogue outputs

119 Force mode analogue outputs

Tab. C/33: Objects for force parameter of 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. C/34: Objects for force parameter for technologymodules



Composition of the objects for “Force mode”

Objects for Force mode: 109d, 111d, 117d, 119d, 125d, 127d

(� Tab. C/32…Tab. C/34)

Instances: 1 … 48

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. C/35: Basic composition of the objects for Force mode



Composition of the objects for “Force state” for digital I/O modules

Objects for Force state: 108d, 110d (� Tab. C/32)

Instances: 1 … 48

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. C/36: Composition of the objects for Force state fordigital I/O modules



Composition of the Objects for “Force state” foranalogue I/O modules


Instances: 1 … 48

Attr.no.


1 Get/Set Channel 0:Value for Forcing

WORD


WORD

… … … …


WORD

Tab. C/37: Composition of the objects for “Force state” foranalogue I/O modules



Composition of the objects for “Force state” fortechnology modules


Instances: 1 … 48

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. C/38: Composition of the objects for Force state technology modules



C.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 Fail safe state digital outputs

113 Fail safe mode digital outputs

114 Idle state digital outputs

115 Idle mode digital outputs

Tab. C/39: Objects for Fail safe and Idle parameters of digital output modules

Object Description

120 Fail safe state analogue outputs

121 Fail safe mode analogue outputs

122 Idle state analogue outputs

123 Idle mode analogue outputs

Tab. C/40: Objects for Fail safe and Idle parameters of analogue output modules



Object Description

128 Fail safe state outputs technology module

129 Fail safe mode outputs technology module

130 Idle state outputs technology module

131 Idle mode outputs technology module

Tab. C/41: Objects for the Fail safe and Idle parameters fortechnology modules



Composition of the objects for “Fail safe mode” and“Idle mode”

Objects for Fail safe mode: 113d, 121d, 129d

Objects for Idle mode: 115d, 123d, 131d

(� Tab. C/39 … Tab. C/41)

Instances: 1 … 48

Attr.no.


1 Get/Set Channel 0:0: Hold last state1: Fail safe/Idle state

BOOL


BOOL

… … … …


BOOL


101 Get All channels: values for Fail safemode and Idle mode

ARRAY

Tab. C/42: Composition of the objects for Fail safe modeand Idle mode



Composition of the objects for “Fail safe state” and“Idle state” for digital output modules

Objects for Fail safe state: 112d

Objects for Idle state: 114d

(� Tab. C/39)

Instances: 1 … 48

Attr.no.



BOOL


BOOL

… … … …


BOOL


101 Get All channels: values for Fail safestate and Idle state

ARRAY

Tab. C/43: Composition of the objects for “Fail safe state”and “Idle state” for digital output modules



Composition of the objects for “Fail safe state” and“Idle state” for analogue output modules

Objects for Fail safe state: 120d

Object for Idle state: 122d

(� Tab. C/40)

Instances: 1 … 48

Attr.no.


1 Get/Set Channel 0: value for Fail safe state and Idlestate

WORD


WORD

… … … …


WORD

Tab. C/44: Composition of the Objects for Fail safe state andIdle state for analogue output modules and technology modules



Composition of the Objects for “Fail safe state” and“Idle state” for technology modules

Object for Fail safe state: 128d

Object for Idle state: 130d

(� Tab. C/41)

Instances: 1 … 48

Attr.no.


1 Get/Set Channel 0: value for Fail safe stateand Idle state

BYTE


BYTE

… … … …


BYTE


WORD

… … … …


WORD


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

BYTE

102 Get/Set All channels: values for Fail safestate and Idle state

ARRAY

Tab. C/45: Composition of the Objects for Fail safe state andIdle state for analogue output modules and technology modules



C.4.9 “Configuration Array Object”

The Configuration Array Object is available only for revisionstatuses later than Rev. 1.2. Further information about thisobject can be found at www.festo.com/sp.

Object class: 199d

Instances: 1

Attr.no.


1 Get/Set Data field with all system and module parameters. ARRAY –

Tab. C/46: “Configuration Array Object”

C.4.10 “Slave Size Object” for “Remote Controller” operating mode

Object class: 136d

Instances: 1

This object is only available in the Remote Controller operating mode.

The slave size object contains the number of I/O bytes forcommunication of the bus node CPX-FB36 with a controlblock (e.g. CPX-FEC). The setting is implemented via DILswitches on the bus node CPX-FB36 (� Tab. 1/3).

Attr.no.


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

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

Tab. C/47: “Slave Size Object” for “Remote Controller” operating mode



C.4.11 “ISDU Access Object”

Object class: 768d

Instances: 1

Attr.no.


1 Get List with instance numbers of CBUS modules withISDU function (ISDU = Indexed Service Data Unit)

ARRAY OFSINT

–

Tab. C/48: “ISDU Access Object”

The object also offers the following services:

Request ServiceCode

Instance1) Attribute2) Data [0 … 1] Data [2] Data [3 … n]

Read 0x32(50d)

Channel CBUS modulenumber

Index Sub-index –

Write 0x33(51d)

Channel CBUS modulenumber

Index Sub-index Data to write

1) The instance can take on the following values: 1= port 1; 2 = port 22) The attribute contains the CBUS module number, starting with 0

Tab. C/49: Services of the object “ISDU Access Object”

The answer for the services 0x32 and 0x33 is:

Data [0] Data [1 … n]

Response Status (� Tab. C/51) Data from ISDU(only for service 0x32 = Read)

Tab. C/50: Answer for the services 0x32 and 0x33



Response Status Description

0 Success

E1h Write data length too long

E2h Port unknown

E3h Device busy

E4h Write failed

E5h Read failed

E6h Read answer too long

E7h State unknown

E8h Port on master not support

E9h Port in invalid state

FFh Timeout

Tab. C/51: Response Status



C.5 Examples

C.5.1 Forcing inputs

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

1 2

3

4 5 6

Instance no.: 1

8 A 8 O

1

8DI 4 AI 8DI 8DO

0Module no.:

22

3

4 5 6 7

Ou t 2

I n1

MS PS

NS PL

TP1 SF

TP2 M

1 Parameterisation: Module CPX-4AE-I, setting of Force mode for channel 2:Object class 117 (� Tab. C/33)Instance 3 (= Module number + 1)Attribute 3 (for channel 2, � Tab. C/35 and Tab. C/52)

Fig. C/1: Example of Forcing (sequence see text)

1. Enable Force mode

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

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



2. Define value for Force state for channel 2:

Objects Force state: 116 (� Tab. C/37)Instance: 3

Attr.No.

Access Parameters Type

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


WORD

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



Tab. C/52: Example: Set Force state for module no. 2

3. Define Force mode for channel

Objects Force state: 117 (� Tab. C/35)Instance: 3

Attr.No.

Access Parameters Type

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

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

BOOL

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



Tab. C/53: Example: Set Force mode for module no. 2



C.5.2 Parameterisation with “Generic Parameter Object”

In this example, a signal extension time with a digital inputmodule and a lower limit value with an analogue input module are parameterised.

1 2

3

4 5 6

Instance no.: 1

8 A 8 O

1

8DI4

AI-I 8DI 8DO

0Module no.:

22

3

4 5 6 7

2

1 Parameterisation module CPX-8DE: Enable signal extension channel 5:Object class 101 (� C.4.6)Instance 1 (= module number)Attribute 7 (� Tab. C/54)

2 Parameterisation module CPX-4AE-I: Lower limit channel 2Object class 101Instance 2 (= module number)Attribute 82 (� Tab. C/55)

Fig. C/2: Examples for parameterisation with the general Module Parameter Object

The following tables show you how to determine the Attributes for the parameterisation. The parameters of the relevantmodules are entered in the tables.

Information on the parameters can be found in the description for the relevant module.



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

Byte Word Word

165

– Monitoring the CPX module 4828 + m * 64 + 0

2

66

Bit 0: Behaviour after short circuit/overloadBit 4, 5: Input debouncing timeBit 6, 7: Signal extension time

4828 + m * 64 + 1

367

– 4828 + m * 64 + 2

468

– 4828 + m * 64 + 3

569

– 4828 + m * 64 + 4

670

– 4828 + m * 64 + 5

771

Signal extension channel x 4828 + m * 64 + 6

8 ... – 4828 + m * 64 + 7

Tab. C/54: Example: parameterisation of signal extension for module no. 1

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

Byte Word Word

165

– Monitoring the CPX module 4828 + m * 64 + 0

266

Bit 0: Behaviour after short circuit/overload 4828 + m * 64 + 1

......

... 4828 + m * 64 + ...

......

... 4828 + m * 64 + ...

1580

Lower limit channel 1 4828 + m * 64 + 14

1681


1782


1883


... ... ... 4828 + m * 64 + ...

Tab. C/55: Example: parameterisation of the lower limit value (module no. 2, channel 2)

Modbus® TCP objects of the CPX-FB36

D-1Festo CPX-FB36-EN en 1611a English

Appendix D

Modbus® TCP objects of the CPX-FB36

D. Modbus® TCP objects of the CPX-FB36

D-2 Festo CPX-FB36-EN en 1611a English

Contents

D. Modbus® TCP objects of the CPX-FB36 D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.1 Overview of Modbus® TCP objects D-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.2 Commands and addresses D-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.3 CPX status information (Group A) D-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4 Process data (Group B and D) D-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.1 Bus node CPX-FB36 D-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.2 Electric modules D-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.3 Pneumatic modules D-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.4 Electrical interface (CP interface) CPX-CP-4-FB D-15. . . . . . . . . . . . . . . .

D.4.5 Composition of diagnostic data (diagnostic word) D-19. . . . . . . . . . . . .

D.4.6 Composition of the data of the I/O diagnostics interface D-20. . . . . . . .

D.5 Diagnostic memory (Groups C and E) D-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.6 Modbus TCP Objects (Group F) D-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.6.1 Addressing examples for Modbus® TCP D-24. . . . . . . . . . . . . . . . . . . . .



D.1 Overview of Modbus® TCP objects

This chapter describes the representation of the CPX terminalwithin the Modbus®/TCP object model. Some information is in English, even in the documentation inother languages, so that the original terms of the protocolspecification can be used clearly.

D.2 Commands and addresses

The table below shows the connection between the Modbus®address and data or parameters of the CPX terminal. The dataare assigned to various groups.

Modbus®command

Functioncode

Modbus®address

Significance Remote I/O16 bit access

Group

read4x registers

3 45357 … 4539145392 … 4564745648 … 4565545656 … 4605546100

CPX status informationInputs process dataDiagnostic memory parametersDiagnostic memory dataModbus® connection timeout

readreadreadreadread

OB CCA

write4x registers

6, 16 40001 … 4025640257 … 4026446100

Outputs process dataDiagnostic memory parametersModbus® connection timeout

writewritewrite

DEA

read/write4x registers

23 45357 … 4539145392 … 4564745648 … 4565545656 … 4605540001 … 4025640257 … 40264

CPX status informationInputs process dataDiagnostic memory parametersDiagnostic memory dataOutputs process dataDiagnostic memory parameters

readreadreadreadwritewrite

OB CCDE

read deviceidentification

43 Objects Objects ID0, 1, 2, 3, 4, 5 read F

Tab. D/1: Overview of the Modbus® function codes for the bus node CPX-FB36 in theRemote I/O operating mode



D.3 CPX status information (Group A)

The status information provides information on the configuration and the fault status of the CPX terminal. It lies in theModbus® address range 45367 … 45391.

Modbus®address

CPX-terminal configuration

Inputs process data

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

45367 Module 0 … 15

45368 Module 16 … 31

45369 Module 32 … 47

Bit n = 0: Module does not existBit n = 1: Module exists

Tab. D/2: Configuration information on the modules of the CPX terminal

Modbus®address

Error detection

Inputs process data

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

45383 Module 0 … 15

45384 Module 16 … 31

45385 Module 32 … 47

Bit n = 0: no errorBit n = 1: error in module n

Tab. D/3: Detection of which module reports an error



Modbus®address

Status register

Inputs process data

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

45391 Bit 4 = 1: Operator unit connected; 0: not connectedBit 11 = 1: Parameter write-protected; 0: no write protectionBit 15 = 1: Force active; 0: force inactive

Tab. D/4: Further status information (extracts from the system data)

Modbus®address

Modbus® connection timeout

Monitoring of the Modbus® connection in milliseconds [ms]

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

46100 0 = deactivatedRange of values: 10 … 65535Standard setting: 10000 (10 s)

Tab. D/5: Modbus® connection timeout



D.4 Process data (Group B and D)

The process image of the input data (Group B) and of the outputdata (Group D) is composed without gaps of the data of themodules as mounted from left to right in the CPX terminal. The Modbus® addresses depend accordingly on the modulesmounted on the CPX terminal. They are arranged in ascendingorder without gaps (n, n +1, n +2, ... ; n corresponds to the firstModbus® address of the module).

Examples of addressing (� D.6.1)

D.4.1 Bus node CPX-FB36

Modbus®address1)

Bus node CPX-FB36 remote I/O

Inputs process data Outputs process data

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Result of access to the I/O diagnosticinterface1)

Access to the I/O diagnostic interface2)

n+1 Data from the system table(read access)

Data for the system table2)

(write access)

n+2 Module diagnostics data (� Tab. D/26) –

1) n corresponds to the first Modbus® address of the module.

2) Composition of the I/O diagnostics interface (� Tab. D/27 … Tab. D/28)

Tab. D/6: Bus node CPX-FB36 remote I/O



D.4.2 Electric modules

Modbus®address1)

Digital input module (CPX-4DE)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n 0 Inputs –

n+1 Module diagnostics data –


Tab. D/7: Digital input module (CPX-4DE)

Modbus®address1)

Digital input module (CPX-8DE)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n 0 Inputs –



Tab. D/8: Digital input module (CPX-8DE)



Modbus®address1)

Digital output module (CPX-4DA)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n x Echooutputs

x Outputs



Tab. D/9: Digital output module (CPX-4DA)

Modbus®address1)

Digital input/output module (CPX-8DE-8DA)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n 0 Inputs x Outputs

n+1 x Echo outputs –



Tab. D/10: Digital input/output module (CPX-8DE-8DA)



Modbus®address1)

Analogue input module (CPX-2AE)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Analogue inputs channel 0 –

n+1 Analogue inputs channel 1 –



Tab. D/11: Analogue input module (CPX-2AE)

Modbus®address1)

Analogue output module (CPX-2AA)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Echo analogue outputs channel 0 Analogue outputs channel 0

n+1 Echo analogue outputs channel 1 Analogue outputs channel 1



Tab. D/12: Analogue output module (CPX-2AA)



D.4.3 Pneumatic modules

Modbus®address1)

MPA1 pneumatic module (1 … 8 valves)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n x Echo outputs x Outputs



Tab. D/13: MPA1 pneumatic module

Modbus®address1)

MPA2 pneumatic module (1 … 4 valves)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n x Echooutputs

x Outputs



Tab. D/14: MPA2 pneumatic module



Modbus®address1)

Pneumatic interface for CPA pneumatic set to 1 ... 8 valves


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

nx Echo outputs x Outputs

n+1 Diagnostic data –


Tab. D/15: Pneumatic interface for CPA pneumatic (1 ... 8 valves)

Modbus®address1)



Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Echo outputs Outputs






Modbus®address1)



Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Echo outputs 0 … 15 Outputs 0 … 15

n+1 x Echo outputs16 … 22

x Outputs 16 … 22




Modbus®address1)

Pneumatic interface for Midi/Maxi pneumatic set to 1 ... 8 valves


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n x Echo outputs x Outputs



Tab. D/18: Pneumatic interface for Midi/Maxi pneumatic (1 ... 8 valves)



Modbus®address1)



Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Echo outputs Outputs




Modbus®address1)



Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Echo outputs 0 … 15 Outputs 0 … 15


x Outputs 16 … 24






Modbus®address1)

Pneumatic interface for Midi/Maxi pneumatic set to 1 ... 32 valves2)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n+1 Echo outputs 0 … 15 Outputs 0 … 15


x Outputs 16 … 26


1) n corresponds to the first Modbus® address of the module.2) Only 26 valves can be used.




D.4.4 Electrical interface (CP interface) CPX-CP-4-FB

The electrical interface (CP interface) CPX-CP-4-FB has connections for 4 strings to each of which maximum 4 CP modules can be connected.

The last used string is decisive for the number of assignedbytes, even if numerically lower strings are not assignedphysically.

Modbus®address1)

Electrical interface (CP interface) CPX-CP-4-FBused string: 1 (Line 1)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Data byte 1 Data byte 0 Data byte 1 Data byte 0

n+1 Data byte 3 Data byte 2 Data byte 3 Data byte 2

n+2 Echo output data 1 Echo output data 0 –




Tab. D/22: Electrical interface (CP interface) CPX-CP-4-FB – used string 1



Modbus®address1)

Electrical interface (CP interface) CPX-CP-4-FBused strings: 1, 2 (Line 1 … 2)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0











Tab. D/23: Electrical interface (CP interface) CPX-CP-4-FB – used strings 1, 2



Modbus®address1)

Electrical interface (CP interface) CPX-CP-4-FBused strings: 1, 2, 3 (Line 1 … 3)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0















Tab. D/24: Electrical interface (CP interface) CPX-CP-4-FB – used strings 1, 2, 3



Modbus®address1)

Electrical interface (CP interface) CPX-CP-4-FBused strings: 1, 2, 3, 4 (Line 1 … 4)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0



















Tab. D/25: Electrical interface (CP interface) CPX-CP-4-FB – used strings 1, 2, 3, 4



D.4.5 Composition of diagnostic data (diagnostic word)

Module diagnostics data

Input data

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

0/1 0/1 Channel number (0 … 63) Error number (0 … 255)

Bit 15 and 14:0 0: Number of the first faulty O-channel1 0: Number of the first faulty I-channel0 1: There is a module error1 1: Reserved

Tab. D/26: Module diagnostics data



D.4.6 Composition of the data of the I/O diagnostics interface

I/O diagnostics interfacewrite access

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

x x x CPX function number

Data from the system table

Bit 15 (control bit): write access to the I/O diagnostics interface takes place with positive edge (0 � 1)Bit 14 = 0: byte value, 1: word valueBit 13 = 0: read request, 1: write request

Tab. D/27: I/O diagnostics interface – write access

I/O diagnostics interfaceread access

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Result of last request

Data from the system table

Result of last request:= 0: Wait= 8000h: Request successful 8000h: Error

8001h: Write protection or operator unit has write access8002h: Writing not permitted, reserved range8003h: Internal error

Tab. D/28: I/O diagnostics interface – read access

Information on the I/O diagnostics interface and examples ofits use can be found in the CPX system description (� P.BE-CPX-SYS-…).



D.5 Diagnostic memory (Groups C and E)

Modbus®address

Diagnostic memory parameters and dataRead access

Input data

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

45648 Run/stop filter 1 (CPX function number 3480)


45652 Error end filter (CPX function number 3484)

45652 Error number filter (CPX function number 3484)

45652 Module/channel filter (CPX function number 3484)

45653 Module number MN (CPX function number 3485)

45654 Channel number CN (CPX function number 3486)

45655 Error (fault) number FN (CPX function number 3487)

45650 Diagnostic memory data – number of entries (CPX function number 3482)

45651 Diagnostic memory data – overrun (CPX function number 3483)

45651 Diagnostic memory data – status (CPX function number 3483)

45656 Diagnostic memory data (CPX function number 3488 + n1))

… …

1)� CPX system description P.BE-CPX-SYS-...

Tab. D/29: Read access to diagnostic memory parameters and data



Modbus®address

Diagnostic memory parametersWrite access

Output data – write and modify

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0



40261 Error end filter (CPX function number 3484)

40261 Error number filter (CPX function number 3484)

40261 Module/channel filter (CPX function number 3484)

40262 Module number MN (CPX function number 3485)

40263 Channel number CN (CPX function number 3486)

40264 Error (fault) number FN (CPX function number 3487)

Tab. D/30: Write access to diagnostic memory parameters

Information on the diagnostic memory can be found in theCPX system description (� P.BE-CPX-SYS-…).



D.6 Modbus TCP Objects (Group F)

Object ID Object name Contents

0 Manufacturer name “Festo AG & Co. KG”

1 Product code “CPX-FB36”

2 MajorMinorRevision “x.y”1)

3 VendorURL “http://www.festo.com”

4 Product name “Modbus® TCP”

5 Model name “CPX Terminal”

1) x: Version Modbus® driver, y: Revision code CPX terminal

Tab. D/31: Modbus® TCP objects



D.6.1 Addressing examples for Modbus® TCP

CPX terminal with digital I/O modules and MPApneumatics

1 2 3

8DI 4DO

1 CPX-FB36

2 Digital I/O modules

3 MPA pneumatics

Fig. D/1: Example 1: CPX terminal with digital I/O modules and MPA pneumatics



Module Location

Modbus®address

Input data

Bit 15 8 7 4 3 0

CPX-FB36 Remote I/O

0 45392 Result of access to the I/O diagnostic interface

45393 Data from the system table (read access)

45394 Diagnostic data

Digital inputmodule (CPX-8DE)

1 45395 0 Input data


Digital outputmodule (CPX-4DA)

2 45397 x Echo output data


MPA pneumaticmodule with diagnostic function












Tab. D/32: Input data addressing example 1 (CPX terminal from Fig. D/1)



Module Location

Modbus®address

Output data

Bit 15 8 7 4 3 0

CPX-FB36 Remote I/O


40002 Data for the system table (write access)

Digital output module (CPX-4DA)

2 40003 x Output data









Tab. D/33: Output data addressing example 1 (CPX terminal from Fig. D/1)



CPX terminal with digital and analogue I/O modulesas well as MPA pneumatics

1 2 3 4

2AI 2AO8DI

1 CPX-FB36

2 Digital I/O modules

3 Analogue I/O modules

4 MPA pneumatics

Fig. D/2: Example 2: CPX terminal with digital and analogue I/O modules as well as MPApneumatics



Module Location

Modbus®address

Input data

Bit 15 8 7 4 3 0

CPX-FB36 Remote I/O


45393 Data from the system table (read access)


Digital inputmodule (CPX-8DE)

1 45395 0 Input data

45396 Module diagnostics data

Analogue inputmodule (CPX-2AE)

2 45397 Analogue inputs channel 0

45398 Analogue inputs channel 1


Analogue outputmodule (CPX-2AA)

3 45400 Echo analogue outputs channel 0

45401 Echo analogue outputs channel 1











Tab. D/34: Input data addressing example 2 (CPX terminal from Fig. D/2)



Module Location

Modbus®address

Output data

Bit 15 8 7 4 3 0

CPX-FB36 Remote I/O


40002 Data for the system table (write access)

Analogue outputmodule (2AO)

3 40003 Analogue outputs channel 0

40004 Analogue outputs channel 1







Tab. D/35: Output data addressing example 2 (CPX terminal from Fig. D/2)

Index

E-1Festo CPX-FB36-EN en 1611a English

Appendix E

Index

E. Index

E-2 Festo CPX-FB36-EN en 1611a English

Contents

E. Index E-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E. Index


Index

A

Abbreviations, product-specific XIV. . . . . . . . . . . . . . . . . . . . .

Address assignment B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Address space B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Addressing B-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Address assignment B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Addressing example (Remote I/O Modbus®� TCP) D-24. . . . .

AdjustData field size 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Diagnostics mode 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .DIL switches 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IP addressing 1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Network protocol 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C

CEC 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configurationin Remote Controller operating mode 3-20. . . . . . . . . . . . . .with CPX-FMT 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .with EDS file 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .with Generic Ethernet Module 3-11. . . . . . . . . . . . . . . . . . .

ConnectNetwork 1-11, 1-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Power supply 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connection and display components 1-4. . . . . . . . . . . . . . . . .

Connection technology 1-13. . . . . . . . . . . . . . . . . . . . . . . . . . .

CPX-CEC 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CPX-FEC 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E. Index


D

Degree of protection 1-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Diagnostic data 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Diagnostics options 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Diagnostics via LED displays 4-4. . . . . . . . . . . . . . . . . . . . . . . .

Diagnostics via status bits 4-12. . . . . . . . . . . . . . . . . . . . . . . . .

Diagnostics via the I/O diagnostics interface 4-13. . . . . . . . . .

DIL switches 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dismounting 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DLR 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E

Edit, Operating mode 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EtherNet/IP Objects C-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

F

Fail safe mode 3-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FEC 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Force Parameter C-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I

I/O diagnostics interface 4-13. . . . . . . . . . . . . . . . . . . . . . . . . .

Idle mode 3-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IGMP snooping 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Intended use VIII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E. Index


L

LED indicators 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Lines, network 1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M

Mounting 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multicast telegram 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N

NetworkConnection technology 1-13. . . . . . . . . . . . . . . . . . . . . . . . .Network cables 1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Network connectors 1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network connection 1-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network setting saved 1-17. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network settings extended 1-20. . . . . . . . . . . . . . . . . . . . . . . .

Notes on the description XI. . . . . . . . . . . . . . . . . . . . . . . . . . . .

O

Objects, Modbus® TCP D-23. . . . . . . . . . . . . . . . . . . . . . . . . . .

Operating modeRemote controller 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Remote I/O 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E. Index


P

ParameterisationExamples C-45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .via configuration data 3-26. . . . . . . . . . . . . . . . . . . . . . . . . .with CPX-FMT and system start with saved parameters 3-27with PLC user program 3-26. . . . . . . . . . . . . . . . . . . . . . . . . .with the operator unit 3-26. . . . . . . . . . . . . . . . . . . . . . . . . .

PELV 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pictograms XIII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Plug connector 1-13, 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Power supply 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ProtocolDevice Level Ring 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .EtherNet/IP 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IGMP 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Modbus TCP 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Q

QuickConnect 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

R

Router 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

S

Segmentation 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Service X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting IP address 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Status bits 4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Strain relief 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Switch 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E. Index


T

Target group X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical data A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Text designations XIII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

U

usedfor network settings C-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . .for system data and diagnostics C-18. . . . . . . . . . . . . . . . . .for the I/O connection C-13. . . . . . . . . . . . . . . . . . . . . . . . . .Overview C-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User information XII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

W

Web server 3-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E. Index


terminal cpx bus node cpxfb36 - festo usa€¦ · d.6.1 addressing examples for modbus® tcp d-24...

Documents