Firmware Release Notes
Oct 19, 2018
*The xx portion of the Firmware version refers to the Product ID which defines the product type
Table of Contents
Please refer to this document to see what new features are included in each new release.
Proper installation requires the use of a cable tie to secure the Telematics Device to the OBD connector, or when securing both sides of an extension harness when attaching it to the OBD connector. If you do not use a cable tie, vibration within the vehicle can result in a poor connection which could indirectly cause the engine computer to fail. This could cause the vehicle to stall and may even cause personal injury if the vehicle is being driven when this happens. Please refer to the Vehicle Specific Installation Notes for any specific installation requirements for certain vehicles.
The following IOXs are currently available:
The Telematics Device can store up to 80,000 logs within the main memory in offline mode. Devices will buffer records over 100 minutes of second-by-second data (6,000 logs) within the accident memory. The last 72 records (1.2 minutes) are sent instantly for accelerometer-triggered accident-level events.
The Telematics Device is 24V compliant.
Telematics Devices with a 9-pin HD harness can support both J1708 and J1939 protocols simultaneously.
Engine status data has moved from protocol-specific logging to generic status data. Regardless of the source, the same data ID is used for any given segment of engine information. Rules are easier to write since the same information is no longer spread across different protocols. However, existing rules may need to be changed to incorporate the new generic status data.
Very few vehicles will return all the data above as it is based on all supported engine protocols.
Where appropriate, engine data is logged using the curve-based algorithm. More information about the curve-based algorithm can be found in the blog below:
VIN is a standard request and should be available on most vehicle types. There are some vehicles that do not reply to the VIN request or that reply with an invalid VIN number. If we do not receive a valid VIN from the vehicle, we will save a VIN containing all 0s. Disabling VIN requests will not prevent a VIN containing all 0s from being logged.
Device Total Fuel (2187) and Device Total Idle Fuel (2188) supersedes Trip Fuel Used (14) and Trip Idle Fuel Used (15). Trip Fuel and Trip Idle Fuel will continue to be logged for an interim period to ensure the Software can calculate your Fuel Usage whether you have the very latest firmware or not.
The Device Total Fuel values are saved in the device flash memory. This ensures they are retained after a firmware update or power cycle of the Telematics Device. If the Telematics Device is moved to a new vehicle (detected by a change in VIN), the Total Fuel values will be reset to zero.
Regardless of how fuel information is received from a vehicle, generic Device Total Fuel record is curved logged and is also saved after ignition OFF. Whether a vehicle is OBD2, J1708, J1939 or other, if fuel information is available, Device Total Fuel will be saved. An additional record, Device Total Idle Fuel, which is the fuel used while road speed is 0, is also saved on ignition OFF.
Seat belt and odometer data are proprietary on most passenger cars. It is our goal to support seat belt and odometer records across all the major vehicle manufacturers. If you are not receiving seat belt or odometer data on your vehicle, please contact Support. You can query what percentage of seat belt, odometer and other engine-based data is supported on your vehicle type though MyAdmin, or refer to the Vehicle Types and Engine Data at the end of this document.
The Telematics Device goes through a comprehensive seat belt data detection and verification process. It normally takes three trips for seat belt data to validate, but can take longer if there are multiple sources of seat belt data on a particular vehicle type. Each trip must last longer than one minute, and must include driving (speed greater than 10 km/hr) to be considered part of the validation process.
On every Telematics Device power up event, a seat belt value of -1 (unknown) is written to prevent the software from creating an ongoing “seat belt unbuckled” exception until the seat belt is re-detected. On every ignition change event, the seat belt state is set to “unknown” if it was in a previous buckled or unbuckled state. Setting the seat belt data to unknown ensures that the data from previous trips is not carried over to the present trip.
The Telematics Device has a two-stage odometer detection process in which we first locate the odometer information, then confirm the units of the odometer value (i.e. miles vs. kilometers). The first stage is locating the information. This can take anywhere from a minute to 40 minutes of ignition ON (driving is not necessary but the vehicle must be on), as the Telematics Device needs to exhaust numerous requests on various protocols.
The second stage requires 0.5 to 5 km of driving to verify that the odometer value is incrementing correctly. The first stage detection can be done over multiple trips. The second stage requires one continuous trip of 5 to 8 km for the units to be verified against GPS data.
The Odometer is logged for every ignition ON, ignition OFF and at every 8 km or every 1 km if GPS is invalid. Odometer validation occurs every time we receive an odometer value to ensure that it does not jump 15 km forwards or backwards between readings. If this happens twice during two trips with no recovery (i.e. the odometer does not return to its value within 15 km), an invalid odometer fault is logged and odometer values stop being reported.
Oil pressure is saved using curve logic under the following conditions:
On some vehicles, there is a discrete DEF level sensor. This will cause the DEF level to log values of 100%, 60%, 20% and 0%. For example, if a vehicle has DEF level between 100% and 20%, it will always report 60%.
Older Ford vehicles, specifically those with the older J1850 PWM OBD2 data bus, could potentially stall when certain valid OBD2 requests were sent to the engine computer. A workaround was implemented on the firmware; therefore, installing Telematics Devices in these vehicle types is no longer a concern.
Below is a link to protocol-specific vehicle data that has been replaced by generic status data in the Telematics Device firmware. Rules that include any of this protocol specific-data must have the new generic status data added to them.
Engine status data has moved from protocol-specific logging to generic status data; however, engine faults are still logged in the protocol-specific format. Several engine faults that are received by proprietary means are logged as generic fault data. When an engine fault is received, it is logged along with a generic fault of either Low priority warning light, or General vehicle warning light depending on the status of the MIL light. This allows a single rule to be used for notification of any engine fault.
Many internal Telematics Device faults have been logged as generic faults. These have been removed from the generic fault data and replaced with developer debug information. This prevents internal device warnings intended for developers from being displayed to end users when looking up vehicle specific faults. There are still device-based issues that are logged as faults when they are explicitly destined for the end user. These faults will often include actions to be taken such as validating the device install or contacting the Reseller.
The accelerometer is calibrated while the vehicle is being driven. This means there are no orientation restrictions when installing a Telematics Device in order for the accelerometer to work. The device does need to be securely installed for the accelerometer data is to be consistent. Because of real-time calibration, it can take one or two trips before the accelerometer is calibrated. Accelerometer data is sampled at 100 Hz and saved using the curve-based algorithm. The range of the accelerometer is from −8 g to +8 g with a resolution of 4 mg/bit.
Telematics Devices that are not securely installed have less reliable accelerometer behavior and may potentially not calibrate. Mounting the device to a surface with excessive vibration or knocking could generate excessive and/or incorrect accelerometer data. The Telematics Device detects excessive accelerometer logging and disables logging of sub-accident level accelerometer data. A Telematics Device fault will be saved at the time of the excessive logging detection.
Once calibrated, the accelerometer is virtually oriented as follows:
The accelerometer constantly logs events over 300mg in the X (front/back) or Y (side/side) direction using the curve-based logging algorithm. This ensures that as long as you set your rules to a minimum of 300mg, they will always be observed.
Beeping for driver feedback on harsh driving events are configured in the Software. Different thresholds are available for acceleration, braking and cornering. No feedback is provided when the vehicle is travelling under 10 km/h.
Any accelerometer event with a combined X/Y magnitude in excess of 2.5g will trigger an accident data upload. When an accident-level event occurs, the accelerometer data is uploaded. Five seconds later, the last minute of the second-by-second rolling accident data buffer is uploaded. Only three accident data buffer uploads can occur per trip. The value of 2.5g is a custom parameter and can be changed. It cannot be set to less than 2 g. Even if accelerometer data has been disabled due to excessive logging, accident level accelerometer data will still be logged.
The accelerometer can be used to detect reverse if you do not receive gear from the vehicle’s engine computer. The device can only detect the vehicle if out-of-reverse for five seconds after coming to a stop, or if the vehicle starts moving forward. Reverse detect is logged as follows:
An audible notification on reverse detection can be enabled in the Software — when enabled the device beeps continuously while reverse is detected.
10 seconds of instantaneous voltage logs are saved using the curve algorithm at every ignition ON event to record the vehicle’s crank voltage curve. An average voltage value is saved whenever it changes by 250 mV or more. If the vehicle voltage falls below 11.6 V for five minutes, the device logs a Low voltage warning fault and forces a heartbeat to ensure the low voltage value is communicated. 11.6 V is the default value and can be changed through a parameter. Heartbeats switch to every 23 hours once this has occurred to help preserve battery power. If the vehicle voltage is consistently lower than 7 V, the Telematics Device will remain in low power mode and will not operate until the voltage rises above 8V.
Curve-based logging is performed on both GPS position and GPS road speed to ensure the best fit on the map, as well as an accurate speed profile and idle time.
The following are default error values for the curve logging:
Note: An estimate error is used to predict where the value should be based on the last saved GPS record and then compares the current point with the estimated point to determine if it should be logged.
If GPS data is invalid, the road speed curve logging is performed using engine based road speed. Latitude and Longitude are used to validate GPS based road speed. If movement is detected by the accelerometer while ignition is off, the GPS is turned on. If the latitude or longitude changes by a sufficient amount (approximately 100m), the trip will be tracked and the modem will connect (if a live unit), and remain connected until the device stops moving.
The Telematics Device obtains the latitude and longitude directly from the GPS engine. For a GPS position from the GPS engine to be considered valid, the following conditions must be met:
Iridium now supports additional record types and can be configured to monitor the following:
Please refer to this document to see all the Access Point Names (APN) that are supported by the release firmware by default.
The Maximum Log Time parameter is used by the Software to determine the period of non-activity each trip requires to be considered complete. It should not be used to enforce data logging frequency. We can reduce the curve logging estimate error and have added a curve speed delta parameter to allow for more effective real-time logging.
The device connects every 30 minutes for the first 2 days. After 2 days, it connects once every 23 hours.
The following are the known issues with the current versions of the release firmware:
The following table in the link below represents an overview of engine data support for Odometer, Driver Seat belt, Fuel Usage, and Fuel Level from the Telematics Devices. The engine data percentage columns are calculated based on the total vehicles that the Telematics Devices have connected to.
Please refer to this document for a list of notices for included firmware/software libraries.