Libelium Waspmote, Техническое руководство

Страница: 52 / 171

-52- v6.3
Energy System
6. Energy System
6.1. Concepts
Waspmote has 4 operational modes.
•
ON
: Normal operation mode. Consumption in this state is
15mA
.
• Sleep : The main program is paused, the microcontroller passes to a latent state, from which it can be woken up by all
asynchronous interruptions and by the synchronous interruption generated by the Watchdog. The duration interval of
this state is from 32ms to 8s . Consumption in this state is 55μA .
•
Deep Sleep
: The main program pauses, the microcontroller passes to a latent state from which it can be woken up by
all
asynchronous interruptions and by the synchronous interruption triggered by the RTC. The interval of this cycle can be
from
seconds to minutes, hours, days
. Consumption in this state is
55μA
.
• Hibernate : The main program stops, the microcontroller and all the Waspmote modules are completely disconnected.
The only way to reactivate the device is through the previously programmed alarm in the RTC (synchronous interrupt).
The interval of this cycle can be from seconds to minutes, hours, days . Almost all devices are totally disconnected from
the battery: only the RTC is powered through the battery, from which it consumes 0.06μA .
Consumption Micro Cycle Accepted Interruptions
ON 15mA ON - Synchronous and Asynchronous
Sleep
55μA ON 32ms - min/hours/days Synchronous (Watchdog) and Asynchronous
Deep Sleep
55μA ON 1s – min/hours/days Synchronous (RTC) and Asynchronous
Hibernate 0.06μA OFF 1s – min/hours/days Synchronous (RTC)
On the other hand, each
module
might have up to 4 operation modes.
•
ON
: Normal operation mode.
• Sleep : In this mode some module functions are stopped and passed to asynchronous use, normally guided by events. It
functions differently in each module and is specific to each one (programmed by the manufacturer).
• Hibernate : In this mode all module functions are stopped and passed to asynchronous use, normally guided by events.
It operates differently in each module and is specific to each one (programmed by the manufacturer).
•
OFF
: By using digital switches controlled by the microcontroller the module is switched off completely. This mode has
been implemented by
Libelium
as an
independent layer of energy control
, so that it can reduce consumption to a
minimum (
~0μA
) without relegating to techniques implemented by the manufacturer.
For complete information about interruption types and their handling, see the Interruption chapter.
Related API libraries:
WaspPWR.h
,
WaspPWR.cpp
All information about the programming and operation of interruptions can be found in the document:
Energy and Power
Programming Guide
.
All the documentation is located in the Development section in the Libelium website.
Note:
The sleep mode for XBee is not a very useful feature, since the advised action is to switch XBee off after transmission. If the user
puts XBee in sleep mode and also switches Waspmote to sleep or deepsleep, and if the SD card is plugged, there will be an excessive
power consumption: 220 μA or more (instead of the expected 110 μA). This is due to parasite power. To solve that, the user should not
use the XBee sleep mode. Another solution is to call
sleep()
or
deepsleep()
with
ALL_OFF
or
SOCKET0_OFF
parameters.