Terminal CPX Busnode CPX-FB36 - FestoElectronics description Bus node Network protocol EtherNet/IP...

Electronicsdescription

Bus node

Network protocolEtherNet/IPModbus TCP

Industrial Ethernet2-Port

8024075en 1309NH[8024081]

Terminal CPX

Bus node CPX-FB36

Contents and general instructions

IFesto P.BE-CPX-FB36-EN en 1309NH English

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

Version en 1309NH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Designation P.BE-CPX-FB36-EN. . . . . . . . . . . . . . . . . . . . . . .

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

� (Festo AG & Co., 73726 Esslingen, Germany, 2013)Internet: http://www.festo.comE-Mail: [email protected]

Reproduction, distribution and utilisation of this document,as well as the communication of its contents to otherswithout explicit authorisation, is prohibited. Offenders willbe liable for damages. All rights are reserved, in particularthe right to file patent, utility model or registered designapplications.


II Festo P.BE-CPX-FB36-EN en 1309NH English

EtherNet/IP®, Modbus®, RSLogix®, RSNetWorx®, SPEEDCON® and TORX®

are registered trademarks of the respective trademark owners in certain countries.


IIIFesto P.BE-CPX-FB36-EN en 1309NH English

Table of contents

Intended use VII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Target group VIII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Service VIII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Information regarding this description IX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Important user information X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

1.1 Installation instructions 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.1 Electrical connection and display elements 1-4. . . . . . . . . . . . . . . . . . .

1.1.2 Dismantling and mounting of the bus node 1-5. . . . . . . . . . . . . . . . . . .

1.2 Setting the DIL switches on the bus node 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.1 Setting the operating mode and protocol 1-9. . . . . . . . . . . . . . . . . . . .

1.2.2 Setting the diagnostics mode for Remote I/O 1-10. . . . . . . . . . . . . . . . .

1.2.3 Setting the data field size for Remote Controller 1-11. . . . . . . . . . . . . . .

1.2.4 Setting IP addressing 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

1.3.1 General information about networks 1-13. . . . . . . . . . . . . . . . . . . . . . . .

1.3.2 Overview of connections, network connectors and cables 1-14. . . . . . .

1.3.3 Network connections of the CPX-FB36 1-17. . . . . . . . . . . . . . . . . . . . . . .

1.3.4 Setting the IP address 1-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.5 Advanced network settings 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Ensuring protection classIP65/IP67. 1-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 Power supply 1-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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


IV Festo P.BE-CPX-FB36-EN en 1309NH English

2.3 Notes on commissioning 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-10. . . . . . . . . . . . . . . . . .

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

3.1.4 Configuration in the Remote Controller operating mode 3-19. . . . . . . .

3.1.5 Setting up a listen-only connection 3-20. . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Parameterisation 3-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.1 Parameterisation when switching on (system start) 3-22. . . . . . . . . . . .

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

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

3.2.4 Parameterisation with the operator unit 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 savedparameters 3-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Reaction of the outputs in the Fail safe or Idle mode 3-28. . . . . . . . . . . . . . . . . . .

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

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

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

4.1 Summary of diagnostics options 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Diagnostics via LEDs 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 CPX-specific LEDs 4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2 Network-specific LEDs 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.3 Protocol-specific LEDs 4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

4.4 Diagnostics via I/O diagnostic interface 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . .


VFesto P.BE-CPX-FB36-EN en 1309NH English

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

4.6 Diagnostics via Modbus TCP 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7 Error handling 4-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

A.1 Technical data, bus node CPX-FB36 A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

B.2 Addressing B-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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 diagnosis 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 Diagnostics Object C-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.4 Diagnostics Trace Object C-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.5 Diagnostics Trace Status Object C-26. . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.6 General Module 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 operating mode Remote Controller) C-42. . . . . .


VI Festo P.BE-CPX-FB36-EN en 1309NH English

C.5 Examples C-43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5.1 Forcing inputs C-43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5.2 Parameterisation with the general Module Parameter Object C-45. . . .

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 Processing data (groups B and D) D-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.1 Module CPX-FB36 D-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.2 Electric modules D-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.3 Pneumatic modules D-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.4 Technology module CP interface D-14. . . . . . . . . . . . . . . . . . . . . . . . . . .

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

D.4.6 Composition of the data of the I/O diagnostic interface D-18. . . . . . . . .

D.5 Diagnostic memory (groups C and E) D-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.6 Modbus/TCP Objects (group F) D-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.6.1 Addressing examples for ModbusTCP D-23. . . . . . . . . . . . . . . . . . . . . . .

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

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


VIIFesto P.BE-CPX-FB36-EN en 1309NH English

Intended use

The bus node CPX-FB36 documented in this description isexclusively intended for use as a participant in networks withEtherNet/IP or Modbus TCP protocols.

The CPX terminal must only be used as follows:

– As intended in industrial environments;outside of industrial environments, e.g. in commercial andmixed-residential areas, actions to suppress interferencemay have to be taken.

– in original status without unauthorised modifications.Only the conversions or modifications described in thedocumentation supplied with the product are permitted.

– in perfect technical condition.

The limit values specified for pressures, temperatures, elec-trical data, torques etc. must be observed.

If standard ancillary components, such as sensors and actuat-ors, are connected, the specified limits for pressures, temper-atures, electrical data, torques, etc. must be complied with.

• Observe the regulations of the trade associations, Ger-man Technical Control Board (TÜV), VDE stipulations orcorresponding national laws and regulations.


VIII Festo P.BE-CPX-FB36-EN en 1309NH English

Target group

This description is intended exclusively for technicianstrained in control and automation technology, who have ex-perience in installing, commissioning, programming and dia-gnosing participants in networks with EtherNet/IP or Mod-bus TCP protocols.

Service

Please consult your local Festo Service agent if you have anytechnical problems.


IXFesto P.BE-CPX-FB36-EN en 1309NH English

Information regarding this description

Further information regarding EtherNet/IP can be found here:

� www.odva.org

General basic information about the mode of operation, as-sembly, installation and commissioning of CPX terminals canbe found in the CPX system description P.BE.CPX-SYS.

An overview of the structure of the user documentation forthe CPX terminal can be found in the CPX system descriptionP.BE.CPX-SYS.


X Festo P.BE-CPX-FB36-EN en 1309NH English

Important user information

Danger categories

This description includes instructions on the possible dangerswhich can occur if the product is used incorrectly. These in-structions are marked with a signal word (Warning, Caution,etc.), printed on a shaded background and marked addition-ally with a pictogram. A distinction is made between the fol-lowing danger warnings:

Warning... means that failure to observe this instruction may resultin serious personal injury or material damage.

Caution... means that failure to observe this instruction may resultin personal injury or material damage.

Note... means that failure to observe this instruction may resultin material damage.

In addition, the following pictogram marks passages in thetext which describe activities with electrostatically sensitivedevices:

Electrostatically sensitive devices: Incorrect handling maycause damage to devices.


XIFesto P.BE-CPX-FB36-EN en 1309NH English

Marking of special information

The following pictograms mark passages in the text whichcontain special information.

Pictograms

Information:Recommendations, tips and references to other informationsources.

Accessories:Specifications on necessary or useful accessories for theFesto product.

Environment:Information on the environmentally friendly use of Festoproducts.

Text designations

• Bullets denote activities that may be carried out in anydesired order.

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

– Arrowheads indicate general lists.


XII Festo P.BE-CPX-FB36-EN en 1309NH 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”.

AA, AO Analogue output

AE, AI Analogue input

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

Bus nodes A bus node connects the CPX terminal to the fieldbus or network; ittransmits control signals to the connected CPX and pneumatic modulesand monitors their operational capability.

C Output

CEC Codesys controller, e.g. CPX-CEC, applicable for control, configurationand commissioning of CPX terminals.

CODESYS Controller Development System

CP Compact Performance

CP module Collective term for the various modules which can be incorporated inthe CP system (decentralised installation system).

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

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

CPX-MMI Operator unit for commissioning and service purposes.

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


XIIIFesto P.BE-CPX-FB36-EN en 1309NH English


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

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

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

DI Digital input (or “Discrete input”)

DIL switches Miniature switches; dual-in-line switches usually consist of severalswitch elements which can be used to implement settings.

DO Digital output (or “Discrete output”)

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

FEC Front End Controller, e.g. CPX-FEC, can be used 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, Front End Controller (CPX-FEC) and CODESYScontroller (CPX-CEC); function modules are also known as technologymodules.

I Input

I/O diagnostics interface Bus-independent, bi-directional diagnostic interface at I/O level;enables access to the internal data of the CPX terminal.

I/O module Collective term for CPX modules that provide analogue or digital inputsand outputs.

I/Os Analogue or digital inputs and outputs.



XIV Festo P.BE-CPX-FB36-EN en 1309NH English


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

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

Pneumatics interface Interface between CPX modules and pneumatics modules within a CPXterminal.The pneumatics interface is used functionally for the electrical side ofthe CPX terminal.

Pneumatic modules Collective term for the pneumatics modules which can be integratedinto a CPX terminal.Pneumatics modules provide, among other things, outputs (workingports) for connecting actuators, e.g. cylinders.Pneumatics modules form the pneumatic side of the CPX- terminal.

Status bits CPX-internal status information (common diagnostic messages) whichare provided as input signals on the fieldbus of the control system(optional function)

Technology module � Function module



XVFesto P.BE-CPX-FB36-EN en 1309NH English

Data type Quantity 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 -2147483648 …2147483647

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/characters — String

SHORT_STRING 8 bit/characters +8 bit lengthspecification

— String with max. 255characters

STRUCT —1) — Structure of any datatypes

UDINT 32 bit 0 … 4294967296 Unsigned Double Integer

UINT 16 bit 0 … 65.536 Unsigned Integer

USINT 8 bit 0 … 256 Unsigned Short Integer

WORD 16 bit 0000h … FFFFh Bit field

1) Dependent on the data types used.

Tab. 0/4: Data types used


XVI Festo P.BE-CPX-FB36-EN en 1309NH English

Installation

1-1Festo P.BE-CPX-FB36-EN en 1309NH English

Chapter 1

Installation

1. Installation

1-2 Festo P.BE-CPX-FB36-EN en 1309NH English

Table of contents

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

1.1 Installation instructions 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.1 Electrical connection and display elements 1-4. . . . . . . . . . . . . . . . . . .

1.1.2 Dismantling and mounting of the bus node 1-5. . . . . . . . . . . . . . . . . . .

1.2 Setting the DIL switches on the bus node 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.1 Setting the operating mode and protocol 1-9. . . . . . . . . . . . . . . . . . . .

1.2.2 Setting the diagnostics mode for Remote I/O 1-10. . . . . . . . . . . . . . . . .

1.2.3 Setting the data field size for Remote Controller 1-11. . . . . . . . . . . . . . .

1.2.4 Setting IP addressing 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

1.3.1 General information about networks 1-13. . . . . . . . . . . . . . . . . . . . . . . .

1.3.2 Overview of connections, network connectors and cables 1-14. . . . . . .

1.3.3 Network connections of the CPX-FB36 1-17. . . . . . . . . . . . . . . . . . . . . . .

1.3.4 Setting the IP address 1-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.5 Advanced network settings 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Ensuring protection classIP65/IP67. 1-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 Power supply 1-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Installation


1.1 Installation instructions

WarningSwitch off the following components before undertakinginstallation and/or maintenance work:

– Compressed air supply

– Operating voltage supply for electronics/sensors

– Load voltage supply for outputs/valves

In this way, you can avoid:

– sudden uncontrolled movements of loose tubing

– unexpected movements of the connected actuators

– undefined switching states of the electronics

CautionThe CPX bus node contains electrostatically sensitivedevices.

• Therefore, do not touch any components.

• Observe the handling specifications for electrostaticallysensitive devices.

They will help you avoid damage to the electronics.

NoteUse protective caps or blanking plugs to seal unused con-nections. You will then comply with protection classIP65/IP67 (� section 1.4).

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

1. Installation


1.1.1 Electrical connection and display elements

The following connection, setting and display componentscan be found on the CPX bus node CPX-FB36:

1

23

4

1 Protocol and CPX-specific LEDs

2 Network connections X1 and X2(one 4-pin M12 socket each, D-coded)

3 DIL switch with transparent cover

4 Service interface for operator unit(CPX-MMI; V24 interface) und USBadapter (for CPX-FMT)

Fig. 1/1: Connection, setting and display components on the bus node CPX-FB36

1. Installation


1.1.2 Dismantling and mounting of the bus node

The bus node is mounted in an interlinking block of the CPXterminal.

1 Bus nodeCPX-FB36

2 Interlinking blockwith contact rails

3 Torx T10 screws

3

1

2

Fig. 1/2: Dismantling / mounting the bus node

Note• Check the start behaviour of the CPX terminal beforereplacing the bus node.

If the Modify LED (M) illuminates or flashes permanentlyafter the system start, “System start with saved paramet-risation and saved CPX expansion” is set or “Force” is act-ive. In this case parameterisation is not created automatic-ally by the higher-order system when replacing the busnode or CPX terminal during servicing.

• Therefore, verify which settings are required before re-placement and restore these settings after replacement.

1. Installation


Dismantling the bus node 1. Loosen the four screws of the bus node with a Torxscrewdriver size T10.

2. Pull the bus node carefully and without tilting away fromthe contact rails of the interlinking block.

Note• Always use the correct screws for the interlinking block,which depend on whether the block is made of metal orplastic:

– for plastic interlinking blocks:self-tapping screws

– for metal interlinking blocks:screws with metric thread.

Both types of screws are enclosed respectively when orderingthe bus node as a single part.

Mounting the bus node 1. Check the seal and the sealing surfaces between the busnode and interlinking block.

2. Place the bus node in the interlinking block withouttilting. Make sure that the corresponding slots with thecontacting terminals on the bottom of the bus node areabove the contact rails.

3. Push the bus node carefully and without tilting as far aspossible into the interlinking block.

4. Set the screws so that the self-cutting threads can beused.

5. Tighten the screws alternately in diagonally oppositesequence with a Torx screwdriver (size T10). Tighteningtorque:0.9…1.1 Nm.

1. Installation


1.2 Setting the DIL switches on the bus node

The DIL switches on the bus node are used to change thefollowing settings.

1 DIL switchgroup 1:Operating modeand protocol

2 DIL switchgroup 2:Diagnostics modefor remote I/O ornumber of I/Obytes for RemoteController

3 DIL switchgroup 3:IP addressing

1 2

3

Fig. 1/3: DIL switches on the bus node

Changes to the DIL switches only take effect when the busnode is restarted.

