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".
The hardware manual contains safety instructions that must be observed!
The features and functions of the communication module are described in detail.
Examples illustrate typical applications.
The theoretical context is only explained as far as it is required for understanding the function of
the communication module.
This documentation does not describe the software of another manufacturer. No
guarantee can be given for corresponding information in this documentation. Information
on the use of the software can be found in the documents for the host (PLC, scanner).
All brand names mentioned in this documentation are trademarks of their corresponding owners.
Tip!
Detailed information on EtherNet/IP can be found on the website of the user organisation
ODVA (Open DeviceNet Vendor Association):
www.odva.org
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD175
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.com
Information regarding the validity
The information given in this documentation is valid for the following devices:
Extension moduleType designationFrom hardware
Communication module EtherNet/IPE84AYCEOVA01.01
From software version 01.02, the "AC Drive Profile" of the Inverter Drives 8400 is supported from
version V13.00.
Screenshots/application examples
All screenshots in this documentation are application examples. Depending on the firmware
version of the communication module and software version of the installed engineering tools
(»Engineer«, »RSLogix 5000«), the screenshots in this documentation may differ from the screen
representation.
version
From software
version
6Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Inverter / DriveLenze inverters of the "Inverter Drives 8400" series
Standard device
ARPAddress Resolution Protocol
Use BOOTPBootstrap Protocol
CodeParameter which serves to parameterise and monitor the drive. In normal usage,
the term is usually referred to as "Index".
SubcodeIf a code contains several parameters, they are stored in "subcodes".
In the documentation, the slash "/" is used as a separator between the code and
the subcode (e.g. "C00118/3").
In everyday language, the term is also referred to as "subindex".
»Engineer«Software from Lenze which supports you throughout the whole machine life
cycle - from planning to maintenance.
EtherNet/IP™ (EtherNet Industrial Protocol) is a fieldbus system based on
Ethernet which uses the Common Industrial Protocol™ (CIP™) for data exchange.
EtherNet/IP™ and Common Industrial Protocol™ (CIP™) are trademarks and
patented technologies, licensed by the user organisation ODVA (Open
DeviceNet Vendor Association), USA.
Use DHCPDynamic Host Configuration Protocol
DSCPDifferentiated Services Codepoints
EDSElectronic Data Sheet
Explicit messagesExplicit Messages are used to transfer parameter data.
HWHardware
IGMPInternet Group Management Protocol
Implicit messagesImplicit Messages are used to transfer I/O data.
"Class 1" connectionI/O connection
"Class 3" connectionExplicit connection
Level 2EtherNet/IP performance level 2:
I/O Message Server including Explicit Message Server
Lenze settingDefault settings of the device, preconfigured ex works.
Basic setting
PLCProgrammable Logic Controller
QoSQuality of Service
RPIRequested Package Interval:
Interval requested between 2 telegrams for cyclic data transmission
»RSLogix 5000«Programming and development software from Rockwell for hosts (scanners) in
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.1General safety and application notes
Danger!
If the following basic safety measures are disregarded, severe injuries to persons and
damage to material assets may result.
Lenze drive and automation components ...
• must only be used as directed.
• must never be commissioned if they display signs of damage.
• must never be technically modified.
• must never be commissioned if they are not fully mounted.
• must never be operated without required covers.
• during and after operation can have live, moving and rotating parts, depending on their degree
of protection. Surfaces can be hot.
The following applies to Lenze drive components ...
• only use the accessories approved.
• Only use original manufacturer spare parts.
Observe all specifications contained in the enclosed documentation and related documentation.
• This is the precondition for safe and trouble-free operation and for obtaining the product
features specified.
Product features
• The specifications, processes, and circuitry described in this document are for guidance only and
must be adapted to your own specific application. Lenze does not take responsibility for the
suitability of the process and circuit proposals.
All works on and with Lenze drive and automation components must only be carried out by qualified
personnel. According to IEC 60364 or CENELEC HD 384 these are persons who ...
• are familiar with installing, mounting, commissioning, and operating the product.
• who have the corresponding qualifications for their work.
( 14)
• who know and can apply all regulations for the prevention of accidents, directives, and laws
applicable at the place of use.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1711
Page 12
2Safety instructions
2.2Device and application-specific safety instructions
2.2Device 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.
Ethernet cable specification
( 31)
Documentation for the standard device, host, system/machine
All the other measures prescribed in this documentation must also be implemented.
Observe the safety instructions and application notes contained in this manual.
2.3Residual hazards
Protection of persons
If the Inverter Drives 8400 are used on a phase earthed mains with a rated mains voltage 400 V,
protection against accidental contact is not ensured without implementing external measures.
Protective insulation
Device protection
The communication module contains electronic components which may be damaged or destroyed
by electrostatic discharge.
Installation
( 23)
( 17)
12
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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.
Possible consequences:
Death or severe injuries
Protective measures:
If protection against accidental contact is required for the control terminals of the
inverter and the connections of the plugged device modules, ...
• a double isolating distance must exist.
• the components to be connected must be provided with the second isolating
distance.
Note!
The existing protective insulation in the Inverter Drives 8400 is implemented according
to EN 61800-5-1.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1717
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.
sequence counter:
Runtime delay = ((66 permanent bytes + I/O data in bytes) x 8 x 10 nsec) + 4 μsec
Runtime delay for an output data packet of an adapter without
Runtime delay = ((62 permanent bytes + I/O data in bytes) x 8 x 10 nsec) + 4 μsec
Example
Delay of an output data packet of the scanners with 8 output data words (16 bytes):
• ((66 permanent bytes + 16 bytes) x 8 x 10 nsec) + 4 μsec
• (82 bytes x 8 x 10 nsec) + 4 μsec
• 6.56 μsec + 4 μsec = 10.56 μsec
32-bit "run/idle header" with 16-bit
32/bit "run/idle header":
Note!
The use of external switches can also lead to runtime delays. Depending on the system
constellation, it may be useful to create a star topology or a line/mix topology.
Network topology
( 27)
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1721
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.1Mounting for standard devices of 0.25 kW and 0.37 kW
E84YCPM002D
[5-1]Mounting for standard devices of 0.25 kW and 0.37 kW
Mounting steps
1. Use a screwdriver to lever out the cover of the MCI slot of the standard device and remove it (1,
2).
2. Loosen the securing screw for the communication module at the standard device (3).
3. Insert the communication module into the MCI slot of the standard device (4).
4. Tighten the securing screw again (5).
24
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Documentation for the standard device, host, system/machine
Observe the notes and wiring instructions contained in this documentation.
5.2.1Wiring according to EMC guidelines
In typical systems, standard shielding is sufficient for Ethernet cables.
However, in environments with a very high level of interference, EMC resistance can be improved
by additionally earthing the cable shield on both sides.
For this observe the following notes:
1. Remove the plastic sheath of the cable at a length of 2 cm.
2. Fasten the cable shield to the shield support of the standard device.
5.2.2Network topology
It is typical of EtherNet/IP to have a rather free topology the limiting factor of which is large
message latencies due to e.g. switches connected in series.
Internal switch latency
The combination of a line and a stub is useful for system wiring.
EtherNet/IP supports the following topologies:
•Line
[5-4]Line topology (S = scanner, A = adapter)
•Switch / star
( 21)
E94AYCEO008
[5-5]Switch / star topology (SW = switch, A = adapter)
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1727
A connection to the EtherNet/IP network is established via RJ45 sockets X259 and X260.
[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.
Ethernet cable specification
The installation and removal of the Ethernet cables is optimised for the use of connectors in
accordance with the "Automation Initiative of German Domestic Automobile Manufacturers"
(AIDA).
( 31)
Note!
To prevent the RJ45 socket from being damaged, insert or remove the Ethernet cable
connector straight (at a right angle) into or from the socket.
E84AYCEO005_2
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1729
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. This function adjusts the
polarity of the RJ45 interfaces so that a connection can be established irrespective of the
polarity of the opposite EtherNet/IP interface and irrespective of the type of cable used
(standard patch cable or crossover cable).
30
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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.
E94YCEI004A
[5-10] Ethernet plug in accordance with EIA/TIA 568A/568B
PairPinSignalEIA/TIA 568AEIA/TIA 568B
31Tx +white / greenwhite / orange
2Tx -greenorange
23Rx +white / orangewhite / green
14blueblue
5white / blueblue / white
26Rx -orangegreen
47white / brownwhite / brown
8brownbrown
32
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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).
The external voltage supply of the communication module is necessary if the power supply for the
basic device fails but communication via the fieldbus is to be maintained.
The parameters of a standard device separated from the mains cannot be accessed.
Wiring of the X258 plug connector
Stop!
Only wire the plug connector if the standard device is disconnected from the mains.
[5-11] Wiring of the 2-pin plug connector with spring connection
How to wire the plug connector with spring connection:
1. Press a screwdriver into the notch below the terminal and keep it pressed.
2. Place the supply cable in the terminal.
E84AYCXX010
3. Remove the screwdriver from the notch.
Assignment of the X258 plug connector
NameDescription
+U = 24 V DC (20.4 V - 0 % ... 28.8 V + 0 %)
I = 140 mA
-Reference potential for the external voltage supply
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1733
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.
In addition, there are codes for diagnosing and monitoring the stations.
Parameter reference
6.1Before initial switch-on
( 106)
Stop!
Before you switch on the Inverter Drive 8400 with the communication module for the
first time, check all the wiring for completeness, short-circuits and earth faults.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1735
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).
The configuration software is necessary for the programming of controller programs, EtherNet/IP
configuration, real-time execution and diagnostics.
The basic parameters of the communication module are stored in the internal configuration
memory and can be used for node detection by the scanner.
For node detection (fieldbus scan), the corresponding device descriptions of the Lenze device family
are used.
Tip!
Here you will find information on configuring with the »RSLogix 5000« programming
software from Rockwell:
I/O configuration with »RSLogix 5000« version 19 or lower
( 68)
I/O configuration with »RSLogix 5000« version 20 or higher
( 73)
36
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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.
The EDS file required for the configuration can be found in the download area at:
www.Lenze.com
Tip!
From version 20 onwards, Rockwell's »RSLogix 5000« programming software features an
"EDS Hardware Installation Tool" that can be used to ...
• install/import EDS files;
• create EDS files;
• carry out EDS uploads;
• delete EDS files from your controller project.
In »RSLogix 5000«, the dialog for the "EDS Hardware Installation Tool" is self-explanatory
and not described further in this documentation.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1737
6.2.2Example: 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.
To establish communication via an EtherNet/IP network, add the controller and its scanner to the I/
O configuration.
How to set the IP configuration of the 1769-L32E CompactLogix controller using the
»RSLogix 5000« programming software:
1. Click on the I/O Configuration folder in the configuration tree.
2. Right click on "1769-L32E Ethernet Port LocalENB" and select "Properties" from the context
menu.
3. Go to the General tab of the "Module Properties: ..." dialog window and enter the IP address
of the scanner.
4. Then click OK.
38
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
6.3Setting 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.
E84AYCEO004
[6-1]"IP ADR" rotary encoding switches
The inscription on the rotary coding switches corresponds to the valencies for determination of the
IP address.
The associated IP address of the communication module is the result of address setting by means of
the rotary encoder switches, e.g. IP address 192.168.100.[IP ADR]
In the default state, the rotary coding switches have been set to "0".
The rotary coding switch is re-evaluated when the following events occur:
• Type 0 reset service to the Identity Object (1 / 0x01)
• Type 1 reset service to the Identity Object (1 / 0x01)
• Switch the voltage supply for the communication module off and then on again.
The current value of the rotary coding switch is indicted in code C13920
( 126);
( 126);
.
40
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Page 41
6Commissioning
6.3Setting node addresses by means of rotary coding switches
6.4Setting 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. You can
assign these IP parameters for the Inverter Drive 8400 in the following ways:
• Setting via the EtherNet/IP configurator of the »Engineer«
• Setting via codes in the »Engineer«
• Setting via a BOOTP/DHCP server
• Setting via the TCP/IP Interface Object (0xF5)
( 45)
( 47)
( 47)
( 43)
Note!
• The assignment of invalid combinations of IP address, subnet mask, and gateway
address can have the consequence that no connection to the EtherNet/IP network can
be established.
•Codes C13010
C13016
• In the case of impermissible settings, the error message EtherNet/IP: Invalid IP
parameters [0x01bc6533] ( 99) is output.
(IP address), C13011 (subnet mask), C13012 (gateway address), and
(multicast IP address) show the IP parameters currently used.
42
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Page 43
6Commissioning
6.4Setting the IP configuration of the Inverter Drive 8400
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.
the IP address) from a server via a TCP/IP network. The BOOTP/DHCP server assigns the IP address
to the client dynamically from a defined address range. This means that the client receives an
unambiguous IP address.
Code C13005
• Value ’0’: The IP configuration currently saved in the communication module is used.
• Value ’1’: BOOTP is used. (Lenze standard setting)
• Value ’2’: DHCP is used.
The setting can also be selected by write access to attribute 3 (configuration control) of instance 1
of the TCP/IP Interface Object (245 / 0xF5)
is used to select how the IP configuration is to be made:
( 141).
6.4.4Setting via the TCP/IP Interface Object (0xF5)
With a scanner, the IP configuration can be set via attribute 5 (interface configuration) of instance 1
of the TCP/IP Interface Object (245 / 0xF5)
After the IP configuration, carry out a node reset ("power off/on" or "Type 0 reset" for the Identity
Object (1 / 0x01) ( 126)).
In the »Engineer«, codes C13010
and C13016
(multicast IP address) show the IP parameters currently used.
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).
By default, the communication module automatically generates the Multicast IP start address for I/
O data transfer. The standard TTL value for Multicast transfer is ’1’; the Multicast I/O data packages
are therefore distributed solely via the local network.
Note!
You can also explicitly set the multicast IP start address and the multicast TTL value. We
recommend, however, not to change the default settings in order to ensure a secure
multicast transmission.
The following multicast codes are configurable:
CodeDescription
C13018
C13019
C13020
Multicast IP Start Address
Multicast IP start addresses serve to send a message to the members of a certain group (i.e. possibly
to several nodes).
The multicast IP start address is set/changed in C13006
The currently used multicast IP address of the drive is displayed in C13016/1...4
Example: Display of the multicast IP address 239.64.2.224
CodeC13016/1
Value239642224
Selection for multicast IP addressing via instance attribute 9 (Mcast Config) in the TCP/IP
Interface Object (245 / 0xF5) ( 141)
• Value ’0’: The default algorithm is used.
• Value ’1’: The address from code C13006
Setting of the multicast TTL value for the validity time of data packets in the EtherNet/IP
network
(Instance attribute 8 (TTL Value) in the TCP/IP Interface Object (245 / 0xF5)
Used to set how many multicast IP addresses will be assigned.
(Instance attribute 9 (Num Mcast) in the TCP/IP Interface Object (245 / 0xF5)
C13016/2C13016/3C13016/4
is used as multicast IP start address.
( 141))
( 141))
.
.
48
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Page 49
6Commissioning
6.5Establishing an online connection via EtherNet/IP with the Lenze »Engineer«
6.5Establishing an online connection via EtherNet/IP with the Lenze »Engineer«
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.1Q-capable switch integrated in the communication module can
manage cyclical EtherNet/IP-communication primarily for normal TCP/IP
communication. In the case of EtherNet/IP, this is done by means of the VLAN
identification in the Ethernet frame (can be set in C13021
• If the redundancy protocol DLR (Device Level Ring) is used, the switch also must be
DLR-compliant.
).
[6-2]Example set-up with an Allen Bradley CompactLogix Controller 1769-L32E (scanner)
For an online connection between the »Engineer« and the drive, the drive must have an IP address
(see Setting the IP configuration of the Inverter Drive 8400
( 42)).
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1749
Page 50
6Commissioning
6.5Establishing 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 IP address of the drive selected in the
display field can be entered manually here.
Via the Search/Enter button, you can establish a connection to devices which have not
appeared in the display field. Corresponding settings for this can be made in the "Enter IP Address"
dialog window that will appear:
Here you can enter an IP address manually or execute the following actions using the buttons:
• Execute the console command Ping.
• Assign the IP address via the Configurator.
Setting via the EtherNet/IP configurator of the »Engineer«
( 43)
50
• Select the device access path to the desired drive by clicking Find.
After having established the online connection, you can continue work with the »Engineer« as
usual.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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.org
• Explicit messaging (for parameter data)
• Implicit messaging (for I/O data)
) and supports the two main types of EtherNet/IP communication:
52Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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. The data are transmitted via corresponding
communication channels depending on their time-critical behaviour.
The I/O data channel transmits I/O data by means of "implicit messages".
• The inverter is controlled by means of the I/O data.
• The transmission of I/O data is time-critical.
• I/O data are transmitted cyclically between the host system (scanner) and the drives (adapters)
(permanent exchange of current input and output data).
• The host system (scanner) has direct access to the I/O data (the data are, for example, stored
directly in the I/O area).
• In the case of Inverter Drives 8400, a maximum of 16 data words (max. 32 bytes) can be
exchanged per direction.
• I/O data are not stored in the inverter.
• I/O data are e.g. setpoints, actual values, control and status words
The parameter data channel transmits parameter data by means of "explicit messages".
• The transmission of parameter data is usually not time-critical.
• Examples of parameter data are operating parameters, motor data, and diagnostic information.
• The parameter data channel provides access to all Lenze codes.
• Parameter changes must be saved by means of code C00002 of the Inverter Drive 8400.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1753
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.
The "cyclic I/O data" transmission mode is supported. The scanner and the adapter use "cyclic I/O
data" to generate their data independently of each other, which are then transmitted depending on
a timer. The user must set the value of the timer in the scanner.
Explicit messages (parameter data transfer)
"Explicit messages" serve to configure and parameterise the individual EtherNet/IP nodes.
Two nodes have a client/server relationship:
The client transmits a job (request). The server receives this job and tries to accomplish it. The server
then transmits the requested data (positive response) or an error message (negative response).
54
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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.
The following drive profiles are supported by the Inverter Drives 8400:
The technology applications integrated in the drive provide the main signal flow for realising a
general or specific drive solution.
For using the Lenze technology application selection in the »Engineer« via standard device code
C00005, the following assembly object instances have to be used in the host (scanner):
Instance IDAssembly object instance
[dec][hex]
1100x6ECustom Output
(from the adapter to the scanner)
1110x6FCustom Input
(from the adapter to the scanner)
See also Assembly Object (4 / 0x04)
The custom assemblies also allow for a user-definable parameter setting, depending on the
application. 16 data words can be freely assigned with variables of the MCI port blocks in the
»Engineer«.
The user-definable parameter setting can be used in addition to the previously set technology
application.
"AC Drive Profile" application200x14Basic Speed Control Output
1100x6ECustom Output
1110x6FCustom Input
210x15Extended Speed Control Output
220x16Speed and Torque Control Output
230x17Extended Speed and Torque Control Output
700x46Basic Speed Control Input
710x47Extended Speed Control Input
720x48Speed and Torque Control Input
730x49Extended Speed and Torque Control Input
( 57)).
Assembly output objects (outputs) are usually used for controlling the enable/disable state of the
drive and for supplying the speed or torque references.
Assembly input objects (inputs) are usually used to monitor the drive status and the runtime values
such as actual speed, current, actual position and position error.
Depending on the data length defined by the scanner, the memory map of the I/O data can have
different sizes.
60
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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.
You can then define the bit 0 of this header in the process image of your PLC:
•0: Idle mode
• 1: Run mode
For the operation with Rockwell PLCs, adaptations are not required.
Assembly input objects (adapter scanner)
The assembly input objects are mapped in the adapter memory starting with byte 0.
The input objects are transmitted in a "modeless" manner, i.e. a 4-byte header (32-bit "Run/Idle
header") is not included in the transfer.
So the start address in the assembly memory map is the actual start of the first assembly data
element.
Please observe the actual assembly lengths when mapping the input objects to the controller
memory.
The contents of the input data depends on the I/O data arrangement in the drive (I/O data mapping
( 57)).
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1761
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.0 EN · 10/2013 · TD17
8.5I/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.
How to carry out the I/O configuration, taking the CompactLogix controller 1769-L32E
with »RSLogix 5000« as an example:
1. Click the I/O Configuration folder in the configuration tree.
For the 1769-L32E CompactLogix controller, the I/O configuration already includes a local
Ethernet port.
If a SoftLogic or ControlLogix controller is used, an Ethernet port scanner needs to be added
to the configuration.
68
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Page 69
8I/O data transfer (implicit messages)
8.5I/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.
Settings for Lenze technology applications or user-definable parameter sets:
If you use a Lenze technology application or an individual parameter set in the drive, you
can exchange up to 16 user-definable words (INT) via the ports MCI_IN and MCI_OUT using
the assembly object instances "Input = 111" and "Output = 110".
Go to "Configuration" and enter the Assembly instance "130" and the Size "0".
70
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Page 71
8I/O data transfer (implicit messages)
8.5I/O configuration with »RSLogix 5000« version 19 or lower
The assembly object instances "Input = 73" and "Output = 23" shown here
exemplify the use of the AC Drive Profile "Extended Speed and Torque".
SettingsDescription
NameDevice name or type of the drive, usually with reference to the process (in the
Comm FormatData format for the assembly object instances ("connection parameters" area)
IP AddressIP address of the drive
InputAssembly object instance for input objects
OutputAssembly object instance for output objects
ConfigurationSelect the Assembly instance "130" and the Size "0" for the configuration. These
example "My_E84AYCEO")
• The IP addres s must be in the same subnetwork like the controller. (Depending on
the subnet mask; in general, the first 3 octets of the IP address must be identical.)
• DNS is not supported; the host name merely describes the device.
• Max. 16 input data words (32 bytes, 16 bits/word)
• The number of input data must correspond to the length of the mapped ports in
the transmit PDO (PDO_TX0), otherwise the adapter will reject the connection
with the error message "Invalid Target to Originator Size" (0x0128).
I/O data mapping
• Max. 16 output data words (32 bytes, 16 bits/word)
• The number of output data must correspond to the length of the mapped ports
in the receive PDO (PDO_RX0), otherwise the adapter will reject the connection
with the error message "Invalid Originator to Target Size" (0x0127).
I/O data mapping
values are required!
( 57)
( 57)
6. Complete the settings with OK.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1771
Page 72
8I/O data transfer (implicit messages)
8.5I/O configuration with »RSLogix 5000« version 19 or lower
8.6I/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.
How to carry out the I/O configuration, taking the CompactLogix controller 1769-L32E
with »RSLogix 5000« as an example:
1. Use the "EDS Hardware Installation Tool" item to import the EDS files
EtherNet/IP nodes.
In »RSLogix 5000«, the dialog for the "EDS Hardware Installation Tool" is self-explanatory
and not described further in this documentation.
2. Click the I/O Configuration folder in the configuration tree.
( 37) of the
For the 1769-L32E CompactLogix controller, the I/O configuration already includes a local
Ethernet port.
If a SoftLogic or ControlLogix controller is used, an Ethernet port scanner needs to be added
to the configuration.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1773
Page 74
8I/O data transfer (implicit messages)
8.6I/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.
Settings for Lenze technology applications or user-definable parameter sets:
•Select "Exclusive Owner - Custom" connection.
If you use the Lenze technology applications or user-definable parameter sets in the
drive, the "Exclusive Owner - Custom" assembly object instance always has to be
selected.
•SetData type = INT.
The INT data type is exchanged via the ports MCI_IN and MCI_OUT of the Inverter Drives
8400. In case of the SINT data type, an additional PLC logic is required for conversion.
•SetTag Suffix = 1.
A tag suffix formulates a module-describing tag name.
76
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Page 77
8I/O data transfer (implicit messages)
8.6I/O configuration with »RSLogix 5000« version 20 or higher
• The drive is inserted in the configuration tree under the "I/O Configuration".
• The corresponding tags are created in the "Controller Tags".
• The example shows the ...
input assembly tags as "MY_EIP8400_FROM_EDS:I1";
output assembly tags as "MY_EIP8400_FROM_EDS:O1";
If you click the "+" in front of the assembly tag name, all data contained in the assembly
tags are shown below it. You can create "alias tags" to reference to single bits of the
assembly tag.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1779
Page 80
8I/O data transfer (implicit messages)
8.6I/O configuration with »RSLogix 5000« version 20 or higher
• NetCtrl (Bit 5) and NetRef (Bit 6) have to be set in order that the drive can receive
start/stop commands and speed/torque command via the network.
• In order to be able to use the torque control of the assembly object distance 23 (0x17),
the "DriveMode" attribute has to be written by means of explicit message
transmission.
Write "DriveMode" attribute
( 154)
Right-click an assembly tag and select the command "New Tag..." in the context menu.
80
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Page 81
8I/O data transfer (implicit messages)
8.6I/O configuration with »RSLogix 5000« version 20 or higher
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.
• The "Download" dialog box will open.
• If a message box reports that »RSLogix 5000« is unable to go online, select the menu
command Communications Communications Who Active and try to find your
controller in the "Who Active" dialog box. If the controller is not shown there, the
EtherNet/IP driver needs to be added to »RSLinx« or configured in »RSLinx«. For more
information, please refer to the »RSLinx« online help.
2. Click the Download button.
• The I/O configuration is downloaded to the controller.
• When the download has been successfully completed, »RSLogix 5000« changes to online
mode and the I/O OK box in the upper left of the screen is green.
3. Select the menu command File Save.
• If this is the first time the I/O configuration is saved, the "Save As" dialog box will open.
• Select a folder and enter a file name to save the configuration to a file on your computer.
• Finally, click the Save button.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1783
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. For other PLC types,
please consult the programming documentation for the corresponding PLC.
Note!
When you use several MSG BLOCKs per adapter, you can work resource-friendly by
sequential triggering and hold available enough communication reserves in the
EtherNet/IP module for further possible clients.
Application note
An example of parameter data transfer (read/write parameters) in a "AC Drive Profile"
application can be found in the download area (Application Knowledge Base) at
www.Lenze.com
.
84Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
In order to write data into code C00011 (reference speed) of the Inverter Drive 8400 by means of
explicit message transfer, for example, the following settings are necessary:
SettingsValue / description
Message Type"CIP Generic"
Service Type"Set Attribute Single" (service code "0x10")
Class"6E" (access to Lenze code)
Instance"11" = Lenze code C00011 of Inverter Drive 8400
Attribute"1" = Subcode of the Lenze code
• If the corresponding Lenze code does not have a subcode, the value ’1’
must be entered here.
• A display code cannot be configured by the "SET" service.
Source ElementVariable in the PLC program used as data source for writing.
Source LengthThe source length has to be set to the length (data type) of the current
parameter (see parameter reference in the software manual/online help of
the inverter).
For writing to code C00011, set the source length to "2 bytes".
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1785
In order to read out Lenze code C00011 (reference speed) of the Inverter Drive 8400 by means of
explicit message transfer, for example, the following settings are necessary:
SettingsValue / description
Message Type"CIP Generic"
Service Type"Get Attribute Single" (service code "0x0E")
Class"6E" (access to to Lenze code)
Instance"11" = Lenze code C00011 of Inverter Drive 8400
Attribute"1" = Subcode of the Lenze code
If the corresponding Lenze code does not have a subcode, the value ’1’ must
be entered here.
DestinationVariable in the PLC program the drive data will be copied to.
When reading code C00011, make sure that the tag used as destination is a
single word in UINT16 format.
86
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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.
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1787
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.
SettingsDescription
Idle ModeThe 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.
Run/Idle Flag (Bit 0) = FALSE:
• The I/O data are invalid and the response parameterised here (C13880/1
is executed on the drive.
• The I/O data are processed as set in (C13885
Overall Ethernet
Communication Timeout
Fault ModeThe adapter (communication module) monitors the I/O connection to the
Overall Ethernet Timeout Time Here, the overall message timeout time (C13881
Explicit Msg Timeout If no "explicit message" has been received within the timeout time for
Clear I/O Data(C13885
If there is no reception of explicit or implicit messages after expiry of the
time set in (C13881
after this time, the reaction parameterised here takes place in the drive
(C13880/4
Access to the web server is not monitored.
scanner.
If no "implicit message" has been received within the timeout time for
implicit messages parameterised by the scanner, the response
parameterised here (C13880/2
If no message has been received within this time, the response
parameterised in (C13880/4
The following messages are monitored:
• Implicit messages
• Explicit messages
• »Engineer« access via EtherNet/IP
explicit messages parameterised by the scanner, the response
parameterised here (C13880/3
maintain internal communication if ...
• the CIP network status (C13862
• an idle event has occurred.
).
), serves to set the I/O data to be processed by the adapter to
"Connected" or
) or if access via »Engineer« no longer takes place
) is executed on the drive.
) is executed.
) is executed on the drive.
) of the controlling I/O connection is not
).
) is set.
)
88Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
Module states are indicated by the ST, ER and DE LEDs.
E84AYCEO007_a
[11-1] LEDs ST, ER, DE
LEDColourStatusDescription
STGreenOn
The communication module is supplied with voltage and is connected to
the standard device.
Blinking
The communication module is supplied with voltage, but is not
connected to the standard device. (Standard device is switched off, in the
initialisation phase, or not available.)
ERRedOn
An error has occurred in the communication module.
DERedOn
The communication module is not accepted by the basic device or the
basic device is not active (see notes in the documentation relating to the
basic device.)
90
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
The communication module is not being supplied with voltage.
OffOn
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.
OffBlinking
CIP module status: "Major Recoverable Fault"
The communication module has a fault that can be rectified.
The status is set if the pending status determining device error shows
the "Fault", "Trouble", "Quick stop by trouble", "Warning locked", or
"Warning" response.
OnOff
CIP module status: "Operational"
The communication module is working perfectly.
BlinkingOff
CIP module status: "Standby"
BlinkingBlinking
The communication module has not been completely configured or the
configuration is defective.
CIP module status: "Device Self Testing"
The communication module is currently undergoing a self-test.
92
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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.1Short overview of the EtherNet/IP error messages
Software manual/»Engineer« online help for Inverter Drives 8400
Here you will find general information on diagnostics & fault analysis and on error
messages.
The following table lists all EtherNet/IP error messages in the numerical order of the error numbers.
Furthermore, the preset error response and - if available - the parameter for setting the error
response are specified.
Tip!
If you click on the cross-reference in the first column, you will get a detailed description
(causes and remedies) of the corresponding error message.
Error no.
[hex]
0x01bc3100
0x01bc5531
0x01bc5532
0x01bc5533
0x01bc6010
0x01bc6011
0x01bc6100
0x01bc6101
0x01bc641f
0x01bc6420
0x01bc6430
0x01bc6533
0x01bc8111
0x01bc8112 44433042EtherNet/IP: Explicit Message Timeout0: No ResponseC13880/3
0x01bc8114 44433044EtherNet/IP: Overall Ethernet Timeout0: No ResponseC13880/4
0x01bc8121 44433057EtherNet/IP: Ethernet cable pulled out1: No Response-
0x01bc8132
0x01bc8273 44433395EtherNet/IP: Duplicate IP Address1: No Response-
Subject area
no.
[dec]
44412544EtherNet/IP: Exist. connect. to 8400 lost0: No Response-
44421809EtherNet/IP: Memory: No Access1: No Response-
44421810EtherNet/IP: Memory: Read Error1: No Response-
44421811EtherNet/IP: Memory: Write Error1: No Response-
44424592EtherNet/IP: Restart by Watchdogreset1: No Response-
44424593EtherNet/IP: Internal Error1: No Response-
44424832EtherNet/IP: Internal Error1: No Response-
44424833EtherNet/IP: Internal Error1: No Response-
44425631EtherNet/IP: Invalid Parameter Set1: No Response-
44425632EtherNet/IP: Error: Lenze Setting Loaded1: No Response-
44425648EtherNet/IP: Invalid Configuration1: No Response-
44425907EtherNet/IP: Invalid IP Parameter1: No Response-
44433041EtherNet/IP: Fault Mode1: No ResponseC13880/2
44433074EtherNet/IP: Idle Mode0: No ResponseC13880/1
Error no.
[dec]
Error textError type
(Error response)
Adjustable
in
96
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD17
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. to 8400 lost [0x01bc3100]
Response (Lenze setting printed in bold)Setting: not possible
None System fault Fault Trouble Quick stop by trouble Warning locked Warning Information
CauseRemedy
• The communication module is being supplied with
external voltage but the Inverter Drive 8400 is not
being supplied with voltage.
• The communication module has not been correctly
connected to the Inverter Drive 8400.
EtherNet/IP: Memory: No Access [0x01bc5531]
• Supply the Inverter Drive 8400 with voltage.
• Securely connect the communication module to the
Inverter Drive 8400.
Response (Lenze setting printed in bold)Setting: not possible
None System fault Fault Trouble Quick stop b y trouble Warning locked Warning Information
CauseRemedy
Access to memory was not possible.Send communication module together with a
EtherNet/IP: Memory: Read Error [0x01bc5532]
Response (Lenze setting printed in bold)Setting: not possible
None System fault Fault Trouble Quick stop b y trouble Warning locked Warning Information
CauseRemedy
Parameter could not be read.• Download application again (including module).
EtherNet/IP: Memory: Write Error [0x01bc5533]
Response (Lenze setting printed in bold)Setting: not possible
None System fault Fault Trouble Quick stop b y trouble Warning locked Warning Information
CauseRemedy
Parameter could not be written.• Download application again (including module).
description of the fault to Lenze.
• Send communication module together with a
description of the fault to Lenze.
• Send communication module together with a
description of the fault to Lenze.
EtherNet/IP: Restart by Watchdogreset [0x01bc6010]
Response (Lenze setting printed in bold)Setting: not possible
None System fault Fault Trouble Quick stop b y trouble Warning locked Warning Information
CauseRemedy
Communication module is defective.Send communication module with error description to
Lenze · E84AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 10/2013 · TD1797