Vehicle-specific Installation Notes

Vehicle-Specific Installation Notes

Table of Contents

Vehicle-Specific Installation Notes        1

Table of Contents        1

Installation Notes on Specific Harnesses        3

HRN-CS14S2        3

16-Pin Harnesses        3

Installation Notes on Specific Vehicles        3

2017 IC PB105        4

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

Installing an Adapter Harness        4

Ford Fusion (All years)        5

2009 Nissan UD        5

Ford Sterling (Multiple years)        6

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

Professional Installation Required        6

Telematics Devices and Third-Party Devices        7

Wheelchair Lifts        8

Intermotive/Interlock        8

Braun/Braunability        8

Ricon/Wabtec        8

Maxon        8

Third-Party Car Alarms        8

Code Systems        8

Other Considerations on Telematics Device and Third-Party Devices        8

Vehicle Specific Bulletins        9

2012–2017 Camry Hybrid — Potential Dash Warning Lights        9

2012–2014 Ford Focus — TSB — Engine Lights        9

GM Vehicles and Seat Belt        10

2009-2010 Blue Bird BB Conventional — Engine Light Flashing        11

2017 Kenworth and Peterbilt Trucks with Paccar Motors        11

Volvo/Mack HD Truck (2019+)        11

Ethernet Updates on BMW G Series Vehicles        11

BMW/Mini Scan Tool Notice        11

2019+ Subaru Starlink Interference        12

Vehicle Specific Bulletins - Europe        12

Mercedes Truck Dash Message        12

European Volvo Bus Interference        12

Scania Dashboard Interference        12

Device Incompatibility in Select EU Iveco Euro 6 Bus and Truck Models        13

Installation Notes on Specific Harnesses


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.

16-Pin Harnesses

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

Installation Notes on Specific Vehicles

2017 IC PB105

The HRN-DS09T2 or HRN-DS09S4 must be modified by the user if the harness is connected to 2017 IC PB105 school buses. This is to accommodate new changes to the diagnostic port in order to maximize the amount of engine data the telematics device can receive from these buses. However, if you are using the HRN-GS09K2, the harness modifications are not required as changes are included with this harness. Please note there is no compatibility for telematics devices prior to version 7.  

Please refer to the diagram to see the wire connection between the male and female connectors on a typical HRN-DS09T2. The first step is to swap the C and J position. Normally, the yellow wire is connected to the C position. After modification, the yellow wire should be attached to the J position and the blue wire should be in the C position when finished. Similarly, the green wire that normally connects to the D position should be connected to the H position, and the purple wire should be in the D position when finished.


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

✱NOTE: Not using an adapter harness when one is required will result in limited engine data, i.e. 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, Installers 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), and Pin G and Battery Negative (Chassis ground).

Not Required:

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


  • If voltage between Pin F — Battery Negative measures between 2V~3V.
  • 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 connector) — an extension harness is likely needed during installation.

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. When installing in this type of vehicle, check for this ABS Check button. If it exists, ensure the device and/or zip-tie are not installed in such a manner as to obstruct or inadvertently trigger this button (see picture below).


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

Professional Installation Required

If the telematics device does not power on when connected, validate 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 obtain an ALDL shunt (SPR-ALDLSHUNT).

