Unit-based odometer and engine hours means that the odometer and engine hours values can be stored on the device directly and applies to the MiX 2000, MiX 4000 and MiX 6000 devices.
Users are able to send these values to the on-board computer using MiX Fleet Manager or the MiX TechTool.
The following is required to move the odometer and engine hours reading from being stored on the server to the mobile device:
The unit has to be running firmware version 4.8 or newer. This functionality is only available with firmware version 4.8 and units running previous versions of firmware will still store and calculate their values server-side. When the firmware version has not been reported to MiX Fleet Manager, the system will default to setting a unit-based odometer value by default and assume it is FW 4.8.
The firmware version is only reported when it sends its daily status message (every 24 hours), when the mobile device reboots, or when a new firmware set is loaded.
Odometer and Engine Hour readings are maintained in the firmware. All server-side offsets stored in the Data Processor are cleared for units running 4.8 and above or where firmware is not known. Changes to the odometer values from MiX Fleet Manager or the MiX TechTool are implemented by sending a trip-safe offset command to the unit to inform it of its odometer reading.
You have to navigate to the Set odometer and Set engine hours pages (see detailed steps below) and set the odometer and engine hours.
Please note that a configuration upload and a subsequent trip is required after loading FW 4.8 in order to set the Engine hours.
Set odometer offset on mobile device
Note: the odometer will only be applied on the the unit when the asset is out of trip - this is different to the server-side solution.
- Click Monitor.
- Under Fleet Admin, click Assets.
- Search for the relevant asset, click the downward actions arrow and select Edit.
- Click on the Mobile device settings tab on the left.
- Click the Set odometer button. Important note: If the asset is currently in trip then the new odometer value will only be applied once the asset is out of trip and will be calculated based on the end of trip odometer reading. The updated value will only be displayed in MiX Fleet Manager at the end of the next trip.
Important Notes
MiX Fleet Manager stores the last received odometer value from the unit which was sent at trip end and displays this on the Assets page. The diagnostics page will show the latest odometer value.
The command will automatically try to upload for a period of 24 hours. If the command fails to upload it will attempt for another three times. You cannot send the command again in this period.
Troubleshooting - why was the odometer value not set?
- Is the unit running firmware version 4.8 or later?
- Is the asset currently in trip?
- Is there a pending set ODO command? (You cannot set the odometer value multiple times if it has not been applied yet.)
Move engine hours from config to firmware
When config is loaded to a MiX 4000 unit with a firmware version that supports on-board engine hours, an additional action-sequence will be sent by the unit along with the regular engine hours related FmConfigEvent.
Upon receipt, the difference between the actual engine hours (received from the server-side value) and what is reported by firmware (above) will be calculated. This offset value is sent to the unit by invoking the SendEngineHoursOffsetCommandToMobileUnit manager in the Config API.
A newly defined "E/H transition state" value is set to indicate that the above process has completed.
Set engine hours offset on mobile device
Note: engine hours will only be applied on the unit when the asset is out of trip - this is different to the server-side solution.
- Click Monitor.
- Under Fleet Admin, click Assets.
- Search for the relevant asset, click the downward actions arrow and select Edit.
- Click on the Mobile device settings tab on the left.
- Click the Set engine hours button. Important note: If the asset is currently in trip then the new engine hours value will only be applied once the asset is out of trip and will be calculated based on the end of trip engine hours reading. The updated value will only be displayed in MiX Fleet Manager at the end of the next trip.
It is important to note that a configuration upload and a subsequent trip is required after loading FW 4.8 in order to set the Engine hours.
Troubleshooting - why was the engine hour value not set?
- Is the FW version running on the unit 4.8 or later?
- Is the asset currently in trip?
- Is there a pending set engine hours command? Remember you cannot set engine hours when there is a pending engine hours command that has not been applied.
You can monitor the uploads by viewing the asset's comms log. The Comms log for the MiX 2000, MiX 4000, and MiX 6000 will include the set odometer and engine hour commands. It is important to note that the odometer and engine hours offset, that is sent to the unit, is displayed in the log and not the value entered on the Set odometer and Set engine hours modal.