Basically, with the newest macros I shared on GitHub, you set Z zero (however you like to), then probe the first tool wherever it’s convenient and repeatable. CNCjs will store the work position relative to your Z zero and apply that to any new tools you probe.
I’m hoping someone (@GrantyGrant?) will make a quality video showing the process. I don’t have the time (5yr old, 3yr old, and one on the way) or patience to make a quality video, but I get a lot of questions. It really is straightforward once you get used to the lack of descriptive prompts. Been super accurate and precise for me too.
Well, today’s announcement for the BitSetter and the new Carbide Motion 418 makes this thread more relevant. I already installed the post-processor that @neilferreri created. Now waiting for my BitSetter to arrive.
There’s nothing special about the post processor. It just adds an M6 to the gcode where a tool change is required. CM, with the bitsetter, will run the tool change sequence when it encounters that M6. It will retract, move to tool change location, and then do all the probing magic. The same can be done with senders, like CNCjs, that allow macros.
@i3oilermaker I cannot confirm as I don’t have a tool setter to test anything, but much like the HDZ, I would love to play with them someday. I’m in the middle of trying to start a side business with my SXXL, so the budget is tight.
(This may be a null point for many) As G-code Master Jedi @neilferreri mentioned, the .pp V-Carve adjustment allows you to save your vcarve gcode with the M6 command automatically inserted at the correct location, the alternative might be manually locating/entering “M6”. The .pp can do this with a multitude of variables, but for the many CNC’ers this may be a null point. If your a nerd like me and want to learn more, this is where I recommend starting vectric link below. (NOT trying to promote vectric at all)
@WillAdams might be able to confirm if the M6 command is all that is required to prompt CM for a tool change then prompt execution of a tool setter code. I doubt its that simple for a few reasons, but as always, if there’s a will, there’s away. (no pun intended)
So excited for Carbide and the incredible dedication to constant innovation and improvement.
So i received and installed my Bitsetter today. Installed Neilferreri PP in my VCarve Pro. No issue writing the gcode from there.
Although it didn’t list the first tool in my file as the first tool.
I only get 1 prompt to turn off router before tool change.
No pause after tool measurement, heads straight back to cutting. No notice to turn on router, no time to slide my Suckit boot back on. I assume that has to do with CM.
@SDDavinci The update just fixes the first tool numbering issue. It won’t change anything else.
Can you (or anyone) run a test with this PP? I’m away from V-carve and my machine until tonight (EST). Grbl_mm_TC.zip (1.3 KB)
Can you explain what happens when Carbide Motion encounters an M6?
Is the M5 to stop the spindle expected?
Is the M3Sxxx expected after the M6?
Ha. Can you be more specific?
I don’t want a tool change to start my job. I typically load the first tool before I start. I was trying to address the issue of Motion reminding its users to start their spindle.