L_MC4P_PathRefFromFile: With G-code file (*.lpp) with more than 30 motion tasks, axle group remains in standstill (corrected from V03.25.00)

Corrected from:

Library: L_MC4P_RoboticHandling (FAST Motion) from V03.25.00

(Update via Package Manager)

Response of the new version:

The behaviour described no longer occurs and the corresponding *.lpp files can be processed without errors.

What happens?

The function modules L_MC4P_PathRefFromFile and MC_MovePath remain in the 'Busy' state and the G-code from the specified *.lpp file is not processed.

As a result, the axle group remains at a standstill.

When does the behaviour occur?

G-code file (*.lpp) with more than 30 driving jobs.
G2 or G3 travel jobs (circular interpolation) with circular arcs of 180° or 360°.

The occurrence can be recognised as follows:

between MC_MovePath.SourceLineNo and L_MC4P_PathRefFromFile.liLineNoDecoded results in a difference of 30 and
L_MC4P_PathRefFromFile.liLineNoDecoded is not on the end of the G-code file (*.lpp)

Which products are affected?

Library: L_MC4P_RoboticHandling (FAST Motion)

Short-term measures / Evaluation / recommendations:

The cause of the occurrence is faulty internal optimisation in the case of split driving jobs.

This optimisation can be deactivated via an invisible property:

MC_MovePath.xOptimisedPathPreparation := FALSE;

Automatic Translation