Corrected from:
- Library: (L-force Motion) L_SM3_DriveUtil (no changes planned for L-force Motion)
(contained in the PLC Designer)
Response of the new version:
______________________________________________________________________________________________
What happens?
In the case of a quick stop via the input of the L_SMC_AxisBasicControl FB, the axis is not directly decelerated along the defined quick stop ramp, but the currently pending following error is compensated first. As a result, the braking distance is correspondingly longer.
When does this behaviour occur?
The behaviour particularly occurs if a big following error appears, e.g. after a position setpoint step change due to an incorrect setpoint calculation, and a quick stop shall be effected via the L_SMC_AxisBasicControl function block after this.
Which products are affected?
- Library: (L-force Motion) L_SM3_DriveUtil
(contained in the PLC Designer)
Short-term measures:
Use the internal quick stop function of the drive via the xDriveStart input of the L_SMC_AxisBasicControl FB.
Evaluation/recommendations:
The above-described short-term measure provides a workaround for the function restriction.
