BL Touch issues
-
@qdeathstar The other two are plugged into the Z-Probe section of the board -- the left two prongs of the 4. As I understand it, those two wires power the BL touch and as mentioned, it turns on and self tests successfully.
-
actually, if you just move the dial to the thing that looks like an arrow with a line through it (diode check) you should hear the meter beep when you touch the two leads together. If that happens, you should touch the two pads. The meter should not beep. If it peeps, the line hasn’t been cut.
-
@kskiff7034 The white and black signal to the duetwifi when the probe is actuated. Make sure you black is pin 3 and white is pin 4. For the DMM in the lower right corner of the dial is a picture of a dot and 3 lines. Switch it to that mode. It should beep when the black and red leads touch each other. If it does then test across the area you cut. If it beeps you didn't cut enough. If it does not beep then you should be good to go.
-
Nope, the red and black wire power it. The white is the trigger input..... the black is another ground. Take a picture, please.
-
-
It's properly cut now, but still same issues.
-
@kskiff7034 Using the same method, check across the cable. So one side at the connector at the bltouch (or the connector right before that to be able to disconnect it, and the other side the through the connector. do this to make sure you have continuity down the entire cable.
-
does you red wire connect to the white wire of the bltouch?
-
Oh man I figured it out. So I guess I applied a little too much heat while doing my heat shrinking on wires and it warped one of my dupont connectors. Replaced it and everything is work as it should.
Thanks so much for the help guys. Sorry it turned out to be something so stupid!
-
So now my new issue is homing z axis lol.
I'm using the G30 command after homing x/y and I get the error "Z probe already triggered at start if probing move."
I'm too tired to figure it out tonight, but wanted to post it to see if anything jumped out to anyone. Here's my Home Z file:
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Sun Jul 29 2018 11:50:39 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G90 ; absolute positioning
G1 X56.8 Y-17.200000000000003 F6000 ; go to first probe point
G30 ; home Z by probing the bed -
G1 X56.8 Y-17.200000000000003 F6000 ; go to first probe point
That's a really odd value. I doubt that this is the problem but maybe.
Can you manually deploy and retract the pin with m401 and m402? That will verify that your deploy and retract macros are working.
If you put the touch into self test and tap the pin with your finger does it stay triggered?
What happens if you send a manual G30 from the console?
-
Disregard. Too tired to be doing this lol.
-
Haha. Get some rest tiger.
-
To explain, one of my connections was lose and causing issues it seems. I send the G30 code and it seems to be working mostly correct except my bed goes the wrong way. I'll figure that out tomorrow.
-
Does the bed move the way you'd expect it to if you move it manually with the buttons? You z motor direction might need to be reversed.
-
Adding a minus to numbers makes it go down, yeah.
-
Although, on second thought that is incorrect. I think you're right. I'll have to adjust some things.
-
Yes in a core xy with a moving bed if z0 is nozzle touching the bed then dropping the down would increase the z value in the positive direction.
Youll have to reserve a motor direction. And ensure your maxima and minima are correct. And may need to modify the homing files if they were dropping the bed before moving in x and y.
