Chiron+Duet3+BlTouch

Phaedrux

Don't change M574, it's correct as it is.

But look at your homing file. It's doing a positive movement away from the endstop.

G1 H1 X405 Y405 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X-5 Y-5 F6000   ; go back a few mm
G1 H1 X405 Y405 F360  ; move slowly to X and Y axis endstops once more (second pass)

Change the X405 Y405 to X-405 and Y-405, reverse the sighs for the rest as well. And remove the H2 from the second line.

razrudy

@Phaedrux said in Chiron+Duet3+BlTouch:

G1 H2

Done. Changed to in both homex and homeall and is working properly. Thanks

; homex.g

G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 X-405 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000       ; go back a few mm
G1 H1 X-405 F360  ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

Why did I needed to remove the H2 in the second line? I am trying to understand the H2 function because on G-code the explanation is not that great

G0 : Rapid Move
G1 : Linear Move
Usage
G0 Xnnn Ynnn Znnn Ennn Fnnn Snnn
G1 Xnnn Ynnn Znnn Ennn Fnnn Snnn
Parameters
Not all parameters need to be used, but at least one has to be used
Xnnn The position to move to on the X axis
Ynnn The position to move to on the Y axis
Znnn The position to move to on the Z axis
Ennn The amount to extrude between the starting point and ending point
Fnnn The feedrate per minute of the move between the starting point and ending point (if supplied)
Hnnn (RepRapFirmware) Flag to check if an endstop was hit (H1 to check, H0 to ignore, other Hnnn see note, default is H0)

Notes: Some firmwares allow for the RepRap to enable or disable the "sensing" of endstops during a move. Please check with whatever firmware you are using to see if they support the H parameter in this way, as damage may occur if you assume incorrectly. In RepRapFirmware, using the H1 or H2 parameter on a delta printer causes the XYZ parameters to refer to the individual tower motor positions instead of the head position, and to enable endstop detection as well if the parameter is H1. H3 may be used to measure axis lengths and H4 can be used to stop when an endstop is hit while updating the position only (H4 is supported in 3.2-b4 and later).

Phaedrux

H2 basically allows you to move an axis even though it hasn't been homed. It's useful for the Z axis which you may want to raise to get the XY axis free to move for it's own homing.

A Former User

Been there done that, its all up and working a long time ago...

razrudy

@CaLviNx can you share your config please ?

A Former User

@razrudy said in Chiron+Duet3+BlTouch:

@CaLviNx can you share your config please ?

Having previously posted config.g files I was vilified for doing things in a very particular way that I do, one bitten twice shy, so I am not willing to share my configuration files at this time sorry.

razrudy

Ok , after holiday break back to my project.
Small problem and not sure if this is the way it should be.
My home position is at the bottom/left of the build plate( moving bed in Y axis). I am assuming that if I move the bed towards me ( let's say top/left corner) this will mean the bed is moving in -Y and hotend in +Y.
My current config for homey is this

G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G90               ; absolute positioning
G1 H1 Y415 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G91               ; relative positioning
P4 P500           ; wait 500ms
G1 H2 Y-5 F6000    ; go back a few mm
G4 P500           ; wait 500ms
G1 H1 Y415 F360  ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

and the motor is M569 P0.1 S1
On DWC Y-10 will move the bed forward ( towards me/ top to bottom) which means hotend is moving Y+10.
Is this the right way to set this?

Also my home position is outside the build plate , what's the best way to "tell" the software where the X0Y0 is on the build plate? I think this is called the Z home offset. For me it will be a ZY home offset because of some clips I have on the build plate. I can get a spacer to fix the Z so it will mach the build plate and just modify the Y home offset to avoid the clips.
How you can see on the picture my build plate is a little bigger( blue) then the print area( white) so I assume I need to define the X0Y0 on build plate so the printer will know where the X410Y410 is.

Chiron Bed.png

I am asking all this because I also want to learn all the things/logics/settings not just copy/paste some config that will work

Phaedrux

You can use a negative value for the M208 minima to tell the firmware that the endstops are beyond the edge of the bed.

So for example if x0,y0 is the front left corner, and the endstops are 20mm beyond that set the M208 minima to -20.

@razrudy said in Chiron+Duet3+BlTouch:

G1 H2 Y-5 F6000 ; go back a few mm

Only use H2 for the Z axis in your homing files to allow it to raise and lower without being homed. For the X and Y axis the moves should either be a homing move with H1 or a regular move without any H.

Phaedrux

@razrudy said in Chiron+Duet3+BlTouch:

On DWC Y-10 will move the bed forward ( towards me/ top to bottom) which means hotend is moving Y+10.
Is this the right way to set this?

This sounds backwards.

Rather than thinking of the bed moving, think of the position of the print head on the bed. If the bed is moving back and away from the front, then the print head is moving closer to the front edge of the bed.

razrudy

This post is deleted!

razrudy

@Phaedrux sorted...it was indeed reverted.....now Y+10 is "moving" the nozzle in Y+ and bed in Y- direction and is homing the right way.

razrudy

Done with basic config and now moving to small tweaks and tunings....I am wondering how much from the start and end g-code I can move to "DWC" and what/how much should stay in slicer? Not sure if there is any benefit on having start and end g-code on DWC. I am using PrusaSlicer and like many other slicer's I can have profile's for each printer I am using. If I match the speeds, accelerations , retractions and all other between firmware and slicer there should be no problem. Plus the start and end g-code in firmware is only to "complement" the slicer.
Can I use M98 P"mymacro.g" in the slicer?

razrudy

Config file at 31/12/2020
This values are just the starting point and some speeds , accelerations , steps/mm , heaters tuning......will need to be adjusted based on your machine

; Configuration file for Duet 3 (firmware version 3) 
; Configuration for Chiron+Titan Aero+Volcano+BlTouch
; executed by the firmware on start-up

; General preferences
G21                                                        ; works in mm
G90                                                        ; send absolute coordinates...
M83                                                        ; ...but relative extruder moves
M550 P"Chiron"                                             ; set printer name

; Drives
M569 P0.0 S1                                               ; physical drive 0.0 goes forwards X
M569 P0.1 S0                                               ; physical drive 0.1 goes backwards Y
M569 P0.2 S0                                               ; physical drive 0.2 goes bacwards ZR
M569 P0.3 S0                                               ; physical drive 0.3 goes backwards ZL
M569 P0.4 S1 D2                                            ; physical drive 0.4 goes forwards E
M584 X0 Y1 Z2:3 E4                                         ; set drive mapping
M350 X16 Y16 Z16 E16 I1                                    ; configure microstepping with interpolation
M92  X80 Y100 Z400 E460                                    ; set steps per mm
M566 X1200 Y1200 Z12 E120                                  ; set maximum instantaneous speed changes (mm/min)
M203 X9000 Y9000 Z180 E1200                                ; set maximum speeds (mm/min)
M201 X1000 Y800 Z250 E250                                  ; set accelerations (mm/s^2)
M906 X1100 Y1100 Z1100 E1100 I30                           ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                                    ; Set idle timeout

; Axis Limits
M208 X-6.0 Y-9.0 Z-20 S1                                   ; set axis minima
M208 X411 Y405 Z445 S0                                     ; set axis maxima-need to remeasure this
M671 X-40:440 Y200:200                                     ; leadscrews position at right and left of the X axis
 
; Endstops
M574 X1 S1 P"!io0.in"                                      ; configure active-high endstop for low end on X via pin io0.in    
M574 Y1 S1 P"!io1.in"                                      ; configure active-high endstop for low end on Y via pin io1.in
;M574 Z1 S1 P"io2.in+io3.in"                               ; configure active-high endstop for low end on Z via pin-for original endstop's
M574 Z1 S2                                                 ; endstop set to z-probe


; Z-Probe
M950 S0 C"io5.out"                                         ; create servo pin 0 for BLTouch
M558 P9 C"^io5.in" H5 F120 T6000                           ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X41.13 Y2.69 Z1.543                               ; set Z probe trigger value, offset and trigger height
M557 X42:405 Y0:405 S121:81                                ; define mesh grid
 

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138               ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                         ; create bed heater output on out0 and map it to sensor 0
M307 H0 A110.3 C842.7 D1.1 S0.5 V23.8 B0                   ; 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"temp1" Y"thermistor" T100000 B4725 C7.06e-8      ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                                         ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 A373.1 C420.1 D3.0 S0.5 V24.1 B0                   ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S285                                               ; set temperature limit for heater 1 to 285C

; Fans
M950 F0 C"out4" Q25000                                     ; create fan 0 on pin out4 and set its frequency
M106 P0 S0 H1 T45                                          ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out5" Q25000                                     ; create fan 1 on pin out5 and set its frequency
M106 P1 S0 H1 T45                                          ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out7" Q25000                                     ; create fan 2 on pin out7 and set its frequency
M106 P2 S0 H-1                                             ; set fan 2 value. Thermostatic control is turned off


; Tools
M563 P0 D0 H1 F0:2                                         ; define tool 0
G10 P0 X-6.0 Y-7.0 Z0.0                                    ; 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
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"        ; set voltage thresholds and actions to run on power loss       
;M564 H0                                                  ; moving axes before/without homing
M591 P1 C"io4.in" S1 D0                                   ; filament run out sensor - work in progress

Phaedrux

@razrudy said in Chiron+Duet3+BlTouch:

Can I use M98 P"mymacro.g" in the slicer?

Yes you can.

There is also a special macro called start.g that will execute when a print is started and will run before any of the sliced gcode file. This can be a good place to do machine prep like homing and preheating.

Ultimately, how you split it up is entirely up to you and what makes most sense for your workflow.

razrudy

I am trying to set the Z offset but apparently I have a problem and not sure if it's a mechanic one or I am missing something
Every time I run G30 S-1 in the same spot I get wrong values...always decreasing with 0.005 or something like this...
I am using

G30 
;Manually lower the nozzle close the build plate
G92 Z0
G1 Z10
G30 S-1

And after each move I get a value with 0.005-0.002 difference

02/01/2021, 16:34:26: G1 XY0
02/01/2021, 16:36:57: G30
02/01/2021, 16:43:21: G92 Z0
02/01/2021, 16:43:46: G30 S-1: Stopped at height 1.435 mm
02/01/2021, 16:43:58: G1 Z10
02/01/2021, 16:44:06: G30 S-1: Stopped at height 1.433 mm
02/01/2021, 16:44:10: G1 Z10
02/01/2021, 16:44:19: G30 S-1: Stopped at height 1.430 mm
02/01/2021, 16:44:24: G1 Z10
02/01/2021, 16:44:32: G30 S-1: Stopped at height 1.425 mm
02/01/2021, 16:44:39: G1 Z10
02/01/2021, 16:44:48: G30 S-1: Stopped at height 1.423 mm
02/01/2021, 16:44:53: G1 Z10
02/01/2021, 16:45:02: G30 S-1: Stopped at height 1.415 mm
02/01/2021, 16:45:09: G1 Z10

I also have problems with mesh bed compensation...it doesn't compensate on the left side. 3/4 of the build plate is coming up nice but the left side the nozzle is always low.
My build plate is crap but until I decide which one to get and replace it I am wondering why the mesh is not applied on the left side.

Maybe because the gantry doesn't properly level with the build plate? Or because the probe is at X42 offset and can't get to X0-X5 for probing?

What's the right order for levelling all this?

I am running 4 points G32 without gantry levelling until I get a good level bed and after that I run
G29 X42:400 Y0:400 P5 and M374( map save)
Load map at the start with M375

Phaedrux

@razrudy said in Chiron+Duet3+BlTouch:

M558 P9 C"^io5.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X41.13 Y2.69 Z1.543 ; set Z probe trigger value, offset and trigger height

You can try improving the repeatability of the BLTouch by changing your M558 and G31 as follows

M558 P9 C"^io5.in" H5 F60 T6000 R0.2 A10
G31 P25 X41.13 Y2.69 Z1.543

See if that helps.

razrudy

So the new BLT settings didn't help. I am still getting differences at every single probe and maybe once in 7-8 I get twice the same reading.
Maybe this happens because I have flexible couplers on the Z ?
Now I am trying to figure out why my heightmap is always ~1mm up on the heightmap tab.

No matter what I am trying I am always ending with this....what I am missing?
I redid multiple times the z calibration using M561 , G92 Z0 , G30 S-1 and setting the new offset and always I end up with this. Maybe this also affect the mesh compensation?
Everything is working except this mesh/leveling thing.

; Configuration file for Duet 3 (firmware version 3) with SBC
; Configuration for Chiron+Titan Aero+Volcano+BlTouch 
; executed by the firmware on start-up

; General preferences
G21                                                        ; works in mm
G90                                                        ; send absolute coordinates...
M83                                                        ; ...but relative extruder moves
M550 P"Chiron"                                             ; set printer name

; Drives
M569 P0.0 S1                                               ; physical drive 0.0 goes forwards X
M569 P0.1 S0                                               ; physical drive 0.1 goes backwards Y
M569 P0.2 S0                                               ; physical drive 0.2 goes bacwards ZL
M569 P0.3 S0                                               ; physical drive 0.3 goes backwards ZR
M569 P0.4 S1 D2                                            ; physical drive 0.4 goes forwards E
M584 X0 Y1 Z2:3 E4                                         ; set drive mapping
M350 X16 Y16 Z16 E16 I1                                    ; configure microstepping with interpolation
M92  X80 Y100 Z400 E407.5                                  ; set steps per mm
M566 X1200 Y1200 Z12 E120                                  ; set maximum instantaneous speed changes (mm/min)
M203 X9000 Y9000 Z180 E1200                                ; set maximum speeds (mm/min)
M201 X1000 Y800 Z250 E250                                  ; set accelerations (mm/s^2)
M906 X1100 Y1100 Z1100 E1100 I30                           ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                                    ; Set idle timeout

; Axis Limits
M208 X-6.0 Y-9.0 Z0 S1                                     ; set axis minima
M208 X400 Y400 Z445 S0                                     ; set axis maxima-need to remeasure this
M671 X-40:440 Y200:200                                     ; leadscrews position at right and left of the X axis
 
; Endstops
M574 X1 S1 P"!io0.in"                                      ; configure active-high endstop for low end on X via pin io0.in    
M574 Y1 S1 P"!io1.in"                                      ; configure active-high endstop for low end on Y via pin io1.in
;M574 Z1 S1 P"io2.in+io3.in"                               ; configure active-high endstop for low end on Z via pin-for original endstop's
M574 Z1 S2                                                 ; endstop set to z-probe


;Stall Detection
;M915 P0 S-5 F0 H200 R0                                    ; P=drive motor , S= sensitivite , H=motorstep/sec ( check home file)

; Z-Probe
M950 S0 C"io5.out"                                         ; create servo pin 0 for BLTouch
M558 P9 C"^io5.in" H5 F60 T6000 R0.2 A10                   ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X41.13 Y2.69 Z1.378                              ; set Z probe trigger value, offset and trigger height
M557 X42:380 Y0:400 P3                                     ; define mesh grid
 
; Piezo Z-probe 
;M558 P8 C"io5.in" I1 R0.4 F300 X0 Y0 Z1                   ;new piezo
;G31 X0 Y0 Z-0.1 P100                                      ;new piezo


; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138               ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                         ; create bed heater output on out0 and map it to sensor 0
M307 H0 A110.3 C842.7 D1.1 S0.5 V23.8 B0                   ; 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"temp1" Y"thermistor" T100000 B4725 C7.06e-8      ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                                         ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 A373.1 C420.1 D3.0 S0.5 V24.1 B0                   ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S285                                               ; set temperature limit for heater 1 to 285C

; Fans
M950 F0 C"out4" Q25000                                     ; create fan 0 on pin out4 and set its frequency
M106 P0 S0 H1 T45                                          ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out5" Q25000                                     ; create fan 1 on pin out5 and set its frequency
M106 P1 S0 H1 T45                                          ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out7" Q25000                                     ; create fan 2 on pin out7 and set its frequency
M106 P2 S0 H-1                                             ; set fan 2 value. Thermostatic control is turned off
;M950 F3 C"out8" Q500                                      ; create fan 3 on pin out8 and set its frequency
;M106 P3 S0 H-1                                            ; set fan 3 value. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F0:2                                         ; define tool 0
G10 P0 X-6.0 Y-7.0 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
;M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"        ; set voltage thresholds and actions to run on power loss       
M564 H0                                                  ; moving axes before/without homing
;M591 P1 C"io4.in" S1 D0                                   ; filament run out sensor - work in progress

And here are the last outputs for G30 S-1

03/01/2021, 15:13:54: G30 S-1: Stopped at height 0.068 mm
03/01/2021, 15:14:03: G1 Z10
03/01/2021, 15:14:21: G30 S-1: Stopped at height 0.075 mm
03/01/2021, 15:14:24: G1 Z10
03/01/2021, 15:14:39: G30 S-1: Stopped at height 0.070 mm
03/01/2021, 15:14:43: G1 Z10
03/01/2021, 15:14:59: G30 S-1: Stopped at height 0.065 mm
03/01/2021, 15:17:59: Upload of config.g successful after 0s
03/01/2021, 15:18:00: : Warning: Firmware reset imminent
03/01/2021, 15:18:00: : Connection to Duet established
03/01/2021, 15:18:00: Connection interrupted, attempting to reconnect...: DCS has been stopped
03/01/2021, 15:18:09: Connection established
03/01/2021, 15:21:33: : Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
03/01/2021, 15:21:33: G29: 9 points probed, min error 0.506, max error 0.940, mean 0.783, deviation 0.134
Height map saved to file heightmap.csv





03/01/2021, 15:38:52: G30
03/01/2021, 15:41:22: G92 Z0
03/01/2021, 15:41:40: G1 Z10
03/01/2021, 15:41:55: G30 S-1: Stopped at height 1.668 mm
03/01/2021, 15:41:58: G1 Z10
03/01/2021, 15:42:12: G30 S-1: Stopped at height 1.665 mm
03/01/2021, 15:42:14: G1 Z10
03/01/2021, 15:42:29: G30 S-1: Stopped at height 1.663 mm
03/01/2021, 15:42:41: G1 Z10
03/01/2021, 15:42:54: G30 S-1: Stopped at height 1.670 mm
03/01/2021, 15:43:02: G1 Z10
03/01/2021, 15:43:20: G30 S-1: Stopped at height 1.668 mm
03/01/2021, 15:44:05: Upload of config.g successful after 0s
03/01/2021, 15:44:06: : Warning: Firmware reset imminent
03/01/2021, 15:44:07: : Connection to Duet established
03/01/2021, 15:44:07: Connection interrupted, attempting to reconnect...: DCS has been stopped
03/01/2021, 15:44:15: Connection established
03/01/2021, 15:50:35: : Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
03/01/2021, 15:50:35: G29: 9 points probed, min error 0.550, max error 1.164, mean 0.872, deviation 0.180
Height map saved to file heightmap.csv





03/01/2021, 18:13:07: G30
03/01/2021, 18:14:56: G92 Z0
03/01/2021, 18:15:06: G1 Z10
03/01/2021, 18:15:23: G30 S-1: Stopped at height -1.138 mm
03/01/2021, 18:15:26: G1 Z10
03/01/2021, 18:15:43: G30 S-1: Stopped at height -1.140 mm
03/01/2021, 18:15:46: G1 Z10
03/01/2021, 18:16:05: G30 S-1: Stopped at height -1.145 mm
03/01/2021, 18:16:36: G1 Z10
03/01/2021, 18:16:52: G30 S-1: Stopped at height -1.133 mm
03/01/2021, 18:16:57: G1 Z10
03/01/2021, 18:17:24: G30 S-1: Stopped at height -1.143 mm






03/01/2021, 19:26:40: M561
03/01/2021, 19:27:14: G92 Z0
03/01/2021, 19:28:08: G30 S-1: Stopped at height 1.395 mm
03/01/2021, 19:28:13: G1 Z5
03/01/2021, 19:28:23: G1 Z10
03/01/2021, 19:28:36: G30 S-1: Stopped at height 1.395 mm
03/01/2021, 19:28:41: G1 Z10
03/01/2021, 19:28:59: G30 S-1: Stopped at height 1.388 mm
03/01/2021, 19:29:13: G1 Z10
03/01/2021, 19:29:16: G1 Z10
03/01/2021, 19:29:18: G1 Z10
03/01/2021, 19:29:35: G30 S-1: Stopped at height 1.388 mm
03/01/2021, 19:29:38: G1 Z10
03/01/2021, 19:30:01: G30 S-1: Stopped at height 1.385 mm
03/01/2021, 19:30:14: G1 Z10
03/01/2021, 19:30:27: G1 Z10
03/01/2021, 19:30:39: G30 S-1: Stopped at height 1.375 mm
03/01/2021, 19:30:49: G1 Z10
03/01/2021, 19:31:16: G30 S-1: Stopped at height 1.372 mm
03/01/2021, 19:32:07: G1 Z10
03/01/2021, 19:32:52: G30 S-1: Stopped at height 1.378 mm
03/01/2021, 19:35:32: Upload of config.g successful after 0s
03/01/2021, 19:35:34: : Warning: Firmware reset imminent
03/01/2021, 19:35:34: : Connection to Duet established
03/01/2021, 19:35:34: Connection interrupted, attempting to reconnect...: DCS has been stopped
03/01/2021, 19:35:43: Connection established
03/01/2021, 19:39:46: : Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
03/01/2021, 19:39:47: G29: 9 points probed, min error 0.474, max error 1.061, mean 0.821, deviation 0.175
Height map saved to file heightmap.csv

I am out of ideas and most likely it's just a small mistake somewhere but can't figure out where the problem is

stuartofmt

I had the same heightmap offset problem a couple of days ago. The documentation is a bit ambiguous. I seem to have solved the problem by doing this in the calibration run (I use a macro).

; Heat Bed and Hotend - Home and Calibrate

T0				;make sure the tool is selected
G90 			; use absolute coordinates
M83 			; extruder relative mode

M117 "Setting Calibration Temperatures"
<snip>
M290 R0 S0		;remove any babysteps
M561            ; reset any bed compensation
M117 "Performing Mesh Calibration"
G28             ; must be homed first
G30				; Perform a single probe to establish Z=0 (should already be at center because of home)
G29 S0			; perform mesh calibration save and load

I did a reboot at this point but am not sure if it's at all required.

Then this at the start of the print job

T0             ; turn on the tool
M561           ; Remove any Bed Compensation

G90 ; use absolute coordinates
M83 ; extruder relative mode
<snip>
G28 ; home all
G30  ; probe bed just to make sure
G29 S1  ; enable mesh leveling
<snip>

I suspect there may be redundancy in my codes but .....

razrudy

That's something I was thinking that there is some residue code that can't be seen on files and messing everything. think I will just save the config and make a new sd card and see how the things are working. ...after I will try your code.