Welcome to the SeeMeCNC Community

I searched around the forums for a while, but I could not find the solution to the problem I am experiencing. During the Initial Function Tests, when I send the command to my printer to check the Endstop status (M119) I receive 'H' on all of them instead of 'L'. For testing purposes, I held down each endstop and sent the same command, but still only received 'H'. (see figure 1)
Figure 1 - MatterControl Terminal Output

For software, I am running the latest Repetier.ino file download from the SeeMeCNC Github. I am communicating with the printer with MatterControl v1.5.0. I have a MacBook Air. I ran the eeprom_clear program again and re-uploaded the Repetier firmware, but this did not fix the issue. I am able to connect to the printer, and I can see that the both thermistors are working properly by outputting the correct temperature. Additionally, the step motors are functional.
Figure 2 - End Stops
Figure 3 - End Stop Connection to Motherboard

Any tips or suggestions are greatly appreciated, as I am stumped right now.

Thanks for the help!

- Sam

Could you take a picture of the end of the endstop lead on a white background (Or a higher res picture of it where it is)? It looks like the crimped sockets are attempting to escape somewhat (Or that you haven't got the shells connected to them, which is arguably worse). I would also check that your endstop connectors are on the spade terminals properly, as I have had issues in the past where they were off center, and would hold in place due to the cover, but not electrically connected (not on the printer though). If it's not that the connectors are attempting to escape, or are otherwise bad on one end or the other, then would you dismount a switch from the top of the tower, and show me a closeup of the area under the lever arm.

Thanks for the response. I took a better picture of the end stop connection. There is a small gap (see attached pic), so maybe that's the issue? Although I've had a lot of difficulty pushing the clamp down any further.

Here is the picture, it looks the one I tried to attach previously was too large a file size.

I cannot tell from the picture and I don't mean to insult you but do you have the wires connected to the correct (min or max) pins on the motherboard?
This is detailed in the manual. Also, the switch has a NC and a NO pins and the wires have to be connected to the proper pins again as detailed in the assembly guide.

Not a problem, definitely makes sense to ensure everything is connected properly. Sorry about the poor photographs, I can try to take some better ones when I get back home.

As for the connection to the motherboard, I connected the white wire into pin position #1 (with the arrow) and connected the black wire to the middle slot. I plugged the X, Y, and Z end stop cables into the lower sockets on the left hand side of the motherboard (labeled max-height stop or something along those lines).

Although now that I'm looking over the manual again, I'm not sure if my wires are seated fully into the locking tab. I remember hearing a click when I inserted, but checking the image I don't think I had a tab sticking out of the second hole. I will check this theory out when I return home.
Thanks,

Sam

Eagle, from what I could see, he is properly connected on the RAMBO as far as where the pins are, but they don't look properly seated.

What I think is very odd is that all three are set high - as if they're shorted together or something.

g.

It's fixed now! Xenocrates - you were correct, my pins attached to the motherboard were not properly seated. I can't believe I didn't see it on my first review of the manual when I was trying to debug the issue. I guess sometimes you just need to take a step back.

Gene - I'm guessing that if there's not a connection between the endstops and the motherboard, the firmware just returns high. I thought in this case it would have returned null or N/A or something.

Thanks for the assistance!

Sam

I'm glad to see you got it worked out!

g.

icanhurdleu wrote:It's fixed now! Xenocrates - you were correct, my pins attached to the motherboard were not properly seated. I can't believe I didn't see it on my first review of the manual when I was trying to debug the issue. I guess sometimes you just need to take a step back.

Gene - I'm guessing that if there's not a connection between the endstops and the motherboard, the firmware just returns high. I thought in this case it would have returned null or N/A or something.

Thanks for the assistance!

Sam

Thanks to Xenocrates, I am also glad that you resolved the problem.

Heh. I only really though about it because I've been working with entirely too many crimped connections recently, and some of the shells are either stubborn to get them in (Especially if you don't use a proper crimping tool), or will let them try to escape, if you accidentally crushed the locking pin. Or worse, both. Glad we got it fixed without you needing to tear much apart, and that a fuse didn't accidentally get killed.