Differences between original Pose in GCODE and Pose imported in RoboDK——革命制度党ntable Version +- RoboDK Forum (//m.sinclairbody.com/forum) +-- Forum: RoboDK (EN) (//m.sinclairbody.com/forum/Forum-RoboDK-EN) + - - -论坛:通用RoboDK问题(//m.sinclairbody.com/forum/Forum-General-questions-about-RoboDK) +--- Thread: Differences between original Pose in GCODE and Pose imported in RoboDK (/Thread-Differences-between-original-Pose-in-GCODE-and-Pose-imported-in-RoboDK) |
Differences between original Pose in GCODE and Pose imported in RoboDK-Frai13-05-13-2021 Hi, I exported a GCODE using Powermill 2021 and I imported it in RoboDK as "Machining Project" with a Kuka robot. The target angles in the RoboDK program are not equal to the original ones, as u can see in the pictures attached. Original GCODE: RoboDK imported Movel: Which is the reason of this difference? Thank you so much. RE: Differences between original Pose in GCODE and Pose imported in RoboDK-Jeremy-05-13-2021 Hi Alvaro, This may or may not be an issue. First, did you try with other Euler angles formats? Right now, in RoboDK, you are using Rot[Z,Y',X''] (standard KUKA format), but it doesn't mean the GCode uses the same representation. Different Euler Angles format can mean that different sets of values represent the same cartesian orientation. It could also be that the post-processor you selected in PowerMill isn't generating the orientation in a way RoboDK understands. If you have a post-processor that does generate .apt files, I would recommend you give it a go instead of the standard G-Code. Jeremy RE: Differences between original Pose in GCODE and Pose imported in RoboDK-colinb83-05-13-2021 What post are you using in Powermill? |