L_MC1P: Target reached state is not set when 'Window target reached'=0 and 'Time target reached' is not effective (corrected from V3.10.0)

Corrected from:
- Library: L_MC1P_MotionControlBasic (FAST Motion) V03.10.00.72
  (contained in PLC Designer V03.10.00.00 and higher)
 
Response of the new version:
The 'Target reached' state (xInPosition output at the L_MC1P_AxisBasicControl FB) is set correctly under consideration of the parameters "Window target reached" (subindex 130) and "Time target reached" (subindex 131). 
The setting "Window target reached" (subindex 130) = 0 means that the evaluation will only be based on the setpoint and the actual value will not be considered.
 
 
What happens?
Under certain conditions, the 'Target reached' state (xInPosition output at the L_MC1P_AxisBasicControl FB) is not set correctly.
The "Time target reached" parameter (subindex 131) is not taken into account.

When does this behaviour occur?
The behaviour occurs if "Window target reached" (subindex 130) is set to 0.
Which products are affected?
- Library: L_MC1P_MotionControlBasic (FAST Motion)
  (contained in the PLC Designer)
 
Short-term measures:
Implement the functionality in the application.
 
Evaluation/recommendations:
A short-term remedy is available.
 

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