8 diagnostics & error management, 1 basics on error handling in the controller, Diagnostics & error management – Lenze 8400 BaseLine D User Manual
Page 142: Basics on error handling in the controller, Diagnostics, Error management, 8diagnostics & error management
8
Diagnostics & error management
8.1
Basics on error handling in the controller
142
Lenze · 8400 BaseLine D · Reference manual · DMS 5.5 EN · 01/2014 · TD05
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
8
Diagnostics & error management
This chapter provides information on error handling, drive diagnostics, and fault analysis.
8.1
Basics on error handling in the controller
Many of the functions integrated into the controller can
• detect errors and thus protect the device from damage or overload, e.g. short-circuit detection,
Ixt overload detection, overtemperature detection, etc.
• detect operating errors by the user, e.g. a missing memory module,
• output warning signals, e.g. if the speed is too high or too low, etc.
Depending on the importance, the error detection in the device responds very fast (e.g. short-circuit
detection < 1 ms) or in a slower cycle (e.g. temperature monitoring approx. 100 ms).
All functions provided with an error detection (e.g. the motor control) supply information to a so-
called error handler. The error handler is processed every 1 ms and evaluates all information.
In this evaluation, the current error (display in
) is generated and the controller is caused to take
the respective error status (e.g. trouble.
The error information in
is used for error diagnosis and contains the following informati-
on:
1. Error type (e.g. "Warning")
2. Error subject area (e.g. "motor management/encoder")
3. The error ID within the error subject area
Together all types of information form the real error number which is unique in the whole device
system.
Structure of the error number (bit coding)
In addition to the control of the device state by the error handler, a logbook function records the er-
rors and their histories.
Tip!
For many device errors, the error type and hence the response of the controller to the error
can be parameterised.