Important: The IVG DA1110R is a complete release based on IVGDA1106R, which was previously broadcasted to Canadian customers. To get additional information about new functionalities on Canadian ELD with a complete description of updates and fixes, please click here to review the IVGDA1106R release notes in addition to the information shown in this release.
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 126.96.36.199
- Zetakey 1.0
- OTNav 5.6.42
- Driver Help 11.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.
In this release, Hours of Service will introduce additional Canadian ELD functionality that will culminate in the complete Canadian ELD application.
Drivers will have complete Canadian ELD functionality before Omnitracs receives third-party certification.
The Canadian ELD mandate effectively replaces paper logs and requires federally regulated motor carriers to equip their vehicles with compliant, third-part-certified ELDs. On March 2, 2021, the Canadian Minister of Transport released a statement on newly formed enforcement procedures around the Canadian Electronic Logging Device (ELD) Mandate, which is slated to go into effect on June 12, 2021. The mandated deadline remains as is. However, the government will begin a phased enforcement rollout after the deadline that focuses on education and awareness at first. Therefore, there will be no enforcement penalties at the start of the mandate.
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.
Update Regarding ELD Compliance
On June 29, 2021 Omnitracs will be submitting an update to the ELD certification documentation provided on the FMCSA ELD Website to indicate that IVG DA1110R is the minimum ELD-compliant version of the IVG.
The IVG DA1110R update includes corrections to ELD functionality that were necessary to comply with the U.S. ELD Mandate. Updating to this version of the IVG is required to maintain an ELD-compliant device. IVG versions previous to version IVG DA1110R are no longer considered ELD-compliant.
Please update your devices at your earliest convenience to ensure you are running IVG version IVG DA1110R.
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.
Change Impacting Drive Time in Canadian Operating Zone
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, an alert displays after 5 minutes. This notification requires the driver to acknowledge the duty status change to On-Duty, not Driving. If the driver fails to acknowledge this notification, the duty status will be automatically transitioned to On-Duty, not Driving status after one additional minute. The current time of the transition will be the effective recorded time. Drivers should be diligent in selecting a desired duty status when driving is complete. This will assist in preserving the amount of available Drive time during the work shift and day.
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 acknowledge the duty status change prompt.
Change Duty Status Screen Update
The Change Status screen has been updated with a new location field. If the vehicle's position is unavailable, the driver will be prompted to enter the location when changing the status manually, as seen in the image below.
Edit Duty Status
The Edit Status view has been updated with a Vehicle ID button available for statuses that were missing or had an editable Vehicle ID. If enabled, this option will take the driver to the Edit Reason View and allow them to enter it without changing anything else on the Duty Status.
Note: This button is only visible if the driver is able to enter the Vehicle ID on the HOS Reason View. Additionally, it will only be enabled if the driver hasn't made any changes on the screen; otherwise, validation of the changes is required, disabling the Vehicle ID button.
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
Team drivers can now request to transfer multiple driving events to an authenticated Co-driver at once. If team drivers forget to change to the active driver, they can use the edit feature on the Certify tab to request a Driving Swap to correct their logs. This feature allows team drivers to submit a request to their authenticated Co-driver to accept the driving on their respective log.
Please note that current duty status can't be edited; so the driver who intends to accept the driving onto their log must update their status in order to prevent the swap from impacting their current status.
On the Certify tab if the driver selects a qualified driving event, the Swap button will display for the driver to select. Please remember that if there is no co-driver associated to the driving event, the Swap button will not be available.
Note: Driving events with an unidentified origin will not allow the event to be swapped, even if a co-driver has been added by the host.
Drivers must enter the date and time window in which the co-driver's driving occurred on their log and select Search. All the driving events that qualify to be transferred will be displayed inside the search window for review.
The driver must review them carefully. If all the events indicated need to be transferred for accuracy they must proceed with the request by taping OK.
If some of the driving events should not be transferred, or there are events missing, tap Cancel and start again by adjusting your search window to ensure you only request the impacted events. Once the driver selects OK, a screen displays asking the driver to enter a Swap Reason with a 60-character limit.
After the driver selects Save, the following prompt displays to inform that the driver must 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 both drivers.
Once the swapped event has been successfully accepted by both drivers, the original driving record will be updated with an inactive event status and the time. It will be filled with an active On Duty not driving event. Likewise, the swapped drive time will appear as an active drive event in the co-driver's log.
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 rejected/inactive.
- If a swap request fails, the host will send a notification to the requesting driver.
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.
Changes related to swapping drive time are relevant for both U.S and Canadian ELDs. The HOS regulations for both countries have always restricted the swapping of erroneously recorded drive time to only an authenticated co-driver in a team driver operation.
The HOS regulations specifically prohibit the shorting, changing to a non-driving, reassignment of automatically recorded driving time, except in the cases of mistakenly accepted unassigned drive time or errors between authenticated team drivers. This new functionality simply restricts the reassignment of automatically recorded drive time to anyone other than an authenticated co-driver in a team driving situation.
Canadian Hours Of Service Alert Updates
In compliance with the Canadian ELD Technical Standards, drivers will be alerted when they are approaching a drive/duty-status HOS limitation. The alerts are based on the HOS limitations of the US or Canadian Operating Zone the driver is operating in. The warnings will display with a written and verbal alert indicating which US or Canadian rule is the minimum clock that is counting down on the alert message to the driver, even when driving is not occurring.
Current Canada South Clocks
- Daily Off Duty time: requires driver to take al least 10 hours of off duty time in a day.
- 13 hour driving which monitors the 13 hours maximum drive time allowed per day and 13 Hours Driving per shift.
- 14 hours On duty /14 hours in a day and 14 work window per shift.
- 16 hour work shift.
- 70Hr Cycle 1 and 120 Hr Cycle 2.
- Cycle 1: 24 Hours off duty required at 336 hours of ON duty or Cycle 2: 24 hours off duty required at 70 hours On duty.
Current Canada North Clocks
- 15 Hours driving which monitors per shift.
- 18 Hours - On duty.
- 20 hour work shift.
- 80Hr Cycle 1 and 120 Hr Cycle 2.
- Cycle 1: 24 Hours off duty required at 336 hours of ON duty or Cycle 2: 24 hours off duty required at 70 hours On duty.
Alerts will be repeated as necessary at one hour, 30 minutes, 15 minutes, before and after violation occurs.
Data Recording Compliance Monitoring
OHOS-5544, OHOS 5795
In compliance with the Canadian ELD Standards and update has been made to the ELD event record information to the required data elements for each event type. The ELD must record the missing required data elements and data diagnostics events for the driver if any required field is missing at the time of recording to trigger a diagnostic when an engine synch diagnostic or malfunction is identified.
Unassign erroneously accepted UVA on the Mobile
OHOS 5345, 5387
Updates have been made to the Unassigned Vehicle Activity to allow a driver to unassign erroneously accepted UVA on the Mobile. When a driver selects the erroneously accepted driving event in the Certify tab, the Unassign button appears, allowing the driver to successfully undo the acceptance that was done in error.
The Driver must enter a Reason for Edit using no more 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 Canadian ELD regulations when in a Canadian operating zone, if more than 30 minutes of unidentified driving show in a 24-hour period on the ELD, it will be recorded as an unidentified driving data diagnostic event.
The data diagnostic indicator will be turned on for all drivers authenticated into that ELD for the current day and the following 14 days.
Data Recording Compliance Monitoring
In compliance with the FMCSA and Canadian ELD Standards and update has been made to the ELD event record information to the required data elements for each event type. The defaults used by the ELD to record the missing required data elements and data diagnostics events for the driver if any required field was missing at the time of recording are now removed. This were used to ensure ERODS would not fail due to blanks when sending ERODS to FMCSA.
Edits screen updated to display requested changes for Drive time swap and Canadian ELD Operating zone
The HOS mobile allows drivers to accept or reject carrier edits of Canadian ELD operating zone events and Driving Swap events.
Drivers must review their original log and the proposed changes and tap Confirm or Reject.
Note: The Canadian HOS regulations restrict the swapping of erroneously recorded drive time to an authenticated co-driver in a team driver operation. In fact, the HOS regulations specifically prohibit the shorting of the ELD username associated with an ELD record to be edited or reassigned, except in the case of mistakenly accepted unassigned drive time or in the case of recording error between authenticated team drivers.
Update on the Inspectors tab
OHOS 5866, 6102, 6569
In order to meet Canadian ELD standards, the Inspector and Driver header in the Day Log tab are now updated to reflect the required information based on the driver operating zone, to ensure compliance while operating in USA or Canada. Whit this update, the Location column now includes: latitude, longitude, geolocation and distance since last valid coordinates.
On the Driver View the sequence ID is added.
On the Inspector view, a column has been updated to reflect Vehicle ID/ Accum. Km/ Odometer. The field will be completed for the appropriate data elements based on the corresponding Event/ Event Code recorded by the ELD.
The Day Log Inspector tab has been updated to include the user ID of the driver who edited the status in the Time/Origin column.
Note: The Day Log Inspectors tab will now show the Accum mileage that excludes any Personal Conveyance time driven since the last Power cycle and the Total Distance (Ending Odometer) in the special driving events such as Yard Move, Personal Conveyance, clear and start events when in the Canadian Operating Zone.
Updates on the Day Log screen tab
OHOS-5211, OHOS-1168, OHOS-6587
In order to meet Canadian ELD standards, the Day Log tab has been updated for it to properly display the accumulated mileage taking Personal Conveyance taken into account when a driver is in the Canadian operating zone. It will now show the Accum mileage & Odometer when both are present on a Canadian ELD event. Also, the Power up, Shut downs that occur during Personal Conveyance will be suppressed from the display.
Additionally, to remain compliant with the Canadian ELD display requirements, intermediate events will be recorded as Yard Move events, so that the FMCSA knows when the vehicle was in motion for 60 minutes or more.
Note: Unit of Measure will be displayed based on the Operating Zone, as seen in the images below, the display will now show Kilometers for all fields when operating in Canada South or Canada North and Miles when the driver is operating in the USA jurisdiction. Unidentified Driver, who has no ruleset will be set by default to physical location.
Special Driving Condition Event Messages
In order to remain compliant with the Canadian ELD display requirements, an update has been made to the Start and Clear special driving condition message for special driving events to include Accumulated distance and Total Distance.
OHOS 5465, 5466, 5467
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.
ERODS Compliance Requirements
In order to meet US ERODS requirements, the US ERODS CSV file will provide the Accumulated distance and it will contain all accumulated mileage since last power cycle including miles driven in Personal Conveyance.
Correct Vehicle ID on the ERODS
With this update drivers are now allowed to edit the vehicle ID for US and Canada. In the event the Truck ID is not displayed correctly, or you require license plate information, you can update that information on the log.
On the New Load page use the Change Truck ID button to correct the truck ID if necessary. Editing the Truck ID will update the host, and will display that ID for the vehicle moving forward. You will be prompted to confirm the change before it will be processed.
New printer driver support for brother printer RJ4230BL is now supported for LTE and 3G units.
|Work Item Number||Description|
In some instances the mobile device was not accurately recording power up and down events. 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.
An issue that was preventing drivers from using the full functionality of Canadian Cycle Change feature has been resolved.
Several eRODS files appeared as sent and successfully received by the FMCSA, but they were missing a required field for Elapse Engine Hours for a specific ELD Event. This issue has been resolved.
In some instances when the mobile was unable to retrieve the recorded Engine Hours as 0.0 in Personal Conveyance, Omnitracs used a default to ensure ERODS were successfully sent to FMCSA, these defaults are now removed.
In some instances when the mobile was unable to retrieve 9999 in Vehicle Distance after a Personal Conveyance event, Omnitracs used a default to ensure ERODS were successfully sent to FMCSA, these defaults are now removed.