Z axis not homing
-
@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 maximahowever 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 the Z probe can go further im just really confused why it thinks it cant
-
@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)
-
@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 gridi thought it may have been the S value but that doesnt seem to make sense as 20 goes into 260
any more ideas?
-
@prior123 what error does it throw
-
@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 -
@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
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@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 itIf 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
-
@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 compensationWhat 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
-
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 ?
-
@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 compensationStrictly 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
