Manual Engineering-En US

User Guide
Offboard Diagnostic Information System Engineering
Confidential. All rights reserved. Any form of reproduction or dissemination

without the prior written consent of the specialist department of Volkswagen
AG is prohibited. Partners receive this document only through the responsible
procurement department. VOLKSWAGEN AG
Copyright © 2007-2019 VOLKSWAGEN AG Version 10.0.0
Offboard Diagnostic User Guide
Information System Engineering
1 Table of Contents
1 Table of Contents ............................................................................................ 2
2 General Operating Information ................................................................... 7
2.1 Header Area .................................................................................................... 7
2.2 Status Line ........................................................................................................ 8
2.3 Expandable Side Bar ...................................................................................... 8
2.4 Function Views ................................................................................................. 8
2.4.1 Start Screen ................................................................................................ 8
2.4.2 Control Module List View......................................................................... 9
2.4.3 Results Views.............................................................................................. 9
2.5 Table Operating Functions ......................................................................... 11
2.5.1 Sort Function for Tables ........................................................................ 11
2.5.2 Filter Function for Tables ....................................................................... 11
2.5.3 Copy Function for Tables ...................................................................... 12
2.5.4 Showing and Hiding Table Columns ................................................... 12
2.5.5 Changing the order of columns in the table ...................................... 12
2.5.6 Text Display for Control Modules with ODX Data ............................ 12
2.5.7 “Display Translated Service Texts" Display Mode ............................. 12
2.5.8 “Display LongNames from the ODX Data" Display Mode .............. 13
2.5.9 “Display ShortNames from the ODX Data" Display Mode ............. 14
2.5.10 Special Handling when Service Text Is Blank (TI MAS00194)......... 14
2.6 Using the Keyboard ..................................................................................... 14
2.7 Presets ............................................................................................................ 14
2.8 Online Help................................................................................................... 15
3 Diagnostic Entry ........................................................................................... 15
3.1 General information .................................................................................... 15
3.2 Start Response .............................................................................................. 16
3.3 Vehicle Selection .......................................................................................... 16
3.4 Managing Vehicle IDs ................................................................................. 17
3.5 Diagnostic Interface Selection .................................................................... 18
3.6 Vehicle Project Selection ............................................................................. 19
2
3.7 Project Entry Service Configuration ........................................................... 20

3.8 Automatic Diagnostic Entry Using the VIN ............................................... 20
3.9 Diagnostic entry with manual VIN selection ............................................ 21
3.10 Communication Path Specification ............................................................ 21
3.11 Diagnostic Entry Configuration .................................................................. 22
3.12 Unloading a Project ..................................................................................... 22
3.13 Evaluating Components List(s).................................................................... 22
3.14 Battery Voltage Monitoring ........................................................................ 23
4 Control Module List View ........................................................................... 23
4.1 Control Module List Columns ..................................................................... 25
4.2 Control Module List Update Cycles ........................................................... 27
4.3 Selecting Control Modules in the Control Module List ........................... 27
4.4 Selecting Diagnostic Functions for a Control Module............................. 27
4.5 Accessing Vehicle Functions ....................................................................... 29
4.6 Accessing Special Functions ....................................................................... 30
4.7 Deactivating Unused Functions .................................................................. 30
5 Identification ................................................................................................. 30
6 DTC memory ................................................................................................. 31
7 Measured Values......................................................................................... 33
7.1 Measured Values Selection View .............................................................. 33
7.1.1 Control Modules with KWP Protocol ................................................... 33
7.1.2 Control Modules with UDS Protocol .................................................... 34
7.2 Measured Values Display View ................................................................. 35
8 Coding ........................................................................................................... 36
8.1 Control Modules with KWP Protocol ......................................................... 36
8.1.1 Short Coding (KWP 1281, KWP 2000) .............................................. 37
8.1.2 Long Coding (KWP 2000) .................................................................... 37
8.2 Control Modules with UDS Protocol .......................................................... 37
8.2.1 UDS Binary Coding and KWP Long Coding ...................................... 37
8.2.2 UDS Plain Text Coding .......................................................................... 38
8.3 Saving Coding as a Preset .......................................................................... 39
8.4 “Special Coding" for KWP Gateways ....................................................... 39
3
9 Adaptation .................................................................................................... 39
10 Basic Setting.................................................................................................. 41
10.3 Special Instructions when Using the Keyboard ........................................ 46
10.4 Short Routines ............................................................................................... 47
11 Output Diagnostic Test Mode .................................................................... 47
11.3 Special Instructions when Using the Keyboard ........................................ 52
12 Hex Services ................................................................................................. 52
13 Access Authorization and Diagnostic Session ......................................... 54
14 Write Data Set.............................................................................................. 57
15 Reading and Writing Memory Cells ......................................................... 58
15.1 Reading Memory Cells ................................................................................ 59
15.2 Display of Read Memory Cells ................................................................... 59
15.3 Manipulating Read Memory Cells ............................................................. 60
15.4 Writing Memory Cells ................................................................................. 61
15.5 Preset Function.............................................................................................. 61
16 Baud Rate...................................................................................................... 62
17 Data upload ................................................................................................. 62
18 Stopping Diagnostic Communication ........................................................ 63
19 Transport Mode ........................................................................................... 63
20 Flashing ......................................................................................................... 63
21 Read Entire System ...................................................................................... 69
21.1 Equipment Level Documentation ............................................................... 69
21.2 DTC memory ................................................................................................. 70
21.3 Displaying and Comparing Logs ............................................................... 72
21.4 Sending Logs................................................................................................. 73
21.5 Equipment Level Check ............................................................................... 75
4
22 Copying Coding / Adaptation ................................................................... 76

23 Coding component lists ............................................................................... 78
23.1 Opening the coding component lists function in the "Control Module
List" View....................................................................................................... 79
23.2 Components List Displays............................................................................ 79
23.3 Button Function ............................................................................................. 81
23.4 Coding the Entire Vehicle Components List Automatically .................... 81
24 OBD ............................................................................................................... 82
24.1 Accessing the OBD Diagnostic Function ................................................... 82
24.2 Service OBD View – FunctionSelection ..................................................... 82
24.3 Supported Functions Display ...................................................................... 83
24.4 OBD Results Display .................................................................................... 83
24.5 Process for Various OBD Services ............................................................. 83
24.5.1 Mode 01 - Check Current Diagnostic Data ....................................... 83
24.5.2 Mode 02 - Request Powertrain Freeze Frame Data ......................... 84
24.5.3 Mode 03 - Request Emissions-Related Diagnostic Trouble Codes . 84
24.5.4 Mode 04 - Erase DTC Memory............................................................ 84
24.5.5 Mode 05 - Request Oxygen Sensor Monitoring Test Results........... 84
24.5.6 Mode 06 - Request On-Board Monitoring Test Results for Specific
Monitored Systems................................................................................. 85
24.5.7 Mode 07 - Request Emissions-Related Diagnostic Trouble Codes
Detected During Current or Last Completed Driving Cycle ............. 85
24.5.8 Mode 08 - Request Control of On-Board System, Test Or
Component ............................................................................................. 85
24.5.9 Mode 09 - Check Vehicle Information ............................................... 85
24.5.10 Mode 0A - Checking the Permanent DTC Memory ................... 85
25 Running GFF Scripts .................................................................................... 86
25.1 Vehicle Features Dialog .............................................................................. 86
25.2 Script Selection ............................................................................................. 86
25.3 Running Scripts ............................................................................................. 87
26 Macro Function ............................................................................................ 87
27 Trace Function .............................................................................................. 89
28 Creating a Results Log ................................................................................ 90
5
29 Support Function .......................................................................................... 91

30 ODX Runtime Data Update ........................................................................ 93
30.1 Configuration ................................................................................................ 93
30.1.1 ODX Info Files ........................................................................................ 93
30.2 Selection of ODX Data Packages .............................................................. 94
30.2.1 Dialog when Updating using Index Files ............................................ 94
30.2.2 Dialog when Updating using Diagnostic Data Server ...................... 94
30.3 Performing ODX Updates ........................................................................... 95
31 Application Update ..................................................................................... 95
32 Connection Test ............................................................................................ 96
33 Hotfixes.......................................................................................................... 96
33.1 Importing a Hotfix ........................................................................................ 96
33.2 Deleting a Hotfix .......................................................................................... 97
34 Appendix ....................................................................................................... 97
34.1 Using the Keyboard ..................................................................................... 97
34.2 Structure of a Flash Control File for Parallel Flashing .......................... 113
35 “ODIS Engineering” Privacy Policy .......................................................... 114
6
2 General Operating Information

User Interface Structure
The user interface for the Offboard Diagnostic Information System Engineering
application is divided into four areas:
 Header Area
 Status Line
 Expandable side bar on the right
 Function view
2.1 Header Area

The header area contains a vehicle communication status display. It is divided
into four areas (from left to right):
Vehicle Project and Identification

 Vehicle Project (such as: VW36x)
 Vehicle ID = VIN (such as: WVWZZZ1K9ZExxxxxx)
Vehicle ID
 Vehicle name (can be edited, linked with the vehicle ID)
Connection Status
 Vehicle connection (for example: VAS5054 – corresponds to the name of
the selected diagnostic interface or "DoIP" during a DoIP diagnosis)
 Vehicle status ("Hardware cannot be reached", "VCI busy", "VCI free",
"KL30", "KL15")
 The "VCI information" dialog can be opened through the "Info button". Fur-
ther details about the VCI connection are displayed here.
 Battery voltage given in volts with two decimal places. If the voltage is less
than 12 volts, it will appear in red; otherwise, it will be in green font. If it is
not available or cannot be determined, a “?” is displayed instead of the
voltage.
Note: the battery voltage is only displayed when a VCI that supports this is
selected.
(Refer to the chapter Battery Voltage Monitoring.)
This information is filled in once the application has detected it and is always
kept up-to-date.
7
Operating Modes
This area contains a button that you can use to switch between the "Diagnostic
tester" and "Administration" operating modes. The "Diagnostic" mode is active
when the application starts.
2.2 Status Line

This area serves as a status display for the program modes (Trace active dis-
play, etc.) and for configuration log and trace settings. The contents are de-
scribed with the corresponding program functions.
2.3 Expandable Side Bar

The side bar on the right edge of the screen contains buttons for various func-
tions that are not always needed during a diagnostic session, so they can be
hidden to enlarge the display area. You can open or close the side bar using
“>>” or “<<” buttons.
The side bar contains additional options for comprehensive functions:
 Log: functions for creating a results log
 Diagnosis: switch to diagnostic session, access authorization, Guided Func-
tions
 Equipment level documentation: use vehicle-specific functions for equipment
level documentation
 Macros: record and run macros
 Trace: operate the trace function
 Help: access to online help, sending a support request, vehicle allocation
(information about allocation between diagnostic data and vehicle projects)
 Configuration: configuration of the diagnostic interface, ODX and applica-
tion update, server connection test, hotfix
 Info: information about the installed software
2.4 Function Views

The various function views are shown in the left area of the application win-
dow.
2.4.1 Start Screen
The start screen appears first when the program starts. It allows you to select a
vehicle project using the drop-down menu. The list contains all vehicle projects
available in the system as well as "Engineering" and "Service" entries. When
one of these entries is selected, the application searches automatically for the
matching project based on the VIN. Otherwise, the exact project you have
specified is loaded. The "►" button under the drop-down menu triggers the
8
automatic or manual loading of the project. The "Control module list" view dis-
plays after the project loads successfully. An "Info" icon is displayed next to the
project selection combo box. After left-clicking on the "Info" icon, the "in-
dex.xml:" file for the vehicle project that is selected in the combo box will open
in the computer's default browser. This file displays the content for the selected
project. After left-clicking on the "Info" icon when selecting "Engineering" or
"Service" projects, the application executes the procedure with the "index.xml"
file for the project that is currently loaded. If there is no "index.xml" file availa-
ble or no project was loaded (as is the case when "Engineering" or "Service"
project selection is used), the message "No project information available" will
appear when the "Info" button is pressed.
Open results tabs will close automatically when the project is changed. Diag-
nostic entry starts (again) with the selected project only when the "Start" button
is pressed.
If you press the "End diagnosis" button (eject symbol), the application returns to
the start status after confirming so that all results tabs are closed and no pro-
ject is loaded.
2.4.2 Control Module List View
The control module list view can be opened by selecting the tab with a vehicle
symbol that is always located at the left, by using the keyboard short F4, or by
selecting the button with the vehicle symbol below the function selection area. It
displays the list control modules in the selected vehicle that were detected dur-
ing diagnostic entry in hierarchical order. The structure is described in more
detail in the "Control module list" chapter (see chapter 4).
2.4.3 Results Views
If a diagnostic or vehicle function should be performed, the operation and the
results views for the function are generally shown in a specific corresponding
results view that opens when the function is accessed.
A variable number of views can be generated at runtime when requested by
the user. The tabs in this view are arranged just like the tabs in the control
module list on the lower edge of the function view area. Each tab (meaning
each respective instance) is assigned to a specific diagnostic or vehicle func-
tion. Various views can be generated in the corresponding tab for each diag-
nostic/vehicle function while running (depending on what can logically be dis-
played on the screen). Only one results view can be opened for a specific con-
trol module for each diagnostic function, even if you open the function again in
the "Control module list" view. Likewise, only one results view is created for
each vehicle-wide function. By default, each tab that is generated contains a
unique name that differentiates it from views that already exist. The name con-
sists of a prefix according to the address of the control module that is being
diagnosed, as well as a suffix that represents the diagnostic function. Prefixes
9
and suffixes are separated by "–". Comprehensive control module functions

use the prefix "FZG". The suffix length is limited to a maximum of three charac-
ters for space reasons. The suffixes are created based on the following pattern:
Diagnostic function Suffix
001 – Identification ID
002 – DTC memory DTC
003 – Measured values MW
004 – Output diagnostic test mode SGD
005 – Basic setting GES
006 – Coding COD
006.04 Components list coding BMC
007 – Adaptation ANP
010.01 Write data set DAT
010.02 Memory cells SPZ
011.01 Hex service HEX
011.05 Data upload DUP
Vehicle function (Prefix FZG-)
040 - OBD service OBD
041 – Engine group GES
042 – Flashing FL
046.01 Coding / adaptation CDA
047 - Reading out complete system GSA
Diagnostic procedures
10
060 - Guided Functions GFF-BTL / GFF-RUN
061 - Macro function MAK
Multiple results views can be created for displaying measured values and run-
ning the "Service OBD" vehicle function by calling these up multiple times. A
number is then added to the prefix "MW" for the "Measured values" or "OBD"
for the OBD vehicle function according to the sequential number of the tabs
that are open. Up to nine results views (MW1 through MW9) can be opened
for measured values.
There are diagnostic functions and vehicle functions where no specific tab is
opened to display the results view. These are operated using specific pop-up
dialogs. For example, these may include the Access authorization, Diagnostic
session, Stop communication and Baud rate diagnostic functions, and the
Transport mode and Stop communication vehicle functions.
The buttons below the function selection or the corresponding keyboard
shortcut (see chapter 2.6) can be used to:
 Close all inactive results tabs (symbol x)
 Switch directly to the control module list view (vehicle symbol)
 Save the window settings for the active results view (folder symbol)
 Copy the active tables to the clipboard (table symbol)
2.5 Table Operating Functions

2.5.1 Sort Function for Tables
In many locations, the results views use tables to display information and some-
times for entering data. Each column can be sorted alphabetically in ascending
or descending order by left-clicking on the column header. Clicking the column
header again reverses the sorting order. The default setting for the first click is
to sort all tables in ascending order, either alphabetically or according to the
ODX data. Columns that contain only numbers are sorted in ascending numeri-
cal order instead. The current sorting order is indicated in the column header
with a triangular arrow. Certain tables may differ from these general guide-
lines based on the context (for example, sorting in groups, different sorting or-
der). This is described in the corresponding chapters.
2.5.2 Filter Function for Tables
There is a general filter function for table content in the results view. If a view
contains a filter, an input field with the label "Filter" is shown aligned at the left
below the corresponding table. After entering filter text in the input field, only
table content that contains an exact match of the entered "filter text" is dis-
played. The filter is not case-sensitive. The filter function is applied immediately
11
each time data is entered in the input field. If there is a table with multiple col-
umns or a tree structure, only the content in the first column is evaluated by the
filter. If there is a tree structure, only the first level is evaluated by the filter. If
an element in a tree is hidden by the filter function, then all of its sub-elements
will also be hidden. The input window is focused by clicking on the window or
using the keyboard shortcut "CTRL + F". If the user opens the entire tree struc-
ture with all levels using the + symbol, the filter function will be applied to all
levels.
2.5.3 Copy Function for Tables
If a table is marked in the results view, the content of the table can be copied to
the clipboard for additional use in external editors, either by clicking on the
active button below the function selection (or using the keyboard shortcut
"CTRL + C").
2.5.4 Showing and Hiding Table Columns
After right-clicking on the table header that contains the column names, a con-
text menu opens. It contains a list of names in the table columns with a check-
box in front. Activating or deactivating a checkbox shows or hides the corre-
sponding table column. The current view can be adjusted using the "win-
dows_preference" button.
2.5.5 Changing the order of columns in the table
The order of columns in a table can be changed using the context menu, which
can be displayed or hidden. You can open the context menu by right-clicking
on the table header. The menu contains arrow buttons for changing the order.
2.5.6 Text Display for Control Modules with ODX Data
In the Administration area (function configuration under ODX text display), you
can select from the following settings for displaying texts for control modules
with ODX data:
 Display translated service texts
 Display translated service texts with TI
 Display LongNames from the ODX data
 Display ShortNames from the ODX data
 Special Handling when Service Text Is Blank (TI MAS00194)
2.5.7 “Display Translated Service Texts" Display Mode
When displaying names, values, and units for control modules with ODX data,
the applicable service text (KD text) from the service reference table (KD table)
is displayed in the language selected for the ODIS Engineering application if
the text identifier (TI) is populated with data. If the service text is not available
in the service table in the selected language, the information to be displayed
12
for TI with data is to be taken directly from the ODX data. The cases are differ-
entiated as follows:
 If there is a parameter name and the long name is populated, the long
name will be displayed with the prefix "[LN]_".
 If there is a parameter name and the long name is not populated, the short
name will be displayed with the prefix "[SN]_".
 If there is a TEXTTABLE entry, this entry will be displayed with the prefix
"[VN]_".
 If there is a unit, the DISPLAY NAME will be displayed with the prefix
"[UN]_".
When displaying names, values and units from control modules populated with
ODX data, the information to be displayed is taken directly from the ODX data
if the TI is not populated with data. The cases are differentiated as follows:
name will be displayed with the prefix "[LO]_".
name will be displayed with the prefix "[SO]_".
"[VO]_".
"[UO]_". The TI will be placed in front of the service text if this is selected in
the "Administration" view. A space serves as a separator.
2.5.8 “Display LongNames from the ODX Data" Display Mode
In this display mode, ODX data is always used directly instead of service texts,
regardless of the TI data.
If the TI is populated with data, the cases are differentiated as follows:
name will be displayed with the prefix "[LN]_".
name will be displayed with the prefix "[SN]_".
"[VN]_".
"[UN]_".
If the TI is not populated with data, the cases are differentiated as follows:
name will be displayed with the prefix "[LO]_".
name will be displayed with the prefix "[SO]_".
13
"[VO]_".
"[UO]_".
2.5.9 “Display ShortNames from the ODX Data" Display Mode
In this display mode, ODX data is always used directly, regardless of the TI da-
ta. No service texts are displayed.
When the TI is populated with data, the cases are differentiated as follows:
 If there is a parameter name, the short name will be displayed with the pre-
fix "[SN]_".
"[VN]_".
"[UN]_".
If the TI is not populated with data, the cases are differentiated as follows:
 If there is a parameter name, the short name will be displayed with the pre-
fix "[SO]_".
"[VO]_".
"[UO]_".
2.5.10 Special Handling when Service Text Is Blank (TI MAS00194)
In the "Function configuration" section in the Administration area, there is an
additional option "Display blank service texts" as a duplicate selection under
the "ODX data display" tab. The following options are available for selection:
 Flat display (default setting)
 Hierarchical display
2.6 Using the Keyboard

As an alternative to using the mouse, you can also navigate and perform func-
tions in various views using the keyboard. The corresponding shortcuts are
listed in the attachment 34.1.
2.7 Presets
Presets store settings and configurations that are saved one time by the user
and then can always be accessed again. They can be found in each view
where you can configure or select content and information displays.
The presets functions described below can be accessed using two controls.
14
Available presets can be selected and activated using the combo box to the left
of the presets button. The names of all presets elements that correspond to the
selected control module type (control module address) and the selected func-
tionality are listed. The selection of a preset adapts the display according to the
information in the preset that is loaded.
The "Preset..." button opens a pop-up menu that provides various operations
for a preset.
The "New" menu item allows you to save the configuration that is currently set
as a preset with a specified name. The "Clear" menu item resets the configura-
tion that is currently set and if there is a stored preset, it is unloaded. The
"Save" menu item allows you to save the configuration that is currently set in a
preset that is already selected. This item is only active if you have changed the
configuration of a stored or loaded preset. The "Rename" menu item allows
you to rename and save a loaded preset. “Delete" allows you to delete the se-
lected preset without changing the selected configuration. The "Restore" preset
allows you to reset a preset back to the original content after changing the con-
figuration.
If you change the configuration of a preset but have not saved the changes yet,
there will be a red asterisk to the left of the combo box and a red frame
around it. "Unsaved settings" will also appear with the name of the preset.
The "Import" and "Export" menu items allow you to share a preset among var-
ious installations of the application. After pressing the button, a file selection
dialog opens. When exporting, you must specify a name under which the ac-
tive preset can be saved locally on the computer. When importing, the preset is
loaded into the application under the name specified in the file.
2.8 Online Help

If you press the "Alt" button in the ODIS Engineering application, keyboard
shortcuts that are available in the current active view will be displayed. Press-
ing "Alt" again closes this view. If you move the mouse over various elements in
the ODIS application, such as buttons, tool tips provide more information about
each element. If there is a keyboard shortcut for an element, it will also be dis-
played.
3 Diagnostic Entry
3.1 General information
If there is an active diagnostic filter, this will be indicated to the user when en-
tering. The user can accept the message and then continue to work with the fil-
ter. If the user performs an action during the display that makes the diagnostic
filter status no longer active, the message will close automatically.
15
3.2 Start Response

The "Diagnostic entry" view opens after starting the application. A full-screen
view of the welcome information with Technical Support contact information
and a copyright notice is initially shown in the "Selection and feedback" area.
In the "Function navigation" area, you can selected a vehicle project or press
the "Start" button. This button contains a large, green arrow that points to the
right. The vehicle project is selected from a drop-down list. If you press "Start"
without selecting a project first, either the vehicle project selected the last time
the application was used or an automatic project entrance is selected, depend-
ing on the project preference set for the control module list in the function con-
figuration section of the Administration area.
3.3 Vehicle Selection

With Diagnosis Over IP (DoIP), it is possible to connect to vehicles using Ether-
net or Internet connections. It is possible to display a selection list of vehicles
that can be reached from the test computer. Regardless of which VCI you have
configured, it is possible to select Diagnosis Over IP (DoIP) vehicles (meaning
DoIP VCIs) in the application. If you press the button with the icon "(multiple
vehicles)" in the entry view ("vehicle selection" tool tip), a vehicle selection list
opens. If a vehicle project is currently loaded, a confirmation dialog for closing
the current project will display first when the button is clicked, before the vehi-
cle selection list opens. A DoIP-capable D-PDU API is loaded to display the ve-
hicle selection list. Once this happens, a vehicle search (broadcast) takes place
in the network. There is an adjustable timeout period in the Diagnostic entry
section of the Administration area where you can specify an exact number of
seconds (the default value is 2 seconds). If no available DoIP vehicle is detected
within the timeout period, confirmation dialog that says "No DoIP-capable ve-
hicles found!" is displayed with the blank vehicle selection list. In other cases,
the first vehicle is selected when the vehicle selection list is first detected. To the
left of the vehicle list, there is a traffic light symbol in front of each vehicle that
signals the status:
Red light "DoIP vehicle busy"
Green light "DoIP vehicle ready"
Light off “DoIP status not yet detected"
Light off with a question mark “DoIP check failed"

above it
You can check the status of all vehicles in the list using the "Check DoIP Entity
Status" button. This also happens for the selected vehicle if you click the "Diag-
16
nostic entry" button. If there are no resources available in this case, the appli-
cation will ask if a connection should be established.
The "Close" button ("X" symbol) closes the vehicle selection list and returns to
the entry view. You can start a new vehicle search using the "Update" button. A
vehicle that was already selected before the update remains selected after the
update if it is still contained in the vehicle selection list. Otherwise, the first vehi-
cle in the list is selected. The "Vehicle ID" button ("magnifying glass" symbol)
opens an input dialog opens where a specific vehicle search can be performed
based on the parameter specifications (selection of the last selected vehicle,
input of a vehicle name, IPv4 address, or Iv6P address).
When the list of DoIP-capable vehicles is displayed, the "Diagnostic entry" but-
ton is only active if a vehicle in the vehicle selection list is selected. If you click
the "Diagnostic entry" button while the vehicle list is displayed, diagnostic entry
will run with the selected vehicle and the selected vehicle project. Double-
clicking and the “Return to a vehicle” button starts diagnostic entry with the se-
lected vehicle and vehicle project. You can also select an "Engineering" or
"Service" project when starting diagnostic entry. If you select the "Engineering"
or "Service" diagnostic entry, the "Determine VIN via VWVIN" step of the di-
agnostic entry will be initiated and the project assigned to the VIN will be
loaded.
In the case of DoIP communication via a VAS6154, the battery voltage/status,
the ignition status, the connection type and - in the case of a Wi-Fi connection -
the strength of the Wi-Fi connection with the VAS6154 are displayed.
Reconnecting
After the loss of a connection is detected by the ECF, a dialog with the follow-
ing options for selection is shown:
 Reestablish the connection (all results are kept)
 Connect to a different vehicle (same project)
 Go back to the home page (all previous results are discarded)
If the option "Back to start selection" is selected, the OK button is always active
regardless of the reconnection status. To end using one of the other two op-
tions, the reconnection must be successful.
3.4 Managing Vehicle IDs

During development and field testing, vehicles are not identified primarily
based on their VINs. There are internal vehicle numbers that are used to identi-
fy vehicles. By allocating VINS to a vehicle ID, they can be displayed and
changed in the application. To allow various users to use the same vehicle IDs,
lists with vehicle IDS can be made accessible on the network drives for the ap-
plication. Then, the known vehicle ID for all vehicles will be displayed in the
17
header and in the vehicle selection list. You can change the current vehicle ID
using a button in the header. You can enter a maximum of 20 characters in the
vehicle ID input field in the dialog that opens. If you edit a vehicle ID, it will be
entered immediately in the vehicle ID file. You can specify a path to the vehicle
ID file to be used in the Save locations tabs in the Vehicle ID section of the ad-
ministration area, so that it can be accessed and managed by all users. If no
vehicle ID can be found for a VIN using the vehicle ID file, a blank vehicle ID
will be displayed for this vehicle. The vehicle ID will be determined again if the
system detects that the diagnostic interface has changed. The vehicle ID is used
as an internal vehicle number in the VDS dialog for the equipment level docu-
mentation.
3.5 Diagnostic Interface Selection

The diagnostic interface selection in the ODIS tester applications is influenced
by the connection between the tester PC and the diagnostic interface. With
DoIP and the VAS6154, there is no longer exactly one diagnostic interface or
vehicle allocated to each tester PC using a direct connection. Rather, it must be
possible to select in the tester PC from a specified number of identical diagnos-
tic interfaces or vehicles. The diagnostic interface function allows a unique
identification and selection of a diagnostic interface.
Once you have pressed the "Diagnostic interface" button in the Configuration
area in the side bar without having a vehicle project loaded, the application
opens a modal dialog. It shows the currently selected diagnostic hardware type
(or "DoIP during DoIP diagnosis), the currently selected diagnostic hardware
serial number (or. "" during DoIP diagnosis) and, if available, the individual
diagnostic hardware ID. With a PassThru or Vector diagnostic interface, the
name is displayed if the diagnostic hardware ID is not available.
If the user has not specified a diagnostic interface instance, "Not specified" will
be displayed instead of the serial number and the diagnostic hardware ID.
The dialog offers the following options for selection:
 "Change VCI" (change VCI device)
 "VCI configuration" (activated only with diagnostic hardware type
VAS6154(A),
 "Detail" (display detailed VCI information)
 "OK" (close the dialog)
If you press the "Change VCI" button, the application unregisters the diagnostic
hardware, switches to a new dialog view after the user confirms the removal of
the current diagnostic hardware, and reads the list of all available diagnostic
interfaces. DoIP VCIs are excluded. Here, the user selects the desired instance
by pressing the "Select" button. The program then returns to the "Current diag-
nostic hardware" dialog and shows the new selection. If the selected diagnostic
18
interface has already been assigned by another tester, it will be indicated to

the user. With the "Update" button, the list of available diagnostic interfaces
will be read again.
If the "Details" button is pressed, the application checks the version information
for the selected diagnostic hardware. This information is then displayed in the
"VCI information" dialog. In the upper section of the window, the current to-
pology relating to the diagnostic tester and diagnostic interface is displayed. If
it is WLAN-INFRASTRUCTURE, the display also contains the line between the
diagnostic tester and access point. If a connecting path is covered by Wi-Fi, its
connection quality will be displayed. After pressing the "OK" button, the "Cur-
rent diagnostic hardware" dialog is active again.
When the "VCI configuration" button is pressed, the program checks the IP ad-
dress of the selected VAS6154(A) VCI and opens a user interface with a
browser frame where you can configure the selected VAS6154(A).
Pressing the "OK" button ends the function for configuring a diagnostic inter-
face.
A check will run when initiating the diagnostic entry to see if there is a connec-
tion to the currently selected diagnostic interface. It not, the user will receive an
error message. It will indicate that the diagnostic interface either cannot be ac-
cessed or it is incorrectly configured. When closing this message, the diagnostic
entry is canceled. The error message also has a “Diagnostic interface” button,
which, when pressed, opens the dialog “Current diagnostic hardware”. This en-
ables the user to configure an available diagnostic interface.
3.6 Vehicle Project Selection

The selectable projects are shown in a drop-down list. When the application
starts, either the vehicle project that was used the last time the program was
used or an automatic project start is preselected in the line that is always visible
in this list, depending on the project preference set for the control module list in
the Administration area function configuration. In the rest of the program se-
quence, the project selected by the user is in this line. You can select a new ve-
hicle project at any time during the program sequence. After performing a di-
agnostic entry, you must then respond to a modal confirmation dialog "Do you
want to change the vehicle project and perform a new diagnostic entry? If so,
all result pages will be closed.” Confirm with “Yes” (Question Mark Icon). The
default focus is on "No". If "Yes" is clicked, first all results views are closed and
then a new diagnostic entry is performed with the selected vehicle project. This
also happens if you select the project that was already used again (see chapter
2.4.1).
19
3.7 Project Entry Service Configuration

Using the "Service" entry, it should be possible to start a diagnostic entry that
uses only service specifications for DIDB MCD projects and VPT/VRT. This is to
ensure that GFF programs are run consistently with the applicable MCD data.
The application provides an entry in the project list called "Service" for this
purpose. The application resets the configuration of the VPT/VRT tables back to
the configuration set in Administration for service or TE data, including the path
for MCD projects, after unloading the diagnostic project.
In Administration, the application gives the user the option of either using ser-
vice MCD projects and service VPT/VRT on an ongoing basis, or using user-
specific MCD projects and user-specific VPT/VRT tables on an ongoing basis. In
Administration, the application still gives the option to specify the path to the
user-specific MCD projects as well as the path to a user-specific VPT/VRT con-
figuration. The projects that match the user configuration set in Administration
are displayed in the project selection list. If you close the MCD project after a
"Service" diagnostic entry, the application will again display projects in the
project list that match the application configuration.
In Administration, the application displays the inactive path to the service-
specific DIDB for information purposes. The application provides an Admin-
istration setting (in the Diagnostic data area on the Connections tab) for a path
to DIDB with user-specific content. The application displays the Administration
setting for the path to the DIDB with user-specific content with the message
"Only for test purposes - no online content update". If the project entry in ODIS
Engineering occurs in the "Service" mode, the application uses the service-
specific DIDB in further use of the program. If the project entry in ODIS Engi-
neering does not occur in the "Service" mode and you have entered a path to
a DIDB in Administration, the application will use the user-specific DIDB in fur-
ther use of the program.
3.8 Automatic Diagnostic Entry Using the VIN

In this variant, the application attempts to determine the vehicle project that is
most suitable based on the VIN read form the connected vehicle. If you select
"Service" or "Engineering", the system then tries to read this from the connect-
ed vehicle. If the reading out fails or an invalid VIN is detected, all available
vehicle projects are shown in the dialog box described below (depending on if
the Service or Engineering mode is selected). If a VIN could be detected, the
program first searches in a table stored locally for an allocation of this VIN to
a vehicle project. If there is such an allocation, the corresponding project is se-
lected. If there is no allocation available or there is no local table, the VRT/VPT
mechanism will make a selection. If multiple applicable vehicle projects are
found, they will be shown in a drop-down list for selection. This list is displayed
in a modal dialog box. After confirming with "OK", the project specified by the
20
user is selected. Diagnostic entry ends if you click "Cancel". The selected vehi-
cle project is then copied into the local allocation table. If one does not exist,
one will be created in this location.
3.9 Diagnostic entry with manual VIN selection

Manual VIN selection can be added to a "standard" diagnostic entry using an
Administration setting. This option detects all VINs contain in a vehicle during
diagnostic entry. If the detected VINs differ from one another, a selection dia-
log for specifying the VIN to use will appear.
The Administration setting for activating manual VIN selection is located on the
"Function configuration" Administration tab in the "Diagnostic entry" area.
3.10 Communication Path Specification

Certain communication paths can be specified for performing diagnostic entry.
These include:
 Automatic detection
 Only allow CAN communication
 Only allow CAN-FD communication
 Only allow DoIP communication
 Selection by user in diagnostic entry
The setting is selected using a drop-down list in Administration in the Diagnostic
communication area of the Function configuration tab.
The communication path configuration only affects diagnostic entry in terms of
project selection and GFF (expanded side bar).
"Automatic detection" establishes CAN communication to the vehicle. The sys-
tem then determines if the vehicle is DoIP, CAN-FD or CAN-capable or not. It is
determined by the supported VCI communication paths, the VI suffix from
VRT/VPT and by the VEHICLE-INFO in the MCD project and diagnostic log in-
formation from the Gateway components list. If all of the requirements for DoIP
support are met, the diagnostic entry is performed via the DoIP communication
path. If not, the CAN-FD support is checked and used if necessary. If neither of
the two communication paths are supported, diagnosis will continue via CAN.
Diagnostic entry will end if there is an error.
With "Only allow CAN communication", the system will try to establish a CAN
communication connection to the vehicle. If there is an error, diagnostic entry
will end and an error message will display.
With "Only allow CAN-FD communication", the system will try to establish a
CAN-FD communication connection to the vehicle. If there is an error, diagnos-
tic entry will end and an error message will display.
21
With "Only allow DoIP communication", the system will try to establish a DoIP
communication connection to the vehicle. If there is an error, diagnostic entry
will end and an error message will display.
With “User selection during diagnostic entry”, all vehicles from the selected ve-
hicle project are displayed for selection after determining the VIN. After the
user selection, the diagnostic entry continues with the selected vehicle. If the
project only contains one vehicle, the selection dialog is skipped. If there is an
error, diagnostic entry will end and an error message will display.
3.11 Diagnostic Entry Configuration

In Administration, you have the option to configure diagnostic entry in the "Di-
agnostic entry" area of the "Function configuration" tab. You can specify which
vehicle data should be detected during diagnostic entry. The following vehicle
data is available:
 Gateway/bus master components list
 Vehicle identification number
 Central elimination counter
 Last deletion date of the functional DTC memory
 Trip odometer
 Mileage
 Time
If no vehicle data should be read, you can make this configuration using the
"Deactivate reading vehicle data" checkbox.
Regardless of the setting for reading the "Gateway/bus master components
list), all control modules that potentially contain a components list are deter-
mined in order to provide a complete evaluation of the components lists.
3.12 Unloading a Project

If you click the "End diagnosis" button (eject symbol), the application returns to
the start status so that all results tabs are closed and no project is loaded. The
application will display a confirmation dialog for this. The option "Yes - un-
load" is selected by default. If the project currently used was loaded from the
vehicle list, the vehicle list will display again after the project closes. If the vehi-
cle list is displayed after the projects closes, it will be updated one time. The
same vehicle that was used for the diagnostic session will be selected in the list.
3.13 Evaluating Components List(s)

Once the application has created a control module list based on the selected
vehicle project, the bus master components list(s) is/are evaluated. This step is
skipped if you deselect the evaluation of the components list(s) in the "Admin-
istration" view (checkbox in the Diagnostic entry area of the Function configu-
22
ration). The result is that all control modules from the vehicle are organized in a
list with only one hierarchy level - meaning, a flat list. Component list infor-
mation is not included in the data structure. If the evaluation of components
lists is selected, the bus master installed in the vehicle is determined. There are
three possibilities:
 Only one bus master is found
 Only one central bus master is found
 Multiple bus masters with components lists are found
In the first case, you can proceed as described for the situation where the eval-
uation of components list(s) was deselected.
The second case generally occurs with KWP2000 gateways. It can also occur
with UDS systems.
In the third case, multiple control modules respond to the query. The compo-
nents lists for all bus masters that are found are read out and the information
contained there is entered in the central control module list.
3.14 Battery Voltage Monitoring

The battery voltage is automatically monitored while a diagnostic session is in
progress. If the battery voltage is under 12 volts or it is starting to go below 12
volts, then a corresponding dialog window is displayed. This must be closed by
the user. The dialog window is only displayed a maximum of one time per di-
agnostic session. The display can be deactivated via the administration setting
“Function configuration → Diagnostic entry → Warning for too low of battery
voltage”.
Regardless of the administration setting, the voltage value at the beginning of
the diagnostic session will be kept in the results log. The log of going over or
below the 12 volt threshold is also carried out during a diagnostic session.
Note: the display and monitoring of the battery voltage is only possible if a
VCI that supports this is selected. For example, the “VAS 6154” and “VAS
6154A” VCIs provide the necessary data, but the “VAS 5054” VCI does not.
4 Control Module List View

As a result, the diagnostic entry delivers a hierarchical list of control modules in
the connected vehicle. The appearance may differ depending on the results of
the diagnostic entry:
 There is no gateway/bus master installed in the vehicle or you have de-
selected evaluation of components list(s) in the Administration area
(Function configuration).
23
 The vehicle has a central gateway and multiple subordinate bus masters
that are linked together in a tree structure by their components lists.
 The vehicle has exactly one central gateway. This applies to KWPxxxx
and vehicle with a mixture of KWP/UDS.
After diagnostic entry, the control module list is first structured and filled with
information determined during diagnostic entry. In the first case, there will be a
"flat" list, and in the second and third cases, there will be a "tree" list whose
nodes represent each bus master. The control modules allocated to a bus mas-
ter are shown one level down in the tree structure.
The control module list contains the following columns:
 System (address, system)
 GW info (bus identifier, protocol combination)
 SB (sleep bit)
 DTC (fault, fault number)
 TP selection (transport protocol selection, selected in the Control module list
area of the Function configuration in the Admin area)
 Connection (connection status)
Displaying Sub-Systems of Diagnostic Classes 1 and 2

The information about possible sub-systems of diagnostic classes 1 and 2 is
determined when the diagnostic function for the main control module is select-
ed. Once identification data from a sub-system in diagnostic class 1 or 2 is de-
termined using the "Identification" or "Coding" diagnostic functions on the
main control module, this information will be shown in the expanded display.
The columns for DTC memories and "TP selection" will remain empty because
this information is not available with these systems. The reloading of these sys-
tems described in this chapter can be activated or deactivated in Administra-
tion (checkbox in the Control module list area of the Function configuration).
The default setting is "activated". Reading identification data from a sub-system
in diagnostic class 1 or 2 can result in a longer response time.
Software Cluster Display

If a bus master supports the software clusters, they will be detected when the
components list is read out and displayed in the control module list. These soft-
ware clusters will be listed directly below their master control module together
with the sub-systems and sorted according to control module address. This is
followed by the control modules from the detected components list. The soft-
ware cluster entries do not have any information about the bus identifier, which
is why the “GW Info” column is empty. When the components list detection is
deactivated, the software clusters are detected the way the sub-systems are,
24
either the first time a diagnostic function is called up for the main control mod-
ule, or when the sub-systems are reloaded.
There is no control module address available for a software cluster, the “Func-
tion ID” will be displayed in square brackets as the address.
Sorting the Control Module List

The control module list can be sorted in ascending and descending order
based on all columns (the exception is a tree view, because it is not part of the
table). The sorting will take place within a level of the hierarchy. The sorting is
indicated in the column heading. Initially, information within the hierarchy level
based on the control module address (numerical). The control modules are also
sorted numerically in the flat list display. Control modules that appear in the
gateway components list multiple times are also shown multiple times in the
control module list (and also in the bus master coding list). In other views where
control modules are listed, there is only one entry per control module.
4.1 Control Module List Columns

Tree View
If there is a hierarchical control module list, the tree structure will be displayed
here. The controls for expanding or collapsing hierarchy levels are located
here. By default, all hierarchy levels with control modules in diagnostic classes
3 and 4 are expanded. Known systems in diagnostic class 4 are displayed as
nodes in the tree structure. In the case of a "flat" list, the tree consists of only
one hierarchy level that is always expanded.
Address - System
This column generally contains the control module address of the affected con-
trol module and after that, the system name separated with a "-" and addition-
al information. If the control module address is not available, the nodes or the
LIN address may be shown if applicable. Node addresses are displayed in
brackets to differentiate them from control module addresses. If there is no ad-
dress for a sub-system, the cell for the corresponding control module will re-
main blank. If no control module address is known for a control module, "????"
is displayed. Control module addresses are always display in 4-digit format,
with zeros added to the beginning if necessary.
Initially, only the system ID is added after the hyphen. Additional identification
information is entered here after the first time the identification data for the af-
fected control module is accessed. The installation status of the affected control
module is added to the system ID if it differs from the coding in the components
list (VBL) for the associated gateway. The following text is displayed there in
red:
25
Not coded => accessible

If the control module is coded as not installed in the associated bus master, but
is detected as a current/optional installation and/or can be reached,
Coded => not detected
If the control module is coded as installed in the associated bus master, but the
bus master does not detect that it is installed.
Coded => communication faulty
If the control module is coded and detected in the associated bus master, but
cannot be reached by the application.
Warranty Info
The bus identifier and/or the protocol combination used for the affected con-
trol module is displayed in this column, if available.
Sleep Icon
If the sleep bit is set, an icon indicating this is displayed in the "SB" column.
DTC
This column is initially populated with information from the service bit for the
respective control module from the components list for the applicable bus mas-
ter. Once the control module is read as part of the diagnostic function for the
DTC memory, the number of faults in this control module is entered in the ap-
plicable cell. If a partial tree is collapsed under a bus master, a "lightning bolt"
symbol will be shown in this location in its entry if there is a fault in one of the
control modules that is not visible.
TB Selection
This column contains a drop-down list for each control module with protocol
combinations determined based on that data that you can select. The selected
protocol is used for communication with the control module. In addition to ex-
plicit protocol data, the list also contains a blank entry for an automatic selec-
tion that is preselected by default. The display of this column can be activated
or deactivated in the Control module list section of the function configuration in
the Administration area.
Connection
An icon in this column indicates the status of the connection with the control
module.
26
4.2 Control Module List Update Cycles

The dynamic content of the control module list is updated in cycles when the
"Control module list" view is active. You can activate or deactivate this update
in the "Administration" view (“Control module list” area in the “Cycle times”
section of the function configuration) (default: "deactivated"). You can also
specify the duration of the refresh interval, between 0 and 99999 milliseconds.
4.3 Selecting Control Modules in the Control Module List

After the initial structuring of the control module list, the control module in the
top line is selected. You can select a different control module in three different
ways:
 by single-clicking with the mouse
 by highlighting lines using the "down arrow" and "up arrow" cursor buttons
 by entering the control module address directly
4.4 Selecting Diagnostic Functions for a Control Module

Once a control module is selected in the control module list, the functions that it
supports are determined. This is not possible with control modules with the
KWP1281 diagnostic protocol, so all functions supported by this protocol are
always displayed here, even if the selected control module only supports some
of them.
The functions that are determined are listed in a Function navigator that is lo-
cated to the right of the control module list under the Diagnostic functions
heading. Restrictions for the functions that are displayed can be activated in
Administration (checkbox in the Control module list section of the Function con-
figuration) so that only available diagnostic functions will be displayed. The
diagnostic functions are listed hierarchically. If applicable, additional sub-items
under a main item can be expanded so that specific variations of the diagnos-
tic function can be selected. The entries for each diagnostic function are de-
scribed in the corresponding chapter. If an item is selected in the function navi-
gator by clicking on it with the mouse, the associated diagnostic function can
be started by pressing the "Enter" button on the keyboard. It can also be start-
ed by double-clicking on the item.
When selecting a main entry, the function associated with the sub-item that is
listed first is usually activated. If the input focus is still in the control module list,
you can switch to the function navigator using the space bar or by pressing the
"Tab" button multiple times. It is also possible to select items in the function
navigator using the "up arrow" and "down arrow" cursor buttons, as long as
the function navigator is focused.
Diagnostic function
27
001 – Identification
002 – DTC memory
 002.01 Read
 002.02 Delete
 002.03 active error
 002.04 Unchecked error paths
 002.05 All error paths
 002.06 DTC snapshots
003 – Measured values
004 – Output diagnostic test mode
005 – Basic setting

 005.01 Basic setting
 005.02 Short routines
006 – Coding
 006.01 Plain text coding
 006.02 Binary coding
 006.03 Code bus master
007 – Adaptation
008 - Access authorization
009 – Diagnostic session
010 – Data transfer
 010.01 Write data set
28
 010.02 Memory cells
011 – Special functions
 011.01 Hex service
 011.02 Baud rate
 011.03 Stop communication
 011.05 Data upload
4.5 Accessing Vehicle Functions

The functions that can affect more than one control module are grouped to-
gether in the function navigator under the heading Vehicle functions.
Vehicle function
040 - OBD service
041 – Engine group
042 – Flashing
045 – Transport mode
 045.01 Activate
 045.02 Deactivate
046 – Vehicle special functions
 046.01 Coding/adaptation
 046.02 Code components list
 046.04 Stop communication

 046.05 Lock vehicle
047 - Reading out complete system
 047.01 Read
29
 047.02 Erase & read
 047.03 Erase & read service bits
The items for each vehicle function are described in the corresponding chapter.
4.6 Accessing Special Functions

Guided Functions (060 - GFF / GFS) and the macros (061 - Macros) can be
run using the menu items in the "Special functions" area of the function naviga-
tor.
4.7 Deactivating Unused Functions

You can activate or deactivate individual diagnostic, vehicle, or special func-
tions in the Administration area under the "Personalize" section of the "Gen-
eral" tab.
5 Identification
If you select a control module in the control module list and activate the "001 -
Identification" diagnostic function in the function navigator, a results view
opens with the identification data that was read out. The tab in this view has a
label that consists of the control module address and the suffix ID, for "Identifi-
cation".
The identification information is shown in two tables. The upper table shows the
system identification, parts number, and the software and hardware versions.
The information for the master control module that is being addressed is shown
in the top line of this table. In the lines that follow, if available, the associated
slave control modules and software clusters are listed. The slave systems are
diagnosed via the master and the cluster via an independent connection.
The entry must be marked in the upper table for additional identification char-
acteristics. In the lower table, the user can switch between standard identifica-
tion characteristics and the expanded identification characteristics for the sys-
tems selected above. The variable "Show standard identification" or "Show ex-
panded identification" button is used for this. The standard identification is dis-
played automatically after selecting an entry in the upper table. The "Update"
button can be used to update the data that is displayed at any time, regardless
of the selected view. In the expanded view, the attributes are shown in a hier-
archy structure, if applicable, and are generally collapsed.
The expanded identification is not available for KWP1281 control modules.
The maintenance history data in the control module can also be erased on con-
trol modules with KWP2000 light plus and Service 0x22. An “Erase mainte-
30
nance history data” button is displayed for this purpose. It is only visible and
active for the affected control modules when the expanded identification is dis-
played.
The workshop code in the lower table can be displayed in two ways. If it is an
ODIS workshop code, the code converted by the ECF will be displayed and the
HEX value will be added in brackets. With a VAS workshop code, only the
converted code is shown.
6 DTC memory
After selecting a control module in the control module list and opening the
"002 - DTC memory" item in the function navigator for the "Control modules"
view, a view opens for displaying the DTC memory contents for the selected
control module. This view has the tab "<Control module address>-DTC". The
contents of the DTC memory that was read are displayed in tables arranged
one above the other. The upper table lists all of the results read from the se-
lected control module. The fault code, the SAE code, the description of the DTC
memory entry, and additional status information, if applicable, are displayed
there.
Clicking on the fault line displays the environmental conditions in the lower ta-
ble. This includes additional information about the selected entry, such as mile-
age, priority, date, frequency, or fault status. The amount and type of this in-
formation may differ from one control module to another. The left column of
the table contains the type/name of the information and the right column con-
tains the value that was read. There may be a ">" in front of the name. This
indicates that there is detailed information about a group that can be expand-
ed or collapsed by clicking on the ">" symbol.
For UDS control modules when the option "Display status bits" is selected, an
additional table with status information about the results status is displayed to
the right of the environmental conditions table.
In the "Update" area, you can have the DTC memory read again by clicking
the "Now" button. Checking off the "Cyclical" checkbox causes the DTC
memory to be read in cycles. The cycle time can be configured in the Admin-
istration area/Cycle times under the "Function configuration" tab. In the "Sort"
area, you can select criteria for sorting the DTC memory entries in the upper
table. The sorting is ascending based on the time when the fault occurred.
Clicking the "Erase DTC memory" button erases the content of the DTC memory
for the selected control module. This button is only active when physical dele-
tion is possible. Clicking the "OBD - Delete" button erases the content of the
DTC memory for all OBD control modules. This button is only active for UDS
control modules if the physical service for deleting the DTC memory for the ver-
sion used is not populated with data.
31
Depending on the ODX data, additional information about a fault may be ac-
cessed for UDS control modules using the Special Data Groups (SDG). If a spe-
cific fault is selected in the upper table in the view, the "DTC info" button can
be used to open a dialog where the additional information is displayed in a
table. The left column of the two-column table contains the name of the infor-
mation and the right column contains the value.
With UDS control modules, you can select from the functions "Read DTC
memory" (item: DTC memory), "Read list of all fault paths that have not been
checked" (unchecked fault paths), and "Read list of all active faults" (active
faults) in a drop-down list in the "filter templates" area. The drop-down list also
contains three items that address templates that can be configured by the user.
These can be set in the Administration area ("DTC memory" area of the func-
tion configuration). The DTC table updates automatically after a function is se-
lected.
For UDS control modules with the supported "developer DTC memory" func-
tion, the identification and display of the developer DTC memory can be acti-
vated via a radio button. Depending on the button selection, the displayed DTC
memory list contains either only the conventional memories or only the devel-
oper DTC memories. When the developer DTC memory is activated, then every
read and deletion process takes place within this OBD function with the select-
ed filter screen and the selected memory areas. For this, individual memory ar-
eas or all memory area can be selected in the displayed selection list using the
"Display all" checkbox.
When the conventional DTC memory is activated and the "Snapshots" function
is supported, the display of snapshots can be activated via the "Read DTC
snapshots" button. Snapshots are displayed in the environmental data table
under the environmental data and the measured values in the respective col-
umns. The displayed snapshots can be exported in XML format using the "Ex-
port DTC snapshots" button. The location of the exported file can be changed
in Administration/Save locations/DTC memory.
For UDS control modules, columns with the individual status bits can be added
to the upper table by activating the checkbox "Show status bits".
Displaying the Diagnostic Status for All Fault Paths (KWP)

The function "Read diagnostic status for all fault paths" is shown in all views for
KWP control modules. The top element in the DTC memory functions in the
function selection tree view is named "DTC memory", and clicking it will have
the DTC memory read. Below the "DTC memory" element are the functions
"002.02 Read" and "002.03 - all fault paths" (for "Read diagnostic status for
all fault paths"). Double-clicking the left mouse button or pressing the Return
button after selected the element in the tree view will perform this function. The
function selection tree view is shown collapsed by default. The selection be-
32
tween the functions "Read DTC memory" and "Read diagnostic status for all
fault paths" can be made in the results view function navigation using a combo
box with the content "DTC memory" and "all paths". This combo box displays
the function selection from the control module list when the "DTC memory" re-
sults view is opened. The DTC table updates automatically after a function is
selected.
7 Measured Values
After selecting a control module in the control module list and opening the
function "003 - Measured values" in the function navigator in the "Control
module list" view, a new results view is created. Its tabs are named "MW<1-
9>" because up to nine measured value views can be created in this way. The
"Measured values" tab has two sequential views. One is for configuring the
measured values to be displayed or record (measured value selection), and
one is to display the measured values that are read (measured value display).
Measured values for multiple control modules can be selected or displayed
together both in the measured value selection and the measured value display.
7.1 Measured Values Selection View

There is a drop-down list in the upper left of this view where you can select a
control module whose measured values can be added for selection. The con-
figuration of the measured values to be displayed differs depending on wheth-
er the measured values were read out from control modules with KWP protocol
or from control modules with UDS protocol. The configuration view is adapted
depending on the control module that was selected in the drop-down list.
7.1.1 Control Modules with KWP Protocol
Measured value blocks with up to four measured values are read for control
modules with KWP protocol. The measured value block numbers are entered in
the "MVB.Position" input field (1 through 255 for KWP 1281, or 1 through 254
for KWP 2000) along with the measured value position within the associated
measured value block separated with a period, if applicable. The input tem-
plates for the measured value block give the option of selecting multiple meas-
ured value blocks and an entire measured value block range with a single in-
put. Measured value block ranges are entered in the format "<Start measured
value block>-<End measured value block>". Individual measured values can-
not be entered. Multiple individual measured values, measured value blocks,
and measured value block ranges can be entered in the input field for meas-
ured value blocks, separated by commas. Blank spaces are ignored. A shared
name can be specified in the "Measured value identifier" text input field for the
measured values that are defied in the "MVB.Position" field.
Example:
33
MVB.Position: 3, 4, 5.1, 7-10 Measured value name: text

Measured values entered multiple times (for example, if there are overlapping
ranges) are only included in the measured value selection once. Invalid entries
(for example, start block < end block, position > 4, or measured value block >
255) are ignored. If you have also entered a measured value name, the appli-
cation will use the name for all measured value blocks that are entered and will
add it to the measured value number.
The "Accept" button is active after making a correct entry. Clicking "Accept"
transfers the input into the right table where the selected measured values are
located. If only one block number is entered, all measured values in this block
will be shown as selected when the "Accept" button is clicked.
After copying one or more measured value blocks into the selection, the but-
tons for moving the selected measured values will become active. If selected
individual blocks are not displayed, they can be moved into the left table by
clicking the "<" button. All measured value blocks located there will not be dis-
played. The "<" button is always active when at least one measured value
block in the right table is selected. Measured value blocks from the left table
can be moved to the right table by clicking the ">" button. The button is always
active when at least one measured value block in the left table is selected. All
measured value blocks can be moved at once using the ">>" or "<<" buttons.
Measured value blocks highlighted in the right table while pressing and hold-
ing the CTRL button can be moved up or down using the "▲"or "▼" buttons in
order to put the selected measured value blocks into the desired order. The
buttons for moving the selected measured values are used the same way with
UDS control modules once the measured value name is selected as described
above.
7.1.2 Control Modules with UDS Protocol
Control modules with UDS protocol do not use any measured value blocks.
Measured values that are available for the selected control module are read
from the Offboard Diagnostic Information System Engineering internal data-
base and their names are displayed in the table on the left. The names dis-
played in the table on the left can stand for a measured value group whose
measured values can be selected or deselected together as a group. You can
use a filter function that filters the measured value selection list based on se-
quences of characters in order to select measured values (see the chapter
2.5.2). You can also specifically reduce the list of selectable measured values in
the combo box by selecting a specific grouping that is part of the database.
The buttons for moving blocks become active by clicking on the desired meas-
ured value name in the left table. The measured value names are added to or
removed from the list on the right using the move buttons, as described above
for KWP control modules.
34
If a user would like to reuse a measured value selection later, it can be stored
in a preset and reused, regardless of the control module protocol definition
(see chapter 2.7).
Clicking the "Continue" button displays the measured values for the measured
value blocks in the right table in the results view.
7.2 Measured Values Display View

After switching to the "Show measured values" view, the current measured val-
ues are read and displayed in a table. The measured value names and the
RDIS are listed in the left columns in the table, and the value and unit are
shown in the other columns. The far right column in this table contains the con-
trol module address for the associated control module. Measured values from
MUX data (mixed measured values) may also contain additional numerical in-
terpretations. They are hidden in the measured values display by default. This
setting can be changed in the Administration/Function configuration area.
The measured values update can be controlled using the controls in the "Up-
date" area. The default setting is updating the measured values in cycles as
quickly as possible. You can specify the desired update interval in seconds in
the Administration area (“Cycle times” view in the function configuration area).
The update cycle can be switched off and on by deactivating/activating the
"cycle" checkbox. When it is not selected, you can update the measured values
as desired using the "Now" button.
Another column in the measured value table (to the left of the control module
address) contains a checkbox that allows you to exclude one or more meas-
ured values from the update. With UDS, the application provides a checkbox
for the upper grouping element (for example "Basic setting status"). With KPW,
each set of blocks has a checkbox. The checkboxes are activated by default. If
you return to the measured value selection and adds additional measured val-
ues in the view, the diagnostic system keeps the status that was set for the
available checkboxes and adds the new measured values with active check-
boxes.
Using the buttons in the "Record" area, the measured values that are read can
be recorded in a file in table format. The directory for saving the results files
can be specified in the Administration area ("Measured value logs" area in the
"Save locations" tab). The file name is created by the application based on the
vehicle name, the date, and the time (mwlog_<VIN>_<Date>T<Time>).
Pressing the "●" (start) button begins or resumes the recording of the measured
value reading. The “▌▌" (pause) button interrupts the measured value record-
ing. It can be resumed with the "●" button. The measured values are then added
to the file that was previously used.
35
Pressing the “■" (stop) button ends the recording and closes the results file. Ac-
tivating recording again using the “●" button starts recording in a new file.
Leaving the results view (returning to the measured value configuration or clos-
ing the tab) ends the recording and closes the results file. Switching to another
tab pauses the recording. Recording resumes when you switch back to the
measured values view.
Measured values for UDS control modules can be arranged in groups in the
measured values view. When this happens, a ">" is added to the beginning of
the group name and the right column will be empty. Clicking ">" opens the
group and displays the measured values. Clicking on the ">" that is now in
front of the group will hide the group again.
The "Back" button returns to the first view in the measured value selection and
you can change the selection of measured values to be displayed.
8 Coding
If you select a control module in the control module list view and open the func-
tion "006 - Coding", a results view opens, whose tab name consists of the con-
trol module address (such as 01) and the suffix "COD" for "Coding". If a Cod-
ing tab is already open for a control module and the function is selected again,
the tab that is already open will be displayed. The configuration and operation
differ depending on whether the coding will be performed with KWP or UDS
control modules.
In both cases, the system first checks if the control module that should be coded
has sub-systems, meaning secondary control modules assigned to this control
module. If this is the case, all systems for the sub-bus will be included in a drop-
down list for selected in the Results view. The drop-down list contains the system
names for all systems in this sub-bus. The master control module is selected
first. You can use the drop-down list to select another sub-system, whose proto-
col-specific coding value will be displayed.
A label with the identification data for the master control module is displayed
above the drop-down list. The coding value for the master control module is
read and displayed immediately upon opening the view. The other displays
and input options may vary depending on the diagnostic protocol and the se-
lected coding type.
8.1 Control Modules with KWP Protocol

The following information explains the Coding function for KWP control mod-
ules. There are two possible code types for these control modules: short coding
and long coding. The code type depends on the control module and cannot be
influenced by the user.
36
8.1.1 Short Coding (KWP 1281, KWP 2000)

After opening the view or selecting the desired sub-system, the coding is read
and displayed in a text field. A new code value can be entered in an editing
field. Pressing the "Accept" button writes the code value in the vehicle system.
There is a security prompt first. Then the written value is read back and dis-
played in the field for the old code value, followed by the original value in pa-
rentheses:
2815 (2842)
The modification and writing process can be repeated if desired. The "Restore"
button displays the value before the last writing process in the input field so
that can be reset using the "Accept" button.
8.1.2 Long Coding (KWP 2000)
The long coding is bit field that contains up to 32 bytes. It can be displayed in
bits or as a byte sequence. The code is displayed in the same way as binary
coding for UDS.
8.2 Control Modules with UDS Protocol

UDS control modules have binary coding and plain text coding. These are dif-
ferent ways of displaying the same type of code. As long as the data supports
it, plain text coding is displayed by default after accessing the coding function
and, if necessary, after selecting the sub-system. Otherwise, binary coding is
displayed.
8.2.1 UDS Binary Coding and KWP Long Coding
The binary coding display for UDS control modules and the long code for KWP
control modules are identical. The following description is based on binary
coding but it still applies to long coding.
In the binary view, the code string is displayed with one byte per line in a table
that cannot be sorted. The table columns contain the byte number, the value in
hexadecimal formate, and the value in binary format. For each display type,
the table contains one column each for the current value and the input. You
can make coding entries directly in the coding table. The application shows the
option for input using a cursor. You can move the cursor as desired within the
table using the "Up arrow", "Down arrow", "Right arrow", and "Left arrow"
buttons. Input is only possible in the "Hex input" and "Binary input" columns.
Only hex value data can be entered in the "Hex input" column, and only bina-
ry value data can be entered in the "Binary input" column. If you press the "En-
ter" button, the application copies the input into the table input columns. The
application performs the actual coding only after the "Accept" button is
pressed. After selecting another (sub-)system using the "System ID" combo box,
the input focus switches to the first line in the associated coding table.
37
If the view is used for long coding on a KWP2000 control module, you can se-
lect the blank line after the last filled coding line and add a new coding byte
there using the "Add byte" button. This process can be repeated as often as
desired. The application fills the columns for the current value in the coding
lines that are added with 0. A selected coding line can also be removed here
using the "Remove byte" button. After removing, the application renumbers the
remaining line in the "Byte no." column.
If necessary, you must enter a sequence of numbers that corresponds to the
coding string in the "Check digit" input field below the table. If there is no
check digit, a warning message appears when saving:
"The coding string could not be checked for errors. Do you want to save any-
way?"
Checking using a check digit can be activated in the Administration (checkbox
in the Coding area of the Function configuration). The default setting is: check-
ing is inactive. If the check is deactivated in Administration, the input field for
the check digit is shown as inactive. If this is the case, there is not message that
the check digit was not used for checking. A check digit is not needed for
changes in the plain text view, because only valid values can be entered here.
In both views, a coding value is selected by clicking on the corresponding line
in the table and the coding string is accepted for the control module after click-
ing the "Accept" button and confirming a security prompt. The status from be-
fore the last writing process is restored in the input line using the "Restore" but-
ton. You can switch to the plain text coding view using the "Plain text" button, if
this view is supported.
8.2.2 UDS Plain Text Coding
In the plain text view, a table in the left section of the view is filled with availa-
ble coding strings. The table contains the columns "Parameter name", "Current
value", and "Input". If one of these coding strings is selected, it will be read,
decoded, and displayed in a table with the name and value of the individual
parameters of which it consists. The lines in the input column are formatted as
drop-down lists when there are numbered parameters. You can make changes
by selecting a value in the list. With other data types, the value in the "Input"
column can be edited. You can switch to the binary coding view using the "Bi-
nary coding" button. If plain text coding is not supported, binary view is select-
ed automatically.
This view uses the general filter function for filtering table content to select the
coding property (see chapter 2.5.2). Filter values that are entered are automat-
ically deleted when a preset is loaded. If coding becomes visible again be-
cause a filter is changed, input values entered previously are displayed again.
If coding must be performed (the "Accept" button is clicked), a checkbox with
the text "Perform control module reset" is displayed in a confirmation dialog.
38
With plain text coding, the checkbox is activated and selected by default (con-
trol module reset is performed) if the ODX data supports the ECU reset service.
Otherwise, the checkbox is deactivated. The "Restore" button restores the status
from before the last writing procedure in the input column. The "Accept" and
"Restore" buttons only have an effect on visible coding. For all values that are
not visible, the value that was previously read is written in the control module.
If the setting "Only show service-related coding texts" is selected under "Cod-
ing" in the "Function configuration" tab of the Admin area, then values that are
populated with the wording "NOT_VISIBLE_IN_SERVICE" are hidden in the
plain text coding.
You can switch to the binary coding view using the "Binary coding" button, if
this view is supported.
8.3 Saving Coding as a Preset

The "Preset..." function (see chapter 2.7) is available in all views for KWP and
UDS coding. This function can be used to save the current coding, which saves
the plain text and binary coding in parallel. When a stored coding is selected
using "Preset..." or using the "Restore coding" button, its content is entered into
the "Input" columns or into the input field for short coding and is written only
after the "Accept" button is pressed. A plausibility test for the preset that is cur-
rently loaded is performed to confirm if the data contain contains the current
available coding type. If the plausibility test fails, you are informed in a dialog
that the preset data does not match the current control module.
8.4 “Special Coding" for KWP Gateways

The "Special coding" function is offered only for gateway control modules, de-
pending on the display type selected for supported functions in the Administra-
tion. The special coding currently stored in the control module is detected when
the components list is read and is displayed as an additional line at the end of
the components list.
9 Adaptation
To perform the adaptation function for the control module that is activated in
the control module list, the entry "007 - Adaptation" must first be selected in
the function navigator of the "Control module list" view for the selected control
module. The display opens in a new results view whose tabs are named ac-
cording to the control module address (for example, 01) plus the suffix "ANP".
The configuration and operation differ depending on whether the adaptation
will be performed with KWP or UDS control modules.
39

Channel Selection
To change the adaptation value for a channel, you must first set it in an input
field and then click the "Select channel" button to select.
Decimal numbers in the range of 0 to 255 are valid for the channel number.
The button for selecting the channel remains deactivated until you have en-
tered a valid channel number. If you have not entered a valid channel number,
then the background of the channel editing field is red to indicate that a pa-
rameter must be entered here.
The current channel value is also displayed as an output in the results view. In
parallel to this, it is copied into the test value output field and displayed as an
input value in the editable input field.
Setting the Input Value

The adaptation value can be changed in the "Input" field. It is initially the same
as the value in the "Test value" output field. If you change the value and con-
firm the change by pressing the "Send test value" button or with the "Enter"
button, the value will be sent to the control module as a new test value and
used temporarily. This process can be repeated as often as desired.
As long as the changed value has not been saved in the control module yet,
you can click the "Reset" button to reset the test value back to the initial value
(which is the value in the "Actual value" column). The test value is also reset
when a new channel is selected or when changing or closing the results view. If
the correct test value was determined, clicking the "Accept" button will save it
in the control module. Only then is the value in the "Actual value" output field
set to the new value. After saving, the "Reset" button is deactivated. However,
both buttons are deactivated when the value in the "Input" field is identical to
the "Old value/Default value" field. You can reset the values of all channels to
the control module factory settings by pressing the "Reset all" button.
Preset Functionality
If a user would like to reuse a parameter selection later, it can be stored in a
preset, regardless of the control module protocol definition (see chapter 2.7).

In contrast to KWP control modules, UDS control modules do not recognize any
numbered adaptation channels, but rather recognize adaptations by name.
When switching to the "Adaptation" view, all available adaptations for the se-
lected control module are listed in a table. Each of these adaptations has a pa-
rameter. They are hidden by default and you can click in the line or click the >
40
in front of the function name to display them. Clicking again or clicking on ">"
hides the parameter list again. To show the parameters for all adaptations at
once, click the "+" button at the bottom right of the table. Clicking "-" will then
close all of the open parameter lists at once. All values that have not been
saved or lost when parameter lists are closed.
You can use a filter function that filters the adaptation selection list based on
sequences of characters (see the chapter 2.5.2). In contrast to the standard fil-
ter behavior, the filter in the adaptation evaluates all fields in the table. It is
also applies to all visible lines. To find all entries that match the selected filter
value, you must also make all entries in the tree visible using the + button be-
fore entering the filter value. A tool tip will refer to the filter.
You can also specifically reduce the list of selectable adaptations in the combo
box by selecting a specific grouping that is part of the database.
In addition to the columns for adaptation/parameter and RDID, that able in the
results tab also contains columns with the current values, editable input values,
and the corresponding units. By clicking a field with input values, these values
can be set (by entering values directly or using a drop-down menu). Pressing
the "Accept" button copies the entered values into the control module. Before
saving, a validity check is performed on the parameter values that were en-
tered as free text. If this check is not successful, the values will not be written
into the control module and you will be informed about the cause in an error
message. If the new values were saved successfully, they will then be displayed
in the "Current value" column. To restore the last saved values, press the "Re-
store" button. The last values that were used are displayed in the "Input" col-
umn. To program the restored values into the control module, click the "Accept"
button.
If a user would like to reuse a parameter selection later, it can be stored in a
preset, regardless of the control module protocol definition (see chapter 2.7).
10 Basic Setting
The "005 - Basic setting" function opens a view with a tab whose name consists
of the control module address (for example, 01) and the suffix "GES". The
basic setting configuration and the displayed measured values differ depend-
ing on whether the function was carried out on control modules with KWP or
UDS protocol.
With access via DoIP, remote diagnosis access is possible. The following mes-
sage will appear in this case:
41
Accessing a vehicle remotely presents a high security risk. Make sure that
! there are no people in the vehicle that you are currently connecting to with a
remote connection.

The following information explains the steps for completing the Basic setting
function on a KWP control module. The results view shows two tables for meas-
ured value output without and with basic setting, as well as areas for channel
selection, status display, and preset functionality.
There is a preset function (see chapter 2.7) that only contains one channel
number. When loading a preset, this channel number is selected and reading
measured values "not in basic setting" starts. When loading a preset, the
channel number that loads is displayed in the edit field next to the "Select
channel" button.
Channel Selection
Decimal numbers in the following range are valid for the channel number:
KWP1281: 0 - 255
KWP2000: 1 - 254
The button for selecting the channel remains deactivated until you have en-
tered a valid channel number. If you have not entered a valid channel number,
then the background of the channel editing field is red to indicate that a pa-
rameter must be entered here. If a channel is switched, the basic setting on the
current channel ends before switching to the new channel.
Status Display
The current basic setting status is displayed in bold font on two lines in the "Se-
lection and feedback" area: the current selected channel and the basic setting
status. “-" will be displayed for the current channel as long as no channel is
selected. There are two separate tables in the "Selection and feedback" area
whose names are "Measured values without basic setting" and "Measured
values with basic setting". The measured values that are received are entered
in the corresponding table, depending on the basic setting status that the con-
trol module reports. Entering new values after a status change leaves the pre-
vious values in the other table unchanged. That means values can be displayed
in both tables at the same time.
42
Controlling a Selected Basic Setting

In the function navigation area, there are two buttons that are aligned with
both tables that say "Activate". If a channel is selected, the two buttons are on-
ly activated in alternation. If no channel is selected (when entering the results
view), both buttons are deactivated.
Basic Setting with KWP1281

After selecting a channel, the "Activate" button for the "Measured values with
basic setting" table is activated. Clicking one of the two "Activate" buttons
changes the activation for both buttons. Clicking the "Activate" button will
cause the measured values to be read in cycles and displayed. "Status not
available" is displayed as the basic setting status.
Basic Setting with KWP2000

If a channel is selected, the measured values are read in cycles and displayed.
Both "Activate" buttons have the same function and activate basic setting. The
basic setting status information is displayed. Only one button is activate at a
time based on the status information:
This means, with control module status info:
- 07, 10: the button for the table "Measured values with basic setting" is deac-
tivated.
- 04, 06: the button for the table "Measured values without basic setting" is
deactivated. Basic setting only stops when exiting the tab and changing the
channel.

With UDS control modules, additional parameters can be set and measured
values can be selected after selecting the basic settings in the specific views.
The following information describes the required steps.
Basic Setting Selection View

In the first view of the function, the desired basic settings must be selected. The
available settings are displayed in the list on the left. The selected tests will ap-
pear in the list located on the right side, which is empty at the beginning. Click-
ing the ">" button moves the selected basic settings from the left list to the
right. To add all basic settings from this list, press the ">>" button. Individual
basic settings can be removed from the list on the right by clicking on the "<"
button. Clicking the "<<" button removes all basic settings from the list. These
basic settings will then appear in the list on the left. The list of selected basic
settings can be sorted. Exactly one basic setting must be selected to do this.
Each time the "▲" button is clicked, the setting moves one position up. Clicking
43
"▼" moves it down one position. Once all of the desired settings have been se-
lected, clicking the "➨" button moves to the next view, setting the parameters.
You can use a filter function (see chapter 2.5.2) that filters the basic setting se-
lection list based on sequences of characters.
Parameter Settings View

The left list contains the basic settings that were selected in the previous view.
The first basic setting is marked by default. Once a basic setting was selected,
the associated parameters are displayed in the right table. Depending on the
parameter type, its value can either be selected from a list field in the right col-
umn or entered as free text. If entered as free text, the system then checks if the
valued entered is valid. If problems are found or a value is missing, the affect-
ed parameter is marked in red and the associated basic setting is displayed in
bold red font. Press the "Default parameters" button to reset all parameters to
their default values. The system then checks for missing or invalid values and
marks the affected parameters and basic settings. As long as there are prob-
lems with the parameters that were set, meaning at least one parameter is
marked in red, an error message will appear when clicking the "➨" button. If
the validity test for all parameters was successful, the next view, "Measured
value selection", is displayed. Clicking "◄━" returns to the previous view in
basic setting selection. Even if basic settings were added or removed there, all
of the affected settings remain the same for the remaining basic settings.
Measured Values Selection View

In this view, measured values that will be displayed during the process can be
selected for each basic setting. Comprehensive measured values, meaning
ones that apply for all basic settings, can also be selected. All previously se-
lected basic settings are listed in the upper list field. The first entry is always the
"Comprehensive" value. Measured values that are not based on a specific
basic setting can be allocated to these and displayed regardless of the basic
setting that is currently activated. For the selected basic setting or for the
"Comprehensive" entry, the available measured values are displayed on the
left side. The measured values displayed can be changed using the option
fields, which are located above the list field. Measured values specific to basic
settings, control modules, and vehicles can be selected. The measured values to
be displayed can be selected here the same way basic settings are selected.
The selected measured values will appear in the list on the right side, which is
empty at the beginning. Clicking the ">" button moves the selected measured
values to the list on the right. To add all visible measured values from this list,
press the ">>" button. Individual measured values can be removed from the
list on the right by clicking on the "<" button. Clicking the "<<" button removes
44
all measured values from the list. These measured values will then appear in
the list on the left. The list of selected measured values can be sorted. Exactly
one measured value must be selected to do this. Each time the "▲" button is
clicked, the item moves one position up. Clicking "▼" moves it down one posi-
tion. Once the desired measured values are selected, you can switch to perform-
ing the basic settings using the "->" button. If vehicle-specific measured values
were selected, you can only switch to performing the basic setting if the control
modules that had measured values selected can be addressed together. If the
control modules cannot be addressed together, a dialog with the conflicts is
displayed. They must be corrected before you can switch to the next page.
Clicking "<-" returns to the previous view in parameters settings. Even if the
parameters are changed or basic settings are added or removed there, the
measured value selection remains for the other basic settings.
You can use a filter function (see chapter 2.5.2) that filters the selection list
based on sequences of characters for selecting the measured values for the
basic settings.
Performing Basic Settings

The actual basic setting for the control module is performed in this view. The
view consists of two lists that each have the columns Name, RDID, value, and
the control module address, if applicable. The upper list, which shows the se-
lected basic settings, also contains both the "Status" and "Results" columns.
The table columns of both lists can be configured (see 2.5.4 and 2.5.5). The
control module address column is the only exception. The control module ad-
dress column shows the control module addresses for the selected measured
values. It is only visible if the comprehensive vehicle measured values were se-
lected and is displayed as the last column.
The basic settings and the associated specific measured values, the status
measured values and the parameters are displayed in the upper list and are
collapsed by default. Clicking on the ">" symbol for an element expands it (or
collapses the element again). All comprehensive measured values and meas-
ured value groups are displayed in the lower list. Measured values can be ar-
ranged in groups. When this happens, a ">" is added to the beginning to indi-
cate there is a group and the right column will be empty. Clicking the ">" sym-
bol opens the group and displays the measured values. Clicking on the ">"
that is now in front of the group will hide the group again. All elements con-
tained in both lists can be opened and closed with the "+" and "-" buttons lo-
cated underneath.
The measured values that are read can be recorded in a table format in a log
file. The storage directory is the application subfolder “DiagnosticProtocols”. The
45
file name is created by the application based on the vehicle name, the date, and
the time (gelog_<VIN>_<Date>T<Time>).
Recording the measured values can be started or continued with the “●” button.
The “▐▐” button pauses the recording, and the “■”ends the recording.
The complete status of all basic settings is displayed above both tree structures
in the "UDS Basic Setting - Status" field. Possible status displays are: active, not
active and ended.
To begin the process, first select the basic settings to be performed. You can
click to select one or more basic settings. Clicking on "►" (start) starts the pro-
cess. Clicking on "■" (stop) ends the process. The "STOP" button (emergency
off) stops all active basic settings. The same applies if the tab is closed or exited
or if you return to the measured value selection using the "<" button. It does
not start again automatically when you return to the "Performing basic setting"
view. It must be started again manually. You can switch to the next basic setting
using the "▐►" (next) button. Clicking on "►" starts the currently selected basic
setting. If it ends, the system will continue with the next basic setting in the list. If
the end of the list is reached, it will move to the first entry in the list. The meas-
ured values for the basic setting that is currently running are shown and all
others are hidden. The "►" is deactivated while this is running. Clicking on “■”
stops the basic setting. You can click “▐►” to continue. The system will begin
with the basic setting that is currently selected, regardless of where the proce-
dure was stopped. Some basic setting procedures require action from the user.
If this is the case, the required action is shown in the measured value table for
the current active measured value. The setting process continues automatically
once the action is performed. The measured values will be displayed once the
basic setting is complete. If the basic setting was not successful, a dialog ap-
pears with an error message that you must confirm.
There is a preset function (see chapter 2.7) that contains the selection, parame-
ter settings, and measured value allocation for the basic settings. Loading a
preset retrieves the configuration that was stored in the preset.
10.3 Special Instructions when Using the Keyboard

Some settings can also be made using keyboard shortcuts. The following codes
are also available in addition to the usual keyboard shortcuts:
Keyboard shortcut and function:
 CTRL + P: start actuator test (play ►)
 CTRL + S: stop actuator test (stop ■)
46
 CTRL + N: while an actuator test is running:

 Next actuator (next ▐►)
 ESC: in the "Perform output diagnostic test mode" view: stop (stop ■)
10.4 Short Routines

The "005.02 - Short routines" function opens a view with a tab whose name
consists of the control module address (for example, 01) and the suffix "FRR".
The function is a separate sub-function of the basic setting with only two views.
Short Routine Selection View

Similar to the basic setting selection for UDS, this view makes it possible to se-
lect short routines for execution and to change the sequence of the selected
routines.
You can use a filter function (see chapter 2.5.2) that filters the short routine se-
lection list based on sequences of characters.
Executing Short Routines

The view for executing short routines shows three tables. The routines to be ex-
ecuted can be selected in the left table. The upper right able also shows the
parameters for the selected routine. They must be filled out completely in order
to execute the routine. The default values for the parameters can be set using
the "Default Parameters” button.
The “►” button must be used to execute the selected routine. If results are pre-
sent for the selected routine, they will be shown in the lower right table.
11 Output Diagnostic Test Mode

You can reach the output diagnostic test mode function after selecting a control
module using the function navigator in the "Control module list view" under the
entry "004 - Output diagnostic test mode". It is controlled in a results view with
a tab whose name consists of the control module address and the suffix "SGD"
(for example, "01 - SGD"). The output diagnostic test mode configuration and
the displayed measured values differ depending on whether the function was
carried out on control modules with KWP or UDS protocol.
With access via DoIP, remote diagnosis access is possible. The following mes-
sage will appear in this case:
Accessing a vehicle remotely presents a high security risk. Make sure that
! there are no people in the vehicle that you are currently connecting to with a
remote connection.
47

The following information explains the steps for performing output diagnostic
test mode on a KWP control module. The results display shows a table for
measured value output as well as areas for configuration and performing.
Output Diagnostic Test Mode Configuration (KWP)

Using the "sequential" and "selective" radio buttons in the "Output diagnostic
test mode" group, you can select between a sequential or a selective output
diagnostic test mode. The "sequential" option is selected by default the first
time the function starts for a control module. If sequential output diagnostic test
mode is not available based on the supported functions that are detected, the
"selective" option will be selected. In the case of a selective actuator test, you
can enter the desired actuator code in a second group. You can select between
decimal and hexadecimal input using the "dez" and "hex" radio buttons. The
group or the input elements it contains are deactivated if sequential output di-
agnostic test mode is selected.
Output Diagnostic Test Mode Operation (KWP)

The "►" (start) button is activated once you have selected sequential output
diagnostic test mode or a concrete actuator, or if it is automatically preselected.
This starts output diagnostic test mode. The "▐►" (next) button allows you to
switch to the next actuator if sequential output diagnostic test mode has been
started and the control module reports that switching is currently permitted
(meaning the status "SGT_LAUFT_NICHTUNTERBRECHBAR" (control mod-
ule_running_cannot be interrupted) is active. The “■" (stop) button allows you
to end output diagnostic test mode.
Actuator Test Results Display (KWP)

The status that is reported during output diagnostic test mode is displayed in
the status line. The actuator code reported by the control module and the asso-
ciated name are in parentheses afterward. The measured values that are re-
ported are displayed in the "Measured values" table.
Preset Function
Using the preset function during a selective actuator test, you can save the se-
lected actuator code under a preset name. If an actuator code has been en-
tered and confirmed. The system automatically switches to selective output di-
agnostic test mode when loading a preset.
48

Output diagnostic test mode can be figured more extensively in control mod-
ules with the UDS protocol. After selecting the output diagnostic test mode func-
tion for a UDS control module, you then enter the actuator selection view. This
contains a list of available control module actuators whose individual parame-
ters can be set. The selected and configured actuator tests can then be run in
sequence or in parallel. You can end the function at any time by closing the
tab. If you leave the tab (for example by selecting another tab) or change the
view, the status of the function in terms of the parameters set is maintained but
any output diagnostic tests that are currently running will stop. This also applies
when switching from running output diagnostic test mode back to setting pa-
rameters. It is not possible to add or set parameters for individual actuators
when output diagnostic test mode is running. The following information de-
scribes the four phases of output diagnostic test mode for UDS control modules
in detail.
Actuator Selection View (UDS)

The left list in this view contains all available actuators for the selected control
module. The list can be sorted alphabetically by clicking on the column header.
The actuators to be tested will appear in the list on the right side, which is emp-
ty at the beginning. One or more actuators can be selected by clicking or using
the arrow keys on the keyboard. The first actuator that begins with the letter
entered is selected. If the same letter is entered again, the next element that
starts with this letter is selected. Clicking the ">" button moves the selected ac-
tuators to the list on the right. To select all actuators and add them to the list,
press the ">>" button. Individual actuators can be removed from the list on the
right by clicking on the "<" button. Clicking the "<<" button removes all actua-
tors from the list. The removed actuators will then appear in the list on the left.
The list of actuators values can be sorted. Exactly one actuator must be select-
ed to do this. Each time the "▲" button is clicked, the item moves one position
up. Clicking "▼" moves it down one position. If all desired actuators are select-
ed, clicking the button moves to the next view, parameter settings.
You can use a filter function (see chapter 2.5.2) that filters the output diagnos-
tic test mode selection list based on sequences of characters.
Parameter Settings View (UDS)

The left list contains the actuators that were selected in the previous view. The
first actuator is marked by default. The available parameters for each selected
actuator are displayed in the right table. Depending on the parameter type, its
value can either be selected from a list field in the right column or entered as
free text. If entered as free text, the system then checks if the valued entered is
valid. If problems are found or a value is missing, the affected parameters are
49
marked in red and the associated actuator is displayed in bold red font. Press
the "Default parameters" button to reset all parameters to their default values.
The system then checks for missing or invalid values and marks the affected
parameters and actuators.
As long as there are problems with the parameters that were set, meaning at
least one parameter is marked in red, an error message that warns you that
there is still a problem with the data will appear when clicking the "->" button.
If the validity test for all parameters was successful, the next view, "Measured
value selection", is displayed. Clicking "<-" returns to the previous view for se-
lecting actuators. Even if actuators were added or removed there, all of the
affected settings remain the same for the remaining actuators.
Measured Value Selection View (UDS)

In this view, measured values that will be displayed during the process can be
selected for each actuator. Comprehensive actuator measured values, meaning
ones that apply for all actuators, can also be selected. Items that are available
for the selected actuator or for the "overall" entry are displayed in the list on
the left. The measured values displayed can be changed using the option
fields, which are located above the list field. Measured values specific to basic
settings, control modules, and vehicles can be selected. The measured values to
be displayed can be selected here the same way actuators are selected. The
right list, which is empty at the beginning, contains the selected measured val-
ues.
Clicking the ">" button moves the selected measured values to the list on the
right. To add all measured values from this list, press the ">>" button. Individ-
ual measured values can be removed from the list on the right by clicking on
the "<" button.
Clicking the "<<" button removes all measured values from the list. These
measured values will then appear in the list on the left. The list of selected
measured values can be sorted. Exactly one measured value must be selected
to do this.
Each time the "▲" button is clicked, the item moves one position up. Clicking
"▼" moves it down one position.
Once the desired measured values are selected, you can switch to performing
output diagnostic test mode using the "➨" button. If vehicle-specific measured
values were selected, you can only switch to performing output diagnostic test
mode if the control modules that had measured values selected can be ad-
dressed together. If the control modules cannot be addressed together, a dia-
log with the conflicts is displayed. They must be corrected before you can
switch to the next page. Clicking "<-" returns to the previous view in parame-
50
ters settings. Even if the parameters are changed or actuators are added or
removed there, the measured value selection remains for the other actuators.
You can use a filter function (see chapter 2.5.2) that filters the selection list
based on sequences of characters for selecting the measured values for the
measured values.
Performing Output Diagnostic Test Mode (UDS)

The actual output diagnostic test mode is performed in this view. The view con-
sists of two lists that each have the columns Name, RDID, value, and the control
module address, if applicable. The control module address column shows the
control module addresses for the selected measured values. It is only visible if
comprehensive vehicle measured values were selected. The selected actuators,
their actuator status and their associated specific measured values and param-
eters are shown in a tree structure in the upper area. They are shown collapsed
by default. The actuator parameters and their values are shown as a tool tip
for this when the mouse cursor is placed over the actuator.
All overall measured values are shown in the lower tree structure.
Measured values can be arranged in groups. When this happens, a ">" is
added to the beginning to indicate there is a group and the right column will
be empty.
Clicking the ">" symbol opens the group and displays the measured values.
Clicking on the "-" that is now in front of the group will hide the group again.
The measured values that are read can be recorded in a table format in a log
file. The storage directory is the application subfolder “DiagnosticProtocols”. The
file name is created by the application based on the vehicle name, the date, and
the time (sglog_<VIN>_<Date>T<Time>).
Recording the measured values can be started or continued with the “●” button.
The “▐▐” button pauses the recording, and the “■”ends the recording.
The overall status of all selected actuator tests displayed in the "Output diag-
nostic test mode - status field" above both tree structures. Possible status mes-
sages are: active, not active and ended. To begin output diagnostic test mode,
first select the actuators to be checked. You can click to select one or more ac-
tuators.
Clicking on "►" (start) starts the actuator test. Clicking on "■" (stop) ends the
actuator test. The buttons are always based on the actuator test that is currently
selected. For example, if you choose the actuators 1 through 3 before starting,
these tests are started by pressing the "►" button. If you reduce the selection to
actuators 2 and 3 and press the "■" button, only actuators 2 and 3 are stopped,
while actuator 1 continues running. Actuators can be started and stopped at any
time independently of each other.
51
The "STOP" (emergency off) button stops all active actuators. The same applies
if the tab is closed or exited or if you return to the previous view using the "<"
button. The actuator test does not start again automatically when your return to
the "Performing output diagnostic test mode" view. It must be started again
manually.
The " " (restart) button restarts the already started actuators with default pa-
rameters from the currently selected actuators.
Using the "▐►" (next) button, a sequential actuator test can be performed on a
UDS control module. There must not be any other active actuator tests. An ac-
tuator must also be selected from the list on the left. If both conditions are met,
the "▐►" button will be activated.
Clicking on "▐►" switches to the next actuator and clicking on "►" starts the test
for this actuator. If the end of the list is reached, clicking "▐►" will move to the
first entry in the list. The measured values for the actuator test that is currently
running are shown. Clicking "■" stops the actuator test that is currently running.
The sequential actuator test can be continued by clicking "▐►" and "►". The sys-
tem will begin with the actuator that is currently selected, regardless of where
the test was stopped.
There is a preset function (see chapter 2.7) that contains the selection, parame-
ter settings, and measured value allocation for output diagnostic test mode.
Loading a preset retrieves the configuration that was stored in the preset.
11.3 Special Instructions when Using the Keyboard

Some settings can also be made using keyboard shortcuts. The following codes
are also available in addition to the usual keyboard shortcuts:
Keyboard shortcut and function:
 CTRL + P: start actuator test (play ►)
 CTRL + S: stop actuator test (stop ■)
 CTRL + N: while an actuator test is running
 Next actuator (next ▐►)
 ESC: in the "Perform output diagnostic test mode" view: (stop ■ )
12 Hex Services
Hex services (tab suffix "HEX") are a function for sending diagnostic PDUs (Pro-
tocol Data Units) on the vehicle bus directly to the control module without using
the associated ODX data. The "Hex service" view is selected the same way oth-
52
er diagnostic functions are selected from the function selection list in the "Con-
trol module list" view (selecting a control module and opening the "011.01 Hex
service" diagnostic function). The left area of the view is divided into four sub-
areas that are arranged one above the other:
 a table for selecting predefined request PDUs
 an input field for the PDU to be sent
 a trace view for diagnostic communication
 a display table for the last response PDU that was received
The areas 1, 3, and 4 can be resized by dragging the sides with the mouse.
The selection table combines two options for using predefined request PDUs.
The first option uses presets and the second option using an ODX browser that
creates PDUs from the ODX data and can be prepared as a PDU that is ready
to send. A request PDU that is selected in this table by double-clicking or that is
created is copied into the input field. You can switch between the two alterna-
tives with UDS control modules using the "Preset" and "ODX data" tabs that
are located above the table. With KWP control modules, only the "Presets" ver-
sion is available.
A request PDU that was prepared in the previous step can be edited in the in-
put field if needed. A request PDU can also be entered completely manually
here. The "Send" button to the right of the input field sends the request PDU to
the control module. The response from the control module is displayed in two
areas located below, called "Trace display" and "Display table". The trace dis-
play lists all requests that were sent and the response received in chronological
order. Depending on the communication type, either the CAN ID or the logical
address (in the case of DoIP) will be shown in the left column of the table. A
tool tip will show the associated long name. The display can be cleared by
clicking the "Delete trace" button. Using the "Copy trace" button, you can copy
the content of the trace display into the clipboard and reuse it in another appli-
cation. The display table located all the way at the bottom displays the last con-
trol module response that was received. The control module response can also
be copied into the clipboard using the "Copy response" button.
"Preset" Tab Selection Table

In this version, frequently-used request PDUs are offered for selection in a sort-
able table with the columns "PDU", "Service name", and the sending type. The
selection cannot be made from a standard table. You can change and/or ex-
pand an existing table and save it as a new table under a different name with
the preset function. In the preset selection drop-down field, there is an entry
with the name "Empty" that allows you to create a preset without any diagnos-
tic PDUs entered. The active preset name (in the combo box) is then deleted.
The standard preset is always present and cannot be overwritten. The lines of a
preset (except for the standard preset) can be edited by clicking the "EDIT" but-
53
ton in the last column of the table line. Pressing this button opens an editing
dialog. Edit mode can also be activated for a selected line by pressing the "F2"
button. A dialog for entering the PDU, the service name, and a selection list for
the sending type opens. Pressing the "Del" (delete) button deletes the selected
line from the table.
ODX Browser Tab Selection Table

The ODX browser allows request PDUs to be created from the ODX data ele-
ments. In the left half, there is a list of services available for the selected control
module (SID and Service/Job columns). Selecting a service displays the list of
parameters for the selected service in the right half. Its values are initially filled
with the initialization values from the data but can be expanded or changed by
the user. Unassigned parameters are marked in red. After completing the pa-
rameter setting, the completed request PDU can be copied into the input line by
double-clicking on the desired service or pressing "Return <┘".
13 Access Authorization and Diagnostic Session

Common Functionalities
The "Access authorization" and "Diagnostic session" functions are listed in the
diagnostic function selection in the control module list as two separate entries in
the "Diagnostic function" area. The entry "009 - Diagnostic session" is used as
the name for the "Session change" function. The entry "008 - Access authoriza-
tion" is used as the name for the "Access authorization" function. Both functions
can also be reached using the side bar ("Diagnostic" area), but only if a diag-
nostic function was performed for the identified control module. Both functions
are performed using a modal dialog that is called "Access authorization" or
"Diagnostic session". A text field in the upper section of the dialog contains the
applicable control module in the format "<Control module address> - <Con-
trol module name>", the reported status, the applicable diagnostic function
and, possibly the applicable parameters in the information area in the session
change or access authorization dialog, so that you can decide which login
code or diagnostic function is necessary. An NRC sent by the control module
that has opened the dialog is displayed there, including the service ID and the
NRC in hex format.
There is a "Perform" button for both functions that can be used to perform the
respective action, either access authorization (after selecting the login method
and entering the login code) or session change (after selecting the target ses-
sion). You can close the dialog without any action using the "Cancel” / “End”
button. After starting the “Access authorization” and/or “Session change” func-
tion, the progress dialog is displayed. A results dialog will indicate if the access
authorization or session change is not completed successfully.
54
"Access Authorization" Dialog

Depending on the range of control module functions, either an access authori-
zation dialog to activate using a code or a dialog for SFD activation is auto-
matically opened.
Code Input:
To set parameters for access authorization using code input, the dialog shows a
list box called "Login method" for selecting the type of access authorization as
well as an input field called "login code" for the access code. A checkbox
called "Show login code" is also displayed. It is deactivated by default. In this
case, only asterisks ("*") are shown in the input field instead of the actual input.
If it is activated, the login code is displayed in plain text. The available KWP
login methods are named and sorted as follows:
KWP2000:
 Automatic access authorization (preselected by default)
 Access authorization level ¾
 Access authorization level 5/6
KWP1281:
 Automatic access authorization
UDS:
The available login methods for UDS control modules are displayed and sorted
based on the ODX data. Login methods that are defined as input parameter
IPA_SecurMetho for the SinglJob_SecurAcces are valid for UDS control mod-
ules. Possible methods may include Login, System Specific, Bootload, and Air-
bag Deployment.
SFD Activation:
The control modules as well as the current activation information are displayed
in the access authorization dialog for the SFD activation; this contains the acti-
vated roll, the type of activation, the remaining minutes, and the activation sta-
tus.
To configure a new activation, there are four selection boxes through which the
desired use case, the requested role, the activation time and the desired login
methods can be set. The selected use case is started with the “Perform” button.
The following six use cases are available:
 Online activation
 Offline activation
 Retrieve and save activation token
 Activation status documentation on backend
 Reset internal SFD data
55
 Manual SFD activation

By performing “Online activation”, a control module can be activated directly
with the selected roll and the activation duration if a connection to the SFD
backend can be successfully established with a PKI card or SecureID login. If
offline tokens are invalid due to a successful online activation, then a prompt
appears asking if these invalid tokens should be deleted.
The use case “Retrieve and save activation token” also requires a connection to
the SFD backend and determines an activation token for the current control
module, which is then stored on the local tester. The save location of the token
can be changed in the administration under "access authorization save loca-
tion".
This stored offline token can also be used for activation via the use case “Of-
fline activation”. The oldest offline token that matches the selected roll and acti-
vation duration is always used for this. If this is the case, a connection to the
SFD backend is not necessary.
With the “manual SFD activation” use case, the SFD activation can be per-
formed even when the tester does not have an Internet connection. A request
structure that is suitable for the control module will be prepared for this, which
can be used by any device with an Internet connection to the SFD IT backend to
generate an activation token. The generated activation token can be used for
activation in this use case.
With both remaining use cases, the activation status of a control module can
also be documented back in the SFD backend or the internal SFD data of a
control module is reset.
„BASIC“, „EXTENDED“ and „SUPERUSER“ can be selected when selecting the
“Requested roll”. “Brief (90 min), “Long (200 km)” and “persistent” can be se-
lected for the activation duration.
You can choose between “PKI authentication” and "SecureID” as the login
method. A login dialog will display if you choose activation with SecureID. The
"Group ID” and the combination of the “PIN + token” must be entered in the
dialog. The “PIN + token” must be typed together with no spaces in between.
The “Access authorization” dialog also has a “Lock control module” button to
lock the SFD activation for the current control module. The button is inactive if
the current control module is not enabled.
The entry “046.05 Lock vehicle” is in the diagnostic function tree for the SFD
locks of all control modules via a functional request. The implementation of this
function must be done first. After performing, a results dialog appears with a
list of all responding control modules including their individual results.
If an error occurs while an SFD use case is in progress, then it is displayed in an
error dialog. Then, or directly after a successful implementation, the activation
56
information is read out again from the control module and displayed in the
dialog. The dialog can be closed with the “End” button.
"Diagnostic Session" Dialog

An information area in the top of the dialog shows which diagnostic session the
control module is currently in.
The active diagnostic session is only detected as follows for UDS control mod-
ules and service 22 KWP control modules:
 UDS: measured values with TI IDE00325 (long name: Active Diagnostic
Session)
 KWP service 22: Record Data Identifier $F186
If the active diagnostic session cannot be detected, for example because the
measured value is not populated with data or because it is a KWP control
module that does not support service 22, "Diagnostic session cannot be detect-
ed" is displayed. The dialog contains a list box for selecting the diagnostic ses-
sion that shows all of the diagnostic sessions that are available for the control
module or the diagnostic protocol.
The available diagnostic sessions for KWP control modules are named and
sorted as follows:
KWP2000:
 Standard on board diagnosis
 Developer mode
 Update programming
 End of line at control module manufacturer
 End of line in Volkswagen group
KWP1281:
the area of the GUI for performing the diagnostic session is deactivated
here
UDS:
The available session change methods for UDS control modules are displayed
and sorted based on the ODX data. Possible sessions may include End of Line
mode (EOL), VW Diagnostic mode, Engineering mode, Programming mode,
and OBD Diagnostic mode.
14 Write Data Set

The "Write data set" function is selected in the function navigator in the "Con-
trol module list" view using the entry "010.01 Write data set". A target data
container (TDC) can be written in the control module using this function (suffix
57
on the tab is "DAT"). Using the "Data set" input field and the "Search" button,
you can select the file with the target data container in a standard file selection
dialog for XML or ZIP files and start the writing process using the "Write data
set" button. You can also open the target data container in an external editor
using the "Start external editor" button. The desired editor can be selected in
the Administration area under "Function configuration->Write data set". The
writing process cannot be stopped once it has started. A status message at the
end of the writing process informs you if the process completed successfully or
not.
15 Reading and Writing Memory Cells

The functions for reading or writing memory cells are provided in the control
module list in the "Diagnostic function" section as entry "010.02 Memory cells".
With KWP1281 control modules, the following functions are offered as sub-
functions:
 Read RAM
 Read ROM/EPROM
 Read/write EEPROM
 Read/write EEPROM (serial)
With KWP2000 control modules, the following detailed functions are offered
as long as "Developer functions" for the applicable control module are report-
ed as supported in the supported functions:
With UDS control modules, the following detailed functions are offered as long
as the service DiagnServi_ReadMemorByAddreMCD20001 is contained in the
data.
Selecting the higher-level entry "Memory cells" always leads to the detailed
function "Read/write EEPROM", regardless of the diagnostic protocol.
After selecting one of the detailed functions for reading or writing memory
cells, a results view will open for this diagnostic function. As with the other indi-
vidual control module functions, the name of the results view consists of the
control module address for the applicable control module and the function
code "SPZ" (for example, 09 - SPZ). The results view is divided as usual into a
function navigation area on the right and the actual results view on the left.
58
15.1 Reading Memory Cells

You can configure the initial address for the memory cells to be read in the
function navigation area. There is a group for this called "Initial address" in the
function navigation area. Within this group, you can set the length of the ad-
dress using a combo box. The bytes that can be selected depend on the diag-
nostic protocol. With KWP1281, the selection contains "2 bytes" and "3 bytes",
with KWP2000, it contains "2 bytes", and with UDS, it contains "1 byte"
through "15 bytes". You can select between decimal and hexadecimal input for
the initial address using two radio buttons. Hexadecimal input for the initial
address is selected by default the first time the results view opens. You can en-
ter the initial address for the address range to be read using an input field. The
initial address input field is highlighted with a red background until you enter a
valid initial address (3-byte example: range between 0x000000 (0 dez.) and
0xFFFFFF (16777216 dez.). It has a decorator that shows the permitted input
values. For UDS, hexadecimal input is necessary for address lengths larger
than 4 bytes and it cannot be changed to a decimal display. The decorate that
indicates the maximum input value is also omitted. When an address length of
"5 bytes" or greater is selected, only the hexadecimal display is available.
You can configure the number of memory cells to be read in the function navi-
gation area. There is a group for this called "Number of memory cells" in the
function navigation area. Within the group, you can selected between decimal
or hexadecimal input for the number of memory cells to be read using two ra-
dio buttons.
Hexadecimal input for the number of memory cells to be read is activated by
default the first time the results view opens. The address length "3 bytes" is pre-
selected. An exception to this is the KWP1281 diagnostic protocol, which has
"2 bytes" preselected. For UDS control modules, you can also set the length
specification using a combo box that contains the values "1 byte" and "2
bytes". The input field for the number of memory cells to be read is highlighted
with a red background until you enter a valid number in the range between
0x0000 (0 dez.) and 0x3E8 (1000 dez.). For UDS control modules, the upper
threshold for a valid input is 0XFF (255 dez.) for the 1-byte specification, and
0xFFE (4094 dez.) for the 2-byte specification. The input field has a decorator
that shows the permitted input values.
You can start the memory cell reading using the "Read cells" button. The button
is only active if the initial address and the number of memory cells to be read
contain valid inputs.
15.2 Display of Read Memory Cells

In the results display, the name of the open detailed function (for example,
"Read/write EEPROM") is displayed in bold font in the upper left. There is a
table located below with the memory cells that have been read or that will be
59
written. The value of the requested memory cells is shown grouped 16 bytes to
a line, as is the case in the results view for the "Hex service" function. The first
column contains the address of the memory content that is displayed beginning
with the start address with an increment of 16 bytes. The table cannot be sort-
ed. Then 16 more columns are shown whose titles contain 0 through 15 or
00x00 through 0x0F depending on the address display type for the offset of
the results byte that is to be displayed. The column headers for the hexadeci-
mal display are two digits with a zero at the beginning (for example, "00").
There is an entry called "Address display" in the "Memory cells" section of the
"Function configuration" in the administration that you can use to switch the
address display between a decimal or hexadecimal format. Both the entries in
the "Address" column and the titles in the 16 offset columns are adapted to the
selected display type.
The 16 bytes in a line are displayed as an ASCII character sequence in the last
column, called "ASCII". If fewer than 16 bytes were read in the bottom line,
only the bytes that were actually read will be displayed as ASCII characters.
Characters that are not contained in the character set that is used or that can-
not be displayed (such as line breaks) are replaced with a period ".". The same
non-proportional character set is used in the table as is used in the "Hex ser-
vices" function.
The individual results bytes are displayed in decimal or hexadecimal format,
depending on the results display option that is selected in the function naviga-
tion area. The width of the table columns is set so that switching from hexadec-
imal to decimal format does not cause the width of the columns to change
(hexadecimal format: two digits, decimal format: maximum three digits). Hexa-
decimal display is active the first time the dialog opens. The memory content in
hexadecimal display is shown with two digits with a zero at the beginning.
15.3 Manipulating Read Memory Cells

Within the results table, you can select entire lines by clicking with the mouse or
by navigating with the up and down arrow keys. You can activate an editing
dialog for the selected line by double-clicking on a line or using the "F2" but-
ton.
In the editing dialog for changing memory cells, the 16 bytes of the selected
line in the table are shown in a table form without using an actual table ele-
ment. The first "column" with the heading "Address" displays the absolute ad-
dress of the memory location shown as a text field. The display type (decimal or
hexadecimal) is taken from the results view and shown after the heading in pa-
rentheses. The second and third "columns" with the heading "Value" display
the current value of the memory cells in an input field in hexadecimal and dec-
imal format. The display type is shown after the heading in parentheses. The
fourth "column" with the heading "ASCII" displays the value of the memory
60
cells in ASCII format in a field that cannot be edited. Characters that are not
contained in the character set that is used or that cannot be displayed (such as
line breaks) are replaced with a period "." in this dialog. You can edit the
memory cells either in the "Value (hex)" or the "Value (dez)" column. A change
is automatically copied into the other input field. Every memory cell that is
changed in comparison to the data read is marked with a decorator near both
input fields. This decorator shows the original value that was read. If a change
is restored (meaning the read value is entered again), the decorator disap-
pears. The Tab button can be used to navigate to the next element that can be
edited. The up/down arrow keys can be used to navigate between lines in the
same column. All input fields that belong to the memory cells that were not
read earlier are deactivated.
By pressing the "Cancel" button, you can discard the changes which closes the
dialog window without accepting the changed values. The changes are copied
into the results view after confirming the changes with the "OK" button or
pressing the Enter button. The numerical display (dec. or hex display) of all
memory cells that changed in comparison to the read values are marked with
bold font and yellow highlighting in the cell background.
15.4 Writing Memory Cells

You can write memory cells using the "Write cells" button. The button is only
activated when one of the following detailed functions:
 Read/write EEPROM (serial)
is selected by the user.
With UDS, the writing button is only activated when the corresponding service
for the control module is populated with data. The button is only activated if
memory cells have already been read. After pressing the "Write cells" button,
a security prompt informs you about the risk of writing directly in memory cells.
Changing physical memory addresses directly can cause irreparable damage

to a control module!
Are you sure you want to continue the writing process?

After confirming, the writing process is performed and the cells are read out again. The
cell writing can be canceled in the security prompt.
15.5 Preset Function

Using the preset function, you can store the memory cell values that are cur-
rently shown in the view, regardless of whether they were already written in a
control module or not. A preset is only offered for selection if the software part
61
number and the software version of the control module that is currently con-
nected match the preset. When saving a preset, a dialog asks, "Do you also
want to save the content of the memory area in the preset?". If you select
"Yes", the values currently displayed for the memory content are also
saved. The ASCII interpretations of the memory content are not stored in the
preset. When loading a preset, the memory area stored there is also read out
again from the control module. Previous results are automatically discarded
without a prompt. If the preset contains content from the memory area, it will
be displayed in bold font with a yellow background if it differs from the values
that are read. After loading a preset, values can be copied into the control
module using the "Write cells" function.
16 Baud Rate
In the "Control module list" view under the diagnostic functions, the entry
"011.02 Baud rate". Opening this after selecting a control module opens a
dialog for switching the baud rate. The dialog contains two buttons for per-
forming actions and an area for displaying the results. The buttons "Switch to 1
Mbaud" or "Switch to default baud rate" switch to a baud rate of 1 Mbaud or
to the default baud rate from the project data. The result is given as text infor-
mation including the target baud rate.
17 Data upload
To transfer data sets from control modules to the local tester, the entry “011.05
- Data upload” must be selected in the function navigator for the “Control
module list” view. This function only supports UDS control modules. The tab
name for this results view consists of the control module address (such as 0001)
and the suffix “DUP” for “data upload”. At the top of this view there is a table
containing data sets that are available on the control module. The lower file
list, however, shows the data sets already locally available.
In the upper table, selection boxes can be used to select available control
module data sets. When the “Upload data set” button is pressed, the control
module transmits the selected data sets to the local directory. This local directo-
ry is configured via the “Search...” button. However, changes to directory paths
will only be in effect for as long as the tab is used.
There is an option to enter user-defined text in the “Free text” column within this
data set table. This additional text will be added to the file name of the data set
downloaded in the future. When entering free text, the naming conventions are
immediately checked; only numbers and letters are permitted that do not ex-
ceed the maximum length of 80 characters. Whenever there is no user-defined
text, the current time stamp with the "yyyyMMddTHHmmss” format is automati-
62
cally used as free text. The file names being transmitted are composed as fol-
lows:
DU_<control module address>_<data set ID>_<VIN>_<data set version>_<data set name>_<free
text>.bin
The lower list displays the local data sets being transmitted from the configured
storage directory. Pressing the “Display” button will open this directory with
Windows File Explorer.
18 Stopping Diagnostic Communication

There is an entry called "011.03 Stop communication" in the "Control module
list" view under both the diagnostic functions as well as the vehicle functions.
The entry under "Diagnostic function" ends any communication with the control
module that is selected in the control module list, regardless of the lock status.
The entry until "Vehicle functions" closes all open connections, regardless of the
lock status. Please note that opening these functions allows the affected control
module(s) to revert back to the default diagnostic session.
19 Transport Mode
To switch transport mode on or off for the entire vehicle, select the entry "045 -
Transport mode" under "Vehicle functions" in the "Control module list" view in
the function navigator. It contains the sub-functions "045.01 Activate" and
"045.02 Deactivate". To switch transport mode on or off, select the corre-
sponding list entry and double-click the corresponding sub-entry to start the
action. A message only appears if there is an error. The message contains de-
tailed information about the error.
20 Flashing
The flashing view with the tab name "FZG_FL" after opening the vehicle func-
tion "042 - Flashing" contains a table of all programmable control modules in
hierarchical order. A control module that is selected in the control module list
when opening is then preselected in this list. The table contains the columns
System / Container (initially contains information about the control modules
from the column), Flash Sequence, and Status. After loading flash files, the
flash containers that are available for a control module and the sessions con-
tained in them are displayed in the table in hierarchy levels below the respec-
tive control module and can be collapsed and expanded. Sub-systems, soft-
ware clusters, or virtual systems may have their own flash container. One or
more flash containers can be added to a control module. The baud rate only
displays if it was set differently than the standard rate from Administration
63
(function configuration). When flashing with a control file and binary files, the
binary files to be used are shown under the corresponding session.
Administration Settings
Standard paths for flash files can be set in Administration under "Save loca-
tions" in the "Flash paths" or "Flashing (Engineering)" areas. The default setting
is the same as in ODIS Service. The corresponding configuration entry from
ODIS Service is used for this. In the function configuration, you must specify in
the Flashing (Engineering) area if a flash procedure for multiple ICAS/HCT
control modules should be canceled if there are errors in individual control
modules. For KWP control modules, there is an option to specify the standard
baud rate for KWP flash procedures. Possible values are: default from the con-
tainer, 1000 KBit, 500 KBit, 100 KBit.
System 42
In the function navigation area, there is a "System 42" button with the System
42 icon. After a login dialog for System 42, it opens a System 42 dialog for
selecting a suitable flash container for the control module that is currently se-
lected. The following information is displayed for each flash container in the
flash container selection table:
 the name of the affected basic control module
 the part number
 the software version
 the hardware version
 the name of the container file
 the release status
A message about flashing is shown within the dialog and is always based on
the container that is currently selected. The default setting for the sorted output
of the entries in the flash container selection table is based on the basic control
module, then the part number, and then the software version. If you click on a
column header in a table to change the sorting order, the table is first sorted by
this column and then based on the default order. The following information is
shown for the control module in the flash container selection dialog:
 the control module name with control module address
 the part number that was read
 the software version that was read
 the hardware version that was read
The selectable flash containers from System 42 can be filtered based on the
following criteria: text filter for the base control module, the part number, the
software and hardware version, as well as using drop-down menus for project
selection and (after selecting a project) release status.
64
The flash containers selected using the checkboxes are downloaded after
pressing the "Complete" button and temporarily stored locally in the path set in
Administration. If a flash container has been downloaded, the flash sessions
contained are automatically allocated to the selected control modules.
After pressing the "Continue" button, the dialog shows all files that are related
to the selected flash containers. In this case, the "Continue" button is deactivat-
ed. You can select all files with the checkboxes. If you have selected more files
that are not flash containers, a "Save file" dialog opens after clicking the
"Complete" button. All files that you have selected using checkboxes are stored
by the application in the selected folder, except for the flash containers.
The diagnostic system gives the following filter options for display in the
"Download System 42" selection window:
 Filter by base control modules using keyboard input
 Filter by part number index using keyboard input
 Filter by software version using keyboard input
 Filter by hardware version using keyboard input
 Filter by release status by drop-down selection
The options for selection in the "Release status" filter correspond to the release
status that is available in System 42. The input fields for filtering are not case-
sensitive. The diagnostic system applies each character in the filter fields as
soon as it is entered. If you use more than one filter, the filter request are com-
bined together with a logical AND.
Release Status Display

Once the author has selected a platform using "Project selection", the "Release
status" column shows the release status for the individual control modules that
was read from System 42. The symbols for displaying the release status are
identical to the symbols used in System 42. The selected platform is also shown
in parentheses in the column header in order to show the reference to the pro-
ject selection. You can set the project reference to the release status display
using a drop-down menu. If the vehicle does not select any vehicle project us-
ing "Project selection", the "Release status" filter is deactivated. The entire "Re-
lease status" column will be filled with question marks if this is the case.
Local Flash Files

There is also a "Local flash file" button with a folder icon. It opens a file selec-
tion dialog for selecting a flash file on a file system, meaning the local hard
drive, a network drive, a CD or DVD, a USB stick, or an SD card.
The file selection filter for local files by default only shows files with the part
number of the selected control module and one of the following formats:
65
- for UDS: *.frf, *.frf-f, *.odx, *.odx-f, *.pdx and *.xml

- for KWP: *.stt, *.xml and *.sgo
By selecting the filter option "UDS flash container (*.frf, *.frf-f, *.odx, *.odx-f,
*.pdx, *.xml)“ for UDS control modules or "suitable KWP control tables (*.stt;
*.sgo)“ for KWP control modules, the filter is reduced to the file extensions. The
“Flash sequence (*.json)” filter reduces the selection to files that can define a
flash sequence. The filter can also be canceled with the filter "All files*.*".
Once a flash container is selected and confirmed in the selection dialog, the
container's availability and format are checked. If the test fails, the procedure
is canceled. If a control file with external binary files is selected, it is also re-
quired that the external binary files must be in the same directory as the control
file. When selecting a flash sequence file, the sequence it contains will be
shown in the interface. If all of the flash data that is specified as required in the
file is not present, the Status column for the affected control modules will con-
tain a note to reload the flash data.
Flash Data Security Specification

For a control module, signed flash containers may be required for flashing. This
is indicated when the required FDS key type is shown as a child node for the
control module in the table; when attempted, a flash container will be down-
loaded.
External Editor
If a container is selected for a control module, ti can be opened in an external
editor using the "Open in external editor" button.
Session Selection
The flash session to be flashed is selected from a flash container using a ses-
sion selection dialog, which is described in the information that follows. When
a flash container or a flash session is selected, the "Session selection" button
for opening the dialog is activated. When a flash container is selected, press-
ing this button opens a session selection dialog for the editor mode. When a
flash container is selected, all sessions that it contains are pre-selected even
though the dialog does not open at this time. The session selection is made in
the dialog using checkboxes. When the session selection dialog opens, all pre-
viously selected sessions are pre-selected. The sequence of the flash sessions is
shown in the sequence in the dialog and is designed for performing the flash-
ing as taken from the MCD system when checking the available sessions. You
cannot sort the table contents for session selection. The session selection dialog
contains a combo box and a label for the baud rate setting that is only activat-
ed with KWP control modules.
66
Sub-systems
Sub-systems for UDS control modules are loaded in the control module list
when the main control module is selected based on the setting selected for
"Load sub-systems" in Administration (Diagnostic communication area function
configuration). (the number of identification attempts for subsystems are also
set at the same location in the administration). Sub-systems for the control
module that is currently selected can be loading using the "Read sub-systems"
button. This button is only active with UDS control modules and if the admin-
istration setting "Load sub-systems" is deactivated (Diagnostic communication
area function configuration), and if the data for the selected control modules is
designed for sub-systems.
Version Check
If there is a version conflict, meaning the control module version is >= the con-
tainer version, or if the version cannot be detected, there is a warning message
that allows you to cancel the flash procedure for the affected control module.
The version check for KWP control modules can be deactivated in Administra-
tion (Flashing (Engineering) area function configuration).
Flash Sequence
For logical control modules, software clusters, and virtual systems, dependen-
cies to other control modules may result during flashing. In such cases, the flash
sequence file (*.json) as well as all of the flash files specified there as required
must be loaded. The flash procedure cannot start if all of the required data is
not loaded. If the flash data for a control module is missing, this will be indicat-
ed in the Status column with the message “(please load!)”.
The sequence in which the flashing should be performed should be entered in
the Flash Sequence column for the flash sessions.
Flash Procedure
A confirmation dialog appears after clicking the "Start flashing" button or with
the "CTRL + P" keyboard shortcut. If program requirements are not met when
starting the flash procedure, the diagnostic system informs you of this. The di-
agnostic system shows the requirements that were not met in a dialog window
that must be confirmed. If the diagnostic system cannot determine the translat-
ed text, it will shows is precondition constants instead. If a flash sequence that
cannot be performed using the available data is defined for a control module,
the flash procedure will be canceled and a note will indicate this. If the proce-
dure is not canceled, you will be asked if the logging should be done in the ex-
isting log or in a new one. A progress dialog appears after the flash procedure
is started. It contains information about the overall progress of the flash proce-
dure (as a progress bar) and additional information. If you press the "Cancel"
67
button, the procedure will be canceled at the next possible moment. If it cannot
be canceled immediately, you will be informed about the cancellation in a sta-
tus report. If errors occur while flashing, they will be logged and the overall
procedure will continue to the end. The exception here is a flash procedure with
a flash sequence. If an error occurs while flashing a control module that is
specified in a flash sequence, the rest of the flashing procedures defined in the
sequence will be canceled. After the completed flash procedure (even if it is
canceled), you will be asked if all DTC memory entries in all control modules
have been deleted. A results dialog is displayed after the entire flash proce-
dure is completed. It shows the number of containers that were flashed unsuc-
cessfully and the number that were not as well as the flash procedures that
were canceled. The log can also be displayed using the "Display log" button (in
the side bar). During the flash procedure, information about the flash process is
automatically added to the results log and saved after each container is com-
pleted. If a new log file was created for the flash procedure, the file name will
be selected automatically as follows:
Flashing_<VIN>_<time stamp>.xml
The time stamp is in the format yyyymmddTThhmmss.
Programming Information
The application displays the programming information that was detected for
service 22 control modules. The results are displayed as a raw value in the first
line of the programming information (F1DF) for service 22 control modules.
Depending on the raw value, other lines may show:
 "Program available"
 "Program deleted"
 "Program consistency reserved"
 "Cannot be programmed according to flash specifications"
 "Can be programmed according to flash specifications"
Parallel Flashing
DKF2 control modules that have a KWP control module as the master control
module cannot be flashed in parallel.
The parallel flashing is controlled by an external flash control file that you link
to manually in the application. You can select the flash control file using the
"Local flash file" selection in the Flashing diagnostic function. If you select a file
with the extension ".xml", it will be interpreted as a flash control file. If such a
file was imported successfully, the flash file data that is read will be displayed
in the control module list for this view. If the file is faulty, there will be a de-
tailed error description instead. After importing successfully, the flash proce-
dure can be started using the "Start quick flashing" button. The progress of the
68
flash process is shown. You can have other procedure details displayed using
the "Details" button.
Please note that:
The application does perform a plausibility test, but it does not check the con-
tent for technical accuracy. You are responsible for the flash control file that is
created and linked.
The attachment34.2 contains a brief description of the structure of a flash file.
21 Read Entire System

The "Read entire system" function is started using the entry "047 - Read entire
system" in the "Vehicle functions" section of the "Control module list" view func-
tion navigator. After selecting the function, the view "FZG - GSA" opens, in
which all control modules are shown in a tree structure with their fault entries.
The tree contains the following information:
 Control module (column header: "System")
 Number of fault entries (column header: "DTC")
The "System" column also contains checkboxes that can be used to select or
deselect control modules. If a control module is selected, it also applies for the
sub-systems that it contains. Sub-systems cannot be selected separately. All
control modules can be selected or deselected at once using the checkbox in
the table header. If all control modules are selected, the checkbox will contain
a check mark. If only some control modules are selected, the checkbox will con-
tain a filled square. If no control modules are selected, the checkbox will be
empty.
You can switch to the DTC memory view for each specific control module that is
displayed. To do this, double-click on the corresponding line. The DTC memory
content for the selected control module is displayed in a new tab.
There are two buttons ("+" and "-") below the tree that can be used to expand
or collapse all of the elements in the tree. If only a specific element should be
collapsed or expanded, this can be done using the small arrow in front of the
element. If there is no arrow, there are no sub-elements for this element.
21.1 Equipment Level Documentation

Actions and configurations for the equipment level documentation are located
together in the "BZD" group. To configure the procedure, the desired steps can
be selected using the "DTC memory" combo box. "Read", "Read & erase", and
"Erase & erase & read" are available. Presets for the procedure can also be
selected using the "Select additional data" button. Additional settings for delet-
ing a procedure step can be selected in the Administration area.
69
The equipment level documentation always diagnoses all coded control mod-
ules in the gateway components list in the vehicle to be tested. If there is no
gateway components list, the maximum potential control module installation
according to the MCD project is diagnosed.
When the procedure starts, a dialog for checking the protocol data opens. In
this dialog, you can select or enter the user name, the measurement location,
the measurement type, the VIN, the vehicle number, and the mileage. The user
name and mileage are required. The VIN and vehicle number are optional. If a
vehicle number is entered, it must be 11 digits on. Otherwise, it will be consid-
ered invalid and there input field will be highlighted in red.
After the process has run, detected faults are displayed under the affected con-
trol module in a hierarchy structure. The fault entries consists of the following
components:
 With UDS/KWP, the SAE code (if available), otherwise the fault code
 The fault type with KWP in decimal format
 The fault text
 In parentheses: the fault type in text format, static/sporadic with KWP, ac-
tive/passive with UDS
The equipment level documentation results can be added to the BZD log as
well as to the results log under the "Log" category using the "New" and "Add"
buttons in the expanded side bar.
21.2 DTC memory

The DTC memory procedure can be configured in the "DTC memory" group
and in the control module tree. The DTC memory procedure is only based on
the control modules that are selected in the tree. The control module selection
with the following entries can be changed in the "Control module selection"
combo box.
 "All control modules": selects all control modules and prevents the selec-
tion from being changed manually.
 "Selected control modules": allows the control modules in the tree to be
selected manually.
 "OBD-relevant control modules": selects all OBD-relevant control mod-
ules and prevents the selection from being changed manually.
The procedure that is performed for the DTC memory is defined using the "Pro-
cedure" combo box. "Read", "Read & erase", and "Erase & erase & read" can
be selected.
Using the "Repeat in cycles" checkbox, the function is repeated at regular in-
tervals after starting. The time between cycles can be set in Administration in
under "Cycle for repeating the process [s]" in area "Read entire system" on the
70
"Vehicle functions" tab. The time interval specification refers to the time that
passes between the start of a cycle to the start of the next cycle. If the time in-
terval is less than the time needed to read the DTC memory, the next cycle will
begin as soon as a cycle ends.
The buttons and configuration options are deactivated when the execution cy-
cle is active (function was started with the checkbox selected). The "Start proce-
dure" button changes to "Cancel" and remains an active button. The execution
cycle can be ended using the "Cancel" button.
Presets for the DTC memory function procedure can be selected using the "Se-
lect additional data" button.
The vehicle function results can be added to the results log under the "Log"
category using the "New" and "Add" buttons in the expanded side bar.
Administration
Additional settings for both the DTC memory and Equipment level documenta-
tion functions can be specified in Administration under the "Vehicle functions"
tab in the "Read entire system" area. You can also specify if OBD control mod-
ules should be erased and if there should be a physical erasing at the end
(control modules that cannot be erased using functional erasing are erased
anyway). The physical erasing can be delayed by entering a delay time.
The time between two DTC memory accessing cycles can also be set.
Another setting allows additional presets to be deactivated (see the following
chapter).
Selecting Additional Data

You can select additional data to be integrated into the operating process for
the Equipment level documentation and DTC memory functions using the "Se-
lect additional data" button. Pressing one of the buttons opens a dialog for se-
lecting presets. The dialog contains four tabs, "Adaptation", Measured values",
“Expanded identification”, and "Addition presets", where the additional data
for the Adaptation, Measured values, and Identification diagnostic services can
be specified. The additional data can be selected using checkboxes in each
tab.
The tab for the measured value presets contains the checkbox "Read only if
there are faults" below the table. If this checkbox is activated, control module
measured values will only be read if there are faults.
The "Additional presets" tab displays measured values and identification pre-
sets. The presets displayed are taken from the folder "bzd_logs/presets". If ad-
ditional presets are added to this folder, they will be selected automatically.
71
The use of additional presets can be deactivated completely using the Admin-
istration settings.
The measured values that were read during the process due to the measured
value presets are also displayed in the tree structure. The sub-element "Meas-
ured values" is added below the control module where a measured value was
read. It contains elements for the individual measured values that were read,
which consist of the measured value names and the value that was measured.
The adaptations that were read out in the procedure based on the "Adapta-
tion" presets are displayed in the "Adaptations" child element, similar to the
measured values.
21.3 Displaying and Comparing Logs

The "Display/compare logs" button gives the option of displaying and compar-
ing logs. A corresponding dialog opens for this. The logs generated by the
"Read entire system" vehicle function are displayed in the dialog in two tree
structures. The first level of the tree contains the categories "Log (local)" and
"Log (download)". The protocols are arranged below as sub-elements. One log
can be selected in each tree for comparison. If a log is selected in each of the
trees, they can be compared using the "Compare logs" button. There is also a
"Display" button of reach of the trees. This allows you to display the selected
log for each tree. The log displays in the computer's default browser. The se-
lected logs in the right selection list can be deleted using the "Delete" button
below the right log tree.
The “Download from VDS” and “Download from AVx” buttons activate the
download functions already stored in the VDS or AVx logs. The user is authen-
ticated in the respective system using a PKI smartcard. If access is not possible
with this card, a notification dialog will ask you to insert the card and enter its
PIN. After connecting successfully, another dialog for downloading externally
stored logs appears. You can check for available logs in the respective system
and have them displayed in a list by entering the 11-digit vehicle number and
additional optional search criteria if desired and then clicking the "Search" but-
ton.
The following optional search criteria is also available when searching for VDS
logs:
 Time period specified as start and end date
 Measurement location
 Measurement type
The logs that are found are selected using a checkbox in the selection list and
downloaded using the "OK" button. The logs are stored in the
"bzd_logs/download" folder in the ODIS Engineering installation path and are
then available in the "Display/Compare" dialog.
72
The "Cancel" button ends the dialog.
21.4 Sending Logs

The "Send logs" function can be accessed using the button for this as well as
the "Send log" button in the side bar in the BZD section. This last option for ac-
cessing the function is also available when there is not connection to the vehi-
cle.
The "Send logs" function sends a list of logs. A dialog opens for this. The loca-
tion where the logs will be sent and the logs to be sent from the "bzd_logs"
folder can be specified in the dialog.
The location where the logs will be sent can be specified using checkboxes in
the "Send location" group. The following send locations are available:
 File server
 Carport
 VDS
 AVx
 E-mail address
The path to the file server can be specified using an input field or can be se-
lected using the "Selection" button and a file selection dialog.
If sending logs by e-mail is selected, an e-mail opens in the default e-mail pro-
gram opens when sending. The logs to be sent are compressed into a ZIP file.
The subject line of the e-mail is "BZD/VDS logs: <log names>". "<Log
names>" is replaced with the names of the logs to be sent, separated by com-
mas. If there are more than two logs to be sent, "..." will be added to the sub-
ject line. An error message is shown if there is no default e-mail program. If the
logs are only sent by e-mail, they are not deleted after sending.
The available logs are displayed in a table and are sorted in ascending order
based on their names by default. Clicking on the header line changes the sort-
ing from ascending to descending and vice versa. All logs can be selected or
deselected at once using the checkbox in the table header. If all logs are se-
lected, the checkbox will contain a check mark. If only some logs are selected,
the checkbox will contain a filled square. If no logs are selected, the checkbox
will be empty.
If only the VDS, AVx and/or Carport send locations are active, logs that were
already transmitted successfully to these locations are not displayed.
Selected logs can be deleted by pressing the "Delete" button. The delete func-
tion can also be performed using the "Del" button if the log table has the focus.
The deletion process only runs after a security prompt in a confirmation dialog.
The option "Yes" (confirming the deletion) is preselected. With the option "Yes
and archive", the selected logs are moved to the "history" folder. When this
73
happens, the application considers the logs to be deleted, but they can still be
reached in the file system.
You can filter the logs using the "Filter" input field. If filter text is entered, only
logs that contain this text in their names are displayed. The number of filtered
logs is shown in the format "x of y log(s)" in an output field to the right of the
filter input field. "x" and "y" are replaced with the respective numbers. The log
filtering field is empty by default so that all logs are displayed.
With the "Open save location" button, the "bzd_logs" folder that contains the
logs opens in Windows Explorer.
You can compare two logs with each other using the "Compare" button. The
button is only active when two logs are selected.
The logs that were previously selected can be sent to the selected send location
using the "Send" button. Only visible and selected logs are sent. If sending to
VDS is activated, the system checks if an internal vehicle number was specified
for each selected log before sending. If there is no number, a dialog for speci-
fying one opens. If Carport is selected as the send location, another dialog for
entering the action code appears before sending.
Logs that were transmitted successfully to VEDS and all other send locations
are deleted. The deletion process only runs after a security prompt in a confir-
mation dialog. The deletion can be confirmed or canceled in the confirmation
dialog. Deleting with archiving can also be selected. When this happens, the
application considers the log to be deleted, but it is still located on the hard
drive in the "bzd_logs/history" folder.
A log is considered to be sent to VDS successfully if the VDS server confirms it
with the status "OK".
After transmitting the logs, a dialog appears that contain any errors that may
have occurred.
Vehicle Number Input

The dialog for entering the internal vehicle number for a VIN opens only once
when sending. If there are more logs without an internal vehicle number but
with a VIN that was already retrieved, the number specified there is automati-
cally entered without opening the dialog again.
In addition to the log names, the dialog also contains the VIN from the log. You
can enter the internal vehicle number in the "Vehicle number" input field. It
must be exactly 11 digits long. Otherwise, the input will be invalid and the field
will be highlighted in red.
The "OK" button sends the logs and the dialog closes. The button is only active
if a valid internal vehicle number was entered.
74
The "Cancel sending" button completely cancels the sending of the logs. No
logs are deleted or sent and the internal vehicle number request is not per-
formed for any other logs.
Action Code Entry

If the "Carport" send location is selected, another dialog for entering the action
code appears before sending. The window for entering the action code is "Ac-
tion code input". You can enter an action code in a one-line text field in the
"Action code input" window. Only letters (A to Z) and numbers can be entered
in the action code input text field. Letters entered in the action code input text
field must be upper case. If the text field for entering the action code is selected
and empty, it will be marked as invalid and highlighted in red. The actual send-
ing process can only be started (by activating the "OK" button) when an action
code has been entered.
Results Display for the Sending Process

After transmitting the logs, a dialog appears. The dialog provides information
about the number of logs that were sent successfully. It also shows a list of logs
that were not transmitted successfully. The detailed view for the dialog shows
the error message for each log that was not transmitted successfully. This mes-
sage contains the response from the VDS server, the AVx server and the Ser-
vice42 server.
21.5 Equipment Level Check

After pressing the "Equipment level check" button, a dialog field that contains
two lists displayed next to each other for the available BZD logs and the avail-
able installation specifications is displayed. The "Equipment level check" func-
tion can also be reached using the "Data" button in the side bar as an entry in
the menu that is expended, without being connected to the vehicle. The list of
available logs from the "bzd_logs" folder is shown in the left area of the dia-
log. Each log can be selected individually using a checkbox. Multiple selections
are not permitted for an installation check.
A button to "Delete" the selected logs is located under the log list. The list of
available installation specifications from the "bzd_logs\VBV" folder is shown in
the right area of the dialog. Each installation specification can be selected indi-
vidually using a checkbox. Multiple selections are not permitted for an installa-
tion check.
A button to "Delete" the selected installation specifications is located under the
installation specification list.
There are two buttons for loading additional installation specifications from
System 42 or from a local folder ("Load from System 42" and "Load from fold-
er") are located to the right of the installation specifications list. To import an
75
installation specification, a dialog opens for you to log in and to select the ve-
hicle project and the installation specification. After loading the installation
specification from System 42, it is stored in the "bzd_logs\VBV" folder and is
automatically entered and preselected in the selection list.
Press the "Load from folder" button opens a file selection dialog with VBV files
(*.xml) preselected. After selecting an installation specification in the file system,
it is stored in the "bzd_logs\VBV" folder and is automatically entered and pre-
selected in the selection list.
After pressing the "Check installation" button, the results of the equipment level
check (comparison of the selected BZD log with the selected installation specifi-
cation) are displayed in the default browser.
22 Copying Coding / Adaptation

In this results view called "FZG-CDA", you can copy coding that has been read
or adaptations into other control modules. The information from one or more
control modules can also be copied.
The view contains the following buttons for this:
 "Read data"
 'Load data"
 "Write data"
A "Read KWP control modules" checkbox that is selected by default is located
below the buttons. If the selection is erased, no KWP control modules are read,
regardless of the selection in the control module list.
The "Adaptation" and "Coding" checkboxes (group name: "Data from all con-
trol modules") are located in the lower right area of the view. Selecting one of
the checkboxes removes the selection from all control modules in the list.
The left area of the view contains a list of all control modules that can be cod-
ed/adapted. All coded control modules are listed in a hierarchy in the "System"
column.
In the second and third columns, "Coding data" and "Adaptation data", icons
indicate if template data is available for this control module. The symbols used
have the following meanings:
Green check mark: all control module parameters can be written, meaning the
data contains the same number of parameters or fewer as the data set that is
loaded.
Yellow warning sign: the data that is loaded matches only parts of the ODX
data, meaning the control module parameters may be incomplete after writing.
76
Red diagonal line: the control module is completely missing in the data that is
loaded or in the vehicle in the ODX data.
In the fourth column, "Data selection", you can select which specific information
should be read or written for a control module using a drop-down list:
 Adaptations
 Codes
 Adaptations and codes
You can restore the selection using the "- Delete selection -" entry. If this hap-
pens, there will be a blank entry in the table.
Examples:
Writing the code for the engine was already individually selected. When se-
lecting the checkbox for adaptations, the entry for the engine is changed to
"Adaptation and codes". Only the adaptation is selected for all other control
modules.
"Adaptation and codes" is already selected for the engine. The checkbox for
codes is already activated and will now be removed. The selection for the en-
gine then changes to "Adaptations".
"Read Data" Function

If the data to be read for one or more control modules was selected using the
drop-down list, the data for the selected systems can be read using the "Read
data" button. The status display for any data that may be loaded is reset when
reading and the data that was read is discarded. A default results log that con-
tains the coding and adaptation information is automatically created when the
reading process starts. The log is automatically saved after the reading pro-
cess.
"Load Data" Function

To prepare information for a later writing process, it will be read from a results
log created with the preceding function. When the "Load data" button is
pressed, a dialog box for selecting the desired results log opens. When read-
ing, the last entry for adapting or coding for each control module is used as a
basis for the subsequent writing process.
The available information is displayed in the "Coding data" and "Adaptation
data" columns as described above.
"Write Data" Function

After a possible preselection of the control modules to be described, the writing
process can be performed using the "Write data" button. If the vehicle to be
described does not contain all of the control modules that were selected previ-
77
ously in the selection list (for example, the selection list generated from a log
for another vehicle), then the extra information will be ignored. The system will
also check of the target control modules are compatible with the code to be
written. The check is based on the VW/Audi part numbers (software part num-
bers). If the condition is not met, various versions of the dialog box will be dis-
played for each control module, where you can skip or perform the writing
process.
Using NRCs for Access Authorization and Diagnostic Session

If access authorization to a control module is needed in the "Copy cod-
ing/adaptation" vehicle function, you have the option to cancel this input or to
combine all further requests under one access authorization for this control
module. Only the adaptation values that can be read are included in the log.
Adaptation values that could not be determined due to an NRC are not includ-
ed in the log for the "Copy coding/adaptation" function.
23 Coding component lists

Coding the Gateway Components List for KWP 2000
For a KWP2000 gateway, the current condition cannot be determined in com-
parison to a UDS gateway. Because of this, the view for coding component lists
is available, however with the following two limitations:
 Only one "Optional installation" is shown in the "Actual" column (meaning
the control module is not coded but the gateway did find it in the vehicle).
 The "Code automatically" button is not displayed here, because the definite
equipment level could not be detected.
Coding UDS Bus Masters (Gateway)

Coding a UDS bus master (gateway) is handled differently, because this func-
tion requires an overall view of the control modules. The assumption is that
multiple bus masters may be present in a vehicle project.
If the bus master supports logical units/software clusters, the separate cluster
components lists will be detected by the control module and integrated into the
displayed components list. Also, any changes that are made to the specified
components and during automatic coding are adopted during writing.
Coding subsystems
With the coding sub-systems function, the code status of sub-systems can be
changed. If the function is supported by the control module, it can be opened
with the navigator function tree.
78
23.1 Opening the coding component lists function in the "Con-

trol Module List" View
To code component lists, the function "006 - Coding" function in the function
navigator has three sub-functions:
 A bus master components list is coded by selecting "006.03 - Coding bus
master" ("BMC" suffix).
 Coding a KWP2000 gateway is done with the "006.04 Coding component
list" function ("BMC" suffix).
 Coding of sub-systems for a control module is done through the "006.05
Coding sub-system" function.
23.2 Components List Displays

Coding the components list for a bus master is done in its own view. The coding
information view is laid out as a table with four column and the following
headers:
 Target
 Current
 Control module
 Warranty Info
The information for the control module actual installation based on the control
module that is displayed is shown here. This is done using the symbols shown in
the table below which identify the "coding status".
Control module Control module Control module Control module

Symbol
present present not present not present
not coded coded not coded coded
✔(green) X
? (gray-
X
blue)
! (gray) X
Tool tips provide more information on the symbols shown.
79
"Specification" Column
After reading out, there is a checkbox in each line of the "Coded" column that
indicates if the control module is coded or not. You can select and deselect the
checkbox.
"Control module" Column

The "control module" column contains the list of control module addresses with
the associated system names (for example, 01 - Engine electronics). If no con-
trol module address is allocated to a system, the node address is displayed in
hexadecimal format and in brackets with the associated system names (for ex-
ample, [42] - Left rear door control module). The node address 0x00 is not
displayed. If the system name for a control module address or a node address
is unknown, then the entry is described as follows:
 Control module address + text [unknown system] (for example, 0000 -
Unknown system).
 Node address + text [unknown system] (for example, [0049] - Unknown
system).
For software clusters, the “Function ID” is added to the entry in parentheses (for
example [C002] - Software Cluster Embedded 1 (0028)).
“Warranty Info" Column

This column contains the following information for gateway components lists:
 GatewayComponentList BusIdentifier (0x2A2D)
 GatewayComponentList DiagProt (0x2A29)
If no value is returned by a service (for example, reserved values or an NRC),
then this value or NRC will not be displayed. If values are returned from both
services, then the responses will be shown next to each other and separated by
" / " (for example, CAN powertrain / ISO TP). The bus identifier is listed first.
For sub-systems, it is displayed in this column of the respective control module
bus (0x061B)
This column remains empty for software clusters due to missing information.
Table Sorting Function

All columns can be sorted in ascending and descending order either alphabeti-
cally or based on status. The order in the "Actual installation" column is not
coded/detected above coded/not detected above coded/detected control
modules. The default sorting for tables is sorting by the control module installa-
tion status and then alphabetically based on the diagnostic/node address.
When sorting alphabetically based on system names, unknown system names
are all the way at the bottom.
80
Any software clusters that are detected are also integrated into this described
sorting order, which can result in a mixed display of component lists and soft-
ware cluster components.
23.3 Button Function

There are up to four buttons in the right section of the results view:
"Accept" Button
The "Accept" button copies the coding based on the selected control modules
into the "Specification" column. Pressing this button opens a confirmation dia-
log: "The coding will be performed based on the "Specification" column. Are
you sure you want to perform the coding?". The input focus is on "Yes" by de-
fault. When confirmed, the coding is performed based on the "Specification"
column in the results tab and then the results view is updated.
"Restore" Button
The "Restore" button, which is only active when the actual status differs from
the original status, restores the original coding status and then updates the re-
sults view.
"Code Automatically" Button

The "Code automatically" button writes the code based on the sub-system
components detected from the control module, meaning the code is written for
all control modules that are marked with the symbols "?" and "✔" under "Actu-
al". Pressing this button opens a confirmation dialog. The display text reads:
“The subsystem installation status detected by the control module will be coded.
User-defined changes will not be transferred. Do you really want to perform
the coding?”. The input focus is on "Yes" by default. After a successful response
from the control module, the coding information is read out again and shown
in the display area.
"Update" button
Using the "Update" button will read out and display the current installation
again.
23.4 Coding the Entire Vehicle Components List Automatically

The "Vehicle functions" area in the "Control module list" view function naviga-
tor contains a function that detects all bus masters in diagnostic class 4 in the
vehicle function and updates the specified components lists based on the read,
detected actual installation. This function is initiated using the "Code compo-
nents lists" button.
81
Starting the function unintentionally can create unnecessary extra work. To pre-
vent this from happening, a confirmation dialog that notifies the user about the
upcoming action is shown before performing the action. The user is given the
choice of performing the action or canceling it, if it was started unintentionally.
Performing the function does not display a control module list results view with
more detailed information about the installation status. During processing, only
one progress dialog and then one results dialog is shown. When processing
these vehicle functions, only the installation status specification coding is
changed in the control module. Other coding/adaptation values are not af-
fected by this function and they remain the same.
24 OBD
A "Service OBD" vehicle function is provided in ODIS for checking the OBD
components in the vehicle. This chapter describes both the required implemen-
tation in the graphic interface and the diagnostic services that are needed to
carry this out. The generic ODX data that is available is used for implementa-
tion of OBD functions. The system displays the list of supported functions after
determining which functions are supported. You can select from this list which
diagnostic functions in the vehicle should be performed. For modes 0x01
through 0x0A, information about which services should be performed in which
order and displayed in the form of results views is described for each individu-
al mode.
24.1 Accessing the OBD Diagnostic Function

The ODIS Engineering application shows the OBD diagnostic function as a ve-
hicle function in the control module list diagnostic function tree (040 - Service
ODB). The results tab for the OBD diagnostic function is initially marked with
the code "OBD". A dollar symbol and the applicable OBD mode ID is added to
the code once you have selected and run an OBD mode. The results view is
displayed as a wizard view.
24.2 Service OBD View – FunctionSelection

The application detects either by K line or via CAN if the vehicle supports OBD
services by checking which protocol the vehicle uses to respond to mode 01,
PID 00. If the vehicle does not respond either by CAN or by K line, the applica-
tion shows that the vehicle does not respond to OBD functions in the results ta-
ble. If the vehicle project data is not populated with OBD functionality, the ap-
plication will show that there is no suitable OBD data. If the connection was
established successfully, the application lists the functional groups used in the
services results table, based on their name from the MCD project. The executa-
ble OBD modes are selected by clicking on them. The application displays
modes that are not populated in the vehicle data in gray under the expected
82
mode name. The entire line is click-sensitive. If you click on the right wizard ar-
row after selecting a mode, the application runs the selected OBD mode. Dou-
ble-clicking on the line for the desired OBD service runs it immediately.
24.3 Supported Functions Display

The vehicle checks the functions supported by the vehicle for modes 01, 02, 05,
06, 08, and 09. It displays the functions supported by the vehicle in a list. If no
control module gives a positive response to the check for supported funs, the
application displays a message: "No control modules have reported a sup-
ported function for this OBD mode". The "Show all" checkbox allows the unfil-
tered list of functions to be displayed regardless of vehicle responses. The en-
tries in the list that the vehicle has reported as not supported are displayed in
gray. Entries in the list that are reported as not supported can be selected. The
application offers the option to filter functions below the list of supported func-
tions.
24.4 OBD Results Display

The application shows a table in the results view. The responses to a parameter
request are displayed one after the other in the table. This is done grouped by
hierarchy one level below the parameter name in ascending order based on
the control module addresses of the control modules that respond. If the control
module implementation is faulty, the control module may not send a response
for a function even though it has been reported as one of its supported func-
tions. You will be informed of this error. The application shows the message
"No response from control module". The opposite case is also possible. In this
case, the application displays the message "Control module reported a result,
but it does not support the function" above the control module response. You
can control the updating of the view using the standard controls in the "Up-
date" group.
You can set the cycle times for all OBD services in the "OBD services" Admin-
istration group. You can use the checkbox "Read in cycles" to specify if the
reading should occur in cycles by default.
24.5 Process for Various OBD Services

24.5.1 Mode 01 - Check Current Diagnostic Data
The application determines all of the PIDs that can be checked in the vehicle in
the step "Supported functions display" and displays them. The standard filter
and sorting functions are available to provide a more clear overview. After se-
lecting the PIDs to be displayed, the data from the selected PIDs will be detect-
ed and displayed in cycles in the “OBD results display” step.
83
24.5.2 Mode 02 - Request Powertrain Freeze Frame Data

The application determines the PIDs that can be checked in the vehicle in the
step "Supported functions display and displays them. All data about the PIDs
you have selected in the step "OBD results display" is detected in cycles and
displayed.
The application detects the number of DTCs stored in the control modules. The
application then determines the DTCs stored in the vehicle. If the number DTCs
detected for at least one control module using Mode 01 - PID 01 does not
match the number of DTCs detected with Mode 03, the application will give an
error message. The error message shows all control modules with the reported
number of faults and the number of DTCs detected, if they do not match. The
DTCs are displayed in groups based on control modules. The results parame-
ters themselves are displayed in hierarchical order. The control modules are
sorted in ascending order based on their control module address. The control
module is displayed as the highest hierarchy element in the group with the
name control module address - control module service name.
24.5.4 Mode 04 - Erase DTC Memory
If you run the Clear/Reset Emissions-Related Diagnostic Information function
without checking mode 03 since the start of diagnosis, the application shows a
warning message in a modal dialog:
The DTC memory has not been checked yet.
The number and content of the DTC memory operating conditions and test re-
sults will be deleted.
Do you want to continue?
Otherwise, the first line of the warning message above will be omitted. The
"Erase" button in this dialog performs the erasing process, and "Cancel" ends
the operation. If control modules respond with NRC $22 (Conditions not Cor-
rect), the following dialog that must be confirmed appears: "At least one con-
trol module has reported that the requirements for erasing have not been met.
Switch the engine of and the ignition on.". This dialog also shows the responses
for all control modules. If all control modules give a positive response, a mes-
sage that reads "Diagnostic data was erased in the following control modules"
appears, and it lists the control modules that gave a positive response. After
performing mode 04, the application returns to the "Accessing OBD modes"
view.
24.5.5 Mode 05 - Request Oxygen Sensor Monitoring Test Results
The application determines all of the TIDs that can be checked in the vehicle in
the step "Supported functions display” and displays them. In this mode, there is
84
an additional step similar to "Supported functions display", where you select

the sensors whose measurement results should be displayed. In the "OBD re-
sults display", the application displays all data about the TIDs and sensors se-
lected by the user. This is done in cycles.
24.5.6 Mode 06 - Request On-Board Monitoring Test Results for Specific
Monitored Systems
The application determines all of the TIDs or OBDMIDs that can be checked in
the vehicle in the step "Supported functions display" and displays them. The
decision about whether TIDs or OBDMIDs are available for selection depends
on the OBD link that is used. The standard filter and sorting functions are
available to provide a more clear overview. After selecting, the data from the
selected TIDs/OBDMIDs will be detected and displayed in cycles in the “OBD
results display” step. You can switch between updates in cycles and manual
updates using the “Cycle” checkbox.
Detected During Current or Last Completed Driving Cycle
The application detects the DTCs stored in the vehicle. The results view shows
the DTCs grouped according to control module. The control modules are sorted
in ascending order based on their control module address. The control module
that is reported is displayed as the highest hierarchy element in the group with
the name control module address - control module service name. The DTC con-
tent is displayed in hierarchical order, the same way the measured values are
displayed.
24.5.8 Mode 08 - Request Control of On-Board System, Test Or Compo-
nent
The application determines all of the TIDs that can be checked in the vehicle in
the step "Supported functions display" and displays them. In contrast to the
usual behavior, the application only allows you to select a single TID. In the
"OBD results display", the application displays all data about the TID you have
selected in cycles.
24.5.9 Mode 09 - Check Vehicle Information
The application determines all of the INFOTYPEs that can be checked in the
vehicle in the step "Supported functions display" and displays them. After an
option to select the INFOTYPEs that should be displayed, where the standard
functions are offered for filtering and sorting, all selected data about the IN-
FOTYPEs you have selected in the step "OBD results display" is detected in cy-
cles and displayed.
24.5.10 Mode 0A - Checking the Permanent DTC Memory
The results view shows the DTCs grouped according to control module. The ap-
plication sorts the control modules in ascending order based on their control
85
module address. The control module is displayed as the highest hierarchy ele-
ment in the group with the name control module address - control module ser-
vice name. The DTC content is displayed the same way as the measured values,
in the columns measured value name, value, and control module address. All
results parameters are displayed in hierarchical order.
25 Running GFF Scripts

Using script functions allows Guided Fault Finding (GFF) function tests to run.
The central initial view for running GFF scrips is the vehicle features dialog,
which can be reached in several ways:
 Pressing the GFF button in the Diagnosis area in the side bar in the initial
view (with no project loaded) opens a VIS entry via the VWVIN vehicle pro-
ject and the vehicle features dialog is displayed after diagnosis starts.
 Pressing the GFF button in the Diagnosis area in the side bar in the control
module list (with a project loaded) opens a dialog that provides an auto-
matic start of diagnosis in "Service” (and “Cancel”). If confirmed, VIS entry
via the VWVIN vehicle project runs and the vehicle features dialog is dis-
played after diagnosis starts. If declined, the project remains loaded and
the vehicle features dialog is displayed.
 Opening "Guided Functions" in the "Diagnostic processes" area of the func-
tion selection from the control module list displays the vehicle features dia-
log immediately.
25.1 Vehicle Features Dialog

Variants and basic features can be entered in this dialog that allow the use to
display the filtered knowledge base as a components list. It contains an input
field for the vehicle VIN and a selection menu for the manufacturer, the model,
the model year, the variant, and the vehicle engine. The selection menus are
activated and populated based on the content of other selection menus.
25.2 Script Selection

Accepting the vehicle features opens the results view in the "GFF-BTL" tab,
where the knowledge base filtered based on the variants detected and the
basic features entered is displayed as a components list. The scripts contained
in the application's internal database (DIDB) are displayed in the selection list
in this view. A GFF scrip selected here is started using the "►" button. The but-
ton with the folder symbol opens a file dialog for an external directory. A GFF
script selected here is run immediately after the file dialog button is pressed.
The default path for the external directory is set in the Administration area
(save locations).
86
25.3 Running Scripts

After selecting and starting a script, another tab, "GFF-RUN", is displayed. It
provides the same operating options as Guided Fault Finding in the Offboard
Diagnostic Information System Service. A test procedure can be ended early
using the "Cancel test" button. Closing the "GFF-RUN" view or switching to the
"GFF-BTL" view during the test procedure is not possible. This button becomes
inactive if a running script is stopped. It is then possible to close the "GFF-RUN"
view or switch to the "GFF-BTL" view. The default log for Guided Fault Finding
is used to log the script process.
The "Save diagnostic log" button in the "GFF-BTL" list stores it in the location
specified in the Administration area (save locations).
Note: In the Administration area, the initial path for diagnostic logs is main-
tained as the default path, and it is not visible and cannot be changed. Logs
are always stored there. If the path displayed in the Administration area is
changed, the diagnostic logs will also be stored in that location.
Note: diagnostic logs saved in the default location are automatically deleted
after 30 days.
26 Macro Function
The ODIS Engineering operating processes can be recorded, saved, and run
again automatically using the macro function. This allows the user to record
recurring operating processes and have them run automatically later. Macros
are recorded and run using the corresponding buttons in the side bar. They
can also be run using an entry in the function navigator in the "Control module
list" view, under the section Diagnostic processes. The user's actions themselves
within the results views and dialogs are not recorded, but rather these activities
are transformed into action sequences for a software interface in the applica-
tion.
Macro Recording
The side bar contains a group of buttons for controlling macro recording. The
“●” button (record) starts recording the user actions that follow. When it is
pressed, a file selection dialog appears first where you can specify the file
name for the macro to be recorded. The directory set in the Administration ar-
ea (Save locations) is preselected as the path. You can also create sub-
directories in this directory and save the macro there. After ending this dialog
with "OK" all of the user's actions that lead to a diagnostic action are record-
ed. The “▐▐” button (pause) pauses the recording. The user actions that follow
are not recorded. The “●” button (record) can be used to resume recording. The
“■” button (stop) stops the recording and closes the macro file.
87
Running a Macro
Macros are run by selecting the "Macro" entry in the function navigator in the
"Control module list" view (in the Diagnostic processes area) or using the >
("Run") button in the macro area in the side bar. A few with the tab "FZG-
MAK" opens. The view contains a list with all macros that are located a directo-
ry that is specified in the Administration area (Save locations) and its sub-
directories. You can select a macro to run here or in any sub-directories that
may be present. After selecting a macro, the “►” button (start) runs the macro.
It can also be run using the "ENTER" key on the keyboard.
The “☼” button (debug symbol) starts running the macro in the individual steps in
the debugger. When it starts running, a window for controlling macros that co-
vers the application's main window opens. During the time that the macro is
running, no user actions that are reached using the main window are possible.
The appearance of the macro window may differ depending on the process
mode (normal or debug mode). In both modes, you receive feedback about the
macro process in a console window. The output from the macro is displayed
here, and the notification when the macro ends. Depending on the reason for
ending the macro, the message "macro execution finished" may appear if the
macro has run until the end, and the message "macro aborted by user" may
appear if the running was canceled by the user. You can control the macro
process using a group of buttons. In both modes, the buttons
►: ("Start"): normal macro process,
▐▐: ("Pause"): pauses the macro process,
■: ("Stop"): stops the macro process
x: close window (only active when no macro is running),
and a drop-down list for selecting the running speed are present. The time in-
terval between running macro steps can be set in this selection list. Pressing an
editing button loads the macro in an external editor for editing.
In normal run mode, the window contains the ☼ button (bug symbol) that al-
lows you to switch to debug mode. In debug mode, the console display is shown
minimized in the lower area of the window. The source text for the macro is also
displayed in a text field. The last lines edited are highlighted. To the right of
that is a list with names and values for the macro's local or global variables.
Instead of the "Debug" button, the "Single step" and "Animate" buttons are
visible in this view. The macro can be run here in individual steps or animated
with the selected time interval. The individual step control is initially active when
switching from normal running mode to debug mode. The following buttons are
available in debug mode:
88
"Individual Step" Button

Pressing this button performs exactly one step in the macro.
"Animate" Button
Pressing this button runs through all of the steps in the macro at the set speed
and shows the process. Pressing "Individual step" returns to individual step
mode.
"Run" Button
Switches back to normal mode and the debug window closes. The current
mode (individual step or animation) is resumed when switching back to debug
mode.
"Stop" Button
Ends the macro process (canceled).
"Close" Button
Closes the debug window (only active after ending or canceling the macro).
Notes:
 Macro control occurs at the macro command level. That means that a diag-
nostic function triggered in a macro step is completed before a "pause" re-
quest goes into effect.
 In individual step mode, the marking for multiple steps may remain in the
same line. This happens when a line consists of multiple sub-expressions (for
example, "for" step).
 Imported Python scripts are not displayed in debug mode. The "Individual
step" button works like "Step into" for internal function calls and like "Step
over" for external calls.
 The minimum interval between two steps in debug mode is 0.1 seconds,
even if it is set to 0.0.
 A macro that has started becomes like part of the application program
code. Errors in the macro process can therefore block the application par-
tially or fully despite the macro cancel function. This is especially true for
macros you have created yourself.
27 Trace Function
You can operate the trace function using buttons in the "Trace" section of the
side bar. The following buttons are used for this:
89
 "Record" button → The recording begins or resumes.

 "Pause" button → The recording is paused.
 "Stop" button → The recording is stopped.
 "Display" button → Displays a trace recording.
Trace File Save Location

You can select a save location for the generated trace file for each of the trace
types under "Save locations" in the Administration view (Save locations area).
The trace control sets up the file name so that existing files will not be overwrit-
ten. The file name is composed as follows:
 CAN Bus trace: <VIN>_<time stamp>_CAN.vmt
 DoIP-Trace: <VIN>_<time stamp>_DoIP.vmt
 K line bus trace: <VIN>_<time stamp>_KLINE.vmt
The time stamp is in the format <YYYMMDD>T<HHMMSS>, for example

"20100229T184556". You can deactivate or active recording for the following
trace types under "Function configuration" in the "Administration" view:
 DoIP trace
 CAN-Bus trace
 K-line trace
 Job trace
Changes made go into effect when a new recording starts.
Displaying a Trace File

After pressing "Display", a selection dialog for the trace type (bus or job trace)
appears. A file selection dialog based on the trace type selection then opens
with the respective file filter in the configured trace directory. The last recording
is selected by default. After the file selection, an external trace editor with the
selected trace file opens. The setting for the external trace editor is located in
Administration under "Function configuration/tracing".
28 Creating a Results Log

The "Log" button in the side bar opens a menu. All of the functions for creating
a results log are located here.
"New"
You can create a new results log using this function. General information, such
as vehicle information, date, and version information, are automatically stored
in the log when creating a new results log.
90
"Add"
The data from the current view/diagnostic function is copied into the log's XML
structure using this function. All additional, context-based data, such parameter
information about actuators, is also copied into the log.
"Comment"
This function opens an input dialog for entering user-specific comments. The
text comments entered are documented in the results log.
"Display”
Using this function, you can display the results log currently saved in the file
system in the computer's default browser. The "Display results log" function is
only active when the current changes are saved.
"Save"
The results log is saved in its current condition in a file under the file name that
was already specified using the "Save" function. If no file name was specified,
the "Save as" function opens the file selection dialog.
Note: In the Administration area, the initial path for results logs is maintained
as the default path, and it is not visible and cannot be changed. Logs are al-
ways stored there. If the path displayed in the Administration area is changed,
the results logs will also be stored in that location.
Note: results logs saved in the default location are automatically deleted after
30 days.
"Save As"
Using this function, you can save the results log in its current condition in a new
file. This opens a file selection dialog where the user can define the file path
and the name of the results log file. The default path set in the Administration
area (Save locations) is preselected in the file selection dialog. The application
suggest a standard file name. If there is an internal vehicle number, the file
name consists of the internal vehicle number, the current date, and the current
time. If there is no internal vehicle number, the VIN will be used instead.
29 Support Function
There is a "Support" button in the side bar for creating and send problem re-
ports. If it is pressed, an input dialog for creating a support request opens. The
input field fields for the subject and the text of the support request are availa-
ble first. The input field for the e-mail text supports clipboard functionalities for
text and graphics. The "Attach current results log" checkbox is activated if there
91
is a current results log available when the support request is opened. If there is
no results log available when the support request is opened or you have deac-
tivated the checkbox, the message "A results log is required for analysis. Do
you want to send the request without a results log?" reminds you that there is
no results log attached to the support request. Using the "Log file" checkbox,
you can attach the current available log files from the application to the sup-
port request. If the checkbox is activated, all ecf.log and engine.log files are
compressed in a ZIP file and attached to the problem report. The checkbox is
deactivated by default. Using the “VCI log files (VAS 6154/A only)” checkbox,
you can attach log files that are on the active VCI to the support request. This
checkbox is not selected by default. The checkbox is also deactivated when the
active VCI is not the VAS 6154/A.
Any number of extern files can also be attached to the problem report using
the "Add user attachments" button. If this button is pressed, various types of
attachments can be added to the support request. A standard file selection dia-
log opens for each type that is selected, and each has a preselected file path,
file name, and file type depending on the type selected. User attachments that
have been added to the support request can also be removed if necessary us-
ing a corresponding button.
Pressing the "Send" button displays a notification that the support e-mail ad-
dress stored in the Administration area (contact data in the Support tab) is cop-
ied into the clipboard. Confirming this notification opens your mail system
where the defined contents were copied into an e-mail and the support e-mail
address can be added with "CTRL + V". If the support request is not sent right
away (for example if in offline mode or if there is a sending error), it will be
stored and sent the next time it is possible. The process from ODIS Service is
used for this. In this case, you will be informed with a message. It is also possi-
ble to save a support request on the local computer in a selected location in-
stead of sending it. To do this, press the "Save" button in the support request
dialog. A save location that serves as a storage directory can be preselected in
the Administration area. The "Support" sub-folder in the ODIS directory is se-
lected by default. If there is not enough storage space there, you can select if
the saving process should be repeated (after freeing up storage space on the
data carrier), or if the data should be saved in a different location. In the sec-
ond case, a file selection dialog asks for the desired save location. If no e-mail
client is set up, pressing the "Send" button will save the support request.
If the external tool ODIS "LogHelper" is installed in the "loghelper" sub-folder,
additional log files will be archived in the "log-extended" local folder when
sending. These expanded log files are too larger to send by e-mail, but they
can be very useful for fault analysis later. This tool is made available by the
ODIS update mechanism.
Warning!
92
All support requests that are more than 14 days old are deleted from the direc-
tory selected in the Administration area when quitting the application.
30 ODX Runtime Data Update

The ODX runtime data update mechanism enables manual and automatic up-
dates to the newest version of an ODX data package. Only vehicle projects for
the Engineering mode are updated using the update mechanism for ODX
runtime data. The update mechanism can run an automatic update check when
the ODIS application starts. It can also be activated manually using a button in
the side bar. The update mechanism provides the ODIS application user access
to ODX information files and additionally a selection of all available ODX data
packets.
30.1 Configuration
The update process can be configured in the Administration section in the "Di-
agnostic data" section of the "General" tab.
The source for the update information can be set using the radio buttons. With
“Update using index files”, the update information is accessed by the applica-
tion through ODX information files on an update server; meaning, through a
network drive that is reached using a URL. With “Update using Volkswagen
diagnostic data server”, the update information is downloaded directly from a
server defined in the application.
The scope of the update can be set in the combo box. Here are the options:
1. Activate automatic check and update to newest version
2. Activate automatic check
3. Deactivate automatic check
With the automatic update (option 1), the selection of available data package
versions is disabled and thus, is automatically updated to the newest version.
This option is activated by default.
A day interval cycle for an automatic update check can be configured in the
entry “Update cycle in days”.
To be able to perform an ODX data update using index files, at least one ODX
info file in XML format must be referenced by entering a path or by selecting in
a file selection dialog. A total of 6 ODX update files that can be used simulta-
neously in the ODX update process can be stored.
30.1.1 ODX Info Files
An ODX info file contains the reference to individual ODX update packages
(for example servers that can be accessed) and additional information about
the packages themselves and the project data set they contains.
93
An update package is identified by the shared version number (date). It con-

tains one or more vehicle projects. The name of the individual data packets in
an update package corresponds t the name of the vehicle project and always
contains exactly one vehicle project. The data package is in a compressed file
format (zip).
30.2 Selection of ODX Data Packages

The application shows a progress dialog after starting the check for updates
(manually or automatically). The application informs you that the update check
is being performed. The update check can only be started manually if the
runtime project is loaded. The button in the side bar for manually starting the
update check is only activated then.
If you have not selected the option for updating automatically to the newest
version, the application displays a dialog after the update check where you
can select the desired version of a complete ODX update package or individu-
al vehicle projects from it. The application shows the available versions of the
update packages and the vehicle projects they contain in a dialog. The appli-
cation selects the current version of the update package and the available ve-
hicle projects stored on the computer.
30.2.1 Dialog when Updating using Index Files
The following information is displayed in a table in this dialog:
 "Version": version number
 "compatible with": compatible ODIS E versions
 "Comments": from the "description” attribute
The table content is structured in a tree format with the levels: “Package”, “Ver-
sion” and “Vehicle project”.
You can select the desired version of the update package or individual vehicle
projects the same way as an update package using a checkbox. It is not possi-
ble to select an entire package.
30.2.2 Dialog when Updating using Diagnostic Data Server
The available data packages can be selected in a combo box in this dialog.
The following information is displayed in a table for all vehicle projects includ-
ed in the package.
 "Update": checkbox to mark the vehicle project to be updated
 "Delete": checkbox to mark the vehicle project to be deleted
 “Name”: name of the vehicle project.
 "Description": from the "description” attribute
 "Status": current status of the vehicle project . Possible values:
o Unknown
94
o Installed
o Not offered by service
o New version available
o Version cannot be identified
Entries with the status “Not offered by service” are highlighted in red and can-
not be marked for update. Entries with the status “Not installed” cannot be
marked for deletion. Markings for update and deletion in the same entry are
excluded. Using the checkbox in the respective column header, all entries can
be marked or deselected for this action.
30.3 Performing ODX Updates

The user can start the update mechanism in the selection dialog with the "Start"
button.
The downloading of each vehicle project is indicated by a progress dialog. The
update mechanism can be canceled prematurely using the "Cancel" button.
The previously available vehicle projects remain when the update process is
canceled.
The deletion of marked vehicle projects is not displayed in the progress dialog
and cannot be interrupted.
After downloading each vehicle project, the application performs a consistency
check on the downloaded files. If there are errors in the consistency check, the
application informs you in a dialog. IN this case, you can download the data
package again or cancel the update process completely. If the consistency
check was successful, the application checks if there is enough storage space in
the installation directory for the diagnostic base components of the ODIS appli-
cation to perform the update. If not, the application will inform you about the
problem. In this case, the update is canceled. If there is enough storage space,
the application starts the actual update of the runtime projects. Runtime pro-
jects that are not contained in the data package selected for the update are
not changed. All runtime projects that are replaced during the update are
saved in a sub-directory in the project data as a backup. The progress of the
update is displayed in a progress dialog. The application must then be restart-
ed.
31 Application Update
The application update mechanism enables manual and automatic updates to
the newest version of the application. Only vehicle projects for the Engineering
mode are updated using the update mechanism for ODX runtime data. The
update mechanism can run an automatic update check when ODIS starts. It
can also be activated manually using a button in the side bar. The update
95
mechanism provides the ODIS application user access to ODX information files
and additionally a selection of all available ODX data packets.
32 Connection Test
Pressing the "Connection test" button under Configuration in the side bar opens
the connection test dialog. It allows a connection test to external systems for
individual services to be configured using checkboxes and run, and it displays
the results status of the connection text for the selected services.
33 Hotfixes
A hotfix is a collection of diagnostic data, test program, images, and docu-
ments and is provided in multiple zip files. The "VaudesSmartlang" is the ex-
ception, because it is located in a JAR. The "installation_index.xml" file lists the
hotfix archive.
In contrast to an update, hotfixes do not modify the installation but are just su-
perimposed over it. All diagnostic data, test programs, images, and documents
can be superimposed by a hotfix.
33.1 Importing a Hotfix

The "Download" button in the expanded side bar under "Configuration" starts
the process of downloading a hotfix. A hotfix must be available in the file sys-
tem in order to load it. A directory selection dialog opens for this. You can se-
lect the directory there that contains the hotfix, particularly the installa-
tion_index.xml file. If a hotfix was previously loaded, you are asked if it should
be overwritten. If you decline this, process is canceled. If confirmed, the current
hotfix is overwritten.
The following checks are performed for the new hotfix:
1. If the selected directory is empty or does not contain an "installa-
tion_index.xml" file, an error message will appear and the hotfix will not
be loaded.
2. The version of the baseline on which the hotfix is based and the baseline
for the ODIS application must be identical. If both versions cannot be de-
termined or if the versions do not match, an error message is shown and
the process is canceled.
If all checks are successful, the new hotfix is loaded.
If an update is performed with a loaded hotfix, the Offboard Diagnostic Infor-
mation System Engineering checks again after restarting if the hotfix baseline
version matches the baseline version of the Offboard Diagnostic Information
System Engineering. If this check is negative, this hotfix is deleted.
96
33.2 Deleting a Hotfix

The "Delete" button under "Configuration" in the expanded side bar is active
once a hotfix is active, meaning before it was installed successfully. This makes
it possible to delete an installed hotfix.
34 Appendix
34.1 Using the Keyboard
As an alternative to using the mouse, you can also navigate and perform func-
tions in various views using the keyboard. The following keyboard shortcuts are
used in all views:
General Functions
Button/Key Combination Function
Return / Enter Performs a function. / Starts an action
Highlights all (such as measured values or

CTRL + A
functions)
Copies the content of a selected table to the

CTRL+ C
clipboard
CTRL + F Activates the filter input
ESC Cancels a function
Edits the selected element (for example in

F2 / space bar
tables)
Spacebar (focus on diagnostic / Switch between the modes "Diagnostic" /

admin) "Admin"
TAB Changes the input focus to the next element
Control Module List

Button / Key Combination Function
97
Changes between the control module list and the

Space bar
diagnostic functions
Navigation between the Results Views

Button/Key Combination Function
F4 Switches to the control module list
CTRL + F4 Closes the current tab
Closes all of the tabs except the current

CTRL + SHIFT + F4
one
ALT + + / ALTGR + + / STRG +

Switches to the tab on the right
PGDN
ALT + - / ALTGR + - / STRG + PGUP Switches to the tab on the left
Functions in the Expandable Side Bar

F1 Starts online help
F3 Support
F5 Creates a new results log
F6 Adds data to the results log
F7 Displays the results log
98
F8 Adds comments to the results log
F9 Changes the diagnostic session
F10 Access authorization
F11 Starts the trace
F12 Stops the trace
Keyboard Operation in Tables and Trees

Up arrow Up one line
Down arrow Down one line
Left arrow Collapses a tree element
Right arrow Expands a tree element
Switches to the next control element that

Any letter
starts with this letter
CTRL + right arrow Moves the selected elements to the right
CTRL + left arrow Moves the selected elements to the left
CTRL + up arrow Moves the selected elements up (sorting)
CTRL + down arrow Moves the selected elements down (sorting)
99
Keyboard Operation in Wizard Pages (Basic Setting, Actuator Test,

Etc.)
ENTER / right arrow Switches to the next wizard page
ESC / left arrow Switches to the previous wizard page
Keyboard Operation in the “Vehicle Selection” View

Button / Key Combina-
Function
tion
Starts editing mode in the selected line in the vehicle
F2
name column
ENTER (in the vehicle ta-
Starts diagnosis in the selected vehicle
ble)
ENTER (vehicle name ed- Copies the current value and selection into the next
iting mode) line
ESC (vehicle name edit-
Cancels editing, any values entered are discarded
ing mode)
SHIFT + ENTER (vehicle
Accepts the new value and edits one cell higher
name editing mode)
CTRL + ENTER (vehicle
Accepts the new value and edits one cell lower
name editing mode)
CTRL + F Focuses on the "Filter" input field
Keyboard Operation in the “Identification” View

ENTER (focus on the table or
Updates the identification data
tree)
Spacebar (focus on expanded Switch between the view "Expanded identifica-
identification / identification) tion" / "Identification"
100

Keyboard Operation in the “DTC Memory” View

ENTER (focus on the table or
Updates the DTC memory
tree)
DEL Erases the DTC memory
Keyboard Operation in the Measured Values View

Keyboard Operation in the “Select Measured Values” View
Moves the selected measured values to
CTRL + RIGHT ARROW (left table)
the right
CTRL + LEFT ARROW (right table)
the left
Moves the selected measured values
CTRL + UP ARROW (right table)
up (sorting)
Moves the selected measured values
CTRL + DOWN ARROW (right table)
down (sorting)
Switches to the Show measured values
CTRL + RIGHT ARROW
view
RIGHT ARROW (and no focus on the Switches to the Show measured values
text field) view
Switches to the Show measured values
ENTER (in the table)
view
ENTER (in the KWP input field meas- Accepts the defined measured value
ured value block) block
CTRL + F (UDS only) Focuses on the "Filter" input field
Keyboard Operation in the “Display Measured Values” View

101

ENTER (in the table) Updates measured values
Switches to the Select measured values
SHIFT + LEFT ARROW
view
LEFT ARROW
view
Keyboard Operation in Adaptation

Keyboard Operation in “KWP Adaptation”
ENTER (in the channel input Performs the "Select channel" function, fo-
field) cuses on the "Input" input field
Performs the "Send test value" function if the
ENTER (in the Input input field) button is activated. Focuses on the "Accept"
button.
Keyboard Operation in “UDS Adaptation”

Starts editing mode in the selected line in the input
F2
column
ENTER (in the input editing Copies the current value and selection into the next
mode) line
ESC (in the input editing
Cancels editing, any values entered are discarded
mode)
SHIFT + ENTER (in the in-
put editing mode)
CTRL + ENTER (in the in-
put editing mode)
Keyboard Operation in the “Output Diagnostic Test Mode” View

Keyboard Operation in the “KWP Output Diagnostic Test Mode” View
102

UP and DOWN ARROW (output
Switches between the "sequential" and
diagnostic test mode option selec-
"selective" option
tion)
UP and DOWN ARROW (actuator Switches between the "hex" and "dez" op-
option selection) tion
CTRL + P Starts the actuator test
CTRL + S Stops the actuator test
CTRL + N Next actuator
Keyboard Operation in UDS Output Diagnostic Test Mode

Keyboard Operation in the “Actuator Selection” View

CTRL + RIGHT ARROW (left table) Moves the selected actuators to the right
CTRL + LEFT ARROW (right table) Moves the selected actuators to the left
CTRL + UP ARROW (right table) Moves the selected actuators up (sorting)
CTRL + DOWN ARROW (right ta- Moves the selected actuators down (sort-
ble) ing)
CTRL + RIGHT ARROW Switches to the Set parameters view
RIGHT ARROW (and no focus on the
Switches to the Set parameters view
text field)
ENTER (in the table) Switches to the Set parameters view
Keyboard Operation in the “Set Parameters” View

Starts editing mode in the selected line in the
F2 (parameters tree table)
value column
ENTER (in the value editing Copies the current value and selection into the
mode) next line
Cancels editing, any values entered are dis-
ESC (in the value editing mode)
carded
SHIFT + ENTER (in the value Accepts the new value and edits one cell high-
editing mode) er
CTRL + ENTER (in the value ed-
iting mode)
103

CTRL + RIGHT ARROW Switches to the Select measured values view
RIGHT ARROW Switches to the Select measured values view
ENTER (in the tree table) Switches to the Select measured values view
SHIFT + LEFT ARROW Switches to the Actuator selection view
LEFT ARROW Switches to the Actuator selection view
ESC Switches to the Actuator selection view

the right
the left
Moves the selected measured values up
(sorting)
CTRL + DOWN ARROW (right ta- Moves the selected measured values
ble) down (sorting)
Switches to the Output diagnostic test
CTRL + RIGHT ARROW
mode view
RIGHT ARROW (and no focus on the Switches to the Output diagnostic test
text field) mode view
Switches to the Output diagnostic test
mode view
SHIFT + LEFT ARROW Switches to the Set parameters view
LEFT ARROW (and no focus on the
text field)
ESC Switches to the Set parameters view
Keyboard Operation in the “Output Diagnostic Test Mode” View

CTRL + P Starts the actuator test
CTRL + S Stops the actuator test
CTRL + N Next actuator
104

SHIFT + LEFT ARROW
view
LEFT ARROW
view
ESC
view
Note: in elements with substructures, such as selected actuators / basic settings
with associated parameters and measured values, the arrow buttons are used
to expand/collapse (LEFT/RIGHT ARROW) and navigate (UP/DOWN ARROW)
within the structure. At the lowest level of a structure, the RIGHT ARROW button
is deactivated, and the LEFT ARROW switches to the previous view.
Keyboard Operation in the “Basic Setting” View

Keyboard Operation in the “KWP Basic Setting” View
ENTER (in the channel input Performs the "Select channel" function, fo-
field) cuses on the activated "Activate" button
Keyboard Operation in the “Engine Group” View

Performs the "Select channel" function, fo-
ENTER (in the channel input field)
cuses on the activated "Activate" button
DOWN ARROW (in the control Selects the next control module in the en-
module selection) gine group
UP ARROW (in the control mod- Selects the previous control module in the
ule selection) engine group
Keyboard Operation in the UDS Basic Setting

Keyboard Operation in the ”Basic Setting Selection” View

Moves the selected basic settings to the
right
Moves the selected basic settings to the
left
CTRL + UP ARROW (right table) Moves the selected basic settings up
105

(sorting)
CTRL + DOWN ARROW (right ta- Moves the selected basic settings down
ble) (sorting)
CTRL + RIGHT ARROW Switches to the Set parameters view
text field)
ENTER (in the table) Switches to the Set parameters view
Keyboard Operation in the “Set Parameters” View

F2 (parameters tree table)
value column
ENTER (in the value editing Copies the current value and selection into the
mode) next line
ESC (in the value editing mode)
carded
SHIFT + ENTER (in the value Accepts the new value and edits one cell high-
editing mode) er
CTRL + ENTER (in the value ed-
iting mode)
CTRL + RIGHT ARROW Switches to the Select measured values view
RIGHT ARROW Switches to the Select measured values view
ENTER (in the tree table) Switches to the Select measured values view
SHIFT + LEFT ARROW Switches to the basic setting selection view
LEFT ARROW Switches to the basic setting selection view
ESC Switches to the basic setting selection view

the right
the left
106

Moves the selected measured values up
(sorting)
CTRL + DOWN ARROW (right ta- Moves the selected measured values
ble) down (sorting)
CTRL + RIGHT ARROW Switches to the Diagnosis view
Switches to the Diagnosis view
text field)
ENTER (in the table) Switches to the Diagnosis view
SHIFT + LEFT ARROW Switches to the Set parameters view
LEFT ARROW (and no focus on the
text field)
ESC Switches to the Set parameters view
Keyboard Operation in the “Perform” View

CTRL + P Starts the basic setting test
CTRL + S Stops the basic setting test
CTRL + N Next basic setting
SHIFT + LEFT ARROW
view
LEFT ARROW
view
ESC
view
Note: in elements with substructures, such as selected actuators / basic settings
with associated parameters and measured values, the arrow buttons are used
to expand/collapse (LEFT/RIGHT ARROW) and navigate (UP/DOWN ARROW)
within the structure. At the lowest level of a structure, the RIGHT ARROW button
is deactivated, and the LEFT ARROW switches to the previous view.
Keyboard Operation in the “Coding” View

Keyboard Operation in the “UDS Binary Coding” View
107

Starts editing mode in the selected column and
F2 (in the table)
line
ENTER (in the editing mode) Accepts the current value
ESC (in the editing mode) Cancels editing, any values entered are discarded
SHIFT + ENTER (in the edit-
ing mode)
CTRL + ENTER (in the edit-
ing mode)
ARROW KEYS (in the table) Navigates the table cursor
ENTER (in the table) Writes the coding value
Keyboard Operation in the “UDS Plain Text Coding” View

F2 (in the tree table)
input column
ENTER (in the input editing Copies the current value and selection into
mode) the next cell
ESC (in the input editing mode)
carded
SHIFT + ENTER (in the input edit- Accepts the new value and edits one cell
ing mode) higher
CTRL + ENTER (in the input edit- Accepts the new value and edits one cell
ing mode) lower
ENTER (in the tree table) Writes the coding value (accept)
Keyboard Operation in the “KWP Long Coding” View

Starts editing mode in the selected column and
F2 (in the table)
line
Copies the current value and selection into the
ENTER (in the editing mode)
next cell
ESC (in the editing mode) Cancels editing, any values entered are discarded
SHIFT + ENTER (in the edit-
ing mode)
CTRL + ENTER (in the edit-
ing mode)
108

ARROW KEYS Navigates the table cursor
ENTER (in the table) Writes the coding value (accept)
Keyboard Operation in the “KWP Short Coding” View

ENTER (in the New code input field) Writes the coding value (accept)
Keyboard Operation in the “Bus Master Coding” View

ENTER (in the table) Writes the coding value (accept)
Keyboard Operation in the “Memory Cells” View

F2 (in the table) Starts the editing dialog
Cancels editing, values already en-
ESC (in the editing dialog)
tered are discarded
UP ARROW (in the editing dialog input
Focus moves up one cell
field)
DOWN ARROW (in the editing dialog
Focus moves down one cell
input field)
RIGHT ARROW (hex option focus) Dez option selection
LEFT ARROW (dez option focus) Hex option selection
ENTER (in the table) Write cells
ENTER (in the input field) Read cells
Keyboard Operation in the Hex Service View

Copies the PDU value into the input
ENTER (in the preset table) field and the focus on the input
field
F2 (in the preset table with user-defined Starts the editing dialog
109

preset)
ESC (in the editing dialog) Closes the editing dialog
DEL (in the preset table with user-defined
Deletes the line
preset)
ENTER (in the input field) Sends the entered diagnostic PDU
SHIFT + UP ARROW, DOWN ARROW (in
Multiple selection
the trace table)
Keyboard Operation in OBD Service

Keyboard Operation in the Function Selection View
Selection of the selected OBD mode and
CTRL + RIGHT ARROW
switches to the parameter selection view
RIGHT ARROW
Keyboard Operation in the “Parameter Selection” View

Moves the selected parameters to the
right
Moves the selected parameters to the
left
Moves the selected parameters up
(sorting)
Moves the selected parameters down
CTRL + DOWN ARROW (right table)
(sorting)
CTRL + RIGHT ARROW Switches to the Display view
Switches to the Display view
text field)
ENTER (in the table) Switches to the Display view
SHIFT + LEFT ARROW Switches to the Functions view
LEFT ARROW (and no focus on the text
Switches to the Functions view
field)
110

ESC Switches to the Functions view
Keyboard Operation in the “Results Display” View

SHIFT + LEFT ARROW Switches to the Parameter selection view
LEFT ARROW Switches to the Parameter selection view
ESC Switches to the Parameter selection view
Keyboard Operation in the “Flashing” View

F2 (in the tree table with selected flash
Starts session selection
container)
CTRL + P Starts flashing
ENTER (in the tree table) Starts flashing
Keyboard Operation in Read Entire System

The key combinations described here only work if there is no modal dialog or
progress dialog open.
CTRL + P Check DTC memory
ENTER (in the tree table) Check DTC memory
CTRL + S Stops the process
Erase the DTC memory and read the
DEL
service bits
Keyboard Operation in the Installation Check Dialog

DEL (in the BZD logs table) Deletes the selected logs
DEL (in the installation specifications ta- Erases the selected installation
ble) specifications
111
Keyboard Operation in the “Send Logs” Dialog

DEL (in the logs table) Deletes the selected logs
CTRL + F Activates the filter input
Keyboard Operation in the “Compare Logs” Dialog

DEL (in the right table) Deletes the selected logs
Keyboard Operation in “Coding/Adaptation”

F2 (in the tree table) Starts data selection editing mode
ESC (in the data selection editing Cancels editing, any values entered
mode) are discarded
ENTER (in the data selection editing Copies the current value and selection
mode) into the next line
Keyboard Operation in GFF

ENTER (in the tree table) Performs the selected script
Keyboard Operation in the “Macros” View

ENTER (in the tree table) Performs the selected macro
112
34.2 Structure of a Flash Control File for Parallel Flashing

The XM flash control file contains the following information as attributes in a
<PROGRAM-MING-CONFIG-FILE> XML element:
 Type of diagnostic system
 Version of the XML flash control file
The MUTE function for the entire flash process is activated or deactivated with
a "Mute" attribute in a <PROGRAMMING-SCHEDULE> XML element. Acti-
vates or deactivates an additional attribute of this "LinkControlHandling"
LinkControl function for the entire flash process.
All elements that should be processed sequentially are combined in a <SE-
QUENTIAL> XML element. All sub-elements within the <PARALLEL> element
are processed in parallel.
These elements can be alternately nested within one another.
The XML flash control file describes a flash jobs that is to be performed by the
diagnostic system for a specific control module in a <FLASH-ECU> XML ele-
ment.
This element contains the following sub-elements:
- <LOGICAL-LINK> contains the control module logical link
- <FILE-NAME> contains the path for the flash container file1
- <SESSION-SHORTNAME> contains the session to be flashed
Fictional Example of a Flash Control File:

<?xml version=“1.0“ encoding=“utf-8“?>
<PROGRAMMING-CONFIG-FILE DiagnosticSystem=“ODIS ENGINEERING”
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:noNamespaceSchemaLocation=”flash_schema_version_1.0.xsd” SchemaVer-
sion=“1.0“>
<PROGRAMMING-SCHEDULE Mute=”ON” LinkControlHandling=”ON”>
<SEQUENTIAL>
<FLASH-ECU>
<LOGICAL-LINK>LL_Ecu1</LOGICAL-LINK>
<FILE-NAME>C:/temp/ecu1Flash.odx<FILE-NAME>
<SESSION-SHORTNAME>Abc_12345_987_ZY</SESSION-SHORTNAME>
</FLASH_ECU>
<PARALLEL>
<SEQUENTIAL>
<FLASH-ECU>
<SESSION-SHORTNAME>Abc_145_9Y</SESSION-SHORTNAME>
</FLASH_ECU>
<FLASH-ECU>
1
Absolute or relative to the flash control file
113
<SESSION-SHORTNAME>Abc_13587Y</SESSION-SHORTNAME>
</FLASH_ECU>
</SEQUENTIAL>
<FLASH-ECU>
<LOGICAL-LINK>LL_ecu4</LOGICAL-LINK>
<SESSION-SHORTNAME>Abc_165_987Y</SESSION-SHORTNAME>
</FLASH_ECU>
</PARALLEL>
<FLASH-ECU>
<LOGICAL-LINK>LL_ecu5</LOGICAL-LINK>
<SESSION-SHORTNAME>Abc_125_987_ZY</SESSION-SHORTNAME>
</FLASH_ECU>
</SEQUENTIAL>
<PROGRAMMING-SCHEDULE>
<PROGRAMMING-CONFIG-FILE>
The flash sequence is then the following:

