Thanks. Just looked over the Pico and decided to go with the Pico H with no wifi. Now to get it ordered and figure out how do set everything up. Communicating between the RPi 4 and the Pico will be an interesting adventure as I have not coded anything like that.
Just to make sure that I understand, the Pico won't miss pulses from the encoder as it doesn't run multitasking, right?
As for the expected pulse rate, the rate will vary but it shouldn't exceed ~1200 pulses/second.
Just to make sure that I understand, the Pico won't miss pulses from the encoder as it doesn't run multitasking, right?
As for the expected pulse rate, the rate will vary but it shouldn't exceed ~1200 pulses/second.
...
Otherwise, an Arduino or Pi Pico would be a good choice. Cheap, deterministic, easy to use. You could keep a running total of the encoder position and supply it on request from the host, or send a message each time it changes.
It would also be worth doing a quick back-of-an-envelope calculation of the expected pulse rate, given it's a 600 pulse encoder and the input will be turning at some rate. It helps put bounds on the problem, and whether a proposed solution will actually work.
Statistics: Posted by gwfami — Tue Sep 10, 2024 10:53 pm