First layer calibration stalls at 2nd x-axis calibration point
Hello everybody,
this is my first post as I've finished building my first prusa mk3 just a few hours ago.
My mk3 passed his selftest and xyz calibrating, but fails at first layer calibration. When bed and nozzle are heated it begins with z-leveling but on the 2nd point it goes up instead of down and hangs there (you hear the motor try to get up even if it has reached the z-axis uper end).
I've uploaded a short video so that you can understand what I mean.
Firmware is updated to the latest one and I've repeated the initial wizard at least three times.
What's the problem here? 😕
Thank you very much!!!
Andreas
Here's the video:
Re: First layer calibration stalls at 2nd x-axis calibration point
Try to reflash.
Sometimes it get screwed up.
---
Gert
Re: First layer calibration stalls at 2nd x-axis calibration point
Reflashed right now, didn't change anything. 😥
Re: First layer calibration stalls at 2nd x-axis calibration point
Here's a better video (with no background noise) where you can hear the sound the mk3 makes when it's reaching the upper z-axis end.
Re: First layer calibration stalls at 2nd x-axis calibration point
Ok, now I'm printing. I chatted with support today (thank you for your time, Peter!), they told me to make a factory reset and if that would not help to downgrade to an older firmware.
I did the following:
1) factory reset with firmware 3.1.3: calibration xyz went fine, but at first layer calibration it stalls on the last levelling point now (before it was the second one, weird thing)
2) flashed 3.1.2, then factory reset and xyz calibration, everything fine. On first layer calibration it stalled on 9th point again. grrr
3) flash 3.2.0-RC1, then factory reset and xyz calibration, and first layer calibration... worked!!!
I already printed the whistle, it was perfect!
But how could that be, if it was a firmware bug why I am the only one to have these problems???
Re: First layer calibration stalls at 2nd x-axis calibration point
Looks to me like some kind of firmware corruption, or maybe a bad einsy board. It seems to be glitching and doing something it shouldn't.