1. Ecu1
2. Ecu2 parallel Ecu4
3. Ecu3 parallel Ecu4
4. Ecu5
35 “ODIS Engineering” Privacy Policy
A. Controller
With this privacy policy, we hereby inform you of the ways in which your per-
sonal data is collected, processed, and used by Volkswagen AG, Berliner Ring
2, 38440 Wolfsburg, Germany, entered into the register of companies at the
district court in Braunschweig under the number HRB 100484 (“Volkswagen
AG”).
In the information that follows, “Volkswagen Offboard Diagnostic Information
System Engineering” will be abbreviated as “ODIS Engineering”.
B. Collection, Processing, and Use of Your Personal Data
114
Principles
The following data may be saved when performing work with the “ODIS Engi-
neering” diagnostic system:
 Importer, dealer number
 Global user ID
 IP address
 E-mail address
This data is only used to ensure you have access to group systems when you
are working with GFF, OBD, and procedures where data is populated (“Flash
mode”). This access is needed to provide you with the required additional in-
formation for the repair procedure, such as software configurations. In addi-
tion, the personal data listed above may be used to provide software support.
The e-mail address is used as the communication platform for this.
The data listed is processed on the basis of a prevailing legitimate interest (Art.
6 Abs. 1 S.1 lit. f DSGVO). The legitimate interest is based on ensuring a
smooth repair process.
The personal data that is collected is deleted by Volkswagen AG after ending
the “ODIS Engineering diagnostic session” on the diagnostic tester or within 30
days after closing a support case. To ensure a smooth support process, the per-
sonal data may also be processed by a contracted partner. The 30-day dele-
tion period is also followed in this case.
C. Your Rights
You may exercise the following rights vis-à-vis Volkswagen AG at any time and
at no cost. Further information on exercising your rights can be found in Section
D.
Right to information: You have the right to obtain information from us about
the processing of your personal data.
Right of rectification: You have the right to request that we correct any person-
al data relating to you which is incorrect or incomplete.
Right to erasure: You have the right to request the erasure of your data if any
of the conditions stated in GDPR Article 17 exists. Under that provision, you
may obtain, for example, the erasure of your data, if they are no longer neces-
sary for the purposes for which they were collected. Furthermore, you may re-
quest erasure if we process your data on the basis of your consent and you re-
voke this consent.
Right to restriction of processing: You have the right to request restrictions on
the processing of your data if the conditions of GDPR Article 18 exist. That is
the case, for example, if you dispute the correctness of your data. You may re-
115
quest that processing is restricted for as long as it takes to examine the correct-
ness of your data.
Right of objection: If processing is based on an overriding interest or if your
data are used for the purpose of direct marketing, you have the right to object
to the processing of your data. An objection is permissible if processing is either
carried out in the public interest, or in the exercise of official authority, or on
account of a legitimate interest pursued by Volkswagen AG or by a third party.
If you exercise your right to object to the data processing, please notify us of
your reasons for objecting. Besides this, you also have the right to object to da-
ta processing for the purpose of direct marketing. The same applies to profil-
ing, if this is related to direct marketing.
Right to data portability: If data processing is based on consent or on the per-
formance of a contract, and the data processing is performed by automated
means, you have the right to receive your data in a structured, commonly used
machine-readable format, and to transmit those data to another data proces-
sor.
Right of revocation: If the data processing is based on consent, you have the
right to revoke your consent to data processing with future effect at any time,
free of charge.
Right to lodge a complaint: You also have the right to lodge a complaint with a
supervisory authority (such as the data protection authority of the Federal State
of Lower Saxony [Die Landesbeauftragte für den Datenschutz Niedersachsen])
concerning our processing of your data.
D. Contact Persons
Contact Person for Exercising Your Rights

