G32 w BLTouch and Z-endstop

jontek2

Hey!

Finally upgraded to a duet 2 wifi from an Smoothieware on a MKS SBase 1.3 and i'm having some issues with my BLTouch. I'm running a BLTouch v3 and a Z-min endstop on a Hypercube with the 220x220 dimensions.

I've got it wired up and can trigger the BLTouch with the following commands:

Pin down: M280 P3 S10 I1
Pin up: M280 P3 S90 I1

However, when i run G32 for auto bed leveling the printer goes to X135 and Y10 and then tries to probe the bed. The first probe is fine, but then the alarm is triggered and it failes:

Error: Z probe was not triggered during probing move

Here's a video showing the problem. I'm executing the G32 command.
https://imgur.com/a/HOQz1KX

Any ideas?

I'm adding my config.g:

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.0.5 on Thu Oct 31 2019 00:59:28 GMT+0100 (centraleuropeisk normaltid)

; General preferences
G90                                     ; send absolute coordinates...
M83                                     ; ...but relative extruder moves
M550 P"Hypercube"                       ; set printer name

M667 S1                                 ; select CoreXY mode

; Network
M551 P"password"                        ; set password
M552 S1                                 ; enable network
M586 P0 S1                              ; enable HTTP
M586 P1 S0                              ; disable FTP
M586 P2 S0                              ; disable Telnet

; Drives
M569 P0 S0                              ; physical drive 0 goes forwards
M569 P1 S0                              ; physical drive 1 goes backwards
M569 P2 S1                              ; physical drive 2 goes forwards
M569 P3 S1                              ; physical drive 3 goes backwards
M584 Y0 X1 Z2 E3                        ; set drive mapping
M350 X256 Y256 E256 I0                  ; configure microstepping without interpolation
M350 Z16 I1                             ; configure microstepping with interpolation
M92 X1280.00 Y1280.00 Z400.00 E6984.63  ; set steps per mm
M566 X600.00 Y600.00 Z12.00 E120.00     ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00     ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1300 E800 I30         ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                        ; set axis minima
M208 X200 Y200 Z150 S0                  ; set axis maxima

; Endstops
M574 X1 Y1 Z1 S0                        ; set active low and disabled endstops

; Z-Probe
M557 X5:170 Y5:170 S20 			; Define mesh grid
M558 P9 H5 F1000 T4000 X0 Y0 Z0          ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves
G31 P25 X30 Y15 Z5.0                    ; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment

; Heaters
M305 P0 T100000 B4138 R4700             ; set thermistor + ADC parameters for heater 0
M143 H0 S120                            ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700             ; set thermistor + ADC parameters for heater 1
M143 H1 S280                            ; set temperature limit for heater 1 to 280C
M307 H3 A-1 C-1 D-1			; Disable the 3th Heater to free up PWM channel 5 on the Duex board.
M307 H4 A-1 C-1 D-1 			; Disable heater 4 to be used to control brush servo

; Fans
M106 P0 S0 I0 F500 H-1                  ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0 I0 F500 H-1                  ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 C"FAN3" S0 I0 F500 H-1          ; set fan 2 name, value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F-1                       ; define tool 0
G10 P0 X0 Y0 Z0                         ; set tool 0 axis offsets
G10 P0 R0 S0                            ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

aidar

May i ask why G32 and not G29?
https://duet3d.dozuki.com/Wiki/Gcode#Section_G29_Mesh_bed_probe

jontek2

I'm used to G32 from Smoothie.

Just tried G29 and it does the exact same as in the video..

fcwilt

Hi,

Did you create the deployprobe.g and retractprobe.g files?

G32 has it's uses for bed leveling but for creating the height map used by mesh compensation (which deals with bed irregularities) you use G29.

Frederick

jontek2

Thanks! I'll start using G29 instead.

Yes, i've created the two files:

Deployprobe.g
M280 P3 S10 I1

Retractprobe.g
M280 P3 S90 I1

fcwilt

Hi,

So all is working now?

Frederick

jontek2

No.

I had the two files already and i'm getting the same result (as in the video) with G29.

fcwilt

Hi,

When I specified the area to be probed I had to take into account my Z-probe offsets.

Frederick

jontek2

I've also done that, see the config above.

fcwilt

@jontek2 said in G32 w BLTouch and Z-endstop:

I've also done that, see the config above.

Well you are cutting the X axis a bit close but I guess it's ok.

Clearly something is wrong as the probe is deployed while moving.

Do M401 and M402 work correctly?

jontek2

The M401 did deploy the probe and M402 retracted it.

Any examples of how your BLTouch is configured?

Could I have wired it wrong?

jontek2

Either there is something wrong with the wiring, however i doubt that since all of the commands are working.

Therefore it must be something wrong with the configuration.

What i've done is:

Wired the BLTouch
Added the two files
Added the following code:

; Z-Probe
M557 X5:170 Y5:170 S20 			; Define mesh grid
M558 P9 H5 F1000 T4000 X0 Y0 Z0          ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves
G31 P25 X30 Y15 Z5.0                    ; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment

Is there something i'm missing?

fcwilt

@jontek2

Hmm...

You have X0 Y0 Z0 parameters in M558.

According to the docs they are obsolete so try removing them.

And if you are not using the most recent firmware upgrade and see if that makes a difference.

Frederick

jontek2

Thanks. There's seems to be an update to it in the latest firmware.

I just redid all of the wiring to the BLTouch and got it working The crimping must have gone bad in one of the signal-wires.

But got some new errors:

Warning: Skipping grid point (0.0, 0.0) because Z probe cannot reach it

It should be able to probe at 0, 0 since the offset is 30 and Y.

fcwilt

@jontek2 said in G32 w BLTouch and Z-endstop:

It should be able to probe at 0, 0 since the offset is 30 and Y.

M557 shows X5:170 Y5:170 S20

Why is it now trying to probe 0, 0?

Frederick

jontek2

Ok, here's an update:

I've got everything to work with the BLTouch and my config now is the following:

; Z-Probe
M558 P9 H5 F100 T2000			; Set Z probe type/mode 9. H=Dive Height. F=Speed the bed moves
G31 X30 Y15 Z1.688 P25			; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment

However i'm getting the following message when i'm trying to do a G29

 Error: G29: No valid grid defined for bed probing

My "Define Area for Mesh Grid Compensation" is the following:

Start coordinate in X direction: 0
End coordinate in X direction: 210
Spacing in X direction: 20
Start coordinate in Y direction: 0
End coordinate in Y direction: 210
Spacing in Y direction: 20

However, if try to enter G29 two more tries - it works. Is this a known bug or am I doing something wrong?

fcwilt

Hi,

What happened to M557 X5:170 Y5:170 S20?

Frederick

jontek2

170x170 was something i had in size from Smoothie.

M557 X5:170 Y5:170 S20

seemed to be something from an earlier firmware version.

fcwilt

@jontek2 said in G32 w BLTouch and Z-endstop:

170x170 was something i had in size from Smoothie.

M557 X5:170 Y5:170 S20

seemed to be something from an earlier firmware version.

I would put it back. It is taking into account the z-probe offsets, as it should.

Though I would be inclined to use X5:165 and Y5:185 to keep the z-probe away just a bit from X and Y max.

Frederick

jontek2

According to the documentation (https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe) the M557 commands is used for the Touch-Mi.