Changes

=='''I'm Alive'''==

=='''I'm Alive'''==

<i>(Currently Evaluation FW)</i><br/>

<b>I‘m Alive</b> <i>(Currently Evaluation FW)</i><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/>

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/>

=='''SMS Record Sending'''==

=='''SMS Record Sending'''==

<b>SMS Record Sending</b> <i>(Currently Evaluation FW)</i><br/>

<i>(Currently Evaluation FW)</i><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/>

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/>

<br/>

<br/>

=='''Movement based tracking'''==

=='''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.<br/>

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.<br/>

<i>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.<br/>

<i>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.<br/>

<br/>

<br/>

=='''Movement events'''==

=='''Movement events'''==

<b>Movement events</b><i> (TAT100 – currently evaluation FW, TAT140 - available)</i><br/>

<i> (TAT100 – currently evaluation FW, TAT140 - available)</i><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/>

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/>

=='''Static Navigation'''==

=='''Static Navigation'''==

 

When enabled, TATXXX doesn't search for a new GNSS fix if no movement is detected. Instead, it sends the previously captured coordinate, saving power. This is especially beneficial for on stop periodic tracking.<br/>

When enabled, TATXXX doesn't search for a new GNSS fix if no movement is detected. Instead, it sends the previously captured coordinate, saving power. This is especially beneficial for on stop periodic tracking.<br/>

<i>Use case example: a client tracks construction equipment which have periods of inactivity. He wants to track it even during this inactivity to ensure that workers did not take that equipment elsewhere. So he uses both on move and on stop tracking, and also enables static navigation. It saves the battery for on stop records.</i><br/><br/>

<i>Use case example: a client tracks construction equipment which have periods of inactivity. He wants to track it even during this inactivity to ensure that workers did not take that equipment elsewhere. So he uses both on move and on stop tracking, and also enables static navigation. It saves the battery for on stop records.</i><br/><br/>

=='''Scheduler tracking'''==

=='''Scheduler tracking'''==

 

Track assets when theft is more likely, such as during work hours or on weekends. This strategy extends the device's lifetime. It also deters personal use of company cars on weekends. For largely stationary assets, opt for very infrequent records, even as rare as once per week.<br/>

Track assets when theft is more likely, such as during work hours or on weekends. This strategy extends the device's lifetime. It also deters personal use of company cars on weekends. For largely stationary assets, opt for very infrequent records, even as rare as once per week.<br/>

<i>Use case example: a client wants to ensure that employees do not use their company car for private matters on weekends. So he uses scheduler to track the car only on weekends.</i><br/>

<i>Use case example: a client wants to ensure that employees do not use their company car for private matters on weekends. So he uses scheduler to track the car only on weekends.</i><br/>

=='''LBS tracking mode'''==

=='''LBS tracking mode'''==

<b>LBS tracking mode</b> (TAT100 - available, TAT140 - Currently Evaluation FW)<br/>

<i>(TAT100 - available, TAT140 - Currently Evaluation FW)</i><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/>

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/>

=='''Temperature: reduce the number of records with operands'''==

=='''Temperature: reduce the number of records with operands'''==

 

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>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/>

<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/>