Bltouch with new firmware

mendenmh

The probe not being pushed all the way on the touch means you may have set your probe offset wrong. The printer will give up probing if it has to go below the programmed low limit on z. If you are zeroed just about where the probe would switch, it might give up too early.

Elliot

@mendenmh When i home all axis it works perfectly. However, when I try to probe for mesh bed that's when I get an issue

Elliot

Dont know if it is also related, I have seen two different lines for M558 which one is correct and what does the 'H','R', 'A', and 'B' stand for?

M558 P9 H9 F120 R0.2 T18000

M558 P9 F100 H5 R0.2 T6000 A5 B1

aidar

Looks like you should start reading here : https://duet3d.dozuki.com/Wiki/Gcode#Section_M558_Set_Z_probe_type

Elliot

@mendenmh Thanks. How would I go about changing this?

aidar

Some more reading will help: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

Elliot

@aidar thanks. It is always good to refresh myself on that. That helped alot.

The one remaining issue I have is that the probe goes down on the first location on the bed. Then it goes to the next, and deploys the probe it then doesn't retract. It will then just go to the positions and not try to probe. It then gets an error. If I manually lift the probe after it then goes to the next location and the same thing happens.

After this is done, the bed is not leveled at all.

Phaedrux

What are you using for your M558 right now?
Do you get any error messages in the console?

Elliot

@Phaedrux

The M558 I. Am using is:

M558 P9 H5 F120 R0.2 T3000

The error I get is:

Error: Z probe already triggered at start of probing move

dc42

What do you have in your deployprobe.g and retractprobe.g files?
Please confirm that you have none of the following commands in any of your homing files or in bed.g:

M98 Pdeployprobe.g
M98 Pretractprobe.g
M401
M402

You can send M401 and M402 manually to test whether probe deployment and retraction is working, but you should always start with the probe retracted before running a command that does probing.

Elliot

@dc42 Thanks. All worked out in the end.

Seems there was something physically wrong with my bltouch.

when testing it out a few days ago it didn't retract properly and got bent. I rebent it and now everything works perfectly. must have been stuck inside and this unstuck it.