G28, G29, G31, & G32 Relationship w/ Probe

[elli]

Hi Duet folks! I am trying to understand the interactions between the above gcode commands with my EZABL on my Taz Workhorse (dual z cartesian printer).

This is my current process for calibrating my printer:

1. G28
2. G32
3. Move to center of bed.
4. Set the z offset through this process here.
5. Calibrate the EZABL from TH3d's instructions.
6. Update G31 in config.g, restart duet
7. G28, G32
8. Heat bed to target temp.
9. Turn off bed
10. G29
11. Start print, which performs 1. M561, 2. G28, 3. g32, 4. G29 s1.

What I find happens is this:

1. My heightmap shows the bed to be below "0" at the XY position that I performed the G30 z calibration, which seems strange.
2. The nozzle is far too close to the bed and I have to perform babystepping to achieve the correct height (often times around half a mm), and not in a way that seems to be consistent with other measurements.
3. Even with g29 s1 and the duet control reporting mesh in use, I can't see any visual indication that the z axis motors are making the small necessary corrections, and I do see (very small) inconsistencies in the first layer.
4. Once a print is finished, I update the config.g with the babystep alterations, yet the next print seems to have it's own first layer oddities that need babystepping.

I have a number of questions about how these commands interact with each other:

1. When calibrating the Z offset for a probe, does the current G31 z offset need to be set to zero first?
2. After changing the z value of G31 in the config, do I need to re-run g29 and get a new heightmap?
3. After each g28, my x gantry becomes crooked, and a G32 is necessary. However, if I run a macro to raise and lower the gantry 150 mm 10 times, a g32 reports the gantry is level (within .002 mm). Is there something wrong with my homeall?
4. Should I be re-establishing my z0 through after g32?
5. Is there a way to verify that G29 movements are occurring outside of just eyeballing my motors?
6. Is my process for establishing my z offset/bed level/print start problematic?
7. Shouldn't my G29 heightmap have a z value of 0 at the point that I established my z-offset?

Sorry for the long post, all of my files should be below.

config.g

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Sat Jun 13 2020 22:43:12 GMT-0500 (Central Daylight Time)

; General preferences
G90                                                    ; send absolute coordinates...
M83                                                    ; ...but relative extruder moves
M550 P"Gertie the Workhorse"                                  ; set printer name

; Network
M552 S1                                                ; enable network
M586 P0 S1                                             ; enable HTTP
M586 P1 S0                                             ; disable FTP
M586 P2 S0                                             ; disable Telnet

; Drives
M569 P0 S0                                             ; physical drive X goes backwards
M569 P1 S0                                             ; physical drive Y goes backwards
M569 P2 S1                                             ; physical drive Z1 goes forwards
M569 P3 S0                                             ; physical drive E0 goes backwards 
M569 P4 S0                                             ; physical drive Z2 goes backwards

; Dual Z Axis
M584 X0 Y1 Z2:4 E3                                     ; two Z motors connected to driver outputs Z and E1
M671 X-141:366.5 Y48:48 S4                             ; leadscrews at left (connected to Z) and right (connected to E1) of X axis

; Motor settings
M350 X32 Y32 Z32 E32 I0                            	   ; configure microstepping without interpolation
M92 X200.00 Y200.00 Z1000.00 E619                    ; set steps per mm
M566 X480.00 Y480.00 Z300.00 E12000                    ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z900.00 E1500.00             ; set maximum speeds (mm/min)
M201 X4500.00 Y4500.00 Z500.00 E10000.00                ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z800 E1000 I30                        ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                                ; Set idle timeout

; Axis Limits
M208 X-50 Y-20 Z-2 S1                                  ; set axis minima
M208 X300 Y315 Z300 S0                                 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"                                    ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                                    ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2                                             ; configure Z-probe endstop for low end on Z

; EZABL
M558 P5 C"!zprobe.in" H5 S.07 A5 F900 T12000            ;connected to Z probe IN pin.
														; Height - 5mm, probe each point 3 times, Feed rate 60, travel rate 6000
G31 P25 X-21 Y-43 Z0.926									; set Z probe trigger value, offset and trigger height
                                                        ; For offset, + is towards bed, - is away from bed.
