Z height and baby stepping in conflict?
-
Hello. I have noticed something:
In the image you can see the Z height reported by DWC. But that is the first layer being printed. It should be 0.2
In the capture you can see that I had to add a baby stepping of -0.45 (my Z offset was too heigh, I knew it from the beggining)
I have double checked the gcode and it is ok, first layer start printing at 0.2:
; head speed 10.000000, filament speed 0.000000, preload 0.000000
G1 X226.02 Y140.091 Z1.2 E0 F240
;
; 'Raft Path', 1.7 [feed mm/s], 9.1 [head mm/s]
G1 X136.682 Y206.799 E0 F12000
G1 X136.682 Y206.799 Z0.2 E0 F240
; 'Destring Prime'
G1 E1 F1125
; head speed 9.090909, filament speed 1.663007, preload 0.000000
G1 X136.671 Y206.681 E0.02167 F545.5So the gcode is actually being sent to 0.2
SO why Im readin on DWC a Z height of 0.45?
And it goes further: I can see the printing mving to layer number 2, and the Z height on the DWC is still 0.45?!
-
Baby stepping is an after the fact correction to get your to the correct position so it's not going to modify the expected height. Does that make sense?
-
@phaedrux but why im seeing those values on the interface?
-
Share your config.g, slicer start gcode, homing files, and the gcode file in question. Firmware and DWC version?
