Abort when probing error

[zuoyan]

My 3d printer bed got scratched due to bl touch reporting an error, but the axis moves continued at a start of a print.

Now I added

if result != 0
  abort "..."

after almost every probing / home moves in most macro files. Is there a easy / tidy way to abort when probing or homing errors just happened?

[dc42]

@zuoyan I can't think of an easier way to check for probing errors.

[zuoyan]

@dc42 I think there may be a bug in both 3.5.4 and 3.6.0. After a print, when the bed z is large, and the next print will trigger a probing error:

G32
Error: meta command: Probe was not triggered during probing move
bed.g: G30 P0 failed # I checked and echoed this in the bed.g file

I watched the move and found the bl touch was extended at the start. When Z moved up for some distance, it triggered this error. Now I tried to fix the issue by adding a check before G30:

if move.axes[2].machinePosition > 10
  G1 Z10

While it's not an issue when calling G32 at the start with a large z. But it happens frequently for a second print.