I’ve build a CNC controller using an Arduino running GRBL 1.1h and I find that Carbide Motion won’t connect to it. Universal Gcode Sender connects to it and controls it just fine but I would like to use Carbide Motion, mainly because I’m more familiar with it. I’ll stick with UGS if I have to but I would like to know why Carbide Motion won’t play with it. Anyone have any ideas?
Carbide Motion only connects to Carbide 3D machines.
Yeah well so it seems. I was just hoping there was some way to make it work.
Ok, thanks Will. I’ll give it a read.
My understanding is that carbide motion does some custom shenanigans with the various C3D devices. So I’m assuming there are some deeper software integrations than just fire and forget gcode sending. (Device drivers and other software Magic maybe 
)
If you’re just interesting in something a little “friendlier” than UGS then maybe give gSender a shot. It was my favorite of the gcode senders I tried awhile back.
Thanks for the comment Tyler. It was more of a curiosity thing than anything else, like “Why the heck won’t this program connect I wonder.” I thought that if someone had done it, I wanted to know how. Since there seems to be some technical barrier I’ll just forget about the idea and move on.
1 Like
As far as I know CM has never worked on any machines not made by C3D. Carbide Create works if you use the generic or gbrl post processor. V6 of CC made separate gcode files which a 3rd party machine could use. Starting in v7 of CC the gcode is encrypted inside the .c2d file and if you buy the pro version of CC you can output separate gcode files. So v7/v8 of CC without the pro license will not work on 3rd party machines.