-
-
Notifications
You must be signed in to change notification settings - Fork 722
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
SAMD21 micros() problem #684
Comments
More detailed data (Version v3) Two examples for the running oscilloscope with triggering on line D4 "pinISR_NotComplete". You can see how often a wrong measurement will be done. This will not occur on a NANO_Every platform! 2022-10-27.11-16-40.mp42022-10-27.11-20-37.mp4 |
More detailed data (Version v3) Two examples for the running oscilloscope with triggering on line D4 "pinISR_NotComplete". You can see how often a wrong measurement will be done. This will not occur on a NANO_Every platform! 2022-10-27.11-16-40.mp42022-10-27.11-20-37.mp4 |
Workaround with TC3 (Version v4) 2022-10-30.17-35-21.mp4 |
has always the same result as
https://arduino.stackexchange.com/questions/12587/how-can-i-handle-the-millis-rollover/12588#12588 |
@JAndrassy If an timer overflow, the current is smaller than the previous -> only at this case the if branch will be calculated |
Hello all,
this is my first time here and I am not sure that my assumption is correct.
The aim of the program is to decode a Manchester signal. The LED_BULITIN indicates a failure and gives a trigger for the oscilloscope.
From time to time the calculation of the „intervalBahnsignalMicros“ goes wrong and the decoding of the signal is corrupted!
This failure was never seen on a NANO_Every platform, but on different SAMD21 platforms like NANO 33 IoT, ARDUINO_Zero, MKR_Zero and MKR WIFI 1010.
Thanks for your help.
Sketch:
The text was updated successfully, but these errors were encountered: