-
Notifications
You must be signed in to change notification settings - Fork 2
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
Due SPI/ encoder reading #62
Comments
562360a likely fixed this issue, I was missing a return(facepalm). I will put this as an enhancement since it is no longer necessary to switch to the onboard counter for V1. |
@nickross4444 @DeepFriedDerp - Can you please re-summarize the issue here, why we would want to solve it, and how we would do so? This will help me in prioritizing the work within our development plan. |
We thought the encoder buffer wasn't working(ended up being software bug), and started brainstorming using the onboard quadrature decoder to count the encoders, instead of an offboard SPI counter(what we have now). The current solution is working well, but it was at some point mentioned that we could leave this as an enhancement to simplify the hardware. I am personally in favor of leaving it how it is now, as we are not having an issues with it, but it has some potential as a relatively advanced project for future team members. |
Much more clear, thanks @nickross4444. I'm going to mark this as |
SPI is reading all 0's from the decoder attached to the Due. @DeepFriedDerp is there a chance the due clock cycle is too fast? I don't remember if we tried slowing it down or not.
The other thing to try in the lab is using the level shifter. The board should work at reduced speeds at 3.3v, but a 5v supply should improve its reliability.
The text was updated successfully, but these errors were encountered: