BLTouch on Duet2Wifi / TEVO Little Monster

avery1701

This was working on firmware 2.05.1 and just upgraded to 3.1.1. The BLTouch will deploy (M401) and retract (M402) and enter test mode (M280 P0 S120), but when I enter G30 it fails with "Error: Z probe already triggered at start of probing move" without ever deploying the probe.config.g

retractprobe.g homedelta.g deployprobe.g

Veti

change to

M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds

M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp

your thermistor config is incorrect. find the correct beta value in your thermistor documenation.

M665 R155 L397.19 B155 H520 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them

this is not the result of delta calibration, and you are not overwriting these settings with M501

avery1701

I cannot run delta calibration because G30 fails. Bed and nozzle heating are working correctly.

Veti

@avery1701 said in BLTouch on Duet2Wifi / TEVO Little Monster:

I cannot run delta calibration because G30 fails. Bed and nozzle heating are working correctly.

but you dont have the values from your 2.05.1 firmware?

Phaedrux

@Veti said in BLTouch on Duet2Wifi / TEVO Little Monster:

M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds

Fixing that should allow G30 to work.

The exclamation point you have in there means invert the signal, so when you go to try to probe with G30, it's already triggered.

avery1701

@Phaedrux said in BLTouch on Duet2Wifi / TEVO Little Monster:

M558 P9 C"^zprobe.in" H5 F120 T6000

That fixed it. Thanks @Phaedrux! That line was automatically generated by the configuration, but I am not sure what I selected to cause it to add the inverted zprobe flag. The config looks nothing like the 2.05.1 firmware config.

Phaedrux

@avery1701 said in BLTouch on Duet2Wifi / TEVO Little Monster:

The config looks nothing like the 2.05.1 firmware config.

Yes, RRF3 is a bit different. Mainly in how pins are assigned and how heaters and fans are defined. Overall it is more logical and flexible.

You can see more on what has changed here: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview

Phaedrux

@avery1701 said in BLTouch on Duet2Wifi / TEVO Little Monster:

That line was automatically generated by the configuration, but I am not sure what I selected to cause it to add the inverted zprobe flag.

On the IO mapping page in the z probe section you would have selected Input pin: zprobe.in (inverted)