L_MC4P: MC_MovePath reports no xDone after execution of the program (corrected from V03.23.00)

Corrected from:
Library: L_MC4P_RoboticHandling (FAST Motion)  from V03.23.00.173
                      (Update via Package-Manager)

Response of the new version: 
The FB MC_MovePath no always correctly reports 'Done'.

 
What happens?
FB MC_MovePath does not report xDone.

When does the behaviour occur? 
Assignment via FB L_MC4P_PathRefFromFile.xExecute = TRUE and
L_MC4P_PathRefFromFile.xExecute is reset before the MC_MovePath has been processed.

Which products are affected?
Library: L_MC4P_RoboticHandling (FAST Motion)
 
Kurzfristige Maßnahmen, Bewertung/Empfehlungen: 
Workaround:
1. PathRefFromFile.xExecute = TRUE ;
    MovePath.xExecute = TRUE ;
...
3. after execution of the program the MovePath.Done reports
4. only then set PathRefFromFile.xExecute = False

Automatic Translation 

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/202100010/1/
Meta data
Taxonomy: Lib L_MC4P_RoboticHandling
AKB-ID: 202100010
Last update: 2023/09/09
Category: Version Informations

Lenze reserves the right to change information on this page at any time. Any liability for the accuracy of the information is excluded.
Contact form