Lenze E94AYCEO User Manual

Download

Page 1

Accessories

EtherNet/IP™

Servo Drives 9400

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

E94AYCEO

Communication Manual EN

Ä.N+ôä

13451095

Page 2

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

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 Identification _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 13

3.3 Product features _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14

3.4 Terminals and interfaces _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 15

4 Technical data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 16

4.1 General data and operating conditions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 16

4.2 Protocol data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 17

4.3 Communication time _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 17

4.4 Internal switch latency _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 18

4.5 Protective insulation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 19

4.6 Dimensions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22

5Installation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 23

5.1 Mechanical installation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 24

5.1.1 Assembly _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 24

5.1.2 Disassembly _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 24

5.2 Electrical installation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 25

5.2.1 Wiring according to EMC guidelines _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 25

5.2.2 Network topology _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 26

5.2.3 EtherNet/IP connection _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 28

5.2.4 Ethernet cable specification _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 30

5.2.5 External voltage supply _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 32

6 Commissioning _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33

6.1 Before initial switch-on _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33

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

6.2.1 EDS files _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 34

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

6.3 Setting the IP configuration of the Servo Drive 9400 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 37

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

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

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

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

6.3.5 Setting the multicast configuration _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 43

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

6.5 Initial switch-on _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 46

2 Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 3

Contents

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

7 Data transfer _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 47

7.1 Communication channels _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 48

7.2 Telegram types _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 49

7.3 EtherNet/IP state diagram _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 50

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

8.1 Technology applications (TA) / drive profiles _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 52

8.1.1 Lenze technology applications / user-definable parameter sets _ _ _ _ _ _ _ _ _ _ _ _ _ _ 52

8.1.2 I/O assemblies _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 53

8.2 I/O configuration in the »Engineer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 55

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

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

8.5 Saving the I/O configuration in »RSLogix 5000« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 69

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

9.1 Write parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 71

9.2 Read parameters _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 72

10 Monitoring _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 74

10.1 Fault with regard to EtherNet/IP communication _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 74

10.2 Interruption of internal communication _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 75

11 Diagnostics _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 76

11.1 LED status displays _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 76

11.1.1 Module status displays _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 77

11.1.2 CIP™ status displays _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 78

11.1.3 Status displays on the RJ45 sockets (X233, X234) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 80

11.2 Diagnostics with the »Engineer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 81

12 Error messages _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 82

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

12.2 Possible causes and remedies _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 83

12.3 CIP™ error messages _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 87

13 Parameter reference _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 88

13.1 Parameters of the standard device that are relevant to communication _ _ _ _ _ _ _ _ _ _ _ _ _ _ 88

13.2 Parameters of the communication module for slot MXI1 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 90

13.3 Parameters of the communication module for slot MXI2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 103

13.4 Table of attributes _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 116

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 3

Page 4

Contents

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

14 Implemented CIP™ objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 119

14.1 General CIP objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 121

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

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

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

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

14.2 EtherNet/IP objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 128

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

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

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

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

14.3 Lenze objects _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 139

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

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

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

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

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

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

4 Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 5

1 About this documentation

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

1 About this documentation

Contents

This documentation only contains descriptions of the E94AYCEO (EtherNet/IP™) communication module.

 Note!

This documentation supplements the mounting instructions supplied with the controller and the Servo Drives 9400 hardware manual.

The mounting instructions contain safety instructions which must be observed!

The features and functions of the communication module are described in detail.

Examples illustrate typical applications.

The theoretical context is only explained as far as it is required for understanding the function of the communication module.

This documentation does not describe the software of another manufacturer. No guarantee can be given for corresponding information in this documentation. Information on the use of the software can be found in the documents for the host system (PLC, scanner).

All brand names mentioned in this documentation are trademarks of their corresponding owners.

 Tip!

Detailed information on EtherNet/IP can be found on the website of the user organisation ODVA (Open DeviceNet Vendor Association):

www.odva.org

5 Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 6

1 About this documentation

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

Target group

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

 Tip!

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

www.lenze.com

Information regarding the validity

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

Extension module Type designation From hardware

version

Communication module EtherNet/IP E94AYCEO VE 01.01.00.00

Screenshots/application examples

All screenshots in this documentation are application examples. Depending on the firmware version of the communication module and software version of the installed engineering tools

From software

version

(»Engineer«, »RSLogix 5000«), the screenshots in this documentation may differ from the screen

representation.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 6

Page 7

1 About this documentation

1.1 Document history

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

1.1 Document history

Version Description

1.0 03/2012 TD17 First edition for field test version V0.3.0.0

2.0 09/2012 TD17 General revision of version V01.01.00.00

3.0 12/2013 TD17 • New layout

• Revision of the parameter descriptions

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 8

1 About this documentation

1.2 Conventions used

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

1.2 Conventions used

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

Type of information Identification Examples/notes

Numbers

Decimal Standard notation Example: 1234

Decimal separator Point In general, the decimal point is used.

Example: 1234.56

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

Binary

• Nibble

Text

Version information Text colour blue All pieces of information that only apply to or from a specific

Program name » « The Lenze PC software »Engineer«...

Control element Bold The OK button... / The Copy command... / The Properties

Sequence of menu commands

Hyperlink Underlined

Icons

Page reference ( 9) Optically highlighted reference to another page. Can be

Step-by-step instructions

In inverted commas

Point

Example: ’100’ Example: ’0110.0100’

software version of the device are highlighted accordingly in this documentation.

Example: This function extension is available from software

version V3.0!

tab... / The Name input field...

If several successive commands are required for executing a function, the individual commands are separated from each other by an arrow: Select the command File

Optically highlighted reference to another topic. Can be activated with a mouse-click in this online documentation.

activated with a mouse-click in this online documentation.

Step-by-step instructions are marked by a pictograph.

 Open to...



Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 8

Page 9

1 About this documentation

1.3 Terminology used

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

1.3 Terminology used

Term Meaning

ACD Address Conflict Detection

Adapter EtherNet/IP slave

Drive Lenze inverters of the "Servo Drives 9400" product series

Inverter

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 so-called "subcodes".

DHCP Dynamic Host Configuration Protocol

DSCP Differentiated Services Codepoints

EDS Electronic Data Sheet

»Engineer« PC software from Lenze which supports you during engineering

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.

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

This manual uses a slash "/" as a separator between code and subcode (e.g. "C00118/3"). In normal usage, the term is also referred to as "Subindex".

(parameterisation, diagnostics, and configuration) throughout the entire life cycle, i.e. from planning to maintenance of the commissioned machine.

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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 10

1 About this documentation

1.4 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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 10

Page 11

2 Safety instructions

2.1 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 applied as directed.

Application as directed

• must never be commissioned if they display signs of damage.

• must never be technically modified.

( 13)

• 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 a safe and trouble-free operation and for achieving the specified product features.

Product features

• The specifications, processes, and circuitry described in this document are for guidance only and must be adapted to your own specific application. Lenze does not take responsibility for the suitability of the process and circuit proposals.

( 14)

All works on and with Lenze drive and automation components must only be carried out by qualified personnel. According to IEC 60364 or CENELEC HD 384 these are persons who ...

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

• who have the corresponding qualifications for their work.

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

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 12

2 Safety instructions

2.2 Device and application-specific safety instructions

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

2.2 Device and application-specific safety instructions

• During operation, the communication module must be securely connected to the standard device.

• With external voltage supply, always use a separate power supply unit, safely separated to EN 61800-5-1 in every control cabinet (SELV/PELV).

• Only use cables that comply with the listed specifications.

Ethernet cable specification

( 30)

 Documentation for the standard device, control system, system/machine

All the other measures prescribed in this documentation must also be implemented. Observe the safety instructions and application notes contained in this manual.

