This documentation exclusively describes the EMF2191IB (POWERLINK) communication
module.
Note!
This documentation supplements the mounting instructions supplied with the
function/communication module and the documentation of the used
standard device.
The mounting instructions contain safety instructions which must be
observed!
The features and functions of the communication module are described in detail.
Examples illustrate typical applications.
Furthermore this documentation contains the following:
ƒ Safety instructions that must be observed.
ƒ Key technical data relating to the communication module
ƒ Information on versions of Lenze standard devices to be used.
ƒ Notes on troubleshooting and fault elimination
The theoretical correlations are only explained in so far as they are necessary for
comprehending the function of the communication module.
This documentation does not describe the software of an original equipment
manufacturer. No responsibility is taken for corresponding information given in this
manual. Information on how to use the software can be obtained from the documents of
the host system (master).
All brand names mentioned in this manual are trademarks of their respective companies.
Tip!
Detailed information about POWERLINK can be found on the website of the
"Ethernet POWERLINK Standardisation Group":
http://www.ethernet−powerlink.org
4
EDSMF2191IB EN 2.0
About this documentation1
Target group
This documentation is intended for all persons who plan, install, commission and maintain
the networking and remote service of a machine.
Tip!
Information and auxiliary devices related to the Lenze products can be found
in the download area at
http://www.Lenze.com
Validity information
The information in this documentation applies to the following devices:
Extension moduleType designationFrom hardware versionFrom software version
POWERLINK
communication module
EMF2191IBVA1.0
EDSMF2191IB EN 2.0
5
1
About this documentation
Document history
1.1Document history
VersionDescription
1.005/2008TD00First edition
2.009/2013TD17l Corrected information on cycle times ( 19)
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.
Your Lenze documentation team
l New chapter structure
6
EDSMF2191IB EN 2.0
1.2Conventions used
This documentation uses the following conventions to distinguish between different
types of information:
Type of informationIdentificationExamples/notes
Spelling of numbers
Decimal separator
DecimalStandard notationExample: 1234
Hexadecimal0x[0 ... 9, A ... F]Example: 0x60F4
Binary
l Nibble
Text
Program name» «PC software
Icons
Page referenceReference to another page with additional
Documentation referenceReference to another documentation with
About this documentation
Conventions used
PointIn general, the decimal point is used.
For instance: 1234.56
0b[0, 1]
Point
Example: ´0b0110´
Example: ´0b0110.0100´
For example: »Engineer«, »Global Drive
Control« (GDC)
information
For instance: 16 = see page 16
additional information
For example: EDKxxx = see
documentation EDKxxx
1
EDSMF2191IB EN 2.0
7
1
About this documentation
Terminology used
1.3Terminology used
TermMeaning
EPSGEthernet Powerlink Standardisation Group
Inverter
Standard device
Slave (CN)Controlled Node
Master (MN)Managing Node
Node IDPOWERLINK node address
MAC address
(MAC ID)
HWHardware
SWSoftware
User organisation which defines POWERLINK.
Inverter, the communication module can be used with ( 12).
POWERLINK node which is a slave in the real−time Ethernet
POWERLINK.
POWERLINK node which has the master function in the real−time
Ethernet POWERLINK.
Media Access Control address
The MAC address is unequivocal worldwide. The MAC address is
represented by six bytes in hexadecimal form the single bytes
being separated by dots. The first three bytes refer to the
manufacturer, the other bytes serve to identify the device.
8
EDSMF2191IB EN 2.0
1.4Notes used
The following pictographs and signal words are used in this documentation to indicate
dangers and important information:
Safety instructions
Structure of safety instructions:
Danger!
(characterises the type and severity of danger)
Note
(describes the danger and gives information about how to prevent dangerous
situations)
Pictograph and signal wordMeaning
Danger!
Danger!
Stop!
About this documentation
Notes used
Danger of personal injury through dangerous electrical voltage.
Reference to an imminent danger that may result in death or
serious personal injury if the corresponding measures are not
taken.
Danger of personal injury through a general source of danger.
Reference to an imminent danger that may result in death or
serious personal injury if the corresponding measures are not
taken.
Danger of property damage.
Reference to a possible danger that may result in property
damage if the corresponding measures are not taken.
1
Application notes
Pictograph and signal wordMeaning
Note!
Tip!
Important note to ensure troublefree operation
Useful tip for simple handling
Reference to another documentation
EDSMF2191IB EN 2.0
9
2
Safety instructions
General safety information
2Safety 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.1General safety information
Danger!
Disregarding the following basic safety measures may lead to severe personal
injury and damage to material assets!
ƒ Lenze drive and automation components ...
... must only be used for the intended purpose.
... must never be operated if damaged.
... must never be subjected to technical modifications.
... must never be operated unless completely assembled.
... must never be operated without the covers/guards.
... can − depending on their degree of protection − have live, movable or rotating parts
during or after operation. Surfaces can be hot.
ƒ For Lenze drive components ...
... only use permitted accessories.
... only use original manufacturer spare parts.
ƒ All specifications of the corresponding enclosed documentation must be observed.
This is vital for a safe and trouble−free operation and for achieving the specified product
features.
The procedural notes and circuit details provided in this document are proposals which
the user must check for suitability for his application. The manufacturer does not
accept any liability for the suitability of the specified procedures and circuit proposals.
ƒ Only qualified skilled personnel are permitted to work with or on Lenze drive and
automation components.
According to IEC 60364 or CENELEC HD 384, these are persons ...
... who are familiar with the installation, assembly, commissioning and operation of
the product,
... possess the appropriate qualifications for their work,
... and are acquainted with and can apply all the accident prevent regulations, directives
and laws applicable at the place of use.
10
EDSMF2191IB EN 2.0
Device− 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 in accordance with EN 61800−5−1 in every control cabinet (SELV/PELV).
ƒ Only use cables that meet the given specifications. ( 30)
Documentation of the standard device, control system, and plant/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
Safety instructions
2
Protection of persons
ƒ If controllers are connected to phase−earthed system with a rated mains voltage
400 V, external measures need to be implemented to provide reliable protection
against accidental contact. (see chapter "4.2", 18)
Device protection
ƒ The communication module contains electronic components that can be damaged
or destroyed by electrostatic discharge.
EDSMF2191IB EN 2.0
11
3
Product description
Application as directed
3Product description
3.1Application as directed
The communication module ...
ƒ is a device intended for use in industrial power systems;
ƒ can only be used in POWERLINK networks;
ƒ can be used together with the following standard devices (nameplate data):
Device typeDesign
82EVxxxxxBxxxXX Vx 1x8200 vector
82CVxxxxxBxxxXX Vx 1x8200 vector, cold plate
82DVxxxKxBxxxXX Vx 1x8200 vector, thermally
EPL 10200E 1x 1xDrive PLC
33.93XXxE. 2x 1xVxxx9321 − 9332 vector
33.938XxE. 1x 0x9381 − 9383 vector
33.93XXxC. 2x 1xVxxx9321 − 9332, with cold plate
(LED flashes once within a second.)
NMT_CS_PREOPERATIONAL_2 / NMT_MS_PREOPERATIONAL_2
(LED flashes twice within a second.)
NMT_CS_READY_TO_OPERATE / NMT_MS_READY_TO_OPERATE
(LED flashes three times within a second.)
NMT_CS_BASIC_ETHERNET
(LED is blinking with a frequency of 10 Hz or depending on the
connection state)
NMT_CS_STOPPED
(LED is blinking with a frequency of 2.5 Hz.)
NMT_CS_OPERATIONAL / NMT_MS_OPERATIONAL
(LED is lit permanently.)
(LED is lit permanently. An error has occurred.)
standard device (see documentation of the standard device).
(ACTIVITY).
16
EDSMF2191IB EN 2.0
General data and operating conditions
4Technical data
4.1General data and operating conditions
FieldValues
Order designationEMF2191IB
Communication profileEthernet POWERLINK V2
InterfaceRJ45, Fast Ethernet Mode MII (according to IEEE 802.3)
Communication mediumTP (100BaseTX, Cat5e)
Cable lengthmax. 100 m between 2 nodes / hubs
Total extensionNumber of nodes x 100 m
Network topologyTree, star, line
Transmission modeHalf duplex
Type of nodeSlave (CN, Controlled Node)
Node addressMax. 239
Conformities, approvalsl CE
l cUL
Baud rate100 Mbps
Voltage supplyExternal supply via separate power supply unit
+V =
−
24VDC(20.4 V − 0%... 28.8 V+ 0%)
I =
140 mA
Reference potential for external voltage supply
Technical data
4
Documentation for Lenze series of devices 8200 vector, 9300 and ECS
Here you can find the ambient conditions and the electromagnetic
compatibility (EMC) specifications applying to the communication module.
EDSMF2191IB EN 2.0
17
4
Technical data
Protective insulation
4.2Protective insulation
Danger!
Dangerous electrical voltage
If Lenze controllers 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.
Possible consequences:
ƒ Death or serious injury
Protective measures:
ƒ If protection against accidental contact is required for the control terminals
of the controller 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.
Insulation between bus and ...Type of insulation
(in accordance with EN 61800−5−1)
l Earth reference / PEFunctional insulation
l With external supplyFunctional insulation
l Power stage
Jitter synchronisation informationapprox. 1 s
Total cycle timesSlave (CN):1, 2, 3 60 ms
Buffer size
Frame sizeMax. asynchronous telegram size (MTU): 1518 bytes
SDO communication methodUDP/IP
Number of RPDOs3
RPDO user data per application (all
RPDOs)
Number of TPDOs1
TPDO user data per applicationmax. 32 objects with a total of max 64 bytes
Delay time
Tx−iso:max. 92 bytes (64 bytes of PDO user data)
Rx−iso:max. 328 bytes (300 bytes of PDO user data)
max. 32 objects with a total of max 64 bytes
T
− T
PReq
T
− T
SoA
Technical data
Data for POWERLINK communication
l The module can be operated with a minimum cycle of
1 ms.
l In multiplex mode, a minimum cycle of 200 sec is
supported if the data is accepted on the millisecond.
: 1900 ns
PRes
:1900 ns
ASnd
4
EDSMF2191IB EN 2.0
19
4
Technical data
Data for POWERLINK communication
Cycle time
4.3.1Cycle time
The cycle time of the communication system is the time in which all process data between
the master (managing node) and the slaves (controlled nodes) are exchanged.
It depends on the data of the communication system and can be calculated as follows e. g.
for a baud rate of 500 kbps:
t
+ 3, 35 @ 10*3(n ) 48 ) 3 BK) ) 0, 24 L ) 0, 2
zykl
The following diagram shows the relation between cycle time and number of connected
fieldbus nodes. The given values refer to the connection of Lenze inverters (e.g. 82xx) with
48 bits (1 parameter data word + 2 process data words).
Cycle time
[ms]
12
t
cycl
nSum of all data bits in the POWERLINK network
BKNumber of bus terminals
LLength of the remote bus cable [km]
Cycle time [ms]
10
8
6
4
2
1
10
Number of nodes
Fig. 4−1Relationship between cycle time and number of nodes
20
3040
4.3.2Processing time in the inverter
There are no interdependencies between parameter data and process data.
Processing timesParameter dataProcess data
Processing time inside the
inverter
Additional times outside
the inverter
l For controller−internal parameters
approx. 30 ms + a tolerance of 20 ms
l Some codes may have a longer
processing time (see documentation
of the inverter)
l Communication transfer times
l Communication processing times of the transmitting node
5060
l There is no synchronisation between
the communication module and the
inverter.
l Times of 8200 vector/motec,
starttec: Approx 3 ms + a tolerance of
2 ms
l Times of 9300 / ECS: Approx. 2 ms +
a tolerance of 1 ms (each being
independent of the basic cycle time)
20
EDSMF2191IB EN 2.0
4.4Dimensions
All dimensions in mm
Technical data
Dimensions
4
2191EPL001B
EDSMF2191IB EN 2.0
21
Installation5
5Installation
Danger!
Inappropriate handling of the communication module and the standard device
can cause serious personal injury and material damage.
Observe the safety instructions and residual hazards described in the
documentation for the standard device.
Stop!
The device contains components that can be destroyed by electrostatic
discharge!
Before working on the device, the personnel must ensure that they are free of
electrostatic charge by using appropriate measures.
22
EDSMF2191IB EN 2.0
5.1Mechanical installation
Fig. 5−1Attaching the communication module
ƒ Plug the communication module onto the standard device (here: 8200 vector).
ƒ Tighten the communication module to the standard device using the fixing screw in
order to ensure a good PE connection.
Installation
Mechanical installation
5
2102LEC014
Note!
For the internal supply of the communication module by the 8200 vector
frequency inverter the jumper has to be adjusted within the interface opening
(see illustration above).
Observe the notes ( 32).
EDSMF2191IB EN 2.0
23
5
5.2Electrical installation
5.2.1Wiring according to EMC (CE−typical drive system)
Installation
Electrical installation
Wiring according to EMC (CE−typical drive system)
For wiring according to EMC requirements observe the following points:
Note!
ƒ Separate control cables/data lines from motor cables.
ƒ Connect the shields of control cables/data lines at both ends in the case of
digital signals.
ƒ Use an equalizing conductor with a cross−section of at least 16mm
(reference:PE) to avoid potential differences between the bus nodes.
ƒ Observe the other notes concerning EMC−compliant wiring given in the
documentation for the standard device.
Wiring procedure
2
1. Comply with bus topology, thus do not use stubs.
2. Observe notes and wiring instructions in the documents for the control system.
3. Only use cables that comply with the given specifications ( 30).
4. Observe notes for the voltage supply of the module ( 32).
24
EDSMF2191IB EN 2.0
Installation
Electrical installation
Network topology
5
5.2.2Network topology
IP routing
IT integration (NAT)
Access protection
Ethernet
Protected segment (machine system)
EPL
router
Hub
max. 100 m
max. 100 m
Hub
Detailed information on this topic can be found in the Ethernet POWERLINK
brochure "Real−time Industrial Ethernet is reality"
EDSMF2191IB EN 2.0
25
5
Installation
Electrical installation
POWERLINK
5.2.3POWERLINK
POWERLINK network segment
Note!
Standard Ethernet nodes are not permitted in the POWERLINK network
segment.
In order to use the real−time capability of the POWERLINK technology, the POWERLINK
nodes must be interconnected in a separate network segment.
In accordance with the POWERLINK rules, only the network master (managing node)
controls the access of the slaves (controlled nodes) to the network. The network master is
the only node that transmits autonomously. All other nodes (controlled nodes) only
transmit when they are entitled to transmit by the master.
Non−POWERLINK nodes (e.g. PCs) typically violate these rules by sending frames
independently of the master. These frames interfere with the cyclic frame exchange of the
POWERLINK nodes and prevent the real−time capability of the POWERLINK.
Connection to the standard Ethernet network
The connection to an external standard Ethernet network is carried out via an Ethernet
POWERLINK router.
These infrastructure component separates the network traffic in the POWERLINK network
segment from the one in the standard Ethernet. The handling of the frames depend on
their direction:
ƒ Standard Ethernet −−−> POWERLINK network segment
Only frames that are addressed to nodes in the POWERLINK network segment are
forwarded. The forwarding takes place in the asynchronous area of the POWERLINK
cycle.
ƒ POWERLINK network segment −−−> Standard Ethernet
Only asynchronous frames that are not addressed to nodes in the POWERLINK network
segment are forwarded.
26
EDSMF2191IB EN 2.0
Installation
Electrical installation
POWERLINK
Topologies in the POWERLINK network segment
Note!
The use of class 1 hubs and switches inside the POWERLINK network segment
is not permitted.
Inside the segment only Ethernet hubs may be used as infrastructure elements. The hubs
must meet the requirements on class 2 repeaters acc. to IEEE 802.3u.
For this purpose, Lenze offers the dual hub integrated into the communication module and
the separate eight−fold hub, type E94AZCEH.
Class 1 hubs and switches are not permissible since they have considerably longer delay
times for the frame forwarding and a bigger jitter. Both sizes reduce the real−time
capability and dynamics.
The cable length between both nodes is limited to 100 m.
The topology rules (IEEE802.3u) required for controlling the collisions may be violated in
the POWERLINK network segment since according to the POWERLINK access order, frame
collisions are prevented. This enables a structure of lines and any hybrid forms between
star and line topology.
5
Recommended topology
For an easy configuration and due to many possible topology variants we recommend to
create networks according to the following rules:
1. Create slave groups with up to 10 nodes
2. Connect groups in star shape to the master (managing node).
3. For more than 2 groups: Use external 8−port hubs, e.g. Lenze hub E94AZCEH.
Exception: For maximally 2 groups, these are directly connected to the two ports of the
communication module.
Master
Hub
1. slave group
2. slave group
Fig. 5−2Star topology for 1 to 2 slave groups
EDSMF2191IB EN 2.0
4. Connect slave groups to the master via one external hub each.
– For max. 7 slave groups one hub is sufficient.
– For more than 7 slave groups, use further hubs.
– The groups can be distributed on the hubs just as you like.
27
5
5.2.4Operation in the standard Ethernet
Installation
Electrical installation
Operation in the standard Ethernet
Note!
Operation in the standard Ethernet does not permit any real−time
communication.
The communication module can be operated in the standard Ethernet for a basic
parameter setting provided that the following applies:
1. Operation of the module in slave mode:
– Network address 239
– IP address: 192.168.100.<EPL address>
2. Real time operation must not be carried out.
3. No integration of a master (EPL address 240) into the standard Ethernet network.
More notes on wiring
ƒ Do not wire, if possible, more than 9nodes in succession in a network line.
28
EDSMF2191IB EN 2.0
Installation
Electrical installation
POWERLINK connection
5
5.2.5POWERLINK connection
You can use a standard Ethernet patch cable for connecting the communication module
to the fieldbus (see "Ethernet cable specifications" ( 30)).
Note!
Plug/remove the Ethernet cable plug in a straight manner (at right angles)
into/from the socket to make sure that the RJ45 socket will not be damaged.
Pin assignment
RJ45 socketPINSignal
E94AYCXX004C
1Tx +
2Tx −
3Rx +
4−
5−
6Rx −
7−
8−
Tip!
The POWERLINK interfaces feature an auto MDIX function. This function
adjusts the polarity of the RJ45 interfaces so that a connection is established
irrespective of the polarity of the opposite POWERLINK interface, and
irrespective of the type of cable used (standard patch cable or crossover cable).
EDSMF2191IB EN 2.0
29
5
Installation
Electrical installation
Specification of the Ethernet cable
5.2.6Specification of the Ethernet cable
Note!
Only use cables complying with the below specifications.
Cable typeS/FTP (Screened Foiled Twisted Pair), ISO/IEC 11801 or EN 50173, CAT 5e
Damping23.2 dB (at 100 MHz and per 100 m)
Crosstalk damping24 dB (at 100 MHz and per 100 m)
Return loss10 dB (per 100 m)
Surge impedance100
Design of the Ethernet cable
Fig. 5−3Design of the Ethernet cable (S/FTP, CAT 5e)
ACable insulation
BBraid
CFoil shielding of the core pairs
TP1 ... TP4Twisted core pairs 1 ... 4
E94YCEP016
30
EDSMF2191IB EN 2.0
Colour code of Ethernet cable
Note!
Wiring and colour code are standardised in EIA/TIA 568A/568B.
You can use 4−pin Ethernet cables in accordance with the industrial standard.
The cable type only connects the assigned pins 1, 2, 3 and 6 with each other.
Installation
Electrical installation
Specification of the Ethernet cable
5
Fig. 5−4Ethernet plug in accordance with EIA/TIA 568A/568B
PairPinSignalEIA/TIA 568AEIA/TIA 568B
3
23Rx +White/orangeWhite/green
1
26Rx −OrangeGreen
4
1
2Tx −GreenOrange
4Not assignedBlueBlue
5Not assignedWhite/blueBlue/white
7Not assignedWhite/brownWhite/brown
8Not assignedBrownBrown
Tx +White/greenWhite/orange
E94YCEI004A
EDSMF2191IB EN 2.0
31
5
Installation
Electrical installation
Voltage supply
5.2.7Voltage supply
Internal voltage supply
Note!
Internal voltage supply has been selected in the case of standard devices with
an extended AIF interface opening (e.g. front of 8200 vector). The area shown
on a grey background in the graphic marks the jumper position.
ƒ By default, this is not supplied internally in the standard device.
ƒ For internal voltage supply place the jumper on the position indicated
below.
In the case of all other device series (9300, ECS), voltage is always supplied
from the standard device.
(Only external voltage supply possible.)
Lenze setting
Internal voltage supply
External voltage supply
Note!
In the case of an external voltage supply and for greater distances between
the control cabinets, always use a separate power supply unit (SELV/PELV) that
is safely separated in accordance with EN 61800−5−1 in each control cabinet.
The external voltage supply of the communication module ...
ƒ is required if communication via the fieldbus is to be continued when the supply of
the device fails.
ƒ is provided via the 2−pin terminal strip with screw−type connection (24 V DC):
TerminalDescription
+External voltage supply
U = 24VDC(20.4 V − 0%... 28.8 V +0%)
I = 85 mA
−Reference potential for external voltage supply
ƒ The parameters of a standard device disconnected from the mains cannot be
accessed.
32
EDSMF2191IB EN 2.0
Electrical installation
Terminal data
AreaValues
Electrical connectionPlug connector with screw connection
1.5 mm
with wire end ferrule, without plastic sleeve
1.5 mm
with wire end ferrule, with plastic sleeve
1.5 mm
(AWG 16)
2
(AWG 16)
2
(AWG 16)
2
(AWG 16)
Installation
Voltage supply
5
EDSMF2191IB EN 2.0
33
6
Commissioning
Before switching on
6Commissioning
During commissioning, system−dependent data as e.g. motor parameters, operating
parameters, responses and parameters for fieldbus communication are selected for the
controller.
In Lenze devices, this is done via codes. The codes are stored in numerically ascending order
in the Lenze controllers and in the plugged−in communication/function modules.
In addition to these configuration codes, there are codes for diagnosing and monitoring
the bus devices.
6.1Before switching on
Stop!
Before switching on the standard device with the communication module for
the first time, check the entire wiring for completeness, short circuit and earth
fault.
34
EDSMF2191IB EN 2.0
6.2Setting the node address
Note!
ƒ Use different node addresses for several networked inverters.
The Lenze setting for the node address (node ID) has the value ’4’:
– link switch in position ’0’
– right switch in position ’4’
ƒ Switch the voltage supply of the inverter/communication module off and
on again to activate changed settings.
Commissioning
Setting the node address
6
E94YCEP001D
Fig. 6−1Setting the node address
Each node has to be assigned to a unique address (node ID).
ƒ Valid address range for slave (controlled node): 1 ... 239
ƒ The corresponding IP address of the communication module results from the setting
of the two rotary switches.
IP address: 192.168.100.<Node ID>
The upgrade mechanism of the "Automation Studio" of the B & R company serves to establish an internet connection via which the necessary installation files are called.
After the upgrade, tick "display customised devices" in the hardware selection list to display the Lenze devices.
The following functions are available:
ƒ Adding Lenze devices to the hardware configuration
ƒ Setting node parameters (e.g. node ID)
ƒ I/O configuration (basic configuration settings of the controller)
ƒ Defining the I/O mapping (assignment of the process data objects of the controller
to the PLC objects)
The communication module is configured like a B & R device. The I/O configuration indicates the code which are compulsory for commissioning the inverter.
If further codes have to be written, library functions from the PLC project can be used. For
this purpose, you can find the "AsEPL" library in the "Library Manager". It provides the functions "EplSDOWrite" and "EplSDORead" which serve to read and write any parameters of
the device.
Indexing the Lenze codes
The index number is converted to a code as follows:
Conversion formula
Index (dec)Index (hex)
24575 − Lenze code0x5FFF − (Lenze code)
Example of C0001 (operating mode):
Index (dec)Index (hex)
24575 − 1 = 245740x5FFF − 1 = 0x5FFE
Further information on the "Automation Studio" functions can be found in the
corresponding documentation.
36
EDSMF2191IB EN 2.0
6.4Initial switch−on
Switch on the inverter and check whether it is ready for operation using the diagnostic
LEDs at the front of the communication module.
ƒ Red diagnostic LEDs must not be on.
ƒ The following signalling should be visible:
LED
Pos.ColourCondition
greenonThe communication module is supplied with voltage and is connected to
green
greenblinkingDepending on the connection state, the data is transmitted or received
yellowonEthernet connection is available (LINK).
Commissioning
Description
the standard device.
The NMT state machine triggers the two−colored LED:
l Green: Display of status messages
l Red: Display of error messages
NMT_CS_BASIC_ETHERNET
(LED is blinking with a frequency of 10 Hz or depending on the
connection state)
NMT_CS_OPERATIONAL / NMT_MS_OPERATIONAL
(LED is lit permanently.)
(ACTIVITY).
6
Initial switch−on
EDSMF2191IB EN 2.0
37
Diagnostics7
7Diagnostics
The LEDs on the front are provided to the communication module for the purpose of fault
diagnostics.
Displays
LED
Pos.ColourCondition
green
green
RedERROR
RedOnThe red and green drive LED indicates the operating status of the
greenblinkingDepending on the connection state, the data is transmitted or received
yellowonEthernet connection is available (LINK).
Description
offThe communication module is supplied with voltage, but has no
connection to the basic device (basic device is either switched off, in the
initialisation phase, or not available).
onThe communication module is supplied with voltage and is connected to
the standard device.
The NMT state machine triggers the two−colored LED:
l Green: Display of status messages
l Red: Display of error messages
(LED flashes once within a second.)
NMT_CS_PREOPERATIONAL_2 / NMT_MS_PREOPERATIONAL_2
(LED flashes twice within a second.)
NMT_CS_READY_TO_OPERATE / NMT_MS_READY_TO_OPERATE
(LED flashes three times within a second.)
NMT_CS_BASIC_ETHERNET
(LED is blinking with a frequency of 10 Hz or depending on the
connection state)
NMT_CS_STOPPED
(LED is blinking with a frequency of 2.5 Hz.)
NMT_CS_OPERATIONAL / NMT_MS_OPERATIONAL
(LED is lit permanently.)
(LED is lit permanently. An error has occurred.)
standard device (see documentation of the standard device).
(ACTIVITY).
38
EDSMF2191IB EN 2.0
8Appendix
8.1Index table
Overview
The following objects specified by the Ethernet POWERLINK communication profile are
supported.
Tip!
The Ethernet POWERLINK specification contains details on the POWERLINK
communication profile and can be obtained from the Ethernet POWERLINK
Standardisation Group (EPSG):
http://www.ethernet−powerlink.org
Appendix
Index table
8
EPL indexSubindexIndex nameMore information
0x1000NMT_DeviceType_U32 42
0x1001ERR_ErrorRegister_U8 42
0x1003ERR_History_ADOM−
0x1006NMT_CycleLen_U32 42
0x1008NMT_ManufactDevName_VS−
0x1009NMT_ManufactHwVers_VS−
0x100ANMT_ManufactSwVers_VS−
0x1010NMT_StoreParam_REC−
0x1011NMT_RestoreDefParam_REC−
0x10181 ... 4NMT_IdentityObject_REC 42
0x1020CFM_VerifyConfiguration_REC−
0x10301 ... 9NMT_InterfaceGroup_0h_REC 43
0x11011Dia_NMTTelegramCount_REC 43
0x14001 ... 2PDO_RxCommParam_00h_REC 43
0x14011 ... 2PDO_RxCommParam_01h_REC 44
0x14021 ... 2PDO_RxCommParam_02h_REC 44
0x16001 ... 20PDO_RxMappParam_00h_REC 44
0x16011 ... 20PDO_RxMappParam_01h_REC 45
0x16021 ... 20PDO_RxMappParam_02h_REC 45
0x18001 ... 2PDO_TxCommParam_00h_REC−
0x1A001 ... 20PDO_TxMappParam_00h_REC 46
0x1C0ADLL_CNCollision_REC 46
0x1C0BDLL_CNLossSoC_REC 46
0x1C0CDLL_CNLossSoA_REC−
0x1C0DDLL_CNLossPReq_REC−
0x1C0EDLL_CNSoCJitter_REC−
0x1C0FDLL_CNCRCError_REC 47
0x1C10DLL_CNLossOfLinkCum_U32 47
0x1C13DLL_CNSoCJitterRange_U32−
EDSMF2191IB EN 2.0
39
8
Appendix
Index table
More informationIndex nameSubindexEPL index
0x1C14DLL_LossOfFrameTolerance_U32−
0x1E401 ... 5NWL_IpAddrTable_0h_REC 48
0x1E4A1 ... 3NWL_IpGroup_REC−
0x1F50PDL_DownloadProgData_ADOM−
0x1F51PDL_ProgCtrl_AU8−
0x1F52PDL_LocVerApplSw_REC−
0x1F811 ... 64NMT_NodeAssignment_AU32 49
0x1F82NMT_FeatureFlags_U32 50
0x1F83NMT_EPLVers_U8 50
0x1F8CNMT_CurrState_U8 51
0x1F8D1 ... 64NMT_MNPResPayloadList_AU32 51
0x1F931 ... 2NMT_EPLNodeID_REC 51
0x1F981 ... 9NMT_CycleTiming_REC−
0x1F99NMT_CNBasicEthernetTimeout_U32 51
0x1F9ANMT_HostName_VSTR 52
0x1F9ENMT_ResetCmd_U8 52
40
EDSMF2191IB EN 2.0
Appendix
Index table
How to read the index table
Model of an index table
IndexName
SubcodeLenzeValuesData type
Access:
Meaning
HeaderMeaning
IndexNumber of the Ethernet POWERLINK index I−xxxx
NameDisplay text
8
Leading
columns
SubcodeNumber of the subcode
Lenze
Values
Data type
FooterMeaning
Accessro: The parameter can only be read (display code)
Meaning
Lenze setting ("Default" setting) of the code
à Display code
The code cannot be configured.
Minimum value[smallest increment/unit]Maximum value
In case of a display code the displayed values are specified.
l BITFIELD_8
l BITFIELD_32
l U88 bit value without sign
l U1616 bit value without sign
l U3232 bit value without sign
l U6464 bit value without sign
l VSVisible String, string with specified length
rw: The parameter can be changed
EDSMF2191IB EN 2.0
41
8
Appendix
Index table
I−1000:
EPL device type
Index
0x1000
SubcodeLenzeValuesData type
−
EPL name
NMT_DeviceType_U32
U32
Access: ro
The object displays the device type of the node.
I−1001:
EPL error register
Index
0x1001
SubcodeLenzeValuesData type
−
EPL name
ERR_ErrorRegister_U8
U8
Access: ro
The object contains currently pending errors arranged according to error classes. The bits
of the error register have the following meaning:
BitDescription
0Generic error, signals an existing error message in the CN which can be read out via StatusResponse
1Amperage
2Voltage
3Temperature
4Communication error
5Device profile−related error
6Reserved (0)
7Manufacturer−specific error
I−1006:
EPL cycle time
Index
0x1006
SubcodeLenzeValuesData type
−11 ... [1 ms] ... 20U32
EPL name
NMT_CycleLen_U32
Access: rw
The object contains the length of the EPL cycle in [s].
I−1018:
EPL identity object
Index
0x1018
SubcodeLenzeValuesData type
1: VendorId_U320x59
2: ProductCode_U322191
3: RevisionNo_U320x00000000
4: SerialNo_U32
EPL name
NMT_IdentityObject_REC
U32
Access: ro
The object contains identification information on the communication module.
Access: ro for subcodes 1, 2, 3, 4, 5
and 7
Access: rw for subcode 6
The object contains information on the Ethernet interface. The subcode 5 contains the
MAC address. When the communication module is produced, the MAC address is assigned
unequivocally worldwide and provides addressing on the lowest level.
I−1101:
EPL telegram counter
Index
0x1101
SubcodeLenzeValuesData type
1: IsochrCyc_U32−−U32
EPL name
DIA_NMTTelegrCount_REC
Access: ro
Subcode 1 of the object contains a counter for POWERLINK cycles. The counter is started
with each power−on of the node at 0. An overflow occurs at 4.294.967.295.
I−1400:
EPL address : RPDO
Index
0x1400
SubcodeLenzeValuesData type
100, 1 ... 240, 253, 254U8
EPL name
PDO_RxCommParam_XXh_REC.NodeID_U8
Access: rw
Subcode 1 of the object contains the node address (node ID) of the transmitting node for
the PDO channel (n+1).
Values > ’0’ describe the origin of a PRes telegram. The value ’0’ is reserved for "PReq"
(cannot be used in systems with a Lenze Servo Drive 9400 as managing node).
The value is only valid if the corresponding object 0x160x has a value > ’0’.
EDSMF2191IB EN 2.0
43
8
Appendix
Index table
I−1401:
EPL address : RPDO
Index
0x1401
SubcodeLenzeValuesData type
100, 1 ... 240, 253, 254U8
EPL name
PDO_RxCommParam_XXh_REC.NodeID_U8
Access: rw
Subcode 1 of the object contains the node address (node ID) of the transmitting node for
the PDO channel (n+1).
Values > ’0’ describe the origin of a PRes telegram. The value ’0’ is reserved for "PReq"
(cannot be used in systems with a Lenze Servo Drive 9400 as managing node).
The value is only valid if the corresponding object 0x160x has a value > ’0’.
I−1402:
EPL address : RPDO
Index
0x1402
SubcodeLenzeValuesData type
100, 1 ... 240, 253, 254U8
EPL name
PDO_RxCommParam_XXh_REC.NodeID_U8
Access: rw
Subcode 1 of the object contains the node address (node ID) of the transmitting node for
the PDO channel (n+1).
Values > ’0’ describe the origin of a PRes telegram. The value ’0’ is reserved for "PReq"
(cannot be used in systems with a Lenze Servo Drive 9400 as managing node).
The value is only valid if the corresponding object 0x160x has a value > ’0’.
I−1600:
EPL number of RPDO
Index
0x1600
SubcodeLenzeValuesData type
000, 1 ... 32U64
EPL name
PDO_RxMappParam_xxh_AU64.NumberOfEntries
Access: rw
The object describes the number of valid mapping entries for the PDO channel (n+1).
The value ’0’ inhibits the PDO channel. The sum of all mapping entries enabled via the
objects 0x160x must not exceed the value ’64’.
44
EDSMF2191IB EN 2.0
I−1601:
EPL number of RPDO
Appendix
Index table
8
Index
0x1601
SubcodeLenzeValuesData type
000, 1 ... 32U64
EPL name
PDO_RxMappParam_xxh_AU64.NumberOfEntries
Access: rw
The object describes the number of valid mapping entries for the PDO channel (n+1).
The value ’0’ inhibits the PDO channel. The sum of all mapping entries enabled via the
objects 0x160x must not exceed the value ’64’.
I−1602:
EPL number of RPDO
Index
0x1602
SubcodeLenzeValuesData type
000, 1 ... 32U64
EPL name
PDO_RxMappParam_xxh_AU64.NumberOfEntries
Access: rw
The object describes the number of valid mapping entries for the PDO channel (n+1).
The value ’0’ inhibits the PDO channel. The sum of all mapping entries enabled via the
objects 0x160x must not exceed the value ’64’.
EDSMF2191IB EN 2.0
45
8
Appendix
Index table
I−1A00:
EPL TPDO
Index
0x1A00
SubcodeLenzeValuesData type
1 ... 32: ObjectMapping−see belowU64
EPL name
PDO_TxMappParam_00h_AU64
Access: rw
The object describes the mapping for the TPDO channel. Subcode 0 describes the number
of valid mapping object entries. Subcodes 1 to 32 describe the mapping of the individual
objects.
The entry is structured as follows:
ByteNameDescription
0, 1IndexEPL index of the mapped object
2SubindexSubindex
3Reserved
4, 5OffsetOffset, calculated from the start of the PDO user data [bits]
6, 7LengthLength of the mapped object [bits]
I−1C0A:
EPL CN: Telegr. collisions
Index
0x1C0A
SubcodeLenzeValuesData type
1: CumulativeCnt_U32−−U32
EPL name
DLL_CNCollision_REC
Access: ro
The object indicates the number of Ethernet collisions detected by the slave (controlled
node).
Each event is counted. Every single event is followed by an error message. No threshold
value management is implemented.
I−1C0B:
EPL CN: Loss of synchr.
Index
0x1C0B
SubcodeLenzeValuesData type
1: CumulativeCnt_U32−−
2: ThresholdCnt_U32−−
3: Threshold_U3210, 1, 2 etc.
EPL name
DLL_CNCollision_REC
U32
Access: see below
The slave (controlled node) expects SoC frames in time intervals which correspond to the
cycle time.
The object indicates the error counters for missing SoC frames.
46
EDSMF2191IB EN 2.0
I−1C0F:
EPL CN: Frame error (CRC)
Appendix
Index table
8
Index
0x1C0F
SubcodeLenzeValuesData type
1: CumulativeCnt_U32−−U32
2: ThresholdCnt_U3200, 1, 2, 3 ...U32
3: Threshold_U3200, 1, 2, 3 ...U32
EPL name
DLL_CNCRCError_REC
Access:
Subcode 3: rw , otherwise ro
The object indicates the number of frame checksum errors detected by the slave
(controlled node).
I−1C10:
EPL CN: Link interruptions
Index
0x1C10
SubcodeLenzeValuesData type
−−−U32
EPL name
DLL_CNLossOfLinkCum_U32
Access: ro
The object indicates the counter of the slave (controlled node) for Ethernet connection
interruptions.
Each event is counted. Every single event is followed by an error message. No threshold
value management is implemented.
EDSMF2191IB EN 2.0
47
8
Appendix
Index table
I−1E40:
EPL IP address
Index
0x1E40
SubcodeLenzeValuesData type
2
3
50xC0A864FE−
ƒ Subcode 2:
EPL name
NWL_IpAddrTable_0h_REC.Addr_IPAD
−
−
U32
Access: ro
The subcode contains the IP address of the communication module. It is derived
according to the following rule from the node address (node ID, I−1F93):
192.168.100.<I−1F93>
ƒ Subcode 3:
The subcode contains the IP subnet mask which limits the IP address range that can be
addressed directly (i.e. without using a gateway in the EPL segment of the routers). In
an EPL segment, the subnet mask is permanently assigned to the value
’255.255.255.0’ (0xFFFFFF00).
ƒ Subcode 5:
The subcode contains the IP address of the EPL router via which the EPL segment is
connected to the higher−level network.
The standard entry corresponds to the standard router address of the POWERLINK
specification:
192.168.100.254
Permissible entries replace the lowest−order byte of the standard entry with the EPL
address of the node which has the function of a router.
48
EDSMF2191IB EN 2.0
I−1F81:
EPL node declaration CN
Appendix
Index table
8
Index
0x1F81
SubcodeLenzeValuesData type
EPL name
NMT_NodeAssignment_AU32
see tableU32
Access: rw
The object describes the slave (controlled node) and its properties.
The describing bit field has the following structure:
Relevance
Bit
0 (LSB)þþ0, 10Node with this ID does not exist
1þþ0, 10Node with this ID is no CN
2þ¨10
3þþ10optional CN.
4þ¨0
5þ¨00Application SW version verification is not required
6þ¨0, 10Automatic application SW update is not allowed
7−−0−Reserved
8þþ0, 10Isochronously accessed CN.
9þþ00Continuously accessed CN
10 ... 30−−0−Reserved
31 (MSB)þþ0, 10Bit 0 .. 30 inhibited
*)
Not permissible for Servo Drives 9400
MNCN
LenzeValueDescription
1Node with this ID exists
1Node with this ID is a CN
*)
starting CNs are not automatically booted
1starting CNs are automatically booted
1obligatory CN.
0
1
1
1Automatic application SW update is allowed
1AsyncOnly CN, bit 9 irrelevant
1
1Bit 0 .. 30 enabled
CN can be reset independently of the current state using the
NMTResetCommunication command
*)
CN must not be reset when being in the NMT_CS_OPERATIONAL state
*)
Application SW version verification is required
*)
Multiplex CN
EDSMF2191IB EN 2.0
49
8
Appendix
Index table
I−1F82:
EPL feature flags
Index
0x1F82
SubcodeLenzeValuesData type
−
EPL name
NMT_FeatureFlags_U32
U32
Access: ro
The object indicates the POWERLINK functions implemented by the slave (controlled
node).
The describing bit field has the following structure:
Relevance
Bit
0¨þIsochronous access is allowedOnly AsyncOnly access
1þþSDO via UDP/IPNo SDO by UDP/IP
2þþSDO via EPL ASnd
3þþSDO integrated in PDONo SDO integrated in PDO
4þþSupport NMT Info ServicesNo NMT Info Services
5þþSupport of extended NMT State CommandsNo extended NMT State Commands
6þþSupport of dynamic PDO mappingNo dynamic PDO mapping
7þ¨NMT services via UDP/IPNo NMT services via UDP/IP
8þþConfiguration manager functionNo configuration manager function
9þþIsochronous multiplex access is possibleOnly isochronous cyclic access is allowed
10¨þAddress assignment via SWNo address assignment via SW
11þ¨Support of basic Ethernet mode of the masterNo support of basic Ethernet mode of the master
12þþDevice can be used as Powerlink to standard Ethernet
13þþDevice can be used as Powerlink to fieldbus routerDevice does not support any Powerlink to fieldbus
14 ... 31−−Reserved (these bits are assigned to FALSE)−
MNCN
TRUEFALSE
(only MN for Servo Drives 9400)
router
No SDO via EPL ASnd
(only CN for Servo Drives 9400)
Device does not support any Powerlink to standard
Ethernet function
router function
I−1F83:
EPL version
Index
0x1F83
SubcodeLenzeValuesData type
−
EPL name
NMT_EPLVers_U8
0x20U8
Access: ro
The object describes the version of the Ethernet POWERLINK communication profile
implemented by the communication module.
The higher−order nibble describes the major version, the lower order nibble describes the
minor version. The implemented value corresponds to the EPL version 2.0.
50
EDSMF2191IB EN 2.0
I−1F8C:
EPL communication status
Appendix
Index table
8
Index
0x1F8C
SubcodeLenzeValuesData type
−
EPL name
NMT_CurrNMTState_U8
see table
Access: ro
The object contains the current NMT state.
I−1F8D:
EPL CN: Max. user data PRes RPDO
Index
0x1F8D
SubcodeLenzeValuesData type
1 ... 10036 bytessee description, unit: ByteU16
EPL name
NMT_PResPayloadList_AU16
Access: rw
This object defines the reserved user data length of the PRes frames.
Each subcode corresponds to a node with the same node ID. The node must have been
enabled via the object 0x1F81. The subcode describes the received PRes frames.
The value must be within the range of 36 ... 1490 bytes. The values are limit values for the
total sizes of the PDO mappings to be defined for received PRes frames.
I−1F93:
EPL device address
Index
0x1F93
SubcodeLenzeValuesData type
−−1 .. 239U8
EPL name
NMT_EPLNodeID_REC.NodeID_U8
Access: ro
The object contains the currently valid node address (node ID).
I−1F99:
EPL CN: Max. MN detection time
Index
0x1F99
SubcodeLenzeValuesData type
−5000000 s0 ... 50000000 sU32
EPL name
NMT_CNBasicEthernetTimeout_U32
Access: rw
The object contains a time interval for a booting slave (controlled node) for detecting a
master (managing node). If a booting slave (controlled node) detects a master (managing
node) during the interval, it changes to NMT_CS_PREOPERATIONAL_1. If not, it changes to
"Basic Ethernet Mode".
EDSMF2191IB EN 2.0
51
8
Appendix
Index table
I−1F9A:
EPL host name
Index
0x1F9A
SubcodeLenzeValuesData type
−−see "naming convention"VS15
EPL name
NMT_Hostname_VSTR
Access: rw
The object contains a DNS−compatible device name. The length is limited to 15 characters.
Naming convention:
ƒ The device name ...
– starts with a letter;
– ends with a letter or a digit.
ƒ The device name consists of ...
– letters (A .. Z), upper or lower case,
– digits (0 .. 9),
– hyphen (−).
Note!
The device name must be unambiguous within the network domain.
I−1F9E:
EPL reset command
Index
0x1F9E
SubcodeLenzeValuesData type
−see tableU8
EPL name
NMT_ResetCmd_U8
Access: wo
The object initiates a reset of the node. The following reset commands are available: