# Fusion 360 Post Processor Maslow 4

**URL:** <https://forums.maslowcnc.com/t/fusion-360-post-processor-maslow-4/20053>\
**Category:** Software\
**Tags:** fusion360\
**Created:** [March 7, 2024, 12:40am UTC](https://forums.maslowcnc.com/t/fusion-360-post-processor-maslow-4/20053 "2024-03-07T00:40:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Frank\_Wiebenga](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/frank_wiebenga/32/22326_2.png) [@Frank\_Wiebenga](https://forums.maslowcnc.com/u/Frank_Wiebenga)\
**Post date:** [March 7, 2024, 12:40am UTC](https://forums.maslowcnc.com/t/fusion-360-post-processor-maslow-4/20053/1 "2024-03-07T00:40:04Z")

</div>

Is version 44104 the correct post processor to use for Maslow 4?

> **[Post Library for Autodesk Fusion | Autodesk Fusion](https://cam.autodesk.com/hsmposts)**
>
> Autodesk Fusion CAM Solutions

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [March 7, 2024, 1:18am UTC](https://forums.maslowcnc.com/t/fusion-360-post-processor-maslow-4/20053/2 "2024-03-07T01:18:15Z")

</div>

I would use the GRBL one. Maslow4 is based on FluicNC which is based on GRBL so anything GRBL should work great.

---

<div class="post-metadata">

**Author:** ![Frank\_Wiebenga](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/frank_wiebenga/32/22326_2.png) [@Frank\_Wiebenga](https://forums.maslowcnc.com/u/Frank_Wiebenga)\
**Post date:** [March 7, 2024, 1:33am UTC](https://forums.maslowcnc.com/t/fusion-360-post-processor-maslow-4/20053/3 "2024-03-07T01:33:58Z")

</div>

Ok perfect, I’ll probably just keep using the Carbide3d post then since that’s grbl as well.

---

<div class="post-metadata">

**Author:** ![MrN808](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/mrn808/32/22275_2.png) [@MrN808](https://forums.maslowcnc.com/u/MrN808)\
**Post date:** [February 15, 2025, 9:33pm UTC](https://forums.maslowcnc.com/t/fusion-360-post-processor-maslow-4/20053/4 "2025-02-15T21:33:05Z")

</div>

Aloha,

I have been using the Fusion Maslow post processor, but in this round the files aren’t working. So I gave the GRBL post a try and the files are MUCH smaller (yay!), but they seem not to know what WCS I’ve set in Fusion. Trying to get some cuts.

---

<div class="post-metadata">

**Author:** ![MrN808](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/mrn808/32/22275_2.png) [@MrN808](https://forums.maslowcnc.com/u/MrN808)\
**Post date:** [February 15, 2025, 10:56pm UTC](https://forums.maslowcnc.com/t/fusion-360-post-processor-maslow-4/20053/5 "2025-02-15T22:56:39Z")

</div>

Could not get the output from the Fusion Maslow post processor to work, so I switched to the Fusion GRBL and, after a kurfluffle regarding Work Coordinate System (WCS), it’s working well! And the GRBL post processor files are MUCH smaller already (like, 390K instead of 3M).

---

<div class="post-metadata">

**Author:** ![md8n](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/md8n/32/28197_2.png) [@md8n](https://forums.maslowcnc.com/u/md8n)\
**Post date:** [February 16, 2025, 11:31pm UTC](https://forums.maslowcnc.com/t/fusion-360-post-processor-maslow-4/20053/6 "2025-02-16T23:31:24Z")

</div>

Try this:

> [@...And the Travelling Salesman arrives at GCodeClean v1.3.0](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/71):
>
> GCodeClean arrives at v1.4.1 - Preamble fixes Thanks to a bug (mainly Fusion 360’s fault) reported by @MrN808, I fixed two oversights of mine in the preamble processing. And here’s the result - Command line version at the moment though - I’ll try and get the GUI version updated soonish [Release v1.4.1 - Preamble Fixes · md8n/GCodeClean](https://github.com/md8n/GCodeClean/releases/tag/v1.4.1)