- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello all, this will probably be an easy problem for some of you, but I have searched for a solution to no avail (as of yet). I'm trying to post-process a Swarf toolpath using the Haas NGC post processor, from this link: https://cam.autodesk.com/hsmposts.
I quite like using the Swarf toolpath to accomplish specific machining paths, it seems to have more flexibility in specific selection of surfaces to be machined and boundaries, while also facilitating machining with the side of the cutter only. I could use other 2D or 3D toolpaths, but they seem to be driven by multiple contours and edges, whereas I can select *one* specific face with Swarf, and configure it to do exactly what I want and only that. Note: this toolpath is only a 3-axis toolpath. On a side note, if you pro-users are aware of how to accomplish this with a non-multi-axis toolpath, that could be useful, and avoid this post-processor issue entirely. However, I would like to use the swarf toolpath, because my machine does have a 4th-axis rotary, which I intend to use for other operations.
A series of numerically ordered screenshots will explain the following:
When using the un-altered post, the error message Fusion 360 gives in the log is "This post configuration has not been customized for simultaneous 5-axis toolpath."
So, I modify the settings in the post-processor configuration screen, changing the "Has A-axis" and "Has B-axis" to "Yes", thinking this may allow the post to accept this Swarf (Multi-Axis) toolpath. The error changes to "Tool orientation is not supported for available machine axes." Problem on line 490, a section of the onOpen() function is causing an error when "setMachineConfiguration(machineConfiguration)" code is called.
I've opened the post-processor file directly, and attempted to search for relevant parameters related to tool orientation, but I'm not altogether sure what to look for. I can read javascript somewhat, but there are so many lines within this post-processor, parsing, querying, and referring to functions within the Fusion 360 CAM processing software, that I don't know how to proceed troubleshooting this.
I'll try to attach .F3D file for clarity as well.
Solved! Go to Solution.
