NuttyMonk
Member

It's probably my code. I have about 3k lines of code and i'm using 5 or 6 timers so i'm probably doing something wrong somewhere. I just went back to elapsedMillis for this as, based on your comments, it seemed to not...

Yeah, been thinking that myself. Oh well, back to the way it was. Thanks for your help Joe. Cheers NM

Hi Joe, i am looking to use a callback routine instead of polling using elapsedMillis if i can. I've been weeding elapsedMillis/Micros out of my project and if i can get this working it'll stay out.. I had been...

p.s. i've been able to determine that the largest value i can put into timeoutMillis is 178,956 which is 178,956,000 when it is put into the timeoutTimer.trigger(); function. Any values larger than this cause the...

Hi Luni, I'm using the TTT in one-shot mode to manage a screen timeout on an attached OLED but it isn't behaving as expected. I've used the following code (this is just part of my code, not all of it) ...

Ah, now that works well. Thanks joe. Getting very accurate times now.

lol. Yup, there is good support on this forum. I was getting microsecond accuracy when i was using elapsedMicros before. I'm not sure if i've used it for timing testing since i moved to the Teensy 4.0 from the 3.2....

So, how does millis() and micros() get their timestamps? do they use timers? I ask because i am using elapsedMicros to test the timing of intervalTimer and it's jumping about between 124,000 125,000 and 126,000...

I can't find anywhere in the elapsedMillis documentation page on PJRC that states what timers it uses. Does anyone know? Cheers NM

OK. So it's a 24MHz clock. That gives it a tick time of 41.67 nanoseconds and the accuracy seems to be within +-1 microsecond. Very nice. The last question is can i have 4 of them running at once? Cheers NM

I've just done a quick test with the intervalTimer library and it's stable as a rock. I've used the code below and i'm checking how long it takes for each step using elapsedMicros and it's showing me that each clock...

I am running 4 clock outputs from the Teensy 4.0. They are for an audio project as a clock source for sequencing purposes. That means i need 4 independent timers. The PIT timers would be good to use as they are 32-bit...

The minimum time interval is about 3.7 milliseconds, the maximum is about 60 seconds, at least for the moment. I also want the clock pulses coming out of the project to be as jitter-free and stable as possible and...

I was just getting the timers and interrupts working and then i realised i don't know how to decide when the 3 cascaded timer channels have reached the correct count. I am currently using elapsedMiros to do the...

Ah, that makes sense. Computers-count-from-zero strikes again!!! lol NM

Hi all, so i found the eeprom.h file in this location C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy4\avr and changed this #define E2END 0x437 to this