07-15-2020, 03:18 PM
To whom it may concern,
I am having issues with RoboDK not properly importing my NC path (G-code). I have attached pictures of the tool path generated with NX and imported into RoboDK using aRobot Machining Project. I noticed that RoboDK adds in a path from the reference frame origin to the start point (which isNOTin the G-code) and that the tool orientation isn't consistent with NX (normal to the face). I'm aware of the offsets within aRobot Machining Project, but we would likeminimalmodifications to a project/station for consistency purposes. Is there a way I can suppress that path addition (I had removed the default approach and retract movements) and determine precisely how RoboDK interprets coordinate system rotations, offsets, and orientations?
Thank you!
I am having issues with RoboDK not properly importing my NC path (G-code). I have attached pictures of the tool path generated with NX and imported into RoboDK using aRobot Machining Project. I noticed that RoboDK adds in a path from the reference frame origin to the start point (which isNOTin the G-code) and that the tool orientation isn't consistent with NX (normal to the face). I'm aware of the offsets within aRobot Machining Project, but we would likeminimalmodifications to a project/station for consistency purposes. Is there a way I can suppress that path addition (I had removed the default approach and retract movements) and determine precisely how RoboDK interprets coordinate system rotations, offsets, and orientations?
Thank you!