Bed Leveling compensates to 1.5~3.5 mm below printing surface
-
There is G90 in there so no need for G92 as much as I understand
-
as milangupta1 said. your bed config should look something like this (adjust for your bed)
and the M665 and M666 should be in the config.g; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v2.0.0 on Thu Aug 29 2019 14:53:59 GMT+0200 (Mitteleuropäische Sommerzeit)
M561 ; clear any bed transform
; Probe the bed at 12 peripheral and 0 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y84.9 H0 Z-99999
G30 P1 X42.45 Y73.53 H0 Z-99999
G30 P2 X73.53 Y42.45 H0 Z-99999
G30 P3 X84.9 Y0 H0 Z-99999
G30 P4 X73.53 Y-42.45 H0 Z-99999
G30 P5 X42.45 Y-73.53 H0 Z-99999
G30 P6 X0 Y-84.9 H0 Z-99999
G30 P7 X-42.45 Y-73.53 H0 Z-99999
G30 P8 X-73.53 Y-42.45 H0 Z-99999
G30 P9 X-84.9 Y0 H0 Z-99999
G30 P10 X-73.53 Y42.45 H0 Z-99999
G30 P11 X-42.45 Y73.53 H0 Z-99999
G30 P12 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed) -
sorry, I've labeled this incorrectly. M665 and M666 are in the config overide. Correcting post.
-
are you using mesh bed compensation?
i.e. loading the heightmap somewhere -
I've used it, but now its disabled.
-
-
@worekarolis
yes. loading it will change the z=0 based on the values in the heightmap. -
@veti
Removing it haven't changed behavior -
Hi,
The trigger height setting for your Z-probe might be wrong.
The H parameter to M665 might be wrong.
Either one can result in Z=0 not being the surface of the bed.
Frederick
-
After updating to 2.04RC1 (2019-07-14b1) issue is gone.
Many thanks for your help!
