X endstop triggers then does not release

Basic Information:

Printer Model: custom
MCU / Printerboard: MKS Gen L V2
Host / SBC Raspberry Pi

klippy.log (1.6 MB)

Describe your issue:


I’m just in the testing stage of building a custom printer. I got a hold of 6 snapmaker linear modules. I don’t have a snapmaker controler nor did I want to use the old drivers built into the modules. So I removed the proprietary boards in the modules and connected the stepper and end stop wires directly to the ribbon cable connecting to the board. On the first move try everything seemed to be working well, but soon after. I got an error that said end stop still triggered after retract.

When I probe end stops, I see that the x end stop gets triggered as soon as the X axis starts to home. This happens even if the X end stop is not plugged into the board. I’ve tried connecting a completely different stepper motor to the X axis with no end stop connected at all. The stepper will rotate a bit then stop.

Rotation seems smooth and in one direction so wiring on the stepper seems right. But still the X end stop gets triggered. I don’t see a retract happening either. What I expect to see is some forward motion, then an end stop hit and some retract. It’s just forward motion then stop. The same thing happens with the linear module.

Edit: to clarify once that end stop gets triggered I cannot release it other than powering down the printer and rebooting. A firmware restart will not untrigger that end stop. If I power down and reboot, then trigger the end stop manually everting works as expected. The instant, I hot home the end stop is triggered adn it will stay triggered.

As for the log, you already tried with un-inverted endstop_pins. Didn’t that work either?

It did not make a difference. I’ve just tried using a very short working USB cable. I was using a very long one before. I thought that I would eliminate that as a problem. I’ve also completely deleted my config and made a new one. Same results.
I’ve also moved from X+ endstop to X- endstop and got the same results. It mystifies me.

I’ve tried another step. I unplugged all stepper motors and all end stops from the board. When I hit home I quickly get end stop still triggered after retract.

At this point, I’m gonna reflash my MCU.

Edit:
reflashing my MCU didn’t make a difference. I got X and Y to home properly by pointing the X end stop to the Z+ pin and the Y to the Y+ pin. Now these two axis home properly. Z now has the issue I had with X to begin with. I’ve tested all the remaining end stop connectors by changing the config file and moving the connector.

When I set a new pin for the end stop, I can toggle the endstop on and off by shorting the s pin to the ground. But when I try to home that axis, the state turns to triggered and stays triggered till I do a hard reboot.

Edit 2:
Solved it. I removed all the Diag jumpers on the board. After that, I was able to map all end stop connectors back to their default pins and it worked.

Sorry for using this place to think aloud.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.