Understanding Post Process and zero RPM with multiple toolpaths.

[RufusToad]

I am a little confused about posting multiple tool paths and separating them by tool paths NOT tool numbers.

Let's say I have 6 tool paths for this part and 3 of these tool paths contain the same endmill. When I process the "setup" it brings in all the tool paths for that setup. I then want to separate them by tool path even though a few still contain the same endmill. Why doesn't the toolpath contain an RPM? The first tool path will contain RPM so I am assuming that Fusion thinks the others will follow the first one but when each toolpath has finished the spindle stops, I load the next tool path and try to start it but again, ZERO RPM. Do I have to post process each tool path individually or is there a way to work around this? Why would Fusion assume the tool path already has the spindle running when each path has been separated?

I kind of understand when you separate each path by the tool numbers because the tool paths are combined at that point into 1 file. I hope this makes sense to someone?

[Laurens-3DTechDraw]

Hi,

When you post-process all toolpaths(let's call them operations) in one go, you get them all in one file. Fusion "assumes" you will run this program in 1 go. If you are going to load the code for each operation separately into the machine, you are best off post-processing each operation separately. That way the post processor will know that it needs to place all the spindle start codes, safe moves, etc. at the beginning and end of your files.

You can also always update the post processors to output each operation as a separate file.

But I would be curious why you want this. What machine and control are we talking about here? And which post-processor are you using?

[RufusToad]

Thank you for explaining. I am just a home hobbyist starting out trying to learn Fusion. I am not swapping over from Spaceclaim but I am attempting to learn more of Fusion for the CAM. I purchased the Langmuir MR1 CNC mill and I needed a CAM package to run it and I loaded a Generic Post to run with it. To answer your questions, I was confused when I processed all the operations because Fusion asks you to separate them (or not) by the tool path or tool number. Since I chose to separate them by the path then they are actually put into the file as separate paths so I would have thought they would be assigned a RPM for each individual operation even though they hold the same bit. This was just a test for me to try and understand BUT with that said I also wanted to separate them because I am just learning this and do not feel comfortable enough yet to let it run but I do hope to get there soon:)

[dwilliamsFM6K4]

See if your post processor has this "Safe start all operations" setting, check that on

Should give full WCS callouts, RPM starts etc for every posted toolpath

 

Pictured is the HAAS NGC post

[RufusToad]

Unfortunately I do not see this option although I wish it were there. Now that I know a bit more I don't have an issue saving them all individually but I would still be confused as to why that option would exist if you cant run them each individually?

[Laurens-3DTechDraw]

Well it's a post-processor made by Langmuir and not Autodesk it seems.

And I think they have tried to make life easier but simultaneously made it more complicated.

The problem you have I think is that the Fusion 360 Hobbyist license doesn't allow the posting of different tools in one file? Well yeah, then this option in the post-processor still won't help for that as that "limitation" happens already before the toolpath is actually run through the post-processor.

[RufusToad]

Just out of curiosity what do you mean by 1 file? When this is saved it saves as multiple and I am just wondering if it considers it as 1 file because it has the same tool used?

[Laurens-3DTechDraw]

Fusion considers it as 1 file if you use the option to split in the post processor properties.

This is because it was a very hacky solution by Langmuir in the post. It's not a Fusion supported workflow so to speak.