L_MC4P - MC_MovePath with auxiliary axes and variables in G-Code: Occurring error message "InvalidPathOrientation" (fixed as of V03.31.00)

Removed from:

Library: L_MC4P_RoboticHandling (FAST Motion) as of V03.31.00

(Update via Package Manager)

Behavior of the new version:

When running a G-code file, it no longer happens that an error message is erroneously displayed.

Description of behavior:

An error message 'InvalidPathOrientation' is erroneously output when a G-code file is run

Under what conditions does the behavior occur?

A G-code file is read in via L_MC4P_PathRefFromFile and moved via MC_MovePath and
the auxiliary axes are read using AUX1...AUX6 programmed and
the target positions of the auxiliary axes are not constant, but are set at runtime via the symbol configuration , e.g. using $GVL.varAux1$ .

Affected products:

Library: L_MC4P_RoboticHandling (FAST Motion)

Short-term measures, Rating/Recommendations:

If up to three auxiliary axes are used, they must be programmed with the coordinate words U, V and W, instead of AUX1..AUX3.

[Automatic Translation]