Installation Notes on Specific Harnesses

HRN-GS16K2, HRN-GS09K2, HRN-GR09K1, and HRN-BD16S5

WARNING! California state law prohibits relocating the in-vehicle diagnostic connector during installation. If you are installing a Geotab harness or adapter, please follow the Direct Plug-In installation instructions in the relevant installation guide to avoid violating state law. Alternatively, you may be able to use an extension or conversion harness to install the GO device directly into the OBDII port or another emissions diagnostic data link connector port. For more information on Geotab harnesses and adapters, please refer to our Harness Identification and Application guide.

1. HRN-GS16K2 Installation - Direct Plug-In
2. HRN-GS09K2 Installation - Direct Plug-In
3. HRN-GR09K1 Installation - Direct Plug-In

Alternatively, telematics devices can be installed directly into the OBDII port using an extension/conversion harness that plugs directly into the OBDII port or other emissions diagnostic data link connector port. For more information on Geotab harnesses and adapters, see Harness Identification and Application.

HRN-CS14S21

This harness is designed to draw power from the vehicle from PIN 14. However, in some situations, the vehicle may receive power from PIN 1. To prevent this, please follow these instructions when installing the harness:

1. Install the harness and check that the Telematics Device can power on.
2. If yes, the install is complete.
3. If not, check which PIN is providing power — PIN 1 or PIN 14.
4. If the power is on PIN 14 and the device is still not turning on, contact Support.
5. If the power is on PIN 1, move the PIN on the connector from PIN 14 to PIN 1.

✱ NOTE: This harness is only compatible with Telematics Devices that are on firmware version X.23.XX or newer.

✱ NOTE: If the pins (1 & 14) attached to the harness do not function, or if alternate power is desired, connect the exposed wire on the battery connector to an active power source while the vehicle is off.

16-Pin Harnesses

For heavy-duty trucks, always use a vehicle-specific harness when offered by the Telematics Provider or vehicle manufacturer. Where a heavy-duty truck-specific harness is not offered by the Telematics Provider or the vehicle manufacturer, use the adapter harness (HRN-CG13S1) for any 16-pin (OBDII) installation method to avoid possible Telematics Device damage.

Hardware Selection for Different Physical Environments

You must select the right Telematics hardware suitable for your specific installation environment and vehicle use. For installations where exposure to the elements (for example, liquids, dust, or interior wet cleaning/powerwash) is anticipated, the Rugged Telematics Device is the device to select (version 8 rated IP67, version 9 rated IP68 and IP69K), otherwise the standard Telematics Device may be used. For additional information regarding environmental contaminants, see the applicable Installation Instructions - Important Safety Information & Limitations of Use.

✱ NOTES:

1. Your Telematics provider does not permit third-party enclosures to be combined with standard Telematics Devices to act as a substitute for the IP-rated Rugged Telematics Device.
2. Telematics Devices generation 9 and newer have remote water intrusion sensing capabilities. The moisture detection will result in a device fault (visible in customer database/portal).
3. Resellers are responsible for correct device selection based on their customer’s application.

Installation Notes on Specific Vehicles

SAE Standard J1939-13 Type 2 — 9-Pin Deutsch Heavy-Duty Connector

In order to comply with SAE standard J1939-13 Type 2 connector, heavy-duty vehicles equipped with GREEN 9-Pin Deutsch connectors may require the use of adapter harness HRN-BS04A1 in conjunction with harnesses HRN-DS09T2, HRN-DR09T2, HRN-DR09S4, and HRN-GS09K2, running firmware version x.17.61+. Vehicles equipped with BLACK 9-Pin Deutsch connectors do not require an adapter harness. For help on identifying which vehicles require the adapter, refer to Installing an Adapter Harness section below.

✱ NOTE: The adapter harness is only required on Telematics Devices version 8 and prior. The adapter harness is not required when using a version 9 Telematics Device. Not using an adapter harness when one is required will result in limited engine data, i.e. the odometer will not be reported. Using an adapter harness when one is not required will result in no engine data at all.

Installing an Adapter Harness

If your vehicle has a Type 2 connector (GREEN 9-Pin port), it may require the use of an adapter harness. During installation, you should keep an adapter harness on hand in case it is required. To determine whether an adapter harness is required, you must use a voltmeter to calculate the voltage between Pin F and Battery Negative (Chassis ground), as well as Pin G and Battery Negative (Chassis ground).

Adapter harness not required:

1. If voltage between Pin F — Battery Negative measures approximately 5V.
2. If voltage between Pin G — Battery Negative measures approximately 1V.

Adapter harness required:

1. If voltage between Pin F — Battery Negative measures between 2V~3V.
2. If voltage between Pin G — Battery Negative measures between 2V~3V.

Ford Fusion (All Years)

