Would anyone be interested in this addition to CM

When a toolpath is started (with the Bitsetter enabled) , the “Tool Change Req’d” window pops up.
Then after changing or not changing tool, it takes a trip to the Bitsetter.
I would find it useful if there was a “SKIP” button in that window. This would eliminate the trip to the Bitsetter and leave the z setting unchanged. It would then go to the “RPM Change” popup (I like this pause, one last check that everything is OK).
I realize the Bitsetter can be enabled and disabled in the setup menu. But the x,y and z are lost when this is toggled.
I frequently run 5 or so toolpaths with same tool, then change tool for the next couple toolpaths.
The SKIP button would give me the best of both worlds.

Thanks
If enough people support the idea maybe they will look at it.
If there is concern that the SKIP would accidentally be triggered, maybe a “Are you sure” popup would be considered. Maybe have the SKIP activated or deactivated in the Setup Menu.

Unfortunately, this can never happen.

We already measure the tool the minimum number of times needed to ensure the user hasn’t changed it without letting Motion know. If we add an option to skip, people will skip, and some of those skips will lead to a crash because the tool will be different from the last time it was measured (because the user changed the tool without thinking).

Those reading might think, “I’d never do that.” But we’ve got LOTS of data to say that even very competent people will click that button and blame the machine.

5 Likes

Reading your post again, it sounds like you’re getting 5 trips to BitSetter for the same tool at the start of each toolpath. If so, you’re probably using 3rd-party CAD/CAM software, and you need to figure out how to eliminate the M6 command at the start of a toolpath if it’s for the same tool. This eliminates the duplicate tool measurements.

3 Likes

This happens using Carbide Create.

If you look at the tool definitions before each M6, they have different geometries, so they likely originated as different tools in the library, even if they share a tool number.

EDIT: To be clearer (and going from memory, so I could be wrong), Create compares the geometry and the tool number to see whether it needs to output an M6.

1 Like

Rob, thank you for the come back. I understand and agree with your reason.
I played around a little.
I plan on starting the toolpath name with a number in the order I need to run it in (1,2 ect).
Then open the file in Notepad and put brackets around the M6 command.
Then rename the file adding in front NM6 (no M6) with a save as.
This will give me the versatility I was looking for.

Thanks again

1 Like

I for one would never use an option like that. I like as any checks and balances as the tool currently offers just to keep me in check/from screwing something up.

1 Like

I just reproduced this with CC 876, using the CC tool #302.

If it’s happening because of different tool geometries, it’s because CC is writing different tool geometries for the same tool.

Tool Prompt Test.c2d (44 KB)