Odosync - How to; Virtual odometer

Role(s): RUC, Service, Unit Manager, Client Administrator.

Odosync (or ‘Odometer Sync' or ‘odometer synchronisation') is the process of calibrating the Ehubo’s GPS distance reading with the vehicle’s odometer reading on the Ehubo. Odosync is necessary, because of differences in tire diameter and operation: some vehicles start/stop more than others which can skew distance measurements, and some are ‘piggybacked’ or carried by other vehicles while still being tracked.

For Light vehicles in NZ, Odosync must be completed 3 times over the first 2000 km of driving to enable MyEROAD AutoRUC.

To enable Odosync:

  1. Administration > Vehicles/Assets

  2. Select a vehicle. The vehicle's drawer will open.

  3. Click Manage Features.

  4. Toggle the 'Odosync prompt' ON/OFF.

Every time this feature is set to ON, the calibration process begins again with Odosync prompts at 500, 1000, and 2000 km, by default.

Additional Odosync prompts can be configured by EROAD on behalf of the Customer org upon request (either by distance driven or elapsed time).

EROAD recommends that Light Vehicles be odosynced either every 2000 km or every month, after the initial Odosync is completed.

Frequency recommendations

New light vehicles should aim to sync the Ehubo with the vehicle’s odometer every week, or every 4000 km - whichever comes first.

After that, every 2000 km or once a month (this can be configured by EROAD for you on request).


Issues: Significant Odometer Jump (Odojump)

If the vehicle operator enters a vehicle odo reading that's out by more than 1000 km of an acceptable range, Odosync cannot be completed on the Ehubo screen. Instead, the operator is advised to contact their supervisor to perform Odosync via MyEROAD.

Odojump restriction will not apply for the first ever Odosync after an Ehubo is provisioned for a vehicle. When an Ehubo is provisioned, the virtual odometer is NULL – there is no prior Odosync. Therefore, Odojump cannot use the virtual odometer as a reference to protect against large offsets in the manual input.

Common Odojump causes

  • Incorrect input by operator, mistake or otherwise

  • Changing the tire size or other vehicle modifications

  • Vehicle towed or transported (e.g. 'piggyback' on a trailer or on a ferry), where the Ehubo keeps accruing distance due to GPS movement

Service and Maintenance schedules may shift

As vehicle maintenance and service schedule can be configured by the Ehubo reading (default) or the virtual odometer, setting a vehicle to perform an Odosync will automatically configure the vehicle to use the MyEROAD Virtual Odometer, without warning or notification.

Odosync How-to

On the Ehubo:

  1. The Odosync prompt appears on the Ehubo screen.


  2. OK. The numberpad screen opens.

  3. Enter the vehicle’s odo reading, and tap DONE.

  4. Acknowledge the distance check with CHANGE or CONFIRM.


If you enter a number that’s 1000 km outside of the expected distance value, you may be asked to contact your manager for a maintenance check.

If the number was in range but incorrectly entered, tap CHANGE and re-enter the number.

Virtual Odometer

The virtual odometer ('Virtual-odo') on MyEROAD is a digital 'counter', which is the Ehubo distance reading, with odosynced calibration. For fleet managers, administrators, tax users and other MyEROAD users, Virtual-odo is a more practical indicator of vehicle odometer than the Ehubo reading.

odosync virtual odo01

Odosync and RUC

Provisioning an Ehubo to a vehicle is the equivalent of a fresh, new install. In NZ, this also requires a RUCHO process to be completed for RUC-eligible vehicles.

Heavies (vehicles over 3.5 t)

Odosync has no impact on RUC for Heavies. Heavies are legally required to use approved electronic distance recorders to track distance travelled, and hence RUC licenses too.

But Heavies can still use Odosync if needed (Note: Odosync will automatically configure the service schedule to use virtual odometer instead of Ehubo reading). MyEROAD users can also manually trigger an Odosync prompt on a specific Ehubo. This will be a one-time prompt, unlike the 500 km/1000 km/2000 km calibration cycle. 

Lights (vehicles under 3.5 t)

For Lights, RUC is based on the vehicle odometer. EROAD’s Virtual-Odo is a reflection of the vehicle odometer. Automatic RUC license renewal (AutoRUC) relies on Virtual-Odo, and is impacted by Odosync. For this reason, the Odojump protection limits the impact on the virtual odometer and RUC.