communication manual e94aycib interbus mxi module mxi...1 about this documentation 4 lenze ·...

L

Ä.N+øä

1345

1099

INTERBUS

Accessories

Servo Drives 9400 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Communication Manual EN

E94AYCIB

2 Lenze · E94AYCIB communication module (INTERBUS) · Communication Manual · DMS 4.0 EN · 02/2014 · TD17

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

1 About this documentation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 41.1 Document history _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 61.2 Conventions used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 71.3 Terminology used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 81.4 Definition of the notes used _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 9

2 Safety instructions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 102.1 General safety and application notes _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 102.2 Device and application-specific safety instructions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 112.3 Residual hazards _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 11

3 Product description _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 123.1 Application as directed _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 123.2 Identification _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 123.3 Product features _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 133.4 Terminals and interfaces _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 14

4 Technical data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 154.1 General data and operating conditions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 154.2 Protocol data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 164.3 Communication time _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 164.4 Protective insulation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 174.5 Dimensions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 20

5 Installation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 215.1 Mechanical installation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22

5.1.1 Assembly _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 225.1.2 Disassembly _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 22

5.2 Electrical installation _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 235.2.1 Wiring according to EMC guidelines _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 235.2.2 Wiring of the INTERBUS _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 245.2.3 INTERBUS connection _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 255.2.4 Dimensions of 9-pole sub-D connectors _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 265.2.5 Bus cable specification _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 275.2.6 Bus cable length _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 275.2.7 External voltage supply _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 28

6 Commissioning _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 296.1 Before initial switch-on _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 296.2 Possible settings via DIP switch _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 30

6.2.1 Setting the number of process data words _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 316.2.2 Setting the number of parameter data words _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 326.2.3 Setting the baud rate _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 33

6.3 Settings in »Engineer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 346.4 Initial switch-on _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 35

Contents

Lenze · E94AYCIB communication module (INTERBUS) · Communication Manual · DMS 4.0 EN · 02/2014 · TD17 3

Contents

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

7 Data transfer _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 36

8 Process data transfer _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 37

9 Parameter data transfer _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 399.1 Addressing of the parameter data _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 399.2 Initialising PCP communication _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 409.3 Supported PMS services _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 41

9.3.1 Initiate _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 419.3.2 Abort _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 419.3.3 Reject _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 419.3.4 Read/Write _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 429.3.5 Get-OD _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 429.3.6 Identify _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 439.3.7 Status _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 44

10 Monitoring _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 4510.1 Interruption of the INTERBUS communication _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 4510.2 Interruption of internal communication _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 46

11 Diagnostics _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 4711.1 LED status displays _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 4711.2 Diagnosing with the »Engineer« _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 48

12 Error messages _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 4912.1 Short overview of the INTERBUS error messages _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 4912.2 Possible causes and remedies _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 50

13 Parameter reference _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 5313.1 Parameters of the standard device that are relevant to communication _ _ _ _ _ _ _ _ _ _ _ _ _ _ 5313.2 Parameters of the communication module for slot MXI1 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 5513.3 Parameters of the communication module for slot MXI2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 6313.4 Table of attributes _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 71

14 Index _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 74

Your opinion is important to us _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 77

1 About this documentation


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


This documentation exclusively describes the E94AYCIB communication module (INTERBUS).

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 ofthe communication module.

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

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

Tip!More information on the INTERBUS can be found on this internet page:

www.interbus.com

Maintenance activities for the INTERBUS technologies are carried out by the userorganisation PROFIBUS & PROFINET International (PI).

www.profibus.com

Note!This documentation supplements the mounting instructions supplied with the communication module and the Servo Drives 9400 hardware manual.

The mounting instructions contain safety instructions which must be observed!

http://www.interbus.comhttp://www.profibus.com



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

Target group

This documentation is intended for all persons who plan, install, commission and maintain thenetworking and remote servicing of a machine.

Tip!Current documentation and software updates with regard to Lenze products can be foundin the download area at:

www.lenze.com

Information regarding the validity

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

Screenshots/application examples

All screenshots in this documentation are application examples. Depending on the firmwareversion of the communication module and the software version of the engineering tools installed(e.g. »Engineer«), the screenshots in this documentation may differ from the actual screenrepresentation.

Extension module Type designation From hardware version

From software version

Communication module INTERBUS E94AYCIB PA 01.00

http://www.lenze.com

1 About this documentation1.1 Document history


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

1.1 Document history

Version Description

1.0 03/2009 TD17 Field test version

2.0 06/2009 TD17 General revision

3.0 11/2009 TD17 General revision

4.0 02/2014 TD17 • New layout• General updates


1 About this documentation1.2 Conventions used

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

1.2 Conventions used

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

Type of information Writing Examples/notes

Spelling of numbers

Decimal Normal spelling Example: 1234

Decimal separator Point The decimal point is always used.For example: 1234.56

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

Binary• Nibble

In inverted commasPoint

Example: ’100’Example: ’0110.0100’

Text

Version information Blue text colour All information that applies to from a certain software version of the device onwards are marked accordingly in this documentation.Example: This function extension is available from software version V3.0 onwards!

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

Control element bold The OK button ... / The Copy command ... / The Properties tab ... / The Name input field ...

Sequence of menu commands

If several commands are required to execute one function, the single commands are separated by an arrow: Select the File Open command to...

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

Icons

Page reference ( 8) Optically highlighted reference to another page. In this online documentation activated via mouse-click.

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

1 About this documentation1.3 Terminology used


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

1.3 Terminology used

Term Meaning

Drive Lenze inverter of the "Servo Drives 9400" product series, with which the communication module can be used.Application as directed ( 12)Inverter

Standard device

Code Parameter which serves to parameterise and monitor the drive. In normal usage, the term is usually referred to as "Index".

Subcode If a code contains several parameters, they are stored in "subcodes".In the documentation, the slash "/" is used as a separator between the code and the subcode (e.g. "C00118/3").In everyday language, the term is also referred to as "subindex".

»Engineer« Lenze PC software which supports you during the "Engineering" process (parameterisation, diagnostics, and configuration) throughout the whole life cycle, i. e. from planning to maintenance of the machine commissioned.

INTERBUS was developed as sensor/actuator bus system for transmitting process data.Maintenance activities for the INTERBUS technologies are carried out by the user organisation PROFIBUS & PROFINET International (PI).

Host PLC, INTERBUS master

PCP Peripherials Communication Protocol for transmitting parameter data

PDO Process data object

PDU Process Data Unit

PMS Peripheral Message Specification

HW Hardware

SW Software


1 About this documentation1.4 Definition of the notes used

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

1.4 Definition of the notes used

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

Safety instructions

Layout of the safety instructions:

Application notes

Danger!(characterises 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 voltageReference to an imminent danger that may result in death or serious personal injury if the corresponding measures are not taken.

Danger! Danger of personal injury through a general source of dangerReference to an imminent danger that may result in death or serious personal injury if the corresponding measures are not taken.

Stop! Danger of property damageReference to a possible danger that may result in property damage if the corresponding measures are not taken.

Pictograph Signal word Meaning

Note! Important note to ensure trouble-free operation Tip! Useful tip for easy handling Reference to another document

2 Safety instructions2.1 General safety and application notes


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

2 Safety instructions

2.1 General safety and application notes

Lenze drive and automation components ...

• must only be used as directed.Application as directed ( 12)

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

• must never be technically modified.

• must never be commissioned if they are not fully mounted.

• must never be operated without required covers.

• during and after operation can have live, moving and rotating parts, depending on their degree of protection. Surfaces can be hot.

The following applies to Lenze drive components ...

• only use the accessories approved.

• Only use original manufacturer spare parts.

Observe all specifications contained in the enclosed documentation and related documentation.

• This is the precondition for safe and trouble-free operation and for obtaining the product features specified.Product features ( 13)

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

All works on and with Lenze drive and automation components must only be carried out by qualifiedpersonnel. 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.

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.

Danger!If the following basic safety measures are disregarded, severe injuries to persons and damage to material assets may result.


2 Safety instructions2.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 corresponding to the given specifications.Bus cable specification ( 27)

2.3 Residual hazards

Protection of persons

If Servo Drives 9400 are used on a phase earthed mains with a rated mains voltage 400 V,protection against accidental contact is not guaranteed without external measures.Protective insulation ( 17)

Device protection

The communication module contains electronic components which may be damaged or destroyedby electrostatic discharge.Installation ( 21)

Documentation for the standard device, host (PLC, master), system/machineAll the other measures prescribed in this documentation must also be implemented. Observe the safety instructions and application notes contained in this manual.

3 Product description3.1 Application as directed


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

3 Product description

3.1 Application as directed

The communication module ...

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

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

Any other use shall be deemed inappropriate!

3.2 Identification

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

[3-1] Identification data

Product series Type designation From hardware version

From software version

Servo Drives 9400 HighLine E94AxHExxx 1A 03.00

Servo Drives 9400 PLC E94AxPExxxx VA 02.00

Regenerative power supply module E94ARNxxxx VA 01.00

E94YCIB005

1 Type designation (type)

E94 Product series

A Version

Y Module identification: Extension module

C Module type: Communication module

IB INTERBUS

2 Hardware version (HW)

3 Software version (SW)


3 Product description3.3 Product features

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

3.3 Product features

• Interface module for the INTERBUS 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.

• Slave functionality

• DIP switch settings:• Number of process data words and parameter data words• Baud rate (500 kbps or 2 Mbps)

• Bus coupling via remote bus according to the RS485 standard

• Up to 10 process data words (20 bytes) can be used.

• 0, 1, 2 order 4 parameter data words can be used.

• The parameter data is transmitted in accordance with the Peripherials Communication Protocol (PCP).

• Access to all Lenze parameters

• Support of the PMS services:• Initiate• Abort• Reject• Read• Write• Get-OD• Identify• Status

3 Product description3.4 Terminals and interfaces


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

3.4 Terminals and interfaces

[3-2] E94AYCIB communication module (INTERBUS)

E94YCIB001B

S205 DIP switches for setting the ...• Number of process data words and

parameter data words• Baud ratePossible settings via DIP switch ( 30)

X205 External voltage supply of the communication module

• 2-pin plug connector with spring connection External voltage supply ( 28)

X206 INTERBUS connection, input (IN)• 9-pole Sub-D plugWiring of the INTERBUS ( 24)

X207 INTERBUS connection, output (OUT)• 9-pin Sub-D socketWiring of the INTERBUS ( 24)

MSMEBSBEDE

LED status displays for diagnostic purposesLED status displays ( 47)


4 Technical data4.1 General data and operating conditions

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

4 Technical data

4.1 General data and operating conditions

Range Values

Order designation E94AYCIB

Communication profile INTERBUS

Communication medium RS485

Interface for communication • Input (IN): 9-pole Sub-D plug• Output (OUT): 9-pole Sub-D socket

Network topology Ring

Type of node Slave

Number of nodes • 1 master• 512 slaves

Baud rate 500 kbps or 2 Mbps(can be set via DIP switch or code)

Max. cable length • 400 m at 500 kbps• 150 m at 2 Mbps

(between the single INTERBUS nodes)

Process data words 0 ... 10 words (16 bits/word)(can be set via DIP switch or code)

Parameter data words 0, 1, 2, 4 words (16 bits/word)(can be set via DIP switch or code)The parameter data is transmitted in accordance with the Peripherials Communication Protocol (PCP).

Max. number of data words 10 words (process data word + parameter data words), 16 bits/word

Max. PDU length 64 bytes

Device identification (module ID) • 3 = 0x03 (0 parameter data words)• 227 = 0xE3 (1 parameter data words)• 224 = 0xE0 (2 parameter data words)• 225 = 0xE1 (4 parameter data words)

Voltage supply External supply via separate power supply unit+: U = 24 V DC (+/- 10 %), Imax = 180 mA- : Reference potential for external voltage supply

Conformities, approvals • CE• UL

(see also hardware manual)

Servo Drives 9400 hardware manualHere you can find the ambient conditions and information on the electromagnetic compatibility (EMC) which also apply to the communication module.

4 Technical data4.2 Protocol data


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

4.2 Protocol data

4.3 Communication time

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

The communication times in an INTERBUS 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

There are no interdependencies between parameter data and process data.

Range Values

Process data words 0 ... 10 words (16 bits/word)

Parameter data words 0, 1, 2, 4 words (16 bits/word)The parameter data is transmitted in accordance with the Peripherials Communication Protocol (PCP).

Supported PMS services • Initiate• Abort• Reject• Read• Write• Get-OD• Identify• Status

Note!The data word sum (process data words + parameter data words) has to consist of 1 ... 10 words (16 bits/word).

Data Processing time

Process data Approx. 4 ms+ 0 ... 1 ms+ 1 ... x ms

Update cycleProcessing time in the moduleRuntime of the application task of the technology application used (tolerance)

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


4 Technical data4.4 Protective insulation

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

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



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

The following illustration ...

• shows the arrangement of the terminal strips and the separate potential areas of the Servo Drive 9400.

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

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

Note!The INTERBUS input (X206) is isolated from the voltage supply (X205) and the INTERBUS output (X207).

E94YCIB007

Reinforced insulation

Basic insulation

Functional insulation

Ext. DC

I/O

X4

X6X6

X5

X7X7

X8X8

X3

X2X1

X105X105

X106

X100

X107

MXI1

MXI2

Bus

Ext. DC

MSI

MMI

X207

X206

X205



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

Example

Which type of protective insulation is used between the bus terminal of the device module in slotMXI1 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 "reinforcedinsulation" type.

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

X5 Digital inputs

X6 Diagnostics

X7 Resolver

X8 Encoder

MXI1, MXI2 Extension module

MMI Memory module

MSI Safety module

X205 External voltage supply (24 V DC)

X206 INTERBUS connection, input (IN)

X207 INTERBUS connection, output (OUT)

4 Technical data4.5 Dimensions


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

4.5 Dimensions

[4-2] Dimensions

E94YCXX005

a 89 mm

b 134 mm

b1 87 mm

e 23 mm


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.

5 Installation5.1 Mechanical installation


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

5.1 Mechanical installation

5.1.1 Assembly

[5-1] Assembly

5.1.2 Disassembly

[5-2] Disassembly

E94YCXX001G

E94AYCXX001H


5 Installation5.2 Electrical installation

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

5.2 Electrical installation

5.2.1 Wiring according to EMC guidelines

In typical systems, standard shielding is sufficient for the INTERBUS cable.

In environments with very strong interferences, the EMC compatibility can be improved by anadditional earthing of the cable shield.

For this observe the following notes:

1. The distance of the additional earthing of the INTERBUS plug (Sub-D, 9-pole) 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 cables 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.

[5-3] Wiring according to EMC guidelines

Documentation for the standard device, host (PLC, master), system/machineObserve the notes and wiring instructions contained in this documentation.

E94YCXX008

A Connection to the shield sheet of the Servo Drive 9400

B IncomingINTERBUS line at X206 (IN)

C Outgoing INTERBUS line at X207 (OUT)

D Communication module in slot MXI1 of the Servo Drive 9400



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

5.2.2 Wiring of the INTERBUS

For communication with the master and all further components, Servo Drives 9400 have to beassembled with communication modules.

The INTERBUS system has to be designed as a ring. Here, go and return lines are integrated in thesame bus cable. The ring comes from the INTERBUS master via all other nodes back again to themaster.

An INTERBUS ring can consist of maximally 513 nodes (1 master + further slaves (slaves)).

[5-4] INTERBUS ring

E94YCIB008

M: Master (e.g. PLC, Industrial PC)S1 ... Sn: Slaves

500 kBit/s: 400 m

2 MBit/s:

�

150 m�

Servo Drive

9400

E94AYCIB

X206 X207

Servo Drive

9400

E94AYCIB

X206 X207

Servo Drive

9400

E94AYCIB

X206 X207

OUTIN OUTIN IN

M

S2S1 Sn



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

5.2.3 INTERBUS connection

The INTERBUS of the communication module is connected via the 9-pole Sub-D plug X206 (input)and the 9-pole Sub-D socket X207 (output).

[5-5] INTERBUS terminals X206 (input) and X207 (output)

Assignment of the 9-pole Sub-D plug X206 (IN)

E94YCIB001C

Pin Name Input/output Description

1 DO1 Input RS485: DO1 not inverted

2 DI1 Output RS485: DI1 not inverted

3 GND Reference potential

4 Free not assigned

5 Vcc5 Output 5 V DC

6 /DO1 Input RS485: DO1 inverted

7 /DI1 Output RS485: DI1 inverted


9 Free not assigned



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

Assignment of the 9-pole Sub-D socket X207 (OUT)

5.2.4 Dimensions of 9-pole sub-D connectors

[5-6] Dimensions of 9-pole sub-D connectors

Pin Name Input/output Description

1 DO2 Output RS485: DO2 not inverted

2 DI2 Input RS485: DI2 not inverted

3 GND Reference potential

4 GND


6 /DO2 Output RS485: DO2 inverted

7 /DI2 Input RS485: DI2 inverted


9 RBST Signalling input Connection to the outgoing INTERBUS is plugged.

Note!Comply with the dimensions for width and depth of the 9-pole Sub-D connectors for the INTERBUS terminals X206/X207.

E94YCIB001G



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

5.2.5 Bus cable specification

The nodes at the bus system must be wired with one of the fieldbus cables that complies with theINTERBUS specification.

A manufacturer of INTERBUS cables is e.g. PHOENIX CONTACT (Germany).

Properties of the bus cable according to the INTERBUS specification

5.2.6 Bus cable length

Set the baud rate according to the length of the bus cable between the single INTERBUS nodes:

Possible settings via DIP switch ( 30) Settings in »Engineer« ( 34)

Note!A cable which does not fulfil the requirements of the INTERBUS specification must not be used!

General properties

Cable type Sold by the meter(e.g. PHOENIX CONTACT: IBS RBC meter-T, order no. 28 06 28 6)

No. of conductors 3 x 2, twisted in pairs, with joint shielding

Conductor cross-section > 0.2 mm2

DC-cable resistance < 96 /km

Impedance (characteristic) • 120 ± 20 % (f = 64 kHz)• 100 ± 15 (f > 1 MHz)

Capacitance per unit length < 60 nF/km (f = 800 Hz)

Baud rate Cable length between the single INTERBUS nodes

500 kbps max.400 m

2 Mbps max. 150 m

Note!Select the baud rate which depends on the data volume, cycle time, and number of nodes just high enough to suit your application.



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

5.2.7 External voltage supply

The communication module can be externally supplied with voltage via separate supply cables atthe 2-pin plug connector X205.

External voltage supply of the communication module is required if the communication via the busshould be maintained when the supply of the standard device fails.

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

Assignment of the plug connector X205

Terminal data

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

Name Explanation

+ U = 24 V DC (+/- 10 %)I = 180 mA

- Reference potential for external voltage supply

Range Values

Electrical connection 2-pin plug connector with spring connection

Possible connections Rigid:

1.5 mm2 (AWG 16)

Flexible:

Without wire end ferrule1.5 mm2 (AWG 16)

With wire end ferrule, without plastic sleeve1.5 mm2 (AWG 16)

With wire end ferrule, with plastic sleeve1.5 mm2 (AWG 16)

Stripping length 9 mm


6 Commissioning6.1 Before initial switch-on

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

6 Commissioning

During commissioning, system-related data such as motor parameters, operating parameters,responses, and parameters for fieldbus communication are defined in the inverter. For Lenzedevices, this is done by means of codes.

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

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

Parameter reference ( 53)

6.1 Before initial switch-on

Note!When parameterising the communication module, please note that the code number depends on the slot of the standard device into which the communication module is plugged.

The first two digits of the code number indicate the slot:• C13nnn for slot MXI1Parameters of the communication module for slot MXI1 ( 55)

• C14nnn for slot MXI2Parameters of the communication module for slot MXI2 ( 63)

You also have to set the Parameters of the standard device that are relevant to communication ( 53).

Stop!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.

6 Commissioning6.2 Possible settings via DIP switch


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

6.2 Possible settings via DIP switch

[6-1] DIP switch

E94YCIB001D

The following can be set via the S205 DIP switch:

• Number of the process data wordsswitches: 1 ... 4 ( 31)

• Number of the parameter data wordsswitches: 5 and 6 ( 32)

• Baud rateswitch: 8 ( 33)

Lenze setting: All switches "OFF"

Switch 7 has no function.

Note!• All DIP switches = "OFF" (Lenze setting):

At switch-on, the configuration from the codes gets active (Settings in »Engineer« ( 34)).

• At least one DIP switch = "ON":At switch-on, the values are accepted from the switch positions.

• The data word sum (process data words + parameter data words) has to consist of 1 ... 10 words (16 bits/word).

• Switch off the voltage supply of the communication module and afterwards on again to activate changed settings.



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

6.2.1 Setting the number of process data words

• The number of process data words can be set via the switches 1 ... 4.

• 0 ... 10 process data words can be used.

• The current setting is displayed in the »Engineer« in C13860/2 / C14860/2.

Note!The data word sum (process data word + parameter data words) has to consist of 1 ... 10 words (16 bits/word).

Impermissible settings are reported by the BE LED (red blinking).

LED status displays ( 47)The communication module then operates internally with the following values:• 2 process data words (PD)• 1 parameter data word (PCP)

DIP switch Number of PD

Switch Max. number of PCP

1 2 3 4

0 OFF OFF OFF OFF 4

1 OFF OFF OFF ON

2 OFF OFF ON OFF

3 OFF OFF ON ON

4 OFF ON OFF OFF

5 OFF ON OFF ON

6 OFF ON ON OFF

7 OFF ON ON ON 2

8 ON OFF OFF OFF

9 ON OFF OFF ON 1

10 ON OFF ON OFF 0

12

34

56

78

ONOFF



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

6.2.2 Setting the number of parameter data words

• The number of parameter data words can be set via the switches 5 and 6.


• The current setting is displayed in the »Engineer« in C13860/1 / C14860/1.

Note!The data word sum (process data word + parameter data words) has to consist of 1 ... 10 words (16 bits/word).


LED status displays ( 47)The communication module then operates internally with the following values:• 2 process data words (PD)• 1 parameter data word (PCP)

DIP switch Number of PCP Switch Max. number of PD

ID code[hex]5 6

0 OFF OFF 10 0x03

1 OFF ON 9 0xE3

2 ON OFF 8 0xE0

4 ON ON 6 0xE1

12

34

56

78

ONOFF



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

6.2.3 Setting the baud rate

• The baud rate can be set via the switch 8.

• Set the baud rate according to the length of the bus cable between the single INTERBUS nodes.

• The current setting is displayed in the »Engineer« in C13863 / C14863.

Note!Select the baud rate which depends on the data volume, cycle time, and number of nodes just high enough to suit your application.

DIP switch Switch 8 Baud rate Cable length between adjacent nodes

OFF 500 kbps max. 400 m

ON 2 Mbps max. 150 m

12

34

56

78

ONOFF

6 Commissioning6.3 Settings in »Engineer«


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

6.3 Settings in »Engineer«

How to activate changed settings in the »Engineer«:1. Execute the device command C00002 = "11: Save start parameters".

2. Carry out a "Reset node" of the node, or switch the voltage supply of the communication module off and then on again.



LED status displays ( 47)The communication module then operates internally with the following values:• 2 process data words• 1 parameter data word

Select the baud rate which depends on the data volume, cycle time, and number of nodes just high enough to suit your application.

Setting Description

PCP data length 0, 1, 2 or 4 parameter data words can be used (C13892 / C14892).

Process data length 1 ... 10 process data words can be used (C13893 / C14893).

Clear process data Setting (C13885 / C14885) the selection of the process data the Servo Drive 9400 is to process for maintaining the internal communication when the INTERBUS has exited the "IBS-ACTIVE" state.

• 0: Use of the last master process data• 1: PDOs are set to the value "0". (Standard setting)

Baud rate Set the baud rate (C13894 / C14894) according to the length of the bus cable between the single INTERBUS nodes:

• 500 kbps: Max. 400 m between the single nodes• 2 Mbps: Max. 150 m between the single nodes


6 Commissioning6.4 Initial switch-on

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

6.4 Initial switch-on

Documentation for the standard deviceObserve 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 inverter can be set via C00142 ("auto restart after mains connection"):

C00142 = "0: Inhibited" (Lenze setting)• The inverter remains inhibited (even if the fault is no longer active).• An explicit controller 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.

7 Data transfer


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

7 Data transfer

The INTERBUS transmits parameter data, configuration data, diagnostic data, alarm messages andprocess data between the host (master) and the inverters (slaves) participating in the fieldbus.Depending on their time-critical nature, the data are transmitted via different communicationchannels.

Communication channels

The process data channel transmits process data.

• The process data serve to control the inverter.

• The transmission of process data is time-critical.

• Process data are cyclically transferred between the host (master) and the inveters connected to the fieldbus (slaves) (continuous exchange of current input and output data).

• The host (master) can directly access the process data. In the PLC, for instance, the data are directly saved to the IO area.

• 0 ... 10 process data words can be used.

• Process data are not saved in the inverter.

• Process data are e.g. setpoints, actual values, control words, and status words.

The parameter data channel serves to transfer parameter data.

• The parameter data channel provides access to all Lenze codes.

• The transmission of parameter data is usually not time-critical.

• Parameter data are, for instance, operating parameters, diagnostic information, and motor data.


• The parameter data is transmitted in accordance with the Peripherials Communication Protocol (PCP).

• The parameter data channel is identical for both transmission directions.


Please observe the direction of the flow of information:• Input data (Rx data): Process data from the inverter (slave) to the master• Output data (Tx data): Process data from the master to the inverter (slave)


8 Process data transfer

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


Configuring process data (PDO mapping)

The Servo Drives 9400 enable the individual mapping of process data. For this purpose, the»Engineer« is provided with a port configurator.

How to set the PDO mapping with the »Engineer«:1. The process data mapping to the port variables is executed in the »Engineer« under the

Process data objects tab of the corresponding fieldbus communication module:

2. Select the receive object PDO_RX0:

Note!• The port mapping for the Servo Drive 9400 is no configuration that can be carried out

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

• The data word sum (process data words + parameter data words) has to consist of 1 ... 10 words (16 bits/word).



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

3. Click the Edit PDO button.

The selection window for editing the process data object is opened:

Here you can transfer 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 PDOs.

4. Confirm the selection with OK.

5. Repeat the steps 2. to 4. for the transmit object PDO_TX0.

6. Then link the ports to application signals in the technology application selected.

The »FB Editor« can be activated in the multiplexer codes (> C03000), if necessary.

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


9 Parameter data transfer9.1 Addressing of the parameter data

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

9 Parameter data transfer

The parameter data of Lenze devices are contained in codes which are listed in this documentationand the documentation of the Servo Drive 9400.

Parameter reference ( 53)

9.1 Addressing of the parameter data

The parameters of a Lenze device are not directly addressed via codes but via an index and subindex.

The conversion is made via an offset: 24575 or 0x5FFF

• INTERBUS index (decimal) = 24575 - Lenze code number (decimal)

• INTERBUS index (hexadecimal) = 0x5FFF - Lenze code number (hexadecimal)

Example of C00105 (deceleration time quick stop (QSP)):

• INTERBUS index (decimal) = 24575 - 105 = 24470

• INTERBUS index (hexadecimal) = 0x5FFF - 0x69 = 0x5F96

Parameter changes must be saved via code C00002 of the Servo Drive 9400.

9 Parameter data transfer9.2 Initialising PCP communication


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

9.2 Initialising PCP communication

Make entries into the CRL (communication relation list) in order that communication between theINTERBUS master and the communication module can take place.

Make the following entries in the CRL of the INTERBUS master:

Field name Entry

Communication reference 2

Connection type Master slave acyclic

Connection attribute Defined

Max-PDU Sending-High-Prio 0

Max-PDU Sending-Low-Prio 64

Max-PDU Receiving-High-Prio 0

Max-PDU Receiving-Low-Prio 64

Supported Services Request 0x803000

Supported Services Response 0x000000

Maximum SCC 1

Maximum RCC 1

Maximum SAC 1

Maximum RAC 1


9 Parameter data transfer9.3 Supported PMS services

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

9.3 Supported PMS services

The parameter data is transferred via PMS services.

In the following, only parameters and their contents are given that are returned by the Lenzeinverters. All other transfer parameters of the given PMS services can be obtained from thecorresponding descriptions of the INTERBUS master.

The following PMS services are supported by Lenze inverters:

• Initiate: Establish a connection of the INTERBUS master to the inverter

• Abort: Abort connection

• Reject: Reject impermissible PMS service

• Read: Read parameters

• Write: Write parameters

• Get-OD: Read out the object directory

• Identify: Identification of the inverter

• Status: Read the status of the inverter

9.3.1 Initiate

The "Initiate" PMS service establishes a logic connection between the INTERBUS master and thecommunication module.

The inverter provides the following parameters:

9.3.2 Abort

The "Abort" PMS service aborts a logic connection between the INTERBUS master and thecommunication module.

9.3.3 Reject

The "Reject" PMS service rejects a non-supported PMS service.

Name Value Description

Profile number 0 No profile is supported.

Password 0 The password function of INTERBUS is not supported.

Access groups 0 No access groups exist.

Access-Protection Supported TRUE Access protection is supported.

Version OD 0 Version of the object directory



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

9.3.4 Read/Write

The "Read" PMS service reads parameters from the inverter. The inverter outputs the requestedparameter or an error message.

The "Write" PMS service writes on parameters of the inverter. The inverter outputs a positivefeedback or an error message.

The following error messages can occur:

9.3.5 Get-OD

The "Get-OD" PMS service reads out the object description for every parameter and data type.

Error Class Error code Additional Code[hex]

Description

6 3 0x00 No access authorisation

6 5 0x10 Impermissible job parameter

6 5 0x11 Invalid subindex

6 5 0x12 Data length too large

6 5 0x13 Data length too small

6 6 0x00 Object is no parameter

6 7 0x00 Object does not exist

6 8 0x00 Data types do not comply with each other

8 0 0x00 Request cannot be executed

8 0 0x20 Request cannot be executed at the moment

8 0 0x21 Cannot be executed because of local control

8 0 0x22 Cannot be executed because of device state

8 0 0x30 Quit value range / parameter can only be changed when the controller is inhibited.

8 0 0x31 Parameter value too high

8 0 0x32 Parameter value too low

8 0 0x33 Sub parameter outside the value range

8 0 0x34 Value of the subparameter is too high

8 0 0x35 Value of the subparameter is too low

8 0 0x36 Maximum value is lower than minimum value

8 0 0x41 Communication object cannot be displayed on process data

8 0 0x42 Length of the process data exceeded

8 0 0x43 General collision with other values



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

9.3.6 Identify

The P "Identify" MS service provides information on how to identify the inverter.

The inverter with the plugged-on communication module provides the following parameters forthis:

Example: Visible string "device type" (15 characters)

Example: Visible string "device version" (15 characters)

Parameter Type Description

Device manufacturer Visible string Company name "Lenze"

Device type Visible-string (15 characters) Device name for inverter and communication module

Device version Visible-string (15 characters) Firmware version of the inverter and the communication module

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

E 9 4 A F H B A F C I B

Character Description

1 ... 3 Product range of the inverter and the communication module ("E94" = 9400 series)

4 Blank

5 ... 8 Firmware of the inverter (from C00200/0)• Character 5: Version ("A" = 1st generation)• Character 6 ... 8: Firmware version

• "FHB" = Servo Drive 9400 HighLine• "FRB" = Servo Drive 9400 regenerative power supply module• "VPB" = Servo Drive 9400 PLC

9 Blank

10 ... 14 Firmware of the communication module (from C13900 / C14900)• Character 10: Version ("A" = 1st generation)• Characters 11 ... 14: Firmware version

• "FCIB" = INTERBUS module

15 Blank

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

0 5 . 0 0 0 1 . 0 0

Character Description

1 ... 5 Firmware version of the inverter (from C00099/0 = "05.00.xx.yy", without internal revision status ["xx"] and build status ["yy"])

6 Blank

7 ... 11 Firmware version of the communication module (from C13902 / C14902 = "01.00.xx", without internal revision status ["xx"])

12...15 Blank



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

9.3.7 Status

The "Status" PMS service provides status information about the inverter.

The inverter provides the following values:

Status Value Description

Logical status 0 = ready for communication Information about the current operating mode of the inverter with regard to communication

Physical status • 0 = ready for operation (device state "OPERATION ENABLED")

• 1 = ready for operation to a limited extent (all other device states)

Information about the current operating status of theinverter.

Local Detail 0 Is not supported.


10 Monitoring10.1 Interruption of the INTERBUS communication

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

10 Monitoring

10.1 Interruption of the INTERBUS communication

An interruption of the INTERBUS communication, e.g. by cable break or failure of the host (PLC,master), is recognised by the communication module.

Responses to communication faults can be set in the Monitoring tab:

If the Servo Drive 9400 does not receive any valid process data in the "IBS-ACTIVE" state, the settingin C13885 / C14885 is taken as a basis for the process data. (Like this the data sent last by the mastercan be used or reset to zero.)

Settings in »Engineer« ( 34)

Settings Description

Response to interrupted INTERBUS communication

When the INTERBUS communication is interrupted, the response set here (C13880/1 / C14880/1) takes place in the inverter.A change in the monitoring response becomes immediately effective.

Response time if the INTERBUS communication is interrupted

If the "IBS-ACTIVE" status (INTERBUS active, cyclic data exchange) is left, the response set under takes place after the response time set here (C13881 / C14881) has elapsed.

• A value of "65535" in this code deactivates the monitoring function. • A change in the monitoring is immediately effective.• The monitoring time elapses when the "IBS-ACTIVE" status is left.• After this response delay has elapsed, the response set is executed with

the error message "INTERBUS: Data exchange stopped [0x00c88131]" ( 52).

10 Monitoring10.2 Interruption of internal communication


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

10.2 Interruption of internal communication

The response to a communication error between the communication module and the Servo Drive9400 can be set via these codes:

• C01501 (module in slot MXI1)

• C01502 (module in slot MXI2)


11 Diagnostics11.1 LED status displays

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

11 Diagnostics

For purposes of fault diagnostics, the communication module is provided with the LEDs on the front.Furthermore you can carry out the Diagnosing with the »Engineer« ( 48).

11.1 LED status displays

Note!During normal operation, the LED BS blinks and the LED MS is permanently lit.

LEDs Pos. Colour Status Description

E94YCIB001E

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

Blinking The communication module is supplied with voltage, but has no connection to the standard device. (The standard device is either switched off, in the initialisation phase, or not available).

ME Red On An error has occurred in the communication module.

BS Green Blinking The INTERBUS communication has been established via the communication module. The INTERBUS is active. Data cycles are executed.

Off The communication module is not active at the fieldbus. Data cycles are not executed.

BE Red On The INTERBUS communication has been interrupted.Data cycles are not executed.

Blinking Impermissible setting:• Process data words + parameter data words

> 10• Process data words + parameter data words

= 0The communication module has been initialised and operates internally with the following values:

• 2 process data words• 1 parameter data word

DE Red On 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.)

11 Diagnostics11.2 Diagnosing with the »Engineer«


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

11.2 Diagnosing with the »Engineer«

In the »Engineer« under the Diagnostics tab, you will find INTERBUS diagnostics information.

Querying the current bus status

C13861 / C14861 displays the bus status of the INTERBUS node:

ValueC13861/14861[hex]

Bus status Description

0xyyy0 IBS-INIT Initialisation

0xyyy1 IBS-ACTIVE The bus is active. Data cycles are executed.

0xyyy2 IBS-READY The bus is ready for operation. No data cycles are executed.

yyy = device-internal use


12 Error messages12.1 Short overview of the INTERBUS error messages

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

12 Error messages

This chapter supplements the error list for the Servo Drive 9400 contained in the reference manualand in the »Engineer« online help with the error messages of the communication module.

12.1 Short overview of the INTERBUS error messages

The following table lists all INTERBUS error messages in the numerical order of the error numbers.Furthermore, the preset error response and - if available - the parameter for setting the errorresponse 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.

Reference manual/»Engineer« online help for the Servo Drive 9400Here you will find general information on diagnostics & fault analysis and on error messages.

Error number Name Response (Lenze setting) Adjustable in

hex dec

0x00c85531 13129009 INTERBUS: No access to the memory 6: Information -

0x00c85532 13129010 INTERBUS: Error while reading the memory 6: Information -

0x00c85533 13129011 INTERBUS: Error while writing into the memory 6: Information -

0x00c86010 13131792 INTERBUS: Internal error 1: No Response -




0x00c86110 13132048 INTERBUS: Internal mapping error 4: Warning locked -

0x00c8641f 13132831 INTERBUS: Parameter set invalid 1: No Response -

0x00c86420 13132832 INTERBUS: Lenze setting loaded 1: No Response -

0x00c88125 13140261 INTERBUS: Invalid configuration 5: Warning -

0x00c88126 13140262 INTERBUS: Reset of communication 1: No Response -

0x00c88127 13140263 INTERBUS: Invalid initialisation 5: Warning -

0x00c88131 13140273 INTERBUS: Data exchange stopped None C13880/1 / C14880/1

0x00c88211 13140497 INTERBUS: Received process data length is contradictory 5: Warning -

0x00c88212 13140498 INTERBUS: Process data length to be sent is contradictory 5: Warning -

12 Error messages12.2 Possible causes and remedies


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

12.2 Possible causes and remedies

This chapter lists all INTERBUS error messages in the numerical order of the error numbers. Possiblecauses and remedies as well as responses to the error messages are described in detail.

INTERBUS: No access to memory [0x00c85531]

INTERBUS: Error while reading the memory [0x00c85532]

INTERBUS: Error while writing into the memory [0x00c85533]

INTERBUS: Internal error [0x00c86010]



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

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

Cause Remedy

Memory could not be accessed. Send module with error description to Lenze.



Cause Remedy

Parameter could not be read. Send module with error description to Lenze.


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

Cause Remedy

Parameter could not be written. Send module with error description to Lenze.



Cause Remedy

Module is defective. Send module with error description to Lenze.



Cause Remedy




Cause Remedy




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


INTERBUS: Internal mapping error [0x00c86110]

INTERBUS: Invalid parameter set [0x00c8641f]

INTERBUS: Lenze setting loaded [0x00c86420]

INTERBUS: Invalid configuration [0x00c88125]

INTERBUS: Reset of the communication stack [0x00c88126]



Cause Remedy

Internal error Send module with error description to Lenze.



Cause Remedy

The selected PDO mapping is invalid:• An object not supporting the required properties has

been specified.• The data word sum (process data words + parameter

data words) has to consist of 1 ... 10 words (16 bits/word).

Repeat Configuring process data (PDO mapping) ( 37).



Cause Remedy

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



Cause Remedy

Access via standard device to the parameter set in the memory module failed.

Download application again (including module).



Cause Remedy

The active configuration is invalid:• Process data words + parameter data words > 10• Process data words + parameter data words = 0

The data word sum (process data words + parameter data words) has to consist of 1 ... 10 words (16 bits/word).

Adapt the number of process data words and parameter data words:

• Process data words + parameter data words = 1 ... 10


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

Cause Remedy

Error when processing the INTERBUS services Execute renewed initialisation by the master.



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

INTERBUS: Invalid initialisation [0x00c88127]

INTERBUS: Data exchange stopped [0x00c88131]

INTERBUS: Received process data length is contradictory [0x00c88211]

INTERBUS: Process data length to be sent is contradictory [0x00c88212]



Cause Remedy

The INTERBUS initialisation has failed. Execute renewed initialisation by the master.

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

None System fault Fault Trouble Quick stop by troubleWarning locked Warning Information

Cause Remedy

Data exchange via INTERBUS has been stopped. • Check cables and terminals.• Execute renewed initialisation by the master.



Cause Remedy

The number of received I/O data via INTERBUS (display in C13860/2 / C14860/2) does not correspond to the number configured by the device through port mapping (display in C13854/1 / C14854/1).The data word sum (process data word + parameter data words) has to consist of 1 ... 10 words (16 bits/word).

Check whether the differing data length is sufficient for the application.If required, adapt the port mapping or the I/O data length of the received data.Configuring process data (PDO mapping) ( 37) Setting the number of process data words ( 31)



Cause Remedy

The number of I/O data to be sent via INTERBUS (display in C13860/2 / C14860/2) does not correspond to the number configured by the device through port mapping (display in C13855/1 / C14855/1).The data word sum (process data word + parameter data words) has to consist of 1 ... 10 words (16 bits/word).

Check whether the differing data length is sufficient for the application.If required, adapt the port mapping or the I/O data length of the data to be sent.Configuring process data (PDO mapping) ( 37) Setting the number of process data words ( 31)


13 Parameter reference13.1 Parameters of the standard device that are relevant to communication

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

13 Parameter reference

This chapter supplements the parameter list and the table of attributes contained in the referencemanual and in the »Engineer« online help for the Servo Drive 9400 with the parameters of theE94AYCIB (INTERBUS) communication module.

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 innumerically ascending order.

C00615

C00636

Reference manual/»Engineer« online help for Servo Drive 9400Here you will find general information on parameters.

Parameter | Name:

C00615 | Resp. to imp. device conf.Data type: UNSIGNED_32

Index: 23960 = 0x5D98

Response to impermissible device configuration

Selection list

1 Fault

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



Read access Write access CINH PLC-STOP No transfer

Parameter | Name:

C00636 | Resp. to new module in MXI1Data type: UNSIGNED_32

Index: 23939 = 0x5D83

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)

1 Fault

6 Information

5 Warning

4 Warning Locked


0 No response


13 Parameter reference13.1 Parameters of the standard device that are relevant to communication


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

C00637

C01501

C01502

Parameter | Name:

C00637 | Resp. to new module in MXI2Data type: UNSIGNED_32

Index: 23939 = 0x5D83

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


1 Fault

6 Information

5 Warning

4 Warning Locked


0 No response


Parameter | Name:

C01501 | Resp. to comm. error with MXI1Data type: UNSIGNED_32

Index: 23074 = 0x5A22

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


0 No response

1 Fault


4 Warning Locked

5 Warning


Parameter | Name:

C01502 | Resp. to comm. error with MXI2Data type: UNSIGNED_32

Index: 23074 = 0x5A22

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


0 No response

1 Fault


4 Warning Locked

5 Warning



13 Parameter reference13.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 E94AYCIB communication module (INTERBUS) for slot MXI2of the Servo Drive 9400 in numerically ascending order.

C13231

C13489

C13531

Parameter | Name:

C13231 | Service codeData type: UNSIGNED_64

Index: 11344 = 0x2C50

This code is for device-internal use only and must not be written to by the user.

Value is bit-coded: Info

Bit 0 Bit 0

... ...

Bit 63 Bit 63


C13231/1 0

... ...

C13231/32 0

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

Parameter | Name:


Index: 11086 = 0x2B4E


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

0 32


C13489/1 0 Service code


Parameter | Name:


Index: 11044 = 0x2B24


Value is bit-coded: Info

Bit 0 Bit 0

... ...

Bit 63 Bit 63


C13531/1 0

... ...

C13531/32 0




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

C13789

C13850

C13851

Parameter | Name:


Index: 10786 = 0x2A22


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

0 32


C13789/1 0 Service code


Parameter | Name:

C13850 | All words from drive to masterData type: UNSIGNED_16

Index: 10725 = 0x29E5

Display of the process data words which are transmitted from the communication module to the master.• In the subcodes 1 ... 32, all process data words to the master are displayed. Only the configured process data

words are valid.

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

0 65535

Subcodes Info

C13850/1

...

C13850/32


Parameter | Name:

C13851 | All words from master to driveData type: UNSIGNED_16

Index: 10724 = 0x29E4

Display of the process data words which are transmitted from the master to the communication module.• In the subcodes 1 ... 32, all process data words to the master are displayed. Only the configured process data

words are valid.


0 65535

Subcodes Info

C13851/1

...

C13851/32




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

C13852

C13853

C13854

Parameter | Name:

C13852 | All words to the basic deviceData type: UNSIGNED_16

Index: 10723 = 0x29E3

Display of the process data words which are transmitted from the communication module to the standard device.• In the subcodes 1 ... 32, all process data words from the communication module are displayed.


0 65535

Subcodes Info

C13852/1

...

C13852/32


Parameter | Name:

C13853 | All words to the basic deviceData type: UNSIGNED_16

Index: 10722 = 0x29E2

Display of the process data words which are transmitted from the standard device to the communication module.• In the subcodes 1 ... 32, all process data words from the standard device are displayed.


0 65535

Subcodes Info

C13853/1

...

C13853/32


Parameter | Name:

C13854 | Length of ports mapped into receive PDOData type: UNSIGNED_8

Index: 10721 = 0x29E1

Display of the total data length (in bytes) of the ports that have been entered into the receive PDO.The data word sum (process data words + parameter data words) has to consist of 1 ... 10 words (16 bits/word).Configuring process data (PDO mapping) ( 37) Display area (min. value | unit | max. value)

0 64

Subcodes Info

C13854/1 Length of the ports entered into the receive PDO




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

C13855

C13860

C13861

Parameter | Name:

C13855 |

communication manual e94aycib interbus mxi module mxi...1 about this documentation 4 lenze ·...

Documents