The MiX Rovi II software versions are available on the MiX Fleet Manager portal under MiX Rovi Configuration.

Updating the software requires a few steps.

The MiX Rovi II allows for over-the-air (OTA) firmware updates and updates via USB. This article explains how to update OTA.

You first need to ensure that the Rovi II is baselined to enable subsequent OTA updates on it. 

Step 1 - Firmware library:

In the firmware library search for the latest Rovi II software package and make it available.

• Click Manage.
• Under the Config Admin heading, click Libraries.
• Click on the Firmware library tab.
• Click on the actions arrow next to the Rovi II firmware.
• Click on Make available.

The firmware will now be available for selection under the Preferred application package section under the MiX Rovi II peripheral settings.

Step 2 - Set the preferred application version

• Click Manage.
• Under Config admin heading, click Libraries.
• Click on the Peripheral library tab on the left.
• Search for the MiX Rovi II device.
• Search for the MiX Rovi II device and either click on the name of the peripheral or click the downwards action arrow and select edit:

• Under Features and settings look for the ROVI application package heading.
• Click on the dropdown list next to the preferred application package version.
• Click Save.

Versions 20.4 and up are marked with a V or L; L is for legacy devices without OS 2.1.4, while V is only for devices with OS 2.1.4.

The selected version will now display in the rreferred version column on the MiX Rovi configuration page. Assets with an installed version older than the preferred version will have the OTA upload action available. (Devices with a version older than 18.17 cannot be upgraded OTA to versions newer than 20.4 and the status will display as ‘Not upgradeable.’ L and V compatibility will be enforced as well.)

Step 3 - Upload application in MiX Rovi Configuration

• Click Manage.
• Under the Config Admin heading, click on MiX Rovi Configuration.
• Click on the actions arrow next to the asset - when an update is available one or both of the following selections will become available:
  • Upload configuration - schedules the existing OTA config update to an individual MiX Rovi II device.
  • Upload application  - schedules an OTA application upload to an individual MiX Rovi II device. Software is transferred to the device while the OBC/vehicle is in-trip. Data is buffered and should resume if the connection is interrupted or the trip is ended and subsequently resumes.
• Click on Upload configuration and/or Upload Application.

These columns are shown on the page:

• • Application package version - this is the currently installed version of software on the MiX Rovi II device. When the cell is highlighted in red it signifies the preferred firmware version has changed and has not been applied.
  • Preferred version - is the version of firmware selected in the MiX Rovi II Peripheral Library.
  • Application package status - is the status of the OTA software update.
  • Rovi config group - is the config group the MiX Rovi II device is assigned to. When the cell is highlighted in red it signifies the config has changed and has not been applied.
  • Rovi config status - is the status of the scheduled OTA config.
  • Last application update - is the date and time the last application update was applied.

 The Application status for the asset will update to Scheduled. Once connectivity is established, the OTA package will be sent by Large File Transfer. The progress of the LFT can be viewed in the File Transfers feature in Scheduler.

Scheduler

• Click Manage.
• Under the Scheduler heading, click on File transfers.
• Here you can view the progress of the firmware upload.
• The page is sorted by the schedule run date (Date scheduled) in descending order by default but you can sort the list by clicking any of the column headers.
• You can filter the files by the transfer status by clicking on one of the filters on the left:

• • Cancelled
  • Cancel pending
  • Completed
  • Failed
  • In progress
  • Notified
  • Paused
  • Scheduled

After the LFT is complete, the uploaded package will be detected by the Rovi when the ignition is turned off; the Rovi will then build the new version from the OTA files. The installation of the new version will finalize when all drivers have logged off and the ignition is turned off again. After rebooting, the update will be complete and the new version info will be sent to the MiX Rovi configuration page. Assets with an installed version equal to or higher than the preferred version will have application status "Complete" and no longer have the upload application action available. If the preferred version is changed again to a newer version, the application status will reset to "Update available" and the upload action will be re-enabled.

The following table shows the statuses throughout the update process.

If something went wrong during the update, the Application status will display an error code: Checksum, Build, Install or Package. A checksum error indicates that the necessary files for the update are missing from the Rovi, meaning the device has not been baselined. The other three error codes are for internal use/diagnostics.

Application Package Bulk Uploads

You can upload new software to the Rovi II from the Rovi Config Groups feature within Config Admin. This will enable users to schedule OTA updates on a group level.

If a Rovi config group contains at least one asset with the “upload application” action enabled, the group “upload application” action will be available for the group. Selecting the group upload action will schedule a transfer for all assets in the Rovi config group.

• Click on Manage.
• Under the Config Admin heading, click on MiX Rovi Configuration.
• Click on the actions arrow next to the config group.
• Click Upload application.
• An application transfer will now be scheduled for all assets in the Rovi config group.