Mesh levelling on 3.1.1
-
@fcwilt 0.00 is what shows up in web control
-
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Oct 20 2020 12:22:07 GMT+1100 (Australian Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-265 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000 ; go back a few mm
G1 H1 X-265 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning -
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Oct 20 2020 12:22:07 GMT+1100 (Australian Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y-265 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F6000 ; go back a few mm
G1 H1 Y-265 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning -
@lael said in Mesh levelling on 3.1.1:
G31 -0.777 ; set the z height at which the probe will recognise it's z
That line is incorrect.
You should have at least the P X Y and Z parameters but you have none and a value all on it's own.
Frederick
-
@lael said in Mesh levelling on 3.1.1:
@fcwilt 0.00 is what shows up in web control
If you comment out the G92 Z0 in homeall.g what value is displayed?
Thanks.
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Oct 20 2020 12:22:07 GMT+1100 (Australian Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F600 ; increase (drop) Z relative to current position by 5mm @300mm/min (5mm/sec)
G1 H1 Z-265 F600 ; decrease Z until the endstop is triggered @10mm / sec
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
G1 H2 Z5 F300 ; lift Z relative to current position - Z=5 @6000mm/min (100mm/sec)
G1 H1 Z-10 F180 ; move Z down until the endstop is triggered @3mm/sec; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
start.g
G28 ;home all axis
G0 X130 Y130 Z10 ; go to bed center, 10mm above
G30 ; probe for datum ref point
G29 S1 ; Load Grid Compensation
T0 ; Selects Tool 0 (active temp)
M703 ; Ensure filament specific settings are loaded
G1 X10 Y10 ; move close to origin -
G28 ;Home All Axis
G92 E0 ;zero extruded lengthG0 X0 Y0 F9000 ; Go to front
Slicer Start G Code:G0 Z0.20 ; Drop to 0.2 above bed
G92 E0 ; zero the extruded length
G1 X40 E35 F600 ; Extrude 35mm of filament in a 4cm line @600mm/min 60mm/sec
G92 E0 ; zero the extruded length
G1 E-1 F30 ; Retract a little
G1 X80 F4000 ; Quickly wipe away from the filament lineG0 F3600 X20 Y20 ;rapid movement to X20, Y20
I had G29 S1 which was removed after creating the start.g macro
-
@fcwilt 0.71mm
-
@lael said in Mesh levelling on 3.1.1:
@fcwilt 0.71mm
OK so the end stop triggers are 0.71 and at the point the Z axis stops moving.
Is that the actual Z position of the nozzle.
If you include the G92 Z0 you are telling the firmware that the Z position is 0.
So where exactly is the nozzle tip - at Z = 0.71 or Z = 0.00 or perhaps something else?
Thanks
Frederick
-
Can we see the code that you use to create the height map?
Thanks.
Frederick
-
@fcwilt so far I've just been running through the mesh levelling tutorial / example and haven't made a macro for it. To remap I've gone through the entire procedure manually.
In terms of the nozzle tip, you mean relative to the bed?
-
@lael said in Mesh levelling on 3.1.1:
I've gone through the entire procedure manually.
Did you do a G30 prior to the G29 that actually started the probing of the bed?
In terms of the nozzle tip, you mean relative to the bed?
Yes.
Frederick
-
@fcwilt said in Mesh levelling on 3.1.1:
@lael said in Mesh levelling on 3.1.1:
I've gone through the entire procedure manually.
Did you do a G30 prior to the G29 that actually started the probing of the bed?
yes
In terms of the nozzle tip, you mean relative to the bed?
The bed is quite warped, but at the center where I run the G30's for printing etc, it is just the right height above the bed to grip a piece of paper lightly. So I guess ~0.1 or a little less or so.
-
If you are going to use the G92 Znnn command you should determine as best you can what the actual nozzle position is and use that value.
Did you correct your G31 command and include the P X Y and Z parameters?
Frederick
-
So what is the relationship between all of the Z points?
Here is my understanding so far:
G92 Z0 sets printing 0 - so the firmware is expecting 0 to be where the nozzle should be when putting down the first layer.
G31 sets the location where the probe will be triggered - so in my case it is a piezo sensor which is triggered when the nozzle impacts the bed. So a -0.7mm makes sense as that is when the nozzle will actually contact the bed?
Home Z will move the head/bed (bed in my case) to the end stop, which will reference that location as zero.
Then mesh compensation will apply the additional compensation it has found above or below the Z point. The G30 datum point - sets the location at which the mesh map will be applied from? or does it overrride the G31 in config.g?
-
@lael said in Mesh levelling on 3.1.1:
The G30 datum point - sets the location at which the mesh map will be applied from? or does it overrride the G31 in config.g?
G30 uses the trigger height from G31
Usually when you have a probe, you don't use a Z min endstop at all. You use the probe for homing Z and creating the mesh. That way the Z0 reference is always the same based on the probe.
-
@lael said in Mesh levelling on 3.1.1:
G92 Z0 sets printing 0 - so the firmware is expecting 0 to be where the nozzle should be when putting down the first layer.
It's essential that the firmware knows the actual position of the nozzle on the X, Y and Z axes. For the Z axis that position can be set using an end stop or a Z probe. While the end stop references the frame, the Z probe references the bed which is better because any changes due to the heating of the bed are compensated for with each setting of the Z=0 datum.
G31 sets the location where the probe will be triggered - so in my case it is a piezo sensor which is triggered when the nozzle impacts the bed. So a -0.7mm makes sense as that is when the nozzle will actually contact the bed?
Not exactly. When the Z probe is triggered the Z trigger height value in G31 is used to set the firmware's Z position value so that the firmware "knows" where the nozzle is positioned on the Z axis. If the value in G31 is wrong the firmware's "knowledge" of the nozzle position will be wrong.
Home Z will move the head/bed (bed in my case) to the end stop, which will reference that location as zero.
Just as the G31 Z trigger height value is used to set the Z position value when the Z probe is triggered the G92 Znnn is used to set the Z position value when the end stop is triggered. Naturally the nnn value needs to match the actual Z position when the end stop is triggered.
Then mesh compensation will apply the additional compensation it has found above or below the Z point. The G30 datum point - sets the location at which the mesh map will be applied from? or does it overrride the G31 in config.g?
The G30 sets the Z=0 datum. The G29 probing is determining the Z difference at each probe point in reference to the point used for G30 - the differences can be plus or minus. Thus the same XY position must always be used when setting the Z=0 datum with G30.
Since the Z=0 datum determines the plus/minus Z values in the height map it is necessary to use G30 when creating the height map AND when loading the height map.
If for some reason the Z=0 datum used when creating the height map differs significantly from the Z=0 datum used when later loading the height map you can get the error about the Z offset.
I hope that covers it and I have'nt made any errors - it's late here.
Frederick
-
@fcwilt So if no G30 was used prior to loading a mesh map, what does it use as the datum? the value from G31, or maybe the current zero point?
-
@Phaedrux I know a lot of people don't, however, with a piezo they will trigger during travel moves as well, so while good as a probe are an unreliable z stop.
Plus, the way I have it set up if the probe fails, the optical end stop will stop the machine. If that sensor fails in the heated chamber, then the estop connected limit switch will prevent hardware damage.