The DIL switch cover must be removed to change the settings.

CautionThe CPX bus node contains electrostatically sensitivedevices.

• Do not therefore touch any contacts.

• Observe the handling specifications for electrostaticallysensitive devices.

This will help you avoid damage to the bus node electronics.

1. Installation


Procedure

1. Switch off the power supply.

2. Remove the DIL switch cover.

3. Change the DIL switch settings (� section1.2.1 ff.).

4. Mount the cover.

Remove the DIL switch cover

1. Unscrew the two mounting screws in the switch cover.

2. Lift off the cover.

Mounting the DIL switch cover

1. Place the cover carefully on the bus node.

Note• Make sure that the seal is seated correctly.

2. Tighten the two mounting screws at first by hand andthen with a max. tightening torque of 0.4 Nm.

1. Installation


1.2.1 Setting the operating mode and protocol

• Use DIL switch group 1 (� Fig. 1/11 ).

Operating mode and protocol Setting of DIL switch group 1

Remote I/O operating modeAll functions of the CPX terminal are controlleddirectly via EtherNet/IP or Modbus TCP.A CPX-FEC or CPX-CEC that may be integratedinto the CPX terminal works as a passive functionmodule without controller.

DIL 1.1: OFF(factory setting)

Operating mode Remote ControllerA CPX-FEC or CPX-CEC integrated into the CPXterminal takes over I/O control.

DIL 1.1: ON

EtherNet/IP protocolThe CPX terminal uses the EtherNet/IP protocol.

DIL 1.2: OFF(factory setting)

Modbus TCP protocolThe CPX terminal uses the Modbus/TCPprotocol.

DIL 1.2: ON

Tab. 1/1: Setting the operating mode and protocol

Setting the diagnostics mode is required for the Remote I/Ooperating mode (� chapter1.2.2).

Setting the data field size is required for the Remote Control-ler operating mode (� chapter1.2.3).

1. Installation


1.2.2 Setting the diagnostics mode for Remote I/O


The functions of these DIL switches depend on the set operat-ing mode of the CPX terminal (� Tab. 1/1).

Diagnostics mode for the Remote I/O operatingmode

Setting of DIL switch group 2

The I/O diagnostic interface and the status bits areswitched off(+ 0 I/O bits)

2.1: OFF2.2: OFF(factory setting)

Status bits are switched on(+ +16 E-bits (8 used))

2.1: OFF2.2: ON

The I/O diagnostic interface is switched on 1)

(+ 16 I/O bits)2.1: ON2.2: OFF

Reserved 2.1: ON2.2: ON

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

Tab. 1/2: Setting of the diagnostics mode for the Remote I/O operating mode

During subsequent activation of the diagnostics module(status bits or I/O diagnostics interface), the CPX-internal I/Oimage can be displaced.

The system controller carries out this adjustment automatic-ally. Manual manipulation, e.g. reconfiguration of the CPXterminal or manual adaptation of the hardware and networkconfiguration are not required.

1. Installation


1.2.3 Setting the data field size for Remote Controller


The functions of these DIL switches depend on the set operat-ing mode of the CPX terminal (� Tab. 1/1).

Number of I/O bytes for the Remote Controlleroperating mode

Setting of DIL switch group 2

8 byte I/8 byte O for communication of the bus nodewith the CPX-FEC or CPX-CEC.

2.1: OFF2.2: OFF(factory setting)

Reserved 2.1: ON2.2: OFF

16 byte I/16 byte O for communication of the bus nodewith the CPX-FEC or CPX-CEC.

2.1: OFF2.2: ON

Reserved 2.1: ON2.2: ON

Tab. 1/3: Setting the number of I/O bytes for the Remote Controller operating mode

The assignment of the I/O addresses and diagnostics ad-dresses can be changed as needed by using the configurationand programming software (e.g. Rockwell RSLogix).

1. Installation


1.2.4 Setting IP addressing


By using DIL switch group 3 you can set the type of address-ing or the IP address of the bus node.

• Set all slide switches to “OFF”, so that when the bus nodeis switched on it receives a dynamic or saved IP address(� section1.3.4).

• Use DIL switches 1 ... 8 to define a binary number otherthan 0 and 255.This number is used as part of the IP address when turn-ing on the bus node.

Dynamic/saved addressing Fixed addressing

12

34

56

78 Setting:

All switches OFF(factory setting)

12

34

56

78 Setting:Host ID ofthe IP address

Tab. 1/4: Settings for addressing type or IP address

Dynamic addressing is set via DHCP/BOOTP by default.If all of the switches in DIL switch group 3 are set to “ON”when switching on the bus node, all IP parameters will bereset to the factory setting.

• Note the detailed information on addressing in sec-tion 1.3.4.

1. Installation


1.3 Connecting to the network

1.3.1 General information about networks

NoteSub-assemblies with Ethernet interfaces should only beoperated in networks if all connected network componentsare supplied by PELV power supplies or integrated powersupplies with equivalent protection.

Installation guidelines

The installation guidelines can be obtained via the ODVA userorganisation:

� Internet: http://www.odva.org

Observe the instructions in these documents.

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 greater network expan-sions.

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

1. Installation


Switches and routers for Industrial Ethernet are available onthe market from various companies. There are many IP20,IP65 or IP67 components.

– Unmanaged Switches:for small network solutions with a low network load orminimal requirements for deterministics

– Managed Switches:for comprehensive network solutions, with diagnosticsand monitoring functions

1.3.2 Overview of connections, network connectors and cables

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

Transmission errors can be caused by:

– faulty screened connection

– branches

– transmission over distances which are too long

– inappropriate cables

Observe the cable specification!

Bus nodes Connection technology Network connectors

CPX-FB36 2 x M12 socket, D-coded, female, 4-pin,corresponding to IEC 61076-2

Festo connector,type NECU-M-S-D12G4-C2-ET

� Internet: www.festo.com/catalogue/

Tab. 1/5: Overview of connection technology and network plugs

1. Installation


RJ45 to M12 converter

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

Example:Connections between devices in the control cabinet with RJ45connection and IP65/IP67 devices with M12 connection.

Cable specification

Use shielded Industrial Ethernet lines of categoryCat 5/Cat 5e or higher (� Tab. 1/6).

Crossover detection The CPX bus node supports the “Crossover detection” func-tion (Auto-MDI/MDI-X). Patch cables or crossover cables canbe optionally used for connecting the bus node to your net-work or a PC. The CPX-FB36 automatically adapts the pro-tective circuit of network connections X1 and X2.

NoteIf the “QuickConnect” function has been activated (� sec-tion 2.1.2 ), the crossover detection function is not avail-able.

In this case the CPX-FB36 sets the pin allocation of networkconnection X2 to “Crossover”.

• Use suitable cables when the crossover detection functionis deactivated:

– Crossover cable with the same port assignment as theconnected equipment

– Patch cable with a different port assignment to theconnected equipment

1. Installation


CPX-FB36 + ...D12G4... Cable specification1)

Cable type Ethernet twisted pair cable, shielded (Shielded Twisted Pair, STP)

Transmission class Category Cat 5/Cat 5e (link class)

Cable diameter 6 ... 8 mm

Wire cross section 0.14 ... 0.75 mm2; 22 AWG2)

Connection length max. 100 m

1) Length corresponding to specification for EtherNet/IP networks (EtherNet/IP Installation Guide),

based on ISO/IEC 11801, ANSI/TIA/EIA-568 (� section 1.3.1)

� Internet: www.odva.org2) Required for max. connection length between network participants

Tab. 1/6: Cable specification overview

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

• Make sure that the network cables are provided withstrain relief.

• Comply with the corresponding regulations set out inEN 60204 part 1.

1. Installation


1.3.3 Network connections of the CPX-FB36

There are two 4-pin, D-coded M12 sockets on the bus nodefor the network connection.The sockets are compatible with SPEEDCON® plugs.

Network connection X1

• Connect the CPX-FB36 via connection X1.

M12 socketEtherNet/IP

Pin allocation Signal Pin equivalent withRJ45 plug

1. TX+2. RX+3. TX–4. RX–Housing

Transmitted data+Received data+Transmitted data–Received data–Screening, FE

1326

Tab. 1/7: Pin allocation of network connection X1 on the CPX-FB36 (M12 4-pin)

Network connection X2

• Connect the CPX-FB36 to the next device via connec-tion X2.

M12 socketEtherNet/IP

Pin allocation Signal Pin equivalent withRJ45 plug

1. RX+2. TX+3. RX–4. TX–Housing

Received data+Transmitted data+Received data–Transmitted data–Screening, FE

3162

Tab. 1/8: Pin allocation of network connection X2 on the CPX-FB36 (M12 4-pin)

NoteWhen crossover detection is activated, the bus node auto-matically exchanges the RX and TX connections.

1. Installation


Connection with plug from Festo

The CPX terminal is connected to the network with Festoplugs, type NECU-M-S-D12G4-C2-ET.The plugs are designed for network cables measuring6...8 mm in diameter.

To comply with protection class IP65/IP67:

• Use Festo plugs

• Seal unused interfaces (� section1.4)

1.3.4 Setting the IP address

The IP address of bus node CPX-FB36 is alternatively set via:

– Dynamic addressing via DHCP/BOOTP (factory setting)

– Saved network settings

– Addressing via DIL switch

NoteWhen changes are made to the network settings of theCPX-FB36 via DIL switch, the Modify LED “M” flashes yel-low.

• Perform a restart of the bus node so that the modifiednetwork settings are applied.

1. Installation


Dynamic addressing via DHCP/BOOTP

• Make sure that a DHCP/BOOTP server is located in thenetwork.

To set the dynamic addressing:

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

2. Alternatively activate DHCP/BOOTP in the bus node via:

– Operator unit CPX-MMI

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

– Programme “BOOTP-DHCP Server” from RockwellAutomation

Saved network settings

The CPX-FB36 offers the option to save the network settingsin a non-volatile memory of the bus node. DHCP/BOOTP isthereby deactivated.

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

2. Alternatively change the network settings via:


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

– Programme “BOOTP-DHCP Server” from RockwellAutomation

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

1. Installation


Addressing via DIL switch

Tip When addressing via DIL switch the bus node obtains a fixedIP address.This setting is recommended for test purposes during com-missioning or for small networks.

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

– Octets 1 ... 3 (saved in the bus node)

– Octet 4 through the setting of DIL switch group 3(� Tab. 1/9)

• Use DIL switch group 3 to define a binary numberbetween 1 and 254. This number is then used as the 4thoctet of the IP address when turning on the bus node.

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 switches in DIL switch group 3 are set to “ON”when switching on the bus node, all IP 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 of the CPX-FB36

• Alternatively change the first 3 octets of the IP addressvia:


– Festo Maintenance Tool CPX-FMT

– Access to corresponding EtherNet/IP objects

The network mask and gateway are set by using the corres-ponding CPX parameters.

1. Installation


1.3.5 Advanced network settings

The following settings for the network connection can be im-plemented via Ethernet link objects (� appendixC.2.4).

Automatic setting When set to the factory setting the CPX-FB36 automaticallydetects the baud rate and duplex mode.

Baud rate

Setting via attribute 6 (Forced Interface Speed) of the Ether-net 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 protection classIP65/IP67.

In order to comply with protection class IP65/IP67, seal anyunused sockets with the appropriate plugs or cover caps.

Connection Port IP65/IP67 Cover IP65/IP67 1)

X1, X2 (M12) Festo connector,type NECU-M-S-D12G4-C2-ET

Cover cap from Festo,type ISK-M12

Service interface (M12) forCPX-MMI + CPX-FMT

Connecting cable and plugof the CPX-MMI or CPX-FMT

Cover cap from Festo,type ISK-M12 2)

1) if connection is not used2) included in scope of delivery, always cover unused connection

Tab. 1/11: Connections and covers for protection class IP65/IP67

1. Installation


1.5 Power supply

WarningElectric shock

Injury to people, damage to the machine and system

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

• Observe the general requirements in accordance withIEC 60204-1 for PELV circuits.

• Use only voltage sources that guarantee a reliable elec-tric disconnection of operating and load voltage in ac-cordance with IEC 60204-1.

• Always connect all circuits for the operating and loadvoltage supplies UEL/SEN, UVAL and UOUT.

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

Observe the information on power supply (� electrical con-nection) as well as on the earthing measures to be carried out(� potential equalisation) contained in the CPX system de-scription.

Preparing for commissioning


Chapter 2

Preparing for commissioning

2. Preparing for commissioning


Table of 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-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

2.3 Notes on commissioning 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 pre-dominantly used in automation technology.

The EtherNet/IP protocol is activated with DILswitch 1.2 = OFF. The bus node is then identified with thedesignation: FB36 - EtherNet IP Remote-IO

After switching the protocol (� section 1.2.1) the followingunmodified parameters are available:

– IP address

– Diagnostics mode

– System parameters

The DIL switch function remains unchanged.

Retentive bus-specific parameters are only active if the relev-ant protocol is selected (� section 1.2.1).

Parameterisation examples can be found in appendix C.5.

2.1.1 Multicast telegram

EtherNet/IP uses IP Multicast telegrams as standard fortransferring process data. An advantage of Multicast com-pared to Unicast is that a telegram can be received by mul-tiple participants.

Simple switches, however, cannot distinguish to which parti-cipant a Multicast telegram is to be transferred. Therefore,these switches send the Multicast telegrams to all devices inthe network.

This results in an EtherNet/IP participant receiving numerousunnecessary telegrams, which must then be discarded fromthe device. This can reduce the response times of the parti-cipants. The demand on the network bandwidth increases.



This does not pose a problem for smaller networks; the per-formance 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 Mul-ticast telegrams are transferred. This allows unnecessaryMulticast traffic to be avoided.

• Activate this function in all switches/routers used.

• Configure at least one switch so that cyclical IGMP quer-ies 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 function QuickConnect (QC) enables a quick-er initialisation of the CPX terminal and a fast connection set-up to 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.



NoteQuickConnect only works if this function is supported byall participating devices.

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

Using QuickConnect:

• Deactivate Auto-Negotiation in the bus node for both net-work connections X1 and X2.

– Baud rate = 100 Mbit/s

– Duplex mode = Full-Duplex� Attribute 6d of the Ethernet link object (Inter-face Control).

• Deactivate Auto-Negotiation and crossover detection forthe corresponding network connection of the counterpartstation (e.g. switch connection).

– Baud rate for connection of the counterpart station =100 Mbit/s

– Duplex mode = Full-Duplex

• Activate QuickConnect via attribute 12 of the TCP/IP inter-face object. (The QuickConnect function in the bus node isin a deactivated state when delivered.)

• Activate QuickConnect in the PLC or in the control pro-gram.

Simplified configuration of QuickConnect on CPX-FB36:

• Set the CPX parameter “IP configuration” to“With saved parameters and QuickConnect”.

Selecting this setting activates QuickConnect and deactivatesAuto-Negotiation for both network connections.



Crossover detection is automatically deactivated in the busnode when Auto-Negotiation is deactivated.Network connection X1 runs in the MDI-mode here and net-work connection X2 runs in the 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 of the Ether-Net/IP specification. When switched on, the bus node re-quires less than 350 ms to accept a TCP connection.

NoteDue to the rapid establishment of the TCP connection, thedetection of already used IP addresses (IP Address Con-flict Detection, ACD) is not executed completely. This canlead to multiple assigned IP addresses only being detectedat a late stage. This can impair the function of the network.



QuickConnect is available for the following modules.

CPX modules Type

Bus node CPX-FB36 CPX-FB36

Digital 4-off input module CPX-4DE


Digital 8-off input module withchannel diagnostics

CPX-8DE-D

Digital 8-off input module, n-switching CPX-8NDE


Digital 16-off input module with channel dia-gnostics

CPX-16DE-D

Digital 16-off input modulewith terminal strip

CPX-L-16DE-16-KL-3POL

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 terminalstrip

CPX-L-8DE-8DA-16-KL-3POL

Analogue 2-off input module(voltage/current)

CPX-2AE-U-I

Analogue 2-off output module(voltage/current)

CPX-2AA-U-I

Analogue 4-off input module (current) CPX-4AE-I

Tab. 2/1: CPX modules which support QuickConnect



QuickConnect is available for the following pneumatics inter-faces and modules.

Pneumatic interfaces Type

Pneumatics interface for VTSA orVTSA-F pneumatics

VABA-10S6-x1

Pneumatics interface for MPA-S valves VMPA-FB-EPL-...

Pneumatics interface for MPA-F valves VMPAF-FB-EPL-...

Pneumatics interface for MPA-L valves VMPAL-FB-EPL-...VMPAL-EPL-CPX

Tab. 2/2: Pneumatics interfaces which supportQuickConnect

Pneumatic modules Type

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

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

MPA1 pneumatics module with diagnosticfunction

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

MPA2 pneumatics module with diagnosticfunction

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

Tab. 2/3: Pneumatics modules which supportQuickConnect

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 by using ringtopology as there are redundant communication pathsbetween two devices. A cable or communication faultbetween two devices will therefore not result in communica-tion failure. Only two faults 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-compatible devices in a ring.Otherwise, the time required for automatic elimination ofa fault 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 func-tion is normally executed by an EtherNet/IP scanner.

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



2.2 Modbus/TCP protocol

Modbus is an open communication protocol based on themaster-slave architecture. This is a standard for communica-tion via TCP/IP in automation technology.

The Modbus/TCP protocol is activated with DILswitch 1.2 = ON. The bus node is then identified with the des-ignation: FB36-MB - Modbus TCP Remote-IO

After switching the protocol (� section 1.2.1) the followingunmodified parameters are available:

– IP address

– Diagnostics mode

– System parameters

The DIL switch function remains unchanged.

Retentive bus-specific parameters are only active if the relev-ant protocol is selected (� section 1.2.1).

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

In order to configure the CPX terminal for Modbus/TCP, youwill require the Modbus addresses of the data and of the I/Osof the CPX terminal (� appendix D).

Addressing examples can be found in appendix D.6.1.



2.3 Notes on commissioning the CPX-FB36

Configuration of the CPX terminal demands a very accurateprocedure, as different configuration specifications are some-times necessary for each station in the network, due to themodular structure.

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

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

The following section describes the configuration andcommissioning procedure using the example ofRockwell/Allen-Bradley controllers (PLC) via the RockwellRSLogix software platform.

2.3.1 Requirements for commissioning

– Installation of the bus node is complete (� chapter 1)

– 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

WarningBefore switching on:

• Make sure that the requirements for commissioninghave been met. Also observe section 3.1.2, especiallyregarding the DIL switch setting.

During operation:

• Do not alter the DIL switch setting. This will prevent acci-dental and uncontrolled movements of the connectedactuators and undefined switching states of the elec-tronics.

Note• Please observe the switching-on instructions in themanual for your controller.

2.3.3 Normal operating status

When the CPX terminal is switched on the status LEDs(� Fig. 4/1) indicate the operating status and correct func-tion of the bus node and of fieldbus communication as a func-tion of the configuration.

– Bus node not configured� Tab. 2/4

– Bus node configured and higher-order PLC is in stopmode� Tab. 2/5

– Bus node configured and higher-order PLC is in run mode� Tab. 2/6

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



Bus node not configured

LED display Status and significance

MS illuminates green:– Device is ready to operate

PS illuminates green:– Voltage supply (Power System, PS) is OK– Operating voltage present

(in the approved range)

NS flashes green:– Fieldbus communication present (“Online”

operating status), but not configured.This is correct in this case because the bus nodeis not configured.

PL illuminates green:– Load voltage present (in the approved range) 1)

TP1/TP2 illuminates green:– 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 ap-

proved range) 1)

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

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



Bus node configured - PLC in stop mode


MS illuminates green:– Module status (MS) is error free

PS illuminates green:– Voltage supply (Power System, PS) is OK– Operating voltage applied


NS illuminates green:– Network status (NS) is error free (“Online”

operating status)– Communication with the fieldbus and with the

PLC is OK



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

approved range) 1)


Tab. 2/5: Status LEDs after switch on – bus nodeconfigured, PLC in stop mode



Bus node configured - PLC in run mode


MS illuminates green:– Module status (MS) is error free

PS illuminates green:– Voltage supply (Power System, PS) is OK– Operating voltage applied


NS illuminates green:– Network status (NS) is error free (“Online”

operating status)– Communication with the fieldbus and with the

PLC is OK



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

approved range) 1)


Tab. 2/6: Status LEDs after switch on – bus nodeconfigured, PLC in 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 library (EDSfor electronic data sheet).

The following options are available for expanding an EDS lib-rary:

– Installing EDS files

– Entering participant properties manually

– Importing participant properties

When the CPX terminal has been registered as a potentialnetwork participant, it can be added to a network.

Commissioning


Chapter 3

Commissioning

3. Commissioning


Table of 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-10. . . . . . . . . . . . . . . . . .

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

3.1.4 Configuration in the Remote Controller operating mode 3-19. . . . . . . .

3.1.5 Setting up a listen-only connection 3-20. . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Parameterisation 3-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.1 Parameterisation when switching on (system start) 3-22. . . . . . . . . . . .

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

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

3.2.4 Parameterisation with the operator unit 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 savedparameters 3-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Reaction of the outputs in the Fail safe or Idle mode 3-28. . . . . . . . . . . . . . . . . . .

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

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

3. Commissioning


3.1 Configuration

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

Method Description Benefits Disadvantages

Configuration with EDSfile� section 3.1.1

Installation ofparticipant propertiesfor the CPX terminal inthe “RSLogix 5000”configuration program.

– With the exceptionof the I/O datalength, the entireconfiguration istransferred from theEDS file.

– Not available with allEtherNet/IPmasters.

– Parameterisation issaved locally in theCPX terminal and islost if the terminal isreplaced.1)

Configuration withGeneric EthernetModule� section 3.1.2

Creation of a newparticipant and manualconfiguration in the“RSLogix 5000”configuration program.

– Works with allversions of RSLogix.

– All settings must beentered manually.

Configuration withCPX-FMT� section 3.1.3

Export of the CPXterminal settings byCPX-FMT and import ofthe settings to the“RSLogix 5000”configuration program.

– Transfer of theexistingconfiguration of theparticipant andparameterisation ofthe CPX Terminal.

Tab. 3/1: Configuration methods

3. Commissioning


3.1.1 Configuration with EDS file

This section describes the commissioning procedure forEtherNet/IP with an Allen-Bradley controller and the “RSLogix5000” program from Rockwell.

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

Obtaining EDS files

• Use the following EDS files for the CPX terminal withCPX-FB36.

File type File name Language Description

EDS cpx_FB36.eds

cpx_FB36RC.eds

English Provides the communication adapter in theconfiguration program.File with information for the Remote Controlleroperating mode.

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

Tab. 3/2: Configuration files for CPX-FB36

EDS- files Source� www.festo.com/sp

1. Enter “CPX-FB36” in the search field.

2. Select the “Firmware and drivers” tab.

3. Click “Device description file”.

4. Select a directory and save the ZIP file.

Icon files Use icon files (included in the ZIP file) to assign icons to theCPX terminal and CPX modules.(Dependent on the configuration program used).

3. Commissioning


Registering the EDS file in RSLogix

1. Start the program RSLogix.

2. Launch the EDS wizard by selecting “EDS Hardware In-stallation Tool” from the “Tools” menu.

1

1 Menu command “EDS Hardware Installation Tool”

Fig. 3/1: Launching the EDS wizard

3. Select the option “Register an EDS-file(s)”.

3. Commissioning


Fig. 3/2: EDS wizard - Options

4. Click the “Next >” button.

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

3. Commissioning


5. Select one of the following options:

– Register a single file

– Register a directory of EDS files

6. Click “Browse” to select the directory and name of theEDS file.

7. Click the “Next >” button.

The procedure for registering the bus node in “RSLogix” iscomplete.

Integrating participants in a project

The integration of the bus node in a new RSLogix project canonly be implemented if there is no online connection betweenRSLogix and the controller (� “Communications”� “Gooffline”).

1. In the “Controller Organizer” window of the “RSLogix5000” program, right-click on “Ethernet” under the “I/OConfiguration” branch.

Fig. 3/4: Context menu in the “Controller Organizer”window

3. Commissioning


2. Select the command “New Module...” from the contextmenu.

This opens the dialogue window “Select Module Type”.

3. Select the “Catalog” tab and choose the module with thedescription “CPX-FB36 Ethernet Module” from the bottomtable.

Fig. 3/5: Integrating bus node CPX-FB36

4. Confirm your selection by pressing “Create”.

Configuring a participant

1. In the “Controller Organizer” window right-click on thenewly integrated module and select the “Properties” com-mand in the context menu.

This opens the dialogue window “Module Properties”.

2. Check and alter the IP address if necessary.

3. Click the “Change” button.

This opens the dialogue window “Module Definition”.

3. Commissioning


4. Enter the correct length of the CPX I/O data in the “Size”field.

This value can either be calculated or retrieved usingCPX-FMT or a web server.

The basic configuration of the CPX terminal in the project isnow complete.

• Parameterise the modules and valve terminals used in theCPX terminal (� chapter 3.2).

3. Commissioning


3.1.2 Configuration with Generic Ethernet Module

This section describes the manual configuration process of aparticipant via the “RSLogix” program using a “Generic Ether-net Module”.

Integrating participants in a project

The integration of the bus node in a new RSLogix project canonly be implemented if there is no online connection betweenRSLogix and the controller (� “Communications”� “Gooffline”).

1. In the “Controller Organizer” window of the “RSLogix”program, right-click on “Ethernet” under the “I/O Config-uration” branch (� Fig. 3/4).

2. Select the option “New Module” from the context menu.

This opens the dialogue window “Select Module Type”.

3. Select the “Catalog” tab and choose the module with thedescription “Generic Ethernet Module” from the bottomtable.

Fig. 3/6: Integrating a bus node as a Generic EthernetModule

3. Commissioning


4. Confirm your selection by pressing “Create”.

Configuring a participant

1. In the “Controller Organizer” window right-click on thenewly integrated module and select the “Properties” com-mand in the context menu.

This opens the dialogue window “Module Properties”.

1 Name(freely selectable)

2 Connectionparameters of theAssemblylnstances

3 Size of theAssemblyInstances

4 IP address

5 Data format

1 2

345

Fig. 3/7: “Module Properties” dialogue window

2. Enter a name for the bus node1.

3. Select one of the following data formats from the list field“Comm Format”5:

– DATA - SINT

– DATA - INT

3. Commissioning


4. Enter the following values in the “Assembly Instance”fields2 depending on the data format.

Data format DATA - SINT DATA - INT

Input 101 111

Output 100 110

Configuration 102 102

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

5. Enter the following values in the “Size” fields3 depend-ing on the operating mode.

Operatingmode

Values

Remote I/O For “Input” and “Output” the number ofallocated inputs/outputs of the CPXterminal:– for data format SINT: in bytes– for data format INT: in words(� Appendix Tab. B/9)

For “Configuration”:– the number of memory slots occupied by

CPX parametersor– 0 (standard setting)

Configuration Assembly not used

RemoteController

For “Input” and “Output” the number ofinputs and outputs set on the CPX-FB36:– for data format SINT: in bytes– for data format INT: in words(� chapter 1.2.3, Tab. 1/3)

For “Configuration”:– 0 (standard setting)

Configuration Assembly not used

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

3. Commissioning


Note for Remote I/O operating modeThe “RSLogix” program does not allow the input “0” as adata length (size) for inputs and outputs.

When using a CPX terminal that does not have any inputs:

• Activate the status bits with the help of DIL switchgroup 2 (� Tab. 1/2)

The following settings then apply for the input data:

– for SINT format: Size = 2

– for INT format: Size = 1

6. Enter an “IP address”4.

7. Confirm all entries by selecting “Apply”.

8. Close the “Module Properties” dialogue window by press-ing “OK”.

Using participant properties

• Use the following data in your controller.

Benefit Description

Vendor name Festo Corporation

Vendor ID 26 = 1Ah

Device Type 12 = 0Ch

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

14026 = 36CAh14027 = 36CBh

Major Revision 1

Input size / output size Depends on CPX equipment

Tab. 3/5: Participant properties - Part 1

3. Commissioning


Benefit Description

Assembly Instances– Input– Output– Configuration

SINT format101100102

INT format111110102

Product name CPX-FB36 Remote I/OCPX-FB36 Remote Controller

Advanced EtherNet/IP participant properties

Request Packet Interval (RPI) ≥ 1 ms

Connections:– Total of all connections– Exclusive Owner– Input only– Listen only

Max. 32Max. 1Max. 32Max. 31 (there has to be simultaneously at least1 Excl.Owner or an input only connection)

Tab. 3/6: Participant properties - Part 2

This basic configuration of the CPX terminal in the network isnow complete.

Information about parameterisation of the modules and valveterminals used in the CPX terminal can be found inchapter 3.2.

3. Commissioning


3.1.3 Configuration with CPX-FMT

With the help of the CPX Festo Maintenance Tool (CPX-FMT) itis possible to export the configuration and complete paramet-erisation of a CPX terminal to a file.

This file can then be imported as an RSLogix project.

Exporting a configuration from CPX-FMT

The CPX-FMT software is available online� www.festo.com/sp/cpx� Engineering Software.

1. Start the “CPX-FMT” program.

2. Make sure there is an Ethernet connection between theCPX-FMT and the CPX terminal.

3. Activate the online function to transfer the current config-uration of the bus node to the PC.

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

If you do not want to use this online function, you can alsoconfigure the CPX terminal offline.

Modifications are also possible after importing the project tothe “RSLogix” program.

3. Commissioning


5. Open the dialogue window for exporting the configurationby selecting “File” > “Export” > “RSLogix (.L5K)” (File > Ex-port > RSLogix (.L5K)).

Fig. 3/8: Exporting the configuration for “RSLogix”

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

Importing the configuration to “RSLogix”

1. Start the program “RSLogix”.

2. Click “Open” in the “File” menu and select the saved L5Kfile.

3. Click “Open”.

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

5. Click “Import”.

The CPX-FMT file is imported into a new RSLogix project(.ACD) as an Ethernet module.

3. Commissioning


Integrating the CPX terminal into an existingRSLogix project

The CPX terminal which is configured and parameterised un-der CPX-FMT appears in the “RSLogix 5000” program as anew Ethernet module.

To integrate this module into an existing RSLogix project:

1. Right-click on the Ethernet module and select the “Copy”command from the context menu.

Fig. 3/9: Copy the Ethernet module

3. Commissioning


2. Open an RSLogix project to integrate the imported Ether-net module.

3. Right-click on “Ethernet” in the existing RSLogix projectand select the “Paste” command from the context menu.

Fig. 3/10: Inserting an Ethernet module

All of the necessary settings of the CPX terminal are trans-ferred to the RSLogix project. This includes, among otherthings, I/O data lengths and IP configuration, as well as allmodule and system parameters.

The basic configuration and parameterisation of the CPX ter-minal in the network is now complete.

To change the parameterisation of the modules and valveterminals used in the CPX terminal, use the “RSLogix” pro-gram.

3. Commissioning


3.1.4 Configuration in the Remote Controller operating mode

When using a CPX-FEC or CPX-CEC in your CPX terminal, theCPX-FB36 is to be used as the Remote Controller.

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 or 16output bytes (dependent on the switch position DIL 2.2� Tab. 1/2).These inputs and outputs are available to the control pro-gram of the CPX-FEC or CPX-CEC.

To use the Remote Controller operating mode:

1. Use DIL switch group 1 to set the bus node to the RemoteController operating mode and select an EtherNet/IP orModbus TCP protocol (� chapter 1.2.1).

– DIL 1.1: ON

– DIL 1.2: OFF (EtherNet/IP protocol)DIL 1.2: ON (Modbus TCP protocol)

2. Use DIL switch group 2 to set the required data field size(� chapter 1.2.3).

3. Follow the instructions in chapter 3.1.1 and 3.1.2 for com-missioning with the “RSLogix” program.

The bus node is thus configured as remote controller.

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 your CPX terminal and set the network addressing(� chapter 1.3.4).

2. Establish a connection to the bus node. To do this, use theprofile “GenericEthernet Device” in the “RSLogix” pro-gram (� chapter 3.1.2).

3. Open the “Module Properties” dialogue window.

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

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

Benefit Assembly Instance Size

Input 101 Number of inputs seton the bus node

Output 1 0

Configura-tion

102 (ConfigurationAssembly)

0

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

6. Enter the IP address of the bus node.

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.

Parameterisation of the CPX-FB36 influences the behaviourof the CPX terminal.

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 fault 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 when switching on (system start)

Parameterisation of the CPX terminal is initially dependent onthe setting of the “System start” parameter. This parameterestablishes whether the default parameters or the paramet-ers saved by the user in the bus node are used when switch-ing 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 switching onthe CPX terminal

System start with 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 overwrit-ten accidentally by the controller.

• Prevent this by changing the “Configuration” connectionparameter using the “RSLogix” programme.

3. Commissioning


To change the “Configuration” connection parameter usingthe “RSLogix” programme, proceed as follows:

1. Make sure there is no online connection between RSLogixand the controller (� “Communications”� “Go offline”).

2. Double-click the “Ethernet” branch in the “Controller Or-ganizer” window to open the “Module Properties” dia-logue window.

1 “Assembly-lnstance” connec-tion parameterfor “Configura-tion”

1

Fig. 3/11: “Module Properties” dialogue window

3. Enter the value “0” for “Configuration” under the As-sembly Instance “Connection Parameters” field.

4. Close the “Module Properties” dialogue window by press-ing “Finish >>”.

The setting “System start with saved parameters” is indicatedby the permanent illumination of the M-LED on the bus nodeafter the system has started.

3. Commissioning


Replacing the bus node

When replacing a bus node with the setting “System startwith saved parameters”, the CPX terminal is not paramet-erised automatically by the higher-order controller.

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 parameterisa-tion to the new bus node. Use the command “Load set-tings...” in the CPX menu.

3. Enable all settings in the “Load” window and start thetransfer to the bus node by pressing “OK”.

3. Commissioning


3.2.2 Methods of parameterisation

Method Description Benefits Disadvantages

Parameterisation viaconfiguration data(Configuration Assembly)� section 3.2.3

Exportparameterisation ofthe CPX terminal byusing CPX-FMT.Import the settings inthe programme“RSLogix”.

– Convenient transferof the completeconfiguration for aCPX terminal.

Parameterisation with theoperator unit CPX-MMI� section 3.2.4

Parameterisation iscarried out withentries via the menus.

– Convenientparameterisationvia menunavigation (plaintext).

– Parameterisation ofthe CPX terminal issaved locally in thebus node and is lostwhen replaced.1)

Parameterisation in thePLC user program� section 3.2.5

Parameterisationthrough explicitmessaging;parameters are savedin the PLC.

– Parameters arereloaded afterevery restart andare therefore alsoretained if thedevice is replaced.

– Requirement: Userprogram required.

Parameterisation usingCPX-FMT and system startwith saved parameters� section 3.2.6

Parameterisation iscarried out withentries via the menus.Parameters are saveddirectly in theCPX-FB36.Start with savedparameters necessary.

– Fast, simpleparameterisationduringcommissioning fortesting theparameters.

– Parameterisation ofthe CPX terminal issaved locally in thebus node and is lostwhen replaced.1)

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

Tab. 3/8: 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 As-sembly) corresponds to the method for configuration withCPX-FMT and transfer of all parameters to the “RSLogix” pro-gram (� section 3.1.3).

3.2.4 Parameterisation with the operator unit CPX-MMI

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

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

3.2.5 Parameterisation in the PLC user program

Program-controlled access to parameters is effected via “Ex-plicit Messaging”. The addresses of the EtherNet/IP objectmodel that are required for this can be found in Appendix C.1.

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

3. Commissioning


3.2.6 Parameterisation using CPX-FMT and system start with savedparameters

Parameterisation corresponds to the method for configura-tion with CPX-FMT and transfer of all parameters to the“RSLogix” program (� section 3.1.3).

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

3. Commissioning


3.3 Reaction of the outputs in the Fail safe 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 assume inthe event of fieldbus communication faults.

In this status, the following applies:

– Inputs are transmitted

– Output channels of the participants are no longer up-dated

In the Fail safe or Idle mode, outputs can assume one of thefollowing states:

Digital outputs/valves Analogue outputs

Freeze current status Freeze current status

Reset output Desired analogue value

Set output

Tab. 3/9: Possible states in the Fail safe/Idle mode

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

Further information can be found in the CPX system descrip-tion (� 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/12: Web server of the CPX-FB36

Procedure

1. Open an Internet browser of your choice on a PC that isconnected to the network.

2. In the address bar of the Internet browser enter the IPaddress of the bus node as follows:http://192.168.2.xxx

3. Commissioning


3.5 Checklist for commissioning a CPX terminal

• Please observe the general commissioning instructions inthe CPX system description.

• Check the DIL switch settings and the network configura-tion before using and replacing CPX terminals.

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

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

• Make sure that the desired parameterisation of the CPXterminal in the start-up phase or after network interrup-tions 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.

• Use spot checks if necessary to check the parameterisa-tion, either with a configuration program (e.g. RSLogix) orwith an operator unit (e.g.B. CPX-MMI).

Diagnostics


Chapter 4

Diagnostics

4. Diagnostics


Table of contents

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

4.1 Summary of diagnostics options 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Diagnostics via LEDs 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 CPX-specific LEDs 4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2 Network-specific LEDs 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.3 Protocol-specific LEDs 4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

4.4 Diagnostics via I/O diagnostic interface 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

4.6 Diagnostics via Modbus TCP 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7 Error handling 4-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4. Diagnostics


4.1 Summary of diagnostics options

The CPX terminal provides comprehensive and user-friendlyoptions for diagnostics and error handling. The following optionsare available, depending on the configuration:

Diagnosticsoption

Brief description Benefits Detailed de-scription

LED display The LEDs show directlyconfiguration errors, hardwareerrors, bus errors, etc.

Fast “On-the-spot” recognitionof errors

Section 4.2

Status bits Internal inputs that supplycoded common diagnosticmessages.

Fast access to error messages,irrespective of the module andmaster.

Section 4.3 andCPX systemdescription

I/Odiagnosticsinterface

The I/O diagnostic interface isa bus-independent diagnosticinterface at I/O level whichpermits access to internal dataof the CPX terminal (16 inputsand 16 outputs).

Detailed error detectionirrespective of the fieldbusused.

Section 4.4 andCPX systemdescription

Diagnostics viaEtherNet/IP

Access to all system data ofthe CPX terminal via thefieldbus.

Detailed module-related andchannel-related error detectionas well as access to thediagnostic memory in theonline mode of theprogramming/configurationsoftware and in the PLC userprogram.

Appendix B(EtherNet/IPObjects)

Diagnostics viathe operatorunit

Operator unit CPX-MMI forconvenient and menu-drivendisplay of diagnosticinformation.

Fast “On-site” error detection Operator unitdescription

Tab. 4/1: Diagnostics options

NoteObserve that the diagnostic information displayed de-pends on the parameterisation of the CPX terminal.

4. Diagnostics


4.2 Diagnostics via LEDs

LEDs for the diagnostics of the CPX terminal are available onthe bus node as well as on the individual modules.

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

LEDs at the bus node CPX-FB36

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

1 CPX-specific LEDs

PS: Power system

PL: Power Load

SF: System Failure

M: Modifiy

2 Bus status LEDs

MS: Module Status

NS: Network Status

TPx:Link/Traffic 1/2

PS

PL

SF

MS

NS

M

1

2PS

PL

SF

MS

NS

TP1

M

TP2

TP2

TP1

Fig. 4/1: LEDs on the CPX bus node

4. Diagnostics


The LEDs are shown in their various states as follows:

lit; flashing; off;

Normal operating status

In normal operating status the following LEDs illuminategreen. The SF LED does not illuminate. The M-LED only illu-minates with the setting “System start with stored paramet-erisation and stored CPX expansion” (� function num-ber 4402).

LED display Operatingstatus

PS

PL

SF

MS

NS

MTP2

TP1

The following LEDs illu-minate green:– PS– PL– MS– NS– TP1/2 1)

The SF LED does not il-luminate:– SFM-LED 2)

Standard

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

2) Only illuminates when starting with saved parameters

Tab. 4/2: Normal operating status

4. Diagnostics


4.2.1 CPX-specific LEDs

PS (power system) – power sensor/logic supply

LED (green) Sequence Status Significance/error handling

LEDilluminated

ON

OFF

No error. Operatingvoltage/sensor supplyapplied

–

LED flashes

ON

OFF

Operating voltage/sensorsupply outside thetolerance range

Eliminate undervoltage

ON

OFF

Internal fuse for theoperating voltage/sensorsupply has responded

1. Eliminate short circuit/overload onmodule side.

2. Dependent on the parameterisationof the module (moduleparameter)1):• The sensor supply voltage will be

switched on again automaticallyafter the short circuit has beeneliminated (factory setting)

• Power Off/On is necessary

LED notilluminated

ON

OFF

Operating voltage/sensorsupply is not applied1)

Check the operating voltageconnection of the electronics

1) The short-circuit, overload and undervoltage diagnostic messages (SCS/SCO/SCV, UOUT/VAL) forthe complete CPX terminal can be suppressed using the “Monitoring” system parameter (functionno. 4401).Monitoring that is set separately for each module (� parameter “Monitoring CPX module”) is notaffected by this system parameter.

Tab. 4/3: LED display PS (Power System)

4. Diagnostics


PL (power load) – power load supply (outputs/valves)

LED (green) Sequence Status Significance/error handling

LEDilluminated

ON

OFF

No error. Load voltageapplied

None

LED flashes

ON

OFF

Load voltage at the systemsupply or additional powersupply outside thetolerance range1)

Eliminate undervoltage

1) The short-circuit, overload and undervoltage diagnostic messages (SCS/SCO/SCV, UOUT/VAL) forthe complete CPX terminal can be suppressed using the “Monitoring” system parameter (functionno. 4401).Monitoring that is set separately for each module (� parameter “Monitoring CPX module”) is notaffected by this system parameter.

Tab. 4/4: LED display PL (Power load voltage)

SF (system failure) – system fault

LED (red) Sequence1) Status Significance/error handling

LED notilluminated

ON

OFF

No error. –

LED flashes

ON

OFF

Simple error/information(error class 1)

� Description of error numbers in theCPX system description

LED flashes

ON

OFF

Error(error class 2)


1) The System Failure LED flashes dependent on the applicable error class.Error class 1 (minor error): 1 * flash, pause timeError class 2 (error): 2 * flashes, pause timeError class 3 (severe error): 3 * flashes, pause time

Tab. 4/5: LED display SF (system error) - Part 1

4. Diagnostics


SF (system failure) – system fault

LED (red) Sequence1) Status Significance/error handling

LED flashes

ON

OFF

Severe error(error class 3)


1) The System Failure LED flashes dependent on the applicable error class.Error class 1 (minor error): 1 * flash, pause timeError class 2 (error): 2 * flashes, pause timeError class 3 (severe error): 3 * flashes, pause time

Tab. 4/6: LED display SF (system error) - Part 2

M (modify) – parameterisation modified or forcing active

LED (yellow) Sequence Status Significance/error handling

LED notilluminated

ON

OFF

System start with standardparametrisation (factorysetting) and current CPXexpansion set; externalparameterisation ispossible (presetting)

None

LEDilluminated

ON

OFF

System start with savedparametrisation and savedCPX expansion has beenset;Parameters and CPXexpansion are savedremanently; externalparameterisation isblocked 1)

Caution when replacing CPX valveterminals with saved parametrisation.With these CPX valve terminals,parametrisation is not carried outautomatically by the higher-orderPLC/IPC when the terminal isreplaced. In these cases, check whichsettings are required before thereplacement and make these settingsif necessary.

1) The display of the Force function (LED flashing) has precedence over the display of the setting forsystem start (LED illuminated).

Tab. 4/7: LED display M (Modify) - Part 1

4. Diagnostics


M (modify) – parameterisation modified or forcing active

LED (yellow) Sequence Status Significance/error handling

LED flashes

ON

OFF

– Force is active 1)

– Network settings havebeen modified

– The force function is enabled

(� system parameter force mode;

function no. 4402).– Restart CPX-FB36 (Power OFF/ON),

(� section 1.3.4)

1) The display of the Force function (LED flashing) has precedence over the display of the setting forsystem start (LED illuminated).

Tab. 4/8: LED display M (Modify) - Part 2

4.2.2 Network-specific LEDs

Connection/data traffic (Link/Traffic)

LED TP1/2 Sequence Status Error handling

Does notilluminate

ON

OFF

No network connection /network cable not connected

• Check network connection

Illuminatesgreen

ON

OFF

Network connection OK (Link) –

Flashes green

ON

OFF

Data traffic (traffic)Flashing frequency isdependent on the traffic.

–

Tab. 4/9: LED display TPx (Link/Traffic)

4. Diagnostics


4.2.3 Protocol-specific LEDs

EtherNet/IP protocol

Module status when using the EtherNet/IP protocol

LEDMS Sequence Status Significance/error handling

Does notilluminate

ON

OFF

Logic supply for bus interfacenot applied

• Check logic supply

Illuminatesgreen

ON

OFF

Operating status normal None

Flashes green

ON

OFF

CPX terminal must be placed inoperation as the configurationis missing, incomplete orincorrect.

• Carry out, complete or correctthe configuration

Flashes red

ON

OFF

Error can be rectified • Complete or correct theconfiguration

Illuminates red

ON

OFF

Error cannot be rectified • Check CPX expansion as wellas other LEDs and, ifnecessary, request service

Flashesred-green

ON

OFF

CPX terminal is in self-test None

Tab. 4/10: LED display MS (module status) for EtherNet/IP protocol

Network status when using the EtherNet/IP protocol

LED NS Sequence Status Significance/error handling

Does notilluminate

ON

OFF

The CPX terminal is offline • Check network connection

Tab. 4/11: LED display NS (network status) for EtherNet/IP protocol - Part 1

4. Diagnostics


Network status when using the EtherNet/IP protocol


Flashes green

ON

OFF

CPX terminal is online and hasreceived an IP address, but theCPX terminal does not have aconfigured connection.

• Check configuration; it ispossible that the CPXterminal is not assigned to amaster/scanner or

Illuminatesgreen

ON

OFF

The CPX terminal is online andhas a connection to thefieldbus

None (normal operating status)

Flashes red

ON

OFF

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

• Check the physicalconnection to themaster/scanner (EtherNetcable).

Illuminates red

ON

OFF

Communication has failed.– Non-permitted IP address

set and already used in thenetwork

• Correct IP address

Flashesred/green

ON

OFF

CPX terminal is in self-test None

Tab. 4/12: LED display NS (network status) for EtherNet/IP protocol - Part 2

Modbus/TCP protocol

Module status when using the Modbus/TCP protocol

LEDMS Sequence Status Significance/error handling

Is off

ON

OFF

Not ready for Modbus connec-tions

–

Illuminatesgreen

ON

OFF

Ready for Modbus connections –

Tab. 4/13: LED display MS (module status) for Modbus/TCP protocol - Part 1

4. Diagnostics


Network status when using the Modbus/TCP protocol


Is off

ON

OFF

No Modbus connection active –

Illuminatesgreen

ON

OFF

At least one Modbusconnection active.

–

Tab. 4/14: LED display MS (module status) for Modbus/TCP protocol - Part 2

4.3 Diagnostics via status bits

Status bits are internal inputs (1 input byte), which serve todisplay common diagnostic messages (global error mes-sages).

NoteIf status bits are to be transmitted via a “Polled” or“Change of state” connection, you must set the DILswitches on the bus node accordingly (� Tab. 1/2).

If all status bits supply logic 0, no error will be reported. Thefollowing table shows the diagnostic information when thereis a 1-signal:

Bit Diagnostic informationwith logic 1

Description

0 Error at valve Module type in which anerror has occurred

1 Error at output

2 Error at input

Tab. 4/15: Overview of status bits - Part 1

4. Diagnostics


Bit Diagnostic informationwith logic 1

Description

3 Error at analoguemodule/technology module

Module type in which anerror has occurred

4 Undervoltage Error type

5 Short circuit/overload

6 wire break

7 Other error

Tab. 4/16: Overview of status bits - Part 2

If various errors occur simultaneously on different types ofmodules, these errors cannot be assigned via the status bits.Errors may be uniquely determined through the I/O dia-gnostics interface or diagnostics via EtherNet/IP access.

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

4.4 Diagnostics via I/O diagnostic interface

For the bus node CPX-FB36, access to the EtherNet/IP Ob-jects through Explicit Message programming is in principlemore appropriate than the use of the I/O diagnostic interface(� section C.1).

Detailed diagnostic information can be accessed via the I/Odiagnostic interface. You can ascertain exactly, for example,on which module and on which channel an error has oc-curred. System diagnostics are retrieved by means of 16 in-put bits and 16 output bits, through which all diagnosticsdata can be read.

4. Diagnostics


NoteTo use the I/O diagnostics interface, it must be activated viaDIL switches on the bus node (� Tab. 1/2).

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

Information on the I/O diagnostics interface (diagnostic in-formation, function numbers)� CPX system description.

Overview of diagnostic data

Diagnostic data Contents / description

Global diagnostic data – General overview of errors

Module diagnostics data – Detail diagnostics per module

Status of diagnosticmemory

– Number of entries in the diagnosticmemory

– Operating mode

Diagnostic memory data – Long-term memory– Detail diagnostics + relative time

stamp per error event

Tab. 4/17: Diagnostic data

4. Diagnostics


4.5 Diagnostics via EtherNet/IP

The CPX system enables diagnostics via the EtherNet/IP pro-tocol. The following diagnostics options are supported here:

– Explicit Messaging via EtherNet/IP Master

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

Overview of diagnostic data with Explicit Messaging

The following EtherCat/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 there arediagnostic data).

– System error number

134d Diagnostic Trace Object – Long-term memory(max. 40 entries)

– Detail diagnostics + relative time stamp per errorevent

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

Tab. 4/18: Diagnostic data with Explicit Messaging

4. Diagnostics


Possible sequence of diagnostics

Possible sequence of diagnostics Diagnostic data Object whichsupplies thediagnostic data

1. Check to see if there are diagnostic dataavailable

Diagnostic status Status and DiagnosticObject (133d)

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

Number of the module Status and DiagnosticObject (133d)

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

General ParameterObject Module (101d)

Tab. 4/19: Possible sequence of diagnostics

4.6 Diagnostics via Modbus TCP

The CPX system enables diagnostics via the Modbus/TCPprotocol.

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

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

4. Diagnostics


4.7 Error handling

The behaviour of the CPX terminal in the event of the follow-ing malfunctions depends on the configured behaviour of themaster module and on the parameterised Fail Safe setting:

– Telegram failure

– Stopping of the masterThe settings under Idle Mode apply here

– Interruption of the bus line.

Depending on the parameterisation, the outputs (valves andelectric outputs) will be switched off (factory setting),switched on or retain their status (� CPX system descrip-tion).

Warning• Ensure that valves and outputs are put into a safe statusif the stated malfunctions occur.

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

NotePlease observe the following if the outputs are reset in theevent of a PLC stop or fieldbus interruption or malfunction:

– Monostable valves move to the basic position

– Double-solenoid valves remain in the current position

– Mid-position valves go into mid-position (pressurized,exhausted or closed, depending on valve type).

4. Diagnostics


Technical appendix

A-1Festo P.BE-CPX-FB36-EN en 1309NH English

Appendix A

Technical appendix

A. Technical appendix

A-2 Festo P.BE-CPX-FB36-EN en 1309NH English

Table of contents

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

A.1 Technical data, bus node CPX-FB36 A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


A-3Festo P.BE-CPX-FB36-EN en 1309NH English

A.1 Technical data, bus node CPX-FB36

General

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

Protection class to EN 60529 IP65 / IP67CPX-FB36 completely mounted, plug connector accordingto accessories, plugged in or equipped with protectivecap.

Protection against electric shock(Protection against direct and indirectcontact in accordance with IEC/DIN 60204-1)

through the use of PELV circuits(Protected Extra Low Voltage)

Intrinsic current consumption at 24 V– from operating voltage supply for

electronics/sensors (UEL/SEN)typ. 100 mA

Galvanic isolation– Ethernet/IP interface Galvanically separated

Module code (CPX-specific) Remote I/O: 224Remote Controller: 171

Module identifier (operator unit) Remote I/O: FB36 - EtherNet IP Remote-IORemote Controller: FB36 - Modbus TCP Remote-IO

Tab. A/1: Technical data – general

Communication

Transmission technology Switched Fast Ethernet;design 100BaseTX according to IEEE 802.3

Transmission rate 10/100 Mbit/s, full/half duplex


A-4 Festo P.BE-CPX-FB36-EN en 1309NH English

Communication

Protocols – IEEE 802.3 (Ethernet) according to RFC 894– Internet Protocol (RFC 791)– User Datagram Protocol (UDP) (RFC 768)– Transmission Control Protocol (TCP) (RFC 793)– Address Resolution Protocol (ARP) (RFC 826)– Internet Control Messaging Protocol (ICMP) (RFC 792)– Internet Group Management Protocol (IGMP) (RFC 1112

& 2236)– HTTP– FTP– DHCP

Fieldbus protocols EtherNet/IP and Modbus TCP– based on industrial Ethernet– based on the Ethernet protocol (IEEE 802.3)

Network connections 2 x M12, D-coded, female, 4-pin� section 1.1.1 (detailed information)

Crossover detection Auto-MDI/MDI-X

Maximum data field size(Input/Output-Size)

Remote I/O operating mode: 64 bytes each for inputs andoutputsRemote Controller operating mode: 8/16 bytes each forinputs and outputs (dependent on the DIL switch position� section 1.2.3)

Tab. A/2: Technical data - communication

Address assignment of the CPX terminal

B-1Festo P.BE-CPX-FB36-EN en 1309NH English

Appendix B

Address assignment of the CPX terminal

B. Address assignment of the CPX terminal

B-2 Festo P.BE-CPX-FB36-EN en 1309NH English

Table of contents

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

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

B.2 Addressing B-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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



B.1 Address assignment

NoteThe address space of a CPX terminal in the EtherNet/IPnetwork is limited.

The CPX bus node for EtherNet/IP provides the CPX ter-minal with an address space of up to 64 bytes for inputs (I)and 64 bytes for outputs (O).

Each module of the CPX terminal occupies a certain num-ber of I/O bits, I/O bytes or words in the context of modulecommunication.

The number of occupied I/O bytes (of the respective mod-ule) can be found in the following tables (Tab. B/1 ...Tab. B/7).

Certain functions, such as the I/O diagnostics interface(STI), also reduce the number of available I/O bytes (infavour of status or diagnostic functions).

Take account of this fact for the planning of your CPX ter-minal.

Determine the number of assigned inputs and outputs priorto commissioning or configuring the CPX terminal. Tab. B/8and Tab. B/9 provide help with this.

Use the configuration documents, the operator unit (CPX-MMI) or the Festo Maintenance Tool (CPX-FMT) to determineaddress assignment or terminal configuration.

In the operator unit display, the individual modules of the CPXterminal are displayed with the respective module identifiers.Using the module identifier and the following tables, you candetermine the module type and, with it, the number of inputsand outputs occupied by the module.



Module identifiers Each module, including the bus node, has its own identifier,the so-called module identifier. It serves to determine andlocalise the module type, for example as part of configura-tion.Apply the module identifiers – from left to right, correspond-ing to the physical order as installed in the CPX terminal – inyour configuration program (e.g. RSLogix).

In graphically oriented configuration programs, the moduleidentifiers are typically found in a separate listing of all avail-able hardware modules or network participants (fielddevices), e.g. in a module directory or module catalogue.

Electric modules

Tab. B/1 ... Tab. B/3 provide an overview of the assigned ad-dress spaces of different electrical modules and of the busnode in the Remote I/O operating mode.

Tab. B/4 shows the assigned address space of the bus nodein the Remote Controller operating mode.

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

Details on the CP interface can be found in the description forthe CP interface (P.BE-CPX-CP-...).



Electric modules Moduletype

Moduleidentifier1)

Allocated addressspace

Designation Inputs Outputs

Bus node for EtherNet/IPin Remote I/O operating mode2)

without diagnostic access

CPX-FB36 FB36-RIO... – –


with status bits [Status]

CPX-FB36 FB36-RIO... 2 bytes/8 (16) E3)

(8 bit used)

–


with I/O diagnostic interface[System Table Interface, STI]

CPX-FB36 FB36-RIO... 2 bytes/16I 2 bytes/16 O

Digital 4-off input module CPX-4DE 4DI 1 byte/4 (8)I3)

–

Digital 8-off input module CPX-8DE 8DI 1 byte/8 I –


CPX-8DE-D 8DI-D 1 byte/8 I –

Digital 8-input module, n-switching: CPX-8NDE 8NDI 1 byte/8 I –

Digital 16-off input module CPX-16DE 16DI 2 bytes/16 I –


CPX-M-16DE-D

16DI-D 2 bytes/16 I –

Digital 16-off input module withterminal strip

CPX-L-16DE-16-KL-3POL

L-16DI-PI 2 bytes/16 I –

1) Module identifier in the operator unit or in the hardware configuration of the programmingsoftware

2) Number of occupied I/O bytes in the Remote Controller operating mode:� Tab. B/43) Diagnostics mode status bits assigned 2 bytes of address space (8 I or 8 bits remain unused);

4-off modules (CPX-4DE and CPX-4DA) occupy 8 I or 8 O, or 1 byte of address space (4 I/O or 4 bitsof address space remain unused)

Tab. B/1: Address assignment of electric CPX modules (overview; bus node in RemoteI/O operating mode) – Part 1



Electric modules Module type Moduleidentifier1)



