Hardware Requirements, Software Dependencies
This release supports MCN CV90-JB424-100 and higher and is composed of the following software:
- PAPI: 50.10.00
- VIOP: 50.13.00
- CoPilot® Truck™ (ALK): 9.64.787
- Omnitracs Weigh Station Bypass provided by Drivewyze™ PreClear: 2.0.2
- Mobile Data Capture: 1.0.216
Most upgrades are done over-the-air. Both the firmware and the operating system are available for download on the Omnitracs Customer Portal (on the Support page, click Firmware/OS); refer to the Installation and Troubleshooting Guide for upgrade procedures.
|Note: If after over-the-air upgrade your drivers notice that vehicle inspection reports are lost, have them record their reports on paper until the unit is upgraded.|
Compatible with Windows CE Operating System (OS) LT0033 or higher.
|Note: Omnitracs suggests OS LT0038 or higher for best driver experience; this operating system is required to use the In-Cab Scanning, Mobile Data Capture, and Workflow 2.0 features.|
New Features and Enhancements
- Drivers can now use Yard Move while they are in Canada.
- Drivers are now allowed to accept an Unassigned Driving Event as Personal Conveyance or Yard Move if they have been enabled to use them in the company settings.
- When drivers transfer eRODS files, they now receive a message letting them know their records will be sent to the FMCSA.
- A new feature allows the carrier to enable the 16-hour Exception from the host at a driver level. If either the fleet 16-hour setting or the driver 16-hour setting denies access to the driver, the 16-hour option is not displayed on the Exceptions screen.
- The MCP50 now captures additional data to send to the new Unassigned Driving Report on the HOS host.
Improvements to Malfunction Alerts and Reporting
- Several malfunction alerts have been improved:
- Position Malfunction alerts now include instructions for the driver to add the location for the duty status when required.
- Data Recording Malfunction alerts now include instructions for the driver to review and correct logs if necessary, and if the malfunction is hindering accurate recording, to use paper logs.
- Engine Sync Malfunction alerts now include instructions for the driver to review and correct logs if necessary, and if the malfunction is hindering accurate recording, to use paper logs.
- Timing Malfunction alerts now include instructions for the driver to use paper logs until the malfunction is corrected.
- Power Malfunction alerts now include instructions for the driver to review and correct logs if necessary, and if the malfunction is hindering accurate recording, to use paper logs.
- To improve malfunction reporting, the Diagnostics and Malfunctions Report now includes the specific trigger for the malfunction event.
- To make the Diagnostics and Malfunctions report more useful and easier to read, the report now has one line for each malfunction and diagnostic event that occurred, with each line indicating when the malfunction cleared and all the drivers who were affected by it.
- The instruction to go to paper logs has been removed for some sensor failures.
- A more intuitive alert for the Data diagnostic now includes what driver action is required.
- The instruction to go to paper logs has been removed for some sensor failures.
- Minor changes have been made to give the application a more unified look across platforms.
- U.S. and Canadian city lists have been updated to include all minor civil division (MCD) types.
Fixes and Software Corrections
|Work Item Number||Description|
|OMCPL-22447||The Info screen now properly displays long company addresses.|
|OMCPL-22443||The Load screen has been updated so that the driver selection drop-down menu does not cover up the view of load information.|
|OMCPL-22448||Long co-driver names are now displayed properly on the Info screen.|
|OMCPL-22431||Updates have been made to ensure that the driver details screen identifies the city or province for all locations.|
|OMCPL-22460||A performance enhancement has been made upon start-up to reduce the number of Power Malfunctions reported.|
|OMCPL-22461||The Position Malfunction timer has been updated to pause when no vehicle motion is detected.|
|OMCPL-22459||The Malfunction timer has been updated to consistently reset at midnight.|
|OMCPL-22440||Co-drivers no longer need to re-enter their password when the vehicle stops the current driving event.|
|OMCPL-22450||A performance enhancement has been made to reduce screen lag time when a driver is automatically transitioned to On Duty status.|
|OMCPL-22414||The co-driver no longer automatically transitions to the Status screen when a driving event begins.|
|OMCPL-22469||The Position Malfunction timer has been updated so it does not continue to count time when the vehicle is not in motion.|
|OMCPL-22376||On the Certify screen, the counter that indicates the number of days certified now updates properly.|
|OMCPL-22391||The system now waits five minutes after an edit is made or until the Send Logs button is selected before it sends edits to the mobile. This allows carriers time to complete the editing process.|
|OMCPL-22377||For duty statuses that span more than one day, each day must be certified individually.|
|OMCPL-22418||On rare occasions, the internal clock used bad date/time values provided from GPS. This issue has been resolved.|
|OMCPL-22421||In rare cases some diagnostic events would not clear without a reset. This issue has been resolved.|
|OMCPL-22429||Old AOBRD functionality that identified the driver as the co-driver of a UVA event if the driving occurred prior to login authentication has been removed.|
|OMCPL-22416||Based on FMCSA guidance, changes were implemented to ensure that some malfunctions are not over-reported.|
|OMCPL-22410||The Certify Logs screen, like the Status tab, now includes a message to indicate if logs have not yet arrived.|
|OMCPL-22425||The process of calculating passenger rule violations has been improved to prevent false positives from being reported.|
|OMCPL-22300||Corrections have been made on the Certify tab to ensure that the banner identifies the work as Certified after logs have been edited.|
|OMCPL-22259||Inspector Mode has been updated to include the ELD Sequence ID for carrier edits.|
|OMCPL-22379||The DayLog Driver and Inspection Mode screens now allow for more than 50 characters to be displayed in the name field.|
|OMCPL-22374||Drivers now receive an alert when unassigned driving cannot be offered to them due to existing driving events.|
|OMCPL-22347||On the Edit Log Status screen, the Exceptions drop-down list now includes "Oil Well Wait Exception" as long as that exception is enabled on the host.|
|OMCPL-22331||The layout of the header has been improved to prevent the scroll bar from covering the co-driver's name.|
|OMCPL-22383||The layout of the Info screen has been improved to prevent the scroll bar from covering the co-driver's name.|
|OMCPL-22378||Intermediate events are no longer duplicated on the mobile display when forward logs are delivered.|
|OMCPL-17773||The beginning of the Trip trigger has been updated to ensure it does not back-date the On Duty period if the driver moves the vehicle at a speed less than five miles per hour immediately before transitioning to On Duty.|
|OMCPL-22399||The mobile was having rendering problems during the transition from the Navigation screen to the Home screen after DriveWyze dismissed the "near bypass station" notification. This issue has been resolved.|
|OMCPL-22472||Updates have been made to ensure the distance since last valid coordinate value is not reset after a reboot.|
|OMCPL-22531||Changes have been made to GPS rollover to help prevent a time jump.|
|OMCPL-22546||Updates have been made to ensure malfunctions are displayed to the active driver when a team is logged into the mobile.|
|OMCPL-22475||On the Hours of Service screen, the driver name drop-down list has been fixed to display drivers who are inactive.|
© 2020 Omnitracs, LLC. All rights reserved.
Omnitracs is a trademark of Omnitracs, LLC. All other trademarks are the property of their respective owners.
Omnitracs endeavors to ensure that the information in this document is correct and fairly stated, but Omnitracs is not liable for any errors or omissions. Published information may not be up to date, and it is important to confirm current status with Omnitracs. Specifications subject to change without notice.
This technical data may be subject to U.S. and international export, re-export or transfer (export) laws. Diversion contrary to U.S. and international law is strictly prohibited.