Ignoring Excessive Odometer and Fuel Meter Readings
In some situations, OBC devices will report erroneous (very large) odometer and fuel meter readings, which can lead to reporting of excessive distances. To avoid this situation, this release sets an arbitrary limits and ignores meter readings that are either zero or less, or 2,000,000 or more.
Ignoring No-Vehicle Odometer Readings
In some cases, OBC devices will report odometer readings without an associated vehicle. This can lead to erroneous distance calculations if the transactions are subsequently matched with the wrong vehicle. With this release, odometer transactions without a vehicle are ignored.
Vehicle Reporting with XRS Trip Data
Route activity derived from the XRS Trip web service has only a single vehicle associated with it. Occassionally, multiple vehicles will be used for a trip, and this leads to the misleading assumption that all activity was associated with the specified single vehicle. Due to this condition, this release no longer associates a vehicle with Stop Begin, Stop End, Delay and Task events derived from the Trip web service.
Consistent Storage of Data in Route Event HOS Vector Cells
The Route Events for on-duty, off-duty, drive and sleeper events have two slots for system vector-cell columns that have not been used consistently in the past:
- Event Code
- Event Description
With this release, the following changes were made to the contents of those two slots:
- For the Omnitracs interface: (1) blank and (2) GPS location description
- For the Telogis: (1) Telogis Substatus and (2) Telogis Remarks