-
Notifications
You must be signed in to change notification settings - Fork 25
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
TMC220x on-board UART compability #13
Comments
Hi @Blaster1920, Short answer: supporting the UART drivers didn't seem feasible within the constraints of this board, but if you can see a way to make it work let me know and we'll take it into consideration. My understanding is that the UART-based TMC drivers require two communication pins (TX and RX) per driver. Please correct me if this is incorrect. The SPI-based TMC drivers require three pins shared among all drivers (MISO, MOSI, SCK) and 1 pin for each driver (CS). On the current design, there are not enough spare GPIO to support adding an extra pin to each driver (also it would be tough to route an extra signal to each driver socket). If there's a way that the UART drivers can work with just a simple jumper using the signals that are already routed to each socket, then it's definitely something I'd be interested in exploring. At the moment, each stepper driver has the following pins/signals:
So, we don't have two pins per driver (outside the usual STEP/DIR/EN) to act as RX & TX. Is it possible to control the TMC2208 with only TX (i.e. no feedback)? If so, it might be possible to use the CHIP SELECT signal as a soft UART TX for that purpose. I'm not familiar enough with the state of TMC220X firmware support to say. Let me know what you think, if you have a way of making it work I'd love to get it included in the design. |
Hi @chrissbarr,
Let me know. |
Hi, |
Hi,
by having a look at the design I noticed that it is missing an important feature to correctly drive the TMC2208 and TMC2209 drivers directly from the MCU. In fact, it looks like you omitted the possibility of choosing between SPI and UART mode: is there a particular reason why you preferred going this way?
Thank you in advance for your time.
The text was updated successfully, but these errors were encountered: