Z axis not homing

PRIOR123

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 15:54:40 GMT+0000 (Greenwich Mean Time)

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

; Network
;M551 P"" ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes backwards
M569 P1 S1 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E93.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X600 Y600 Z600 E600 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-5.5 Y-10 Z0 S1 ; set axis minima
M208 X220 Y220 Z250 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

; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-49 Y9 Z1.597 ; set Z probe trigger value, offset and trigger height
M557 X-15:165 Y20:230 S20 ; define mesh grid
;M557 X5:205 Y5:165 S20 ; Define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T98801 B4185 ; 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" T98801 B4185 ; configure sensor 1 as thermistor on pin e0temp
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 S280 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"Part Cooling" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"Heatsink/Hotend" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 C"PartCooling" S1 H1 T45 ; set fan 2 name and value. Thermostatic control is turned on

; Tools
M563 P0 S"PrintHead01" 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 S1 B57600 ; enable support for PanelDue
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool

PRIOR123

@jay_s_uk This has stopped the warning sign! thank you

jay_s_uk

@prior123 all sorted now?

PRIOR123

@jay_s_uk

the homing error is fixed but the x and y positioning when homing the Z via home all isnt working

jay_s_uk

@prior123 because you're in absolute mode. Surely X-38 Y-10 is off your bed or even outside your axis limits

PRIOR123

@jay_s_uk so should i comment out that line then? sorry im pretty unknown when it comes to programming

jay_s_uk

@prior123 well where do you want the nozzle to move to when you do the G30?

PRIOR123

@jay_s_uk probably X-60 and Y-10

But i just changed that in the homeall.g and it doesnt seem to be doing anything

jay_s_uk

@prior123 how? That's way outside your bed limits set in M208 in your config

PRIOR123

@jay_s_uk this has helpe massively! thank you.

How can i work out the true measurements essentially ive defined it all no with

M208 X60 Y-10 Z0 S1 ; set axis minima
M208 X235 Y235 Z260 S0 ; set axis maxima

however im not trying to define the mesh coordinates and i am continuously getting this

Warning: Skipping grid point X=200.0, Y=180.0 because Z probe cannot reach it
Warning: Skipping grid point X=220.0, Y=180.0 because Z probe cannot reach it
Warning: Skipping grid point X=220.0, Y=200.0 because Z probe cannot reach it
Warning: Skipping grid point X=200.0, Y=200.0 because Z probe cannot reach it

PRIOR123

@prior123 the Z probe can go further im just really confused why it thinks it cant

jay_s_uk

@prior123 your z probe has an offset of x-49. That means it can probe any further than 49mm before your x maximum. So with a maximum of 235, you can only probe up to X186 (otherwise the nozzle will have to go outside the machine limits)

PRIOR123

@jay_s_uk said in Z axis not homing:

235

sooo close now

ive recalibrated the Z probe, and redefined both the bed size and mesh size.

I have just one last issue it still wont hit the last point on the bed and throws out an error before continuing the rest of the G32 code

G31 P500 X-43 Y10 Z3.79 ; set Z probe trigger value, offset and trigger height
M557 X60:260 Y30:245 S20 ; define mesh grid

i thought it may have been the S value but that doesnt seem to make sense as 20 goes into 260

any more ideas?

jay_s_uk

@prior123 what error does it throw

PRIOR123

@jay_s_uk
G32
Warning: Skipping grid point X=240.0, Y=30.0 because Z probe cannot reach it
Warning: Skipping grid point X=260.0, Y=30.0 because Z probe cannot reach it
Warning: Skipping grid point X=260.0, Y=50.0 because Z probe cannot reach it
Warning: Skipping grid point X=240.0, Y=50.0 because Z probe cannot reach it

jay_s_uk

@prior123 again, you cant probe those points because your nozzle will go outside your axis limits. Based on 260, the closest you can go is X217

fcwilt

@prior123 said in Z axis not homing:

@jay_s_uk
G32
Warning: Skipping grid point X=240.0, Y=30.0 because Z probe cannot reach it
Warning: Skipping grid point X=260.0, Y=30.0 because Z probe cannot reach it
Warning: Skipping grid point X=260.0, Y=50.0 because Z probe cannot reach it
Warning: Skipping grid point X=240.0, Y=50.0 because Z probe cannot reach it

If the warnings are in response to G32 we need to see your bed.g file.

Do you understand how the probe X and Y offsets limit where the probe can reach?

And, just FYI, I find it easier to use the P parameter for M557 rather than the S parameter. I care more about the number of grid points rather than the actual spacing of the grid points.

Frederick

PRIOR123

@fcwilt said in Z axis not homing:

557
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 15:54:40 GMT+0000 (Greenwich Mean Time)
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation

What would i put for the M557 if it wasnt using an S value? i only put an S value because it feels easier to understand if i know the distance

PRIOR123

@jay_s_uk

So i know what you are saying but am i changing the

M557 X60:260 Y30:245 S20

to

M557 X217:260 Y30:245 S20 ?

fcwilt

@prior123 said in Z axis not homing:

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 15:54:40 GMT+0000 (Greenwich Mean Time)
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation

Strictly speaking you are not using bed.g as it was intended.

G32 is the command for bed leveling, be it manual or automatic. G32 invokes bed.g.

G29 is the command for mesh bed compensation. G29 invokes mesh.g

The DWC has menu items for G32 and G29. If you follow the convention above then the actions performed using the DWC will match what the DWC menu items say.

What you have will certainly work, it is just "out of sync" with the conventions and the DWC menu items.

To follow the convention you would simply create the file mesh.g and move into it the commands you currently have in bed.g.

What would i put for the M557 if it wasnt using an S value? i only put an S value because it feels easier to understand if i know the distance

For example If, instead of Snn, I put P20 the firmware generates a 20 x 20 grid. If I put P20:10 it generates a 20 x 10 grid.

To me the number of points is of greater interest than the exacting spacing of the points.

Frederick