L_MC4P: Axes not programmed in the NC program do not behave as expected with MovePath (corrected from V03.26.00)

Corrected from:

Library: L_MC4P_RoboticHandling (FAST Motion) from V03.26.00

(Update via Package Manager)

Response of the new version:

All non-programmed axes now remain correctly at the start position.

What happens?

If an NC programme (*.lpp file) is run and not all axes are programmed in the first movement block (e.g. N10 G01 Z100), then the started axis moves correctly to the specified position (here Z-->100).

However, all other axes (e.g. X and Y) move to position zero, although the movements of these axes have not been assigned.

When does the behaviour occur?

NC program (*.lpp file) and use of MC_MovePath and L_MC4P_PathRefFromFile.
In the NC file, individual axes of the kinematics are not programmed in the first movement block.

Which products are affected?

Library: L_MC4P_RoboticHandling (FAST Motion)

Short-term measures / evaluation / recommendations:

As a remedy, specify the position for all Cartesian axes of the kinematics in the first block of an NC file.

Automatic Translation

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