Skip to main content
KB_Header_SiteLogo.svg
Omnitracs Knowledge Base

MCP110/MCP200 AA1683R Release Notes

Hardware Requirements, Software Dependencies

This document covers a firmware release that supports MCN CA90-J9937-10 and higher and is composed of the following software:

  • PAPI 200.12.50
  • VIOP 200.16.02

Upgrade Procedures

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 following guides for upgrade procedures.

Compatibility

  • MCP110: Windows XPE operating system builds OS129 and OS130
  • MCP200: Windows XPE operating system builds OS29 and OS30

Features and Enhancements

In addition to ELD enhancements, the following features/enhancements are available with this firmware release.

User Interface

The interface is now translated into French.

Weigh Station Bypass

Upgraded to 2.0.1A.

Navigation Applications

  • Omnitracs Navigation 4.4.34
  • Navigo 5.6

ELD Changes

The features and enhancements listed here are related to the ELD mandate and are viewable when using ELDs, units that have the ELD firmware and have toggled ELD on for those units. Additionally, there may be:

  • AOBRDs – The unit doesn’t have the ELD firmware and application functions as it did before the upgrade.
  • AOBRD Mode – The unit has the ELD firmware, but hasn’t enabled ELD for the unit; the unit has some ELD features enabled.
  • ELD – The unit was upgraded to ELD-compatible firmware and full ELD features are toggled on.

Note: Be aware that the driver may not edit previously certified logs.

In all instances, when referring to an “authenticated” driver, that is a driver who has successfully logged in to the AOBRD/ELD. A driver can tell if they’re authenticated if their user ID resolves to their full name.

Feature/Function

AOBRD

ELD-capable, running as AOBRD

ELD

Unassigned Driving reconciled

Host only

Mobile; if rejected then returned to the host

Mobile; if rejected then returned to the host

Mobile Edits can be disabled

Yes

Yes

No

Driver must approve/decline edits from carrier

No

No

Yes

Auto on-duty/off-duty at login/logout

Yes

No

No

Events timed to seconds

No

Yes

Yes

Capture VIN from ECM

No

Yes

Yes

Capture Engine Hours from ECM

No

Yes

Yes

Complete edit audit history visible on host

No (original and last only)

No (viewable in ELD Driver Log Report if running a mixture of ELD units +/- AOBRD mode units or AOBRDs)

No (viewable in ELD Driver Log Report)

Minimum Duty Status Duration (1-5 min configurable at host)

Yes

Yes

No

Configurable BOT threshold

Yes

Yes

No

Exempt Driver

No

Yes

Yes

Personal Conveyance Limits and implementation like Off-Duty Driving

Yes

Yes

No

Yard Move

No

Yes

Yes

Enforced Certification of Logs

No

Yes

Yes

Enforced entry of Load/Trailer Info

No

Yes

Yes

ELD Diagnostics and Malfunctions plus Sensor Failures

No (current sensor failures only)

No (current sensor failures only)

Yes

Send ERODS file from mobile

No

No

Yes

Driver Security (Password prompt for co-driver to access HOS application)

No

Yes

Yes

Comparison – How ELD Firmware Affects AOBRDs

Please note that how Hours of Service and log in/log out functions on the MCP is directly affected by the firmware version. Some features that are implemented for the ELD mandate are exposed to the driver even if ELD is not turned on for the unit.

  • Login/Log out (duty status) – Upon login or log out, drivers are prompted to select a duty status. See Driver Login Changes for details.
  • Certification (not approve) – Driver now goes to the Certify tab (not Approve) to review and certify their logs in 24 hour increments, not multiple days at a time. Additionally, drivers must approve their logs daily.
  • Loads – Drivers must provide load information for each load they carry and are prompted to provide it if they have not. See Load Information Form and Manner Changes for details.
  • Driver Log Edits – Drivers are prompted to approve driver log edits performed by the carrier. Additionally, how log edits are handled differs between AOBRDs and ELDs. See Carrier-Initiated Driver Log Edits for details.
  • Security password prompt – If there are two drivers logged in to the MCP, the co-driver is required to provide their password to access their logs.
  • BOT – See for Beginning of Trip/End of Trip for details.
  • Durations to seconds – All driver hours are now recorded to the second, not to the minute.
  • Drive time – All drive time is now collected and must be allocated to a driver. If the drive time was generated by a non-ELD driver, like a mechanic, you should create that driver in Hours of Service and indicate that they are ELD-exempt. See ELD Exempt Drivers for details.
  • Driver edits – AOBRDs are not required to allow drivers to edit their logs although they are permitted per regulation guidance. ELDs, however, are required to provide that function. There is no longer an option to toggle that permission on/off for ELDs in the Hours of Service host application, and if a driver is not granted permission to edit logs on an AOBRD, when the driver logs into an ELD, it will ignore the host application’s setting and permit the driver to edit his logs.
  • Editing logs – Neither drivers nor back office personnel can edit drive time.

Sending ERODS

With Hours of Service, an ERODS file can be generated by and transferred from both the in-cab device and the host application to Omnitracs’ internal EDS (ERODS Delivery Service) server.

  • Mobile – Upon receiving the ERODS file from the mobile device, the EDS displays a notification on the mobile via the Alert Manager.
  • Host – In the Admin section, there are two new tabs, ERODS (Request) and ERODS (Status).

ERODS file transfer statuses are: Success, Failure, or Pending.

Host Edits of Driver Logs

On an AOBRD unit, if a driver's previous duty status (not part of their current duty cycle) is edited through the host application, the edited duty status dates are sent to the driver and presented for re-certification.

Note: Be aware that days in the driver’s current duty cycle that were not edited are not uncertified (reverted to uncertified).

Tab Changes

The Carriers tab should display the carrier information as entered in the Hours of Service back office application. The carriers tab and carriers set up in Hours of Service does not identify separate companies the driver may haul for, just divisions of a single company like bulk versus refrigerated or hazmat versus DTTS (defense transportation tracking system). If your company has multiple divisions that are their own carrier entities, you would enter those in the Hours of Service back office application and the driver would select the carrier here.

ELD Exempt Drivers

You can identify drivers as ELD exempt, meaning that they’re not subject to the ELD requirements. This difference allows you to create ELD exempt drivers like mechanics who can perform yard moves or longer road tests, short haul drivers using an ELD-equipped vehicle, or test drive vehicles.

When an ELD exempt driver logs in or out of the MCP, the driver is alerted of their exempt status. While in exempt mode, the MCP records automatic transitions to and from Driving Duty Status.

Exempt driver mode is available when running ELD firmware in AOBRD mode and full ELD-capable devices. If the driver’s exempt status changes while driver is logged, the mobile will notify them of this change.

While in exempt driver mode, the ELD:

  • Does not prompt the driver to accept or reject carrier edits or unidentified driving time
  • Does not prompt the driver for missing load info or to certify logs
  • Does not show or enforce rest break rules
  • Does not show the ERODS transfer button
  • Displays collected exempt driver data in the header for all days in that duty cycle

While in exempt mode, the mobile follows AOBRD personal conveyance and driver edit rules, if configured by the carrier for the driver.

Unassigned Driving Time (Unassigned Vehicle Activity - UVA)

If any unassigned driving time (drive time without an associated driver ID) is generated on an ELD-equipped vehicle, that UVA stays with the MCP and must be assigned to one of the following:

  • A driver
  • An ELD-exempt driver (like a mechanic)
  • “No Driver” or a category such as Fuel Dock, OEM Maintenance, etc.

When a non-exempt driver logs in to an MCP that has UVA, the driver is prompted to review and confirm that this is their drive time. If a driver:

  • Confirms that the UVA is theirs, that time is transferred to their logs on the MCP and notification is sent to the Hours of Service host application.
  • Rejects the UVA, they must enter a comment about why they are rejecting the time and a notification is sent to the host.

