L_MC4P: TM Pick&Place: Travel request to the current position is not completed (corrected from V3.10.0)

Corrected from: 
Library:  L_MC4P_RoboticHandling (FAST Motion)  from V03.10.00.105
                L_TT1P_TechnologyModules_LM (TM Pick&Place)  from V03.10.00.8
               (contained in PLC Designer from V03.10.00)

Response of the new version:
The motion function block correctly outputs xDone=TRUE when two travel profiles with the same target position are executed in a row.

 
What happens?
The programmed travel profile is not completed. The motion function block does not output xDone=TRUE although the axis is at the programmed position.
 
When does this behaviour occur?
If a travel request with a target position to which the axis has travelled in the last travel request is triggered by means of a motion function block such as MC_MoveLinearRelative or by means of the Pick&Place technology module, the travel request is not completed with xDone=TRUE.
 
Which products are affected?
Library:  L_MC4P_RoboticHandling (FAST Motion)
                L_TT1P_TechnologyModules_LM (TM Pick&Place)
                (contained in PLC Designer)
 
Short-term measures:
Do not execute two travel profiles with the same target position in a row.
 
Evaluation/recommendations:
The programmed travel profile is not completed although the axis is at the target position. When linking travel profiles, the sequence profile will not be started. In general, two travel profiles with the same target position are not executed in a row.
 

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