Fusion 360 Postprocessor for the Altmill

Community Support Fusion 360
1

Hello Everyone,

My Altmill is setting in my shop in boxes since it came the day before I had surgery with a 6 week recovery ahead. In the meantime, I am trying to learn as much as I can about using Fusion 360 for my CAM software, specifically about postprocessing files. I have read all I can find on the forum up to this point and was wondering if there are any updates on what postprocessor to use. I did not know if there is anything for GRBLHAL.

What I have seen so far in reading the posts on this forum is that when using Fusion 360 , one uses the Fusion 360 GRBL postprocessor. It sounds like it will work in the GRBLHAL environment of the Altmill G Sender???

When I searched with CoPilot I got this response below: (indicating that tweaks are needed for using the GRBL Post Processor with the Altmill G Sender, tweaks being something way above my pay grade currently.)

For the Sienci AltMill, the recommended Fusion 360 post processor is GRBL—specifically tailored for GRBL-based machines like the AltMill.

Here’s how to set it up effectively:

· :white_check_mark: Post Processor: Use the GRBL post from Fusion 360’s post library.

· :gear: Settings Tweaks:

o Set Safe Retracts to “Clearance Height” instead of “G28” to avoid unexpected plunges if your machine isn’t homed.

o Disable M6 output unless you’re using tool changes.

o Disable Tool Number output unless needed.

Sienci also recommends using their own software, gSender, to send the G-code to the AltMill. It’s optimized for GRBLHAL and works seamlessly with Fusion-generated code.

Finally, from CoPilot I got this information.:

The latest GRBLHAL-specific Fusion 360 postprocessor is being actively developed and shared on GitHub. You can find experimental and updated versions here:

  • The main repository for GRBLHAL and Grbl post processors (including Fusion 360 support) is: grblHAL/PostProcessors on GitHub. This repo includes experimental versions like those by @raenji-sk and updates by @Dietz0r, which address issues such as disabling G2/G3 arcs in ZX and YZ planes[1].

For the absolute latest version, check the releases and commit history in that repository. There are forks and contributions noted, which may provide newer experimental features.

With all of that said I am wondering how those of you using fusion 360 are handling the postprocessing for the Altmill .

Any feedback would be GREATLY appreciated.

2

Co-Pilot gave you the correct answer. I can check later what post processor I use but it is one taken directly from the list that Fusion provides. I am pretty sure I applied one tweak but they are straight forward to apply and definitely not above anyone’s pay grade.

You can use the post processor that Fusion provides without any tweaks.

1 Like
3

I use the Fusion Grbl post processor. I don’t see a GRBLHAL version in the standard list of post processors

4

Thanks for the reply, Jens.

So, it sounds like I can go ahead and use the GRBL postprocessor. I would be interested in what tweak you made.

Here are the ones CoPiltot suggested.

· :gear: Settings Tweaks:

o Set Safe Retracts to “Clearance Height” instead of “G28” to avoid unexpected plunges if your machine isn’t homed.

o Disable M6 output unless you’re using tool changes.

o Disable Tool Number output unless needed.

I’m not quite sure why one would disable tool changes, but then my Altmill is sitting in boxes yet so I have no clue what I’m talking about. Also, I’m not quite sure what they are getting at as to the retracts and clearance height mods.

5

I looked at the post processor file but I couldn’t tell but I suspect there was no modification made because yes it is indeed beyond my pay grade :frowning:

In the back of my mind I seem to think there was some configuration someplace that was for ordinary folk (much simpler) but I don’t recall the details. For all I know that mod was related to my 3D printers. It could also have been in gSender …..

In any case, I use the GRBL post processor and have not had any issues

6

grblHAL is just a continuation/extension of getting for more capable controllers. Gcode generated for grbl is 100% compatible with grblHAL controllers.

The “tweaks to the post processor” are just check boxes when you post.

Most people don’t use G28 locations, so including that in your output can result in a crash.

Not including M6 is probably a pull from the decade or so when most grbl interfaces had no decent way to handle tool changes. Tool numbers as well.