Printer does not use heightmap in print

Hey,

i still have a problem with the abl…

The leveling process works, but while printing the first layer the distance between nozzle and printbed is a mess at some points. Some points are too close, some to far away. I used Octoprint to create a heightmap. It says I’ve a difference of 0.5 mm in my bed.

As I checked luban while printing the first layer I realized, that the Z-Axis isn’t moving. After leveling it should move to compensate the measured distances, right?

I also read an article that the Artisan had the same problem caused by a firmware bug.

Does the Snapmaker 2.0 also has this problem?

It did have this bug at one point, but that was fixed well over a year ago.
You can check if the mesh is active by using the M420V G-code command in the Luban console. To manually turn it on, you can use M420S. If you are doing the bed leveling process via the touchscreen, it should automatically turn on, but I have found that sometimes the machine requires a restart for this to happen.

The Z-axis movement is often virtually imperceptible. That 0.5mm is the difference between the highest and lowest points across the whole bed, so depending on the size of the model, the bed difference can be quite a lot less. For more information on issues with bed leveling, give this forum post a read: Bed Leveling - Revisited & Detailed

1 Like