Support Home Portal Log in
Open navigation

Run Hour/ODO Discrepancies in TG

Run Hour and Odometer estimates for an asset are displayed in Telematics Guru in the following places.  

  1. On the Odo/Hours Page
  2. On the Manage Assets Grid
  3. In the Maintenance Schedules view
  4. On the Live View (web and app)
  5. In Run Hours Reports

How these readings are calculated is discussed here: Run Hours + Odometer in TG

Run Hours
Total Length of all trips (i.e. time between trip start and trip end logs)
Odometer Readings
Total distance of all trips. This is calculated by the distance between each point - or if on-board trip distance calculations are enabled on a device these values are used.

At times, there may be discrepancies between views 1-5 above. 

Telematics Guru stores an Odo/Run hour estimate in the database. This is only updated at the end of each trip. It is done this way for an important reason.

Consider a device which is driving, in trip, and drives out of coverage for a period of 1 day (24 hours)

  • It begins a trip and first leaves coverage when the run hours are 100 hours
  • It may leave coverage, and 1hr later, park just outside of coverage
  • As far as TG is concerned, until it returns to coverage, it is still in trip the entire time (as no further updates are received)
  • So if it stayed out of coverage for 1 day and run hours were just continuously updated during the trip, it would read 124hrs
  • Then, when returning to coverage, it would only drive for 1 more hour (1 hour out, park, 1 hour back) - so the run hours were actually only 102hrs
  • Depending on when reports are run, we might get different values, which we don't want.

Assets which may run for weeks on end (such as generators) can cause some strange behaviour.

The Run Hour/ODO database value is only updated on trip end for this reason. Some other values shown in TG however are the current Run Hour/ODO value + total trip time/distance. 

  1. Odo/Hours Page
    1. Displays database run hours value (only updated on trip end) + current total trip time
  2. Manage Assets Grid
    1. Displays the database run hours value
  3. Maintenance Schedules View
    1. Displays database run hours + total trip time
  4. Live view
    1. Displays database run hours + total trip time
  5. Run Hours Reports
    1. The Run Hour reports do not output the total lifetime reading - as the reports are based on a time period - i.e. run hours between 1st Jan and 1st Feb. Total trip time is included - any assets currently in trip are indicated as they have the potential to be incorrect if out of coverage. 


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.