Note: Accumulated UVA is not presented to a non-exempt driver until that driver’s logs have been pulled down from the host application.

On the host application, UVA continues to show on the Vehicle Details page as it accumulates on the MCP (same as it does today). However, the host user cannot take any action against that UVA until one of the following occurs:

  • The UVA is Rejected by a non-exempt driver on that MCP
  • Eight days pass without a non-exempt driver logging into that MCP

Beginning of Trip/End of Trip

For AOBRDs or units running in AOBRD mode, the beginning of trip (BOT) and end of trip (EOT) thresholds are still set in the Hours of Service back office application on the Administration > HOS Setup tab.

For ELDs, BOT is triggered when the vehicle’s speed is equal to or greater than 5 MPH (8 KPH) at any time. There is no distance threshold (how far a vehicle must travel while at speed).

For ELDs and Enhanced AOBRD units, EOT is triggered after five minutes of no movement and the driver is prompted to indicate that driving has ended. The driver sees a pop-up asking, “Vehicle stopped for five minutes, switch to On Duty?” If the driver responds:

  • YES – The driver is put into ON DUTY and the activity is recorded as the time when the wheels stopped moving.
  • NO – The driver remains in DRIVE.
  • No response – After one additional minute, the driver is transitioned to ON DUTY, and the activity is reported as the time when the wheels stopped moving (6 minutes earlier).

No Minimum Duty Status

Minimum duty status for AOBRDs or units running in AOBRD mode is set on the Administration > HOS Setup page in the Hours of Service back office application. For ELDs, there is no minimum duty status and all time is recorded.

Yard Move and Personal Conveyance

Yard move is a driver-initiated event that identifies when an ELD-equipped vehicle is moved in a private yard, without public access. Settings for Yard Move and Personal Conveyance are defined on the Administration > HOS Settings page in the Hours of Service back office application. After the fleet settings are enabled, individual drivers may be enabled to use Yard Move and Personal Conveyance via Driver Administration.

Personal conveyance replaces off duty drive time and can be set to be unlimited, meaning the driver can operate for any length of time in personal conveyance, or limited, meaning you identify how many minutes a driver may be in personal conveyance before receiving an alert on the ELD.

For ELDs with drivers in personal conveyance, Omnitracs no longer reads the truck’s ECM and no odometer readings are recorded during this driver-initiated event. While in personal conveyance, position accuracy is reduced to 10 miles (16 kilometers). The finer resolution GPS and engine data are captured for duty statuses that precede and follow personal conveyance.

The ELD does not automatically transition the driver to Drive when the customer-defined personal conveyance threshold is met (number of minutes). Instead, the driver is alerted that the Personal Conveyance threshold established by the customer was exceeded, but the driver’s duty status is NOT changed to Drive. The driver must manually terminate the personal conveyance duty status.

Note: Because personal conveyance is triggered when selected by the driver, not when the wheels are in motion, you may see a decrease in the number of personal conveyance events and an increase in the total time in personal conveyance in your logs.

When drive time accumulates as personal conveyance or yard move, it’s indicated on the Graph tab as a different color, not on a separate line. Yard move accumulates on the on-duty line and personal conveyance accumulates on the off-duty line.

Load Information Form and Manner Changes

Load information must be entered for each day or the driver incurs a form and manner violation. If the load/trailer information is missing, drivers are now prompted to enter it for any days in the driver’s current duty cycle upon logout.

If load information isn’t entered, the driver is prompted to enter is while logging out.

Duty Status Splits

Internal duty status splits at midnight and at state crossings are no longer recorded on an ELD or AOBRD-mode units.

Enhanced Sensor Failure Logic

When an error occurs or is cleared, the driver is notified on the MCP and the Hours of Service host application is updated with that information. These errors are viewable in the Hours of Service back office application and on the Sensor Failure report.