NOTE: The ALDL shunt is only compatible with telematics devices that are on firmware version 111.X.XX and 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 ( Please note that this is not a complete list and there may be some vehicles that are not listed in the document.


Validate whether GND is on PIN 4 or PIN 5 of the vehicle diagnostic port. PIN 16 of the port is PWR as shown in the connector image to the right.

Screenshot 2016-07-26 at 9.46.10 AM.png


If GND is on PIN 5, insert the ALDL shunt between PIN 4 and PIN 5 and push it all the way down into the recess.

If GND is on PIN 4, no ALDL shunt is needed. If the device does not power on, please contact support.



Bend the shunt handle back and forth repeatedly to detach it.



Ensure that the shunt sits flush with the bottom of the connector and that it is pushed all the way into the recess. Connect the telematics device to the vehicle’s diagnostic port again and verify that it powers on and beeps six times.


Once the device powers on, please refer to the installation steps in the Telematics Device Install Insert (

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


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 (No Engine Data). Contact your dealer/Reseller for more information.


Currently no gateway module exists. You must keep device in Listen Only Mode (no engine data). Contact your dealer/reseller for more information.


Currently no gateway module exists. You must keep device in Listen Only Mode (no engine data). Contact your dealer/reseller for more information.


Currently no gateway module exists. You must keep device in Listen Only Mode (no engine data). Contact your dealer/reseller for more information.

Third-Party Car Alarms

Code Systems

Certain third-party car alarms may beep during ignition off periods when the telematics device sends out heartbeats. This occurs because the telematics devices wake up at regular intervals to send a hello message and download new parameters (as required). Due to the device waking up, the alarm system may think there is activity in the vehicle and cause the alarm to beep.

There are two solutions to this:

  • 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.
  • 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, and PTOs.

If the method of communication for the third-party device does not use standard OBD-II 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 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 OBD-II parameters (no engine data). This repeats every 10 minutes, until the scanning device is removed.

Customers have the option to request to apply a parameter that disables the logic that causes the telematics device to stop requests. Please note that Customers who choose to apply this parameter must acknowledge that it may result in a third-party device to behave in a non-interoperable manner.

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 to appear on the dash, loss of power steering/brakes, failure to start the vehicle, and the potential for the vehicle to stall while moving.

We have observed that 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:

NHTSA Reference #10055324, TSB Reference #ASI-44460

GM Vehicles and Seat Belt

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:

  • Chevrolet Colorado — any year
  • Chevrolet Trailblazer — any year
  • Chevrolet Uplander — any year
  • GMC Canyon — any year
  • GMC Envoy — any year

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

  • 2007 Chevrolet Silverado — all models other than Classic
  • 2008 and newer Chevrolet Silverado
  • 2008 and newer Chevrolet Express – G1500, G2500, G3500
  • 2006 and newer Chevrolet HHR
  • 2006 and newer Chevrolet Impala
  • 2005 and newer Chevrolet Malibu
  • 2007 and newer Chevrolet Suburban
  • 2007 and newer Chevrolet Tahoe
  • 2009 and newer Chevrolet Traverse
  • 2007 and newer Chevrolet Avalanche
  • 2009 and newer Chevrolet Aveo
  • 2005 and newer Chevrolet Cobalt
  • 2011 and newer Chevrolet Cruze
  • 2007 and newer Chevrolet Equinox
  • 2007 and newer Chevrolet Suburban
  • 2011 and newer Chevrolet Volt
  • 2007 and newer GMC Volt
  • 2008 and newer GMC Savana
  • 2007 GMC Sierra — all models other than Classic
  • 2008 and newer GMC Sierra — all trim levels
  • 2010 and newer GMC Terrain
  • 2007 and newer GMC Yukon
  • 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 first install, and again for each subsequent firmware update. While it is impossible to prevent flickering during first install, the request is later stored in the device memory, and cannot be made again if the first install does not receive a valid response.

2017 Kenworth and Peterbilt Trucks with Paccar Motors

2017 Kenworth and Peterbilt trucks with Paccar motors MX13 and MX15 are not compatible with the HRN-DS09T2, HRN-DR09T2, and HRN-DR09S4 harnesses, and the HRN-GS09K2 kit on firmware 107.9.37, 109.9.37, 110.9.37, 102.11.37 or older. Engine data cannot be read from the vehicle when using these harnesses with these firmware versions.

Your telematics provider has released a new adapter harness HRN-BS04A1 available to order on MyAdmin. This adapter harness will resolve any compatibility issues going forward when used with HRN-DS09T2, HRN-DR09T2, HRN-DR09S4 or HRN-GS09K2, as well as recent production firmware. All affected devices should replace their current installation to add this new adapter as well as ensure devices are on the latest version of firmware.

    Volvo/Mack HD Truck (2019+)

For North American Volvo/Mack heavy-duty trucks (2019 and newer), use SPR-VOVKIT. 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 hardware fix to be available by Q4 2020. 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 DME (Digital Motor Electronics) 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 dash 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.

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. out 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. Please note, this workaround also minimizes the number of engine data requests from the telematics device.

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 busses. 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 recommended 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 recommended 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 EU Iveco Euro 6 Bus and Truck Models

There is an incompatibility between telematics devices prior to version 9, and select EU Iveco Euro 6 bus and truck models. When a telematics device and an external scan tool are connected simultaneously, tests show that excessive voltage resulting in 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.