During a particularly long carve, Carbide Motion lost connection to the machine. I seem to recall that some competitors claim that their software is capable of restarting where it left off. Is this possible with Carbide Motion?
Thanks,
Roy
During a particularly long carve, Carbide Motion lost connection to the machine. I seem to recall that some competitors claim that their software is capable of restarting where it left off. Is this possible with Carbide Motion?
Thanks,
Roy
Yes, it was added in a recent update:
Thanks, Will! Iâm on the latest build 667, and I donât see that option. Do I have to roll back to the previous version?
No, it should be in that version.
You should see it after selecting the file, shows up below Start Pause Stop buttons
It did not show up for me.
I think you need to know the line number to start from. As a job is running it is flashing the line of gcode the machine is executing.
On really long carves I periodically write down the line number and percent of the job that has run so far.
Thanks, Guy! Iâll start doing that. Regardless though, the restart option never appeared for me.
Seems kind of cumbersome to have to write the number down. I would think that the last line number executed successfully would be something that the software could EASILY persist - so that it would be available on restart. The software could clear that persistent value upon successful completion of the job.
When you do the restart, CM could fill the line number with the line number that it âremembersâ and give the operator a choice to use it, or substitute another number.
Would that be possible?
I thought the same thing!
I donât think the machine knows what the last line âsuccessfullyâ executed is. Partly because it is pushing the GRBL to the controller and partly because itâs all successful from a CM perspective even if your bit broke or got dragged across the wrong spot on the material.
Maybe having a âcheckpointâ button on CM that you could hit periodically would be handy.
I donât know about everyone else, but I never leave my machine entirely unattendedâŚhowever, I will do other things in the shop while keeping my ears tuned to the machine. having to write down a number - or even push a button is a PITA. Perhaps a periodic checkpoint without a button? Every âbuffers worthâ of GCode?
I get it but it still wonât necessarily be the place you need to restart. The buffer could have sent 20 times before you get over there to hit the stop button.
Maybe using a gcode preview tool like @Tod1d has linked to before would be a way to visually identify the right spot and get the line number from that.
Sometimes you may want to restart from a certain point even if there were no issues like to clean up fuzzies.
Without the closed loop stepper motors I donât think there is a foolproof answer.
OKâŚnow weâre talking! ![]()
Correct. Itâs âdrip-feedingâ the machine a buffer full of data at a time. However, it could remember the line numbers from the last buffer sent, and get you pretty close. If anything, youâre going to want to rewind a bit anyways.
That being said, you can pretty easily get it close. Look at the replay of the simulation, look at where the job stopped. Measure the cut depth for a Z value to search for. Narrow down which toolpath if more than one, then search for those values.
I use ncviewer to find a good point to restart.
Do not pick a point with an arc, it will reject it.