Skip to content

Resolution and Performance #41

Answered by luni64
sganz asked this question in Q&A
May 4, 2024 · 1 comments · 1 reply
Discussion options

You must be logged in to vote

I think a nano might be too slow for your 360ppr + 6 low-res encoders. I did a quick experiment with a nano and the 74165 code. I measured some 160 µs per tick. That gives you a reading frequency of 1/160E-6 = 6.25 kHz, which might be a bit slow for your 360ppm encoder.
Any reason why you want to use that ancient processor? If your project is cost-sensitive, you could use a SEED XIAO (~5 EUR), which can tick in 68 µs (14 kHz). Or, if you can spend about 30 EUR, a Teensy 4.X, which would do the same in 3 µs. (Depending on what you're trying to do, using a Teensy probably won't require a second processor, which might reduce the complexity and saves the cost for the second processor)

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@sganz
Comment options

Answer selected by sganz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants