Справочник Пользователя для Imarda New Zealand Limited V301-IX
V301 – User Manual
© IMARDA | 2016
Confidential
DC300P3618_V7
14
4.4
Backup Battery
The Vector 301 has a 2200mAh backup battery. The battery backup is provided for two reasons - firstly to
let the operating system do an orderly shutdown in the event of power loss or deep voltage dips during
starter motor cranking, and secondly to provide sufficient time to send notifications of power failure or
accident in the event of power being suddenly removed.
As the usage of the backup battery during normal operation is minimal, one of the design trade-offs made
in Vector 301 is a long recharge time (to minimise power supply requirements). A full recharge can take 15
Hours, as the charging current is limited to around 150mA. Charging time is also dependent on
temperature. For example, battery charging is disabled below 0C as LiPo batteries cannot be charged
below this temperature or above 45C
Operating time on the optional backup battery is up to 2 hours. This varies according to temperature.
let the operating system do an orderly shutdown in the event of power loss or deep voltage dips during
starter motor cranking, and secondly to provide sufficient time to send notifications of power failure or
accident in the event of power being suddenly removed.
As the usage of the backup battery during normal operation is minimal, one of the design trade-offs made
in Vector 301 is a long recharge time (to minimise power supply requirements). A full recharge can take 15
Hours, as the charging current is limited to around 150mA. Charging time is also dependent on
temperature. For example, battery charging is disabled below 0C as LiPo batteries cannot be charged
below this temperature or above 45C
Operating time on the optional backup battery is up to 2 hours. This varies according to temperature.
4.5
Wakeup Sources
The Vector 301 can be placed into a suspend state or Off state
When in suspend, the following conditions will wake the Vector 301 back to the "On" state:
When in suspend, the following conditions will wake the Vector 301 back to the "On" state:
1.
State change from low (0V) to high (>7V) on the ignition line
2.
Accelerometer (if enabled, can be enabled via software)
3.
Incoming calls/message from modem (if enabled)
4.
4 of the Digital Inputs (if enabled)
5.
Real Time Clock (if enabled)
6.
GPS Antenna Fault
The following conditions can be programmed to wake the Vector 301 from a "Off" state:
1.
State change from low (0V) to high (>7V) on the ignition line
2.
Accelerometer (if enabled, can be enabled via software,)
3.
Real Time Clock (if enabled)
4.6
File System
The Vector 301 uses FLASH memory, which is persistent storage designed to retain data at power loss, but
not meant for heavy amounts of I/O or large amounts of data transfer. The FLASH memory in the Vector
301 makes use of a file system manager specifically designed to minimize/distribute wear to the use-
sensitive FLASH memory.
Although the underlying hardware implementation is different, the application developer will read and write
to FLASH memory the same way they would on a traditional Windows machine with a hard drive. The .NET
Compact Framework uses the same functions as the traditional framework to read and write from the file
system.
READ FIRST: FLASH memory has a limited lifetime based on number of writes. The FLASH
memory used in the Vector 301 has a minimum write threshold of 100,000 times; beyond that reliability
and performance are not guaranteed. Applications should be designed/coded keeping this limitation in
mind at all times.
For example, if planning for data logging on Vector 301, implement a simple buffer. Hold the data in
memory for a period (eg. an hour or two), and then flush it to disk only on a schedule only as frequent as
is required by your specifications. This practice will significantly extend the lifetime of the Vector 301's
flash memory.
not meant for heavy amounts of I/O or large amounts of data transfer. The FLASH memory in the Vector
301 makes use of a file system manager specifically designed to minimize/distribute wear to the use-
sensitive FLASH memory.
Although the underlying hardware implementation is different, the application developer will read and write
to FLASH memory the same way they would on a traditional Windows machine with a hard drive. The .NET
Compact Framework uses the same functions as the traditional framework to read and write from the file
system.
READ FIRST: FLASH memory has a limited lifetime based on number of writes. The FLASH
memory used in the Vector 301 has a minimum write threshold of 100,000 times; beyond that reliability
and performance are not guaranteed. Applications should be designed/coded keeping this limitation in
mind at all times.
For example, if planning for data logging on Vector 301, implement a simple buffer. Hold the data in
memory for a period (eg. an hour or two), and then flush it to disk only on a schedule only as frequent as
is required by your specifications. This practice will significantly extend the lifetime of the Vector 301's
flash memory.