NORD Drivesystems BU0510 User Manual
Page 71
BU 0510 GB-3911
Subject to technical alterations
71
Display
in the ControlBox
Fault
Text in the ParameterBox
Cause
Remedy
Group
Details in
P700 / P701
14.5
Pos. diff. Speed
Change of position and speed do not match
Check the position detection and the control setting in
P630
14.6
Diff. between Abs. and Inc.
Difference between absolute and incremental encoders
Check the position detection and the control setting in
P631
Position change for the absolute and incremental
encoders do not match
14.7
Max. Pos. Exceeded
Maximum position exceeded
Check the specified setpoint and the control setting in
P615
14.8
Min. Pos. Undershot
Minimum position undershot
Check the specified setpoint and the control setting in
P615
E025
25.0
Hiper. abs./inc. error
Hiperface encoder monitoring detects an error during
comparison of data between the incremental and absolute
signals. (absolute position deviates from that which is
calculated incrementally)
Poor cable shielding
The Sin/Cos signals are not connected or are
defective. Check with P709[-09] and [-10]
25.1
Universal encoder
communication
Communication error for the universal encoder interface (CRC
checksum error)
Poor cable shielding
Encoder triggering incorrectly set. (BISS, SSI)
SSI does not support Multiply Transmit
25.2
No corresp. universal
encoder
No connection to selected universal encoder
Encoder not connected or data cable not connected
correctly
No voltage supply to encoder
Incorrect encoder type set
25.3
Universal encoder resolution The set universal encoder resolution does not match that
which is transmitted by the encoder.
25.4
Universal encoder error
The universal encoder reports an internal error to the the FI
Restart encoder
NOTE
Parameter P650[-03] counts the communication errors to the universal encoder since switch-
on. If this parameter has a high value, this may indicate a poorly shielded encoder cable. This
may also be the cause of the error.
A communication error does not necessarily result in a fault. An error is only triggered if
several consecutive communications have failed.