I’ve been refining my FluidNC workflow lately and ended up building a few tools that might help others running similar setups.
I started by writing a custom Fusion 360 CPS specifically for FluidNC. The generic posts were adding modal clutter and commands FluidNC doesn’t even use, so I built one from scratch that outputs clean, predictable G‑code. It handles units, offsets, motion modes, and start/end sequences exactly the way FluidNC expects them. It also supports proper M6 Tx tool‑change output, full coolant control, 4th‑axis support, and the ability to start machining from a specific machine‑coordinate position without relying on G28. You can also define the exact machine‑coordinate position where the machine should end when the program finishes. The CPS behaves according to how FluidNC actually works, not how Fusion assumes it works.
On the sender side, I took NCSender and made a FluidNC‑focused fork. I reworked the communication layer, improved buffer handling, and made the sender sync correctly with FluidNC’s internal state. The goal was to eliminate hidden automation and keep everything under explicit control. The project grew enough that it deserved its own identity, so I renamed it mfsender.
I also want to give a genuine thanks to the original creator of NCSender — their work was the inspiration and the foundation for this whole fork. Without that starting point, mfsender wouldn’t exist.
Alongside the CPS and mfsender, I’ll also be releasing a set of Fluid‑written macros for finding centers, edges, Z references, and more. These are the same macros I use daily in my own workflow.
Everything will be available soon on my Patreon for anyone who wants a cleaner, more controlled FluidNC toolchain.
Maybe you and @siganberg can work together on it so there’s not a new sender again?
Besides that: Nice job! Since you forked NCSender, make sure it is available outside of your Patreon, for free! It’s published under an open source license you’ve got to honour as well (or pay Siganberg): GitHub - siganberg/ncSender
Just to clarify — mfsender is an open-source fork of ncSender and remains available on GitHub in full compliance with the original license.
The Patreon supports the additional FluidNC-specific work around it (custom macro system and Fusion 360 CPS development), not the original ncSender code.
The intention isn’t to fragment the ecosystem — only to extend it for a FluidNC workflow.
Cool. It sounds like you tried to work with the original developer but it didn’t work out since he didn’t know FluidNC and was focused on GrblHAL. So, a fork makes sense.
FYI, I got pibot board to play with and I was working on v2 of ncSender both Pro and Community version so decided to stub the different protocol while Im on it.
I just add 4axis support. the project it is ready for use. I am running a production job at the shop and its working great. I hope to release the version this week.
