Shapeoko - Suggested Changes

When in the middle of a project, you decide to press PAUSE the machine stops x and Y and raises Z. Your options are to START (Continue) or STOP. It would be nice that upon pressing stop, the machine exits the program and allows you to select JOG. As it is, STOP tells the machine to HOME. After pressing PAUSE, options could include STOP, or HOME.

If a Bit Setter is enabled - Upon initializing the machine, it wants to check on the height of the bit. If you start a program, it wants to check the height of the bit.
If on initialize you don’t have a bit in the router, It can cause problems it attempts to check the height and there is not a bit there. There is also not STOP or PAUSE button available so you either crash or you scramble to kill power to the brain.
Seems like the first check bit height is not needed.

If you are having any problem where you would like to disable the bit setter, you have to have a bit setter actuation upon initialization before you can get to a screen to disable the bitsetter.

There’s been some recent good discussion on related topics you may want to contribute to:

Connect to the machine, go to the Settings pane, then disable the BitSetter.


Wonder if there is a way (w/o cluttering UI) to display almost like a dashboard icon for active settings. Like lit up icon for BitSetter Enabled, lit up icon for BitRunner enabled, etc. I’m not sure if it helps the root issue, but trying to think of ways to give more visibility that there is a setting (and its state) w/o changing the actual workflow.

1 Like

My point is that since running a new file forces the bitsetter routine, there is no need for the bitsetter routine upon the initialization of the machine. If it did not force the bit setter routine on “startup” then I would have a chance at going to the settings to disable the bitsetter. As it is, you had better be ready to check the height of some bit on startup.


I think it also depends on the program you use for toolpaths and the starting gcode it uses. You may be able to delete the gcode that calls for the tool change quickly before transferring to CM.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.