Add Cancel/Pause button to ToolChange Popup

As I run multiple toolpaths, I often find that I need to tweak the one that just completed and find that it would be good to have a ‘clean’ exit path–any chance to get a Cancel/Pause button on the toolchange popup where the machine is already stopped (something small in the upper corner to reduce accidental presses)?
I don’t like clicking Pause while it’s actively moving X/Y for fear it may miss a step and offset my Set Zero thus negating my ability to recut the previous toolpath.
Thanks!

I understand your concern about missing steps, but stopping it is not likely to have that effect. many times I’ve had jobs get to a tool change, hit “ok” then immediately click pause and stop in CM to stop the run and be able to tweak something and I’ve had no issues.

4 Likes

Two things that occurred to me reading this.

  1. Would a “rerun toolpaths since last tool change” option be useful? Sometimes the boards I use end up with fuzzies, which can be a pain to sand. I keep thinking I need to just rerun the tool path and see if it cleans it up. (but been too lazy to go to my design computer (not in shop) to pull out the toolpath)
  2. You mentioned smaller buttons to limit accidental presses, I would like bigger buttons with more separation so its easier to press for the things I do want. I am running CM on one of the ~10 inch Fusion5 windows tablets (and I have fat fingers :smiley: ) (actually this one I have been wanting for a while)
    John
2 Likes

The entire point of pause is to safely stop the machine without losing location. Pressing pause is completely safe.

7 Likes

Yes, I can see a benefit to rerunning the last toolpath as well. Personally, I’ve only had a few cases where that would be useful, I tend to almost always need to make changes when rerunning. My CC PC is in the shop, so maybe it’s too easy for me to tweak the runs? :slight_smile:
I’m not an interface designer so will leave that to the experts, am okay with more and bigger buttons but would be good to have some clear separation from the existing ‘OK’ button and all new ones since the Ok will likely be the one used 95% of the time and want to keep it as the obvious and easiest to click option.

I press pause frequently. Most times it’s to adjust the dust boot so it doesn’t interfere with the depth of cut. I’ve never had an issue.

1 Like

My complaint with pause is if I am running bit runner the spindle stops and does not restart when I continue. I am screwed if I don’t remember to unplug bit runner and plug the spindle in hot and manually restart it.

@KWW Are you running a spindle or router? Bitrunner is only used with a router and should turn back on as soon as you click resume.
Bitrunner is not compatible with a spindle since the VFD controls the spindle.

I am running the router. When I pause, the router stops, but does not start when I resume. It’s as if the bit runner doesn’t see the “set spindle speed” line of code so doesn’t close the power switch. If while paused I plug the router into a hot receptacle it runs. At the next tool change I plug the router back into the bit runner and all is normal.

I dont use the bitrunner but a quick search brought this video up. skip to 2:09 to see the bitrunner test.
https://www.youtube.com/watch?v=tnWFB9iW8Sg&t=103s

Perhaps you can get someone to try a test run with a router. The video test was a spindle.
I’m just trying to help find bugs. Y’all have a superb profane customer support to match.

It’s the same test with a router

I agree that it is the same test with the router. But they both test the router start / stop function by sending an MDI command.
What I am suggesting be tested is whether the start command is sent in a trial running a job and pausing between tool changes then resuming to see if bitrunner sends a start command to the controller.
I had ankle surgery today so I have too much time to think about it and it will be a “bit before I’m running” :smirk:
Thanks
KWW

The test just tells you if the bitrunner turns on and off using the MDI commands which takes out the possibility of a hardware issue. Like I mentioned before I don’t use bitrunner so maybe someone here with bitrunner experience or an email to support with your issue can clear it up.

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