Mesh level failure
-
Hi,
Today I went to print something. I did a mesh level. For some reason the last probe point did not trigger. Not triggering is not the biggest issue. Instead of dropping the build surface and making the last move it left the nozzle on the table and made the last move. This left a big gouge in my build surface.
Seems the code that does the mesh level needs to be looked at. I would think instead of just stopping at where it thinks Z = 0 was, it should still lower the table like any successful probe before making any more moves.
running Duet WiFi 3.3
-
Sorry to hear that. Can you give us some details about your setup?
When you say it didn't trigger do you mean it crashed the nozzle into the bed?
-
The setup is a TronXY X5SA Pro updated to Duet2 WiFi. Has been running fine for a very long time.
Crashed into bed, I guess that's true. I have it set up so worse it can do is 1/2mm or so. Not sure why the probe didn't trigger ( newest TronXY probe ). The missed trigger is not the biggest issue. What is is the behavior after that. At worst, software should have reported the mesh level failed. It really should have lowered the bed before moving regardless of having missed the trigger or not.
-
Well if it triggered but incorrectly it may not be aware there was a probe failure and may believe it's at an incorrect height.
Probing is a delicate operation because we're trusting the probe to function. If the probe didn't trigger at all you'd get a probe not triggered error.
-
That's the thing, it did not trigger at the last point. It flagged the error, but it should have moved the table away from the nozzle before going to its homing point and not assumed anything about where the nozzle was.
