Accessories EtherNet/IP™ 13444431 Ä.
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.
About this documentation ________________________________________________________________ 1 About this documentation Contents This documentation exclusively contains descriptions of the EtherNet/IP™ bus system for the Inverter Drives 8400 motec. Note! This documentation supplements the mounting instructions supplied with the Communication Unit and the "Inverter Drives 8400 motec" hardware manual.
About this documentation ________________________________________________________________ Target group This documentation addresses to persons who configure, install, commission, and maintain the networking and remote maintenance of a machine. Tip! Current documentation and software updates with regard to Lenze products can be found in the download area at: www.Lenze.
About this documentation Document history ________________________________________________________________ 1.1 Document history Version 7 Description 1.0 08/2012 TD17 First edition 2.0 10/2013 TD17 New layout Revised chapters: I/O data transfer (implicit messages) ( 44) Parameter data transfer (explicit messages) ( 73) Implemented CIP™ objects ( 108) Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.
About this documentation 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 Decimal separator Hexadecimal Binary • Nibble Standard notation Point 0x[0 ... 9, A ... F] 0b[0, 1] Example: 1234 The decimal point is always used. For example: 1234.
About this documentation Terminology used ________________________________________________________________ 1.3 Terminology used Term Meaning ACD Address Conflict Detection Adapter EtherNet/IP slave Inverter / Drive Lenze drive of the "Inverter Drives 8400 motec" product series Standard device ARP Address Resolution Protocol BOOTP Bootstrap Protocol Code Parameter which serves to parameterise and monitor the drive. In normal usage, the term is usually referred to as "Index".
About this documentation Notes used ________________________________________________________________ 1.
Safety instructions 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.
Safety instructions Device and application-specific safety instructions ________________________________________________________________ 2.2 Device and application-specific safety instructions During operation, the Communication Unit must be connected to the Wiring Unit and the Drive Unit. 2.3 Documentation for Inverter Drives 8400 motec, control system, plant/machine All the other measures prescribed in this documentation must also be implemented.
Product description Application as directed ________________________________________________________________ 3 Product description 3.1 Application as directed The EtherNet/IP Communication Unit ... • is a unit that can only be used in conjunction with the following modules: Product series Type designation Inverter Drives 8400 motec Drive Unit E84DGDVxxxxxxxx (from version V04.01) Inverter Drives 8400 motec Wiring Unit E84DGVNxx • is a device intended for use in industrial power systems.
Product description Features and variants ________________________________________________________________ 3.
Product description Connections and interfaces ________________________________________________________________ 3.3 Connections and interfaces E84DG029 [3-1] EtherNet/IP Communication Unit Pos. Description A1 / LED Position of LEDs for EtherNet/IP status display LED status displays ( 78) A2 EtherNet/IP connections (M12 sockets, 5-pin, D-coded) EtherNet/IP connection ( 23) A3 A4 B1 ...
Product description Connections and interfaces ________________________________________________________________ • By default, the EtherNet/IP connections and the LEDs for the EtherNet/IP status displays are already mounted and wired: • EtherNet/IP connection A2 to plug connector X31 • EtherNet/IP connection A3 to plug connector X32 • LEDs on plug connector X55 • At positions A1 ... A4 and B1 ... B4, it is also possible to design the EtherNet/IP connections and other connections (e.g. digital inputs) freely.
Technical data General data and operating conditions ________________________________________________________________ 4 Technical data 4.1 Hardware manual for Inverter Drives 8400 motec Here you will find the ambient conditions and information on the electromagnetic compatibility (EMC) that also apply to the Communication Unit.
Technical data Protocol data ________________________________________________________________ 4.2 Protocol data Range Values I/O data words 1 ... 10 data words to scanner (16 bits/word, max. 20 bytes) 1 ... 8 data words from scanner (16 bits/word, max. 16 bytes) Supported CIP services 4.
Technical data Internal switch latency ________________________________________________________________ 4.4 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.
Installation ________________________________________________________________ 5 Installation Stop! Electrostatic discharge Electronic components within the Communication Unit can be damaged or destroyed by electrostatic discharge. Possible consequences: • The Communication Unit is defective. • Fieldbus communication is not possible or faulty. • I/O signals are faulty. • The safety function is faulty. Protective measures Discharge electrostatic charges before touching the Communication Unit.
Installation Mechanical installation ________________________________________________________________ 5.1 Mechanical installation Mounting instructions for Inverter Drive 8400 motec Here you will find detailed information on the installation. 0.37 ... 3.0 kW 4.0 ... 7.5 kW E84DG023a E84DG023b [5-1] Mechanical installation of the 8400 motec components Legend for fig. [5-1] 21 1 Drive Unit 2 Communication unit 3 Wiring Unit A Cover of the Drive Unit EDK84DG...
Installation Electrical installation ________________________________________________________________ 5.2 Electrical installation Hardware manual for Inverter Drives 8400 motec Here you can find detailed information on ... • the digital and analog inputs/outputs; • the relay output; • the integrated safety system (safety option); • the wiring of the terminals. Observe the notes and wiring instructions contained in this documentation! 5.2.
Installation Electrical installation ________________________________________________________________ • Tree via switches S SW SW SW E94AYCEO006 [5-4] Tree topology (S = scanner, SW = switch) • Switch / switch SW SW SW E94AYCEO007 [5-5] 5.2.
Installation Electrical installation ________________________________________________________________ 5.2.3 External voltage supply • The external voltage supply can be used to establish EtherNet/IP communication for commissioning and to query the data of the digital and analog inputs. • Furthermore, the external voltage supply serves to maintain EtherNet/IP communication if the main supply fails. • The digital inputs RFR, DI1 ... DI5 and the analog input can continue to be evaluated.
Commissioning 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.
Commissioning Configuring the host system (scanner) ________________________________________________________________ 6.2 Configuring the host system (scanner) To be able to communicate with the Communication Unit, the host system (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).
Commissioning 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.
Commissioning 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 1769-L32E CompactLogix controller with integrated EtherNet/IP interface is used to communicate with Inverter Drives 8400 motec. The »RSLogix 5000« programming software from Rockwell is used for the configuration.
Commissioning 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.
Commissioning Setting the IP configuration of the Inverter Drive 8400 motec ________________________________________________________________ 6.3 Setting the IP configuration of the Inverter Drive 8400 motec The IP configuration is required for addressing the Inverter Drive 8400 motec to ensure that communication between the PC/»Engineer« or the scanner and the drive can be effected via EtherNet/IP. For this, an IP address, subnet mask, and gateway address must be allocated.
Commissioning Setting the IP configuration of the Inverter Drive 8400 motec ________________________________________________________________ 6.3.1 Setting via the EtherNet/IP configurator of the »Engineer« Note! • Changes in the IP parameters will become effective immediately. • An existing IP connection to the Inverter Drive 8400 motec will be interrupted. How to set the IP parameters via the EtherNet/IP configurator: 1.
Commissioning Setting the IP configuration of the Inverter Drive 8400 motec ________________________________________________________________ 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 Unit executes a stack reset.
Commissioning Setting the IP configuration of the Inverter Drive 8400 motec ________________________________________________________________ 6.3.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 Description IP Config Control Selection (C13005) of how the IP configuration is to be made: • 0: The IP configuration currently saved in the Communication Unit is used.
Commissioning Setting the IP configuration of the Inverter Drive 8400 motec ________________________________________________________________ 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.
Commissioning Setting the IP configuration of the Inverter Drive 8400 motec ________________________________________________________________ 6.3.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.
Commissioning Setting the IP configuration of the Inverter Drive 8400 motec ________________________________________________________________ 6.3.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).
Commissioning Establishing an online connection via EtherNet/IP with the Lenze »Engineer« ________________________________________________________________ 6.4 Establishing an online connection via EtherNet/IP with the Lenze »Engineer« [6-1] 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.
Commissioning 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.
Commissioning Initial switch-on ________________________________________________________________ 6.5 Initial switch-on Establishing communication • To establish a communication, the Inverter Drive has to be supplied with mains voltage. • For EtherNet/IP communication, the Communication Unit has to be supplied with voltage. If this is not the case, the error message "CE04: MCI communication error" (error no. 01.0127.00002) is output.
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.
Data transfer 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.
Data transfer 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.
Data transfer 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) ( 110) via instance attributes 5 and 8; • indicated via the MS LED (see LED status displays ( 78)). 43 Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.
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 ...
I/O data transfer (implicit messages) Configuring I/O data ________________________________________________________________ 8.1 Configuring I/O data • The I/O data configuration is specified during the initialisation phase of the scanner (PDO mapping). • To the scanner, up to 10 data words (max. 20 bytes) can be sent. • From the scanner, up to 8 data words (max. 16 bytes) can be sent.
I/O data transfer (implicit messages) Configuring I/O data ________________________________________________________________ • In the assembly input object instances 70 ... 73 (0x46 ... 0x49), this data is not used due to profile conformity reasons. • The I/O data configuration is application-specifically predefined in the device description files and can be adapted, if necessary.
I/O data transfer (implicit messages) I/O data mapping ________________________________________________________________ 8.2 I/O data mapping I/O data transfer takes place via the MCI interface. • The I/O data are accessed via the port blocks MCI_IN and MCI_OUT. These port blocks are also referred to as I/O data channels. • The MCI_IN port block maps the received data objects. • The MCI_OUT port block maps the data objects to be sent. • To the scanner, up to 10 data words (max. 20 bytes) can be sent.
I/O data transfer (implicit messages) Technology applications (TA) / drive profiles ________________________________________________________________ 8.3 Technology applications (TA) / drive profiles The Inverter Drives 8400 motec 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.
I/O data transfer (implicit messages) Technology applications (TA) / drive profiles ________________________________________________________________ 8.3.2 "AC Drive Profile" application The Inverter Drives 8400 motec supports the EtherNet/IP-specific "AC Drive Profile". The standard device code C00005 = "1100: AC Drive Profile" serves to select the "AC Drive Profile" application. The "AC Drive Profile" contains ...
I/O data transfer (implicit messages) I/O assemblies ________________________________________________________________ 8.4 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 ( 47)).
I/O data transfer (implicit messages) 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.
I/O data transfer (implicit messages) I/O configuration in the »Engineer« ________________________________________________________________ 8.5 I/O configuration in the »Engineer« 8.5.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.
I/O data transfer (implicit messages) 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.
I/O data transfer (implicit messages) 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. Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.
I/O data transfer (implicit messages) 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.
I/O data transfer (implicit messages) I/O configuration in the »Engineer« ________________________________________________________________ 8.5.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).
I/O data transfer (implicit messages) I/O configuration with »RSLogix 5000« version 19 or lower ________________________________________________________________ 8.6 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. Up to and including software version 19, the I/O configuration is carried out without EDS files.
I/O data transfer (implicit messages) 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 · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.
I/O data transfer (implicit messages) 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.
I/O data transfer (implicit messages) 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".
I/O data transfer (implicit messages) 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.
I/O data transfer (implicit messages) I/O configuration with »RSLogix 5000« version 20 or higher ________________________________________________________________ 8.7 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 ( 27) are used for the I/O configuration.
I/O data transfer (implicit messages) 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. Open the "Select Module Type" dialog window, go to the Catalog tab and select "E84DGFCG Motec". 5. Confirm the selection with Create. 63 Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.
I/O data transfer (implicit messages) 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 · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.
I/O data transfer (implicit messages) 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.
I/O data transfer (implicit messages) 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.
I/O data transfer (implicit messages) 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.
I/O data transfer (implicit messages) 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 ...
I/O data transfer (implicit messages) 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’.
I/O data transfer (implicit messages) 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).
I/O data transfer (implicit messages) 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.
I/O data transfer (implicit messages) Saving the I/O configuration in »RSLogix 5000« ________________________________________________________________ 8.8 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.
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. For all Allen-Bradley devices of the CompactLogix, ControlLogix and SoftLogix series, the MSG instruction provides the application possibilities described in this chapter.
Parameter data transfer (explicit messages) Write parameters ________________________________________________________________ 9.
Parameter data transfer (explicit messages) Read parameters ________________________________________________________________ 9.
Parameter data transfer (explicit messages) Read parameters ________________________________________________________________ For every "explicit message", the path for sending the message via the Ethernet port of the controller to the IP address of the drive needs to be set under the Communication tab. If you need assistance with the setting of this path, please consult the PLC manufacturer. Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.
Monitoring ________________________________________________________________ 10 Monitoring Fault with regard to EtherNet/IP communication The response of the Inverter Drive 8400 motec to a fault with regard to EtherNet/IP communication can be set in the »Engineer« under the Monitoring tab. Settings Description Idle Mode The 32-bit real time header sent by the scanner is evaluated. • Run/idle flag (bit 0) = 1: • The scanner indicates the validity of the I/O data.
Diagnostics LED status displays ________________________________________________________________ 11 Diagnostics EtherNet/IP communication can be diagnosed via the LEDs of the Communication Unit. Moreover, the »Engineer« serves to show diagnostic information. 11.1 LED status displays E84DG056 LED MS Colour / status Green Red Off Off Off On Description CIP module status: "Nonexistent" The Communication Unit is not supplied with voltage.
Diagnostics LED status displays ________________________________________________________________ LED NS Colour / status Green Red Off Off Off On Description CIP network status: "No IP Address" The Communication Unit is not supplied with voltage or does not yet have an IP address. CIP network status: "Duplicate IP" The Communication Unit cannot access the fieldbus (IP address conflict). Off Blinking 250 ms 250 ms CIP network status: "Connection Timeout" A time-out is executed.
Diagnostics Diagnosing with the »Engineer« ________________________________________________________________ 11.2 Diagnosing with the »Engineer« In the »Engineer« under the Diagnostics tab, you will find EtherNet/IP diagnostics information.
Error messages Short overview of the EtherNet/IP error messages ________________________________________________________________ 12 Error messages This chapter complements the error list in the software manual and the »Engineer« online help for the Inverter Drive 8400 motec by EtherNet/IP error messages. 12.
Error messages Possible causes and remedies ________________________________________________________________ 12.2 Possible causes and remedies This chapter lists all EtherNet/IP error messages 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.
Error messages Possible causes and remedies ________________________________________________________________ EtherNet/IP: Restart by watchdog reset [0x01bc6010] Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response) No reaction System fault Fault Trouble TroubleQuickStop WarningLocked Warning Information Cause Remedy Device is defective. Send the device and a description of the fault to Lenze.
Error messages Possible causes and remedies ________________________________________________________________ EtherNet/IP: Invalid Configuration [0x01bc6430] Response (Lenze setting printed in bold) Setting: not possible None System fault Fault Trouble Quick stop by trouble Warning locked Warning Information Cause Remedy Module configuration is faulty. Check and correct module configuration.
Error messages Possible causes and remedies ________________________________________________________________ EtherNet/IP: Idle Mode [0x01bc8132] (nt05: COM fault 5) Response (Lenze setting printed in bold) Setting: C13880/1 None System error Error Fault 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.
Error messages CIP™ error messages ________________________________________________________________ 12.3 CIP™ error messages Error code [hex] Error designation Description 0x000 SUCCESS No error 0x001 ... Instance error messages ( 121) of the Connection Manager Object (6 / 0x06) ( 120) 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.
Error messages 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) ( 135) Lenze device errors are output with the DRIVECOM error numbers. The following tables show the assignment of the Lenze device errors and "CAN Emergency Error Codes" to the DRIVECOM errors.
Error messages Mapping of Lenze device errors to DRIVECOM errors ________________________________________________________________ Lenze error Error number [32 bits] Error message CAN Emergency Error Code DRIVECOM error Error number [hex] Error message xx.0123.00090 OC13: Maximum current for Fch exceeded 0x2000 0x2000 Current xx.0123.00093 OT2: Speed controller output is limited 0xF000 0x7310 Speed xx.0123.00094 FC01: Switching frequency reduction 0x2000 0xF000 Additional functions xx.
Error messages Mapping of Lenze device errors to DRIVECOM errors ________________________________________________________________ Lenze error Error number [32 bits] 89 Error message CAN DRIVECOM error Emergency Error Code Error number [hex] Error message xx.0184.00001 Ck01: Pos. HW limit switch 0x8600 0x8600 xx.0184.00002 Ck02: Neg. HW limit switch 0x8600 0x8600 Positioning controller Positioning controller xx.0184.00005 Ck15: Error message sig.
Error messages 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.
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 13 Parameter reference This chapter supplements the parameter list and the table of attributes in the software manual and the »Engineer« online help for the Inverter Drive 8400 motec by the parameters of the E84DGFCGxxx Communication Unit (EtherNet/IP). 13.
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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 motec ( 30) Setting range (min. value | unit | max.
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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 motec ( 30) Setting range (min. value | unit | max.
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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) ( 126)) Display range (min. value | unit | max.
Parameter reference Parameters of the Communication Unit ________________________________________________________________ C13017 Parameter | Name: Data type: UNSIGNED_16 Index: 11558 = 0x2D26 C13017 | Ethernet Config Control Setting of the baud rate for the Ethernet connections Selection list 0 Auto-Negotiation 1 10 Mbps 2 100 Mbps 3 Reserved 4 Reserved 5 10 Mbps/Half Duplex 6 10 Mbps/Full Duplex 7 100 Mbps/Half Duplex 8 100 Mbps/Full Duplex 9 Reserved 10 Reserved 11 Reserved 12 Reserved Subcodes Lenze s
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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) ( 126)) Setting range (min. value | unit | max.
Parameter reference Parameters of the Communication Unit ________________________________________________________________ C13840 Parameter | Name: Data type: UNSIGNED_8 Index: 10735 = 0x29EF C13840 | DLR Network Topology Display of the used DLR network topology (Device Level Ring) (Instance attribute 1 (Network Topology) in the Device Level Ring (DLR) Object (71 / 0x47) ( 122)) Selection list (read only) 0 Linear 1 Ring Read access Write access CINH PLC STOP No transfer PDO_MAP_RX PDO_MAP_
Parameter reference Parameters of the Communication Unit ________________________________________________________________ C13844 Parameter | Name: Data type: UNSIGNED_32 Index: 10731 = 0x29EB C13844 | Beacon Times Display of the beacon times (μs) Subcodes Info C13844/1 Beacon interval C13844/2 Beacon timeout Read access Write access CINH PLC STOP No transfer PDO_MAP_RX PDO_MAP_TX COM MOT C13845 Parameter | Name: Data type: UNSIGNED_32 Index: 10730 = 0x29EA C13845 | Beacon Frames
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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).
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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 Unit (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.
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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.
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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 ... ...
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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 ... ...
Parameter reference Parameters of the Communication Unit ________________________________________________________________ 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 ( 77)) A change in the monitoring response becomes immediately effective. Setting range (min. value | unit | max.
Parameter reference Parameters of the Communication Unit ________________________________________________________________ C13902 Parameter | Name: C13902 | Firmware Version Data type: VISIBLE_STRING Index: 10673 = 0x29B1 The code contains a string with a length of 11 bytes. The firmware version is displayed (e.g. "00.01.00.00").
Parameter reference 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.
Parameter reference Table of attributes ________________________________________________________________ Table of attributes Code 107 Name Index Data dec hex DS DA 11575 0x2D37 A 4 DT Access Factor R W UNSIGNED_8 C13000 IP address C13001 Subnet mask 11574 0x2D36 A 4 UNSIGNED_8 C13002 Gateway address 11573 0x2D35 A 4 UNSIGNED_8 C13003 MAC-ID 11572 0x2D34 E 1 OCTET_STRING C13005 IP Config Control 11570 0x2D32 E 1 UNSIGNED_8 C13006 Multicast IP
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.).
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.
Implemented CIP™ objects 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.
Implemented CIP™ objects 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".
Implemented CIP™ objects 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.
Implemented CIP™ objects General CIP objects ________________________________________________________________ 14.1.
Implemented CIP™ objects 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.
Implemented CIP™ objects General CIP objects ________________________________________________________________ Instance attributes for input data of the scanner Attribute Service ID Name Data type Value 3 Data ARRAY of SINT / INT / DINT Max.
Implemented CIP™ objects General CIP objects ________________________________________________________________ Instance attribute "Data" (attribute 3) Instance Byte 20 (0x14) 0 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Fault Reset Bit 0 Run Fwd 1 2 Speed Reference (Low Byte) 3 21 (0x15) 0 Speed Reference (High Byte) Net Ref NetCtrl Fault Reset Run Rev Run Fwd 1 2 Speed Reference (Low Byte) 3 Speed Reference (High Byte) Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP
Implemented CIP™ objects General CIP objects ________________________________________________________________ Instance Byte 22 (0x16) 0 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Fault Reset Bit 0 Run Fwd 1 2 Speed Reference (Low Byte) 3 Speed Reference (High Byte) 4 Torque Reference (Low Byte) 5 23 (0x17) Torque Reference (High Byte) 0 Net Ref NetCtrl Fault Reset Run Rev Run Fwd 1 2 110 (0x6E) 70 (0x46) Speed Reference (Low Byte) 3 Speed Reference (High Byte) 4 Torque Refe
Implemented CIP™ objects General CIP objects ________________________________________________________________ Note! In order to be able to use the torque control for the assembly object instances 22 (0x16), 23 (0x17), 72 (0x48), 73 (0x49), the "DriveMode" attribute has to be written by means of explicit message transfer. Write "DriveMode" attribute ( 138) Data mapping of the output assemblies Data component [Bits 0 ...
Implemented CIP™ objects General CIP objects ________________________________________________________________ Data mapping of the input assemblies Data component [Bits 0 ...
Implemented CIP™ objects 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".
Implemented CIP™ objects 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.
Implemented CIP™ objects 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.
Implemented CIP™ objects 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 ...
Implemented CIP™ objects 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).
Implemented CIP™ objects 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 125 Service code [hex] Name Description 0x0E Get_Attribute_Single Outputs the value of a certain attribute.
Implemented CIP™ objects 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.
Implemented CIP™ objects EtherNet/IP objects ________________________________________________________________ Attribute Service ID Name Data type Value 5 Interface Configuration: STRUCT of: Current TCP/IP configuration Get IP Address UDINT C13010 (active IP address) Network Mask UDINT C13011 (active subnet mask) Gateway Address UDINT C13012 (active gateway address) Name Server UDINT Name Server 2 UDINT Domain Name 1 STRING 6 Get / Set Host Name STRING Host name of the device (C1389
Implemented CIP™ objects 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.
Implemented CIP™ objects EtherNet/IP objects ________________________________________________________________ Structure of the ARP message (attribute 11, "ArpPdu") Field size [Bytes] Field name Value Hardware Address Type 1: Ethernet H/W 2 Protocol Address Type 0x0800: IP 1 HADDR LEN 6: Ethernet H/W 1 PADDR LEN 4: IP 2 OPERATION 1: Request 2: Response 6 SENDER HADDR H/W address of the sender 4 SENDER PADDR Protocol address of the sender 6 TARGET HADDR H/W address of the target 4 T
Implemented CIP™ objects 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.
Implemented CIP™ objects 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 ...
Implemented CIP™ objects 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.
Implemented CIP™ objects "AC Drive Profile" objects ________________________________________________________________ 14.3 "AC Drive Profile" objects The standard device code C00005 = "1100: AC Drive Profile" serves to select the "AC Drive Profile" application. The "AC Drive Profile" contains ... • the data basis for motor parameters, • management functions of the motor control devices, • Device-specific functions of the drive, e.g. speed ramps, torque control etc.
Implemented CIP™ objects "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.
Implemented CIP™ objects "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.
Implemented CIP™ objects "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 ( 87) 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.
Implemented CIP™ objects "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.
Implemented CIP™ objects "AC Drive Profile" objects ________________________________________________________________ Supported service codes 14.3.4 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.
Implemented CIP™ objects 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.
Implemented CIP™ objects Lenze objects ________________________________________________________________ Supported service codes 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. Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.
Implemented CIP™ objects 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 placed on the MCI_OUT interface of the Communication Unit and sent to the scanner via the assembly object instance 111 (0xE6). Class attributes Attribute Service ID Name Data type Value 1 Get Revision UINT 2 (0x0002) 2 Get Max.
Implemented CIP™ objects 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 via the assembly object instance 110 (0xE5, Custom Output) and placed on the MCI_IN interface of the Communication Unit. Class attributes Attribute Service ID Name Data type Value 1 Get Revision UINT 2 (0x0002) 2 Get Max.
Implemented CIP™ objects 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) 137 AC drive profile objects 133 AC Drive Profile technology application 49 Active Conflict Detection State (C13847) 98 Active gateway address (C13012) 94 Active IP address (C13010) 93 Active Multicast IP Address (C13016) 94 Active subnetwork mask (C13011) 93 Address Conflict Detection (C13846) 98 All words from scanner (C13851) 100 All words to scanner (C13850) 99 Application as directed 13 Application not
Index ________________________________________________________________ Cyclic I/O data 42 D Data mapping of the input assemblies 119 Data mapping of the output assemblies 118 Data transfer 40 Device and application-specific safety instructions 12 Device Level Ring (DLR) Object (71 / 0x47) 122 Device protection 12 Device type 17 DHCP server 35 Diagnostics 78 Diagnostics with the »Engineer« 80 DLR Network Status (C13841) 97 DLR Network Topology (C13840) 97 Document history 7 Drive profiles 48 DRIVECOM error
Index ________________________________________________________________ H N Hostname (C13899) 104 Network topology 17, 22 Notes used 10 nt05 - COM fault 5 (error message) 85 nt14 - COM fault 14 (error message) 82 Number of nodes 17 I I/O assemblies 50 I/O configuration in the »Engineer« 52 I/O configuration with »RSLogix 5000« version 19 or lower 57 I/O configuration with »RSLogix 5000« version 20 or higher 62 I/O data 45 I/O data mapping 47 I/O data transfer (implicit messages) 44 Identity Object (1 /
Index ________________________________________________________________ T Table of attributes 106 Target group 6 TCP/IP Interface Object 35 TCP/IP Interface Object (245 / 0xF5) 126 Technical data 17 Technology applications (TA) 48 Telegram types 42 Terminology used 9 Transmission mode 17 Type of node 17 U User-definable parameter sets 48 V Validity of the documentation 6 Vendor ID 17 Versions 14 VLAN tagging 124 Voltage supply 17, 24 W Write "DriveMode" attribute 138 Write DriveMode (attribute ID 6) 138
)(('%$&. 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.
Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP · 13444431 · EDS84DMOTEIP EN 2.0 - 10/2013 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.
