How do you get the software to continue where it left off after it encounters an error? I was 2 1/2 hours into an adaptive clearing pass when an operation error pops up (wish I would have calmly took a photo). The program stops and the only option I see is "Rub Program"...HOPING it would just start back from where it was...I pressed it. Now it has started back over from the beginning. Is there a way to make the program restart from where it is/was and is there a way to make it fast forward to where it was?
Short version: You don't. Something happened, that caused Grbl to enter an alarm mode. The reason for the alarm was serious enough that Grbl went into alarm mode, so its safe to assume position was lost, or a crash occured, serial corruption, or a limit or EMI, etc You cannot just start it mid job as Gcode is a conversation, there are commands leading up to it. You can hand-edit the gcode to get to the right spot, add the right modals, and all the other required earlier bits of conversation, but its really hard (depending on your grasp of gcode) You can air-cut at 200% speed using the feedrate override slider or You can learn how to re-CAM but exclude work already done, to avoid having to air cut sections that is already done But over and above all that, the right fix is to make your machine reliable: See docs:blackbox:faq-emi [OpenBuilds Documentation] - assuming here (Based on your other thread Probe question and dust boot issues - I know you have a dust boot - so my first instinct for a error middle of the job is: Is that dust hose Grounded properly) Catch the Alarm next time - if you panic clicked it away, the Serial Log tab holds it too. That will give us clues to the real cause of the alarm so you can address it. Careful, if position was lost, or offsets was reset clicking RUN is a disaster waiting to happen. It errored for a reason - position could be lost. At the very least re-home and check that Work Zero is still in the correct place before running a file after an alarm -- also the reason one cannot "automatically" just resume - the operator has to get involved to see what happened, address it, and then plan the correct course to resume, hand editing gcode as needed, etc - complicated
I was hoping to have the static situation avoided by not having the hose anywhere near the control wiring. While it is not on the jib arm, it is supported up and above the system. Guess I will have to look at grounding it.... Luckily, this project was just pine. So, I am not out much money (material wise). I'll glue up another and have another go at it with 200% air routing before cutting the next piece
