Summary:
"Trips" are generated when there is an ignition on and then off and an asset moves from point A to point B. When viewing the Trips page, you should see a list of trips in the Trips Panel.
If trips are not appearing, it's often due to the tracker not being configured correctly. To generate trips, the device must send the following data:
Ignition or Motion Events
Odometer Readings
Most GPS tracking devices support sending this data. If they are not already enabled, you can activate them via SMS or GPRS commands provided by the hardware manufacturer.
A trip starts when the tracker sends an ignition ON or motion ON event.
A trip ends when it sends an ignition OFF or motion OFF event.
If the distance travelled is less than 100 metres, it will be treated as a zero-distance trip and hidden by default.
To view these, enable the “Show Zero Distance Trips” checkbox on the Trips page.
Short trips: our system require a minimum distance (e.g. 100 meters) otherwise it will be considered a zero distace trip.
Hardware limitations: Some budget devices don’t support sending odometers and/or ignition/motion events
Hardware configuration: The device is not configured to send odometer and/or ignition/motion events
Hardware Installation: The ignition/digital input 1 wire on tracker is not connected/is loose
Check Tracker Data Flow
Ensure data is being received from the tracker and is up to date.
Confirm the tracker is configured to send records in chronological order (oldest first).
Some trackers support a diagnostic command to check if messages are being buffered—refer to the device documentation or contact the manufacturer.
Verify Ignition Events on the Platform
Navigate to Asset Info → Events and check for ignition ON/OFF events around the time of the trip.
If ignition events are missing:
Contact the manufacturer to confirm whether the device supports ignition events.
Request the relevant SMS or GPRS command to enable ignition detection.
If the device doesn't support ignition events, you can enable ignition override in Admin → Device → Advanced.
Verify Ignition Status on the Platform
Go to Asset Info → Info → Telemetry an check for ignition status changes around the time of the trip.
If the ignition status is not changing when the trip started/stopped the tracker is not detecting ignition correctly
For a vehicle tracker with an ignition wire, check the wire is not loose / is connected
For a vehcile tracker without an ignition wire (2 wire installation) check the ignition detection setting - this might be voltage range or motion detection - for voltage range check the upper and lower boundary and consider if its installed in a 12v or 24v battery
Check Odometer Readings
Go to Asset Info → Info → Telemetry and verify that the odometer was incrementing during the trip.
If the odometer remains at 0 or does not increment:
Contact the manufacturer to confirm if odometer reporting is supported.
Ask for the required SMS or GPRS command to enable odometer transmission.
If the hardware does not support this feature, use the odometer override in Admin → Device → Advanced.
There are three methods used to calculate odometer readings, depending on the capabilities of the tracker and vehicle:
1. Tracker-Based (GPS Odometer) — Most Common
This is the most widely used method.
The tracker calculates odometer readings virtually using GPS coordinates.
As the device moves from one point to another, the distance is measured and incrementally added to the odometer value.
This method works on any asset type, does not require vehicle integration and works purely from location data.
2. Tracker-Based (CAN Bus Odometer) — Less Common
Used when the tracker and vehicle both support CAN Bus integration.
The tracker reads the physical odometer value directly from the vehicle’s onboard computer via the CAN bus.
This provides the most accurate reading but requires proper installation and configuration.
The platform estimates distance based on GPS positions received from the tracker.
While useful for low-cost or basic trackers, it may be less accurate than tracker-based methods.
If your odometer is not showing any movement or remains at zero, it could be due to one of the following reasons:
1. The Device is Not Properly Configured
The tracker may not be sending odometer data to the platform due to incorrect configuration.
Ensure the odometer feature is enabled using the correct SMS or GPRS commands.
2. The Device Doesn't Support Odometer Calculation
Some low-cost or basic trackers lack built-in odometer functionality.
In this case, consider using the platform-based odometer override.
3. Poor Installation (Ignition Wire Not Connected)
Certain trackers only start accumulating distance after receiving an ignition signal.
If the ignition wire is not connected, the device may not calculate or report odometer data at all.
To get better trip and odometer tracking:
Increase your reporting frequency (e.g., 30 seconds or event-based).
Use devices with ignition detection and CAN support, if you want odometer from the vehicle.
Avoid budget hardware with limited capabilities for ignition and odometer reporting
We recommend Teltonika or similar devices that offer:
Ignition + movement trip logic
Virtual odometer smoothing
CAN integration (on supported models)
As a last resort, you can enable a software override for trip detection. This should only be used if the tracker hardware does not support ignition events or odometer readings.
Navigate to admin, select your client, navigate to devices and click edit