Hi, I do a lot of milling work using rhinoCAM as a toolpath generator. Using the gcode interpreter is very usefull for 3 axis work, but I was unable to use it to read 5 axis toolpath.
As far as I know, APT CLS IJK post-processor in rhinoCAM is a good file format to describe target orientation in 5 axis toolpath and reference frame, so please find as an attached file a little script I made to use basic targets informations, speeds & feeds contained within this file format. (Thank you @tristangobin for the 3x3 matrix part).
Maybe it could be an enhancement to make the gcode interpreter a little bit more post-processor dependent.
As I picture it, the shift + up or down arrow on the component could give us access to variations of that component, each one adapted to various post-processors.
What do you think ?
PS : the script only work well with 1 setup in rhinoCAM and only work with toolpath discetized with linear segments and not with arcs. So expect a massive amount of targets. You can ignore the GHpython part that I use to set spindle speed with a custom expression that is relevent to the robotic cell I'm using.
Hi, I do a lot of milling work using rhinoCAM as a toolpath generator. Using the gcode interpreter is very usefull for 3 axis work, but I was unable to use it to read 5 axis toolpath. As far as I know, APT CLS IJK post-processor in rhinoCAM is a good file format to describe target orientation in 5 axis toolpath and reference frame, so please find as an attached file a little script I made to use basic targets informations, speeds & feeds contained within this file format. (Thank you @tristangobin for the 3x3 matrix part).
Maybe it could be an enhancement to make the gcode interpreter a little bit more post-processor dependent.
As I picture it, the shift + up or down arrow on the component could give us access to variations of that component, each one adapted to various post-processors.
What do you think ?
PS : the script only work well with 1 setup in rhinoCAM and only work with toolpath discetized with linear segments and not with arcs. So expect a massive amount of targets. You can ignore the GHpython part that I use to set spindle speed with a custom expression that is relevent to the robotic cell I'm using.
APTCLSIJK.zip