Maximize battery life of asset trackers: Difference between revisions
No edit summary |
No edit summary |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
=='''I'm Alive'''== | =='''I'm Alive'''== | ||
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.<br/> | 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.<br/> | ||
<u>"I'm alive" checks save up to 50% battery power compared to regular records.</u><br/> | <u>"I'm alive" checks save up to 50% battery power compared to regular records.</u><br/> | ||
| Line 14: | Line 14: | ||
=='''SMS Record Sending'''== | =='''SMS Record Sending'''== | ||
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.<br/> | 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.<br/> | ||
<u>Battery savings: up to 30% lower consumption than standard record.</u><br/> | <u>Battery savings: up to 30% lower consumption than standard record.</u><br/> | ||
<i>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.</i><br/> | <i>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.</i><br/> | ||
<br/> | <br/> | ||
=='''Movement based tracking'''== | =='''Movement based tracking'''== | ||
| Line 26: | Line 27: | ||
<br/> | <br/> | ||
=='''Movement events'''== | =='''Movement events'''== | ||
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.<br/> | 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.<br/> | ||
<i>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.</i><br/> | <i>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.</i><br/> | ||
| Line 43: | Line 44: | ||
=='''LBS tracking mode'''== | =='''LBS tracking mode'''== | ||
LBS is a less precise but battery-saving tracking method using cell towers. When high precision isn't crucial, LBS can extend battery life. Note, it sends an LBS data list, from which coordinates can be calculated on the platform.<br/> | LBS is a less precise but battery-saving tracking method using cell towers. When high precision isn't crucial, LBS can extend battery life. Note, it sends an LBS data list, from which coordinates can be calculated on the platform.<br/> | ||
<u>Battery savings: around 30%</u><br/> | <u>Battery savings: around 30%</u><br/> | ||
| Line 51: | Line 52: | ||
Set up TATXXX to send temperature records only if the specified range is breached. For instance, if the range is -20 to -10, TATXXX scans periodically and triggers an alarm for -22. If within range, it saves battery by not sending records unnecessarily.<br/> | Set up TATXXX to send temperature records only if the specified range is breached. For instance, if the range is -20 to -10, TATXXX scans periodically and triggers an alarm for -22. If within range, it saves battery by not sending records unnecessarily.<br/> | ||
<u> | <u>Bluetooth® scanning consumes much less power than record sending. However, very frequent sensor scans may still drain the battery, so it's recommended to scan every ~3 hours or less frequently.</u><br/> | ||
<i>Use case example: a company transports temperature-sensitive goods, requiring the range to stay between -20 and -5. They employ the EYE Sensor and TATXXX with | <i>Use case example: a company transports temperature-sensitive goods, requiring the range to stay between -20 and -5. They employ the EYE Sensor and TATXXX with Bluetooth® scanning every 3 hours. If the temperature drops to -22 during a scan, TATXXX sends a record for the manager to take action.</i> | ||
| Line 58: | Line 59: | ||
[[Category:TAT100 Configuration]] | [[Category:TAT100 Configuration]] | ||
[[Category:TAT140 Configuration]] | [[Category:TAT140 Configuration]] | ||
[[Category:TAT141 Configuration]] | |||
[[Category:TAT240 Configuration]] | |||