Hardware Requirements and Software Dependencies
This firmware release supports the following and higher MCNs:
- CV90-JC339-1xx, -2xx, -3xx
- CA90-JE045-1xx, -2xx
- CV90-JE045-1xx, -2xx
- CA90-JC339-1xx, -2xx, -3xx
and is composed of the following software:
- PAPI 1.9.1
- VIOP 10.00
- WEC2013 OS (OS 61)
- Nuance 1.0
- CoPilot 10.7.2.1654
- Navigo 188.8.131.52
- Zetakey 1.0
- OTNav 5.6.42
- Driver Help 10.00
- DriveWyze 2.0.1
- 3G units (UAs 108000000 - 108499999) are compatible with the Microsoft Windows Embedded Compact operating system (WEC2013 OS) OS33 or higher.
- LTE units (UA 108500000 or higher) are compatible with the Microsoft Windows Embedded Compact operating system (WEC2013 OS) OS50 or higher.
Most upgrades are done over-the-air. The IVG firmware is available for download on the Customer Portal (see the Installation and Troubleshooting Guide).
The interface is now available in French and Spanish.
New Features and Enhancements
HOS Updates in Support of Canadian ELD requirements
The introduction of changes to the Hours of Service (HOS) application in preparation for compliance with the Canadian ELD mandate provides for functionality in compliance with the Canadian ELD Technical Standards.
Over the next several releases, Hours of Service will introduce additional Canadian ELD functionality that will culminate in the complete Canadian ELD application.
It is possible that drivers will have complete Canadian ELD functionality before Omnitracs receives third-party certification.
Please note that the Canadian ELD mandate effectively replaces paper logs and requires federally regulated motor carriers to equip their vehicles with compliant, third-party-certified ELDs on or before June 12, 2021.
Once the device is certified, the certification body will provide Omnitracs with a certification number. Omnitracs will embed this number in the ELD software in the appropriate data field.
Note: Canadian ELD Certification only applies to the IVG, not MCPs.
IVG Ruleset Changes for Canadian ELD
Canadian ELD rules require you to identify an Operating Zone change when crossing between Canada South, Canada North and the US. In order to improve our customer experience, we are also providing you with a PDF version of the features listed below. This job aid can be printed and handed to your drivers on the field.
Canadian Operating Zone Changes
In order to be compliant with Canadian ELD standards, drivers operating in Canada will no longer be able to backdate their end of trip automatically when transitioning from Driving to On duty.
If the vehicle is not in motion, and alert displays after 5 minutes. This notification requires the driver to acknowledge the duty status change to On Duty. If the driver fails to acknowledge this notification, the duty status will be automatically transitioned to On duty status after the 6 minute threshold. The current time of the transition will be the effective recorded time.
However, if the driver is driving in the US or Mexico, the backdate will continue to be registered at the time that the vehicle came to a stop even if the driver fails to confirm the duty status change.
Canadian Cycle Changes
In compliance with the Canadian ELD Technical Standards, drivers operating in Canada will be enabled for the Canadian Cycle Change.
In order to ensure a clear understanding of the Cycle Change for drivers operating in multiple zones, the button text in the Canadian Clocks Tab has been updated to: Canadian Cycle Change, as seen in the image below.
Off Duty Deferral Events
In compliance with the Canadian ELD Technical Standards, the Off Duty time deferred to the next day will be displayed without seconds in the Off Duty Deferral confirmation screen. As you can see in the image below, it displays HH:MM instead of HH:MM:SS .
Driver Swap Request
OHOS 5182, 5183, 5184,5185,5212,5213,5224
The Certify tab has been updated to allow drivers to swap driving events if there are co-drivers associated to the specific events.
After the driver selects a driving event, the Swap button displays for the driver to select. Please remember that if there is no co-driver associated to the driving event, the Swap button will remain hidden.
Note: Driving with an unidentified origin will not allow the event to be swapped, even if a co-driver has been added by the host.
The driver must select a start and end date for the screen to display the eligible driving events for Driving Swap.
Once the driver selects ok, a screen displays asking the driver to enter a Driving Swap Reason with a 60 character limit.
After the driver selects Save, the following prompt displays to inform that if the driver select Confirm to acknowledge the swap. This action will lock the all the impacted statuses from editing until the swap is accepted or rejected by the co-driver.
When both drivers have addressed it, all the accepted swaps will change to inactive driving events and update the associated On duty events as active.
Notes to consider:
- If the co-driver rejects any of the swaps, the rejected driving events will remain as active and the On Duty status will change to to rejected/inactive.
- If a swap request fails, the host will unlock the event for editing allowing the driver to request a new swap.
If a swap or edit is selected after a request has already been made, a prompt will display to let the driver know that their duty statuses are locked.
Swap request fail on Mobile
Please consider that if a swap request fails on the mobile, the driver will need to contact their administrator in order to make a new swap request.
Unassign an accept UVA on the Mobile
Updates have been made to the Unassigned Vehicle Activity to allow a driver to Unassign an accepted UVA on the Mobile. When a driver selects a driving event that was previously a Unassigned UVA in the Certify tab the Unassign button displays, allowing the driver to successfully unassign the event from the drivers logs.
The Driver must enter a Reason for Edit no longer than 60 characters and select Save.
Once the driver saves the edit reason a prompt displays indicating that all impacted duty statuses will be locked from further editing until they have been prompted from the host to review and confirm the edit changes.
Unassigned Vehicle Activity Storage
In order to stay compliant with the Canadian ELD requirements, the storage of UVA will be increased to display the current and past 14 days of unidentified driving events on the mobile, under the Unidentified Driver profile.
Carrier edits in Canadian ELD Operating Zone events
The HOS mobile allows drivers to accept or reject carrier edits of Canadian ELD operating zone events.
The edit prompt has been updated to remove the part mentioning that the carrier requested the change, the text will now say: Drive Time Swap - Requires approval by two drivers, as seen in the image below.
Drivers must tap Confirm to accept the the carrier edit.
Update on the Inspectors tab
In compliance with the Canadian ELD standards, the Inspector and Driver header in Day Log tab will be updated to have the Location column to include: latitude, longitud, geolocation and distance since last valid coordinates.
On the Driver View the sequence ID is added.
On the Inspector view the header is updated to display Accum. km/Odometer to include Vehicle ID ie: Vehicle ID/Accum. km/ Odometer.
In order to remain compliant with the Canadian ELD display requirements, driver logs in the host and mobile Inspectors tab will be updated to display the certification events on the date of the log being certified, not on the date the certification was performed.
Example: If a drivers log dated August 15th but was not certified by the driver until August 20th, the certification event should be displayed on the August 15th log event list indicating that it was certified on the 20th.
If a status is Edited it will now display:Edited: time in the Time/Origin column on the Inspector view.
New printer driver support for brother printer RJ4230BL is now supported for LTE and 3G units.
|Work Item Number||Description|
|OOTIS 25506||There were multiple reports from drivers receiving violations due to the fact that the mobile was note recording power up and down events correctly; causing the FMCSA to register the engine hours and other data as invalid. This issue has been resolved.|
The text for the denial prompt that is displayed to the driver when attempts to perform an Off Duty Deferral event, was incomplete when the driver's name and last name were too long. This issue has been resolved by switching from using the full name to the Login ID for all 4 pop-ups related to Off-Duty Deferral.
When the driver is set up for Canadian Ruleset in the mobile and has satisfied the required off duty time, a denying prompt displayed. This issue has been resolved.
On the Unidentified driver profile the Distances were not recorded properly for the odometer, this issue has been resolved.