Eliminate unnecessary tool measuring

Approximately half the time I use CM with my Nomad Pro I am doing repeat operations with the same bit, same setup. But for each of these iterations CM forces another unnecessary bit measurement. For the 24 operations I did this morning this took as much time as the actual machining. It also seems unnecessary wear and tear on the machine.

How about changing the dialog that appears after clicking Start to include an option to bypass tool measuring when the bit is not changed. Please. Of course this assumes there is a Z-zero already in memory.

CM has improved substantially through the years. I remember when you had to click to leave a page before clicking on the menu to enter a new page. I think this would be an improvement as well.

2 Likes

You should be able to remove the M6 tool changes for your G-code and then CM will not measure anything.

But, if there’s an M6 in the file, we need to measure the tool.

1 Like

How would this work the first time I use the nc file and need to measure? Would I then need two files, one for the first time with the M6 and one for subsequent uses without the M6?

Can you just disable the BitSetter on the Nomad?

I don’t think there’s a way to do this outside of disconnecting wires under the machine. Unlike Shapeko, where the bit setter is an add-on, on the Nomad it is standard and built in.

Removing the M6 in a text editor is easy enough to do although curious that CM couldn’t override that on command versus the necessity of manually doing it.

Assuming you’ve previously set your zero, you hit the load new tool button the first time you start up the machine., and let the machine measure the tool once. That’s it. From there you just run the M6-less program and you don’t need to probe again for the remainder of your session.

2 Likes