L_MC1P_BrakeTest: When executed again after error reset, slipping does not lead to finish (corrected from V03.21.00)
Corrected from: Library: L_MC1P_MotionControlBasic (FAST Motion) from V03.21.00.102
(Update via Package-Manager)
L_MC1P_MotionControlBasic (FAST Motion) from V03.20.01.01 (Preliminary version)
This version is only made available in agreement with Lenze and for individual cases only.
Update via manual installation of the new library version and integration into the project using placeholders.
Response of the new version:
Brake slippage is now reliably detected even if the brake test function is executed several times, and the brake test function is terminated with the associated error message.
What happens?
When the brake test function is carried out again, slipping of the brake (brake wear) is not detected. For the duration (2 * Ramptime + Holdtime) the motor then operates with the specified torque against the closed but slipping brake. The speed can increase to a greater or lesser extent, depending on the still effective frictional force of the brake.
When does the behaviour occur?
i950 Servo Inverter only: The brake test function is carried out a second time after the brake has already been detected as slipping during the previous run, with an error message being output. Running it again first requires an error reset.
Which products are affected?
Library: L_MC1P_MotionControlBasic (FAST Motion)
Short-term measures, Evaluation/Recommendations:
If a brake malfunction (slipping) has been detected via the brake test function, the brake should generally be inspected first and checked for possible defects. Workaround: First carry out a power switch to reinitialize the system and then restart the brake test function if necessary.
Notice:
The preliminary version of the library 'L_MC1P' is only intended for short-term remedy in existing systems. If the brake test function is used and the described workaround is not considered sufficient.
If necessary, please contact the responsible Lenze sales company.
