Firmware ≤ 02.00 - DMS 2.1 EN - 03/2011 L 193
8400 motec | Software Manual
Diagnostics & error management
Basics on error handling in the controller
9 Diagnostics & error management
This chapter provides information on error handling, drive diagnostics, and fault analysis.
9.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 C00165
) is generated and the controller is
caused to take the respective error status (e.g. trouble).
The error information in C00166/1..3
is used forerror diagnosis and contains the following
information:
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)
( 204)
In addition to the control of the device state by the error handler, a logbook function
records the errors and their histories. Logbook
( 197)
Tip!
For many device errors, the error type and hence the response of the controller to
the error can be parameterised. Setting the error response
( 201)
To Next Page
Loading...
Need help?
General
