-
Notifications
You must be signed in to change notification settings - Fork 0
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
Calibration glitch with long run times #13
Comments
Another example, were I modulate timer2 slightly when it is setup...
Timer2 is stuck for the rest of the log, meaning that the timer interrupt did not trigger at what should have been the end of the 10s period (~1214.183943). |
Have evidence to confirm that there is (was) an issue with the timers NOT triggering, or the interrupt being missed, I added some protection and some "!!!!!" alerting/messaging
Unit 2: Occurs 11.5s after "7350s" which shows that the timers are reset shortly before this.... so why didn't Timer2 trigger?
Unit 3 has Timer1 fail instead.
|
Testing with Rev2.0, and seen a glitch where the calibration appears to change during a long session. Ie. after multiple hours...
It looks like the process which toggles between two divider values is getting stuck. Normally Timer-2 would run for 10s, with Timer-1 running for a fraction of this - depending on the fractional part of the calibration value. The when Timer-2 terminates it re-setups Timer-1 and Timer-2.
However it seems that Timer-1 never restarts for some reason.
The text was updated successfully, but these errors were encountered: