Mk3s calibration failed after firmware 3.9.3 update
Hi guys,
I have mk3s with P.I.N.D.A. 2, everything is working fine untill upgrade firmware to 3.9.3 . I did not change any HW, only firmware.
I tried calibration wizard and when it comes to calibrate first Z point of 4 total, the carriage is misaligned (pinda is not straight over the circle, but more to the left), and there's error on the display:
Calibration failed!
Check the axes and run again.
What did happen? Firmware bug?
RE: Mk3s calibration failed after firmware 3.9.3 update
i had the same thing happen. did you find a fix?
RE: Mk3s calibration failed after firmware 3.9.3 update
i had the same thing happen. did you find a fix?
Nope. Waiting for a fix from PrusaLabs. This must be firmware bug, because I did not have changed anything else.
My old fw - worked fine:
prusa3d_fw_MK3S_3_9_1_3518.hex
New fw - bug:
prusa3d_fw_MK3S_3_9_3_3556.hex
RE: Mk3s calibration failed after firmware 3.9.3 update
OMG I've just found it!
At the beginning of the whole calibration process (wizard) the printer head finds most left and most upper point. It searches it using crash detection. But the problem is, that the head is trying to find these points only cca 50mm from it's curent (and not known) position. So in case of the head head is not near these points, it will not find them, store bad points, then go all the way down to the bed, and will not be able to find 1st Z calibration point.
So the solution is:
After the firmware flash, just BEFORE starting the caliration process:
1. Turn off the printer or disconnect from mains 230V.
2. Move the printer head up by rotating both threaded rods so it touches the most upper position, then move cca 10mm down.
3. Move the printer head left manually, so it touches most left position, then move cca 10mm right.
After these 3 steps you can start automatic calibration process (wizard).
Also make sure, that "crash points" are not blocked by any obstacle, ie. cable ties or something else.
|It worked for me and I must say this was finally not a bug caused by newest firware.