Suppose a person didn’t quite start at the right spot to do an auto probe run. The probing fails. Is there a way to abort the probing?
When the probing fails because no contact was made within a certain distance, the machine locks up with an error. As soon as you clear the error, the probing continues. I have not found a method that allows the operator to abort the probing run in order to reset things. Am I blind or is there no way to say ‘cancel the probing operation’?
Edit: Forgot - gSender 1.4.12
Jens,
I had a probe takes to long error just yesterday. (Am using standard probe block a bit more to probe z). I am using 1.2.2 and had to restart the probing routine.
Somewhere between my bunker and your bunker, something happened.
Are you saying that you were able to abort the probing routine? If so, how?
Not abort, it aborted itself and I had to restart to continue probing.
Let me re-phrase … the probing routine times out and the mill stops with an error. As soon as you clear the error, the probing resumes. It does that a number of times. I was wondering if there was a way to stop the probing so that you don’t have to go through 5 or 6 error messages that need to be cleared. Yes, it eventually thinks it has found the right spot (it hasn’t) and it stops because it thinks it is done. It is very annoying and also somewhat concerning as the probing routine could potentially run into some objects on the table.
I did not attempt to do an emergency stop so I don’t know if that would stop the probing routine. I hate using the emergency stop if I don’t have to.
Anyway, IMHO there should be a way to abort probing on the main screen.
I only came to tell that in older versions, the routine stopped after an error. I agree you should be able to abort.
Anyhooo, can you speed up the proces by estopping your machine, take of the magnet from spindle, reconnect the estop and manualy contact the magnet to speedstep through the proces that needs to be aborted?
Yeah … no … not going to screw around with trying to outsmart gSender …
Makes me wonder why the visualizer has a ‘pause’ and ‘stop’ button yet the built-in gcode routine has no such buttons on the screen. Sloppy …
Edit: Since the probing routine already halts if it can’t find an edge, all that would be required after the error is cleared is to provide a popup with two straight forward options - continue / abort
Having said that, I still think it would be appropriate to have an ‘abort’ button on the screen
2 Likes
@Jens I beleive we noticed this issue and addressed it in the newer 1.5.# versions so that aborting on a probing routine stops the rest of the code from running. Have you tried it past 1.4.12 yet?
No, I am still on 1.4.12 although I am re-evaluating at the moment because of lock-outs where the cursor no longer gets recognized (same issue I had noted before). I am thinking that 1.5.3 might have enough bugs ironed out to justify another go at it.
BTW, did you ever consider giving the user an option of enabling screen (and only the screen) blanking? If not I will have to try and remember what file I modified.
I still have it down in my notes from when you first mentioned it, but since it’s not yet been asked by anyone else we’ve not prioritized working on it, hope that’s ok by you 
1 Like