Latest posts made by Plop
RE: persistent z-height offset
Thanks for your reply. Mesh compensation is used and I've followed the calibration steps on the website you linked. What confuses me is that, after the calibration steps are completed the nozzle touches the bed at z=0, as you'd expect. it's only for the print that the nozzle is in the wrong place.
homing files are attached.
The first few lines of the test print are here (I guess that includes the slicer start code?)
;Generated with Cura_SteamEngine 4.4.1
M82 ;absolute extrusion mode
G1 Z15.0 F6000 ;Move the platform down 15mm
;Prime the extruder
G1 F200 E3
G1 F1500 E-6.5
G0 F3600 X164.623 Y154.349 Z0.3
G1 F1500 E0
persistent z-height offset
I am working on a core XY printer that uses an IR z-probe for bed detection and levelling. The z-probe presently measures against a layer of blue tape. My config.g is attached.
The problem I experience is that, whilst when I move the nozzle to z=0 it reliably touches the build plate - as intended. When printing though it always keeps a approx. 3-5mm distance from the build plate.
I've measured the z-probe's offset a number of times (at the correct bed and nozzle temperatures) and, for a given set of trials the number in config.g is repeatable. Strangely though, if I try the same series of measurements a few days later that number changes by a few mm.
When trying to calibrate the z-probe's offset the value provided by the z-probe remains the same. I mention this as, when homing the z-axis, the z-probe reading fluctuates quite a bit, without environmental variables (be they related the printer or surrounding lighting) changing at all.
The above made me wonder if I use the wrong z-probe. The bed is aluminium and I appreciate that picking an IR probe for this arrangement was not the smartest move. This said, I would have hoped the blue tape avoided reflectivity problems.
Even taken the above into account, it is still the case that the height above the bed at which the nozzle tries to print seems consistent, seemingly independently of the z-trigger height.
Any comments and suggestions?
z-stop not triggering
Newby here, I'm afraid. I've got a DuetWifi board for a core XY printer. The z-min stop for some reason is not triggering when I query it (x and y are fine).
It is not the wiring or the switch as it is recognised by the software if connected to either x-min or y-min stops. Is there something wrong with the DuetWifi board? Do I need to re-map the input read by the software (i'm not using the max-endstops)? If so, how do I go about this?
I use the 2.02 firmware version