Digital 4-off output module CPX-4DA 4DO – 1 byte/4 (8) O2)

Digital 8-off output module CPX-8DA 8DO – 1 byte/8 O

Digital 8-output high current outputmodule

CPX-8DA-H 8DO-H – 1 byte/8 O

Digital multi I/O module with terminalstrip

CPX-L-8DE-8DA-16-KL-3POL

L-8DI8DO-PI 1 byte/8 I

1 byte/8 O

Digital multi I/O module CPX-8DE-8DA 8DI/8DO 1 byte/8 I

1 byte/8 O

Analogue 2-off input module CPX-2AE-U-I 2AI 2 words/32 I

–

Analogue 4-off input module CPX-4AE-U-I 4AI 4 words/64 I

–

Analogue 4-off input module CPX-4AE-I 4AI-I 4 words/64 I

–

Analogue 4-off input module(temperature module for RTD sensors)

CPX-4AE-T 4AI-T 2 wordsor4 words/32/64 I3)

–

Analogue 4-off input module(temperature module for TC sensors)

CPX-4AE-TC 4AI-TC 4 words/64 I

–

Analogue 4-off input module(pressure sensor module 0 ... 10 bar)

CPX-4AE-P-B10

4AI-P-B10 4 words/64 I

–


2) Diagnostics mode status bits assigned 2 bytes of address space (8 I or 8 bits remain unused);4-off modules (CPX-4DE and CPX-4DA) occupy 8 I or 8 O, or 1 byte of address space (4 I/O or 4 bitsof address space remain unused)

3) Number of inputs switchable between 2 and 4







Analogue 4-off input module(pressure sensor module -1 ... 1 bar)

CPX-4AE-P-B2 4AI-P-B2 4 words/64 I

–

Analogue 2-off output module CPX-2AA-U-I 2AO – 2 words/32 O

CP interface CPX-CP-4-FB CPI max.8 words/128 I2)

max.8 words/128 O2)

CTEL master module32 byte I and 32 byte O

CPX-CTEL-4-M12-5POL

CTEL max.16 words/256 I2)

max.16 words/256 O2)


2) Address space assignment depends on the string allocation


Configurationof the bus node

The identification of the bus node and the diagnostics modeare configured in the Remote I/O operating mode(� Tab. B/1 ... Tab. B/3).

Only the identification of the bus node is configured in theRemote Controller operating mode (� Tab. B/4).




Bus node for EtherNet/IPin Remote Controller operating mode

CPX-FB36 FB36-RC... 8 bytes/64 I

8 bytes/64 O


Tab. B/4: Address assignment of the bus node in the Remote Controller operatingmode



Pneumatic interfaces and pneumatic modules

Tab. B/5 ... Tab. B/7 provide an overview of the assigned ad-dress spaces of various pneumatic interfaces and modules.

Configurationof the pneumatics (valves)

The valves are configured according to the pneumatic inter-face used:

– Valves of type 03 (Midi/Maxi), type 12 (CPA) andtype 44/45 (VTSA/VTSA-F or ISO):

For expansion of the valve side, only one configurationprocess is required for the pneumatics interface. In thepneumatic interface, the number of valve coils is set usinga DIL switch.

– Valves of type 32 and 33 (MPA, MPA-F, MPA-L and MPA-Por VPPM pneumatic modules):

From a technical point of view, the individual MPA pneu-matic modules each represent an electric module for con-trolling the attached valves.

A configuration process is required for each pneumaticmodule of type MPA:

– Pneumatic modules of typeMPA1 each occupy 1 byte ofaddress space or 8 outputs regardless of how manyvalves are attached to the pneumatic module.

– Pneumatic modules of typeMPA2 each occupy 1 byte ofaddress space or 8 outputs, but only 4 bits are used.

- Pneumatic modules of typeMPA-P each occupy 1 word(2 bytes) of address space or 16 inputs.

- Pneumatic modules of type VPPM each occupy 2 wordsof address space or 1 word I/1 word O or 16 inputs and16 outputs.Pneumatic modules of type MPA-P and VPPM are ana-logue modules. Observe the order of the modules in ad-dressing or I/O mapping (� Tab. B/10).



Additional information on the pneumatics can be found in thecorresponding pneumatics descriptions (� document over-view “Descriptions of the CPX terminal” in the CPX systemdescription P.BE-CPX-SYS...).

The manuals for the pneumatic valve cluster (Midi/Maxi, CPA,MPA and VTSA/VTSA-F or ISO) contain the address assign-ment within the pneumatic modules.

For further information about MPA pneumatic modules andthe pneumatic interfaces:� description of the CPX I/O mod-ules P.BE-CPX-EA-...).



CPX pneumatic interfaces1) Type Moduleidenti-fier1) 4)


Inputs Outputs

Pneumatics interface for MPA-Svalves (type 32)

VMPA-FB-EPL-... – – –

Pneumatic interface for MPA-Fvalves (type 33)

VMPAF-FB-EPL-... – – –

Pneumatic interface for MPA-Lvalves (type 34)2)

– 1...4 solenoid coils– 1...8 solenoid coils– 1...16 solenoid coils– 1...24 solenoid coils– 1...32 solenoid coils

VMPAL-FB-EPL-... – –

1 byte/8 O1 byte/8 O2bytes/16O3 bytes/24 O4 bytes/32 O

Pneumatic interface for VTSA orVTSA-F pneumatics(CPX type 44/45: 1-..-..)with setting:3)

– 1...8 solenoid coils– 1...16 solenoid coils– 1...24 solenoid coils– 1...32 solenoid coils

VABA-10S6-x1 ISO plug-in ortype 44 ortype 453)

–

1 byte/8 O2 bytes/16 O3 bytes/24 O4 bytes/32 O

Pneumatic interface for Midi/Maxivalves (CPX type 03: 1-..-..)with setting:3)

– 1...8 solenoid coils– 1...16 solenoid coils– 1...24 solenoid coils– 1…32 solenoid coils (26 effective)

CPX-GP-03-4.0 TYPE3 –

1 byte/8 O2 bytes/16 O3 bytes/24 O4 bytes/32 O

Pneumatic interface for CPA valves(CPX type 12: 1-..-..)with setting:3)

– 1...8 solenoid coils– 1...16 solenoid coils– 1…24 solenoid coils (22 effective)

CPX-GP-CPA-10CPX-GP-CPA-14

CPA10/14 –

1 byte/8 O2 bytes/16 O3 bytes/24 O

1) Module identifier in the operator unit or in the hardware configuration of the programming software2) Setting with rotary switch in the pneumatic interface3) Setting with DIL switch in the pneumatic interface4) Display text (module identifier) dependent on the version of the operator unit

Tab. B/5: Overview of CPX pneumatic interfaces



CPX pneumatic modules forMPA-S and MPA-F

Type ofelectronicsmodule

Moduleidentifier1)


Inputs Outputs

MPA1 pneumatic module(CPX type 32/33: 1-8V..)without electrical isolation

VMPA1-FB-EMS-8 MPA1S – 1 byte/8 O

MPA1 pneumatic module(CPX type 32/33-G: 1-8V..)with electrical isolation

VMPA1-FB-EMG-8 MPA1G – 1 byte/8 O

MPA2 pneumatics module(CPX type 32/33: 1-4V..)without electrical isolation

VMPA2-FB-EMS-4 MPA2S – 1 byte/4 (8) O2)

MPA2 pneumatics module(CPX type 32/33-G: 1-4V..)with electrical isolation

VMPA2-FB-EMG-4 MPA2G – 1 byte/4 (8) O2)

MPA1 pneumatic module(CPX type 32/33: 1-8V..)with diagnostic function D2

VMPA1-FB-EMS-D2-8

MPA1S-D – 1 byte/8 O

MPA1 pneumatic module(CPX type 32/33-G: 1-8V..)with electrical isolation,with diagnostic function D2

VMPA1-FB-EMG-D2-8

MPA1G-D – 1 byte/8 O

MPA2 pneumatics module(CPX type 32/33: 1-4V..)without electrical isolation,with diagnostic function D2

VMPA2-FB-EMS-D2-4

MPA2S-D – 1 byte/4 (8) O2)

MPA2 pneumatics module(CPX type 32/33-G: 1-4V..)with electrical isolation,with diagnostic function D2

VMPA2-FB-EMG-D2-4

MPA2G-D – 1 byte/4 (8) O2)

1) Module identifier in the operator unit or in the hardware configuration of the programming software2) In principle, MPA2 modules occupy 8 O (1 byte) of address space (4 O or 4 bits remain unused)

Tab. B/6: Overview of CPX pneumatic modules for MPA-S and MPA-F - Part 1



CPX pneumatic modules forMPA-S and MPA-F

Module type Moduleidentifier1)


Inputs Outputs

VPPM proportional pressure-regu-lating valve (type 32)

VPPM-6TA-L-1-F... VPPM 1 word/16 I

1 word/16 O

MPA−P pressure sensor module VMPA-FB-PS-... MPA-P 1 word/16 I

–

1) Module identifier in the operator unit or in the hardware configuration of the programming software

Tab. B/7: Overview of CPX pneumatic modules for MPA-S and MPA-F - Part 2

Calculating the number of inputs/outputs

Use Tab. B/8 and Tab. B/9 to calculate the number of inputsand outputs (address assignment) of your CPX terminal.

Input/output modules and system diagnostics Inputs Outputs

1. Status bits or I/O diagnostics interface1) + ____ I + ____ O

2. Number of input modules CPX-4DE + __ x 8I2) + ____ I

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

4. Number of input modules CPX-(M-)16D(E),L-16DE-…

+ __ x 16I + ____ I

5. Number of output modules CPX-4DA + __ x 8O2) + ____ O

6. Number of output modules CPX-8DA, 8DA-H + __ x 8 O + ____ O

7. Number of multi I/O modules CPX-8DE-8DA,L-8DE-8DA…

+ __ x 8 I/O + ____ I + ____ O

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

9. Number of analogue input modules CPX-4AE-I,4AE-U-I

+ __ x 64 I + ____ I

10. Number of analogue input modules CPX-4AE-T + __ x 32 I/ x 64 I + ____ I

Tab. B/8: Identifying the assigned address space (total of inputs and outputs) - Part 1



Input/output modules and system diagnostics Inputs Outputs

11. Number of analogue input modules CPX-4AE-TC + __ x 64 I + ____ I

12. Number of analogue input modules CPX-4AE-P-… + __ x 64 I + ____ I

13. Number of analogue output modules CPX-2AA-U-I + __ x 32 O + ____ O

14. Number of inputs and outputs of other modules(e.g. CP interface, VPPM-/MPA-P pneumaticmodule)

+ __ I/O + ____ I + ____ O

15. Midi/Maxi, CPA-, MPA-L and VTSA/VTSA-F pneumatic interfaces:Number of configured valve solenoid coils (+ 8 O ... 32 O; factoryconfigured presets are 32 O (Midi/Maxi, VTSA/VTSA-F/MPA-L) or24 O (CPA))

+ ____ O

16. Number of MPA1- or MPA2 pneumatic modules + __ x 8 O2) + ____ O

17. Sum total of inputs/outputs to be configuredTotal from 1 to 16 (max. 512 I and 512 O)

= ____ I = ____ O

1) Number of occupied inputs /outputs� Tab. B/12) 4-off modules CPX-4DE and CPX-4DA as well as MPA2 pneumatic modules generally occupy 8

inputs or outputs (1 byte; available address space remains partially unused)

Tab. B/9: Identifying the assigned address space (total of inputs and outputs) - Part 2



B.2 Addressing

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 out-puts when the status bits and the I/O diagnostic interfaceare deactivated.

– The I/Os of different module types are assigned separ-ately 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 the interface is activated, itwill occupy the first 16 inputs and outputs in the addressrange.

2. Analogue modules Modules with analogue inputs/outputs

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

4. Digital modules Modules with digital inputs/outputs

1) Depending on the setting, this address range can also be occupied by status bits (� Note aboveand Tab. 1/2).

Tab. B/10: Sequence of addressing



Data formats

In RSLogix the I/Os of the bus node can be configured in SINTor INT format.

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.

These Assembly Instances are used for the SINT format.

– Inputs: Assembly Instance 101

– Outputs: Assembly Instance 100

Using the INT format

If the INT format is to be used, then the size of the 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 RSLogix depending onthe configuration of the CPX terminal.

These Assembly Instances are used for the INT format:

– Inputs: Assembly Instance 111

– Outputs: Assembly Instance 110

Note• Make sure that the two output assemblies 100 and 110are not accessed simultaneously.



Configuration examples

Example 1: CPX terminal with MPA1- and MPA2 pneumatic

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

– Status bits and I/O diagnostic interface deactivated

Module no.: 0

1 2

8DI 4DO

3

1 2 3 4 5 6

4

1 Bus node CPX-FB36

2 MPA pneumatic interface

3 MPA1 pneumatic modules (8 DO each)

4 MPA2 pneumatic modules (4 DO each)

Fig. B/1: Example terminal 1: (with MPA1- and MPA2 pneumatic)

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

Moduleno.

Module Input address Output address

0 Bus node CPX-FB36 – –

1 Digital 8-input module CPX-8DE I0 ... I7 –

Tab. B/11: Addressing of example terminal 1 - Part 1 (� Fig. B/1)



Moduleno.


2 Digital 4-output module CPX-4DA – O0 ... O71)

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

4 MPA1 pneumatic module (8 DO) – O16 ... A23

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

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

1) 8 bits occupied, 4 bits used.

Tab. B/12: Addressing of example terminal 1 - Part 2 (� Fig. B/1)



Example 2: CPX terminal with CP interface

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

– Status bits and I/O diagnostic 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 (16DO) on the CPinterface (string 1)

3 CP input module (16 DI)

4 Sensor

5 Cylinder

6 CP output module (16DO) on the CPinterface (string 4)

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



Moduleno.


0 Bus node CPX-FB36 – –


2 Digital 4-output module CPX-4DA – O128...O1351)

3 CP interfaceCP-I, here: 4 byte I, 16 byte O

I0 ... I31 O0 ... A127

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

I40 ... I47 O136 ... A143



1) 8 bits occupied, 4 bits used

Tab. B/13: Addressing of example terminal 2 (� Fig. B/2)



Example 3: CPX terminal with analogue module and VTSApneumatic

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

– Status bits activated and /I/O diagnostic interface deac-tivated

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

1 2

8DI 8DI 4DO 8DI 2AO

3

8DO

Module no.: 0 1 2 3 4 5 6

1 Bus node CPX-FB36 (with DIL 3.2 toON for status bits)

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

3 VTSA pneumatics (type 44)

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



