[Fabian Borgmann]

Hello,
I am encountering an issue when importing G-code into RoboDK. Specifically, toolpaths that are meant to follow a trajectory outside the X-Y plane are not being interpreted correctly. Instead of creating the correct 3D toolpath, RoboDK generates a path that is strictly aligned along the Z-axis.
This problem occurs when the G-code includes rotations or movements around axes other than X and Y (such as A, B, or C for rotational axes). Instead of maintaining the intended trajectory in 3D space, RoboDK appears to ignore the rotational components and produces a simplified path along the Z-axis, which leads to incorrect simulations and execution. I believe RoboDK is interpreting the following code line incorrectly. G0 X0. Y-15.588 Z26.8 A-60: 

The expected behavior is that RoboDK should account for the rotations and produce the correct toolpath in 3D space, reflecting the combined movements along X, Y, and Z, as well as any rotational movements specified in the G-code.
The attached pictures show the problem

[Albert]

Importing G-code files for 4-axis and 5-axis robot machining tasks highly depends on how the machine was built when you output orientation data as A, B, C angles. I recommend you to use the I,J,K vector instead to specify the orientation. Alternatively, you can use the APT format.

What CAD/CAM software are you using? What options do you have as post processors?