L_MC1P - MC_MoveContinuousAbsolute: 'ArithmeticError_MoveContAb', when final speed cannot be reached with profile parameters (corrected from V03.18.00)

Corrected from:
Library: L_MC1P_MotionControlBasic (FAST Motion) V03.18.00.252
(update via Package Manager)

Response of the new version:

Positioning is executed after the start request via the Execute input.

If the parameterised final speed cannot be reached because the distance to be traversed is too short, the InEndVelocity output is set for one cycle when the target position has been reached. After that, the drive continues accelerating to the parameterised final speed. After reaching the final speed, the InEndVelocity output is set again.

What happens?

MC_MoveContinuousAbsolute FB / MC_MoveContinuousRelative FB:

After the start request via the Execute input, positioning is not executed.

The ErrorId output displays an "ArithmeticError_MoveContAb" or an "ArithmeticError_MoveContRel" error.

When does this behaviour occur?
- Jerk limitation is deactivated (Jerk input = 0)

- The distance to be traversed is so short that the selected final speed (EndVelocity input) cannot be reached.

Which products are affected?
Library: L_MC1P_MotionControlBasic (FAST Motion)

Short-term measures, Evaluation/recommendations:

Set the jerk limitation to a value greater than 0 (Jerk input > 0)

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/201800258/1/