2.3 Residual hazards

Protection of persons

If Servo Drives 9400 are used on a phase earthed mains with a rated mains voltage of  400 V, the protection against accidental contact is not ensured without external measures.

Protective insulation

Device protection

The communication module contains electronic components which may be damaged or destroyed by electrostatic discharge.

Installation

( 23)

( 19)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 12

Page 13

3 Product description

3.1 Application as directed

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

3 Product description

3.1 Application as directed

The EtherNet/IP communication module ...

• is an accessory module that can be used in conjunction with the following standard devices:

Product series Type designation From hardware

Servo Drives 9400 HighLine E94AxHExxxx 1A 04.00

Servo Drives 9400 PLC E94AxPExxxx VA 02.00

Regenerative power supply module E94ARNxxxx VA 01.00

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

Any other use shall be deemed inappropriate!

3.2 Identification

The type designation and hardware and software version of the communication module are specified on the nameplate:

E94YCDN005

version

1 Type designation (type)

E94 Product series

AVersion

Y Module identification: Extension module

C Module type: Communication module

EO EtherNet/IP

2 Hardware version (HW)

3 Software version (SW)

From software

version

[3-1] Identification data

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 14

3 Product description

3.3 Product features

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

3.3 Product features

• Interface module for the EtherNet/IP communication system to be connected to the expansion slots of the Servo Drives 9400

• The communication module can either be supplied internally by the standard device or externally by a separate voltage source.

• The Servo Drive 9400 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 32 I/O data words (64 bytes) are possible.

• Further CIP features:

• Max. 8 CIP connections

• 1 "exclusive owner" connection

• I/O connection type: cyclic

•Minimum I/O cycle time: 2 ms

• Support of multicast messages, "IGMP snooping" (V2 according to RFC 2236), UCMM, ACD, BOOTP/DHCP, VLAN tagging/DSCP

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 14

Page 15

3 Product description

3.4 Terminals and interfaces

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

3.4 Terminals and interfaces

X232 External voltage supply of the communication

module

• 2-pin plug connector with spring connection

External voltage supply

X233

EtherNet/IP terminals

X234

• RJ45-sockets

• each with 2 LED status displays for diagnostics

Network topology EtherNet/IP connection Status displays on the RJ45 sockets (X233, X234)

( 80)

LED status displays for diagnostic purposes

Module status displays

CIP™ status displays

NS DE

( 32)

( 26)

( 28)

( 77)

( 78)

E94YCEO001B

[3-2] E94AYCEO communication module (EtherNet/IP)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 16

4Technical data

4.1 General data and operating conditions

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

4 Technical data

4.1 General data and operating conditions

Range Values

Order designation E94AYCEO

Communication profile EtherNet/IP

Communication medium S/FTP (Screened Foiled Twisted Pair), ISO/IEC 11801 or EN 50173, CAT 5e

Interface for communication RJ45: Standard Ethernet (in accordance with IEEE 802.3), 100Base-TX (Fast

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 43 (0x2B), Generic device

Product code 9400 (0x24B8)

TCP port 9410 (GCI)

Baud rate • 10 Mbps

Transmission mode Half duplex / full duplex

Switching method Store-and-Forward

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

Voltage supply External supply via separate power supply unit

Conformities, approvals • CE

Ethernet)

• 100 Mbps

+ : U = 24 V DC (20.4 ... 28.8 V), I

- : Reference potential for external voltage supply

•UL

(see also hardware manual)

= 130 mA

max

 Servo Drives 9400 hardware manual

Here you can find the ambient conditions and data on the electromagnetic compatibility (EMC), which also apply to the communication module.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 16

Page 17

4Technical data

4.2 Protocol data

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

4.2 Protocol data

Range Values

I/O data words 1 ... 32 words (max. 64 bytes, 16 bits/word)

Supported CIP services • Get_Attributes_All

• Get_Attribute_Single

• Set_Attribute_Single

• Reset (only type ’0’)

•Forward_Open

•Forward_Close

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 reference manual/ »Engineer« online help for the Servo Drive 9400).

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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 18

4Technical data

4.4 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. bit 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-

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

( 26)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 18

Page 19

4Technical data

4.5 Protective insulation

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

4.5 Protective insulation

 Danger!

Dangerous voltage

If the Servo Drives 9400 are operated on a phase earthed mains with a rated mains voltage  400 V, external measures need to be implemented in order to ensure protection against accidental contact.

Possible consequences:

Death or severe injuries

Protective measures:

If protection against accidental contact is required for the control terminals of the inverter and the connections of the plugged device modules, ...

• a double isolating distance must exist.

• the components to be connected must be provided with the second isolating distance.

 Note!

The protective insulation provided in Servo Drives 9400 is implemented in accordance with EN 61800-5-1.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 20

4Technical data

Ext. DC

I/O

X6X6

X7X7

X8X8

X105X105

X106

X100

X107

MXI1

MXI2

Bus

Ext. DC

MSI

MMI

4.5 Protective insulation

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

The following illustration ...

• shows the arrangement of the terminal strips and the separate potential areas of the inverter.

• serves to determine the decisive protective insulation between two terminals located in differently insulated separate potential areas.

Reinforced insulation

Basic insulation

Functional insulation

[4-1] Protective insulation in accordance with EN61800-5-1

Terminal strip Connection Terminal strip Connection

X100 L1, L2, L3 (Single Drive only) X1 CAN on board 9400

+UG, -UG X2 State bus

X105 U, V, W 24 V (ext.)

Rb1, Rb2 (Single Drive only) X3 Analog inputs/outputs

X106 Motor PTC X4 Digital outputs

X107 Control of the motor holding

brake

E94YCXX007

X5 Digital inputs

X6 Diagnostics

X7 Resolver

X8 Encoder

MXI1, MXI2 Extension module

MMI Memory module

MSI Safety module

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 20

Page 21

4Technical data

4.5 Protective insulation

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

Example

Which type of protective insulation is used between the bus terminal of the device module in slot MXI1 or MXI2 and the mains terminal X100?

The separate potential area with the better protective insulation is decisive.

• The separate potential area of the bus terminal of the device module has a "functional insulation".

• The separate potential area of the mains terminal has a "reinforced insulation".

Result: The insulation between mains terminal X100 and the bus terminal is of the "reinforced insulation" type.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 22

4Technical data

4.6 Dimensions

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

4.6 Dimensions

a 89 mm

b 134 mm

b1 87 mm

e 23 mm

[4-2] Dimensions

E94YCXX005

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 22

Page 23

5 Installation

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

5 Installation

 Stop!

Electrostatic discharge

Electronic components within the communication module can be damaged or destroyed by electrostatic discharge.

Possible consequences:

• The communication module is defective.

• Fieldbus communication is not possible or faulty.

Protective measures

• Before touching the module, be sure that you are free of electrostatic charge.

23 Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 24

5 Installation

5.1 Mechanical installation

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

5.1 Mechanical installation

5.1.1 Assembly

[5-1] Assembly

5.1.2 Disassembly

[5-2] Disassembly

E94YCXX001G

E94AYCXX001H

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 24

Page 25

5 Installation

5.2 Electrical installation

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

5.2 Electrical installation

 Documentation for the standard device, control system, system/machine

Observe the notes and wiring instructions contained in this documentation.

5.2.1 Wiring according to EMC guidelines

In typical systems, standard shielding is sufficient for Ethernet cables.

However, in environments with a very high level of interference, EMC resistance can be improved by additionally earthing the cable shield on both sides.

For this observe the following notes:

1. The distance between the additional earthing and the Ethernet plug depends on the module slot and is as follows:

• approx. 10 cm for the upper slot (MXI1)

• approx. 20 cm for the lower slot (MXI2)

2. Measure the appropriate distance along the cable and, starting from this point, remove 2 cm of the cable's plastic sheath.

3. Connect the cable shield to the shield sheet of the Servo Drive 9400.

A Connection to the shield sheet of the Servo

Drive 9400

B Ethernet cable at X234

C Ethernet cable at X233

D Communication module in slot MXI1 of the

Servo Drive 9400

E94YCXX008

[5-3] Wiring according to EMC guidelines

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 26

5 Installation

AAA

SWSWSW

5.2 Electrical installation

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

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

EtherNet/IP supports the following topologies:

•Line

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

( 18)

E94AYCEO008

•Switch / star

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

•Tree via switches

E94AYCEO005

E94AYCEO006

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

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 26

Page 27

5 Installation

SWSW

5.2 Electrical installation

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

•Switch / switch

E94AYCEO007

[5-7] Switch / switch topology (S = switch)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 28

5 Installation

5.2 Electrical installation

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

5.2.3 EtherNet/IP connection

The EtherNet/IP connection is carried out via the RJ45 sockets X233 and X234.

You can use a standard Ethernet patch cable to connect the communication module to the EtherNet/IP fieldbus.

Ethernet cable specification

The installation and removal of the Ethernet cables is optimised for the use of connectors in accordance with the "Automation Initiative of German Domestic Automobile Manufacturers" (AIDA).

( 30)

 Note!

To prevent the RJ45 socket from being damaged, insert or remove the Ethernet cable connector straight (at a right angle) into or from the socket.

Pin assignment

RJ45 socket Pin Signal

1Tx +

2Tx -

3Rx +

6Rx -

E94AYCXX004C

 Note!

Dependent on the configuration of the Ethernet port of the device to be connected, we recommend the use of a cross-over cable.

 Tip!

The EtherNet/IP interfaces feature an auto-MDIX function. This function adjusts the polarity of the RJ45 interfaces so that a connection can be established irrespective of the polarity of the opposite EtherNet/IP interface and irrespective of the type of cable used (standard patch cable or crossover cable).

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 28

Page 29

5 Installation

5.2 Electrical installation

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

Mounting clearance

When ordering and using your Ethernet cable, note the amount of free space available.

E94YCET017

[5-8] Mounting clearance

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 30

5 Installation

5.2 Electrical installation

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

5.2.4 Ethernet cable specification

 Note!

Only use cables that meet the listed specifications.

Ethernet cable specification

Ethernet standard Standard Ethernet (in accordance with IEEE 802.3), 100Base-TX (Fast

Cable type S/FTP (Screened Foiled Twisted Pair), ISO/IEC 11801 or EN 50173, CAT 5e

Damping 23.2 dB (for 100 MHz and 100 m each)

Crosstalk damping 24 dB (at 100 MHz and per 100 m)

Return loss 10 dB (per 100 m)

Surge impedance 100 

Ethernet)

Structure of the Ethernet cable

[5-9] Structure of the Ethernet cable (S/FTP, CAT 5e)

E94YCEP016

A Cable insulation

B Braid

C Foil shielding

TP1

Twisted core pairs 1 ... 4

...

Colour code of the Ethernet cable

TP4

( 31)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 30

Page 31

5 Installation

5.2 Electrical installation

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

Colour code of the Ethernet cable

 Note!

Wiring and colour code are standardised in EIA/TIA 568A/568B.

In accordance with the industrial standard, the use of 4-pin Ethernet cables is permissible. The cable type only connects the assigned pins 1, 2, 3 and 6 to one another.

E94YCEI004A

[5-10] Ethernet plug in accordance with EIA/TIA 568A/568B

Pair Pin Signal EIA/TIA 568A EIA/TIA 568B

3 1 Tx + white / green white / orange

2 Tx - Green orange

2 3 Rx + white / orange white / green

1 4 blue blue

5 white / blue blue / white

2 6 Rx - orange Green

4 7 white / brown white / brown

8brown brown

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 32

5 Installation

5.2 Electrical installation

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

5.2.5 External voltage supply

The communication module can be supplied externally with voltage via separate supply cables at the 2-pole plug connector X232.

 Note!

With external voltage supply, always use a separate power supply unit, safely separated to EN 61800-5-1 in every control cabinet (SELV/PELV).

The external voltage supply of the communication module is necessary if the power supply for the basic device fails but communication via the fieldbus is to be maintained.

The parameters of a standard device separated from the mains cannot be accessed.

Assignment of the X232 plug connector

Name Description

+ U = 24 V DC (20.4 ... 28.8 V)

I = 130 mA

- Reference potential for the external voltage supply

Terminal data

Range Values

Electrical connection 2-pin plug connector with spring connection

Possible connections Rigid:

1.5 mm

Flexible:

Without wire end ferrule

1.5 mm

With wire end ferrule, without plastic sleeve

1.5 mm

With wire end ferrule, with plastic sleeve

1.5 mm

Stripping length 9 mm

(AWG 16)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 32

Page 33

6 Commissioning

6.1 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

 Note!

When parameterising the communication module, please note that the code number depends on the slot of the Servo Drive 9400 into which the communication module is plugged.

The first two digits of the code number indicate the slot:

•C13nnn for slot MXI1

Parameters of the communication module for slot MXI1

•C14nnn for slot MXI2

Parameters of the communication module for slot MXI2

Additionally set Parameters of the standard device that are relevant to communication

( 88)

6.1 Before initial switch-on

 Stop!

( 88)

( 90)

( 103)

Before switching on the Servo Drive 9400 and the communication module for the first time, check the entire wiring for completeness, short circuit and earth fault.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 34

6 Commissioning

6.2 Configuring the host system (scanner)

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

6.2 Configuring the host system (scanner)

To be able to communicate with the communication module, the host (scanner) must be configured first.

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

The configuration software is necessary for the programming of controller programs, EtherNet/IP configuration, real-time execution and diagnostics.

The basic parameters of the communication module are stored in the internal configuration memory and can be used for node detection by the scanner.

For node detection (fieldbus scan), the corresponding device descriptions of the Lenze device family are used.

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 must be imported into the controller project of the scanner 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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 34

Page 35

6 Commissioning

6.2 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 CompactLogix controller 1769-L32E with an integrated EtherNet/ IP interface is used to communicate with Servo Drives 9400.

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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 36

6 Commissioning

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

• Information on project planning with the »RSLogix 5000« programming software by Rockwell can be found here:

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

( 58)

( 63)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 36

Page 37

6 Commissioning

6.3 Setting the IP configuration of the Servo Drive 9400

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

6.3 Setting the IP configuration of the Servo Drive 9400

The IP configuration is required for addressing the Servo Drive 9400 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 Servo Drive 9400:

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

( 40)

( 42)

( 38)

 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

C14012

parameters currently used.

• In the case of impermissible settings, the error message EtherNet/IP: Invalid IP

parameters [0x00c86533] ( 84) is output.

(gateway address), and C13016 / C14016 (multicast IP address) show the IP

/ C14010 (IP address), C13011 / C14011 (subnet mask), C13012 /

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 38

6 Commissioning

6.3 Setting the IP configuration of the Servo Drive 9400

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

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 Servo Drive 9400 will be interrupted.

• This procedure cannot be applied if the network is configured by a BOOTP/DHCP server.

Setting via a BOOTP/DHCP server

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

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

( 42) (C13005 / C14005)

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

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 38

Page 39

6 Commissioning

6.3 Setting the IP configuration of the Servo Drive 9400

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

2. A double-click on an 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 module carries out a stack reset.

• The IP parameters are written to codes C13000 (subnet mask) und C13002

•Code C13005 that the address transferred can be used.

/ C14005 (IP configuration reference) is set to ’0: Saved address’ to ensure

/ C14002 (gateway address).

/ C14000 (IP address), C13001 / C14001

 Tip!

Check whether the configuration has been transferred successfully.

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

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 40

6 Commissioning

6.3 Setting the IP configuration of the Servo Drive 9400

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

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 stored in the communication module 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 the IP address (C13000

Subnet mask Setting the subnet mask (C13001

Gateway Address Setting 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

/ C14005) of how the IP configuration is to be effected:

/ C14000)

/ C14001)

 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 module off and on again.

/ C14002)

/ C14006)

( 43)

/ C14019)

( 121) of the node, or switch the

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 40

Page 41

6 Commissioning

6.3 Setting the IP configuration of the Servo Drive 9400

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

IP address

The IP address is set/changed in C13000

In C13010/1...4

Example: Display of the IP address 192.168.0.10

Code C13010/1

Value 192 168 0 10

/ C14010/1...4 the currently used IP address is shown.

C14010/1

/ C14000.

C13010/2 C14010/2

C13010/3 C14010/3

C13010/4 C14010/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

In C13011/1...4

Example: Display of the subnet mask 255.255.255.0

Code C13011/1

Value 255 255 255 0

/ C14011/1...4 the currently used subnet mask is shown.

C14011/1

/ C14001.

C13011/2 C14011/2

C13011/3 C14011/3

C13011/4 C14011/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

In C13012/1...4

Example: Display of the gateway address 192.168.0.10

Code C13012/1

Value 192 168 0 10

/ C14012/1...4 the currently used gateway address is shown.

C14012/1

/ C14002.

C13012/2 C14012/2

C13012/3 C14012/3

C13012/4 C14012/4

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 42

6 Commissioning

6.3 Setting the IP configuration of the Servo Drive 9400

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

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 module is used.

• Value ’1’: BOOTP is used. (Lenze standard setting)

• Value ’2’: DHCP is used.

This setting can also be made by means of write access to attribute 3 (Configuration Control) of instance 1 of the TCP/IP Interface Object (245 / 0xF5)

/ C14005 is used to define how the IP configuration is to be carried out:

( 132).

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

A scanner serves to set the IP configuration 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) ( 121)).

In »Engineer«, codes C13010

C14012

currently used.

(gateway address), and C13016 / C14016 (multicast IP address) show the IP parameters

/ C14010 (IP address), C13011 / C14011 (subnet mask), C13012 /

( 132).

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 42

Page 43

6 Commissioning

6.3 Setting the IP configuration of the Servo Drive 9400

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

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 module automatically generates the Multicast IP start address for I/ O data transfer. The standard TTL value for Multicast transfer is ’1’; the Multicast I/O data packages are therefore distributed solely via the local network.

 Note!

You can also explicitly set the multicast IP start address and the multicast TTL value. We recommend, however, not to change the default settings in order to ensure a secure multicast transmission.

The following multicast codes are configurable:

Code Description

C13018

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

/ C14019 Setting of the multicast TTL value for the validity time of data packets in the EtherNet/IP

C13019

C13020

/ C14020 Used to set how many multicast IP addresses will be assigned.

IP Interface Object (245 / 0xF5) ( 132)

• Value ’0’: The default algorithm is used.

• Value ’1’: The address stored in code C13006 address.

network (Instance attribute 8 (TTL Value) in the TCP/IP Interface Object (245 / 0xF5)

(Instance attribute 9 (Num Mcast) in the TCP/IP Interface Object (245 / 0xF5)

/ C14006 is used as multicast IP start

( 132))

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

In C13016/1...4

Example: Display of the multicast IP address 239.64.2.224

Code C13016/1

Value 239 64 2 224

/ C14016/1...4 the currently used multicast IP address of the drive is shown.

C13016/2

C14016/1

C14016/2

/ C14006.

C13016/3 C14016/3

C13016/4 C14016/4

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 44

6 Commissioning

6.4 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 module can manage cyclic EtherNet/IP communication preferentially to normal TCP/IP communication. In the case of EtherNet/IP this is effected using 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.

/ C14021).

[6-1] Example setup: Allen-Bradley CompactLogix controller with Servo Drives 9400

For an online connection between the »Engineer« and the drive, the drive must have an IP address (see Setting the IP configuration of the Servo Drive 9400

( 37)).

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 44

Page 45

6 Commissioning

6.4 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«

( 38)

• 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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 46

6 Commissioning

6.5 Initial switch-on

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

6.5 Initial switch-on

 Documentation for the Servo Drive 9400

Observe the safety instructions and information on residual hazards.

 Note!

Establishing communication

In order to establish communication via an externally supplied communication module, the standard device must be switched on as well.

For further communication of the externally supplied module it is not relevant whether the standard device is switched on or not.

Protection against uncontrolled restart

After a fault (e.g. short-term mains failure), it is sometimes undesirable or even impermissible for the drive to restart.

In the Lenze setting of Servo Drives 9400, the restart protection is activated.

The restart behaviour of the drive can be set via C00142 ("auto restart after mains connection"):

C00142 = "0: Inhibited" (Lenze setting)

• The drive remains inhibited (even if the fault is no longer active).

• An explicit drive enable causes the drive to start up in a controlled manner: LOW-HIGH edge at digital input X5/RFR.

C00142 = "1: Enabled"

• An uncontrolled restart of the drive is possible.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 46

Page 47

7 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:

47 Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 48

7 Data transfer

7.1 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 drive is controlled by means of the I/O data.

• The transmission of I/O data is time-critical.

• I/O data are transmitted cyclically between the host system (scanner) and the drives (adapters) (permanent exchange of current input and output data).

• The host system (scanner) has direct access to the I/O data (the data are, for example, stored directly in the I/O area).

• In the case of Servo Drives 9400, maximally 32 data words (max. 64 bytes) for each direction can be exchanged.

• I/O data are not stored in the drive.

• 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 Servo Drive 9400.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 48

Page 49

7 Data transfer

7.2 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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 50

7 Data transfer

7.3 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 LED MS (see CIP™ status displays

/ C14861;

( 121) via instance attributes 5 and 8;

( 78)).

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 50

Page 51

8 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 port modules in the drive (adapter):

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

Preconditions for establishing an I/O connection

• The data length of the displayed ports in the receive PDO (PDO_RX0) must comply with the length of the I/O data of the assembly object instance 110 (0x6E, Custom Output) in the scanner.

• The data length of the displayed ports in the transmit PDO (PDO_TX0) must comply with the length of the I/O data of the assembly object instance 111 (0x6F, Custom Input) in the scanner.

( 55)

( 58)

( 63)

• An I/O data object can contain a maximum of 32 mapping entries.

• The maximum data length of an I/O data object is 64 bytes

51 Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 52

8 I/O data transfer (implicit messages)

8.1 Technology applications (TA) / drive profiles

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

8.1 Technology applications (TA) / drive profiles

The Servo Drive 9400 is provided with different drive profiles. They define a standardised or individual control and status word assignment as well as the standardisation of setpoint and actual value scalings.

The Servo Drive 9400 supports Lenze technology applications and user-definable parameter sets.

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

In order to use the Lenze technology applications, the following assembly object instances must 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.1.2 I/O assemblies

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

The length of the I/O data must correspond to the resulting length of the mapped ports (I/O configuration in the »Engineer«

The communication module supports the "I/O Assembly Object" class "0x04" (Assembly Object (4 /

0x04) ( 124)).

• For the data exchange, the assembly object instances 110 (0x6E, Custom Output), and 111 (0x6F, Custom Input) are supported

• Both assembly objects transmit a maximum of 64 bytes of I/O data, respectively.

( 55)).

• Depending on the data length defined by the scanner, the memory map of the data can have a different size.

Assembly output objects are usually used for controlling the enable/disable state of the drive and for supplying the speed or torque references.

Assembly input objects 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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 54

8 I/O data transfer (implicit messages)

8.1 Technology applications (TA) / drive profiles

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

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 configuration

in the »Engineer« ( 55)).

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 54

Page 55

8 I/O data transfer (implicit messages)

8.2 I/O configuration in the »Engineer«

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

8.2 I/O configuration in the »Engineer«

For the Servo Drives 9400 HighLine the I/O data can be arranged individually (mapping). For this purpose, the »Engineer« is provided with a port configurator.

 Note!

The port mapping is no configuration that can be carried out online for the Servo Drive

9400. For this purpose, an update of the »Engineer« project and a subsequent download of the application is always required.

Below you can find a description of the steps required to realise an I/O data communication with the host (scanner) in which one control/status word and one 32 bit setpoint/actual value are exchanged each.

 How to implement PDO mapping using the »Engineer«:

1. In the »Engineer«, the mapping of the I/O data is carried out under the Process data objects

tab of the respective fieldbus communication module:

2. Select the receive object PDO_RX0:

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 56

8 I/O data transfer (implicit messages)

8.2 I/O configuration in the »Engineer«

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

3. Click the Edit PDO button. The Process data object structure:PDO_RX0 selection window

opens:

Here you can map the individual ports from the Port Selection list to the receive PDO "PDO_RX0" by clicking the >> button. The Up and Down buttons serve to shift the sequence of the ports within the PDO.

4. Repeat steps 2. and 3. for the send object PDO_TX0.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 56

Page 57

8 I/O data transfer (implicit messages)

8.2 I/O configuration in the »Engineer«

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

In the following example, ...

• the ports "LPortControl1" and "Lport32In1" (a total of 6 bytes) have been mapped into

the receive PDO PDO_RX0;

• the ports "LPortStatus1" and "LPort32Out1" (a total of 6 bytes) have been mapped into

the transmit PDO PDO_TX0.

5. Then link the mapped ports to application signals in the technology application selected.

• Activate the »FB-Editor« via the multiplexer codes (from code C03000) if this has not been done yet.

• If the »FB Editor« is activated, the multiplexer codes are no longer available. In this case, you must carry out the interconnection directly in the »FB Editor«.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 58

8 I/O data transfer (implicit messages)

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

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

8.3 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 ( 34).

 How to carry out the I/O configuration, taking the CompactLogix controller 1769-L32E

with »RSLogix 5000« as an example:

1. Click on 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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 58

Page 59

8 I/O data transfer (implicit messages)

8.3 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 by clickingOK.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 60

8 I/O data transfer (implicit messages)

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

Example settings

Settings Description

Name Device name or drive type, usually referring to the process (in the example

"My_E94AYCEO")

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

IP Address IP address of the drive

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

Input Assembly object instance for input objects

• Max. 32 input data words (64 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).

Output Assembly object instance for output objects

• Max. 32 output data words (64 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).

Configuration Select the assembly instance "1" and the size "0" for the configuration. These values

are required!

6. Complete the settings with OK.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 60

Page 61

8 I/O data transfer (implicit messages)

8.3 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 settings

Setting Description

Requested Packet Interval (RPI)

Use Unicast Connection over EtherNet/IP

Set RPI  2.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).

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.

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 scanner into the error status if the EtherNet/IP connection to the drive (adapter) fails while the scanner is in operation.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 62

8 I/O data transfer (implicit messages)

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

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

9. Complete the settings with OK.

• The I/O configuration is now complete.

• The corresponding tags are then created in the "controller tags" of the control project:

In the example, the drive was named "My_E94AYCEO". There are three tag sets labelled "My_E94AYCEO":

• "My_E94AYCEO:C" for the assembly configuration instance "1"

• "My_E94AYCEO:I" for the assembly input object instance "111"

• "My_E94AYCEO:O" for the assembly output object instance "110"

Click on the [+] in front of the "My_E94AYCEO" data to display the I/O data words of the assemblies.

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

( 69).

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 62

Page 63

8 I/O data transfer (implicit messages)

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

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

8.4 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

( 34) 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.

( 34) 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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 64

8 I/O data transfer (implicit messages)

8.4 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. Go to the "Select Module Type" dialog box and select "E94AYCEO" on the Catalog tab.

5. Confirm the selection with Create.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 64

Page 65

8 I/O data transfer (implicit messages)

8.4 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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 66

8 I/O data transfer (implicit messages)

8.4 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 Value / description

Name Name (type) of the connection

• "Exclusive owner": The scanner controls the adapter outputs.

• "Listen only": If a connection has been established, the scanner only receives the input data.

• "Input only": The scanner does not transmit any output data to the adapter, but only receives the input data.

Number of I/O data words A maximum of 32 data words (max. 64 bytes) for each direction

Selection of the data type • 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).

9. Complete the settings with OK.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 66

Page 67

8 I/O data transfer (implicit messages)

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

Required settings

Settings Description

Requested Packet Interval (RPI)

Input type "Multicast" input type:

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

Set RPI  2.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).

"Unicast" input type: The input data is sent from the adapter to the scanner by means of unicast

telegrams.

This option serves to put the scanner into the error status if the EtherNet/IP connection to the drive (adapter) fails while the scanner is in operation.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 68

8 I/O data transfer (implicit messages)

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

In the example, the drive was named "My_E94AYCEO".

• Tag "My_E94AYCEO:I.ConnectionFaulted" for the connection status

• Tag set "My_E94AYCEO:I.Data" for the assembly input object instance "111"

• Tag set "My_E94AYCEO:O.Data" for the assembly output object instance "110"

If you click "+" before the assembly tag name, all data contained in the assembly tag are displayed below.

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

( 69).

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 68

Page 69

8 I/O data transfer (implicit messages)

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

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

8.5 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 · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 70

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

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.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 70

Page 71

9 Parameter data transfer (explicit messages)

9.1 Write parameters

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

9.1 Write parameters

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

Settings Value / description

Message Type "CIP Generic"

Service Type "Set Attribute Single" (service code "10" [hex])

Class "6E" [hex] (access to Lenze code)

Instance "11" = Lenze code C00011 of the Servo Drive 9400

Attribute "1" = Subcode of the Lenze code

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

• 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 documentation of the drive). For writing to code C00011, set the source length to "4 bytes".

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 72

9 Parameter data transfer (explicit messages)

9.2 Read parameters

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

9.2 Read parameters

If you want to use explicit EtherNet/IP messaging, for instance, in order to read the Lenze code

C00011 (motor reference speed) of the Servo Drive 9400, the following settings are required:

Settings Value / description

Message Type "CIP Generic"

Service Type "Get Attribute Single" (service code "e" [hex])

Class "6E" [hex] (access to Lenze code)

Instance "11" = Lenze code C00011 of the Servo Drive 9400

Attribute "1" = Subcode of the Lenze code

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

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 DINT format.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 72

Page 73

9 Parameter data transfer (explicit messages)

9.2 Read parameters

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

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

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

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 74

10 Monitoring

10.1 Fault with regard to EtherNet/IP communication

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

10 Monitoring

10.1 Fault with regard to EtherNet/IP communication

The response of the Servo Drive 9400 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) = TRUE:

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

Run/Idle flag (Bit 0) = FALSE:

• The I/O data is invalid and the response parameterised here (C13880/1

C14880/1

• The I/O data is processed as set in (C13885

Overall Ethernet Communication Timeout

Fault Mode The adapter (communication module) monitors the I/O connection to the

Overall Ethernet Communication Timeout Timer

Timeout in the case of explicit messages

Clear I/O Data Setting (C13885

If the time set in (C13881 implicit messages are received any more or if there is no more access via the »Engineer«, the response parameterised here (C13880/4 effected in the drive. Access to the web server is not monitored.

scanner. If there is no "implicit message" received within the time-out time for implicit messages parameterised by the scanner, the response

parameterised here (C13880/2

Here, the overall message monitoring time (C13881 / C14881) is set. If no message is received within this time, the response parameterised in

The following messages are monitored:

• Implicit messages

• Explicit messages

• »Engineer« access via EtherNet/IP

If there is no "explicit message" reveived within the time-out time for explicit messages parameterised by the scanner, the response parameterised here (C13880/3

order to maintain the internal communication if ...

• the CIP network status (C13862 connection is not "Connected" or

• an idle event has occurred.

) is activated in the drive.

/ C14881) has elapsed and no explicit or

/ C14880/2) is activated in the drive.

(C13880/4

/ C14880/4) is activated.

/ C14880/3) is activated in the drive.

/ C14885), which I/O data is to processed by the adapter in

/ C14885).

/ C14880/4) is

/ C14862) of the controlling I/O

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 74

Page 75

10 Monitoring

10.2 Interruption of internal communication

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

10.2 Interruption of internal communication

The response to a communication error between the communication module and the Servo Drive 9400 can be set via standard device codes C01501 MXI2).

(module in slot MXI1) and C01502 (module in slot

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 76

11 Diagnostics

11.1 LED status displays

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

11 Diagnostics

The LEDs on the front of the communication module serve to diagnose faults. Moreover, the »Engineer« serves to show diagnostic information.

11.1 LED status displays

 Note!

LED status displays for trouble-free operation:

• The LEDs ST

• The green LEDs on the X233 and X234 RJ45 sockets are lit, and the yellow LEDs are

blinking or jittering

The following status displays are distinguished:

• Module status displays

( 77) and NS ( 78) are permanently on.

( 80).

( 77)

• CIP™ status displays

• Status displays on the RJ45 sockets (X233, X234)

( 78)

( 80)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 76

Page 77

11 Diagnostics

250 ms

11.1 LED status displays

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

11.1.1 Module status displays

Module states are indicated by the ST, ER and DE LEDs.

E94AYCEO001E

[11-1] LEDs ST, ER, DE

LED Colour Status Description

ST Green On

The communication module is supplied with voltage and is connected to the standard device.

ER Red On

DE Red On

Blinking

The communication module is supplied with voltage, but is not connected to the standard device. (Standard device is switched off, in the initialisation phase, or not available.)

An error has occurred in the communication module.

The communication module is not accepted by the basic device or the basic device is not active (see notes in the documentation relating to the basic device.)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 78

11 Diagnostics

250 ms

11.1 LED status displays

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

11.1.2 CIP™ status displays

CIP statuses are indicated by the MS and NS LEDs.

E94AYCEO001E

[11-2] LEDs MS, NS

LED Colour / status Description

MS Green Red

Off Off CIP module status: "Nonexistent"

The communication module is not being supplied with voltage.

Off On

CIP module status: "Major Unrecoverable Fault" The communication module has a fault that cannot be rectified. The status is set if the pending status determining device error shows

the "System fault" response.

Off Blinking

CIP module status: "Major Recoverable Fault" The communication module has a fault that can be rectified. The status is set if the pending status determining device error shows

the "Fault", "Trouble", "Quick stop by trouble", "Warning locked", or "Warning" response.

On Off

CIP module status: "Operational" The communication module is working perfectly.

Blinking Off

CIP module status: "Standby" The communication module has not been fully configured yet, or the configuration is incorrect (e.g. invalid IP address).

Blinking Blinking

CIP module status: "Device Self Testing" The communication module is currently undergoing a self-test.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 78

Page 79

11 Diagnostics

250 ms

11.1 LED status displays

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

LED Colour / status Description

NS Green Red

Off Off CIP network status: "No IP Address"

The communication module is not being supplied with voltage or has not been given an IP address.

Off On

CIP network status: "Duplicate IP" The communication module is unable to gain access to 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 module is working perfectly and has established a

connection to the scanner.

Blinking Off

CIP network status: "No Connections" The communication module ...

•is working correctly;

• has been assigned an IP address;

Blinking Blinking

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

CIP network status: "Self-Test" The communication module is currently undergoing a self-test.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 80

11 Diagnostics

50 ms

11.1 LED status displays

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

11.1.3 Status displays on the RJ45 sockets (X233, X234)

The LEDs on the RJ45 sockets X233 and X234 indicate the Ethernet connection status.

E94AYCEO001E

[11-3] LEDs Link , Act

LED Colour Status Description

Link Green Off No Ethernet connection

There is a physical Ethernet connection.

Act Yellow Off No Ethernet data transfer

On or

flickers

Data are being exchanged via Ethernet.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 80

Page 81

11 Diagnostics

11.2 Diagnostics with the »Engineer«

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

11.2 Diagnostics 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 / C14010

Active Subnetwork Mask C13011 / C14011

Active gateway address C13012 / C14012

Active Multicast IP Start Address C13016 / C14016

CIP Module Status C13861 / C14861

CIP Network Status C13862 / C14862

Ethernet Port X233 connection status C13863/1 / C14863/1

Ethernet Port X234 connection status C13863/2 / C14863/2

/ C14003

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 82

12 Error messages

12.1 Short overview of the EtherNet/IP error messages

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

12 Error messages

This chapter supplements the error list in the reference manual and the »Engineer« online help for the Servo Drive 9400 by the error messages of the communication module.

 Reference manual/»Engineer« online help for the Servo Drive 9400

Here you will find general information on diagnostics & fault analysis and on error messages.

12.1 Short overview of the EtherNet/IP 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 number Name Response (Lenze setting) Adjustable in

hex dec

0x00c85531

0x00c85532

0x00c85533

0x00c86010

0x00c86011

0x00c86100

0x00c86101

0x00c8641f

0x00c86420

0x00c86430

0x00c86533

0x00c88111

0x00c88112 13140242 EtherNet/IP: Explicit Message Timeout 1: No Response C13880/3 /

0x00c88114 13140244 EtherNet/IP: Overall Ethernet Timeout 1: No Response C13880/4 /

0x00c88132 13140274 EtherNet/IP: Idle Mode 1: No Response C13880/1 /

0x00c88142 13140290 EtherNet/IP: Class 1 Connection Closed 6: Information -

0x00c88143

0x00c88273

13129009 EtherNet/IP: Memory: No Access 6: Information -

13129010 EtherNet/IP: Memory: Read Error 6: Information -

13129011 EtherNet/IP: Memory: Write Error 6: Information -

13131792 EtherNet/IP: Restart by Watchdogreset 1: No Response -

13131793 EtherNet/IP: Internal Error 1: No Response -

13132032 EtherNet/IP: Internal Error 1: No Response -

13132033 EtherNet/IP: Internal Error 1: No Response -

13132831 EtherNet/IP: Invalid Parameter Set 1: No Response -

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

13132848 EtherNet/IP: Internal mapping error 6: Information -

13133107 EtherNet/IP: Invalid IP Parameter 1: No Response -

13140241 EtherNet/IP: Fault Mode 1: No Response C13880/2 /

13140291 EtherNet/IP: Class 3 Connection Closed 6: Information -

13140595 EtherNet/IP: Duplicate IP Address 1: No Response -

C14880/2

C14880/3

C14880/4

C14880/1

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 82

Page 83

12 Error messages

12.2 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: No access to memory [0x00c85531]

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

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

Cause Remedy

Access to memory was not possible. Send communication module together with a

EtherNet/IP: Error while reading from memory [0x00c85532]

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

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

description of the fault to Lenze.

Cause Remedy

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

EtherNet/IP: Error while writing to memory [0x00c85533]

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

EtherNet/IP: Internal error [0x00c86011]

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

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

Cause Remedy

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

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

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

Cause Remedy

Communication module is defective. Send communication module together with a

• Send communication module together with a description of the fault to Lenze.

description of the fault to Lenze.

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

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

Cause Remedy

Communication module is defective. Send communication module together with a

description of the fault to Lenze.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 84

12 Error messages

12.2 Possible causes and remedies

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

EtherNet/IP: Internal error [0x00c86100]

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

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

Cause Remedy

Communication module is defective. Send communication module with error description to

EtherNet/IP: Internal error [0x00c86101]

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

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

Cause Remedy

Communication module is defective. Send communication module with error description to

EtherNet/IP: Invalid parameter set [0x00c8641f]

Lenze.

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

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

Cause Remedy

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

EtherNet/IP: Lenze setting loaded [0x00c86420]

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

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

Cause Remedy

Access to parameter set in memory module via standard device was not successful.

EtherNet/IP: Internal mapping error [0x00c86430]

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

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

Cause Remedy

The entered I/O data mapping is invalid.

• An object not supporting the required properties has been specified.

• More than 64 bytes of data have been mapped.

• Send communication module together with a description of the fault to Lenze.

• Download application again (including module).

• Send communication module together with a description of the fault to Lenze.

Repeat I/O configuration in the »Engineer«

( 55).

EtherNet/IP: Invalid IP parameters [0x00c86533]

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

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

Cause Remedy

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

Setting the IP configuration of the Servo Drive 9400 ( 37)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 84

Page 85

12 Error messages

12.2 Possible causes and remedies

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

EtherNet/IP: Fault Mode [0x00c88111]

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

 None  System fault  Fault  Trouble  Quick stop by trouble  Warning locked  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 [0x00c88112]

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

 None  System fault  Fault  Trouble  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.

• Check cables and terminals.

• Plug in the network cable into the Ethernet port.

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

• Increase timeout time for implicit messages.

• Check cables and terminals.

• Plug in the network cable into the Ethernet port.

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

• Increase timeout time for explicit messages.

EtherNet/IP: Overall Ethernet communication timeout [0x00c88114]

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

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

EtherNet/IP: Idle Mode [0x00c88132]

EtherNet/IP: Class 1 Connection Closed [0x00c88142]

Cause Remedy

• Failure of »Engineer« communication via Ethernet

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

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

 None  System fault  Fault  Trouble  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.

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

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

/ C14881 has expired,

• Check cables and terminals.

• Plug in the network cable into the Ethernet port.

• Increase the overall Ethernet timeout time in C13881

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

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

Cause Remedy

The scanner has closed the controlling "Class 1" connection.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Check scanner functionality.

Page 86

12 Error messages

12.2 Possible causes and remedies

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

EtherNet/IP: Class 3 Connection Closed [0x00c88143]

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

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

Cause Remedy

Scanner has closed a "Class 3" connection. Check scanner functionality.

EtherNet/IP: Duplicate IP address [0x00c88273]

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

 None  System fault  Fault  Trouble  Quick stop by trou ble  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.

Correct IP address (C13000

Setting the IP configuration of the Servo Drive 9400 ( 37)

/ C14000).

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 86

Page 87

12 Error messages

12.3 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

( 126) of the Connection Manager

Object (6 / 0x06) ( 126)

requested service.

activated.

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 88

13 Parameter reference

13.1 Parameters of the standard device that are relevant to communication

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

13 Parameter reference

This chapter supplements the parameter list and the attribute table in the reference manual and the »Engineer« online help for the Servo Drive 9400 by the parameter of the E94AYCEO (EtherNet/ IP) communication module.

 Reference manual/»Engineer« online help for the Servo Drive 9400

Here you will find general information on parameters.

13.1 Parameters of the standard device that are relevant to communication

In this chapter communication-relevant parameters of the Servo Drive 9400 are listed in numerically ascending order.

C00615

C00636

Parameter | Name:

C00615 | Resp. to imp. device conf.

Response to impermissible device configuration

Selection list

1Fault

3 Quick stop by trouble

4 Warning Locked

6 Information

0 No response

Subcodes Lenze setting Info

C00615/1 0: No Response Reserved

C00615/2 1: No Response Resp. to imp. module in MXI1

C00615/3 1: No Response Resp. to imp. module in MXI2

C00615/4 0: No Response Reserved

C00615/5 0: No Response Reserved

 Read access  Write access  CINH  PLC-STOP  No transfer

Parameter | Name:

C00636 | Resp. to new module in MXI1

Response for the case where a new module has been plugged into slot 1 of the standard device.

Selection list (Lenze setting printed in bold)

1Fault

6 Information

5 Warning

4 Warning Locked

3 Quick stop by trouble

0 No response

 Read access  Write access  CINH  PLC-STOP  No transfer

Data type: UNSIGNED_32

Index: 23960 = 0x5D98

Data type: UNSIGNED_32

Index: 23939 = 0x5D83

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 88

Page 89

13 Parameter reference

13.1 Parameters of the standard device that are relevant to communication

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

C00637

C01501

Parameter | Name:

C00637 | Resp. to new module in MXI2

Response if a new module has been plugged into module slot 2 of the standard device.

Selection list (Lenze setting printed in bold)

1Fault

6 Information

5 Warning

4 Warning Locked

3 Quick stop by trouble

0 No response

 Read access  Write access  CINH  PLC-STOP  No transfer

Parameter | Name:

C01501 | Resp. to comm. error with MXI1

Response to a communication error between an "intelligent" module in slot 1 and the standard device

Selection list (Lenze setting printed in bold)

0 No response

1Fault

3 Quick stop by trouble

4 Warning Locked

5 Warning

 Read access  Write access  CINH  PLC-STOP  No transfer

Data type: UNSIGNED_32

Index: 23939 = 0x5D83

Data type: UNSIGNED_32

Index: 23074 = 0x5A22

C01502

Parameter | Name:

C01502 | Resp. to comm. error with MXI2

Response to a communication error between an "intelligent" module in slot 2 and the standard device

Selection list (Lenze setting printed in bold)

0 No response

1Fault

3 Quick stop by trouble

4 Warning Locked

5 Warning

 Read access  Write access  CINH  PLC-STOP  No transfer

Data type: UNSIGNED_32

Index: 23074 = 0x5A22

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 90

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

13.2 Parameters of the communication module for slot MXI1

This chapter lists the parameters of the E94AYCEO communication module (EtherNet/IP) for slot MXI2 of the Servo Drive 9400 in numerically ascending order.

C13000

C13001

Parameter | Name:

C13000 | IP address

Setting of the IP address

Setting the IP configuration of the Servo Drive 9400

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 Servo Drive 9400

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

( 37)

Data type: UNSIGNED_8

Index: 11575 = 0x2D37

Data type: UNSIGNED_8

Index: 11574 = 0x2D36

C13002

Parameter | Name:

C13002 | Gateway address

Setting of the gateway address

Setting the IP configuration of the Servo Drive 9400

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

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 90

( 37)

Data type: UNSIGNED_8

Index: 11573 = 0x2D35

Page 91

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13003

C13005

C13006

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 configuration reference

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 Servo Drive 9400

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

( 37)

communication module 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: OCTET_STRING

( 132))

Index: 11572 = 0x2D34

Data type: UNSIGNED_8

Index: 11570 = 0x2D32

Parameter | Name:

C13006 | Multicast IP Start Address

Setting of the multicast IP address

Setting the IP configuration of the Servo Drive 9400

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

( 37)

Data type: UNSIGNED_8

Index: 11569 = 0x2D31

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 92

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13010

C13011

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

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

( 132))

Data type: UNSIGNED_8

Index: 11565 = 0x2D2D

Data type: UNSIGNED_8

Index: 11564 = 0x2D2C

C13012

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

( 132))

Data type: UNSIGNED_8

Index: 11563 = 0x2D2B

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 92

Page 93

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13016

C13017

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

Parameter | Name:

C13017 | Ethernet Config Control

Setting of the baud rate for the Ethernet connections

• Depending on the configuration of the Ethernet port of the device to be connected, we recommend the use of a cross-over cable.

EtherNet/IP connection

• After changing the setting, carry out a "Type 0 Reset" for the Identity Object (1 / 0x01) switch off and on the voltage supply of the communication module.

Selection list

0Auto-Negotiation

1 Reserved

2 Reserved

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 X233

C13017/2 0: Auto-Negotiation Ethernet setting port X234

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 28)

Data type: UNSIGNED_8

Index: 11559 = 0x2D27

Data type: UNSIGNED_16

Index: 11558 = 0x2D26

( 121) of the node or

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 94

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13018

C13019

C13020

Parameter | Name:

C13018 | Multicast Config Alloc Control

Data type: UNSIGNED_8

Index: 11557 = 0x2D25

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

/ 0xF5) ( 132)

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

Data type: UNSIGNED_8

Index: 11556 = 0x2D24

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)

( 132))

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

Parameter | Name:

C13020 | Multicast Config Num Mcast

Data type: UNSIGNED_8

Index: 11555 = 0x2D23

Used to set how many multicast IP addresses will be assigned. (Instance attribute 9 (Num Mcast) in the TCP/IP Interface Object (245 / 0xF5)

( 132))

Setting range (min. value | unit | max. value) Lenze setting

1321

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

C13021

Parameter | Name:

C13021 | Quality of Service (VLAN-Tagging)

Data type: UNSIGNED_8

Index: 11554 = 0x2D22

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)

( 130))

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

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 94

Page 95

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13022

C13840

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) ( 130))

C13022/5 43 QoS DSCP High Prio

(Instance attribute 6 (DSCP High Prio) in the Quality of

Service (QoS) Object (72 / 0x48) ( 130))

C13022/6 31 Reserved

C13022/7 27 QoS DSCP Explicit Msg

(Instance attribute 8 (DSCP Explicit Msg.) in theQuality of

Service (QoS) Object (72 / 0x48) ( 130))

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Data type: UNSIGNED_8

Index: 11553 = 0x2D21

C13841

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)

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)

Selection list (read only)

0 Normal

1 Ring Fault

2 Unexpected Loop detected

3 Partial network fault

4 Rapid fault/restore cycle

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 128))

Data type: UNSIGNED_8

Index: 10735 = 0x29EF

Data type: UNSIGNED_8

Index: 10734 = 0x29EE

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 96

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13842

C13843

C13846

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)

( 128))

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

( 128))

10733 = 0x29ED

C13850

Parameter | Name:

C13846 | Address Conflict Detection

Data type: UNSIGNED_8

Index: 10729 = 0x29E9

Activation of the address conflict detection (ACD) (Instance attribute 10 (Selectcd) in the TCP/IP Interface Object (245 / 0xF5)

( 132))

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

Parameter | Name:

C13850 | All words to scanner

Data type: INTEGER_16

Index: 10725 = 0x29E5

Display of the I/O data words transferred from the communication module (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/32

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 96

Page 97

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13851

C13852

Parameter | Name:

C13851 | All words from scanner

Display of the I/O data words transferred from the scanner to the communication module. 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/32

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13852 | All words to the basic device

Display of the I/O data words transferred from the communication module to the standard device.

Display range (min. value | unit | max. value)

-32768 32767

Subcodes Info

C13852/1

...

C13852/32

 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: INTEGER_16

Index: 10723 = 0x29E3

C13853

Parameter | Name:

C13853 | All words to the basic device

Display of the I/O data words transferred from the standard device to the communication module.

Display range (min. value | unit | max. value)

-32768 32767

Subcodes Info

C13853/1

...

C13853/32

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Data type: INTEGER_16

Index: 10722 = 0x29E2

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 98

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13858

C13861

Parameter | Name:

C13858 | Ethernet Port Statistics

Display of statistical values for the data transfer via the Ethernet connections

Subcodes Info

C13858/1 Ethernet port X233: RX

C13858/2 Ethernet port X233: RX CRC error

C13858/3 Ethernet port X233: RX rejected

C13858/4 Ethernet port X233: TX

C13858/5 Ethernet port X233: TX rejected

C13858/6 Ethernet port X234: RX

C13858/7 Ethernet port X234: RX CRC error

C13858/8 Ethernet port X234: RX rejected

C13858/9 Ethernet port X234: TX

C13858/10 Ethernet port X234: TX rejected

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

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.

CIP™ status displays

Selection list (read only)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

( 78)

0 Nonexistent

1 Device Self Testing

2 Standby

3 Operational

4 Major Recoverable Fault

5 Major Unrecoverable Fault

( 121))

Data type: UNSIGNED_32

Data type: UNSIGNED_16

Index: 10717 = 0x29DD

Index: 10714 = 0x29DA

C13862

Parameter | Name:

C13862 | CIP Network Status

Display of the current CIP network status

• The status is also indicated via the NS LED.

CIP™ status displays

Selection list (read only)

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 98

( 78)

0 No IP Address

1 Nonexistent

2 Established

3 Timed Out

4 Duplicate IP

5 Self-Test

Data type: UNSIGNED_16

Index: 10713 = 0x29D9

Page 99

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13863

C13870

Parameter | Name:

C13863 | Ethernet Port

Display of the baud rate currently used on the Ethernet connections

Selection list (read only)

0 Nonexistent

1 10 Mbps/Half Duplex

2 10 Mbps/Full Duplex

3 100 Mbps/Half Duplex

4 100 Mbps/Full Duplex

5 Reserved

6 Reserved

Subcodes Info

C13863/1 Ethernet port X233 link state

C13863/2 Ethernet port X234 link state

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13870 | CIP Connections State

Display of the current CIP connection status

Selection list (read only)

0 Nonexistent

3 Established

4 Timed Out

Subcodes Info

C13870/1 Status of CIP connection 1

... ...

C13870/8 Status of CIP connection 8

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Data type: UNSIGNED_16

Index: 10712 = 0x29D8

Index: 10705 = 0x29D1

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17

Page 100

13 Parameter reference

13.2 Parameters of the communication module for slot MXI1

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

C13871

C13872

Parameter | Name:

C13871 | CIP Connections Type

Display of the current CIP connection types

• "Listen Only" connections are not displayed.

Selection list (read only)

0 Nonexistent

1 Exclusive Owner

2 Input Only

3 Listen Only

4 Explicit Connection

Subcodes Info

C13871/1 Type of CIP connection 1

... ...

C13871/8 Type of CIP connection 8

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Parameter | Name:

C13872 | CIP Connection Triggers

Display of the current CIP connection class

Selection list (read only)

0 Nonexistent

1 Class 1, Cyclic, Client

163 Class 3, App. Obj., Server

Subcodes Info

C13872/1 Trigger of CIP connection 1

... ...

C13872/8 Trigger of CIP connection 8

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Data type: UNSIGNED_16

Index: 10704 = 0x29D0

Index: 10703 = 0x29CF

C13873

Parameter | Name:

C13873 | CIP Connections RPI

Indication of the current RPI times (Requested Package Interval) of the CIP connections

Display range (min. value | unit | max. value)

0 ms 4294967295

Subcodes Info

C13873/1 RPI of CIP connection 1

... ...

C13873/8 RPI of CIP connection 8

 Read access  Write access  CINH  PLC STOP  No transfer  PDO_MAP_RX  PDO_MAP_TX  COM  MOT

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17 100

Data type: UNSIGNED_32

Index: 10702 = 0x29CE