Skip to content
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

Waveform Scheduler is not precise [Cyclops rev3.6] #16

Closed
oyeb opened this issue Aug 21, 2016 · 1 comment
Closed

Waveform Scheduler is not precise [Cyclops rev3.6] #16

oyeb opened this issue Aug 21, 2016 · 1 comment
Labels

Comments

@oyeb
Copy link
Collaborator

oyeb commented Aug 21, 2016

This affects only Teensy 3.2
The Teensy loses time while in the ISR, while the code (and design) assumed that this loss would be negligible. But, tests with an oscilloscope have confirmed that the loss is significant ~20usec on avg. per ISR.

The only solution is to apply a compensation in the scheduling of "the-coming-ISR". IMO, any design would require a compensation of this sort.

A portable solution is to Measure time spent in ISR using another Timer and compensate. This is better than hardcoding time spent in interrupts, because time depends on the clock speed (Teensy's clock speed can be changed easily!).

@oyeb
Copy link
Collaborator Author

oyeb commented Aug 21, 2016

The 👆 fix will also mitigate

  • the error of cascading signal updates (will expand later)
  • update period of 50usec but got period of ~70usec (or more)

@jonnew jonnew added the wontfix label Nov 13, 2017
@jonnew jonnew closed this as completed Mar 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants