Terminal CPX. Bus node CPX FB36. Description. Network protocol EtherNet/IP Modbus TCP. Industrial Ethernet 2-Port en 1611a [ ]

Transcription

1 Terminal CPX Bus node CPX FB36 Description Network protocol EtherNet/IP Modbus TCP Industrial Ethernet 2-Port en 1611a [ ]

2

3 Contents and general instructions Original... de Version... en 1611a Designation... CPX-FB36-EN Order no (Festo AG & Co. KG, D Esslingen, 2016) Internet: service_international@festo.com Reproduction, distribution or sale of this document or communication of its contents to others without express authorization is prohibited. Offenders will be held liable for damages. All rights are reserved, in particular the right to file patent, utility model or registered design applications. I

4 Contents and general instructions EtherNet/IP, Modbus, ROCKWELL AUTOMATION, SPEEDCON are registered trademarks of the respective trademark owners in certain countries. II

5 Contents and general instructions Contents Intended use... Safety instructions... Qualification of specialized personnel (target group)... Service... Notes regarding this description... Important user information... VIII IX X X XI XII 1. Installation General instructions for installation Connection and display components Dismantling and mounting Settings of the DIL switches Removing and attaching cover Arrangement of the DIL switches Setting the DIL switches Setting the operating mode and network protocol Setting diagnostic mode or data field size Setting IP addressing Connecting to the network General instructions Overview of connection technology and network plug connectors Cable specification Network connections Setting the IP addressing Extended network settings Ensuring the degree of protection Power supply of the CPX terminal III

6 Contents and general instructions 2. Preparing for commissioning EtherNet/IP protocol Multicast telegram QuickConnect Device Level Ring protocol (DLR) Modbus TCP protocol Notes on commissioning of the CPX-FB Requirements for commissioning Switching on the power supply Normal operating status Participants in the network Participant properties (EDS file) Commissioning Configuration Configuration with EDS file Configuration with Generic Ethernet Module Configuration with CPX-FMT Configuration in the Remote Controller operating mode Setting up a Listen only connection Parameterisation Parameterisation during switch-on [system start] Methods of parameterisation Parameterisation via configuration data Parameterisation with the control device CPX-MMI Parameterisation in the PLC user program Parameterisation using CPX-FMT and system start with saved parameters Behaviour of the outputs in the Fail safe mode or Idle mode Web server Checklist for commissioning a CPX terminal Replacing the bus node IV

7 Contents and general instructions 4. Diagnostics Diagnostics options Diagnostics via LED displays CPX-specific LED displays Network-specific LED indicators Diagnostics via status bits Diagnostics via the I/O diagnostics interface Diagnostics via EtherNet/IP Diagnostics via Modbus TCP Error handling ( Fail safe ) A. Technical appendix... A-1 A.1 Technical data... A-3 B. Address assignment of the CPX terminal... B-1 B.1 Address assignment... B-3 B.1.1 Bus node... B-4 B.1.2 Digital modules... B-5 B.1.3 Analogue modules... B-9 B.1.4 Technology modules... B-10 B.2 Addressing... B-12 B.2.1 Basic rules for addressing... B-12 B.2.2 Data formats... B-13 B.2.3 Examples of addressing... B-14 B.3 Address assignment after extension/conversion... B-20 V

8 Contents and general instructions C. EtherNet/IP Objects of the CPX-FB36... C-1 C.1 Overview of Ethernet/IP objects... C-3 C.2 Objects for network settings... C-8 C.2.1 Device Level Ring Object... C-8 C.2.2 QoS Object... C-9 C.2.3 TCP/IP Interface Object... C-10 C.2.4 Ethernet Link Object... C-12 C.3 Objects for the I/O connection... C-13 C.3.1 Assembly Object... C-13 C.4 Objects for system data and diagnostics... C-18 C.4.1 Identity Object... C-18 C.4.2 Global System Object for operating mode Remote I/O... C-20 C.4.3 Status and Diagnosis Object... C-23 C.4.4 Diagnosis Trace Object... C-24 C.4.5 Diagnosis Trace Status Object... C-26 C.4.6 Generic Parameter Object... C-28 C.4.7 Force Parameter... C-31 C.4.8 Fail safe and Idle parameters... C-36 C.4.9 Configuration Array Object... C-42 C.4.10 Slave Size Object for Remote Controller operating mode... C-42 C.4.11 ISDU Access Object... C-43 C.5 Examples... C-45 C.5.1 Forcing inputs... C-45 C.5.2 Parameterisation with Generic Parameter Object... C-47 VI

9 Contents and general instructions D. Modbus TCP objects of the CPX-FB36... D-1 D.1 Overview of Modbus TCP objects... D-3 D.2 Commands and addresses... D-3 D.3 CPX status information (Group A)... D-4 D.4 Process data (Group B and D)... D-6 D.4.1 Bus node CPX-FB36... D-6 D.4.2 Electric modules... D-7 D.4.3 Pneumatic modules... D-10 D.4.4 Electrical interface (CP interface) CPX-CP-4-FB... D-15 D.4.5 Composition of diagnostic data (diagnostic word)... D-19 D.4.6 Composition of the data of the I/O diagnostics interface... D-20 D.5 Diagnostic memory (Groups C and E)... D-21 D.6 Modbus TCP Objects (Group F)... D-23 D.6.1 Addressing examples for Modbus TCP... D-24 E. Index... E-1 VII

10 Contents and general instructions Intended use The bus node described in this description is intended exclusively for use in CPX terminals from Festo for installation in a machine or automated system. In combination with a CPX terminal, the bus node is used for communication as a participant in networks with the protocols EtherNet/IP or Modbus TCP. The CPX terminal may only be used as follows: as intended in industrial environments; outside of industrial environments, e.g. in commercial and mixed-residential areas, actions to suppress radio interference may have to be taken in its original state without unauthorised modifications; only the conversions or modifications described in the documentation supplied with the product are permitted. in perfect technical condition only in combination with approved components Observe the specified limit values. Take into consideration the applicable regulations for the destination as well as directives and standards, regulations of the inspection organisations, insurance companies and national regulations. VIII

11 Contents and general instructions Safety instructions Before assembly or installation work, switch off the power supply, switch off the compressed air supply, exhaust any pneumatic components. For the electrical power supply, only use PELV circuits in accordance with IEC /EN Note the information on installation and power supply as well as on potential equalisation (earthing measures) in the CPX system description ( P.BE-CPX-SYS- ). Observe the handling specifications for electrostatically sensitive devices. Seal unused connections with cover caps to achieve the required degree of protection. Use connection technology with the required degree of protection. Observe the specifications in the CPX system description, in the descriptions of the valve terminal used as well as in the assembly instructions of the individual components. Observe the instructions for correctly mounting the CPX terminal. Place only a completely mounted and wired CPX terminal into operation. Only switch on the compressed air and load voltage if the system has been professionally installed, configured and parameterised. Make sure that nobody enters the positioning range of the actuators. Switching off the compressed air or load voltage is not a suitable locking mechanism. Unintentional movement of actuators may occur in the event of a malfunction. IX

