mjs513
Senior Member+
@KurtE
Ran a test with analog read in the interrupt and worked down to 20us. This makes sense since analog read is taking about 17us.
Did get response on github discussion:
So pretty much done until the next problem.
Oh - forgot - someone tested to see if native ethernet was working with it and the short answer is yes it does.
Ran a test with analog read in the interrupt and worked down to 20us. This makes sense since analog read is taking about 17us.
Did get response on github discussion:
I guess that the problem is not in the analogRead but the integer lastCurrent. lastCurrent is several bytes wide so setting it is not an atomic operation. If you get an interrupt in the middle of setting lastCurrent then the value can be aything. As an int is 4 bytes on the Teensy and faster clock I guess that the chance that it is corrupted is much higher.
So pretty much done until the next problem.
Oh - forgot - someone tested to see if native ethernet was working with it and the short answer is yes it does.