Hi,
I'm using the Teensy 3.1 in a prototype. I'm collecting sensor data with a sample rate of 1000 Hz. The Teensy needs like 600 us to get and calculate on sample which lets him wait around 400 us for the next interrupt. This sample frequency needs to be as accurate as possible and the time is tracked by the micros() command.
1. Is there a good way to let the Teensy sleep and wake up again on the interrupt (this is High active!!!)? If so what would the start up time be like? And is is possible to use the micros() command?
2. Is there another way to reduce the current consumption? Like turning off specific peripherals? I'm using SPI and Analog inputs.
3. In the Low Power thread with duffs library it is mentioned that the Teensy 3.1 should draw like 18.8mA running at 48MHz. My Teensy 3.1 is running at 28mA at 48MHz! Why? It says the Mini54 chip was updated in the release 1.16, I'm using 1.2, do I need to do anything in order to get this update running like burn bootloader?
I'm using the Teensy 3.1 in a prototype. I'm collecting sensor data with a sample rate of 1000 Hz. The Teensy needs like 600 us to get and calculate on sample which lets him wait around 400 us for the next interrupt. This sample frequency needs to be as accurate as possible and the time is tracked by the micros() command.
1. Is there a good way to let the Teensy sleep and wake up again on the interrupt (this is High active!!!)? If so what would the start up time be like? And is is possible to use the micros() command?
2. Is there another way to reduce the current consumption? Like turning off specific peripherals? I'm using SPI and Analog inputs.
3. In the Low Power thread with duffs library it is mentioned that the Teensy 3.1 should draw like 18.8mA running at 48MHz. My Teensy 3.1 is running at 28mA at 48MHz! Why? It says the Mini54 chip was updated in the release 1.16, I'm using 1.2, do I need to do anything in order to get this update running like burn bootloader?