12 Contents and general instructions Qualification of specialized personnel (target group) The product must only be commissioned by trained experts in control and automation technology who are familiar with: mounting, installation, operation and diagnostics of control systems, networks and fieldbus systems the applicable regulations for accident prevention and occupational safety the documentation for the product. Service Consult your local Festo repair service if you have any technical problems. X

13 Contents and general instructions Notes regarding this description This description contains specific information on the installation, configuration, parameterisation, commissioning, programming and diagnostics with the CPX-FB36 bus node for EtherNet/IP and Modbus TCP. An overview of the structure of user documentation for the CPX terminal can be found in the CPX system description ( P.BE.CPX-SYS- ). Additional information regarding EtherNet/IP can be found here: Additional information regarding Modbus TCP can be found here: The bus node has been certified by the Open Device Vendor Association (ODVA): 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. XI

14 Contents and general instructions Important user information Danger categories This description includes instructions on the possible dangers that can occur if the product is used incorrectly. These danger warnings are marked with a signal word (warning, caution, etc.), placed on a grey background and additionally marked with a pictogram. A distinction is made between the following danger warnings: Warning... means that non-observance can result in serious personal injury or damage to property. Caution... means that injury to people and damage to property can occur if this warning is not observed. Note... means that damage to property can occur if this warning is not observed. In addition, the following pictogram marks passages in the text that describe activities involving electrostatic sensitive devices: Electrostatically sensitive devices: Incorrect handling can cause damage to devices. XII

15 Contents and general instructions Marking of special information The following pictograms mark passages in the text that contain special information. Pictograms Information: Recommendations, tips and references to other information sources. Accessories: Information about necessary or useful accessories for the product. Environment: Information on the environmentally friendly use of the product. Text designations Bullet points denote activities that can be carried out in any order. 1. Numerals label activities that must be carried out in the sequence specified. Arrowheads indicate general lists. XIII

16 Contents and general instructions The following product-specific terms and abbreviations are used in this description: Term/abbreviation Significance 160 d Decimal numbers are marked in part by a low-set d. A0 h AO AI BOOTP Bus node CEC CoDeSys CP CP module CPX-CP interface CPX-FMT CPX-MMI CPX modules Hexadecimal numbers are marked by a low-set h. Analogue output Analogue input Dynamic protocol for automatic assignment of IP addresses (Boot protocol, predecessor of DHCP). Provides the connection to specific fieldbuses. It transmits control signals to the connected modules and monitors their ability to function. CoDeSys Controller, e.g. CPX-CEC, usable for control, configuration and commissioning of CPX terminals. Controller Development System Compact Performance Collective term for the various modules which can be integrated into the CP system (decentralised installation system). Interface for connecting decentrally arranged CP modules to a CPX terminal. Festo Maintenance Tool for configuration and parameterisation of CPX terminals. Operator unit for commissioning and service purposes. Collective term for electric modules which can be incorporated into a CPX terminal: bus nodes, I/O modules and function modules (technology modules). CPX modules provide, among other things, electrical inputs and outputs for connecting sensors and actuators. CPX modules form the electrical side of the CPX terminal. Tab. 0/1: CPX-specific terms and abbreviations - part 1 XIV

17 Contents and general instructions Term/abbreviation CPX terminal DHCP DI DIL switches DO EtherNet/IP FEC Function module I I/O diagnostics interface I/O modules I/O signal I/Os Modbus TCP O Significance Complete system consisting of various CPX modules with or without pneumatics modules. Dynamic protocol for automatic assignment of IP addresses (Dynamic Host Configuration Protocol). Digital input Dual in-line switches consist of several switch elements with which settings can be made. Digital output Communication protocol for connecting various devices in a network. Control block, e.g. CPX-FEC, usable as: stand-alone system controller (PLC, Stand Alone operating mode) system controller (PLC, Remote Controller operating mode) fieldbus slave (Remote I/O operating mode) Collective term for modules with additional functions, e.g. CPX-CP interface, control block (CPX-FEC) and CoDeSys controller (CPX-CEC); function modules are also known as technology modules. Digital input Network-independent diagnostic interface at I/O level, which enables access to the internal data of the CPX terminal. Collective term for the CPX modules that provide digital or analogue inputs and/or outputs. Input/output signal of an I/O module; also referred to as a process signal. Analogue or digital inputs and outputs. Communication protocol via TCP/IP in automation technology. Digital output Tab. 0/2: CPX-specific terms and abbreviations - part 2 XV

18 Contents and general instructions Term/abbreviation Pneumatic interface Pneumatic modules Status bits Technology module Significance Interface between CPX modules and pneumatic modules within a CPX terminal. The pneumatic interface counts functionally as part of the electrical side of the CPX terminal. Collective term for the pneumatics modules which can be integrated into a CPX terminal. They provide outputs (working ports) for connecting actuators, e.g. cylinders. They form the pneumatic side of the CPX terminal. Internal inputs that supply coded common diagnostic messages Function module Tab. 0/3: CPX-specific terms and abbreviations - part 3 XVI

19 Contents and general instructions Data type Size Range of values Description ARRAY 1) Structure with identical data types BOOL 1 bit 0 false and 1 true Logical data type BYTE 8 bit 00 h FF h Bit field DWORD 32 bit h FFFFFFFF h Bit field DINT 32 bit Signed Double Integer INT 16 bit 32,768 32,767 Signed Integer Padded EPATH Max. 12 bytes Logical segments of a path specification SINT 8 bit Signed Short Integer STRING 8 bit/character String SHORT_STRING 8 bit/character + 8 bit length specification String with max. 255 characters STRUCT 1) Structure of any data types UDINT 32 bit 0 4,294,967,296 Unsigned Double Integer UINT 16 bit 0 65,536 Unsigned integer USINT 8 bit Unsigned Short Integer WORD 16 bit 0000 h FFFF h Bit field 1) Dependent on the data types used Tab. 0/4: Data types used XVII

20 Contents and general instructions XVIII

21 Installation Chapter 1 Installation 1-1

22 1. Installation Contents 1. Installation General instructions for installation Connection and display components Dismantling and mounting Settings of the DIL switches Removing and attaching cover Arrangement of the DIL switches Setting the DIL switches Setting the operating mode and network protocol Setting diagnostic mode or data field size Setting IP addressing Connecting to the network General instructions Overview of connection technology and network plug connectors Cable specification Network connections Setting the IP addressing Extended network settings Ensuring the degree of protection Power supply of the CPX terminal

23 1. Installation 1.1 General instructions for installation Warning Uncontrolled movements of the actuators and loose tubing, undefined switching states of the electronic components Injury caused by moving parts, damage to machine and to system Before mounting and installation work: Switch off the power supplies Switch off the compressed air supply Exhaust any pneumatic components. Note Electrostatically sensitive devices Do not touch any components. Observe the handling specifications for electrostatically sensitive devices. Note Ensuring the required degree of protection Use cover caps to seal unused connections ( 1.4 Ensuring the degree of protection). Information about mounting of the CPX terminal can be found in the CPX system description ( P.BE-CPX-SYS-...). 1-3

24 1. Installation Connection and display components 1 Network-specific and CPX-specific LED indicators 2 Network connections [X1], [X2] 3 DIL switches 4 Service interface ) 2 socket, M12, D-coded, 4-pin 2) Socket, M12, A-coded, 5-pin; for the control device CPX-MMI or Festo Maintenance Tool CPX-FMT Fig. 1/1: Connection and display components Dismantling and mounting The bus node is installed in an interlinking block of the CPX terminal ( Fig. 1/2). 1 Screws 2 Interlinking block 3 Bus node CPX-FB Fig. 1/2: Dismantling/mounting 1-4

25 1. Installation Dismantling the bus node 1. Unscrew the screws. 2. Pull the bus node without tilting out of the interlinking block. Mounting the bus node 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. 1. Check seal and sealing surface. Replace damaged parts. 2. Push the bus node 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: 1 Nm ± 10 %. 1-5

26 1. Installation 1.2 Settings of the DIL switches The following settings can be made through the DIL switches: Operating mode and network protocol Diagnostic mode or data field size IP addressing The settings of the DIL switches become effective only after the power supply is switched on Removing and attaching cover To set the DIL switches at the bus node, the cover must be removed. Removing the DIL switch cover 1. Switch off power supply. 2. Unscrew the screws. 3. Remove the DIL switch cover. Attaching the DIL switch cover 1. Put the DIL switch cover in place. Make sure that the seal is seated correctly. 2. Tighten the screws. Tightening torque: max. 0.4 Nm. 1-6

27 1. Installation Arrangement of the DIL switches 1 DIL switch 1: operating mode and network protocol 2 DIL switch 2 diagnostic mode or data field size 1) DIL switch 3: IP addressing 1) Depending on the set operating mode Fig. 1/3: DIL switches Setting the DIL switches Procedure 1. Switch off power supply. 2. Remove the DIL switch cover ( 1.2.1). 3. Make the settings for the DIL switches ( ). 4. Re-attach the DIL switch cover ( 1.2.1). 1-7

28 1. Installation Setting the operating mode and network protocol DIL switch1.1 DIL 1.1: OFF (Factory setting) DIL 1.1: ON Operating mode Remote I/O All functions of the CPX terminal are controlled directly by the higher-order controller (PLC). A control block integrated into the CPX terminal (e.g. CPX-CEC or CPX-FEC) works as a passive function module without controller. Remote controller A control block integrated into the CPX terminal (e.g. CPX-CEC or CPX-FEC) takes over I/O control. This operating mode is only useful if a control block is integrated into the CPX terminal. Tab. 1/1: Setting the operating mode DIL switch1.2 DIL 1.2: OFF (Factory setting) Network protocol EtherNet/IP The CPX terminal uses the EtherNet/IP network protocol. DIL 1.2: ON Modbus TCP The CPX terminal uses the Modbus TCP network protocol. Tab. 1/2: Setting the network protocol 1-8

29 1. Installation Setting diagnostic mode or data field size The function of DIL switch 2 is dependent on the set operating mode of the CPX terminal ( Tab. 1/1). DIL switch2 2.1: OFF 2.2: OFF (Factory setting) 2.1: ON 2.2: OFF 2.1: OFF 2.2: ON 2.1: ON 2.2: ON Diagnostics mode (Remote I/O) 1) I/O diagnostics interface and status bits switched off I/O diagnostics interface is switched on Status bits switched on Reserved Data field size (Remote Controller) 2) 8 byte I/8 byte O for communication of the bus node with a control block (e.g. B. CPX- FEC) 32 byte I/32 byte O for communication of the bus node with a control block (e.g. B. CPX-FEC) 3) 16 byte I/16 byte O for communication of the bus node with a control block (e.g. B. CPX-FEC) 64 byte I/64 byte O for communication of the bus node with a control block (e.g. B. CPX-FEC) 4) 1) Setting of the diagnostic mode is available only in the remote I/O operating mode. 2) Setting of the data field size is available only in the remote controller operating mode. 3) From Revision 12 4) From Revision 13 Tab. 1/3: Setting diagnostic mode or data field size During subsequent activation of the diagnostics mode (status bits or I/O diagnostics interface), the CPX-internal I/O illustration or address allocation can be shifted. The system controller carries out this adjustment automatically. Manual manipulation, e.g. a reconfiguration of the CPX terminal or manual adaptation of the hardware and network configuration, are not required. 1-9

30 1. Installation Setting IP addressing DIL switch3 IP addressing DIL 3.8: DIL 3.7: DIL 3.6: DIL 3.5: DIL 3.4: DIL 3.3: DIL 3.2: DIL 3.1: 2 7 = 2 6 = 2 5 = 2 4 = 2 3 = 2 2 = 2 1 = 2 0 = The type of addressing or the host ID of the IP address of the bus node is set via DIL switch elements Possible settings: 0 = Dynamic addressing via DHCP/BOOTP = Permissible address range 255 = Reset all IP parameters to factory setting Factory setting: 0 Tab. 1/4: Setting IP addressing Dynamic addressing is set via DHCP/BOOTP by default. If all of the switch elements of DIL switch3 are set to ON when the bus node is switched on, all IP parameters will be reset to the factory setting. Example Setting IP address of the bus node DIL 3.8: DIL 3.7: DIL 3.6: DIL 3.5: DIL 3.4: DIL 3.3: DIL 3.2: DIL 3.1: OFF Off ON Off Off ON ON Off 2 5 = = = 2 Example: = = 38 (Host-ID) Set IP address: Tab. 1/5: Example IP addressing 1-10

31 1. Installation 1.3 Connecting to the network General instructions Note Unauthorised access to the device can cause damage or malfunctions. When connecting the device to a network: Protect the network from unauthorised access. Measures to protect the network include: firewall Intrusion Prevention System (IPS) network segmentation virtual LAN (VLAN) Virtual Private Network (VPN) security at physical access level ( Port Security ). For further notes, please refer to the guidelines and standards for security in information technology, e.g. IEC 62443, ISO/IEC An access password protects only against accidental changes. Note Assemblies with Ethernet interfaces should only be operated in networks if all connected network components are supplied by PELV circuits or integrated circuits with equivalent protection. 1-11

32 1. Installation Installation guidelines Installation guidelines can be sourced from the ODVA user organization ( Use of switches and routers The switch integrated in the bus node permits division of the network into several segments. With use of additional switches and routers, the network can be divided into additional segments. Thus, it is possible to structure the network and realise a greater network expansion. Independent of the network structure, the expansion of a network segment must not exceed certain connection lengths. Copper connecting cable: (Ethernet twisted pair cable, 22 AWG): max. 100 m between network participants Switches and routers for Industrial EtherCat are available in the market from various companies and in a variety of components in IP20, IP65 or IP67. Unmanaged Switches: For small networks with a low network load or minimal requirements for determinism Managed Switches: For comprehensive networks with diagnostics and monitoring functions 1-12

33 1. Installation Overview of connection technology and network plug connectors Note Faulty installation and high transmission rates may cause data transmission errors as a result of signal reflections and attenuations. Observe cable specification ( Tab. 1/7). Transmission errors can be caused by: faulty screened connection branches transmission over distances which are too long unsuitable cables. Connection technology 2 x socket M12, D-coded, 4-pin, in accordance with IEC , SPEEDCON compatible Network connectors Plug connector NECU-M-S-D12G4-C2-ET Tab. 1/6: Overview of connection technology and network plug connectors RJ45 to M12 converter For EtherNet/IP installations, it may be necessary to change between RJ45- and M12 connection technology. Example: Connections between devices in a control cabinet and IP65/IP67 devices. 1-13

34 1. Installation Cable specification Use sheathed Industrial Ethernet wiring of category Cat 5/Cat 5e or higher ( Tab. 1/7). The CPX bus node supports the crossover detection function (Auto-MDI/MDI-X). To connect the bus node to the network or to a PC, this means you can choose between patch cables or crossover cables. The circuitry of the network connections X1 and X2 is adjusted automatically. Cable specification Cable type Transmission class Cable diameter 1) Ethernet twisted pair cable, screened Category Cat 5/Cat 5e 6 8 mm Wire cross section mm 2 ; 22 AWG 2) Connection length 3) Maximum 100 m ( end-to-end link ) 1) When using plug NECU M S D12G4 C2 ET 2) Required for maximum connection length between network participants 3) Corresponding to specification for EtherNet/IP networks, based on ISO/IEC 11801, ANSI/TIA/EIA-568 ( General instructions) Tab. 1/7: Cable specification Note When mounting the CPX terminal on a moving part of a machine: Use network wiring with tension relief. Observe corresponding stipulations of IEC 60204/EN

35 1. Installation 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. Both connections have Auto-Negotiation and Crossover detection (factory setting). When crossover detection is activated, the bus node automatically exchanges the transmitted and received data. If crossover detection is deactivated, assignment of the pins for transmitted and received data at the XP2 connection is crossed. As a result, several bus nodes in a row can each be connected with a patch cable. Socket 1) Pin Connection [X1] 2) Connection [X2] 2) M12, 4-pin Signal Explanation Signal Explanation Housing TD+ RD+ TD RD Shield Transmitted data + Received data + Transmitted data Received data Functional earth RD+ TD+ RD TD Shield Received data + Transmitted data + Received data Transmitted data Functional earth 1) Functional earth is accomplished via the housing 2) Pin activation with deactivated crossover detection Tab. 1/8: Pin allocation of the network connections [X1] and [X2] If the QuickConnect function has been activated, the crossover detection function is not available. Further notes on wiring with deactivated crossover detection can be found in chapter

36 1. Installation Connection with plug connector by Festo The CPX terminal is connected to the network with plugs NECU-M-S-D12G4-C2-ET. The plugs are designed for network lines with cable diameters of mm. To comply with degree of protection IP65/IP67: Use Festo plugs. Use cover caps to seal unused connections ( 1.4 Ensuring the degree of protection) Setting the IP addressing Alternatively the IP address for the bus node can be set via: Dynamic addressing via DHCP/BOOTP (factory setting) Saved addressing Static addressing via DIL switches Note If changes are made to the network settings through the DIL switches, the Modify LED (M) flashes yellow. Restart the bus node so that the revised network settings can be taken over. 1-16

37 1. Installation Dynamic addressing via DHCP/BOOTP Make sure there is a DHCP/BOOTP server in the network. To set the dynamic addressing: 1. Switch all switch elements of the DIL switch 3 into the OFF position ( Tab. 1/4). 2. Alternatively, activate dynamic addressing via DHCP/ BOOTP using: Operator unit (CPX-MMI) Festo Maintenance Tool (CPX-FMT) software BOOTP-DHCP Server software from Rockwell Automation Saved network settings The bus node offers the option of saving network settings in a non-volatile memory unit in the bus node. DHCP/BOOTP is thereby deactivated. 1. Switch all switch elements of the DIL switch 3 into the OFF position ( Tab. 1/4). 2. Alternatively change the network settings via: Operator unit CPX-MMI Festo Maintenance Tool (CPX-FMT) program BOOTP-DHCP Server program from Rockwell Automation Use this setting to activate the storage of network settings in a non-volatile memory of the bus node. 1-17

38 1. Installation Addressing via DIL switches When addressing via DIL switches, the bus node obtains a fixed IP address. This setting is recommended for test purposes during commissioning or for small networks. The IP address of the bus node consists of 4 octets: Octets 1 3: stored in the bus node Octet 4: setting via DIL switch 3 Set a binary number between 1 and 254 over the DIL switch elements This number is then used as the 4th octet of the IP address when the bus node is switched on. Example with IP address: Example with IP address: = = = = 38 Tab. 1/9: Examples of fixed values for the 4th octet of the IP address (binary coded) If all of the switch elements of DIL switch3 are set to ON when the bus node is switched on, all network parameters will be reset to the factory setting. 1-18

39 1. Installation Factory settings of the CPX-FB36 IP address octet IP address octet 4 0 1) Network mask Gateway ) Dynamic addressing via DHCP/BOOTP Tab. 1/10: Factory settings Alternatively, change the first 3 octets of the IP address with: Operator unit CPX-MMI Festo Maintenance Tool CPX-FMT Festo Field Device Tool FFT Access via EtherNet/IP objects ( C.1) The network mask and gateway are set by using the corresponding CPX parameters. 1-19

40 1. Installation Extended network settings The following settings for the network connection can be made through the Ethernet link object 0xF6 (246 d ) ( C.2.4). In the factory setting, the bus node automatically detects the baud rate and duplex mode. Baud rate Setting via attribute 6 (Forced Interface Speed) of the Ethernet link object: 10 Mbit/s 100 Mbit/s Duplex mode Setting via attribute 6 (control bits, bit 1) of the Ethernet link object: Half duplex Full duplex 1-20

41 1. Installation 1.4 Ensuring the degree of protection Use connection technology with the required degree of protection ( examples in Tab. 1/11). Use cover caps to seal unused connections. Compressed air Connection technology Cover cap Network connection (M12) Plug connector NECU-M-S-D12G4-C2-ET ISK-M12 Service interface (M12) Connecting cable KV-M12-M ) ISK-M12 1) Connecting cable for the operator unit (CPX-MMI) Tab. 1/11: Connection technology and cover caps for degree of protection IP65/IP67 (examples) 1-21

42 1. Installation 1.5 Power supply of the CPX terminal CPX terminals are supplied with operating and load voltage through interlinking blocks or end plates. Warning Electric 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/EN (Protective Extra-Low Voltage, PELV). Observe the general requirements in accordance with IEC/EN for PELV circuits. Use only voltage sources that ensure a reliable electric separation from the mains network in accordance with IEC/EN Always connect all of the power circuits for operating and load voltage supplies U EL/SEN and U VAL/OUT. The current consumption of a CPX terminal depends on the number and type of integrated modules and components. Observe the information on power supply ( electrical connection) as well as on the earthing measures to be carried out ( potential equalisation) contained in the CPX system description. 1-22

43 Preparing for commissioning Chapter 2 Preparing for commissioning 2-1

44 2. Preparing for commissioning Contents 2. Preparing for commissioning EtherNet/IP protocol Multicast telegram QuickConnect Device Level Ring protocol (DLR) Modbus TCP protocol Notes on commissioning of the CPX-FB Requirements for commissioning Switching on the power supply Normal operating status Participants in the network Participant properties (EDS file)

45 2. Preparing for commissioning 2.1 EtherNet/IP protocol EtherNet/IP is an industrial Ethernet protocol, which is predominantly used in automation technology. The EtherNet/IP protocol is activated with DIL switch 1.2 in the OFF position ( Tab. 1/2). The bus node is then identified with the designation FB36 - EtherNet IP Remote-IO. After switching the protocol, the following unmodified parameters are available: IP address Diagnostics mode System parameters The DIL switch function remains unchanged. Retentive bus-specific parameters are only active if the relevant protocol is selected ( section 1.2.4). Parameterisation examples can be found in the appendix ( C.5) Multicast telegram EtherNet/IP uses IP Multicast telegrams as standard for transferring process data. The advantage of Multicast compared to Unicast is that a telegram can be received by multiple participants. Simple switches, however, cannot distinguish to which participant a Multicast telegram is to be transferred. Therefore, these switches send the Multicast telegrams to all devices in the network. This results in an EtherNet/IP participant receiving numerous unnecessary telegrams, which must then be discarded from 2-3

46 2. Preparing for commissioning the device. This can reduce the response times of the participants. The demand on the network bandwidth increases. This does not pose a problem for smaller networks; the performance for larger networks, however, can be improved with the following functions and/or protocols. Use of switches with IGMP snooping Segmentation of the network Switches with IGMP snooping By using an IGMP (Internet Group Management Protocol), the switches are able to decide to which devices the various Multicast telegrams are transferred. As a result, unnecessary data traffic is avoided through Multicast. Activate this function in all switches/routers used. Configure at least one switch so that cyclical IGMP queries are sent. The IGMP snooping function cannot work properly without these IGMP queries. Segmentation of the network Split the machine into smaller network segments. This can be realised without changing the network cabling, for example, by using VLANs. 2-4

47 2. Preparing for commissioning QuickConnect The EtherNet/IP QuickConnect function enables a quicker initialisation of the CPX terminal and a fast connection set-up to the EtherNet/IP master. QuickConnect is commonly used for applications with a tool change, for which the downtime should be minimised by the disconnection and connection of devices. Note QuickConnect only works if this function is supported by all participating devices. Make sure that intermediate switches and routers in your network support this function. The QuickConnect function in the bus node is in a deactivated state when delivered. Using QuickConnect : 1. Activate QuickConnect via attribute 12 of the TCP/IP interface object ( C.2.3). This automatically deactivates Crossover detection in the bus node. 2. Restart the bus node so that the revised network settings can be taken over. 3. Use the same settings for baud rate and duplex mode at the counterpart station (e.g. switch) and at the PLC as in the bus node. For fast connection set-up: 100 MBit/s Full duplex 4. Activate QuickConnect in the PLC or the control program. 2-5

48 2. Preparing for commissioning Simplified configuration of QuickConnect at the bus node CPX-FB36: Set the CPX parameter IP configuration to with saved parameters and QuickConnect. With activation of QuickConnect, the Crossover detection is deactivated for both network connections. As a result, connection X1 runs in the MDI-mode and connection X2 runs in the MDI-X mode. This allows a line topology to be constructed with patch cables: TP1 TP2 X1 X2 X1 X2 X1 X2 MDI MDIX MDI MDIX MDI MDIX PLC or switch 3 I/O device (e.g. B. CPX-FB36) 2 Patch cable Fig. 2/1: QuickConnect line topology with patch cables The bus node corresponds to a Class A device in accordance with the EtherNet/IP specification. When switched on, the bus node requires less than 350 ms to accept a TCP connection. Due to the rapid establishment of the TCP connection, the detection of already used IP addresses (ACD, IP Address Conflict Detection ) is not executed completely. Multiple assigned IP addresses are only detected late. As a result, the network can be disturbed. If IP addresses are correctly assigned in the network, deactivate the ACD via attribute 10 of the TCP/IP interface object ( C.2.3). 2-6

49 2. Preparing for commissioning QuickConnect is available for the following modules: CPX modules Bus node Digital 4-off input module Digital 8-off input module Digital 8-off input module with channel diagnostics Digital 8-off input module, n-switching Digital 16-off input module Digital 16-off input module with channel diagnostics Digital 16-off input module, with terminal strip Digital 4-off output module Digital 8-off output module Digital 8-off output module, high-current variant Digital 8-off input/output module Digital 16-off input/output module, with terminal strip Analogue 2-off input module (voltage/current) Analogue 2-off output module (voltage/current) Analogue 4-off input module (current) Order code CPX-FB36 CPX-4DE CPX-8DE CPX-8DE-D CPX-8NDE CPX-16DE CPX-M-16DE-D CPX L 16DE 16 KL 3POL CPX-4DA CPX-8DA CPX-8DA-H CPX-8DE-8DA CPX L 8DE 8DA 16 KL 3POL CPX 2AE U I CPX 2AA U I CPX 4AE I Tab. 2/1: CPX modules, which support QuickConnect 2-7

50 2. Preparing for commissioning QuickConnect is available for the following pneumatic modules and pneumatic interfaces: Pneumatic modules MPA1 pneumatic module MPA2 pneumatic module MPA1 pneumatic module with diagnostic function MPA2 pneumatic module with diagnostic function Type VMPA1-FB-EM...-8 VMPA2-FB-EM...-4 VMPA1-FB-EM...-D2-8 VMPA2-FB-EM...-D2-8 Tab. 2/2: Pneumatic modules that support QuickConnect Pneumatic interfaces for VTSA or VTSA F pneumatics for MPA S valves for MPA F valves for MPA L valves Type VABA 10S6 X1 VMPA FB EPL VMPAF FB EPL... VMPAL FB EPL... VMPAL EPL CPX Tab. 2/3: Pneumatic interfaces that support QuickConnect Device Level Ring protocol (DLR) The Device Level Ring protocol (DLR) allows multiple devices to be operated in a ring topology. Requirements All DLR devices feature an integrated Ethernet switch with at least 2 external ports and support the DLR Protocol. 2-8

51 2. Preparing for commissioning Ring Supervisor Ring Node 4 Ring Node 1 Ring Node 3 Ring Node 2 Fig. 2/2: Device Level Ring topology, example The availability of the network can be increased through the ring topology, as there are redundant communication paths between two devices. A cable or communication error between two devices will therefore not result in communication failure. Only two errors in a ring will lead to a malfunction. A ring always consists of at least one ring supervisor and any number of ring nodes. Only use DLR-capable devices in a ring. Otherwise, the time required for automatic elimination of an error may be adversely affected. Operate the bus node as a ring node either in a beaconbased or announce-based configuration. Operation as a ring supervisor is not possible. This function is normally executed by an EtherNet/IP scanner. The DLR protocol is configured via the DLR object (class code 47 h ). 2-9

52 2. Preparing for commissioning 2.2 Modbus TCP protocol Modbus is an open communication protocol based on the master-slave architecture. It is a standard for communication via TCP/IP in automation technology. The Modbus TCP protocol is activated with DIL switch 1.2 in the ON position ( Tab. 1/2). The bus node is then identified with the designation FB36-MB - Modbus TCP Remote-IO. After switching the protocol, the following unmodified parameters are available: IP address Diagnostics mode System parameters The DIL switch function remains unchanged. Retentive bus-specific parameters are only active if the relevant protocol is selected ( section 1.2.4). The configuration options via Modbus TCP correspond to those via EtherNet/IP. Exception: EtherNet/IP objects cannot be accessed via Modbus TCP. In order to configure the CPX terminal for Modbus TCP, the Modbus addresses of the data and of the inputs and outputs of the CPX terminal are required. ( D). Addressing examples can be found in the appendix ( D.6.1). 2-10

53 2. Preparing for commissioning 2.3 Notes on commissioning of the CPX-FB36 Configuration of the CPX terminal requires an exact procedure, as different configuration specifications are sometimes necessary for each station in the network, due to the modular structure. Detailed instructions and further information can be found in the documentation or the online help for the controller or control program. Note The bus node CPX-FB36 can be used on all EtherNet/IP or Modbus TCP controllers. The following section describes the configuration and commissioning procedure using the example of a controller from Allen-Bradley with the help of the Studio 5000 software from Rockwell Automation Requirements for commissioning Installation of the bus node is complete. The DIL switches of the bus node are set correctly. All connecting cables are connected and checked. 2-11

54 2. Preparing for commissioning Switching on the power supply Warning Uncontrolled movement of the actuators, undefined switching statuses. Injury to people, damage to the machine and system. Before switching on: Make sure that the requirements for commissioning are met. Check settings of the DIL switches. During operation: Leave switch elements of the DIL switches unchanged during operation. Note Observe the switching-on instructions in the controller manual Normal operating status After the CPX terminal is switched on, the status LEDs ( Fig. 4/1) indicate the operating status and correct function of the bus node as well as of the network communication dependent on the configuration. Bus node not configured ( Tab. 2/4) Bus node configured and higher-order controller (PLC) is in stop mode ( Tab. 2/5) Bus node configured and higher-order controller (PLC) is in the Run stop mode ( Tab. 2/6) Information on diagnostics using the LED displays can be found in section

55 2. Preparing for commissioning Bus node not configured LED indicator [MS] Status and significance Device ready for operation Lights up green [PS] Lights up green [NS] Flashes green [PL] Power supply (Power System, PS) is OK Operating voltage present (in the approved range) Network communication present but not configured (operating status online ), In this case, this is correct, because the bus node is not configured. Load voltage present (in the approved range) 1) Lights up green [TP1], [TP2] Lights up green Device is correctly connected to the bus node Internal communication between bus node and device 1 or device 2 is error free Operating and load voltage present (in the approved range) 1) 1) Display dependent on monitoring and signal from the connected device. Tab. 2/4: Status LEDs after switch-on bus node not configured 2-13

56 2. Preparing for commissioning Bus node configured PLC in the stop mode LED indicator [MS] Status and significance Module status (MS) error free Lights up green [PS] Lights up green [NS] Lights up green [PL] Power supply (Power System, PS) is OK Operating voltage present (in the approved range) Network status (NS) error free ( online operating status) Communication with the network and PLC OK Load voltage present (in the approved range) 1) Lights up green [TP1], [TP2] Lights up green Device is correctly connected to the bus node Internal communication between bus node and device 1 or device 2 is error free Operating and load voltage present (in the approved range) 1) 1) Display dependent on monitoring and signal from the connected device. Tab. 2/5: Status LEDs after switch-on bus node configured, PLC in the Stop mode 2-14

57 2. Preparing for commissioning Bus node configured PLC in the Run mode LED indicator [MS] Status and significance Module status (MS) error free Lights up green [PS] Lights up green [NS] Lights up green [PL] Power supply (Power System, PS) is OK Operating voltage present (in the approved range) Network status (NS) error free ( online operating status) Communication with the network and PLC OK Load voltage present (in the approved range) 1) Lights up green [TP1], [TP2] Lights up green Device is correctly connected to the bus node Internal communication between bus node and device 1 or device 2 is error free Operating and load voltage present (in the approved range) 1) 1) Display dependent on monitoring and signal from the connected device. Tab. 2/6: Status LEDs after switch-on bus node configured, PLC in the Run mode 2-15

58 2. Preparing for commissioning 2.4 Participants in the network When using the CPX terminal as a new network participant for the first time, the configuration program is to be informed of certain network properties. These network properties are integrated into the participant properties Participant properties (EDS file) The participant properties are predominantly managed by the configuration program in a list or library, e.g. EDS file (Electronic Data Sheet). The following options are available for expanding an EDS library: Install EDS files Enter participant properties manually Import participant properties As soon as the CPX terminal has been registered as a potential network participant, it can be added to a network. 2-16

59 Commissioning Chapter 3 Commissioning 3-1

60 3. Commissioning Contents 3. Commissioning Configuration Configuration with EDS file Configuration with Generic Ethernet Module Configuration with CPX-FMT Configuration in the Remote Controller operating mode Setting up a Listen only connection Parameterisation Parameterisation during switch-on [system start] Methods of parameterisation Parameterisation via configuration data Parameterisation with the control device CPX-MMI Parameterisation in the PLC user program Parameterisation using CPX-FMT and system start with saved parameters Behaviour of the outputs in the Fail safe mode or Idle mode Web server Checklist for commissioning a CPX terminal Replacing the bus node

61 3. Commissioning 3.1 Configuration A CPX terminal with bus node CPX-FB36 can be configured using various methods. Method Description Advantages Disadvantages Configuration with EDS file ( 3.1.1) Installation of participant properties for the CPX terminal in the Studio 5000 configuration program. With the exception of the I/O data length, the entire configuration is transferred from the EDS file. Not available with all EtherNet/IP masters. Parameterisation is saved locally in the CPX terminal and is lost if the terminal is replaced. 1) Configuration with Generic Ethernet Module ( 3.1.2) Creation of a new participant and manual configuration in the Studio 5000 configuration program. Works with all versions All settings must be entered manually. Configuration with CPX-FMT ( 3.1.3) Export of the CPX terminal settings by CPX- FMT and import of the settings to the Studio 5000 configuration program. Transfer of the existing configuration of the participant and parameterisation of the CPX terminal. Tab. 3/1: Configuration methods 3-3

62 3. Commissioning Configuration with EDS file This section describes the configuration of the bus node as participant in a controller from Allen-Bradley with the help of the Studio 5000 software (V ) from Rockwell Automation using an equipment description file (EDS file) from Festo. The fundamental aspects of this description also apply for other control systems. Obtaining EDS files Use one of the following EDS files for the CPX terminal with CPX-FB36. File type File name Language Description EDS cpx_fb36.eds English Provides the communication adapter in the configuration program. cpx_fb36rc.eds English File with information for the Remote Controller operating mode. ICO cpx_fb36.ico Icon file for representing the CPX terminal or mode in the configuration program. Tab. 3/2: Device description files for CPX-FB36 The current device description file is available on the Festo Support Portal ( 3-4

63 3. Commissioning Registering the EDS file 1. Start Studio 5000 software. 2. Start EDS Wizard: [Tools], [EDS Hardware Installation Tool] Fig. 3/1: Starting EDS Wizard 3. In the Rockwell Automation's EDS Wizard dialogue, select the option Register an EDS file(s) and confirm it with the Next > button. Fig. 3/2: EDS Wizard Options 3-5

64 3. Commissioning 4. Select one of the following options: Register a single file Register a directory of EDS files 5. Actuate Browse button and select EDS file from the corresponsing directory. Fig. 3/3: EDS Wizard with selected EDS file 6. Confirm selection with the Next > button. The procedure for registering the bus node is complete. 3-6

65 3. Commissioning Integrate participants into the project and configure them Configuration of the bus node can only take place if there is no online connection to the controller. 1. Terminate an existing online connection to the higher-order controller: [Communications], [Go Offline] 2. Open Select Module Type dialogue: In the Controller Organizer window in the I/O Configuration directory, click on Ethernet with the right mouse button and select New Module in the context menu. Fig. 3/4: Context menu for New Module 3-7

66 3. Commissioning 3. In the Catalogue tab, select the module with the description CPX-FB36 Ethernet/IP 2-Port Remote I/O from the table. Fig. 3/5: Integrating bus node in the project as a participant 4. Confirm selection with the Create button. This opens the dialogue New Module for configuration of the new participant ( Fig. 3/6). Fig. 3/6: Configuring a participant 3-8

67 3. Commissioning 5. Enter a name for the bus node. 6. Enter IP address of the bus node. 7. Open the Module Definition dialogue and click on the Change button. Add screenshot of the dialogue Module Definition Fig. 3/7: Enter I/O data length 8. Enter I/O data length (number of inputs and outputs) of the CPX terminal. This value can either be calculated or retrieved using CPX FMT or a web server. 9. Confirm entries with the OK button. 10. Close the Module Definition dialogue. The bus node appears as a newly integrated participant in the Controller Organizer window in the I/O Configuration/ Ethernet directory. 3-9

68 3. Commissioning Changing configuration of the participant Configuration of the bus node can only take place if there is no online connection to the controller. 1. Terminate an existing online connection to the higher-order controller: [Communications], [Go Offline] 2. Open Select Module Type dialogue: In the Controller Organizer window in the I/O Configuration/Ethernet directory, click on the corresponding module with the right mouse button and select Properties in the context menu. Fig. 3/8: Context menu for Properties 3. Change configuration of the participant through the input fields and confirm with the OK button. 3-10

69 3. Commissioning Configuration with Generic Ethernet Module This section describes the manual configuration of the bus node as participant in a a controller from Allen-Bradley with the help of the Studio 5000 software (V ) from Rockwell Automation. The fundamental aspects of this description also apply for other control systems. Integrate participants into the project and configure them Configuration of the bus node can only take place if there is no online connection to the controller. 1. Terminate an existing online connection to the higher-order controller: [Communications], [Go Offline] 2. Open Select Module Type dialogue: In the Controller Organizer window in the I/O Configuration directory, click on Ethernet with the right mouse button and select New Module in the context menu ( Fig. 3/4). 3. In the Catalogue tab, select the module with the description Generic Ethernet Module from the table. Fig. 3/9: Integrating a bus node as a Generic Ethernet Module 3-11

70 3. Commissioning 4. Confirm selection with the Create button. This opens the dialogue Module Properties for configuration of the module as participant ( Fig. 3/10). Fig. 3/10: Configuring a participant 5. Enter a name for the bus node. 6. Select data format (Data - SINT or Data - INT) in the Comm Format list field. 7. Enter IP address of the bus node. 8. Enter values for Assembly Instance dependent on the selected data format ( Tab. 3/3). Data format Data SINT Data INT Input Output Configuration Tab. 3/3: Input values for Assembly Instance 9. Enter values for Size dependent on the selected operating mode ( Tab. 3/4). 3-12

71 3. Commissioning Operating mode Remote I/O Values Input and output : Number of assigned inputs and outputs of the CPX terminal: for data format SINT: in bytes for data format INT: in words The entry Size = 0 for inputs and outputs is not permissible in the Remote I/O operating mode. Configuration Number of memory slots occupied by CPX parameters or 0 (standard setting) 1) Remote controller Input and output : Set data field size ( Tab. 1/3): for data format SINT: in bytes for data format INT: in words Configuration 0 (standard setting) 1) 1) Configuration Assembly not used Tab. 3/4: Input values for Size When using a CPX terminal without inputs: Activate status bits via DIL switch 2 ( Tab. 1/3). The following settings then apply for the input data ( Input ): for SINT format: Size = 2 for INT format: Size = Confirm entries with the OK button. 11. Close the Module Properties dialogue. The bus node appears as a newly integrated participant in the Controller Organizer window in the I/O Configuration/Ethernet directory. 3-13

72 3. Commissioning Using participant properties Use the following data in the higher-order controller ( Tab. 3/5). Characteristic Vendor Name Description Festo Corporation Vendor ID 26 = 1A h Device Type 12 = 0C h Product code (dependent on the operating mode) Remote I/O Remote controller = 36CA h = 36CB h Major revision 1 Input size / Output size Dependent on CPX expansion Assembly instance Input Output Configuration SINT format INT format Product Name CPX-FB36 Remote IO CPX-FB36 Remote controller Extended EtherNet/IP participant properties Min. bus cycle time (RPI) Request Packet Interval Connections Total of all connections Exclusive owner Input only Listen only 1 ms Max. 32 Max. 1 Max. 32 Max. 31 1) 1) Only with simultaneous connection Exclusive Owner or Input only Tab. 3/5: Participant features 3-14

73 3. Commissioning Changing configuration of the participant Configuration of the bus node can only take place if there is no online connection to the controller. 1. Terminate an existing online connection to the higher-order controller: [Communications], [Go Offline] 2. Open Select Module Type dialogue: In the Controller Organizer window in the I/O Configuration/Ethernet directory, click on the corresponding module with the right mouse button and select Properties in the context menu. Fig. 3/11: Context menu for Properties (Generic) 3. Change configuration of the participant through the input fields and confirm with the OK button. 3-15

74 3. Commissioning Configuration with CPX-FMT With the Festo Maintenance Tool software (CPX-FMT), it is possible to export the configuration and complete parameterisation of a CPX terminal to a file and then import the file into the controller as a project. This section describes the transmission of the configuration file to a controller from Allen-Bradley with the help of the Studio 5000 software (V ) from Rockwell Automation. The fundamental aspects of this description also apply for other control systems. Exporting a configuration from CPX-FMT The Festo Maintenance Tool (CPX-FMT) software is available in the Festo Support Portal ( 1. Start CPX-FMT software. 2. Make sure that an Ethernet connection exists between CPX-FMT and the CPX terminal. 3. Activate the online function to transfer the current configuration of the bus node to the PC. 4. Change the configuration and parameterisation for the CPX terminal with CPX-FB36, if necessary. The CPX terminal can also be configured offline. Changes are also possible after importing the project in the Studio5000 software. 3-16

75 3. Commissioning 5. Open dialogue for export of the configuration: [File], [Export], [RSLogix (.L5K)]. Fig. 3/12: Exporting a configuration for Studio Select and save a directory and name to save the L5K file. Importing configuration 1. Start Studio 5000 software. 2. Open saved L5K file: [File], [Open] and select the saved L5K file. 3. Confirm selection with the Open button. 4. Select the directory and name for the file to be imported. 5. Confirm selection with the Import button. The L5K file is imported into a new project (.ACD) as an Ethernet module. 3-17

76 3. Commissioning Integrating the CPX terminal into an existing project The CPX terminal configured and parameterised with the Festo Maintenance Tool software appears in the Studio 5000 software as an Ethernet module. To integrate this module into an existing project: 1. In the Controller Organizer window in the I/O Configuration directory, right click on the Ethernet module and select Copy in the context menu. Fig. 3/13: Copying the Ethernet module 3-18

77 3. Commissioning 2. Open the project in which the imported Ethernet module is to be added. 3. In the Controller Organizer window in the I/O Configuration directory, right click on Ethernet and select Paste in the context menu. Fig. 3/14: Inserting an Ethernet module The project has now take over all required settings of the CPX terminal. This includes, among other things, I/O data lengths, the IP configuration, as well as all module and system parameters. Configuration and parameterisation are hereby completed. Changes to the parameterisation of the modules and valve terminals used in the CPX terminal are made through the Studio 5000 software. 3-19

78 3. Commissioning Configuration in the Remote Controller operating mode When a control block CPX-FEC or CPX-CEC is used in the CPX terminal, the bus node must be used in the Remote Controller operating mode. In principle, the bus node is configured in the same manner as in the Remote I/O operating mode, but with different I/O data lengths. The bus node then occupies 8 or 16 input bytes and 8 or 16 output bytes, dependent on the setting of the DIL switch 2.2 ( Tab. 1/3). These inputs and outputs are available to the control program of the control block. To use the Remote Controller operating mode: 1. Set Remote Controller operating mode through the DIL switch 1.1 ( Tab. 1/1). 2. Set the network protocol through the DIL switch 1.2 ( Tab. 1/2). 3. Set the required data field size through the DIL switch2.1 ( Tab. 1/3). The bus node is thus configured in the Remote Controller operating mode. 3-20

79 3. Commissioning Setting up a Listen only connection When the participant properties have been configured (e.g. by installation of an EDS file), the following steps are required for configuration. 1. Install CPX terminal and set IP addressing ( 1.3.5). 2. Make connection to the bus node. In the Studio 5000 software, use the Generic Ethernet Device profile for this purpose ( 3.1.2). 3. Open the Module Properties dialogue. 4. Select the data format DATA - SINT from the Comm Format list field ( Fig. 3/10). 5. Enter the following values in the Connection Parameters field: Connection Parameters Assembly Instance Size Input 101 Number of inputs set on the bus node Output 1 0 Configuration 102 ( Configuration Assembly ) 0 Tab. 3/6: Properties for Connection parameters 6. Enter IP address of the bus node. 3-21

80 3. Commissioning 3.2 Parameterisation Warning Uncontrolled movements of the actuators, undefined switching states Injury to people, damage to the machine and system During the parameterisation process, make sure that nobody is within the sphere of influence of moving parts of your system. The CPX terminal is supplied from the factory with preset parameters. These parameters are saved in the bus node. These parameters can be used to largely adapt the behaviour of the CPX terminal to the relevant application. A distinction is made between the following variants: System parameters, e.g. setting reaction times, switching off error messages Module parameters (module- and channel-specific), e.g. diagnostic settings, settings for error handling, settings for debounce times of inputs, settings for forcing Parameters of the diagnostic memory A detailed description of the individual parameters as well as basic principles of application can be found in the CPX system description ( P.BE-CPX-SYS-...). The module parameters can be found in the descriptions for the modules, e.g. description of the CPX pneumatic interfaces and CPX I/O modules ( P.BE-CPX-EA-...). 3-22

81 3. Commissioning Parameterisation during switch-on [system start] Parameterisation during system start of the CPX terminal is initially dependent on the setting of the parameter [system start]. This parameter establishes whether the default parameters or the parameters saved by the user in the bus node are used when switching on the CPX terminal. The parameterisation is loaded again after every interruption of the power supply or the network connection. An exchange of individual CPX modules is therefore possible, for example, without the need for re-parameterisation. Sequence of parameterisation when the CPX terminal is switched on System start with standard parameters ( default parameters ) 1. The controller transmits the parameterisation that is saved in the controller to the bus node. 2. The bus node distributes this parameterisation to the individual modules. System start with saved parameters 1. The bus node distributes the parameterisation that is saved in the bus node to the individual modules. The parameterisation saved in the bus node can be overwritten accidentally by the controller. Prevent accidental overwriting of the saved parameterisation by changing the Configuration connection parameter using the Studio 5000 software. 3-23

82 3. Commissioning To change the Configuration connection parameter with the Studio 5000 software: 1. Terminate an existing online connection to the higher-order controller: [Communications], [Go Offline] 2. Open Module Properties dialogue: Double-click on Ethernet in the Controller Organizer window in the I/O Configuration directory. 1 1 Assemblylnstance connection parameter for Configuration Fig. 3/15: Module Properties dialogue 3. Enter the value Assembly Instance = 0 for Configuration in the Connection Parameters area. 4. Close the Module Properties dialogue with the Finish >> button. If the Modify (M) LED on the bus node lights up permanently after system start-up, [System start with saved parameters] is set. 3-24