Lenze E84DGFCG User Manual

Download

Accessories

EtherNet/IP™

Inverter Drives 8400 motec

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

E84DGFCGxxx

Communication Manual EN

Ä.MM@ä

13444431

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

1 About this documentation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 5

1.1 Document history _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 7

1.2 Conventions used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 8

1.3 Terminology used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 9

1.4 Notes used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 10

2Safety instructions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 11

2.1 General safety and application notes _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 11

2.2 Device and application-specific safety instructions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 12

2.3 Residual hazards _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 12

3 Product description _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 13

3.1 Application as directed _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 13

3.2 Features and variants _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14

3.3 Connections and interfaces _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 15

4 Technical data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 17

4.1 General data and operating conditions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 17

4.2 Protocol data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 18

4.3 Communication time _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 18

4.4 Internal switch latency _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 19

5Installation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 20

5.1 Mechanical installation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 21

5.2 Electrical installation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22

5.2.1 Network topology _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22

5.2.2 EtherNet/IP connection _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 23

5.2.3 External voltage supply _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 24

6 Commissioning _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 25

6.1 Before initial switch-on _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 25

6.2 Configuring the host system (scanner) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 26

6.2.1 EDS files _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 27

6.2.2 Example: IP configuration of the Allen-Bradley 1769-L32E CompactLogix controller _ _ _ 28

6.3 Setting the IP configuration of the Inverter Drive 8400 motec _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 30

6.3.1 Setting via the EtherNet/IP configurator of the »Engineer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 31

6.3.2 Setting via codes in the »Engineer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33

6.3.3 Setting via a BOOTP/DHCP server _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 35

6.3.4 Setting via the TCP/IP Interface Object (0xF5) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 35

6.3.5 Setting the multicast configuration _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 36

6.4 Establishing an online connection via EtherNet/IP with the Lenze »Engineer« _ _ _ _ _ _ _ _ _ _ _ 37

6.5 Initial switch-on _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 39

2 Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Contents

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

7 Data transfer _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 40

7.1 Communication channels _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 41

7.2 Telegram types _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 42

7.3 EtherNet/IP state diagram _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 43

8 I/O data transfer (implicit messages) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 44

8.1 Configuring I/O data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 45

8.2 I/O data mapping _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 47

8.3 Technology applications (TA) / drive profiles _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 48

8.3.1 Lenze technology applications / user-definable parameter sets _ _ _ _ _ _ _ _ _ _ _ _ _ _ 48

8.3.2 "AC Drive Profile" application _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 49

8.4 I/O assemblies _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 50

8.5 I/O configuration in the »Engineer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 52

8.5.1 Lenze technology application / configuring user-definable parameter sets _ _ _ _ _ _ _ _ 52

8.5.2 Configuring "AC Drive Profile" application _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 56

8.6 I/O configuration with »RSLogix 5000« version 19 or lower _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 57

8.7 I/O configuration with »RSLogix 5000« version 20 or higher _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 62

8.8 Saving the I/O configuration in »RSLogix 5000« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 72

9 Parameter data transfer (explicit messages) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 73

9.1 Write parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 74

9.2 Read parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 75

10 Monitoring _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 77

11 Diagnostics _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 78

11.1 LED status displays _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 78

11.2 Diagnosing with the »Engineer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 80

12 Error messages _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 81

12.1 Short overview of the EtherNet/IP error messages _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 81

12.2 Possible causes and remedies _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 82

12.3 CIP™ error messages _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 86

12.4 Mapping of Lenze device errors to DRIVECOM errors _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 87

13 Parameter reference _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 91

13.1 Parameters of the Communication Unit _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 91

13.2 Table of attributes _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 106

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 3

Contents

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

14 Implemented CIP™ objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 108

14.1 General CIP objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 110

14.1.1 Identity Object (1 / 0x01) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 110

14.1.2 Message Router Object (2 / 0x02) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 112

14.1.3 Assembly Object (4 / 0x04) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 113

14.1.4 Connection Manager Object (6 / 0x06) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 120

14.2 EtherNet/IP objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 122

14.2.1 Device Level Ring (DLR) Object (71 / 0x47) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 122

14.2.2 Quality of Service (QoS) Object (72 / 0x48) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 124

14.2.3 TCP/IP Interface Object (245 / 0xF5) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 126

14.2.4 Ethernet Link Object (246 / 0xF6) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 130

14.3 "AC Drive Profile" objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 133

14.3.1 Motor Data Object (40 / 0x28) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 134

14.3.2 Control Supervisor Object (41 / 0x29) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 135

14.3.3 AC Drive Object (42 / 0x2A) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 137

14.3.4 Write "DriveMode" attribute _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 138

14.4 Lenze objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 139

14.4.1 Lenze Class (101 / 0x65) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 139

14.4.2 Lenze Class (103 / 0x67) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 141

14.4.3 Lenze Class (104 / 0x68) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 142

14.4.4 Lenze Class (110 / 0x6E) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 143

Index _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 144

Your opinion is important to us _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 148

4 Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

About this documentation

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

1 About this documentation

Contents

This documentation exclusively contains descriptions of the EtherNet/IP™ bus system for the Inverter Drives 8400 motec.

 Note!

This documentation supplements the mounting instructions supplied with the Communication Unit and the "Inverter Drives 8400 motec" hardware manual.

The hardware manual contains safety instructions that must be observed!

The properties and functions of the EtherNet/IP for the Inverter Drive 8400 motec 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 Unit.

This documentation does not describe any software provided by other manufacturers. No warranty can be given for corresponding data provided in this documentation. For information on how to use the software, please refer to the host (PLC, master) documents.

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

5 Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

About this documentation

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Target group

This documentation addresses to persons who configure, install, commission, and maintain the networking and remote maintenance of a machine.

 Tip!

Current documentation and software updates with regard to Lenze products can be found in the download area at:

www.Lenze.com

Information regarding the validity

The information given in this documentation is valid for the following devices:

Product series Type designation Version

Inverter Drives 8400 motec

EtherNet/IP Communication Unit

E84DGFCGxNx EtherNet/IP

E84DGFCGxJx EtherNet/IP + Safety

Features and variants

Screenshots/application examples

All screenshots in this documentation are application examples. Depending on the firmware version of the field devices and the software version of the Engineering tools installed (»Engineer«, »RSLogix 5000«), the screenshots in this documentation may differ from the actual screen display.

( 14)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 6

About this documentation

Document history

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

1.1 Document history

Version Description

1.0 08/2012 TD17 First edition

2.0 10/2013 TD17 New layout Revised chapters:

I/O data transfer (implicit messages) Parameter data transfer (explicit messages) Implemented CIP™ objects

( 108)

( 44)

( 73)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

About this documentation

Conventions used

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

1.2 Conventions used

This documentation uses the following conventions to distinguish between different types of information:

Type of information Writing Examples/notes

Spelling of numbers

Decimal Standard notation Example: 1234

Decimal separator Point The decimal point is always used.

For example: 1234.56

Hexadecimal 0x[0 ... 9, A ... F] Example: 0x60F4

Binary

• Nibble

Text

Program name » « PC software

Control element bold The OK button... / the Copy command... / the

Hyperlink Underlined

Icons

Page reference ( 8) Optically highlighted reference to another page. It is

Step-by-step instructions

0b[0, 1] Example: ’0b0110’

Example: ’0b0110.0100’

Example: Lenze »Engineer«

Characteristics tab... / the Name input field...

Optically highlighted reference to another topic. It is activated with a mouse-click in this documentation.

activated with a mouse-click in this documentation.

Step-by-step instructions are indicated by a



pictograph.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 8

About this documentation

Terminology used

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

1.3 Terminology used

Term Meaning

ACD Address Conflict Detection

Adapter EtherNet/IP slave

Inverter / Drive Lenze drive of the "Inverter Drives 8400 motec" product series

Standard device

ARP Address Resolution Protocol

BOOTP Bootstrap Protocol

Code Parameter which serves to parameterise and monitor the drive. In normal usage,

Subcode If a code contains several parameters, they are stored in "subcodes".

»Engineer« Software from Lenze which supports you throughout the whole machine life

DHCP Dynamic Host Configuration Protocol

DSCP Differentiated Services Codepoints

EDS Electronic Data Sheet

Explicit messages Explicit Messages are used to transfer parameter data.

HW Hardware

IGMP Internet Group Management Protocol

Implicit messages Implicit Messages are used to transfer I/O data.

"Class 1" connection I/O connection

"Class 3" connection Explicit connection

Level 2 EtherNet/IP performance level 2:

Lenze setting Default settings of the device, preconfigured ex works.

Basic setting

PLC Programmable Logic Controller

QoS Quality of Service

RPI Requested Package Interval:

»RSLogix 5000« Programming and development software from Rockwell for hosts (scanners) in

Scanner EtherNet/IP master or client

Host

SW Software

TTL Time To Live:

UCMM Unconnected Message Manager

the term is usually referred to as "Index".

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".

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.

I/O Message Server including Explicit Message Server

Interval requested between 2 telegrams for cyclic data transmission

EtherNet/IP networks (e.g. Allen-Bradley Logix controllers).

Validity time of data packets in the EtherNet/IP network

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

About this documentation

Notes used

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

1.4 Notes used

The following signal words and symbols are used in this documentation to indicate dangers and important information:

Safety instructions

Layout of the safety instructions:

 Pictograph and signal word!

(characterise the type and severity of danger)

Note

(describes the danger and gives information about how to prevent dangerous situations)

Pictograph Signal word Meaning

Danger! Danger of personal injury through dangerous electrical voltage



Danger! Danger of personal injury through a general source of danger



Stop! Danger of property damage



Application notes

Pictograph Signal word Meaning

Note! Important note to ensure trouble-free operation

Reference to an imminent danger that may result in death or serious personal injury if the corresponding measures are not taken.

Reference to a possible danger that may result in property damage if the corresponding measures are not taken.



Tip! Useful tip for easy handling



Reference to another document



Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 10

Safety instructions

General safety and application notes

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

2 Safety instructions

 Note!

It is absolutely vital that the stated safety measures are implemented in order to prevent serious injury to persons and damage to material assets.

Always keep this documentation to hand in the vicinity of the product during operation.

2.1 General 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.

Application 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.

Features and variants

• 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.

• Only qualified personnel may work with and on Lenze drive and automation components. In accordance with IEC 60364 and CENELEC HD 384, these are persons ...

• are familiar with installing, mounting, commissioning, and operating the product.

• who have the corresponding qualifications for their work.

• who know and can apply all regulations for the prevention of accidents, directives, and laws applicable at the place of use.

( 13)

( 14)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Safety instructions

Device and application-specific safety instructions

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

2.2 Device and application-specific safety instructions

During operation, the Communication Unit must be connected to the Wiring Unit and the Drive Unit.

 Documentation for Inverter Drives 8400 motec, control system, 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.3 Residual hazards

Device protection

The Communication Unit contains electronic components that can be damaged or destroyed by electrostatic discharge.

Installation

( 20)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 12

Product description

Application as directed

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

3 Product description

3.1 Application as directed

The EtherNet/IP Communication Unit ...

• is a unit that can only be used in conjunction with the following modules:

Product series Type designation

Inverter Drives 8400 motec

Drive Unit

Inverter Drives 8400 motec

Wiring Unit

• is a device intended for use in industrial power systems.

• should only be used under the operating conditions prescribed in this documentation.

• can only be used in EtherNet/IP networks.

E84DGDVxxxxxxxx (from version V04.01)

E84DGVNxx

• can also be used without being connected to the EtherNet/IP network.

Any other use shall be deemed inappropriate!

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Product description

Features and variants

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

3.2 Features and variants

The EtherNet/IP Communication Unit is available in the following versions:

Product series Type designation Product features

Enclosure

IP 65

EtherNet/IP

M12

I/O: Terminal

Inverter Drives 8400 motec

EtherNet/IP Communication Unit

• The EtherNet/IP Communication Unit is ...

• mounted on top of the Wiring Unit (E84DGVNxx);

• supplied internally via the Drive Unit (E84DGDVxxxxxxxx) or externally via a separate voltage source.

• The I/O connections can be brought into the device via M12 connectors or cable glands.

• Devices without an integrated safety system (safety option) have no analog input and no relay output.

E84DGFCGANP 

E84DGFCG9NP  

E84DGFCGAJP  

E84DGFCG9JP  

I/O: M12

Safety

• The integrated safety system can be used on machines for the protection of persons.

• The Inverter Drive 8400 motec is always an adapter device: EtherNet/IP adapter with "Level 2" functionality

• 2-port interface with integrated switch functionality

• Access to all Lenze parameters (configurable via TCP/IP using the Lenze »Engineer«)

• Up to 3 TCP/IP socket connections for communication with the Lenze »Engineer«

• Support of "IP Config Pending" (activation of changed IP configuration by "power off/on" or "type 0 reset")

• Support of the redundancy protocol DLR (Device Level Ring) as "beacon-based ring node"

• Up to 10 input data words to the scanner (20 bytes)

• Up to 8 output data words from the scanner (16 bytes)

• Further CIP features:

• Max. 8 CIP connections

• 1 "exclusive owner" connection

• I/O connection type: cyclic

•Minimum I/O cycle time: 4 ms

• Support of multicast messages, UCMM, ACD, BOOTP/DHCP, VLAN tagging/DSCP

 Hardware manual for Inverter Drives 8400 motec

Here you will find detailed information on the integrated safety system (safety option).

Software manual / »Engineer« online help for the Inverter Drive 8400 motec

Here you will find detailed information on how to configure the safety system (safety option).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 14

Product description

Connections and interfaces

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

3.3 Connections and interfaces

[3-1] EtherNet/IP Communication Unit

Pos. Description

A1 / LED Position of LEDs for EtherNet/IP status display

LED status displays

A2 EtherNet/IP connections (M12 sockets, 5-pin, D-coded)

A4 Positions for further freely designable inputs and outputs:

B1 ... B4

X3 / X4 / X61 Terminal strips for wiring the connections at A4 and B1 ... B4

X5 Plug connector for connection to the Drive Unit

X31 Plug connector for wiring the EtherNet/IP connection at A2

X32 Plug connector for wiring the EtherNet/IP connection at A3

X55 Plug connector for the wiring of the LEDs to A1

EtherNet/IP connection

• Digital inputs

•Digital output

• Analog input (only for E84DGFCGxJx)

• Relay output (only for E84DGFCGxJx)

• Connection of "Safety Option" safety system (only for E84DGFCGxJx)

E84DG029

( 78)

( 23)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Product description

Connections and interfaces

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

• By default, the EtherNet/IP connections and the LEDs for the EtherNet/IP status displays are already mounted and wired:

• EtherNet/IP connection A2 to plug connector X31

• EtherNet/IP connection A3 to plug connector X32

• LEDs on plug connector X55

• At positions A1 ... A4 and B1 ... B4, it is also possible to design the EtherNet/IP connections and other connections (e.g. digital inputs) freely.

• For the connections, 5-pin M12 connectors or - alternatively - cable glands (cable cross-section max. 1.0 mm

• The M12 connectors, cable glands and prefabricated system cables can be obtained from various manufacturers.

• Wire the M12 connectors or cable glands used to the corresponding contacts of the terminal strips/plug connectors X3, X4 and X61.

, AWG 18) can be used.

 Hardware manual for Inverter Drives 8400 motec

Observe the notes and wiring instructions contained in this documentation.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 16

Technical data

General data and operating conditions

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

4 Technical data

 Hardware manual for Inverter Drives 8400 motec

Here you will find the ambient conditions and information on the electromagnetic compatibility (EMC) that also apply to the Communication Unit.

4.1 General data and operating conditions

Range Values

Order designation • E84DGFCGxNx (EtherNet/IP)

• E84DGFCGxJx (EtherNet/IP + Safety)

Communication profile EtherNet/IP

Standards / specifications Safety engineering: EN 954-1, EN 13849-1, IEC 61508

Interface for communication • EtherNet/IP port 1: M12 socket, 5-pin, D-coded

Network topology Tree, star, and line

Type of node Adapter (slave)

Number of nodes Max. 254 in the subnetwork

Max. cable length 100 m

Vendor ID 587 (0x24B), Lenze (’Lenze AC Tech’ in older Rockwell data)

Device type 2 (0x02), AC Drive

Product code 8440 (0x20F8)

Baud rate • 10 Mbps

Transmission mode Half duplex / full duplex

Switching method Store-and-forward / cut-through

Switch latency Approx. 125 μs at max. telegram length

External voltage supply • U = 24 V DC (20 V - 0 % ... 29 V + 0 %)

Conformities, approvals • CE

(up to safety category 4)

• EtherNet/IP port 2: M12 socket, 5-pin, D-coded

• 100 Mbps

•I

= 400 mA

max

•UR / cUR

(see also hardware manual)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Technical data

Protocol data

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

4.2 Protocol data

Range Values

I/O data words 1 ... 10 data words to scanner (16 bits/word, max. 20 bytes)

1 ... 8 data words from scanner (16 bits/word, max. 16 bytes)

Supported CIP services • Get_Attributes_All

• Get_Attribute_Single

• Set_Attribute_Single

• Reset (types ’0’ and ’1’ only)

•Forward_Open

•Forward_Close

• Get_Member

4.3 Communication time

The communication time is the time between the start of a request and the arrival of the corresponding response.

The communication times in an EtherNet/IP network depend on the ...

• processing time in the inverter;

• telegram runtime (baud rate / telegram length);

• nesting depth of the network.

processing time within the inverter

Data Processing time

Process data (I/O data) 10 ms

+ 0 ... 1 ms + 1 ... x ms

Parameter data Approx. 30 ms + a tolerance of 20 ms (typically)

Some codes may require a longer processing time (see software manual / »Engineer« online help for Inverter Drive 8400 motec).

Lenze standard update cycle (can be changed in the Rockwell engineering tool)

Processing time in the module Runtime of the application task of the technology application used (tolerance)

There are no interdependencies between parameter data and I/O data.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 18

Technical data

Internal switch latency

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

4.4 Internal switch latency

The integrated 2-port switch causes runtime delays. For "store-and-forward" and 100 Mbps, these runtime delays can be calculated as follows.

Runtime delay for an output data packet of the scanners incl. 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

( 22)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Installation

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

5 Installation

 Stop!

Electrostatic discharge

Electronic components within the Communication Unit can be damaged or destroyed by electrostatic discharge.

Possible consequences:

• The Communication Unit is defective.

• Fieldbus communication is not possible or faulty.

• I/O signals are faulty.

• The safety function is faulty.

Protective measures

Discharge electrostatic charges before touching the Communication Unit.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 20

Installation

Mechanical installation

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

5.1 Mechanical installation

 Mounting instructions for Inverter Drive 8400 motec

Here you will find detailed information on the installation.

0.37 ... 3.0 kW 4.0 ... 7.5 kW

E84DG023a

E84DG023b

[5-1] Mechanical installation of the 8400 motec components

Legend for fig. [5-1]

1Drive Unit

2 Communication unit

3 Wiring Unit

A Cover of the Drive Unit

EDK84DG... Mounting instructions of the Drive Unit, Communication Unit, Wiring Unit

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Installation

AAA

Electrical installation

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

5.2 Electrical installation

 Hardware manual for Inverter Drives 8400 motec

Here you can find detailed information on ...

• the digital and analog inputs/outputs;

•the relay output;

• the integrated safety system (safety option);

• the wiring of the terminals.

Observe the notes and wiring instructions contained in this documentation!

5.2.1 Network 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.

( 19)

EtherNet/IP supports the following topologies:

•Line

[5-2] Line topology (S = scanner, A = adapter)

•Switch / star

[5-3] Switch / star topology (SW = switch, A = adapter)

E94AYCEO008

E94AYCEO005

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 22

Installation

SWSWSW

SWSW

Electrical installation

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

•Tree via switches

E94AYCEO006

[5-4] Tree topology (S = scanner, SW = switch)

•Switch / switch

[5-5] Switch / switch topology (SW = switch)

5.2.2 EtherNet/IP connection

Pin Signal Description

1 Tx + Data line (transmitted data, plus)

2 Rx + Data line (received data, plus)

3 Tx - Data line (transmitted data, minus)

4 Rx - Data line (received data, minus)

5- not assigned

E94AYCEO007

• M12 socket, 5-pole, D-coded

• Wiring at terminal strip X31 / X32

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Installation

Electrical installation

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

5.2.3 External voltage supply

• The external voltage supply can be used to establish EtherNet/IP communication for commissioning and to query the data of the digital and analog inputs.

• Furthermore, the external voltage supply serves to maintain EtherNet/IP communication if the main supply fails.

• The digital inputs RFR, DI1 ... DI5 and the analog input can continue to be evaluated.

• The external voltage supply is done via the terminals 24E and GND of the terminal strip X3.

• Permissible voltage (DC) / max. current:

• U = 24 V DC (20 V - 0 % ... 29 V + 0 %)

•I

= 400 mA

max

• Access to parameters of a device that is disconnected from the mains is not possible.

 Hardware manual for Inverter Drives 8400 motec

Here you can find detailed information on how to wire the Communication Unit.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 24

Commissioning

Before initial switch-on

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6 Commissioning

During commissioning, plant-specific data such as motor parameters, operating parameters, responses, and parameters for fieldbus communication are defined for the inverter. Lenze devices use codes for this purpose.

The codes of the inverter and for communication are saved to the memory module in a non-volatile data set.

In addition, there are codes for diagnosing and monitoring the stations.

Parameter reference

The data from the drive or the memory module can only be read with the main voltage supply (400/ 500 V AC).

For commissioning with 24 V DC, only the data of the digital and analog inputs in the last two data words are valid and readable (see Configuring I/O data

6.1 Before initial switch-on

 Stop!

Before the Inverter Drive 8400 motec is switched on for the first time, the entire wiring must be checked for completeness, short circuit and earth fault.

( 91)

( 45)).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Commissioning

Configuring the host system (scanner)

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.2 Configuring the host system (scanner)

To be able to communicate with the Communication Unit, the host system (scanner) must be configured first.

The configuration of EtherNet/IP networks always requires an EtherNet/IP configuration software (e.g. »RSLogix 5000« from Rockwell) for the host system (scanner).

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 Unit are stored in the internal configuration memory and can be used for the 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

( 57)

I/O configuration with »RSLogix 5000« version 20 or higher

( 62)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 26

Commissioning

Configuring the host system (scanner)

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.2.1 EDS files

Depending on the EtherNet/IP scanner configuration software, the EDS files (Electronic Data Sheet) may be used for the configuration of the network profile, the communication with the participating devices and the automatic generation of tags. For this purpose, the EDS files have to be imported into the controller project of the EtherNet/IP configuration software.

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 · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Commissioning

Configuring the host system (scanner)

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.2.2 Example: IP configuration of the Allen-Bradley 1769-L32E CompactLogix controller

In this example, the Allen-Bradley 1769-L32E CompactLogix controller with integrated EtherNet/IP interface is used to communicate with Inverter Drives 8400 motec.

The »RSLogix 5000« programming software from Rockwell is used for the configuration.

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.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 28

Commissioning

Configuring the host system (scanner)

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

5. Go to the Port Configuration tab and enter the IP configuration, BOOTP setting, Ethernet baud rate and duplex mode.

6. Then click OK.

• Now, the scanner is configured for the EtherNet/IP network.

• Here you will find information on project planning with the »RSLogix 5000« programming software from Rockwell:

I/O configuration with »RSLogix 5000« version 19 or lower I/O configuration with »RSLogix 5000« version 20 or higher

( 57)

( 62)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Commissioning

Setting the IP configuration of the Inverter Drive 8400 motec

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.3 Setting the IP configuration of the Inverter Drive 8400 motec

The IP configuration is required for addressing the Inverter Drive 8400 motec to ensure that communication between the PC/»Engineer« or the scanner and the drive can be effected via EtherNet/IP. For this, an IP address, subnet mask, and gateway address must be allocated. You have the following options to select the IP parameters for the Inverter Drive 8400 motec:

• 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)

( 33)

( 35)

 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] ( 84) is output.

(IP address), C13011 (subnet mask), C13012 (gateway address), and

(multicast IP address) show the IP parameters currently used.

( 31)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 30

Commissioning

Setting the IP configuration of the Inverter Drive 8400 motec

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.3.1 Setting via the EtherNet/IP configurator of the »Engineer«

 Note!

• Changes in the IP parameters will become effective immediately.

• An existing IP connection to the Inverter Drive 8400 motec will be interrupted.

 How to set the IP parameters via the EtherNet/IP configurator:

1. Execute the menu command Online  PROFINET / EtherNet/IP configurator addresses ....

The "Assign IP addresses" dialog window is opened and all Lenze EtherNet/IP nodes connected are listed.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Commissioning

Setting the IP configuration of the Inverter Drive 8400 motec

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

2. A double-click on a EtherNet/IP node opens the "Configure nodes" dialog window.

Here you can set the IP parameters.

3. Click on Transferred.

• The IP configuration is transferred to the corresponding EtherNet/IP node.

• The Communication Unit executes a stack reset.

•The IP parameters are written to codes C13000

C13002

•Code C13005 transferred address can be used.

(gateway address).

(IP configuration reference) is set to ’0: Saved address’ to ensure that the

(IP address), C13001 (subnet mask), and

 Tip!

Check whether the configuration has been transferred successfully.

For this purpose, open the "Assign IP addresses" dialog window (see step 1) and click the Find device button.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 32

Commissioning

Setting the IP configuration of the Inverter Drive 8400 motec

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.3.2 Setting via codes in the »Engineer«

You can also set the IP parameters manually in the »Engineer« under the Settings tab. The values will be transferred to the corresponding codes.

Settings Description

IP Config Control Selection (C13005

• 0: The IP configuration currently saved in the Communication Unit is

used.

• 1: The IP configuration is assigned by a BOOTP server using the BOOTP.

• 2: The IP configuration is assigned by a DHCP server using the DHCP.

IP Address Setting of the IP address (C13000

Subnet mask Setting of the subnet mask (C13001

Gateway Address Setting of the gateway address (C13002

Multicast IP Start Address Setting of the Multicast IP start address (C13006

Setting the multicast configuration

Multicast Config TTL Value Setting of the multicast TTL value (C13019

) of how the IP configuration is to be made:

)

 How to activate changed settings in the »Engineer«:

1. Execute device command C00002 = "11: Save all parameter sets".

The current IP configuration is stored in the memory module of the drive.

2. Carry out a "Type 0 reset" for the Identity Object (1 / 0x01) voltage supply of the Communication Unit off and on again.

)

( 36)

)

( 110) of the node, or switch the

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Commissioning

Setting the IP configuration of the Inverter Drive 8400 motec

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

IP address

The IP address is set/changed in C13000

The IP address currently used is displayed in C13010/1...4

Example: Display of the IP address 192.168.124.16

Code C13010/1

Value 192 168 124 16

C13010/2 C13010/3 C13010/4

Subnet mask

The subnet mask indicates which part of the IP address is evaluated as net ID or host ID.

Valid subnet masks are defined in accordance with RFC 1878

The subnet mask is set/changed in C13001

The subnet mask currently used is displayed in C13011/1...4

Example: Display of the subnet mask 255.255.255.0

Code C13011/1

Value 255 255 255 0

C13011/2 C13011/3 C13011/4

Gateway address

The gateway address is valid if the network address of the IP address and the gateway address are identical.

If the gateway address and the IP address are identical or if the address is ’0.0.0.0’, gateway functionality is not used.

The gateway address is set/changed in C13002

The gateway address currently used is displayed in C13012/1...4

Example: Display of the gateway address 192.168.124.16

Code C13012/1

Value 192 168 124 16

C13012/2 C13012/3 C13012/4

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 34

Commissioning

Setting the IP configuration of the Inverter Drive 8400 motec

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.3.3 Setting via a BOOTP/DHCP server

DHCP is the acronym for "Dynamic Host Configuration Protocol". This protocol is defined in RFC 2131 and is a compatible advancement of the "Bootstrap Protocol" (BOOTP) according to RFC 951.

Both protocols enable network nodes to query information about the network configuration (e.g. 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 Unit 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:

( 126).

6.3.4 Setting 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) ( 110)).

In the »Engineer«, codes C13010 and C13016

(multicast IP address) show the IP parameters currently used.

(IP address), C13011 (subnet mask), C13012 (gateway address),

( 126).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Commissioning

Setting the IP configuration of the Inverter Drive 8400 motec

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.3.5 Setting the multicast configuration

Several scanners ("Listen only" or "Input only" connections) can access multicast telegrams which are sent by drives. Settings for multicast configuration have to be carried out as well in the EtherNet/IP configuration software (z. B. »RSLogix 5000« from Rockwell).

By default, the Communication Unit automatically generates the multicast IP start address used for the I/O data transfer. The TTL default value for multicast transmission is ’1’, so the multicast I/O data packets are exclusively propagated 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:

Code Description

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

Code C13016/1

Value 239 64 2 224

Selection for multicast IP addressing via instance attribute 9 (Mcast Config) in the TCP/IP

Interface Object (245 / 0xF5) ( 126)

• 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/2 C13016/3 C13016/4

is used as multicast IP start address.

( 126))

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 36

Commissioning

Establishing an online connection via EtherNet/IP with the Lenze »Engineer«

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.4 Establishing an online connection via EtherNet/IP with the Lenze »Engineer«

 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 Unit can manage cyclic EtherNet/IP communication with priority over regular TCP/IP communication. With EtherNet/IP this is effected via the VLAN identification in the Ethernet frame (adjustable in C13021

• If the redundancy protocol DLR (Device Level Ring) is used, the switch also must be DLR-compliant.

[6-1] Example set-up with an Allen Bradley CompactLogix Controller 1769-L32E (scanner)

For an online connection between the »Engineer« and the drive, the drive has to have an IP address (see Setting the IP configuration of the Inverter Drive 8400 motec

( 30)).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Commissioning

Establishing an online connection via EtherNet/IP with the Lenze »Engineer«

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

In the »Engineer«, you can use the Online  Set communication path and go online menu command to select the EtherNet/IP communication path. The previously configured EtherNet/IP nodes are shown in the "Communication path" dialog window:

If the device access path is not configured correctly, the 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«

( 31)

• 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 · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 38

Commissioning

Initial switch-on

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6.5 Initial switch-on

Establishing communication

• To establish a communication, the Inverter Drive has to be supplied with mains voltage.

• For EtherNet/IP communication, the Communication Unit has to be supplied with voltage. If this is not the case, the error message "CE04: MCI communication error" (error no.

01.0127.00002) is output. The error has to be reset in the Inverter Drive in order that the EtherNet/IP communication can be established.

• The external voltage supply serves to maintain EtherNet/IP communication if the main supply fails.

External voltage supply

• During mains connection, all parameters (codes) are read.

• For addressing the drive, a valid IP configuration is required if communication between the PC/ »Engineer« and the drive is to be effected via EtherNet/IP.

Setting the IP configuration of the Inverter Drive 8400 motec

( 24)

( 30)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Data transfer

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

7 Data transfer

EtherNet/IP uses CIP™ (Common Industrial Protocol) for the data exchange between devices via an Ethernet network – just like the closely related bus systems DeviceNet and ControlNet.

Lenze implements the CIP following the ODVA standard (Open DeviceNet Vendor Association,

www.odva.org

• Explicit messaging (for parameter data)

• Implicit messaging (for I/O data)

) and supports the two main types of EtherNet/IP communication:

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 40

Data transfer

Communication channels

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

7.1 Communication channels

 Note!

The terms "input" and "output" refer to the point of view of the scanner:

• Input data is produced by the adapter and consumed by the scanner.

• Output data is produced by the scanner and consumed by the adapter.

EtherNet/IP transmits parameter data and I/O data between the host system (scanner) and the drives (adapters) connected to the fieldbus. 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).

• To the scanner, up to 10 data words (max. 20 bytes) can be sent.

• From the scanner, up to 8 data words (max. 16 bytes) can be sent.

• I/O data 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 via code C00002 of the Inverter Drive 8400 motec.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Data transfer

Telegram types

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

7.2 Telegram types

The "implicit message" and "explicit message" telegram types are transmitted between the host system (scanner) and the drive (adapter).

Implicit messages (I/O data transfer)

"Implicit messages" are transmitted or received according to the producer/consumer principle. There is one transmitter and no receiver or an optional number of receivers.

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).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 42

Data transfer

EtherNet/IP state diagram

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

7.3 EtherNet/IP state diagram

[7-1] EtherNet/IP state diagram

The current EtherNet/IP device state is ...

• output via code C13861

• output in the Identity Object (1 / 0x01)

• indicated via the MS LED (see LED status displays

;

( 110) via instance attributes 5 and 8;

( 78)).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8 I/O data transfer (implicit messages)

To exchange I/O data (implicit messages) between the host system (scanner) and the drive (adapter), you have to ...

• Assign the I/O data to the internal ports (MCI) in the drive (adapter):

I/O data mapping I/O configuration in the »Engineer«

• Configure the I/O data transfer in the host (scanner):

I/O configuration with »RSLogix 5000« version 19 or lower I/O configuration with »RSLogix 5000« version 20 or higher

( 47)

( 52)

( 57)

( 62)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 44

I/O data transfer (implicit messages)

Configuring I/O data

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8.1 Configuring I/O data

• The I/O data configuration is specified during the initialisation phase of the scanner (PDO mapping).

• To the scanner, up to 10 data words (max. 20 bytes) can be sent.

• From the scanner, up to 8 data words (max. 16 bytes) can be sent.

•In the 111 (0x6F, Custom Input) assembly object instance, the I/O data is entered in the last two words:

Data word Bits Function Value / description

Word 9 0

... 9

10 Digital input 3 0 (FALSE) Open

11 Digital input 4 0 (FALSE) Open

12 Digital input 5 0 (FALSE) Open

13 Reserved

14 I/O status 0 (FALSE) Data in word 9/10 are not valid.

15 Connection status of the

Word 10 0 RFR 0 (FALSE) Open

1 Digital input 1 0 (FALSE) Open

2 Digital input 2 0 (FALSE) Open

3 Digital input 3 0 (FALSE) Open

4 Digital input 4 0 (FALSE) Open

5 Digital input 5 0 (FALSE) Open

6 ... 13

14 I/O status 0 (FALSE) Data in word 9/10 are not valid.

15 Connection status of the

Analog input value (0 ... 10 V)

drive

Reserved

drive

10 V = 1000

1 (TRUE) Closed

1 (TRUE) Data in word 9/10 are valid.

0 (FALSE) Drive is offline ("Stay alive" operation)

1 (TRUE) Drive is online

1 (TRUE) Closed

1 (TRUE) Data in word 9/10 are valid.

0 (FALSE) Drive is offline ("Stay alive" operation)

1 (TRUE) Drive is online

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

Configuring I/O data

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

• In the assembly input object instances 70 ... 73 (0x46 ... 0x49), this data is not used due to profile conformity reasons.

• The I/O data configuration is application-specifically predefined in the device description files and can be adapted, if necessary.

I/O configuration in the »Engineer«

( 52)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 46

I/O data transfer (implicit messages)

Field bus

8400

Application

Communication Unit

Drive Unit

MCI_IN

Word 1

...

Word 8

MCI_OUT

Word 1

...

Word 10

I/O data mapping

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8.2 I/O data mapping

I/O data transfer takes place via the MCI interface.

• The I/O data are accessed via the port blocks MCI_IN and MCI_OUT. These port blocks are also referred to as I/O data channels.

•The MCI_IN port block maps the received data objects.

•The MCI_OUT port block maps the data objects to be sent.

• To the scanner, up to 10 data words (max. 20 bytes) can be sent.

• From the scanner, up to 8 data words (max. 16 bytes) can be received.

• The ports/function blocks of the I/O data objects are interconnected with the Lenze »Engineer«.

[8-1] Outer and inner data transfer between bus system, inverter, and application

 Software manual / online help for the Inverter Drive 8400 motec

Here you will find detailed information on the port/function block interconnection in the »Engineer« and on the port blocks.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

Technology applications (TA) / drive profiles

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8.3 Technology applications (TA) / drive profiles

The Inverter Drives 8400 motec is provided with various drive profiles. They define a standardised/ individual control and status word assignment and the standardisation of setpoints and actual value scalings.

The following drive profiles are supported by the Inverter Drives 8400:

• Lenze technology applications / user-definable parameter sets

• "AC Drive Profile" application

8.3.1 Lenze technology applications / user-definable parameter sets

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 ID Assembly object instance

[dec] [hex]

110 0x6E Custom Output

(from the adapter to the scanner)

111 0x6F Custom Input

(from the adapter to the scanner)

8.3.2 "AC Drive Profile" application

The Inverter Drives 8400 motec supports the EtherNet/IP-specific "AC Drive Profile".

The standard device code C00005 = "1100: AC Drive Profile" serves to select the "AC Drive Profile" application.

The "AC Drive Profile" contains ...

• the data basis for motor parameters,

• management functions of the motor control devices,

• Device-specific functions of the drive, e.g. speed ramps, torque control etc.

For using the "AC Drive Profile", the following assembly object instances in the host (scanner) have to be used:

Instance ID Assembly object instance

[dec] [hex]

20 0x14 Basic Speed Control Output Outputs: From the scanner to

21 0x15 Extended Speed Control Output

22 0x16 Speed and Torque Control Output

23 0x17 Extended Speed and Torque Control Output

70 0x46 Basic Speed Control Input Inputs: From the adapter to

71 0x47 Extended Speed Control Input

72 0x48 Speed and Torque Control Input

73 0x49 Extended Speed and Torque Control Input

the adapter

the scanner

8.4 I/O assemblies

 Note!

The terms "input" and "output" refer to the point of view of the scanner:

• Assembly input objects (input) are sent from the adapter to the scanner.

• Assembly output objects (output) are sent from the scanner to the adapter.

The length of the I/O data must correspond with the respective resulting length of the mapped ports (I/O data mapping

The Communication Unit supports the Assembly Object (4 / 0x04) ( 113) and the "AC Drive Profile"

objects ( 133).

For data exchange, the Communication Unit supports the following assembly object instances:

Instance ID Assembly object instance

[dec] [hex]

Lenze technology applications / userdefinable parameter sets

AC Drive Profile" application 20 0x14 Basic Speed Control Output

110 0x6E Custom Output

111 0x6F Custom Input

21 0x15 Extended Speed Control Output

22 0x16 Speed and Torque Control Output

23 0x17 Extended Speed and Torque Control Output

70 0x46 Basic Speed Control Input

71 0x47 Extended Speed Control Input

72 0x48 Speed and Torque Control Input

73 0x49 Extended Speed and Torque Control Input

( 47)).

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.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 50

I/O data transfer (implicit messages)

I/O assemblies

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Assembly output objects (scanner  Adapter)

Assembly output objects are assumed to have a 4-byte header (32-bit "run/idle header"). When mapping the assemblies, this header will automatically be added to the data stream by most AllenBradley PLC/SLC equipment.

If your PLC does not support this header (like the Rockwell PLCs do), add a preceding 32-bit header to the output image.

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

( 47)).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration in the »Engineer«

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8.5 I/O configuration in the »Engineer«

8.5.1 Lenze technology application / configuring user-definable parameter sets

 How to configure the Lenze technology applications / user-definable parameter sets in the

»Engineer«:

1. Select the application (C00005 = 1000) in the Application parameters tab.

In the example, the "speed actuating drive" application is configured.

2. Make the default setting of the I/O configuration.

Select "MCI" control mode (C00007 = 40).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 52

I/O data transfer (implicit messages)

I/O configuration in the »Engineer«

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

3. On the Ports tab, the port blocks

shown.

MCI_IN and MCI_OUT for the I/O data objects are

• By clicking the required port, the preconfigured signal combination can be obtained from the

• If you want to complement or change the signal combination, click the Variable … button.

application variables.

Change

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration in the »Engineer«

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

4. In the "Edit port" dialog window, you can assign signals to the I/O data words via the button.  Select the signals and confirm the selection with OK.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 54

I/O data transfer (implicit messages)

I/O configuration in the »Engineer«

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

For some data words, you can also assign signals to the individual bits via the and buttons.

 Select the signals and then confirm the selection with OK.

5. Use the standard device code C00002 to execute the command "11: Save all parameter sets".

The changed settings are activated and saved with mains failure protection.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration in the »Engineer«

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8.5.2 Configuring "AC Drive Profile" application

 How to configure the "AC Drive Profile" application in the »Engineer«:

1. Select the "AC Drive Profile" application (C00005 = 1100) in the Application parameters tab.

2. Make the default setting of the I/O configuration.

Select "MCI" control mode (C00007 = 40).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 56

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 19 or lower

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8.6 I/O configuration with »RSLogix 5000« version 19 or lower

The following example describes the I/O configuration of the Allen-Bradley 1769-L32E CompactLogix controller using the Rockwell »RSLogix 5000« programming software up to version

19.

Up to and including software version 19, the I/O configuration is carried out without

EDS files.

 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.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 19 or lower

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

2. Right click on "Ethernet" and execute the "New Module ..." command from the context menu.

3. Open "Communications" and select "ETHERNET-MODULE | Generic Ethernet Module".

4. Confirm the selection with OK.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 58

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 19 or lower

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

5. Go to the "New Module" dialog window and define the properties of the newly added device .

The terms "input" and "output" refer to the point of view of the scanner:

• Assembly input objects (input) are sent from the adapter to the scanner.

• Assembly output objects (output) are sent from the scanner to the adapter.

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 10 user-definable words (INT) via the MCI_OUT port using the assembly

object distance "Input = 111". The "Output = 110" assembly object instance serves to exchange up to 8 user-definable words (INT) via the MCI_IN port.

Go to "Configuration" and enter the Assembly instance "130" and the Size "0".

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 19 or lower

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Settings for an "AC Drive Profile" application:

The assembly object instances "Input = 73" and "Output = 23" shown here exemplify the use of the AC Drive Profile "Extended Speed and Torque".

Settings Description

Name Device name or type of the drive, usually with reference to the process (in the

Comm Format Data format for the assembly object instances ("connection parameters" area)

IP Address IP address of the drive

Input Assembly object instance for input objects

Output Assembly object instance for output objects

Configuration Select the Assembly instance "130" and the Size "0" for the configuration. These

example "My_8400_motec")

• The IP address 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. 10 input data words (20 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).

•In the 111 (0x6F, Custom Input) assembly object instance, the I/O data is entered in the last two words (see Configuring I/O data

I/O data mapping

• Max. 8 output data words (16 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!

( 47)

( 45))

6. Complete the settings with OK.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 60

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 19 or lower

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

7. Under I/O Configuration in the configuration tree, right click "1769-L32E Ethernet Port

LocalENB" and select "Properties".

8. Go to the Connection tab and set further properties.

Required setting

Setting Description

Requested Packet Interval (RPI)

Set RPI  4.0 ms. (Standard setting: 10 ms) The RPI [ms] specifies the intervals for the I/O data exchange between the drive

(adapter) and the controller (scanner).

Optional settings

Settings Description

Inhibit module This option serves to interrupt or inhibit the communication to the adapter.

Major Fault On Controller If Connection Fails While In Run Mode

Use Unicast Connection over EtherNet/IP

This option serves to put the controller into the error status if the EtherNet/IP connection to the drive fails while the controller is running.

Option deactivated (standard setting):

• The input data is sent from the adapter to the scanner by means of multicast telegrams.

• Other scanners can access this data in addition to the currently configured scanner ("Listen only" or "Input only" connections).

Option activated: The input data is sent from the adapter to the scanner by means of unicast

telegrams.

9. Complete the settings with OK.

• The I/O configuration is now complete.

• The corresponding tags will then be created in the "Controller Tags" of the controller project.

10. The last step is Saving the I/O configuration in »RSLogix 5000«

( 72).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8.7 I/O configuration with »RSLogix 5000« version 20 or higher

The following example describes the I/O configuration of the Allen-Bradley 1769-L32E CompactLogix controller using the Rockwell »RSLogix 5000« programming software from version

20.

From software version 20 onwards, EDS files

( 27) are used for the I/O configuration.

 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.

( 27) 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 · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 62

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

3. Right click on "Ethernet" and execute the "New Module ..." command from the context menu.

4. Open the "Select Module Type" dialog window, go to the Catalog tab and select "E84DGFCG Motec".

5. Confirm the selection with Create.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6. In the "New Module" dialog window, select the General tab and allocate a name and

an unique IP address.

Example settings:

DNS is not supported; the host name merely describes the device.

7. Click the Change ... button.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 64

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8. Go to the "Module Definition" dialog window and make the connection settings.

The terms "input" and "output" refer to the point of view of the scanner:

• Assembly input objects (input) are sent from the adapter to the scanner.

• Assembly output objects (output) are sent from the scanner to the adapter.

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.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Settings for an "AC Drive Profile" application:

• Select "AC Drive" connection.

In the example, the AC Drive Profile "Exclusive Owner - AC Drive Ext. Speed & Torque" is used.

•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.

9. Complete the settings with OK.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 66

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

10. Open the "New Module" dialog window, select the Connection tab and set further

properties.

"Name" displays the name of the connection set under 8..

The example shows an "Exclusive Owner - Custom" connection. According to this, the name of an "AC Drive Profile" connection may be displayed here too.

Required settings

Settings Description

Requested Packet Interval (RPI)

Input type Select the "Multicast" input type.

Set RPI  4.0 ms. (Standard: 10 ms) The RPI [ms] specifies the intervals for the I/O data exchange between the drive

(adapter) and the controller (scanner).

• The input data is sent from the adapter to the scanner by means of multicast telegrams.

• Other scanners can access this data in addition to the currently configured scanner ("Listen only" or "Input only" connections).

Optional settings

Settings Description

Inhibit module This option serves to interrupt or inhibit the communication to the adapter.

Major Fault On Controller If Connection Fails While In Run Mode

This option serves to put the drive into the error status if the EtherNet/IP connection to the drive fails while the controller is running.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

11. Complete the settings with OK.

• The drive is inserted in the configuration tree under the "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 · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 68

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

12. Create an "alias tag".

Example with the assembly object instance 23 (0x17):

For a forward motion of a conveyor, bit ’0’ (Run Fwd) is to be referenced by byte ’0’.

Instance Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

(0x17)

Net

Ref

NetCtrl Fault

Reset

Speed Reference (Low Byte)

Speed Reference (High Byte)

Torque Reference (Low Byte)

Torque Reference (High Byte)

Run Rev

Run Fwd

 Note!

• 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

( 138)

Right-click an assembly tag and select the command "New Tag..." in the context menu.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

13. Go to the "New Tag" dialog window and ...

•assign a Name for the tag (in the example: "Conveyor_1_RUN_FWD");

•set Type = "Alias";

• select the Alias address which is to be referenced for the alias tag. (in the example: "MY_EIP8400_FROM_EDS:O1.Data(0).0" (bit ’0’ of byte ’0’)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 70

I/O data transfer (implicit messages)

I/O configuration with »RSLogix 5000« version 20 or higher

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

14. Confirm the settings with the Create button.

The alias tag "Conveyor_1_RUN_FWD" is created below the "Controller Tags":

Name Value Force Mask Style Data Type

. . . . . . . . . . . . . . .

[–] MY_EIP8400_FROM_EDS:O1 {. . .} {. . .} _024B:E84AYCE...

[+] MY_EIP8400_FROM_EDS:O1.Data[1] 0 Decimal SINT

[+] MY_EIP8400_FROM_EDS:O1.Data[2] 0 Decimal SINT

[+] MY_EIP8400_FROM_EDS:O1.Data[3] 0 Decimal SINT

[+] MY_EIP8400_FROM_EDS:O1.Data[4] 0 Decimal SINT

[+] MY_EIP8400_FROM_EDS:O1.Data[5] 0 Decimal SINT

Conveyor_1_RUN_FWD 0 Decimal BOOL

15. The last step is Saving the I/O configuration in »RSLogix 5000«

( 72).

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

I/O data transfer (implicit messages)

Saving the I/O configuration in »RSLogix 5000«

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8.8 Saving the I/O configuration in »RSLogix 5000«

After adding the scanner and the adapter to the I/O configuration, the configuration must be downloaded to the controller. The configuration file should also be saved on your computer.

 How to save the I/O configuration:

1. Select the menu command Communications  Download.

• 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 · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 72

Parameter data transfer (explicit messages)

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

9 Parameter data transfer (explicit messages)

An "explicit message" is a logical instruction in the PLC program used for messaging. It can be used to read or write to either a parameter setting or the data of an assembly object.

For all Allen-Bradley devices of the CompactLogix, ControlLogix and SoftLogix series, the MSG instruction provides the application possibilities described in this chapter. 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

73 Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Parameter data transfer (explicit messages)

Write parameters

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

9.1 Write parameters

In order to write data into code C00011 (reference speed) of the Inverter Drive 8400 motec by means of explicit message transfer, for example, the following settings are necessary:

Settings Value / 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 motec

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 Element Variable in the PLC program used as data source for writing.

Source Length The 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 drive).

For writing to code C00011, set the source length to "2 bytes".

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 74

Parameter data transfer (explicit messages)

Read parameters

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

9.2 Read parameters

In order to read out Lenze code C00011 (reference speed) of the Inverter Drive 8400 motec by means of explicit message transfer, for example, the following settings are necessary:

Settings Value / description

Message Type "CIP Generic"

Service Type "Get Attribute Single" (service code "0x0E")

Class "6E" (access to Lenze code)

Instance "11" = Lenze code C00011 of Inverter Drive 8400 motec

Attribute "1" = Subcode of the Lenze code

If the corresponding Lenze code does not have a subcode, the value ’1’ must be entered here.

Destination Variable 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.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Parameter data transfer (explicit messages)

Read parameters

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

For every "explicit message", the path for sending the message via the Ethernet port of the controller to the IP address of the drive needs to be set under the Communication tab.

If you need assistance with the setting of this path, please consult the PLC manufacturer.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 76

Monitoring

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

10 Monitoring

Fault with regard to EtherNet/IP communication

The response of the Inverter Drive 8400 motec to a fault with regard to EtherNet/IP communication can be set in the »Engineer« under the Monitoring tab.

Settings Description

Idle Mode The 32-bit real time header sent by the scanner is evaluated.

• Run/idle flag (bit 0) = 1:

• The scanner indicates the validity of the I/O data.

• Run/idle flag (bit 0) = 0:

• 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 Mode The adapter (Communication Unit) 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 after the time set in (C13881 »Engineer«, the response parameterised here is activated in the drive (C13880/4

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

) there is no longer any access via the

) is executed on the drive.

) is executed.

) is executed on the drive.

) of the controlling I/O connection is not

) is set.

77 Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Diagnostics

250 ms

LED status displays

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

11 Diagnostics

EtherNet/IP communication can be diagnosed via the LEDs of the Communication Unit. Moreover, the »Engineer« serves to show diagnostic information.

11.1 LED status displays

LED Colour / status Description

MS Green Red

Off Off CIP module status: "Nonexistent"

The Communication Unit is not supplied with voltage.

Off On

CIP module status: "Major Unrecoverable Fault" The Communication Unit has an unrecoverable fault.

Off Blinking

CIP module status: "Major Recoverable Fault" The Communication Unit has a recoverable fault.

On Off

CIP module status: "Operational" The Communication Unit is working correctly.

Blinking Off

CIP module status: "Standby" The Communication Unit has not been completely configured yet, or the configuration is incorrect.

E84DG056

Blinking Blinking

CIP module status: "Device Self Testing" The Communication Unit performs a self-test.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 78

Diagnostics

250 ms

LED status displays

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

LED Colour / status Description

NS Green Red

Off Off CIP network status: "No IP Address"

The Communication Unit is not supplied with voltage or does not yet have an IP address.

Off On

CIP network status: "Duplicate IP" The Communication Unit cannot access the fieldbus (IP address conflict).

Off Blinking

CIP network status: "Connection Timeout" A time-out is executed.

On Off

CIP network status: "Connected" The Communication Unit is working correctly and has established a

connection to the scanner.

Blinking Off

CIP network status: "No Connections" The Communication Unit ...

•is working correctly;

• has been assigned an IP address;

• has not been integrated into the network by the scanner yet.

Blinking Blinking

CIP network status: "Self-Test" The Communication Unit performs a self-test.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Diagnostics

Diagnosing with the »Engineer«

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

11.2 Diagnosing with the »Engineer«

In the »Engineer« under the Diagnostics tab, you will find EtherNet/IP diagnostics information.

Display Code

MAC-ID C13003

Active IP Address C13010

Active Subnetwork Mask C13011

Active Gateway Address C13012

Active multicast IP address C13016

Process data C13850, C13851

CIP Module Status C13861

CIP Network Status C13862

Ethernet Port X31 Link State C13863/1

Ethernet Port X32 Link State C13863/2

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 80

Error messages

Short overview of the EtherNet/IP error messages

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

12 Error messages

This chapter complements the error list in the software manual and the »Engineer« online help for the Inverter Drive 8400 motec by EtherNet/IP error messages.

12.1 Short overview of the EtherNet/IP error messages

 Software manual/»Engineer« online help for the Inverter Drive 8400 motec

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 444 33042 EtherNet/IP: Explicit Message Timeout 0: No Response C13880/3

0x01bc8114 444 33044 EtherNet/IP: Overall Ethernet Timeout 0: No Response C13880/4

0x01bc8132 444 33074 EtherNet/IP: Idle Mode

0x01bc8273 444 33395 EtherNet/IP: Duplicate IP Address 1: No Response -

Subject area no. [dec]

444 12544 EtherNet/IP: Exist. connect. to 8400 lost 1: No Response C01501/2

444 21809 EtherNet/IP: Memory: No Access 1: No Response C01501/2

444 21810 EtherNet/IP: Memory: Read Error 1: No Response C01501/2

444 21811 EtherNet/IP: Memory: Write Error

444 24592 EtherNet/IP: Restart by watchdog reset 1: No Response C01501/2

444 24593 EtherNet/IP: Internal Error 1: No Response C01501/2

444 24832 EtherNet/IP: Internal Error 1: No Response C01501/2

444 24833 EtherNet/IP: Internal Error 1: No Response C01501/2

444 25631 EtherNet/IP: Invalid Parameter Set 1: No Response C01501/2

444 25632 EtherNet/IP: Error: Lenze Setting Loaded 1: No Response -

444 25648 EtherNet/IP: Invalid Configuration 1: No Response -

444 25907 EtherNet/IP: Invalid IP Parameter 1: No Response -

444 33041 EtherNet/IP: Fault Mode 1: No Response C13880/2

Error no. [dec]

Error text Error type

(nt14: COM fault 14)

(nt05: COM fault 5)

(Error response)

1: No Response C01501/2

0: No Response C13880/1

Adjustable in

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Error messages

Possible causes and remedies

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

12.2 Possible causes and remedies

This chapter lists all EtherNet/IP error messages in the numerical order of the error numbers. Possible causes and remedies as well as responses to the error messages are described in detail.

EtherNet/IP: Exist. connect. to 8400 lost [0x01bc3100]

Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response)

 None  System fault  Fault  Trouble  Quick stop by trouble  Warning locked  Warning  Information

Cause Remedy

• The Communication Unit is being supplied with external voltage but the Inverter Drive 8400 motec is not being supplied with voltage.

• The Communication Unit is not correctly connected to the Drive Unit.

• Switch the voltage supply of the Inverter Drive 8400 motec off and on again.

• Check wiring and terminals.

• Check internal plug connection between Communication Unit and Drive Unit. For this purpose, the Inverter Drives 8400 motec has to be unscrewed. Please observe the information provided in the mounting instructions of the Communication Unit and Drive Unit.

• If this error continues to occur, please contact the Lenze service. (it might be necessary to replace the Communication Unit.)

EtherNet/IP: Memory: No Access [0x01bc5531]

Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response)

 No reaction  System fault  Fault  Trouble  Quick stop by trouble  WarningLocked  Warning  Information

Cause Remedy

Access to memory was not possible. Send the device and a description of the fault to Lenze.

EtherNet/IP: Memory: Read Error [0x01bc5532]

Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response)

 No reaction  System fault  Fault  Trouble  TroubleQuickStop  WarningLocked  Warning  Information

Cause Remedy

Parameter could not be read. • Download application again (including module).

EtherNet/IP: Memory: Write Error [0x01bc5533] (nt14: COM fault 14)

Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response)

 No reaction  System fault  Fault  Trouble  TroubleQuickStop  WarningLocked  Warning  Information

Cause Remedy

Parameter could not be written. • Download application again (including module).

• Send the device and a description of the fault to Lenze.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 82

Error messages

Possible causes and remedies

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

EtherNet/IP: Restart by watchdog reset [0x01bc6010]

Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response)

 No reaction  System fault  Fault  Trouble  TroubleQuickStop  WarningLocked  Warning  Information

Cause Remedy

Device is defective. Send the device and a description of the fault to Lenze.

EtherNet/IP: Internal Error [0x01bc6011]

Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response)

 No reaction  System fault  Fault  Trouble  Quick stop by trouble  WarningLocked  Warning  Information

Cause Remedy

Device is defective. Send the device and a description of the fault to Lenze.

EtherNet/IP: Internal error [0x01bc6100]

Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response)

 No reaction  System fault  Fault  Trouble  TroubleQuickStop  WarningLocked  Warning  Information

Cause Remedy

Device is defective. Send the device and a description of the fault to Lenze.

EtherNet/IP: Internal error [0x01bc6101]

Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response)

EtherNet/IP: Invalid parameter set [0x01bc641f]

EtherNet/IP: Lenze setting Loaded [0x01bc6420]

 No reaction  System fault  Fault  Trouble  TroubleQuickStop  WarningLocked  Warning  Information

Cause Remedy

Device is defective. Send the device and a description of the fault to Lenze.

Response (Lenze setting printed in bold) Setting: C01501/2 ( Adjustable response)

 No reaction  System fault  Fault  Trouble  TroubleQuickStop  WarningLocked  Warning  Information

Cause Remedy

No active parameter set could be loaded. • Download application again (including module).

Response (Lenze setting printed in bold) Setting: not possible

 None  System fault  Fault  Trouble  Quick stop by trouble  Warning locked  Warning  Information

• Send the device and a description of the fault to Lenze.

Cause Remedy

Access to parameter set was not possible. • Download application again (including module).

• Send the device and a description of the fault to Lenze.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Error messages