In addition to the legacy speedometer and odometer Omnitracs Sensor Failures, the ELD mandate introduces additional diagnostic and malfunction reporting requirements. Both ELDs and units running in AOBRD-mode incorporate all of these events.  The existing Sensor Failure report is being replaced with a Diagnostics and Malfunctions Report that shows both the existing AOBRD sensor Failures and the new ELD diagnostics and malfunctions on a single report.

Odometer Sensor Failure

The odometer sensor validates both that the odometer is working correctly and that the physical connection among the ELD, odometer, and ECM is active. The ELD detects the sensor status by querying the ECM when one of three states is detected:

  • Immediately after vehicle movement
  • Immediately after stopped (0 MPH/KPH for 3+ consecutive seconds)
  • When a driving status is split (when the driver accepts a split or creates an edit to split a status)

An error is recorded when any of the following verification criteria is met:

  • When the odometer reading is less than 0
  • When the odometer reading is over 10 million
  • When the odometer decreases by 1.0 mi (1.6 km) between readings

When the ELD records an error, it uses alert manager to send the driver an odometer sensor failure event and the error is recorded in the Day Log, Driver View, but not in the Day Log, Inspector Mode or the ERODS file transmitted to enforcement.

The error state is cleared when, during the next triggering event, the ELD determines that the trigger is no longer active. When the ELD clears the error, it uses alert manager to send the driver an odometer sensor failure clear event and the “error clear” is recorded in the Day Log, Driver View, but not in the Day Log, Inspector Mode or the ERODS file transmitted to enforcement

Note: The odometer sensor failure query/recording is suspended during when the driver is in the personal conveyance duty status.

In a later release, there will be a report that can be run from the HOS host app to aggregate these errors.

Road Speed Sensor Failure

The road speed sensor validates the ECM’s speedometer data by comparing it to GPS data. The road speed sensor data is validated every 60 seconds the ELD records an error when any of the following verification criteria is met:

  • The ECM reports that road speed is 0 and GPS speed exceeds 10 MPH (16 KPH) for 5 or more minutes
  • The ECM reports that road speed is static and the GPS speed exceeds 10 MPH (16 KPH) for 5 or more minutes
  • The road speed from the ECM is fixed at 1 MPH (1.6 KPH) or greater and the GPS speed reads 0 for 5 or more minutes

When the ELD records an error, it uses alert manager to send the driver a road speed sensor failure event and the error is recorded in the Day Log, Driver View, but not in the Day Log, Inspector Mode or the ERODS file transmitted to enforcement.

The road speed sensor error is cleared when the verification criteria is no longer met. When the ELD clears the error, it uses alert manager to send the driver an odometer sensor failure clear event and the “error clear” is recorded in the Day Log, Driver View, but not in the Day Log, Inspector Mode or the ERODS file transmitted to enforcement

Note: The road speed sensor failure query/recording is suspended during when the driver is in the personal conveyance duty status.

Power Compliance Monitoring

The ELD mandate requires that the ELD monitors ECM data to ensure that the unit becomes “fully functional” within one minute of CMV engine receiving power.

If the ELD is not fully functional within one minute of engine power up, the ELD triggers a power data diagnostics event, logs it in both the ERODS and driver log detail for the currently authenticated driver, and provides a continuous visual indicator of the diagnostic to the driver.

If the aggregate time that the ELD spends with an active power data diagnostics exceeds 30 minutes within a continuous 24-hour logging period, across all drivers for that vehicle, including unidentified drivers, the ELD triggers a power compliance malfunction event, logs it in both the ERODS and driver log detail for the currently authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when a diagnostic or malfunction event is triggered, the diagnostic or malfunction event is recorded under the unidentified driver profile.

When the 24-hour logging day ends, the ELD clears the diagnostic or malfunction, updates the ERODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

