Inverter

Inverter Drives 8400 protec

Diagnostics Handbook
for the Customer Daimler
Contents
Description page
Block diagram 2
Mains connection X10 3
Motor connection X21 4
Brake resistor connection X20 5
Control connection X41 6
Control connection X42 7
Control connection X43 8
Analog input X50 9
Fieldbus connections X31 and X32 10
Connection "Safety options 30" X62 11
Connection "Safety options 30" X63 12
Connection "Safety options 30" X64 13
Diagnostic interface X70 14
Nameplate 15
Structure of the 7-segment display 16
Meaning of LED 1/2 19
Meaning of LED 2/2 20
Troubleshooting the device 21
Typical errors 22
Engineer in a few steps - start 23
Engineer in a few steps - connection 27
Engineer in a few steps - diagnostic picture 31
Engineer in a few steps - diagnostic picture / error details 32
Engineer in a few steps - logbook 34
Engineer in a few steps - Diagnostic via monitor 38
Engineer in a few steps - data logger 43
Engineer in a few steps - choosing the right parameters 47
Engineer in a few steps - data logger - procedure - example 50
Engineer in a few steps - data logger - cursor settings 56

Engineer in a few steps - data logger - configuration, saving, loading 61

Important codes 62
Short instructions for device replacement 63
Project data backup 65
GDC data backup 66
Parameter comparison (two data sets) 68
Index 71

1
Block diagram

2
X10 mains connection

X10

3
X21 motor connection

X20
X21

4
X20 brake resistor connection

X20
X21

5
X41 control connections

X41

6
X42 control connections

X42

7
X43 control connections

X43

8
X50 analog input

X50

9
X31 and X32
fieldbus connections

X31 X32

10
X62 "Safety Option 30"
connection

X62

11
X63 "Safety Option 30"
connection

X63

12
X64 "Safety Option 30"
connection

X64

13
X70 Diagnostic interface

X70

14
Nameplate

Type designation

Type Serial number

Manufacturing number
code
Material number

Software version QEV-number

Power
(firmware)

Hardware version

15
Structure of the
7-segment display

7-segment display:
DC-bus voltage
558V

16
Structure of the
7-segment display

If there are no problems during operation,

specific process parameters appear on the
display. Use pushbutton T2 to switch between
the individual parameters.

T2
pushbutton

17
Structure of the
7-segment display
If an error arises during operation, this will
appear on the display. The following list
provides an overview of possible error
messages.

18
Meaning of LED 1/2

Status
LEDs

19
Meaning of LED 2/2

20
Troubleshooting the device

 Check the plug connections

(are all connectors plugged in correctly?).

 Compare the error message on the device

with the fault list.

 Check the LED display

(slide 20).

 Depending on the evaluation of the

fault list, take the appropriate
measures. Use the Engineer
to read out the logbook.

 If required, replace the device

(e.g. dH10 error).

 Compare the saved project (parameters)

with the project on the device to
ensure that the parameter setting
and the Profinet name still are
correct.

21
Typical errors
Note: Drive does not rotate – e.g. if a
remote/local switch-over took place. This may
affect drives that are controlled via a variable
setpoint. In this case, it may occur that the drive
receives a setpoint too low for rotating.

Error text Description Measures

Check the life bit on the control. Check whether

User error no. 1 the device is on the bus / whether communication
(US01) Life bit is missing is functioning properly (no cables unplugged
etc.). Check whether the Profinet name on the
device (C13899) is identical with the name on the
control.
The link-1 / link-2 LEDs must flash.

 User error no. 2 Temperature

(US02) monitoring of the Check whether the thermal contact of the brake
brake resistor has resistor is connected (X50) / whether it is too hot
been triggered (caution: the temperature may be very high!).

Check whether the negative hardware limit

User error no. 3 Overflow of the position has been approached / whether there is
(US03) negative HW limit a cable break.
switch for protective It is possible to traverse the drive in the opposite
door applications direction.

Check whether the positive hardware limit

 User error no. 4 Overflow of the position has been approached / whether there is
(US04) positive HW limit a cable break.
switch for protective It is possible to traverse the drive in the opposite
door applications direction.

22
Engineer in a few steps

23
Engineer in a few steps

When the Engineer has been started, the

project query window opens.

Here the software checks the path used

to store the AFS file.

If the checked project has been created

with an older version of the Engineer
software, a message appears asking you
whether it is to be opened without
updating. Alternatively, the project can be
updated using the latest library data.

24
Engineer in a few steps

Selection by
clicking
Available menu bar

25
Engineer in a few steps

When the project has been opened, the

inverter can be selected in the project tree
structure (function abbreviation).

Then the following tabs are available

• Application parameters
• FB Editor
• Terminal assignment
• Diagnostics
• Data logger
• User menu
• Ports
• All parameters
• Features
• Documentation

as well as the level for the safety

parameters (Safety Option 30) and the
PROFINET parameters.

26
Engineer in a few steps

27
Engineer in a few steps

In order to establish communication with the

inverter, the communication path must be
defined first.

The selected communication path and the

communication parameters are saved when
the project is saved. When communication
is established again, the communication
path and the parameters do not need to be
set again. If another communication path is
selected, the setting must be altered
appropriately.

The following communication paths are

available:

• Diagnostic adapter
• PROFINET

28
Engineer in a few steps -
connection establishment

29
Engineer in a few steps -
connection establishment

For communication via Profinet, the

corresponding IP address must be
entered. Alternatively, the IP address
can also be obtained from the project
(see below).

30
Engineer in a few steps -
diagnostics view

C0137:

Drive

diagnostics

C0165/2:

Current error

Important status
bits relating to the
operating state of
the drive are
displayed in the
visualisatio by
means of LEDs

ready


31
Engineer in a few steps -
diagnostics view

Clicking the "current error" button shows

the error details.

32
Engineer in a few steps -
diagnostics view
For diagnostic purposes, a separate tab is
available summarising all important states and
actual values in a single view. The diagnostics
view may be helpful both for troubleshooting
and for normal operation. Here you will find
information on state variables such as
utilisation, flowing current, available voltage,
etc.

"Monitoring" summarises all the important

monitoring functions in a single view.

Under "Device information" you will find i.a. the

firmware version or the serial number of the
inverter.

Furthermore, there you will also find the

logbook containing the saved errors.

Via the "All parameters" tab, you can always

have a look at all the display codes of the
device. Display or read-only codes have an
ochre background.

33
Engineer in a few steps -
logbook
1st step

2nd
step

34
Engineer in a few steps -
logbook

35
Engineer in a few steps -
logbook
It is possible to declare the events to be
written into the logbook (via parameter 169
or the "Configure…“ button of the logbook).
The events are saved with the time stamp
of the control card running time.
Export of the logbook data into a
file (e.g. for E-mailing)

Note:
By means of a parameterisable filter
(C169), you can exclude certain
events from being entered into the
logbook! For further details, refer to
the online help of the Engineer.

36
Engineer in a few steps -
logbook
Events that can be logged in the logbook:
– System error messages (TRIP,
warning, fault, etc.)
– Error messages generated by the user
program
– Controller enable
– Control reset
– Loading/saving of parameter sets
– Program download/firmware download
– Switch-off of the drive controller (low-
voltage)
– Error acknowledgement (TRIP reset)
– Formatting the file system

The logbook function integrated into the

controller records important events within the
system in chronological order and thus plays an
important role in troubleshooting / diagnosing
the controller. The structure of the logbook
corresponds to a "ring buffer". A new entry is
always written to the next free position within
the memory – if all memory units are assigned,
the oldest entry is deleted for a new entry ("first-
in-first-out" principle, also known as "FIFO").

37
Engineer in a few steps -
logbook

Instead of the message window,

alternatively a monitor window can be
shown beneath the project view and the
working area. Here, the most important
actual states of the controller are displayed.

When an online connection has

been established, the actual values
of up to 16 parameters of the devices
included in the project can be shown
in the monitor window.

Via the "Selection" list field, you can

define whether the monitor window for the
entire machine or a monitor window
for a certain device of the project
is shown.

38
Engineer in a few steps -
logbook
If the monitor window for the machine
has not yet been configured, the
display area for this monitor window
remains empty at first.

The monitor window for a device is

already preconfigured with useful
display parameters. This configuration
can be adapted as required.

The size of the configured display fields

is automatically adjusted to the size of the
monitor window.

Furthermore, empty columns at the right

edge and/or empty rows at the bottom are
automatically hidden to ensure an optimal
display.

Clicking the window icon of a

display field shows the
corresponding display in full
in the monitor window.

39
Engineer in a few steps -
logbook

Select the Monitor tab

at the bottom of the

application window to

show the monitor

window instead of the

message window.

40
Engineer in a few steps -
logbook

The monitor window

can be customised by

using the adjust

button.

41
Engineer in a few steps -
logbook
Select the parameter
you will use as
a new display code
at the selected field

In this box, the

type of
presentation can
be adjusted for
the selected field

42
Engineer in a few steps -
data logger

When an online connection has been

established to the device, the
trigger condition and the

 sampling rate must be set and the

 variables to be recorded must be selected
 via the data logger user interface.

During the measurement, the measured values

are represented graphically.

43
Engineer in a few steps -
data logger

44
Engineer in a few steps -
data logger

Data logger:

 Phase: Project

 Tab: Data logger

45
Engineer in a few steps -
data logger

Note!

The online connection

Double-click this
Text
must exist!

area and a window

for selecting the

variables to be

recorded appears.

46
Engineer in a few steps -
data logger

47
Engineer in a few steps -
data logger

1s/div  results in a total recording time of 10s.

48
Engineer in a few steps -
data logger

Note: If several variables are

recorded, the memory space

required increases and the

maximum recording time

decreases!

49
Engineer in a few steps -
data logger

Here you can

select the trigger
event. Click
the Channel
field to open a
selection window.

50
Engineer in a few steps -
data logger
There are different options to choose from for
the trigger event. Click on the relevant field to
select the event.

Selection of one of
the 4 measuring
channels

Selection
of a
variable

Selection of Force
trigger.
The oscilloscope
starts recording as
soon as the Start
button has been clicked

51
Engineer in a few steps -
data logger

In this area,
a trigger delay
can be set.

Note:
A trigger delay is a temporaly
delay in recording in relation
to the trigger event.

52
Engineer in a few steps -
data logger
Pre-trigger

Selecting a negative
delay time detects signals
prior to the trigger
event.
The trigger time is
marked by a dotted line in
the oscillograph.
A maximum of -100% can be recorded
prior to the trigger event (complete
display range).
With triggering on occurrence of
an event, it is thus possible to
detect the values that have
caused the event.

53
Engineer in a few steps -
data logger
Post-trigger

Selecting a positive
delay time detects signals
occurring a certain time
after the trigger event.
The trigger event can be outside of
the oscillograph / display range
(max. +400 %).
With triggering on occurrence of
an event, it is thus possible to
detect values arising long after
the event.

54
Engineer in a few steps -
data logger

Note:

For the first measurement, the

scaling of the displayed

measured values usually must

be adapted to improve the

representation of the curve.

This can be done automatically

by clicking the marked button!

55
Engineer in a few steps -
data logger

In addition to the zoom and scaling function,

the oscilloscope also provides a "cursor
function" which can be used to display
individual measured values for a selected
channel or the difference between any two
measured values.

If the Cursor tab is in the foreground, the

cursor function is active and two moveable
vertical measuring lines are displayed on the
oscillograph.

The selected channel's curve is identified

accordingly.

56
Engineer in a few steps -
data logger

You can access the cursor settings

via the "Cursor" button.

57
Engineer in a few steps -
data logger

The curve of the selected

channel is highlighted (channel

1 = black).

The current cursor data is

displayed in this area. The active

cursor appears as a solid red

line.

58
Engineer in a few steps -
data logger

You can use the mouse to move the cursor to any position on

the selected curve.

For example, a measurement of 33.16 Hz has been

taken here. The differential value shows the

difference between this and the second cursor

(17.08 Hz).

59
Engineer in a few steps -
data logger

This button provides access to a zoom function.

Dragging with the mouse enlarges an area in the

measurement window.

60
Engineer in a few steps -
data logger
Two more buttons can be used to save or
reload the current vertical channel settings
(template file, own configuration).

Load configuration file

Save configuration file

61
Important codes

The Lenze term codes stands for

parameters. The codes are numbered
and every code has a name and
a meaning. The exact meaning of the
individual codes is listed under Help.
It can be accessed by placing
the cursor on the desired code and
pressing the F1 key.

The most important codes at a glance:

C11: Reference speed

C12: Acceleration time
C13: Deceleration time
C22: Maximum current
C53:
C81: Rated motor power
C88: Rated motor current
C105: Deceleration time - quick stop
C13899: Profinet name

62
Short instructions for
device replacement
1. Set the service switch [A] to the OFF
position.
2. Disconnect all the plug connections.
3. Disconnect the PE connection at the
earthing stud [B].
4. Remove the device.
5. Take out the memory module [C] and
insert it into the replacement device.
6. Install the replacement device.
7. Screw in the PE connection at [B]
and plug in all the connectors.
8. Set the service switch [A] to ON.
9. Carry out the procedure for transferring the
safety data.

C B
63
Short instructions for
device replacement
Precondition ->

Transfer of parameters:
Use the pushbuttons T1 and T2 to carry out the routine as
described:

1. LED S_Ack lights up -> Press and hold T1&T2

simultaneously -> S_Ack starts to flash.
2. LED S_Ack stops flashing -> Release T1&T2
immediately (within 2.5s)
3. LED S_Ack lights up -> Press and hold T1&T2
simultaneously -> S_Ack starts to flash.
4. LED S_Ack stops flashing -> Release T1&T2
simultaneously (within 2.5s)
5. Transfer successfully completed -> S_Error, S_Ack =
OFF and S_State = ON.

64
Project data backup

Always read the parameters out of the

controller before saving the project!

2. Save the project

1. Read the parameters out again

65
GDC data backup
Always read the parameters out of the
controller before saving the GDC file.

1. Read the parameters out again

2. Export the parameters

66
GDC data backup

1. Select "all parameters"

2. Go ahead for saving

67
Parameter comparison
(two data sets)

1st step 2nd step

68
Parameter comparison
(two data sets)

Compares the offline data

with the online data

69
Parameter comparison
(two data sets)

70
Index

71
Version control
Date Version Released by

25.03.2013 1.0 Karsten Peter Seifert

22.01.2014 3.0 Matthias Langer

72