BL-Touch - multiple problems -

dutti

@Phaedrux said in BL-Touch - multiple problems -:

M98 Pconfig.g

yes

Phaedrux

try M98 P"config.g"

dutti

@Phaedrux said in BL-Touch - multiple problems -:

M98 Pconfig.g

´´´Response to long, see console´´.
I havent connected the expansion board, yet. Is this a problem?

Phaedrux

Are you in the DWC gcode console when you send that?

dutti

@Phaedrux yes

dutti

I homed z again. It's homing without triggering manual the BL.

Also when I go down with the z axis... doesn't care which amount and then homing z, the z motors are turning back always the same amount and it stops.
--> I hope that helps

Phaedrux

I'm not exactly sure what you mean.

Looking back over your config.g I notice two things on your M558 command that we can try changing.

M558 P9 C"^io7.in" H15 F120 1400

First, you're missing the T in front of the 1400 to define the travel speed between probe points.

Second, try removing the ^ from in front of io7.in. I think it's only zprobe.in that requires the pullup.

I'd still like to see what the gcode console output is from sending M98 P"config.g" It should echo SOMETHING back.

dutti

M558 P9 C"io7.in" H15 F120 T1400 ----> doesn´t work

M98 P"config.g"
--> response to long, see console

Should I buy a other sensor?
My motivation after a few days is down.....

JoergS5

@barbarossa-cologne what does the console say? If you cannot read it, you can download it into a file:
https://duet3d.dozuki.com/Wiki/Duet_Web_Control_Manual#Section_G_Code_Console

dutti

@JoergS5

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).