Moduleno.


0 Bus node CPX-FB36 with status bits I0 ... I151) –





I32 ... I39 O40 ... A47

5 Analogue 2-output moduleCPX-2AA

– O0 ... A31

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

– O48 ... A55

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

Tab. B/14: Addressing of example terminal 3 (� Fig. B/3)



B.3 Address assignment after extension/conversion

A special feature of the CPX terminal is its flexibility. If therequirements placed on the machine change, the equipmenton the CPX terminal can also be modified.

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

– Additional modules are inserted between existing mod-ules.

– Existing modules are removed or replaced by other mod-ules which have fewer or more input/output addresses.

– Interlinking blocks (VTSA) and/or pneumatic manifoldblocks (MPA-L) for monostable valves are replaced byinterlinking blocks/manifold blocks for bistable valves orvice versa (� pneumatics description).

– Additional interlinking blocks (VTSA) and/or manifoldblocks (MPA-L) are inserted between existing ones.

– Status bits or the I/O diagnostic interface are activated/deactivated.



Example terminal 3modified

The next diagram shows with terminal 3 as an example(� Fig. B/3) the effects of modifications to the address as-signment.

The following has been changed:

– The status bits have been deactivated.

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

– The pneumatic interface has been set to 16 solenoid coils(outputs) in order to reserve addresses for an extensionto the pneumatics.

1 2

16DI 8DI 4DO 8DI 2AO

3

8DO

Module no.: 0 1 2 3 4 5 6

1 Modified status bits deactivated

2 Modified: 8DI module replaced by16DI module

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

Fig. B/4: Example terminal 3 after extension/modification(compare with Fig. B/3)



Moduleno.


0 Bus node CPX-FB36 withdeactivated status bits

Dependent on DIL switch settings

(� Tab. 1/2)





I24 ... I31 O40 ... A47

5 Analogue 2-output moduleCPX-2AA

– O0 ... A31

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

– O48 ... A63

bold =modified module1) 8 bits occupied, 4 bits used

Tab. B/15: Addressing of example terminal 3 after extension/modification (� Fig. B/4)

EtherNet/IP Objects of the CPX-FB36

C-1Festo P.BE-CPX-FB36-EN en 1309NH English

Appendix C

EtherNet/IP Objects of the CPX-FB36

C. EtherNet/IP Objects of the CPX-FB36

C-2 Festo P.BE-CPX-FB36-EN en 1309NH English

Table of 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 diagnosis 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 Diagnostics Object C-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.4 Diagnostics Trace Object C-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.5 Diagnostics Trace Status Object C-26. . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.6 General Module 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 operating mode Remote Controller) C-42. . . . . .

C.5 Examples C-43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5.1 Forcing inputs C-43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5.2 Parameterisation with the general Module Parameter Object C-45. . . .



C.1 Overview of Ethernet/IP objects

This chapter describes the representation of the CPX terminalwithin the Ethernet/IP object model. Some of the informationis in English even in the documentation in other languages, sothat the original terms of the Ethernet/IP specification can beused 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 Comment

1d 1 Identity object General CIPObjects

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-specific Ob-jects246d 2 Ethernet Link Object

71d 1 Device Level Ring Object

72d 1 QoS Object

132d 1 Global System Object CPX-specificobjects forparameterisa-tion and dia-gnostics

133d 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 of EtherNet/IP objects of the CPX-FB36 - Part 1



Objectclass

Instances(dec.)

Name Comment

114d … 115d122d, 123d130d, 131d

1 ... 48 Idle Parameter CPX-specificobjects forparameterisa-tion

101d 1 ... 48 Generic Parameter Object

102d 1 ... 48 Discrete Input Object CPX-specificobjects forparameterisa-tion of the in-puts and out-puts

103d 1 ... 48 Discrete Output Object

104d 1 ... 48 Analogue Input Object

105d 1 ... 48 Analogue Output Object

106d 1 ... 48 Function Input Object

107d 1 ... 48 Function Output Object

108d 1 ... 48 Discrete Input Force State Object CPX-specificobjects forparameterisa-tion of Force,Fail safe andIdle mode

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 Fail safe State Object4)

113d 1 ... 48 Discrete Output Fail safe Mode Object

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

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




Objectclass

Instances(dec.)

Name Comment

116d 1 ... 48 Analogue Input Force State Object CPX-specificobjects forparameterisa-tion of Force,Fail safe andIdle mode

117d 1 ... 48 Analogue Input Force Mode Object

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

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

120d 1 ... 48 Analog Output Fail safe State Object

121d 1 ... 48 Analog Output Fail safe Mode Object

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

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

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

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

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

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

128d 1 ... 48 Function Output Fail safe State Object

129d 1 ... 48 Function Output Fail safe Mode Object

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

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


Objectclass

Instances(dec.)

Name Comment

136d 1 Slave Size Object CPX-specificObject

Tab. C/5: Special EtherNet/IP object for the remote controller operating mode



Counting mode Applicable for the module-oriented objects in Tab. C/3 ...Tab. C/4 is: Instance 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 func-tion numbers as well as their assignment to the objects canbe found in the following sections.

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



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 Network Topology:0: Linear1: Ring

USINT

2 Get Network Status:0: 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 set tozero

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

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 mes-sagesdefault = 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 various Ether-Net/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

With the TCP/IP Interface Object you can configure the net-work settings of a device.

Attr.No.


1 Get Status:Interface Status

DWORD

2 Get Configuration Capability DWORD

3 Get/Set Configuration Control DWORD

4 Get Physical Link ObjectPath SizePath

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

8 Get/Set TTL Valuefor EtherNet/IP multicast packets

USINT

9 Get/Set Mcast config:IP multicast address configuration– Alloc Control– Reserved– NumMcast– Mcast Start Addr

STRUCT of

USINTUSINTUINTUDINT

Tab. C/8: Network settings with TCP/IP Interface Object -Part 1



Attr.No.


10 Set SelectAcd BOOL

11 Get/Set LastConflictDetected:– ACDactivity– RemoteMAC

– ArpPDU

STRUCT ofUSINTARRAY of6 USINTARRAY of28 USINT

12 Set QuickConnect 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.5):

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 to 100 Mbit/s/Full-Duplex (Auto-Negotiationoff), the following values must be written in Attribute 6, In-stance 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 the exchange of data with the Objects cantake place via one connection.

The following Object instances are saved in the AssemblyObject:

Instance Description

100 Output data

101 Input data

102 Configuration data

110 Output data with padding (output data in INTformat)

111 Input data with padding (input data in INT format)

Tab. C/11: Instances for Assembly Object



Remote I/O operating mode

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

Instance 101: Input

Within the instance “Input Assembly Object” all inputs of theCPX system are transmitted cyclically over the network bymeans of a communication connection.The following sequence applies during transmission:

Sequence of transmission

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

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

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

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

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, ifactive

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 outputsof the CPX system will be transmitted over the network bymeans of one communication connection. The following se-quence applies during transmission:

Sequence of transmission

1. I/O diagnostic interface/status byte, if active (16-bitorientated)

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

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

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

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)


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, ifactive

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. Numberof


199 1 Configuration Array data ARRAY

Tab. C/16: Instance 102 member list

The I/O Objects 102 ... 107 also possess the following attrib-utes:

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) of aword.

Instance 100: Output

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

Obj. Attrib-utes


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



Instance 101: Input

Instance 101 (input) possesses the following member list:

Obj. Attrib-utes


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



Transmission by communication types Polled communicationor 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 diagnosis

C.4.1 Identity Object

Object class: 1d

Instances: 1

The Identity Object contains the identification and generalinformation on the CPX-FB36.

Service Code 5d:ResetParameter 0 emulates a Power CycleParameter 1 resets the device to the factory settings and thenemulates a Power Cycle.

Attr.No.


1 Get VendorID: 1Ah UINT

2 Get Device Type: 0Ch UINT

3 Get Product Code:Remote I/O: 36CAhRemote Controller: 36CBh

UINT

4 Get Revision (major/minor) ARRAY of2 USINT

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 Unrecoverable FaultBit 10: Major Recoverable FaultBit 11: Major Unrecoverable FaultBit 12-15: reserved, shall be 0

WORD

6 Get Serial number UDINT

7 Get Product NameCPX-FB36 Remote-I/OCPX-FB36 Remote Controller

SHORT_STRING

14 Get/Set

Semaphore STRUCT

100 Get Operating Mode:Remote Controller: TRUERemote 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 RemoteI/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 equipment status (bit 4)Specifies whether the current equipment fittedto the CPX corresponds to the saved CPXequipment status.0: equal1: unequal

0 (bit 4)

Operator unit (bit 5)Specifies whether or not an operator unit isconnected.0: No operator unit connected1: Operator unit connected

0 (bit 5)

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

0 (bit 6)

Bit 7: reserved 0 (bit 7)

Tab. C/22: Attributes of the System Object for operating mode Remote I/O (Part 1)



Attr.No.


2 Get Fail safe modeSpecifies whether the Fail Safe mode is active orinactive.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 CPX terminal (bit 0 ... 7)Specifies whether the monitoring of shortcircuit/overload and undervoltage is active orinactive.Bit 0: Monitoring SCS (short

circuit/overload sensor supply)Bit 1: Monitoring SCO (short

circuit/overload outputs)Bit 2: Monitoring UOut

(Undervoltage outputs)Bit 3: Monitoring UVal

(Undervoltage valves)Bit 1: 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/overload 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: reserved1: active (presetting)0: inactive

BYTE 4401 (bit 0 ... 7)

10 Get/Set Fail safe mode0: Reset all outputs (presetting)1: Hold last state (Retain signal status)2: Assume Fail safe mode

BYTE 4402 (bit 0, 1)

11 Get/Set Force mode0: blocked1: 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

(factory setting) and current CPX expansion;external parameterisation possible(presetting)

1: System start with saved parameters andsaved CPX expansion; parameters and CPXexpansion are saved remanently; externalparameterisation is blocked; the M-LED onthe CPX 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 Diagnostics 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 interface16 output bits (task data) of the I/O diagnosticinterface

WORD

6 Get Data I/O diagnostic interface16 input bits (reply data) of the I/O diagnostic inter-face

WORD

Tab. C/25: Attributes of the Status and Diagnostics Object



C.4.4 Diagnostics Trace Object

Object class: 134d

Instances: 1 ... 40

An instance is created for each diagnostic entry.

Attr.No.

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

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

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

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

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

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

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

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

7 Get Modulecode 3)

Module code of the modulewhich registered the error

BYTE n = 10 * d + 5

8 Get Modulenumber

Module position of themodule which registered theerror; 63 = error notmodule-related

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

9 Get Channelnumber 3)

Number of the first faultychannel

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

1) d (diagnostic event) = 0 ... 39 ; most current diagnostic event = 0;2) Measured from the time the power supply was switched on3) If the error number = 0, the content is also 0. If the error number is between 128 ... 199

(error class 3), the content is not relevant (service case).

Tab. C/26: Attributes of the Diagnostics Trace Object - Part 1



Attr.No.

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

10 Get Error number Possible error messages

� System description,

chapter 5

BYTE n = 10 * d + 8

11 Get Subsequentchannels 1)

Number of subsequentchannels with the same error

BYTE n = 10 * d + 9

1) If the error number = 0, the content is also 0. If the error number is between 128 ... 199(error class 3), the content is not relevant (service case).

Tab. C/27: Attributes of the Diagnostics Trace Object - Part 2



C.4.5 Diagnostics 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(bits 0 ... 7)

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

BYTE 3483(bits 0, 1)

3 Get/Set Clear_trace1, access via EDS BYTE -

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

BYTE -

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

BYTE 3480(bit 0)

6 Get/Set Run/stop filter 10: Stop after 40 entries (store the first 40 entries)1: Overwrite old entries (store 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 FN2: Record up to the defined FN + MN3: Record up to the defined FN + MN + KN4: Record from the defined FN5: Record from the defined FN + MN6: Record from the defined FN + MN + KN7: reserved

BYTE 3484(bits 0 ... 2)

Tab. C/28: Attributes of the Diagnostics Trace Status Object - Part 1



Attr.No.

Access Name Type Functionno.

8 Get/Set End of error filter0: Record going errors (end of error) (filter inactive,

presetting)1: Do not record going errors (end of error) (filter

active)

BYTE 3484(bit 3)

9 Get/Set Error number filterFN = error number0: Error number filter inactive (presetting)1: Record only defined FN2: Do not record defined FN3: reserved


10 Get/Set Module/channel filterWith this diagnostic memory filter, the registering oferrors of other modules or channels can be sup-pressed in order that errors in a particular module orchannel can be analysed.FN = error number0: Module/channel filter inactive (presetting)1: Record only FN of a module2: Record only FN of a channel3: reserved


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

BYTE 3485(bits 0 ... 7)

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

BYTE 3486(bits 0 ... 7)

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

BYTE 3487(bits 0 ... 7)

Tab. C/29: Attributes of the Diagnostics Trace Status Object - Part 2



C.4.6 General Module Parameter Object

Object class: 101d

Instances: 1 ... 48

Applicable 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 4-input module CPX-4AE-I– temperature module CPX-4AE-T– CPX-CP interface

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

– byte parameters through the Attribute 1 ... 64– word parameters through the Attribute 65 ... 127– double-word parameters through the Attribute 129 ... 189

Procedure forparameterisation

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

2. Search for this function number in the last column ofTab. C/30 (byte and word parameter) or Tab. C/31(double-word parameter)

3. Read the appropriate Attribute number from the table.

Examples for parameterisation with the general Module Para-meter Object can be found in section C.5.2.



Attribute no. Parameter Function no.

Byte Word Word

165

– Parameters:� Description of the respectivemodule

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 wordparameters to the function numbers



Attribute no. Parameter Function no.

Byte DWord DWord DWord DWord

1

129

– – – Parameters:

� Description of the

respective 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 function numbers



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/Omodules

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 technologymodule



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 statefor 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 statefor analogue I/O modules

Objects for Force state: 116d, 118d (� Tab. C/33)

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 statefor technology modules

Objects for Force state: 124d, 126d

(� Tab. C/34)

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 statetechnology 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 ofdigital 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 ofanalogue 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 and Idlemode

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 andIdle statefor 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 andIdle state for digital output modules



Composition of the Objects for Fail safe state andIdle statefor analogue output modules



(� 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 andtechnology modules



Composition of the Objects for Fail safe state andIdle statefor technology modules



(� 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 andtechnology 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.

Access Description Type Functionno.

1 Get/Set Data field with all system and module parameters. ARRAY –

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

Object class: 136d

Instances: 1

This Object is only available in the operating mode RemoteController. It contains the number of I/O bytes for communic-ation of theCPX-FB36 with the CPX-FEC or CPX-CEC. The set-ting is implemented via DIL switches on the CPX-FB36(� Tab. 1/3).

Attr.No.


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

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



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 O 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/46)

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 section 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 Parameter Type

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


word

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



Tab. C/46: 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 Parameter Type

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

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

BOOL

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



Tab. C/47: Example: Set Force mode for module no. 2



C.5.2 Parameterisation with the general Module Parameter Object

In this example a signal extension time with a digital inputmodule and a lower limit value with an analogue input mod-ule are parameterised.

1 2

3

4 5 6

Instance no.: 1

8 O 8 O

1

8DI4

AI-I8DI 8DO

0Module no.:

22

3

4 5 6 7

2

1 Parameterisation module CPX-8DE: Enable signal extension channel 5:Object class 101 (� section C.4.6)Instance 1 (= module number)Attribute 7 (� Tab. C/48)

2 Parameterisation module CPX-4AE-I: Lower limit channel 2Object class 101Instance 2 (= module number)Attribute 82 (� Tab. C/49)

Fig. C/2: Examples for parameterisation with the general Module Parameter Object

The following tables show you how to ascertain the Attributesfor the parameterisation. The parameters of the relevant mod-ules are entered in the tables.

Information on the parameters can be found in the descrip-tion 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/48: 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/49: Example: parameterisation of the lower limit value (module no. 2, channel 2)

Modbus/TCP Objects of the CPX-FB36

D-1Festo P.BE-CPX-FB36-EN en 1309NH English

Appendix D

Modbus/TCP Objects of the CPX-FB36

D. Modbus/TCP Objects of the CPX-FB36

D-2 Festo P.BE-CPX-FB36-EN en 1309NH English

Table of 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 Processing data (groups B and D) D-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.1 Module CPX-FB36 D-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.2 Electric modules D-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.3 Pneumatic modules D-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.4.4 Technology module CP interface D-14. . . . . . . . . . . . . . . . . . . . . . . . . . .

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

D.4.6 Composition of the data of the I/O diagnostic interface D-18. . . . . . . . .

D.5 Diagnostic memory (groups C and E) D-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.6 Modbus/TCP Objects (group F) D-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.6.1 Addressing examples for ModbusTCP D-23. . . . . . . . . . . . . . . . . . . . . . .



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 in order that the original termsof the protocol specification can be used clearly.

D.2 Commands and addresses

The table below shows the correlation between the Modbusaddress and data or parameters of the CPX terminal. The dataare assigned to various groups.

Modbuscommand

Func-tioncode

Modbusaddress

Meaning RemoteI/O 16-bitaccess

group

read4x registers

3 45357...4539145392...4564745648...4565545656...46055

CPX status informationProcessing data inputsDiagnostic memory parametersDiagnostic memory data

ReadReadReadRead

ABCC

write4x registers

6, 16 40001...4025640257...40264

Processing data outputsDiagnostic memory parameters

WriteWrite

DE

read/write4x registers

23 45357...4539145392...4564745648...4565545656...4605540001...4025640257...40264

CPX status informationProcessing data inputsDiagnostic memory parametersDiagnostic memory dataProcessing data outputsDiagnostic memory parameters

ReadReadReadReadWriteWrite

ABCCDE

read deviceidentification

43 Objects objects ID0, 1, 2, 3, 4, 5 Read F

Tab. D/1: Overview of the Modbus function codes for the CPX-FB36 in the Remote I/Ooperating mode



D.3 CPX status information (group A)

The status information provides information on the configura-tion and the fault status of the CPX terminal. It lies in theModbus address range 45367 to 45391.

Modbusaddress

CPX terminal configuration

Processing data inputs

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

45367 Module 0 ... 15

45368 Module 16 ... 31

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

Modbusaddress

Error detection


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 faultBit n = 1: Fault in module n

Tab. D/3: Reognition, which module registers a fault



Modbusaddress

Status register


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 (extract from system data)

D.4 Processing data (groups B and D)

The processing image of the input data (group B) and of theoutput data (group D) is composed without gaps of the dataof the modules as they are fitted from left to right in the CPXterminal.The Modbus addresses depend accordingly on the modulesfitted on your CPX terminal. They are arranged in ascendingorder without gaps (n, n +1, n +2, ..., n corresponds to thefirst Modbus address of the module).

Addressing examples (� section D.6.1)

D.4.1 Module CPX-FB36

Modbusaddress1)

CPX-FB36 Remote I/O

Processing data inputs Processing data outputs

Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Result of access to the I/O diagnosticinterface1)

Access to the I/O diagnostic interface2)

Tab. D/5: CPX-FB36 Remote I/O – Part 1



Modbusaddress1)

CPX-FB36 Remote I/O

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 diagnostic interface� Tab. D/27 ... Tab. D/28

Tab. D/6: CPX-FB36 Remote I/O – Part 2

D.4.2 Electric modules

Modbusaddress1)

Digital 4-off 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 4-off input module (CPX-4DE)

Modbusaddress1)



Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n 0 Inputs –

Tab. D/8: Digital 8-off input module (CPX-8DE) - Part 1



Modbusaddress1)




Tab. D/9: Digital 8-off input module (CPX-8DE) - Part 2

Modbusaddress1)

Digital 4-off 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/10: Digital 4-off output module (CPX-4DA)

Modbusaddress1)

Digital 8-off 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/11: Digital 8-off input/output module (CPX-8DE-8DA)



Modbusaddress1)

Analogue 2-off 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/12: Analogue 2-off input module (CPX-2AE)

Modbusaddress1)

Analogue 2-off 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/13: Analogue 2-off output module (CPX-2AA)



D.4.3 Pneumatic modules

Modbusaddress1)

Pneumatic MPA1 module type 32 (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



Modbusaddress1)

Pneumatic MPA2 module type 32 (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: MPA pneumatic modules



Modbusaddress1)

Pneumatic interface for CPA pneumatics type 12set to 1 ... 8 valves


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0


n+1 Diagnostic data –


Tab. D/15: CPA pneumatic interface

Modbusaddress1)



Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Echo outputs Outputs






Modbusaddress1)



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




Modbusaddress1)

Pneumatic interface for pneumatics type Midi/Maxi (type 03)set to 1 ... 8 valves


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0




Tab. D/18: Midi/Maxi pneumatic interface



Modbusaddress1)



Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0

n Echo outputs Outputs




Modbusaddress1)



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






Modbusaddress1)

Pneumatic interface for pneumatics type Midi/Maxi (type 03)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 Technology module CP interface

The CP interface has connections for 4 strings to each ofwhich 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.

Modbusaddress1)

CPX-CP interfaceused 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: CPX-CP interface



Modbusaddress1)

CPX-CP interfaceused strings: 1, 2 (Line 1 ... 2)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0














Modbusaddress1)

CPX-CP interfaceused strings: 1, 2, 3 (Line 1 ... 3)


Bit 15 12 11 8 7 4 3 0 15 12 11 8 7 4 3 0


















Modbusaddress1)

CPX-CP interfaceused 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






















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) Fault 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 fault1 1: reserved

Tab. D/26: Module diagnostics data

D.4.6 Composition of the data of the I/O diagnostic 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 is made to the I/O diagnostics interface with a 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 in thechapter “Diagnostics and error handling”.



D.5 Diagnostic memory (groups C and E)

Modbusaddress

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 Fault end filter (CPX function number 3484)

45652 Fault number filter (CPX function number 3484)

45652 Module/Channel filter (CPX function number 3484)

45653 Module number MN (CPX function number 3485)

45654 Channel number CN (CPX function number 3486)

45655 Fault number FN (CPX function number 3487)

45650 Diagnostic memory data – number of entries (CPX function number 3482)

45651 Diagnostic memory data – 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

Tab. D/29: Read access to diagnostic memory parameters and data



Modbusaddress

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 Fault end filter (CPX function number 3484)

40261 Fault number filter (CPX function number 3484)

40261 Module/Channel filter (CPX function number 3484)

40262 Module number MN (CPX function number 3485)

40263 Channel number CN (CPX function number 3486)

40264 Fault number FN (CPX function number 3487)

Tab. D/30: Write access to diagnostic memory parameters

Information on the diagnostic memory can be found in theCPX system description in the appendix “Parameters anddata of the CPX terminal”.



D.6 Modbus/TCP Objects (group F)

Object ID Object name Table of 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 ModbusTCP

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 Loca-tion

Modbusaddress

Input data

Bit 15 8 7 4 3 0

CPX-FB36Remote 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 8-off inputmodule (CPX-8DE)

1 45395 0 Input data


Digital 4-offoutput module(CPX-4DA)

2 45397 x Echo outputdata


MPA pneumaticsmodule withdiagnosticfunction

3 45399 x Echo output data











Tab. D/32: Input data addressing example 1 (CPX terminal from Fig. D/1)



Module Loca-tion

Modbusaddress

Output data

Bit 15 8 7 4 3 0

CPX-FB36Remote I/O


40002 Data for the system table (write access)

Digital 4-off out-put module(CPX-4DA)

2 40003 x Output data

MPA pneumaticsmodule withdiagnostic functi-on








Tab. D/33: Output data addressing example 1 (CPX terminal from Fig. D/1)



CPX terminal with digital and analogue I/O modules

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 and MPApneumatics



Module Loca-tion

Modbusaddress

Input data

Bit 15 8 7 4 3 0

CPX-FB36Remote I/O


45393 Data from the system table (read access)


Digital 8-off inputmodule (CPX-8DE)

1 45395 0 Input data

45396 Module diagnostics data

Analogue 2-offinput module(CPX-2AE)

2 45397 Analogue inputs channel 0

45398 Analogue inputs channel 1


Analogue 2-offoutput module(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 Loca-tion

Modbusaddress

Output data

Bit – – 15 8 7 4 3 0

CPX-FB36Remote I/O


40002 Data for the system table (write access)

Analogue 2-offoutput module(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 P.BE-CPX-FB36-EN en 1309NH English

Appendix E

Index

E. Index

E-2 Festo P.BE-CPX-FB36-EN en 1309NH English

Table of contents

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

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

E. Index


E.1 Index

A

Abbreviations, Product-specific XII. . . . . . . . . . . . . . . . . . . . .

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

Address space B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Addressing B-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Address assignment B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Addressing example, Remote I/O Modbus TCP D-23. . . . . . .

Assembly 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B

Baud rate 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C

Cables, Network 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CEC 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ConnectingNetwork 1-13, 1-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Voltage supply 1-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connection technology 1-14. . . . . . . . . . . . . . . . . . . . . . . . . .

CP interface B-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CPA pneumatics B-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CPX-CEC 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CPX-FEC 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D

Diagnostic data 4-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

E. Index


Diagnostics via I/O diagnostic interface 4-13. . . . . . . . . . . . .

Diagnostics via LEDs 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

DIL switch cover, Remove and mount 1-8. . . . . . . . . . . . . . . . .

DIL switches 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dismantling 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DLR 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Duplex mode 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E

Electric modules B-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Electrical connection and display components 1-4. . . . . . . .

EtherNet/IP Objects C-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

F

Fail safe mode 3-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

fec 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Force parameter C-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I

I/O diagnostics interface 4-13. . . . . . . . . . . . . . . . . . . . . . . . .

ICO/BMP file 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Idle mode 3-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IGMP snooping 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Inputs, Calculate address allocation B-12. . . . . . . . . . . . . . . .

Instructions on the description IX. . . . . . . . . . . . . . . . . . . . . . .

Intended use VII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interfaces, Pneumatics B-8. . . . . . . . . . . . . . . . . . . . . . . . . . .

IP address, Setting 1-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E. Index


IP65/IP67 1-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISO pneumatics (VTSA) B-8. . . . . . . . . . . . . . . . . . . . . . . . . . .

L

LayoutBus nodes B-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .in Remote Controller operating mode 3-19. . . . . . . . . . . . .Pneumatics (valves) B-8. . . . . . . . . . . . . . . . . . . . . . . . . . . .with CPX-FMT 3-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .with EDS files 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .with Generic Ethernet Module 3-10. . . . . . . . . . . . . . . . . . .

LEDs 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M

Midi/Maxi pneumatics B-8. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Module identifiers B-3, B-4. . . . . . . . . . . . . . . . . . . . . . . . . . .

moduleselectrical B-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .pneumatic B-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multicast telegram 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N

NetworkConnection technology 1-14. . . . . . . . . . . . . . . . . . . . . . . .Network cables 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Network connectors 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . .Segmentation 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network setting, Saved 1-19. . . . . . . . . . . . . . . . . . . . . . . . . .

Network settings, advanced 1-22. . . . . . . . . . . . . . . . . . . . . .

E. Index


O

Objectsfor network settings C-8. . . . . . . . . . . . . . . . . . . . . . . . . . . .for system data and diagnostics C-18. . . . . . . . . . . . . . . . .for the I/O connection C-13. . . . . . . . . . . . . . . . . . . . . . . . .Overview C-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outputs, Calculate address allocation B-12. . . . . . . . . . . . . .

P

ParameterisationExamples C-43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .via configuration data 3-26. . . . . . . . . . . . . . . . . . . . . . . . .with CPX-FMT and system start with saved parameters 3-27With operator unit 3-26. . . . . . . . . . . . . . . . . . . . . . . . . . . .with PLC user program 3-26. . . . . . . . . . . . . . . . . . . . . . . . .

PELV 1-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pictograms XI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pin allocation, Network interfaceX1 1-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .X2 1-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Plug 1-14, 1-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pneumatic interfaces B-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pneumatic modules B-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Protection class IP65/IP67 1-23. . . . . . . . . . . . . . . . . . . . . . .

ProtocolDevice Level Ring 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .EtherNet/IP 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IGMP 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Modbus TCP 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Q

QuickConnect 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

R

Remote Controller 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Router 1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E. Index


S

Service VIII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SettingData size 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Diagnostics mode 1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . .DIL switches 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IP addressing 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Operating mode 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Protocol 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Status bits 4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Strain relief 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Switch 1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

T

Target group VIII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Text markings XI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

U

Used, Modbus TCP D-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User instructions X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

V

Voltage supply 1-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

VTSA pneumatics (ISO) B-8. . . . . . . . . . . . . . . . . . . . . . . . . . .

W

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

E. Index


Terminal CPX Busnode CPX-FB36 - FestoElectronics description Bus node Network protocol EtherNet/IP...

Documents

Transcript of Terminal CPX Busnode CPX-FB36 - FestoElectronics description Bus node Network protocol EtherNet/IP...