Lenze EMF2191IB Bedienungsanleitung

EDSMF2191IB.M\}Ä.M\}äCommunication ManualPOWERLINK EMF2191IBCommunication moduleL−force Communication

Safety instructionsGeneral safety information2 10EDSMF2191IB EN 2.02 Safety instructions Note!It is absolutely vital that the stated safety measur

Safety instructionsDevice− and application−specific safety instructions2 11EDSMF2191IB EN 2.02.2 Device− and application−specific safety instruct

Product descriptionApplication as directed3 12EDSMF2191IB EN 2.03 Product description3.1 Application as directed The communication module ...ƒ is

Product descriptionIdentification3 13EDSMF2191IB EN 2.03.2 IdentificationE82AF000P0B201XXLTypeId.-No.Prod.-No.MAC-ID2191EPL013  33.2191IB V

Product descriptionProduct features3 14EDSMF2191IB EN 2.03.3 Product featuresƒ Powerful and real−time capable communication system for motion and g

Product descriptionConnections and interfaces3 15EDSMF2191IB EN 2.03.4 Connections and interfaces2191EPL001BConnectionsPos. DescriptionPOWERLIN

Product descriptionConnections and interfaces3 16EDSMF2191IB EN 2.0DisplaysLEDDescriptionPos. Colour Condition greenoff The communication module i

Technical dataGeneral data and operating conditions4 17EDSMF2191IB EN 2.04 Technical data4.1 General data and operating conditions Field Values

Technical dataProtective insulation4 18EDSMF2191IB EN 2.04.2 Protective insulation Danger!Dangerous electrical voltageIf Lenze controllers are use

Technical dataData for POWERLINK communication4 19EDSMF2191IB EN 2.04.3 Data for POWERLINK communicationField ValuesJitter synchronisation inform

Contentsi 2EDSMF2191IB EN 2.01 About this documentation 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical dataData for POWERLINK communicationCycle time4 20EDSMF2191IB EN 2.04.3.1 Cycle timeThe cycle time of the communication system is the tim

Technical dataDimensions4 21EDSMF2191IB EN 2.04.4 Dimensions2191EPL001BAll dimensions in mm

Installation5 22EDSMF2191IB EN 2.05 Installation Danger!Inappropriate handling of the communication module and the standard devicecan cause seriou

InstallationMechanical installation5 23EDSMF2191IB EN 2.05.1 Mechanical installation2102LEC014Fig. 5−1 Attaching the communication moduleƒ Plug t

InstallationElectrical installationWiring according to EMC (CE−typical drive system)5 24EDSMF2191IB EN 2.05.2 Electrical installation5.2.1 Wiring a

InstallationElectrical installationNetwork topology5 25EDSMF2191IB EN 2.0 5.2.2 Network topology IP routingIT integration (NAT)Access protectionE

InstallationElectrical installationPOWERLINK5 26EDSMF2191IB EN 2.0 5.2.3 POWERLINKPOWERLINK network segment Note!Standard Ethernet nodes are not p

InstallationElectrical installationPOWERLINK5 27EDSMF2191IB EN 2.0Topologies in the POWERLINK network segment Note!The use of class 1 hubs and s

InstallationElectrical installationOperation in the standard Ethernet5 28EDSMF2191IB EN 2.05.2.4 Operation in the standard Ethernet Note!Operation

InstallationElectrical installationPOWERLINK connection5 29EDSMF2191IB EN 2.0 5.2.5 POWERLINK connection You can use a standard Ethernet patch c

Contents i 3EDSMF2191IB EN 2.06 Commissioning 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

InstallationElectrical installationSpecification of the Ethernet cable5 30EDSMF2191IB EN 2.0 5.2.6 Specification of the Ethernet cable  Note!Only

InstallationElectrical installationSpecification of the Ethernet cable5 31EDSMF2191IB EN 2.0 Colour code of Ethernet cable Note!Wiring and colou

InstallationElectrical installationVoltage supply5 32EDSMF2191IB EN 2.0 5.2.7 Voltage supply Internal voltage supply Note!Internal voltage supply

InstallationElectrical installationVoltage supply5 33EDSMF2191IB EN 2.0Terminal dataArea ValuesElectrical connection Plug connector with screw co

CommissioningBefore switching on6 34EDSMF2191IB EN 2.06 Commissioning During commissioning, system−dependent data as e.g. motor parameters, operati

CommissioningSetting the node address6 35EDSMF2191IB EN 2.06.2 Setting the node address  Note!ƒ Use different node addresses for several networ

CommissioningConfiguration via the "Automation Studio"6 36EDSMF2191IB EN 2.06.3 Configuration via the "Automation Studio"The up

CommissioningInitial switch−on6 37EDSMF2191IB EN 2.06.4 Initial switch−onSwitch on the inverter and check whether it is ready for operation using

Diagnostics7 38EDSMF2191IB EN 2.07 DiagnosticsThe LEDs on the front are provided to the communication module for the purpose of faultdiagnostics.Di

AppendixIndex table8 39EDSMF2191IB EN 2.08 Appendix8.1 Index tableOverviewThe following objects specified by the Ethernet POWERLINK communication

About this documentation1 4EDSMF2191IB EN 2.00Fig. 0Tab. 01 About this documentationContentsThis documentation exclusively describes the EMF2191IB

AppendixIndex table8 40EDSMF2191IB EN 2.0More informationIndex nameSubindexEPL index0x1C14 DLL_LossOfFrameTolerance_U32 −0x1E40 1 ... 5 NWL_IpAddrT

AppendixIndex table8 41EDSMF2191IB EN 2.0 How to read the index tableModel of an index tableIndex NameSubcode Lenze Values Data typeAccess:Meanin

AppendixIndex table8 42EDSMF2191IB EN 2.0 I−1000: EPL device type Index0x1000EPL nameNMT_DeviceType_U32Subcode Lenze Values Data type−U32Access:

AppendixIndex table8 43EDSMF2191IB EN 2.0I−1030: EPL MAC address Index0x1030EPL nameNMT_InterfaceGroup_0h_RECSubcode Lenze Values Data type1: In

AppendixIndex table8 44EDSMF2191IB EN 2.0I−1401: EPL address : RPDO Index0x1401EPL namePDO_RxCommParam_XXh_REC.NodeID_U8Subcode Lenze Values Data

AppendixIndex table8 45EDSMF2191IB EN 2.0I−1601: EPL number of RPDO Index0x1601EPL namePDO_RxMappParam_xxh_AU64.NumberOfEntriesSubcode Lenze Val

AppendixIndex table8 46EDSMF2191IB EN 2.0 I−1A00: EPL TPDO Index0x1A00EPL namePDO_TxMappParam_00h_AU64Subcode Lenze Values Data type1 ... 32: Obje

AppendixIndex table8 47EDSMF2191IB EN 2.0I−1C0F: EPL CN: Frame error (CRC) Index0x1C0FEPL nameDLL_CNCRCError_RECSubcode Lenze Values Data type1:

AppendixIndex table8 48EDSMF2191IB EN 2.0I−1E40:EPL IP address Index0x1E40EPL nameNWL_IpAddrTable_0h_REC.Addr_IPADSubcode Lenze Values Data type2

AppendixIndex table8 49EDSMF2191IB EN 2.0 I−1F81: EPL node declaration CN Index0x1F81EPL nameNMT_NodeAssignment_AU32Subcode Lenze Values Data ty

About this documentation 1 5EDSMF2191IB EN 2.0 Target groupThis documentation is intended for all persons who plan, install, commission and maint

AppendixIndex table8 50EDSMF2191IB EN 2.0 I−1F82: EPL feature flags Index0x1F82EPL nameNMT_FeatureFlags_U32Subcode Lenze Values Data type−U32Acce

AppendixIndex table8 51EDSMF2191IB EN 2.0I−1F8C: EPL communication status Index0x1F8CEPL nameNMT_CurrNMTState_U8Subcode Lenze Values Data type−

AppendixIndex table8 52EDSMF2191IB EN 2.0I−1F9A: EPL host name Index0x1F9AEPL nameNMT_Hostname_VSTRSubcode Lenze Values Data type−−see "namin

Index 953EDSMF2191IB EN 2.09 IndexAAddress settings, 35Application as directed, 12Automation Studio, configuration, 36BBaud rate, 17CCable sp

Index954EDSMF2191IB EN 2.0HHardware version, type code, 13II−1000: EPL device type, 42I−1001: EPL error register, 42I−1006: EPL cycle time, 42I

Index 955EDSMF2191IB EN 2.0TTechnical data, 17Terminal data, 33Topologies in the POWERLINK network segment, 27Transmission mode, 17Type code,

© 09/2013FLenze Automation GmbHHans−Lenze−Str. 1D−31855 AerzenGermanyService Lenze Service GmbHBreslauer Straße 3D−32699 ExtertalGermany(+49(0)51 54

About this documentationDocument history1 6EDSMF2191IB EN 2.01.1 Document historyVersion Description1.0 05/2008 TD00 First edition2.0 09/2013 TD17

About this documentationConventions used1 7EDSMF2191IB EN 2.01.2 Conventions usedThis documentation uses the following conventions to distinguish

About this documentationTerminology used1 8EDSMF2191IB EN 2.01.3 Terminology usedTerm MeaningEPSG Ethernet Powerlink Standardisation GroupUser orga

About this documentationNotes used1 9EDSMF2191IB EN 2.01.4 Notes usedThe following pictographs and signal words are used in this documentation to