BLtouch does not work after changing to DUEX5 board
-
I'm beginning to think your BLTouch may be failed.
-
@Phaedrux said in BLtouch does not work after changing to DUEX5 board:
I'm beginning to think your BLTouch may be failed.
Dammit... couldn't there be any other reason for the bltouch to light up red all the time?
-
Photo of the BLTouch? It doesn't have a trace to cut, but it also has a metal pin, so perhaps it's a very old version that requires the resistor?
It was working on a Duex2? Do you still have the Duex2 to test with to see if it works there again?
If you really need to return to printing you could set the probe type to 0 and use manual probing. M558 P0
-
@Phaedrux said in BLtouch does not work after changing to DUEX5 board:
Photo of the BLTouch? It doesn't have a trace to cut, but it also has a metal pin, so perhaps it's a very old version that requires the resistor?
It was working on a Duex2? Do you still have the Duex2 to test with to see if it works there again?
If you really need to return to printing you could set the probe type to 0 and use manual probing. M558 P0
Problem is that I manage to connect 12VDC to 5VDC and burned the duex2
I manage to fix the DuetWIFI but not the Duex2, that's why I bought a new Duex5.
-
@Haggan90 said in BLtouch does not work after changing to DUEX5 board:
Problem is that I manage to connect 12VDC to 5VDC and burned the duex2
The BLTouch is on 5v as well...
-
@Phaedrux said in BLtouch does not work after changing to DUEX5 board:
@Haggan90 said in BLtouch does not work after changing to DUEX5 board:
Problem is that I manage to connect 12VDC to 5VDC and burned the duex2
The BLTouch is on 5v as well...
Well... that's something I had NOT thought of >.<
But how is it still lighting up? -
Well the led is still getting 5v but I think maybe the logic portion got fried.
-
@dc42 Is it possible that the BLTouch got fried when I connected 12VDC on the 5VDC rail?
-
@Phaedrux I ordered a new BLtouch, should be arriving today!
-
@Phaedrux Well, now I got the new BLtouch installed and everything is working again!
Thank you for pointing out the obvious solution -
Glad it's working now.