Possible causes and remedies

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

EtherNet/IP: Invalid Configuration [0x01bc6430]

Response (Lenze setting printed in bold) Setting: not possible

 None  System fault  Fault  Trouble  Quick stop by trouble  Warning locked  Warning  Information

Cause Remedy

Module configuration is faulty. Check and correct module configuration.

EtherNet/IP: Invalid IP Parameters [0x01bc6533]

Response (Lenze setting printed in bold) Setting: not possible

 None  System fault  Fault  Trouble  Quick stop by trouble  Warning locked  Warning  Information

Cause Remedy

One or more IP parameters are faulty. Check and correct IP configuration.

Setting the IP configuration of the Inverter Drive 8400 motec ( 30)

EtherNet/IP: Fault Mode [0x01bc8111]

Response (Lenze setting printed in bold) Setting: C13880/2

 No reaction  System fault  Fault  Trouble  TroubleQuickStop  WarningLocked  Warning  Information

Cause Remedy

• Connection to scanner has been interrupted.

• Controlling I/O connection failed by timeout.

• Within the timeout time for implicit messages parameterised by the scanner, no "implicit messages" have been received.

EtherNet/IP: Explicit Message Timeout [0x01bc8112]

Response (Lenze setting printed in bold) Setting: C13880/3

 None  System error  Error  Fault  Quick stop by trouble  Warning locked  Warning  Information

Cause Remedy

• Connection to scanner has been interrupted.

• Failure of an explicit connection

• Within the timeout time for explicit messages parameterised by the scanner, no "explicit messages" have been received.

EtherNet/IP: Overall Ethernet Timeout [0x01bc8114]

Response (Lenze setting printed in bold) Setting: C13880/4

 None  System error  Error  Fault  Quick stop by trouble  Warning locked  Warning  Information

• Check cables and terminals.

• Plug the network cable into the EtherNet/IP terminal.

• Check Requested Package Interval (RPI) of I/O connection.

• Increase timeout time for implicit messages.

• Check cables and terminals.

• Plug the network cable into the EtherNet/IP terminal.

• Check Requested Package Interval (RPI) of the explicit connection.

• Increase timeout time for explicit messages.

Cause Remedy

• Failure of »Engineer« communication via Ethernet

• When the time set in C13881 access via the »Engineer«.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 84

has expired, there is no

• Check cables and terminals.

• Plug in network cable.

• Increase the overall Ethernet timeout time in C13881

Fault with regard to EtherNet/IP communication ( 77)

Error messages

Possible causes and remedies

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

EtherNet/IP: Idle Mode [0x01bc8132] (nt05: COM fault 5)

Response (Lenze setting printed in bold) Setting: C13880/1

 None  System error  Error  Fault  Quick stop by trouble  Warning locked  Warning  Information

Cause Remedy

• Scanner has received an idle event.

• The scanner is in the "PROG" mode.

• In the "Scanner Command Register", the run/ idle flag (bit 0) is 0.

EtherNet/IP: Duplicate IP Address [0x01bc8273]

Response (Lenze setting printed in bold) Setting: not possible

 None  System fault  Fault  Trouble  Quick stop by trouble  Warning locked  Warning  Information

Cause Remedy

An IP address has been allocated twice within the network. The addresses of the network nodes must differ from each other.

Set the scanner to the run mode. Run/idle flag (bit 0) = 1

