I am looking for the low power design with Teensey. My hardware is design with the same focus - having control pins to toggle the power of module-wise circuitry.
Right now my code snippet is like this in loop() function of Ardunio,
power_mgmt.disable_all(); ///I am disabling power to all the modules of my hardware for which I have availability of control pin
time_mgmt.power_down();
power_mgmt.enable_all(); ///I am enabling power to all the modules of my hardware for which I have availability of control pin
...................
Implementation for time_mgmt.power_down() is like this,
SnoozeBlock config_teensy(alarm);
err_status v_time_mgmt:ower_down()
{
Snooze.deepSleep(config_teensy);
return NO_ERR;
}
.........................
Basically I am trying to wakeup with the RTC. My need is to wake up at every 15 minutes, read the data from attached sensors -> send it over XBEE, and then again go back to sleep for 15 minutes. There is a provision of digital I/O for all the modules (i.e. XBEE, Attached Sensors) to disable the power going to them which I am handing with power_mgmt.disable_all().
I have put the multi-meter in series to my power source and measured current at both the instants - at the deep_sleep and at the operational time. When it is operational, I am seeing current around 100mA, and when it is in deep_sleep, I am seeing current around 28mA.
After debugging across the hardware, it was figured that almost all the the current is being taken by the Teensey itself even though it is in deep sleep. How can I manage Teensey firmware to get as minimum current as possible when I put it in sleep mode - seek some guidance?
Right now my code snippet is like this in loop() function of Ardunio,
power_mgmt.disable_all(); ///I am disabling power to all the modules of my hardware for which I have availability of control pin
time_mgmt.power_down();
power_mgmt.enable_all(); ///I am enabling power to all the modules of my hardware for which I have availability of control pin
...................
Implementation for time_mgmt.power_down() is like this,
SnoozeBlock config_teensy(alarm);
err_status v_time_mgmt:ower_down()
{
Snooze.deepSleep(config_teensy);
return NO_ERR;
}
.........................
Basically I am trying to wakeup with the RTC. My need is to wake up at every 15 minutes, read the data from attached sensors -> send it over XBEE, and then again go back to sleep for 15 minutes. There is a provision of digital I/O for all the modules (i.e. XBEE, Attached Sensors) to disable the power going to them which I am handing with power_mgmt.disable_all().
I have put the multi-meter in series to my power source and measured current at both the instants - at the deep_sleep and at the operational time. When it is operational, I am seeing current around 100mA, and when it is in deep_sleep, I am seeing current around 28mA.
After debugging across the hardware, it was figured that almost all the the current is being taken by the Teensey itself even though it is in deep sleep. How can I manage Teensey firmware to get as minimum current as possible when I put it in sleep mode - seek some guidance?