M557 X10:250 Y10:240 P15:15                                 ; define mesh grid - also defines printable area

; Heaters
M308 S11 P"mcu-temp" Y"mcu-temp" A"Duet Board"         ; Configure MCU sensor
M308 S0 P"bedtemp" Y"thermistor" T100000 B3974         ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                                  ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00                                       ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                ; map heated bed to heater 0
M143 H0 S120                                           ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor"  T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp Semitec 104NT-4-R025H42G
M950 H1 C"e0heat" T1                                   ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                                       ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S300                                           ; Set temperature limit for extruder to 300C
M141 H2                                                ; Assign chamber heater to heater 2
M307 H2 B1                                             ; chamber heater operates in bang-bang mode
M308 S2 P"e1temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2                                   ; create chamber heater output on e0heat and map it to sensor 2
M143 H2 S70                                            ; Set temperature limit for chamber to 60C


; Fans
M950 F0 C"fan0" Q500                                   ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                         ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                                   ; create fan 1 on pin fan1 and set its frequency
M106 P1 S0 H11 T38                                     ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 S"Extruder" D0 H1 F0                           ; define tool 0
G10 P0 X0 Y0 Z0                                        ; set tool 0 axis offsets
G10 P0 R0 S0                                           ; set initial tool 0 active and standby temperatures to 0C



; Custom settings are not defined

; Miscellaneous

M575 P1 B57600 S1


M501                                                   ; load saved parameters from non-volatile memory
T0                                                     ; select first tool

config-override.g

; config-override.g file generated in response to M500 at 2021-07-15 11:57
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 R0.347 C415.820:415.820 D3.10 S1.00 V23.6 B0 I0
M307 H1 R1.733 C383.952:251.337 D6.50 S1.00 V24.0 B0 I0

bed.g

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Thu Jun 11 2020 21:09:00 GMT-0500 (Central Daylight Time)
M561									 ; turns off mesh compensation

G1 Z5 

G30 P0 X10 Y130 Z-99999
G30 P1 X270 Y130 Z-99999 S2

homeall.g

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Sat Jun 13 2020 22:43:12 GMT-0500 (Central Daylight Time)

G91                                 ; relative positioning
G1 H2 Z15 F6000                     ; lift Z relative to current position
G1 H1 X-345 Y-340 F6000             ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000                   ; go back a few mm
G1 H1 X-345 Y-340 F6000             ; move slowly to X and Y axis endstops once more (second pass)
G90                                 ; absolute positioning
G1 X161 Y183   F6000                  ; go to first bed probe point and home Z
M558 F900  				            ; Home EZABL Fast 15mm/s
G30                    				; home Z by probing the bed
M558 F450              				; Home EZABL Slow 7.5mm/s
G30                    				; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91                                ; relative positioning
;G1 Z5 F100                         ; lift Z relative to current position
;G90                                ; absolute positioning

Print Start Gcode

;This G-Code has been generated specifically for the LulzBot TAZ Workhorse with HE 0.5mm Tool Head
G28
G32
G29 S1
M104 R{first_layer_temperature[0]-60}
M190 S{first_layer_bed_temperature[0]} ; bed heating up
G1 X20 Y0 Z3 F3000
M109 R{first_layer_temperature[0]}
G1 E1 F75 ; prime tiny bit of filament into the nozzle
G1 X20 Z0.5 E5 F500 ; start purge line
G1 X50 E15 Z0.5 F500 ; finish purge line

My heightmap:

RepRapFirmware height map file v2 generated at 2021-08-19 14:14, min error -0.432, max error -0.019, mean -0.203, deviation 0.093
axis0,axis1,min0,max0,min1,max1,radius,spacing0,spacing1,num0,num1
X,Y,10.00,250.00,10.00,240.00,-1.00,17.14,16.43,15,15
 -0.304, -0.364, -0.372, -0.387, -0.402, -0.402, -0.409, -0.432, -0.432, -0.413, -0.402, -0.398, -0.387, -0.349, -0.312
 -0.278, -0.308, -0.304, -0.319, -0.334, -0.342, -0.357, -0.387, -0.391, -0.372, -0.372, -0.368, -0.349, -0.319, -0.286
 -0.233, -0.286, -0.278, -0.278, -0.282, -0.286, -0.312, -0.342, -0.345, -0.319, -0.308, -0.312, -0.304, -0.282, -0.252
 -0.192, -0.222, -0.199, -0.188, -0.184, -0.192, -0.237, -0.278, -0.289, -0.274, -0.267, -0.259, -0.252, -0.244, -0.211
 -0.143, -0.192, -0.173, -0.151, -0.136, -0.151, -0.196, -0.229, -0.244, -0.229, -0.218, -0.207, -0.199, -0.203, -0.177
 -0.102, -0.128, -0.102, -0.094, -0.094, -0.109, -0.154, -0.196, -0.207, -0.199, -0.188, -0.184, -0.177, -0.184, -0.139
 -0.064, -0.113, -0.090, -0.090, -0.098, -0.113, -0.147, -0.181, -0.184, -0.162, -0.154, -0.154, -0.162, -0.162, -0.132
 -0.038, -0.061, -0.046, -0.057, -0.079, -0.098, -0.132, -0.166, -0.169, -0.147, -0.139, -0.147, -0.151, -0.154, -0.117
 -0.019, -0.064, -0.061, -0.083, -0.102, -0.117, -0.143, -0.169, -0.166, -0.139, -0.124, -0.132, -0.154, -0.139, -0.109
 -0.027, -0.057, -0.053, -0.079, -0.102, -0.117, -0.139, -0.169, -0.173, -0.139, -0.121, -0.132, -0.158, -0.147, -0.102
 -0.057, -0.105, -0.113, -0.128, -0.143, -0.147, -0.166, -0.181, -0.169, -0.128, -0.113, -0.136, -0.162, -0.147, -0.102
 -0.079, -0.117, -0.124, -0.147, -0.158, -0.162, -0.184, -0.199, -0.188, -0.162, -0.154, -0.169, -0.169, -0.154, -0.098
 -0.121, -0.188, -0.196, -0.211, -0.218, -0.214, -0.229, -0.244, -0.237, -0.207, -0.192, -0.192, -0.169, -0.147, -0.094
 -0.158, -0.199, -0.207, -0.225, -0.241, -0.248, -0.274, -0.297, -0.297, -0.274, -0.259, -0.244, -0.207, -0.177, -0.117
 -0.211, -0.278, -0.290, -0.305, -0.312, -0.312, -0.331, -0.349, -0.342, -0.319, -0.297, -0.267, -0.237, -0.199, -0.147

and a screenshot:

[fcwilt]

@elli said in G28, G29, G31, & G32 Relationship w/ Probe:

You normally would not be setting baby-stepping in your config.g file, it's something you do while watching the first layer printing.

1. When calibrating the Z offset for a probe, does the current G31 z offset need to be set to zero first?

No

2. After changing the z value of G31 in the config, do I need to re-run g29 and get a new heightmap?

When creating a heightmap you always need to first set the Z=0 Datum using a single G30 at a fixed XY location. It can be one of the probe points used when creating your height map or it can be the center of the bed. Regardless of what point you use it must always be the same point. Changing the Z Trigger Height in G31 requires setting the Z=0 Datum again and thus requires creating a new height map

3. After each g28, my x gantry becomes crooked, and a G32 is necessary. However, if I run a macro to raise and lower the gantry 150 mm 10 times, a g32 reports the gantry is level (within .002 mm). Is there something wrong with my homeall?

I've never found it necessary to change speed when using a Z probe. To get greater accuracy you can adjust the S parameter in your M558 or you can force averaging of a fixed number of probes by setting A to the number of probes and S to -1.

4. Should I be re-establishing my z0 through after g32?

Yes. You need to set the Z=0 Datum after using G32 to level the bed or before using G29 to create/load your height map.

5. Is there a way to verify that G29 movements are occurring outside of just eyeballing my motors?

Yes but G29 has been verified by others as working correctly.

6. Is my process for establishing my z offset/bed level/print start problematic?

7. Shouldn't my G29 heightmap have a z value of 0 at the point that I established my z-offset?

Don't know what you mean by "established by z-offset".

---

You may want to use this approach to leveling your bed with G32 - this is my code cut down to the essentials:

M671 X-180:0:180 Y-65:130:-65 S3 ; positions of ball studs
  
; --- level bed leveling ---

while true
  ; run leveling pass

  ; --- probe near ball studs ---
  
  G30 P0 X-145 Y-65 Z-99999    ; probe near ball stud #1
  G30 P1 X0    Y100 Z-99999    ; probe near ball stud #2
  G30 P2 X145  Y-65 Z-99999 S3 ; probe near ball stud #3

  ; check results - exit loop if results are good

  if move.calibration.initial.deviation < 0.02
    break

  ; check pass limit - abort if pass limit reached

  if iterations = 5
    M291 P"Bed Leveling Aborted" R"Pass Limit Reached"
    abort "Bed Leveling Aborted - Pass Limit Reached"

; --- finish up ---

; --- set Z=0 datum which can be affected by leveling ---

M98 P"center_probe.g" ; position for probing
G30                   ; do single probe which sets Z to trigger height of Z probe

[elli]

@fcwilt Thanks for the response. Going to play with this and may have further questions.

[elli]

@fcwilt I've made some small changes to my approach.

my bed.g now looks like this:

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Thu Jun 11 2020 21:09:00 GMT-0500 (Central Daylight Time)
M561									 ; turns off mesh compensation

G1 Z5 

G30 P0 X10 Y130 Z-99999
G30 P1 X270 Y130 Z-99999 S2

G1 X151 Y168
G30

and my heightmap looks better. However, I'm still seeing issues in which all of my prints start with the nozzle scraping the bed. I would post more reference code in here, but frankly at this point I don't know where I would look to understand why this is happening.

[Phaedrux]

@elli said in G28, G29, G31, & G32 Relationship w/ Probe:

S.07

S0.07 is actually less strict a tolerance than the default. I suggest you remove that part entirely. If you're going to use the A value to force it to probe twice, you should at least let it get some accuracy out of it instead of accepting a looser range of repeatability.

If you notice that you need to baby step up by the same amount each time after fixing that S value, then you can simply modify your G31 Z value to take that amount into effect. If Z0.926 is too close to the bed, reduce it by the amount you are baby stepping.

Also a dive speed of 900 may be too fast to get a good probe resolution. Try M558 F300 instead and see if you get better accuracy.

[elli]

@phaedrux Made those changes, but still seeing the nozzle entirely too close to the bed. After the above steps, the number I'm getting from my g30 s-1 is 1.631, which is what I'm putting as my g31 z value. With this, i have to baby step up about .46 mm because the nozzle is scraping the bed so hard. I'm just not understanding why my z probe calibration is deviating from the measured value by 25%. This feels like I'm doing something fundamentally wrong in my calibration, rather than need to make some minor changes.

[Nurgelrot]

@elli I'm having the same issue the other way, I manually set my z offset and manually level my bed and I can print fine. But if I do a G29 and generate a height map I get a warning that the offset (that I just printed with correctly manually) is too large. The map that it creates is level. BUT all points are floating above zero .02. to.15 depending on the mood it seems. And if I apply the height map of course it prints too high.

I'm at a total loss I've been printing with this config for while now don't know what I did to mess up G29. Feeling really dumb, whatever is causing it I cant see it--- Following and going over my settings as well.

[Phaedrux]

Have you re-created the heightmap after making those changes?
Are you clearing your heightmap before doing your G30 S-1 test?

[fcwilt]

@elli said in G28, G29, G31, & G32 Relationship w/ Probe:

@phaedrux Made those changes, but still seeing the nozzle entirely too close to the bed. After the above steps, the number I'm getting from my g30 s-1 is 1.631, which is what I'm putting as my g31 z value. With this, i have to baby step up about .46 mm because the nozzle is scraping the bed so hard. I'm just not understanding why my z probe calibration is deviating from the measured value by 25%. This feels like I'm doing something fundamentally wrong in my calibration, rather than need to make some minor changes.

To get accurate results from G30 S-1 you have to already have your logical Z position matching the actual Z position.

If that match is off G30 S-1 will return an incorrect value.

You can always resort to trial and error.

• set the Z=0 Datum at your standard XY point
• after it has finished probing the reported Z position should be the sum of the M558 H parameter and the G31 Z parameter
• move the nozzle to that XY point
• with something like my 1mm thickness gauge execute a G1 Zn at some slow speed where n is the thickness of your object
• check the gap between the nozzle and the bed
• if it is too large increase the G31 Z parameter by the difference - if it is too small decrease the parameter by the difference.

Repeat until you find the correct value for the Z parameter

[elli]

@fcwilt Sure, I can resort to trial and error, but I'm not understanding why my process is not resulting in a meaningful outcome. Rather than brute forcing this, I'd like to understand what I'm doing wrong so that I may correct it and the machine operates as expected.

[fcwilt]

@elli said in G28, G29, G31, & G32 Relationship w/ Probe:

@fcwilt Sure, I can resort to trial and error, but I'm not understanding why my process is not resulting in a meaningful outcome. Rather than brute forcing this, I'd like to understand what I'm doing wrong so that I may correct it and the machine operates as expected.

Well the normal approach relies on there being a fixed physical relationship in the Z axis of the Z probe and tool nozzle which is complicated a bit with multiple tools.

Thus I think it is best to set the Z offset of tool 0 to 0 to keep things simple and use tool 0 for determining the Z probe Z Trigger Height setting needed in G31.

The Z offset of all other tools can be set in relation to tool 0.

---

You set the logical Z position (what the firmware "thinks" the Z position is) to match the actual Z position by jogging the nozzle down until it is just touching the bed or some thickness gauge type object and set the logical Z position using G92 Zn where n is the thickness of the object or 0 if you didn't use one.

Once the logical position matches the physical position then you can use G30 S-1 to determine the Z Trigger Height setting you would use in G31.

---

Once you have set the G31 Z Trigger Height setting you can then set the Z=0 Datum using G30 and then verify that Z=0 actually has the nozzle just touching the bed.

It is common for folks to have the G31 command in config.g which means config.g needs to be executed to apply the new setting.

I use a different approach in that I have a file called config_probe.g which contains the M558 and G31 commands needed to configure the Z probe. I invoke that file whenever I want to insure the Z probe is using the most recent settings. Using M98 P"config_probe.g" in config.g insures the Z probe is setup on printer boot/reboot.

For testing I have a DWC Macro which contains M98 P"config_probe.g" so I can quickly and easily apply any new settings entered into the config_probe.g file.

Frederick

[JoergS5]

@elli maybe the temperature of the nozzle is the reason, is it cold at calibration? It will expand by about 0.2 mm at 200 °C increase if the hotend is 50 mm long. ( https://forum.duet3d.com/topic/8779/z-offset-depending-on-hotend-temp-setting/4 )

[elli]

@joergs5 This has definitely helped, although I'm still seeing some issues.

@fcwilt @Phaedrux is there anything that can be gleaned from the fact that my mesh is a "saddle" shape? I've tinkered with my z probe trigger height and the conditions under which I establish my Z=0 Datum, but I've also noticed that there is a fair deviation in trigger height at different points on the bed, roughly .2mm of deviation. When reviewing this document it states that the z trigger height should not very significantly in different XY positions. I have no way of altering the surface of the bed mechanically.

Regarding the z trigger height variations, I'm confident that my z probe is not under any stress causing it to move independently of the toolhead and I believe the EZABL probe is parallel to the bed (although I've been told that having a minute angle in the orientation of the probe to the bed isn't a huge deal?). What other things can I verify/assess to understand what might be causing the inconsistencies in my z trigger height?

I have a small concern that my x gantry is sagging, but this is only from looking at the mesh data, this is the only thing I can seem to think of that would lead to such significant variation. I'm about to get a camera set up to take photos of the profile of the gantry in relation to the bed at different x coordinates to see if there is sag when the toolhead is in the middle of the gantry, but not sure where else to go at this moment.

[fcwilt]

@elli

I've only seen one image of your mesh and it looks pretty good except I would suspect that you didn't set the Z=0 datum prior to creating the mesh.

Do you have a more recent image done at temp and with the setting of the Z=0 datum?

Frederick

[Phaedrux]

Sag in the gantry can be a bit harder to deal with since it can have the effect of altering the trigger height as the probe moves across the arc of the sag. If that is the case you could measure the trigger height at the center of the bed and the trigger height at the edge of the x gantry to see how much it varies. Then you could try altering the heightmap points by hand to account for that trigger height variation.

[elli]

@phaedrux @fcwilt

My z=0 point is meant to be 131,125, and currently is reporting a z value of -.024.

here is my heightmap.csv:

 -0.129, -0.184, -0.204, -0.224, -0.244, -0.249, -0.254, -0.279, -0.274, -0.269, -0.244, -0.244, -0.224, -0.194, -0.169
 -0.094, -0.124, -0.139, -0.159, -0.179, -0.184, -0.199, -0.229, -0.229, -0.214, -0.194, -0.199, -0.184, -0.169, -0.139
 -0.054, -0.104, -0.109, -0.114, -0.129, -0.134, -0.159, -0.194, -0.194, -0.179, -0.154, -0.164, -0.149, -0.139, -0.114
 -0.019, -0.039, -0.039, -0.029, -0.029, -0.039, -0.079, -0.124, -0.129, -0.114, -0.094, -0.094, -0.084, -0.084, -0.069
  0.026, -0.014, -0.014,  0.001,  0.011, -0.004, -0.044, -0.089, -0.094, -0.089, -0.069, -0.059, -0.049, -0.059, -0.039
  0.061,  0.041,  0.051,  0.056,  0.051,  0.036,  0.001, -0.044, -0.049, -0.044, -0.019, -0.019, -0.014, -0.029, -0.009
  0.096,  0.051,  0.051,  0.051,  0.036,  0.026, -0.004, -0.044, -0.039, -0.024,  0.001, -0.009, -0.009, -0.019,  0.001
  0.111,  0.091,  0.091,  0.081,  0.061,  0.046,  0.016, -0.024, -0.014,  0.006,  0.026,  0.016,  0.011, -0.004,  0.021
  0.121,  0.081,  0.076,  0.056,  0.026,  0.011, -0.004, -0.039, -0.024, -0.009,  0.016,  0.011,  0.001, -0.004,  0.021
  0.106,  0.086,  0.076,  0.061,  0.031,  0.021,  0.001, -0.029, -0.024,  0.001,  0.041,  0.021,  0.001,  0.001,  0.026
  0.086,  0.036,  0.021,  0.006, -0.019, -0.019, -0.034, -0.054, -0.034, -0.009,  0.021,  0.001, -0.014, -0.009,  0.031
  0.046,  0.021,  0.006, -0.009, -0.029, -0.029, -0.044, -0.064, -0.044, -0.019,  0.006, -0.024, -0.014, -0.004,  0.031
  0.011, -0.044, -0.064, -0.084, -0.094, -0.094, -0.104, -0.124, -0.109, -0.089, -0.064, -0.059, -0.029, -0.014,  0.031
 -0.039, -0.069, -0.089, -0.104, -0.124, -0.124, -0.144, -0.164, -0.154, -0.139, -0.104, -0.094, -0.054, -0.034,  0.006
 -0.089, -0.144, -0.164, -0.184, -0.204, -0.209, -0.219, -0.239, -0.219, -0.204, -0.169, -0.144, -0.104, -0.079, -0.029

[Phaedrux]

Can you run this test print and see how your current mesh performs?

bedlevel_nozzle_0.4_200x200-0.3-0.8.stl

[elli]

@phaedrux Can do. Will report back later. Having contractor work done in my workshop at the moment.

[fcwilt]

@elli said in G28, G29, G31, & G32 Relationship w/ Probe:

My z=0 point is meant to be 131,125, and currently is reporting a z value of -.024.

If the XY point used when setting the Z=0 Datum is one of the points in the grid the difference (in theory) should be zero.

Many things can cause that to not happen.

But 0.024 is not far off.

Frederick

[Phaedrux]

@fcwilt said in G28, G29, G31, & G32 Relationship w/ Probe:

If the XY point used when setting the Z=0 Datum is one of the points in the grid the difference (in theory) should be zero.

Easiest way is to just pick a point from the mesh near the center of the bed, mouse over it and get the XY point coordinate and use that.