How is the “Height Map” Used?
-
And to clarify, yes it appears to be working. I can definitely generate a height map. Are there other things I should be looking for to confirm its working?
Other than obviously not crashing into the bed.
-
The best way to test is to print a first layer test print twice. Once with G29 in the start gcode, and again with G29 S0 in the start gcode to disable it.
Something like this file works well.
bedlevel_nozzle_0.4_200x200-0.3-0.8.stl
I think the missing piece of the puzzle in your case was not using the probe to home z.
-
@Phaedrux thank you so much. You guys really know your stuff. I'll go ahead and work on this right now.
How can I save/export all of my settings as a JSON once I have it dialed in?
-
@tmeryhew said in How is the “Height Map” Used?:
How can I save/export all of my settings as a JSON once I have it dialed in?
You can back up the .g files in the /sys folder of your SD card.
From DWC, go to the system tab, there is a check box above the list of files, click it to select all the files, then right click on the file list area and select "Download as zip" to save all the files there as a zip file on your computer.
Then if you ever needed to restore the configuration to that point you could upload that zip file again to the system tab. Or extract it and upload a particular file you want.
-
I've gone in and made the changes you describe. I am running the file you sent as we speak. I sent M122 and this was the result.
Should my "comp offset" be 0.000? Does this mean anything?
-
No the important thing is that it indicates the mesh is loaded.
It should be moving the Z axis to compensate for the surface of the bed now.
-
@Phaedrux so when I run the test print the second time with G29 S0, should it still probe the bed? Because that is what it's doing right now.
-
@tmeryhew said in How is the “Height Map” Used?:
@Phaedrux so when I run the test print the second time with G29 S0, should it still probe the bed? Because that is what it's doing right now.
Yes G29 S0 probes the bed.
G29 by itself first looks for a file mesh.g - if found the file is executed.
If the file is not found then G29 behaves just like G29 S0 and probes the bed creating the height map.
Some folks create a height map with every print.
Others, like me, have a separate macro for creating the height map when desired.
That height map is then simply loaded using G29 S1 at the start of every print.
Your printer - your choice.
Frederick
-
Sorry I should have said G29 S2 to clear the heightmap.
https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_G29_Mesh_bed_probe
-
This first one is with the start code set to G29 S2.
This second picture is when I had it set to G29.
-
And when it had G29 did it actually probe the bed surface?
-
@Phaedrux Yes it did. It just seems like it performed worse with the mesh compensation on...
-
Ok, let's work on improving your BLtouch performance.
M558 P9 C"^zprobe.in" H5 F240 T12000Let's try changing that to this
M558 P9 C"^zprobe.in" H4 F120 T6000 R0.5 A10It may take slightly longer to perform the G29 but the results should be more accurate.
You should also go through this again and remeasure your trigger height and XY offsets for G31.
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
