%&'"()*+,,-,,.".
! 2'$'
! #
From the functional point of view, owa4x can work in one of the following
functional modes:
State Short
Description
Active Circuits Wakeup
sources
Wake up
time
Power
sources
No Power No power
supply
available.
RTC V_IN
Main bat
n.a. Backup
battery
OFF Minimal power. RTC
Dig inputs
Movement
RS232-RX0
RTC
Main bat
DIN0..9
Movement
RX0
Slow
(boot)
V_IN, Main
Battery
STANDBY Low power
with fast
response to
wakeup
events.
RTC
Movement
Dig inputs
CPU (halt)
RAM (refresh)
GSM
RS232
CAN
RTC
Main bat
DIN0..9
Movement
RX0
GSM event
CAN1
Fast V_IN, Main
Battery
RUN All circuits
running.
All n.a.
All events
monitored
n.a. V_IN, Main
Battery
4.1 owa4x functional modes
Once the owa4x is switched on, it starts executing the boot loader. Then, if the
user stops the process, the owa4x will remain in Service Mode. Otherwise the
owa4x continues loading the kernel and the file system.
The customer application is able to select the desired mode, usually based on
the current consumptions.
In Run mode the microprocessor is running at 800 MHz. If the customer
application wants or needs lower speed, it can send the owa4x to either
Standby or Off mode (see owa4x Programming Reference Manual and
Programming guide).
From Standby and Off modes, the customer application can wake up the owa4x
to Run mode with an event preconfigured with a mask. The difference between
Standby and Off modes are the possible events that will be listened for as
trigger conditions. For further information about the trigger possibilities, see the
Programming guide.
These modes offer the possibility to build powerful and flexible applications that
can handle situations where power supply can be constrained.
! '
The owa4x is a unit designed to run at all times, as it will be installed in remote
places. As such, the power management will reset the unit whenever the main
system is not running, and that means that the standard “poweroff –halt” or
/2
To Next Page
Loading...
General