BLTouch Probe Won't Deploy

Charlie

@fcwilt
Im assuming that "reset" means sending an M999 command, or powering off the duet. In that case, X and Y works wonderfully when I home them individually. Furthermore, the X and Y portions of the Home All function work as intended as well.

Charlie

@joergs5
Unfortunately, this did not fix the issue. I appreciate the attempt though!

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

@fcwilt
Im assuming that "reset" means sending an M999 command, or powering off the duet. In that case, X and Y works wonderfully when I home them individually. Furthermore, the X and Y portions of the Home All function work as intended as well.

Great.

So with X and Y homed:

move X and Y to center of the bed either by jogging or issuing G1 commands
issue a G92 Z3 to force Z to be marked as homed (this allows jogging Z)
jog Z to 3 mm off the bed (now the logical and physical Z positions are in sync)
change to the DWC Console page
issue a G30

Post what happens.

Frederick

Charlie

@fcwilt
So I did this, but with one exception. I didnt jog the z to be 3mm off the bed, as I was concerned about crashing the nozzle.

The probe did not deploy, and the error: "Error: Probe was not triggered during probing move" was displayed on the console.

Charlie

@joergs5 said in BLTouch Probe Won't Deploy:

@charlie a last additional idea: M208 has Z minimum 0 and the BLTouch starts at 3 mm height. It may be that it cannot probe below 0 because of M208. This was changed in 3.4 somewhere if I remember correct, but if you use 3.3 firmware, it may be a try to set the M208 Z limit below 0.

Something odd happened that may help those smarter than I!

I issued an M208 S1 Z-100 command in the DWC console (which is along the lines of what I believed you asked me to do). I then issued a G30 command. Please keep in mind that this was after I did what @fcwilt asked, which was to issue a G92 Z3 command.

The print head seemed to move down around 3mm, and then the probe deployed.

fcwilt

I made a post but came back to find your new post.

I need to think.

fcwilt

@charlie

OK what are your current probe configuration commands (M950 M558 G31)?

Frederick

Charlie

@fcwilt
Here is the current Z Probe section of the config.g file, containing the M950, M558, and G31.

; Z Probe

M558 K0 P9 F120 H3 R0 T6000 A1 B0 C"0.io4.in"  ; Set Z probe type.
                                               ; K (Z probe number): 0 (1).
                                               ; P (Z Probe type): 9 (BLTouch probe).
                                               ; F (Feed rate. Probing speed [mm/min]): 120.
                                               ; H (Dive height [mm]): 3.
                                               ; R (Recovery time [seconds]): 0.
                                               ; T (Travel speed [mm/min]): 6,000.
                                               ; A (Max number of times to probe each point): 1.
                                               ; B (Heaters): 0 (Leave all heaters on while probing).
                                               ; C (Endstop input): 0. (Mainboard) io4.in.

M950 S0 C"0.io4.out"                           ; Create GPIO/servo pin.
                                               ; S (Output/servo pin number): 0.
                                               ; C (Pin name): 0. (Mainboard) io4.out.

G31 P500 X0 Y22.0 Z3.105 K0                    ; Set Z probe.
                                               ; P (Trigger value): 500.
                                               ; X (Probe X offset [mm]): 0.
                                               ; Y (Probe Y offset [mm]): 22.000.
                                               ; Z (Probe Z offset [mm]): 3.105 (This is modified for Z probe calibration. A higher offset number moves the nozzle closer to the bed.).
                                               ; K (Z probe number): 0.

M557 X25:325 Y25:313.5 P3                      ; Define Z probe mesh grid (This is the probe point grid, not the nozzle grid).
                                               ; X (Min:Max X coordinates to probe [mm]): 35 (Min) : 325 (Max).
                                               ; Y (Min:Max Y coordinates to probe [mm]): 25 (Min) : 313.5 (Max).
                                               ; P (Points to probe in each direction): 3.

fcwilt

@charlie

Thanks.

Let's changes things just a bit:

M950 S0 C"0.io4.out"
M558 P9 C"0.io4.in" H3 T6000 F120 A1 R0.2 B0
G31 P25 X0 Y22.0 Z3.105

Reset and try what I suggested before BUT lets use G92 Z7 instead of G92 Z3

Frederick

Charlie

@fcwilt
Same problem. Probe did not deploy. Same error: "Error: Probe was not triggered during probing move"

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

Same problem. Probe did not deploy. Same error: "Error: Probe was not triggered during probing move"

And yet when you issued the M208 S1 Z-100 and then the G30 it seemed to work?

Frederick

Charlie

@fcwilt
This is correct, but I cant seem to replicate the scenario in which it worked.

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

@fcwilt
This is correct, but I cant seem to replicate the scenario in which it worked.

Well we are overlooking something simple.

Did you post what the DWC Z Probe readout value is?

Frederick

Charlie

@fcwilt
Z Probe readout value is 0, and remains 0 for the entire homing attempt.

Charlie

Im unsure as to whether this means anything, but the BLTouch light remains a solid red when the machine is idle, as well as before and during the homing process. Of course the light shuts off when I power off the machine to prevent crashing, but the probe also deploys when power is turned off while the Z probe is occuring.

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

Im unsure as to whether this means anything, but the BLTouch light remains a solid red when the machine is idle, as well as before and during the homing process. Of course the light shuts off when I power off the machine to prevent crashing, but the probe also deploys when power is turned off while the Z probe is occuring.

Well it's getting late and I've got to get some sleep.

Sorry we couldn't get it sorted in this session.

I will run some tests with my BLTouch and see I can determine what conditions could be causing your problems.

Talk to you later.

Good night.

Frederick

Charlie

@fcwilt

No worries, same here. Thank you so much for the time that you have put into this issue. I greatly appreciate it!

Im hoping that this isnt an interference issue that will require shielding.

Thanks again! Good night.

Charlie

@phaedrux

It is clear. I was just confused regarding the use of "Servo pin number" in M950 vs "Servo index" in M280. But honestly, thats more an issue with me.

Unfortunately, this issue persists.

Phaedrux

@charlie said in BLTouch Probe Won't Deploy:

M558 K0

Can you try without the K0? If you only have a single probe, best to leave it off.

Can you please share your full config.g?
What exactly do you have in your deployprobe.g and retractprobe.g files in the sys folder?
Does M401 and M402 work to deploy or retract the probe?
Does the probe deploy when you send G30?
Does the BLTouch pin deploy and retract when power is first applied?
How exactly is the BLtouch wired?
And The results of M122 and M98 P"config.g"?
Also send M558, G31, by themselves are see what they return.

JoergS5

@phaedrux said in BLTouch Probe Won't Deploy:

deployprobe.g and retractprobe.g files

I want to add that the filenames are deployprobe0.g and retractprobe0.g (so with 0 added), but I thought it is ok because of the K0.

The code is in GCodes3.cpp DeployZProbe() and RetractZProbe(), and looks ok.

The filenames must be all lowercase.