Bltouch blinking red on Duet wifi+ Duex5 RRF 3

droftarts

Also see https://duet3d.dozuki.com/Wiki/BLTouch_Troubleshooting

Ian

Eman74

sorry guys yesterday I was out, I tried both with:

M950 S0 C"!exp.heater7"

and

M950 S0 C"duex.pwm5"

they don't work for me.

I looked to all troubleshooting documents and tried using the config tool, here are
deployprobe.g:

; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Sat Jul 04 2020 19:19:39 GMT-0300 (Argentina Standard Time)
M280 P0 S10 ; deploy BLTouch

and retractprobe.g:

; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Sat Jul 04 2020 19:19:39 GMT-0300 (Argentina Standard Time)
M280 P0 S90 ; retract BLTouch

some pictures of my wiring:

I also tried using both 5V logic and 3.3V logic from the jumper, when I issue the M401 the BLTouch(3.1) starts blinking but does not deploy, I tried also using another BLTouch(3.1) already working on my cartesian printer but it has the same behaviour.
All wiring signals are tested and double-checked with a tester.

I'm starting to think if there is a way to connect the BLTouch all on the main board, just in case my duex has something wrong.

Eman74

do I need to remove the M307 here? that's the only thing I saw somewhere in the docs but I'm not sure.

; config-override.g file generated in response to M500
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A99.1 C453.2 D2.2 S1.00 V0.0 B0
M307 H1 A372.3 C109.6 D4.6 S1.00 V24.2 B0
M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

droftarts

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

do I need to remove the M307 here?

Yes. It’s defining H7, which is shared with PWM5, after the probe is defined, so overriding it. You haven’t posted your whole config.g, so difficult to know you were using config_override.g. Was it like this in RRF 2.x as well?

You haven’t answered my earlier questions. You have a clone Duex. You have non standard wiring colours, and don’t show the BLTouch itself to know what is wired where. All this makes it difficult to help you. I’m not omniscient and omnipresent!

Ian

Eman74

I'm deeply sorry, I did not saw your previous question, and if any additional config file is needed please let me know.

here is my config.g:

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 20 2021 18:21:46 GMT+0100 (Central European Standard Time)

; General preferences
G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"EmanXY"                                 ; set printer name
M669 K1                                        ; select CoreXY mode

; Network
M552 S1                                        ; enable network
M586 P0 S1                                     ; enable HTTP
M586 P1 S0                                     ; disable FTP
M586 P2 S0                                     ; disable Telnet

; Drives
M569 P0 S1                                     ; physical drive 0 goes forwards
M569 P1 S1                                     ; physical drive 1 goes forwards
M569 P2 S1                                     ; physical drive 2 goes forwards
M569 P3 S1                                     ; physical drive 3 goes forwards
M584 X0 Y1 Z5:6:7 E3                               ; set drive mapping
M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E409.00              ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00            ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00        ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00            ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30                   ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X400 Y425 Z520 S0                         ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"                            ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                            ; configure active-high endstop for high end on Y via pin ystop
M574 Z1 S2                             ; configure Z-probe endstop for low end on Z

; Z-Probe
;M558 P1 C"zprobe.in" H5 F120 T6000            ; set Z probe type to unmodulated and the dive height + speeds
;G31 P500 X0 Y0 Z2.5                           ; set Z probe trigger value, offset and trigger height

; BLTouch


M558 P9 C"^zprobe.in" H3 F120 T3000             ; BLTouch connected to Z probe IN pin, free up MOD pin           
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
;M558 P9 C"^zprobe.in" H5 F100 T6000            ; set Z probe type to bltouch and the dive height + speeds old C"zprobe.in+zprobe.mod"
;M950 S0 C"exp.heater7"                         ; assign GPIO port 0 to heater7 on expansion connector, servo mode

;M280 P0 S10 				                    ; send control signal to BLTouch through servo/gpio 0
G31 P25 X28 Y-61 Z0    		                    ; BLTouch set offset
M557 X50:350 Y50:350 S50                        ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                          ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00                               ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                        ; map heated bed to heater 0
M143 H0 S120                                   ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138  ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                           ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                               ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                   ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                           ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                              ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"duex.fan4" Q500                      ; create fan 2 on pin duex.fan4 and set its frequency
M106 P2 S1 H1 T15                              ; set fan 2 value. Thermostatic control is turned on
M950 F3 C"duex.fan5" Q500                      ; create fan 3 on pin duex.fan5 and set its frequency
M106 P3 S1 H1 T15                              ; set fan 3 value. Thermostatic control is turned on
M950 F4 C"duex.fan6" Q500                      ; create fan 4 on pin duex.fan6 and set its frequency
M106 P4 S1 H1 T15                              ; set fan 4 value. Thermostatic control is turned on
M950 F5 C"duex.fan7" Q500                      ; create fan 5 on pin duex.fan7 and set its frequency
M106 P5 S1 H1 T45                              ; set fan 5 value. Thermostatic control is turned on
M950 F6 C"duex.fan8" Q500                      ; create fan 6 on pin duex.fan8 and set its frequency
M106 P6 S1 H1 T45                              ; set fan 6 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0                               ; define tool 0
G10 P0 X0 Y0 Z0                                ; set tool 0 axis offsets
G10 P0 R0 S0                                   ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600                              ; enable support for PanelDue

All original only duex5 I think is not (I don't recall if I bought the original one it was long ago, the rest is all original 100%), the original cable provided was too short, I just replaced it.

regarding the M401 when I launch it the BLTouch starts to blink.

when nothing is wired I can see a red 1000 on z-probe, when all is wired the value is 0.

I changed the config so many times that my SD cards started to fail, I just replaced it with a 32Gb one.

I removed the M307 from the override file on the H7 but keeps doing it, I'll proceed disabling all M307 and give it a try.

My wiring it's still not perfect, and it's my first ever build... but here's the picture (I tried to hide the flat cable which cover the rest):

Eman74

@Eman74

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