Maximize battery life of asset trackers

Revision as of 06:45, 2 October 2023 by Karolis.C (talk | contribs) (Created page with "==Maximizing Battery Life== TAT family trackers offer various features to significantly extend battery life. These features can be used individually or combined for enhanced...")

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)
Main Page > Autonomous Trackers > TAT100 > TAT100 Configuration > Maximize battery life of asset trackers

Maximizing Battery Life

TAT family trackers offer various features to significantly extend battery life. These features can be used individually or combined for enhanced effectiveness.
1.1 I’m Alive Feature
1.2 SMS Record Sending
1.3 Movement-based tracking
1.4 Movement events
1.5 Static Navigation
1.6 Scheduler tracking
1.7 LBS tracking mode
1.8 Temperature with operands

I‘m Alive (Currently Evaluation FW)
This feature wakes up the device more frequently to check for pending commands, without using GNSS or sending records. It allows for a reduced periodic tracking frequency, as location can be requested via SMS/GPRS commands, triggering frequent reporting or configuration changes. The most frequent "I'm alive" check occurs every 3 hours. "I'm alive" checks save up to 50% battery power compared to regular records. Use case example: leasing company needs to track their cars only when they are stolen. Their core need is seamless device installation and possibility to learn the location when the machinery is stolen. They disable periodic records for battery saving, relying on the "I'm alive" feature. When theft occurs, they send an SMS/GPRS command to activate TAT recovery mode with frequent reporting.
SMS Record Sending (Currently Evaluation FW)
It enables data retrieval without server connection, reducing power usage. SMS records contain fixed information determined by device configuration (e.g., Location Source - LBS or GNSS) and triggering event.
Battery savings: up to 30% lower consumption than standard record.
Use case example: it may be used for all use cases as with regular reporting, the main requirement is that clients have software that supports SMS records.

Movement-based tracking
TATXXX is primarily used for theft prevention and recovery. Since thieves typically move the asset during theft, tracking it only during motion reduces unnecessary records when stationary and increases the total number of relevant records when in motion.
Use case example: if a car is stolen, it obviously needs to be driven/towed (moved), and if it is parked for weeks (stopped), then what’s the point of tracking it? If that’s the case, on stop records may be turned off, which would help to achieve much more relevant (on move) records with the same battery.
If a car is stolen, it will be in motion (driven/towed). If it's simply parked for an extended period, tracking becomes irrelevant. In this case, turning off "on stop" records saves battery power and results in more total records during motion.

Movement events (TAT100 – currently evaluation FW, TAT140 - available)
This feature sends a movement event with the last known coordinates when the asset starts moving, without using power for a new GNSS fix (if a previous fix was successful). This speeds up the process and reduces battery usage for record transmission.
Use case example: when a user rents a construction generator and picks it up, the device can send a movement event with the last known coordinates without performing a new GNSS fix. This conserves battery power and ensures that the location information is quickly and accurately transmitted to the server, allowing the rental company to monitor the movement of their assets efficiently.