- home-x-common
; called by homex.g and homeall.g
G1 H1 X155 F3300 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X-5 F3300 ; go back a few mm
G1 H1 X10 F100 ; move slowly to X axis endstop once more (second pass)
G1 H2 X-155 F3300 ; move X 5mm away from endstop
;G1 H2 X-140 F3300 ; move X 5mm away from endstop
G92 X0 ; make X=5mm the zero position
- home-y-common
; called by homey.g and homeall.g
G1 H1 Y-155 F3300 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 Y5 F3300 ; go back a few mm
G1 H1 Y-10 F100 ; move slowly to X axis endstop once more (second pass)
;G1 H2 y5 F3300
;G92 Y-5
@Phaedrux said in [Nozzle piezo] G31 Trigger Z-height being ignored:
You can remove the X0 Y0 Z0
There is a space between R0. and 4 which should be removed.
T300 is very slow travel speed between points. T3000 or 6000 would be more normal I think.
I fixed the mistakes and increased speed to T3000
@Phaedrux said in [Nozzle piezo] G31 Trigger Z-height being ignored:
How did you determine that value?
Use this to see if it is accurate.
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing#calibrate-the-z-probe-trigger-height
the -0.96 comes from babystepping when I used this guide you provide i would get -0.36, but if I made that the babystepping value it still printed in the air.
@Phaedrux said in [Nozzle piezo] G31 Trigger Z-height being ignored:
What do you have in your slicer start gcode section?
here is the first few lines from slicer generated gcode which include the start code. I have tried a different slicer Cura where I don't even put in start gcode and it doesn't make a difference
; generated by PrusaSlicer 2.6.0-beta4+linux-x64-GTK3 on 2023-06-12 at 19:01:22 UTC
; external perimeters extrusion width = 0.45mm
; perimeters extrusion width = 0.45mm
; infill extrusion width = 0.45mm
; solid infill extrusion width = 0.45mm
; top infill extrusion width = 0.40mm
M73 P0 R1
;TYPE:Custom
G90 ; use absolute coordinates
M83 ; extruder relative mode
;M104 S170 ; set extruder temp for bed leveling
M140 S100 ; set bed temp
;M109 R170 ; wait for bed leveling temp
M190 S100 ; wait for bed temp
;M204 T1250 ; set travel acceleration
G28 ; home all without mesh bed level
;G29 ; mesh bed leveling
;M204 T2500 ; restore travel acceleration
M104 S260 ; set extruder temp
G92 E0
M290 R0 Z-1.12
;G1 Y-2 X179 F2400
G1 Z50.000 F420
M109 S260 ; wait for extruder temp
;Prime the extruder
G92 E0
G1 F200 E3
G92 E0
; intro line on X
M73 P5 R1
G1 X120 F1000
M73 P6 R1
G1 Z0.2 F720
M73 P12 R1
G1 X110 E8 F900
M73 P16 R1
G1 X40 E10 F700
G92 E0
;M221 S100 ; set flow to 100%
G21 ; set units to millimeters
G90 ; use absolute coordinates
M83 ; use relative distances for extrusion
M107
;LAYER_CHANGE
;Z:0.2
;HEIGHT:0.2
;BEFORE_LAYER_CHANGE
G92 E0.0
;0.2
@Phaedrux said in [Nozzle piezo] G31 Trigger Z-height being ignored:
It's hard to tell from your photo, but it looks like the mesh is very offset from the grid. What does it look like from a top view?
I have since changed the extruder that has the piezo and forgort to take screenshot of mesh
@Phaedrux said in [Nozzle piezo] G31 Trigger Z-height being ignored:
Can you also confirm for me that -X moves go to the left, +X moves go to the right, -Y moves go to the front, +Y moves go to the back?
yes everything works fine. you will see from my start gcode I am inluding babystepping gcode in the start gcode with R0 and that how I am printing and the prints come out correct left side to left, right to right and so on.
One thing that I wonder about is does Duet support Z max endstop and z probe at the same time? so I home using Z max endstop and only use the z probe for bed leveling; when I read the guide below I don't think they mention the configuration I have . Configuration_cartesian
anyway my workaround at this time is using M290 R0 Z-0.96 in the slicer start code and put G31 Z0 in config.g and this works well