Correct the IP address (C13000

Setting the IP configuration of the Inverter Drive 8400 motec ( 30)

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Error messages

CIP™ error messages

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

12.3 CIP™ error messages

Error code

[hex]

0x000 SUCCESS No error

0x001 . . . Instance error messages

0x002 RESOURCE_UNAVAILABLE Resource required to perform the service not available.

0x003 INVALID_PARAM_VALUE Invalid parameter value

0x008 SERVICE_NOT_SUPP Service is not supported.

0x009 INVALID_ATTRIB_VALUE Invalid attribute.

0x00B ALREADY_IN_STATE The object is already in the required state.

0x00C OBJ_STATE_CONFLICT The object cannot perform the service.

0x00E ATTR_NOT_SETTABLE The attribute is write-protected.

0x00F PRIVILEGE_VIOLATION Access denied.

0x010 DEVICE_STATE_CONFLICT The current state of the device prohibits performing the

0x011 REPLY_DATA_TOO_LARGE The response data are longer than the response buffer

0x013 NOT_ENOUGH_DATA The data length is too short.

0x014 ATTRIBUTE_NOT_SUPP The attribute is not supported.

0x015 TOO_MUCH_DATA The data length is too long.

0x016 OBJECT_DOES_NOT_EXIST The object is not supported by the adapter.

0x017 FRAGMENTATION The fragmentation for the requested service is currently not

0x020 INVALID_PARAMETER Invalid parameter

Error designation Description

( 121) of the Connection Manager

Object (6 / 0x06) ( 120)

requested service.

activated.

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 86

Error messages

Mapping of Lenze device errors to DRIVECOM errors

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

12.4 Mapping of Lenze device errors to DRIVECOM errors

Via the instance attribute "FaultCode" of the Control Supervisor Object (41 / 0x29) ( 135) Lenze device errors are output with the DRIVECOM error numbers.

The following tables show the assignment of the Lenze device errors and "CAN Emergency Error Codes" to the DRIVECOM errors.

 Software manual/»Engineer« online help for the Inverter Drive 8400 motec

Here you will find detailed information about the Lenze error messages listed in the following table.

Lenze error CAN DRIVECOM error

Error number

[32 bits]

xx.0111.00002 Su02: One mains phase is missing 0x3000 0x3000 Voltage

xx.0111.00003 Su03: Too frequent mains switching 0x3000 0x3000 Voltage

xx.0111.00004 Su04: CU insufficiently supplied 0x3000 0x3000 Voltage

xx.0111.00006 Su06: Power input overload 0x3000 0x3000 Voltage

xx.0119.00000 OH4: Heat sink temp. > Switch-off temp. -5°C 0x4000 0x4000 Temperature

xx.0119.00001 OH1: Heatsink overtemperature 0x4000 0x4000 Temperature

xx.0119.00002 OH7: Motor temperature resolver > C121 0x4000 0x4000 Temperature

xx.0119.00003 OH9: Motor overtemperature resolver 0x4000 0x4000 Temperature

xx.0119.00012 Sd6: Error temperature sensor resolver 0x7300 0x7300 Sensor

xx.0119.00015 OH3: Motor temperature (X106) triggered 0x4000 0x4000 Temperature

xx.0119.00020 OH6: Motor temperature MultiEncoder > C12 1 0x4000 0x4000 Temperature

xx.0119.00021 OH12: Motor overtemperature MultiEncoder 0x4000 0x4000 Temperature

xx.0119.00022 Sd12: Error temperature sensor MultiEncoder 0x7300 0x7300 Sensor

xx.0119.00050 OC5: Ixt overload 0x2000 0x2000 Current

xx.0123.00001 OT1: Maximal torque reached 0x8300 0x8302 Torque limiting

xx.0123.00007 OC7: Motor overcurrent 0x2000 0x2000 Current

xx.0123.00014 OU: DC bus overvoltage 0x3100 0x3110 Mains overvoltage

xx.0123.00015 LU: DC bus undervoltage 0x3100 0x3120 Mains undervoltage

xx.0123.00016 OC1: Power section - short circuit 0x2000 0x2130 Short Circuit

xx.0123.00017 OC2: Power section - earth fault 0x2000 0x2120 Short to Earth

xx.0123.00024 Sd2: Wire breakage resolver 0x7300 0x7303 Resolver 1 defective

xx.0123.00026 Sd7: Error encoder communication 0x7300 0x7305 Incremental encoder 1 defective

xx.0123.00027 Sd4: Wire breakage MultiEncoder 0x7300 0x7300 Sensor

xx.0123.00030 OC10: Maximum current reached 0x2000 0x2000 Current

xx.0123.00031 OC17: Clamp sets pulse inhibit 0xF000 0xF000 Additional functions

xx.0123.00032 OS1: Maximum speed limit reached 0x8400 0x8402 Velocity Limiting

xx.0123.00033 OS2: Max. motor speed 0x8400 0x8400 Speed Controller

xx.0123.00056 ID2: Motor data identification error 0xF000 0xF000 Additional functions

xx.0123.00057 ID1: Motor data identification error 0xF000 0xF000 Additional functions

xx.0123.00058 ID3: CINH motor data identification 0xF000 0xF000 Additional functions

xx.0123.00059 ID4: Error resistor identification 0xF000 0xF000 Additional functions

xx.0123.00060 ID7: Motor control does not match motor data 0xF000 0xF000 Add itional functions

xx.0123.00062 Sd8: Encoder angular drift monitoring 0x7300 0x7300 Sensor

xx.0123.00065 OC12: I2xt overload - brake resistor 0xF000 0x7110 Brake Chopper

xx.0123.00071 OC11: Current clamp for too long (>1 sec) 0xF000 0xF000 Additional functions

xx.0123.00074 ID5: Error pole position identification 0xF000 0xF000 Additional functions

xx.0123.00075 ID6: Error resolver ident. 0xF000 0xF000 Additional functions

Error message Emergency

Error Code

Error number

[hex]

Error message

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Error messages

Mapping of Lenze device errors to DRIVECOM errors

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Lenze error CAN DRIVECOM error

Error number

[32 bits]

xx.0123.00090 OC13: Maximum current for Fch exceeded 0x2000 0x2000 Current

xx.0123.00093 OT2: Speed controller output is limited 0xF000 0x7310 Speed

xx.0123.00094 FC01: Switching frequency reduction 0x2000 0xF000 Additional functions

xx.0123.00095 FC02: Maximum speed for Fchop 0xF000 0xF000 Additional functions

xx.0123.00096 OC14: Limitation direct-axis current controller 0xF000 0xF000 Additional functions

xx.0123.00097 OC15: Limitation cross current controller 0xF000 0xF000 Additional functions

xx.0123.00098 OC16: Limitation torque controller 0xF000 0xF000 Additional functions

xx.0123.00099 FC03: Limitation field controller 0xF000 0xF000 Additional functions

xx.0123.00105 OC6: I2xt overload - motor 0x2000 0x7120 Motor

xx.0123.00145 LP1: Motor phase failure 0x3000 0x3130 Phase Failure

xx.0123.00200 SD10: Speed limit - feedback system 12 0x7300 0x7300 Sensor

xx.0123.00201 SD11: Speed limit - feedback system 67 0x7300 0x7300 Sensor

xx.0123.00205 SD3: Open circuit - feedback system 0x7300 0x7301 Tacho defective

xx.0125.00001 An01: AIN1_I < 4 mA 0xF000 0xF000 Additional functions

xx.0125.00002 An02: AIN2_I < 4 mA 0xF000 0xF000 Additional functions

xx.0126.00001 Ab01: Axis bus timeout 0x8000 0x8000 Monitoring

xx.0126.00002 Ab02: Axis bus IO error 0x8100 0x8100 Communication

xx.0127.00002 CE04: MCI communication error 0x7000 0x7500 Communication

xx.0127.00015 CE0F: MCI control word 0xF000 0xF000 Additional functions

xx.0131.00000 CE4: CAN Bus Off 0x8000 0x8000 Monitoring

xx.0131.00006 CA06: CAN CRC error 0x8000 0x8000 Monitoring

xx.0131.00007 CA07: CAN Bus Warn 0x8000 0x8000 Monitoring

xx.0131.00008 CA08: CAN Bus Stopped 0x8000 0x8000 Monitoring

xx.0131.00011 CA0b: CAN HeartBeatEvent 0x8130 0x8000 Monitoring

xx.0131.00015 CA0F: CAN control word 0xF000 0x8000 Monitoring

xx.0135.00001 CE1: CAN RPDO1 0x8100 0x8100 Communication

xx.0135.00002 CE2: CAN RPDO2 0x8100 0x8100 Communication

xx.0135.00003 CE3: CAN RPDO3 0x8100 0x8100 Communication

xx.0135.00004 CP04: CAN RPDO4 0x8100 0x8100 Communication

xx.0140.00013 CI01: Module missing/incompatible 0x7000 0x7000 Additional Modules

xx.0144.00001 PS01: No memory module 0x6300 0x6300 Date Set

xx.0144.00002 PS02: Par. set invalid 0x6300 0x6300 Date Set

xx.0144.00003 PS03: Par. set device invalid 0x6300 0x6300 Date Set

xx.0144.00004 PS04: Par. set device incompatible 0x6300 0x6300 Date Set

xx.0144.00007 PS07: Par. mem. module invalid 0x6300 0x6300 Date Set

xx.0144.00008 PS08: Par. device invalid 0x6300 0x6300 Date Set

xx.0144.00009 PS09: Par. format invalid 0x6300 0x6300 Date Set

xx.0144.00010 PS10: Memory module link invalid 0x5000 0x5000 Device Hardware

xx.0144.00031 PS31: Ident. error 0x6300 0x6300 Date Set

xx.0145.00014 dF14: SW-HW invalid 0x5530 0x6000 Device software

xx.0145.00015 dF15: DCCOM CU2 error 0x6100 0x6100 Internal software

xx.0145.00024 dF18: BU RCOM error 0x6100 0x6100 Internal software

xx.0145.00025 dF25: CU RCOM error 0x6100 0x6100 Internal software

xx.0145.00026 dF26: Appl. watchdog 0x6200 0x6010 Software reset (watchdog)

xx.0145.00033 dF21: BU watchdog 0x6100 0x6010 Software reset (watchdog)

xx.0145.00034 dF22: CU Watchdog 0x6100 0x6010 Software reset (watchdog)

xx.0145.00035 dF10: AutoTrip reset 0xF000 0xF000 Additional functions

xx.0145.00050 dF50: Retain error 0x6100 0x6100 Internal software

xx.0145.00051 dF51: CuCcr error 0x6100 0x6100 Internal software

xx.0145.00052 dF52: BuCcr error 0x6100 0x6100 Internal software

Error message Emergency

Error Code

Error number

[hex]

Error message

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 88

Error messages

Mapping of Lenze device errors to DRIVECOM errors

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Lenze error CAN DRIVECOM error

Error number

[32 bits]

xx.0184.00001 Ck01: Pos. HW limit switch 0x8600 0x8600 Positioning controller

xx.0184.00002 Ck02: Neg. HW limit switch 0x8600 0x8600 Positioning controller

xx.0184.00005 Ck15: Error message sig. brake 0x8600 0x8600 Positioning controller

xx.0184.00007 Ck03: Pos. SW limit position 0x8600 0x8600 Positioning controller

xx.0184.00008 Ck04: Neg. SW limit position 0x8600 0x8600 Positioning controller

xx.0184.00015 Ck14: Target position outside SW limit

xx.0184.00064 Ck16: Time overrun manual operation 0x8600 0x8600 Positioning controller

xx.0184.00153 Ck05: Error following error 1 0x8611 0x8611 Following error

xx.0184.00154 Ck06: Error following error 2 0x8611 0x8611 Following error

xx.0184.00155 Ck07: Traversing range limit exceeded 0x8612 0x8612 Reference limit

xx.0184.00156 Ck08: Reference position unknown 0x8612 0x8612 Reference limit

xx.0184.08005 Ck09: Positioning mode invalid 0x8600 0x8600 Positioning controller

xx.0184.08007 Ck10: Profile data implausible 0x8600 0x8600 Positioning controller

xx.0184.08009 Ck11: Operating mode inva lid 0x8600 0x8600 Positioning controller

xx.0184.08014 Ck12: Profile number invalid 0x8600 0x8600 Positioning controller

xx.0184.08015 Ck13: Error FB MCKCtrlInterface 0x8600 0x8600 Positioning controller

xx.0400.00009 dH09: EEPROM power unit 0x5530 0x7600 Data memory

xx.0400.00016 dH10: Fan failure 0x5000 0x5000 Device Hardware

xx.0400.00104 dH68: Adjustment data error CU 0x5530 0x6000 Device software

xx.0400.00105 dH69: Adjustment data error BU 0x5530 0x6000 Device software

xx.0980.00001 User error 1 0x6200 0x6200 User software

xx.0981.00002 User error 2 0x6200 0x6200 User software

xx.0982.00003 User error 3 0x6200 0x6200 User software

xx.0983.00004 User error 4 0x6200 0x6200 User software

xx.0984.00001 User error 5 0x6200 0x6200 User software

xx.0985.00002 User error 6 0x6200 0x6200 User software

xx.0986.00003 User error 7 0x6200 0x6200 User software

xx.0987.00004 User error 8 0x6200 0x6200 User software

Error message Emergency

position

Error Code

0x8600 0x8600 Positioning controller

Error number

[hex]

Error message

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Error messages

Mapping of Lenze device errors to DRIVECOM errors

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

EtherNet/IP error messages

Lenze error DRIVECOM error

Error number

[32 bits]

xx.0444.12544

xx.0444.21809

xx.0444.21810

xx.0444.21811

xx.0444.24592

xx.0444.24593

xx.0444.24832

xx.0444.24833

xx.0444.25631

xx.0444.25632

xx.0444.25648

xx.0444.25907

xx.0444.33041

xx.0444.33042

xx.0444.33044

xx.0444.33074

xx.0444.33395

Error message Error number

EtherNet/IP: Exist. connect. to 8400 lost 0x7510 Serial Interface No 1

EtherNet/IP: Memory: No Access 0x7600 Data memory

EtherNet/IP: Memory: Read Error 0x7600 Data memory

EtherNet/IP: Memory: Write Error 0x7600 Data memory

EtherNet/IP: Restart by Watchdogreset 0x6010 Software reset (watchdog)

EtherNet/IP: Internal Error 0x6100 Internal software

EtherNet/IP: Invalid Parameter Set 0x7421 Invalid Parameters

EtherNet/IP: Error: Lenze Setting Loaded 0x7421 Invalid Parameters

EtherNet/IP: Invalid Configuration 0x7421 Invalid Parameters

EtherNet/IP: Invalid IP Parameter 0x7421 Invalid Parameters

EtherNet/IP: Fault Mode 0x7000 Additional Modules

EtherNet/IP: Explicit Message Timeout 0x7500 Communication

EtherNet/IP: Overall Ethernet Timeout 0x7500 Communication

EtherNet/IP: Idle Mode 0x7000 Additional Modules

EtherNet/IP: Duplicate IP Address 0x7421 Invalid Parameters

[hex]

Error message

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 90

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

13 Parameter reference

This chapter supplements the parameter list and the table of attributes in the software manual and the »Engineer« online help for the Inverter Drive 8400 motec by the parameters of the E84DGFCGxxx Communication Unit (EtherNet/IP).

13.1 Parameters of the Communication Unit

 Software manual/»Engineer« online help for the Inverter Drive 8400 motec

Here you will find general information on parameters.

This chapter lists the parameters of the E84DGFCGxxx Communication Unit (EtherNet/IP) in numerically ascending order.

C13000

C13001

Parameter | Name:

C13000 | IP Address

Setting of the IP address

Setting the IP configuration of the Inverter Drive 8400 motec

Setting range (min. value | unit | max. value)

0 255

Subcodes Lenze setting Info

C13000/1 192 IP address (most significant byte)

C13000/2 168 IP address

C13000/3 124 IP address

C13000/4 16 IP address (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13001 | Subnetwork Mask

Setting of the subnet mask

Setting the IP configuration of the Inverter Drive 8400 motec

Setting range (min. value | unit | max. value)

0 255

Subcodes Lenze setting Info

C13001/1 255 Subnet mask (most significant byte)

C13001/2 255 Subnet mask

C13001/3 255 Subnet mask

C13001/4 0 Subnet mask (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 30)

Data type: UNSIGNED_8

Index: 11575 = 0x2D37

Data type: UNSIGNED_8

Index: 11574 = 0x2D36

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

C13002

C13003

C13005

Parameter | Name:

C13002 | Gateway Address

Setting of the gateway address

Setting the IP configuration of the Inverter Drive 8400 motec

Setting range (min. value | unit | max. value)

0 255

Subcodes Lenze setting Info

C13002/1 0 Gateway address (most significant byte)

C13002/2 0 Gateway address

C13002/3 0 Gateway address

C13002/4 0 Gateway address (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13003 | MAC ID

Display of the MAC-ID

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13005 | IP Config Control

Selection how the IP configuration is to be effected. (Instance attribute 3 (Configuration Control) in the TCP/IP Interface Object (245 / 0xF5)

Setting the IP configuration of the Inverter Drive 8400 motec

Selection list (Lenze setting printed in bold) Info

0 Use stored IP The IP configuration currently saved in the

1Use BOOTP The IP configuration is assigned by the scanner using

2 Use DHCP The IP configuration is assigned by the scanner using

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 30)

( 126))

( 30)

Communication Unit is used.

BOOTP.

DHCP. The assignment of a gateway address which is not in the same subnetwork than the IP address, is rejected.

Data type: UNSIGNED_8

Data type: OCTET_STRING

Data type: UNSIGNED_8

Index: 11573 = 0x2D35

Index: 11572 = 0x2D34

Index: 11570 = 0x2D32

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 92

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

C13006

C13010

Parameter | Name:

C13006 | Multicast IP Start Address

Setting of the multicast IP address

Setting the IP configuration of the Inverter Drive 8400 motec

Setting range (min. value | unit | max. value)

0 255

Subcodes Lenze setting Info

C13006/1 239 Multicast IP start address (most significant byte)

C13006/2 64 Multicast IP start address

C13006/3 2 Multicast IP start address

C13006/4 224 Multicast start address (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13010 | Active IP Address

Display of the active IP address (Instance attribute 5 (IP Address) in the TCP/IP Interface Object (245 / 0xF5)

Display range (min. value | unit | max. value)

0 255

Subcodes Info

C13010/1 Active IP address (most significant byte)

C13010/2 Active IP Address

C13010/3 Active IP Address

C13010/4 Active IP address (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 30)

( 126))

Data type: UNSIGNED_8

Index: 11569 = 0x2D31

Data type: UNSIGNED_8

Index: 11565 = 0x2D2D

C13011

Parameter | Name:

C13011 | Active Subnetwork Mask

Display of the active subnetwork mask (Instance attribute 5 (IP Network Mask) in the TCP/IP Interface Object (245 / 0xF5)

Display range (min. value | unit | max. value)

0 255

Subcodes Info

C13011/1 Active subnet mask (most significant byte)

C13011/2 Active Subnetwork Mask

C13011/3 Active Subnetwork Mask

C13011/4 Active subnet mask (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 126))

Data type: UNSIGNED_8

Index: 11564 = 0x2D2C

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

C13012

C13016

Parameter | Name:

C13012 | Active Gateway Address

Display of the active gateway address (Instance attribute 5 (Gateway Address) in the TCP/IP Interface Object (245 / 0xF5)

Display range (min. value | unit | max. value)

0 255

Subcodes Info

C13012/1 Active gateway address (most significant byte)

C13012/2 Active gateway address

C13012/3 Active gateway address

C13012/4 Active gateway address (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13016 | Active Multicast IP Address

Display of the active multicast IP address

Display range (min. value | unit | max. value)

0 255

Subcodes Info

C13016/1 Multicast IP address (most significant byte)

C13016/2 Multicast IP address

C13016/3 Multicast IP address

C13016/4 Multicast IP address (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 126))

Data type: UNSIGNED_8

Index: 11563 = 0x2D2B

Data type: UNSIGNED_8

Index: 11559 = 0x2D27

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 94

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

C13017

Parameter | Name:

C13017 | Ethernet Config Control

Setting of the baud rate for the Ethernet connections

Selection list

0Auto-Negotiation

1 10 Mbps

2 100 Mbps

3 Reserved

4 Reserved

5 10 Mbps/Half Duplex

6 10 Mbps/Full Duplex

7 100 Mbps/Half Duplex

8 100 Mbps/Full Duplex

9 Reserved

10 Reserved

11 Reserved

12 Reserved

Subcodes Lenze setting Info

C13017/1 0: Auto-Negotiation Ethernet setting port X31

C13017/2 0: Auto-Negotiation Ethernet setting port X32

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Data type: UNSIGNED_16

Index: 11558 = 0x2D26

C13018

C13019

Parameter | Name:

C13018 | Multicast Config Alloc Control

Selection for multicast IP addressing via instance attribute 9 (Mcast Config) in the TCP/IP Interface Object (245 /

0xF5) ( 126)

Selection list (Lenze setting printed in bold)

0 Default Allocation Algorithm

1 Multicast IP Start Address

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13019 | Multicast Config TTL Value

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)

Setting range (min. value | unit | max. value) Lenze setting

1 255 1

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 126))

Data type: UNSIGNED_8

Index: 11557 = 0x2D25

Data type: UNSIGNED_8

Index: 11556 = 0x2D24

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

C13020

C13021

C13022

Parameter | Name:

C13020 | Multicast Config Num Mcast

Used to set how many multicast IP addresses will be assigned. (Instance attribute 9 (Num Mcast) in the TCP/IP Interface Object (245 / 0xF5)

Setting range (min. value | unit | max. value) Lenze setting

181

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13021 | Quality of Service (VLAN-Tagging)

Used to set whether QoS tags will be used for the prioritisation of the data packets to be transferred. (Instance attribute 1 (802.1Q Tag Enable) in the Quality of Service (QoS) Object (72 / 0x48)

Selection list (Lenze setting printed in bold)

0 802.1Q Tag Disable

1 802.1Q Tag Enable

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13022 | Quality of Service (DSCP)

Setting for the prioritisation of the data packets to be transferred using Differentiated Services Codepoints (DSCP)

Setting range (min. value | unit | max. value)

063

Subcodes Lenze setting Info

C13022/1 59 Reserved

C13022/2 47 Reserved

C13022/3 55 Reserved

C13022/4 47 QoS DSCP Scheduled

(Instance attribute 5 (DSCP Scheduled) in the Quality of

Service (QoS) Object (72 / 0x48) ( 124))

C13022/5 43 QoS DSCP High Prio

(Instance attribute 6 (DSCP High Prio) in the Quality of

Service (QoS) Object (72 / 0x48) ( 124))

C13022/6 31 Reserved

C13022/7 27 QoS DSCP Explicit Msg

(Instance attribute 8 (DSCP Explicit Msg.) in the Quality

of Service (QoS) Object (72 / 0x48) ( 124))

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 126))

Data type: UNSIGNED_8

Index: 11555 = 0x2D23

Data type: UNSIGNED_8

Index: 11554 = 0x2D22

( 124))

