BL-Touch - multiple problems -
-
@Phaedrux
What do you mean with ´´actually wired up to the ioin and out pins´´? -
I mean that your config looks ok, now the wiring must be correct for the config to work.
-
@Phaedrux
ok sry.
I tested the wiring. Its not the problem....
this is the last problem I have to solve before starting. Thats really bad. -
If that's the case and the wiring is good please update your firmware (as linked above for the Duet + SBC). Send M115 after to verify.
Then please send M98 Pconfig.g and report any errors.
-
@Phaedrux
M98 Error: Non-empty string expected
firmware is updated -
That's a weird error. You're sending this exactly?
M98 Pconfig.g -
-
try M98 P"config.g"
-
@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? -
Are you in the DWC gcode console when you send that?
-
@Phaedrux yes
-
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 -
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 1400First, 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.
-
M558 P9 C"io7.in" H15 F120 T1400 ----> doesn´t work
M98 P"config.g"
--> response to long, see consoleShould I buy a other sensor?
My motivation after a few days is down..... -
@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 -
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 -
@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 + speedsIf this is from your current config.g, you need to swap the lines round. M558 before M950
HTH
Paul
-
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 hereRailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
Voron 2.4 disassembled..... Waiting for the RailCore Mini.... -
@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.
-
