Z Probe Sensor profile reading as 0

R3play

@jester said in Z Probe Sensor profile reading as 0:

M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0

Remove that line in config-override.g

Jester

I removed that line and still getting the same issue. It is still coming up with the manual bed probing also

R3play

@jester
This is what I have in my config.g file

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X31 Y-8 Z2.48 ; Set Z probe trigger value, offset and trigger height
M557 X15:195 Y15:195 S20 ; Define mesh grid

Try adding the M574 command and change the trigger value (P) in the G31 command to 25.

Besides that, does the pin deploys, retract, selftest and resets when sending the following commands?

Pin Down: M280 P3 S10 I1
Pin Up: M280 P3 S90 I1
Self-Test: M280 P3 S120 I1
Reset BLTouch + Pin Up: M280 P3 S160 I1

Jester

@r3play said in Z Probe Sensor profile reading as 0:

M574 Z1 S2 ; Set endstops controlled by probe

I added the M574 command and changed the value to 25 and still no luck, it responds to the testing commands though.

R3play

@jester Then I would have no clue what else could be wrong.
Going to leave this to the experts here.

Jester

Thanks for the help anyways

Phaedrux

What do you have in your deployprobe and retractprobe macro files?

Does the probe respond to M401 and M402?

The zProbe box in the DWC is not an accurate way to test the BLTouch because of the way that it triggers and instantly resets. The display may briefly flash to 1000 and then immediately go back to 0.

If the probe responds to M401 and M402, try doing a dynamic test by positioning the head far above the bed and issuing a G30 command to start a probe move. Trigger the probe pin by hand. If the movement stops, you're good to go. If it doesn't stop, kill the power to stop movement, and double check your wiring, because something isn't connected right.

dc42

Let me confirm my understanding of the original problem:

Hello, I have been trying to program my BL Touch for over a week now and when I run M558 it shows profile as 0

I took this to mean that if you send M558 without parameters, it says the probe type is 0. Is that right?

Which firmware version are you using? Probe type 9 was added several months ago, but if your firmware is very old then it won't support probe type 9.

Jester

@phaedrux said in Z Probe Sensor profile reading as 0:

What do you have in your deployprobe and retractprobe macro files?

Does the probe respond to M401 and M402?

The zProbe box in the DWC is not an accurate way to test the BLTouch because of the way that it triggers and instantly resets. The display may briefly flash to 1000 and then immediately go back to 0.

If the probe responds to M401 and M402, try doing a dynamic test by positioning the head far above the bed and issuing a G30 command to start a probe move. Trigger the probe pin by hand. If the movement stops, you're good to go. If it doesn't stop, kill the power to stop movement, and double check your wiring, because something isn't connected right.

it does respond to M401 and M402 but when I do a G30 it will just bring up manual bed compensation pop up

Jester

@dc42 said in Z Probe Sensor profile reading as 0:

Let me confirm my understanding of the original problem:

Hello, I have been trying to program my BL Touch for over a week now and when I run M558 it shows profile as 0

I took this to mean that if you send M558 without parameters, it says the probe type is 0. Is that right?

Which firmware version are you using? Probe type 9 was added several months ago, but if your firmware is very old then it won't support probe type 9.

I am currently on 1.21

Phaedrux

@jester 1.21 RC2 and above should support the P9 probe type. 1.21 is quite old at this point though. I'd suggest looking into updating to 2.02.

https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

Can you post your homing files as well? Do you happen to have an M558 command in them?

What happens if you send your complete M558 command in the gcode console and then send M558 again with no parameters. Does it read back type 0, or type 9?