Low Power Configuration - Revision history

AnalysIR at 15:48, 10 December 2019

2019-12-10T15:48:53Z

← Older revision		Revision as of 08:48, 10 December 2019
Line 5:		Line 5:
	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.		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 never enters sleep mode~~. ~~For battery operation, the~~ system automatically goes to sleep after sending any outstanding IR signals.		The firmware, also checks whether the device is being powered from a USBserial adapter(5V) or 2xAAA batteries and sets a variable (usbPowered) to true or false accordingly. When not running on batteries (i.e. supply voltage is greater than 4 Volts) the variable is set to true. The system automatically goes to sleep after sending any outstanding IR signals. The only exception is the bootloader 30 second delay(with blinking red LED) which is triggered automatically on power-up and if powered from USB when the buttons 1,3,7,9 are pressed in sequence.

			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.

	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 be disabled for normal battery operation.

	In debug mode, the UART peripheral is re-enabled on wake-up as it is required to print debug information to serial. DEBUG should be disabled for normal operation.

	Most users, should leave all of the low power operations as is. Any future improvements will be made available for use.		Most users, should leave all of the low power operations as is. Any future improvements will be made available for use.
Line 19:		Line 18:

	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:
	* KIR_MISC-functions.ino => KIR_initPins		* KIR_MISC-functions.ino => KIR_initPins()
	* KIR_MISC-functions.ino => KIR_initLowPowerSleep		* KIR_MISC-functions.ino => KIR_initLowPowerSleep()
	* KIR_MISC-functions.ino => KIR_goToSleep		* KIR_MISC-functions.ino => KIR_goToSleep()


	'''''[[KontroLIR - Arduino compatible IR remote control\|> KontroLIR Home]]'''''		'''''[[KontroLIR - Arduino compatible IR remote control\|> KontroLIR Home]]'''''

AnalysIR at 12:04, 11 November 2019

2019-11-11T12:04:17Z

← Older revision		Revision as of 05:04, 11 November 2019
Line 16:		Line 16:
	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. 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 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 powered on during idle this will reduce battery life 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:
	* ~~KIR-MISC~~-functions.ino => ~~initPins~~		* KIR_MISC-functions.ino => KIR_initPins
	* ~~KIR-MISC~~-functions.ino => ~~initLowPowerSleep~~		* KIR_MISC-functions.ino => KIR_initLowPowerSleep
	* ~~KIR-MISC~~-functions.ino => ~~goToSleep~~		* KIR_MISC-functions.ino => KIR_goToSleep


	'''''[[KontroLIR - Arduino compatible IR remote control\|> KontroLIR Home]]'''''		'''''[[KontroLIR - Arduino compatible IR remote control\|> KontroLIR Home]]'''''

AnalysIR at 17:48, 24 October 2019

2019-10-24T17:48:29Z

← Older revision		Revision as of 10:48, 24 October 2019
Line 10:		Line 10:
	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.		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.		In debug mode, the UART peripheral is re-enabled on wake-up as it is required to print debug information to serial. DEBUG should be disabled for normal operation.

	Most users, should leave all of the low power operations as is. Any future improvements will be made available for use.		Most users, should leave all of the low power operations as is. Any future improvements will be made available for use.

AnalysIR at 17:47, 24 October 2019

2019-10-24T17:47:18Z

← Older revision		Revision as of 10:47, 24 October 2019
Line 5:		Line 5:
	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.		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.		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 never enters sleep mode. For battery operation, the system automatically goes to sleep after sending any outstanding IR signals.

AnalysIR at 14:52, 7 October 2019

2019-10-07T14:52:11Z

← Older revision		Revision as of 07:52, 7 October 2019
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 ~~Power_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.		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. ~~For 5V~~, the system ~~runs at 16MHz and~~ does not enter sleep mode. For battery operation, the system ~~defaults to running at 8MHz and~~ automatically goes to sleep after sending any outstanding IR signals.		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 sytem is awoken by a pin change interrupt on any of the remote's buttons.

	~~In debug~~ mode, the ~~UART peripheral~~ is ~~re-enabled on wake-up as it is required to print debug information to serial~~.		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:

AnalysIR at 12:22, 6 October 2019

2019-10-06T12:22:45Z

← Older revision		Revision as of 05:22, 6 October 2019
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 low power mode when idle.
Line 23:		Line 23:


	[[KontroLIR - Arduino compatible IR remote control\|=> KontroLIR Home]]		'''''[[KontroLIR - Arduino compatible IR remote control\|> KontroLIR Home]]'''''

AnalysIR at 11:28, 6 October 2019

2019-10-06T11:28:47Z

← Older revision		Revision as of 04:28, 6 October 2019
Line 1:		Line 1:
			[[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 low power mode when idle.

Line 19:		Line 21:
	* KIR-MISC-functions.ino => initLowPowerSleep		* KIR-MISC-functions.ino => initLowPowerSleep
	* KIR-MISC-functions.ino => goToSleep		* KIR-MISC-functions.ino => goToSleep


			[[KontroLIR - Arduino compatible IR remote control\|=> KontroLIR Home]]

AnalysIR at 15:18, 5 October 2019

2019-10-05T15:18:14Z

← Older revision		Revision as of 08:18, 5 October 2019
Line 15:		Line 15:
	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.

	The low power operations are generally implemented in the following files~~/functiond~~:		The low power operations are generally implemented in the following files and functions:
	* KIR-MISC-functions.ino => initPins		* KIR-MISC-functions.ino => initPins
	* KIR-MISC-functions.ino => initLowPowerSleep		* KIR-MISC-functions.ino => initLowPowerSleep
	* KIR-MISC-functions.ino => goToSleep		* KIR-MISC-functions.ino => goToSleep

AnalysIR: Created page with "We have designed the reference firmware to operate in an extremely low power mode when idle. In Power_Down mode, the device typically uses less than 1uAmp of current, which m..."

2019-10-05T15:16:07Z

Created page with "We have designed the reference firmware to operate in an extremely low power mode when idle. In Power_Down mode, the device typically uses less than 1uAmp of current, which m..."

New page

We have designed the reference firmware to operate in an extremely low power mode when idle.

In Power_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. For 5V, the system runs at 16MHz and does not enter sleep mode. For battery operation, the system defaults to running at 8MHz and 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 sytem is awoken by a pin change interrupt on any of the remote's buttons.

In debug mode, the UART peripheral is re-enabled on wake-up as it is required to print debug information to serial.

Most users, should leave all of 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.

The low power operations are generally implemented in the following files/functiond:
* KIR-MISC-functions.ino => initPins
* KIR-MISC-functions.ino => initLowPowerSleep
* KIR-MISC-functions.ino => goToSleep