defragster
Senior Member+
Indications so far the T_3.6 can handle it from my speed test. Compile your current version at 48 Mhz and see if it needs to be bumped higher to run the same as your default 240 (180?) MHz builds. If it can run under half speed - then adding a second even more intense filter set should work. That was my goal in running at 24 and 48 to see how much headroom there was after pulling the samples and running the Euler version.
If I have some idea this might lead to a solution to a background task I had in mind - I could more be helpful with the SD and such mechanics than the math you three seem to have well in hand. And as Brian just added - if it would use a second Teensy for logging would be really fun . I've watched the SD card usage and libs go by - SD latency does seem to bite at times. A second dedicated pass through logger (T_3.5 or T_3.6 ) could simplify and not impact the TestTeensy. A defined standard would make that easier for group use.
If I have some idea this might lead to a solution to a background task I had in mind - I could more be helpful with the SD and such mechanics than the math you three seem to have well in hand. And as Brian just added - if it would use a second Teensy for logging would be really fun . I've watched the SD card usage and libs go by - SD latency does seem to bite at times. A second dedicated pass through logger (T_3.5 or T_3.6 ) could simplify and not impact the TestTeensy. A defined standard would make that easier for group use.