when will the new Z-height actually be saved?

achrn

That instruction is to set the probe trigger height. You seem to be talking about something else.

That set of commands only sets up the trigger height of the probe so that the machine knows where the nozzle is relative to the bed when the probe triggers.

If what you mean is that you have changed where the nozzle is relative to the endstop switches (by changing the geometry of some or all of the endstops / carriages / rods / effector / nozzle / hotend) you need to re-run delta calibration (G32) not recalibrate the z probe trigger height.

jay_s_uk

This post is deleted!

Phaedrux

Please post your homeall, homez, bed.g, start.g and your slicer start gcode section so we can see what is happening.

The smart effector has a negative G31 Z offset because it contacts the bed and presses into it. So -0.1 sounds fine, but perhaps you have another command altering it after startup.

holco62

The G32 (achrn) dit the trick But what a hassle to sort everything out for a beginner

What is the way to setup Auto calibrating before each print?

jay_s_uk

add G32 to your start gcode

holco62

@jay_s_uk

It looks that I don't have a start gcode in my System Directory, or I can't find it

fcwilt

@holco62 said in when will the new Z-height actually be saved?:

@jay_s_uk

It looks that I don't have a start gcode in my System Directory, or I can't find it

Hi,

They are talking (I think) about the place in S3D where you can enter gcode to be executed before the start of the print.

You can also, if you wish, create "start.g" in your system directory and put gcode there - the firmware executes "start.g" at the start of the print.

Frederick

holco62

@Phaedrux

I don't know where to find the rest

bed.g

holco62

Tomorrow is a new day, I have to go to bed now.

But thanks for all the help

Phaedrux

@holco62 said in when will the new Z-height actually be saved?:

I don't know where to find the rest

in the /sys folder along with config.g

holco62

This all I have in the System Directory

System Directory.png

holco62

@fcwilt said in when will the new Z-height actually be saved?:

@holco62 said in when will the new Z-height actually be saved?:

@jay_s_uk

It looks that I don't have a start gcode in my System Directory, or I can't find it

Hi,

They are talking (I think) about the place in S3D where you can enter gcode to be executed before the start of the print.

You can also, if you wish, create "start.g" in your system directory and put gcode there - the firmware executes "start.g" at the start of the print.

Frederick

Made a start.g directory with a G32 file in it, but for the rest I am lost Start.G.png

engikeneer

@holco62 he meant create a file called start.g in your duet system directory (/sys folder). In that file, put the line:

G32

To answer your other question on the files, please attach your bed.g and homedelta.g files from the system directory (i can see the file names in the screenshot)

holco62

@engikeneer said in when will the new Z-height actually be saved?:

@holco62 he meant create a file called start.g in your duet system directory (/sys folder). In that file, put the line:
G32 
To answer your other question on the files, please attach your bed.g and homedelta.g files from the system directory (i can see the file names in the screenshot)

Thanks

start.g is working, one thing though, it das the calibration with a gold bed/hotend, is there a way to bring up the temps first?

The bed.g and the homedelta.g files

bed.g.png homedelta.g.png

Phaedrux

@holco62 said in when will the new Z-height actually be saved?:

is there a way to bring up the temps first?

You could add a bed heat up command to the start of your bed.g. something like.

M140 S60 ; set bed to 60 and continue
G28 ; home towers
M116 ; for for tempts to be reached
G30.... etc ; probe for calibration

fcwilt

@holco62 said in when will the new Z-height actually be saved?:

...is there a way to bring up the temps first?

Short answer - yes - @Phaedrux has shown a simple approach.

Long answer - there are several different ways to do all that is needed to start a print.

For example, instead of putting everything in bed.g you leave just the essential commands there (the commands you already have) and put everything else (setting temps, waiting for temps, etc) in start.g including the G32 to invoke bed.g.

As you become more comfortable with the firmware there are lots of things possible.

I'm including my equivalent of "start.g" just to give you an idea of the possibilities BUT I am NOT suggesting that you try to adopt anything I have done at this time.

There are lots of extra ; characters there that I added because {1} appeared at the start of empty lines when I pasted the code

; select tool and configure based on filament selected

T0							; select tool 0 so extruder commands below will work
M703							; configure selected filament (sets bed/extruder temps, extrusion multiplier)

; check for selected filament

if move.extruders[0].filament = ""
  M291 R"No Filament Selected" P"Cannot Continue" S2 T0
  abort

; check bed heater active temp setting

if heat.heaters[0].active = 0 
  M291 R"Bed Heater Active Temp = 0" P"Cannot Continue" S2 T0
  abort

; check extruder heater active temp setting

if heat.heaters[1].active = 0 
  M291 R"Extruder Heater Active Temp = 0" P"Cannot Continue S2 T0
  abort
;
; check if homed - allows homing (OK button) or canceling (CLOSE button)
;
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
  M291 R"Printer has not been homed" P"Home and Continue?" S3 T0
  G28
;
; setup to print
;
M291 R"Preparing to print" P"Please wait..." T0
;
M106 P2 S255					; lights on
M106 P3 S255					; lights on
M106 P4 S255					; lights on
;
G90						; absolute moves
G1 Z100     F1200				; position for cleaning
G1 X0 Y-145 F6000				; position for cleaning
;
M291 R"Heating Extruder/Bed" P"Please wait..." T0
;
M116							; wait for temps to reach set points
;
M291 R"Priming Extruder" P"Please wait..." T0
;
G92 E0							; reset the extruder logical position
M83							; extruder relative mode
G1  E10 F120					        ; prime the extruder
M400							; wait for extruding to finish
G92 E0							; reset the extruder logical position
;
M98 P"beep_alert_1.g"                                   ; beep paneldue
;
M291 R"Clean Nozzle and Bed" P"Click OK to begin printing" S3 T0
;
M98 P"mesh_comp_map_load.g"		                ; load height map as needed
;
M118 L0 P4 S"FT5|Print begun"

holco62

@fcwilt said in when will the new Z-height actually be saved?:

@holco62 said in when will the new Z-height actually be saved?:

...is there a way to bring up the temps first?

Short answer - yes - @Phaedrux has shown a simple approach.

Long answer - there are several different ways to do all that is needed to start a print.

For example, instead of putting everything in bed.g you leave just the essential commands there (the commands you already have) and put everything else (setting temps, waiting for temps, etc) in start.g including the G32 to invoke bed.g.

As you become more comfortable with the firmware there are lots of things possible.

I'm including my equivalent of "start.g" just to give you an idea of the possibilities BUT I am NOT suggesting that you try to adopt anything I have done at this time.

There are lots of extra ; characters there that I added because {1} appeared at the start of empty lines when I pasted the code
; select tool and configure based on filament selected

T0							; select tool 0 so extruder commands below will work
M703							; configure selected filament (sets bed/extruder temps, extrusion multiplier)

; check for selected filament

if move.extruders[0].filament = ""
  M291 R"No Filament Selected" P"Cannot Continue" S2 T0
  abort

; check bed heater active temp setting

if heat.heaters[0].active = 0 
  M291 R"Bed Heater Active Temp = 0" P"Cannot Continue" S2 T0
  abort

; check extruder heater active temp setting

if heat.heaters[1].active = 0 
  M291 R"Extruder Heater Active Temp = 0" P"Cannot Continue S2 T0
  abort
;
; check if homed - allows homing (OK button) or canceling (CLOSE button)
;
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
  M291 R"Printer has not been homed" P"Home and Continue?" S3 T0
  G28
;
; setup to print
;
M291 R"Preparing to print" P"Please wait..." T0
;
M106 P2 S255					; lights on
M106 P3 S255					; lights on
M106 P4 S255					; lights on
;
G90						; absolute moves
G1 Z100     F1200				; position for cleaning
G1 X0 Y-145 F6000				; position for cleaning
;
M291 R"Heating Extruder/Bed" P"Please wait..." T0
;
M116							; wait for temps to reach set points
;
M291 R"Priming Extruder" P"Please wait..." T0
;
G92 E0							; reset the extruder logical position
M83							; extruder relative mode
G1  E10 F120					        ; prime the extruder
M400							; wait for extruding to finish
G92 E0							; reset the extruder logical position
;
M98 P"beep_alert_1.g"                                   ; beep paneldue
;
M291 R"Clean Nozzle and Bed" P"Click OK to begin printing" S3 T0
;
M98 P"mesh_comp_map_load.g"		                ; load height map as needed
;
M118 L0 P4 S"FT5|Print begun"