"The Free Software Foundation urged developers to choose or any later version..." [gnu.org] but if developers did not so choose, are the terms not precisely as they are written? While FSF may consider it bad, I'm not sure I see an ambiguity in...
On the T3.2, the large numbers near 4M would make sense if instead of + pulse width, it was counting - pulse width (duration from falling edge to next rising edge). It works out to be about right for the typical interval between pulses, which...
Update: I found my T4.1 board and ran the same code on it, with the same source signal of pulses. The T4.1 has higher resolution by counting a faster-running clock. It still has the too-large-number glitches described above, but they are far more...
In case of interest, here's a histogram of pulse lengths captured by the above code. In this case, pulse length is some function of gamma ray energy, and the rightmost peak around 580 counts on the horizontal axis is due to a small Cs-137 test...
I'm wondering if you might comment on what I'm seeing. I have pulses typically around 5 microseconds in length, on average about 20 of them per second, but each one arrives at a truly random time (this is a gamma scintillator, timing is random...
You can measure period, high time, or low time with the FreqMeasureMulti library. Most of the examples measure total period, but you just need to specify an argument in the constructor to measure high time or low time. It uses the terms SPACE and...
I'm wondering if there is some example Teensy 4 code that demonstrates how to measure a positive-going pulse width (as distinct from either pulse position, or frequency) with the best available accuracy, which I presume would mean hardware input...