BL-Touch - multiple problems -

dutti

M98 P"config.g"
Error: M569: Response timeout: CAN addr 1, req type 6018, RID=108
Error: M569: Response timeout: CAN addr 1, req type 6018, RID=109
Error: M569: Response timeout: CAN addr 1, req type 6018, RID=110
Error: M350: Response timeout: CAN addr 1, req type 6021, RID=111
Response timeout: CAN addr 1, req type 6021, RID=112
Response timeout: CAN addr 1, req type 6021, RID=113
Error: M906: Response timeout: CAN addr 1, req type 6017, RID=114
Response timeout: CAN addr 1, req type 6017, RID=115
Response timeout: CAN addr 1, req type 6017, RID=116
Error: M557: bad grid definition: Too many grid points; suggest increase spacing to 31.8mm
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 404C

PaulHew

@barbarossa-cologne said in BL-Touch - multiple problems -:

; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"^io7.in" H15 F120 1400 ; set Z probe type to bltouch and the dive height + speeds

If this is from your current config.g, you need to swap the lines round. M558 before M950

HTH

Paul

PaulHew

Mine from a DUET2 for comparison

M558 P9 C"^zprobe.in" H5 R1 F120 T6000 A5 S0.02  ;BLTouch connected to Z probe IN pin
M950 S0 C"duex.pwm1"				             ;BLTouch Servo (S0) on duet pwm1
G31 X2 Y42 Z0.513 P25                            ; Customize your offsets appropriately - do a paper test, and put the probed value in the Z value here

JoergS5

@barbarossa-cologne said in BL-Touch - multiple problems -:

Error: M557: bad grid definition: Too many grid points; suggest increase spacing to 31.8mm

I checked it, from 15 to 650 are 21.16 points, so if it is rounded down to 21 it would reach the 441 limit of Duet 2 (limit of Duet 3 is not known to me). So reducing 650 a bit or S bigger than 30 would be the safe side.

dutti

@JoergS5
I reduced the amount...

@PaulHew
I changed it. Same problem.....

dutti

The software is homing Z without triggering anything. That´s really confusing for me..

dutti

@PaulHew
Like this?
; Endstops
M574 X2 S1 P"!io3.in" ; configure active-high endstop for high end on X via pin !io3.in
M574 Y2 S1 P"!io0.in" ; configure active-high endstop for high end on Y via pin !io0.in

; Z-Probe
M558 P9 C"^io7.in" H15 F120 T1400 ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:650 Y15:650 S30 ; define mesh grid

JoergS5

@barbarossa-cologne the CAN errors mean your Duet misses the expansion board.

You should set X and Y offsets for BLTouch in G31. This is described with an example in https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+5:+Upgrades/54#s231
G31 Z value means trigger height, 2.5 mm seens too low, please try a higher value.

dutti

@JoergS5
Done.
In general I know About the settings. The main problem is that its not deploying or retracting. Also the software is crazily homing without triggerning the BL.
Selftest ist working

dutti

@JoergS5
Trigger height - 4 --> not working.
Is it a big problem that I haven´t connect the expansion board?

JoergS5

@barbarossa-cologne you can check the core position of BLTouch. This is the allen hex screw on top of the BLTouch. It is turnable by 180° to change deploy-retract distance.
https://www.antclabs.com/bltouch-v3
the picture " Correct position of Core (V3.x)" the black core's position can be changed by turning the screw with an inbus (Allen key).

JoergS5

@barbarossa-cologne said in BL-Touch - multiple problems -:

@JoergS5
Is it a big problem that I haven´t connect the expansion board?

I don't have this board, I don't know, it was only a comment about why the error message appeared.

dutti

@JoergS5
I tried to turn in almost 20 positions. Not working....

JoergS5

@barbarossa-cologne you posted the wiring as
Wiring:
BL ---------Duet
White - io7.in
Black - GND
Yellow - io7.out
Red - 5v

but the BLtouch has 5 cables, 2 for endstop and 3 for servo. You can check whether cabling is ok by controlling the match. In my experience the colors of the cables are sometimes wrong, so I would look the original positions on the 5-pin-connector *) on the BLTouch and compare them with yours, then check that they are connected correctly to the Duet 3 pins.

*) On my Smart 2.0, Smart 3.1 and Geetech clone: viewed from the back, pin down: from left to right brown-red-yellow-black-white. 3 servo + 2 endstop.

dutti

@JoergS5
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_Num_3

I wired like this....

JoergS5

@barbarossa-cologne my experience is that the colors are sometimes wrong, better check the positions on the 5-pin-connector to be sure. I saw an image in the internet of the antclabs where black and white were exchanged. And the Creality ones cross a cable for the 3 pin connector.

dutti

@JoergS5
Without seeing the picture I thougth the same. I´ll try it on sunday.
Thanks for your help!!

Phaedrux

At this point I think you should try swapping from io7 to io4 or io5 just to try a different connection. Update the config as needed to point to the new connection.

And if that still doesn't work I would try connecting the BLTouch directly to the board with the short leads straight from the BTouch without the extension.

If that still doesn't work I would get another BLtouch to test with.

dutti

@Phaedrux
Ok. I'll do it on Sunday!
I have a cheap Chinese BL fake at home. Should I take this BL at last try?
Is there any other sensor you can recommend if it's not working?
The duet one?

Phaedrux

The BLtouch is a good probe when it's working. It's surface agnostic and a contact probe and it's quite accurate and repeatable when configured correctly. It's the most popular option for a reason.

The IR Probe is also very good, but your print surface must be compatible with the IR sensor.