Line 29: |
Line 29: |
| 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/> |
| 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.<br/> | | 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.<br/> |
− | [[File:TAT100_Movement_Events.png|border|class=tlt-border|500px]]<br/> | + | [[File:TAT100 Movement Events.png|border|class=tlt-border|500px]]<br/> |
| | | |
| <b>Static Navigation </b> <br/> | | <b>Static Navigation </b> <br/> |
Line 38: |
Line 38: |
| 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/> |
− | [[File:TAT100_Scheduler.png|border|class=tlt-border|500px]]<br/> | + | [[File:TAT100 Scheduler.png|border|class=tlt-border|500px]]<br/> |
| | | |
| <b>LBS tracking mode</b> (TAT100 - available, TAT140 - Currently Evaluation FW)<br/> | | <b>LBS tracking mode</b> (TAT100 - available, TAT140 - Currently Evaluation FW)<br/> |