Engine Synchronization Compliance Monitoring

The ELD mandate requires that the ELD mobile unit monitor the data it receives from the ECM and other onboard sensors to ensure continued operation of the ELD and to record/monitor Engine hours, odometer, and speed. The following data requirements are monitored and maintained to ensure that the ELD:

  • Remains powered on when the commercial motor vehicle (CMV) engine is powered on
  • Accurately detects the vehicle motion status
  • Accurately logs vehicle miles over the course of an ignition power cycle, and the total operating time of the vehicle
  • Accurately logs elapsed engine hours over the course of an ignition power cycle, and the total operating time of the vehicle
  • Accurately detects the CMV’s vehicle identification number

If the ELD cannot acquire updated values for the previous parameters within five seconds of the need, the ELD triggers an engine synchronization data diagnostics event, logs it in the ERODS and driver log detail for the currently authenticated driver, and provides a continuous visual indicator of the diagnostic to the driver.

If the aggregate time that the ELD is not connected to any of the required data sources exceeds 30 minutes within a continuous 24-hour logging period, across all drivers for that vehicle, including unidentified drivers, the ELD triggers an engine synchronization compliance malfunction event, logs it in the ERODS and driver log detail for the currently authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when a diagnostic or malfunction event is triggered, the diagnostic or malfunction event will be recorded under the unidentified driver profile.

When the 24-hour logging day ends, the ELD clears the diagnostic or malfunction, updates the ERODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

Timing Compliance Monitoring

The ELD mandate requires that the ELD obtain and record date and time information automatically without external input or interference from a motor carrier, driver, or any other person. This test is currently performed when the MCP boots and drift typically never exceeds two seconds.

If the ELD detects a deviation from Coordinated Universal Time (UTC) of more than 10 minutes, it records a timing compliance malfunction, logs it in the ERODS and driver log detail for the current authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when the malfunction event is triggered, the malfunction event is recorded under the unidentified driver profile.

When the deviation from UTC is less than 10 minutes, the ELD clears the malfunction, updates the ERODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

Positioning Compliance Monitoring

The ELD mandate requires that the ELD determine the CMV’s GPS position at least once every 5 miles (8 km) of driving. The following data requirements are monitored to ensure that the ELD:

  • Acquires an accurate GPS position at least every 5 miles (8 km) of driving
  • Accurately records the position information in standard latitude/longitude coordinates, to a hundredths of a degree precision
  • Verifies that the position information is recorded with a maximum of 0.5 miles (0.8 km) deviation from position of the CMV
  • Reports the position information to within 1 mile (1.6 km) of the position of the CMV
  • Reduces reporting precision to tenths of a degree when in personal conveyance mode
  • Includes distance traveled since last location query for any ELD events that require location information
  • >Verifies that the position information is recorded with no less than 10 miles deviation from position when in personal conveyance

If the ELD is unable to acquire a valid position measurement while the vehicle is in motion for 60 minutes or more within a continuous 24-hour logging period, the ELD sets a positioning compliance malfunction event, logs it in the ERODS and driver log detail for the current authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when the malfunction event is triggered, the malfunction event is recorded under the unidentified driver profile.

When the authenticated driver’s 24-hour logging day ends, the ELD clears the malfunction, updates the ERODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

If a duty status change ELD event requiring position information occurs, and the ELD is unable to collect such data, and the ELD has not set a positioning compliance malfunction, the ELD prompts the driver to manually enter position information via alert manager. The driver is required to enter the missing data as an edit.

If the driver does not enter position information when prompted, the ELD sets a missing required data element diagnostic event, logs it in the ERODS and driver log detail for the current authenticated driver, and provide a continuous visual indicator of the malfunction to the driver. The ELD will remove the missing required data element diagnostic visual indicator when the authenticated drivers logs out.

Data Recording Compliance Monitoring

