@Phaedrux I just tried but it prevents me from posting new topics... it seems the same issue there was this morning...

@fcwilt said in Endstops triggered without anything connected:

M98 P"config.g"

M98 P"config.g"

HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

this is what I get, anyway I'll soon update to RRF3, my understanding is it's way more powerful and has more development potential

@Phaedrux sure it's a duet wifi with a duex5 I'm going to start a thread thank you

I'm in the middle of a BLTouch nightmare... and I keep banging my head over it...

My BLTouch is original latest version 3.1

I updated to RRF 3 (lost a lot of time to get all axis and endstop working but all seems good a part from the BLTouch)

here is my config.g related (deployprobe and retracct are standard..):

M574 Z1 S2                                     ; configure Z-probe endstop for low end on Z
M558 P9 C"^zprobe.in" H5 F100 T3000            ; BLTouch connected to Z probe IN pin, free up MOD pin
M950 S0 C"exp.heater7"                         ; servo/gpio 0 is Z probe MOD pin tried also duex.pwm5 and !exp.heater7 without success
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

My Troubleshooting:

1. Double-checked wiring and tested connectivity with a tester;
2. verified jumper presence on duex 5
3. verified led on heater7 is switched on when I start the system
4. replaced BLTouch with another perfectly working on my cartesian printer with duet wifi and the behaviour is the same erroneous one, it does lights on and blink red without passing the switch-on test
5. tried other heaters on the duex with same result...

NOTE: I have 3 Z motors configured and working on Drive 5:6:7 (M584 X0 Y1 Z5:6:7 E3)

Any help would be really appreciated I followed all documents but somewhere something is just not right and I know it shouldn't be a huge thing cause I tried with another surely working one and it does the same thing so it's a config matter somewhere...

@droftarts I just got tired of banging my head and followed steps to upgrade to 3.2.2 ...wish me luck...

@droftarts I actually followed all your recommendations, with no luck.
I'm a bit struggling here cause I double-checked the wiring, my bltouch is latst version and should support both 3.3v and 5v, I configured jumper for 3.3 logic and I'm using PWM5 but I cannot get the pin to deploy.
I'll keep trying but I'm starting to think I should upgrade to RRF3 to get better results...

@Agniusm said in Duet Wifi BLTouch wiring:

https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/

following as I'm doing same installation too, but I have a duex5 and I'm using PWM5 channel for servo function (so for me it's P5 and not P9, and I prefer to run the M307 line before)

@eman74
the second correct code mode I was meant to write is

; Endstops
M574 X1 S1 P"xstop"                            ; configure active-high endstop for low end on X via pin xstop
M574 Y2 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

Hi all, I'm having some hard time with my CoreXY printer which is finally working and able to print but my Y axis is flipped and I discovered the reason:

my homing (config working with Y flipped) is on the backword left, which is not compatible with standard slicers config where X1-Y1 are located to the bottom Left:

My Config

X-Min,Y-Min ------- X-Max,Y-Min1
X-Min,Y-Max ------- X-Max,Y-MAX

; 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 S0                                     ; physical drive 3 goes backwards E3D HEMERA
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 Z1666.00 E409.00             ; set steps per mm
M566 X750.00 Y750.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 X600.00 Y600.00 Z30.00 E250.00            ; set accelerations (mm/s^2)
M906 X1600 Y1600 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

Now looking at documentations and forum to get my Y-Min (Y1) positioned on my front left should be pretty easy by modifying my M574 command for Y endstop as following:

; 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

Except for the fact that my duet wont accept that and when I try to home the Y axis does nothing other than messaging "G28 Error: Failed to enable endstops" and "G28 Error: homing failed"

The hardware and electronic part works perfectly, in fact I can print and home consistently with my old config which has Y axis flipped.

Does anyone knows if I'm missing something?

@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 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?

@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:

1. Performs well the initial self test
2. Performs well the M401 (fixed blue light)
3. 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

@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

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

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

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

@Eman74