![]() In the CAM tab in the Options menu, what affect does the Default Tool X Axis Orientation have on the simulation? Does this specify how the X axis of the TCP is matched to the reference frame? When I changed the default from -X to +X, the Robot Machining Project Preferred Tool X Axis changed from 90,180 to 90,0. How does RoboDK match the path and tool orientation by default? When the Path to Tool Offset values are all set to zero, the TCP and reference frame, in which I import my NC program with respect to, do not match. How are the Frame Offset and Tool Offset values different from the Path to Tool Offset values, if there is any difference? What affect does the Preferred Tool X Axis have on the simulation? What axes do these rotations occur about/with respect to? What order are these rotations done in? I noticed that the Motoman post processed job (.JBI) file is the same for 90,180 as 0,0 but intermediate values affect the simulation and post processed job file. Thank you Jeremy! I have few more questions regarding the Preferred Orientation section in the Robot Machining Project window. You will, therefore, lock the rotation around the Z-axis. Simply bring the "Optimization parameters" to zero. This degree of freedom is usually the rotation around the Z axis of the TCP." Are there ways in RoboDK to fully constrain this motion about the 6th axis so RoboDK does not manipulate the G-code commands and orientation(s)? Quote: From RoboDK's documentation, "Since a 6-axis robot is used to follow a 3-axis or 5-axis CNC manufacturing program we have an additional degree of freedom to define. It only affects the orientation of the tool with respect to the path. Minimum tool Orientation Change and Tool Orientation Follows Path has no effect on the imported points and their precision. Path to Tool offset will create an Offset between the path and the active tool following the orientation of the selected reference frame. Quote: What impact do the Path to Tool Offset and Select Algorithm, specifically Minimum Tool Orientation Change and Tool Orientation Follows Path, parameters have on importing and exporting G-code files? Does this affect the accuracy of the simulation? This error shouldn't affect the imported G-code.Īll useful G-code commands are interpreted by RoboDK. ![]() Quote: When importing a G-code program, the following G-code import error is shown: “Tool height compensation has no effect.” Could you provide an explanation and/or supplementary documentation for how RoboDK interprets all G-code commands and reasons for this error? This degree of freedom is usually the rotation around the Z axis of the TCP." Are there ways in RoboDK to fully constrain this motion about the 6th axis so RoboDK does not manipulate the G-code commands and orientation(s)?Ĭould you provide any supplementary documentation for the Motoman post processors? ![]() ![]() What impact do the Path to Tool Offset and Select Algorithm, specifically Minimum Tool Orientation Change and Tool Orientation Follows Path, parameters have on importing and exporting G-code files? Does this affect the accuracy of the simulation?įrom RoboDK's documentation, "Since a 6-axis robot is used to follow a 3-axis or 5-axis CNC manufacturing program we have an additional degree of freedom to define. When importing a G-code program, the following G-code import error is shown: “Tool height compensation has no effect.” Could you provide an explanation and/or supplementary documentation for how RoboDK interprets all G-code commands and reasons for this error? After reading the RoboDK documentation provided and consulting tutorial videos, I have a few questions: I am currently researching the applicability of RoboDK to our Motoman MH180 robot for simulation purposes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |