Changing dive height for bed probe

BoA

My issue: After powering up printer, the bed/gantry is not parallel to the XY plane. Let's say maximum difference can be like 20mm. Homing is in the middle of the bed, but... when after homing executing bed.g probing points next to lead screws creates posibility of collision with the bed. Moving to probing points with G30 does not check if probe is triggered during that move. Soo... dive height has to be large enough to make head far enough from bed during G32.

However.... After bed leveling is done, dive height could be reduced to 0.5mm to make bed probing for mesh (G29) much faster. Not sure how I can do that, as just stating M558 with H paramter returns an error

M558 H0.5
Error: M558: Z probe 0 not found

Any suggestion how this can be done properly?

Phaedrux

If it's getting that far out of level after power off perhaps adding some endstops on the Z axis to get it close first before using the probe would be a good option.

As for the M558 error, do you have multiple probes defined? Firmware version?

droftarts

@BoA Can you share your config.g, homing macro, and the macro that you call to do bed levelling?

Ian

BoA

Ahh.... forgot the basics.

Duet3 6HC standalone, RRF 3.4.6
No multiple probes - only one (super pinda).

config.g
homez.g
bed.g

droftarts

@BoA I can't see anything in those files that changes the probe, or cancels it. If you send M558 or M558 K0, it should report the probe settings. Perhaps do that between running each macro, and see when/if it disappears.

I don't think it's an issue with sending M558 H0.5; I can do that and then report the probe dive height has changed:

M558
Z Probe 0: type 8, input pin io3.in, output pin nil, dive heights 3.0,3.0mm, probe speeds 600,120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 5, max diff 0.03

M558 H0.5

M558
Z Probe 0: type 8, input pin io3.in, output pin nil, dive heights 0.5,0.5mm, probe speeds 600,120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 5, max diff 0.03

I'm on RRF 3.5.0-rc.2, but I don't think anything has changed in probing since 3.4.6.

Ian

BoA

@droftarts OK. I did exactly like You, and... it works. No idea why could not get that working yesterday. Thanks.