BLTouch Probe Won't Deploy

Charlie

@phaedrux said in BLTouch Probe Won't Deploy:

Are you using toolboards or expansion boards or just the 6HC?

I am using 6HC and an expansion board.

Do you need to be in G91 to run a G30? If I send a G90, then G30, I have the probing issue. If I send G91, then G30, it seems to probe. Is this my issue?

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

@phaedrux said in BLTouch Probe Won't Deploy:

This sets your dive height to 2mm, but your probe trigger height is over 3mm.
Do you see how that could be an issue?

Yes, I definitely see how that can be an issue. With that said, I set that value to 8mm and the issue persists.

In you homing files where you are using G30 you are invoking G30 twice.

Now this is not related to your problem but you don't really need to do it twice.

So, as a test, change the code so you only do it once and be sure the dive height is large enough.

As a reference my dive height setting is 5 and the Z trigger height setting is 1.8. and I always start probing at Z=10.

Frederick

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

Do you need to be in G91 to run a G30? If I send a G90, then G30, I have the probing issue. If I send G91, then G30, it seems to probe. Is this my issue?

I double checked my code to be sure and it is always put into G90 mode before do the G30.

Frederick

JoergS5

@charlie said in BLTouch Probe Won't Deploy:

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

Im not sure what this means. Please let me know if you would like to provide more information.

This was analysis of the firmware source code. It accepts 0 in the deploy/retract files and also K0. It was only a check, you don't need to do anything.

About your problem, I am currently thinking about whether moving -3 away from the endstop is maybe too low and not reset to no-contact or contact (I don't know your endstop), so the endstop may not trigger at the next slow move, which is G1 H1 and doesn't set the endstop triggered then.

E. g. such a type:

approached with high speed, 3 mm back may be too low.

Charlie

@fcwilt said in BLTouch Probe Won't Deploy:

In you homing files where you are using G30 you are invoking G30 twice.
Now this is not related to your problem but you don't really need to do it twice.
So, as a test, change the code so you only do it once and be sure the dive height is large enough.

Correct. I am using the first G30 to do a coarse home, and then the second G30 to do a fine home.

I tried doing one G30, and the probe still did not deploy.

@fcwilt said in BLTouch Probe Won't Deploy:

As a reference my dive height setting is 5 and the Z trigger height setting is 1.8. and I always start probing at Z=10.

What do you mean that you always start probing at 10mm? Isnt that dependent on your last print height?

Charlie

@fcwilt said in BLTouch Probe Won't Deploy:

I double checked my code to be sure and it is always put into G90 mode before do the G30.

Okay, thats the way that it used to work for me as well. Now the probe wont deploy unless I have a G91 before my M558 and G30 in my homez.g file.

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

@fcwilt said in BLTouch Probe Won't Deploy:

I double checked my code to be sure and it is always put into G90 mode before do the G30.

Okay, thats the way that it used to work for me as well. Now the probe wont deploy unless I have a G91 before my M558 and G30 in my homez.g file.

Did you remove the double G30s in the homing files?

Frederick

Charlie

@joergs5 said in BLTouch Probe Won't Deploy:

This was analysis of the firmware source code. It accepts 0 in the deploy/retract files and also K0. It was only a check, you don't need to do anything.

Okay, thank you for doing that analysis!

@joergs5 said in BLTouch Probe Won't Deploy:

About your problem, I am currently thinking about whether moving -3 away from the endstop is maybe too low and not reset to no-contact or contact (I don't know your endstop), so the endstop may not trigger at the next slow move, which is G1 H1 and doesn't set the endstop triggered then.

Im assuming that youre referring to the G1 H0 X-3 F6000 in my homex.g file and G1 H0 Y-3 F6000 in my homey.g file. My switches are Omron 653-D2F-5L. It has 0.5mm of movement differential, but it couldnt hurt to try 5mm.

Charlie

@fcwilt said in BLTouch Probe Won't Deploy:

Did you remove the double G30s in the homing files?

No, just put G91 before the M558 and G30s. Here is the new homez.g file that appears to work.

; Voron.
; 0:/sys/homez.g
; Called to home the Z axis via G28 Z.
; 2020/10/24/20:02

G91                   ; Set axes (not extruders) to relative positioning mode.
G1 H2 Z5 F6000        ; Lift Z relative to current position.
G90                   ; Set axes (not extruders) to absolute positioning mode.
G1 X175 Y151.5 F6000  ; Move X and Y axes so the Z probe is at the center of the bed.
G91
M558 F600 H2 A1       ; Set Z probe. Feed rate: 600 mm/min. Dive height: 2 mm. Times to probe: 1.
G30                   ; Z probe quickly (1 of 2 passes).
M558 F120 H5 A1       ; Set Z probe. Feed rate: 120 mm/min. Dive height: 5 mm. Times to probe: 1.
G30                   ; Home Z by probing the bed slowly (2 of 2 passes).
G90

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

Im assuming that youre referring to the G1 H0 X-3 F6000 in my homex.g file and G1 H0 Y-3 F6000 in my homey.g file. My switches are Omron 653-D2F-5L. It has 0.5mm of movement differential, but it couldnt hurt to try 5mm.

As long as the movement is adequate to insure the endstop sensor is no longer activated your good.

But it has nothing to do with your G30 issue. The first G1 H1 marks the axis as homed. The second one may (or may not) make the stopping position a bit more accurate but that is all it does.

Frederick

Charlie

With the modification to the homex.g file to include G91 before the M558, the probe is working intermittently. Any other considerations that Im not making? Could interference be a part of the problem?

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

With the modification to the homex.g file to include G91 before the M558, the probe is working intermittently. Any other considerations that Im not making? Could interference be a part of the problem?

I would try this.

In the config.g file set your M558 to the values you want to use during probing.
Remove/comment out both M558s and one G30 in your home Z file
Reset
Home X
Home Y
Home Z

Frederick

Charlie

@fcwilt

Thank you for your response. Unfortunately I tried this already, and it failed to deploy. Also, when performing a G29, the probe extended on the first probe point, but failed to deploy on the second one.

Phaedrux

@phaedrux said in BLTouch Probe Won't Deploy:

Are you using toolboards or expansion boards or just the 6HC?

Charlie

@phaedrux
Yes, I am using a Duet 3 Expansion board 3HC

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

@phaedrux
Yes, I am using a Duet 3 Expansion board 3HC

Move your connection to the 6HC to rule out any problems with communications to the 3HC or the 3HC itself.

Frederick

Charlie

@fcwilt said in BLTouch Probe Won't Deploy:

Move your connection to the 6HC to rule out any problems with communications to the 3HC or the 3HC itself.

It is.

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

@fcwilt said in BLTouch Probe Won't Deploy:

Move your connection to the 6HC to rule out any problems with communications to the 3HC or the 3HC itself.

It is.

Did you try it with the 3HC disconnected?

Frederick

Charlie

@fcwilt
Issue persists with 3HC disconnected at the can port and with the fuse removed.

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

@fcwilt
Issue persists with 3HC disconnected at the can port and with the fuse removed.

This is just bizarre.

I did a number of tests on my printer, but it was with a Duet 2 WiFi board, and I could not create any conditions, short of incorrect code, to cause the probe to fail.

I do have a 6HC. It won't be hard to hook up one of my spare BLTouch.

But that is for tomorrow.

Frederick