-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] (y_min & x_max endstop not detected) #23
Comments
Thank you in for reporting this. I'll have a look in the evening. When upgrading, please keep in mind that this repository is in early beta status. |
Than you for your support. |
In "pins_TIGORILLA_14.h" they are not defined and the default pins in the included "pins_RAMPS.h" are different |
The problem is an incorrect pin in pins_RAMPS.h |
Sorry, I overwrote the pin config when pulling from the Marlin repo. Fix incoming in a few minutes! |
Are you sure this was the right fix? now none of my end stops work anymore |
Ugh. Thanks for reporting. I can't test it atm, I am not at my printer right now. Could you try this one? |
Forget what i just wrote. I recompiled the version again to double check and it seems to work now. No idea what went wrong. |
No worries. Just a weird glitch maybe. I'm still leaving this open for some more time, if someone else reports it, we know it wasn't you. |
Latest version works for me |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Bug Description
When triggered, both the y_min & x_max endstop do not change state
My Configurations
I'm running latest 2.0.x commit 9b7f0ba, with stock code, no modifications
Moved from Marlin 1.1.9 and there was no problem on that firmware.
Tried to compare both configuration file in the "Endstop" section but without any result
Expected behavior: [Normal Homing of all Axes]
Actual behavior: [Y Axis and the second Z axis keep pushing the rail after reaching the endstop]
The text was updated successfully, but these errors were encountered: