BTT SKRat V1.0 V-minion X and Y endstops will not trigger.
i believe i am out of options on what to do for the title issue. i have arranged the wires for the X and Y endstops appropiately for the SKRat board and per the RATos documentation. signal and ground are hooked up for each, both have correct pin mapping, pullup's have been added to each endstop pin, and i have physically checked voltage and continuity for all connections, wires, switches, etc.... the only way i can see them "triggered" is if i add the ! in front of the applicable pin. below is my printer.cfg for reference. any help would be greatly appreciated as i'm on my 9th total hour of trying to figure this out.
33 Replies
and if you add the
!
it shows as always triggered?@TheTik yep, exactly.
If you have your multimeter looking at the sensor pin, do you see a change in voltage when the switch state is changed?
ok i just checked again to make sure. they both show 0.31v open and closed they go to 0.00v
.31 is too low, that should be showing 5V
or whatever is being supplied
on the board, it has a 5v pin but the other docs said not to plug that in for physical endstops with 3 pins, just the SIGNAL and GND. i could plug that back in and see if something good (or bad) happens,
the three pins of the endstop should be 5V, Signal, and GND (not sure the order or color)
alrighty, i switched them up and still no trigger but it also sent a MCU shutdown this go round. for example, the board shows Y-stop being 5v+ GND PC1. the endstop has symbols for G (ground i assume) NO and NC. on Y i have the signal wire going to NC, GND going to NO, and 5v+ going to G.
no, you'll only want to connect to either NO (Normally Open) or NC (Normally Closed)
I've got an Octopus, not an SKRat, but lemme check my endstop wiring
ok, thak you so much!


only trouble is that the switches are on little breakout boards so I don't know exactly how it is wired.

thats the board side
Hmm interesting. I juat reminded to have them all in but here is how it is at this moment.




The little green light on the endstop turns on when pressed so something is happening
good start, but yeah that sense pin (PB5, PC1, PC0) should be changing from 5V to 0V or vice versa when the switch is triggered.
Crazy thing is, my prox sensor works as advertised. Any metal close to its tip triggers the "triggered" for z endstop
remove the pullup, anything happen?
No change at all. Could my prox sensor being wired to the Servo and Probe port and not the dedicated proximity port be affecting those?
I wouldn't think so
alrighty, that rules that out atleast.
They're not even the same bank of inputs. Probe and servo are
PE
while the others are PB
and PC
ahh that makes sense. i didnt even think of that. im going to try an entire different type of endstop and see what happens.
Ugh, no dice again. And it went into shutdown again.
shutdown suggests that we're shorting the 5V to GND
Makes sense as I kept switching wire orientation while testing the switches.
Unplug all but one switch, get that one working, then make the others match?
that way we know we're only screwing around with one, the others won't affect anything, including weird shorts
gotcha, i unplugged Y from the board until X is up and running. thank you again for all the help, even if it dosent get fixed, i appreciate it.
do my best, even if it isn't any good 😛
haha thanks regardless lol. so i removed the diag jumpers underneath the motor drivers for x and y and still no change.
@TheTik well I got it working. Only had to switch a minor component (switched the mainboard to an SKR minie3 v3 lol). I got everything moving and stopping but right now I'm just trying to work out why the z keeps coming up when I home x or y and even z itself. Had quite a few emergency stops with that.
Check which motor driver slots you're using. I don't know about that board specifically, but some have two ports duplicates of each other
STEPPER_BUZZ might be useful
Ah true, ill give z a buzz and see what happens. This board has 4 integrated tmc2209 drivers but 5 motor ports (Z0 and Z1)
I found the issues, it was the meat servo in front of the keyboard. I forgot to update my stepper_z to the ratios for the belt drive I installed. It was still assuming I had a lead screw. Every 10mm z move was like 30ish in real life. Its good to go now so I just need to clean up the wiring and all done