Corrected from:
Library: L_MC1P_MotionControlBasic (FAST Motion) from V03.17.00.226
(update via Package Manager)
Response of the new version:
For negative input values, including zero at the acceleration override 'lrOverrideAcc', the minimum possible value is now internally used for the calculation and not as before incorrectly the value 1.0.
What happens?
A negative input value (including zero) is selected at the acceleration override 'lrOverrideAcc'.
For the acceleration override, only values in the range of a minimum value up to +1.0 are permissible.
The value zero is explicitly not permissible! (keyword 'division by zero').
When does this behaviour occur?
The behaviour occurs when selecting values below the permissible value range of the acceleration override input.
Which products are affected?
Library: L_MC1P_MotionControlBasic (FAST Motion)
Short-term measures:
Only select values in the range of >0.0...1.0, i.e. not exactly zero and no negative values.
Evaluation/recommendations:
Actually, in practical operation, the acceleration override is probably only used in very few, special applications.
Therefore we do not expect a noteworthy number of problems in the behaviour of existing systems due to the above correction.
