I have a job loaded and on the screen, then ran the job. How do I clear the screen and the job out? Typically I will load the next job. Is there something really obvious that I’m not seeing?
Thanks
I have a job loaded and on the screen, then ran the job. How do I clear the screen and the job out? Typically I will load the next job. Is there something really obvious that I’m not seeing?
Thanks
As far as I am aware, you just load the next job on top of it. When you shut down for the day it clears everything.
Yes that’s correct I shut down the menu and then reload. And the job is gone. Is there a way to do that without those steps?
![]()
Can we make a button out of that no_job_loaded.cnc?
If you load that as a job it doesn’t have any g code in it don’t know how you would make a button for that..
I think you’d have to create an app that uses the centroid API, and tie a button to that app.
Theoretically, you could make a button for the VCP that calls a “no function function” that you wrote if you really wanted to but I have yet to see a down side to leaving the last program loaded until you load another. In Mach, I think it was different where you couldn’t make edits to the previous file if it was already loaded but with centroid I feel like I make edits all the time and then save and reload the job.
I think the main reason is that the Cycle Start button is used to start any loaded Gcode file, but its also used to run through any macro code that is called from anywhere else. And there are so many “hit cycle start” prompts in most of the macros that you get a little tap happy on the cycle start button. If the macro is already done (if the macro writer didn’t do a good job providing a good, visible prompt it can be hard to tell if CNC12 is still hung up in a macro or not) and you hit Cycle Start, you will accidentally start the Gcode that you have loaded. I don’t know how many times I have heard my spindle fire up and then I have to go quickly hit the cycle stop button.
Mach4 start button was only for the loaded gcode and MDI, and all utility code execution was managed by mouse clicks on seperate prompts in popup windows.
You could edit loaded mach4 gcode and re-execute, just like in cnc12.
The downside to leaving it in is that it can accidently be started. I think I started one of these by hitting the space bar on the keyboard. I am just learning, so I am poking around in the ui. I have started one of this completed jobs 3 time. Then there is the paniced how do I stop this thing. I would love to be able to close the file.
This all started because when I ran a job, I didn’t have the dust boot on. My keyboard got sprayed with dust and wood chips it is pretty close to the spoilboard. I was doing a clean up with a vacuum went to the keyboard. I must have hit the right combination of keys because the next thing I knew it was ready to fire up again..