Skip to content

TMC2209 setup not possible after power cycling TMC2209 #85

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

Open
koombot opened this issue Jan 13, 2025 · 1 comment
Open

TMC2209 setup not possible after power cycling TMC2209 #85

koombot opened this issue Jan 13, 2025 · 1 comment

Comments

@koombot
Copy link

koombot commented Jan 13, 2025

I've been running some tests with the library using the examples but have encountered an issue and I'm not sure how to resolve it.

When following the examples it encourages you to turn the power off to the motor to see what happens (assuming you have comms and driver is setup). On doing this the example reports that driver is not communicating. On resuming power the MC reports that the stepper driver is communicating but not setup.

There are two options I have found that fix this: either resetting the MC (If monitoring the serial port in Arduino IDE) or if programming with VS Code if you stop monitoring the serial port and then resume monitoring the serial port.

I have tested this with an ESP32 and an Arduino mega with the same behaviour observed.

Does anyone have any insight as to the issue? The examples seem to suggest that a power cycle will be okay, but I'm not seeing it.

@koombot
Copy link
Author

koombot commented Jan 13, 2025

I've solved half the issue. I was running the TestCommunication example with the ESP32 and on the stepper_driver.isCommunicatingButNotSetup() where it runs stepper_driver.setup(serial_stream) i forgot to explicitly state the Rx and Tx pins (as per the change in the ESP32 UART outlined in issue #70

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant