Posts made by dlc60

@chrishamm said in Suddenly, information windows at the bottom of the DWC page:

@dlc60 It's Simplify3D that keeps sending status requests to the Duet via HTTP, which creates a lot of extra messages on DWC, too. I suggest you don't use the Simplify3D Machine Interface, it shouldn't be needed if you have DWC open anyway.

That was humbling. I should have known that. I am not used to the new S3D's interface and didn't realize what that connection actually meant.

Thanks for the heads up.

be well,

My DWC 3.5.1 has started throwing up windows that look like this at the bottom of the DWC page, right in the middle, blocking what I want to look at. The window looks like it is giving a command-by-command commentary on what is happening. Which is not really very interesting.
Why is it doing this and can I turn it off? I use the FIrefox browser.

It does not go away and is constantly updating. It only just started doing this when I connected with the Simplify3D 5.1 version slicer.

be well,
DLC

@droftarts said in Duet Maestro with latest firmware and web control is sluggish.:

@dlc60 said in Duet Maestro with latest firmware and web control is sluggish.:

I cleared the cache and cookies on my browser and all is well now.

That kind of surprises me, but hey, it's a computer, so...

That surprises me, too! But thanks, I’m glad you found a solution to resolve it. I’ll try and remember this if it is reported again. I suspect that a cached file was corrupted, or not updated with a newer version.

I actually had to do this the other day too, but for a different website that wasn’t behaving correctly. Deleting ‘downloaded content’ (or something like that) was enough to restore functionality, rather than deleting cookies, which has the annoying habit of logging you out of websites.

Ian

Every few days I have to kill the web control page and reload when the web page gets too laggy. It starts out fine, then gradually gets more and more laggy. This is with Web contro/Firmware 3.51.

My machine with web control 3.2.1 and firmware 3.1.1 does not do this.

be well,
DLC

SOLVED

@Phaedrux said in Problems with BLTouch bed leveling - part 2:

Your homing files are not correct for using a probe to home Z. They are set as if you have an endstop for Z.

G1 H1 moves are for endstops. To use the probe, you must use G30.

See here for examples: https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_cartesian#homing-z

You don't need to use M500 at all. You've set the trigger height directly in config.g. But for that trigger height to be used correctly, you need to use G30 to home the Z axis.

This did the trick. I had to craft a special homeall.g To put the nozzle in the middle of the bed, that was where my "base" Z = 0 was done. Also because the would be off the bed when X and Y homed, I could not leave it there. But it all came together and my map provides a "flat" bed.
It is kind of amazing since I have been fighting "potato chip" bed syndrome on my TronXY that has SIX tramming screws! I am not talking about throwing this printer out the window any more.

G91                     ; relative mode
G1 H2 Z5 F200           ; raise head 5mm
G1 H1 X-350 Y-350 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-350             ; home X axis
G1 H1 Y-350             ; home Y axis
G1 X5 Y5 F6000          ; go back a few mm
G1 H1 X-350 F360        ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-350             ; then move slowly to Y axis endstop
G90                     ; back to absolute mode
G1 X175 Y175 F2000      ; put head over the centre of the bed, or wherever you want to probe
G30                     ; lower head, stop when probe triggered and set Z to trigger height

Thanks for all the pointers!
Be well,
DLC

@Phaedrux said in Problems with BLTouch bed leveling - part 2:

Your homing files are not correct for using a probe to home Z. They are set as if you have an endstop for Z.

G1 H1 moves are for endstops. To use the probe, you must use G30.

See here for examples: https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_cartesian#homing-z

You don't need to use M500 at all. You've set the trigger height directly in config.g. But for that trigger height to be used correctly, you need to use G30 to home the Z axis.

Oh, I did not know that using the Z-min end stop was not compatible with using the BLTouch mapping. I will correct that and use the proper G30 Z-min home.

Thanks! This bed mesh process has a lot more nuance than I thought it did.

be well,
DLC

RESOLVED

@Phaedrux said in Problems with BLTouch bed leveling - part 2:

@DIY-O-Sphere said in Problems with BLTouch bed leveling - part 2:

This means that the config.g is always overwritten with the values from the config-override.g.

Not everything though. Only values that have been saved with M500. If M500 P31 has never been used before to save a G31 Z value, it won't be present in config-override.g. Definitely worth checking though.

@dlc60 Please post your full config.g, config-override.g, and homing files. Even you slicer start gcode. Chances are your Z position is being changed somewhere.

I do not have a config-override.g file. Your comment about the home files made me look, and I found this:

G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 Z-300 F1800 ; move Z down until the endstop is triggered
G92 Z0            ; set Z position to axis minimum (you may want to adjust this)

That is where my G92 setting gets overridden.
So, after doing my mesh leveling run, should I do a M500 to save these settings? I am still learning Reprap on Duet, all my experience up until now has been Marlin and EEPROM stores and recoveries.

I pulled the G92 entries from homez.g and homeall.g. Things work correctly now.
Thank you for providing the hint I needed to understand what was going on!

be well,
DLC

@DIY-O-Sphere said in Problems with BLTouch bed leveling - part 2:

@dlc60
I assume you are using M501 at the end of your config.
At least that's what I saw in another post.
This means that the config.g is always overwritten with the values from the config-override.g.
Please check whether a different value is stored here for G31.
If you change values, the current status must be written with M500.
In your case M500 G31.

I am not. I do not fully understand what that does. Could it be that simple?

be well,
DLC

See last message in this thread.

I am back with another machine unable to get a working bed level mesh with BLTouch. It is just too high off the bed, I can adjust my G31 Z height to anything I want apparently, but it won't change where the tip goes.
Here is the Z probe bit of my config.g file:

; Z-Probe
M950 S0 C"zprobe.mod"								   ; Duet 2 Maestro BLTouch MOD
M558 P9 C"^zprobe.in" H5 F120 T6000                    ; Duet 2 Maestro BLTouch sense
G31 X-40.5 Y0 Z1.70						           ; 0 mm Y, 43.5 MM X, 3.5 mm above nozzle, G30 command will tune this
M557 X9:289 Y30:310 S40                               ; define mesh grid Xmin:Xmax Ymin:Ymax Spacing

I have my BLTouch -40.5mm X and 0mm Y and retracted the tip is 3.5mm above the print nozzle.
I use a Z end stop and it is set to put the nozzle 0.05mm above the bed. I set this with a stainless steel feeler gauge. The is the point that I set G92 Z0 at.

I move to dead center of my 330mm bed and the G30 S-1 consistently reports this.

My mesh procedure is exactly what is given on the duet site.
Assumes M558 mesh set up in config.g already.

Make sure there is no filament stuck to the nozzle (do this test with the nozzle and bed hot)
Cancel any existing bed compensation by sending M561

Send M564 S0 to allow movement lower than where the firmware thinks Z=0 is. This is to ensure that you can lower the nozzle all the way to the bed in step 5.

Move the head to the middle of the bed (my preference)

Command the print head down in small steps, using the jog buttons in DWC or by sending individual G1 Z[value] commands, until the nozzle just touches the bed or just grips a sheet of paper.
Create a macro to lower the head by e.g. 0.02mm for greater accuracy (G91 followed by G1 Z-0.02).

Send G92 Z0 to define that height as Z=0

Command the nozzle up 5mm (G1 Z5)

Send G30 S-1 to probe the bed without resetting the Z=0 position

Read off the Z height from the web interface. That is the trigger height.
Repeat the previous two steps a couple of times to make sure you are getting a consistent result
In config.g set the G31 command for height in the Z parameter (ex. G31 X-40.5 Y0 Z1.70).

Run G29 S0 to probe the points, this saves to sys/heightmap.csv
Put G29 S1 at the end of config.g so this map is loaded at startup.
Put M376 H5 at end of config.g to set max height mm where mesh leveling calcs stop being done.

Since my G31 probe location is already set up, I don't need to edit this into the config.g every time.
I have done this procedure at least 20 times and done some minor variations countless times. The nozzle never gets closer than about 0.3mm above the bed. I measured it with a feeler gauge.
I get a very reasonable height map for this crappy TronXY bed with a glass plate on it.

I clearly am missing something. Can anyone tell me what is going on?

be well,
DLC

SOLVED IT.

I cleared the cache and cookies on my browser and all is well now.

That kind of surprises me, but hey, it's a computer, so...

be well,
DLC

@dlc60 said in Duet Maestro with latest firmware and web control is sluggish.:

@droftarts said in Duet Maestro with latest firmware and web control is sluggish.:

@dlc60 3.5.1 works fine on my Maestro. Run the SD card tests as shown here: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues

Backup the SD card and reformatting might help. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#formatting

Otherwise a new card; see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#specification

Make sure the RRF and DWC versions match too.

Ian

Ian,

I used both the included uSD card and a 4GB card formatted FAT32 Windows. No difference. I'll try the tests and reformatting my 4GB card to FAT16 - I just used what was in the last Maestro that I bought with no changes (2 or 3 years ago on the firmware available then, that one is snappy. But, <stuff> happens.

I made sure my web control and firmware were the same rev. So, that is fine.

Coincidentally, this project is putting a Maestro on a TronXY printer like that in your tag line.

be well,
DLC

I reformatted the 4GB card to FAT instead of FAT32, moved my files over and did the performance check (M122) and got this:
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest read time 1.3ms, write time 0.0ms, max retries 0
which is exactly what the Duet site says my Maestro should be able to do.
Still sluggish with command delays.

Someone said to shut down the web viewer and restart it. Not sure how to do that, and since I have rebooted the Maestro several times, I don't think that is an answer anyway. I'll try flushing my browser cache and see what happens.

DLC

@droftarts said in Duet Maestro with latest firmware and web control is sluggish.:

@dlc60 3.5.1 works fine on my Maestro. Run the SD card tests as shown here: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues

Backup the SD card and reformatting might help. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#formatting

Otherwise a new card; see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#specification

Make sure the RRF and DWC versions match too.

Ian

Ian,

I used both the included uSD card and a 4GB card formatted FAT32 Windows. No difference. I'll try the tests and reformatting my 4GB card to FAT16 - I just used what was in the last Maestro that I bought with no changes (2 or 3 years ago on the firmware available then, that one is snappy. But, <stuff> happens.

I made sure my web control and firmware were the same rev. So, that is fine.

Coincidentally, this project is putting a Maestro on a TronXY printer like that in your tag line.

be well,
DLC

I recently brought up a Duet Maestro on a DIY printer. I used the latest firmware and web control and configuration utility as of last week (around May 16).
The web interface is sluggish. It will take up to 2 seconds to respond to a command or button click, the exact timing is inconsistent. I have tried it with the installed uSD card and with a 4GB class 4 uSD card, no difference.
A print job appears to run fine, only the web control hesitates after every command. Another thing, when I click on a system file, I see a message pop up saying "downloading file" for a second or two before the file opens.

I have another printer using a Maestro that I set up a couple of years ago, I think the firmware and web control is 3.1. It works fine and is responsive. System files open instantly when clicked on.

Does the new firmware/web control not work well on the old Duet Maestro?

be well,
DLC

@Phaedrux said in config.g file created with RRF tool M350 Array too long error:

Can you share your config.json file as well?

Sure, here you go.

be well

configtool.json

This was my best guess for a place to ask this question.
Details:
Duet 2 Maestro
F/W 3.5.1, Web 3.5.1
RRF 3.5.0
Printer: custom CoreXY with single extruder.

Problem:
I just updated my Maestro to firmware/web 3.5.1 and used the RRF config tool to build my initial config.g file.
I got this error:
Error in start-up file macro line 45: in file macro line 45 column 19: M350: array too long, max length = 0
Line 45 doesn't have an M350, but there is one near there for the extruder. (attached config.g file)

; Extruders
M584 E3 ; set extruder mapping
M350 E16 I1 ; configure microstepping with interpolation
M906 E1000 ; set extruder driver currents
M92 E764 ; configure steps per mm
M566 E120 ; set maximum instantaneous speed changes (mm/min)
M203 E7200 ; set maximum speeds (mm/min)
M201 E250 ; set accelerations (mm/s^2)

My last RRF config file for another printer was from a prior version of RRF and this looks different, I am scratching my head. Can anyone see what is going wrong?

Any hint appreciated. Be well,
DLC

config.g

@stuartofmt said in unable to get BLTouch mesh compensation to work properly.:

@dlc60

This macro may be overkill, but may help. It will calculate the probe points for you. I use it for quick calibrations (small number of probe points) t0 get the bed more-or-less level then a more comprehensive calibration.

To use you would likely need to have global zprobe_index = 0 at the start (I use a couple of different zprobes hence the variable)

; Creates a mesh calibration
; Assumes the bed limits (actual area reachable by the nozzle)
; have been set with M208
; Assumes the probe offset has been set with G31
;
;--- Prerequisites --------------
; global.zprobe_index MUST  be defined.  The probe number to use.
;
; --- CHANGE THESE SETTINGS TO YOUR REQUIREMENTS ---
;
; Heat Bed and Nozzle ?
var set_temp = false
;
;  Set bed and nozzle temp -- Note that this is not too critical
var bed_temp = 50.0       ; set at an reasonable temp (e.g. 50 should be good enough for PLA and PETG
var nozzle_temp = 150.0   ; set high enough to allow for some expansion but not enough to ooze
;
; Set margin to limit area of bed to be probed should be >= 1.0
var X_margin = 1.0 
var Y_margin = 1.0
;
; Set the number of probe points in X and Y axis
var P_X_points = 0
var P_Y_points = 0
;
; ------------------------------------------
; --- SHOULD NOT CHANGE BELOW THIS POINT ---
;-------------------------------------------
;
;Ensure a tool is selected
;
if state.currentTool < 0   ; no tool selected
	var msg = "Cannot run if no tool is selected"
	M117 {var.msg}
	abort {var.msg}

M291 R"How Many Probe points" P"Select a number" K{"9","16","64","100","Cancel"} S4
if input = 0
    set var.P_X_points = 3
    set var.P_Y_points = 3

elif input = 1
    set var.P_X_points = 4
    set var.P_Y_points = 4

elif input = 2
    set var.P_X_points = 8
    set var.P_Y_points = 8

elif input = 3
    set var.P_X_points = 10
    set var.P_Y_points = 10
else
    abort "Selection cancelled"

M291 R"Hot or Cold Calibration" P"Turn on Heaters" K{"YES","NO","Cancel"} S4
if input = 0
    set var.set_temp = true

elif input = 1
    set var.set_temp = false

else
    abort "Selection cancelled"
;
;initialize local variables
var X_grid_min = 0.0
var X_grid_max = 0.0
var Y_grid_min = 0.0
var Y_grid_max = 0.0
; Get the limits for accessible parts of the bed i.e. where nozzle can reach
var X_min = move.axes[0].min
var X_max = move.axes[0].max
var Y_min = move.axes[1].min
var Y_max = move.axes[1].max
;  Set the probe offset
var X_offset = sensors.probes[{global.zprobe_index}].offsets[0]
var Y_offset = sensors.probes[{global.zprobe_index}].offsets[1]
;
;   ------------  MACRO STARTS HERE-----------------
;
G90 			; use absolute coordinates
M83 			; extruder relative mode
;
if var.set_temp
    echo "Wait for Calibration Temperatures to be reached"
    M104 S{var.nozzle_temp} 		
    M140 S{var.bed_temp}    		; set bed temp a compromise between PLA and PETG
    M116			; wait for temperatures to be reached
    ;G1 E-4 F3600	; retract filament quickly so no ooze


M290 R0 S0		;remove any babysteps
M561            ; reset any bed compensation


;
; Calculate X max and min probe points
if var.X_offset >= 0.0   ; right hand probe point is limited
    set var.X_grid_min = {var.X_min + var.X_margin + var.X_offset}
    set var.X_grid_max = {var.X_max - var.X_margin}
else
    set var.X_grid_min = {var.X_min + min(var.X_margin, -var.X_offset)} 
    set var.X_grid_max = {var.X_max - var.X_margin + var.X_offset} ; X offset is negative so we add

echo "X offset " ^ var.X_offset ^ " (" ^ var.X_grid_min ^ ":" ^ var.X_grid_max ^ ")"  
;
;  Calculate Y max and min probe points
if var.Y_offset >= 0.0
    set var.Y_grid_min = {var.Y_min + var.Y_margin + var.Y_offset}
    set var.Y_grid_max = {var.Y_max - var.Y_margin}  
else
    set var.Y_grid_min = {var.Y_min + min(var.Y_margin, -var.Y_offset)}   
    set var.Y_grid_max = {var.Y_max - var.Y_margin + var.Y_offset} ; Y offset is negative so we add

echo "Y offset " ^ var.Y_offset ^ " (" ^ var.Y_grid_min ^ ":" ^ var.Y_grid_max ^ ")" 
;
; Set the grid probe points
M557 X{var.X_grid_min,var.X_grid_max} Y{var.Y_grid_min,var.Y_grid_max} P{var.P_X_points,var.P_Y_points}
M557            ;report the settings
;
echo "Performing Mesh Calibration"
G28             ; must be homed first
G30	K{global.zprobe_index}			; Perform a single probe to establish Z=0 (should already be at center because of home)
G29 K{global.zprobe_index} S0			; perform mesh calibration save and load
G0 Z50 F3000 	; lower bed

echo "Calibration Complete"
if var.set_temp
    G1 E4 F300 	    ; put filament back
    ; Turn off heaters
    M568  S0 R0 A0           ; Reset temps and turn off hotend
    M140 S0 R0               ; Reset bed temps
    M140 S-273               ; Turn of bed heater
ob 

I created a simpler macro that does most of what you do here, Kind of a combination of yours and Rob's.
Mine handles homing, bed and nozzle heating, and compensation. As Rob mentioned, the G92 Z0 is not very useful for me since I have a Z end stop that I set to 0.05 mm at the center of the bed. That is my reference point. Then I get a G30 S-1 at that point to find the offset there, set my config.g G31 probe offsets. This is my starting point. Then I fire off the compensation macro.

This has proven itself to work reasonably well. Certainly better than trying to manually tram the bed to any great precision. Metal plates and biosilicate glass have proven to be not very flat.

Thank you everyone!

be well,
DLC

@paralepsis said in unable to get BLTouch mesh compensation to work properly.:

@dlc60 Ok. I'm not sure if this will help, but here's precisely what I do to set up my height map.

G1 X102 Y60 F2400 ; move to a consistent spot for probing
G29 S2                ; clear mesh
G30                   ; probe once

G91  ; relative positioning
G1 Z5
G90  ; absolute positioning

M557 X6.75:288 Y40:298.75 P10:10 
G29 S4 P"/sys/probePoints10x10all.csv"; load probePoints10x10all.csv to skip points

G29 S0 ; probe and enable mesh
M376 H5 ; taper over first 5mm (ought to be more than enough)

Obviously X and Y must be homed prior to this. You can ignore the G29 S4; that's for working around magnets. I won't say this is the "right" way to do things, but it certainly works consistently for me, and I get very small discrepancies in height map (as one would hope!).

Rob

Rob,

I did these steps first:
M561 to clear any mesh.
homed all
moved to center of bed and up 5mm
G30 S-1 to find offset.
Modified config.g G31 probe offset.
Restarted.
Then this
Homed all, moved to center 5mm up
M561 to clear any mesh
Ran your sequence but didn't do the G30 single probe - and ran my M557 pattern.
I am now getting what I expect to see, a well laid down first layer. and a reasonable height map, which could be better, but isn't too bad.

I have no idea where I may have gone wrong - Maybe should not have stayed up so late?

be well,
DLC

@paralepsis said in unable to get BLTouch mesh compensation to work properly.:

@dlc60 Ok. I'm not sure if this will help, but here's precisely what I do to set up my height map.

G1 X102 Y60 F2400 ; move to a consistent spot for probing
G29 S2                ; clear mesh
G30                   ; probe once

G91  ; relative positioning
G1 Z5
G90  ; absolute positioning

M557 X6.75:288 Y40:298.75 P10:10 
G29 S4 P"/sys/probePoints10x10all.csv"; load probePoints10x10all.csv to skip points

G29 S0 ; probe and enable mesh
M376 H5 ; taper over first 5mm (ought to be more than enough)

Obviously X and Y must be homed prior to this. You can ignore the G29 S4; that's for working around magnets. I won't say this is the "right" way to do things, but it certainly works consistently for me, and I get very small discrepancies in height map (as one would hope!).

Rob

Rob,

All the instructions that I have say to do G30 S-1 to find the Z probe offset to update the G31 in the config.g file. What does your Line 3 above do? What is your G31 probe offset look like when you start this? Are you working always with a previously set G31 in config.g? You are not setting the G92 Z0 either, are you using whatever you currently have?

be well,
DLC

@paralepsis said in unable to get BLTouch mesh compensation to work properly.:

@dlc60 So if you just boot up, home X and Y, home Z, and then move to Z=0, how far is the nozzle from the bed, in reality? Couple of mm away?

Nope, about 0.05 mm according to my gap gauge.

be well,
DLC

@paralepsis said in unable to get BLTouch mesh compensation to work properly.:

@dlc60 I'm not sure I'll be able to answer all your questions, but here are a couple of things:

• The range you've selected in M557 (start, spacing of 20 in X and Y) has mesh points at Y=190, which is not reachable according to the combination of Ymax (210) and probe Y offset (-21) that you've chosen. You could get rid of those warnings by tweaking the M557 parameters (e.g., Y4:189).
• The height map looks like it would be decent if not for a ~2mm discrepancy in offset. Sounds like you're probing separately to figure out what the Z offset should be, but you then need to account for that in the G31 Z parameter. A larger Z parameter will bring the nozzle closer to the bed.
• I would suggest concentrating on getting Z=0 to be in the right place first, and then worry about the height map.

Hope this helps.

Thanks for replying - I understand the unreachable points, since that isn't much of a problem, I've back-burnered tweaking that setting.

I agree about the height map. As noted, I do a Z=0 set everytime I run the sequence. That has been pretty repeatable. I also tried to adjust the Z offset by baby stepping and add that tweak to the Z offset, but it did not appear to change anything. I know what the issue is, I just seem to be doing something wrong when following the setup procedure.

be well,

Essentials
Duet 2 Maestro ver. 3.1.1
Custom CoreXY
Genuine BLTouch ver. 3
Wired and working with all the gcode commands, deployprobe.g, retractprobe.g files.
My offset for the BLTouch: X0, Y-21, Z4.1

(edit 1)
More details:
I have a Z-min limit switch as well as a BLTouch. I set that limit to 0.05mm at the center of my build plate.
I do all steps with both the bed and the hot end at temperature, not cold.

I have repeatedly done the on-line suggested steps
M561
M564 H0
G92 Z0
G30 S-1
Edit config.g to change the G31 settings with the last result
G29 Do the matrix probe, which banged along fine. Here are the console results.

4/14/2024, 10:39:49 PM G29 S0
Warning: Skipping grid point (190.0, 190.0) because Z probe cannot reach it
Warning: Skipping grid point (170.0, 190.0) because Z probe cannot reach it
Warning: Skipping grid point (150.0, 190.0) because Z probe cannot reach it
Warning: Skipping grid point (130.0, 190.0) because Z probe cannot reach it
Warning: Skipping grid point (110.0, 190.0) because Z probe cannot reach it
Warning: Skipping grid point (90.0, 190.0) because Z probe cannot reach it
Warning: Skipping grid point (70.0, 190.0) because Z probe cannot reach it
Warning: Skipping grid point (50.0, 190.0) because Z probe cannot reach it
Warning: Skipping grid point (30.0, 190.0) because Z probe cannot reach it
Warning: Skipping grid point (10.0, 190.0) because Z probe cannot reach it
Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
90 points probed, min error -2.367, max error -2.046, mean -2.219, deviation 0.082
Height map saved to file 0:/sys/heightmap.csv
4/14/2024, 10:28:28 PM Upload of config.g successful after 0s (Did not reboot after the save)
4/14/2024, 10:27:52 PM G30 S-1
Stopped at height 1.846 mm
4/14/2024, 10:26:58 PM G92 Z0
4/14/2024, 10:24:46 PM G0 X100 Y 100
4/14/2024, 10:24:26 PM M564 H0

This one turned out especially bad. Every time I run the sequence it seems to get worse.
I have attached my config.g file, I think.
config.g
heightmap.csv

I have two questions:
All the instructions I have seen have you add the G31 Z offset as you measure it. The start the sequence. After the G30 S-1 step, then modify the G31 Z offset in config. I originally did this and told the software to restart after the save, then ran G29 S0 to get the height table. That did not work well, I got a bad first layer the nozzle clearly too high up.
Using baby steps got the nozzle where I wanted it, but changing the G31 offset by that change accomplished nothing that I could see - I tried arbitrary adjustments, still nothing.
Then I started doing the G29 S0 mesh probe without restarting after the config.g save. Still nozzle too high off the bed, and adjusting the G31 Z value did nothing.

My two questions:
What am I doing wrong? What step am I missing.
After changing the config.g G31 Z offset to the G30 S-1 value, do I need to restart the Duet before running the G29 S0 mesh probe?

Any help appreciated. I am scratching my head. All the steps seem to work as indicated, and I do see the mesh Z adjustments happening, but it the nozzle is just too far off the plate.
I Set my Z endstop and adjust screws at each corner, which gets kinda close before I do any of the above.

Thank you and be well,
DLC