Fusion 360 Post Processor MPCNC v3.0 (Beta 3) is Available

The post-processor, by default, enables no option that would not align with your F360 license. As the user, you need to determine what is enabled and how this aligns with your license.

Scale Feedrate should scale the Z feedrate, and for your configuration, I recommend setting it on. I would carefully check your GCode after making the change, as I would have thought the Max Z Cut Speed or the Max Toolpath Speed should have placed hard limits on the Z5 F3000.

I have now reviewed the code and with Scale Feedrate disenable there is NO Scaling or Limiting of the feedrates. This is why the F3000 is making it through in the GCode.

I have not updated the GitHub with the latest Betas. Since the code is JavaScript, the single file is inside the post-processor zip file. Just unzip and you can review the code.

I understand the default choices now and I will check my license terms and proceed appropriately.

ChatGPT to the rescue:

Option Effect Alone Effect Combined
Scale Feedrate Scales all feedrates (safe global slowdown). If combined with Enforce Feedrate, every move outputs the scaled-down feedrate — no inheritance confusion.
Enforce Feedrate Forces F codes on every line, no logic change. Ensures your scaled feeds are always explicit in G-code.
Allow Rapid Z Determines if Z uses G0 or G1. When false, Z moves respect your (possibly scaled + enforced) feedrate — safest option for fragile or slow Z axes.

Don this Beta v3 isn’t on the github repo right?

That is correct it isn’t. It’s JavaScript just unzip the file and you have the source.

Hey Don, could you explain this

enables no option that would not align with your F360 license** . As the user, you need to determine what is enabled and how this aligns with your license.

I’m on basic hobby fusion licence. I’ve notice my travel speeds in-between cuts are quite slow. Is there an option in the post processor or in Linking I should change?

Im having great results with fusion. But I’m a bit overwhelmed with the amount of settings. If you have any tips on settings that would help that would be amazing.

Yeah, that’s a limitation of the Personal Use (Hobby) license. I use EstlCAM for creating the gcode. If you have your heart set on using Fusion for creating gcode, you may need to manually edit the output to increase the travel speeds.

In the hobby version of F360 all moves are G1 (slow cutting moves), F360 sends no fast G0 (rapid moves) to the post processor. This results in very slow overall performance.

As a developer I have respected F360 defaults and pass G1s from F360 as G1s, and G0s from F360 as G0s. This creates a GCode file as F360 intended and as aligns with your license.

That said, if you are a hobbiest there are options in the post processor that you can enable that greatly increase overall performance - but you should not be enabling these if you are doing production work. If you are doing production work with the hobbiest version of F360, these options were not intended to bypass the need to be licensed correct - you should instead buy a production license for F360.

That said, as I hobbiest I do enable these option as my work is limited to small personal projects and nothing I create is sold or given to others.

The post processor can’t change the hobbiest output into the same as the production output of F360, but it can sure help. For clarity, get a production license if you need production speeds.

Options that help are:

  • converting G1 cutting moves to G0 rapids, if the Z position is above a defined Safe height
  • Convert G1 cutting moves to G0 rapids, if the move is only vertical, is going up, and the target is above the defined Safe height
  • Convert the first G1 cutting move at the beginning of a cutting sequence to a G0 rapid - as a cutting sequence always moves to the first location before a cut occurs.

For these to work you must ensure your Safe height is set to align with the clearance heights you used in F360.

As a hobbiest I consider enabling these to be within the spirit of how I’m using F360. If I was doing production work then I would purchase a production license, in which case these options would result in no conversation of G1s to G0s as they would all be correct prior to reaching the post processor.

I hope this helps explain what options are available to hobbiests who are playing around.

IMHO, adding these features are great and should be used by everyone using the hobby license. There’s no legal reason to worry (that I know of) for you or the user. I conpletely disagree with Fusion’s choice in making everything G1 in the hobby license too, so I think you’re free of any moral objections.

If someone is signed up for a hobby license and making production parts (at least, over a few trinkets for a side business that is struggling to pay rent), then that is a problem and the G0 isn’t the reason that is amoral.

This is the fusion section. And this post specifically is about the post processor that can replace the G0 rapids as Don said.

Thanks guys, this has helped a lot.

Don / Others, would you mind posting a screenshot of your settings in the Post Processor Output bit? I would love to see what bits you’ve changed etc.

Mine is probably default at the moment.

I’m running a Primo MPCNC, but thinking I can bump up my Max cutting rates.

Hobbiest should consider enabling all options in Section 3, but only if they are not doing production work. Safe Z to Rapid takes a layer name where rapids are safe (ā€œRetractā€), if this is not defined within the F360 environment for some reason then 15 mm is used. Users need to ensure this value is set correctly in their F360 setup.

I won’t comment on the other options as my use of F360 for milling has been extremely limited. The other options are material and machine specific.

I wrote the post processor during Covid, mostly as a challenge to myself. My early career was as a software engineer building CAD tools. Having used F360 and built an MPCNC I hated the fact that I couldn’t drive the MPCNC effectively from F360.

3 Likes

Hi there Im a new MPCNC user and Im using V3 pp with Fusion on the mac. I have a couple of issues with the a parallel pass. I would have put it down to an issue with slip on the machine but while watching i noticed a couple of moments where CNC seemed to just stop moving. Im new so Im not able to read or understand Gcode yet unfortunately.

I highlighted the areas which seemed to have an issue. I had a similar issue on two different tool paths, so I thought it might be code related.

LilaFine359.gcode (3.3 MB)

the second image is a test pattern I did, and you can see a similar depression. on both parts I had two passes, an adaptive clearing, which seemed to work perfectly, then a fine detail parallel pass which both seemed to have issue.