" Probe was not triggered during probing move" Emergency Stop?
-
Hello,
i am using a D5M+ with a BLTouch.
This is my Routine
Home XY
G30 in the middle of the bed
G32 to adjust 3 leadscrews
G29 to do a meshSometimes, when the moon is not in the right position, the leadscrews have to much difference etc
The probe will not trigger and DWC will say " Probe was not triggered during probing move"Most of the time it will occure when leveling the leadscrews or at mesh bed.
My min "problem" is that even if DWC says " Probe was not triggered during probing move" it will proceed to print the file.
This could result in the nozzle hitting the bed or in other damage....
So my Question is:
- Is there a option to halt the job if the probe is not triggerd?
-
I don't know that answer to your question. I think you can depending on the firmware. What firmware version are you using?
Are you using the file bed.g for leveling the bed and the file mesh.g for creating the height map?
Have you tried increasing the dive height parameter (H) in M558 when leveling the bed?
Frederick
-
thats possible but not the solution of the poblem
even if i increase H and the probe would not deploy because of some junk on the probe pin it would not solve the issue -
@pcr said in " Probe was not triggered during probing move" Emergency Stop?:
thats possible but not the solution of the poblem
even if i increase H and the probe would not deploy because of some junk on the probe pin it would not solve the issueSo what firmware version are you using? That ability to check for an error I believe depends on the firmware version.
Frederick
-
ahh sorry 3.4B5
-
@pcr said in " Probe was not triggered during probing move" Emergency Stop?:
ahh sorry 3.4B5
Scroll down in this documentation to where they have an example of using result and abort during bed leveling.
The example uses a while loop which aborts if the bed leveling fails.
Frederick
