Use this table to resolve the most common situations. If the problem continues, contact support (Appendix D).
| Situation | What it means | What to do |
|---|---|---|
| Unit shows Not Registered Yet | No data has been received since the unit was created. | Configure the device to send data to the server address and port shown in the Register Vehicle form, and check that the IMEI is correct (Chapter 4). |
| Unit shows GPS Not Updated | The device is sending data, but without a valid satellite position. | Check the device installation and GPS reception, and review the raw data in D-Logs (Chapter 14). |
| Unit is Offline | The device is not communicating with the platform. | Check the device power and connectivity. Use D-Logs to see when data was last received (Chapter 14). |
| Mileage differs from the vehicle odometer | The calculated mileage needs alignment. | Adjust Odometer (km) and Mileage Accuracy (%) in Mileage & Engine (Chapter 4). |
| Fuel fills or drains are missed or false | Fuel detection settings do not match the vehicle. | Review the sensor keys, fill/drain thresholds, Adaptive Mean and Fuel Accuracy in Fuel Settings (Chapter 4). |
| A sensor is not visible in Monitoring | The sensor is hidden from the Monitoring module. | Turn on the Monitoring toggle for that sensor in the Sensor tab (Chapter 4). |
| A command cannot be sent | The command is not assigned to the unit, or does not match the device. | Assign the command to the unit and check its syntax for the device model (Chapter 18). |
| A user cannot see some units | The units are not in the user’s access rights. | Grant access in Users or in the unit’s Access tab (Chapters 4 and 5). |
| A deleted record is missing | Deleted records are kept in Trash for 30 days. | Restore it from Trash within 30 days (Chapter 22). |
| A long date range is not accepted | Some features have a maximum date range. | Shorten the range; see Appendix A. |