Skip to main content
KB_Header_SiteLogo.svg
Omnitracs Knowledge Base

MAS50 Version CA1020R External Release Notes

Introduction

This document describes the new or modified features of software version CA1020R for the mobile application server (MAS).

Hardware Requirements

The software version CA1020R release supports MCN CV90-JB424-100 and higher.

Software Dependencies

The software version CA1020R is composed of the following software:

  • PAPI:  50.10.00
  • VIOP:  50.09.05 
  • ALK: 9.2.0.2230

Upgrade Procedures

Most upgrades are done over-the-air.

Compatibility

Compatibility with Windows CE Operating System (OS) LT0033 or higher.

Note: OS LT0038 or higher is required for the scanning feature.

OS LT0040 has BT support and is required for extended productivity.

New Features

Navigation – ALK CoPilot

  • Workflow 2.0 routes are now processed and displayed by ALK CoPilot.
  • ALK Copilot now launches into the Map View screen allowing it to properly process Workflow and dispatched routes.
  • Fleet Portal.

GSM Support for Canada

The MCP can now communicate on GSM.

Hours of Service (HOS) Canadian Rules

In continuing efforts to fortify the enforcement of Canadian rules, changes and enhancements were made to HOS. In general, enhancements for Canadian rules fall under these areas:

  • Enabling compliance with Canadian Rules
  • Providing useful information to plan better and be aware of upcoming violations or past violations regarding these rules.

Day Off Clock

  • Previously the Day-off clock was calculated exactly 336 hours from the time the driver returned to On-Duty after being off 24 hours.
  • We are now reinterpreting this rule to be based on duty days. The Day off clock is now calculated such that the driver can work 14 days between 24-hour off periods.  The clock now starts at midnight of the day which the driver returns to work after 24 hours off.

Daily Off Duty Rules

  • All daily off-duty rules for Canada Main are now enforced both on the mobile and web application (host)
  • 10 hours off per day (8 for Canadian North)
  • 2 hours that is not part of an 8 hour reset (not applicable to Canadian North)
  • Minimum 30 minutes off to count towards the above two bulleted item (not applicable to Canadian North)
  • HOS now has the ability to determine how long a driver must stay off duty to get both the extra two hours off and a shift reset. To optimize the driver’s log, HOS takes any off duty status time, longer than 8 hours, that cross midnight and allocates it to satisfy the daily off duty rule:
    • All daily off-duty rules for Canada Main are now enforced both on the mobile and web application (host)
    • All daiff-duty rules for Canada Main are now enforced both on the mobile and web application (host)
    • A shift reset is always given first
  • HOS now tracks driving warnings and violations and daily off-duty (working) warnings and violations separately. The first is only applicable while driving and the latter is applicable when working (driving or on-duty)

Off Duty Deferral Rules

  • For Drivers running under Canadian Main rules they need both 8 hours off duty (Off-Duty or Sleeper) to earn a reset and 2 additional hours off.  If the company allows it, drivers may have the option to defer the 2 hours off until the next day. This is referred to as an Off-Duty Deferral. 
  • The deferred time must be taken in conjunction with an 8-hour shift reset.
  • If the driver takes the 8 hours off, but not the deferred time, he still gets a shift reset, however, he is in violation of the deferral rules.
  • Drivers cannot take both an off duty deferral and a split sleeper berth.
  • To support compliance of the Off Duty Deferral rules, several changes have been made to both the web application (host) and the mobile unit.

Sleeper Pairing

  • Drivers can pair sleeper statuses instead of taking an 8-hour shift reset. When pairing, the time in the sleeper status is not counted toward the shift.
  • HOS now offers a setting that allows drivers to indicate when they will pair sleeper berth segments. The setting is a new check box added to both the mobile and web application (host). The check box can be toggled so that users can see how their clocks are calculated with and without pairing.
  • Potential violations for sleeper pairing will continue to be reported as today on both the mobile and web application (host).
  • After a shift reset, the HOS pessimistic clock shows, even if driver checks the Will SB checkbox because before first SB, there is nothing to pair and the Pessimistic/Optimistic clock is the same. After a shift reset or 2nd SB, we assume they will always pair SB until the next reset.

Critical Event Reporting (CER)

Hard brake events based on ABS activation are now supported.

TPM

High Temperature and Fast Leak features have been added.

Fixes/Enhancements

Critical Event Reporting (CER)

Excessive false positive Lane Departure Warning Disablement events were occurring from Mobileye devices. Code has been added to filter LDW Disablement events from Mobileye devices.

ALK CoPilot

  • Previously the 24-hour POI update interval was not reliable. New update interval value is set at 4 hours to increase POI update reliability.
  • New incoming Dispatch Address was not generated in the ALK application when navigation was in Follow Me mode (no destination address) even though the log file showed the dispatch was processed by OmniAPI. This has been fixed.
  • When dispatches were received and processed by CoPilot, but a route was not generated, the dispatch would not be persisted after a reboot/reset. This has been resolved.

WorkFlow

  • Previously Workflow Routes ACKed successfully but were not processed. Customers were resending routes multiple times to get the mobile to properly display them for the driver. This has been fixed. This has been resolved.
  • A new Report Temperature screen has been added.

Scanning

  • Custom scanning properties, including Document Types, Max Pages per Batch, etc., were not persistent across all mobile units. Instead, some units were reverting to the default settings. This has been fixed.
  • Previously when a page was scanned but canceled midway using the DocketPort468Q2, the page got stuck on the "Cancelling" window (was not rejected). The only way to clear this was to reboot. This has been fixed.

Training

Updates to the What's New Onboard Help for the MCP50 have been added to include information on HOS, CER Overspeed, FTV/FTW, CoPilot RouteSync, and Scanning.

Performance Monitoring (PM)

It appeared there was missing STRACS data and an overlapping driver 0 record. This was not the case, as there was no error and misinterpretation of missing miles.

Sprint PRL

The correct, latest PRL files from Sprint were not provided to be pushed to all the mobile units. Correct files were provided and this has been resolved.

State Miles

State Miles data was not reported (missing) for some mobile units due to CDEF 334 not being set so the TIU would use the correct default value. This has been fixed.

Vehicle Inspection Reporting (VIR)

  • When entered into freeform fields (e.g., Trailer ID or Describe Defects), the special characters & " < were not processed correctly and were preventing the trailer and vehicle inspections from posting to the Host site. The mobile would send a return message that showed up in the logs but not in ESS transaction. This has been fixed.
  • Previously only 200 characters could be entered in the Describe Defects field. Now 400 characters can be entered.

Vehicle Monitoring (VM)

Previously, ongoing faults were never indicated via email. If a fault continuously switched between being active and inactive every few minutes, the subsequent faults (after the first) were only getting reported to the end user every 40 minutes with the current configuration. This has been fixed.

Known Issues

Due to the different release schedules for our MCP50, MCP100, MCP110, and MCP200 mobile releases and the next HOS web application (host) release, the possibility exists that the HOS clock may differ between the web application and mobile for our Canadian customers. This was a known issue and will be resolved when the HOS web application (host) was released in June 2015.


© 2019 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.

  • Was this article helpful?