Low Power Configuration: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
'''''[[KontroLIR - Arduino compatible IR remote control|> KontroLIR Home]]''''' | '''''[[KontroLIR - Arduino compatible IR remote control|> KontroLIR Home]]''''' | ||
We have designed the reference firmware to operate in an extremely low power mode when idle. | We have designed the reference firmware to operate in an extremely efficient low power mode when idle ''(i.e. in standby / PWR_DOWN mode)''. | ||
In | In PWR_Down mode, the device typically uses less than 1uAmp of current, which means batteries could last up to several years. Depending on level of usage, we expect battery life to be from 1 to 2 years or more. | ||
The firmware, also checks whether the device is being powered from a USBserial adapter(5V) or 2xAAA batteries. | The firmware, also checks whether the device is being powered from a USBserial adapter(5V) or 2xAAA batteries. When not running on batteries (supply voltage is greater than 4 Volts), the system does not enter sleep mode. For battery operation, the system automatically goes to sleep after sending any outstanding IR signals. | ||
On start-up, any unused peripherals are disabled to reduce power and when entering PWR_Down mode (sleep/standby) all other active peripherals are disabled. the system is awoken by a pin change interrupt resulting from a press of any of KontroLIR's buttons. | |||
Most users, should leave all of low power operations as is. Any future improvements will be made available for use. | In debug mode, the UART peripheral is re-enabled on wake-up as it is required to print debug information to serial. DEBUG should bw disable for norma operation. | ||
Most users, should leave all of the low power operations as is. Any future improvements will be made available for use. | |||
Advanced users can try to implement even lower power operation and are welcome to contribute any improvements to the code base. | Advanced users can try to implement even lower power operation and are welcome to contribute any improvements to the code base. | ||
The external I2C EEPROM and IR receivers are typically powered via GPIO pins and are typically powered off when not in use. The user is responsible for powering these on when used. | The external I2C EEPROM and IR receivers are typically powered via GPIO pins and are typically powered off when not in use. The user is responsible for powering these on when used. If they are left powerd on during idle this will reduce batterylife significantly. There is no need for these to be powered on during IDLE. | ||
The low power operations are generally implemented in the following files and functions: | The low power operations are generally implemented in the following files and functions: | ||
Revision as of 06:52, 7 October 2019
We have designed the reference firmware to operate in an extremely efficient low power mode when idle (i.e. in standby / PWR_DOWN mode).
In PWR_Down mode, the device typically uses less than 1uAmp of current, which means batteries could last up to several years. Depending on level of usage, we expect battery life to be from 1 to 2 years or more.
The firmware, also checks whether the device is being powered from a USBserial adapter(5V) or 2xAAA batteries. When not running on batteries (supply voltage is greater than 4 Volts), the system does not enter sleep mode. For battery operation, the system automatically goes to sleep after sending any outstanding IR signals.
On start-up, any unused peripherals are disabled to reduce power and when entering PWR_Down mode (sleep/standby) all other active peripherals are disabled. the system is awoken by a pin change interrupt resulting from a press of any of KontroLIR's buttons.
In debug mode, the UART peripheral is re-enabled on wake-up as it is required to print debug information to serial. DEBUG should bw disable for norma operation.
Most users, should leave all of the low power operations as is. Any future improvements will be made available for use.
Advanced users can try to implement even lower power operation and are welcome to contribute any improvements to the code base.
The external I2C EEPROM and IR receivers are typically powered via GPIO pins and are typically powered off when not in use. The user is responsible for powering these on when used. If they are left powerd on during idle this will reduce batterylife significantly. There is no need for these to be powered on during IDLE.
The low power operations are generally implemented in the following files and functions:
- KIR-MISC-functions.ino => initPins
- KIR-MISC-functions.ino => initLowPowerSleep
- KIR-MISC-functions.ino => goToSleep