L_MC1P - MC_TouchProbe and Continous-Mode: Status TP detected is not set at same TP position (corrected from V03.23.00)
Corrected from:
Library: L_MC1P_MotionControlBasic (FAST Motion) as of V03.23.00.159
(Update via Package Manager)
Response of the new version:
With the new controller variants (C5xx and C7xx) this limitation does not occur anymore, because when inserting the EtherCAT devices the timestamps for the touch probe event are automatically inserted into the EtherCAT mapping. Thus a change/update of the TP event is always detected.
For the older controller variants, e.g. C3200, the function restriction still exists. For these controller types no change is possible/planned.
What happens?
L_MC1P - MC_TouchProbe: The TP status 'NewValueStored_...' is not set under certain conditions.
In case of occurrence it cannot be recognized in the application that a TP event has occurred and a new TP position has been determined.
When does this behaviour occur?
TP mode 'Continous Update
The determined TP position is exactly the same as the TP position from the previous TP event. This usually only occurs if you have selected the zero pulse as the TP event and always travel over the same zero pulse within this one motor revolution.
Which products are affected?
Library: L_MC1P_MotionControlBasic (FAST Motion)
Which products are affected? Library: L_MC1P_MotionControlBasic (FAST Motion)
Short-term measures, Evaluation/recommendations:
Use TP-Mode Single.
A safe handshake between application and TP function can be realized by means of the TP mode single.
