The Implications And Concerns Caused By Swapping Modules Between Vehicles (SSM75366)

WARNING: This page is about the Defender 110, which is a different variant/trim than selected.

Publication date: 2021-04-27
Reference number: SSM75366

THE IMPLICATIONS AND CONCERNS CAUSED BY SWAPPING MODULES BETWEEN VEHICLES

TECHNICAL SERVICE BULLETIN

Reference Number(s): SSM75366, Date of Issue: April 27, 2021

LAND ROVER:	Defender/L663; Discovery/L462; Discovery Sport/L550; New Range Rover Evoque/L551; Range Rover/L405; Range Rover Evoque/L538; Range Rover Sport/L494; Range Rover Velar/L560
SERVICE CATEGORY:	Diagnostic Software Hardware

ISSUES

Incompatible software has been loaded to the module using PATHFINDER or Software Over the Air (SOTA).
The Car Configuration File (CCF) from another vehicle has been loaded.

Many Technical Assistance cases has been submitted stating that concerns with the vehicle have only happened since a module has been replaced and programmed using PATHFINDER.

Investigations have concluded that swapping modules from other vehicles (for diagnosis purposes) has caused these concerns.

CAUSE

Incompatible software has been loaded to the module using PATHFINDER or Software Over the Air (SOTA)

Our latest diagnostic platforms require up to date module assembly information to be stored in a 'cloud based' format.

Jaguar Land Rover store a 'digital twin' of the vehicle, this information gets updated regularly.

Every time a PATHFINDER session is closed, all the module information from that session is loaded to a server. If a module with different (incompatible software) is fitted during that session, the information will be updated regardless of this.

When the module is then replaced the new module will be supplied with no software (in most cases), PATHFINDER will need to use the information from the server to select the compatible software. Since the information on the server is now incorrect, incompatible software will be loaded to the new module.

When any SOTA update is completed, the same information on the server is referenced. Fitting a module from another vehicle can cause the incorrect information to be stored within the 'digital twin'. This can cause incompatible software to be loaded via SOTA.

The Car Configuration File (CCF) from another vehicle has been loaded to the vehicle

During a PATHFINDER diagnosis session, the Vehicle Identification Number (VIN) is read from most modules fitted to the vehicle. This information is used to select the correct vehicle information from the server.

When a module has been fitted from another vehicle the VIN number does not match the VIN number of the vehicle we are intending to diagnose. In this situation PATHFINDER changes the session VIN number to the one stored within the swapped module. Pathfinder then downloads the information for that (incorrect) vehicle from the server.

If the CCF select application is completed, the CCF from the incorrect vehicle will be loaded. This causes major concerns with the vehicle connected to PATHFINDER as the CCF file is not correct for the vehicle. To add to this, when the session is closed, the incorrect CCF file and vehicle information is stored on the server.

ACTION

DO NOT swap modules from other vehicles for diagnostic purposes.

The statement below is taken from the DTC (Diagnostic Trouble Codes) index within TOPIx

CAUTION: Diagnosis by substitution from a donor vehicle is NOT acceptable. Substitution of control modules does not guarantee confirmation of a fault, and may also cause additional faults in the vehicle being tested and/or the donor vehicle.