The contact person for the assertion of your rights and further information can
be found on the following website https://datenschutz.volkswagen.de.
Data Protection Officer

Our data protection officer is your point of contact for matters concerning data
protection:
Data protection officer of Volkswagen AG
Berliner Ring 2, 38440 Wolfsburg, Germany
datenschutz@volkswagen.de
Version dated: June 2018
116

Manual Engineering-En US

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Engineering-En US

Uploaded by

Copyright:

Available Formats

User Guide

Offboard Diagnostic Information System Engineering

Confidential. All rights reserved. Any form of reproduction or dissemination

3.7 Project Entry Service Configuration ........................................................... 20

22 Copying Coding / Adaptation ................................................................... 76

29 Support Function .......................................................................................... 91

2 General Operating Information

2.1 Header Area

Vehicle Project and Identification

2.2 Status Line

2.3 Expandable Side Bar

2.4 Function Views

and suffixes are separated by "–". Comprehensive control module functions

Diagnostic function Suffix

002 – DTC memory DTC

003 – Measured values MW

004 – Output diagnostic test mode SGD

005 – Basic setting GES

006 – Coding COD

006.04 Components list coding BMC

007 – Adaptation ANP

010.01 Write data set DAT

010.02 Memory cells SPZ

011.01 Hex service HEX

011.05 Data upload DUP

Vehicle function (Prefix FZG-)

040 - OBD service OBD

041 – Engine group GES

046.01 Coding / adaptation CDA

047 - Reading out complete system GSA

060 - Guided Functions GFF-BTL / GFF-RUN

061 - Macro function MAK

2.5 Table Operating Functions

2.6 Using the Keyboard

2.8 Online Help

3.2 Start Response

3.3 Vehicle Selection

Red light "DoIP vehicle busy"

Green light "DoIP vehicle ready"

Light off “DoIP status not yet detected"

Light off with a question mark “DoIP check failed"

3.4 Managing Vehicle IDs

3.5 Diagnostic Interface Selection

interface has already been assigned by another tester, it will be indicated to

3.6 Vehicle Project Selection

3.7 Project Entry Service Configuration

3.8 Automatic Diagnostic Entry Using the VIN

3.9 Diagnostic entry with manual VIN selection

3.10 Communication Path Specification

3.11 Diagnostic Entry Configuration

3.12 Unloading a Project

3.13 Evaluating Components List(s)

3.14 Battery Voltage Monitoring

4 Control Module List View

Displaying Sub-Systems of Diagnostic Classes 1 and 2

Software Cluster Display

Sorting the Control Module List

4.1 Control Module List Columns

Not coded => accessible

4.2 Control Module List Update Cycles

4.3 Selecting Control Modules in the Control Module List

4.4 Selecting Diagnostic Functions for a Control Module

002 – DTC memory

 002.03 active error