Accessories EtherNet/IP™ 13443009 Ä.
Contents ________________________________________________________________ 1 1.1 1.2 1.3 1.
Contents ________________________________________________________________ 7 7.1 7.2 7.
Contents ________________________________________________________________ 14 Implemented CIP™ objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14.1 General CIP objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14.1.1 Identity Object (1 / 0x01) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14.1.2 Message Router Object (2 / 0x02) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14.1.
1 About this documentation ________________________________________________________________ 1 About this documentation Contents This documentation only contains descriptions of the E84AYCEO (EtherNet/IP™) communication module. Note! This documentation supplements the mounting instructions supplied with the communication module and the hardware manual "Inverter Drives 8400".
1 About this documentation ________________________________________________________________ Target group This documentation is intended for all persons who plan, install, commission and maintain the networking and remote servicing of a machine. Tip! Current documentation and software updates with regard to Lenze products can be found in the download area at: www.Lenze.
1 About this documentation 1.1 Document history ________________________________________________________________ 1.1 Document history Version Description 1.0 08/2012 TD17 2.0 12/2012 TD17 3.0 10/2013 TD17 First edition • Revision for software version 01.
1 About this documentation 1.2 Conventions used ________________________________________________________________ 1.2 Conventions used This documentation uses the following conventions to distinguish between different types of information: Type of information Writing Examples/notes Spelling of numbers Decimal separator Point Hexadecimal 0x[0 ... 9, A ... F] Binary • Nibble In inverted commas Point The decimal point is always used. For example: 1234.
1 About this documentation 1.3 Terminology used ________________________________________________________________ 1.3 Terminology used Term Meaning ACD Address Conflict Detection Adapter EtherNet/IP slave Inverter / Drive Lenze inverters of the "Inverter Drives 8400" series Standard device ARP Address Resolution Protocol Use BOOTP Bootstrap Protocol Code Parameter which serves to parameterise and monitor the drive. In normal usage, the term is usually referred to as "Index".
1 About this documentation 1.4 Definition of the notes used ________________________________________________________________ 1.
2 Safety instructions 2.1 General safety and application notes ________________________________________________________________ 2 Safety instructions Note! It is absolutely vital that the stated safety measures are implemented in order to prevent serious injury to persons and damage to material assets. Always keep this documentation to hand in the vicinity of the product during operation. 2.
2 Safety instructions 2.2 Device and application-specific safety instructions ________________________________________________________________ 2.2 Device and application-specific safety instructions • During operation, the communication module must be securely connected to the standard device. • With external voltage supply, always use a separate power supply unit, safely separated to EN 61800-5-1 in every control cabinet (SELV/PELV). • Only use cables corresponding to the given specifications.
3 Product description 3.1 Application as directed ________________________________________________________________ 3 Product description 3.1 Application as directed The communication module ... • is an accessory module that can be used in conjunction with the following standard devices: Product series Type designation From software version Inverter Drives 8400 StateLine E84AVSCxxxxx 11.00 Inverter Drives 8400 HighLine E84AVHCxxxxx 11.00 Inverter Drives 8400 TopLine E84AVTCxxxxx 02.
3 Product description 3.3 Product features ________________________________________________________________ 3.3 Product features • Interface module for the EtherNet/IP communication system, for attachment to the expansion slots of Inverter Drives 8400 • The communication module can either be supplied internally by the standard device or externally by a separate voltage source.
3 Product description 3.4 Connections and interfaces ________________________________________________________________ 3.
4 Technical data 4.1 General data and operating conditions of the EtherNet/IP ________________________________________________________________ 4 Technical data 4.1 General data and operating conditions of the EtherNet/IP Range Values Order designation E84AYCEO Communication profile EtherNet/IP Communication medium S/FTP (Screened Foiled Twisted Pair), ISO/IEC 11801 or EN 50173, CAT 5e Interface for communication RJ45 Standard Ethernet (according to IEEE 802.
4 Technical data 4.2 Protective insulation ________________________________________________________________ 4.2 Protective insulation Danger! Dangerous voltage If the Inverter Drives 8400 are operated on a phase-earthed mains with a rated mains voltage of 400 V, external measures need to be implemented in order to ensure protection against accidental contact.
4 Technical data 4.2 Protective insulation ________________________________________________________________ The following illustration ... • shows the arrangement of the terminal strips and the separate potential areas of the Inverter Drive 8400. • serves to determine the decisive protective insulation between two terminals located in differently insulated separate potential areas. Bus Ext.
4 Technical data 4.2 Protective insulation ________________________________________________________________ Example Which type of protective insulation is used between the bus terminal of the device module in slot MCI and the X100 mains terminal? The separate potential area with the better protective insulation is decisive. • The separate potential area of the bus terminal of the device module has a "functional insulation".
4 Technical data 4.3 Protocol data ________________________________________________________________ 4.3 Protocol data Range Values I/O data words 1 ... 16 words (max. 32 bytes, 16 bits/word) Supported CIP services 4.4 • Get_Attributes_All • Get_Attribute_Single • Set_Attribute_Single • Reset (types ’0’ and ’1’ only) • Forward_Open • Forward_Close • Get_Member Communication time The communication time is the time between the start of a request and the arrival of the corresponding response.
4 Technical data 4.5 Internal switch latency ________________________________________________________________ 4.5 Internal switch latency The integrated 2-port switch causes runtime delays. For "store-and-forward" and 100 Mbps, these runtime delays can be calculated as follows. Runtime delay for an output data packet of the scanners incl.
4 Technical data 4.6 Dimensions ________________________________________________________________ 4.6 Dimensions E84AYCEO005_1 [4-2] Dimensions Type E84AYCEO 22 Dimensions [mm] a b c c1 67 50 57 8 Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.
5 Installation ________________________________________________________________ 5 Installation Stop! Electrostatic discharge Electronic components within the communication module can be damaged or destroyed by electrostatic discharge. Possible consequences: • The communication module is defective. • Fieldbus communication is not possible or faulty. Protective measures Before touching the module, be sure that you are free of electrostatic charge.
5 Installation 5.1 Mechanical installation ________________________________________________________________ 5.1 Mechanical installation The communication module can be plugged in or unplugged from the MCI slot when the drive is switched on. When the module is plugged in, it is detected automatically, and a function and version plausibility check is executed. 5.1.1 Mounting for standard devices of 0.25 kW and 0.37 kW E84YCPM002D [5-1] Mounting for standard devices of 0.25 kW and 0.
5 Installation 5.1 Mechanical installation ________________________________________________________________ 5.1.2 Mounting for standard devices of 0.55 kW or more E84YCPM002A [5-2] Mounting for standard devices of 0.55 kW or more Mounting steps 1. Slightly impress the pressure surface of the top side of the MCI slot cover of the standard device (1). 2. Tilt the cover forward and remove it from the standard device (2). 3.
5 Installation 5.1 Mechanical installation ________________________________________________________________ 5.1.3 Replacing the communication module E84YCPM002B [5-3] Replacing the communication module Mounting steps 1. Loosen the securing screw for the communication module at the standard device (1). 2. Pull the communication module out of the MCI slot of the standard device (2). 3. Insert the new communication module into the MCI slot of the standard device (3). 4.
5 Installation 5.2 Electrical installation ________________________________________________________________ 5.2 Electrical installation 5.2.1 Documentation for the standard device, host, system/machine Observe the notes and wiring instructions contained in this documentation. Wiring according to EMC guidelines In typical systems, standard shielding is sufficient for Ethernet cables.
5 Installation 5.2 Electrical installation ________________________________________________________________ • Tree via switches S SW SW SW E94AYCEO006 [5-6] Tree topology (S = scanner, SW = switch) • Switch / switch SW SW SW E94AYCEO007 [5-7] 28 Switch / switch topology (SW = switch) Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.
5 Installation 5.2 Electrical installation ________________________________________________________________ 5.2.3 EtherNet/IP connection A connection to the EtherNet/IP network is established via RJ45 sockets X259 and X260. E84AYCEO005_2 [5-8] EtherNet/IP terminals X259 and X260 For connection of the communication module to the EtherNet/IP fieldbus, a standard Ethernet patch cable is suitable.
5 Installation 5.2 Electrical installation ________________________________________________________________ Pin assignment of the RJ45 sockets RJ45 socket E94AYCXX004C Pin Signal 1 Tx + 2 Tx - 3 Rx + 4 - 5 - 6 Rx - 7 - 8 - Note! Dependent on the configuration of the Ethernet port of the device to be connected, we recommend the use of a cross-over cable. Tip! The EtherNet/IP interfaces feature an auto-MDIX function.
5 Installation 5.2 Electrical installation ________________________________________________________________ 5.2.4 Ethernet cable specification Note! Only use cables that meet the listed specifications. Ethernet cable specification Ethernet standard Standard Ethernet (in accordance with IEEE 802.3), 100Base-TX (Fast Ethernet) Cable type S/FTP (Screened Foiled Twisted Pair), ISO/IEC 11801 or EN 50173, CAT 5e Damping 23.
5 Installation 5.2 Electrical installation ________________________________________________________________ Colour code of the Ethernet cable Note! Wiring and colour code are standardised in EIA/TIA 568A/568B. In accordance with the industrial standard, the use of 4-pin Ethernet cables is permissible. The cable type only connects the assigned pins 1, 2, 3 and 6 to one another.
5 Installation 5.2 Electrical installation ________________________________________________________________ 5.2.5 External voltage supply The communication module can be externally supplied with voltage via separate supply cables at the 2-pin plug connector X258. Note! With external voltage supply, always use a separate power supply unit, safely separated to EN 61800-5-1 in every control cabinet (SELV/PELV).
5 Installation 5.2 Electrical installation ________________________________________________________________ Terminal data Range Values Electrical connection 2-pin plug connector with spring connection Possible connections Rigid: 0.2 ... 1.5 mm2 (AWG 24 ... 16) Flexible: Without wire end ferrule 0.2 ... 1.5 mm2 (AWG 24 ... 16) With wire end ferrule, without plastic sleeve 0.2 ... 1.5 mm2 (AWG 24 ... 16) With wire end ferrule, with plastic sleeve 0.2 ... 1.5 mm2 (AWG 24 ...
6 Commissioning 6.1 Before initial switch-on ________________________________________________________________ 6 Commissioning During commissioning, plant-specific data such as motor parameters, operating parameters, responses, and parameters for fieldbus communication are defined for the inverter. Lenze devices use codes for this purpose. The codes of the inverter and for communication are saved to the memory module in a non-volatile data set.
6 Commissioning 6.2 Configuring the host system (scanner) ________________________________________________________________ 6.2 Configuring the host system (scanner) To be able to communicate with the communication module, the host (scanner) must be configured first. The configuration of EtherNet/IP networks always requires an EtherNet/IP configuration software (e.g. »RSLogix 5000« from Rockwell) for the host system (scanner).
6 Commissioning 6.2 Configuring the host system (scanner) ________________________________________________________________ 6.2.1 EDS files Depending on the EtherNet/IP scanner configuration software, the EDS files (Electronic Data Sheet) may be used for the configuration of the network profile, the communication with the participating devices and the automatic generation of tags. For this purpose, the EDS files have to be imported into the controller project of the EtherNet/IP configuration software.
6 Commissioning 6.2 Configuring the host system (scanner) ________________________________________________________________ 6.2.2 Example: IP configuration of the Allen-Bradley 1769-L32E CompactLogix controller In this example, the Allen-Bradley CompactLogix control unit 1769-L32E with integrated EtherNet/ IP interface is used for communication with the Inverter Drives 8400. The »RSLogix 5000« programming software from Rockwell is used for the configuration.
6 Commissioning 6.2 Configuring the host system (scanner) ________________________________________________________________ 5. Go to the Port Configuration tab and enter the IP configuration, BOOTP setting, Ethernet baud rate and duplex mode. 6. Then click OK. • Now, the scanner is configured for the EtherNet/IP network.
6 Commissioning 6.3 Setting node addresses by means of rotary coding switches ________________________________________________________________ 6.3 Setting node addresses by means of rotary coding switches Note! • Each network node address must only be used once. • Adjustable address range: 1 ... 254 You can set the node address (IP address) by means of the two "IP ADR" rotary coding switches located on the front.
6 Commissioning 6.3 Setting node addresses by means of rotary coding switches ________________________________________________________________ Possible settings of the rotary coding switches Position of the rotary coding switches 0 × 16 0 0 ... 15 1 ...
6 Commissioning 6.4 Setting the IP configuration of the Inverter Drive 8400 ________________________________________________________________ 6.4 Setting the IP configuration of the Inverter Drive 8400 IP configuration is necessary in order to assign an address to the Inverter Drive 8400 so that communication between the PC/»Engineer« or the scanner and the drive is possible via EtherNet/ IP. For this purpose, an IP address, subnet mask and gateway address have to be assigned.
6 Commissioning 6.4 Setting the IP configuration of the Inverter Drive 8400 ________________________________________________________________ 6.4.1 Setting via the EtherNet/IP configurator of the »Engineer« Note! • Changes in the IP parameters will become effective immediately. • An already existing IP connection to the Inverter Drive 8400 is interrupted. How to set the IP parameters via the EtherNet/IP configurator: 1.
6 Commissioning 6.4 Setting the IP configuration of the Inverter Drive 8400 ________________________________________________________________ 2. A double-click on a EtherNet/IP node opens the "Configure nodes" dialog window. Here you can set the IP parameters. 3. Click on Transferred. • The IP configuration is transferred to the corresponding EtherNet/IP node. • The communication module carries out a stack reset.
6 Commissioning 6.4 Setting the IP configuration of the Inverter Drive 8400 ________________________________________________________________ 6.4.2 Setting via codes in the »Engineer« You can also set the IP parameters manually in the »Engineer« under the Settings tab. The values will be transferred to the corresponding codes. Settings / Display Description Rotary coding switch Display of the value set by means of the rotary coding switches (C13920).
6 Commissioning 6.4 Setting the IP configuration of the Inverter Drive 8400 ________________________________________________________________ IP address The IP address is set/changed in C13000. The IP address currently used is displayed in C13010/1...4. Example: Display of the IP address 192.168.124.16 Code C13010/1 C13010/2 C13010/3 C13010/4 Value 192 168 124 16 Subnet mask The subnet mask indicates which part of the IP address is evaluated as net ID or host ID.
6 Commissioning 6.4 Setting the IP configuration of the Inverter Drive 8400 ________________________________________________________________ 6.4.3 Setting via a BOOTP/DHCP server DHCP is the acronym for "Dynamic Host Configuration Protocol". This protocol is defined in RFC 2131 and is a compatible advancement of the "Bootstrap Protocol" (BOOTP) according to RFC 951. Both protocols enable network nodes to query information about the network configuration (e.g.
6 Commissioning 6.4 Setting the IP configuration of the Inverter Drive 8400 ________________________________________________________________ 6.4.5 Setting the multicast configuration Several scanners ("Listen only" or "Input only" connections) can access multicast telegrams which are sent by drives. Settings for multicast configuration have to be carried out as well in the EtherNet/IP configuration software (z. B. »RSLogix 5000« from Rockwell).
6 Commissioning 6.5 Establishing an online connection via EtherNet/IP with the Lenze »Engineer« ________________________________________________________________ 6.5 Establishing an online connection via EtherNet/IP with the Lenze »Engineer« [6-2] Note! • In order to ensure perfect operation of cyclic EtherNet/IP communication, online access with the »Engineer« should be executed via an IEEE 802.1Q-capable switch. • The IEEE 802.
6 Commissioning 6.5 Establishing an online connection via EtherNet/IP with the Lenze »Engineer« ________________________________________________________________ In the »Engineer«, you can use the Online Set communication path and go online menu command to select the EtherNet/IP communication path. The previously configured EtherNet/IP nodes are shown in the "Communication path" dialog window: If the device access path is not configured correctly, the display field can be entered manually here.
6 Commissioning 6.6 Initial switch-on ________________________________________________________________ 6.6 Initial switch-on Documentation for the Inverter Drive 8400 Note! Observe the safety instructions and information on residual hazards. Establishing communication In order to establish communication via an externally supplied communication module, the standard device must be switched on as well.
7 Data transfer ________________________________________________________________ 7 Data transfer EtherNet/IP uses CIP™ (Common Industrial Protocol) for the data exchange between devices via an Ethernet network – just like the closely related bus systems DeviceNet and ControlNet. Lenze implements the CIP following the ODVA standard (Open DeviceNet Vendor Association, www.odva.
7 Data transfer 7.1 Communication channels ________________________________________________________________ 7.1 Communication channels Note! The terms "input" and "output" refer to the point of view of the scanner: • Input data is produced by the adapter and consumed by the scanner. • Output data is produced by the scanner and consumed by the adapter. EtherNet/IP transmits parameter data and I/O data between the host system (scanner) and the drives (adapters) connected to the fieldbus.
7 Data transfer 7.2 Telegram types ________________________________________________________________ 7.2 Telegram types The "implicit message" and "explicit message" telegram types are transmitted between the host system (scanner) and the drive (adapter). Implicit messages (I/O data transfer) "Implicit messages" are transmitted or received according to the producer/consumer principle. There is one transmitter and no receiver or an optional number of receivers.
7 Data transfer 7.3 EtherNet/IP state diagram ________________________________________________________________ 7.3 EtherNet/IP state diagram [7-1] EtherNet/IP state diagram The current EtherNet/IP device state is ... • output via code C13861; • output in the Identity Object (1 / 0x01) ( 126) via instance attributes 5 and 8; • indicated via the MS LED (see LED status displays ( 89)). Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.
8 I/O data transfer (implicit messages) ________________________________________________________________ 8 I/O data transfer (implicit messages) To exchange I/O data (implicit messages) between the host system (scanner) and the drive (adapter), you have to ...
8 I/O data transfer (implicit messages) 8.1 I/O data mapping ________________________________________________________________ 8.1 I/O data mapping I/O data transfer takes place via the MCI interface. • Access to the I/O data takes place via port blocks LP_MciIn and LP_MciOut. • The LP_MciIn port block maps the received data objects. • The LP_MciOut port block maps the data objects to be sent. • Up to 16 data words (32 bytes) per direction can be exchanged.
8 I/O data transfer (implicit messages) 8.2 Technology applications (TA) / drive profiles ________________________________________________________________ 8.2 Technology applications (TA) / drive profiles The Inverter Drives 8400 is provided with various drive profiles. They define a standardised/ individual control and status word assignment and the standardisation of setpoints and actual value scalings.
8 I/O data transfer (implicit messages) 8.2 Technology applications (TA) / drive profiles ________________________________________________________________ 8.2.2 "AC Drive Profile" application From inverter drive version V13.00 and communication module version V01.02, the EtherNet/IPspecific "AC Drive Profile" is supported. The standard device code C00005 = "1100: AC Drive Profile" serves to select the "AC Drive Profile" application. The "AC Drive Profile" contains ...
8 I/O data transfer (implicit messages) 8.3 I/O assemblies ________________________________________________________________ 8.3 I/O assemblies Note! The terms "input" and "output" refer to the point of view of the scanner: • Assembly input objects (input) are sent from the adapter to the scanner. • Assembly output objects (output) are sent from the scanner to the adapter. The length of the I/O data must correspond with the respective resulting length of the mapped ports (I/O data mapping ( 57)).
8 I/O data transfer (implicit messages) 8.3 I/O assemblies ________________________________________________________________ Assembly output objects (scanner Adapter) Assembly output objects are assumed to have a 4-byte header (32-bit "run/idle header"). When mapping the assemblies, this header will automatically be added to the data stream by most AllenBradley PLC/SLC equipment. If your PLC does not support this header (like the Rockwell PLCs do), add a preceding 32-bit header to the output image.
8 I/O data transfer (implicit messages) 8.4 I/O configuration in the »Engineer« ________________________________________________________________ 8.4 I/O configuration in the »Engineer« 8.4.1 Lenze technology application / configuring user-definable parameter sets How to configure the Lenze technology applications / user-definable parameter sets in the »Engineer«: 1. Select the application (C00005 = 1000) in the Application parameters tab.
8 I/O data transfer (implicit messages) 8.4 I/O configuration in the »Engineer« ________________________________________________________________ 3. On the Ports tab, the port blocks shown. MCI_IN and MCI_OUT for the I/O data objects are • By clicking the required port, the preconfigured signal combination can be obtained from the application variables. • If you want to complement or change the signal combination, click the Variable … button.
8 I/O data transfer (implicit messages) 8.4 I/O configuration in the »Engineer« ________________________________________________________________ 4. In the "Edit port" dialog window, you can assign signals to the I/O data words via the button. Select the signals and confirm the selection with OK. 64 Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.
8 I/O data transfer (implicit messages) 8.4 I/O configuration in the »Engineer« ________________________________________________________________ For some data words, you can also assign signals to the individual bits via the buttons. Select the signals and then confirm the selection with OK. and 5. Use the standard device code C00002 to execute the command "11: Save all parameter sets". The changed settings are activated and saved with mains failure protection.
8 I/O data transfer (implicit messages) 8.4 I/O configuration in the »Engineer« ________________________________________________________________ Preconfigured signal combination in the "FB Editor" By setting the standard device code C00007 = "40: MCI" , the preconfigured signal combination is activated. The function block editor (FB Editor) is used to display the port blocks LP_MciIn and LP_MciOut with the preconfigured signal combinations. Here, you can also complement or change the signal combination.
8 I/O data transfer (implicit messages) 8.4 I/O configuration in the »Engineer« ________________________________________________________________ 8.4.2 Configuring "AC Drive Profile" application How to configure the "AC Drive Profile" application in the »Engineer«: 1. Select the "AC Drive Profile" application (C00005 = 1100) in the Application parameters tab. 2. Make the default setting of the I/O configuration. Select "MCI" control mode (C00007 = 40).
8 I/O data transfer (implicit messages) 8.5 I/O configuration with »RSLogix 5000« version 19 or lower ________________________________________________________________ 8.5 I/O configuration with »RSLogix 5000« version 19 or lower The following example describes the I/O configuration of the Allen-Bradley 1769-L32E CompactLogix controller using the Rockwell »RSLogix 5000« programming software up to version 19.
8 I/O data transfer (implicit messages) 8.5 I/O configuration with »RSLogix 5000« version 19 or lower ________________________________________________________________ 2. Right click on "Ethernet" and execute the "New Module ..." command from the context menu. 3. Open "Communications" and select "ETHERNET-MODULE | Generic Ethernet Module". 4. Confirm the selection with OK. Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.
8 I/O data transfer (implicit messages) 8.5 I/O configuration with »RSLogix 5000« version 19 or lower ________________________________________________________________ 5. Go to the "New Module" dialog window and define the properties of the newly added device . The terms "input" and "output" refer to the point of view of the scanner: • Assembly input objects (input) are sent from the adapter to the scanner. • Assembly output objects (output) are sent from the scanner to the adapter.
8 I/O data transfer (implicit messages) 8.5 I/O configuration with »RSLogix 5000« version 19 or lower ________________________________________________________________ Settings for an "AC Drive Profile" application: The assembly object instances "Input = 73" and "Output = 23" shown here exemplify the use of the AC Drive Profile "Extended Speed and Torque".
8 I/O data transfer (implicit messages) 8.5 I/O configuration with »RSLogix 5000« version 19 or lower ________________________________________________________________ 7. Under I/O Configuration in the configuration tree, right click "1769-L32E Ethernet Port LocalENB" and select "Properties". 8. Go to the Connection tab and set further properties. Required setting Setting Description Requested Packet Interval (RPI) Set RPI 4.0 ms.
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 8.6 I/O configuration with »RSLogix 5000« version 20 or higher The following example describes the I/O configuration of the Allen-Bradley 1769-L32E CompactLogix controller using the Rockwell »RSLogix 5000« programming software from version 20. From software version 20 onwards, EDS files ( 37) are used for the I/O configuration.
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 3. Right click on "Ethernet" and execute the "New Module ..." command from the context menu. 4. Go to the "Select Module Type" dialog box and select "E84AYCEO" on the Catalog tab. 5. Confirm the selection with Create. 74 Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 6. In the "New Module" dialog window, select the General tab and allocate a an unique name and IP address. Example settings: DNS is not supported; the host name merely describes the device. 7. Click the Change ... button. Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 8. Go to the "Module Definition" dialog window and make the connection settings. The terms "input" and "output" refer to the point of view of the scanner: • Assembly input objects (input) are sent from the adapter to the scanner. • Assembly output objects (output) are sent from the scanner to the adapter.
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ Settings for an "AC Drive Profile" application: • Select "AC Drive" connection. In the example, the AC Drive Profile "Exclusive Owner - AC Drive Ext. Speed & Torque" is used. • Set Data type = INT. The INT data type is exchanged via the ports MCI_IN and MCI_OUT of the Inverter Drives 8400.
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 10. Open the "New Module" dialog window, select the Connection tab and set further properties. "Name" displays the name of the connection set under 8.. The example shows an "Exclusive Owner - Custom" connection. According to this, the name of an "AC Drive Profile" connection may be displayed here too.
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 11. Complete the settings with OK. • The drive is inserted in the configuration tree under the • The corresponding tags are created in the "I/O Configuration". "Controller Tags". • The example shows the ...
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 12. Create an "alias tag". Example with the assembly object instance 23 (0x17): For a forward motion of a conveyor, bit ’0’ (Run Fwd) is to be referenced by byte ’0’.
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 13. Go to the "New Tag" dialog window and ... • assign a • Name for the tag (in the example: "Conveyor_1_RUN_FWD"); set Type = "Alias"; • select the Alias address which is to be referenced for the alias tag. (in the example: "MY_EIP8400_FROM_EDS:O1.Data(0).
8 I/O data transfer (implicit messages) 8.6 I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 14. Confirm the settings with the Create button. The alias tag "Conveyor_1_RUN_FWD" is created below the "Controller Tags": Name Value ... Force Mask ... [–] MY_EIP8400_FROM_EDS:O1 {. . .} Style ... ... {. . .} Data Type ... _024B:E84AYCE... [+] MY_EIP8400_FROM_EDS:O1.Data[1] 0 Decimal SINT [+] MY_EIP8400_FROM_EDS:O1.
8 I/O data transfer (implicit messages) 8.7 Saving the I/O configuration in »RSLogix 5000« ________________________________________________________________ 8.7 Saving the I/O configuration in »RSLogix 5000« After adding the scanner and the adapter to the I/O configuration, the configuration must be downloaded to the controller. The configuration file should also be saved on your computer. How to save the I/O configuration: 1. Select the menu command Communications Download.
9 Parameter data transfer (explicit messages) ________________________________________________________________ 9 Parameter data transfer (explicit messages) An "explicit message" is a logical instruction in the PLC program used for messaging. It can be used to read or write to either a parameter setting or the data of an assembly object.
9 Parameter data transfer (explicit messages) 9.1 Write parameters ________________________________________________________________ 9.
9 Parameter data transfer (explicit messages) 9.2 Read parameters ________________________________________________________________ 9.
9 Parameter data transfer (explicit messages) 9.2 Read parameters ________________________________________________________________ For every "explicit message", the path for sending the message via the Ethernet port of the PLC to the IP address of the drive needs to be set under the Communication tab. This path depends on the PLC used. If you need assistance with the setting of this path, please consult the PLC manufacturer.
10 Monitoring ________________________________________________________________ 10 Monitoring Fault with regard to EtherNet/IP communication You can set the reactions of the Inverter Drive 8400 to a fault in EtherNet/IP communication in »Engineer« by opening the Monitoring tab and making the appropriate settings. Settings Description Idle Mode The 32-bit real time header sent by the scanner is evaluated. Run/Idle Flag (Bit 0) = TRUE: • The scanner indicates the validity of the I/O data.
11 Diagnostics 11.1 LED status displays ________________________________________________________________ 11 Diagnostics The LEDs on the front of the communication module serve to diagnose faults. Moreover, the »Engineer« serves to show diagnostic information. 11.1 LED status displays Note! LED status displays for trouble-free operation: • The LEDs MS ( 90) and NS ( 91) light up permanently.
11 Diagnostics 11.1 LED status displays ________________________________________________________________ 11.1.1 Module status displays Module states are indicated by the ST, ER and DE LEDs. ST ER DE E84AYCEO007_a [11-1] LEDs ST, ER, DE LED Colour Status ST Green On Description The communication module is supplied with voltage and is connected to the standard device. Blinking 250 ms 250 ms The communication module is supplied with voltage, but is not connected to the standard device.
11 Diagnostics 11.1 LED status displays ________________________________________________________________ 11.1.2 CIP™ status displays CIP statuses are indicated by the MS and NS LEDs. MS NS E84AYCEO007_b [11-2] LEDs MS, NS Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.
11 Diagnostics 11.1 LED status displays ________________________________________________________________ LED MS Colour / status Green Red Off Off Off On Description CIP module status: "Nonexistent" The communication module is not being supplied with voltage. CIP module status: "Major Unrecoverable Fault" The communication module has a fault that cannot be rectified. The status is set if the pending status determining device error shows the "System fault" response.
11 Diagnostics 11.1 LED status displays ________________________________________________________________ LED NS Colour / status Green Red Off Off Off On Description CIP network status: "No IP Address" The communication module is not being supplied with voltage or has not been given an IP address. CIP network status: "Duplicate IP" The communication module is unable to gain access to the fieldbus (IP address conflict).
11 Diagnostics 11.1 LED status displays ________________________________________________________________ 11.1.3 Status indicators at the RJ45 sockets (X259, X260) The LEDs at RJ45 sockets X259 and X260 indicate the status of the Ethernet connection. Link Act Link Act E84YCEO003C [11-3] LEDs Link , Act LED Colour Status Link Green Off Description No Ethernet connection On There is a physical Ethernet connection.
11 Diagnostics 11.2 Diagnostics with the »Engineer« ________________________________________________________________ 11.2 Diagnostics with the »Engineer« In the »Engineer«, the Diagnostics tab displays various pieces of EtherNet/IP diagnostic information.
12 Error messages 12.1 Short overview of the EtherNet/IP error messages ________________________________________________________________ 12 Error messages This chapter supplements the error list in the software manual and in the »Engineer« online help system for the Inverter Drive 8400 by adding the EtherNet/IP error messages to the list. 12.
12 Error messages 12.2 Possible causes and remedies ________________________________________________________________ 12.2 Possible causes and remedies In this chapter, all EtherNet/IP error messages are listed in the numerical order of the error numbers. Possible causes and remedies as well as responses to the error messages are described in detail. EtherNet/IP: Exist. connect.
12 Error messages 12.2 Possible causes and remedies ________________________________________________________________ EtherNet/IP: Internal Error [0x01bc6011] Response (Lenze setting printed in bold) Setting: not possible None System fault Fault Trouble Quick stop by trouble Warning locked Warning Information Cause Remedy Communication module is defective. Send communication module with error description to Lenze.
12 Error messages 12.2 Possible causes and remedies ________________________________________________________________ EtherNet/IP: Invalid IP parameters [0x01bc6533] Response (Lenze setting printed in bold) Setting: not possible None System fault Fault Trouble Quick stop by trouble Warning locked Warning Information Cause Remedy One or more IP parameters are faulty. Check and correct IP configuration.
12 Error messages 12.2 Possible causes and remedies ________________________________________________________________ EtherNet/IP: Idle Mode [0x01bc8132] Response (Lenze setting printed in bold) Setting: C13880/1 None system fault Fault Trouble Quick stop by trouble Warning locked Warning Information Cause Remedy • Scanner has received an idle event. • The scanner is in the "PROG" mode. • In the "Scanner Command Register", the run/ idle flag (bit 0) is 0.
12 Error messages 12.3 CIP™ error messages ________________________________________________________________ 12.3 CIP™ error messages Error code [hex] Error designation Description 0x000 SUCCESS No error 0x001 ... Instance error messages ( 136) des Connection Manager Object (6 / 0x06) ( 135) 0x002 RESOURCE_UNAVAILABLE Resource required to perform the service not available. 0x003 INVALID_PARAM_VALUE Invalid parameter value 0x008 SERVICE_NOT_SUPP Service is not supported.
12 Error messages 12.4 Mapping of Lenze device errors to DRIVECOM errors ________________________________________________________________ 12.4 Mapping of Lenze device errors to DRIVECOM errors Via the instance attribute "FaultCode" of the Control Supervisor Object (41 / 0x29) ( 150) Lenze device errors are output with the DRIVECOM error numbers. From inverter drive version V13.00 and communication module version V01.
12 Error messages 12.4 Mapping of Lenze device errors to DRIVECOM errors ________________________________________________________________ Lenze error Error number [32 bits] Error message CAN DRIVECOM error Emergency Error Code Error number [hex] Error message xx.0123.00071 OC11: Current clamp for too long (>1 sec) 0xF000 0xF000 Additional functions xx.0123.00074 ID5: Error pole position identification 0xF000 0xF000 Additional functions xx.0123.00075 ID6: Error resolver ident.
12 Error messages 12.4 Mapping of Lenze device errors to DRIVECOM errors ________________________________________________________________ Lenze error Error number [32 bits] 104 Error message CAN Emergency Error Code DRIVECOM error Error number [hex] Error message xx.0145.00050 dF50: Retain error 0x6100 0x6100 Internal software xx.0145.00051 dF51: CuCcr error 0x6100 0x6100 Internal software xx.0145.00052 dF52: BuCcr error 0x6100 0x6100 Internal software xx.0184.00001 Ck01: Pos.
12 Error messages 12.4 Mapping of Lenze device errors to DRIVECOM errors ________________________________________________________________ EtherNet/IP error messages Lenze error Error number [32 bits] Error message DRIVECOM error Error number [hex] Error message xx.0444.12544 EtherNet/IP: Exist. connect. to 8400 lost 0x7510 xx.0444.21809 EtherNet/IP: Memory: No Access 0x7600 Data memory xx.0444.21810 EtherNet/IP: Memory: Read Error 0x7600 Data memory xx.0444.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ 13 Parameter reference This chapter supplements the parameter list and the table of attributes for the Inverter Drive 8400 contained in the software manual and in the »Engineer« online help by the parameters of the communication module E84AYCEO (EtherNet/IP). 13.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13002 Parameter | Name: Data type: UNSIGNED_8 Index: 11573 = 0x2D35 C13002 | Gateway Address Setting of the gateway address Setting the IP configuration of the Inverter Drive 8400 ( 42) Setting range (min. value | unit | max.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13006 Parameter | Name: Data type: UNSIGNED_8 Index: 11569 = 0x2D31 C13006 | Multicast IP Start Address Setting of the multicast IP address Setting the IP configuration of the Inverter Drive 8400 ( 42) Setting range (min. value | unit | max.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13012 Parameter | Name: Data type: UNSIGNED_8 Index: 11563 = 0x2D2B C13012 | Active Gateway Address Display of the active gateway address (Instance attribute 5 (Gateway Address) in the TCP/IP Interface Object (245 / 0xF5) ( 141)) Display range (min. value | unit | max.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13017 Parameter | Name: Data type: UNSIGNED_16 Index: 11558 = 0x2D26 C13017 | Ethernet Config Control Setting of the baud rate for the Ethernet connections Dependent on the configuration of the Ethernet port of the device to be connected, we recommend the use of a cross-over cable.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13020 Parameter | Name: Data type: UNSIGNED_8 Index: 11555 = 0x2D23 C13020 | Multicast Config Num Mcast Used to set how many multicast IP addresses will be assigned. (Instance attribute 9 (Num Mcast) in the TCP/IP Interface Object (245 / 0xF5) ( 141)) Setting range (min. value | unit | max.
13 Parameter reference 13.
13 Parameter reference 13.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13848 Parameter | Name: Data type: OCTET_STRING Index: 10727 = 0x29E7 C13848 | Last Conflicted MAC ID Display of the MAC address of the EtherNet/IP node with the last address conflict (ACD). The data of the last conflict will only be saved in this code if ACD is active at the moment when the conflict occurs (C13846 = 1).
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13851 Parameter | Name: Data type: INTEGER_16 Index: 10724 = 0x29E4 C13851 | All words from scanner Display of the I/O data words transferred from the scanner to the communication module (adapter). In the subcodes, all I/O data words transferred from the scanner are displayed. However, only the configured I/O data words are valid. Display range (min. value | unit | max.
13 Parameter reference 13.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13862 Parameter | Name: Data type: UNSIGNED_16 Index: 10713 = 0x29D9 C13862 | CIP Network Status Display of the current CIP network status • The status is also indicated via the NS LED.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13871 Parameter | Name: Data type: UNSIGNED_16 Index: 10704 = 0x29D0 C13871 | CIP Connections Type Display of the current CIP connection types • "Listen Only" connections are not displayed. Selection list (read only) 0 Nonexistent 1 Exclusive Owner 2 Input Only 3 Listen Only 4 Explicit Connection Subcodes Info C13871/1 Type of CIP connection 1 ... ...
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13874 Parameter | Name: Data type: UNSIGNED_32 Index: 10701 = 0x29CD C13874 | CIP Connections Timeout Time Display of the timeouts (ms) of the CIP connections Display range (min. value | unit | max. value) 0 ms 4294967295 Subcodes Info C13874/1 Timeout time of CIP connection 1 ... ...
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13881 Parameter | Name: Data type: UNSIGNED_16 Index: 10694 = 0x29C6 C13881 | Overall Ethernet Timeout Time Setting of the overall monitoring time (see Fault with regard to EtherNet/IP communication ( 88)) A change in the monitoring response becomes immediately effective. Setting range (min. value | unit | max.
13 Parameter reference 13.1 Parameters of the communication module ________________________________________________________________ C13902 Parameter | Name: Data type: VISIBLE_STRING Index: 10673 = 0x29B1 C13902 | Firmware Version The code contains a string with a length of 11 bytes. The firmware version is displayed (e.g. "01.00.01.00").
13 Parameter reference 13.2 Table of attributes ________________________________________________________________ 13.2 Table of attributes The table of attributes contains information required for communication with the inverter via parameters. How to read the table of attributes: Column Meaning Code Parameter name Cxxxxx Name Parameter short text (display text) Text hex Index under which the parameter is addressed. The subindex for array variables corresponds to the Lenze subcode number.
13 Parameter reference 13.
14 Implemented CIP™ objects ________________________________________________________________ 14 Implemented CIP™ objects An EtherNet/IP node can be seen as an accumulation of objects. An individual object is characterised by its class, its instances and attributes. Several services such as read and write services can be applied to these objects. Note! This chapter only describes the CIP objects implemented by Lenze and the properties supported by them (attributes, service codes etc.).
14 Implemented CIP™ objects ________________________________________________________________ General class attributes Attribute Service ID Name Data type Description 1 Get Revision UINT Revision no. of the object 2 Get Max. Instance UINT Max.
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ 14.1 General CIP objects 14.1.1 Identity Object (1 / 0x01) The "Identity Object" provides the identification and general information about the device. Class attributes Attribute Service ID Name Data type Value 1 Get Revision UINT 1 (0x0001) 2 Get Max. Instance UINT 1 (0x0001) 3 Get Number of Instances UINT 1 (0x0001) 6 Get Max.
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ Instance attribute "Status" (attribute 5) Bits Name Description 0 Owned The state ’1’ indicates that the device (or an object within the device) has an owner. Within a master/slave model, the state ’1’ indicates that the "predefined master/slave connection set" is assigned to a master. Outside the master/slave model, it means "TBD".
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ 14.1.2 Message Router Object (2 / 0x02) With the "Message Router Object", a client can address a service for the transfer of data to any object class or instance. Class attributes Attribute Service ID Name Data type Value 1 Get Revision UINT 1 (0x0001) 2 Get Max.
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ 14.1.
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ Instance attributes for output data of the scanner Attribute Service ID Name Data type Value 3 Get / Set Data ARRAY of SINT / INT / DINT Max.
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ Instance attributes for input data of the scanner Attribute Service ID Name Data type Value 3 Get / Set Data ARRAY of SINT / INT / DINT Max.
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ Instance Byte 23 (0x17) 0 Bit 7 Bit 6 Bit 5 Bit 4 Net Ref NetCtrl Bit 3 Bit 2 Bit 1 Bit 0 Fault Reset Run Rev Run Fwd 1 110 (0x6E) 70 (0x46) 2 Speed Reference (Low Byte) 3 Speed Reference (High Byte) 4 Torque Reference (Low Byte) 5 Torque Reference (High Byte) 0 Custom Output ... ...
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ Data mapping of the output assemblies Data component [Bits 0 ...
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ Supported service codes 134 Service code [hex] Name Description 0x0E Get_Attribute_Single Outputs the value of a certain attribute. 0x10 Set_Attribute_Single Changes the value of a certain attribute. Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ 14.1.4 Connection Manager Object (6 / 0x06) The "Connection Manager Object" manages the internal resources for the I/O data transfer (implicit messaging) and the parameter data transfer (explicit messaging). The instance specified by the "connection manager" class refers to a "connection instance" or a "connection object".
14 Implemented CIP™ objects 14.1 General CIP objects ________________________________________________________________ Instance error messages Error code [hex] Extended code [hex] 0x000 - 0x001 Error designation Description SUCCESS No error 0x106 OWNERSHIP_CONFLICT The connection could not be established because another connection has already occupied the required resources. It is only possible to establish an "exclusive owner" connection to the adapter.
14 Implemented CIP™ objects 14.2 EtherNet/IP objects ________________________________________________________________ 14.2 EtherNet/IP objects 14.2.1 Device Level Ring (DLR) Object (71 / 0x47) The "Device Level Ring (DLR) Object" provides status information for the DLR protocol. The DLR protocol is a "layer 2" protocol enabling the use of an Ethernet ring topology. Note! Only the "beacon-based ring node" mode is supported.
14 Implemented CIP™ objects 14.2 EtherNet/IP objects ________________________________________________________________ Instance attribute "Capability Flags" (attribute 12) Bits Name Description 0 Announce-based Ring Node Is not supported (state ’0’). 1 Beacon-based Ring Node The state ’1’ is set if the ring node implementation is based on the processing of "beacon frames". See also: • C13844 (Beacon Times) • C13845 (Beacon Frames) 2 ...
14 Implemented CIP™ objects 14.2 EtherNet/IP objects ________________________________________________________________ 14.2.2 Quality of Service (QoS) Object (72 / 0x48) The "Quality of Service (QoS) Object" enables different classifications and prioritisations of the data packets for EtherNet/IP communication. For this purpose, the EtherNet/IP messages are marked with "802.1Q tags" and "Differentiated Services Codepoints" (DSCP).
14 Implemented CIP™ objects 14.2 EtherNet/IP objects ________________________________________________________________ Attribute Service ID Name Data type Value 7 Set DSCP Low USINT 31: Messages with low priority Is not supported at the moment. 8 Set DSCP Explicit USINT 27: "Explicit messages" (parameter data) (C13022/7) Supported service codes 140 Service code [hex] Name Description 0x0E Get_Attribute_Single Outputs the value of a certain attribute.
14 Implemented CIP™ objects 14.2 EtherNet/IP objects ________________________________________________________________ 14.2.3 TCP/IP Interface Object (245 / 0xF5) The "TCP/IP Interface Object" serves to configure the TCP/IP network interface of the device. Class attributes Attribute Service ID Name Data type Value 1 Get Revision UINT 2 (0x0002) 2 Get Max.
14 Implemented CIP™ objects 14.
14 Implemented CIP™ objects 14.2 EtherNet/IP objects ________________________________________________________________ Instance attribute "Status" (attribute 1) Bits Name 0 ... 3 Interface Configuration Status Description 4 Mcast Pending This bit indicates a pending change of the multicast configuration in attribute 9 (Mcast Config) and/or the TTL value (C13019). It is set to ’1’ if either a multicast attribute or the TTL value is set.
14 Implemented CIP™ objects 14.
14 Implemented CIP™ objects 14.2 EtherNet/IP objects ________________________________________________________________ 14.2.4 Ethernet Link Object (246 / 0xF6) The "Ethernet Link Object" provides general information and status information about the Ethernet interfaces (IEEE 802.3). Note! Write accesses to writable attributes become effective immediately. Class attributes Attribute Service ID Name Data type Value 1 Get Revision UINT 3 (0x0003) 2 Get Max.
14 Implemented CIP™ objects 14.2 EtherNet/IP objects ________________________________________________________________ Attribute Service ID Name Data type Value 8 Get Interface State USINT Current operating status of the Ethernet interface • 0: Unknown status • 1: Enable (The interface can send and receive data.) • 2: Disable • 3: Testing • 4 ... 255: Reserved 9 Set Admin State USINT Administrative status • 0: Reserved • 1: Enable • 2: Disable • 3 ...
14 Implemented CIP™ objects 14.2 EtherNet/IP objects ________________________________________________________________ Instance attribute "Control Bits" (attribute 6, Interface Control) Bits Name Description 0 Auto-negotiate Activation of "Link Auto-Negotiation" • 0: "Link Auto-Negotiation" is not active. The device uses the settings of the bits "Forced Duplex Mode" (bit 1) and "Forced Interface Speed" (see attribute 6, Interface Control). • 1: "Link Auto-Negotiation" is active.
14 Implemented CIP™ objects 14.3 "AC Drive Profile" objects ________________________________________________________________ 14.3 "AC Drive Profile" objects From inverter drive version V13.00 and communication module version V01.02, the EtherNet/IP specified "AC Drive Profile" is supported. The standard device code C00005 = "1100: AC Drive Profile" serves to select the "AC Drive Profile" application. The "AC Drive Profile" contains ...
14 Implemented CIP™ objects 14.3 "AC Drive Profile" objects ________________________________________________________________ 14.3.1 Motor Data Object (40 / 0x28) The "Motor Data Object" provides a data basis for motor parameters. Class attributes Attribute Service ID Name Data type Value 1 Get Revision UINT 1 (0x0001) 2 Get Max.
14 Implemented CIP™ objects 14.3 "AC Drive Profile" objects ________________________________________________________________ 14.3.2 Control Supervisor Object (41 / 0x29) The "Control Supervisor Object" describes all management functions of the devices used to control the motor. Class attributes Attribute Service ID Name Data type Value 1 Get Revision UINT 1 (0x0001) 2 Get Max.
14 Implemented CIP™ objects 14.3 "AC Drive Profile" objects ________________________________________________________________ Attribute Service ID Name Data type Value 13 Get FaultCode UINT DRIVECOM error code of the error causing the Faulted status. Mapping of Lenze device errors to DRIVECOM errors ( 102) 15 Get CtrlFromNet BOOL Status of run/stop control • 0: Run/stop control via local setting on the device or terminal • 1: Run/stop control via network (e.g.
14 Implemented CIP™ objects 14.3 "AC Drive Profile" objects ________________________________________________________________ 14.3.3 AC Drive Object (42 / 0x2A) The "AC Drive Object" describes the device-specific functions of the drive, e.g. speed ramps, torque control etc. Class attributes Attribute Service ID Name Data type Value 1 Get Revision UINT 1 (0x0001) 2 Get Max.
14 Implemented CIP™ objects 14.3 "AC Drive Profile" objects ________________________________________________________________ Attribute Service ID Name Data type Value 24 Get / Set TorqueScale SINT Torque scaling factor [Nm/2TorqueScale] Value range: -128 ... 127 29 Get / Set RefFromNet BOOL Status of reference speed / reference torque • 0: Reference via local setting on the device or terminal • 1: Reference via network (e.g.
14 Implemented CIP™ objects 14.3 "AC Drive Profile" objects ________________________________________________________________ 14.3.4 Write "DriveMode" attribute In order to be able to use the torque control for the Assembly-Objektinstanzen 22 (0x16), 23 (0x17), 72 (0x48), 73 (0x49), the "DriveMode" attribute has to be written by means of explicit message transfer.
14 Implemented CIP™ objects 14.4 Lenze objects ________________________________________________________________ 14.4 Lenze objects 14.4.1 Lenze Class (101 / 0x65) The "Lenze Class (101 / 0x65)" enables the access to the adjustable error responses to EtherNet/IP errors which can be set in code C13880. Note The attributes of this class are described in the EDS file.
14 Implemented CIP™ objects 14.4 Lenze objects ________________________________________________________________ Supported service codes 156 Service code [hex] Name Description 0x01 Get_Attributes_All Outputs a list of the attributes and the attribute's values for a certain object. 0x0E Get_Attribute_Single Outputs the value of a certain attribute. 0x10 Set_Attribute_Single Changes the value of a certain attribute.
14 Implemented CIP™ objects 14.4 Lenze objects ________________________________________________________________ 14.4.2 Lenze Class (103 / 0x67) The "Lenze Class (103 / 0x67)" provides the image of the scanner input data. The input data for the scanner are provided at the MCI_OUT interface of the communication module and are sent to the scanner by means of the assembly object instance 111 (0xE6).
14 Implemented CIP™ objects 14.4 Lenze objects ________________________________________________________________ 14.4.3 Lenze Class (104 / 0x68) The "Lenze Class (104 / 0x68)" provides the image of the scanner output data. The output data of the scanner are sent by means of the assembly object instance 110 (0xE5, Custom Output) and are provided at the MCI_IN interface of the communication module.
14 Implemented CIP™ objects 14.4 Lenze objects ________________________________________________________________ 14.4.4 Lenze Class (110 / 0x6E) The "Lenze Class (110 / 0x6E)" enables read or write access to Lenze codes. The Lenze code must be specified as an "instance" (corresponding code no. 1 ... 65535) and its subcodes must be specified as "attributes". Note! • If the corresponding Lenze code does not have a subcode, the value '0' must be entered in the attribute.
Index ________________________________________________________________ A AC Drive Object (42 / 0x2A) 152 AC drive profile objects 148 AC Drive Profile technology application 59 Activating changed setting 51 Active Conflict Detection State (C13847) 113 Active gateway address (C13012) 109 Active IP address (C13010) 108 Active Multicast IP Address (C13016) 109 Active subnetwork mask (C13011) 108 Address Conflict Detection (C13846) 113 All words from scanner (C13851) 115 All words to scanner (C13850) 114 All w
Index ________________________________________________________________ Configuring user-definable parameter sets 62 Conformities 16 Connection Manager Object (6 / 0x06) 135 Connections 15 Control Supervisor Object (41 / 0x29) 150 Conventions 8 Conventions used 8 Cyclic I/O data 54 D Data mapping of the input assemblies 133 Data mapping of the output assemblies 133 Data transfer 52 Device and application-specific safety instructions 12 Device Level Ring (DLR) Object (71 / 0x47) 137 Device protection 12 Devi
Index ________________________________________________________________ H Hostname (C13899) 120 I I/O assemblies 60 I/O configuration in the »Engineer« 62 I/O configuration with »RSLogix 5000« version 19 or lower 68 I/O configuration with »RSLogix 5000« version 20 or higher 73 I/O data mapping 57 I/O data transfer (implicit messages) 56 Identification 13 Identity Object (1 / 0x01) 126 Implicit messages 56 Implicit messages (I/O data transfer) 54 Information regarding the validity 6 Initial switch-on 51 Inp
Index ________________________________________________________________ S Safety instructions 10, 11 Saving the I/O configuration in »RSLogix 5000« 83 Screenshots/application examples 6 Setting the IP configuration 42 Setting via the EtherNet/IP configurator of the »Engineer« 43 Short overview of EtherNet/IP error messages 96 State diagram 55 Status displays (LEDs) 89 Status indicators at the RJ45 sockets (X259, X260) 94 Structure of the Ethernet cable 31 Subnet mask 46 Subnetwork mask (C13001) 106 Supervis
)(('%$&. 164 Your opinion is important to us These instructions were created to the best of our knowledge and belief to give you the best possible support for handling our product. If you have suggestions for improvement, please e-mail us to: feedback-docu@Lenze.de Thank you for your support.
E84AYCEO communication module (EtherNet/IP™) · Communication Manual · EDS84AYCEO · 13443009 · DMS 3.0 EN · 10/2013 · TD17 Lenze Drives GmbH Postfach 10 13 52 D-31763 Hameln Germany +49 (0)51 54 / 82-0 +49 (0)51 54 / 82-28 00 Lenze@Lenze.de www.Lenze.com Service Lenze Service GmbH Breslauer Straße 3 D-32699 Extertal Germany 00 80 00 / 24 4 68 77 (24 h helpline) +49 (0)51 54 / 82-11 12 Service@Lenze.
