Hey there @Griff. Glad more people are learning. I find that there is not much to learn with GCode senders. They pretty much all perform the same duty with different interfaces and bells and whistles. I think our main limitation is our control board. It uses GRBL and, it’s my impression, is on the basic end or control for CNCs. Mach3 seems to be more powerful for example. GRBL is all I’ve ever used so it’s only my impression.
CNCjs has a great interface and with knowledge of GCode you can mimic all the functionality of Carbide Motion and probably more. This is why I have started this thread. I am a little disillusioned with Carbide3D and their probe. I love my Nomad and Carbide Motion but feel I could no more with CNCjs.
Using CNCjs you will have to get comfortable with how your workflow needs to change. Carbide Motion automates a lot of things for you and makes it almost foolproof. You can, with Macros, have the same functionality as any GCode sender, I think. It’s a matter of just getting used to it. Not a lot to re-learn, just a new order of things. It will give you more flexibility in the end. Once I have it figured out, I will post a tutorial on my process for anyone interested. Thanks to @neilferreri I am getting very close. All the mechanics are there. I need to figure out how some calculations are made and where those values get stored for everything to work as we expect in Carbide Motion.