Missing Trips

Missing Trips

When a User navigates to the History section of the platform, expecting to see trips, and does not, we consider these "missing trips". 


Trips in the platform are created from Ignition On to Ignition Off messages. The first Ignition On message is the start of a trip, and the first Ignition Off message the end of the trip.


Missing trips are the result of two main causes:


1. No data from the Device

  • The Device has sent no data for whatever reason, and

2. No ignition messages being recognised by the platform 

  • No ignition option chosen on the Device on the platform, or
  • The ignition option chosen does not correspond to the installation of the device.


To determine if trips are really missing, or whether the ignition messages are the problem, use Slow Mode in the History tab. 


Navigate to History and click on the Options drop down box. Choose Mode, then Slow (scans all data).



The platform will attempt to reconstruct Trips based on data received, if available. If no Trips appear, filter the data. Navigate to History and click on the Options drop down box. Choose Filter, then choose Show All at the top of the list.



If no Trips are created, check the telmetry. If this is blank, there is no data from the Device to create Trips from. Please check the SIM card has data and if so, the Device for any fault.



If there are Trips, however no ignition noticed in the data, check and change the Ignition Input on the Device, if needs be. Navigate to Administration, and the Device in question.



Scroll down the Details tab of the Device to the Inputs & Outputs section. Check the Ignition Input. If this needs to be changed, click Edit.



To change the Ignition Input, click on the drop down list and choose the Ignition Input that corresponds to the installation. Once chosen, click Save.




If the Ignition Input is correct, please check the installation wiring. 


NOTE: 
  • OBDII Devices may not pick up a proper ignition sense from the vehicle, and therefore different ignition inputs can be tried to see which reflects the most accurate trips,
  • If none of the above assist in rectifying the trips, please contact the hardware manufacturer to ascertain the possible cause. If needs be, add the telemetry data for the Device and day in question.

 


    • Related Articles

    • Strange trips

      Strange Trips Trips in the platform are created from Ignition On to Ignition Off messages. The first Ignition On message is the start of a trip, and the first Ignition Off message the end of the trip. The platform supports data from the devices in ...