BLTouch not really working

modl

I tried reverting from RFF3.4.5 to 3.4.4 following the advice in the release notes because of some potential homing issues. It didn't solve the issue

modl

@jay_s_uk They work every time at startup, but not after homing x and y

jay_s_uk

@modl that indicates that you either have a wiring issue or you have something in your homing files thats causing issues.
can you post homex.g and homey.g?

modl

@jay_s_uk So M401 and 402 actually work after homing x alone.

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Mon Jan 09 2023 14:50:13 GMT+0100 (Central European Standard Time)
G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 X-360 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000    ; go back a few mm
G1 H1 X-360 F360  ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Mon Jan 09 2023 14:50:13 GMT+0100 (Central European Standard Time)
G91                ; relative positioning
G1 H2 Z5 F6000     ; lift Z relative to current position
G1 H1 Y-1000 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F6000     ; go back a few mm
G1 H1 Y-1000 F360  ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000    ; lower Z again
G90                ; absolute positioning

jay_s_uk

@modl so theres nothing in there that should stop M401 and M402 from working.
next is to look at your wiring and make sure nothing is being pulled etc

modl

Ok M401 and M402 don't work after homing y alone, could there be a short somewhere with y endstops or motors ? Or could an overload cause this?

modl

@jay_s_uk Physically everything looks fine. And if i'm resetting the system, M401 and M402 will work at the exact same position

jay_s_uk

@modl can you home Y and then send M558 and post the output?

modl

@jay_s_uk
At startup

M558
Z Probe 0: type 9, input pin io4.in, output pin nil, dive height 5.0mm, probe speeds 120,120mm/min, travel speed 6000mm/min, recovery time 0.20 sec, heaters normal, max taps 1, max diff 0.03

After homing Y

M558
Z Probe 0: type 9, input pin io4.in, output pin nil, dive height 5.0mm, probe speeds 120,120mm/min, travel speed 6000mm/min, recovery time 0.20 sec, heaters normal, max taps 1, max diff 0.03

modl

@jay_s_uk I found the culprit !! I actually had an extruder wired the wrong way when i first powered the machine, I rewired it as soon as i found out but it's been getting really hot even if idle since then. I unplugged it from the board and the probing now works. How to know if the stepper is cooked ?

Thank you very much for all your replies and your guidance

modl

Hope i didn't cook the driver...

jay_s_uk

@modl glad you found the culprit! if it gets very hot even when not in use thats not a very good sign at all. is RRF generating any warnings?

modl

@jay_s_uk No RRF doesn't ring. I tested the coils resistance though one is .4 ohms the other is 4.8. I guess this one's cooked. Any way to know how the driver is doing except plugging in an other axis an changing config.g?

jay_s_uk

@modl thats probably the easiest way to test the driver. Thats the way i usually test drivers

modl

@jay_s_uk OK I'll try that. Again thank you very much!

modl

It was actually pretty fast, and the driver is doing fine

jay_s_uk

@modl fantastic!