Prusa-firmware-buddy: [BUG]First Mesh bed levelling attempt fails everytime

[jsilva-iii]

Printer type - [MINI]

Printer firmware version- 4.0.5, .

Original or Custom firmware - Original

Optional upgrades - Filament Runout Sensor

Printing from :**USB drive

After powering on printer, load filament, selecting print, printer cools temp for mesh bed leveling, it homes, to the front right, clicks four times against the right hand end ( as viewed from front), moves bed forward, repeats, moves bed forward, print head then probes the remaining eight points properly. I usually cxl the print and restart after which the mesh bed levelling routine works as expected, i.e. homes, then probes all 16 points while moving around the bed

How to duplicate:
Turn on printer and attempt to print, first attempt at mesh bed leveling will do the same.

So far I have printed different 6 items all of them behave in exactly the same way.

Video only has the second row the first four points the head is completely against the right hand side, the leveling for the first four points is done in the same spot

I can email the video file as it's too large to upload

[JohnnyDeer]

Hi @jsilva-iii , thank you for reporting. Please send video to [email protected] , it will helps a lot :)

[jsilva-iii]

Johnny

Hi, this happens almost all the time, after resetting it prints perfectly.

https://photos.app.goo.gl/dvuZxLrutRPe1g3L7

Thanks
Jorge

On Tue., Jun. 16, 2020, 1:48 a.m. JohnnyDeer, [e-mail]
wrote:

Hi @jsilva-iii https://github.com/jsilva-iii , thank you for reporting.
Please send video to [email protected] , it will helps a lot
:)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/561#issuecomment-644544914,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQ4GIBDSEQ25YUM47OMRQDRW4BRFANCNFSM4N24D56Q
.

[monsterguy]

I have the same issue with bed levelling malfunctioning on the first attempt after powering on.
It heats to 170/60 and then does the following -
https://photos.app.goo.gl/CP9npE8aaZeGhF2h8
The video ends with me cancelling the print as it starts to heat towards print temperature.

All subsequent prints until power off operate as expected.

(Version info - https://photos.app.goo.gl/J9rQVZP5TvKrfF756)

[jsilva-iii]

Hi - just a correction - I don't reset the printer, I cancel the print and restart it.

[4nthonylin]

Just wanted to chime in, I also see this issue and a reset always fixes it as well.

[posttenebre]

I have the same issue. It does not occur when the print head is more distal from the Z screw side. So if you change the end gcode for the printer to position the head at X2 it will not have issues with mesh bed leveling on the next start up.

G1 X2 Y180 F4200 ; park print head (previous x178)

It has not been an issue since firmware 4.1.0-final, but I figure I would put my hacked solution into the comments here in case someone else needs a quick solution.

[JohnnyDeer]

Hi, is this still a issue?

[jsilva-iii]

Yes, I just move the head to the middle of the arm and I don't have that
problem

On Mon., Nov. 9, 2020, 5:35 a.m. JohnnyDeer, [e-mail]
wrote:

Hi, is this still a issue?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/561#issuecomment-723925999,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQ4GIHMXA6KENH6KMVW5TLSO7AX7ANCNFSM4N24D56Q
.

[monsterguy]

Yes, it still happens every time unless I use one of the methods to avoid it.
Firmware and slicer updates have not changed or fixed the issue.

[jsilva-iii]

Hi - I have resolved this issue. I contacted support, they suggested I do a factory reset and see the output. I did and the X axis failed, everything else worked. They then got me to send videos of the MBL failing which I did, they suggested I undo my belt tension and see if I still had the issue, I undid the belt so is was pretty much close to lose and still it failed. They suggested the board was faulty and asked me to post it back and they would send the replacement. Problem solved, passed self test and MBL works as expected.