Professional Documents
Culture Documents
The focus with SDD was based on a symptom driven approach allowing the Technician to narrow down
the fault possibilities based on DTCs present.
PATHFINDER has a slightly different approach where Concern areas can be selected leading to a
Guided Diagnostic flow. The Guided Diagnostic flow is a set of questions and tests that lead you through
to a diagnosis.
Another focus in PATHFINDER development was to reduce the clutter on the screen and provide a
cleaner experience.
The functionality and icons shown in this document refer to PATHFINDER version 148 onwards.
Areas Covered:
• Screen Layouts and Information: What is where, what the icons are for and how to get
around.
2 Right Frame Here, you have access to screenshot and Quick Start menu
for SDD Quick Launch menu to access debug and monitor.
3 Lower Frame This allows you to select the type of session you are planning
on running.
In SDD, once the vehicle is detected, you are asked about the type of session you want to launch. You
are then not able to select the other session types/functionality without a session restart.
In PATHFINDER, the main visual framework is always present within a session, providing you with
status information and navigation control.
Offline
Disconnected from
VCI
In PATHFINDER, the outstanding campaigns for a vehicle are shown directly in the Vehicle Home
screen. If the outstanding campaigns are clicked, PATHFINDER will either:
1. Launch the PATHFINDER function(s) required for the campaign when supported by a
Guided Diagnostic flow.
2. Transfer you to a TOPIx page about the campaign. You can read the Campaign detail
but you cannot launch it from this page.
Note: If the Campaign is not supported directly with a Guided Diagnostic flow, it is important to read the
campaign detail to understand how to complete the campaign.
Service Functions
In SDD, 'Service Functions' includes component replacement setup applications, as well as general
service applications like Pre-Delivery Inspection (PDI) and Service Interval reset.
In PATHFINDER, this is called 'Service'. ‘Service’ contains general service applications, and certain
functions that involve multiple Electronic Control Units (ECUs) such as 'immobilization’.
Diagnostics
In SDD, diagnostics use a symptom driven approach, allowing the Technician to narrow down the fault
possibilities based on Diagnostic Trouble Codes (DTCs) present.
In PATHFINDER, the approach to diagnostics has changed. ‘Guided Diagnostics’ provide a new way
of identifying faults by leading you through a set of questions, querying DTCs in the vehicle and taking
action to resolve the fault or directing you to use specific tools.
We have reduced the list of 2049 possible 'customer symptoms' down to 107 'concern areas'. This
makes it much easier to find the correct guidance for the fault you are experiencing. If any further detail
is required to narrow down a fault, you will be asked a question within the test itself.
Tests vary in complexity from simple TSB and DTC relevance checks to highly complex routines that
can:
● read signals from the vehicle
● drive actuators
● run on-demand self-tests
● update software
● make decisions based on snapshot data values, etc.
Tool Functionality
Being experienced with SDD, you will be familiar with tools available within it but in PATHFINDER, there
are some changes in the way these tools operate.
‘Datalogger’ is one of these. In PATHFINDER, similar functionality can be found in ‘Live Data’.
Live Data allows you to view up to four signals at the same time in a graphical view. Alternatively, Live
Data has a table view, which does not have a limitation to the number of signals displayed. However,
we recommend a maximum of 10 signals are displayed at once, as the refresh rate decreases
proportionately with the number of signals.
Live Data does not support the saving/review of this data. It is recommended to use the ‘Screen Capture’
function to have Live Data information saved with the session files.
PATHFINDER is limited to displaying Live Data from one ECU at a time, compared to SDD which allows
data from any module to be displayed side-by-side.
The following are examples of tools present in SDD but are not supported in PATHFINDER:
SDD Pathfinder
SDD 2 weeks
PATHFINDER Weekly
On occasion, additional releases will be made to address market concerns where a manual patch
cannot be implemented.
How it works:
SDD requires a sequential patch update or full DVD release download/install.
PATHFINDER only downloads and installs content that has been changed from your current version.
However, once your version gets too old, a full download is required.
Note: Updates are small and downloaded/installed quickly if each update is taken. Content is complete
including any NGI updates required.
Note: If updates have not been taken for a while, an update package needs to be created and then
downloaded/installed. This means it will take a long time to create/download and install the large update.
In PATHFINDER, the software update created is based on the number of releases out of date your
machine is. If your installation is two versions out of date, it will require at least twice the amount of time
to create the update, download and install it. Older versions will take multiple times more.
PATHFINDER handles session files slightly differently. Session files are sent to JLR when you start a
new session or within 20 minutes of completing a session, whichever is soonest. A ‘Session File
Extractor’ is available for you to save the session file for your use - this can only be completed if the
session file has not been sent to us.
Vehicle Connection
Both SDD and PATHFINDER require a Vehicle Communication Interface (VCI) to send and receive
information from the vehicle.
SDD uses the JLR VCI, but can also use other VCIs like Mongoose JLR-Pro or DA-Davina2.
PATHFINDER supports the JLR DoIP VCI. The DoIP VCI MUST only be used with a USB cable.
Note: The WiFi USB Dongle and Ethernet cables supplied with the DoIP VCI MUST NOT be used, and
should be stored safely within your service department for future use when formally announced.
Note: WiFi Connection for DoIP VCI is NOT supported, and the functionality must be disabled for
all DoIP VCIs. There have been reported instances of connectivity concerns, resulting in module
updates and programming failing when the WiFi Connection has been used for the DoIP VCI.
All DoIP VCIs must be connected to the JLR Approved Diagnostic Equipment using the Universal
Serial Bus (USB) connection.
1. Close PATHFINDER
2. Ensure the VCI is connected to the machine via the USB connection
3. Select 'Start' from the lower left corner
4. Select 'All Programs'
5. Select 'Bosch' folder
6. Select 'VCI Software(JLR)' folder
7. Select 'VCI Manager (JLR)'
8. From the 'VCI Explorer' tab, select the VCI device and select 'Connect'
9. Select 'Network Setup' tab
10. Within the Interface Control window - untick the Enable Wireless Interface option
c2t5ZmVycm87MjAyMi0wNS0wM1QxMjowNDozNi43MjBaOzEyMy4yMzEuODQuMjE1O1NBSkFDMDRWMUREUzk1Njg5