The ELD mandate requires that the ELD monitor its storage capacity, both integrity of the stored information and to verify that there is sufficient data storage space, and record the appropriate malfunctions if any of those capabilities stop functioning properly.

If the ELD is unable to record or retain required events or retrieve logs that are not available via the host component, the ELD sets a data recording compliance malfunction, updates the ERODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

The ELD does not record power data diagnostic events while a data recording compliance malfunction is active.

If there is no authenticated driver logged in when the malfunction event is triggered, the malfunction event is recorded under the unidentified driver profile.

When the ELD resumes recording or retaining required events or retrieving logs, the ELD clears the malfunction, updates the ERODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

If any required fields are missing from an event record, the ELD sets missing required data elements data diagnostic, log it in the ERODS and driver log detail for the current authenticated driver, and provides a continuous visual indicator of the malfunction to the driver.

If there is no authenticated driver logged in when the diagnostic event is triggered, the diagnostic event is recorded under the unidentified driver profile.

When required fields are no longer missing from the specific event records, the ELD clears the malfunction, updates the ERODS and driver log detail for the currently authenticated driver to indicate that the event is cleared, and clears the visual indicator.

GPS Sensor Failure – Removed

Because new, ELD required sensor validation tests provide more information than the old GPS sensor failure, the MCP no longer checks for GPS sensor errors using the standard GPS Sensor Failure.

Diagnostics and Malfunctions Report

When there’s a malfunction on the MCP, that error and the error correction are displayed to the driver in the Alert Manager and are recorded at the host. The new Diagnostics and Malfunctions report shows any errors and error corrections.

Driver Log Edits

When a unit is running ELD, all drivers, regardless of host settings, are permitted to edit logs on the MCP. Please keep in mind that drivers cannot shorten drive time or change personal conveyance or yard move to a non-driving activity. For AOBRD-mode driver edit permissions are controlled by host settings.

Driver Login Changes

There must always be an active driver. When a single driver logs in, that driver is by default the active driver. When a co-driver logs in, that driver can be identified as inactive or the active driver.

To ensure driver security, the co-driver is prompted to reenter a password to view or edit logs. The active driver can access logs without providing a password.

Time Resolution Format – ELD and AOBRD-mode

Times now display with a resolution to seconds. For vehicles with ELD software, the time is accurate to the second and displays the true values. For vehicle with AOBRD software, the time is accurate to the minute and displays 00 for the seconds. With ELD software, violations are reported when the driver is in violation for one second. For AOBRD software, violations are still reported when the driver is in violation for one minute.

For information on how web services were affected, see Web Services.

The example below shows the new time resolution format for duty statuses reported from ELD software.

Carrier-Initiated Driver Log Edits

When a driver’s logs are edited by the carrier (back office personnel at your company), ELDs handle changes differently than AOBRDs and AOBRD Mode units. AOBRDs and AOBRD Mode units function the same way: host application edits are accepted immediately upon receipt by the mobile unit.

Edits made to driver logs through the Hours of Service host application for ELD software are not automatically accepted, but remain in a Pending state until reviewed and accepted by the driver through the in-cab hardware. The edited record is pending within the Hours of Service host application until the driver accepts or rejects the proposed changes. Additionally, the driver must review and accept or reject those changes upon login to the Hours of Service mobile application.

Note: Pending duty status changes cannot be edited after they are sent to the driver.

The look and function of carrier-initiated edits to logs for a driver using AOBRD software are unchanged. Edits to logs for a driver using ELD software are not automatically accepted, but remain in a Pending state until reviewed and accepted by the driver through the in-cab software. The edited record for the driver with ELD software displays as italic and is flagged as Pending within the Hours of Service host application until the driver accepts or rejects the proposed changes.

Note: Edits made to a driver’s logs while the driver is not logged into a vehicle remain Pending until the driver logs into a vehicle. If the driver logs into a vehicle using an AOBRD, the Pending edits immediately become active.

In summary:

  • If the software in the cab is an AOBRD or AOBRD Mode, carrier-initiated log updates are still automatically accepted and are never shown as Pending within the Hours of Service host application.
  • If the software is ELD-compliant, the driver is prompted upon login to the in-cab software to accept reject those changes. Until they’re acknowledged by the driver, the edited log record shows as Pending within the Hours of Service host application.

The original, unedited logs display on reports until the driver accepts the proposed carrier-initiated edits.

When a driver logs in to a mobile running ELD software, the driver is prompted to review and accept or reject the changes.

Approve

To comply with ELD requirements, the Approve tab is renamed Certify and certifications are done per 24 hour period, not for multiple days at a time.

If certifications are pending, the driver is notified on the Hours of Service home screen by a pop up (to certify carrier initiated edits) or by on-screen text that the driver should be familiar with today. To review and certify logs, the driver goes to Certify tab and scrolls to the date requiring certification.

Old

New

Certifying

Certified

Unassigned Vehicle Movement

What was previously referred to as “Unknown” driving, e.g. when a driver’s credentials are rejected upon login or a driver logs out before being authenticated, is no longer reported as such by the mobile. Drive time recorded by a mobile without an authenticated driver is reported as Unidentified Driving. This means that no “Driving” duty status records display on the mobile running ELD software in the Vehicle Details page of the Hours of Service application when the “Unknown” filter is selected.

When unidentified driving is recorded on an ELD, the next driver that logs in to that mobile is required to accept or reject the unassigned driving records that have been saved by the mobile.

Note: A host user will not be able to assign these Unidentified Driving records unless a driver has rejected them or an 8-day period has passed with no action taken on the mobile.

Vehicle Identification Number (VIN) Capture

To meet the requirements of the ELD mandate, the VIN is captured from the JBus and displayed on the mobile interface and in reports.

Engine Hours Capture

Accumulated Engine Hours are recorded when a change in duty status occurs. Total Engine Hours are recorded for non-duty status change events such as vehicle power up/down, driver login/logout, and when malfunctions and data diagnostics alerts occur.

Screen Changes

In addition to the previously stated functional changes, all screens in Hours of Service were updated to be easier to read. Below are the details of the screens that have changed features or are new to this release.

Initial Login

When logging in to the MCP, drivers are no longer On Duty by default. They are prompted to identify their duty status immediately after they enter their ID and password.

Logging Out

There’s a logout prompt that parallels the login prompt for drivers forcing them to identify their duty status when they log out.

Change Duty Status

The Change Duty Status screen has changed to make it easier to use. The duty status DRIVE cannot be manually selected by drivers with ELD firmware.

Today, the driver is automatically placed into various duty status when location, distance, or time thresholds are met. With this firmware release, the only automatically assigned duty status is driving activity.

Old

New

Fixes

General

  • The preferred roaming list is updated.
  • The mobile no longer reboots when changes are made to the audio or language settings.
  • Spurious power malfunction errors are no longer being reported.
  • General performance updates and fixes.
  • Invalid characters are no longer accepted on the login screen. Those characters incldue: ^ & _ [ ] { } <> ~ ` \ |

Critical Event Reporting

Detroit Assurance P4 trucks are now supported and do not generate false alerts.

Exact Fuel

Some customers experienced an issue in 165x firmware releases that affected Exact Fuel delivery. This issue is corrected and its data is now accurately sent to the host application.

Hours of Service

  • The Hours of Service interface was changed so that after an upgrade, the application no longer falsely indicates that the inactive driver became the active driver.
  • Comments related to duty statuses on the Graph Tab are now correctly associated with each status.
  • Drivers may now select YES or NO when prompted to switch to On-Duty from Driving at end of trip.
  • End of Personal Conveyance duty statuses are being recorded and displayed correctly.
  • To reduce confusion during roadside inspections, the driver day log header displays "AOBRD" when the MCP is running in AOBRD-mode.
  • The Clock In/Clock Out time field is now restricted to valid times.
  • The location in the Day Log now resolves to a city state/province not a latitude/longitude.
  • The driver is no longer prompted multiple times to reenter load information.
  • Drivers cannot select or edit a log to select the special condition Personal Conveyance while off duty if personal conveyance is not enabled for that driver.
  • ELD diagnostic and malfunction alerts are suppressed for MCPs in AOBRD mode. Events and notifications for sensor failures (GPS, odometer, and speedometer) are still displayed.
  • The date and time a diagnostic/malfunction alert was generated is now displayed through Alert Manager.
  • The status that is automatically populated with Remarks details on the HOS graph is now consistent with other platforms.
  • The Yard Move duty status is now ended if a driver changes from US to Canadian rules.
  • The Day Log Certify and Graph screens now allow drivers to navigate among only eight days of on an 8-day duty cycle.
  • New validation on speedometer values ensures that spurious vehicle movement segments are not recorded.
  • The Yard Move duty status may be ended now by the driver manually changing the duty status as well as a 20 MPH (31 km/h) speed threshold, power cycling (turn off/on) the MCP, or both. This feature can be configured at the host.
  • The MCP no longer reports false border crossings.
  • With this firmware release, the current geolocation is used when a duty status generated by a team driver at end of trip or when a driver's logs are split at midnight.
  • A new CMV entry will be written to ERODS only when a driver uses a different ELD unit or the associated VIN changes. In that case, the ELD Event records will point to the appropriate CMV record.
  • The Edit button on the Certify tab is disabled when the driver selects their current duty status. This prevents the driver from editing their duty status record on the day it begins.
  • Regional settings for use of commas and decimals in numeric fields are ignored for latitude/longitude fields to ensure accurate lat/long formats are stored and sent to the host application in the expected format.
  • Upon start up, the MCP now filters invalid accumulated miles and distance since last valid coordinates before calculating, displaying, and passing those values to the host applications. This filter prevents invalid odometer validation failure notifications.
  • Drivers are now prompted to review and accept/reject all drive time swaps.
  • Driver mode now correctly displays distances in kilometers when that unit of measure is selected.
  • The Clock In/Clock Out date field now respects the drivers preferred date format.
  • The Load ID entry screen was updated to display the full load ID, have consistent look and function as compared with other platforms, the Invalid Unload Time is displayed when there is a date conflict.
  • The Load History screen now correctly refreshes with accurate historic load information after a load is deleted.
  • Drivers are now prevented from entering commas in the Trailer ID field.
  • The inactive driver's ID now correctly displays in all locations as expected.
  • The pending Carrier Edits prompt now displays even if another alert is displayed with the notification is received by the MCP.
  • Underscores "_" are now correctly displayed on the New Load and Edit Load screens.
  • Certified logs may now be edited from the Certify tab.
  • Clock in/clock out validations were updated to alert the driver when invalid clock in/out dates/times are entered. Those changes include:
    • clock-out: driver is not already on-duty
    • clock-out: clock-out time provided is in the past
    • clock-in: the clock-in would overwrite driving time
    • clock-in: the clock-in would overwrite personal conveyance
    • clock-in: the clock-in would overwrite yard move
    • clock-in: the clock-in would overwrite records involved in a driving swap
  • To prevent instances where the active driver and co-driver are in a driving state at the same time, pop-ups no longer prevent drivers from using the Driver Login application while Hours of Service is updating behind the scenes.

In-Cab Printing

Brother printer RJ4040 is now supported.

Navigo

When using Workflow with Navigo, routes are now correctly generated when the Navigation button is pushed.

Omnitracs Navigation

  • Omnitracs Navigation is no longer configured to launch automatically in the background by default. Customers may set it to launch automatically by default.
  • The mobile no longer blue-screens when Navigation is running in the background.

Weigh Station Bypass

Upgraded to version 2.0.1A to reduce communication failures.


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