Printbed uneven - lower in the back, higher in the front
My Bed is slightly lower in the back than in the front. If I run the v2calibration.gcode without any z axis live adjust, the first lines are not squished and not sticking to the print surface, but the last 2 lines are sticking pretty well, and are even squished too much. You can see it in the following video:
https://drive.google.com/file/d/0B01rH3-x6sJXTXk0ckVFQThCVVE/view?usp=sharing
I bought the kit and assembled it. All calibration went fine, and the xyz calibration finished with "all axes are perpendicular. Congratulations!". I even successfully checked all axis with an angle for perpendicularity.
The frog and gears from the SD card printed very good, but larger objects like the legs from the camera tripod from thingiverse http://www.thingiverse.com/thing:1460181 peel off the print surface in the lower part of the print bed (no brim or skirts used).
I also tried the bed level correction feature until the end of parameters (back +50, front -50), but this didn't seem to change anything.
Any ideas, what might causing this effect? Im running out of ideas 🙁
Re: Printbed uneven - lower in the back, higher in the front
You need rear -50 and front +50...
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: Printbed uneven - lower in the back, higher in the front
I would have assumed that mesh bed leveling should take care of that?
Re: Printbed uneven - lower in the back, higher in the front
Sorry, i confused the signing in my post. With rear -50 and front +50 the v2calibration.gcode produces the following result:
+ : too squished
0 : good
- : not sticking
+ + + - - -
-
-
- - - - - - -
-
-
- - - - - - -
-
-
0 0 0 0 0
0
0
0 0 0 0 0
0
0
+ + + + +
The start of the line is a bit thicker than the rest, i guess it is extruding more filament at that point. I also assumed, that mesh bed levelling would work this out, but it didn't manage to do this in my case.