I think there is at least a documentation issue here, but also a missing concept that users are coming up with (wrong) ways to fill in. Even the YouTube tutorials posted by AutoDesk personnel aren't teaching the appropriate workflow.
This very useful video uses two different bits within one setup, but since there are only two operations (each using a different bit), and he didn't show the post processing step it doesn't have to deal with the idea of creating 2 nc files under one setup that contain the paths per bit.
Patrick Rainsberry's awesome face carving video does try to deal with how you post process different files for each bit, but does so by creating two different setups which will break rest milling.
But I think that this confusion is built into the data model for Fusion's CAM. The Setup has a post process tab where you specify what becomes the default filename for the nc file. This works great when there is only one nc file to be generated for the Setup (one bit, or I assume a CNC with a carousel), but the only things that fall under a Setup are Operations and Folders. A Folder however doesn't have a post process tab like the Setup does, so there's no built in concept that this folder is actually the level at which you are dealing when you are going to be post processing your operations. For example in Patrick's video the right thing to do seems to be to create two folders under the one setup, name each for the bit used, and change its missing post processing tab to "rough" and "finish". Then when you click on that folder and post process from there it'll guide you through what filename is appropriate for the nc file.
I actually think that the Setup/Folder/Operation objects don't clearly model the relationship between the concepts of CAM. It seems in reality the hierarchy is:
- Setups which are placing a piece of stock in the machine positioned in a certain way
- Uses of a particular tool within that setup (1/8 ball nose)
- The operations using that tool in that setup (carve this pocket, then carve that pocket)
It's the middle level that's not clearly represented, and except for degenerate cases of a single bit it's the level at which I suspect post processing should be done.
Add to the confusion that the rest machining documentation and tooltips talk about the "previous operation", not the "previous operation within this setup". Now that seems obvious to be now and it probably seemed obvious to the authors, but I assure you it is not obvious to someone trying to learn this.
I think at the very least there should be a section added to the concepts section of the help which explains this concept hierarchy.
Should I submit this on IdeaStation, or is this post sufficient? Am I incorrect in anything said above?