The Telematics Device cannot be installed directly to the ALDL connector (due to the location of the connector). An extension harness is likely needed during installation.

Ford F-Series (2019+)

Use two cable ties to secure the HRN-GS16K2 to the Factory Ford OBDII module as shown above.

✱ NOTE: Over tightening cable ties may lead to damaging the harness connector

2009 Nissan UD

The Telematics Device must be connected to the 9-pin diagnostic connector (do not connect directly to the 16-pin ALDL connector) in order to receive engine data correctly.

Ford Sterling (Multiple Years)

In some model years, this vehicle may have an ABS Check button near the diagnostic connector. If it exists, ensure the device and/or cable-tie are not installed in such a manner as to obstruct or inadvertently trigger the button (see image below).

Vehicles with GND on PIN 5 only (111 Product ID)

Professional Installation Required

If the Telematics Device does not power on when connected, ensure that the engine diagnostic port has power. The Telematics Device requires GND on PIN 4 of the engine diagnostics port. If your vehicle's engine diagnostic port has GND on PIN 5 rather than PIN 4, insert the ALDL shunt between PIN 4 and PIN 5 as shown below. Please contact your Authorized Reseller to order an ALDL shunt (SPR-ALDLSHUNT).

✱ NOTE: The ALDL shunt is only compatible with Telematics Devices that are on firmware version 111.X.XX and newer and that have a recess for the shunt around PIN 4 and PIN 5, as shown in the installation steps below. Telematics Devices that do not meet these conditions do not require the ALDL shunt.

For a list of vehicle makes and models that require an ALDL shunt, see (http://goo.gl/NeM1kC). This is not a complete list and there may be some vehicles that are not listed in the document.

Once the device powers on, please refer to the installation steps in the Telematics Device Install Insert (goo.gl/rkLRiA).

Telematics Devices and Third-Party Devices

We have experienced issues with Telematics Devices and certain aftermarket third-party devices from certain manufacturers (e.g. wheelchair lifts and idle mode controllers). Generally, these specific devices do not work well with the Telematics Device or any other devices plugged into the diagnostic port. Symptoms you may experience include the vehicle failing to start or being unable to shift out of park.

To assist with this, some manufacturers provide a Gateway Module connector that allows another device to be plugged into the diagnostic connector. This allows the Telematics Device and other diagnostic tools to work in conjunction with the third-party device.

Wheelchair Lifts

Intermotive/Interlock

When the Advanced Fast Idle System (AFIS Series) is in use, the Telematics Device must be plugged into the Gateway Module (which must be purchased from Intermotive directly), otherwise the device will need to be put into Listen-Only Mode (limited/no engine data). Contact your dealer/Reseller for more information.

Braun/Braunability

Currently no Gateway Module exists. You must keep the device in Listen-Only Mode (limited/no engine data). Contact your dealer/Reseller for more information.

Ricon/Wabtec

Currently no Gateway Module exists. You must keep the device in Listen-Only Mode (limited/no engine data). Contact your dealer/Reseller for more information.

Maxon

Currently no Gateway Module exists. You must keep the device in Listen-Only Mode (limited/no engine data). Contact your dealer/Reseller for more information.

Vehicle/Battery Kill Switch

This is also known as the Emergency/Power off switch. Select vehicles offer the operator the ability to cut off battery power to all the vehicle’s electronic systems. Your Telematics Provider strongly discourages standard installation of a Telematics Device in these vehicles. For vehicles with such battery switches — Customers are encouraged to seek an alternate method of installation that offers continuous power to the Telematics Device, in the event the Vehicle Kill Switch is engaged. Failing to adhere may result in some engine data being lost until the Telematics Device finishes post-reset provisioning.

Third-Party Car Alarms

Certain third-party car alarms may trigger during ignition off periods when the Telematics Device sends out heartbeats. This occurs because the Telematics Devices turn on at regular intervals to send a hello message and download new parameters, as required. Due to the device turning on, the alarm system may indicate there is activity in the vehicle and cause the alarm to trigger.

There are two solutions to this:

1. Adjust the sensitivity on the third-party car alarm to not set off when the vehicle is turned off and the network is actively communicating.
2. Turn off heartbeats on the Telematics Device so that no communication occurs during ignition-off periods. This can be done through a custom parameter. Please contact your dealer/Reseller for further information.

Other Considerations on Telematics Device and Third-Party Devices

Over time, we have learned that connecting a Telematics Device to a vehicle where a third-party device is present can cause the third-party device to lose functionality. This includes, but is not limited to: wheelchair lifts, idle control modules, PTOs, and scan tools.

If the method of communication for the third-party device does not use standard OBDII commands, or if the third-party device is not interoperable on a vehicle network with a Telematics Device, or another third-party device, the Customer should contact their Reseller Support to enable Listen-Only Mode on the Telematics Device.

Customers are also encouraged to contact the third-party device vendor to inquire about a compatibility mode setting. If a compatibility mode is not available, Customers can request to apply Listen-Only Mode to their devices. If a compatibility mode is available and enabled, Listen-Only Mode is not required. Also, our Telematics Devices have firmware logic to halt requests if excessive errors are detected on the vehicle’s CAN network.

✱ NOTE: When in Listen-Only Mode, all vehicle types (except J1939 or GM) have reduced engine data support. For example, a device cannot request Revolutions per minute (RPM), or calculate idle time accurately.

In the event that a third-party scanning device is connected after the Telematics Device is connected, the Telematics Device will detect the presence of the new hardware, and temporarily stop requesting OBDII parameters (limited/no engine data). This repeats every 10 minutes, until the scanning device is removed. Customers have the option to request parameters that adjust the Telematics Device’s sensitivity, whilst in the presence of other third-party hardware.

Vehicle Specific Bulletins

2012-2017 Camry Hybrid — Potential Dash Warning Lights

We have detected that some 2012–2017 models of the Toyota Camry Hybrid display intermittent dashboard warning lights when connected to a version 7 Telematics Device with product ID 111, or version 8 Telematics Device with product ID 114. Our investigation has determined that the unique electrical characteristics inside the impacted vehicles can cause damage to the device circuitry, leading to the symptoms described. We have designed and tested a new type of Telematics Device (product ID 113 for version 7, and product ID 115 for version 8). Going forward, we will only be producing this new Telematics Device type.

2012-2014 Ford Focus — TSB — Engine Lights

We are aware of a Ford Focus Service Bulletin impacting all 2012–2014 Ford Focuses. The bulletin indicates that there is the potential in these vehicles for the CAN circuit, located on the underside of the front passenger seat, to short to ground. This issue can cause erratic behavior to occur inside the vehicle. Possible symptoms include engine warning lights appearing on the dash, loss of power steering/brakes, failure to start the vehicle, and the potential for the vehicle to stall while moving.

! IMPORTANT: The likelihood of these symptoms occurring is higher with a version 6 Telematics Device installed.

We strongly recommend that any Customer using a version 6 device in a 2012–2014 Ford Focus have the vehicle serviced under the TSB Reference #ASI-44460 before continuing to use the Telematics Device in the vehicle.

More information on this issue is available here:

1. http://www.fordproblems.com/tsbs/Focus/2014/
2. http://www-odi.nhtsa.dot.gov/owners/SearchSafetyIssues

NHTSA Reference #10055324, TSB Reference #ASI-44460

GM Vehicles and Seat Belt Data

Some GM vehicles require the version 7 of the device or newer to properly detect seat belt data due to the hardware limitations of the version 5/version 6 device.

The following vehicles types will receive seat belt data on V5/V6:

1. Chevrolet Colorado — any year
2. Chevrolet Trailblazer — any year
3. Chevrolet Uplander — any year
4. GMC Canyon — any year
5. GMC Envoy — any year

The following vehicles will not receive seat belt data when used with V5/V6:

1. 2007 Chevrolet Silverado — all models other than Classic
2. 2008 and newer Chevrolet Silverado
3. 2008 and newer Chevrolet Express – G1500, G2500, G3500
4. 2006 and newer Chevrolet HHR
5. 2006 and newer Chevrolet Impala
6. 2005 and newer Chevrolet Malibu
7. 2007 and newer Chevrolet Suburban
8. 2007 and newer Chevrolet Tahoe
9. 2009 and newer Chevrolet Traverse
10. 2007 and newer Chevrolet Avalanche
11. 2009 and newer Chevrolet Aveo
12. 2005 and newer Chevrolet Cobalt
13. 2011 and newer Chevrolet Cruze
14. 2007 and newer Chevrolet Equinox
15. 2007 and newer Chevrolet Suburban
16. 2011 and newer Chevrolet Volt
17. 2007 and newer GMC Volt
18. 2008 and newer GMC Savana
19. 2007 GMC Sierra — all models other than Classic
20. 2008 and newer GMC Sierra — all trim levels
21. 2010 and newer GMC Terrain
22. 2007 and newer GMC Yukon
23. Cadillac CTS

2009-2010 Blue Bird BB Conventional — Engine Light Flashing

Some Blue Bird vehicles flicker their engine warning lights when confronted with a request for Service Distance Remaining. When this occurs, the engine responds with “0xFFFF'' indicating it cannot support the request. However, the instrument cluster interprets this as a potential engine issue, and triggers a warning. The request is made on all J1939 vehicles during the first installation, and again for each subsequent firmware update. While it is impossible to prevent flickering during the first installation, the request is later stored in the device memory, and cannot be made again if the first installation does not receive a valid response.

2017+ Kenworth and Peterbilt Trucks with Paccar Engines

2017+ Kenworth and Peterbilt trucks with MX-series Paccar engines equipped with a generation 9 or newer Telematics Device require either the HRN-GS09K2 or the HRN-DR09S4, to capture additional engine data. For installations with a Telematic Device prior to generation 9, an additional adapter harness (HRN-BS04A1) is required to gather additional engine data. The adapter harness is not required with version 9 Telematics Devices.

Volvo/Mack HD Truck

For North American Volvo (2004 or newer)/Mack (2019 or newer) heavy-duty trucks , use HRN-CM24Y1 + HRN-CE10K2. Do not use HRN-GS16K2.

Ethernet Updates on BMW G Series Vehicles

Your Telematics Provider has identified an issue where select BMW vehicles with G series engines may be unable to complete software updates when a third-party device is installed with a universal T-harness (HRN-GS16K2). Your Telematics Provider is anticipating a hardware fix to be available by Q2 2021. To work around this issue, it is recommended to unplug the third-party device and the T-harness from the vehicle prior to updating the software. Your Telematics Provider disclaims any costs associated with failing to adhere to the advice above.

BMW/Mini Scan Tool Notice

We have identified a communication issue between third-party devices and the BMW or Mini scan tools. When a third-party device is connected to select BMW vehicles with F and G series engines, you may be unable to connect the BMW scan tool to the vehicle Digital Motor Electronics (DME) control unit. To work around the issue, it is recommended that you temporarily remove the third-party device and complete an ignition cycle prior to connecting a BMW scan tool. Your Telematics Provider anticipates a firmware fix in the upcoming months.

2019+ Subaru Starlink Interference

We have determined that select 2019+ Subaru vehicles equipped with the Starlink system may display a message or alert on the vehicle dashboard when a third-party device is installed. To mitigate this issue, we have developed a firmware fix available on firmware version XXX.28.30. Customers should contact their authorized telematics Reseller to verify the devices are on the latest firmware version.

Mercedes me Interference

Your Telematics Provider has identified an incompatibility with select light duty Mercedes vehicles model year 2017 or newer equipped with the Mercedes me platform in parallel with a Telematics Devices version 8 or older. A message may appear on the dashboard of the vehicle indicating, “Mercedes me service limited, see user manual” when a version 8 or below Telematics Device initiates a request on the CAN network. To work around this issue, Customers are encouraged to install a version 9 Telematics Device or alternatively, contact their Telematics Service Provider to apply Listen-Only Mode to the affected devices.

Vehicle Specific Bulletins — Europe

Mercedes Truck Dash Message

We have identified an incompatibility between our Telematics Device and the following Mercedes-Benz vehicle models: Actros, Antos, Arocs, Atego, and Axor. When a third-party device (i.e. a Telematics Device) is installed into the OBDII port in the vehicles listed above, a message may appear on the dashboard. This message does not indicate an actual DTC or engine fault, rather the message is an Information message. Third-party device installation may interfere with the real-time display of the tachograph Driving Hours data; however, the recorded tachograph data is not affected.

Mercedes-Benz provides two options to circumvent the device incompatibility. However, both options require a qualified Mercedes Engineer to service the vehicle and may impact the engine data available from the vehicle. For more information, please click here or contact your OEM-authorized service garage. You also have the option to contact and request your Telematics Service Provider to apply the Listen-Only Mode to the affected devices to disable the information alert referenced above.

✱ NOTE: This workaround also minimizes the number of engine data requests from the Telematics Device.

An alternative option is to install a version 9 Telematics Device using HRN-CW03K3 and IOX-UREADER. In this configuration, the Telematics Device will not require Listen-Only Mode and will report engine data.

European Volvo Bus Interference

We have identified a potential issue when a third-party device (i.e. a Telematics Device) is installed in 2013 or newer Euro 6 Volvo buses. When the CAN line receives multiple VIN requests, the vehicle’s Engine Control Unit (ECU) may react by shutting down while idling. To work around this issue, Customers are encouraged to contact their Reseller Support prior to installation to enable a parameter on the Telematics Device to disable the VIN request.

Scania Dashboard Interference

We have identified an interoperability issue between the Telematics Device and select Euro 6 Scania vehicles: a dashboard message may appear as a result of a VIN request. To work around the issue, Customers are encouraged to contact their Reseller Support prior to installation to enable a parameter on the Telematics Device to disable the VIN request.

Device Incompatibility in Select Iveco Euro 6 Bus and Truck Models

There is an incompatibility between Telematics Devices prior to version 9, and select Iveco Euro 6 bus and truck models. When a Telematics Device and an external scan tool are connected simultaneously, tests show that excessive voltage — damage to the device can occur. To workaround the issue, it is recommended that you temporarily remove the device before connecting a scan tool. Improvements in Telematics Device version 9 will prevent this issue from recurring in Iveco vehicles.