How to do a larger than 3 x 3 matrix level

CalibrationTest.stl (71.4 KB) CalibrationTest_40300071.gcode (129.6 KB)

So I made a quick and dirty 20x20 test square that will only do the bottom layer (0.20 tall) and should run well with standard luban quick print settings (at least it looked good when I loaded it) It should give people an idea which calibration locations need more tweaking. I’m going to run mine later today, hopefully it should help out.

I should state though, I’ve made it for a build area of 280x330 to match the glass I have which is narrower in the X than the build platform, but when I level the nozzle is close to the edge of the glass which is 280mm wide, scale it to 300 wide if you want the test cube to be slightly closer to the proper center (the 20x20 cube will scale as well, but this isn’t a test of the X stepper count)

7 Likes

Thanks for sharing this STL… I have been looking for one exactly like this

I’m having serious bed adhesion issues even with large flat base parts and even other materials. I’ve tried cleaning thoroughly and with IPA… I noticed my bed seemed to tilt away at one side, so I decided to try get everything as flat as I could and go from there.

I got the Matrix from the “Auto-Level” from the console, Data below, but I can’t for the life of me understand how/what to do to get the right values to fill the 2nd matrix in the Google sheet? I tried running the Check Level Hot 7x7 gcode but the nozzle is way above the calibration card at all points.
image
I have had to move and re-fix my level sensor due to a hot end clog but it is secure in place and followed the setup steps for it.

I just can’t see where it says to get that data? Can someone put it in layman’s terms for me?

The values for the second matrix (manual) come from doing a manual adjustment for each grid point and then enter those values from the listing in the console (M420V).

You either set each value with a M421InJnZn.nnn (where n are the numbers to fill in)
or with a M421InJnQ.nn (This one increments the z value by the .nn, so it can be + or -)

What I do is create a macro in Luban that increments all the grid points by some value where I get those values from doing the Check Level gcode file and writing down the amounts I think they need to go up or down (it’s just a guess). Then I put those values in the macro and run it then do another Check Level to see if I’m happy with the results. If so, then I do the M420V and record those values in the second (manual) matrix.

The third matrix just calculates the difference between the two (auto & manual) so you can then create a macro that is used after doing an auto level. You only need to do that if for some reason you need to do another Auto Level (like you switched modules).

In the Google sheets there are links to explain some of the steps used. Some of those just switch to a different tab on the bottom of the sheet. Did you look at the link “Using Check Level”?