-
-
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] tmc2209 motor driver uart not working with skr pro v1.2 #26989
Comments
Configuration_adv.zip |
You have enabled #define SOFTWARE_DRIVER_ENABLE This stops all stepper drivers moving. This Issue Queue is for Marlin bug reports and development-related issues, and we prefer not to handle user-support questions here. (As noted on this page.) For best results getting help with configuration and troubleshooting, please use the following resources:
After seeking help from the community, if the consensus points to a bug in Marlin, then you should post a bug report. |
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. |
Did you test the latest
bugfix-2.1.x
code?Yes, and the problem still exists.
Bug Description
With skr pro v1.2, tmc2209 motor driver uart does not work, but when I switch to the tmc2209 standalone version, it starts working. It was working normally in the old version marlin. When I upgrade to the latest version, none of the engines work.
Bug Timeline
No response
Expected behavior
I was expecting the motors to work with tmc2209 watch uart.
Actual behavior
None of the motor drivers worked.
Steps to Reproduce
No response
Version of Marlin Firmware
Marlin-2.1.2.2
Printer model
BTT skr pro V1.2
Electronics
No response
LCD/Controller
No response
Other add-ons
No response
Bed Leveling
UBL Bilinear mesh
Your Slicer
Cura
Host Software
None
Don't forget to include
Configuration.h
andConfiguration_adv.h
.Additional information & file uploads
No response
Configuration_adv.zip
The text was updated successfully, but these errors were encountered: