Is there a way that I can take the config.g file that I have modified and convert it to the .json file so I can use the config tool to generate new homeing gcode?

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.

@Phaedrux I'll try those things. Thanks.

@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.

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.

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

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 have to be missing something... I don't think that the mesh map ever gets used when I am doing my first bed level tests.

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v2 on Thu Jan 03 2019 22:56:02 GMT-0600 (Central Standard Time)
M561                ; clear any bed transform
M98 Pdeployprobe.g  ; deploy mechanical Z probe
G29                 ; probe the bed and enable compensation
M98 Pretractprobe.g ; retract mechanical Z probe
G29 S1              ; added because I read about it in Duet forum https://forum.duet3d.com/topic/4374/bed-mesh-compensation/5

In my config.g

; Z-Probe
M574 Z1 S2                                         ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1                                ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F100 T2000                              ; Set Z probe type to bltouch and the dive height + speeds
G31 P500 X39 Y-47 Z1.20                             ; Set Z probe trigger value, offset and trigger height
M557 X45:405 Y50:370 S20                           ; Define mesh grid for gekotek
;M557 X45:420 Y20:430 S30                           ; Define mesh grid for buildplate
G29 S1                                              ; Load the last bed mesh autocalibration

I put a G29 S1 in both the homez.g and homeall.g. homez.g is below.

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2 on Thu Jan 03 2019 22:56:03 GMT-0600 (Central Standard Time)
G29 S2            ; clear bed map
G91               ; relative positioning
G1 Z5 F6000 S2    ; lift Z relative to current position
G90               ; absolute positioning
G1 X210 Y215 F4000; go to first probe point
G30               ; home Z by probing the bed
G29 S1            ; Load the last bed mesh autocalibration

Is there a way that I can take the config.g file that I have modified and convert it to the .json file so I can use the config tool to generate new homeing gcode?

Thanks. My mistake.

Do you have any plans to implement a firmware solution for XY, XZ, and YZ skew? I'm working on a large format printer and am finding Z axis skew to be a pain. It would be great if there was a feature that would straighten up things in the firmware.