BL-Touch - multiple problems -

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.

dutti

@Phaedrux
ok. Then I´ll do everything to become the BL to work.

dutti

@JoergS5
Changing the cable order wasn´t helpful.
There is also the problem that the duet homes the z axis. Also when the BL isn´t connected.
@Phaedrux

dutti

; 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 X20 Y100 Z4 ; set Z probe trigger value, offset and trigger height
M557 X15:650 Y15:650 S60 ; define mesh grid

JoergS5

@barbarossa-cologne from documentation, setting lower P for G31 seems better:
G31 P25 X20 Y100 Z4

and
M558 P9 C"io7.in" H15 F120 T1400
without the ^, because Duet 3 IO ports all have pullups already.

https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Duet_3_endstop_inputs each IO of Duet 3 has already pullup resistors: "Endstop devices can be connected to the IO_0 through IO_9 connectors. Each endstop input has a 27K pullup resistor, so the endstop devices only need to sink 0.12mA."

You wrote above, that removing ^ didn't work, but how did you mention, maybe it was the wrong P of G31 or some other cause.

dutti

@JoergS5
ITS WORKING!!!!!!
I connected the BL to IO4.
I think the IO7 connector isn´t working.
Refund Duet???
I´m not sure about the ´´^ ´´. Let it like this and its working now.

JoergS5

@barbarossa-cologne I am glad to hear that!!

dutti

@JoergS5
And NO. I´m a Idiot. the ´´^ `` must be deleted. Thanks Jörg and @Phaedrux

dc42

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

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

M98 Pconfig.g

´´´Response to long, see console´´.

So switch to the Console page of DWC to see the messages.

I havent connected the expansion board, yet. Is this a problem?

You will get some error messages from running config.g if it refers to ports on an expansion board that isn't connected.

Phaedrux

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

@JoergS5
And NO. I´m a Idiot. the ´´^ `` must be deleted. Thanks Jörg and @Phaedrux

So you're able to use io7 when removing the ^?

dutti

@dc42
ok. problem solved.
thanks

dutti

@Phaedrux
no IO7 is dead. with or without. no retract or deploy

JoergS5

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

@Phaedrux
no IO7 is dead. with or without. no retract or deploy

I would make an image from the soldered side of io7 and publish so it can be valued whether it may be a soldering problem.

dutti

@JoergS5
ok. I´ll do it!

Phaedrux

In addition to the photos can you also provide the following:

The output of M122
The output of M98 P"config.g"
Your current config.g

Also please do this test and report the results:

Send M950 J5 C"io7.in", then read the state of the pin by sending: echo sensors.gpIn[5]

Do this both with and without a jumper shorting io7.in to ground.

Result should be 0 with the jumper, 1 without