Data type: UNSIGNED_8

Index: 11553 = 0x2D21

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 96

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

C13840

C13841

C13842

Parameter | Name:

C13840 | DLR Network Topology

Display of the used DLR network topology (Device Level Ring) (Instance attribute 1 (Network Topology) in the Device Level Ring (DLR) Object (71 / 0x47)

( 122))

Selection list (read only)

0 Linear

1 Ring

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13841 | DLR Network Status

Display of the DLR network status (Device Level Ring) (Instance attribute 2 (Network Status) in the Device Level Ring (DLR) Object (71 / 0x47)

( 122))

Selection list (read only)

0 Normal

1 Ring Fault

2 Unexpected Loop detected

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Data type: UNSIGNED_8

Index: 10735 = 0x29EF

Data type: UNSIGNED_8

Index: 10734 = 0x29EE

C13843

Parameter | Name:

Data type: UNSIGNED_8

C13842 | Supervisor IP Address

Display of the supervisor IP address (Instance attribute 10 (Supervisor IP Address) in the Device Level Ring (DLR) Object (71 / 0x47)

( 122))

Display range (min. value | unit | max. value)

0 255

Subcodes Info

C13842/1 Supervisor IP address (most significant byte)

C13842/2 Supervisor IP Address

C13842/3 Supervisor IP Address

C13842/4 Supervisor IP address (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13843 | Supervisor MAC ID

Data type: OCTET_STRING

Index: 10732 = 0x29EC

Display of the supervisor MAC ID (Instance attribute 10 (Supervisor MAC Address) in the Device Level Ring (DLR) Object (71 / 0x47)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 122))

10733 = 0x29ED

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

C13844

C13845

C13846

Parameter | Name:

Data type: UNSIGNED_32

C13844 | Beacon Times

Display of the beacon times (μs)

Subcodes Info

C13844/1 Beacon interval

C13844/2 Beacon timeout

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

Data type: UNSIGNED_32

C13845 | Beacon Frames

Display of beacon frame information

Subcodes Info

C13845/1 Beacon frames - port X31

C13845/2 Beacon frame error - port X31

C13845/3 Beacon frames - port X32

C13845/4 Beacon frame error - port X32

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13846 | Address Conflict Detection

Activation of the address conflict detection (ACD) (Instance attribute 10 (SelectAcd) in the TCP/IP Interface Object (245 / 0xF5)

( 126))

Changing this value requires a reset of the device ("power off/on" or "type 0 reset").

Selection list (Lenze setting printed in bold)

0 Deactivated

1Enable

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Index: 10731 = 0x29EB

Index: 10730 = 0x29EA

Data type: UNSIGNED_8

Index: 10729 = 0x29E9

C13847

Parameter | Name:

C13847 | Active Conflict Detection State

Data type: UNSIGNED_8

Index: 10728 = 0x29E8

Display of the status of address conflict detection (ACD)

Selection list (read only)

0 Not conflicted

1 Conflicted

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 98

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

C13848

C13849

Parameter | Name:

C13848 | Last Conflicted MAC ID

Display of the MAC address of the EtherNet/IP node with the last address conflict (ACD). The data of the last conflict will only be saved in this code if ACD is active at the moment when the conflict occurs

(C13846 (Instance attribute 11 (RemoteMAC) in the TCP/IP Interface Object (245 / 0xF5)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13849 | Last Conflicted IP Address

Display of the IP address of the EtherNet/IP node with the last address conflict (ACD). The data of the last conflict will only be saved in this code if ACD is active at the moment when the conflict occurs

(C13846

Display range (min. value | unit | max. value)

0 255

Subcodes Info

C13849/1 Last conflicted IP address (most significant byte)

C13849/2 Last conflicted IP address

C13849/3 Last conflicted IP address

C13849/4 Last conflicted IP address (least significant byte)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

=1).

( 126))

=1).

Data type: OCTET_STRING

Index: 10727 = 0x29E7

Data type: UNSIGNED_8

Index: 10726 = 0x29E6

C13850

Parameter | Name:

C13850 | All words to scanner

Display of the I/O data words transferred from the Communication Unit (adapter) to the scanner. In the subcodes, all I/O data words transferred to the scanner are displayed. However, only the configured I/O data words are valid.

Display range (min. value | unit | max. value)

-32768 32767

Subcodes Info

C13850/1

...

C13850/10

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Data type: INTEGER_16

Index: 10725 = 0x29E5

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013

Parameter reference

Parameters of the Communication Unit

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

C13851

C13858

Parameter | Name:

C13851 | All words from scanner

Display of the I/O data words transferred from the scanner to the Communication Unit (adapter). In the subcodes, all I/O data words transferred from the scanner are displayed. However, only the configured I/O

data words are valid.

Display range (min. value | unit | max. value)

-32768 32767

Subcodes Info

C13851/1

...

C13851/8

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13858 | Ethernet Port Statistics

Display of statistical values for the data transfer via the Ethernet connections

Subcodes Info

C13858/1 Ethernet port X31: RX

C13858/2 Ethernet port X31: RX CRC error

C13858/3 Ethernet port X31: RX discarded

C13858/4 Ethernet port X31: TX

C13858/5 Ethernet port X31: TX discarded

C13858/6 Ethernet port X32: RX

C13858/7 Ethernet port X32: RX CRC error

C13858/8 Ethernet port X32: RX discarded

C13858/9 Ethernet port X32: TX

C13858/10 Ethernet port X32: TX discarded

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Data type: INTEGER_16

Index: 10724 = 0x29E4

Data type: UNSIGNED_32

Index: 10717 = 0x29DD

C13861

Parameter | Name:

C13861 | CIP Module Status

Display of the current CIP module status (Instance attribute 8 (State) in the Identity Object (1 / 0x01)

• The status is also indicated via the MS LED.

LED status displays

Selection list (read only)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013 100

( 78)

0 Nonexistent

1 Device Self Testing

2 Standby

3 Operational

4 Major Recoverable Fault

5 Major Unrecoverable Fault

( 110))

Data type: UNSIGNED_16

Index: 10714 = 0x29DA

Lenze E84DGFCG User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

1 About this documentation

1.1 Document history

1.2 Conventions used

1.3 Terminology used

1.4 Notes used

2 Safety instructions

2.1 General safety and application notes

2.2 Device and application-specific safety instructions

2.3 Residual hazards

3 Product description

3.1 Application as directed

3.2 Features and variants

3.3 Connections and interfaces

4 Technical data

4.1 General data and operating conditions

4.2 Protocol data

4.3 Communication time

4.4 Internal switch latency

5 Installation

5.1 Mechanical installation

5.2 Electrical installation

5.2.1 Network topology

5.2.2 EtherNet/IP connection

5.2.3 External voltage supply

6 Commissioning

6.1 Before initial switch-on

6.2 Configuring the host system (scanner)

6.2.1 EDS files

6.2.2 Example: IP configuration of the Allen-Bradley 1769-L32E CompactLogix controller

6.3 Setting the IP configuration of the Inverter Drive 8400 motec

6.3.1 Setting via the EtherNet/IP configurator of the »Engineer«

6.3.2 Setting via codes in the »Engineer«

6.3.3 Setting via a BOOTP/DHCP server

6.3.4 Setting via the TCP/IP Interface Object (0xF5)

6.3.5 Setting the multicast configuration

6.4 Establishing an online connection via EtherNet/IP with the Lenze »Engineer«

6.5 Initial switch-on

7 Data transfer

7.1 Communication channels

7.2 Telegram types

7.3 EtherNet/IP state diagram

8 I/O data transfer (implicit messages)

8.1 Configuring I/O data

8.2 I/O data mapping

8.3 Technology applications (TA) / drive profiles

8.3.1 Lenze technology applications / user-definable parameter sets

8.3.2 "AC Drive Profile" application

8.4 I/O assemblies

8.5 I/O configuration in the »Engineer«

8.5.1 Lenze technology application / configuring user-definable parameter sets

8.5.2 Configuring "AC Drive Profile" application

8.6 I/O configuration with »RSLogix 5000« version 19 or lower

8.7 I/O configuration with »RSLogix 5000« version 20 or higher

8.8 Saving the I/O configuration in »RSLogix 5000«

9 Parameter data transfer (explicit messages)

9.1 Write parameters

9.2 Read parameters

10 Monitoring

11 Diagnostics

11.1 LED status displays

11.2 Diagnosing with the »Engineer«

12 Error messages

12.1 Short overview of the EtherNet/IP error messages

12.2 Possible causes and remedies

12.3 CIP™ error messages

12.4 Mapping of Lenze device errors to DRIVECOM errors

13 Parameter reference

13.1 Parameters of the Communication Unit

C13000 | IP Address

C13001 | Subnetwork Mask

C13002 | Gateway Address

C13003 | MAC ID

C13005 | IP Config Control

C13006 | Multicast IP Start Address

C13010 | Active IP Address