-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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] Compilation fails for BTT SKR1.4 Turbo when using dual Z endstops #19595
Comments
BTT SKR 1.3 has min and max endstops |
@ellensp thanks for a quick response, I would appreciate it if you could help me a bit more. The problem I was facing when trying to use I would appreciate it if you could clarify for what reason pins labeled for filament sensors can't be used as regular endstops if from hardware point of view there is no difference between mechanical endstop and a mechanical filament runout sensor, could that be that you are most concerned about I'm wondering what makes this change different from what I'm trying to propose 2822c08? it introduced the following code:
why enabled stall sensitivity makes it acceptable assigning those pins as endstops? |
wrong again. PWRDET does not have a pull up resistor. |
@ellensp I see, so PWRDET doesn't have the required resistor attached, but the rest two do, does that mean that they can be standardly assigned to the max endstops? Also what makes my approach non standard if that is no different from what the code does today when stall guard enabled? If one is migrating from SKR1.3 with a setup similar t mine that is pretty much exactly what they would want to do isn't that right? Besides the assigning wouldn't happen if one does not have |
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
Currently if user tries to enable dual Z axis with independent endstops for BTT SKR1.4T the compilation would fail with the following error:
A simple way to fix it is to update pins for SKR1.4 to allow using
E0DET
,E1DET
andPWRDET
as endstops. That would be the same solution which is already applied and working for SKR1.3 boards where you can see that exactly the same pins are being assigned to two different functions.https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/src/pins/lpc1768/pins_BTT_SKR_V1_3.h#L47
https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/src/pins/lpc1768/pins_BTT_SKR_V1_3.h#L94
In addition pins
E0DET
,E1DET
andPWRDET
are being used as max endstops in current version ofpins_BTT_SKR_V1_3.h
so it seems it should be fine to extend that behavior to cover more configurationshttps://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/src/pins/lpc1768/pins_BTT_SKR_V1_4.h#L59
https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/src/pins/lpc1768/pins_BTT_SKR_V1_4.h#L70
https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/src/pins/lpc1768/pins_BTT_SKR_V1_4.h#L81
I tried to submit a pull request #19532 fixing the issue but without much communication it was closed almost right away. So I'm trying to follow up on it with this bug report and see what can I change to get it merged.
My Configurations
Required: Please include a ZIP file containing your
Configuration.h
andConfiguration_adv.h
files.Steps to Reproduce
Expected behavior: [What you expect to happen]
Build successful
Actual behavior: [What actually happens]
Build fails with
Can make it work if the following line is added to
pins_BTT_SKR_V1_3.h
fileAdditional Information
Attachments:
The text was updated successfully, but these errors were encountered: