Here’s another plugin im developing right now.
5 Likes
Here’s the new plugin
4 Likes
Based on something I read on the FluidNC Discord today, it sounds like efforts to add support for FluidNC has been abandoned.
Efforts for FluidNC and what? NCSender? Did I miss something?
1 Like
Efforts to support FluidNC in NCSender.
1 Like
Since I don’t use FluidNC and don’t have a machine to test it on, it’s very difficult for me to dedicate time to developing support for it. Because the project is open source, anyone is welcome to fork it and do the work needed to make it compatible.
If you have time to create an interface layer for different controller firmware, I’d prefer that approach, especially if you plan to submit a pull request in the future. This would greatly reduce regression testing across different firmware types and provide better isolation.
That’s the same approach I would take if I decide to support FluidNC in the future and have a machine available to test it. At the moment, I don’t even have space in the garage for a third CNC, even if I wanted to build one.
1 Like
I completely understand that and I don’t blame you one bit. I’ve had my own experiences trying to support hardware I don’t have.
I might look at the code out of curiosity, but I don’t use senders at all with FluidNC (just run directly off the SD using the default WebUI) so I personally am unlikely to pursue it.
Yah, ncSender is client-server app so rewriting it to be just purely client (on a server/controller) might be a lot of work.
But you can always run ncSender on headless mode even on old pi 3 or 4 and just use powerful client to do the virtualization side just like with web-ui.
1 Like