I have to be missing something: Mesh bed leveling w/ BL Touch
-
I am on the most recent firmware also.
@fcwilt said in I have to be missing something: Mesh bed leveling w/ BL Touch:
In your homeZ.g file, before executing G30, you are positioning X,Y to 210,215 - where do those values come from?
This is the center of my bed. I like to home z in the center.
@fcwilt said in I have to be missing something: Mesh bed leveling w/ BL Touch:
I put everything related to my Z probe into a macro file configprobe.g which allows me to make changes, as needed, without having to reboot the firmware.
Would you mind sharing that macro?
-
I am also seeing where it is being saved in the G-Code Console. So I guess my question now is how do I get it to load that map without running the entire probe cycle.
G32
323 points probed, mean error -0.019, deviation 0.035
Height map saved to file heightmap.csv -
M375 or G29 S1
-
@xHOBOPHOBIAx said in I have to be missing something: Mesh bed leveling w/ BL Touch:
I am also seeing where it is being saved in the G-Code Console. So I guess my question now is how do I get it to load that map without running the entire probe cycle.
G32
323 points probed, mean error -0.019, deviation 0.035
Height map saved to file heightmap.csvThe height map should be loaded at the point but perhaps invoking bed.g with G32 is doing something odd.
As I mentioned, I think, I invoke mesh bed probing using a macro which basically does:
- M98 P"configprobe.g"
- G28 which invokes homeALL.g which in turn simply invokes: homeZ1.g homeX.g homeY.g homeZ2.g
- G29 which does the "mesh" probing
homeZ1.g does the "normal" homing of Z.
homeZ2.g does the setting of the Z=0 datum using G30configprobe.g does basically what you are doing in config.g to setup the Z-probe.
I'm out of town or I would just post the macro for you to examine.
Frederick
-
So with that information it looks like the map is being created and loaded.
Does anyone know how the z height is calculated if the print head goes to an area where the probe was not able to hit? That may be the issue.
-
@xHOBOPHOBIAx said in I have to be missing something: Mesh bed leveling w/ BL Touch:
... That may be the issue.
I don't think you've said what you thought was the issue yet, and what sort of machine you are using?
-
@DocTrucker said in I have to be missing something: Mesh bed leveling w/ BL Touch:
@xHOBOPHOBIAx said in I have to be missing something: Mesh bed leveling w/ BL Touch:
... That may be the issue.
I don't think you've said what you thought was the issue yet, and what sort of machine you are using?
Large coreXY printer. I am trying to print a small square at each corner and in the center to test bed level and mesh compensation. I home z with my BL Touch. I run the bed probing through the web interface. The front squares and the square in the middle of the bed have the same first layer where the two at the back of the bed are printing with the nozzle further from the bed.
I tried a large square just in the center of the machine and it's first layer looks uniform. I am thinking the back two squares in my first test were printing over an area of the bed that wasn't probed because of my BL Touch offset and that could be the cause of the issue.
-
@xHOBOPHOBIAx said in I have to be missing something: Mesh bed leveling w/ BL Touch:
Does anyone know how the z height is calculated if the print head goes to an area where the probe was not able to hit?
Those areas will be interpolated.
M98 Pdeployprobe.g ; deploy mechanical Z probe
You should remove all the manual deploy and retract commands. The firmware will take care of deployment state.
G31 P500
Reduce your P500 to P25 to increase trigger sensitivity.
G29 S1
Best not to load the heightmap in config.g since you havent homed your printer yet. You should either move the G29 S1 to the end of your homeall.g or to the slicer start gcode after the Z axis has been homed.
-
@Phaedrux I'll try those things. Thanks.
-
I will keep testing, but I thing it is going like I am expecting now. I can feel the lead screws making small movements while printing so something is happening.