Join GitHub today
Limits on CYCLE_TIME_US vs. SAMPLE_US? #5
As I played with modifying CYCLE_TIME_US and SAMPLE_US defines in the code, I couldn't get it working with pretty much anything that doesn't equal to exactly 1000 samples per cycle.
Hi, Thanks for the feedback. I got a very similar problem reported on the blog:
There is probably something weird going on here. I need to take a deeper look. Thanks for opening an issue!
pushed a commit
Nov 14, 2013
If it's expecting 1000 integer samples can I just go in there and put in some code that will interpret the frequency into 1000 steps even if some of those steps don't change the duty cycle due to the timing granularity?
I am struggling to figure out where this would even happen in the pi-blaster code...