Terminal CPX Bus node CPX-FB39 - Festo...Bus node CPX-FB39 6 Festo – P.BE-CPX-FB39-EN – 1504NH...

Electronics

description

Network protocol

Sercos III

8028633

1504NH

[8028639]

Bus node CPX-FB39

Terminal CPX

Bus node CPX-FB39

2 Festo – P.BE-CPX-FB39-EN – 1504NH – English

Translation of the original instructions

P.BE-CPX-FB39-EN

CODESYS®, SERCOS®, SPEEDCON® are registered trademarks of the respective trademark owners in

certain countries.

Identification of hazards and instructions on how to prevent them:

Warning

Hazards that can cause death or serious injuries.

Caution

Hazards that can cause minor injuries or serious material damage.

Other symbols:

Note

Material damage or loss of function.

Recommendations, tips, references to other documentation.

Essential or useful accessories.

Information on environmentally sound usage.

Text designations:

� Activities that may be carried out in any order.

1. Activities that should be carried out in the order stated.

– General lists.

Bus node CPX-FB39

Festo – P.BE-CPX-FB39-EN – 1504NH – English 3

Table of Contents – Bus node CPX-FB39

1 Safety and requirements for product use 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Safety 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.1 General safety instructions 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.2 Use for intended purpose 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Requirements for product use 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.1 Technical requirements 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.2 Qualification of the specialized personnel (requirements for the personnel) 9. . .

1.2.3 Range of application and certifications 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.4 Quoted guidelines and standards 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Installation 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 General instructions on installation 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Electrical connections and indicators 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Mounting and dismantling 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Mounting 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Dismantling 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.3 Complying with degree of protection IP65/IP67 13. . . . . . . . . . . . . . . . . . . . . . . . .

2.4 Settings of the DIL switches on the bus node 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.1 Removing and attaching the DIL switch cover 14. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.2 Arrangement of the DIL switches 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.3 Setting the DIL switches 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.4 Setting the operating mode 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.5 Setting of the diagnostic mode (remote I/O) 16. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.6 Setting of the I/O mode (remote controller) 17. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.7 Set the Sercos address 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5 Connecting to the network 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.1 General notes about Sercos networks 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.2 Overview of connection technology and network plugs 19. . . . . . . . . . . . . . . . . . .

2.5.3 Cable specification 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.4 Network connections 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.5 Setting the IP address 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.6 Webserver function 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6 Power supply 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Commissioning 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 General points about Sercos III 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Depiction of the CPX system on the Sercos-device model 25. . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Device description 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bus node CPX-FB39


3.4 Address assignment 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.1 Bus node 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.2 Digital modules 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.3 Analogue modules 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.4 Technology modules 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.5 Determination of the address assignment 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Addressing 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5.1 Basic rules for addressing 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5.2 Example 1: CPX terminal with electronic modules VMPA1 and VMPA2 36. . . . . . . .

3.5.3 Example 2: CPX terminal with electrical interface (CP interface) 37. . . . . . . . . . . .

3.5.4 Example 3: CPX terminal with analogue module and pneumatic interface 38. . . . .

3.5.5 Address assignment after extension/conversion 39. . . . . . . . . . . . . . . . . . . . . . . .

3.6 Incorporation in the host system 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6.1 Codesys control software 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6.2 Installing device description files (SDDML files) 40. . . . . . . . . . . . . . . . . . . . . . . . .

3.6.3 Inserting field bus 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6.4 Insert bus node 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6.5 Inserting other modules 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6.6 I/O assignment 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.6.7 Changing parameters in Codesys 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.7 Parameterisation 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.7.1 Introduction to parameterisation 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.7.2 Prerequisite for parameterization 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.7.3 Methods of parameterisation 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.7.4 Parameterisation via the Festo Maintenance Tool (CPX-FMT) software 52. . . . . . .

3.7.5 Parameterization with the control device (CPX-MMI) 52. . . . . . . . . . . . . . . . . . . . .

3.7.6 Parameterization via Sercos III 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Diagnostics and error handling 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Summary of diagnostics options 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Diagnostics via LED displays 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 Standard operating status 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2 CPX-specific LEDs 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.3 Network-specific LEDs 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 Diagnostics via status bits 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4 Diagnostics via the I/O diagnostics interface 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5 Diagnostics via Sercos III 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5.1 Basic diagnostic functions 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5.2 I/O diagnostics 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5.3 I/O diagnostics with Festo-specific extensions 62. . . . . . . . . . . . . . . . . . . . . . . . . .

4.6 Error handling 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bus node CPX-FB39


A Technical appendix 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.1 Technical data 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.2 List of abbreviations 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B Identification Numbers (IDNs) 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1 Sercos Communication Profile (SCP) 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.1 Function Group - SCP Identification 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.2 Function Group - Timing 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.3 Function Group - Telegram Setup 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.4 Function Group - Control 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.5 Function Group - Bus Diagnosis 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.6 Function Group - Connection 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1.7 Function Group - NRT 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2 Generic Device Profile (GDP) 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.1 Function Group - Diagnosis 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.2 Function Group - Administration 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.3 Function Group - Identification 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.4 Function Group - Time 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3 Function Specific Profile IO (FSP IO) 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3.1 Function Group - Generic I/O 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3.2 Function Group - Bus Coupler 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3.3 Manufacturer-specific extensions to the Function Specific Profile IO (FSP IO) 73. .

B.4 Overview of the supported classes 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.4.1 Supported classes of the Sercos Communication Profile (SCP) 74. . . . . . . . . . . . .

B.4.2 Supported classes of the Generic Device Profile (GDP) 74. . . . . . . . . . . . . . . . . . .

C Diagnostic messages 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.1 Depiction of CPX diagnostic classes on Sercos diagnostic classes 75. . . . . . . . . . . . . . . . . . .

C.2 Depiction of CPX diagnostic messages on Sercos status codes 75. . . . . . . . . . . . . . . . . . . . .

Index 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bus node CPX-FB39


Instructions on this documentation

This description contains specific information about the installation, commissioning and diagnostics of

the CPX bus node for Sercos III as well as specific information about Sercos III relating to the paramet

erization, commissioning, programming and diagnostics of a CPX terminal in a Sercos III network.

You will find further information about Sercos III on the Internet:

� www.sercos.org

General basic information about the mode of operation, mounting, installation and commissioning of

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

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

An overview of the structure of user documentation for the CPX terminal can be found in

the CPX system description (� P.BE-CPX-SYS-…).

Service

Please consult your regional Festo contact if you have any technical problems.

1 Safety and requirements for product use



1.1 Safety

1.1.1 General safety instructions

� The general safety information in the corresponding chapters must be observed.

Special safety and danger warnings are written directly before the action instruction.

Please Note

Damage to the product from incorrect handling.

� Switch off the supply voltage before mounting and installation work. Switch on sup

ply voltage only when mounting and installation work are completely finished.

� Never unplug or plug in a product when powered!

� Observe the handling specifications for electrostatically sensitive devices.

1.1.2 Use for intended purpose

The module described in this document, used in conjunction with a CPX terminal, makes it possible to

connect up as a participant on a Sercos III network.

The module is intended for use in an industrial environment. Outside of industrial environments, e.g. in

commercial and mixed-residential areas, actions to suppress interference may have to be taken.

The module is intended exclusively for use in CPX terminals from Festo for installation in machines or

automated systems and may be used only in the following ways:

– In perfect technical condition

– in original status without unauthorised modifications, except for the adaptations described in this

documentation

– within the limits of the product defined through the technical data (� A.1 Technical data).



Warning

Electrical voltage

Injury caused by electric shock, damage to machine and to system

� For the electrical power supply, use only PELV circuits in accordance with

IEC 60204-1 (Protective Extra-Low Voltage, PELV).

� Observe the general requirements of IEC 60204-1 for PELV circuits.

� Use only voltage sources which guarantee reliable electrical isolation of the operat

ing and load voltage in accordance with IEC 60204-1.

� Always connect all circuits for operating and load voltage supply UEL/SEN, UVAL and

UOUT.

Through the use of PELV circuits, protection against electric shock (protection against direct and indir

ect contact) is ensured in accordance with IEC 60204-1.

� Note the information about the power supply and about the applicable grounding

measures provided in the CPX system description (� P.BE-CPX-SYS-…).

Please Note

In the event of damage caused by unauthorised manipulation or other than intended

use, the guarantee is invalidated and the manufacturer is not liable for damages.

1.2 Requirements for product use

� Make this documentation available to the design engineer, installer and personnel responsible for

commissioning the machine or system in which this product is used.

� Make sure that the specifications of the documentation are always complied with. Consider also the

documentation for other components and modules (e.g. CPX system description, P.BE-CPX-SYS-…).

� Take into consideration the legal regulations applicable for the location as well as:

– Regulations and standards

– Regulations of the testing organisations and insurers

– national specifications.



1.2.1 Technical requirements

General conditions for the correct and safe use of the product, which must be observed at all times:

� Comply with the connection and ambient conditions specified in the technical data of the product

(� Appendix A.1) and for all connected components.

Only compliance with the limit values or load limits permits operation of the product in accordance

with the relevant safety regulations.

� Observe the notes and warnings in this documentation.

1.2.2 Qualification of the specialized personnel (requirements for the personnel)

This description is directed exclusively to technicians trained in control and automation technology,

who are experienced in:

– the installation, commissioning, programming and diagnosis of programmable controllers (PLCs)

and field bus systems

– the applicable regulations for operating safety-engineered systems

– the applicable regulations for accident prevention and industrial safety

– the documentation for the product.

1.2.3 Range of application and certifications

Standards and test values, which the product complies with and fulfils, can be found in the “Technical

data” section (� Appendix A.1). The product-relevant EU directives can be found in the declaration of

conformity.

Certificates and declaration of conformity on this product can be found at www.festo.com.

1.2.4 Quoted guidelines and standards

Issue status

ANSI/TIA-568-B.1-3:2003-02 IEC 61076-2:2011-06

IEC 60204-SER:2013-04 IEEE 802.3:2012

IEC 60204-1:2009-02 ISO/IEC 11801:2008-09

IEC 60529:2001-02

Tab. 1.1

2 Installation


2 Installation

2.1 General instructions on installation

Warning

Uncontrolled movement of the actuators, loose tubing, undefined switching states of

the electronics

Injury caused by moving parts, damage to machine and to system

Before mounting and installation work:

� Switch off the power supply

� Switch off the compressed air supply

� Vent the pneumatics.

Caution

The CPX bus node contains electrostatically sensitive devices.

� Therefore, do not touch any components.


They will help you avoid damage to the electronics.

Please Note

Ensuring degree of protection IP65/IP67

� Use cover caps or dummy plugs to seal unused connections

(� 2.3.3 Complying with degree of protection IP65/IP67).

2 Installation


2.2 Electrical connections and indicators

The following connections and displays are located on the bus node:

1 Network status and CPX-specific LEDs

2 Network connection X11)

3 Network connection X21)

4 DIL switch cover

5 Service interface2) for the control device

(CPX-MMI) or the Festo Maintenance Tool

software (CPX-FMT)

1

2

3

4

5

1) Connection bush M12, D-coded, 4-pin2) Connection bush M12, A-coded, 5-pin

Fig. 2.1

2 Installation


2.3 Mounting and dismantling

Warning

Electrical voltage


� Switch supply power off before assembly work.

2.3.1 Mounting

Please Note

Material damage due to incorrect mounting

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

– plastic: thread-cutting tapping screws

– metal: screws with metric thread.

When ordering an individual module, all the screws required are enclosed.

1. Check seal and sealing surface. Replace

damaged parts.

2. Push the module carefully and without tilting

into the interlinking block up to the stop.

3. Turn the screws into the existing thread.

4. Tighten the screws in diagonally opposite

sequence. Tightening torque: 0.9 … 1.1 Nm.

1 Screws

2 Module

3 Interlinking block

2

3

1

Fig. 2.2

Please Note

In the Remote I/O operating mode, the bus node must be placed as the first module

(slot 0) to the far left of the CPX terminal.

2.3.2 Dismantling

1. Unscrew screws.

2. Pull the module without tilting out of the interlinking block.

2 Installation


2.3.3 Complying with degree of protection IP65/IP67

� Use connection technology with type of protection IP65/IP67 (� www.festo.com/catalogue,

examples in Tab. 2.1).

� Use cover caps to seal unused connections.

connection Connection technology Cover cap

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

Service interface Connecting cable KV-M12-M12-…1)

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

2) Included in the scope of delivery

Tab. 2.1

2 Installation


2.4 Settings of the DIL switches on the bus node

In order to set the bus node, you must first remove the cover for the DIL switches.

Caution

The CPX bus node contains electrostatically sensitive devices.

� Therefore, do not touch any components.


They will help you avoid damage to the electronics.

2.4.1 Removing and attaching the DIL switch cover

� Use an appropriate tool to remove or attach the DIL switch cover.

Please Note

Observe the following notes when removing or attaching the DIL switch cover:

� Disconnect the power supply before removing the cover.

� Make sure that the seal is seated correctly when attaching the cover!

� Tighten the two mounting screws with a max. torque of 0.4 Nm.

2.4.2 Arrangement of the DIL switches

There are 3 DIL switches available for configuring the bus node. These are located under the DIL switch

cover (� 2.4.1 Removing and attaching the DIL switch cover).

1 DIL switch 1:

– operating mode “remote I/O”

– operating mode “remote controller”

2 DIL switch 2:1)

– diagnostics mode (remote I/O)

– I/O mode (remote controller)

3 DIL switch 3:

– Sercos address (1 … 255)

1 2

3

1) The function is dependent on the set operating mode (� DIL switch 1)

Fig. 2.3

2 Installation


2.4.3 Setting the DIL switches

1. Switch supply power off.

2. Remove DIL switch cover (� 2.4.1).

3. Perform required settings (� 2.4.4 … 2.4.7).

4. Reinstall DIL switch cover (� 2.4.1).

Please Note

Parameterisation via DIL switch settings is taken over only when the power supply is

switched on.

2.4.4 Setting the operating mode

With the DIL switch element 1.1 on DIL switch 1 the operating mode of the bus node is set.

Operating mode Setting DIL switch 1

Remote I/O operating mode

All functions of the CPX terminal are controlled directly by the

Sercos controller or by a superordinate PLC/IPC. The bus node

takes charge of connection to the Sercos III network.

1.1: OFF

(factory setting)

Remote Controller operating mode

An FEC or CEC integrated into the CPX terminal controls all

functions of the CPX terminal, i.e. the FEC or CEC undertakes the

I/O control. The bus node takes charge of connection to the

Sercos III network.

1.1: ON

Tab. 2.2

Please Note

Setting of the operating mode via DIL switch 1 has priority over all other settings.

The switch element 1.2 of DIL switch 1 is reserved and without function.

2 Installation


2.4.5 Setting of the diagnostic mode (remote I/O)

The diagnostic mode is available only in the remote I/O operating mode.

Diagnostic mode (remote I/O operating mode) Setting DIL switch 2

I/O diagnostics interface and status bits are switched off 2.1 OFF

2.2 OFF

(factory setting)

I/O diagnostics interface is switched on1) 2.1 ON

2.2 OFF

Status bits are switched on2) 2.1 OFF

2.2 ON

Reserved 2.1 ON

2.2 ON

1) The I/O diagnostic interface occupies an additional 16 input and 16 output bits

2) The status bits occupy an additional 16 input bits

Tab. 2.3

Please Note

The diagnostics mode reduces the available address space.

� When planning your CPX terminal, consider that the number of input and output bits

available for communication is reduced with usage of the diagnostic mode.

Subsequent activation of the diagnostics mode requires a reconfiguration.

� Observe that the CPX-internal I/O image can be displaced during subsequent activa

tion of the diagnostics mode.

� In this case, repeat the network configuration.

2 Installation


2.4.6 Setting of the I/O mode (remote controller)

The I/O mode is available only in the remote controller operating mode.

Number of I/O bytes (Remote Controller operating mode) Setting DIL switch 2

8 byte I/8 byte O for communication of the bus node with the

CPX-FEC or CPX-CEC.

2.1 OFF

2.2 OFF

(factory setting)

Reserved 2.1 ON

2.2 OFF

16 byte I/16 byte O for communication of the bus node with the

CPX-FEC or CPX-CEC.

2.1 OFF

2.2 ON

Reserved 2.1 ON

2.2 ON

Tab. 2.4

2 Installation


2.4.7 Set the Sercos address

DIL switch elements 3.1 to 3.8 are used for setting the binary coding of the Sercos address.

If all switch elements of DIL switch 3 are in the OFF setting, the Sercos address can

altered dynamically by write accesses to parameter S-0-1040.

Sercos address Setting DIL switch 3

Permitted addresses:

– 1 … 255 (via DIL switches)

– 0 … 511 (dynamically via S-0-1040)1)

Factory reset:

– 0 (DIL switch)

– 254 (dynamic) 12

34

56

78 3.8: 27 128

3.7: 26 64

3.6: 25 323.5: 24 16

3.4: 23 8

3.3: 22 43.2: 21 2

3.1: 20 1

1) Only with dynamic address issue (all switch elements in the OFF setting)

Tab. 2.5

Address 05 Address 38 Address 55 Address 106 Address 239

12

34

56

78

+

–

––

+–

Address:

–

5

1

4

–

12

34

56

78

+

–

––

–+

Address:

+

38

32

42

–

12

34

56

78

+

–

+–

++

Address:

+

55

32

42

–

16

1 12

34

56

78

–

+

–+

–+

Address:

+

106

6432

8

2

–

12

34

56

78

+

+

–+

++

Address:

+

+

239

1286432

8421

Tab. 2.6

2 Installation


2.5 Connecting to the network

2.5.1 General notes about Sercos networks

Please Note

A Sercos network must always be structured as as ring or line topology.

For this reason, the use of hubs or switches is not permitted.

Please Note

Connecting a PC to the Sercos network (e.g. to use the bus node with the CPX-FMT soft

ware).

– With line topology:

� Connect the PC to the free port of the Sercos slave.

– With ring topology:

� Use a network tap suitable for Sercos.

Please Note

Sub-assemblies with Ethernet interfaces should only be operated in networks if all con

nected network components are supplied by PELV circuits or integrated power circuits

with equivalent protection.

Installation guidelines

Installation guidelines can be sourced from the Sercos user organization

(� http://www.sercos.org).

2.5.2 Overview of connection technology and network plugs

Note

Faulty installation and high transmission rates may cause data transmission errors as a

result of signal reflections and attenuations.

� Note wiring specification (� Tab. 2.8).

Transmission errors can be caused by:

– faulty screened connection

– branches

– transmission over distances which are too long

– unsuitable cables.

Connection technology Network connectors

2 x M12 bush, D-coded, 4-pin, in accordance with

IEC 61076-2, SPEEDCON compatible

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

Tab. 2.7

2 Installation


2.5.3 Cable specification

� Use sheathed Industrial Ethernet wiring of category Cat 5 or higher.

The bus node supports the “crossover detection” function (Auto-MDI/MDI-X).

To connect the bus node to the network or to a PC, this means you can choose between

patch cables or crossover cables.

The circuitry for network connections X1 and X2 is adapted automatically.

CPX-FB39 Cable specification

Cable type Industrial Ethernet cable, screened

Transmission class Category Cat 5

Cable diameter 6 … 8 mm

Wire cross section 0.14 … 0.75 mm², AWG 221)

Connection length Maximum 100 m2)

1) Required for maximum connection length between the network participants

2) corresponding to specification for Ethernet networks, based on ISO/IEC 11801, ANSI/TIA/EIA-568

Tab. 2.8

Please Note

When mounting the CPX terminal on a moving part of a machine.

� Use network wiring with tension relief.

� Note corresponding stipulations of IEC 60204.

2.5.4 Network connections

There are two 4-pin, D-coded M12 sockets on the bus node for the network connection. The sockets are

compatible with SPEEDCON plugs.

Socket1)

M12, 4-pin Pin

Connection [X1] Connection [X2]

Signal Explanation Signal Explanation

1

2

3

4

TX+

RX+

TX–

RX–

Transmitted data +

Received data +

Transmitted data –

Received data –

RX+

TX+

RX–

TX–

Received data +

Transmitted data +

Received data –

Transmitted data –

1) Functional earth is accomplished via the housing.

Tab. 2.9

Functional earth

Please Note

The shielded connection for both network connections is linked by RC element to the

ground potential of the CPX terminal.

� Connect the ground connection of left-hand terminal plate in a low-current and

low-impedance manner to the ground potential (� CPX system description

P.BE-CPX-SYS-…).

2 Installation


2.5.5 Setting the IP address

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

– Dynamic addressing via DHCP/BOOTP

– Stored network setting.

The IP address is factory-set to 192.168.1.20.

Dynamic addressing via DHCP/BOOTP

Make sure that a DHCP/BOOTP server is located in the network.

� Alternatively activate dynamic addressing by DHCP/BOOTP via:

– Operator unit (CPX-MMI)

– Festo Maintenance Tool (CPX-FMT) software

– Sercos IDNs.

Saved network settings

The bus node CPX-FB39 offers the option of saving network settings in a non-volatile memory unit.

DHCP/BOOTP is thereby deactivated.

� Alternatively change the network settings via:

– Operator unit (CPX-MMI)

– Festo Maintenance Tool (CPX-FMT) software

– Higher-order system

– Sercos IDNs.

This activates saving of the network settings.

2 Installation


2.5.6 Webserver function

A web server is integrated in the bus node CPX-FB39. It makes available read access to the most im

portant parameters and diagnostic functions of the CPX terminal.

Procedure

1. Open an Internet browser on a PC with a connection to the network.

2. Enter the set/identified IP address of the bus node in the address line of the Internet browser

(� 2.5.5 Setting the IP address).

Fig. 2.4

2 Installation


2.6 Power supply

The operating and load voltage supply is directed via the interlinking blocks (� CPX system descrip

tion P.BE-CPX-SYS-…).

Warning

Electrical voltage


� For the electrical power supply, use only PELV circuits in accordance with

IEC 60204-1 (Protective Extra-Low Voltage, PELV).

� Observe the general requirements of IEC 60204-1 for PELV circuits.

� Use only voltage sources which guarantee reliable electrical isolation of the operat

ing and load voltage in accordance with IEC 60204-1.

� Always connect all circuits for operating and load voltage supply UEL/SEN, UVAL and

UOUT.

Through the use of PELV circuits, protection against electric shock (protection against direct and indir

ect contact) is ensured in accordance with IEC 60204-1.

Note the information about the power supply and about the applicable grounding meas

ures (� CPX system description P.BE-CPX-SYS-…).

3 Commissioning


3 Commissioning

Please Note

Only commission a correctly installed CPX terminal (� 2 Installation).

Please Note

A firmware update can be performed by the Festo Field Device Tool (FFT).

The current version is available on the Festo Support Portal on the Internet

(� www.festo.com/sp).

– General information on commissioning the CPX terminal as well as a detailed

description of individual parameters is found in the CPX system description

(� P.BE-CPX-SYS-…).

– Information on commissioning the analogue pneumatic interfaces and I/O modules

can be found in the description (� P.BE-CPX-EA-…).

– Instructions on commissioning the pneumatic components can be found in the corres

ponding description of pneumatics.

3.1 General points about Sercos III

Please Note

The bus node CPX-FB39 is a remote I/O system that communicates with the Sercos

controller via the Sercos IO profile (Function Specific Profile IO).

Sercos III is an Ethernet-based communication protocol for automation applications.

Communication on a Sercos III network is based on the time-stop process with cyclical data transmis

sion in the form of telegrams based on the master-slave principle. This combines real-time and non-

real-time communication channels in a communication system.

Real Time Channel (RTC)

During transmission in real-time, a distinction is made between two types of telegram.

– Master data telegram (MDT): For communication of nominal/setpoint data from master to slaves.

– Acknowledge telegram (AT): For communication of status data from slaves to master and for trans

verse communication between the individual controllers or slaves.

Non-real-time channel (Universal Communication Channel - UCC)

For the exchange of standard Ethernet telegrams between any participants on the network.

You will find further information about Sercos III on the Internet:

� www.sercos.org

3 Commissioning


3.2 Depiction of the CPX system on the Sercos-device model

The underlying depiction of the CPX system on Sercos is illustrated by the next graphic (� Fig. 3.1).

The CPX system is illustrated here as a Sercos device with a Sercos interface, a Sercos slave and the

associated sub device. Communication is performed by the Sercos interface and the Sercos slave. Gen

eric parts of the device application are implemented as part of the sub device. The resource IO is as

signed to the sub device: It depicts the Sercos function profile (Function Specific Profile IO) and in

cludes a depiction of the individual CPX modules on Sercos.

consists uses

includesincludes

corresponds

owns owns

includes

0…n1 1…n

0…n1

1

1 1

1

1

1 1

11

1 1

CPX system CPX modules

Sub Device Resource IODevice

(logical)

Sercos

interface

Sercos

slave

Generic Device Profile Function Specific Profile IO

Sercos Communication Profile

Application

Physical structure

communication

Sercos-III network

Fig. 3.1

3.3 Device description

During initial commissioning of a Sercos participant, the controller software is notified of certain prop

erties of the participant. These properties are administered in what are known as device description

files in standardized XML format.

The device description of Sercos-III devices is in the form of SDDML files (Sercos Device Description

Markup Language) and is based on the Sercos-III device model. This provides a separate device de

scription file for each device.

The device description files (SDDML files) are available on the Festo support portal on the

Internet (� www.festo.com/sp).

3 Commissioning


3.4 Address assignment

A CPX terminal consists of a different number of inputs and outputs, depending on your order and the

configuration of the bus node.

The inputs and outputs are assigned automatically within the CPX terminal.

When using device description files (SDDML files) the controller software can extrapolate

the complete address assignment automatically.

Warning

Uncontrolled movement of the actuators, undefined switching statuses.

Injury to people, damage to the machine and system.

The byte sequence of the process data is Little Endian.

� Ensure that the process data is interpreted correctly.

Please Note

– Including bus nodes, a maximum of 10 electrical modules plus a pneumatic interface

and/or MPA pneumatic module is permitted in a CPX terminal.

– The address space of a CPX terminal is limited. The bus node provides the CPX ter

minal a maximum address space of 64 bytes for inputs and 64 bytes for outputs.

– An activated diagnostic mode reduces the number of available I/O bytes.

– Each module of the CPX terminal occupies a specific number of bits, bytes or words

for module communication.

� Establish the address assignment (number of allocated inputs/outputs) on the CPX terminal prior to

commissioning.

Tab. 3.8 serves to determine the address assignment and/or the number of assigned

inputs and outputs on the CPX terminals.

The number of assigned inputs and outputs for modules can be found in the following

tables:

– Bus node CPX-FB39:

– FG S-0-1500.SI.0 – Bus Coupler (� Tab. 3.1)

– Digital modules:

– FG S-0-1502.SI.0 – Digital Output (� Tab. 3.2)

– FG S-0-1503.SI.0 – Digital Input (� Tab. 3.3).

– Analog modules:

– FG S-0-1504.SI.0 – Analog Output (� Tab. 3.4)

– FG S-0-1505.SI.0 – Analog Input (� Tab. 3.5).

– Technology modules:

– FG S-0-1507.SI.0 – Complex Protocol (� Tab. 3.6)

– FG S-0-1508.SI.0 – Sub Bus Master(� Tab. 3.7).

3 Commissioning


3.4.1 Bus node

FG S-0-1500.SI.0 (Bus Coupler)

Bus node CPX-FB39 Module type Module

identifiers1)

Allocated address space

Inputs Outputs

Remote I/O operating mode

without diagnostics mode CPX-FB39 FB39-RIO – –

Status bits2) 1x 16 bit3) –

I/O diagnostics interface4) 1x 16 bit 1x 16 bit

Remote Controller operating

mode4)

CPX-FB39 FB39-RC 8x 8bit

8x 16 bit5)

8x 8 bit

8x 16 bit5)

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

2) The additional input data are set up as FG S-0-1503.SI.0 (Digital Inputs).

3) Diagnostic mode status bits assigns 2 byte address space (8 inputs and/or 8 bits remain unused).

4) The additional input and output data are set up as FG S-0-1507.SI.0 (Complex Protocol).

5) Assigned address space depends upon the setting of DIL switch 2.2.

Tab. 3.1

If the bus node is operated in Remote Controller operating mode, then only the FG Bus

Coupler with additional FG Complex Protocol is depicted on structural entity 0. No depic

tion of I/O modules takes place on Sercos objects.

3 Commissioning


3.4.2 Digital modules

FG S-0-1502.SI.0 (Digital Output)

Module designation Module type Module

identifiers1)


Inputs Outputs

Output module

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

8-fold CPX-8DA 8DO – 8x 1 bit

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

Input/output module

each 8x CPX-8DE-8DA 8DI/8DO 8x 1 bit3) 8x 1 bit

each 8-fold (with terminal

strip)

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

3POL

L-8DI8DO-PI 8x 1 bit3) 8x 1 bit

Electronics module

for MPA1 pneumatics module

(1 … 8 valves)

VMPA1-FB-EMS-8 MPA1S – 8x 1 bit4)

for MPA2 pneumatic module

(1 … 4 valves)

VMPA2-FB-EMS-4 MPA2S – 8x 1 bit5)

Electronics module (electrically isolated)


(1 … 8 valves)

VMPA1-FB-EMG-8 MPA1G – 8x 1 bit4)


(1 … 4 valves)

VMPA2-FB-EMG-4 MPA2G – 8x 1 bit5)

Electrical module with diagnostic function


(1 … 8 valves)

VMPA1-FB-EMS-D2-8 MPA1S-D – 8x 1 bit4)


(1 … 4 valves)

VMPA2-FB-EMS-D2-4 MPA2S-D – 8x 1 bit5)

Electrical module with diagnostic function (electrically isolated)


(1 … 8 valves)

VMPA1-FB-EMG-D2-8 MPA1G-D – 8x 1 bit4)


(1 … 4 valves)

VMPA2-FB-EMG-D2-4 MPA2G-D – 8x 1 bit5)


2) Digital 4x output modules (CPX-4DA) always occupy 8 outputs or 1 byte of address space.

3) Input data � FG S-0-1503.SI.0 (Digital Input)

4) VMPA1 modules always occupy 8 outputs regardless of the number of valves fitted.

5) VMPA2 modules always occupy 8 outputs, although only 4 bits are used.

6) Setting via DIL switches of the pneumatic interface.

3 Commissioning


Module designation Allocated address spaceModule

identifiers1)

Module typeModule designation

OutputsInputs

Module

identifiers1)

Module type

End plate (pneumatic interface

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

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

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

1 ... 4 solenoid coils – – 8x 1 bit





Pneumatic interface

for valve terminal

VTSA-/VTSA-F

with setting:6)

VABA-… VTSA -

type 44/45

1 ... 8 solenoid coils – 8x 1 bit





2) Digital 4x output modules (CPX-4DA) always occupy 8 outputs or 1 byte of address space.

3) Input data � FG S-0-1503.SI.0 (Digital Input)

4) VMPA1 modules always occupy 8 outputs regardless of the number of valves fitted.

5) VMPA2 modules always occupy 8 outputs, although only 4 bits are used.

6) Setting via DIL switches of the pneumatic interface.

Tab. 3.2

3 Commissioning


FG S-0-1503.SI.0 (Digital Input)


identifiers1)


Inputs Outputs

input module

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

8 valves CPX-8DE 8DI 8x 1 bit –

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

8-fold (with channel

diagnostics)

CPX-8DE-D 8DI-D 8x 1 bit –

16 valves CPX-16DE 16DI 16x 1 bit –

16-fold (with channel

diagnostics)

CPX-M-16DE-D 16DI-D 16x 1 bit –

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

INPUT/OUTPUT MODULE

each 8x CPX-8DE-8DA 8DI/8DO 8x 1 bit 8x 1 bit3)

each 8-fold (with terminal

strip)

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

3POL

L-8DI8DO-PI 8x 1 bit 8x 1 bit3)


2) Digital quadruple input modules (CPX-4DE) always occupy 8 inputs.

3) Output data � FG S-0-1502.SI.0 (Digital Output)

Tab. 3.3

– The address assignment within the individual CPX I/O modules can be found in the

description for the I/O modules (� P.BE-CPX-EA-…).

– Information about pneumatic interfaces and pneumatic modules can be found in the

corresponding pneumatics descriptions.

– An overview of the “Descriptions of the CPX terminal” documentation can be found in


– From the technical point of view, the individual pneumatic modules each represent an

electric module for controlling the attached valves.

3 Commissioning


3.4.3 Analogue modules

FG S-0-1504.SI.0 (Analog Output)


identifiers1)


Inputs Outputs

Analog module (2 outputs) CPX-2AA-U-I 2AO – 2x 16 Bit

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


2) Input data � FG S-0-1505.SI.0 (analog input)

Tab. 3.4

FG S-0-1505.SI.0 (Analog Input)


identifiers1)


Inputs Outputs

Pressure sensors VMPA-FB-PS-… MPA-P 1x 16 bit –

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

Analogue module

2 inputs CPX-2AE-U-I 2AI 2x 16 Bit –

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

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

4 inputs (temperature module

for RTD sensors)

CPX-4AE-T 4AI-T 2x 16 Bit

4x 16 bit3)

–

4 inputs (temperature module

for TC sensors)

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

4 inputs (pressure sensor

module 0 … 10 bar)

CPX-4AE-P-D10 4AI-P-D10 4x 16 bit –

4 inputs (pressure sensor

module –1 … 1 bar)

CPX-4AE-P-B2 4AI-P-B2 4x 16 bit –


2) Output data � FG S-0-1504.SI.0 (analog output)

3) Depending on the configuration.

Tab. 3.5

The address assignment within the individual CPX analogue I/O modules can be found in

the description for the analogue I/O modules (� P.BE-CPX-AX-…).

3 Commissioning


3.4.4 Technology modules

FG S-0-1507.SI.0 (Complex Protocol)


identifiers1)


Inputs Outputs

INPUT/OUTPUT MODULE CPX-2ZE2DA 2CI2DO 3x 32 bit 3x 32 bit

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

Control block

(multi-axis interface)

CPX-CMXX CMXX 8x 16 bit 8x 16 bit

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

Control block

(FHPP interface)

CPX-CM-HPP CM-HPP 32x 8 bit 32x 8 bit

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


Tab. 3.6

FG S-0-1508.SI.0 (Sub bus Master)


identifiers1)


Inputs Outputs

Electrical interface

(CP interface)

CPX-CP-4-FB CPI maximum

16x 8 bit2)

maximum

16x 8 bit2)


with setting:

CPX-CTEL-4-M12-5POL CTEL

0E/0A byte – –

0E/8A byte – 8x 8bit

0E/16A byte – 16x 8 bit



8E/0A byte 8x 8bit –

16E/0A byte 16x 8 bit –



8E/8A byte 8x 8bit 8x 8bit

16E/16A byte 16x 8 bit 16x 8 bit




2) Maximum assigned address space is dependent on the string allocation

3 Commissioning


Module designation Allocated address spaceModule

identifiers1)

Module typeModule designation

OutputsInputs

Module

identifiers1)

Module type


with setting:

CPX-CTEL-2-M12-5POL-LK CTEL-2-LK

I-port LK

master

8E/8A byte 8x 8bit 8x 8bit




2) Maximum assigned address space is dependent on the string allocation

Tab. 3.7

Details on the technology modules can be found in the corresponding descriptions

(� P.BE-CPX-…).

3 Commissioning


3.4.5 Determination of the address assignment

Tab. 3.8 serves to determine the address assignment and/or the number of assigned

inputs and outputs on the CPX terminals.

Modules (analogue/digital) and diagnostics mode Inputs Outputs

bus node

With status bits + 16 I + _____ I

with I/O diagnostics interface + 16 I/O + _____ I + _____ O

Analogue modules

CPX-2AE-U-I + ___ x 32 I + _____ I

CPX-4AE-I, CPX-4AE-U-I, CPX-4AE-P-…, CPX-4AE-TC + ___ x 64 I + _____ I

CPX-4AE-T + ___ x 32/64 I1) + _____ I

CPX-2AA-U-I + ___ x 32 O + _____ O

VMPA-FB-PS-… (pressure sensors) + ___ x 16 I + _____ I

VPPM-…TA-L-1-F… (Proportional pressure regulators) + __ x 16 I/O + _____ I + _____ O

Technology modules

e.g. CPX-CMAX-C1-1, CPX-2ZE2DA, CPX-CP-4-FB + ___ I/O + _____ I + _____ O

Digital modules

CPX-4DE, CPX-8DE, CPX-8NDE, CPX-8DE-D + ___ x 8 I2) + _____ I

CPX-16DE, CPX-M-16DE-D, CPX-L-16DE-16-KL-3POL + ___ x 16 I + _____ I

CPX-4DA, CPX-8DA, CPX-8DA-H + ___ x 8 O2) + _____ O

CPX-8DE-8DA, CPX-L-8DE-8DA-16-KL-3POL + __ x 8 I/O + _____ I + _____ O

VMPA1-…, VMPA2-… (Pneumatic modules) + ___ x 8 O2) + _____ O

VMPAL-…, VABA-… (pneumatic interfaces)

Number of configured valve solenoid coils (+8 O … 32 O)3) + _____ O

Sum total of the assigned inputs and outputs of your CPX terminal

(maximum 512 I and 512 O): = _____ I = _____ O

1) The number of inputs is dependent on the setting.

2) Digital modules with 4 inputs or outputs (CPX-4DE, CPX-4DA) as well as electric modules and electronic modules VMPA2 always

occupy 8 inputs or 8 outputs.

3) At the factory, 32 O (VABA, VMPAL) are configured.

Tab. 3.8

3 Commissioning


3.5 Addressing

3.5.1 Basic rules for addressing

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

– Counting is byte-wise from left to right, in ascending order without gaps.

Even modules with less than 8 bits occupy 8 bits of address space, but do not use all this space.

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

gnostic interface are deactivated.

Please Note

Address assignment with activated status bits or activated I/O diagnostics interface.

– If the 8 status bits are activated, these occupy the first 16 inputs in the address

range, although only 8 inputs are used.

– If the I/O diagnostics interface is activated, it will occupy the first 16 inputs and

outputs in the address range.

– The inputs and outputs of various different types of module are assigned separately from one an

other, and the sequence depends on the arrangement of modules in the CPX terminal.

– Input data: S-0-1500.SI.9 (Container Input Data)

– Output data: S-0-1500.SI.5 (Container Output Data).

Please Note

In the Remote I/O operating mode, the bus node must be placed as the first module

(slot 0) to the far left of the CPX terminal.

3 Commissioning


3.5.2 Example 1: CPX terminal with electronic modules VMPA1 and VMPA2

The following graphic shows a CPX terminal with electronic modules VMPA1 and VMPA2 and the follow

ing setting:

– status bits and I/O diagnostics interface deactivated.

Module no.: 0

1 2

8DI 4DO

3

1 2 3 4 5 6

4

1 Bus node CPX-FB39

2 End plate VMPAL (pneumatic interface)

3 Electronic module VMPA1 (8DA)

4 Electronic module VMPA2 (4DA)

Fig. 3.2

The following diagram shows an example of the address assignment for the CPX terminal depicted:

No. Module Function group0 CPX-FB39

1 CPX-8DE S-0-1503.1.9

2 CPX-4DA S-0-1502.2.5

3 VMPA-1 (8DA) S-0-1502.3.5

4 VMPA-1 (8DA) S-0-1502.4.5

5 VMPA-2 (4DA) S-0-1502.5.5

6 VMPA-2 (4DA) S-0-1502.6.5

S-0-1500.0.9 (input data 1 byte)S-0-1503.1.9 (module 1) 8 bit

S-0-1500.0.5 (output data 5 byte)S-0-1502.2.5 (module 2) 8 bit1)

S-0-1502.3.5 (module 3) 8 bit

S-0-1502.4.5 (module 4) 8 bit

S-0-1502.5.5 (module 5) 8 bit1)

S-0-1502.6.5 (module 6) 8 bit1)

1) 8 bit assigned, 4 bit used

Fig. 3.3

3 Commissioning


3.5.3 Example 2: CPX terminal with electrical interface (CP interface)

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

– status bits and I/O diagnostics interface deactivated.

1 2 3 4 5 6Module no.: 0

8DI 4DO 8DI 8DO

1

2

3

4

5

6

1 Bus node CPX-FB39

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

electrical interface

3 cylinders

4 CP input module (16DI)

5 Sensor

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

electrical interface

Fig. 3.4


No. Module Function group0 CPX-FB39

1 CPX-8DE S-0-1503.1.9

2 CPX-4DA S-0-1502.2.5

3 CPX-CP-4-FBI1) S-0-1508.3.9

S-0-1508.3.5

4 CPX-8DE-8DA S-0-1503.4.9

S-0-1502.4.5

5 VMPA-1 (8DA) S-0-1502.5.5

6 VMPA-1 (8DA) S-0-1502.6.5

S-0-1500.0.9 (input data 6 byte)S-0-1503.1.9 (module 1) 8 bit

S-0-1508.3.9 (module 3) 4x 8 bit

S-0-1503.4.9 (module 4) 8 bit


S-0-1508.3.5 (module 3) 16x 8 bit

S-0-1502.4.5 (module 4) 8 bit

S-0-1502.5.5 (module 5) 8 bit

S-0-1502.6.5 (module 6) 8 bit

1) Here 4 byte inputs and 16 byte outputs 2) 8 bit assigned, 4 bits used

Fig. 3.5

3 Commissioning


3.5.4 Example 3: CPX terminal with analogue module and pneumatic interface

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

– status bits activated and I/O diagnostic interface deactivated

– pneumatic interface set with DIL switch to 1 ... 8 solenoid 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-FB39 (status bits activated)

2 Pneumatic interface (set with DIL switch to

1 ... 8 solenoid coils)

3 VTSA pneumatics

Fig. 3.6


No. Module Function group0 CPX-FB39 S-0-1503.0.9

1 CPX-8DE S-0-1503.1.9

2 CPX-8DE S-0-1503.2.9

3 CPX-4DA S-0-1502.3.5

4 CPX-8DE-8DA S-0-1503.4.9

S-0-1502.4.5

5 CPX-2AA-U-I S-0-1504.5.5

6 VABA (8DA)3) S-0-1502.6.5

S-0-1500.0.9 (input data 5 byte)S-0-1503.0.9 (module 0) 16 bit1)

S-0-1503.1.9 (module 1) 8 bit

S-0-1503.2.9 (module 2) 8 bit

S-0-1503.4.9 (module 4) 8 bit


S-0-1502.4.5 (module 4) 8 bit

S-0-1504.5.5 (module 5) 2x 16 bit

S-0-1502.6.5 (module 6) 8x 1 bit

1) 16 bit assigned, 8 bit used

2) 8 bit assigned, 4 bits used

3) Set via DIL switches to 1 … 8 valve coils

Fig. 3.7

3 Commissioning


3.5.5 Address assignment after extension/conversion

If the requirements for the machine or system change, the CPX terminal can be adapted as required due

to its modular design.

Caution

If the CPX terminal is extended or converted at a later stage, input/output addresses

may be shifted. This applies in the following cases:

– Additional modules are inserted between existing modules.

– Existing modules are removed or replaced by other modules which have fewer or

more input/output addresses.

– Interlinking blocks or pneumatic connection blocks for monostable valves are re

placed by interlinking blocks/connection blocks for bistable valves or vice versa

(� Pneumatics description).

– Additional interlinking blocks or connection blocks are inserted between existing ones.

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

– The configured addresses of the pneumatic interface are modified.

Please Note

If the configuration of a CPX terminal was changed, new requirements for the CPX ter

minal that may be necessary must be checked and adjusted, if necessary.

Moreover, it should be noted that the needed address space may increase due to modific

ation of the CPX terminal and thus the slave addresses of the following slaves in the net

work must be checked and adjusted if necessary.

3 Commissioning


3.6 Incorporation in the host system

3.6.1 Codesys control software

To incorporate a CPX terminal in a Sercos-III network you can for example use Codesys control software

from 3S (Smart Software Solution) (� www.codesys.com).

The contents of this documentation serve as an example of the use of Codesys software

and relate to version 3.5 SP4 in the Professional presentation format and an English

language setting.

The user interface for this software can be adapted individually and the window arrangement can be

changed. The following illustration shows a possible layout for the user interface.

1

2

3

4

1 Parameter register (“Parameter tab”)

2 Editor window (“Editor window”)

3 Device window (“Device window”)

4 Device tab (“Device tab”)

Fig. 3.8

3.6.2 Installing device description files (SDDML files)

To insert the module extension of your CPX terminal in the control software and to be able to configure

it, the device description files (SDDML files) of all modules used in the CPX terminal need to be installed

once.

The device description files (SDDML files) are available on the Festo support portal on the

Internet (� www.festo.com/sp).

Please Note

Requirements for execution of the subsequent steps:

– Device description files (SDDML files) downloaded from the Festo Support Portal

and unpacked.

3 Commissioning


Approach:

1. Start Codesys software.

2. Menu Tools (“Tools”) > Device Repository… (“Device Repository…”).

The device repository dialog (“Device Repository”) opens up.

Fig. 3.9

3. Press the Install button … (“Install…”).

The “Install Device Description”dialog opens up.

Fig. 3.10

4. Mark the required XML files and press the “Open”button.

The selected device description files (SDDML files) are then installed.

The device description files (SDDML files) are then available in the Codesys control

software.

3 Commissioning


3.6.3 Inserting field bus

Please Note


– Codesys project set up with programmable controller (PLC)

– Device description files (SDDML files) available in Codesys

(� 3.6.2 Installing device description files (SDDML files)).

Procedure

1. Highlight entry of device in device window (“Device window”).

2. Project menu (“Project”) > Add device… (“Add Device…”).

The “Add Device”dialog opens up.

Fig. 3.11

3. Extend the “sercos”entry and highlight the “sercos Master”entry.

4. Press the “Add Device”button.

The “sercos Master”entry appears in the device window (“Device window”).

The Sercos master is now available as field bus in the Codesys project and the bus node

can be added to the device tree (� 3.6.4 Insert bus node).

3 Commissioning


Setting the cycle time

1. Highlight “sercos_Master (sercos Master)”entry in the device window (“Device window”).

2. Project menu (“Project”) > Edit object (“Edit Object”).

The device tab (“Device tab”) “sercos_Master”appears in the Editor window (“Editor window”).

Fig. 3.12

3. In the parameter tab (“Parameter tab”) “sercos Master”, set the Sercos cycle time (“sercos Cycle

time”).

3 Commissioning


3.6.4 Insert bus node

Please Note




(� 3.6.2 Installing device description files (SDDML files))

– Field bus inserted in project (� 3.6.3 Inserting field bus).

Procedure

1. Highlight “sercos_Master (sercos Master)”entry in the device window (“Device window”).



Fig. 3.13

Please Note

Depending on the diagnostics mode, there is a choice of 3 entries:

– CPX-FB39-RIO (without diagnostic mode)

– CPX-FB39-RIO-ST (with status bits)

– CPX-FB39-RIO-STI (with diagnostic interface).

3. Highlight corresponding bus node entry.


3 Commissioning


In the device window (“Device window”), 2 entries appear for the bus node (� Fig. 3.14).

– First entry: Bus node gateway

– Second entry: Bus node module.

1

2

1 Bus node gateway 2 Bus node module

Fig. 3.14

The CPX-FB39 module is now available as a bus node in the Codesys project and other

modules of the CPX terminal can be added to the device tree

(� 3.6.5 Inserting other modules).

3 Commissioning


Setting the Sercos address

1. Highlight bus node gateway entry in the device window (“Device window”).


The corresponding device tab (“Device tab”) appears in the editor window (“Editor window”).

Fig. 3.15

3. Enter the correct Sercos address in the “sercos Slave”parameter tab (“Parameter tab”).

Please Note

The entry for the Sercos address must match the setting of DIL switch 3 on the bus node

(� 2.4.7 Set the Sercos address).

3 Commissioning


3.6.5 Inserting other modules

Please Note




(� 3.6.2 Installing device description files (SDDML files))

– Field bus inserted in project (� 3.6.3 Inserting field bus)

– Bus node inserted in project (� 3.6.4 Insert bus node).

Procedure

1. Highlight bus node gateway entry (upper entry) in the device window (“Device window”).



Fig. 3.16

3. Highlight the module.


5. Insert other modules in accordance with steps 3. and 4.

Expansion of the CPX terminal is now available in the Codesys project and assignment of

the inputs and outputs to variables in the higher-level controller (I/O mapping) is now

possible (� 3.6.6 I/O assignment).

3 Commissioning


3.6.6 I/O assignment

Once all devices on the CPX terminal have been inserted in the Codesys controller software project, the

inputs and outputs on the individual modules can be depicted on a higher-level control unit.

Procedure

1. Click entry of device in the device window (“Device window”) with the right-hand mouse button.

A context menu appears on screen.

2. In the context menu, select “Edit IO mapping”.

The device tab (“Device tab”) “Edit IO mapping”appears in the editor window (“Editor window”).

Fig. 3.17

All inputs and outputs on the individual modules are displayed in the Editor window

(“Editor window”) and can be assigned to the variables in the higher-level controller.

3 Commissioning


3.6.7 Changing parameters in Codesys

With the help of Codesys software, the user-defined parameters (“User Parameters”) of the modules

inserted in a project can be displayed and changed.

Procedure

1. Highlight the entry of a module in the device window (“Device window”).


The corresponding device tab (“Device tab”) appears in the editor window (“Editor window”).

3. Select parameter tab (“Parameter tab”) for user-defined parameters (“User Parameters”).

The parameter appear in the editor window (“Editor window”).

Fig. 3.18

4. Select the parameter settings by double-clicking “Value”in the (“Value”) column and edit the value

using the pulldown menu.

The parameter settings can be displayed as a symbolic value (standard) or as a numerical

value. Refer to the corresponding CPX modules to find the meaning of the applicable

numerical values.

The changeover of display involves setting or not setting the tick on Symbolic Values

(“Symbolic values”).

3 Commissioning


3.7 Parameterisation

3.7.1 Introduction to parameterisation

The CPX terminal is supplied with factory-preset parameters (default parameterisation).

The system characteristics of a CPX terminal and of individual modules and channels can be parameter

ized individually. A distinction is made here between the following parameters:

Parameter Description Examples

System parameters Global system functions for the

complete CPX terminal

– Short-circuit monitoring

– System start

Module parameters Module and channel-specific functions

of the respective module

– Input debounce time

– Signal extension time

Diagnostic memory

parameters

Operating method of the diagnostic

memory

– Remaining entries with Power ON

– Error number filter

Tab. 3.9

A detailed description of the individual parameters as well as basic principles of applica

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

Which parameters stand for the modules used are found in the description for the re

spective module.

Caution

If the Modify-LED (M) lights up permanently, the parameterisation is not stored locally in

the bus node and is not restored automatically by the higher-order system upon re

placement.

� In these cases, check before replacement to see which settings are required and

carry out these settings.

Changes in parameterisation or application-specific parameter settings result in

changes to the module or system behaviour.

� Check especially when replacing CPX terminals to see which settings are necessary

and make sure that these are restored, if necessary (e.g. by appropriate system-

start parameterisation).

Warning

The connected actuators can move unexpectedly!

Modification of the signal statuses and parameters can trigger dangerous movements of

the connected actuator technology.

� Make sure that nobody is in the positioning range of connected actuators, and be

very careful with the parameterisation or manipulation of signal statuses.

� Always note the instructions relating to “Force”, “Idle Mode”and “Fail Safe”in the

CPX system description (� P.BE-CPX-SYS-…), in the description for the CPX-MMI

(� P.BE-CPX-MMI-1-…) and in the online help for the CPX-FMT.

3 Commissioning


3.7.2 Prerequisite for parameterization

Please Note

A CPX terminal can be parameterised only if the function “System start with default

parameterisation and current CPX expansion” is activated.

� Set the system parameter “System start”accordingly.

With the system parameter “System start”, you can define the starting characteristics of the CPX ter

minal.

Factory settings are used unless parameterization is altered.

� Select the setting “System start with default parameterization and current CPX expansion”to permit

the required parameterization.

� To conduct the parameterization, use the Festo Maintenance Tool (CPX-FMT) software or the control

device (CPX-MMI).

� After parameterization, change the setting of the system parameter “System start”to “System start

with stored parameterization and stored CPX expansion”to define the settings and to save them in

the module.

After a reboot of the CPX terminal, the Modify-LED (M) lights up continuously on the bus node. The

terminal uses the saved parameter settings.

Caution

If the Modify-LED (M) is lit continuously, the parameterization during replacement is not

set up automatically by the higher-level controller.

� In such cases, examine before replacement which settings are required and imple

ment them.

3.7.3 Methods of parameterisation

A CPX terminal with the bus node CPX-FB39 can be parameterised with various methods.

Method Benefits Disadvantages

Festo Maintenance Tool

(CPX-FMT)

Menu-guided parameter

entries via PC software

Easy parameter entry guided by

menu in plain text.

Parameterisation is saved locally

in the CPX terminal and is lost if

the CPX terminal or bus node is

replaced.

Operator unit (CPX-MMI)

Menu-guided parameter

entry

Easy parameter entry guided by

menu in plain text.

Parameterisation is saved locally

in the CPX terminal and is lost if

the CPX terminal or bus node is

replaced.

Sercos III Parameterisation can be carried

out via the control system.

The controller must support the

configuration via SDDML files.

Tab. 3.10

3 Commissioning


3.7.4 Parameterisation via the Festo Maintenance Tool (CPX-FMT) software

With the Festo Maintenance Tool (CPX-FMT) software, a CPX terminal can be parameterized via a USB or

Ethernet connection.

Please Note

To run the software on the bus node via a USB connection, you need a USB connector

cable and the USB adapter NEFC-M12G5-0.3-U1G5.

The current version of the Festo Maintenance Tool (CPX-FMT) software is available for

download in the Festo Support Portal (� www.festo.com/sp).

3.7.5 Parameterization with the control device (CPX-MMI)

With the operator unit (CPX-MMI), a CPX terminal can be parameterised through a menu even without

controller software.

Information on general operation of the operator unit can be found in the corresponding

description (� P.BE-CPX-MMI-1-…).

Please Note

The last parameterisation set or received in the CPX terminal is always valid.

3.7.6 Parameterization via Sercos III

The bus node can be parameterized directly by the controller via Sercos III.

This has the advantage that all parameters are saved in the controller software and auto

matically transferred to the bus node at run-up of the controller.

As a result, parameterisation remains intact if the bus node is replaced.

4 Diagnostics and error handling



4.1 Summary of diagnostics options

The CPX terminal provides comprehensive and user-friendly options for diagnostics and error handling.

The following options are available, depending on the configuration:

Diagnostic

possibility

Brief description Benefits Detailed

Description

LED display The LEDs show directly

configuration errors, hardware

errors, bus errors, etc.

Fast “on-the-spot” error

detection

Section 4.2

Status bits Internal inputs that supply

coded common diagnostic

messages.

Fast access to error

messages, irrespective of

the module and master.

Section 4.3 and CPX

system description

(� P.BE-CPX-SYS-…)

I/O

diagnostics

interface

Bus-independent diagnostic

interface at I/O level, which

enables access to the internal

data of the CPX terminal

(16 inputs and 16 outputs).

Detailed error recognition:

the diagnostic data can be

processed further, e.g.

with a PLC user program.

Section 4.4 and CPX

system description


Diagnostics via

the operator

unit (CPX-MMI)

Diagnostic information can be

displayed on the operator unit

in a convenient and

menu-driven manner.

Fast “on-the-spot”

recognition of errors

Operator unit

description

(� P.BE-CPX-MMI-1-…)

Diagnostics

via Sercos III

Access to all system data of

the CPX terminal over the

network.

Detailed error detection Section 4.5

Tab. 4.1

Please Note

Note that the available diagnostic information is dependent on the DIL switch settings

on the bus node, (� 2.4.5 Setting of the diagnostic mode (remote I/O)) as well as on

the parameterisation of the CPX terminal.

You can find additional information on general diagnostics of the CPX terminal in the CPX

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

Information on diagnostics of the pneumatics, of the pneumatic interface and of the I/O

module are found in the corresponding descriptions.



4.2 Diagnostics via LED displays

LED displays for the diagnostics of the CPX terminal are available on the bus node as well as on the

individual modules.

The significance of the LED displays on the electric modules can be found in the descrip

tion for the relevant module.

LED displays on the bus node CPX-FB39

PS

PL

S

TP1

TP2 M

PS

PL

S

TP1

TP2 M

SD

SD 1

2SF

SF

1 Network-specific LEDs:

– S (green, orange, red)1)

– SD (green, orange, red)1)

– TP1 (green)

– TP2 (green)

2 CPX-specific LEDs:

– PS (green)

– PL (green)

– SF (red)

– M (yellow)

1) This figure depicts a green LED as an example.

Fig. 4.1

In the following sections, the different statuses of the LED displays are represented as follows:

LED lights up; LED flashes; LED is out



4.2.1 Standard operating status

LED display operating status

PS

PL

S

TP1

TP2 M

SD

SF

These LEDs light up green:

– S

– SD

– PS

– PL

These LEDs flash green:

– TP1 and TP2

The yellow LED (M) lights up, flashes or is dark.1)

The red LED (SF) is dark.

Standard

1) Depending on the data communication or configuration.

4.2.2 CPX-specific LEDs

PS (power system) – power sensor/logic supply

LED (green) Process Status Significance / error handling

LED

illuminated

ON

OFF

No error. Operating voltage/

sensor supply applied.

–

LED flashes

ON

OFF

Operating voltage/sensor

supply outside the toler

ance range.

� Eliminate undervoltage.

ON

OFF

Internal fuse for the operat

ing voltage/sensor supply

has responded.

1. Eliminate short circuit/overload.

2. Depending on the parameterisation:

� Sensor power supply is

switched back on automatically

after remedying the short

circuit (factory setting).

� Power OFF/ON necessary.

LED

not illuminated

ON

OFF

Operating voltage/sensor

supply is not applied.

� Check the operating voltage

connection of the electronics.

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

LED (green) Process Status Significance / error handling

LED

illuminated

ON

OFF

No error.

Load voltage applied.

–

LED flashes

ON

OFF

Load voltage at the system

supply or additional supply

outside the tolerance range.

� Eliminate undervoltage.



SF (system failure) – system fault

LED (red) Sequence1) Status Significance/error handling

LED flashes

ON

OFF

Simple error/information

(error class 1)

Description of error numbers in the

CPX system description

(� P.BE-CPX-SYS-…).ON

OFF

Error

(error class 2)

ON

OFFSerious error

(error class 3)

LED

not illuminated

ON

OFFNo error –

1) The system fault LED flashes depending on the class of fault which has occurred.

Error class 1 (slight error): 1× flash, pause time

Error class 2 (error): 2× flashes, pause time

Error class 3 (severe error): 3× flashes, pause time

M (modify) – parameterisation modified or Force active

LED (yellow) Process Status Significance / error handling

LED

illuminated

ON

OFF

Setting: System start with

saved parametrisation and

saved CPX expansion;

Parameters and CPX

expansion are stored

permanently.

For replacement of the bus node or

CPX terminal in case of service,

parameterisation is not created

automatically by the higher-order

system (PLC/IPC).

� Save and apply the parameterisa

tion when the bus node is re

placed.

LED flashes

ON

OFF

Force is active1) The Force function is enabled.

Further information can be found in

the CPX system description

(� P.BE-CPX-SYS-…).

LED

not illuminated

ON

OFF

Setting: System start with

default parameterisation

(factory setting) and cur

rent CPX expansion;

external parameterisation

is possible (presetting).

–

1) The display of the Force function (LED flashing) has priority over the display of the setting for the system start (LED illuminated).



4.2.3 Network-specific LEDs

S – Sercos III

LED status Process State Priority Significance / error handling

DarkON

OFF

UCC mode 0 No Sercos communication

lights up

Orange

ON

OFF

CP0 0 Communication phase 0 is active.

Alternates

Orange/

Green

OFF

ON

ON

OFF


The green LED flashes every

3 seconds once.

Alternates

Orange/

Green

OFF

ON

ON

OFF


The green LED flashes twice every

3 seconds.

Alternates

Orange/

Green

ON

OFF

ON

OFF


The green LED flashes 3 times

every 3 seconds.

lights up

Green

ON

OFF


Alternates

Green/

Orange

ON

OFF

ON

OFF

HP0 1 Device is in hot-plug phase 0.

Alternates

Green/

Orange

OFF

ON

ON

OFF


The orange LED flashes once

every 3 seconds.

Alternates

Green/

Orange

OFF

ON

ON

OFF


The orange LED flashes twice

every 3 seconds.

FLASHES

Green

ON

OFF

Fast Forward

� Loopback

2 RT status has changed from

Fast-Forward to Loopback.

Alternates

Red/

Orange

ON

OFF

ON

OFF

Application Error 3 Application Error

� GDP and FSP status codes

Alternates

green/red

ON

OFF

ON

OFF

MST Losses

(IDN S-0-1003)/2

4 MST failures� (IDN S-0-1003)/2

(� B.1.5)

lights up

red,

ON

OFF

Communication

error

5 Communication error

� SCP status codes



S – Sercos III

LED status Significance / error handlingPriorityStateProcess

FLASHES

Orange

ON

OFF

Identification 6 Identification (address assignment

or configuration fault) (C-DEV.Bit15)

FLASHES

red,

ON

OFF

Watchdog Error 7 Watchdog Error

SD – Sub Device

LED status Process State Priority Significance / error handling

lights up

red,

ON

OFF

Application Error

(C1D)

1 Application Error

� GDP and FSP status codes

lights up

Orange

ON

OFF

Parameterization

Level (PL)

0 Sub Device in Parameterization

Level

lights up

Green

ON

OFF

Operating Level

(OL)

0 Sub Device in Operating Level

DarkON

OFF

Sub Device not

active

0 –

TP1 – Traffic Port 1 (connection port 1 active)

LED status Process Status Significance / error handling

lights up

Green

ON

OFF

Network connection OK –

FLASHES

Green

ON

OFF

Data traffic –

DarkON

OFF

No network connection or

Ethernet cable not connected.

� Check Ethernet connection.

TP2 – Traffic Port 2 (connection port 2 active)

LED status Process Status Significance / error handling

lights up

Green

ON

OFF

Network connection OK –

FLASHES

Green

ON

OFFOFFOFF

Data traffic –

DarkON

OFF

No network connection or

Ethernet cable not connected.

� Check Ethernet connection.



4.3 Diagnostics via status bits

Status bits are internal inputs that serve to display common diagnostic messages (global error mes

sages).

Please Note

The diagnostic mode “Status bits” must be activated via DIL switch 2.2 on the bus node

(� 2.4.5 Setting of the diagnostic mode (remote I/O)).

Status bits are treated as inputs and there can be queried, linked and processed as “standard” inputs.

In the case of activated “Status bits” diagnostics mode, the first 16 inputs are assigned

although only 8 inputs are used (� 3.5.1 Basic rules for addressing).

Status bits are treated as “normal” inputs.

– If all status bits supply a 0-signal, no error is reported.

– If at least one status bit delivers a 1-signal, there is a fault. The diagnostic information when there is

a 1-signal is shown in the following table.

Bit Diagnostic information with a 1-signal Description

0 Fault at valve or pneumatic module Module type in which an error has occurred

1 Error on output module

2 Error on input module

3 Error on analogue module or technology module

4 Undervoltage Error type

5 Short circuit/overload

6 Wire break

7 Other error

Tab. 4.2

Please Note

If various errors occur simultaneously on different types of modules, these errors can

not be assigned via the status bits.

Errors can be uniquely defined via the I/O diagnostics interface, if needed.

Further notes on the function and content of the status bits are found in the CPX system

description (� P.BE-CPX-SYS-…).



4.4 Diagnostics via the I/O diagnostics interface

Detailed diagnostic information on the CPX terminal can be accessed via the “I/O diagnostics interface”

diagnostics mode. You can ascertain this exactly, e.g. by noting on which module and channel an error

has occurred. To call up this information, 16 input bits and 16 output bits enable all diagnostic informa

tion to be read out.

Please Note

To use the “I/O diagnostic interface” diagnostics mode, it must be activated via DIL

switch 2 on the bus node (� 2.4.5 Setting of the diagnostic mode (remote I/O)).

If the “I/O diagnostic interface” is activated, it will occupy the first 16 inputs and outputs

in the address range (� 3.5.1 Basic rules for addressing).

The following table provides an overview of the available diagnostic information.

Diagnostic information Description

Global diagnostic data – General overview of errors

Diagnostic data module – Detailed diagnostics per module

Diagnostic data status – Number of entries in the diagnostic memory

– Operating mode

Diagnostic memory data – Long-term memory

– Detailed diagnostics and relative time stamp per fault event

Tab. 4.3

Further notes on the function and content of the I/O diagnostics interface can be found in




4.5 Diagnostics via Sercos III

Various diagnostic options are available for diagnostics via Sercos III and these can be selected by their

corresponding IDNs.

– Basic diagnostic functions (� 4.5.1 Basic diagnostic functions)

– Diagnostic basic functions with I/O-specific extensions (� 4.5.2 I/O diagnostics)

– Diagnostics acc. to the CPX standard of Festo

(� 4.5.3 I/O diagnostics with Festo-specific extensions).

4.5.1 Basic diagnostic functions

The basic diagnostic functions are supported by every Sercos device. This involves predefined status

codes being transmitted via S-0-0390. Error messages can be acknowledged by S-0-0099.

To interrogate the characteristics and chronological sequence of diagnostic messages, a

trace function is available via S-0-1303.

IDNs for the basic diagnostic function (function group diagnostics)

IDN Designation Explanation

S-0-0099 Reset Class 1 Diagnostic Acknowledge diagnostic event

S-0-0390 Diagnostic Number Current diagnostic event as a status code

S-0-1303 Diagnostic trace Diagnostic record

S-0-1303.0.03 Diagnosis Trace State Status of diagnostic record

S-0-1303.0.10 Diagnosis Trace Buffer 1 Diagnostic memory 1

S-0-1303.0.11 Diagnosis Trace Buffer 2 Diagnostic memory 2

Tab. 4.4

4.5.2 I/O diagnostics

I/O diagnostics involve Sercos standard diagnostics with I/O-specific extensions (e.g. channel-precise

localization).

Only the highest priority (S-0-1500.0.32) and the current (S-0-1500.0.33) diagnostic

message are displayed. If several faults occur simultaneously, a few messages are not

visible.

IDNs for I/O diagnostics (Bus Coupler function group)


S-0-1500.0.02 IO Status Current status of inputs and outputs

S-0-1500.0.32 IO Diagnosis Message I/O diagnostic message with the highest

priority

S-0-1500.0.33 Current I/O Diagnosis Message Current I/O diagnostic message

Tab. 4.5



4.5.3 I/O diagnostics with Festo-specific extensions

The Festo-specific extensions for I/O diagnostics provide access to all available diagnostic functions in

accordance with the CPX standard.

The division into system, module and channel diagnostics provides access at any time to all diagnostic

messages (� Tab. 4.6). That means that no diagnostic messages remain undetected, even in the pres

ence of simultaneously occurring faults.

IDNs for Festo-specific extensions


S-0-1500.SI.150 CPX System Diagnostics CPX system diagnostics

S-0-1500.0.151

IO_FG.SI.151

Module Diagnostics Module diagnosis

S-0-1500.0.152

IO_FG.SI.152

Channel Diagnostics Channel diagnostics

Tab. 4.6



4.6 Error handling

With the following malfunctions, the behaviour of the CPX terminal depends on the configured beha

viour of the master module and the parameterised fail-safe setting:

– Telegram failure

– stop of the master

– interruption in the bus cable.

Depending upon the configuration, the outputs (valves and electrical outputs) are

switched off (factory setting), switched on or they retain their existing status.

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

These characteristics can be altered using the Festo Maintenance Tool (CPX-FMT) software, the control

device (CPX-MMI) or Sercos mechanisms.

Change via Sercos

� Change configuration of fallback values (� Tab. B.12 (IO_FG.SI.22 - Fallback Value Output)).

� Change configuration of fallback values (� Tab. B.12 (IO_FG.SI.02 - Configuration Of IO_FG).

Change via CPX-FMT/CPX-MMI

� Change configuration of failsafe values (� CPX system description P.BE-CPX-SYS-…, online help

with CPX-FMT software or description of control device P.BE-CPX-MMI-1-…).

Please Note

A change in the fallback and backup values via Sercos also has a corresponding impact

on the failsafe entries in the CPX system table (� Tab. B.14).

In the event of any retrospective adjustment of fallback values via CPX-FMT or CPX-MMI,

the backup value characteristics provided for in the Sercos standard no longer apply.

Warning

Accidental activation of actuators!

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

� Ensure that valves and outputs relating to the aforementioned problems are placed

in a safe condition.

Please Note

If the outputs are reset in conjunction with PLC-Stop, field bus interruption or a fault,

pay attention to the following:

– monostable valves move to the initial position.

– Double solenoid valves remain in the current position.

– Mid-position valves go into mid-position (pressurized, exhausted or closed, depend

ing on valve type).

A Technical appendix



A.1 Technical data

General information

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

Degree of protection in accordance with

IEC 60529, completely mounted, plug connector

in accordance with accessories plugged in or

equipped with cover cap

IP65/IP67

Protection against electric shock

(Protection against direct and indirect contact in

accordance with IEC 60204-1)

through the use of PELV circuits

(Protected Extra Low Voltage)

Module code (CPX-specific)

Remote I/O

Remote controller

224 (sub-module code 3)

171 (sub-module code 3)

Module identifier (in operator unit CPX-MMI)

Remote I/O

Remote controller

FB39-RIO

FB39-RC

Power supply

Operating voltage/load voltage � CPX system description (P.BE-CPX-SYS-…)

Intrinsic current consumption at 24 V

from operating voltage supply for

electronics/sensors (UEL/SEN)

typ. 100 mA (internal electronics)

Galvanic isolation

between bus interface and CPX periphery (power

supplies)

Yes

Mains buffering time at least 25 ms

Network-specific characteristics

Network protocol Sercos III

Specification Standards/norms with reference to Sercos III:

– IEEE 802.3

– IP-based protocols (UDP, TCP, ICMP, …)

Transmission rate 100 Mbit/s full duplex

Input/output size 64 byte/64 byte (operating-mode-independent)

Crossover detection Auto-MDI/MDI-X



A.2 List of abbreviations

The following product-specific terms and abbreviations are used in this manual:

Term/abbreviation Meaning

Address space The sum of available addresses, independent of the assignment.

AI Analogue input (input channel, 16 bits)

AO Analogue output (output channel, 16 bits)

AT Acknowledge telegram

Bus node Create the connection to certain networks and fieldbuses, conduct

control signals to the connected modules and monitor their functioning

capability.

C-CON Connection Control

C-DEV Device Control

CEC Control block CPX-CEC for configuration, commissioning and

programming of various components and equipment from Festo.

CFG Configuration

CP Communication Phase

CPX modules Collective term for the various modules which can be integrated into a

CPX terminal.

CPX system description


Description that gives an overview of structure, components, function,

installation and commissioning as well as basic information on

parameterisation of CPX terminals (� www.festo.com).

CPX terminal Modular electrical terminal

Diag Diagnostics

Diagnostic data Detailed diagnostics information

DIL switches Miniature switch that consists of several switching elements, with

which, for example, basic settings can be made; DIL = dual in-line

FEC Control block, e.g. CPX-FEC, usable as:

– fieldbus slave (remote I/O operating mode)

– system controller (PLC, remote controller operating mode)

– stand-alone system controller (PLC, stand-alone operating mode)

FG Function Group

FSP Function Specific Profile

GDP Generic Device Profile

I Digital input

IDN Identification Number

IO Input/output

I/O diagnostics interface The I/O diagnostics interface is a bus-independent diagnostics interface

at I/O level, permitting access to internal data of the CPX terminal.

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

outputs (CPX input modules and CPX output modules)

MDT Master Data Telegram

1) The designation NRT channel is no longer used on Sercos units and has been replaced by the designation UCC.



Term/abbreviation Meaning

MTU Maximum Transfer Unit

NRT channel1) Non Real Time � UCC

O Digital output

Parameter With the aid of parameterisation, the characteristics of the CPX terminal

or the characteristics of the individual modules and I/O channels can be

adapted to each particular application. Parameters can be read and

modified.

PDIN Process Data Input

PDOUT Process Data Output

PLC/IPC Programmable logic controller/industrial PC

Pneumatics interface The pneumatics interface is the interface between the modular

electrical peripherals and the pneumatics.

SCP Sercos Communication Profile

S-DEV Device Status

Status bits Internal inputs that supply coded common diagnostic messages.

SVC Service Channel

SYNC Synchronization

UCC Universal Communication Channel

Var Variables

1) The designation NRT channel is no longer used on Sercos units and has been replaced by the designation UCC.

Tab. A.1

B Identification Numbers (IDNs)



To provide a better overview, the IDNs at Sercos are sorted into function groups and classes.

Sorting into function groups depicts the view of the specification. Here, the IDNs are sorted by func

tionality. Sorting in classes depicts the view of the application. For this, the IDNs are assembled in

groups that are needed for defined applications.

B.1 Sercos Communication Profile (SCP)

B.1.1 Function Group - SCP Identification

IDN Designation Class Explanation

S-0-1000 SCP Type & Version SCP_VarCFG SCP type and SCP version

Tab. B.1

B.1.2 Function Group - Timing


S-0-1002 Communication Cycle Time

(tScyc)

SCP_VarCFG Cycle time (0.5 … 65 ms)

Tab. B.2

B.1.3 Function Group - Telegram Setup


S-0-1009 Device Control (C-Dev) Offset

In MDT

SCP_VarCFG –

S-0-1010 Lengths Of MDTs SCP_VarCFG Lengths of Master Data

Telegrams MDT

S-0-1011 Device Status (S-Dev) Offset

In AT

SCP_VarCFG –

S-0-1012 Lengths Of ATs SCP_VarCFG Lengths of Acknowledge

Telegrams AT

S-0-1013 SVC Offset In MDT SCP_VarCFG –

S-0-1014 SVC Offset In AT SCP_VarCFG –

Tab. B.3



B.1.4 Function Group - Control

IDN Name Class Explanation

S-0-0021 IDN List Of Invalid Operation

Data For CP2

SCP_VarCFG –

S-0-0022 IDN List Of Invalid Operation

Data For CP3

SCP_VarCFG –

S-0-0127 CP3 Transition Check SCP_VarCFG Procedure Command to

check all parameters needed

for CP3

S-0-0128 CP4 Transition Check SCP_VarCFG Procedure Command to

check all parameters needed

for CP4

Tab. B.4

B.1.5 Function Group - Bus Diagnosis


S-0-0014 Interface Status SCP_VarCFG –

S-0-1003 Allowed MST Losses In

CP3/CP4

SCP_VarCFG –

S-0-1026 Version Of Communication

Hardware

SCP_VarCFG SERCON100S Version:

V04 R11

S-0-1028 Error Counter MST-P&S SCP_Sync_0x02 –

S-0-1035 Error Counter Port 1 & Port 2 SCP_VarCFG –

S-0-1040 Sercos Address SCP_VarCFG Sercos Address of CPX-FB39

Factory setting: 254 (0xFE)

S-0-1044 Device Control (C-DEV) SCP_Diag –

S-0-1045 Device Status (S-DEV) SCP_Diag –

S-0-1046 List Of Sercos Addresses In

Device

SCP_VarCFG Value of parameter S-0-1040

Tab. B.5



B.1.6 Function Group - Connection


S-0-0187 IDN List Of Configurable Data

As Producer

SCP_VarCFG Contains the following IDNs:

S-0-1500.0.2 (� B.3.2)

S-0-1500.0.9 (� B.3.2)

S-0-1500.0.150 (� B.3.3)

S-0-1500.0.151 (� B.3.3)

IO_FG.SI.9 (� B.3.1)

IO_FG.SI.151 (� B.3.3)

S-0-0188 IDN List Of Configurable Data

As Consumer

SCP_VarCFG Contains the following IDNs:

S-0-1500.0.1 (� B.3.2)

S-0-1500.0.5 (� B.3.2)

IO_FG.SI.5 (� B.3.1)

S-0-1050.SI.1 Connection Setup SCP_VarCFG

SCP_Sync

– 1)

S-0-1050.SI.2 Connection Number SCP_VarCFG –

S-0-1050.SI.3 Telegram Assignment SCP_VarCFG –

S-0-1050.SI.4 Maximum Length Of

Connection

SCP_VarCFG Total length of the IDNs

stored in S-0-0187 and

S-0-0188 less the length of

S-0-1500.0.5 + S-0-1500.0.9

S-0-1050.SI.5 Current Length Of Connection SCP_VarCFG –

S-0-1044.SI.6 Configuration List SCP_VarCFG –

S-0-1050.SI.8 Connection Control (C-CON) SCP_Diag –

S-0-1050.SI.9 Connection State SCP_VarCFG_0x02 –

S-0-1050.SI.10 Producer Cycle Time SCP_Sync –

S-0-1050.SI.11 Allowed Data Losses SCP_Sync –

S-0-1050.SI.12 Error Counter Data Losses SCP_Sync –

S-0-1051 Image Of Connection Setups SCP_VarCFG –

1) Also on SCP_Sync the local bus of the CPX terminal is not synchronized to the superimposed Sercos bus cycle.

Tab. B.6

B.1.7 Function Group - NRT


S-0-1017 NRT Transmission Time SCP_VarCFG –

Tab. B.7



B.2 Generic Device Profile (GDP)

B.2.1 Function Group - Diagnosis


S-0-0095 Diagnostic Message unclassified Diagnostic event

(Sercos-specific) of IDN

S-0-0390 in clear text

S-0-0099 Reset Class 1 Diagnostic GDP_Basic –

S-0-0390 Diagnostic Number GDP_Basic Current diagnostic event with

highest priority in the CPX

system as a status code.

S-0-1303.0.01 Diagnosis Trace Configuration GDP_DiagTAdv Contains IDN S-0-1500.SI.33

(� Tab. B.13)

S-0-1303.0.02 Diagnosis Trace Control GDP_DiagT –

S-0-1303.0.03 Diagnosis Trace State GDP_DiagT –

S-0-1303.0.10 Diagnosis Trace Buffer 1 GDP_DiagT Maximal 100 entries

S-0-1303.0.11 Diagnosis Trace Buffer 2 GDP_DiagT Maximal 100 entries

S-0-1303.0.12 Diagnosis Trace Buffer 3 GDP_DiagTAdv Maximal 100 entries

Tab. B.8

B.2.2 Function Group - Administration


S-0-0017 IDN List Of All Operation Data GDP_Basic –

S-0-0025 IDN List Of All Procedure

Commands

unclassified –

Tab. B.9



B.2.3 Function Group - Identification


S-0-1300.SI.1 Component Name GDP_Id English module designation

(long) in UTF8 format

S-0-1300.SI.2 Vendor name GDP_Id Manufacturer name Festo SE & Co. KG

S-0-1300.SI.3 Vendor code GDP_Basic Manufacturer code 0xFE

S-0-1300.SI.4 Device name GDP_Id English module designation

(short) in UTF8 format

S-0-1300.SI.5 Vendor Device ID GDP_Basic Manufacturer device number

(unique ID for each type of

CPX module)

S-0-1300.SI.6 Connected To Sub Device unclassified On all CPX modules 0

S-0-1300.SI.7 Function Revision GDP_Rev –

S-0-1300.0.8 Hardware Revision GDP_Rev –

S-0-1300.0.9 Software revision GDP_Rev –

S-0-1300.0.10 Firmware Loader Revision GDP_Rev –

S-0-1300.SI.11 Order Number GDP_Id Part number for the

electronics assembly

S-0-1300.SI.12 Serial number GDP_Id –

S-0-1301 List Of GDP Classes & Version GDP_Basic 0x00010001

S-0-1302.SI.01 FSP Type & Version GDP_Basic –

S-0-1302.SI.02 Function Groups GDP_Basic IO Function Groups

S-0-1302.SI.03 Application Type GDP_Id –

Tab. B.10

B.2.4 Function Group - Time


S-0-1305.0.1 Sercos Current Time GDP_DiagT –

S-0-1305.0.2 Sercos Current Fine Time –

S-0-1305.0.3 Sercos Current Coarse Time –

Tab. B.11



B.3 Function Specific Profile IO (FSP IO)

B.3.1 Function Group - Generic I/O

IDN Name Explanation

IO_FG.SI.1 Name Of IO_FG Name of function group

S-0-1500.SI.0

S-0-1502.SI.0

S-0-1503.SI.0

S-0-1504.SI.0

S-0-1505.SI.0

S-0-1506.SI.0

S-0-1507.SI.0

S-0-1508.SI.0

S-0-1509.SI.0

Bus Coupler

Digital output

Digital input

Analog Output

Analogue input

counter

Complex Protocol

Sub Bus Master

Sub Bus Slave

IO_FG.SI.2 Configuration Of IO_FG –

IO_FG.SI.3 Channel Quantity PDOUT Number of output channels

IO_FG.SI.4 Channel Width PDOUT Width of output channels [Bit]

IO_FG.SI.5 PDOUT Output data of the CPX module

IO_FG.SI.7 Channel Quantity PDIN Number of input channels

IO_FG.SI.8 Channel Width PDIN Width of input channels [Bit]

IO_FG.SI.9 PDIN Input data for the CPX module

IO_FG.SI.19 Parameter Channel Receive –

IO_FG.SI.20 Parameter Channel Transmit –

IO_FG.SI.22 Fallback Value Output –

Tab. B.12

B.3.2 Function Group - Bus Coupler

IDN Name Explanation

S-0-1500.SI.1 IO Control Behaviour of inputs and outputs

S-0-1500.SI.2 IO Status Status display of inputs and outputs

S-0-1500.SI.3 List Of Module Type Code Display of module type code for all modules

S-0-1500.SI.5 Container OutputData Container output data1)

S-0-1500.SI.9 Container InputData Container input data1)

S-0-1500.SI.19 Parameter Channel Receive Module-specific parameters of the bus node2)

S-0-1500.SI.20 Parameter Channel Transmit Puffer for the module-specific parameters1) 3)

S-0-1500.SI.23 Local Bus Cycle Time Cycle time of the local bus

S-0-1500.SI.32 IO Diagnostic Message Diagnostic message with the highest priority

S-0-1500.SI.33 Current IO Diagnostic Message Current diagnostic message

1) This IDN is implemented as a byte list with variable length.

2) This IDN only permits read access and is implemented as a byte list with variable length.

3) This does not involve the current value for the module-specific parameters from the CPX system table. The current parameter

values can be interrogated via S-0-1500.SI.19.

Tab. B.13



B.3.3 Manufacturer-specific extensions to the Function Specific Profile IO (FSP IO)


S-0-1500.SI.150 CPX System Diagnostics CPX System Diagnostics1)

This IDN is implemented as an 8-byte value.

Byte 0: Status bits (error type and source of error)

Byte 1: Module number and diagnostic status

Byte 2: Error number

S-0-1500.SI.151

IO_FG.SI.151

Module Diagnostics Diagnostic data of the CPX module to which the

IO function group is assigned.1) 2)

Byte 0: Number of the first defective channel

Byte 1: Module error number

Byte 2: Info 2 (reserved)

Byte 3: Info 3 (reserved)

S-0-1500.SI.152

IO_FG.SI.152

Channel Diagnostics Diagnostic data of all channels of the CPX module

to which the IO function group is assigned.1) 3)

The content of the IDN is the fault number of the

corresponding channel.

S-0-1500.SI.200 CPX system parameters Global system parameters of the CPX system

This IDN is implemented as a byte list with a

length of 8.4)

1) This IDN only permits read access.

2) All sessions of this IDN are implemented as a 4-byte value. One session corresponds to one CPX module.

3) All sessions of this IDN are implemented as a 1-byte list. The length of the list is computed from the total of I channels and O

channels for the corresponding IO function group.

4) Due to the fact that the behaviour of the outputs in the event of a fault with Sercos is specified by parameters IO_FG.SI.02 and

IO_FG.SI.22, the system parameter “Behaviour in response to a Fail State” is factory set to “Fault Mode”.

By setting this parameter to 00 (All Outputs Reset) or 01 (Hold Last State), the specific substitute value characteristics of Sercos

are disabled. The system parameter “Behaviour in an Idle Mode fail state” is not used.

Tab. B.14



B.4 Overview of the supported classes

B.4.1 Supported classes of the Sercos Communication Profile (SCP)

Class Description

SCP_VarCFG This class is needed to initialize the cyclical exchange of data between

master and slave.

A slave that implements the class SCP_VarCFG provides the following functions:

– Accesses via the service channel are completely supported

– Cyclical transmission of “Device Control” and “Device Status”

– The slave defines which data can be transmitted cyclically and how

many connections are possible. The slave provides the master with

these data to enable the master to initialize all connections correctly.

SCP_WDCon A slave that implements the class SCP_WDCon provides a watchdog

function that enables connections to be monitored and, in the event of

connection terminations, to initiate corresponding fault responses.

SCP_Diag A slave that implements class SCP_Diag provides information that helps to

run bus diagnostics.

SCP_NRTPC A slave that implements class SCP_NRTPC enables the UCC (Universal

Communication Channel) to be used for the transmission of

non-Sercos-Ethernet telegrams.

SCP_Cyc A slave that implements the class SCP_Cyc provides all of the functions

needed to transmit and to receive cyclical data (produce and consume).

Tab. B.15

B.4.2 Supported classes of the Generic Device Profile (GDP)

Class Description

GDP_Basic Contains all the essential IDNs needed for a Sercos device.

GDP_DiagT Basic function of the Sercos Diagnostic Trace.

GDP_DiagTAdv Extended functions of the Sercos Diagnostic Trace.

GDP_Id Contains IDNs with information for the identification of a device or module.

GDP_Rev Contains IDNs with information for overhauling (hardware and firmware) of

the bus node.

Tab. B.16

C Diagnostic messages



C.1 Depiction of CPX diagnostic classes on Sercos diagnostic classes

CPX diagnostic class Sercos diagnostic class

Fault class 1: Information or minor fault Operational State

Fault class 2: Standard/extended diagnostics Warning (C2D)

Fault class 3: System fault, general Error (C1D)

Tab. C.1

C.2 Depiction of CPX diagnostic messages on Sercos status codes

CPX fault numbers that are not assigned to a Sercos status code in the following table are

reported as manufacturer-specific status codes.

CPX-

Error

number

Description Serco-

status

code

Description

0 No Error 0x0000 No Error

1 General Diagnosis 0x1000 General Error

2 Short Circuit 0x2130 Short Circuit

3 Wire Fracture/Idling Current I/O 0x2360 Wire Break

4 Short Circuit In Actuator Supply 0x3420 Actuator Supply

5 Undervoltage In Power Supply 0x3400 Supply Voltage

9 Lower Limit Exceeded 0x8920 Measured Value Underrange

10 Upper Limit Exceeded 0x8910 Measured Value Overrange

11 Short Circuit Valve 0x2340 Short Circuit

12 Pilot Valve Function Warning – –

13 Wire Fracture (Open Load) 0x2360 Wire Break

14 Condition Counter Exceeded 0x8B00 Preventive Maintenance Required

(Condition Monitoring)

15 Module/Channel Failure 0xB010 Device Errors

16 Module Code Incorrect 0xB002 Incorrect Local Bus Slave Present

17 I/O Length Incorrect 0xB030 Local Bus Configuration Error

18 Address Range Exceeded 0xB030 Local Bus Configuration Error

19 Life Cycle Exceeded – –

20 Fault In Parameterizing Signal Range 0x6320 Parameter Error

21 Fault In Parameterizing Data Format 0x6320 Parameter Error

22 Fault In Parameterizing Linear Scaling 0x6320 Parameter Error



CPX-

Error

number

DescriptionSerco-

status

code

Description

23 Fault In Filter Measured Value 0x6320 Parameter Error

24 Fault In Parameterizing Lower Limit 0x6320 Parameter Error

25 Fault In Parameterizing Upper Limit 0x6320 Parameter Error

26 Fault In Actuator Supply 0x3420 Actuator Supply

27 Wrong Device Type Mounted – –

28 Alarm Value Reached 0x8110 Process Data Monitoring

29 Fault In Parameterizing 0x6320 Parameter Error

30 No New Output Data (Slave) 0xB023 Local Bus I/O Data Communication

Error

31 No Bus Connection (Slave) 0xB000 Local Bus

(System Bus Of The Modular Station)

32 No STI Read Access (Slave) 0xB000 Local Bus


33 No Parameter Access (Slave) 0xB000 Local Bus


34 CP Module Lost/Fault 0xA001 Sub Bus Slave Missing

35 CP Configuration Failure 0xA002 Incorrect Sub Bus Slave Present

36 Short Circuit CP Line 0x2340 Short Circuit

37 Fault In Controlling – –

38 Missing Valve – –

39 Maintenance Required 0x8B00 Preventive Maintenance Required

(Condition Monitoring)

40 Life Guard – –

41 Heart beat – –

42 Com Cycle Period (Sync) – –

43 CAN Overrun (Objects Lost) – –

44 Invalid PDO Received – –

45 CAN Warn Limit Reached – –

46 CAN Recovered From Bus Off – –

47 Bus Power Lost – –

48 Fault In Calibration – –

49 Lower Drop Out Signal – –

50 Upper Drop Out Signal – –

51 Sensor Limit Exceeded 0x8900 Sensors

52 Short Circuit Cold Junction Comp. – –

53 Open Load Cold Junction Comp. – –

54 Calibration Data Incorrect – –

55 Invalid Process Value – –

56 Short Circuit I-Port 0x2340 Short Circuit



CPX-

Error

number

DescriptionSerco-

status

code

Description

57 Device Missing/Failure I-Port 0xA001 Sub Bus Slave Missing

58 I-Port Configuration Error 0xA030 Sub Bus Configuration Error

59 Input Overload – –

60 Signal Underflow/Overflow 0x8000 Monitoring

61 Overvoltage In Power Supply Supply Voltage

64 Number Of Modules Incorrect 0xB004 Local Bus Devices Amount Error

(Too Many Devices)

65 F_Dest_Add Mismatch – –

66 F-Communication Fault – –

67 F-Communication Timeout – –

68 Leakage Current – –

69 F-Parameter Fault – –

70 Station Equipment Status Incorrect – –

71 Bus Connection Lost – –

76 Reserve – –

77 Reserve – –

78 Value Out Of Range 0xA010 Device Errors

79 Another Function Failure 0xA010 Device Errors

80 Function Failure 0xA010 Device Errors

81 Monitoring Diag 1 0x8000 Monitoring




100 Configuration Error 0xB030 Local Bus Configuration Error

101 Execution Error 0x5010 Component Error

102 Record Error 0x5010 Component Error

103 Control Error 0x5200 Control System

104 System Error A 0x5010 Component Error

105 System Error B 0x5010 Component Error

106 Error In Valve 0x5010 Component Error

107 Controller Error 0x5200 Control System

108 Encoder Error 0x5010 Component Error

109 Error Motor Or Power Stage 0x5010 Component Error

115 Subsystem Module/Channel Failure 0xA010 Device Errors

128 Switch Unit Defective – –

129 CBUS Asic Not Ready 0xB041 Local Bus Hardware Error

130 CPU Hardware Trap 0xB041 Local Bus Hardware Error

131 CBUS C-Manager Not Ready 0xB041 Local Bus Hardware Error

132 Watchdog Overflow 0x6010 Software Reset (Watchdog)

133 Remanent Memory Defective 0xB041 Local Bus Hardware Error



CPX-

Error

number

DescriptionSerco-

status

code

Description

134 Flash System Memory Defective 0xB041 Local Bus Hardware Error

135 Number Of Module Parameters > 64 0xB030 Local Bus Configuration Error

136 Slave Not Ready 0xB020 Communication Errors

137 CBUS Diagnostic Telegram 0xB020 Communication Errors

138 CBUS Init Fault (Module Gap) 0xB020 Communication Errors

139 Order Queue Full 0xB020 Communication Errors

140 CBUS-EEPROM Error 0xB041 Local Bus Hardware Error

141 CBUS C-Timeout Error 0xB020 Communication Errors

142 CBUS Telegram Fault 0xB020 Communication Errors

143 BIU Access Error 0x6100 Internal Software (Firmware)

144 Licence Error – –

145 Built-In Self Test Failed 0x5010 Component Error

150 NETOS Fatal Error 0x6100 Internal Software (Firmware)

200 Fault Parameter Transfer Module n – –

201 Invalid Field Bus Address – –

202 Protocol Asic Not Ready – –

203 MMI Serves CPX Module – –

204 Invalid Setting Switch Unit – –

205 Module Set To Default Values – –

255 Unknown Fault 0x1000 General Error

Tab. C.2

Bus node CPX-FB39


Index

A

Abbreviations, Product-specific 65. . . . . . . . . . . .

Address assignment 26. . . . . . . . . . . . . . . . . . . . .

– Determination 34. . . . . . . . . . . . . . . . . . . . . . . .

– Technology modules 32. . . . . . . . . . . . . . . . . . .

Addressing 35. . . . . . . . . . . . . . . . . . . . . . . . . . . .

C

Commissioning 24. . . . . . . . . . . . . . . . . . . . . . . . .

– Address assignment 26. . . . . . . . . . . . . . . . . . .

– Addressing 35. . . . . . . . . . . . . . . . . . . . . . . . . .

Connection technology 19. . . . . . . . . . . . . . . . . .

D

Device description files 40. . . . . . . . . . . . . . . . . .

Diagnostics mode 16. . . . . . . . . . . . . . . . . . . . . .

Diagnostics options, Overview 53. . . . . . . . . . . .

Diagnostics via LED displays 54. . . . . . . . . . . . . .

Diagnostics via status bits 59. . . . . . . . . . . . . . . .

Diagnostics via the I/O diagnostics interface 60.

DIL switches

– Layout 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

– Remove/attach cover 14. . . . . . . . . . . . . . . . . .

– Set 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dismantling 12. . . . . . . . . . . . . . . . . . . . . . . . . . .

E

Edit, Sercos address 18. . . . . . . . . . . . . . . . . . . .

Electrical connections and indicators 11. . . . . . .

Electrical interface (CP interface) 37. . . . . . . . . .

F

Fail safe 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Festo Maintenance Tool (CPX-FMT) software 52. .

Force 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I

I/O diagnostics interface 60. . . . . . . . . . . . . . . . .

Idle mode 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Intended use 7. . . . . . . . . . . . . . . . . . . . . . . . . . .

IP address, setting 21. . . . . . . . . . . . . . . . . . . . . .

IP65/IP67 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L

LED indicators 54. . . . . . . . . . . . . . . . . . . . . . . . .

– CPX-specific 55. . . . . . . . . . . . . . . . . . . . . . . . .

– Network-specific 57. . . . . . . . . . . . . . . . . . . . . .

Lines, network 20. . . . . . . . . . . . . . . . . . . . . . . . .

M

Module identifiers 64. . . . . . . . . . . . . . . . . . . . . .

Modules, Technology 32. . . . . . . . . . . . . . . . . . . .

Mounting 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N

Network 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

– Cables 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

– Connection technology 19. . . . . . . . . . . . . . . . .

– Pin allocation 20. . . . . . . . . . . . . . . . . . . . . . . .

– Plug connector 19. . . . . . . . . . . . . . . . . . . . . . .

Notes on the documentation 6. . . . . . . . . . . . . . .

O

Operating mode 15. . . . . . . . . . . . . . . . . . . . . . . .

– Remote controller 15. . . . . . . . . . . . . . . . . . . . .

– Remote I/O 15. . . . . . . . . . . . . . . . . . . . . . . . . .

Operator unit (CPX-MMI) 52. . . . . . . . . . . . . . . . .

P

Parameterization 50. . . . . . . . . . . . . . . . . . . . . . .

– Methods 51. . . . . . . . . . . . . . . . . . . . . . . . . . . .

– Requirements 51. . . . . . . . . . . . . . . . . . . . . . . .

– via the Festo Maintenance Tool (CPX-FMT)

software 52. . . . . . . . . . . . . . . . . . . . . . . . . . . .

– with the operator unit (CPX-MMI) 52. . . . . . . .

PELV 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pneumatic interface 38. . . . . . . . . . . . . . . . . . . . .

Power supply 23. . . . . . . . . . . . . . . . . . . . . . . . . .

S

Safety instructions, General 7. . . . . . . . . . . . . . .

SDDML files 40. . . . . . . . . . . . . . . . . . . . . . . . . . .

Sercos address 18. . . . . . . . . . . . . . . . . . . . . . . . .

Sercos III 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Servicing 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bus node CPX-FB39


Set

– Diagnostics mode 16. . . . . . . . . . . . . . . . . . . . .

– DIL switches 15. . . . . . . . . . . . . . . . . . . . . . . . .

– IP address 21. . . . . . . . . . . . . . . . . . . . . . . . . . .

– Operating mode 15. . . . . . . . . . . . . . . . . . . . . .

Status bits 59. . . . . . . . . . . . . . . . . . . . . . . . . . . .

T

Technical data 64. . . . . . . . . . . . . . . . . . . . . . . . .

Technology modules 32. . . . . . . . . . . . . . . . . . . .

W

Web servers 22. . . . . . . . . . . . . . . . . . . . . . . . . . .

Reproduction, distribution or sale of this document or communication of its contents to others without express authorization isprohibited. Offenders will be liable for damages. All rights reserved in the event that a patent, utility model or design patent isregistered.

Copyright:Festo SE & Co. KGPostfach73726 EsslingenGermany

Phone:+49 711 347-0

Fax:+49 711 347-2144

e-mail:[email protected]

Internet:www.festo.com

Original: de

Terminal CPX Bus node CPX-FB39 - Festo...Bus node CPX-FB39 6 Festo – P.BE-CPX-FB39-EN – 1504NH...

Documents

Transcript of Terminal CPX Bus node CPX-FB39 - Festo...Bus node CPX-FB39 6 Festo – P.BE-CPX-FB39-EN – 1504NH...