Bltouch blinking red on Duet wifi+ Duex5 RRF 3

dc42

@Eman74 said in Bltouch blinking red on Duet wifi+ Duex5 RRF 3:

M950 S0 C"!exp.heater7" ; servo/gpio 1 is Z probe MOD pin ;M950 S0 C"duex.pwm5" ; create servo/gpio 0 on pwm5 on Duex5

As you have connected the BLTouch servo input to the DueX PWM output, the second M950 command is the correct one.

Eman74

@dc42 I just retried it but it doesn't work, it doesn't even try to blink when I launch the M401.

It's so frustrating, my other duet wifi on the cartesian works sweetly.

can I try using some PWM on the duet wifi to make the bltouch work? (just thinking to use the duex5 only for motors and 12v fans up until I'll buy an original one)

droftarts

@Eman74 Apologies, thinking about it I was wrong about M307 in config_override.g. It shouldn’t matter as M950 sets the pin in config.g. It would cause problems in RRF 2.x.

I’ll ask once more: does the probe deploy and retract on power up? If it doesn’t, disconnect all wiring except +5V and GND, and work out why it doesn’t.

Somewhere between the BLTouch and the Duex, the wiring changes, and I can’t see where (on mobile). I suspect either a short between wires, or a swapped wire.

Edit: unfortunately there are no other PWM pins in the board apart from those on the expansion connector.

Ian

Eman74

@droftarts my english is probably not good enough, that's also on mr, unfortunately no matter what config I used till now at the startup nothing happens, sometimes I so the bltouch starting blinking (as if the deploy test was failing).

With a tester I made sure all signals were proper directly from the BlTouch connection up to the other end, so no swapped wires. On top of that I can tell you that wires on the probe (Black correspond to black on the BLTouch and Green correspond to white on the BLTouch) and on the servo (Blue is Brown, Red is Red and yellow is green on the BLTouch)

I quitted buying non original things long time ago I'm starting to suspect all this mess is cause of the F.... duex clone... anyway I'll redo all pin crimping, just in case.

I tried using only 5V and GND with and without Z Probe with all available M950 (just in case... with no luck)

Now I'm not the kind of person which leave things unresolved so I started looking around the DUEX (cause I felt the problem was there...). Now I don't know if this happens also on the original DUEX but the clone do not provide power to the PWM...
...wait for it...
...rolling the drums....
unless you remember to put the jumper on the 5V AUX Jumper select...

so.. now it works perfectly with the proper config:

M950 S0 C"duex.pwm5" 			                ; create servo/gpio 0 on pwm5 on Duex5
M558 P9 C"^zprobe.in" H5 F120 T6000             ; BLTouch connected to Z probe IN pin, free up MOD pin

IT WORKSSSS!!!!

Thank you all for the help, Grazie, Merci.

droftarts

@Eman74 glad you worked it out! My next suggestion was to remove the Duex and try it directly on the Duet pins. That should have narrowed it down to wiring or the Duex.

Ian

Eman74

@droftarts Thank you very much Ian, at the moment I can finally see the bltouch running a full self test at printer startup which is a huge improvement finally.

When I send M401 the pin is deployed and when I send M402 the pin is retracted but when I try to home as soon as the pin retracts the bltouch starts blinking and the bed keep rising towards my hotend (trying triggering manually the bltouch to avoid the hotend digging in my bed)

here is my homez.g:

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 20 2021 18:21:46 GMT+0100 (Central European Standard Time)
; called to home the Z axis

G91                ; relative positioning
G1 H2 Z5 F6000     ; lift Z relative to current position
G90                ; absolute positioning
G1 X200 Y210 F6000 ; Probe Z on the center of the bed
G30                ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91               ; relative positioning
;G1 Z5 F100        ; lift Z relative to current position
;G90               ; absolute positioning

I completely deleted the config-override and my config.g for z is:

; BLTouch
M950 S0 C"duex.pwm5" 			                ; create servo/gpio 0 on pwm5 on Duex5
M558 P9 C"^zprobe.in" H5 F120 T6000             ; BLTouch connected to Z probe IN pin, free up MOD pin           
G31 P25 X28 Y-61 Z0.0    		                    ; BLTouch set offset
M557 X50:350 Y50:350 S50                        ; define mesh grid

is there any additional option I can use to improve probing... like adding something on the zprobe.in or similar? Any idea of what can it be? (I'll keep looking for all possible solutions in the meantime)

DIY-O-Sphere

@Eman74
The homez looks fine.
Please post the homeall.g (In the older ones there was a call for deployprobe.g witch should be replaced )

Eman74

@DIY-O-Sphere sure, here it is:

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 20 2021 18:21:46 GMT+0100 (Central European Standard Time)
G91                    ; relative positioning
G1 H2 Z5 F6000         ; lift Z relative to current position
G1 H1 X-348 Y326 F3000 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-348            ; home X axis
G1 H1 Y326             ; home Y axis
G1 X5 Y-5 F6000        ; go back a few mm
G1 H1 X-348 F360       ; move slowly to X axis endstop once more (second pass)
G1 H1 Y326             ; then move slowly to Y axis endstop
G90                    ; absolute positioning
G1 X200 Y210 F6000 	   ; Probe Z on the center of the bed
G30                    ; home Z by probing the bed


; Uncomment the following lines to lift Z after probing
;G91                    ; relative positioning
;G1 Z5 F100             ; lift Z relative to current position
;G90                    ; absolute positioning

DIY-O-Sphere

@Eman74
Seems to be right.
Does the Bltouch perform the selftest at the power up?

Eman74

@DIY-O-Sphere yes it does, I also looked at other troubleshooting and bypassed all cabling connecting the bltouch directly with short cables and the behaviour is the same:

Performs well the initial self test
Performs well the M401 (fixed blue light)
performs well the M402 (fixed red light)

but when I try to home or to manually trigger the bltouch start to blink red

all this test were done with two original BLTouch v3.1 one of them was connected to an already perfectly working cartesian printer

Phaedrux

Can you confirm that the white wire from the BLtouch is extended all the way to the zprobe.in pin?

Eman74

@Phaedrux yes if you look at posted pictures the white cable is connected to the duet wifi probe connector as green cable. Basically the white is on the GND and the black is on the probe.
Should I invert them?

Phaedrux

@Eman74 said in Bltouch blinking red on Duet wifi+ Duex5 RRF 3:

Should I invert them?

No, the white wire should be connected to the Zprobe in pin.

You can try removing the ^ from C"^zprobe.in"

Eman74

@Phaedrux too late... I inverted them and (believe me I don't know why cause white is connected to the green) but finally it does home!!!!

it works... I'd like to thank you and this fantastic community of very kind and helpful 3D printing lovers and professionals

Phaedrux

Then I suspect there is a crossed wire somewhere.