Manual Service-En US

Offboard Diagnostic Information
System Service User Guide
ODIS Service 11.0.0

Confidential. All rights reserved. Any form of reproduction or dissemination without the prior written
consent of the specialist department of Volkswagen AG is prohibited. Contractual partners receive this
document only through the responsible procurement department. VOLKSWAGEN AG
Copyright © 2007-2022 VOLKSWAGEN AG

Table of Contents
Table of Contents .................................................................................................................................... 2
Table of Figures....................................................................................................................................... 7
List of Tables ......................................................................................................................................... 19
1 Introduction ................................................................................................................................... 19
1.1 Comments about the User Guide ........................................................................................... 19
1.2 Structure of the User Guide ................................................................................................... 19
2 System Requirements .................................................................................................................... 22
3 Installation ..................................................................................................................................... 23
4 Update ........................................................................................................................................... 39
4.1 Installing a Fallback Version ................................................................................................. 52
4.2 Restart during Updates .......................................................................................................... 54
4.3 Serious Errors during Updates............................................................................................... 55
4.4 Starting the Program .............................................................................................................. 56
4.4.1 Checking the License .................................................................................................... 56
4.4.2 Warnings and Notes (Disclaimer) ................................................................................. 58
4.4.3 Logs That Have Not Been Sent ..................................................................................... 59
4.4.4 Specifying the diagnostic interface................................................................................ 60
5 Application Start/User Interface .................................................................................................... 62
5.1 User interface ........................................................................................................................ 63
5.1.1 Info area ......................................................................................................................... 63
5.1.2 Working Area (Client Area) .......................................................................................... 66
5.1.3 Modes ............................................................................................................................ 67
5.1.4 Standard functions ......................................................................................................... 68
5.1.4.1 Log submenu ............................................................................................................. 69
5.1.4.2 Data submenu ............................................................................................................ 70
5.1.4.3 Extras submenu ......................................................................................................... 70
5.1.4.4 Help submenu ............................................................................................................ 71
5.1.4.5 Info submenu ............................................................................................................. 71
5.1.4.6 Trace submenu .......................................................................................................... 72
5.1.4.7 Legal Submenu .......................................................................................................... 72
5.1.5 Status area...................................................................................................................... 73
5.2 Operation ............................................................................................................................... 74
5.2.1 Touchscreen................................................................................................................... 74
5.2.2 Mouse and Keyboard..................................................................................................... 74
5.3 Screenshots for Support Requests ......................................................................................... 74
5.4 Control Module Negative Response Display ........................................................................ 76
6 Diagnosis Operating Mode ............................................................................................................ 80
6.1 Diagnosis Procedure .............................................................................................................. 80
6.2 Diagnostic Entry .................................................................................................................... 82
6.2.1 Connecting a Vehicle .................................................................................................... 84
6.2.1.1 Checking the Diagnostic Interface ............................................................................ 84
6.2.1.2 VIN Display .............................................................................................................. 85
6.2.2 Starting Diagnosis ......................................................................................................... 86
6.2.2.1 Diagnosis with Vehicle Data Stored Centrally .......................................................... 91
6.2.3 Vehicle Features Dialog (VFD)..................................................................................... 92
6.2.4 Logging in to Group Systems ........................................................................................ 96
6.2.4.1 Authentication with SecurID ..................................................................................... 97
6.2.4.1.1 Requirements ....................................................................................................... 98
6.2.4.1.2 Initial Registration in the WS Gateway ............................................................... 98
6.2.4.1.3 Additional Messages in the WS Gateway ......................................................... 100
6.2.4.2 Authentication in Group Retail Portal (GRP).......................................................... 101
6.2.5 Wi-Fi Connection Status ............................................................................................. 102
6.2.6 Low battery warning message ..................................................................................... 103
6.2.7 Communication Selection when Setting up a Connection (DoIP/CAN-FD/CAN/K-Line)
104
6.2.8 Using the K Line Adapter............................................................................................ 107
6.2.9 Customer Satisfaction Survey ..................................................................................... 108
6.2.10 Selecting an Order ....................................................................................................... 109
6.2.11 Control Module Identification ..................................................................................... 118
6.2.11.1 Control Module List ............................................................................................ 124
6.2.11.2 Networking Diagram ........................................................................................... 127
6.2.11.3 DTC Memory ...................................................................................................... 134
6.2.11.4 Equipment List .................................................................................................... 138
6.2.11.5 Components List .................................................................................................. 140
6.2.12 Starting Guided Fault Finding (GFF) .......................................................................... 141
6.3 Test Plan and Special Functions .......................................................................................... 143
6.3.1 Start Modules, Traversal Test, Test Plan Calculation ................................................. 144
6.3.2 DISS / TPI ................................................................................................................... 147
6.3.2.1 Coding assistant ....................................................................................................... 155
6.3.3 Special Functions......................................................................................................... 157
6.4 Working with GFF .............................................................................................................. 158
6.4.1 Measured Values ......................................................................................................... 173
6.4.1.1 Read Measured Values Results Window (Measured Value Table)......................... 175
6.4.1.2 Read Measured Values Results Window (ODX Data) ............................................ 177
6.4.2 Gateway Coding .......................................................................................................... 178
6.4.3 Documents ................................................................................................................... 181
6.4.4 Test Verification .......................................................................................................... 185
6.4.5 Component Selection................................................................................................... 186
6.4.6 Help ............................................................................................................................. 187
6.4.7 Build Status Documentation for Components that are Not Diagnostic-Capable......... 188
6.4.7.1 Recording Data ........................................................................................................ 190
6.4.7.1.1 Manual Recording ............................................................................................. 190
6.4.7.1.2 Recording by Scanner........................................................................................ 191
6.4.8 Quick View in Workshop Information ........................................................................ 192
6.4.8.1 Pressing the “Quick View” Button .......................................................................... 193
6.4.8.2 “Quick View in Workshop Information” Dialog .................................................... 194
6.5 End Diagnosis...................................................................................................................... 194
6.6 Quick Entrance .................................................................................................................... 203
6.7 Diagnosis without a Vehicle ................................................................................................ 206
6.7.1 Diagnostic Entry .......................................................................................................... 207
6.7.2 Test Plan and Special Functions .................................................................................. 209
6.7.3 Working with GFF ...................................................................................................... 210
6.7.4 End Diagnosis.............................................................................................................. 210
6.7.5 Connecting Later to a Vehicle ..................................................................................... 211
6.8 Documents ........................................................................................................................... 212
6.8.1 Documents in GFF ...................................................................................................... 218
7 OBD Mode .................................................................................................................................. 220
7.1 Starting OBD ....................................................................................................................... 221
7.2 Switching to OBD Operating Mode .................................................................................... 225
7.3 OBD General Information ................................................................................................... 226
7.3.1 Starting OBD from Other Operating Modes ............................................................... 226
7.3.2 Accessing OBD Functions .......................................................................................... 227
7.3.3 Logging ....................................................................................................................... 234
7.3.4 Using the Keyboard ..................................................................................................... 234
7.4 Control Module-Specific Functions .................................................................................... 235
7.4.1 Adaptation ................................................................................................................... 236
7.4.1.1 Control Modules with KWP Protocol ..................................................................... 236
7.4.1.2 Control Modules with UDS Protocol ...................................................................... 239
7.4.2 Coding Bus Master ...................................................................................................... 244
7.4.2.1 Coding KWP bus masters ........................................................................................ 246
7.4.2.2 Coding UDS bus masters......................................................................................... 248
7.4.3 Coding ......................................................................................................................... 250
7.4.3.1 Coding KWP Control Modules ............................................................................... 251
7.4.3.2 Coding UDS Control Modules ................................................................................ 253
7.4.3.3 Technical Notes (Support Information) ................................................................... 261
7.4.4 Coding subsystems ...................................................................................................... 262
7.4.5 Coding software compositions .................................................................................... 265
7.4.6 DTC Memory .............................................................................................................. 269
7.4.7 Basic Setting ................................................................................................................ 273
7.4.7.1 Basic Setting on KWP Control Modules ................................................................. 273
7.4.7.2 Basic Setting on UDS Control Modules .................................................................. 275
7.4.8 Identification ............................................................................................................... 282
7.4.9 Measured Values ......................................................................................................... 284
7.4.10 Output Diagnostic Test Mode ..................................................................................... 287
7.4.10.1 Output Diagnostic Test Mode on KWP Control Modules................................... 287
7.4.10.2 Output Diagnostic Test Mode on UDS Control Modules ................................... 290
7.4.11 Access Authorization................................................................................................... 299
7.4.11.1 Access Authorization via Login Methods ........................................................... 299
7.4.11.2 Access Authorization via Online Tokens (SFD Activation) ............................... 302
7.4.12 Data Upload ................................................................................................................. 306
7.4.13 Multiple identification data ......................................................................................... 308
7.5 Vehicle-Specific Functions ................................................................................................. 311
7.5.1 Complete System DTC Memory ................................................................................. 311
7.5.2 Transport Mode ........................................................................................................... 314
7.5.3 Components List.......................................................................................................... 316
7.5.4 OBD............................................................................................................................. 317
7.6 End OBD ............................................................................................................................. 321
8 Flash Mode .................................................................................................................................. 323
8.1 Starting Flashing.................................................................................................................. 324
8.2 Identifying the Vehicle ........................................................................................................ 327
8.3 Group Systems Login .......................................................................................................... 331
8.4 Order Selection .................................................................................................................... 332
8.5 Identifying Control Modules ............................................................................................... 335
8.6 Working with Flash Programs ............................................................................................. 335
8.7 Diagnostic Objects when Flashing ...................................................................................... 337
8.8 Ending Flashing................................................................................................................... 339
9 General Diagnostic Entry ............................................................................................................ 341
10 Infomedia Button ..................................................................................................................... 343
11 Measuring Equipment Mode ................................................................................................... 343
11.1 Measuring Equipment General Information ........................................................................ 343
11.2 The Multimeter Client Area ................................................................................................ 345
11.2.1 Voltage Measurement with URDI Measuring Cable .................................................. 352
11.2.2 Current Measurement with URDI Measuring Cable ................................................... 353
11.2.3 Resistance Measurement with URDI Measuring Cable .............................................. 353
11.2.4 Diode Test with URDI Measuring Cable .................................................................... 354
11.2.5 Continuity Test with URDI Measuring Cable ............................................................. 356
11.2.6 Voltage Measurement Using DSO1 Measuring Socket .............................................. 357
11.2.7 Current Measurement with Current Clamp ................................................................. 357
11.2.8 Pressure Measurement using T/D Measuring Socket .................................................. 359
11.2.9 Temperature Measurement using T/D Measuring Socket ........................................... 360
11.3 The Client Area - Oscilloscope ........................................................................................... 360
11.3.1 Image Position, Time Basis and Line Strength ........................................................... 364
11.3.2 Setting Channel Parameters ......................................................................................... 365
11.3.3 Setting the Measuring Mode ....................................................................................... 368
11.3.4 Long-Term Measurement in Recorder Mode .............................................................. 371
11.3.5 Setting Trigger Parameters .......................................................................................... 375
11.3.6 Bandwidth Limitation.................................................................................................. 379
11.3.7 Specified Curves Functionality ............................................................................... - 379 -
11.3.8 Freeze Frame ........................................................................................................... - 383 -
11.3.9 Day/Night Mode ...................................................................................................... - 384 -
11.4 Transferring Measured Values From Diagnosis Mode ................................................... - 385 -
11.5 Measuring Technology Administration ........................................................................... - 387 -
12 Administration Mode .......................................................................................................... - 389 -
12.1 Operation ......................................................................................................................... - 389 -
12.2 General Area.................................................................................................................... - 393 -
12.2.1 Brand Design ........................................................................................................... - 393 -
12.2.2 Language ................................................................................................................. - 395 -
12.2.3 Update ..................................................................................................................... - 397 -
12.2.4 System Logging ....................................................................................................... - 399 -
12.2.5 System Environment ............................................................................................... - 401 -
12.2.6 License Information................................................................................................. - 402 -
12.2.7 Global Configuration ............................................................................................... - 403 -
12.2.8 GFF Process ............................................................................................................ - 405 -
12.2.9 Dealer Data .............................................................................................................. - 406 -
12.3 Save Locations Area ........................................................................................................ - 407 -
12.3.1 Database .................................................................................................................. - 407 -
12.3.2 Diagnostic Session................................................................................................... - 409 -
12.3.3 Flash Path ................................................................................................................ - 410 -
12.3.4 Diagnostic Log ........................................................................................................ - 412 -
12.3.5 Support .................................................................................................................... - 415 -
12.4 Support Area.................................................................................................................... - 416 -
12.4.1 Contact Data ............................................................................................................ - 416 -
12.4.2 E-mail Outgoing Server ........................................................................................... - 417 -
12.4.3 Hardware and Software ........................................................................................... - 421 -
12.5 Connections Area ............................................................................................................ - 422 -
12.5.1 Brand Settings ......................................................................................................... - 422 -
12.5.2 Group System: Logon.............................................................................................. - 423 -
12.5.3 Group System: GFF................................................................................................. - 424 -
12.5.4 Group System: ElsaPro............................................................................................ - 425 -
12.5.5 Group System: Carport ............................................................................................ - 426 -
12.5.6 Group System: DISS ............................................................................................... - 427 -
12.5.7 Group System: eShop .............................................................................................. - 428 -
12.5.8 Group System: Login .............................................................................................. - 429 -
12.5.9 Mirror Server 2 ........................................................................................................ - 431 -
12.5.10 Support application.............................................................................................. - 432 -
12.6 Certificates Area .............................................................................................................. - 432 -
12.6.1 Client certificate ...................................................................................................... - 432 -
12.6.2 Trust Certificate ....................................................................................................... - 437 -
12.7 Test Baseline Area........................................................................................................... - 441 -
12.7.1 Data Configuration .................................................................................................. - 442 -
13 Additional Program Functions ............................................................................................ - 443 -
13.1 Log .................................................................................................................................. - 443 -
13.1.1 General .................................................................................................................... - 444 -
13.1.2 Diagnostic Log ........................................................................................................ - 446 -
13.1.3 OBD Log ................................................................................................................. - 448 -
13.2 Data ................................................................................................................................. - 450 -
13.2.1 Current Tab.............................................................................................................. - 451 -
13.2.2 Diagnostic Session................................................................................................... - 452 -
13.2.2.1 Repair Interruption .......................................................................................... - 453 -
13.2.2.2 Continuing a Repair ......................................................................................... - 456 -
13.2.2.3 Logging ........................................................................................................... - 461 -
13.2.3 Hotfix....................................................................................................................... - 461 -
13.3 Extras ............................................................................................................................... - 471 -
13.3.1 Search ...................................................................................................................... - 472 -
13.3.2 Diagnostic Interface................................................................................................. - 475 -
13.3.3 Test drive ................................................................................................................. - 479 -
13.3.3.1 Starting Road Test Mode ................................................................................. - 479 -
13.3.3.2 Special Case VAS6154(A) with Connection Type "Wi-Fi Infrastructure" ..... - 480 -
13.3.3.3 Ending Road Test Mode .................................................................................. - 482 -
13.3.3.4 Special Case VAS6154(A) with Connection Type "Wi-Fi Access Point" ...... - 485 -
13.3.4 Update ..................................................................................................................... - 486 -
13.3.5 Connection Test ....................................................................................................... - 487 -
13.3.6 DoIP Connection Test ............................................................................................. - 490 -
13.4 Help ................................................................................................................................. - 493 -
13.4.1 Online Help ............................................................................................................. - 494 -
13.4.2 Support .................................................................................................................... - 499 -
13.4.2.1 Support Request via Email .............................................................................. - 500 -
13.4.2.2 Support Request via the Support Application ................................................. - 508 -
13.4.3 Troubleshooting....................................................................................................... - 512 -
13.5 Info .................................................................................................................................. - 513 -
13.5.1 New ......................................................................................................................... - 514 -
13.5.2 Versions ................................................................................................................... - 514 -
13.5.3 Disclaimer ............................................................................................................... - 515 -
13.6 Trace ................................................................................................................................ - 523 -
13.7 Legal ................................................................................................................................ - 524 -
13.8 Missing Translations ....................................................................................................... - 525 -
14 Error Messages .................................................................................................................... - 526 -
14.1 Error IDs .......................................................................................................................... - 528 -
14.2 Additional Error Messages .............................................................................................. - 576 -
14.2.1 Firewall Messages ................................................................................................... - 576 -
14.2.2 Browser Messages ................................................................................................... - 577 -
15 Keyword Index .................................................................................................................... - 578 -
16 Glossary ............................................................................................................................... - 582 -
Table of Figures
Figure 1.1 Example of an active link in the table of contents ............................................................... 19
Figure 1.2 Example of the Diagnosis Procedure ................................................................................... 21
Figure 1.3 Example of a section of a procedure with individual steps .................................................. 21
Figure 3.1 Starting installation .............................................................................................................. 24
Figure 3.2 Installation language selection ............................................................................................. 24
Figure 3.3 The Offboard Diagnostic Information System Service Setup Assistant .............................. 25
Figure 3.4 Platform selection ................................................................................................................ 26
Figure 3.5 Diagnostic interface selection .............................................................................................. 27
Figure 3.6 VAS 6154(A) Host name ..................................................................................................... 28
Figure 3.7 License Selection ................................................................................................................. 29
Figure 3.8 Start menu folder selection .................................................................................................. 30
Figure 3.9 Copying process display ...................................................................................................... 31
Figure 3.10 Completed installation ....................................................................................................... 32
Figure 3.11 PostSetup start .................................................................................................................... 33
Figure 3.12 Client certificate ................................................................................................................. 34
Figure 3.13 Language selection............................................................................................................. 35
Figure 3.14 PostSetup data display ....................................................................................................... 36
Figure 3.15 PostSetup data installation ................................................................................................. 37
Figure 3.16 Internet Options for Internet Explorer 9............................................................................. 38
Figure 4.1 Pause download ................................................................................................................... 40
Figure 4.2 Updates ready for installation .............................................................................................. 40
Figure 4.3 Checking for updates ........................................................................................................... 41
Figure 4.4 No updates available ............................................................................................................ 41
Figure 4.5 Reinstallation required ......................................................................................................... 42
Figure 4.6 Available updates ................................................................................................................. 42
Figure 4.7 Missing update files ............................................................................................................. 43
Figure 4.8 Warning before updating ..................................................................................................... 44
Figure 4.9 Updating using the network ................................................................................................. 45
Figure 4.10 Client certificate ................................................................................................................. 46
Figure 4.11 Error message when site.xml is missing ............................................................................ 47
Figure 4.12 Establishing a connection to the update site ...................................................................... 47
Figure 4.13 Warning when there is insufficient disk space ................................................................... 48
Figure 4.14 Available updates display .................................................................................................. 49
Figure 4.15 No updates available .......................................................................................................... 50
Figure 4.16 Update progress indicator .................................................................................................. 51
Figure 4.17 Error when performing the update ..................................................................................... 51
Figure 4.18 Multiple updates available ................................................................................................. 53
Figure 4.19 Identifying a fallback version ............................................................................................ 53
Figure 4.20 Fallback information .......................................................................................................... 54
Figure 4.21 Dialog for restarting during updates .................................................................................. 54
Figure 4.22 Error message if application is not restarted ...................................................................... 55
Figure 4.23 Error message about uninstalling the application .............................................................. 55
Figure 5.1 Starting Offboard Diagnostic Information System Service ................................................. 62
Figure 5.2 Message stating the license will soon expire ....................................................................... 56
Figure 5.3 Logging into the group systems for extending a license ...................................................... 56
Figure 5.4 Success message when the license has been extended......................................................... 57
Figure 5.5 Error message when extending the license .......................................................................... 57
Figure 5.6 Window with warnings and notes (part 1) ........................................................................... 58
Figure 5.7 Window with warnings and notes (part 2) ........................................................................... 59
Figure 5.8 Message regarding transmission of the diagnostic log ........................................................ 60
Figure 5.9 Wi-Fi warning message and expiration date in the future ................................................... 61
Figure 5.10 Wi-Fi warning message for expiration on the same day .................................................... 61
Figure 5.11 Wi-Fi warning message for an expired certificate ............................................................. 61
Figure 5.12 Offboard Diagnostic Information System Service user interface ...................................... 63
Figure 5.13 The Info area ...................................................................................................................... 64
Figure 5.14 Display when there are connection problems with the VCI .............................................. 65
Figure 5.15 Note dialog when there are connection problems with the VCI ........................................ 65
Figure 5.16 Operating Modes menu ...................................................................................................... 67
Figure 5.17 Standard Functions menus ................................................................................................. 69
Figure 5.18 Log submenu ...................................................................................................................... 69
Figure 5.19 Data submenu..................................................................................................................... 70
Figure 5.20 Extras submenu .................................................................................................................. 71
Figure 5.21 Help submenu .................................................................................................................... 71
Figure 5.22 Info submenu ..................................................................................................................... 72
Figure 5.23 Trace submenu ................................................................................................................... 72
Figure 5.24 Legal Submenu .................................................................................................................. 73
Figure 5.25 Status area - sample test plan calculation ........................................................................... 73
Figure 5.26 Making a screenshot .......................................................................................................... 75
Figure 5.27 Support request with a screenshot ...................................................................................... 75
Figure 5.28 Note from the control module with Negative Response Code ........................................... 76
Figure 6.1 Diagnostic entry process ...................................................................................................... 81
Figure 6.2 Diagnostic Entry .................................................................................................................. 82
Figure 6.3 Entry window after starting the application ......................................................................... 83
Figure 6.4 Connecting the Vehicle section............................................................................................ 84
Figure 6.5 Note about specifying a unique diagnostic interface ........................................................... 85
Figure 6.6 VIN read automatically ........................................................................................................ 85
Figure 6.7 Entering the VIN manually .................................................................................................. 86
Figure 6.8 Start Diagnosis section ......................................................................................................... 86
Figure 6.9 Diagnostic entry start window ............................................................................................. 87
Figure 6.10 Unpermitted Bluetooth connection .................................................................................... 88
Figure 6.11 Battery not connected......................................................................................................... 89
Figure 6.12 Ignition is switched off ...................................................................................................... 89
Figure 6.13 Ignition status not recognized ............................................................................................ 90
Figure 6.14 Status area - example of determining a VIN ...................................................................... 91
Figure 6.15 Performing the Vehicle Features Dialog section ............................................................... 92
Figure 6.16 Dialog for selecting vehicle equipment.............................................................................. 92
Figure 6.17 Error during automatic identification ................................................................................. 93
Figure 6.18 VIN not found .................................................................................................................... 94
Figure 6.19 Entering the VIN manually ................................................................................................ 94
Figure 6.20 Logging in to Group Systems section ................................................................................ 96
Figure 6.21 SecurID card ...................................................................................................................... 98
Figure 6.22 Create PIN .......................................................................................................................... 99
Figure 6.23 Assign PIN ......................................................................................................................... 99
Figure 6.24 Check the PIN and confirm it with the token ................................................................... 100
Figure 6.25 PIN created successfully .................................................................................................. 100
Figure 6.26 Password input screen ...................................................................................................... 101
Figure 6.27 Group Retail Portal input screen ...................................................................................... 102
Figure 6.28 Warning message when the Wi-Fi connection quality is poor......................................... 103
Figure 6.29 Low battery warning message.......................................................................................... 103
Figure 6.30 Error dialog for invalid MCD project .............................................................................. 104
Figure 6.31 Error message when there is a conflict between the MCD project and the Administration
setting .................................................................................................................................................. 105
Figure 6.32 Request to change the communication method ................................................................ 105
Figure 6.33 Vehicle connection through DoIP failed .......................................................................... 106
Figure 6.34 Vehicle search unsuccessful............................................................................................. 106
Figure 6.35 Loss of connection with VAS6154(A)............................................................................. 107
Figure 6.36 Using the K line adapter................................................................................................... 108
Figure 6.37 Information dialog about the customer satisfaction survey ............................................. 109
Figure 6.38 Work order selection section - diagnostic entrance ......................................................... 109
Figure 6.39 Work order selection section - Flash entrance ................................................................. 110
Figure 6.40 Order view during diagnostic entry ................................................................................. 111
Figure 6.41 Login to group systems not possible ................................................................................ 113
Figure 6.42 Order list view.................................................................................................................. 114
Figure 6.43 Order detail view.............................................................................................................. 115
Figure 6.44 No DISS concerns ............................................................................................................ 116
Figure 6.45 Entering the RO number .................................................................................................. 116
Figure 6.46 "Work without order" selection ....................................................................................... 117
Figure 6.47 Identifying Control Modules section ............................................................................... 118
Figure 6.48 Gateway control module malfunction in communication ................................................ 119
Figure 6.49 Communication malfunction Gateway control module with communication test ........... 120
Figure 6.50 "Check components list" dialog ....................................................................................... 121
Figure 6.51 Editing the coding status .................................................................................................. 122
Figure 6.52 "Unrecognized control modules" dialog .......................................................................... 123
Figure 6.53 "Working with base variant" dialog ................................................................................. 124
Figure 6.54 Control module list view .................................................................................................. 125
Figure 6.55 Control module information............................................................................................. 126
Figure 6.56 Sorting the control module list ......................................................................................... 126
Figure 6.57 Networking diagram view ................................................................................................ 128
Figure 6.58 Buttons for individual control modules ........................................................................... 130
Figure 6.59 Context menu (control module buttons) .......................................................................... 131
Figure 6.60 Entering a Control Module as Installed ........................................................................... 131
Figure 6.61 Italic display of control modules manually entered as installed ...................................... 132
Figure 6.62 "Select version" dialog ..................................................................................................... 132
Figure 6.63 Selecting control module guided functions ...................................................................... 133
Figure 6.64 DTC memory entries view ............................................................................................... 134
Figure 6.65 Opening a DTC memory entry......................................................................................... 135
Figure 6.66 Information about a DTC memory entry ......................................................................... 135
Figure 6.67 Sorting DTC list ............................................................................................................... 136
Figure 6.68 Context menu in the DTC memory view ......................................................................... 137
Figure 6.69 Equipment list view ......................................................................................................... 138
Figure 6.70 Equipment list context menu............................................................................................ 139
Figure 6.71 Select version ................................................................................................................... 140
Figure 6.72 Inactive tab „Components list“ ........................................................................................ 141
Figure 6.73 Starting GFF section ........................................................................................................ 141
Figure 6.74 Starting Guided Fault Finding.......................................................................................... 142
Figure 6.75 Test plan and special functions section ............................................................................ 144
Figure 6.76 Start module, traversal test, test plan calculation section ................................................. 144
Figure 6.77 Version selection view ..................................................................................................... 145
Figure 6.78 DISS / TSB section .......................................................................................................... 147
Figure 6.79 View inside the DISS tab after the diagnostic entrance ................................................... 147
Figure 6.80 Table with DISS concerns................................................................................................ 148
Figure 6.81 Coding assistant dialog window ...................................................................................... 149
Figure 6.82 Example of out-of-date DISS concern ............................................................................. 150
Figure 6.83 Function buttons in the DISS tab ..................................................................................... 151
Figure 6.87 Transfer diagnostic object to test plan ............................................................................. 152
Figure 6.88 Deselected customer code ................................................................................................ 153
Figure 6.89 Selecting the complete view ............................................................................................ 154
Figure 6.90 Complete view of a customer code .................................................................................. 155
Figure 6.91 Coding assistant ............................................................................................................... 156
Figure 6.92 Special Functions view .................................................................................................... 158
Figure 6.93 Working with GFF section............................................................................................... 159
Figure 6.94 View of test plan version 1 .............................................................................................. 160
Figure 6.95 View of test plan version 2 - cause-specific diagnosis .................................................... 161
Figure 6.96 Activating a test in the test plan ....................................................................................... 163
Figure 6.97 Sporadic DTC memory entry decision dialog .................................................................. 164
Figure 6.98 Note when executing test programs with “unauthorized DTC memory entries”. ............ 165
Figure 6.99 Test view in the Operation tab ......................................................................................... 166
Figure 6.100 Message and instruction window in the test procedure ................................................. 168
Figure 6.101 Sequence of steps in the test procedure.......................................................................... 169
Figure 6.102 Screen buttons to select alternate test steps.................................................................... 170
Figure 6.103 Display of selected test steps ......................................................................................... 171
Figure 6.104 Decision buttons in the test program.............................................................................. 172
Figure 6.105 Print button in the test program...................................................................................... 173
Figure 6.106 Measurement selection ................................................................................................... 174
Figure 6.107 Measured values display (measured value table) ........................................................... 175
Figure 6.108 Description of a measurement........................................................................................ 176
Figure 6.109 Measured values display (ODX data) ............................................................................ 177
Figure 6.110 Selection of control module to be coded ........................................................................ 178
Figure 6.111 Display of the coded/not coded control modules in the test program ............................ 179
Figure 6.112 Special coding - brand selection .................................................................................... 180
Figure 6.113 Inquiry before writing the Gateway coding ................................................................... 180
Figure 6.114 Inquiry with changed coding.......................................................................................... 181
Figure 6.115 Function descriptions in the test program ...................................................................... 182
Figure 6.116 Local and global documents in the test program ........................................................... 183
Figure 6.117 Document view .............................................................................................................. 184
Figure 6.118 Verification mode inquiry .............................................................................................. 185
Figure 6.119 Test selection window.................................................................................................... 186
Figure 6.120 Help window .................................................................................................................. 188
Figure 6.121 Equipment documentation (BZD) for components that are not diagnostic-capable ...... 189
Figure 6.122 Message dialog for incorrect check sums ...................................................................... 190
Figure 6.123 Message dialog for errors in scanned data ..................................................................... 191
Figure 6.124 “Quick View in Workshop Information” button ............................................................ 192
Figure 6.125 “Quick view is not supported for the vehicle” message ................................................ 193
Figure 6.126 “Currently no analysis codes” message ......................................................................... 193
Figure 6.127 “Quick View in Workshop Information” dialog ............................................................ 194
Figure 6.128 End Diagnosis section .................................................................................................... 195
Figure 6.129 End Diagnosis ................................................................................................................ 196
Figure 6.130 Ending fault finding ....................................................................................................... 197
Figure 6.131 Ending fault finding when the test plan is completed .................................................... 197
Figure 6.132 Note about changing the vehicle .................................................................................... 198
Figure 6.133 Erases the DTC memory ................................................................................................ 198
Figure 6.134 Performing the readiness code program ......................................................................... 199
Figure 6.135 Send diagnostic log? ...................................................................................................... 200
Figure 6.136 Print/save diagnostic log ................................................................................................ 201
Figure 6.137 Select diagnostic log ...................................................................................................... 201
Figure 6.138 Support request .............................................................................................................. 202
Figure 6.139 Manual control module selection ................................................................................... 204
Figure 6.140 Quick entrance test plan ................................................................................................. 205
Figure 6.141 Print/save diagnostic log ................................................................................................ 206
Figure 6.142 Diagnostic entry process without a vehicle:................................................................... 207
Figure 6.143 Start screen for diagnostic entry without a vehicle: ....................................................... 208
Figure 6.144 Error message in the start screen.................................................................................... 209
Figure 6.145 Test plan view during diagnosis without a vehicle ........................................................ 209
Figure 6.146 Sample control module list for diagnosis without a vehicle .......................................... 210
Figure 6.147 Notice about detected vehicle ........................................................................................ 211
Figure 6.148 Selecting a document to display..................................................................................... 212
Figure 6.149 Viewing a document ...................................................................................................... 213
Figure 6.150 Example 1, document tree .............................................................................................. 214
Figure 6.151 Example 1, document view ............................................................................................ 215
Figure 6.152 Example 2, document tree .............................................................................................. 216
Figure 6.155 Document with Hot Spot................................................................................................ 217
Figure 6.156 Open Hot Spot................................................................................................................ 218
Figure 6.157 Displaying documents for a test plan ............................................................................. 219
Figure 7.1 OBD entry start window .................................................................................................... 221
Figure 7.2 Control modules tab in the OBD operating mode .............................................................. 222
Figure 7.3 Example of OBD view in adaptation ................................................................................. 224
Figure 7.4 Starting OBD ..................................................................................................................... 227
Figure 7.5 Control module OBD selection window ............................................................................ 228
Figure 7.6 Vehicle OBD selection window......................................................................................... 229
Figure 7.7 Control module OBD selection window during diagnostic entry ...................................... 230
Figure 7.8 Vehicle OBD selection window during diagnostic entry ................................................... 230
Figure 7.9 OBD: sample tab name ...................................................................................................... 233
Figure 7.10 Warning about adaptation that is not supported ............................................................... 234
Figure 7.11 Selection of function versions .......................................................................................... 236
Figure 7.12 KWP adaptation ............................................................................................................... 237
Figure 7.13 Resetting the adaptation ................................................................................................... 238
Figure 7.14 UDS adaptation ................................................................................................................ 240
Figure 7.15 Warning when closing the parameter list ......................................................................... 241
Figure 7.16 Dialog for input assistance for special parameter values ................................................. 242
Figure 7.17 Security prompt before performing the adaptation .......................................................... 243
Figure 7.18 Error message about invalid adaptation value ................................................................. 243
Figure 7.19 The adaptation function is not supported ......................................................................... 244
Figure 7.20 Error message for control module that is not a bus master .............................................. 244
Figure 7.21 Coding KWP bus masters ................................................................................................ 246
Figure 7.22 Security prompt before coding ......................................................................................... 246
Figure 7.23 Progress bars during coding ............................................................................................. 247
Figure 7.24 Error when coding (example) .......................................................................................... 247
Figure 7.25 Editing special code ......................................................................................................... 248
Figure 7.26 Coding UDS bus masters ................................................................................................. 249
Figure 7.27 Security prompt before automatic coding ........................................................................ 249
Figure 7.29 Error when coding (example) .......................................................................................... 250
Figure 7.30 Short coding ..................................................................................................................... 251
Figure 7.31 Security prompt before coding ......................................................................................... 252
Figure 7.32 Confirmation message after coding ................................................................................. 252
Figure 7.33 Prompt to reset the ignition .............................................................................................. 252
Figure 7.34 New and old code............................................................................................................. 253
Figure 7.35 Error message when coding due to incorrect data ........................................................... 253
Figure 7.36 UDS binary coding .......................................................................................................... 255
Figure 7.37 KWP long coding ............................................................................................................. 255
Figure 7.38 User input with binary coding .......................................................................................... 256
Figure 7.39 Security prompt before binary coding.............................................................................. 257
Figure 7.40 Note about missing check sum for binary code ............................................................... 258
Figure 7.41 Note about incorrect check sum for binary code ............................................................. 258
Figure 7.42 Confirmation message after coding ................................................................................. 258
Figure 7.43 Prompt to reset the ignition .............................................................................................. 259
Figure 7.44 Warning when changing to plain text coding .................................................................. 259
Figure 7.45 UDS plain text coding ...................................................................................................... 260
Figure 7.46 The coding function is not supported ............................................................................... 261
Figure 7.47 Coding subsystems........................................................................................................... 262
Figure 7.48 Security prompt before accepting the coding................................................................... 263
Figure 7.52 Progress bars during the restoration ................................................................................. 265
Figure 7.53 Progress bars during the update ....................................................................................... 265
Figure 7.54 Coding software compositions ......................................................................................... 266
Figure 7.57 Error when coding software compositions (example) ..................................................... 267
Figure 7.60 Progress bars during the restoration ................................................................................. 268
Figure 7.61 Progress bars during the update ....................................................................................... 269
Figure 7.62 KWP DTC memory ......................................................................................................... 269
Figure 7.63 Sorting the DTC memory entries ..................................................................................... 270
Figure 7.64 UDS DTC Memory .......................................................................................................... 272
Figure 7.66 KWP Basic Setting .......................................................................................................... 274
Figure 7.67 UDS basic setting - basic setting selection ...................................................................... 276
Figure 7.68 UDS basic setting - setting parameters ............................................................................ 277
Figure 7.69 UDS basic setting - measured value selection ................................................................. 278
Figure 7.70 UDS basic setting - performing ....................................................................................... 280
Figure 7.71 The basic setting function is not supported ...................................................................... 282
Figure 7.72 Remote access warning .................................................................................................... 282
Figure 7.73 Results window for OBD identification........................................................................... 283
Figure 7.74 Measured value selection ................................................................................................. 285
Figure 7.75 KWP - Measured value display ....................................................................................... 286
Figure 7.76 The measured values function is not supported ............................................................... 287
Figure 7.78 KWP Output Diagnostic Test Mode ................................................................................ 288
Figure 7.79 Output Diagnostic Test Mode Status ............................................................................... 289
Figure 7.80 UDS actuator selection..................................................................................................... 290
Figure 7.81 Setting UDS actuator parameters ..................................................................................... 292
Figure 7.82 UDS output diagnostic test mode - problems with setting parameters ............................ 293
Figure 7.83 UDS Measured Value Selection ...................................................................................... 294
Figure 7.84 UDS Output Diagnostic Test Mode ................................................................................. 295
Figure 7.85 Example of an actuator test on several actuators ............................................................. 297
Figure 7.86 The output diagnostic test mode function is not supported .............................................. 298
Figure 7.87 Remote access warning .................................................................................................... 298
Figure 7.88 Access Authorization ....................................................................................................... 299
Figure 7.89 Access authorization - successful .................................................................................... 300
Figure 7.90 Access authorization - unsuccessful ................................................................................ 301
Figure 7.91 Access authorization is not supported. ............................................................................. 301
Figure 7.92 Access authorization with online tokens .......................................................................... 302
Figure 7.93 Check for available SFD activation tokens ...................................................................... 303
Figure 7.94 Preparation of SFT activation request structure for manual SFD activation ................... 303
Figure 7.95 Entering the activation token for manual SFD activation ................................................ 304
Figure 7-96 Error dialog when loading invalid token data from a file ................................................ 304
Figure 7-97 Error dialog when there is invalid token data in the clipboard ........................................ 305
Figure 7.96 Access authorization - successful .................................................................................... 305
Figure 7.97Access authorization - unsuccessful ................................................................................. 305
Figure 7.98 Results window for OBD data upload ............................................................................. 306
Figure 7.99 Detail dialog for all diagnostic requirements that are not met ......................................... 307
Figure 7.100 Selection dialog when there are existing local data sets ................................................ 308
Figure 7.101 Identification selection ................................................................................................... 309
Figure 7.102 Multiple identification data display ............................................................................... 310
Figure 7.103 Multiple identification data function not supported ....................................................... 311
Figure 7.104 Complete System DTC Memory.................................................................................... 312
Figure 7.105 Selecting the method of erasing the DTC memory ........................................................ 313
Figure 7.106 Warning message before erasing the DTC memory ...................................................... 313
Figure 7.107 Transport Mode .............................................................................................................. 314
Figure 7.108 Message indicating the switch to transport mode was successful .................................. 315
Figure 7.109 Transport error ............................................................................................................... 315
Figure 7.110 Transport mode is not supported. ................................................................................... 316
Figure 7.111 Components List ............................................................................................................ 316
Figure 7.112 Display when there is faulty communication with a control module ............................. 317
Figure 7.113 The OBD function is selected ........................................................................................ 318
Figure 7.114 The OBD parameter is selected ..................................................................................... 319
Figure 7.115 OBD result display ......................................................................................................... 320
Figure 7.116 End OBD........................................................................................................................ 322
Figure 7.117 Confirm end of OBD...................................................................................................... 322
Figure 7.118 Saving the OBD log ....................................................................................................... 323
Figure 8.1 Work Process in Flashing Mode ........................................................................................ 324
Figure 8.2 Starting Flashing Section ................................................................................................... 325
Figure 8.3 Flash entry start window .................................................................................................... 327
Figure 8.4 Identifying the Vehicle Section.......................................................................................... 327
Figure 8.5 Vehicle Analysis during Flash Entry ................................................................................. 328
Figure 8.6 Manual vehicle identification............................................................................................. 329
Figure 8.7 Automatic vehicle identification ........................................................................................ 330
Figure 8.8 Warning message when the Wi-Fi connection quality is poor........................................... 331
Figure 8.9 Logging in to Group Systems section ................................................................................ 331
Figure 8.10 Group Systems Login Window ........................................................................................ 331
Figure 8.11 Selecting an Order Section............................................................................................... 333
Figure 8.12 Selecting an Order for Flashing ....................................................................................... 333
Figure 8.13 Identifying Control Modules section ............................................................................... 335
Figure 8.14 Control Module Identification ......................................................................................... 335
Figure 8.15 Running Flash Programs Section ..................................................................................... 336
Figure 8.16 Available Flash Programs ................................................................................................ 336
Figure 8.17 Estimated time remaining in a flashing process ............................................................... 337
Figure 8.18 Basic features manual selection ....................................................................................... 338
Figure 8.19 Manual control module selection ..................................................................................... 338
Figure 8.20 Ending Flashing Section .................................................................................................. 339
Figure 8.21 Ending the Flash Session ................................................................................................. 339
Figure 8.22 Ending the Flash Session ................................................................................................. 340
Figure 8.23 Erase DTC memory ......................................................................................................... 340
Figure 9.1 “Active diagnostic filter” message dialog .......................................................................... 341
Figure 9.2 “Active diagnostic filter missing access authorization” message dialog ........................... 342
Figure 9.3 Prompt to try activation again when there is an active diagnostic filter ............................ 342
Figure 1.1: Measuring equipment user interface - multimeter ............................................................ 344
Figure 1.2: Layout of the multimeter client area ................................................................................. 345
Figure 1.3: Min/Max measured value display ..................................................................................... 346
Figure 1.4: layout of the multimeter client area .................................................................................. 347
Figure 1.5: buttons for measuring parameters ..................................................................................... 349
Figure 1.6: DC measured value display .............................................................................................. 349
Figure 1.7: AC measured value display .............................................................................................. 350
Figure 1.8: client area when the “URDI voltage” measurement is active ........................................... 352
Figure 1.9: client area when “URDI current” measurement is active ................................................. 353
Figure 1.10: client area when “URDI resistance” measurement is active ........................................... 354
Figure 1.11: client area when “URDI diode test” is active ................................................................. 355
Figure 1.12: client area when “URDI continuity test” is active .......................................................... 356
Figure 1.13: client area when “DSO1” voltage measurement is activated .......................................... 357
Figure 1.14: client area when the “current clamp” measurement is active ......................................... 358
Figure 1.15: client area when “Pressure/TD” measurement is activated............................................. 359
Figure 1i16: client area when “Temperature T/D” measurement is active ......................................... 360
Figure 1.17: Layout of the oscilloscope client area ............................................................................. 361
Figure 1.18: “Oscilloscope” display area ............................................................................................ 362
Figure 1.19: setting channel A parameters .......................................................................................... 365
Figure 1.20: Setting the measuring mode ............................................................................................ 369
Figure 1.21: Setting parameters for long-term measurement .............................................................. 372
Figure 1.22: Evaluating the long-term measurement .......................................................................... 373
Figure 1.23: Setting parameters for the trigger.................................................................................... 376
Figure 1.24: Client area of the specified curves function ................................................................ - 379 -
Figure 1.25: Plotting specified curves ............................................................................................. - 381 -
Figure 1.26: Plotting specified curves for two channels ................................................................. - 381 -
Figure 1.27: Displaying specified curves ........................................................................................ - 382 -
Figure 1.28: Display area in night mode ......................................................................................... - 384 -
Figure 1.29: Display area in day mode ............................................................................................ - 385 -
Figure 1.30: Displaying diagnostic measured values in the multimeter .......................................... - 387 -
Figure 1.31: Displaying diagnostic measured values in the oscilloscope ....................................... - 387 -
Figure 1.32: Enabling expert mode in the specified curves function .............................................. - 389 -
Figure 12.1 Administration window................................................................................................ - 390 -
Figure 12.2 Selecting the Design .................................................................................................... - 394 -
Figure 12.3 Language setting .......................................................................................................... - 395 -
Figure 12.4 Additional Windows language support ........................................................................ - 396 -
Figure 12.5 Windows language display codes ................................................................................ - 397 -
Figure 12.6 Update view ................................................................................................................. - 398 -
Figure 12.7 Configuration error when checking for updates........................................................... - 399 -
Figure 12.8 System configuration view........................................................................................... - 400 -
Figure 12.9 System environment view ............................................................................................ - 401 -
Figure 12.10 License Information Part 1 View ............................................................................... - 402 -
Figure 12.11 License Information Part 2 View ............................................................................... - 403 -
Figure 12.12 Global configuration view ......................................................................................... - 404 -
Figure 12.13 GFF procedure details view ....................................................................................... - 405 -
Figure 12.14 View of the dealer data details ................................................................................... - 406 -
Figure 12.15 Database Directory..................................................................................................... - 408 -
Figure 12.16 Diagnostic Session Save Location ............................................................................. - 409 -
Figure 12.17 Flash paths view ......................................................................................................... - 411 -
Figure 12.18 Diagnostic log view ................................................................................................... - 412 -
Figure 12.19 Support view .............................................................................................................. - 415 -
Figure 12.20 Support view .............................................................................................................. - 416 -
Figure 12.21 E-mail Outbox Server View ....................................................................................... - 417 -
Figure 12.22 Error message about an incorrect mail server ............................................................ - 420 -
Figure 12.23 Error message about an incorrect sender address....................................................... - 420 -
Figure 12.24 Hardware and software view...................................................................................... - 421 -
Figure 12.25 Brand Settings View .................................................................................................. - 422 -
Figure 12.26 Group system view: Logon ........................................................................................ - 423 -
Figure 12.27 Group System: GFF ................................................................................................... - 424 -
Figure 12.28 Group system ElsaPro view ....................................................................................... - 425 -
Figure 12.29 Carport View .............................................................................................................. - 427 -
Figure 12.30 DISS View ................................................................................................................. - 428 -
Figure 12.31 Group system eShop view.......................................................................................... - 429 -
Figure 12.32 Group system view: Login ......................................................................................... - 430 -
Figure 12.33 Mirror server 2 view .................................................................................................. - 431 -
Figure 12.34 Support application view ........................................................................................... - 432 -
Figure 12.35 Client certificates view............................................................................................... - 433 -
Figure 12.36 The hardware ID in the client certificate does not match .......................................... - 434 -
Figure 12.37 The validity period has expired. ................................................................................. - 434 -
Figure 12.38 The format is not supported. ...................................................................................... - 435 -
Figure 12.39 Client certificate detail view ...................................................................................... - 436 -
Figure 12.40 Trust certificate view ................................................................................................. - 438 -
Figure 12.41 The validity period has expired. ................................................................................. - 439 -
Figure 12.42 The format is not supported. ...................................................................................... - 439 -
Figure 12.43 Trust certificate detailed view .................................................................................... - 440 -
Figure 12.44 Data configuration view ............................................................................................. - 442 -
Figure 13.1 Screen button log ......................................................................................................... - 444 -
Figure 13.2 Diagnostic log selection ............................................................................................... - 446 -
Figure 13.3 Successfully sent diagnostic log .................................................................................. - 447 -
Figure 13.4 Error when sending diagnostic log............................................................................... - 447 -
Figure 13.5 Successful diagnostic log transmission multiple selection .......................................... - 448 -
Figure 13.6 Faulty diagnostic log transmission multiple selection ................................................. - 448 -
Figure 13.7 Maximum number of values exceeded ........................................................................ - 450 -
Figure 13.8 Data button ................................................................................................................... - 451 -
Figure 13.9 Query when canceling a diagnostic session ................................................................. - 453 -
Figure 13.10 Saving a diagnostic session ........................................................................................ - 454 -
Figure 13.11 Warning when VIN was entered manually ................................................................ - 455 -
Figure 13.12 Feedback after Saving a Diagnostic Session .............................................................. - 455 -
Figure 13.13 Loading a diagnostic session file ............................................................................... - 457 -
Figure 13.14 No vehicle with battery voltage connected ................................................................ - 458 -
Figure 13.15 Out-of-date diagnostic session ................................................................................... - 459 -
Figure 13.16 Error when loading a diagnostic session .................................................................... - 460 -
Figure 13.17 Login when loading a diagnostic session ................................................................... - 460 -
Figure 13.18 Selecting the hotfix directory ..................................................................................... - 462 -
Figure 13.19 Hotfix already loaded ................................................................................................. - 463 -
Figure 13.20 Error while loading the hotfix .................................................................................... - 463 -
Figure 13.21 Hotfix baseline version error...................................................................................... - 464 -
Figure 13.22 Copying the hotfix ..................................................................................................... - 464 -
Figure 13.23 Installing the hotfix .................................................................................................... - 465 -
Figure 13.24 Error while installing the hotfix ................................................................................. - 465 -
Figure 13.25 Hotfix installation successful ..................................................................................... - 466 -
Figure 13.26 Reinitializing GFF after loading a hotfix ................................................................... - 466 -
Figure 13.27 Hotfix deleted successfully ........................................................................................ - 467 -
Figure 13.28 Reinitializing GFF after deleting a hotfix .................................................................. - 467 -
Figure 13.29 Loading test baseline.................................................................................................. - 468 -
Figure 13.30 Confirming loading the test baseline.......................................................................... - 468 -
Figure 13.31 Loading in the background ........................................................................................ - 469 -
Figure 13.32 Loading the test baseline ............................................................................................ - 469 -
Figure 13.33 Loading test baseline canceled by user ...................................................................... - 469 -
Figure 13.34 Error when loading the test baseline .......................................................................... - 470 -
Figure 13.35 Test baseline loaded correctly .................................................................................... - 470 -
Figure 13.36 Updating the test baseline .......................................................................................... - 471 -
Figure 13.37 Sending a diagnostic log with test baseline................................................................ - 471 -
Figure 13.38 Extras Menu Content ................................................................................................. - 472 -
Figure 13.39 Search function form.................................................................................................. - 473 -
Figure 13.40 Search function results display .................................................................................. - 474 -
Figure 13.41 Search result example ................................................................................................ - 475 -
Figure 13.42 Specifying the diagnostic interface ............................................................................ - 476 -
Figure 13.43 Detailed information regarding the current diagnostic interface ............................... - 477 -
Figure 13.44 Wi-Fi connection quality display ............................................................................... - 478 -
Figure 13.45 No Wi-Fi connection.................................................................................................. - 478 -
Figure 13.46 Activating the road test mode .................................................................................... - 479 -
Figure 13.47 Confirming the activated road test mode ................................................................... - 480 -
Figure 13.48 Request to switch to “Wi-Fi access point”................................................................. - 481 -
Figure 13.49 Message about the switch to road test mode being canceled ..................................... - 481 -
Figure 13.50 End road test mode ..................................................................................................... - 482 -
Figure 13.51 Confirming the canceled road test mode .................................................................... - 483 -
Figure 13.52 Confirming the ended road test mode ........................................................................ - 483 -
Figure 13.53 Group system access in road test mode...................................................................... - 484 -
Figure 13.54 Ending road test mode without a network connection ............................................... - 485 -
Figure 13.55 Request to switch to “Wi-Fi infrastructure”............................................................... - 486 -
Figure 13.56 Message about canceling the switch to infrastructure mode ...................................... - 486 -
Figure 13.57 Notes when starting a manual update......................................................................... - 487 -
Figure 13.58 Selecting a brand for the connection test ................................................................... - 488 -
Figure 13.59 Connection test configuration .................................................................................... - 489 -
Figure 13.60 Connection test is being performed............................................................................ - 490 -
Figure 13.61 No DoIP diagnostic interface selected ....................................................................... - 491 -
Figure 13.62 DoIP diagnostic interface cannot be connected ......................................................... - 491 -
Figure 13.63 Successful DoIP connection test ................................................................................ - 491 -
Figure 13.64 Successful DoIP connection test with multiple DoIP vehicles as the result .............. - 492 -
Figure 13.65 Result of second stage of DoIP connection test ......................................................... - 492 -
Figure 13.66 Error during DoIP connection test ............................................................................. - 493 -
Figure 13.67 DoIP connection test progress dialog......................................................................... - 493 -
Figure 13.68 Help menu .................................................................................................................. - 494 -
Figure 13.69 Online Help ................................................................................................................ - 495 -
Figure 13.70 Navigation menu ........................................................................................................ - 495 -
Figure 13.71 Context-Based Online Help ....................................................................................... - 496 -
Figure 13.72 The Online Help window ........................................................................................... - 497 -
Figure 13.73 Searching in Online Help ........................................................................................... - 498 -
Figure 13.74 Menu bar in Online Help ........................................................................................... - 498 -
Figure 13.75 Open support request in a different version ............................................................... - 500 -
Figure 13.76 Support Request via Email ......................................................................................... - 500 -
Figure 13.77 End support request.................................................................................................... - 501 -
Figure 13.78 Error while saving a support request.......................................................................... - 502 -
Figure 13.79 Error while saving a support request (2) .................................................................... - 503 -
Figure 13.80 Information about feedback sender ............................................................................ - 503 -
Figure 13.81 Error classification feedback ...................................................................................... - 504 -
Figure 13.82 Error priority feedback ............................................................................................... - 505 -
Figure 13.83 Additional attachments .............................................................................................. - 505 -
Figure 13.84 Logging into the mail server for feedback ................................................................. - 506 -
Figure 13.85 Incorrect login to mail server ..................................................................................... - 507 -
Figure 13.86 Feedback message with an offline connection ........................................................... - 508 -
Figure 13.87 Support Request via the Support Application ............................................................ - 508 -
Figure 13.88 Required fields in the support application not completed .......................................... - 509 -
Figure 13.89 Error description missing in the support application ................................................. - 509 -
Figure 13.90 Required fields in the support application including error description are missing ... - 510 -
Figure 13.91 Support application sent successfully ........................................................................ - 510 -
Figure 13.92 Support application not sent successfully .................................................................. - 510 -
Figure 13.93 Support application error when creating the request.................................................. - 511 -
Figure 13.94 Support application error source ................................................................................ - 511 -
Figure 13.95 Support application priority ....................................................................................... - 511 -
Figure 13.96Support application feedback message when there is an offline connection .............. - 512 -
Figure 13.97 Troubleshooting guide: sample content ..................................................................... - 513 -
Figure 13.98 Information Area ........................................................................................................ - 514 -
Figure 13.99 Version information window ..................................................................................... - 515 -
Figure 13.100 Disclaimer – Table of Contents ............................................................................... - 516 -
Figure 13.101 Disclaimer – Chapter 1 ............................................................................................ - 516 -
Figure 13.102 Disclaimer – Chapter 2 (Part 1) ............................................................................... - 517 -
Figure 13.111 Disclaimer – Chapter 8.1 ......................................................................................... - 521 -
Figure 13.113 Disclaimer – Chapter 10 .......................................................................................... - 522 -
Figure 13.117 Legal menu............................................................................................................... - 524 -
Figure 13.118 Example of missing translations in the basic information dialog ............................ - 525 -
Figure 13.119 Example of missing translations in a test plan ......................................................... - 525 -
Figure 13.120 Example of missing translations when performing a test program .......................... - 526 -
Figure 14.1 Error message explanations ......................................................................................... - 527 -
Figure 14.2 Windows firewall message .......................................................................................... - 577 -
Figure 14.3 Browser security warning ............................................................................................ - 578 -
List of Tables
Table 5.1 Negative Response Code (NRC) from control module with KWP 2000 .............................. 79
Table 5.2 Negative Response Code from control module with KWP 1281 .......................................... 80
Table 6.1 Meaning of the SCP status numbers.................................................................................... 112
Table 6.2 Actions for the Sporadic DTC memory entry decision and result statuses for the test program
............................................................................................................................................................. 165
Table 7.1 Control Module OBD View Names .................................................................................... 232
Table 7.2 Vehicle OBD View Names ................................................................................................. 232
Table 7.3 Keyboard shortcuts table ..................................................................................................... 235
Table 8.1 Meaning of the SCP status numbers.................................................................................... 334
Table 1.1 Adjusting the time basis ...................................................................................................... 364
Table 1.2: Measuring connection accuracy ......................................................................................... 368
Table 1.3: Maximum measuring duration for a long-term measurement ............................................ 373
Table1.4: Color of measurement curves .......................................................................................... - 382 -
Table 14.1 Error IDs table ............................................................................................................... - 576 -
1 Introduction
1.1 Comments about the User Guide
This handbook describes how to use the Offboard Diagnostic Information System Service program
from the Volkswagen Group. The program is used during workshop diagnosis and can identify vehicle
control modules, read DTC memory entries and assist with vehicle repairs through Guided Fault Find-
ing. Functions such as measurement support, flashing control modules and vehicle self-diagnosis expand
the range of application. All important information and services from the Volkswagen Group are avail-
able while working via a network connection to the group systems.
Offboard Diagnostic Information System Service is designed for all brands in the Volkswagen group.
To visualize the important procedures such as diagnosis and flashing, the chapters on these topics con-
tain illustrations that show exactly which portion of the procedure is being described, what the previous
step was and what will be done next.
1.2 Structure of the User Guide

Using the Table of Contents in the PDF document is recommended in order to access the information
needed quickly. If the manual is available in electronic form, you can click directly on the desired topic
in the table of contents to go to the chapter.
Figure 1.1 Example of an active link in the table of contents

The blue pushpin is generally used for bullet points or to structure the procedures within the system.
Notice:
The red pushpin with the word Notice: and a frame (for black and white printouts) indicates especially
important notes that must be followed.
Note:
This symbol is used for supplementary information and useful tips.
Font types:
All system components such as menus, interfaces, buttons, keyboards or touchscreen are written in bold
font. This makes it easier to search within the manual and in Offboard Diagnostic Information System
Service. File names or paths are shown in italic font.
Example: "The vehicle basic features must be selected after clicking the Start diagnosis button. The
Vehicle features form appears."
Cross-reference:
You can switch to related topics quickly using the cross-references in this user guide. These are also
linked in electronic form.
Cross-reference:
The following chapter, Name of Chapter, contains additional information.
Figure 1.2 Example of the Diagnosis Procedure
In the example shown above, the entire diagnosis procedure is presented. The diagnosis procedure is
divided into four sections with each section containing the individual steps. The section that is currently
being described is shown in red.
The description of the individual sections with the individual steps appears as shown below:
Figure 1.3 Example of a section of a procedure with individual steps

This example shows the individual steps in their logical, chronological order. The step that is currently
being described is shown in red.
Notice:
This manual should be read completely before using Offboard Diagnostic Information System Ser-
vice for the first time. The warnings and notes regarding working with Offboard Diagnostic Infor-
mation System Service and the vehicle during diagnostic and repair procedures must be followed ex-
actly.
Currentness of illustrations: all illustrations are up-to-date, even if they have an older version number.
2 System Requirements
The following conditions must be met to use Offboard Diagnostic Information System Service:
Hardware requirements
VAS6154(A)
- Multi-core CPU 2GHz or higher recommended
RAM >= 4 GB (8 GB recommended)
Hard disk storage > 30 GB, NTFS standard file system. The application uses default Windows paths
for installation.
Supported tester hardware
VAS6150D
VAS6150E
VAS6160
Software requirements
Windows 10, 64-bit
Libraries (DLL) for Microsoft Visual Studio 2019
Internet Explorer 11.0
Adobe Acrobat Reader Version 11 or Adobe Acrobat Reader DC

“Arial Unicode MS Regular” font
Notice:
The required libraries for Microsoft Visual Studio 2019 are displayed in the Windows system settings
for “Apps & Features” as “Microsoft Visual C++ 2015-2019 Redistributable (x64)...”. Without these
libraries, a tester cannot generate a hardware key, which makes it impossible to purchase a license for
the unit in the Offboard Diagnostic Information System eShop.
The local administrator must be informed if the required files are not available.
3 Installation
This chapter covers the Offboard Diagnostic Information System Service installation procedure.
Notice:
If an older version of Offboard Diagnostic Information System Service is already installed on the
device, the older version must be removed before you can start installing the current Offboard Diag-
nostic Information System Service.
Administrator rights for the operating system on the tester or laptop are required to install, remove and
configure Offboard Diagnostic Information System Service.
There are two possible installation options.
The first option is online installation:
Open the e-mail received from the eShop.
Download the license certificate through the eShop.
Click the URL in the e-mail to reach the versions of the installation file (setup.exe) on the Mir-
rorserver 2.
Save setup.exe in any directory.
Double click the saved setup.exe to start the installation wizard.
The section option is offline installation:
Download the license certificate through the eShop.
Insert the DVD with the installation data into the drive.
Once the DVD starts, select the version that was ordered.
Click the correct setup.exe to start the installation wizard.
Notice:
With the offline installation, it is important to install the version of Offboard Diagnostic Information
System Service that was ordered. If the setup.exe file for a different version is installed, it will not be
possible to start the application because the license will not match.
The installation wizard starts.
Figure 3.1 Starting installation
Cancel: you can cancel the Offboard Diagnostic Information System Service installation by clicking
on this button.
The preferred language for the installation must be selected.
Figure 3.2 Installation language selection
When selecting a language, click the List field to select the desired language for Offboard Diagnostic
Information System Service. German is displayed as the default language.
OK: The selection is confirmed.
Cancel: the installation is canceled.
After selecting the language, a message appears instructing you to close all open programs.
Figure 3.3 The Offboard Diagnostic Information System Service Setup Assistant
Next: the installation of Offboard Diagnostic Information System Service continues.
Notice:
Open programs should be closed before installing the Offboard Diagnostic Information System Ser-
vice to ensure that the Offboard Diagnostic Information System Service is installed correctly.
The default target folder is C:\Program Files (x86)\Offboard_Diagnostic_Information_System_Service
The path may differ if the operating system is in another language.
For example, C:\Program Files\Offboard_Diagnostic_Information_System_Service

Using the list field Target platform, you must now select the device on which Offboard Diagnostic
Information System Service will be installed.
Figure 3.4 Platform selection
With diagnostic systems, the type of diagnostic system is selected here. Always select Standard
PC/notebook for PCs or notebooks as long as the device is not listed separately in the list.
Back: the installation goes back one step.
Select the desired diagnostic interface using the Diagnostic interface list field.
Figure 3.5 Diagnostic interface selection

Figure 3.6 VAS 6154(A) Host name
If VAS6154(A) was selected, the screen for entering a host name appears. Entering a host name is op-
tional and can be skipped. The permitted characters can be displayed using the question mark symbol to
the right of the input field.
Notice:
To install and use a remote diagnosis head, please refer to the document Installation and Operation on
VAS 6150 from Base CD 15 and higher version 1.11.
A valid certificate is assigned to the Offboard Diagnostic Information System Service when selecting
the file with the certificate. The certificate is in the form of a license.dat file.
Figure 3.7 License Selection
Search: you can search for the location of the license.dat file in the Windows file directory.
An example of the location of the certificate is:
C:\Licenses\license.dat
Click the license.dat certificate file to automatically transfer the file location into the input field.
Copy the license to the installation folder: if the checkbox is checked off, the certificate will be copied
into the standard installation folder. If the checkbox is not checked off, the Offboard Diagnostic Infor-
mation System Service will be installed without a certificate file. The certificate must then be installed
separately before starting the system for the first time.
The standard installation folder for the license file is:
C:\Program Files\Offboard_Diagnostic_Information_System_Service\license\license.dat

The name of the Start menu folder can be selected after that. "Offboard Diagnostic Information
System Service" is used as the default. Or you can deselect the checkbox for creating a start menu
folder.
Figure 3.8 Start menu folder selection
If the Create shortcuts for all users checkbox is activated, a link on the desktop to Offboard Diag-
nostic Information System Service will be created for each user. If the checkbox is not selected, the
link on the desktop is only visible to the user who installed Offboard Diagnostic Information System
Service.
The following links are also created on the desktop for all users:
 ODIS Service Diagnostic Interface Configuration: opens the program for configuring the diag-
nostic interface.
Next: the Offboard Diagnostic Information System Service installation continues. The copying and
installation procedure starts.
A progress bar shows the progress of the copy and installation process.
Figure 3.9 Copying process display
Notice:
The installation process can last several minutes depending on computer speed.
The installation procedure for the PDU-API diagnostic component is shown separately.
This installation procedure cannot be influenced.
Once the installation procedure is complete for all components, the last view of the installation assistant
will open.
Figure 3.10 Completed installation
Finish: clicking on this button will end installation of Offboard Diagnostic Information System Ser-
vice.
You can now double click the link on the desktop to start Offboard Diagnostic Information System
Service. Offboard Diagnostic Information System Service can also be started through the start menu
Start > All Programs>-Offboard Diagnostic Information System Service.
The Offboard Diagnostic Information System Service installation ends the first time the application
is started. The Offboard Diagnostic Information System PostSetup opens.
Note:
If a special proxy server must be used to access the Internet due to legal requirements (for example in
Cuba), this can be entered in a certain file (in the installation directory: jre\lib\net.properties). The de-
scription of possible entries is also included in this file. A change should only occur in coordination with
support.
Figure 3.11 PostSetup start
The installation completion by the PostSetup functions as a software update. It can be performed via the
Internet using a preset URL on the importer mirror server. The correct URL, user name and password
are needed. If the installation data for the PostSetup local are available, for example on a DVD, then it
is possible to complete the installation without having to use the Internet.
URL: mirror server address (depending on the importer).
Select local directory: open Windows Explorer, which can used to select the directory with the Post-
Setup files.
User name: user name for accessing the mirror server
Password: password for accessing the mirror server.
Install the client certificate: the client certificate can be imported using this button. The Client Certif-
icate dialog opens.
Note:
The client certificate is required during the updates to communicate with the group system and mirror
server.
Cancel: the PostSetup is canceled.

The PostSetup continues.
Figure 3.12 Client certificate
Selection...: the client certificate can be selected with this button. The file selection dialog opens. If the
corresponding certificate is selected, it will be displayed in the read-only text field near the Selection...
button.
Password: the password for the selected certificate must be entered in this input field.
Importer: pressing this button imports the selected client certificate. The button is active when a client
certificate is selected and the password is entered.
Cancel: cancels the client certificate import. The dialog will be closed.
Client certificates are imported in the same way as through the application administration. If an error
occurs while importing, an error message from the chapter Client certificate may be displayed depend-
ing on the type of error. In the case of an error the dialog will close.
Reference:
Also refer to the chapter Client certificate in Administration Mode.
After selecting the update server and after successful authentication the user can select the installation
language. The progress in determining the languages from the specified mirror server is displayed in a
progress dialog.
Figure 3.13 Language selection
The installation language is shown in bold type (here German) and cannot be deselected by the user.
This is indicated with an additional note, The installation language cannot be deselected. A total of
five languages can be selected if the installation language is supported by the mirror server, otherwise
four can be selected.
It is possible to navigate backward in steps in the PostSetup using this knob.
The PostSetup continues.
Note: only the languages that were already installed by the mirror server are shown in the list of
available languages.
Figure 3.14 PostSetup data display
Before the files installation begins, the available updates, the maximum download size of the files
being installed, and the download time for an installation via the Internet depending on the type of
connection are displayed.
The technical versions for diagnostic data and for each licensed brand are also displayed. It is possible
that there is no technical version specified for a brand and the diagnostic data table is shown without
any version information.
Update selection: with the update selection the user can select the post setup version to be installed. If
the highest possible version is not used, a fallback situation will result.
Cross-reference:
Also refer to Installing a Fallback Version

Figure 3.15 PostSetup data installation
The diagnostic data and vehicle projects for the brands entered in the license certificate and the help
files will now be installed in the language that was selected at the beginning of the post setup. Each file
package and the progress of the installation is displayed in the progress dialog
Offboard Diagnostic Information System Service can now be used if the installation was completed
correctly.
Notice:
It is possible to cancel the installation of the language-dependent diagnostic data, vehicle projects and
help files the first time Offboard Diagnostic Information System Service is started. However, you
will not be able to work with the application.
If shared network drives will be set up for use by several Offboard Diagnostic Information System
Service testers, refer to the Microsoft Windows documentation on setting up shared network drives.
You can set up the folder structure according to your preferences. The Offboard Diagnostic Infor-
mation System Service local path structure after the automatic installation and the preset folder names
in the expanded Administration area are a good starting point.
Cross-reference:
Also refer to the chapter Administration Mode.
Notice:
If Internet Explorer version 9/11 is selected as the default browser, the following setting must be made
so that communication to the group systems can function correctly:
Figure 3.16 Internet Options for Internet Explorer 9
In the "Advanced" tab for browser Internet options, the check mark must be removed from the entry
"Show friendly HTTP error messages".
Notice:
An error message may appear if a firewall is active when installing Offboard Diagnostic Information
System Service. Access to OffboardDiagLauncher.exe must not be blocked.
Reference:
Also refer to the chapter Additional Error Messages.
Note:
The installation can also be done using a software sharing program. In this case, the installation may run
completely in the background with no dialog windows.
4 Update
There are regular software and data updates for Offboard Diagnostic Information System Service.
The update cycle, the settings for loading in the background and for the automatic updating of the access
data can be configured in Admin.
Cross-reference:
Refer also to the chapters General Area and Connections Area under Administration Mode.
In the Offboard Diagnostic Information System Service start configuration, the system searches for
updates daily. Testing can take place when the program is started, when the program is ended or when
ending a diagnostic session, depending on if a test has already taken place or not on the current date.
The progress of the update search may differ depending if it was executed at the start or end of the
application, at the ending of a diagnostic session or manually.
1. Update search at the start of an application or when ending a diagnostic session
The update search when starting Offboard Diagnostic Information System Service or when ending a
diagnostic session runs in the background. If running in the background is configured in the Admin area,
then any updates found are automatically downloaded in the background.
The result of the update search will be displayed by a symbol in the status bar. The following symbols
can be displayed and you can click on them:
: An update is downloading. It is possible to pause a download. A dialog opens if you click on the
symbol:
Figure 4.1 Pause download
Close: closes the dialog and continues downloading.
Pause: closes the dialog and pauses the download.
: This symbol appears if the download was interrupted. Click on this symbol to continue the down-
load.
Downloading continues automatically if a diagnostic session was ended even if was manually continues
before.
When downloading ends, another dialog informs the user that the update can now be installed:
Figure 4.2 Updates ready for installation
Yes: starts the update.
No: the update is not installed. The files to be downloaded are available for installation at a later time.
Yes, shut down afterward: the update loads and then the operating system shuts down. In this case, the
update process is performed automatically. The user does not have to do anything unless an error occurs.
: The time point for testing the updates is exceeded, or update were downloaded, which can now be
installed. Clicking on the symbol starts either the update check or the update process.
: When checking for updates, it was determined that reinstallation is required. If you click on the
symbol, the "Reinstallation required" dialog that is described below will open.
: When checking for updates, all of the required data was not available on the update server. If you
click on the symbol, the "Missing update files" dialog described below opens.
An instruction text with more detailed information appear when the mouse is moved over the symbol.
Clicking on the symbol starts the update check. This runs just like the check described below when
ending the application.
2. Update check when ending the application or manually
If check for updates is performed when ending Offboard Diagnostic Information System Service,
then the use see a message. This message closes automatically when the check is ended. The message
appears when the user manually starts the update by clicking on Update.
Figure 4.3 Checking for updates
A message appears if no updates were found.
Figure 4.4 No updates available
OK: closes the message window.
If a new version was found that cannot be installed through an update and that requires a reinstallation,
the following message will appear:
Figure 4.5 Reinstallation required
If updates were found, a dialog appears where the user has to possibility to install the updates now. If
load in background is not activated in the Admin area, the update is downloaded. If the option is acti-
vated, then the update is downloaded while performing Offboard Diagnostic Information System
Service as long as there are no diagnostic sessions active. This can accelerate the update process.
Figure 4.6 Available updates
Yes: downloads the update and starts the update process.
No: the update is not downloaded and/or installed.
Yes, shut down afterward: the update loads and then the operating system shuts down. In this case, the
update process is performed automatically. The user does not have to do anything unless an error occurs.
Notice:
Shutting down the operating system can be prevented in any case by other active third-party applications,
for example, by a mail program. Offboard Diagnostic Information System Service has no influence
over these applications. If such applications do prevent automatic downloading, it is recommended to
refer to their documentation.
If all required files are not available on the mirror server during the update check, an error message will
appear. The dialog contains the names of the missing files.
Figure 4.7 Missing update files
Cancel: closes the dialog without performing the update.
When the update process starts, a wizard guides the user through the process on several pages.
If there is already an update when starting the application, which was downloaded earlier, then the wiz-
ard will appear just before starting Offboard Diagnostic Information System Service.
Each page of the wizard has three screen buttons:
Next moves to the next page of the wizard.
Back takes you back one step.
Cancel: cancels installation of the update. Offboard Diagnostic Information System Service starts
then in the earlier version.
A warning appears on the first page of the wizard informing the user that existing diagnostic sessions
may become incompatible after performing the update. This message must be confirmed.
Figure 4.8 Warning before updating
The update source, from which it must be taken, must be entered first. If these entries were already done,
then this page of the wizard is no longer displayed.
Figure 4.9 Updating using the network
URL: the URL for the update server (Mirrorserver 2) can be changed in an update via the network. The
preset URL is taken from the Admin area and can be changed permanently there.
Select local directory: if the update is installed using a CD/DVD or a network drive, the drive with the
inserted update CD/DVD or the folder on the network drive can be selected using this button. User name
and password are not required for an offline update.
User name: user name entry.
Password: password entry.
Install the client certificate: the client certificate can be imported using this button. The Client Certif-
icate dialog opens.
Note:
The client certificate is required during the updates to communicate with the group system and mirror
server.
Figure 4.10 Client certificate
Selection...: the client certificate can be selected with this button. The file selection dialog opens. If the
corresponding certificate is selected, it will be displayed in the read-only text field near the Selection...
button.
Password: the password for the selected certificate must be entered in this input field.
Importer: pressing this button imports the selected client certificate. The button is active when a client
certificate is selected and the password is entered.
Cancel: cancels the client certificate import. The dialog will be closed.
Client certificates are imported in the same way as through the application administration. If an error
occurs while importing, an error message from the chapter Client certificate may be displayed depend-
ing on the type of error. In the case of an error the dialog will close.
Reference:
Also refer to the chapter Client certificate in Administration Mode.
The local administrator must be contacted for access to the update server.
An update can made online or offline.
In the case of an offline update, the system checks if the site.xml file is in the specified directory. If it
is not, an error message appears and checking for updates ends.
Figure 4.11 Error message when site.xml is missing
Notice:
An error message may appear if a firewall is active when installing updates. Access to the application
file OffboardDiagLauncher.exe must not be blocked.
Administrator rights are needed for the operating system on the tester or laptop in order to perform
an update.
Reference:
Also refer to the chapter Additional Error Messages.
A progress indicator shows the connection being established to the update site.
Figure 4.12 Establishing a connection to the update site
Cancel: the update is canceled.
Once the connection to the update site is established, the Offboard Diagnostic Information System
Update indicates the size of the available updates and the estimated time required for download depend-
ing on the type of Internet connection. If the memory requirements needed exceed what is actually
available, then a message appears informing the user.
Figure 4.13 Warning when there is insufficient disk space
The save location can be changed in this case, for example, to a different hard drive disc or partition.
Clicking on Directory opens a file selection dialog, in which the new save location can be selected. The
OK screen button is active if there is sufficient space in the new save location.
OK: continues the update process.
Cancel: switches back to the configuration data entry. From here, you can either cancel the update pro-
cess or restart it, for example, after cleaning the hard drive disc.
If there is sufficient disk space and an update was found, the size of the update and the estimated down-
load time are displayed. An update has a unique version number, which is the one in the main compo-
nents (in the illustration “4.32.10”). If a current application version is assigned to an update, it will be
indicated in parentheses, for example “4.32.10 (3.2)”.
The determined technical versions for diagnostic data and for each licensed brand are also displayed.
This version list can be incomplete or even empty if a brand does not have a defined technical version
or the selected update does not alter the diagnostic data.
Figure 4.14 Available updates display
If there are multiple updates available, they will be listed in the selection list in the upper right. The must
current update or the highest version number is always selected by default.
Reference:
For more information about installing an update other than the most current update version, refer to the
chapter Installing a Fallback Version.
If there is no update data available, Offboard Diagnostic Information System Service will show the
following message:
Figure 4.15 No updates available
If update data is available, there will be updates for the following areas:
1. Individual program sections of Offboard Diagnostic Information System Service, if they are
licensed.
2. Data that was edited by Offboard Diagnostic Information System Service, such as diagnostic
data, test programs and similar.
3. Programs offered by third parties such as MCD server.
The progress indicator shows the progress of the installation for all update components.
Figure 4.16 Update progress indicator
Cancel: cancels installation of the update.
If there are errors during the update process, they will be shown collectively in a dialog.
Figure 4.17 Error when performing the update
The individual error messages will be listed in detail in the dialog text field.
OK: closes the dialog.
Notice:
The data update may take a long time, depending on the amount of data.
With updates to third-party applications, individual installation routines may start. If this happens, fol-
low the instructions they provide.
Note:
The update can also be done using a software sharing program. In this case, the update may run com-
pletely in the background with no dialog windows.
4.1 Installing a Fallback Version

It is possible for a non-functional update to be installed. When this happens, an earlier version can be
installed.
The requirement for this is that there must be a current setup file or an installation DVD with Offboard
Diagnostic Information System Service available. The updates are done based on this base installation.
First, Offboard Diagnostic Information System Service must be completely installed to ensure that
the faulty update is removed.
Then the application can be re-installed.
Reference:
The Offboard Diagnostic Information System Application installation is described in the chapter
Installation.
The update takes place after the installation and PostSetup are complete. The versions available on the
mirror server are displayed to the user on the assistance page Results of Checking for Updates.
Figure 4.18 Multiple updates available
The desired version can now be selected here.
The rest of the update process runs as described in the chapter Update.
If a version other than then newest one was selected, this will be indicated in the application by adding
the word FALLBACK to the version number in the name of the application window.
Figure 4.19 Identifying a fallback version
This is also done in the diagnostic log - the word FALLBACK is included with the software version
name in the naming there.
If there is an update later, the word FALLBACK will be added to the title in the update window and an
additional info text will appear on the first page of the wizard.
Figure 4.20 Fallback information
After a successful update, the FALLBACK version identification is removed.
4.2 Restart during Updates

Sometimes the computer must be restarted when updating third party applications. If this is the case, the
following dialog will appear:
Figure 4.21 Dialog for restarting during updates
Restart now: automatically restarts the computer after waiting a moment.

Perform later: ends the application without restarting the application or computer.
If you would like to perform the restart manually later, you will not be able to use the application. The
following note will appear if you try to start it:
Figure 4.22 Error message if application is not restarted
Note:
Sometimes the computer must be restarted immediately and the update is not completed. After the com-
puter restarts, restart the application to finish the update if necessary.
4.3 Serious Errors during Updates

In rare cases, if the update of a third party application is not successful, malfunctions such as application
errors will occur, for example during diagnosis. These cannot be corrected without reinstalling the ap-
plication.
If such an error occurs, the following error message will appear:
Figure 4.23 Error message about uninstalling the application
If you try again to start the application without reinstalling it, the error message will appear again. You
will not be able to perform any more updates or diagnostics. This error message will disappear once you
uninstall the application.
4.4 Starting the Program
4.4.1 Checking the License
The license is checked for validity when the program starts. If the license is still valid for 14 days or
less, a dialog informs the user and offers the option to extend the license. There must be an applicable
URL for eShop so that a connection to eShop can be established.
Figure 4.24 Message stating the license will soon expire
Yes: starts renewing the license.
No: cancel the renewal.
Chooses the brand in the left list for which the license is being renewed.
If the user selects yes, a dialog appears to log into the group systems.
The dialog that is shown depends on the specification for the login process.
For login with GRP, see the chapter 6.2.4.2 “Authentication in Group Retail Portal (GRP)”.
Otherwise, the following dialog for entering the user name and password will be shown.
Figure 4.25 Logging into the group systems for extending a license
Accept: performs the registration.

Cancel: cancels the registration. In this case, the license cannot be renewed.
If the registration was successful, the system will now try to get the licenses from eShop.
If successful, the user sees another dialog:
Figure 4.26 Success message when the license has been extended
OK: closes the dialog and continues starting Offboard Diagnostic Information System Service.
In the case of an error, another dialog appears:
Figure 4.27 Error message when extending the license
OK: closes the dialog and continues starting Offboard Diagnostic Information System Service.
If the license could not be extended or if the process was interrupted, then the dialog for extending the
license appears each time Offboard Diagnostic Information System Service starts. The dialog also
always appears each time the application is started after the license has expired. The application stops if
license renewal fails.
Once the startup process is complete, the user interface is shown in the Diagnosis mode.
4.4.2 Warnings and Notes (Disclaimer)
A window with warnings and notes to observe also opens.
Figure 4.28 Window with warnings and notes (part 1)

Notice:
The OK button for closing the window with warnings and notes is only active once you have scrolled
or paged through the entire text.
Figure 4.29 Window with warnings and notes (part 2)
Ok: the window will close.
After closing the window, Offboard Diagnostic System Information Service is ready for work.
Cross-reference:
For more detailed information, refer to the chapter Troubleshooting.
4.4.3 Logs That Have Not Been Sent

If there are diagnostic logs from an earlier diagnostic session when you start the program that were not
sent (for example, the application was ended incorrectly), they will be sent now. A message to the group
system is necessary here.
Figure 4.30 Message regarding transmission of the diagnostic log
The global user ID and password for group systems access are required to log in.
Transfer: the login data is sent to the group systems. The diagnostic log that was automatically stored
is sent after a successful login.
Cancel: the login data is discarded and the attempt to send is canceled.
4.4.4 Specifying the diagnostic interface

If the VCI type VAS6154(A) was configured in the installation of the Off-Board Diagnostic Infor-
mation Service System, an additional VCI-specific configuration must be performed the first time the
user starts the application. The corresponding selection dialog is displayed. This selection must be
made even when only one instance of VAS6154(A) is connected.
Cross-reference:
Refer to the chapter Diagnostic Interface.
For all other VCI types, the specific VCI is selected automatically after installation if only one instance
of the type is available. If there are multiple types, a dialog for selecting a diagnostic interface will be
shown.
Cross-reference:
Refer to the chapter Diagnostic Interface.
Once a specific VCI instance is selected, the system will always try to use this instance. This is also the
case after a restart and happens regardless of whether the selection was made automatically or by the
user. Selecting another instance is described in chapter Diagnostic Interface.
If the VCI is a VAS6154(A), a Wi-Fi certificate check will occur after successfully connecting to the
VCI. The check takes place only once each time Off-Board Diagnostic Information System Service
is started and once per VAS6154(A) device.
If it is determined that the Wi-Fi certificate will expire within the specified time, a warning message
will be displayed as long as the expiration date is in the future.
Figure 4.31 Wi-Fi warning message and expiration date in the future
If the expiration date is in 0 days, the following warning message appears:
Figure 4.32 Wi-Fi warning message for expiration on the same day
If a negative amount of time remaining is calculated, this means that the Wi-Fi certificate is already
expired and the following warning message is displayed:
Figure 4.33 Wi-Fi warning message for an expired certificate

Note:
If it is determined when starting the Diagnostic Information System Service that the Wi-Fi certificate
for the VAS6154(A) will soon expire/has expired, this will be noted in the diagnostic log during GFF
and flash diagnostic entry as an entry in steps performed.
Cross-reference:
Additional information for the diagnostic entries is located in the chapters Diagnosis Operating Mode,
OBD Mode, and Flash Mode.
5 Application Start/User Interface

This chapter contains a brief introduction about the user interface and how to work with Offboard Di-
agnostic System Information Service. When individual functions are discussed, there are cross refer-
ences to additional chapters in this manual if detailed descriptions are available.
Offboard Diagnostic System Information Service is started through the Windows start menu after
installing:
Figure 5.1 Starting Offboard Diagnostic Information System Service

5.1 User interface
Figure 5.2 Offboard Diagnostic Information System Service user interface
The user interface is divided into several areas:
Info area
Working Area (Client Area)
Modes
Standard functions
Status area
The following sections will describe the tasks in the individual areas.
5.1.1 Info area

The Information area contains general information about the license, the order and the vehicle that is
currently connected.
Figure 5.3 The Info area
The left area shows the importer, dealer and order number.
The center area contains the vehicle ID and the engine code.
For independent market operators, the remaining runtime of the diagnostic flat rate is shown in the
center area after logging into the group systems.
The right area uses symbols to indicate if:
 There is a diagnostic connection to the vehicle
o There is a diagnostic connection
o There is no diagnostic connection
o No diagnostic connection is detected

 There is a network connection
o There is a network connection
o There is no network connection

 The ignition is on
o The ignition is switched on
o The ignition is switched off
o The ignition status was not detected

 There is a connection type, or if there is no connection at all
o Ethernet
o Bluetooth
o USB
o Indicates a Wi-Fi connection The connection quality is shown directly under
the vehicle symbol. If the VCI – Router and Diagnostic tester – Router are established
via Wi-Fi in the Wi-Fi infrastructure mode, the display will show the quality of which-
ever connection has poorer quality.
o No connection
 Button for displaying the VCI information dialog in which the connection section
between the diagnostic tester and VCI is shown in detail.
 The current battery voltage level in volts
o Values greater than or equal to 12V are shown in green
o Values less than 12V are shown in red
o If the voltage is not available or an error occurred when checking
A red frame around the right section indicates that there are connection problems with the VCI, for
example:
Figure 5.4 Display when there are connection problems with the VCI
In this case, check the connection. The information in the area is no longer current. A note dialog will
also be displayed for marking.
Figure 5.5 Note dialog when there are connection problems with the VCI
Reference:
See also the chapter Diagnostic Interface.
Notice:
When there is no network connection, there is no connection to the group systems. Functions that
depend on a connection to the group systems, such as flashing, are not available.
Notice:
The battery voltage is only displayed when a VCI that supports this is selected.
Reference:
See also the chapter Low battery warning message.
5.1.2 Working Area (Client Area)

The work area is the central part of the application. All relevant data that are available during diagnosis
and testing - such as wiring diagrams, test plans and measuring results - are displayed here. All data is
also entered here, such as entering measurements in tests, selecting test steps and identifying control
modules individually.
Outside of a diagnostic session, a start window that differs in the individual operating modes will be
displayed.
During a diagnostic session there is a tab bar with various tabs in the working area for each operating
mode. Individual tabs will be activated depending on the type and scope of the work session. Inactive
tabs have no content and are grayed out.
Tab bar for the Flashing mode:
Tab bar for the Diagnosis mode:
Tab bar for the Info mode:
Tab bar for the Admin mode:

Notice:
In the tab bar for the Info mode, the tabs Work orders and History are not available for independent
market operators.
5.1.3 Modes
In the Operating modes menu, you can click the desired button to switch to various operating modes.
Figure 5.6 Operating Modes menu
The following modes are available:
Diagnosis mode:
OBD mode:
Flashing mode:
Measurement: operating mode

Infomedia button:
Admin: operating mode
The following chapters describe the individual operating modes.
Notice:
You can only switch between the Diagnosis and Flashing operating modes if the current diagnosis or
flash session was already ended.
When you are in Diagnosis and Flashing operating modes, you can switch to the OBD operating mode
and vice versa, if no test program or diagnostic function (for example, Read all DTC memories) is
currently being performed.
If you have entered using the OBD operating mode, it is not possible to change the operating mode.
Reference:
See also chapter End Diagnosis and Diagnostic Session.
5.1.4 Standard functions

The Standard functions menu contains functions that can be accessed at any time in Offboard Diag-
The following standard functions are available:

Figure 5.7 Standard Functions menus
5.1.4.1 Log submenu
Using the Protocol submenu
Figure 5.8 Log submenu
 Logs from Guided Fault Finding and OBD can be saved and printed,
 Logs from Guided Fault Finding can be sent and copied,
 OBD logs can be generated, edited and displayed.
Cross-reference:
Also refer to the chapter Log.
Notice:
By clicking on the name bar, you can expand and hide
the menus on the right side.
5.1.4.2 Data submenu
Using the Data submenu, you can
Figure 5.9 Data submenu
 Print current views

 Pause diagnostic sessions and resume them later
 Download hotfixes
Cross-reference:
Also refer to the chapter Data.
5.1.4.3 Extras submenu
The Extras submenu contains:

Figure 5.10 Extras submenu
 The search function

 The possibility to change the diagnostic interface
 The road test mode
 The possibility to update the application
Cross-reference:
Also refer to the chapter Extras.
5.1.4.4 Help submenu
The Help submenu contains the following functions:
Figure 5.11 Help submenu
 Online help
 The feedback function for support inquiries
Cross-reference:
Also refer to the chapter Help.
5.1.4.5 Info submenu
The Info submenu contains:

Figure 5.12 Info submenu
 Information on new functions under the News section

 Information on software and data versions
 Descriptions of symbols used in the application
Cross-reference:
Also refer to the chapter Troubleshooting.
5.1.4.6 Trace submenu
The Trace submenu provides the following options:
Figure 5.13 Trace submenu
 Record, pause, and end the Bus trace
Cross-reference:
Also refer to the chapter Trace.
5.1.4.7 Legal Submenu
The Legal submenu provides the following options:

Figure 5.14 Legal Submenu
 Displays the privacy policy
The privacy policy can also be displayed using the link on the start screen.
5.1.5 Status area

The current process and its status are shown in the status area.
Figure 5.15 Status area - sample test plan calculation
For example, the progress when calculating the test plan can be tracked during diagnostic entry.
The buttons for adjusting the size of the work area and ending Offboard Diagnostic Information
System Service are located on the right near the status bar.
The Hide button hides the operating modes and standard functions area.
The Show button can be used to display this area again.
Clicking on the Full screen button hides the Information area and the operating modes and
standard functions area.
To show the Information area and the operating conditions and standard functions area
again, click the button.
This button ends the Offboard Diagnostic Information System Service program. After click-
ing this button, a prompt appears asking if you really want to end the program. Offboard Diagnostic
Information System Service will end after you confirm with Yes. If Guided Fault Finding was per-
formed, it must be ended first. Otherwise the system will ask if a support request should be send at the
end of the diagnostic session.
Cross-reference:
Also refer to the chapter End Diagnosis.
5.2 Operation
Offboard Diagnostic Information System Service can be operated using the mouse and keyboard as
well as the touchscreen. The buttons are displayed larger for easier operation on the tester and the
touchscreen.
5.2.1 Touchscreen
A touchscreen is a sensor screen that is present on some diagnostic devices. The user touches buttons
with the finger and/or a stylus instead of using a mouse and keyboard.
Note:
The right mouse button is not used with the touchscreen. Menus and buttons that are accessed with the
right mouse button are displayed by pressing and holding the desired button on the touchscreen for
approximately 1 second.
5.2.2 Mouse and Keyboard

The mouse can be used to operate the program. Place the cursor on the desired button and click the left
mouse button to confirm.
Menus and buttons in the context menu that are accessed using the right mouse button can also be
accessed by clicking and holding the left mouse button for approximately one second.
The keyboard is needed to enter values in test programs or Guided Functions when required by the test
steps. Manual VIN entry also requires a keyboard.
5.3 Screenshots for Support Requests

In many Offboard Diagnostic Information System Service dialogs, error messages and message win-
dows, there is a screen button with symbol of a camera on it at the bottom on the left side. This makes
it possible to make a screenshot of the current view.
If a support request is made after that, then the screenshot is added automatically to the request.
Example:
The screen button for making a screenshot is available in this message:
Figure 5.16 Making a screenshot
If you use the screen button, the application makes a screenshot of the actual surface of Offboard Di-
agnostic Information System Service.
Many screenshots can be generated if desired. When a support request is generated the next time, the
screenshots are contained there already in the free text window.
Figure 5.17 Support request with a screenshot
Cross-reference:
For more information regarding generating a support request, see Support.

5.4 Control Module Negative Response Display
Negative response codes from the control module are displayed in Offboard Diagnostic Information
System Service only if they cancel the started diagnostic function. A Note from the control module
with the coded control module response code opens in this case.
Figure 5.18 Note from the control module with Negative Response Code
The negative control module response (NRC = Negative Response Code) coded value displayed here
has a different meaning according to the control module log.
The meanings of the hexadecimal NRC for KWP 2000 and KWP 1281 are listed in the following
tables.
NRC (Hex value) Negative response name Meaning
generalReject
No closer specified rejection to the tester re-
10
quest
(also for OBD)
FunctionNotSupported / invalid- The desired function is not supported in the

11
Format specified parameters or not at all.
SubfunctionNotSupported / in-
validFormat The desired subfunction is not supported in
12
the specified parameters or not at all.
(also for OBD)
The previous request is still not processed, a

21 busyRepeatRequest
new request is rejected without being saved.
The conditions for performing the function

conditionsNotCorrect or re- are not met or requests, that must be processed
22
questSequenceError in a specific sequence, were sent an incorrect
sequence.
The service is being processed, the process is

still
23 routineNotComplete
not completed
One or more of the parameters are outside of

a permissible
31 requestOutOfRange
value range
Processing the service requires a SecurityAc-

securityAccessDenied / secu- cess,
33
rityAccessRequested
that was not processed or was incorrect
35 invalidKey Incorrect access authorization
The maximum number of incorrect access at-

tempts through
36 exceedNumberOfAttempts
SecurityAccess was exceeded
The wait time after a specific number of
incorrect attempts to gain access to the control

37 requiredTimeDelayNotExpired
module, is
not complete
40 downloadNotAccepted Download not accepted
41 improperDownloadType Incorrect download type
canNotDownloadToSpeci- Download not possible to the requested ad-

42
fiedAddress dress
canNotDownloadNumber-
43 Download does not have the correct length
OfBytesRequested
50 uploadNotAccepted Upload not accepted
51 improperUploadType Improper upload type
canNotUploadFromSpeci-
52 Cannot download from the specified address
fiedAddress
canNotUploadNumber-
53 Upload does not have the correct length
OfBytesRequested
71 transferSuspended Transfer suspended
72 transferAborted Transfer aborted
74 illegalAddressInBlockTransfer Illegal address in block transfer

illegalByteCountInBlockTrans-
75 Illegal byte count in block transfer
fer
76 illegalBlockTransferType Illegal block transfer type
blockTransferDataCheck-
77 Block transfer data check sum error
sumError
The service was received correctly and is be-

requestCorrectlyReceived-Re-
78 ing processed, however the response is pend-
sponsePending
ing. (also for OBD)
incorrectByteCountDuring-
79 Illegal byte count in block transfer
BlockTransfer
serviceNotSupportedInActive- Service not supported in active diagnostic

80
DiagnosticMode mode
The flash in the control module does not con-

tain a program and the control module is in the
boot sector. After restarting the
90 noProgramm
diagnostic data transfer, only update program-
ming is possible.
The tester uses the scaling as

91 scalingNotSupported
determined for KWP1281.
Table 5.1 Negative Response Code (NRC) from control module with KWP 2000
Block title/content Negative response name Meaning
0A block counter old No Ack -1 Error during data transfer

Block title/content Negative response name Meaning
Function is either unknown or cannot

0A block counter No Ack UB
be performed at the moment
Table 5.2 Negative Response Code from control module with KWP 1281
On control modules with UDS protocol, the negative response is constructed as
7F <service number> NRC
The NRC (Negative Response Code) is service-specific but often conforms to the meanings in KWP
2000. If needed, ISO Standard 14229 or VW Standard VW-80124 is recommended.
6 Diagnosis Operating Mode

This chapter covers the scope of functions in the Diagnosis mode.
6.1 Diagnosis Procedure

The following chapters describe the typical work procedure in a diagnostic session with Offboard Di-
agnostic Information System Service. A diagnostic session is characterized by the steps diagnostic
entry, test plan and special functions, working with Guided Fault Finding (GFF) and ending the
diagnosis.
Figure 6.1 Diagnostic entry process
In the diagnostic entry section, a connection to the vehicle is established, the login into the group
systems is completed, the vehicle is identified (GMD), a matching order is selected from ElsaPro, the
vehicle control modules are identified and, lastly, the GFF start is initiated.
In the test plan and special functions section, the start module and traversal tests are completed
and the test plan is calculated automatically and adapted manually using DISS if needed. The test plan
and special functions for Guided Fault Finding are available at the end of this section.
The completion of GFF tests is the focus of the working with GFF section.
In the end diagnosis section, the diagnostic session is completed with the clearing of the DTC
memory, the performing of end modules and the option for feedback.
In addition to this typical diagnostic session procedure, there are additional options in the Diagnosis
operating mode such as marking control modules as installed later, switching control module versions,
checking individual control modules using Guided Functions or performing a complete self-diagnosis.
6.2 Diagnostic Entry
In the diagnostic entry section, a connection to the vehicle is established, the vehicle is identified
(GMD), the login to the group systems is completed, a matching order is selected from ElsaPro the
vehicle control modules are identified and, lastly, the GFF start is initiated.
Figure 6.2 Diagnostic Entry
Note:
The illustrations that follow in this chapter were created without background graphics, so their appear-
ance will differ from your version.
Note:
When starting the application, you may be prompted to select the diagnostic device, which results from
the automatic VIN detection.
Note:
It is possible to run a diagnosis without a vehicle for the purpose of Guided Fault Finding (GFF) in this
mode. For additional information and a description, see Diagnosis without a Vehicle.
Note:
With special vehicle types, parts of the process shown here may differ slightly or may be omitted.
After starting the application without any diagnostic hardware or a vehicle connected, the input screen
will appear as follows:
Figure 6.3 Entry window after starting the application

VIN: the VIN that was read from the connected vehicle will be displayed in this field. If it cannot
be read, you may need to enter it manually (see 6.2.1).
Work with GFF: if this option is activated, Guided Fault Finding (GFF) (see 6.4) will be started.
If it is not activated, quick entry will be used (see 6.6).
Start diagnosis: this button will become active when there is a valid VIN (see 6.2.2).
Continue diagnosis: this button is active when a valid VIN is entered or read and there is session
data available for this VIN. The text will then change to “Continue diagnosis from ...”. If the session is
from the previous day or earlier, the date will be listed instead of the three dots. If it is from the same
day, the time will be shown instead. Only the last or newest diagnostic session will be offered.
Privacy policy: Clicking this link opens a dialog that displays the current privacy policy. The pri-
vacy policy can also be displayed using a button in the Standard functions in Legal Submenu.
6.2.1 Connecting a Vehicle

The Connecting a Vehicle section describes how to connect the vehicle to Offboard Diagnostic In-
formation System Service before starting the diagnosis.
Figure 6.4 Connecting the Vehicle section
When a vehicle is connected, the VIN will be read automatically and displayed in the input screen. If
this process takes too long, then the diagnostic interface may not be configured correctly.
Cross-reference:
To configure or change the diagnostic interface, see the chapter Diagnostic Interface.
6.2.1.1 Checking the Diagnostic Interface
If no concrete VCI instance was specified by the installation and multiple instances of the configured
type are available or there is at least one available VAS6154(A) with configured type VAS6154(A),
then the user will be prompted to make a specification when the application starts.
Figure 6.5 Note about specifying a unique diagnostic interface
Do not show this note again: If “Do not show this note again” is activated, the “No VCI specified”
dialog will not be displayed after restarting the application. The dialog will generally not be displayed
if a diagnostic interface was specified. Activating removes the option to specify the diagnostic interface
directly when starting the application, if it was not specified earlier.
Close: ends the dialog without specifying a diagnostic interface.
Specify VCI: the dialog will be closed and the “Specify VCI” dialog will be opened so that the user can
specify an instance.
Link: chapter Diagnostic Interface
The “Specify VCI” dialog shows all available diagnostic interfaces. There is no restriction on the VCI
type from the installation.
If the user selects a VAS6154 (A) that has the “In use” status, a message will appear, indicating that this
VAS6154 (A) cannot be selected.
6.2.1.2 VIN Display
If a VIN was automatically determined, it will be displayed and it will not be possible to change it:
Figure 6.6 VIN read automatically
If the VIN could not be read automatically, you will need to enter it manually in the VIN field. The
VIN that was entered will be checked for plausibility. For example it must be the correct length (17
characters). There is no additional functional test of the VIN. Make sure it is entered correctly, be-
cause it will not be possible to change it after diagnostic entry.
Figure 6.7 Entering the VIN manually
6.2.2 Starting Diagnosis

The Starting Diagnosis section describes that actual start of diagnosis and its requirements.
Figure 6.8 Start Diagnosis section
To activate the button for starting diagnosis, the following requirements must be met:
 You must be in Diagnosis mode.

 Diagnostic hardware must be detected.
 A vehicle must be connected.
 The vehicle VIN must have been read automatically or entered manually. If you are an inde-
pendent market operator, you can also manually change a dummy VIN
(“XXXXXXXXXXXXXXXXX”) that was read out from the vehicle later. This is necessary to
enable logging into the group system, which is required for independent market operators. A
correct VIN is needed, from which the brand can be determined.
 The VIN must be associated with a licensed brand.
 You must have logged into the group system because you would like to perform diagnosis based
on a work order or because you are an independent market operator.
Then the Offboard Diagnostic Information System Service user interface will appear as follows:
Figure 6.9 Diagnostic entry start window
Clicking on this button will start diagnostic entry.
First the diagnostic hardware is checked.

Notice:
Figure 6.10 Unpermitted Bluetooth connection
Yes: you will work with Bluetooth at your own responsibility.
No: a Bluetooth connection will not be established.
The use of Bluetooth connections is not permitted in all countries. If communication to the vehicle is
established via a Bluetooth connection in one of these countries, Offboard Diagnostic Information
System Service will display a message to inform you of this.
Cross-reference:
For a detailed description of changing diagnostic hardware, refer to the chapter Diagnostic Interface.
Diagnostic entry runs in the Control modules tab.
Once diagnostic entry has started, it can be stopped by clicking on this button.
A diagnosis that has already been performed can be ended using this button. This
does not close Offboard Diagnostic Information System Service.
At the start of diagnostic entry, Offboard Diagnostic Information System Service checks the vehicle
status in terms of battery and ignition status:
Is the battery connected (terminal 30 - battery voltage)?
Is the vehicle ignition switched on (terminal 15 - ignition)?
If the battery is not connected, the Battery not connected dialog appears.
Figure 6.11 Battery not connected
If the ignition is switched off, the message Ignition switched off appears.
Figure 6.12 Ignition is switched off
Repeat: the ignition is checked again.
Continue: the system continues the diagnostic entry.
Cancel: the diagnostic entry is canceled.
Notice:
For several vehicles, the pin that transmits the terminal 15 signal is not assigned on the OBD socket.
Offboard Diagnostic Information System Service cannot detect the ignition status for this vehicle. In
this case, the ignition is off dialog will not be displayed.
If the ignition status is not detected, the message Ignition status not detected appears.
Figure 6.13 Ignition status not recognized
Repeat: the ignition status is checked again.
Continue: the system continues the diagnostic entry.

Notice:
The status of the battery, ignition and vehicle recognition are checked during the following activities:
 Diagnostic Entry
 Reading a control module DTC
memory
 Reading DTC memory for all
control modules
 Manual control module identifi-
cation
 Diagnostic exit
Note:
Diagnostic entry may last several minutes.
Notice:
Offboard Diagnostic Information System Service cannot be ended while compiling the control mod-
ule list.
The current progress of the diagnostic entry is indicated at the lower right of the user interface.
Figure 6.14 Status area - example of determining a VIN
6.2.2.1 Diagnosis with Vehicle Data Stored Centrally
This section describes the changes in the process if there is a login into the group system and vehicle
data for this vehicle was stored centrally and can be retrieved successfully.
Note:
Centrally-stored vehicle data can only be used for certain brands.
If centrally-stored vehicle data is available, the vehicle features will also be determined for this vehicle.
In that case, the vehicle features dialog (see next chapter) will be skipped.
In addition, all control modules will no longer be read out, but rather only those that contain DTC entries
as part of the centrally-stored vehicle data or currently in the vehicle.
The control module information in the centrally-stored vehicle data forms the specified components.
The number of control modules in the control modules tab is visibly reduced. It is not possible to identify
or diagnose additional control modules, whether new or optional.
6.2.3 Vehicle Features Dialog (VFD)

The following section describes the identification of a vehicle based on its features. This section will be
skipped if the vehicle features have already been determined by the group system information.
Figure 6.15 Performing the Vehicle Features Dialog section
The central element is the dialog Vehicle Features Dialog (GMD).
Figure 6.16 Dialog for selecting vehicle equipment

If the ignition status is OK, the VIN was read from the vehicle, and the vehicle features cannot be
specified clearly, then the vehicle features dialog will be displayed in order to select the vehicle features.
The VIN can be corrected manually if necessary by switching vehicle identification from automatic to
manual.
Cancel: the vehicle identification and diagnostic entry are canceled.
The vehicle identification for determining GFF diagnostic data in the vehicle features dialog can be
performed automatically or manually. Vehicle features that were not identified clearly must be identi-
fied manually.
If an error occurs during automatic identification, a message appears with the request to identify the
vehicle manually.
Figure 6.17 Error during automatic identification
OK: identification mode switches to manual.
There are two basic reasons why the automatic identification fails:
 An error occurs when reading the VIN, for example due to a faulty control module.
 An error occurs when checking the diagnostic data associated with the VIN, the database is out-
of-date or incorrect.
In the event that the VIN could not be detected from the vehicle, the message VIN not found is also
displayed.
Figure 6.18 VIN not found
Repeat: an attempt is made to read the VIN.
Continue: the diagnostic entry continues. The message for the manual vehicle identification described
above appears.
If no error occurs during automatic identification, you can switch between automatic and manual mode.
When changing from automatic to manual mode, all of the previously determined vehicle features
remain, but they can be changed. If vehicle features are changed, all previously selected features become
invalid. When changing from manual to automatic mode, all of the vehicle features that were entered
manually and checked for validity remain. This means the validity of features entered manually will be
checked again automatically and modified if necessary. For example, an invalid VIN is replaced with
the VIN that was read automatically.
Figure 6.19 Entering the VIN manually
In manual mode, the VIN that was entered is checked for plausibility. For example it must be the correct
length (17 characters). There is no additional functional test of the VIN. The VIN that was entered
manually must be plausible in order to continue manual vehicle identification. Otherwise there are no
restrictions or dependencies when selecting from the vehicle features that are offered.
Notice:
If a plausible but technically incorrect VIN was entered, Offboard Diagnostic Information System
Service may prepare tests for GFF that do not lead anywhere due to the incorrect prerequisites. Manual
VIN entry should be used with caution.
In automatic mode, it is not possible to change the VIN and the identified vehicle features.
After determining the VIN, vehicle identification continues.
In the vehicle features dialog, there are several list fields that make it possible to select from several
suggestions, if available.
Select the vehicle manufacturer in the Manufacturer list field.
The models produced by the selected manufacturer are displayed in the Model list field.
After selecting the model, select the model year for the selected vehicle in the Model year list field.
When the model year is selected, the version type can be selected in the Versions list field (for example:
sedan, wagon, etc.).
Lastly, the vehicle engine is selected in the Engine list field.

Notice:
If the vehicle is switched during a diagnostic session, Offboard Diagnostic Information System Ser-
vice reads the VIN again and indicates that the vehicle has changed.
Each vehicle change is entered in the diagnostic log.
Note:
Each of the individual list fields are only active if a selection was made in the list field above.
Click Accept to accept the vehicle basic features. The vehicle is identified.
6.2.4 Logging in to Group Systems

The next step after the vehicle features dialog is logging in to the group systems.
Note:
Offboard Diagnostic Information System Service must have an online connection. If no login is pos-
sible, diagnostic entry will be canceled.
Figure 6.20 Logging in to Group Systems section
A GRP login is used to log into group systems (see 6.2.4.2). After successful authentication, it remains
until the connected vehicle is disconnected outside of the diagnostic session, or the authentication ex-
pires outside of a diagnostic session.
This button is available in all views of Offboard Diagnostic Information System Service that
use data from the group systems. It can be used to log in again at any time.
After logging in successfully, access to services such as ElsaPro, CarPort, DISS, etc. is possible in the
course of the diagnostic session.
You can use this button to log out of the GRP at any time. The button is located in the expanding
bar next to the button for ending the application.
Notice:
No diagnostic or flash sessions are possible without logging in. Entry will then be canceled.
After logging in successfully, Offboard Diagnostic Information System Service for independent mar-
ket operators shows the time remaining on the flat rate subscription in days and hours under Remaining
time in the Info area. Refer to Figure 5.3 The Info area.
The independent workshops do not have access work orders and History.
Notice:
Offboard Diagnostic Information System Service makes Diagnosis and Flashing available only to
licensed brands.
You can check the license content in the Administration area:
Cross-reference:
Refer also to the chapter License Information under Administration Mode.
6.2.4.1 Authentication with SecurID
The group system login for independent market operators is performed using the Internet. A SecurID
card and different authorizations are needed. The following describes registering using the SecurID
card.
The authentication is performed according to the principle two-factor authentication:
 Must know: user ID + PIN

 Must have: SecurID card
Figure 6.21 SecurID card
6.2.4.1.1 Requirements
The following prerequisites must be met in order to use the SecurID card for authentication:
 Network connection to the Internet (proxies with authentication are not supported)
 GeKo and, if needed, SVM authorization
 Volkswagen Internet WebService Access Authorization
When referring to authorizations the following must be differentiated:
 Volkswagen Internet WebService Access Authorization and

 Application Authorization (for example, GeKo)
Both authorizations must be requested for the same user ID!
Notice:
All authorizations are user-specific!
The SecurID card must not be given to others!
The owner of the independent market operator is responsible for the cards!
The following components are needed for the Volkswagen Internet WebService access authorization:
 Global user ID
 SecurID card
 PIN (password)
6.2.4.1.2 Initial Registration in the WS Gateway
It is necessary to create a PIN before the logging in for the first time or if the PIN was reset. This is
referred to as the new PIN mode.
Notice:
The user selects a 4 to 6 digit number for the PIN. The PIN must be kept confidential and may not be
shared with another person!
To create the PIN:

 Enter the following Internet address (URL) in your browser: https://ws-gateway.vw-
group.com/wsgwpin/app
 Enter the global user ID and the current displayed SecurID card number code (token) in the
fields (see illustration):
Figure 6.22 Create PIN
 Confirm with Log in.

 It is necessary to enter the new PIN in the Pin field in the following window. The PIN must
contain 4 to 6 numbers. The PIN is confidential and must not be given to another person!
Figure 6.23 Assign PIN
 Confirm with Set pin.

 Enter the assigned PIN in the Pin field.
 Wait until the next token on the SecurID card is displayed and then enter it in the Token field:
Figure 6.24 Check the PIN and confirm it with the token
 Confirm with Log in.

 "Log in successful" will be displayed if the setting the PIN was successful.
Figure 6.25 PIN created successfully
Note: it is possible to check if the registered user has GeKo authorization for this brand by selecting the
brand in the Brand field and then confirming using the Test Service button.
6.2.4.1.3 Additional Messages in the WS Gateway
The message Offboard Diagnostic Information System Service always checks the global user ID and
password. Do the following when entering the password:
 Enter the user ID in the global user ID field.

 First enter the password in the password field and then enter the displayed token (TTTTTT)
from the SecurID card.
Note: the small bar on the left side of the SecurID card display shows the validity of the displayed token.
The following is an example of a dialog for when entering the values:

 DP12345 = Global User-ID (GUID)
 pppppp = 4-6 digit PIN
 TTTTTT = 6-digit token
Note: only the place holder appears in the actual dialog field when entering the password.
Figure 6.26 Password input screen
Login: the login data is sent to the group systems.
6.2.4.2 Authentication in Group Retail Portal (GRP)
Some of the services used by Offboard Diagnostic Information System Service require logging into
the Group Retail Portal. In such cases, a dialog called GRP Login Dialog and an embedded browser
will be displayed. The login screen for the Group Retail Portal will be shown in the browser and it must
be used for the login.
Figure 6.27 Group Retail Portal input screen
6.2.5 Wi-Fi Connection Status

If the diagnosis was started with a Wi-Fi diagnostic interface, the system periodically checks during the
diagnostic entry if there is another suitable Wi-Fi connection available. If this is not the case, a warning
message is displayed. If two Wi-Fi signals are used in the W-Fi infrastructure mode, the one with the
poorer connection quality will be included in the calculation.
Figure 6.28 Warning message when the Wi-Fi connection quality is poor
Ok: closes the window.
6.2.6 Low battery warning message
Notice:
The display and monitoring of the battery voltage is only possible if a VCI that supports this was se-
lected. For example, the “VAS 6154” and “VAS 6154A” VCIs provide the necessary data.
If it is determined during a diagnostic session that the battery voltage has fallen below 12V for at least
60 seconds, a warning dialog will inform the user about this. This will close automatically if the voltage
increases above 12V or more again. But if the user closes the dialog first, it will appear again after 5
minutes if the battery voltage is still below 12V, if the battery voltage remains below 12V for at least 60
seconds. If the battery voltage increases to 12 V or more within 5 minutes, this timeout will be removed.
The dialog can be displayed again if the voltage drops below 12V for at least 60 seconds again.
Figure 6.29 Low battery warning message

6.2.7 Communication Selection when Setting up a Connection
(DoIP/CAN-FD/CAN/K-Line)
After successfully selecting the vehicle features, the MCD project that applies to the vehicle is deter-
mined. This determines if the communication to the vehicle will be done through DoIP, CAN-FD, or
CAN/K line.
If the vehicle supports a connection via DoIP or CAN-FD, the connected diagnostic interface will be
checked to see if it supports the corresponding communication path. If both paths are available, DoIP
communication will be given preference. If neither of these two communication paths are available, the
rest of the procedure will take place using the standard CAN/K-line communication path. If this is the
case and there is no vehicle information for CAN/K-line in the MCD project that is used, diagnostic
entry will end with the error message Figure 6.30.
Figure 6.30 Error dialog for invalid MCD project
The decision of whether to use DoIP, CAN-FD, CAN/K-line, or automatic communication can be made
in the Admin area. When a selection is made in the Administration area, the communication method that
was detected automatically will be overwritten. The setting will only apply to the next diagnosis and
then will be reset automatically. If there is no vehicle information about the specified communication
method in the MCD project that was detected, diagnostic entry will be canceled with the error message
from Figure 6.31.
Cross-reference:
Also refer to the Administration chapter GFF Process.
Figure 6.31 Error message when there is a conflict between the MCD project and the Administration setting
The VRT/VPT tables may contain a preferred communication path for the current vehicle. In this case,
this communication path will be given preference over all others depending on the administration set-
tings. If the MCD project or diagnostic interface used does not support this communication method, the
user will be given the option to select another communication method (see Figure 6.32)
Next: the connection to the vehicle will be established with the diagnostic interface that is currently
Figure 6.32 Request to change the communication method
connected using the communication method selected in the dialog.
Change VCI: opens the dialog for changing the diagnostic interface.
Cancel: does not select a communication method and closes the dialog.
Cross-reference:
Refer to chapter Diagnostic Interface.
If the DoIP communication method is selected and it is supported by the MCD project and the diagnostic
interface, a vehicle search will then run to establish vehicle communication via DoIP. If an error occurs
in the DoIP process from this point onward, other communication paths will not be checked and diag-
nostic entry will be canceled.
Figure 6.33 Vehicle connection through DoIP failed
OK: closes the dialog and cancels diagnostic entry.
If the exact DoIP diagnostic interface is not found during the local vehicle search on the diagnostic
interface, a corresponding dialog is displayed and diagnostic entry is opened.
Figure 6.34 Vehicle search unsuccessful

If the connection with a VAS6154 (A) is interrupted (when a vehicle is present and the connection type
WLAN-ACCESSPOINT or WLAN-INFRASTRUCTURE is used), the user is then informed that the
loss of connection can be corrected by reconfiguring the VCI using the keypad. The dialog will also
indicate if the previous connection was established via infrastructure mode or the point-to-point mode.
Figure 6.35 Loss of connection with VAS6154(A)
In the case of DoIP communication via a VAS6154(A), 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(A) are displayed.
6.2.8 Using the K Line Adapter

The K line adapter may be necessary with certain vehicles. If Offboard Diagnostic Information Sys-
tem Service detects such a vehicle, a dialog opens where the user is requested to connect the K line.
If the basic equipment dialog is displayed, the request to use the K line adapter will occur immediately
after closing the dialog. Otherwise, the request will come after the VIN is detected.
Figure 6.36 Using the K line adapter
The user must confirm the process using the checkbox. The OK button will only be active after doing
this.
OK: continues the diagnostic entrance.
Cancel: closes the dialog and cancels diagnostic entrance.
6.2.9 Customer Satisfaction Survey

If Guided Fault Finding (GFF) is to be used, the system will check if a customer satisfaction survey is
available and if you have any knowledge of it before you select the work order. In this case, an additional
dialog opens and it will remain open during the rest of the diagnosis.
Figure 6.37 Information dialog about the customer satisfaction survey
This dialog will close automatically when diagnosis ends, if it has not already closed. This is also infor-
mational, meaning the dialog will not appear during diagnostic entry in the future.
6.2.10 Selecting an Order

After logging in to the group systems, an order is selected for the diagnostic session. It is also possible
to work without an order. This is decided in this section.
Figure 6.38 Work order selection section - diagnostic entrance
The same procedure takes place when entering a flash session in the Flashing mode.
Figure 6.39 Work order selection section - Flash entrance
In the course of flash entrance, the selected work order is displayed in the Work orders tab after logging
into the group systems. The procedure for selecting the work order is the same in both modes.
Cross-reference:
The work order selection during flash entrance is also described in the chapter Order Selection under
Flash Mode.
The view changes to the Orders tab after logging in to the group systems.
Figure 6.40 Order view during diagnostic entry
Offboard Diagnostic Information System Service lists all available orders for the identified vehicle
in the Orders tab.
In the work order list, the work order number is displayed under Work order, the current status in the
service core process is displayed under SCP status, and the vehicle license plate number, the deadline
for the work order and descriptive text about the work order are also displayed.
The table that follows lists the meaning of the SCP status numbers.
SCP Status No. Meaning
1 Appointment scheduling
2 Appointment preparation
3 Vehicle drop-off
4 Services rendered
5 Quality control
6 Vehicle return
7 Finishing
8 Completed
Table 6.1 Meaning of the SCP status numbers
Offboard Diagnostic Information System Service checks if there is an online connection to the group
systems in order to load order and vehicle data from ElsaPro.
The web service configuration for access to ElsaPro is described here:
Cross-reference:
Refer also to the chapterGroup System: ElsaPro under Administration Mode.
Usually, the login to the group systems at the start of diagnostic entry is successful. If not or if the online
connection was interrupted after logging in, the following error message appears.
Figure 6.41 Login to group systems not possible
It is possible to log in again and correct the login data, if necessary.
Transfer: the login is performed again.
Cancel: the login is canceled. As result, no data from the group systems such as orders from ElsaPro
will be available.
Note:
You can reload order data from ElsaPro using the button. Authorized dealers can also log in to
the group systems again. This button is available in all views of Offboard Diagnostic Information
System Service that use data from the group systems.
Reference:
Refer to the chapter Info.
If there is a connection to the group systems, Offboard Diagnostic Information System Service lists
all of the orders available in ElsaPro.
Figure 6.42 Order list view
The desired order must be clicked to display order details.
Details: clicking on this button displays the order details.

Figure 6.43 Order detail view
In the Detailed order view, four sub-areas display order information such as Order type, Order date,
Order status and Pick-up date, customer information such as Name, Title, Address and Tele-
phone,order items with information such as Item number, Type and Text, as well as DISS concerns
with DISS concern ID, Customer comments, Customer code and TSBs from DISS.
DISS complaints can be updated using this button.
Reference:
For information on DISS concerns, refer to the chapter DISS / TPI.
Show order list: by clicking on this button, you can switch from the detailed view back to the order list.
You can select an order for the diagnostic session from this list or you can enter an order with a manual
order number.
You can select a marked order with order number from ElsaPro for the diagnostic session by clicking
on the Select order button.
If a work order was selected, which has no DISS complaints, then an applicable message appears.
Figure 6.44 No DISS concerns
OK: the message closes and the work order selection continues.
If there is no connection to the group systems, only a standard order for working with a manual
order number can be entered. It is possible to assign a number to this order and select it for the diag-
nostic session.
Figure 6.45 Entering the RO number
If a manual order number must be assigned, you must mark the standard order for working with
manual order number in the list by clicking with the left mouse button.
Own work order no.: clicking this button opens a window for entering the order number that can be
entered as free text consisting of letters and numbers.
Accept: the order number is used.
Cancel: an order number is not assigned.
Without order: diagnostic entry will continue without an order.
Figure 6.46 "Work without order" selection
You must click the Without order button.
Even orders that are called up from ElsaPro do not necessarily need a work order number. These orders
are shown with a light red mark in the Order column. To be able to use such an order, an order must be
entered first as described above in Standard order for working with a manual order number. The
order can then be selected.
Notice:
Only orders with order numbers can be selected for a diagnostic session. The selected order applies to
the entire diagnostic session. It cannot be changed.
An order is required to invoice warranty.
The order number is added to the diagnostic log.
This completes the order selection.
6.2.11 Control Module Identification

Control module identification begins after order selection. Offboard Diagnostic Information System
Service evaluates the Gateway components list first.
Figure 6.47 Identifying Control Modules section
It is necessary to set up communication to the Gateway control module. If this fails, the user receives a
dialog. This differs depending if the diagnostic object for communication malfunction is available
for the vehicle. If not, the following dialog appears:
Figure 6.48 Gateway control module malfunction in communication
Repeat: the system tries again to set up communication with the Gateway control module.
Continue: the diagnostic entry continues although there is no connection to the Gateway control mod-
ule. A list of devices cannot be determined.
If the diagnostic objects for communication malfunctions is available for the vehicle, then a different
dialog rather than the one described above is displayed, which offers the user the possibility to perform
a test program to correct the malfunction.
Figure 6.49 Communication malfunction Gateway control module with communication test
Perform communication test: the progress of the Guided Fault Finding is displayed. The diagnostic
objects for communication malfunctions is performed to correct the malfunction. The diagnostic entry
ends after the test program is performed and the start screen for diagnostics mode is displayed. From
here, a new diagnostic entry can take place.
Repeat: the system tries again to set up communication with the Gateway control module.
Continue: the diagnostic entry continues although there is no connection to the Gateway control mod-
ule. A list of devices cannot be determined. The diagnostic object for communication malfunctions is
included in the test plan and can be performed from there.
If the vehicle is marked in the equipment network for CAN diagnosis, the Gateway components list
with information on the communication protocol, the vehicle specified installation, the vehicle actual
installation and the current DTC memory status is read.
If a difference between the vehicle specified installation and actual installation is found based on the
status information from the Gateway components list, Offboard Diagnostic Information System Ser-
vice opens a Check components list window with the control modules listed in the order provided by
the Gateway. This components list can be sorted in the test window according to diagnostic address,
control module name, coding status and installation status.
Figure 6.50 "Check components list" dialog
Figure 6.39. "Check components list" dialog
The installation status is indicated with these symbols:
The specified installation that is displayed matches the actual installation.
The specified installation that is displayed matches the actual installation. The specified installa-
tion was changed and not coded yet.
The specified installation that is displayed does not match the actual installation.
The specified installation that is displayed does not match the actual installation. The specified
installation was changed and not coded yet.
Close: the window is closed.
The installation status can be edited through Coding status.

Figure 6.51 Editing the coding status
Only the coded or not coded setting can be edited.
To edit, highlight the control module with the mouse and right-click in the coding status to open the list
window for selection.
Coded means the control module is contained in the specified components.
Not coded means the control module is not contained in the specified components.
Perform coding: the changes to the coding settings are accepted and the components list is read again.
If there are still differences between the actual and specified components, the dialog appears again.
Close: ends the component list check and accepts the existing coding.
Note:
For the following automatic control module identification, a readout plan is created in the background
that includes all control modules that are addressed independently during identification by the system.
The readout plan consists of information about the MCD project, Gateway components list and control
module nodes in the equipment network. This reduces the list to the control modules that are most likely
to be installed in the vehicle.
Both the master control modules and any existing sub-systems are automatically identified.
If control modules marked in the equipment network as installed are not recognized in automatic iden-
tification, it is possible to have them read out again. The Unrecognized control modules (definitely
installed) dialog opens.
Figure 6.52 "Unrecognized control modules" dialog
Figure 6.41. "Unrecognized control modules" dialog
All unrecognized control modules are displayed in the left field of the dialog. Marking one or more
control modules and clicking the arrow button > will move them to the right window to be identified
again.
Control modules can also be moved to the left window using < if you do not wish to repeat the identifi-
cation.
Repeat readout: clicking this button begins another attempt to read these control modules. If the control
modules are still not recognized, the dialog opens again. The list of control modules then contains only
the ones that were selected before.
Close: this button closes the dialog and ends the repeated identification.
Variant Identification with UDS Control Modules
During variant identification of UDS control modules, it is possible that no matching diagnostic data is
available for the variants that were found. This may occur if the diagnostic data is not up-to-date. Off-
board Diagnostic Information System Service offers the possibility to check the connection to the
group systems. However, if diagnosis is limited to a base variant, the user will be informed with a mes-
sage.
Figure 6.53 "Working with base variant" dialog
Continue: diagnostic entry continues with the base variant.
Cancel: closes the dialog and cancels diagnostic entrance.
If the user decides to diagnose with a base variant, an entry will be generated in the error message area
of the diagnostic log. If the user continues with multiple base variants, an entry will be generated for
each. The entries will all be logged under fault number ODS6910E.
6.2.11.1 Control Module List
The control modules can be viewed in the control module list or in the networking diagram. The desired
view is opened using the corresponding button.
Figure 6.54 Control module list view
The Control module list shows the control modules that are part of the maximum installation. The
control modules installed in the vehicle are shown in black. The unidentified control modules are shown
in gray. Control modules marked as "installed" afterward are shown in black italics. Control modules
with DTC entries or control modules whose DTC entries cannot be determined are shown in red.
The Control modules table has three columns.
Address column
The Address column shows the diagnostic address for each control module.
DTC column
The DTC column shows the number of DTCs for each control module. A question mark is shown in the
column if the number cannot be determined.
Name column
The Name column shows the name of each control module.

Figure 6.55 Control module information
There is additional information about the control module in parentheses after the control module name.
The name of the version is only displayed when the version is set.
System name
Variant
Software part number
Software version number
System name
There are several options for sorting the columns.
The Sorting button opens additional buttons for sorting the table contents.
Figure 6.56 Sorting the control module list
Ascending address: click this button to sort the control modules according to the value of the diagnostic
address from low to high.
Ascending DTC: this button sorts the control modules according to the number of DTCs.
Ascending name: this button lists all control modules in alphabetical order.
There are three sorting possibilities for address, DTC and name:
1. Ascending (address number, number of DTCs, control module name)

2. Descending (address number, number of DTCs, control module name)
3. Unsorted (address number, number of DTCs, control module name)
The sorting can be changed in this sequence. The names of the buttons will change accordingly.
Note:
Clicking the Change sorting button displays the Descending DTC button. Clicking the Descending DTC
button displays control modules with the most DTC entries at the beginning of the table. This is helpful
for a quick overview of the control modules with DTCs.
An additional option for sorting the table contents is clicking on the column header in the table. Click-
ing the Address column header once sorts the diagnostic addresses in ascending order. Clicking the
header again will sort the numbers in descending order. Clicking the column header a third time shows
the diagnostic addresses unsorted in the order in which they were originally read. The sorting process is
the same for the DTC and Name columns.
This button switches the view between actual installation and maximum instal-
lation.
Actual installation: clicking this button displays only the control modules that are ac-
tually installed.
Maximum installation: clicking this button displays all of the possible control
modules for that vehicle model.
Note:
No control modules without protocols and no control modules that are inherited from a functional group
are displayed.
Note:
With special control module types, the display of the names shown may differ from the name shown
here. With these control modules, the diagnostic or transport protocol will be shown instead of the soft-
ware part number, software version number, and system name.
6.2.11.2 Networking Diagram
Once the control module reading begins, the vehicle networking diagram can be displayed on the Con-
trol modules tab.
Figure 6.57 Networking diagram view
Clicking on the Networking diagram tab on the Control modules tab opens an illustrated
overview of the current networking diagram in the overall view.
The Networking diagram shows the networking between control modules in the maximum installation.
Clicking on an illustrated control module displays a note under the Networking diagram that indicates
the control module system name.
There are several navigation buttons under the Networking diagram.
In order from left to right:
Change to networking diagram overall view
After zooming in, this button returns to the networking diagram overview.
Zooming in on the networking diagram

Each click on the button zooms in on the Networking diagram and shows more detail. If the
button is not active, the view of the networking diagram has zoomed in as much as possible.
Zooming out in the networking diagram
Each click on the button zooms out of the Networking diagram. This button is not active when
the networking diagram is in the overall view.
Scrolling in the networking diagram
Clicking the button moves the Networking diagram.
After activating the button, click any location on the Networking diagram and drag it in the desired
direction with your finger, if using the touchscreen. When using the mouse, press and hold the left mouse
button while dragging it in to the desired location on the Networking diagram.
This button is not active when the networking diagram is in the overall view.
Note:
Double-clicking on the touchscreen or the left mouse button is only possible when the symbol is
not activated.
The illustration of the Control modules can be used to determine the condition of each individual Con-
trol module.
The control module was not identified and is part of the maximum installation.
The control module was found and identified and does not contain any DTC entries.
DTC entries were found for the control module or could not be determined due to errors.
The control module was not identified but was manually entered as "installed".
Clicking and holding for approximately 1 second or right-clicking on a control module in the network-
ing diagram or control module list opens another button bar. The buttons available there depend on
the selected control module.
Figure 6.58 Buttons for individual control modules
The following buttons are available above the context menu:

Figure 6.59 Context menu (control module buttons)
When you click on the Measurement button, Offboard Diagnostic Information System Service
changes to the Measurement mode.
Cross-reference:
Also refer to the chapter Fehler! Verweisquelle konnte nicht gefunden werden..
Clicking on the Identify control modules button will perform a preferred control module or later
control module identification, depending on when the button is clicked:
 The preferred identification is performed during automatic control module identification.

It changes the sequence of automatic control module identification.
 The later identification is performed after control module identification is complete. An
unknown and unidentified control module is manually entered as installed afterward. If the
entry is made by confirming the message from Offboard Diagnostic Information System Ser-
vice, the control module is entered as manually installed.
Figure 6.60 Entering a Control Module as Installed
Yes: the control module is marked entered as entered manually and shown in the networking diagram
and the control module list.
No: the control module is marked not entered as installed.
If a control module was manually entered as installed later because it could not be identified automat-
ically, it will display in the control module list and the networking plan in italic font.
Figure 6.61 Italic display of control modules manually entered as installed
After identifying the control module, the system checks if there are several versions available. If not,
the base version is automatically used. If several versions were found, the dialog Select version is dis-
played. This dialog can also be opened using the Select version button and responds as described in the
following.
With the Select version button, you can select a version of the control module if more than one
version exists. The possible control module versions are displayed.
The versions may change at any time.
Figure 6.62 "Select version" dialog
Select: after selecting the control module version and clicking this button to confirm, the control module
list, the DTC memory and the test plan are updated automatically.
Close: clicking this button closes the form without selecting a version.
The version selection is only available for control modules that have already been identified or entered
manually.
Cross-reference:
Also refer to the chapter Start Modules, Traversal Test, Test Plan Calculation.
If you click the Read DTC memory again button, only the DTC memory entries for the selected
control module are read again. The test plan updates automatically.
To read the DTC memory again for all identified control modules, click the Read all DTC memo-
ries button. This also updates the test plan.
After identifying a control module, the Guided Functions button can open a selection that contains
all function tests for this control module such as output diagnostic test mode for the crash signal. When
a function test is selected and the Perform button is clicked, the program is performed on the Operation
tab.
Figure 6.63 Selecting control module guided functions
Perform: clicking this button performs the marked Guided Function in the Operation tab.
Cancel: the Guided Functions window closes.
The OBD button and Vehicle OBD button are described in detail in the "OBD" chapter of this
manual.
Cross-reference:
Also refer to the chapter OBD Mode.
Notice:
Under certain circumstances, it is possible that the Control module OBD and Vehicle OBD functions
may not be included in the context menu for the Diagnosis operating mode. OBD can only be done
using the OBD operating mode.
6.2.11.3 DTC Memory
The available DTC memory for each control module can be viewed in the DTC memory view. This list
only contains control modules that have a DTC memory entry.
Figure 6.64 DTC memory entries view
Clicking on the DTC memory list tab on the Control modules tab lists the control modules
with DTC memory entries.
The entries are closed first, the list indicates the control modules.
Figure 6.65 Opening a DTC memory entry
Double-click to open or close a DTC memory entry. If it is marked with a plus sign (+) or a negative
sign (-), it can also be opened or closed by clicking on the plus or minus sign.
The following picture illustrates the details about the control module.
Figure 6.66 Information about a DTC memory entry
The following information is available in the DTC memory entry as indicated by the numbers:
Event code
Symptom code
Event location
Symptom
Memory status
The view can be switched between the two views using the Display button:
the standard ambient conditions are shown
the standard ambient conditions are not shown
The standard ambient conditions provides information about:
 Status
 Date and time of the entry
 Mileage
 Priority
 Frequency counter
 Time Indication Bit
 Elimination counter/driving cycle
The sequence in an entry can be changed by clicking the Sorting button within
the DTC memory entry. The active sorting sequence is grayed out in the menu.
Figure 6.67 Sorting DTC list
Mileage: clicking this button sorts the content in ascending order according to mileage.
Priority: this button displays the content according to its importance.
Frequency counter: clicking this button sorts the content according to the frequency counter (how often
the event was detected).
Status: this button displays the content according to its status.
Sporadic/static: this button lists the faults entered as sporadic at the top of the list.
Cross-reference:
Also refer to the chapter Control Module List.
Clicking and holding approximately one second or right-clicking on a control module opens the control
module button bar as in the control module context menu.
Figure 6.68 Context menu in the DTC memory view
The context menu buttons are described in more detail in the Networking diagram chapter.
Cross-reference:
Also refer to the chapter
Note:
Networking Diagram.
6.2.11.4 Equipment List
The equipment lists shows the characteristics of the equipment specified for the vehicle. These are de-
termined based on the equipment network, which is specified after confirming the basic characteristic
dialog.
Figure 6.69 Equipment list view
Clicking on the Equipment list tab on the Control modules tab lists equipment and indicates
if it is installed or not.
Equipment characteristics can be displayed as follows:
Not installed and only one version available (gray text)

Installed
Not installed and multiple versions available (gray text and individual versions are separated with
|)
When starting diagnostic entry, all equipment characteristics are shown as not installed.
To mark an equipment characteristic as installed and to select a version, if applicable, click the Select
version button in the context menu for the equipment characteristic.
Figure 6.70 Equipment list context menu
A window opens where the desired version and installation status can be selected.
Figure 6.71 Select version
The top entry in the list is always not installed. If it is selected, the installation status of the equipment
characteristic changes to not installed.
Selecting a version changes the installation status to installed.
If the dialog is opened when a version is already selected, this version will be marked with a * in front
of it.
Select: accepts the selected version and sets the installation status to installed, or not installed if this
list entry had already been selected. The button is only active once a selection is made.
Close: closes the dialog and discards the selection.
The test plan is updated automatically each time the installation status or an equipment characteristics
for an installed version is changed.
6.2.11.5 Components List
In Diagnosis operating mode, the Components list tab on the Control modules tab is inactive.
Only when switching to the OBD operating mode does the tab become active.
Figure 6.72 Inactive tab „Components list“
Cross-reference:
Refer also to the chapter Components List under OBD Mode.
Note:
here. With these control modules, the diagnostic or transport protocol will be shown instead of the avail-
able identification data.
6.2.12 Starting Guided Fault Finding (GFF)

Guided Fault Finding can be started once control module identification is complete.
Figure 6.73 Starting GFF section
Offboard Diagnostic Information System Service opens the Diagnostic entry confirmation window
with the note that Guided Fault Finding (GFF) should be started.
Figure 6.74 Starting Guided Fault Finding
OK: confirming with this button starts Guided Fault Finding.
The next chapter describes the procedures that Offboard Diagnostic Information System Service per-
forms during Guided Fault Finding in more detail.
Cross-reference:
Also refer to the chapter Working with GFF.
Notice:
If control modules currently installed in the vehicle were not identified, it is possible to enter them in
the networking diagram or in the control module list as installed, select a version, if necessary, and
then add as a diagnostic object in component selection.
Reference:
Also refer to the chapter
Note:
Networking Diagram.
Reference:
Also refer to the chapter Component Selection.
6.3 Test Plan and Special Functions

In the test plan and special functions section, the start module and traversal tests are completed and
the test plan is calculated automatically and adapted manually using DISS if needed. The test plan and
special functions for Guided Fault Finding are available at the end of this section.
Figure 6.75 Test plan and special functions section
6.3.1 Start Modules, Traversal Test, Test Plan Calculation

This section describes how Offboard Diagnostic Information System Service performs the start mod-
ule and traversal test and then calculates the test plan.
Figure 6.76 Start module, traversal test, test plan calculation section
When Guided Fault Finding starts, start module and traversal tests are performed on the Operation tab.
These tests run in the background.
In a traversal test, the control module versions are set based on the control module information that was
read out. If a version cannot be identified automatically, or a vehicle-specific attribute should be entered,
a message with a selection will appear. If there are several versions of individual control modules within
the traversal test, a dialog opens to select a version.
Figure 6.77 Version selection view
To select a control module version, click next to the respective control module in the Version field. A
button appears that is used to open the menu in order to select the version.
Set version: the selected control module versions are accepted.
After setting the control module versions, the preparation of the test plan begins.
The automatic preparation of the test plan and the sequence of the test programs depend on the DTC
entries that were read from the control modules, from Technical Service Bulletins (TSBs) and from
customer comments during vehicle drop-off, which are available in coded form. These coded customer
comments are comprised of fault objects (such as components), fault types (for example, "it rattles")
and conditions (for example, temperature).
The test programs in the test plan are sorted according to their chances of success in Guided Fault
Finding, from greatest to lowest.
There are several methods for creating a test plan and updating it. For additional information on creating
a test plan, refer to the following chapters:
Creating a test plan during diagnostic entrance.

Cross-reference:
Refer to the chapter Diagnostic Entry.
Creating a test plan by selecting the version
Cross-reference:
Refer to the chapter
Note:
Networking Diagram.
Updating the test plan by reading the DTC memory again.
Cross-reference:
Refer to the chapter DTC Memory.
Updating a test plan using DISS.
Cross-reference:
Refer to the chapter DISS / TPI.
After completing diagnostic entry and performing the start modules, either the Test plan or DISS view
will be shown, depending on the selected ElsaPro order. The criteria are:
Type of repair order Displayed tab
No order Test plan
ElsaPro order without customer code Test plan
ElsaPro order with customer code but without DISS

TSB
6.3.2 DISS / TPI
This section describes how the creation of the test plan can be affected by creating and including con-
cerns.
Figure 6.78 DISS / TSB section
Figure 6.79 View inside the DISS tab after the diagnostic entrance
All of the DISS concerns from ElsaPro for the selected order are listed. Manual concerns can also be
created using the coding assistant. The Guided Fault Finding test plan can be affected by these concerns.
Figure 6.80 Table with DISS concerns
The table listing of DISS complaints contains four columns whose width can be changed by clicking
and dragging.
1. DISS Concern ID: the identification number for a concern.

2. Customer comment: that is the concern in the words of the customer as recorded at the time
the order was created.
3. Customer code: that is the text coding of the customer comment.
4. TSB from DISS: the number of the TSB to which the concern is assigned by the DISS system.
There are two possible categories for DISS concerns:
1. Concerns from the DISS system: this concerns provides all of the DISS information from the
order that is currently being used from ElsaPro and is called up automatically in the background
at the start of the diagnostic selection when the order is selected. An online connection with
login to the group systems is required for the list of concerns from DISS.
2. Manual concerns: these concerns are entered manually and shown in the customer code col-
umn. The DISS concern ID is always "manual". The two right columns have no information.
These concerns are also available offline with no login to the group system.
The coding assistant produces a manual concern. Clicking on the Coding... button next to a marked
empty concern line opens the Coding assistant dialog.
Figure 6.81 Coding assistant dialog window
Offboard Diagnostic Information System Service adds a new row for a manual concern each time a
manual code is added to the concern table.
Cross-reference:
The procedure for using the coding assistant is described in more detail in the chapter Coding assistant.
Functions for displaying TSBs:
The lower section of the concerns lists contains the function buttons that can be used to select a marked
concern in the customer code overview, to add items to the test plan, or to access suitable TSB lists from
the DISS system.
Clicking this button updates DISS concerns. If there is a more current DISS concern for an
existing concern ID, the existing concern will be replaced. If the existing concern is already used in the
diagnosis (meaning it was added to the test plan), then the updated concern will be shown in addition to
the existing one. The existing concern will be marked as out-of-date with a gray background and cannot
be used for any more actions.
Figure 6.82 Example of out-of-date DISS concern
The remaining function buttons are only activated for DISS concerns that are present and not marked as
out-of-date.
Figure 6.83 Function buttons in the DISS tab
Coding...: all customer coding details are displayed in the table in the customer coding overview win-
dow of the highlighted concern.
If this button is used with a selected empty line, the window opens with coding assistant.
Supplement test plan: the Transfer diagnostic objects to test plan window opens, in which associated
diagnostic objects are displayed with available codes. These diagnostic objects can be added to the test
plan. Not all of the concerns have associated diagnostic objects. If that is the case, the test plan cannot
be supplemented. A detailed description of this function is provided later in this section.
Supplement test plan:
If the Supplement test plan button for a highlighted concern was pressed in the DISS tab, the Transfer
diagnostic objects to test plan dialog opens.
Figure 6.84 Transfer diagnostic object to test plan
This dialog lists all of the complete customer codes that belong to the current order, including those
added manually. The upper half of the dialog lists the customer codes and their TSBs from DISS. If
available, the lower half lists the diagnostic objects associated with the selected TSB.
If a TSB does not have any connections to diagnostic objects, the TSB will be marked with an *. This
TSB cannot be selected.
The customer code/TSB that was opened using the Supplement test plan function is selected automat-
ically. The diagnostic objects for this selected customer code/TSB are also determined automatically.
The diagnostic objects can be selected or deselected individually or all at once by clicking the checkbox
in the left column.
Select all: all diagnostic objects are selected.
Deselect all: all diagnostic objects are deselected.
Transfer to test plan: clicking this button transfers the diagnostic objects for the selected customer
codes/TSBs to the test plan calculation. Customer codes/TSBs and their diagnostic objects that were
already transferred to the test plan are grayed out in the list view. They cannot be transferred to the test
plan again.
Close: no diagnostic objects are transferred. The dialog window is closed.
Diagnostic objects are only displayed for the marked customer codes/TSBs.
Figure 6.85 Deselected customer code
In the illustration above, no customer code is selected, which is why no diagnostic objects are displayed
in the lower list.
Close: the dialog window is closed.
Notice:
Test programs that were transferred to the test plan as a result of reevaluating the added diagnostic
objects can only be removed again in the Test plan tab.
Reference:
The Complete view can be accessed for the marked customer codes using the context menu for the right
mouse button.
Figure 6.86 Selecting the complete view
This function is the same as the Complete customer code function described above.
Close: the dialog window is closed.

Figure 6.87 Complete view of a customer code
In the Customer code complete view, all coding levels from the coding assistant are displayed with
available entries.
Close: the complete view is closed.
Test plan creation can be completed after editing the DISS concerns.
6.3.2.1 Coding assistant
The coding assistant is used as follow:

Figure 6.88 Coding assistant
The customer code fields can be filled in using the coding assistant. To simplify the process, the coding
assistant indicates the required coding fields step-by-step in the correct order with a green border.
The coding levels to be filled in are located on the left as buttons, namely groups and subgroups of
Components/Functions, Types of Complaints as well as Constraints and General Constraints..
Fields are located next to the buttons, in which the selected coded values are displayed. Once an entry
is made in a coding field, all of the buttons for the secondary fields that can now be filled are activated.
In the right window, suitable values are displayed for the green-bordered buttons. These values can be
selected by clicking. The active button is shown as a heading. The Constraints button is shown at the
top of illustration.
Constraints and General constraints are marked and can be added or removed by clicking on the arrow
buttons << or >>.
Depending on the hints provided by the coding assistant, it is also possible to click on an activated button
on the left side, which is then shown with a green border and can be filled. After filling the field, the
coding assistant continues providing assistance as described above.
Notice:
Fields marked with a * at the right are required fields that must be filled out in order to expand the test
plan with manual customer codes.
The General constraints field contains constraints that are not directly allocated to the customer code.
When it is filled, the result is that no diagnostic objects can be found for the current customer code.
6.3.3 Special Functions

In addition to the Guided Fault Finding test plan, there are additional test programs with the same name
in the Special functions tab.
Special functions are vehicle-specific test programs. They are not selected within diagnostic entrance
through vehicle basic features or control modules. They are made available from the database for indi-
vidual vehicles.
Clicking the special functions tab in Diagnosis mode displays the tests that are available for the whole
vehicle.
Notice:
In Flashing mode, the available flash programs for the vehicle are listed in the Special functions tab
after the vehicle and control module identification. There is no test plan in this mode.
Reference:
Also refer to the chapter Working with Flash Programs.
Special functions in Diagnosis mode include coding the immobilizer and transport protection, for ex-
ample.
Figure 6.89 Special Functions view
There are two columns in this view. The Tests column contains all of the test programs available for the
vehicle. The Status column indicates the status of the test program.
The test programs are grouped by theme.
Cross-reference:
Perform test: the highlighted test program is performed. Offboard Diagnostic Information System
Service switches to the Operation tab.
Show documents: the documents allocated to the vehicle are displayed. Offboard Diagnostic Infor-
mation System Service switches to the Information mode.
6.4 Working with GFF

The completion of GFF tests is the focus of the Working with GFF section.
Figure 6.90 Working with GFF section
After creating the test plan, you can switch to the list of test programs by clicking on the Test plan tab.
The test plan can be displayed in two different versions, depending on the vehicle that is connected.
Figure 6.91 View of test plan version 1
In version 1, there is a tab with available tests on the Test plan tab. This table has two columns.
Status: this column indicates the status of the test by means of a symbol.
This symbol indicates that the test has not been performed yet.
When there are functions, this symbol indicates that the function was performed successfully. During
fault finding, this symbol indicates that a malfunction was found in the component/system that was
checked.
This symbol indicates that the user canceled a test.
This symbol indicates that the diagnostic system canceled a test.
When there are functions, this symbol indicates that the function was not performed successfully.
During fault finding, this symbol indicates that a malfunction was found in the component/system that
was checked, or that a detailed test must still be performed.
This symbol indicates that the program was not completed. An error occurred when running the
program, or the user canceled the program.
This symbol indicates that the test should be performed again.
This symbol indicates that the diagnosis was completed and the component was repaired.
Tests: this column contains the possible test programs sorted according to their chance of success. The
+ symbol in front of a test will expand it. If available, the DTC memory entries will be listed below in
the order in which their tests were added to the test plan. The first line shows the control module with
the diagnostic address from which the DTC memory entry was read. The DTC memory entry is in the
second line.
This symbol indicates that the test program was automatically added to the test plan due to “unauthor-
ized DTC memory entries”. Unauthorized means that the control module contains a DTC memory entry
even though there is no error in the vehicle. This test program does not need to be executed in order to
complete the test plan.
Figure 6.92 View of test plan version 2 - cause-specific diagnosis
In version 2, the Test plan tab shows a table for cause-specific diagnosis. All vehicle faults that were
detected will appear in the table. As a sub-element to the concerns, the table shows the tests that can be
run that deal with a cause for the fault. This table has three to four columns.
Fault cause: this column contains the faults in the vehicle to be diagnosed. By expanding the fault, the
test programs that are used to analyze and correct the fault will be displayed. Selecting a fault will
expand it. In this case, the rest of the elements will remain collapsed. In addition, an entry for fault
information will also be displayed that contains the control modules involved with the fault. In turn, the
control module entries contain the DTC entries and information about them.
Repair location: this column will only be displayed if no vehicle is connected. This column indicates
where the test program can be performed. The following values can be displayed:
1. Remote: the program can be performed on the vehicle remotely.

2. Mobile: the program can be performed by a mobile service or in a workshop.
3. Workshop: the program must be performed in a workshop.
Status: this column indicates the status of the test program using a symbol. The symbols shown are the
same as those in test plan version 1.
Priority: this column indicates the probability that a test program will resolve the associated fault.
Perform test: this button is used to start the highlighted test. Offboard Diagnostic Information Sys-
tem Service then switches to the Operation tab.
Documents: documents for the test plan or for a marked test program can be displayed using this button.
Offboard Diagnostic Information System Service then switches to the Information tab.
Cross-reference:
There are additional explanations about the documents made available in Guided Fault Finding in the
chapter Documents.
Select own test: this button opens the Tests overview window, in which test programs for individual
vehicle diagnostic objects can be added to the test plan.
Cross-reference:
Remove: test programs that were added manually can be removed from the test plan using this button.
To select a test program (test), either click on the text line marked in gray or on the appropriate symbol
at the left.
Figure 6.93 Activating a test in the test plan
The Perform test screen button becomes active after clicking.
The content of the selected test program is displayed under the list as an explanation.
Perform test: clicking this screen button starts the test program.
If a Wi-Fi diagnostic interface is used when starting the test program, the system periodically checks if
there is another suitable Wi-Fi connection available. It not, a warning message about the Wi-Fi connec-
tion status is displayed.
Cross-reference:
Also refer to the chapter Wi-Fi Connection Status.
If there are only sporadic DTC memory entries when starting a test program, the modal dialog will
display “Sporadic DTC memory entry decision”. This gives the option to react individually to the current
situation, and it can also influence which action should be performed next.
Figure 6.94 Sporadic DTC memory entry decision dialog
This dialog will close when one of the four option buttons is pressed. The following table indicates
which action will be performed depending on the selected action and which result status for the selected
test program will then be displayed in the test plan:
Option Action Result status for the selected test

program
The associated test program

1 will be performed. The result status will be set ac-
cordingly.
The “Elsa-R View” will open in The current result status for
2 a separate window. The asso- the test program will remain.
ciated test program will not be
performed. As long as the
“Elsa-R View” is not imple-
mented in ODIS, button 2 will
remain inactive.
The associated test program
3 will not be performed. Result status “OK” will be set:
The associated ambient con-

4 ditions will be displayed in the The current result status for the
“Ambient conditions” modal di- test program will remain.
alog. After closing the “Ambi-
ent conditions” dialog, the
“Sporadic DTC memory entry
decision” dialog will be dis-
played again. The associated
test program will not be per-
formed.
Table 6.2 Actions for the Sporadic DTC memory entry decision and result statuses for the test program
If the selected test program has been automatically added due to “unauthorized DTC memory entries”,
the following message will appear before it is performed:
Figure 6.95 Note when executing test programs with “unauthorized DTC memory entries”.
Yes: the test program will be performed.
No: the test program is not performed and the system does not switch to the Process tab.
Offboard Diagnostic Information System Service now switches to the Operation tab, where the in-
structions and input options for the test program that has started are displayed.
Figure 6.96 Test view in the Operation tab
The name of the active test program is shown in the upper left ("Error in ECM" in the example above),
with the name of the current step below it ("Reporting" in the example above).
OK/Next: this screen button confirms a message and moves to the next test step.
Cancel test: if the test is ended early by clicking on this screen button, the canceled test program is
identified with the symbol on the Test plan tab under the Status column. When canceling, the
vehicle brought to a safe state, where additional action may be necessary.
Help: this screen button is available when help information is available for a test program. Pressing the
button displays the help information in a separate dialog.
Cross-reference:
Also refer to the chapter Help.
The navigation screen buttons under the messages can be used to navigate within the individual mes-
sages.
Goes back to the first message of the current test step. If the first message of a test step is
already being shown, it goes back to the previous test step. This button is only active if there are still
messages before the current display position in the history.
Displays the last available message of the current test step. If the last message of a test step is
already being shown, it advances to the next test step. This button is only active if there are still messages
after the current display position in the history.
One message back. If the first message of a test step is already being shown, it goes back to the
previous test step. This button is only active if there are still messages before the current display position
in the history.
One message forward/next message. If the last message of a test step is already being shown, it
advances to the next test step. This button is only active if there are still messages after the current
display position in the history.
Notice:
The history is limited to the last 20 test steps performed. The navigation buttons can only go back so
far.
The font size inside the message and instruction window can be changed using both screen buttons at
the bottom on the left side. Repeatedly pressing the buttons on the screen makes the font size larger or
smaller (maximum three sizes). Any changes to the font size will remain after closing Offboard Diag-
Makes the font size larger. The screen button turns off once the maximum font size is reached.
Makes the font size smaller. The screen button deactivates once the minimum font size is
reached.
The Message and instruction window is located in the center of the operation view.
Figure 6.97 Message and instruction window in the test procedure
The test procedure message window contains information and instructions for the individual test steps.
The individual steps in the active test program that have already been performed are listed in the left
area. The display for the test steps can be configured under Administration in the GFF process section.
Cross-reference:
Refer also to the chapterGFF Process under Administration Mode.

Figure 6.98 Sequence of steps in the test procedure
Click the navigation screen buttons described above or click the individual test steps on the left near the
fault finding notes (for example: Procedure, Model selection, Delay, DTC evaluation, etc.) at any
time to display the completed messages and view the fault finding tips as long as they are still available
in the test step history. Each active test step is shown with a blue border.
A test program can provide alternative test steps for selection.

Figure 6.99 Screen buttons to select alternate test steps
In the example shown above, the desired campaign can be selected with the numbered screen buttons (-
1- and -2- here). If the screen button -2- is clicked in the example, the next instruction for correcting the
fault is displayed.
Figure 6.100 Display of selected test steps
In this example, the -2- screen button was selected, which is indicated by the -2- under the possible
selections.
A test program can prompt decisions by means of screen buttons.

Figure 6.101 Decision buttons in the test program
In the example above, the question asked in the test program must be answered by clicking on Yes or
No.
The screen buttons shown here may have different names. The names depend on the content of the test
program. The test program may also prompt you to enter values using the keyboard. In this case, an
input window will open instead of the screen button.
A test program can display the Print button.

Figure 6.102 Print button in the test program
Pressing the Print button sends a print job is sent to the operating system. The printout contains the
default header and footer, the title of the test currently being performed and the message currently being
displayed in the output field.
If a test program message must be printed out, the button is bordered in red. The Complete/Next button
is then inactive. The red border is removed and the Complete/Next button becomes active only after the
message is printed.
Note:
The Complete/Next button may remain inactive if there are other document buttons with a red border.
6.4.1 Measured Values

In some test programs, it is necessary to read the measurements from one or more control modules.
These measured values are determined either from the measured value tables or from the ODX data
(UDS control modules only).
In this case, the user will be requested to select the measurements. This takes place in the following
dialog:
Figure 6.103 Measurement selection
All available measurements appear in the table.
Selection: click the box to select or deselect a measurement.
ID: the measured value text ID. If the measured values are based on ODX data, this field may be empty.
Measurement: the name of the measurement. If the measured values are based on the ODX data and
no text ID could be determined, translation is not possible. In this case, the long name of the measured
value will be displayed.
Click on the column header to sort the table by ID or Measurement.
Search: it is possible to search for a measured value based on the name or ID in the list. Enter the text
to be searched in the field next to the Search button. The search can be run by clicking on the button or
pressing the Enter key on the keyboard. The Measured value and ID columns will be searched.
If the search finds a match, the entry found will be marked but not selected automatically.
Select all: select all measurements in the table. The screen button is off when all the measurements are
selected.
Deselect all: deselect all measurements in the table. The screen button is off when no measurements are
selected.
OK: the dialog closes and the selected measurements are incorporated into the test program.
Cancel: closes the dialog without saving the measurements.
The measurements read by the test program are then displayed in a table. These are separated based on
whether the measured values came from a measured value table or from the ODX data.
6.4.1.1 Read Measured Values Results Window (Measured Value Table)
Figure 6.104 Measured values display (measured value table)
Address: the control module address that is processing the measurement.
Name: the measurement name.
Value: the measured value.
Unit: the measured value unit.
Target value: the expected value or a range of values in which the measurement may be found.
Click on the column header to sort the table by Address or Name.
Begin Updating: begins updating the measurements periodically. The column header changes to Stop
Updating while the measurement is running.
Stop Updating: stops the measurement currently running.
Description: opens a new dialog with a description of the measurement.
Add to the test plan: adds the selected measurement to the test plan.
Ok: ends the dialog and stops the measurement. The measured value data is then shown as a table in the
procedure window.
When a measurement is selected and the description screen button has been activated, a dialog window
with the exact description of the measurement will open:
Figure 6.105 Description of a measurement
Close: closes the window.

6.4.1.2 Read Measured Values Results Window (ODX Data)
Figure 6.106 Measured values display (ODX data)
Measured value name: the name of the measured value. If no text ID could be determined, translation
is not possible. In this case, the long name of the measured value will be displayed.
ID: the measured value text ID. If it could not be determined, the field will be empty.
Value: the result of the measurement with the unit.
Clicking on the column header sorts the table by Measured value name or ID.
Search: it is possible to search for a measured value based on the name or ID in the list. Enter the text
to be searched in the field next to the Search button. The search can be run by clicking on the button or
pressing the Enter key on the keyboard. The Measured value name and ID columns will be searched.
If the search finds a match, the entry found will be marked. If the entry is in a hidden node, the note will
be opened.
The measured values can be updated either in cycles or one time.
Update once: starts a one-time update of the measured values.

Start update: begins updating the measurements periodically. The button then changes to "Stop update"
and can be pressed to stop the update cycle.
Ok: closes the window. The measured value data is then shown as a table in the procedure window.
6.4.2 Gateway Coding

If a program for Gateway coding is accessed, the test sequence will have a few special instructions.
These are described below.
The test program determines which control module is already coded in Gateway and which additional
control modules are available for selection. These are shown to the user in a dialog.
Figure 6.107 Selection of control module to be coded
All control modules are listed in the left column, which from the data were identified and are still not
marked in Gateway as installed.
The control modules in the right column are marked as in Gateway as installed.
describes the control modules in the right list.
describes the control modules in the left list.

OK: coding with the current selection continues.
Cancel: the selection is discarded and coding is canceled.
If you confirm the dialog with OK, the selection is shown in a list. The control modules coded or to be
coded appear in front of the not coded ones.
Figure 6.108 Display of the coded/not coded control modules in the test program
If you continue the test program with Complete/Next, then additional decisions for special coding must
be made for some vehicles. You will be asked for vehicle brand, vehicle version, the number of door
and if the vehicle has right-hand or left-hand drive. This information is already in the Gateway control
module and can be changed by the user. The information read from the Gateway is framed in blue.
This inquiry for this information is also constructed the same and displays the brand as shown in the
example:
Figure 6.109 Special coding - brand selection
Clicking on the information to be coded open the window with the next inquiry.
After all the decisions for special coding are made, the user must confirm one more time that the Gate-
way coding should be written now:
Figure 6.110 Inquiry before writing the Gateway coding
If this test step is answered with yew, then the coding will be written into the control module.
With No, the coding is canceled. If the selection of coded control modules was changed earlier, then the
user is instructed to confirm the cancellation.
Figure 6.111 Inquiry with changed coding
Clicking on yes cancels the coding.
With No the new coding is written into the Gateway control module.
6.4.3 Documents
Documents can also be supplied in the test programs for individual test steps.
Figure 6.112 Function descriptions in the test program
The documents are accessed using the corresponding buttons, for example Networking diagram. The
name of the document, and therefore the name of the button, depends on the test program.
Clicking the Networking diagram button displays that document.
This pertains only to documents that are integrated into the test programs.
Local and global documents can be allocated to a test program. Local documents pertain to individual
test steps. Global documents pertain to the entire test program.
Figure 6.113 Local and global documents in the test program
If several local and global documents are integrated into a test program, all of the local documents will
be listed in an upper block and all of the global documents in a lower block. Both blocks are clearly
separated from one another. Documents with the same name are numbered in both blocks.
Cross-reference:
For additional information on the documents, refer to the chapter Documents.
Figure 6.114 Document view
The document is displayed in its own window. No other actions are possible while this window is open.
Print: opens the Print dialog to print the current document.
Close: clicking this button will switch from the document view back to the test step in the test program
in order to continue with the test.
This button is initially deactivated. It is only relevant if the document contains hot spots. The
button will activate if one is clicked. When pressed, the previous document will be displayed.
Cross-reference:
For more information on hot spots in documents, refer to the chapter Documents.
Other buttons may also be displayed, depending on the type of document.

Displays the complete document.
Makes the document view larger.
Makes the document view smaller.
If the view was made larger previously, clicking this button makes it possible to move the section
of the document that is currently displayed by clicking and dragging.
The display of some documents may be configured in the test program so that they must be printed out.
The buttons for the affected documents are indicated by a red border. If this is the case, the Print dialog
will open automatically when the document is displayed. The document cannot be closed until this dia-
log is closed or canceled.
After the test program is completed, clicking the Complete/Next button ends the test. Offboard Diag-
nostic Information System Service switches back to the table view in the Test plan tab and the next
tests can begin.
6.4.4 Test Verification

A test program can be performed more than once by selecting it and starting the test again using the
Perform test button. If the test program was already completed at least once without interruption, a
message will appear, asking if a Verification should be performed.
The verification mode allows you to check entries other than the ones in the previous test in order to
either confirm or disprove the earlier results (verification).
Figure 6.115 Verification mode inquiry
Yes: clicking this button starts a test again that was already performed successfully. Depending on the
type of test, it can be performed again with different parameters or selections.
No: clicking this button performs successful test again using the same parameters.
6.4.5 Component Selection
In the Test plan tab, it is possible to add additional tests for vehicle components or documents to the test
plan manually.
Click the Select own test... button in the Test plan tab to do this.
The Test overview window appears, which displays the vehicle diagnostic objects. The desired test or
document can be selected here from the menu tree structure.
Figure 6.116 Test selection window
Click the plus symbol (+) to navigate deeper into the structure. Documents can also be added to the test
plan in addition to components. Selected documents are listed like test programs.
Documents: the Documents button will be active if the selected object has at least one document. Click-
ing on this closes the dialog and opens the document in the Info view. After displaying the document,
the system switches back to the Test plan view and the Test overview opens again with the last objected
selected there marked.
Attach to test plan: once the required test for a component or document is selected, it is added by
clicking this button. A test program or document can also be selected by double-clicking.
Additional components or documents can then be added.

Manually added tests are located at the end of the test plan.
This test programs and documents can be removed from the test plan using the Remove button in the
Test plan tab.
You can also search for a testing using the search function by clicking the Search symbol.
Cross-reference:
Also refer to the chapter Search.
The test program for the manually added components and documents can now be started by clicking the
Perform test button.
Note:
Tests and documents that were added to the test plan manually are shown in light blue.
Notice:
Components that were added to the test plan manually but not tested with the Perform test button are
NOT transferred when the test plan is recalculated.
6.4.6 Help
Test programs may contain help information. This information can be accessed by clicking on the Help
button while performing the test program.
Figure 6.117 Help window
The help window may contain a button to print the help information.
Clicking on the Print symbol sends a print job to the operating system. The printout contains the
default header and footer and the help information displayed in the window.
6.4.7 Build Status Documentation for Components that are Not Diag-
nostic-Capable
The equipment documentation (BZD) is a system for traceability of components in the vehicle.
In the event of recalls, warranty and goodwill procedures, and in-house fault situations (local cam-
paigns), the BZD allows for exact tracing of faulty, documented components, such as engines, airbags,
or brake boosters, to individual vehicles. This makes it possible to isolate the quantity of vehicles actu-
ally affected and minimize costs associated with damage cases.
Components that are not diagnostic-capable like control modules will have an external ID with a bar
code or 2D code and corresponding writing applied to them or integrated into existing labels, in order
to make this component unique and traceable. Among other things, the bar code or 2D code contains
Build group data or serial numbers of the components (hereafter referred to a serial numbers) that enable
mapping to the manufacturer, production facility, and production date.
Some test programs request the user to record such components. The following dialog will open for this:
Figure 6.118 Equipment documentation (BZD) for components that are not diagnostic-capable
The components that are already recorded will be displayed in the table.
Components whose build group/serial number appears multiple times are highlighted in red.
An empty element will always be displayed in the bottom line, regardless of the sorting. It allows for
manual recording of components.
Recorded components can be changed manually.
Build group/serial number: the build group or serial number of the recorded component. Empty for
an empty element. Clicking will start manual editing of a component that has already been recorded
(a new one if there is an empty element).
Recording: the way the component was recorded:

 A – automatically scanned in
 M – manually entered
 E – scanned in and then edited.
Empty for an empty element.
Check sum: to avoid errors during recording, a check sum check will be performed for the build
groups/serial numbers after recording. A symbol will indicate the result of the check:
 for a successful check (OK)
 for an incorrect check sum (not OK)
Empty for an empty element.
Trash can symbol: a recorded component can be removed from the table by clicking this symbol.
Not present with an empty element.
Notes: messages about the editing status of recorded components are displayed in this area. The follow-
ing messages are possible:
 "At least one build group data sequence/serial number must be entered."
 "At least one build group data sequence is inconsistent (the check sum test has failed)."
 "There are duplicate build group data/serial numbers."
Multiple messages can be displayed if they apply.
Complete: recorded data can be transferred to GFF for further processing using this button. The dialog
will be closed. The button is only active if at least one build group was recorded and there are no
duplicate build groups/serial numbers.
If the check sum test resulted in an error for at least one build group, the following dialog will be
displayed:
Figure 6.119 Message dialog for incorrect check sums
“Back” closes the message dialog and recording of the build groups can be resumed.
“Complete” closes the message and recording dialogs and the recorded data will be transferred to
GFF for further processing despite the check sum error.
Cancel: this button discards the recorded build group data and the dialog will be closed without trans-
ferring to GFF.
6.4.7.1 Recording Data
The build group data can be recorded by manual input using the keyboard or by scanning in barcodes or
2D codes.
Data scanned in by the scanner functions like data entered with the keyboard.
6.4.7.1.1 Manual Recording
Manual recording of build groups is started by clicking an existing build group/serial number or this cell
in an empty element. The cursor shows the input position. The changed input can be confirmed with
“Return” or discarded with “Escape”. In both cases, the editor closes.
If the empty element was edited and input was confirmed with "Return”, the new build group will be
included in the sorting and a new empty element will be added to the bottom and immediately opened
for input. This makes it easier to manually input multiple build groups.
After editing a build group that is already present, the empty element will not then be opened for editing.
Note:
Scanner input functions the same way that keyboard input does. This means when the editor is open,
characters entered by the scanner will be added where the cursor is. The combination of keyboard and
scanner can lead to incorrect input and display of error messages.
6.4.7.1.2 Recording by Scanner
Recording of build groups by scanning bar codes or 2D codes can be started once the table is in focus,
regardless of whether an element is open for editing or not.
Barcodes or 2D codes can contain data for multiple build groups that are separated by a “&”. Each
individual data set must begin with a “#” and contain four “#”. The build groups/serial numbers that are
relevant here can follow the fourth “#”, separated by “*”. Data sets that do not contain a build group/se-
rial number will be ignored.
The data from a scanned barcode or 2D code will be analyzed and any existing build group or serial
numbers will be extracted. A dialog will indicate errors in the scanned data, if present.
Figure 6.120 Message dialog for errors in scanned data
All build groups/serial numbers that are detected correctly will be transferred into the table as entries.
If a build group was open for editing when scanning, it will be replaced by the first scanned build group
and all additional scanned data will be added as new entries.
If no build group was open, all scanned data will be added as new entries.
Note:
Data recorded by the scanner will be processed the same way as keyboard input. If an entry in the table
is open for editing when scanning, all scanned characters will initially be stored in a scanner buffer.
Once a “=” is entered in this buffer, the buffer content will be forwarded for processing.
If there is a scanning error, there may be characters in the scanner buffer that are not completed with
“=”. This can also happen with a combination of scanner and keyboard input when the editor is not
active.
The scan buffer is cleared when manual input is started (activation of the editor by clicking the cell).
This means that any characters present that are not ended with “=” will be discarded.
The processing of scanner buffer data can be forced by entering a “=” on the keyboard when the editor
is not activated.
6.4.8 Quick View in Workshop Information

With the quick view, workshop information can be displayed actively based on the context without
having to exit the Offboard Diagnostic Information System Service to search for information in ex-
ternal group systems.
Quick View can be started while running test programs using a button under the GFF message window.
The button is shown with a red outline in Figure 6.121.
Figure 6.121 “Quick View in Workshop Information” button

Notice:
During diagnostic entry, the system will check if the quick view is available for the current vehicle. The
“Quick view in workshop information” button will only be displayed if quick view is available or if
errors occurred when checking if quick view is available.
The check for availability of quick view can fail, for example if diagnostic entry was performed without
logging in first.
The button will only be active and available for the user to select if the current message window displays
texts that contain analysis codes for workshop information or if errors occurred when checking if quick
view is available.
6.4.8.1 Pressing the “Quick View” Button
If errors occur during diagnostic entry when checking for the availability of ASID information, the check
will be performed again now.
If it turns out that quick view is not supported for the vehicle, a message will be displayed (see Figure
6.122) and the “quick view” button will be hidden.
Figure 6.122 “Quick view is not supported for the vehicle” message
If it turns out that ASID is supported but there are currently no analysis codes in the text in the message
window, a message will be displayed (see Figure 6.123) and the “quick view” button will be deactivated.
Figure 6.123 “Currently no analysis codes” message
If quick view is supported for the vehicle and there currently are analysis codes, a modal dialog for
displaying quick view workshop information will be opened.
6.4.8.2 “Quick View in Workshop Information” Dialog
The quick view dialog can display information in multiple tabs. The analysis codes contained in the
GFF message window at the time it is opened will determine which tabs are displayed.
The Figure 6.124 displays this dialog, for example:
Figure 6.124 “Quick View in Workshop Information” dialog
The content of available tabs will be determined once they become active. If errors occur when deter-
mining the content, error messages about this will be displayed and the tab will remain empty. The
process of determining the tab content will be repeated during activation if the content could not be
determined before.
The available information will be displayed in the interface language that is currently selected.
6.5 End Diagnosis

In the end diagnosis section, the diagnostic session is completed with the clearing of the DTC memory,
the performing of end modules and the option for feedback.
Figure 6.125 End Diagnosis section
To end diagnosis, click the End diagnosis button on the Control modules tab.
Figure 6.126 End Diagnosis
Offboard Diagnostic Information System Service then opens the End diagnosis confirmation win-
dow with the question Do you want to end the current diagnostic session?
Yes: the diagnosis is ended.
No: diagnosis is not ended. It continues with no changes.
After selecting Yes, Offboard Diagnostic Information System Service then asks in the Exit GFS:
Decision to end GFF? window if it should continue Guided Fault Finding. If all of the tests listed in
the test plan were not performed, the window contains a message indicating that the test plan was not
completed.
Figure 6.127 Ending fault finding
Yes: Guided Fault Finding continues and does not end.
No: Guided Fault Finding is ended and the system continues exiting the diagnosis.
If all of the tests listed in the test plan were performed instead of only tests due to unauthorized DTC
memory entries are open, the following window with the same selection options will appear:
Figure 6.128 Ending fault finding when the test plan is completed
If a Wi-Fi diagnostic interface is used when ending the diagnosis, the system periodically checks if there
is another suitable Wi-Fi connection available. It not, a warning message about the Wi-Fi connection
status is displayed.
Cross-reference:
Also refer to the chapter Wi-Fi Connection Status.
If the vehicle was switched during the diagnostic session, Offboard Diagnostic Information System
Service asks if the repair should be continued on the connected vehicle or if the session in progress
should be canceled.
Figure 6.129 Note about changing the vehicle
Continue: the system continues exiting the diagnosis.
Cancel: clicking this button cancels the diagnostic exit and continues the repair on the connected vehi-
cle.
If diagnostic exit continues, the DTC memory for all control modules, including the OBD control mod-
ules, is erased.
If a new DTC memory check produced new or different results, Offboard Diagnostic Information
System Service asks if a new test plan should be calculated.
Figure 6.130 Erases the DTC memory
Yes: clicking on this button creates the test plan again and continues Guided Fault Finding.
No: no new test plan is created and the system continues exiting Guided Fault Finding.
In the next step when ending diagnosis, the end module is performed. These programs are based on the
vehicle type that was diagnosed and its equipment versions. There is no set group of end module pro-
grams. Diagnostic editors create them individually for the available vehicle types. The sequence in
which they run is also not the same for all vehicles. Likewise, the program sequence may also be very
different.
The end module programs are listed in the Operation tab as with guided fault finding and decisions
may have to be made or questions may have to be answered, depending on the program.
Notice:
One exception is the Readiness code program. This program is a fixed component of Offboard Diag-
nostic Information System Service and is always performed when ending Guided Fault Finding.
For diesel vehicles with diesel particulate filter, the readiness code program is an end module that is
created by diagnostic editors. Because of this, the program sequence may differ for diesel vehicles.
Figure 6.131 Performing the readiness code program
Yes: clicking this button performs the readiness code test program.
No: the readiness code program is not performed.
In the last program in the Operation tab, you must decide if the diagnostic log will be sent to Support.
Figure 6.132 Send diagnostic log?
Send: the diagnostic log will be sent to Support automatically as long as a network connection is avail-
able. If there is currently no network connection, the diagnostic log will be saved and will be sent the
next time Offboard Diagnostic Information System Service is started.
Cross-reference:
Also refer to Diagnostic Log for detailed information about sending diagnostic logs.
Skip: the diagnostic log is not sent.
The Exit GFF: print/save diagnostic log dialog comes after the end module. In this dialog, you can
select if a diagnostic log should be printed or saved.
Figure 6.133 Print/save diagnostic log
Print: Offboard Diagnostic Information System Service opens the Select diagnostic log dialog. After
selecting the log type, which can also be canceled, a formatted diagnostic log is sent to the standard
Windows printer driver. This will open and it can be printed with all known Windows settings. You
must confirm with OK to end the print process. The Exit GFF: print/save diagnostic log dialog then
opens.
Save: Offboard Diagnostic Information System Service opens the Select diagnostic log dialog. After
selecting the log type, which can also be canceled, the Windows save dialog for saving the log opens.
After saving or canceling the save, the Exit GFF: print/save diagnostic log dialog opens.
Figure 6.134 Select diagnostic log
In addition to the desired diagnostic log version, you can also select the OBD log here. If OBD log is
checked off, both the diagnostic log and the OBD log will be printed/saved.
OK: sends the desired log to the printer or the save function,
Cancel: returns to the previous dialog without any further action.

Cross-reference:
Refer to the chapter Log for detailed information on selecting the log type and saving the log.
Next: Offboard Diagnostic Information System Service continues exiting GFF.
To conclude, Offboard Diagnostic Information System Service opens the Send support request di-
alog. Here it is again possible to send the diagnostic log with a support request.
Figure 6.135 Support request
Cancel: the support request is canceled and is not sent.
Send support request: an automatic support request is sent with the diagnostic log.
If there are errors in the program sequence, you can also edit the support request and add your own
comments and screenshots.
Add comments: the feedback dialog opens for further editing. This button is only available when ending
the diagnostic session if Offboard Diagnostic Information System has detected errors in the program
sequence.
The Feedback chapter provides a more detailed description of the support request.
Cross-reference:
Also refer to the chapter Support.
This ends the diagnostic session. Offboard Diagnostic Information System Service is in the Diagnosis
mode start view.
6.6 Quick Entrance

A diagnostic entrance without Guided Fault Finding is also called diagnostics quick entrance. You can
work in this mode only when there is no order. The self-diagnosis functions are available. In addition to
this, Guided Functions and Special Functions can be performed.
In most cases, the test plan is not available and its tab is not active.
To perform Guided Functions, it is necessary to select a control module in the list of control modules or
in the network plan and then click on Guided Functions in the context menu.
Cross-reference:
See the description of Guided Functions in the chapter
Note:
Networking Diagram.
Since the knowledge base during the diagnostic quick entrance is only partially filtered and not all at-
tributes of the equipment network are known, then the note must be caught up in some cases in order to
determine the Guided Functions belong to a control module.
A dialog is displayed which requires the user to complete the missing equipment characteristics. The
control module can tell which version is installed, or, if the control module is installed or not.
Figure 6.136 Manual control module selection
The following is an example of a dialog. Which available characteristics that are actually displayed
depends on the current equipment network and the on the diagnostic objects contained in the knowledge
base.
OK: accepts the selection and ends the dialog.
GFF programs may contain Guided Functions and Special Functions, which transmit diagnostic objects
relevant to the vehicle. If this is the case, then the test plan tab is active, and if necessary, the new
diagnostic objects are added there. They can then be performed as the other tests.
The GFF program sometimes needs more information, which was not transmitted completely during a
diagnostics quick entrance, about the equipment network in order to transmit the diagnostic objects.
In this case, the dialog described above for manually selecting a control module is called up.
Using this information determined from there, the diagnostic objects relevant to the vehicle are trans-
mitted and are displayed in the test plan tab.
Figure 6.137 Quick entrance test plan
Only the Perform test... screen button is available in this mode. The test is executed just like GFF
diagnostic programs when the screen button is pressed.
Cross-reference:
The test programs performed previously will be checked again after the diagnostic session is over if
quick entrance was used exclusively. If the check is positive, then a dialog will be asked to save and
print the diagnostic log.
Figure 6.138 Print/save diagnostic log
Print: the formatted diagnostic log is sent to the Windows printer and can be printed there. The diag-
nostic log print/save dialog will appear again at the end.
Save: the Windows save dialog opens and then the diagnostic log can be saved. The diagnostic log
print/save dialog will appear again at the end.
Next: the diagnostic exit continues.
Cross-reference:
Refer to the GFF Exit: diagnostic log print/save dialog in the chapter End Diagnosis.
6.7 Diagnosis without a Vehicle
Note:
Diagnosis without a vehicle is only available for certain markets, and data is only available for certain
newer vehicle models.
Some newer vehicles can send information about their status to a group system. This makes it possible
to use the data for an overview or an analysis based on the test plan or technical documentation before
the vehicle enters the workshop. The session data that results can then be used as a basis for the “correct”
diagnosis with a connected vehicle (see chapter Connecting Later to a Vehicle).
The diagnostic process is naturally shorter:
Figure 6.139 Diagnostic entry process without a vehicle:
6.7.1 Diagnostic Entry
Notice:
For diagnostic entry without a vehicle, there must be no vehicle connected. Otherwise, automatic VIN
detection will start and then it would no longer be possible to enter a VIN other than the one that was
read out.
When there is no vehicle connected, the entry screen appears as follows (see also Diagnostic Entry):
Figure 6.140 Start screen for diagnostic entry without a vehicle:
The diagnostic entry is completed in fewer steps and it requires a connection to the group system.
Next, enter the VIN in the VIN field, then log into the group system and start diagnosis by clicking the
“Start diagnosis” button.
Notice:
The login to the group system will only take place for the specified VIN. If you have typed or entered a
different VIN, then you must log in again, even if the brand remains the same.
If the VIN contains too few or too many characters, you cannot log into the group system.
The “Start diagnosis” button will remain grayed out if there is no successful login.
If there is no data available in the group system for the VIN that was entered, you will receive an error
message indicating this when you click the “Start diagnosis” button and you will remain in the start
screen:
Figure 6.141 Error message in the start screen
If diagnosis started successfully, the data will then be loaded from the group system. If it is complete
and contains all of the basic features, you will skip over the basic features dialog and go directly to the
repair order selection view (see chapter Selecting an Order).
Guided Fault Finding (GFF) will start immediately after the repair order is selected.
6.7.2 Test Plan and Special Functions

At the start of GFF, the traversal test will be run and the test plan will be determined. Start modules will
not be run when this happens.
Additional information about diagnosis with vehicles can be found in that chapter Start Modules, Tra-
versal Test, Test Plan Calculation.
The test plan that is created can be expanded as usual by creating and including concerns. See chapter
DISS / TPI.
Special functions and test programs cannot be run without a vehicle. The “Run test...” button will be
deactivated.
Figure 6.142 Test plan view during diagnosis without a vehicle

6.7.3 Working with GFF
Because test programs generally cannot be performed during diagnosis without a vehicle, the test plan
and any information available about the individual test programs it contains can only be viewed and
additional test programs can be added manually.
Documents about the vehicle and access to ElsaPro is also available in the Info mode.
The OBD and Measuring Equipment modes are deactivated.
Additional restrictions can be seen in the control module list. All control modules will be listed there,
but the following items will be grayed out in the context menu:
 Identify control module

 Guided Functions
 Check DTC memory
 Read all DTC memories
 Control module OBD
 Vehicle OBD
Figure 6.143 Sample control module list for diagnosis without a vehicle
6.7.4 End Diagnosis

Ending the diagnosis leads to an abbreviated diagnostic exit, for example DTC memory entries cannot
be deleted.
An incomplete run of the test plan is not permitted and the end modules will not be performed.
In contrast to diagnostic entry with a vehicle, the diagnostic session will be automatically saved during
diagnostic exit without a vehicle.
6.7.5 Connecting Later to a Vehicle

The following timeframes are considered connecting to a vehicle later:
 You connect the vehicle after you have started diagnosis without a vehicle. It does not matter if
this occurs while diagnostic entry is in progress or afterward.
 You load a session file for a connected vehicle that was created during diagnosis without a
vehicle.
During this later connection, the VIN is read out and compared with the one from the session file. If
they are identical, you will receive the following message:
Figure 6.144 Notice about detected vehicle
YES: performs the comparison with the connected vehicle.
NO: closes the dialog. The vehicle will not be used.
During the comparison with the connected vehicle, the sections of diagnostic entry that are omitted
during diagnostic entry without a vehicle are now performed to allow the actual vehicle situation to be
integrated into the test plan. This means:
 The suitable vehicle project is loaded.

 The gateway components list is read out.
 Control modules that were already reported as faulty by the group system and that are marked
as faulty in the vehicle will be read out with the DTC memory entries.
 The start modules will be run.
 The test plan will be updated.
After the comparison with the connected vehicle, GFF, special functions, OBD, and Measuring Equip-
ment can be used without any further restrictions and the test programs from the test plan can now be
run, for example.
Notice:
If the diagnostic session is saved after the comparison, you will always need to have the connected
vehicle in order to load it again.
6.8 Documents
Offboard Diagnostic Information System Service makes a wide variety of documents available.
These documents come from the knowledge bank in the diagnostic database and are based on the vehicle
being diagnosed and its equipment versions. Documents are available in the Diagnosis and Flashing
modes.
Notice:
The document tree display on the Documents tab is only available once diagnostic or flash session has
been completed, because the documents are only assembled for the vehicle that is being diagnosed.
Vehicle documents: clicking this button displays all of the documents available for the entire vehicle
in a tree structure in the Documents tab.
Figure 6.145 Selecting a document to display

In the tree structure, individual branches can be opened or closed by clicking the plus sign [+] or minus
sign [-].
After marking a document listed in the tree structure with the mouse, the button for displaying the doc-
ument appears.
Show document: the marked document opens.
The document can also be opened by double-clicking directly on the document tree.
Figure 6.146 Viewing a document
Clicking this button returns to the document structure. If a hot spot is shown, clicking on the
button returns to the initial document.
Other buttons may also be displayed, depending on the type of document.
Displays the complete document.
Makes the document view larger.

Makes the document view smaller.
If the view was made larger previously, clicking this button makes it possible to move the section
of the document that is currently displayed by clicking and dragging.
There are documents that contain only text or illustrations as well as documents that combine text and
illustrations. The combined text-illustration documents are displayed next to each other.
The following are three examples of typical documents for a vehicle.
Example 1 for a text document.
Figure 6.147 Example 1, document tree
Selection of: Suspension - Repair Manual - General Information on Checking Wires

Figure 6.148 Example 1, document view
Example 2 for a combination text/illustration document:

Figure 6.149 Example 2, document tree
Selection of: Body - Specified Values – Headlamp Adjustment
Example 3 for an image document.

There are Hot Spots in illustration documents. Hot spots are areas of the illustration that are outlined in
red.
Figure 6.152 Document with Hot Spot

Clicking a Hot Spot opens another illustration with a more detailed view of the area that was outlined
in red.
Figure 6.153 Open Hot Spot
Documents can be printed out in the current view.
Cross-reference:
See also chapter Current Tab.
6.8.1 Documents in GFF

There are a number of different documents for the Guided Fault Finding test programs. These documents
are available in Diagnosis mode, either in the test plan view or in the test programs themselves.
Cross-reference:
Figure 6.154 Displaying documents for a test plan
Documents: clicking this button on the Test plan tab in Diagnosis mode opens a context menu where
you can select if documents should be displayed for a test plan or a test program:
Test plan documents: all documents related to diagnostic objects contained in the test plan are provided
in a tree structure.
Test program documents: all documents related to diagnostic objects contained in the test program
that is marked are provided in a tree structure.
After selecting the document type, Offboard Diagnostic Information System switches from the Test
plan tab to the Documents tab.
Documents for the test programs contain the following content. The test program determines which
documents are available.
Block diagram
CD content file
Adjusting guidelines
Component location
Description of function
Function test guide
Measuring equipment
Pin assignment
Fuse assignment
Connector view
Tools
Wiring diagram
Repair manual
7 OBD Mode
The following chapters describe under which conditions the control module OBD functions as well as
Guided Fault Finding are available, how the OBD functions are accessed and what the individual func-
tions are able to do.
OBD gives the user the opportunity to access individual diagnostic functions for the control module or
vehicle. OBD is generally used when:
 There is no GFF for the vehicle (very old or very new model),
 There is no GFF for that particular problem,
 The GFF suggests using OBD.
In contrast to GFF, the user must interpret the results.

7.1 Starting OBD
Figure 7.1 OBD entry start window
Clicking on Start OBD starts the OBD entry.
The vehicle VIN is found here and is used to identify the vehicle.
If a clear identification is not possible, the basic information dialog opens, in which the user must fill in
the missing information.
Cross-reference:
Refer to the chapter Vehicle Features Dialog (VFD).
Then the components list is read and displayed in the Components list tab under the Control modules
tab.
The Control modules tab in the OBD operating mode is structured like the Control modules tab in the
Diagnosis operating mode.
Figure 7.2 Control modules tab in the OBD operating mode
It contains the tabs:
Networking diagram
Cross-reference:
See chapter
Note:
Networking Diagram in the section Diagnosis Operating Mode.
Control module list
Cross-reference:
See chapter Control Module List in the section Diagnosis Operating Mode.
Components list
Cross-reference:
Refer to chapter Components List in the Vehicle-Specific Functions section.

DTC memory list: the DTC memory list tab is inactive during the OBD operating mode. The tab
only becomes active when switching to the Diagnosis operating mode.
Cross-reference:
Refer to chapter DTC Memory in the Diagnosis Operating Mode section.
Equipment list: the Equipment list tab is inactive during the OBD operating mode. The tab only
becomes active when switching to the Diagnosis operating mode.
Cross-reference:
Refer to chapter Equipment List in the Diagnosis Operating Mode section.
The selection lists for the OBD and vehicle functions are also available:
To quickly start a vehicle function, the function can be selected from a list. The vehicle-specific
functions
Total DTC memory
Transport mode
OBD customer service
Engine group
Lock vehicle
are available. After selecting the desired function, it is started by clicking on and is displayed in
its own tab in the Results tab (except for the Transport mode function).
To quickly start an OBD function for the control module selected in the Components list, Control
module list or Networking diagram, the function can be selected from a list. The control module-
specific OBD functions
DTC memory
Identification
Output Diagnostic Test Mode
Basic setting
Coding
Bus master coding
Coding subsystems
Coding software compositions
Measured Values
Adaptation
Access authorization
Data Upload
Multiple Identification Data
are available. After selecting the desired function, it is started by clicking on and is displayed in
its own tab in the Results tab (except for the Access authorization function).
The results views of OBD are displayed as in the example Adaptation as follows.
Figure 7.3 Example of OBD view in adaptation
The view is divided into three areas.

The actual OBD function is performed in the main area.
The tabs for the different selected OBD and vehicle functions are listed under the main area. Here,
the user can move between the different tabs or can close them by clicking on .
With control module-specific OBD functions, the name of the control module is displayed here. If
the name is too long can cannot be shown completely in the field, then clicking on the field shows the
complete name. For vehicle-specific functions, the specific text for the vehicle function is displayed in
this field.
The move quickly to a different OBD function for the same control module, use the list to do this.
All control module-specific OBD functions are listed in this list. After selecting the desired function,
clicking on starts and displays it in its own tab. This selection list is not available for several
vehicle-specific functions.
7.2 Switching to OBD Operating Mode

You can also switch to the OBD operating mode if a Diagnostic entry or Flash entry was already
performed. Switching is possible if one of the following diagnostic entries was performed:
Diagnostic entry with Guided Fault Finding
Diagnostic entry without Guided Fault Finding
Flash entry
If you switch to the OBD operating mode for the first time after one of the above-mentioned entries, a
complete OBD entry is no longer performed. The basic information dialog is not displayed, since the
OBD operating mode is being performed with the data available from the previous diagnostic entry.
Cross-reference:
Refer to the chapter Vehicle Features Dialog (VFD).
Then you are taken directly to the Components list tab for the OBD operating mode.
To switch to the OBD operating mode, there must not be any Test program or Diagnostic function
(for example, Read all DTC memories) currently in progress.
Use the Main diagnosis type button to end the diagnosis. It is not possible to end the diagnosis using
the button for the OBD operating mode. If you use the button in the Main diagnosis type to end the
diagnosis, the OBD operating mode is also ended at the same time.
Cross-reference:
Refer to chapter Ending Flashing in the Flash Mode section. Refer to chapter End Diagnosis in the
Diagnosis Operating Mode section.
Note:
If the Components list tab is active in the Control modules tab when switching from the OBD operat-
ing mode to the Diagnosis operating mode, the Control module list tab is activated in the Diagnosis
operating mode. If the DTC memory list tab or Component list tab is active when switching from the
Diagnosis operating mode to the OBD operating mode, the Components list tab is activated in the
OBD operating mode.
7.3 OBD General Information

7.3.1 Starting OBD from Other Operating Modes
After entering using the OBD operating mode, there are three additional possibilities to perform OBD
functions in Offboard Diagnostic Information System Service:
A diagnosis is performed with Guided Fault Finding without an order.
A diagnosis is performed with Guided Fault Finding with an order.
The diagnostic entry was started as quick entry without the option work with Guided Fault Find-
ing.
Note:
In both cases, an additional entry into the Guided Fault Finding in the
Control Modules using this screen button is possible. This starts automatic control module identifica-
tion and Guided Fault Finding.
Cross-reference:
Refer also to the chapter Diagnostic Entry and
Note:
Networking Diagram.
7.3.2 Accessing OBD Functions

OBD functions can be accessed from the Control module list, the Networking diagram or the Com-
ponents list.
You must click and hold the control module with the left mouse button (approximately 1 second) or
with the right mouse button in the Control module list and the Networking diagram. Then a context
menu opens with the OBD buttons. Some screen buttons are deactivated depending the operating mode
(OBD or Diagnosis).
Figure 7.4 Starting OBD
Control module OBD: clicking this button opens the OBD functions selection window with OBD
functions for the marked control module.
Control module-specific OBD functions can be accessed by double clicking on the respective control
module in the Components list. The OBD functions selection window with the OBD functions also
opens for the selected control module.
Figure 7.5 Control module OBD selection window
The name of the control module is shown in the window.
Perform: the function that is marked is performed. Offboard Diagnostic Information System Service
switches to the Results tab (except with the Access authorization function).
Cancel: no function is performed and the window closes.
Functions can be performed by double clicking on the name of the function.
You can choose among DTC memory, Identification, Output Diagnostic Test Mode, Basic Setting,
Code, Bus Master Coding, Code Sub-Systems, Code Software Compositions, Measured Values,
Adaptation, Access Authorization, Data Upload, and Multiple Identification Data. The Bus master
coding function is only available when the selected control module is a bus master control module. The
Code Sub-Systems and Code Software Compositions functions are only available if the selected con-
trol module supports them.
So long as a function is reported as not supported by the control module on a KWP2000 control module,
the user is shown the message "The selected function is not supported by the control module. Do you
want to try to run the function anyway?"
Yes: the function continues to be performed.

No: closes the dialog and stops performing the function.
Vehicle OBD: clicking this button opens the OBD functions selection window with OBD functions for
the whole vehicle.
Figure 7.6 Vehicle OBD selection window
Perform: the function that is marked is performed. Offboard Diagnostic Information System Service
switches to the Results tab (except with the Transport mode function).
Cancel: no function is performed and the window closes.
Functions can be performed by double clicking on the name of the function.
Here you can choose between the Complete DTC memory, Transport mode, OBD customer service,
Engine group, and Lock vehicle functions.
OBD can be accessed in diagnostics during the diagnostic entry. Not all diagnostic functions are avail-
able in this case to prevent any unintended interactions. You can select the Identification and Measured
values functions in the Control module OBD selection window. All other functions are grayed-out and
cannot be selected until the diagnostic entry is completed. No function can be selected in the Vehicle
OBD window.
Figure 7.7 Control module OBD selection window during diagnostic entry
Figure 7.8 Vehicle OBD selection window during diagnostic entry

Control module-specific OBD functions can also be accessed directly from the Results view or from
the Components list, Control module list and Networking diagram tabs in the Control modules tab.
The desired function is selected from the list at the upper right and is started by clicking on .
Vehicle-specific functions can also be accessed directly from the Components list, Control module
list and Networking diagram tabs in the Control modules tab. The desired function is selected from
the list at the upper left and is started by clicking on .
Cross-reference:
Refer to the description in OBD Mode.
The function is performed and the results are displayed in the Results tab. Each function for each control
module has its own separate tab there. These tabs have different names for the individual functions.
The names for control module-specific OBD functions are as follows:
Function Tab Name
Adaptation ANP
Coding Bus Master BMC
Coding COD
Coding subsystems SSC
Code software compositions SWCO
DTC Memory ESP
Basic Setting GES
Identification ID
Measured Values MW
Function Tab Name
Output Diagnostic Test Mode SGD
Data Upload DUP
Multiple identification data MD
Table 7.1 Control Module OBD View Names
With these functions, the address of the control module is also added to the beginning of the name in
the tab.
Functions that relate to the whole vehicle may have the following names:
Function Tab Name
Total DTC memory VEH - ESP
Engine group VEH - GES
OBD customer service OBD1
Table 7.2 Vehicle OBD View Names
The transport mode and access authorization functions are not listed here because they are shown in a
separate window and not in the Results tab.
Example:
The tab for the DTC memory function for the electronic central electrical system with address 0009 is
named
"0009 - ESP".
Figure 7.9 OBD: sample tab name
Each function can only be active once per control module. If a tab for a function is already open for a
control module and the function is selected again, the tab that is already open will be displayed. To
restart the function completely, you must first click to close the existing tab.
If the control module does not support the function, a warning appears and the system does not switch
to the Results tab.
Figure 7.10 Warning about adaptation that is not supported
Ok: the note will close.
7.3.3 Logging
The OBD functions can be logged while being performed and saved or printed at any point in time.
At the beginning of OBD, a new OBD log is generated. The user can add the data from the actual result
view to it. It is also possible with some OBD functions, which add data in regular intervals.
The screen buttons in the menu are used to use the OBD log. They are described in the OBD log chapter.
Cross-reference:
Refer to the chapter OBD Log.
7.3.4 Using the Keyboard

Some settings can also be made using keyboard shortcuts. The following shortcuts are available:
Keyboard
Function
Shortcuts
CTRL+ C Copies the content of a selected table to the clipboard
Tab Selects the controls on a result view one after the other.
CTRL + left ar-

In views with two selection lists: moves an element from the right to the left list
row
CTRL + right
In views with two selection lists: moves an element from the left to the right list
arrow
Keyboard
Function
Shortcuts
CTRL + up ar-
Moves the selected element up one position in a selection list
row
CTRL + down
Moves the selected element down one position in a selection list
arrow
Shift + left ar-

Switches back to the previous view
row
Shift + right ar-

Switches to the next view
row
Only with output diagnostic test mode and basic setting: start actuator test/basic set-
CTRL + P
ting (Play)
Only with output diagnostic test mode and basic setting: stop actuator test/basic setting
CTRL + S
(Stop)
Only during output diagnostic test mode and basic setting and while performing a
CTRL + N actuator test/basic setting: Next actuator/next basic setting (the same as the Next
screen button)
Only with output diagnostic test mode: in the perform output diagnostic test mode
ESC
view: same as the Stop All screen button.
Table 7.3 Keyboard shortcuts table
Some OBD functions have additional abbreviations. These are described for each function.
7.4 Control Module-Specific Functions

7.4.1 Adaptation
The configuration and operation differ depending on whether the adaptation will be performed with
KWP or UDS control modules.
7.4.1.1 Control Modules with KWP Protocol
When starting the function, the function version must be selected first on some control modules.
Figure 7.11 Selection of function versions
After selecting the function versions and confirming with OK,the Adaptation view is shown.
An adaptation channel must first be selected there. KWP1281 has channels 0 through 99, KWP2000
has channels 0 through 255. In both cases, channel 0 as a special function: selecting is resets all control
module adaptation channels.
Figure 7.12 KWP adaptation
To select a channel, the desired channel number must be entered in the input field and confirmed
with the Select channel or Enter button. The value is checked for correctness when it is entered. If the
number is outside of the permissible value range or if the field is empty, the field appears in red and the
Select Channel screen button is deactivated.
Select Channel: selects the channel entered.
New adaptation values are entered in the Input field .
Actual Value: the adaptation value read from the control module.
Test value: the current test value. Initially identical with the value in the actual value column.
Input: the value entered by the user. Initially identical with the value in the actual value column.
There are four screen buttons on the right side of the view:
Send test value: send the value from the Entry field for testing to the control module. The value is
stored there only temporarily.
Transfer: programs the changed adaptation value into the control module. This value is stored perma-
nently.
Reset: resets the test value to the original value.
Reset all: if test values were set on more than one channel, they will be reset to their respective initial
values as long as the new values were not programmed into the control module using the Transfer
function. This screen button does the same as channel 0. The user must confirm this action in a dialog:
Figure 7.13 Resetting the adaptation
Yes: resets the test values on all channels to their original value.
No: closes the dialog without resetting the test values.
Measured values read from the control module will be shown in a list in the Measured values area
and periodically updated, as long as the control module or data supports this function.
To change the adaptation value for a channel, complete the following steps:
Select the channel.
Click Select channel to confirm.
Change the adaptation value in the entry field and confirm with the send test value or with Enter. The
value is then sent to the control module as the new test value. This process can be repeated as often as
desired. A validity test is not performed while entering. If the entered value lies outside of the valid
value range, the Entry field turns red and the Send test value and Accept screen buttons are deactivated.
Example:
Four channels were selected in the illustrations above. For the instrument cluster control module used
here in the example, the language shown is set in this channel. Value 1 stands for German and value 2
stands for English. If the user now sets the test value to 2, all messages in the instrument cluster display
will appear in English until another test value is entered, the Reset button is pressed or another channel
is selected.
As long as the changed value has not been saved in the control module yet, the user can click the Reset
button to reset the test value back to the original 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 tabs.
If the correct test value was determined, clicking the Transfer button will save it in the control module.
Only then is the value in the actual value column set to the new value. After saving, the Reset button
is deactivated.
It is also possible to apply a newly entered value without Send test value.
7.4.1.2 Control Modules with UDS Protocol
With UDS control modules, all of the available adaptation functions for the selected control module
are listed in a table when you switch to the Adaptation tab. They can be used to change the control
module adaptation values.
This is shown in the following illustration using the control module with diagnostic address 17 (instru-
ment cluster):
Figure 7.14 UDS adaptation
The adaptation functions table has five columns:
Adaptation/Parameter: the name of the adaptation function or parameter.
RDID: the Record Data Identifier.
Current value: the parameter value read out from the control module.
Input: the new parameter value. Click in the Input column for the desired parameter to change the
value. The new value can be selected from a list or entered as free text, depending on the parameter
type
Unit: the unit of the adaptation value.
Each adaptation function has parameters . They are hidden by default. You can double-click in
the line or click the + in front of the function name to display them. Double-clicking again or clicking
on - hides the parameter list again.
To show the parameters for all functions at once, click the button at the bottom right of the table.
Clicking will then close all of the open parameter lists at once. Opening the lists may take some
time, depending on the number of available functions.
Note:
All values that have not been saved or lost when parameter lists are closed. A message will warn the
user about this:
Figure 7.15 Warning when closing the parameter list
Yes: the values that were entered are discarded and the parameter list is closed.
No: the parameter list stays open and the values entered remain.
Note about input assistance for special parameter values:
When selecting input fields for camshaft and crankshaft adaptations for special engine control modules,
an additional input dialog opens in order to simplify and validate these input values.
Figure 7.16 Dialog for input assistance for special parameter values
OK: accepts the entered correction values in the input column of the adaptation table. This button is
only active if the check digit that was entered matches the calculated check digit.
Cancel: ends the dialog without accepting the values.
There is an entry field under the table which can be used to filter the adaptation functions.
Filter: if a text or a partial text is entered in the filter field , then only those measurements that
contain the name of this text or partial text will be displayed.
There are three screen buttons at the bottom of the view:
Restore: restores the value for the selected adaptation function that was saved in the control before the
last programming procedure. Clicking the button displays the last values used in the Input column.
These apply only to the adaptation values visible. To program the restored values into the control mod-
ule, click the Transfer button.
Restore all: restores the value for all adaptation functions that was saved in the control before the last
programming procedure. Clicking the button displays the last values used in the Input column. To pro-
gram the restored values into the control module, click the Transfer button.
Transfer: once the values for all desired adaptation channels have been changed, they can be saved by
pressing the Transfer button. These apply only to the adaptation values visible. The user must confirm
the saving process:
Figure 7.17 Security prompt before performing the adaptation
Yes: the new adaptation values will be written.
No: the adaptation values are not written into the control module.
Reset control module: this option is only active for control modules that support it. If there is a check
mark, the control module will be reset after programming the adaptation values.
Before saving, a validity check is performed on the parameter values that were entered as free text. If
this check is not successful, the values will not be written into the control module and the user will be
informed about the cause in an error message:
Figure 7.18 Error message about invalid adaptation value
If the new values were saved successfully, then will then be displayed in the Current value column.
The Adaptation function may not be supported by all control modules. If so, a notice appears.
Figure 7.19 The adaptation function is not supported
Using the keyboard:
Using the arrow keys on the keyboard allow you to navigate between the individual lines in the table.
In the edit mode in the Entry field, you can change using the spacebar or the F2 button. Using the enter
key applies the new value. Using the ESC key leaves the edit mode without applying the value.
7.4.2 Coding Bus Master

The Code bus master function is only available for control modules that are bus masters. If it is called
up for another control module, an error message will appear.
Figure 7.20 Error message for control module that is not a bus master
Ok: closes the dialog without calling up the function.
The coding of the components list for a bus master control module (Gateway) is different from the
coding for other control modules because it is an overall control module coding. A vehicle project may
contain several bus masters.
The Code bus master view shows the components list in a table, which contains all of the control
modules assigned to the selected bus master. The table also includes the partitioned software cluster of
the bus master, as long as the bus master supports this.
The table consists of three columns. The first column ("Specification") determines if that control mod-
ule should be included in the bus master components list. It is irrelevant if the control module to be
added is a bus master control module itself. When opening the Bus master coding view, the current
code status is read from the control module. A check mark is entered in this column for all control
modules that are already contained in the bus master control module components list.
The second column contains the current status of the control module in the components list ("Actual").
The systems have the following meanings:
The control module is installed and coded.
The control module is installed but not coded.
The control module is coded but not installed.
The third column contains the diagnostic address, followed by the control module name separated by
a hyphen. If no diagnostic address is specified for a control module, the node address will be displayed
in brackets instead. The node address 0x00 is not displayed. If the control module name is unknown,
"Unknown system" will be displayed instead.
Example: 00 - Unknown system or [49] - Unknown system
The table can be sorted in ascending and descending order by clicking on the column title.
The buttons under the table differ depending on whether the control module is a bus master, a KWP or
a UDS control module. The various views are described in the information that follows.
7.4.2.1 Coding KWP bus masters
Figure 7.21 Coding KWP bus masters
Once the user has configured the components list, the coding process can be started using the Transfer
button. A note window appears first, which the user must confirm.
Figure 7.22 Security prompt before coding
Yes: programs the code into the bus master control module.
No: closes the dialog without coding.
During the coding, a dialog with a message indicating that the coding process is running appears.
Figure 7.23 Progress bars during coding
If errors occur during the coding process, the process is canceled and an error message appears.
Figure 7.24 Error when coding (example)
If the coding process was completely successfully, the components list will be read from the Gateway
control module again and displayed.
Once the original code that was read out is changed, the Restore button is activated. Clicking on this
button restores the code that was read from the bus master control module during the last coding proce-
dure.
The Special coding button can be used to edit the special coding detected by the control module. This
includes the vehicle brand, vehicle model, the number of doors and if the vehicle has right-hand or left-
hand drive. This information is already in the bus master control module, but it can be changed by the
user.
As long as a special code is available, it will be displayed in the text line above the buttons. If a special
code could not be read, the text "Special coding not available" appears there. If the control module does
not support special coding, the button will be deactivated.
Figure 7.25 Editing special code
If the button is pressed, a dialog window in which the special code can be changed using selection lists
opens. The special code already exists.
The button becomes active once the coding information is changed. It resets the information back
to the original values.
Write: writes the selected code into the control module and updates the "Special coding" text in the
components list. The coding in the control module list is not changed.
Cancel: the dialog closes and the coding is not written.
In bus master control modules that are addressed with Service 22, there is no special coding and so
neither the button nor the note are displayed.
7.4.2.2 Coding UDS bus masters
Coding UDS bus master control modules is identical to KWP bus masters, except there is no special
coding. Because of that, neither the button nor the note are shown. Instead, there is the "Code automat-
ically" function described below. The components list can also include the bus master software cluster
in addition to the control modules.
There is also an additional Bus system column that indicates on which CAN bus a control module is
located or if this is a bus master.
Figure 7.26 Coding UDS bus masters
Code automatically: this button writes the code based on the subsystem components list and the soft-
ware cluster detected from the control module, meaning the code is written for all control modules that
are marked with the symbols and under "Current installation". The user must confirm the
process after pressing this button.
Figure 7.27 Security prompt before automatic coding
Yes: the code is written.
Figure 7.29 Error when coding (example)
If the coding process was completely successfully, the components list will be read from the Gateway
control module again and displayed.
Note:
The Code automatically function is not available for vehicle projects that contain Daimler control mod-
ules because there is no components list for these. The button is then deactivated.
7.4.3 Coding
The configuration and operation differ depending on whether the coding will be performed with KWP
or UDS control modules.
The process of selecting the subsystem to be coded, meaning the control module that is subordinate to
the current control module, is the same in both cases:
The system will check if subsystems are present.
The system names of all available subsystems are displayed in a selection list. An entry is generally not
preassigned. Instead, "Please select a subsystem" is displayed in the list.
The user selects a subsystem or the control module itself.
The current control module code is read automatically.
If the control module does not have any subsystems, steps 2 and 3 are skipped. The control module is
then selected automatically when the Coding tab opens and the code is read directly.
The remaining steps differ depending on the diagnostic protocol and code type.
7.4.3.1 Coding KWP Control Modules
The following information explains the Coding function for KWP control modules. There are two pos-
sible 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.
Short Coding:
Figure 7.30 Short coding
Transfer: programs the code into the control module.
Restore: enters the last coded value into the New code field. Clicking Transfer saves the restored code
in the control module.
First the application checks if the control module, on which the coding should be performed, has any
subsystems. If this is the case, all subsystem is displayed in the system ID list. There you can select
either a subsystem or the control module.
After opening the tab or selecting the desired subsystem, the code is read from the control module and
displayed in the Old code field. The new value can be entered in the New code field and confirmed with
the Enter key. The Transfer button will then become active.
After confirming the Transfer button, a message with a security prompt appears.
Figure 7.31 Security prompt before coding
Yes: programs the new code value into the control module.
No: the programming process is not performed.
If the coding was successful, another message appears:
Figure 7.32 Confirmation message after coding
After confirming the message, the user is prompted to reset the control module:
Figure 7.33 Prompt to reset the ignition
To do this, the ignition key must be in the "Off" position and then turned back to the previous position.
The new value will now be displayed in the Old code field followed by the original code value in
parentheses:
Figure 7.34 New and old code
This process can be repeated as often as desired. If the coding was not successful due to an invalid value
or another problem, the user will be informed with an error message and the previous code will not be
changed. The message depends on the error that occurred. For example, it could indicate that vehicle
communication could not be established. The coding process can be performed again after correcting
the problem. The following illustration shows an example of an error message:
Figure 7.35 Error message when coding due to incorrect data
Long Coding:
With long coding, the values to be coded are displayed as a bit field up to 40 bytes long. It is displayed
both in binary and hexadecimal format. The code is displayed in the same way as binary coding for UDS
control modules.
7.4.3.2 Coding UDS Control Modules
UDS control modules have binary coding and plain text coding. These are different 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.
UDS binary coding and long coding KWP:
The binary coding display for UDS control modules and the long code for KWP control modules are
generally identical, with a few exceptions. The following description is based on binary coding but it
still applies to long coding.
The code string is displayed in a table format. Each row in the table corresponds to a byte in the code
string:
Figure 7.36 UDS binary coding
Figure 7.37 KWP long coding

The table has five columns:
Byte No.: the byte number in the code string.
Current Hex Value: the value in hexadecimal format.
Current Binary Value: the value in binary format.
Hex Input: the user input in hexadecimal format.
Binary Input: the user input in binary format.
There are three buttons below the table:
Transfer: programs the changed code string into the control module.
Restore: restores the last code that was used.
Plain text coding: UDS only: switches to plain text coding if it is supported by the control module. If
not, the button will be deactivated.
Add byte: KWP only: adds a new line that represents a byte after the selected coding byte. This byte is
pre-filled with 0x00.
Remove byte: KWP only: removes the selected line.
The value of a byte can be changed in both binary and hexadecimal. When you click in one or both cells,
or use the spacebar or the F2 button, a new input screen appears:
Figure 7.38 User input with binary coding
If one of the two values was changed, the corresponding binary or hexadecimal value will update auto-
matically during input. Closing the input form discards the changes.
Transfer: the changes are transferred into the table.
Cancel: discards the changes.

UDS only: once all of the desired changes have been made, the check sum corresponding to the code
string must be entered into the Check sum input field. The check sum can be calculated as follows:
The code string is divided into groups containing 2 bytes each. If there is an uneven number of bytes,
the value 00 will be added to one of the bytes. The values are added and any possible excess is rounded
down.
Example:
Code string: F0 01 02 04 08 10 20
F001 +
0204 +
0810 +
2000
11A15 & 0xFFFF = 1A15
Check sum: 1A15
The user must press the Transfer button to program the code into the control module. A prompt appears
before saving the code:
Figure 7.39 Security prompt before binary coding
Yes: the code string is checked for errors based on the check sum.
No: the coding process is canceled.
If there is a check mark next to Reset control module, the control module will be reset automatically
when coding is complete. This means the control module will be switched off and then on again auto-
matically. Otherwise, the user must reset the control module manually when coding is complete. To do
this, turn the ignition key once to the "Off" position and then back to the previous position.
UDS only: if nothing was entered in the Check sum field, a warning message will appear:
Figure 7.40 Note about missing check sum for binary code
Yes: programs the code string into the control module.
No: the code string is not programmed.
If a check sum was entered that does not match the code string, the following message appears:
Figure 7.41 Note about incorrect check sum for binary code
Yes: programs the code string into the control module anyway.
No: the code string is not programmed.
If the coding was successful, another message appears:
Figure 7.42 Confirmation message after coding
The new parameters are now displayed in the table.

If there is an error, the user will be notified with an error message stating why the code could not be
saved. The message depends on the error that occurred. For example, it could indicate that vehicle com-
munication could not be established.
The coding process can be performed again after correcting the problem.
Cross-reference:
Refer to the chapter Error Messages.
If the code is successful and the control module was not reset automatically, the user will be prompted
to reset the control module manually after confirming the message:
Figure 7.43 Prompt to reset the ignition
To do this, the ignition key must be in the "Off" position and then turned back to the previous position.
In UDS control modules that support the function, the user can click the plain text button to switch to
the view for plain text coding. Changes that were already made in the binary view are not transferred
here. In this case, the user will be informed with a message:
Figure 7.44 Warning when changing to plain text coding
Yes: changes to plain text coding. Any changes made in binary view will be discarded.
No: does not change to plain text coding. Changes made in the binary view will remain.
Once the code is saved with no errors, the Restore button is activated. Clicking this button will restore
the last code that was used. To program the restored code into the control module, click the Transfer
button.
Plain text coding.
When changing to plain text coding, the current code string is read from the control module and sepa-
rated into its individual parameters. These are displayed with the name and read value in the table.
Figure 7.45 UDS plain text coding
The table has three columns:
Parameter name: the name of the parameter in the code string.
Current value: the current code value.
Input: the user input.
It is also possible to filter the parameters.
Filter: if a text or a partial text is entered in the filter field, then only those parameters that contain the
name of this text or partial text will be displayed.
There are three buttons below the table:

Transfer: programs the changed code string into the control module.
Restore: restores the last code that was used.
Binary coding: changes to the binary coding view.
To change the value of a parameter, the user must click the input column in the desired parameter line.
The value can then be selected from a selection list.
With this code type, it is not necessary to enter a check sum because only codes that come from the data
and are therefore valid can be selected.
Click the Transfer button to start the coding process. Except for checking with the check sum, the
process runs the same way as with binary coding. Refer to that section for more information.
The Code function may not be supported by all control modules. If so, a notice appears.
Figure 7.46 The coding function is not supported
7.4.3.3 Technical Notes (Support Information)
Not contained in the user manual.
MCD Jobs for Coding UDS Control Modules:
 Standard ECU Coding Read (StandECUCodinRead)

 Standard ECU Coding Write (StandECUCodinWrite)
 Subsystem Coding Read (SinglJob_SubsyCodinRead)
 Subsystem Coding Write (SinglJob_SubsyCodinWrite)
Algorithm for Calculating the Check Sum for UDS Binary Coding:
Divide code string into 2-byte groups (short int values). If there is an uneven number of bytes, supple-
ment with 00 for the calculation. Add all short int values and round off if necessary.
Example:
Code string: F0 01 02 04 08 10 20
F001 +
0204 +
0810 +
2000
11A15 & 0xFFFF = 1A15
7.4.4 Coding subsystems

With the coding sub-systems function, the code status of sub-systems can be changed.
Figure 7.47 Coding subsystems
The meaning of the “Specification”, “Actual”, and "Control Module” columns can be found in the chap-
ter Coding Bus Master.
Reference:
Also refer to the chapter Coding Bus Master.
The respective bus for a control module is displayed in the bus system column.
Accept: the selected specified components will be written.

Figure 7.48 Security prompt before accepting the coding
If the coding process was completely successfully, the coding will be read from the control module again
and displayed. Otherwise, an error dialog will appear.
Code automatically: the code based on the subsystem components list detected from the control module
is written, meaning the code is written for all control modules that are marked with the symbols and
under "Current installation".
If the coding takes a while, a dialog with a message indicating that the coding process is running will
appear.
If errors occur during the coding process, the process is canceled and an error message appears. If the
coding process was completely successfully, the coding will be read from the control module again and
displayed.
Restore: restores the status that was present when the view was opened. The button can only be selected
if the current installation differs from the original starting installation.
If the process takes a while, a dialog with a message indicating that the coding process is running will
appear.
Figure 7.52 Progress bars during the restoration
If there is an error, an error message will appear. After the coding process ends, the coding will be read
from the control module again and displayed.
Update: the current installation will be read out again and displayed.
If the process takes a while, a dialog with a message indicating that the update is running will appear.
Figure 7.53 Progress bars during the update
7.4.5 Coding software compositions

Software compositions for a master control module can be coded using a separate view. The current
coding is shown initially.
Figure 7.54 Coding software compositions
The software compositions are shown in the upper area. Their current specified components can be
changed. The status of the actual installation can be ✔(coded) and ? (not coded). The Control Module
column contains the address in hexadecimal format (list number) and the system name, separated by a
“-”. The bus system column is not populated.
The system names for the software components in the selected software composition are displayed in
the lower table.
Accept: the selected specified components will be written.
Figure 7.57 Error when coding software compositions (example)
If the coding process was completely successfully, the coding will be read from the control module again
and displayed.
Code automatically: saves all software compositions as coded.

If the coding takes a while, a dialog with a message indicating that the coding process is running will
appear.
If errors occur during the coding process, the process is canceled and an error message appears. If the
coding process was completely successfully, the coding will be read from the control module again and
displayed.
Restore: restores the status that was present when the view was opened. This button can only be selected
if the specified installation is changed.
If the process takes a while, a dialog with a message indicating that the coding process is running will
appear.
Figure 7.60 Progress bars during the restoration
If there is an error, an error message will appear. After the coding process ends, the coding will be read
from the control module again and displayed.
Update: reads the current coding statuses.
If the process takes a while, a dialog with a message indicating that the update is running will appear.
Figure 7.61 Progress bars during the update
7.4.6 DTC Memory

The DTC memory function reads the current DTC memory content for a control module. It also offers
the option of erasing the DTC memory.
Figure 7.62 KWP DTC memory
The content of the DTC memory is displayed in tables arranged one over the other. The upper table
lists all of the events read from the selected control module. The table has four columns:
Fault Code: the code number of the fault.

SAE Code: the code number of the fault in SAE format.
Fault Text: the description of the fault.
Active: indicates if the fault is active or not.
Clicking on the event line displays the environmental conditions in the lower table . Additional
information, such as mileage, date, fault status etc. as well as the number and type can vary from
control module to control module. The table contains two columns:
Type/Name: the type of information.
Value: the value that was read.
There may be a + in front of the name. This indicates that there is detailed information that can be
displayed by clicking the +. If the group is opened, there will be a - in front of the main entry. Clicking
on this symbol hides the group again.
To the right near the table there are three areas for additional functions:
Update : pressing the Now button reads the DTC memory again. Activating the In cycle checkbox
causes the DTC memory to be read in cycles. The input field below specifies the cycle time. If the cycle
time is changed, the Now button must be clicked again to accept the new cycle time.
Sort : criteria can be entered here for sorting the DTC memory entries in the upper table. Clicking
on the column headers in the upper table reverses the sorting order (ascending/descending). The
default sorting is ascending based on priority and the time when the fault occurred:
Figure 7.63 Sorting the DTC memory entries

Delete : clicking on DTC memory or using the Delete button erases the contents of the DTC memory
in the selected control module. A confirmation dialog follows. Confirming with the Yes button erases
the DTC memory. Entering No cancels the procedure.
On some control modules, it is possible to erase not only the DTC memory of the control modules itself,
but the DTC memories of all OBD control modules connected. In this case the OBD systems screen
button is activated. A warning message appears when it is confirmed. If this is confirmed with Continue,
then the DTC memory in all OBD control modules are erased. Cancel closes the dialog without any
additional action.
If no control module responds to the request to delete the DTC memory after clicking the OBD systems
button, a warning message will appear.

Notice:
After erasing the DTC memory, it is read again immediately and the content is displayed. If the DTC
memory is not empty and it contains all or some of the faults that were displayed before deleting, the
control module did not accept the erase command or that fault was entered again immediately because
the cause was not corrected.
Erased DTCs CANNOT be recovered.
Figure 7.64 UDS DTC Memory
With UDS control modules, another table with information about the event status is displayed to
the right of the ambient conditions table
Name: name of the status bit.
Value: value of the status bit.
Show snapshots : by activating the DTC snapshots checkbox, snapshots for the selected entry in
table will be displayed in table , below the ambient conditions and measured values. The check-
box is deactivated if snapshots are not supported by the active control module.
Note:
With special control module types, the display of the control module information in the upper left header
area may differ from the content shown here. Also, the snapshot data cannot be read out separately for
these control modules. It will always be read out and displayed together with the DTC memories and
environmental conditions. In this case, the DTC snapshots checkbox will be hidden automatically in
the display because it has no function.
7.4.7 Basic Setting

The basic setting configuration and the displayed measured values differ depending on whether the
function was carried out on control modules with KWP or UDS protocol.
7.4.7.1 Basic Setting on KWP Control Modules
The following information explains the steps for completing the Basic setting function on a KWP con-
trol module.
After selecting the function versions and confirming with OK, the basic setting view is displayed.
Figure 7.66 KWP Basic Setting
The desired setting channel must be entered in the input field by clicking on the Select channel
screen button or using the enter key.
KWP1281 has channels 0 through 255, KWP2000 has channels 1 through 254. A validity test is not
performed while entering. If the value entered is outside of the valid value range, the entry field turns
red and the Select channel screen button is deactivated.
In the first list , all measurements are listed that are available for the selected channel if the control
module is not in basic setting.
Value: the value reported by the control module.
Click the Activate button to start the setting process. All measurements are processed one after the other
and shown in the lower list .
The setting process stops if a different channel is selected or the view is closed while the function is
running. The same applies if the button next to the list is clicked.
Some basic setting procedures require action from the user. If this is the case, the required action is
shown in the list for the current active measured value. The setting process continues automatically
once the action is performed.
The result appears in the Status field when the basic setting is completed.
Example:
The required action "Press accelerator pedal" is displayed as the measured value. If the user completes
this action, this text will disappear from the measured value table and the setting process will continue.
After the basic setting is completed, the new measurements are displayed in the list . If the basic
setting was not successful, a dialog appears with an error message that the user must confirm. The mes-
sage depends on the error that occurred. For example, it could indicate that vehicle communication could
not be established. The basic setting process can be performed again after correcting the problem.
Cross-reference:
Also refer to the chapter Error Messages.
7.4.7.2 Basic Setting on UDS Control Modules
With UDS control modules, additional parameters can be set and measured values can be selected after
selecting the basic settings. The following steps are required:
1. Basic settings selection

2. Setting basic setting parameters
3. Selecting measured values
4. Performing the basic setting
The following information describes the individual steps in detail.
Basic settings selection

Figure 7.67 UDS basic setting - basic setting selection
In the first view of the function, the desired basic settings must be selected. The available basic settings
are displayed in the list on the left . The selected tests will appear in the list on the right side ,
which is empty at the beginning.
Filter: if a text or a partial text is entered in the filter field, then only those basic settings that contain
the name of this text or partial text will be displayed.
Moves the selected basic settings from left list to the right list.
Moves all basic settings to the right list.
Moves the selected basic settings from right list to the left list.
Moves all basic settings to the left list.
The list of selected basic settings can be sorted. To do this, a specific basic setting must be selected
in the right list.
Moves the entry up one position.

Moves the entry down one position.
Switches to the next view, Setting parameters.
If a parameterization or measurement selection is not necessary, you can change directly to per-
form basic setting with this screen button.
Setting parameters
Figure 7.68 UDS basic setting - setting parameters
Default Parameters: press this button to set all parameters back to their standard values. The system
then checks for missing or invalid values and marks the affected parameters and basic settings.
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 . De-
pending 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 parameter is marked in red and the associated
basic setting is displayed in bold red font.
Cross-reference:
Refer to the illustration of parameter problems in the chapter Output Diagnostic Test Mode.
Switches to the next view, Measured Value Selection. As long as there are problems with the
parameters that were set, meaning at least one parameter is marked in red, an error message will appear
when clicking the button. You can only switch to the next view once all parameters have valid values
and there are no more red markings.
Switches back to the previous view. Even if basic settings were added or removed there, all of the
affected settings remain the same for the remaining basic settings.
Cross-reference:
Measured value selection
Figure 7.69 UDS basic setting - measured value selection
Name: the name of the measured value.
Selection: the name of the selected measured values.
In this view, measured values that will be displayed during the process can be selected for each basic
setting.
The available measured values are shown on the left side . 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.
Moves the selected measured values from the left list to the right list.
Moves all measured values to the right list.
Moves the selected measured values from the right list to the left list.
Moves all measured values to the left list.
Filter: if a text or a partial text is entered in the filter field, then only those measurements that contain
the name of this text or partial text will be displayed.
The list of selected measured values can be sorted. To do this, a specific measured value must be
selected in the right list.
Moves the entry up one position.
Moves the entry down one position.
Changes to Performing Basic Settings.
Switches back to the previous view. Even if the parameters are changed or basic settings are added
or removed there, the measured value selection remains for the other basic settings.
Performing Basic Settings

Figure 7.70 UDS basic setting - performing
Name: name of the basic setting, parameter, measured value, or measured value group.
Status: the current status of the basic setting.
Result: the current result of the basic setting.
Value: the values of the parameter and measured values or an error message that occurs when starting
and stopping the basic setting.
The basic setting for the control module is performed in this view. The basic settings including the
associated parameter values and any additional status measured values are display at the top in a list
.
The measured values that apply for all basic settings are shown in the lower list .
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 + opens the group and displays the meas-
ured values. Clicking on the - that is now in front of the group will hide the group again.
The status of the currently selected basic setting 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.
Start: starts performing the basic setting.
Stop: stops the basic setting.

Stop all: stops all active basic settings.
Next: switches to the next basic setting.
Switches back to setting the parameters. This stops the basic setting. This also applies when the
tab is closed or exited. It does not start again automatically when the user returns to the Performing
Basic Setting view. It must be started again manually.
Switches back to the basic setting selection. This stops the basic setting.
If you clicked Next to go to the next basic setting, then clicking on Start starts the basic setting selected.
If it is ended, 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 measured values for the basic setting that is cur-
rently running are shown and all others are hidden.
The Start screen button is deactivated and is grayed out. Clicking on Stop stops the basic setting. Click
Next to continue. The system will begin with the basic setting that is currently selected, regardless of
where the procedure 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.
Cross-reference:
Some settings can also be made using keyboard shortcuts. Refer to the chapter Using the Keyboard.
The new measured values that were set are displayed once the basic setting is complete. If the basic
setting was not successful, a dialog appears with an error message that the user must confirm. The mes-
sage depends on the error that occurred. For example, it could indicate that vehicle communication could
not be established. The basic setting process can be performed again after correcting the problem.
Cross-reference:
The result appears in the Status field when the basic setting is completed.
The Basic setting function may not be supported by all control modules. If so, a notice appears.
Figure 7.71 The basic setting function is not supported
After starting the OBD function basic setting a check takes place if the diagnostic access uses a diag-
nostic remote access. In this case, a warning message is displayed that should raise awareness.
Figure 7.72 Remote access warning
Note:
Diagnostic remote access will be used if the VCI currently being used is using a WLAN_AC-
CESSPOINT or WLAN_INFRASTRUCTURE connection type, or if the VCI is a DoIP VCI.
7.4.8 Identification
The Identification OBD function is used to read various fixed values from the control module such as
part number, software version, etc. These values can only be displayed. They cannot be changed.
Figure 7.73 Results window for OBD identification
In the example here, the gateway control module was selected and the identification was performed.
The upper table has three columns that contain information read from the control module.
System identification: the name of the control module.
Part number: the control module's unique part number.
Software version: the current software version.
The main control module that is being addressed is displayed in the top line of the tab. The other lines -
if applicable - contain additional supporting control modules that are reached through the main control
module. In the example above, it is the “Multifunction steering wheel” subsystem with the IDE
“E221__MFL-DC1”. If the main control module that is being addressed also supports software clusters,
these will also be detected and listed in the lines that follow. The detection of software cluster identifi-
cation takes place through a separate control module connection. If present, software compositions with
any software components will also be displayed.
The entry must be marked in the upper table for additional identification characteristics.
In the lower table , the user can switch between standard identification characteristics and the ex-
panded identification characteristics for the systems selected above. Use the Display expanded identi-
fication screen button. If this was confirmed, then the expanded identification is displayed and the
screen button changes to Display default identification. The standard identification is displayed auto-
matically after selecting an entry in the upper table.
This button is deactivated for KWP1281 control modules, subsystems, software compositions including
software components and software clusters, and control modules that belong to a vehicle project that
contains Daimler control modules.
The maintenance history data in the control module can be erased on control modules with KWP200
light plus and Service 0x22. An “Delete maintenance history data” button is displayed for this purpose.
It is only visible and active when the expanded identification is displayed.
The Filter entry field is active when the expanded identification is displayed. The attributes can be
filtered here. If a text or partial text is entered, only the attributes that contain that text or partial text in
their names are displayed.
For UDS control modules, two buttons are displayed on the right side at the bottom, with which all the
attributes of the expanded identification can be opened or closed. Both of these buttons can only be used
in the “Expanded identification” view.
Opens all attributes for the expanded identification
Closes all attributes for the expanded identification
Using the Update button reads the identification data again.
Note:
With special control module types, the number of columns and the properties displayed may differ from
the content shown here. Accordingly, there may be different column and attribute labels with these
control modules.
7.4.9 Measured Values

The top left indicates the control module that was selected. The example shows the electronic central
electrical system control module. The Measured values tab has two views: one for configuring the
measured values to be recorded (see the upper illustration) and one to display the measurement results.
After compiling the measured values to be displayed in the first view as shown in the upper illustration,
click the Show measured values button to enter the measured value display.
The configuration of the measurements to be displayed differs only slightly between control modules
with KWP and control modules with UDS protocol.
First, the measured values to be read must be selected:

Figure 7.74 Measured value selection
For control modules with KWP protocol, measured value blocks with up to four measured values are
read. The measured value block number (1 through 254) and, if necessary, the measured value position
within the affected block (separated by a period) are entered in the Block.Position input field. The Ac-
cept button is active after completing the entry. If a block number is entered that is outside of the range
of valid values, Transfer remains deactivated.
Clicking Transfer transfers the input into the right list where the selected measured values are
located. If only the block number is entered, all four measured values for this block will be displayed
when you click the Transfer button. By entering additional measured values, any four measured values
from various blocks can be configured for display.
Example:
Input: 8 Transfer Transferred selection: 8.1, 8.2, 8.3, 8.4
All measured value blocks are transferred.
Input: 1.2 Transfer Transferred selection: 1.2
Only the measured value in the selected position is transferred.
The buttons for moving blocks become active when you click on the desired measured value block in
either list.
Moves the selected measured value blocks to the left list .
Moves the selected measured value blocks to the right list .
Moves all measured values blocks to the left list.
Moves all measured value blocks to the right list.
The list of selected measured value blocks can be sorted.
Moves the selected entry up one position.
Moves the selected entry down one position.
These buttons are used the same way with UDS control modules once the measured value name is se-
lected as described above.
After all measurements were selected, clicking on the screen button or using the enter key changes
the view to Display measurements.
Figure 7.75 KWP - Measured value display

UDS control modules group the measurements. Clicking on the + opens and clicking on - closes. By
default, all groups are open.
The measured values update can be controlled using the controls in the Update area. The default setting
is updating the measured values in cycles as quickly as possible. When a measurement is selected, using
the enter key performs the same action.
You can set the desired update interval in the input field. You can switch the update cycle off by remov-
ing the check mark in the "cycle" checkbox. When it is not selected, you can update the measured values
as desired using the Now button.
Using the button or using the ESC key takes you back to the first view and you can change the
selection of the measurements to be displayed.
Note:
area may differ from the content shown here.
The Measured values function may not be supported by all control modules. If so, a notice appears.
Figure 7.76 The measured values function is not supported
7.4.10 Output Diagnostic Test Mode

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.
7.4.10.1 Output Diagnostic Test Mode on KWP Control Modules
After selecting the function versions and confirming with OK, the output diagnostic test mode view
is shown.
Figure 7.78 KWP Output Diagnostic Test Mode
You can select between selective and sequential output diagnostic test mode for control modules with
the KWP protocol. The default selection is sequential. Not all diagnosis types are supported, depending
on the control module. The buttons are deactivated if this is the case.
Start: starts the output diagnostic test mode.

Next: switches to the next actuator (not supported by all control modules).
Stop: stops output diagnostic test mode.
When the user selects selective output diagnostic test mode, then a numeric actuator code is to be
entered in the field next to it. If the actuator code is missing or is invalid, the field stays red. The value
range is 0 - 65535 (decimal) or 0x0000 - 0xFFFF (hexadecimal).
First, if one of the two options was selected - and the control module supports this - the Start screen
button is activated. Clicking this button starts output diagnostic test mode.
Selective output diagnostic test mode
Output diagnostic test mode starts and the actuator code input field is locked until the function ends or
is canceled.
Sequential output diagnostic test mode
After starting diagnosis on the first actuator, the buttons Start and the actuator code input field are
deactivated until the function ends or the user cancels it using the Stop button.
Some control modules allow diagnosis to continue on the following actuator while the function is run-
ning. If this is the case, the Next button is activated while the function is running. Clicking this button
stops diagnosis on the current actuator and starts with the next one.
In control modules that use the KWP 2000 protocol, the measured values are read from the control
module in cycles in addition to the diagnostic status. A selection is not possible. The control module
specifies which measured values are displayed.
If output diagnostic test mode ends, the results are displayed in the Output diagnostic test mode -
status field.
Figure 7.79 Output Diagnostic Test Mode Status
If addition measured values were read from the control module, they are displayed in the Measured
values table.
Cross-reference:
7.4.10.2 Output Diagnostic Test Mode on UDS Control Modules
Output diagnostic test mode can be figured more extensively in control modules with the UDS protocol.
After selecting the output diagnostic test mode function for a UDS control module, the user then enters
the Actuator selection view (refer to Figure 7.80 UDS actuator selection). This contains a list of avail-
able control module actuators whose individual parameters can be set. The selected and configured ac-
tuator 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 parameters. It is not possible to add or set
parameters for individual actuators when output diagnostic test mode is running.
The following information describes the four phases of output diagnostic test mode for UDS control
modules in detail.
Actuator selection
Figure 7.80 UDS actuator selection

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 empty at the beginning.
One or more actuators can be selected by clicking or using 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.
The actuators can be filtered in the Filter entry field. If a text or partial text is entered, only the actuators
whose names contain this text or partial text are displayed.
Cross-reference:
For additional information on using the keyboard, refer to the chapter Using the Keyboard.
When you click an actuator in either of the lists, the buttons to move that actuator become active.
Moves the selected actuator to the left list .
Moves the selected actuator to the right list .
Moves all actuators to the left list.
Moves all actuators to the right list.
The list of selected actuators can be sorted.
Switches to the next view, Setting parameters.
If a parameterization is not needed, click on this screen button to change to Performing Output
Diagnostic Test Mode.
Setting parameters
Figure 7.81 Setting UDS actuator parameters
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 marked in red and the associated actuator is displayed
in bold red font.
Figure 7.82 UDS output diagnostic test mode - problems with setting parameters
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.
Switches to the next view, Measured Value Selection. 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. You can only switch
to the next view once all parameters have valid values and there are no more red markings.
Switches back to the previous view. Even if actuators were added or removed there, all of the
affected settings remain the same for the remaining actuators.
Cross-reference:
Measured value selection

Figure 7.83 UDS Measured Value Selection
Selection: the name of the selected measured values.
In this view, measured values that will be displayed during the process can be selected for each actuator.
The measured values available for the selected actuator appear in the left list . The measured values
to be displayed can be selected here the same way actuators are selected. The selected measured values
will appear in the list on the right side , which is empty at the beginning.
The measurements can be filtered in the Filter entry field. If a text or a partial text is entered, then only
the measurements are displayed that contain the name of the text or partial text.
When you click on a measured value in either of the lists, the buttons to move that actuator become
active.
Moves the selected measured values to the left list .
Moves the selected measured values to the right list .
Moves all measured values to the left list.

Moves all measured values to the right list.
The list of selected measured values can be sorted.
Cross-reference:
The measured values can also be selected with the keyboard. Information on using the keyboard can be
found in the chapter Using the Keyboard.
Changes to Performing Output Diagnostic Test Mode.
Switches back to the previous view. Even if the parameters are changed or actuators are added or
removed there, the measured value selection remains for the other actuators.
Performing Output Diagnostic Test Mode
Figure 7.84 UDS Output Diagnostic Test Mode
Name: name of the actuator, parameter, measured value, or measured value group.
Value: the values of the parameters and measured values or an error message that occurs when starting
and stopping the output diagnostic test mode.
The actual output diagnostic test mode is performed in this view. The selected actuators included ac-
tuator status (if available) and the associated parameter values are shown at the top in a tree structure
. The parameter values are shown collapsed by default. Clicking on + expands the measured values.
The actuator parameters and their values are also shown when the mouse cursor is placed over the actu-
ator.
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 + opens the group and displays the meas-
ured values. Clicking on the - that is now in front of the group will hide the group again.
The overall status of all selected actuator tests displayed in the Output diagnostic test mode - status
field above both tree structures. Possible status messages 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 actuators.
Start: starts the actuator test.
Stop: stops the actuator test.
Stop all: stops all active actuator tests.
Next Switches to the next actuator.
Switches to the previous view. All actuator tests stop. This also applies when the tab is closed. The
actuator test does not start again automatically when the user returns to the Performing output diag-
nostic test mode view. It must be started again manually.
Changes back to actuator selection. The actuator test is stopped.

Note:
Figure 7.85 Example of an actuator test on several actuators
The Start and Stop buttons are only for the currently selected actuator test.
For example, if the user chooses the actuators through before starting, these tests are started by
pressing the Start button. If the selection is reduced to actuators and and the Stop button is
pressed, only the actuators and are stopped and actuator continues to run. Actuators can be
started and stopped at any time independently of each other.
Using the Next button, a sequential actuator test sequential actuator test can be performed on a UDS
control module. There must not be any other active actuator tests. An actuator must also be selected
from the list on the left. If both conditions are met, the button will be activated.
Clicking on Next switches to the next actuator and clicking on Start starts the test for the actuators. If
the end of the list is reached, clicking Next will move to the first entry in the list. The measured values
for the actuator test that is currently running are shown.
Clicking Stop stops the actuator test that is currently running. The sequential actuator test can be con-
tinued using Next or Start. The system will begin with the actuator that is currently selected, regardless
of where the test was stopped.
Cross-reference:
The Output diagnostic test mode function may not be supported by all control modules. If so, a notice
appears.
Figure 7.86 The output diagnostic test mode function is not supported
After starting the output diagnostic test mode OBD function, a check takes place if the diagnostic access
uses a diagnostic remote access. In this case, a warning message is displayed that should raise awareness.
Figure 7.87 Remote access warning
Note:
Diagnostic remote access will be used if the VCI currently being used is using a WLAN_AC-
CESSPOINT or WLAN_INFRASTRUCTURE connection type, or if the VCI is a DoIP VCI.
Note:
area may differ from the content shown here, which does not contain any identification values but rather
only the diagnostic or transport log. Furthermore, the performance view for these types of control mod-
ules does not contain any general or actuator-specific status display.
7.4.11 Access Authorization

To perform access authorization, a dialog opens. The content of the dialog differs with each protocol.
As long as the control module supports the SFD activation (vehicle diagnostic protection) with online
tokens, a dialog for SFD activation is automatically displayed.
It appears automatically when access authorization is required in a different OBD function.
7.4.11.1 Access Authorization via Login Methods
Figure 7.88 Access Authorization
Login methods: the type of access authorization to be performed is selected here.
Control modules with KWP1281 protocol have only automatic access authorization.
Control modules with KWP 2000 protocol have the following possibilities to perform the access au-
thorization.
 Automatic access authorization

 Access authorization level 3/4
 Access authorization level 5/6
Control modules with UDS protocol have different methods for access authorization depending on the
data.
Login code: enter the access code in this field. By default, the password is masked over with *. As long
as the field is empty, it remains red and the Perform screen button is deactivated.
Display login code: selecting this option displays the password in the login code in plain text.
Perform: performs the access authorization with the selected login method.
Cancel: cancels the dialog without issuing an access authorization.
In the Information area at the top of the dialog, the control module, for which the access authorization
is being performed, is displayed. If a dialog was opened from another OBD function, the NRC sent by
the control module is displayed in addition to information about the function to be called up.
In order to perform access authorization, select the login method and enter the password in the login
code field. Clicking on Perform begins issuing the access authorization.
If the access authorization was performed successfully, a message appears that closes automatically after
a few seconds.
Figure 7.89 Access authorization - successful
In the case of an error or if the access authorization was interrupted, a message appears.
Figure 7.90 Access authorization - unsuccessful
If the selected control module does not support the "Access authorization" diagnostic function, the user
will be informed of this in a window when the function is selected. This is the case especially for Daimler
control modules. Access authorization is always declined for these control modules.
Figure 7.91 Access authorization is not supported.

7.4.11.2 Access Authorization via Online Tokens (SFD Activation)
Figure 7.92 Access authorization with online tokens
Activation information: the current SFD activation information from the current control module is
displayed here.
Configure function: you can select between online activation and manual SFD activation here.
Lock control module: removes the SFD activation for the current control module. This button is only
activated when enabled.
Perform: performs the SFD activation with the “BASIC” role and “short (90 min)” activation duration
via online token or manual activation.
End: ends the dialog without issuing an access authorization.
In the Information area at the top of the dialog, the control module, for which the access authorization
is being performed, is displayed. If a dialog was opened from another OBD function, the NRC sent by
the control module is displayed in addition to information about the function to be called up.
To perform access authorization with online tokens, the “Online activation” use case must be selected
and the Perform button must be pressed. If there is currently no valid login to the group systems, a login
dialog will appear for logging in. It may be the DSS login dialog or the GRP login dialog.
For devices without an Internet connection, the “Manual SFT activation” use case is available. If this is
active when the Perform button is pressed, the dialog window for checking if there is already an acti-
vation token will open.
Figure 7.93 Check for available SFD activation tokens
If there is no activation token available, a dialog will open when the Next button is pressed that will
prepare an activation request structure that is suitable for the control module. With this structure, a valid
token for activating the control module can be generated in the SFT IT backend.
Figure 7.94 Preparation of SFT activation request structure for manual SFD activation
If an activation token has already been generated, a dialog where the available token should be entered
will open when the Next button is pressed. Once the token is entered, the activation can be started by
pressing the Activate control module button.
Figure 7.95 Entering the activation token for manual SFD activation
If the user attempts to apply invalid token data either by entering it from a file or from the clipboard, an
error dialog will open.
Figure 7-96 Error dialog when loading invalid token data from a file
Figure 7-97 Error dialog when there is invalid token data in the clipboard
If the access dialog is called up manually using the function list, the dialog will remain open after acti-
vating and it will update the activation information. In this case, the dialog can be closed using the End
button.
If the access dialog is automatically called up due to missing access authorization, the access dialog will
be closed and then a follow-up message or error message will be displayed for a few seconds.
Figure 7.98 Access authorization - successful
Figure 7.99Access authorization - unsuccessful

7.4.12 Data Upload
The data upload OBD function is used to transfer data sets from UDS control modules to the local
tester. Control modules with KWP diagnostic protocol are not supported.
Figure 7.100 Results window for OBD data upload
The data sets that are available on the current control module are listed in the upper table display .
The individual data sets are selected using the selection boxes in the Upload column. All data sets can
be deselected or selected at once using the selection box in the column header.
The table has five columns:
Data block address: the address of the data set.
Data block version: the version of the data set.
Data block name: the name of the data set.
Free text: user-defined text added to the file name.
Upload: selection of the data set for an upload.
This user-defined free 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 per-
mitted that do not exceed the maximum length of 80 characters. When there is a blank free text field,
the current time stamp with the "yyyyMMddTHHmmss” format is automatically used as free text.
The lower file list shows the data sets that are already saved locally with the *.bin file ending, which
are contained in the selected storage directory. The path to the storage directory is displayed under Save
in. The storage directory is configured using the Search… button, but remains the same for the duration
of the results tab.
The file names of the data sets being transmitted are composed as follows:
DU_<control module address>_<data set ID>_<VIN>_<data set version>_<data set name>_<free text>.bin
The following actions can be performed in this OBD function:
Data set upload: upload the selected data sets.
Search…: opens a selection dialog for the storage directory.
Display…: opens the storage directory with the Windows file explorer.
When you start the data transfer using the Data set upload button, the requirements will be checked
first. If any requirements are not met, the upload process will not begin. The detail dialog contains the
data sets in the format “<Data set ID> - <Data set name> (<Number of requirements>)” in the upper
list. If you press the Details >> button, the requirements that are not met will appear in the lower list for
the selected data set.
Figure 7.101 Detail dialog for all diagnostic requirements that are not met
Details<<: opens the lower list for displaying the requirements that are not met.
Next: checks the requirements again.
Cancel: cancels the entire upload process.

If there is already a data set in the local storage directory with an identical file name, you can choose to
overwrite, rename the local file automatically, or cancel the entire upload process.
Figure 7.102 Selection dialog when there are existing local data sets
Overwrite: overwrites the local file set.
Rename: automatically changes the local data set name.
Cancel: cancels the entire upload process.
After transferring successfully, the lower file list will be updated. If problems occur during the
transfer, they will be collected and displayed in a detail dialog at the end.
7.4.13 Multiple identification data

The “Multiple identification data” OBD function enable simultaneous detection of up to 8 identification
data items using a single diagnostic request. The Multiple identification data tab has two views: one
for configuring the identifications to be recorded (see the first image) and one to display the identifica-
tion results (see the second image). After compiling the identifications to be displayed in the first view,
the detection and display of results occurs in the second view.
First, the identifications to be read out must be selected:

Figure 7.103 Identification selection
The identification values are selected using the buttons in the center of the view. The selected identifi-
cation values are moved into the right table when they are selected from the left table and vice versa
when a selection is cleared. All values can be moved at once using the or buttons. If all values
have already been moved, then the respective button will be inactive. Once at least one of the identifi-
cation values in a table in selected, you can use the or button to move the selected value between
the available and the selected table. Multiple items can be selected using the Shift/Ctrl key.
Example:
Input: Distance Transfer Transferred selection: distance
The buttons for moving become active when you click on the desired identification name in either list.
Moves the selected identification to the left list .
Moves the selected identification to the right list .
Moves all identifications to the left list.
Moves all identifications to the right list.
The list of selected identifications can be sorted:

After all identifications have been selected, clicking on the button or using the enter key changes
the view to Display multiple identification data.
Figure 7.104 Multiple identification data display
Name: block number or name of the identification.
The multiple identification data is collected in blocks with eight identifications each. Clicking on the +
opens and clicking on - closes. By default, all blocks and subordinate identification groups are collapsed.
The identifications can be updated by clicking the now button in the Update area.
The button returns to the first view and you can change the selection of identification data to be
displayed.
The Multiple identification function may not be supported by all control modules. If so, a notice ap-
pears.
Figure 7.105 Multiple identification data function not supported
7.5 Vehicle-Specific Functions

The following describes the OBD functions, which do not apply to specific control modules, but rather
to the entire vehicle.
7.5.1 Complete System DTC Memory

The Complete system DTC memory function reads the DTC memory for all control modules installed
in the vehicle.
Figure 7.106 Complete System DTC Memory
The view consists of a table with two columns:
System: the control module diagnostic address followed by its name.
Fault: the number of faults that were read.
When changing the view, the table updates automatically, meaning it attempts to read the faults for
every control module that is installed.
If the control module DTC memory is empty, a 0 is displayed in green font in the same column. For
control modules that have entries in the DTC memory, the number of faults is displayed in red font in
the Fault column. A + also appears in front of the diagnostic address. If the user clicks on it, the faults
that are occurred are listed in detail. For additional information on a fault, click the + in front of the
fault.
If the DTC memory for a control module could not be read, the Fault column remains empty for this
control module.
The user has three possibilities to update the table: clicking on now, using CTRL + P, or checking
periodic.
In the first and second case, the table is updated one time. Clicking Cancel stops the update.
If the user decides to update in cycles, the table updates continuously according to the interval shown
in the text field below the option. The value is entered in seconds. An interval of 30 seconds is used by
default. If no value is entered, the last value entered is used. If the interval is smaller than the time needed
for the update, the reading will begin again immediately after the current reading cycle ends. The interval
can be changed during the update cycle. Use the Return key to confirm the new value. To end the update
cycle, clear the check mark next to the Cycle option. You can also update the table between cycles by
clicking the now button.
After all DTC memories are read, the Read DTC memory function can be selected for the affected
control module by double-clicking on a line in the table. For this to work, it must be possible to read the
control module DTC memory. The DTC memory content for the selected control module is displayed
in a new tab.
Cross-reference:
Refer to the chapter DTC Memory.
Once the DTC memory is read completely at least one time, the user has the option to erase the DTC
memory for the entire system. There are several ways of doing this that depend on the control module
or vehicle. For example, the DTC memories can be erased all at once or one after the other.
Figure 7.107 Selecting the method of erasing the DTC memory
To erase the DTC memory at once, select Complete system in the list in this example (preselected as
the default) and click the Perform button. A security prompt appears:
Figure 7.108 Warning message before erasing the DTC memory
Yes: the DTC memories for all control modules that support this function are erased.
No: the deleting process is not performed.

Once the deleting process has ended, a dialog lists any errors that may have occurred. If the process was
successful, there are no additional messages.
To erase the control module DTC memories one after another, select Individually from the list. The
security prompt mentioned above appears and the user must confirm it with Yes. The control module
DTC memories are then erased one after the other. The control module DTC memory is read again after
each deletion process and the results are displayed in the table.
Notice:
After erasing the DTC memory, it is read again immediately and the content is displayed. If the DTC
memory is not empty and it contains all or some of the faults that were displayed before deleting, the
control module did not accept the erase command or that fault was entered again immediately because
the cause was not corrected.
Erased DTCs CANNOT be recovered.
7.5.2 Transport Mode

The following dialog opens:
Figure 7.109 Transport Mode
Perform: performs the selected function.

Finish: closes the dialog.
Cancel: cancels the switch to transport mode.
To switch transport mode on or off individually, select the corresponding item in the list and click "Per-
form" to confirm. The result of the function (successful / not successful) is displayed in the information
area above the list:
Figure 7.110 Message indicating the switch to transport mode was successful
If an error occurs, a new message with detailed information about the error will appear:
Cross-reference:
Figure 7.111 Transport error
Depending on the type of error that occurred, an additional error message with detailed information may
also appear (for example, that a connection to the vehicle could not be established). After correcting the
problem, you can try switching to or from transport mode again.
If the selected vehicle project does not support the "Transport mode" diagnostic function, the user will
be informed of this in a window when the function is selected. This is especially the case with vehicle
projects that contain Daimler control modules.
Figure 7.112 Transport mode is not supported.
7.5.3 Components List

The Components list shows the vehicle's coded actual installation. The number of faults that have oc-
curred is also displayed for each control module, if applicable.
Figure 7.113 Components List
System: the control module diagnostic address followed by its name.
Bus system: the bus identifier and/or the protocol combination used for the affected control module is
displayed in this column, if available.
SB: sleep bit. Indicates if the vehicle bus is in standby mode.
Fault: the number of faults in the control module DTC memory.

Available subsystems and software compositions including software components and software clusters
will also be displayed. Control modules that have secondary control modules are marked with a +.
Clicking on it displays the next level of control modules. The first level is shown by default. The example
shows the diagnostic interface that serves as the primary control module to all of the other secondary
control modules.
Control modules in which faults have occurred are shown in red. The number of faults is also shown in
the "Fault" column.
Control modules that are coded as installed but could not be addressed are shown in bold, red font:
Figure 7.114 Display when there is faulty communication with a control module
The components list can be updated manually or in cycles. To update manually one time, click the now
button.
in the text field below the option. The value is entered in seconds. If the interval is smaller than the time
needed for the update, the reading will begin again immediately after the current reading cycle ends.
The interval can be changed during the update cycle. Use the Return key to confirm the new value. To
end the update cycle, clear the check mark next to the Cycle option. You can also update the table
between cycles by clicking the now button.
Note:
Special vehicle types do not contain a gateway control module or do not support a components list. In
these cases, the maximum equipment installation will be displayed instead of the components list. There
is also no sleep bit information in these cases, so the SB column is omitted.
In addition, with special control module types, the name displayed may differ and contain no identifica-
tion values, but rather only the diagnostic or transport protocol.
7.5.4 OBD
Different OBD services can be performed using OBD functions and the vehicle OBD functions are
checked.
This occurs in three steps:
The OBD function is selected

The OBD parameter is selected
Result display
The OBD functions are selected
Figure 7.115 The OBD function is selected
As soon as the list of OBD functions is selected, the is active.
Switches to the next view of the OBD parameter selection.
The OBD parameter is selected

Figure 7.116 The OBD parameter is selected
In this view, the Parameters belonging to the OBD function are selected, which are displayed when the
function is being performed.
The available parameters are shown in the left list . The selected parameters are shown in the right
list , which is empty at the beginning.
The actuators can be filtered in the Filter entry field. If a text or a partial text is entered, then only the
parameters are displayed that contain the name of the text or partial text.
Show all: by default only the parameters that are identified as being supported by the vehicle are shown.
If Show all is selected, then all parameters are shown. The unsupported parameters are shown in light
gray text.
When you click on a parameter in either of the lists, the buttons to move that actuator become active.
Moves the selected parameter to the left list .
Moves the selected parameters to the right list .
Moves all parameters to the left list.
Moves all parameters to the right list.

The list of selected parameters can be sorted.
Cross-reference:
The parameters can also be selected with the keyboard. Information on using the keyboard can be found
in the chapter Using the Keyboard.
Switches to the result display.
Switches back to the previous view.
OBD result display
Figure 7.117 OBD result display
The OBD function in this view. The results parameters are shown in a table in three columns:
Measurement name: the name of the OBD functionality or of the parameter.

Adr.: the control module diagnostic address that has sent the value.
The answers from the control modules are shown hierarchically structured, sorted by diagnostic address.
If a control module does not respond even though it supports the OBD function, this will be indicated
in the Value column with the text "no response from control module". The text also appears if an answer
is erroneous. These texts appear in red.
in the text field below the option. The value is entered in seconds. If the interval is smaller than the time
needed for the update, the reading will begin again immediately after the current reading cycle ends.
The interval can be changed during the update cycle. Use the Return key to confirm the new value. To
end the update cycle, clear the check mark next to the Cycle option. You can also update the table
between cycles by clicking the now button.
Switches to the previous view.
7.6 End OBD

OBD can be ended if the OBD functions are closed.
To end the OBD session, you must switch to the Control modules tab.
Figure 7.118 End OBD
Clicking this button begins the process of exiting the OBD. You must confirm the
prompt that follows.
Figure 7.119 Confirm end of OBD
Yes: OBD ends.
No: OBD does not end.
If, during OBD, result data were entered into the OBD log and they were not saved manually, then the
user has the possibility, to save the log. In this case, another inquiry appears:
Figure 7.120 Saving the OBD log
Yea: the OBD log is saved under the previously selected file name or under the file name configured in
the Admin area. OBD ends.
No: OBD ends and the protocol is discarded.
Offboard Diagnostic Information System Service then returns to the start page in the OBD mode.
8 Flash Mode
In addition to diagnosis, Offboard Diagnostic Information System Service also offers the ability to
flash.
The process used in Flashing mode is very similar to Diagnosis mode, but it is less comprehensive
overall. Guided Fault Finding and control module functionalities are not available in this mode.
Figure 8.1 Work Process in Flashing Mode
When entering the flashing process, the vehicle is connected to the tester and identified, login to the
group systems is completed, an order is selected for the session and the control modules are identified.
The flash programs determined for the vehicle can then be performed.
The flash session ends when the desired flash work is complete.
8.1 Starting Flashing

In the Starting flashing section, the vehicle is connected to the tester and flash entry begins.
Figure 8.2 Starting Flashing Section
Flashing is available after selecting Flashing mode.
The chapter Starting diagnosis describes the process of connecting the vehicle in detail.
Cross-reference:
For details on vehicle identification, refer to the chapter Connecting a Vehicle.
Notice:
For legal reasons, not every diagnostic connection, such as a Bluetooth connection, can be used for
flashing. If an unpermitted diagnostic connection is used for flashing,Offboard Diagnostic Infor-
mation System Service gives a warning message and requests the user to use a legally permitted con-
nection.
Continue: the flash entry is continued despite the request to connect a wired connection.
Cancel: the flash entry is canceled.
Reference:
For a detailed description on changing diagnostic hardware, refer to the chapter Diagnostic Interface.
The flash entry can begin once the vehicle is connected.

Figure 8.3 Flash entry start window
Click Start flashing to begin flash entry.
8.2 Identifying the Vehicle

The vehicle is identified once flash entry starts.
Figure 8.4 Identifying the Vehicle Section
Offboard Diagnostic Information System Service first tries to analyze the vehicle automatically.
Figure 8.5 Vehicle Analysis during Flash Entry
If the vehicle is recognized completely, meaning the VIN, brand, model and model year are clearly
recognized, vehicle identification will run completely automatically without displaying the vehicle fea-
tures dialog.
If the automatic vehicle identification fails, Offboard Diagnostic Information System Service dis-
plays a vehicle features dialog with entries for VIN, Manufacturer, Model and Model year.
Figure 8.6 Manual vehicle identification
The defining vehicle features can be selected manually in this dialog.
Transfer: the selected vehicle features are transferred and flash entry continues.
Cancel: vehicle identification is canceled.
Cross-reference:
For a detailed description of the basic information dialog, refer to the chapter Vehicle Features Dialog
(VFD).
When referring to that section, keep in mind that the vehicle features dialog is not as detailed for flash
entry.
You can switch between manual and automatic vehicle identification.

Figure 8.7 Automatic vehicle identification
For example, the VIN can be entered and then the identification, if necessary, can run automatically. In
automatic identification, the features with a gray background cannot be changed.
Transfer: the flash entry continues.
Cancel: vehicle identification is canceled.
Vehicle identification ends.
If the flashing was started with a Wi-Fi diagnostic interface, the system periodically checks during the
flash entry if there is another suitable Wi-Fi connection available. If this is not the case, a warning
message is displayed.
Figure 8.8 Warning message when the Wi-Fi connection quality is poor
8.3 Group Systems Login

The next section of the flash entry includes logging into the group systems.
Figure 8.9 Logging in to Group Systems section
Offboard Diagnostic Information System Service opens a login window in order to log in.
Figure 8.10 Group Systems Login Window

The login is required once per session. The global user ID and password for group systems access are
required to log in.
Transfer: the login data is sent to the group systems.
Cancel: the login data is discarded. Authorized dealers can repeat the login at any time.
This button is available in all views of Offboard Diagnostic Information System Service that
use data from the group systems. It can be used to log in again at any time.
Notice:
Offboard Diagnostic Information System Service makes Diagnosis and Flashing available only to
licensed brands.
You can check the license content in the Administration area:
Reference:
Refer also to the chapter License Information under Administration Mode.
An independent market operator must log in to the group systems at the beginning of a diagnostic
or flash session online.
If the login is interrupted, Offboard Diagnostic Information System Service will return to the start
screen.
After logging in successfully, Offboard Diagnostic Information System Service shows the remaining
period of validity for the flat rate in days and hours under Remaining run time in the Information area
of the application interface. Refer to Figure 5.3 The Info area.
The independent workshops do not have access to Work orders and History .
Cross-reference:
Also refer to the chapter Logging in to Group Systems.
8.4 Order Selection

After logging into group systems, an order is selected or created manually for the flash session.
Figure 8.11 Selecting an Order Section
If the login is successful, Offboard Diagnostic Information System Service accesses the order data
for the current vehicle from ElsaPro.
Figure 8.12 Selecting an Order for Flashing
Offboard Diagnostic Information System Service switches to the Orders tab and shows a list of all
available orders for the vehicle.
In the work order list, the work order number is displayed under Work order, the current status in the
service core process is displayed under SCP status, and the vehicle license plate number, the deadline
for the work order and descriptive text about the work order are also displayed.
The table that follows lists the meaning of the SCP status numbers.
1 Appointment scheduling
2 Appointment preparation
3 Vehicle drop-off
4 Services rendered
5 Quality control
6 Vehicle return
7 Finishing
8 Completed
Table 8.1 Meaning of the SCP status numbers
If an order from ElsaPro will be used, the desired order must be marked here.
Select order: clicking this button continues flash entry with the order from ElsaPro.
An order can also be added manually. Standard order for working with a manual order number is
selected in the list first.
Enter number...: clicking this button opens a window for entering the manual order number.
Select order: flash entry continues with the manual order.
No order: if you will be working without an order, click this button to continue flash entry.
Cross-reference:
Also refer to the chapter Selecting an Order.
This completes the order selection.

If Offboard Diagnostic Information System Service is configured in this way, then the control mod-
ules must now be identified. Otherwise the special functions tab opens. This tab displays the list of
flash programs that can be used for the vehicle.
8.5 Identifying Control Modules

The vehicle control modules are identified after selecting the order. This step is optional and it happens
only if Offboard Diagnostic Information System Service was configured this way.
Figure 8.13 Identifying Control Modules section
Offboard Diagnostic Information System Service shows a progress indicator for the control module
identification.
Figure 8.14 Control Module Identification
Cancel flash entry: the flash entry is canceled.
Once control module identification is complete, Offboard Diagnostic Information System Service
opens the Special functions tab and displays the flash programs that are available for the identified
vehicle in a table.
8.6 Working with Flash Programs

After identifying the control modules, flash programs can be run.
Figure 8.15 Running Flash Programs Section
Offboard Diagnostic Information System Service lists the available flash programs on the special
functions tab.
Figure 8.16 Available Flash Programs
Clicking the desire flash program marks it.
The test programs are grouped by theme.
Perform test...: the highlighted flash program is started. Offboard Diagnostic Information System
Service switches to the Operation tab.
Display documents: this button can be used to display associated documents, if available. Offboard
Diagnostic Information System Service then switches to Information mode, Documents tab.
The flash programs run the same way the GFF diagnostic programs run.
Cross-reference:
No other actions can be performed during flashing. The estimated time remaining until the process is
complete is displayed in the Operation tab.
Figure 8.17 Estimated time remaining in a flashing process
Flash sessions can be saved and then opened again and continued just like diagnostic sessions. The
application detects automatically if a diagnostic or flash session should be saved or resumed.
Cross-reference:
For detailed information on saving flash sessions, refer to the chapter Data.
8.7 Diagnostic Objects when Flashing

In addition to the flash programs, additional functions or GFF programs, which are relevant for the
vehicle, can appear in the special function tab. These can then be performed as the other tests.
In some cases, not all the basic features needed to perform the special function or GFF program, were
transmitted during the flash entry. If the basic features are missing, then the user will see a dialog when
performing such a test that allows the user to add the missing basic features.
Figure 8.18 Basic features manual selection
The model year, version and engine can always be accessed in this dialog. The dialog will not appear
if one of these criterion was already identified. The dialog will not appear if all the criteria were already
identified.
The special function or the GFF program for identifying the diagnostic objects needs more information
about the equipment network. If this is the case, a dialog is displayed where the user is requested to
complete any missing equipment characteristics. The control module can tell which version is installed,
or, if the control module is installed or not.
Figure 8.19 Manual control module selection
The following is an example of a dialog. Which available characteristics that are actually displayed
depends on the current equipment network and the on the diagnostic objects contained in the knowledge
base.
Using this information, the diagnostic objects determined as relevant for the vehicle and as the last
elements will appear in the special function tab.
The elements run the same way the GFF diagnostic programs run.
Cross-reference:
8.8 Ending Flashing

The flash session ends when the desired flash programs are complete.
Figure 8.20 Ending Flashing Section
To end the flash session, you must switch to the Flashing tab.
Figure 8.21 Ending the Flash Session

Clicking this button begins the process of exiting the flash session. You must confirm
the prompt that follows.
Figure 8.22 Ending the Flash Session
Yes: the flash session ends.
No: the flash session does not end.
If the flash session ends, the DTC memory for all control modules, including the OBD control modules,
is erased. If a new DTC memory check produced new or different results, Offboard Diagnostic Infor-
mation System Service asks if the flash sessions should be continued.
Figure 8.23 Erase DTC memory
Yes: the current flash session will be continue and the flash exit will be canceled.
No: the flash exit will continue.
Depending on the vehicle, end module programs may run here just as they do when exiting Guided Fault
Finding. It is also possible to send a feedback about a flash session. The feedback can also be skipped.
Offboard Diagnostic Information System Service then returns to the start page in the Flashing mode.
Cross-reference:
For detailed information on exiting Guided Fault Finding, refer to the chapter End Diagnosis.
9 General Diagnostic Entry

Regardless of the mode, a check for active diagnostic filters (also diagnostic firewall) is performed in
each diagnostic entry. An active diagnostic filter should prevent writing control module services from
running during normal vehicle operation. These services will only be permitted under certain circum-
stances, such as when the hood is open.
If there is an active diagnostic filter during diagnostic entry, the user will be notified of this using a
message that describes where the filter can be deactivated. The user can accept the message and then
continue to work with the filter. If the user performs an action during the display that makes the diag-
nostic filter status no longer active, the message will close automatically.
Figure 9.1 “Active diagnostic filter” message dialog
If the cause for the active diagnostic filter is missing access authorization, the user can perform this with
the following dialog. “Skip” keeps the active diagnostic filter.
Figure 9.2 “Active diagnostic filter missing access authorization” message dialog
If the diagnostic filter is still active after performing, the following dialog will appear to the user and
activation can be attempted again.
Figure 9.3 Prompt to try activation again when there is an active diagnostic filter
Note: if you continue working with an active filter and then errors occur during communication
with control modules, the note about active diagnostic filters will appear again within the error
message. Examples: “The diagnostic firewall is currently active. Please switch the ignition off
and press and hold the emergency flasher button for at least 3 seconds.” or “Make sure that
access authorization was activated at the gateway. There must be an activation for certain di-
agnostic communications.”
10 Infomedia Button
The Infomedia button that is available in the operating modes does not open an operating mode, but
rather opens an external browser window where information from the Volkswagen Group systems is
displayed.
Clicking this button opens the Elsa2Go group system in an external browser
for the VIN that is currently available. It is not necessary to log into the browser window in order to
display information about the vehicle.
11 Measuring Equipment Mode
11.1 Measuring Equipment General Information

The Measuring equipment mode can be accessed using the Measuring equipment button in the start
screen of the user interface, in the operating modes section (right edge of the screen).
The measuring equipment mode gives users the ability to perform their own measurements outside of
Guided Fault Finding using measuring equipment with parameters that can be set. The measuring
results are displayed numerically or in graph form on the screen.
"Offboard Information System Service user interface” chapter
The Multimeter user interface is automatically active when started:

Figure 11.1: Measuring equipment user interface - multimeter
The user interface in the measuring equipment mode is divided into the following six sections:
Info area:
This area shows general information about the procedure.
Tab bar:
The multimeter or oscilloscope client area can be activated using the tabs in the tab bar.
Chapter 11.2 The Multimeter Client Area

Chapter 11.3 The Client Area - Oscilloscope
Client Area:
The layout of the client area will change depending on the function activated by the tab. All of the
specific measuring parameters for the selected measuring option will be displayed within this working
area.
Figure 11.2: Layout of the multimeter client area

Figure 11.17: Layout of the oscilloscope client area
Modes:
You can switch to the Info, Diagnosis and Admin modes at any time by clicking the buttons. The last
measuring functions that were set will remain after switching.
Chapter 11.5 Measuring Technology Administration
Standard functions:
Note:
The current screen view can be printed using the Data button in the standard functions area.
Clicking the full screen button in the standard functions area will hide the information area and
the modes and will enlarge the rest of the areas.
Status line:
System status messages are displayed in the status line.
The base settings of the Measuring equipment mode, such as the measurement units, can only be
changed in the Admin mode.
11.2 The Multimeter Client Area

The Multimeter tab in the tab bar activates the corresponding Client Area. Using the Multimeter func-
tion, measuring cables connected to the sockets can be set by the user and used. Measuring functions
can be set, measurements can be performed and the results of the measurements can be read.
The following work area is visible when the multimeter function is active:
Figure 11.2: Layout of the multimeter client area
The multimeter client area is divided into the following three areas:
Display area:
The lower portion of the display area displays measured values graphically in the form of a measurement
bar or bar chart. Switch conditions and measured values for the selected measuring options are displayed
in the center area. The upper portion displays important system messages such as if the measuring tech-
nology must be calibrated.
Operating area:
The various buttons in the operating area can be used to start or end measuring functions and to set the
required measuring parameters such as Connection and Measuring range.
Setting the measuring parameter section
Function area:
In the function area, the relevant service functions for each measuring function or for the selected test
procedure can be selected using the appropriate buttons. The following functions can be selected, de-
pending on the measuring function:
Freeze frame:
"freezes" the current display. The measurement repeat cycle is paused and the last measured value is
displayed. Click again to continue the measurement cycle. The freeze frame function can be triggered
remotely using the remote control button on the probes for the URDI and DSO measuring cables (red
measuring cable).
Minimum/maximum:
displays of extreme values can be set and used via measuring cables connected to the sockets. Measuring
functions can be set, measurements can be performed and the results of the measurements can be read.:
display of extreme values. Once the function is activated, the current minimum and maximum measure-
ment values are displayed with a vertical marker within the measuring bar. The extreme values are also
displayed numerically under the marker. When deactivating the function, the extreme values that were
measured up to that point are discarded.
Figure 11.3: Min/Max measured value display

Calibrate:
start the calibration of the measuring cable manually. A manual calibration should always be performed
if a measuring cable was replaced or connected in another location or if there were high temperature
fluctuations. A calibration is performed automatically when starting the URDI resistance (measuring
range <= 100Ω), URDI current and URDI continuity test measuring functions.
Measured Values Diagnosis:
display of measured values and measured value blocks that are read from a control module in cycles.
They must be loaded first in the Diagnosis operating mode and then transferred to the Measuring Tech-
nology operating mode. The button is only visible if measured value blocks were already loaded in the
Diagnosis operating mode.
Chapter 11.4 Transferring Measured Values From Diagnosis Mode
Note:
The freeze frame function can be triggered remotely using the remote control buttons on the probes for
the U/R/D and DSO measuring cables.
The operating area of the multimeter client area is divided into two function blocks:
Figure 11.4: layout of the multimeter client area
Function block 1:
All measuring functions and parameters for the URDI measuring system are combined in function block
1. the related display of measured values is highlighted with a yellow background. The following meas-
uring functions are available:
 URDI voltage - measurement of AC and DC voltage

Chapter 11.2.1 Voltage Measurement with URDI Measuring Cable
 URDI current - measurement of AC and DC voltage
Chapter 11.2.2 Current Measurement with URDI Measuring Cable
 URDI resistance - measurement of ohm resistance
Chapter 11.2.3 Resistance Measurement with URDI Measuring Cable
 URDI diode test - tests the polarity and function of a diode
Chapter 11.2.4 Diode Test with URDI Measuring Cable
 URDI Continuity Test - tests if two points are connected to each other with low impedance (<=
2Ω).
Chapter 11.2.5 Continuity Test with URDI Measuring Cable
Function block 2:
In function block 2, all measuring functions and parameters for the voltage measurement via the DSO1
connection as well as various pressure sensors, a temperature sensor or the voltage measurement via the
current clamp connection are summarized. the related display of measured values is highlighted with a
green background. The following measuring functions are available:
 Voltage DSO1 - measurement of AC and DC voltage

Chapter 11.2.6 Voltage Measurement Using DSO1 Measuring Socket
 Current clamp current - measurement of AC and DC voltage
Chapter 11.2.7 Current Measurement with Current Clamp
 Pressure T/D - pressure measurement
Chapter 11.2.8 Pressure Measurement using T/D Measuring Socket
 Temperature T/D - temperature measurement
Chapter 11.2.9 Temperature Measurement using T/D Measuring Socket
Note:
The measuring functions URDI resistance (measuring range <= 100Ω), URDI current and URDI con-
tinuity test have an automatic calibration which runs the first time they are started. Whether or not a
measuring cable needs to be calibrated automatically also depends on the device. A request for additional
action appears if necessary in the form of a system message.
In addition, the buttons in the multimeter client area operating area may have different names than the
illustration "Layout of the client area - multimeter operating area". This depends on the device (for
example, “Pressure T/D-1” and “Temperature T/D-2” instead of “Pressure T/D” and “Temperature
T/D”).
Notice:
To be able to start the measuring functions from function block 1 and 2, the correct measuring cable
must be connected to the device sockets. An error message appears if this is not the case.
Setting the measuring parameter:
If a measuring function was started successfully in the operating area, the specific measuring parameter
buttons (such as DC or AC measurement) will be added to the respective function block. If a measuring
parameter is not available for the active measuring function, the corresponding button will be inactive
(black) (for example, when activating the URDI resistance function, the A/C button will be inactive).
Figure 11.5: buttons for measuring parameters
The following section describes the characteristics of the measuring parameters. The URDI voltage
measuring option in function block 1 is used as an example.
Setting the DC connection:
Clicking the "=" button activates the DC voltage or direct current measurement type:
When starting a measuring option, the DC voltage or current measuring parameter activates automati-
cally as long as that measurement type is supported. The measuring bar in the display area is centered
and divided into a positive and a negative area.
Figure 11.6: DC measured value display

Setting the AC connection:
Clicking the "~" button activates the AC voltage or alternating current measurement type.
The measuring bar in the display area is aligned with the left.
Figure 11.7: AC measured value display
Setting the measuring range:
When starting a measuring option, the automatic measuring range selection is active. In this case, the
arrow buttons located to the left and right near the measuring range display are inactive and cannot be
used.
Measuring range button in DC automatic mode
Measuring range button in AC automatic mode
Clicking the measuring range display button switches from automatic to manual measuring range selec-
tion. In this case, the arrow buttons located to the left and right near the measuring range display will be
blue. Once the lowest or highest measuring range is reached, the corresponding button becomes inactive
(gray).
Measuring range button in DC manual mode
Measuring range button in AC manual mode

Note:
In addition to the display directly in the measuring range button, the current measuring range is also
display at the left and right ends of the measuring bar scale in the display area.
If the current measured value is outside the set measuring range, the characters "++++" will appear in
the display field if the value is above the range and “ " will appear if the value is below the range.
Setting single measurement or parallel measurement:
During an individual measurement, only one measuring option from function block 1 or 2 is active.
During a parallel measurement, a measuring option from function block 1 and 2 are active at the same
time.
Note:
If parallel measuring is active, both measuring results will be displayed in the display area.
Measuring connection accuracy:
Connection Connection Measurements Value range Resolution

DMM-URDI AC/DC Voltage 2V 0.00006104
DMM-URDI AC/DC Voltage 20 V 0.0006104
DMM-URDI AC Voltage 40 V 0.001221
DMM-URDI DC Voltage 50 V 0.001526
DMM-URDI AC/DC Current 0.2A 0.000006104
DMM-URDI AC/DC Current 2A 0.00006104
DMM-URDI DC Resistance 10 Ω 0.0003052
DMM-URDI DC Resistance 100 Ω 0.003052
DMM-URDI DC Resistance 1 kΩ 0.03052
DMM-URDI DC Resistance 10 kΩ 0.3052
DMM-URDI DC Resistance 100 kΩ 3,052
DMM-URDI DC Resistance 1 MΩ 30.52
DMM-URDI DC Resistance 10 MΩ 305.2
DMM-DSO AC/DC Voltage 0.4 V 0.00001221
DMM-DSO AC/DC Voltage 1.6 V 0.00004883
DMM-DSO AC/DC Voltage 4V 0.0001221
DMM-DSO AC/DC Voltage 16 V 0.0004883
DMM-SZ 50 AC/DC Current 5A 0.0001526
DMM-SZ 50 AC/DC Current 25 A 0.0007630
DMM-SZ 100 AC/DC Current 5A 0.0001526
DMM-T/D DC Pressure 1 bar 0.00003052
DMM-T/D DC Temperature Liq 200 0.006104
DMM-T/D DC Temperature Air 400 0.01221
11.2.1 Voltage Measurement with URDI Measuring Cable
The "URDI voltage" measuring function is activated using the button with the same name.
Figure 11.8: client area when the “URDI voltage” measurement is active
The following measuring parameters can be set:
 Connection: DC voltage or AC voltage

 DC voltage measuring range: ± 2V | ± 20V | ± 50V
 AC voltage measuring range: 0...2V | 0...20V | 0...40V
 Automatic or manual measuring range selection
 Functions: freeze frame, minimum/maximum, calibrate
11.2.2 Current Measurement with URDI Measuring Cable
The "URDI current" measuring function is activated using the button with the same name:
Figure 11.9: client area when “URDI current” measurement is active
 Connection: DC or AC
 DC measuring range: ± 200mA | ±2A
 AC measuring range: 0...200mA | 0...2A
11.2.3 Resistance Measurement with URDI Measuring Cable
The "URDI resistance" measuring function is activated using the button with the same name:
Figure 11.10: client area when “URDI resistance” measurement is active
 Measuring ranges: 0...10Ω / 0...100Ω / 0...1kΩ / 0...10kΩ / 0...100kΩ / 0...1MΩ / 0...10MΩ

Notice:
Calibration is necessary when manually selecting the measuring ranges 0...10Ω or 0...100Ω. The red
and black measuring probes must be brought together. A request for additional action appears in the
form of a system message. The text “Calibration in progress” appears in the display area during the
calibration.
Note:
With manual calibration, additional contact resistance can be compensated up to the measurement ob-
ject. Through a short circuit directly to the measurement object, the calibration includes not just the
measuring cable but also the supply line to the measurement object.
11.2.4 Diode Test with URDI Measuring Cable

The "URDI diode test" measuring function is activated using the button with the same name:
Figure 11.11: client area when “URDI diode test” is active
The result of the diode test is displayed as a graphic within the display area. The following four con-
ditions can be identified:
Short circuit:
diode faulty or the connected measuring object does not have a diode function
Break:
diode faulty or the connected measuring object does not have a diode function
Throughput:
Diode switched in conducting direction

Reverse direction:
Diode switched in reverse direction.
11.2.5 Continuity Test with URDI Measuring Cable
The "URDI continuity test" measuring function is activated using the button with the same name:
Figure 11.12: client area when “URDI continuity test” is active
The continuity test result is displayed as a symbol within the display area. The following two condi-
tions can be identified:
Continuity closed:
if wiring resistance <= 2Ω). There is also an audio signal when there is continuity.
No continuity:
if wiring resistance > 2Ω)

11.2.6 Voltage Measurement Using DSO1 Measuring Socket
The "DSO1 voltage" measuring function is activated using the button with the same name:
Figure 11.13: client area when “DSO1” voltage measurement is activated
 Connection: DC voltage or AC voltage

 DC measuring range: ± 0.4V | ± 1.6V | ± 4V | ± 16V | ± 40V | ± 160V | ± 400V
 AC measuring range: 0...0.4V | 0...1.6V | 0...4V | 0...16V | 0...40V | 0...160V | 0...400V
11.2.7 Current Measurement with Current Clamp
The "current clamp" current measuring function is activated using the button with the same name:
Figure 11.14: client area when the “current clamp” measurement is active
The following four types of current clamps are supported: 50A current clamp / 100A current clamp /
500A current clamp / 1800A current clamp.
 Connection: DC or AC
 DC measuring range: ± 5A | ± 10A | ± 50A | ± 100A | ...
 AC measuring range: 0...5A | 0...10A | 0...50A | 0...100A | ...
Notice:
There is a request to calibrate the first time the measuring option is started. A current measurement can
only be started once the message "Calibration in progress" is no longer displayed in the upper section of
the display area. The current clamp must not clamp any live wires during the calibration.
If the current clamp is open, the earning "Current clamp not closed!" appears in the display area, but the
measurement in progress is not interrupted. For this reason, make sure the current clamp is seated cor-
rectly before starting a measurement with a long duration.
Note:
When measuring with the current clamp, calibrate again manually after change from low to high current
due to the magnetizing effects.
The maximum possible measuring range for a connected current clamp is automatically detected and
the measuring parameters are adapted.
11.2.8 Pressure Measurement using T/D Measuring Socket
The "Pressure T/D" measuring function (can also be called "Pressure T/D-1", depending on the
device) is activated using the button with the same name:
Figure 11.15: client area when “Pressure/TD” measurement is activated
During a pressure measurement, clicking the Filter button filters out high-frequency interference. The
corresponding button is also displayed in function block 2 in the measuring parameters area.
 Measuring range: automatic or manual measuring range selection

 Functions: freeze frame, minimum/maximum
Note:
When a pressure sensor is connected, it is identified automatically and the measuring range is adjusted.
The measurement unit for the pressure measurement can be set to "bar" or "lb/in2" in the Admin mode.
11.2.9 Temperature Measurement using T/D Measuring Socket
The "Temperature T/D" measuring function (can also be called "Temperature T/D-2", depending on
the device) is activated using the button with the same name:
Figure 11i16: client area when “Temperature T/D” measurement is active
 Measuring range: -20...200°C

 Functions: freeze frame, minimum/maximum
Note:
The connected temperature sensor for measurements in fluid or air is identified automatically. The unit
of measure for the temperature measurement can be set to "°C" or "°F" in Admin mode.
11.3 The Client Area - Oscilloscope

The "Oscilloscope" tab in the tab bar activates the corresponding Client Area. Using the Oscilloscope
function, measuring cables connected to the sockets can be set by the user and used. Measuring functions
can be set, measurements can be performed and measuring results can be displayed, stored and compared
on the digital memory oscilloscope.
The following work area is visible when the "Oscilloscope" function is active:
Figure 11.17: Layout of the oscilloscope client area
The oscilloscope client area is divided into three areas:
Display area:
Measuring curves with a two-dimensional coordinate system are displayed in this area. The horizontal
axis (X-axis) is the time axis and the vertical axis (Y-axis) is the amplitude axis. Up to four measuring
curves can be displayed at the same time. To match the measuring parameters better (in the corners of
the display area), the letter on the buttons and the measuring curves are displayed in different colors.
 Yellow - Channel A
 Green - Channel B
 Blue - Channel A specified curve
 Red - Channel B specified curve
Figure 11.18: “Oscilloscope” display area
Operating area:
Parameters for various measuring functions can be set in the operating area using the buttons. The but-
tons displayed depend on the function that is active in the function area.
Chapter 11.3.1 Image Position, Time Basis and Line Strength

Function area:
In the function area, the relevant service functions for each measurement or for the selected test proce-
dure can be selected using the appropriate buttons. The following functions can be selected:
Freeze frame:
The measurement cycle is stopped and the last graph is displayed. The buttons Cursor 1 and Cursor 2
also appear.
Chapter 11.3.8 Freeze Frame
Channel A and Channel B:
Setting parameters for channel A and B

Chapter 11.3.2 Setting Channel Parameters
Trigger mode:
Setting Trigger Parameters
Chapter 11.3.5 Setting Trigger Parameters
Measuring mode:
Setting the measuring mode
Chapter 11.3.3 Setting the Measuring Mode
Cursor 1 and Cursor 2:
specify the start/end point of a marking
Chapter 11.3.8 Freeze Frame
Bandwidth limitation:
activate/deactivate a band pass filter. The bandwidth limitation is already activated after starting the
"Oscilloscope" client area.
Chapter 11.3.6 Bandwidth Limitation
Specified curves:
Record and play back specified curves
Chapter 11.3.7 Specified Curves Functionality
Day/night mode:
switches the display area between a dark and light background
Chapter 11.3.9 Day/Night Mode

11.3.1 Image Position, Time Basis and Line Strength
In the digital memory oscilloscope basic setting, the image position and time basis of the measuring
curves can be set using the arrow buttons displayed in the operating area.
Image position:
the measuring curves can move horizontally on the grid. The trigger point (colored arrow corre-
sponding to the channel color) also moves. The corresponding arrow button becomes inactive when the
farther left or right position is reached.
Time basis:
the sampling of the measuring curves on the x-axis can be increased and decreased. The current time
basis is displayed in the lower right of the display area. The corresponding arrow button is inactive when
the maximum or minimum time basis is reached.
Line strength:
the line strength of the curves can be increased or decreased by 1 pixel by pressing both buttons in the
area 1-7. The initial line strength is 2 pixels.
Notice:
The Channel A, Channel B, Measuring mode, Trigger mode and Specified curves buttons must not
be activated in order to adjust the image position and time basis.
Time basis in write mode Time basis in other modes

0.2...100 s/Div. 1.25 µs/Div. to 0.1 s/Div.
1 channel active
With long-term measurement active: With Min/Max function active: 5 µs/Div. to 0.1
5ms/Div. to 100 s/Div. s/Div.
0.2...100 s/Div. 2.5 µs/Div. to 0.1 s/Div.
2 channels ac-
With long-term measurement active: With Min/Max function active: 5 µs/Div. to 0.1
tive
5ms/Div. to 100 s/Div. s/Div.
Table 11.1 Adjusting the time basis

Note:
The smallest time basis (1.25 µs/Div.) can only be adjusted in single channel mode (channel A or chan-
nel B active). The smallest time basis available in two channel mode is 2.5 µs/Div. Time bases 20, 50
and 100 s/Div can only be adjusted in the Recorder measuring mode.
11.3.2 Setting Channel Parameters

Clicking the Channel A or Channel B button activates the operating area to set parameters for the
corresponding channel. Clicking the selected button again exits mode for setting channel parameters.
After activating the Channel A or Channel B button, a form in the same color as the activated channel
appears in the operating area for setting parameters. The following information uses channel A as an
example for how to set channel parameters. The process for channel B is identical.
Figure 11.19: setting channel A parameters
Allocating the measuring option:
Clicking on the arrow in the Channel list field in the operating area can allocate the desired measuring
functions to the active channel.
The following measuring functions are available for selection:

 OFF - no measuring connection selected
 DSO1 - DSO channel A
 DSO2 - DSO channel B
 kV - kV clamp
 Temp. T/D - temperature according to the sensor that is connected
Also depending on the device: Temp. T/D-1 and Temp. T/D-2
 Pressure T/D - pressure according to the connected sensor
Also depending on the device: Pressure T/D-1 and Pressure T/D-2
 CC- Current clamp
Note:
During a parallel measurement, a measuring option is assigned to channel A and channel B and both are
active. During an individual measurement, either channel A or channel B is active.
Setting the measuring range:
The measuring range (measurement unit/Div.) can be set using the arrow buttons in the operating area.
The corresponding button is inactive (gray) if the minimum or maximum measuring area is reached.
The selected measuring range is shown together with the connection in the display area in the same color
as the channel (channel A at upper left, channel B at lower left).
Setting the connection:
Clicking on the arrow in the Connection list field in the operating area can allocate the desired meas-
urement type to the active channel.
The following measuring parameters are available for selection:
 AC - connection for AC
When there is an AC connection, the DC portion of the measuring signal is blocked and only the AC
portion is displayed. This is useful when the DC portion of a measurement signal is considerably higher
than the AC portion and this would result in an incorrect display.
 DC - connection for DC
With a DC connection, the DC and AC portion is displayed.
 GND (ground) connection to ground

The selected connection ("=" DC; "~" AC) is shown together with the measuring range in the display
area in the same color as the channel (channel A at upper left, channel B at lower left).
Setting the filter:
Clicking on the arrow in the Filter list field in the operating area can allocate the desired filter type to
the active channel.
The following filter types are available for selection:
 OFF - No filter is active.

 HF (high-pass filter) - Only portions above a threshold frequency pass the filter.
 LF (low-pass filter) - Only portions below a threshold frequency pass the filter.
Chapter 11.3.6 Bandwidth Limitation
Showing extreme values:
Clicking the Min/Max button in the operating area activates the extreme values display.
The current minimum and maximum measured values from the time the function was activated are
displayed in the center of the lower section of the display area in the same color as the channel. When
deactivating the function, the extreme values that were measured up to that point are discarded.
Note:
The Min/Max function is activated or deactivated at the same time for both channels during a parallel
measurement.
Moving the measuring curve:
The scroll bar (at the right near the display area) can be used to slide the measuring curves vertically.
The trigger point (colored arrow ( ) corresponding to the channel color) also moves. The measuring
curves for channels A and B can be moved separately from each other.
The offset to the zero line is displayed under the scroll bar.
Notice:
Only one channel can be activated if the smallest time basis (1.25 µs/Div) is set. The button for the
second channel is hidden.
Measuring connection accuracy:
Connection Connection Measurements Value range Resolution

OSZI-DSO AC/DC Voltage 0.4 V 0.0001954
OSZI-DSO AC/DC Voltage 1.6 V 0.0007816
OSZI-DSO AC/DC Voltage 4V 0.001954
OSZI-DSO AC/DC Voltage 16 V 0.007816
OSZI-KV DC Voltage 8000 V 3,908
OSZI-KV DC Voltage 20000 V 9,770
OSZI-KV DC Voltage 40000 V 7:54 PM
OSZI-T/D DC Temperature Liq 200 0.1443
OSZI-T/D DC Temperature Air 400 0.5626
OSZI-T/D DC Pressure 1 bar 0.001222
OSZI-SZ 50 AC/DC Current 5A 0.002443
OSZI-SZ 50 AC/DC Current 25 A 0.01221
OSZI-SZ 100 AC/DC Current 5A 0.002443
Table 11.2: Measuring connection accuracy
11.3.3 Setting the Measuring Mode

When you click the measuring mode button, a parameter template for setting the measured value re-
cording mode appears in the operating area. The selected mode applies to channel A and B. The se-
lected measuring mode is shown at the center of the lower section of the display area in blue text.
Figure 11.20: Setting the measuring mode
Notice:
The measuring mode buttons that are visible depend on the channel parameters set. The measuring
modes that are not supported by the measuring functions assigned by the channels are hidden.
Measured value recording in Auto Setup mode:
Clicking the Auto Setup mode performs an automatic setup. This means the amplitude of the active
channels, the time basis and the trigger threshold are set automatically. The Auto Setup is only per-
formed once each time it is called up. The measuring mode then changes automatically to Auto Level
Mode.
Measured value recording in Auto Level mode:
When you click the Auto Level button, the set trigger threshold (potential threshold in the range of
±100% of the signal amplitude) is updated automatically so there is always a triggered signal regardless
of the signal amplitude.
Note:
Auto Setup and Auto Level can only function correctly when there is a periodic signal with low inter-
ference.
In the Auto Level measuring mode, signals can be triggered regardless of their amplitude height and
zero point position because the triggering is based on an amplitude value as a percentage. When switch-
ing from the Auto Setup mode, the trigger is set automatically to 0% of the amplitude value.
Measured value recording in Auto mode:
When you click the Auto button, the measurement starts automatically when there is a valid trigger event
(according to the set trigger threshold) or after the end of a waiting period that depends on the set time
basis.
Note:
The Auto measuring mode should be used if there is no information about the signal. A measuring curve
will also appear if the trigger lies outside the amplitude (untriggered display). The trigger can then be
directed manually to a value in the amplitude range to keep a fixed image.
Measured value recording in Normal mode:
When you click the Normal button, the measuring cycle will only occur when there is a valid trigger
event.
Note:
The Normal measuring mode should only be used when there is exact information about the amplitude
height and frequency of the measuring signal. A triggered measuring curve will then be displayed if the
trigger lies within the amplitude range of the adjacent signal.
Measured value recording in Single mode:
When you click the Single button, the measurement will only be performed one time after a valid trigger
event. The signal is measured and displayed immediately as freeze frame. Note that there must be a valid
trigger event.
Measured value recording in Recorder mode:
When you click the Recorder button, the measurement will be performed without a trigger. The meas-
uring curve in the display area is displayed continuously from left to right. The Recorder measuring
mode is used to display low-frequency or slow signal (such as oxygen sensors). A long-term measure-
ment is also possible in this measuring mode.
Chapter 11.3.4 Long-Term Measurement in Recorder Mode

Note:
High-frequency or fast signals cannot be displayed in the Recorder measuring mode. The time basis can
be set between 0.2 and 100 s/Div.
The Trigger mode function for setting trigger parameters is not available after activating the Recorder measur-
ing mode.
Notice:
If no measuring curve is displayed after starting the Auto Setup measuring mode, the following points
should be checked in the order listed:
1. Is the DSO measuring cable connected to the device socket and the signal source correctly?
2. Were the channel parameters set correctly? Is the desired measuring option assigned to the channel
correct (for example, channel A is assigned to DSO1)?
3. Is the measuring mode and the trigger (if necessary) set correctly?
4. Automatic setup must be repeated to complete.
Chapter 11.3.2 Setting Channel Parameters

Chapter 11.3.3 Setting the Measuring Mode
11.3.4 Long-Term Measurement in Recorder Mode
Notice:
A Long-term measurement can only be performed in Recorder measuring mode. This function is not
available in all other measuring modes.
The Long-term measurement function is available in the function area after activating the Recorder
measuring mode.
In this measuring function, a user-defined time period in which the measurement will be taken can be
set. After recording, the measuring curves are compressed and displayed within the width of the window.
The following bullet points explain the usage of the long-term measurement.
Setting parameters for long-term measurement:
Clicking the Long-term measurement button in the function area displays the corresponding param-
eter form in the operating area. The freeze frame function is automatically activated while setting the
parameters.
Figure 11.21: Setting parameters for long-term measurement
Setting the measurement duration:
After clicking the Minutes or Hours buttons, you can increase or reduce the measurement duration using
the blue arrow buttons that point to the sides. The corresponding button is inactive (gray) when the
maximum or minimum time interval is reached. The elapsed recording time is displayed in the upper
right section of the display area. The measuring duration remains the same when repeating the measure-
ment.
Adjusting the time basis:
The process for setting the time basis is like the process described in the chapter Image Position and
Time Basis. The set time basis in the long-term measurement function is stored independently of the
time basis for other measuring modes.
Note:
The time basis (sampling rate) limits the maximum measuring duration for a long-term measurement.
The quantity of data increases proportionally as the sample rate increases. The maximum recording time
is 55 hours and 33 minutes at a time basis of 10s/Div.
The device will automatically adapt the measuring duration as needed when the time basis changes. The
following table lists the maximum measuring duration in relation to the selected time basis:
set time basis [time/Div.] Maximum measuring duration [h:min]
5ms/Div. 12:01 AM
10ms/Div. 12:03 AM
20ms/Div. 12:06 AM
50ms/Div. 12:16 AM
0.1s/Div. 12:33 AM
0.2s/Div. 1:06 AM
0.5s/Div. 2:46 AM
1s/Div. 5:33 AM
2s/Div. 11:06 AM
5s/Div. 27:46
10s/Div. 55:33
Table 11.3: Maximum measuring duration for a long-term measurement
Starting the long-term measurement:
Clicking the activated freeze frame button starts the long-term measurement.
If the set measurement duration is elapsed, the freeze frame function is activated automatically and the
measurement ends. The message "Long-term measurement ended" also appears in the display area. All
recorded data are compressed to fit the width of the display area.
Once the measurement ends, the measuring curves can be evaluated with the cursor function and a se-
lected area can be enlarged using the zoom function. The corresponding buttons are shown in the func-
tion area (refer to the bullet point "Evaluating the Long-Term Measurement").
Figure 11.22: Evaluating the long-term measurement
Note:
The values set for a measurement cannot be changed during a long-term measurement.
Connecting or disconnecting USB peripheral devices is not recommended during an active measurement
because it could result in loss of data.
Stopping the long-term measurement:
A long-term measurement can be ended early using the freeze frame button. The data that has been
measured up to that point can be evaluated even though the measurement was ended. The text "Long-
term measurement canceled" appears in the display area.
Evaluating the long-term measurement:
The Cursor 1 and Zoom buttons are displayed once the long-term measurement ends.
The Zoom button is only available when the Cursor 1 button is not active. It is used to enlarge sections
of the measuring curve.
There are two ways to enlarge a section of the displayed measuring curve with the Zoom function:
 Clicking on the area of the curve that you would like to enlarge displays this section immediately
with the minimum possible time basis and over the entire width of the display area.
 Clicking the start point of the area of the curve that you would like to enlarge (press and hold the
right or left button) and then moving the arrow to the desired end point. The marking cursor is
displayed for easier navigation.
The enlarged area is then enlarged and displayed over the entire width of the display area.
After marking an area, blue arrow buttons are displayed in the operating area. They can be used to move
the marked area to the left or right.
Clicking the Cursor 1 button activates the cursor function. This is also possible from the Zoom function
in order to evaluate an enlarged section of the measuring curve. In the function area, you can then switch
between Cursor 1 and Cursor 2 using the buttons.
You can move the marking cursor ( ) in the display area along the displayed measuring curve by
clicking with the mouse or using the touchscreen.
The amplitude and time value for the current position are shown in the function area.
You can position the cursor more accurately on the grid using the orange arrow buttons in the operating
area.
If both cursors are active, the amplitude and time differences between the cursor positions are displayed
in the function area instead of the amplitude and time value.
Note:
The amplitude values and the amplitude difference in the function area are marked in the color of the
corresponding channel. If both channels are active, the values are shown under one another. The time
value is the same for both channels.
11.3.5 Setting Trigger Parameters

The trigger settings can be changed by clicking the Trigger mode button. After activating the function,
the form for setting the parameters appears in the operating area.
Figure 11.23: Setting parameters for the trigger
If parameters were already set for a channel, the relevant settings are automatically transferred to the
trigger. Setting additional trigger parameters is not necessary in this case. If parameters were not set for
any channels, a measuring connection must first be defined as the trigger before additional settings are
possible.
Adjusting the trigger threshold:
The trigger threshold can be set to any trigger value between ± 100% of the maximum measuring range
using the scroll bar on the right side of the display area. The maximum measuring range is shown in the
upper right of the display area in blue text. The trigger threshold is 0 when the trigger is in its default
condition.
An arrow in the display area indicates the current trigger threshold. If the trigger threshold is in the
valid amplitude range, the arrow will be the same color as the respective channel. The arrow is blue
when there is an external trigger. The arrow is red when the trigger threshold is outside the valid ampli-
tude range.
The direction of the arrow (pointing up or down) indicates if the trigger was triggered on the rising
(positive) or falling (negative) side.
The trigger voltage is displayed under the scroll bar. In the Auto Level measuring mode, the trigger
voltage is indicated as a relative percentage value of the measuring signal amplitude (for example, the
trigger voltage is 2.5 volts when the signal amplitude is ±5V and the trigger threshold is set at +50%).
Notice:
If the Recorder measuring mode is activated, the Trigger mode function is not available. There will be
an untriggered measuring data capture.
Selecting a trigger channel:
The following measuring functions can be seat as the trigger by clicking on the arrow in the channel list
field:
 OFF - no measuring connection selected

 DSO2 - DSO socket 2
 DSO1 - DSO socket 1
 KV - KV clamp via KV device socket
 Temp. - temperature via T/D device socket or, depending on the device, also:
 Temp. T/D-1 and Temp. T/D-2 via T/D-1 and T/D2 device socket
 Pressure - pressure via T/D device socket or, depending on the device, also:
 Pressure T/D-1 and Pressure T/D-2 via T/D-1 and T/D2 device socket
 CC- Current clamp via current clamp device socket
 Trigger clamp - trigger clamp via trigger clamp device socket
The adjacent measurement signals for the selected measuring function can then be used as a trigger
event in order to trigger an oscilloscope measurement.
Note:
The corresponding measuring cable must be connected to the appropriate device socket for the selected
trigger channel. If no measuring cable is connected, the error message "Trigger missing" appears in the
display area.
Selecting a trigger connection:
The measurement type can be selected by clicking on the connection list field.
 AC - connection for alternating current/voltage

When there is an AC connection, the DC portions of the measuring signal is blocked and only the
AC portion is displayed. This is useful when the DC portion of a measurement signal is considerably
higher than the AC portion and this would result in an incorrect display.
 DC - connection for direct current/voltage
With a DC connection, the DC and AC portion is displayed.
 GND (ground) connection to ground
Selecting a filter:
The filter type can be selected by clicking on the Filter list field arrow. In this way, undesired portions
of the measuring signal (in the high- or low-frequency range) can be diminished.
 OFF - No filter is active.

 HF (high-pass filter) - Only portions above a threshold frequency pass the filter.
 LF (low-pass filter) - Only portions below a threshold frequency pass the filter.
Selecting a trigger side:
The trigger side can be selected by clicking on the Side list field arrow.
 pos. - the measuring signal is triggered on the increasing side

 neg. - the measuring signal is triggered on the decreasing side
The positive or negative side is indicated in the display area with an arrow (trigger threshold) pointing
up or down.
Moving the trigger point horizontally:
The blue horizontal arrow buttons move the trigger point (arrow in the display area) left or right on the
grid.
If the trigger point is outside the display area after moving it, the arrow is red.
Setting the trigger amplitude value range:
The trigger amplitude is set with the blue vertical arrow buttons.
With externally triggered measuring signals, changing the trigger amplitude value range does not have
any effects on the measuring range and the display of the triggered measuring signal.
The value range set for the trigger amplitude is indicated in the upper right section of the display area
in blue. The value is only visible when the trigger mode function is active.
Notice:
The trigger threshold, filter, trigger side and trigger amplitude cannot be set for the trigger clamp.
11.3.6 Bandwidth Limitation
Clicking the Bandwidth limitation (BWL) button activates the function with the same name. A low-pass
filter with a limiting frequency of 75kHz is set on the active measuring channels.
The bandwidth limitation activation is indicated in the center of the display area near the time basis.
Note:
The bandwidth limitation feature is automatically deactivated by the measuring technology application.
This prevents the high frequency band from being filtered out by a bandwidth limitation that was set
unintentionally when there is a user-defined signal sampling rate.
The threshold is at a time basis <= 0.1 ms/Div (sampling rate >= 500kHz).
11.3.7 Specified Curves Functionality

Clicking the Specified curves button activates the function with the same name. The Back button deac-
tivates the function. After activating the function, the form for setting the parameters appears in the
operating area.
Figure 11.24: Client area of the specified curves function

Note:
Specified curves are designed to assist the diagnostic technician during Guided Fault Finding as well as
free measurements by providing reference curves. The current measured signal (yellow and green meas-
uring curves) can be compared with the reference signal (blue and red measuring curves). If the proper-
ties of the measured signals match the properties of the reference curve, it can be assumed that the
vehicle components being checked are OK.
There are primarily two modes when using the specified curves function:
 User mode: only existing specified curves can be displayed. Only the "Show" button is available.
 Expert modes: in addition to the display, specified curves can be recorded, stored, deleted, edited
and implemented in the function test by authorized users.
Note:
Password authentication in the Admin mode is required to unlock the complete specified curve func-
tionality.
Notice:
If the specified curves function is active, parameters can be set for the channels, the trigger and the
measuring mode.
Recording specified curves:
To be able to record specified curves parameters must be set for at least one channel first. Simultaneous
recording of two channels is also possible.
Clicking the Record button begins recording the measuring signal as a specified curve.
If the measurement is only running on one channel, the next step is specifying the file name and save
location of the specified curve.
- 380 -
Figure 11.25: Plotting specified curves
If measurements are running on both channels, you must choose between the following plotting options
before entering the file name and save location:
Figure 11.26: Plotting specified curves for two channels
The selection is made by clicking on the appropriate button and then confirming with the OK button.
Then a file name and storage directory are entered after that as with a single channel measurement.
The affected settings for the channels, the trigger, the measuring mode, time basis and image position
are stored.
Displaying specified curves:
Clicking the Display button can display specified curves that were recorded.
After selecting the directory and the specified curve file, the corresponding specified curve is displayed
in the display area. The file name for the specified curve is show in the bottom center of the display
area. The previous specified curve file format *.sk2 and the *.sk3 file format that was introduced with
ODIS are both supported.
If a measurement is running at the same time, it is stopped and the channels, the trigger, the measuring
mode, the time basis and the image position are set according to the specified curves. You can tell the
measuring curves apart by their color:
- 381 -
Channel Color of the measuring signal and its measuring Color of the specified curve and
range
its measuring range
Yellow (measuring in the upper left of the display Blue (measuring in the upper right of the dis-
A
area) play area)
Green (measuring in the lower left of the display Red (measuring in the lower right of the dis-
B
area) play area)
Table11.4: Color of measurement curves
Figure 11.27: Displaying specified curves
When displaying specified curves, the measuring signal may lie exactly on the signal recorded for the
specified curve. To differentiate better between both series of curves, the measuring curve can be moved
vertically away from the specified curve using the scroll bar on the right side of the display area. The
respective channel must be selected in the foreground with the channel A and channel B button in the
operating area.
Saving specified curves:
Clicking the save button can save the displayed specified curve with all channel settings under a different
directory. The file name stays the same.
- 382 -
Deleting specified curves:
The displayed specified curve can be deleted by clicking the Delete button.
A dialog appears to confirm the deletion. The specified curve is finally deleted after confirming with the
Yes button. The measurements set with the parameters used by the specified curve continue running.
Freeze frame:
Pressing the freeze frame button stops the measurement cycle and displays the last graph. Unlike the
freeze frame function, no evaluation options are available outside the specified curves function.
11.3.8 Freeze Frame

Pressing the freeze frame button stops the measurement cycle and displays the last graph. Unlike the
freeze frame function, no evaluation options are available outside the specified curves function. The
buttons Cursor 1 and Cursor 2 also appear in the function area.
You can move the marking cursor ( ) in the display area along the displayed measuring curve by
clicking with the mouse or using the touchscreen. The amplitude and time value for the current position
are shown in the function area:
You can position the cursor more accurately on the grid using the orange arrow buttons in the operating
area.
If both cursors are active, the amplitude and time differences between the cursor positions are displayed
in the function area instead of the amplitude and time value.
- 383 -
Note:
The amplitude values and the amplitude difference in the function area are marked in the color of the
corresponding channel. If both channels are active, the values are shown under one another. The time
value is the same for both channels.
11.3.9 Day/Night Mode

Clicking the day/night mode button switches the background of the display area between dark and light.
Dark background:
Figure 11.28: Display area in night mode
Light background:
- 384 -
Figure 11.29: Display area in day mode
11.4 Transferring Measured Values From Diagnosis Mode

It is possible to transfer measured values from the Diagnosis mode into the Measuring equipment
mode.
Notice:
The Measured value diagnosis function is only available when measured values are selected in the
Diagnosis mode.
Diagnostic entry chapter
Presettings in the diagnosis operating mode:
Clicking the Diagnosis button activates the mode. The desired control module must be selected next.
Diagnostic entry chapter

The control module for which measured values should be transferred must be marked. Then click in the
active selection with the right mouse button. The following button group appears, in which the Measur-
ing equipment button must be selected:
- 385 -
Depending on the type of control module, a window for selecting a measured value block (KWP control
modules) or individual measured values (UDS control modules) will appear. After selecting the meas-
ured value block or individual measured values (a maximum of four measured values can be shown),
confirm with the OK button.
After confirmation, the system automatically switches to the Measuring equipment mode. The Meas-
ured value diagnosis function is available for the Multimeter and Oscilloscope functions.
After clicking the Measured value diagnosis button, the first four measured values are shown in the
display area.
- 386 -
Figure 11.30: Displaying diagnostic measured values in the multimeter
Figure 11.31: Displaying diagnostic measured values in the oscilloscope
11.5 Measuring Technology Administration

Special settings for Measuring equipment can be carried out in the Admin mode. The following ac-
tions are available for selection within the list fields on the Measuring equipment and Measuring
equipment actions tabs.
- 387 -
GDI device driver:
The GDI driver for the connected measuring device can be configured here. If the desired driver is not
shown in the list field, check if the suitable driver was installed correctly.
Physical units:
This function offers the option of specifying the physical units for various measurement sizes in inde-
pendent measuring technology. The specified settings are not taken into consideration in Guided Fault
Finding. The following physical units can be configured:
 Voltage: V (volt)
 Current: A (ampere)
 Resistance: Ω
 Pressure: bar, lb/in2 (pounds of force per square inch)
 Temperature: °C (degrees Celsius), °F (degrees Fahrenheit)
Signal sensor:
The signal sensor function allows the duration and pitch of the continuity test signal to be adjusted. A
value between 0 and 3000 ms can be entered for the signal duration. A frequency between 0 and 4000
Hz can be selected for the signal tone.
Measuring equipment GDI components:
The version number of the GDI components being used can be viewed under this item.
Self-test:
The self-test allows access to performing self-test functions integrated in the units. A measuring device
performs special internal check to assure that it is functioning correctly. Self-tests are supported in the
simple measuring technology as well as in the high voltage measuring technology. There are two
switches used to perform self-tests - one for the simple measuring technology and one for the high
voltage measuring technology. When you use the measuring technology switch, a self-test will be per-
formed on the measuring device for the simple measuring technology which is part of the GDI device
driver. When you operate the high voltage measuring technology, a self-test is performed on the con-
nected VAS6558(A) high voltage measuring device. OK will appear if the self-test was successful. If
the test fails, not OK will appear.
Specified curves functionality:
After clicking the specified curves action function, the user must be authenticated to activate the Expert
mode in the Oscilloscope specified curves function. A request appears to enter the location ID and pass-
word in the entry field in the display.
- 388 -
After entering the information correctly, the Activate and Cancel buttons appear. If the specified curves
function is already activated, the Deactivate button appears instead of Activate.
Figure 11.32: Enabling expert mode in the specified curves function
Chapter 11.3.7 Specified Curves Functionality
12 Administration Mode
12.1 Operation
Various Offboard Diagnostic Information System Service settings can be configured in Administra-
tion mode.
The following view is visible after clicking the Admin button.
- 389 -
Figure 12.1 Administration window
The administration view contains five tabs for system settings that are arranged according to areas. These
tabs are:
 General
System-based settings such as language or update mode are managed here.
 Save locations
The save locations for system and work data are selected here.
 Support
The support settings are managed here.
 Connections
The connections to individual group systems services are managed here.
 Certificate
The necessary certificates for Internet access are linked here to the individual group systems
services.
 Test Baseline
The test environment can be configured here. This function is only available for all users.
- 390 -
The listed settings options are located within this tab.
To make changes, click the desired settings in the left selection window to make a selection. The con-
figuration options are in the right window.
Saved changes can be reset to their default factory settings with the Reset button.
Changes that have not been saved yet can be restored to their default settings with
the Discard button.
Clicking the Save button saves the changes made.
Notice:
Changing system settings can interfere with the use of Offboard Diagnostic Information System Ser-
vice. The configuration should only be changed if requested by support. The user is responsible for any
changes made that are not recommended by support.
The following administration areas are available:
General Area:
Brand Design
Language
Update
System Logging
System Environment
License Information
Global Configuration
GFF Process
Dealer Data
Save Locations Area
Database
Diagnostic Session
Flash Path
Diagnostic Log
- 391 -
Support
Support Area
Contact Data
E-mail Outgoing Server
Connections Area:
Brand Settings
Group System: Logon
Group System: GFF
Group System: ElsaPro
Group System: Carport
Group System: DISS
Group System: eShop
Group system: Mirror Server 2
Group system: support application
Group System: Login
Network addresses for various login services that Offboard Diagnostic Information System
Service uses can be set in this field.
Figure 12.32 Group system view: Login
All addresses being used for Login, DSS, GRP authentication services are listed in the group system
details: Login view.
GRP
GRP Retail
- 392 -
 GRPDSS
 DSS Logon
 Logon
 Saved changes can be reset to their default settings with the Reset button.
 Changes that have not been saved yet can be restored to their default settings
with the Discard button.
Offboard Diagnostic Information System Serves specifies addresses for these services.
Notice:
If incorrect addresses are entered here, the necessary authentications will not be completed successfully.
It is normally not necessary to change these network addresses.
Mirror Server 2
Certificates Area:
Client certificate
Trust Certificate
Test Baseline Area:
Data Configuration
12.2 General Area

12.2.1 Brand Design
In this area, the Offboard Diagnostic Information System Service graphic interface can be adapted to
a specific group brand.
- 393 -
Figure 12.2 Selecting the Design
Use the selection lists for details on brand design.
Designs of licensed brands may be selected. In addition, Neutral and Dynamic are available.
When Neutral is selected, Offboard Diagnostic Information System Service displays with a neutral
logo regardless of the brand.
The dynamic design matches to the brand automatically identified during the diagnostic entry, so long
as there is a design for this brand. Otherwise the neutral design is used.
Saved changes can be reset to their default settings with the Reset button.
the Discard button.
- 394 -
12.2.2 Language
The Offboard Diagnostic Information System Service language can be changed using the language
list field.
Figure 12.3 Language setting
The desired language can be selected in Language details in the Language list. The languages are
available which the user selected during the post setup.
the Discard button.
- 395 -
Note:
Only the user interface language changes. If documents are available in the selected language, they will
be displayed in the new language that was set. Otherwise the documents remain in the installed language.
The following steps are necessary to use Offboard Diagnostic Information System Service in different
languages (especially East Asian characters):
In the Windows operating system, open Control Panel -> Regional and Language Options.
Figure 12.4 Additional Windows language support
On the Languages tab, activate the options in the Additional language support area.
OK: the changes are made and the window closes.
Cancel: the changes are not made and the window closes.
Transfer: the changes are made but the window does not close.
- 396 -
Figure 12.5 Windows language display codes
In the Expanded tab, activate all Code page conversion tables.
In the Expanded tab, activate the Standard settings for user accounts.
OK: the changes are made and the window closes.
Cancel: the changes are not made and the window closes.
Transfer: the changes are made but the window does not close.
Restart the system. The languages are then available.
12.2.3 Update
The cycle that Offboard Diagnostic Information System Service uses to check for updates on the
mirror server 2 can be set in Update details.
- 397 -
Figure 12.6 Update view
Load in background: when this option is activated, Offboard Diagnostic Information System Ser-
vice download program updates in the background, if there are any. For performance reasons, down-
loading the in background pauses when a diagnostic session starts. The same applies if there is not
enough memory available for the update.
Temporary download folder: this is used to specify the folder where the program updates will be stored
temporarily until they can be installed. The path to the folder can either be entered manually or browsed
for in the folder system by pressing the Browse... button.
Checking schedule: with this option, the user can specify if the program should check for updates ac-
cording to a cycle, meaning each time a certain number of days passes, or always on the days of the
week that are indicated.
Cycle (in days, 1-7): only relevant if Cycle was selected as the schedule to check for updates. 1 is
entered in this field as a default. That means the system will check for available program updates each
day starting from the first time the program is started. The desired update cycle can be entered here in
days. For example, enter the number 5 to search for updates every five days. The cycle cannot be more
than 7 days.
- 398 -
Days of week for updates: only relevant if On certain days of the week was selected as the schedule
to check for updates. The desired day of the week to check for updates is selected here. Multiple days
or all days of the week can be selected.
If no day was selected, a note about this will display when the program automatically checks for updates
every day.
Figure 12.7 Configuration error when checking for updates
the Discard button.
12.2.4 System Logging

The content of the system logging can be determined in a selection window. The system logging is
written in a log file that is sent with the feedback.
- 399 -
Figure 12.8 System configuration view
If the feedback support team requires more detailed information, the content can be set in System log-
ging details under Settings.
The selection:
 All
Contains all log contents listed here. This file is the largest, so transferring it can take the longest.
 Information
Contains log contents with information.
 Warnings
Contains log contents with warnings.
 Fault
Contains log contents with errors.
 Serious error
Contains log contents with serious errors.
The scope of log information that is recorded can range from "serious errors" up to "all". A detailed log
output can result in loss of performance.
- 400 -
the Discard button.
12.2.5 System Environment

This area provides information on Offboard Diagnostic Information System Service system settings.
Figure 12.9 System environment view
System environment details shows
 The system path to the installation directory and the data directory
- 401 -
 The software and data versions
 The save location of the DIDB DB Basis database
 The version of the ECP
 The manufacturer and versions of the external diagnostic applications MCD server and PDU
API
The information here cannot be changed. This view is only to provide information.
12.2.6 License Information

This view displays all of the details about the license.
Figure 12.10 License Information Part 1 View
- 402 -
Figure 12.11 License Information Part 2 View
The following licensing information is displayed:
 versions of the product and brand,

 The license file's expiration date, serial number and save path
 The country code under information
 The importer and dealer numbers as well as dealer type under licensed brand(s)
 The hardware ID and tester type under hardware
 The version of the start program under launcher
This is only for general information. The settings cannot be changed.
Cross-reference:
Also refer to Notice in the chapter Diagnostic Entry.
12.2.7 Global Configuration

In the global configuration, all tester devices (testers, notebooks) access the same configuration file so
all devices have the same settings.
- 403 -
Figure 12.12 Global configuration view
The global configuration file must be saved in a previously selected path in the local network.
Select: a path can be set on individual testers under global configuration directory using this button.
Use global configuration: this is used to determine if the tester will use the global configuration settings
if a corresponding file was specified in the directory described above.
Change global configuration: here you select if the tester configuration file should be written into the
global configuration directory. If so, the global configuration data will be overwritten.
the Discard button.
- 404 -
Notice:
If no global configuration data is selected, Offboard Diagnostic Information System Service will use
the available local configuration settings.
12.2.8 GFF Process

The Guided Fault Finding process can be configured in this section.
Figure 12.13 GFF procedure details view
Always display test steps: the listing of individual test steps on the left side of the Guided Fault Finding
operation view can be switched on or off using this setting. The test steps are always displayed if the
setting is activated. Otherwise the test step listing for Traversal tests, Test programs and Start and
end modules is switched off.
Cross-reference:
- 405 -
Avoid DoIP connection: if this setting is activated, there will be no diagnostic communication through
DoIP during the next diagnostic entry. This adjustment only applies to the next diagnostic entry and
then is automatically set to the default value avoid.
Avoid Can-FD communication: if this setting is activated, there will be no diagnostic communication
via CAN-FD during the next diagnostic entry. This adjustment only applies to the next diagnostic entry
and then is automatically set to the default value not used.
the Discard button.
12.2.9 Dealer Data

The dealer data display in the diagnostic log can be configured here.
Figure 12.14 View of the dealer data details
Facility ID: dealer data, which can be found in the diagnostic log in the "facility ID" field, can be entered
in this field.
- 406 -
It is possible to enter a free text without any limitation to length and with line breaks. If the field stays
empty, then nothing will appear in the "facility ID" field in the diagnostic log.
the Discard button.
12.3 Save Locations Area

12.3.1 Database
The save location of the diagnostic database can be set in this area.
- 407 -
Figure 12.15 Database Directory
Select: in database details, this button can be used to select the save location of the database directory
in the Windows file system.
the Discard button.
- 408 -
Notice:
This path may only be changed with consent from support. Otherwise, the vehicle diagnostic data will
no longer be available.
If the database will be copied to a different location, the new path must be entered here.
12.3.2 Diagnostic Session

The save location and file name specification for the diagnostic session data can be preset in this area.
Offboard Diagnostic Information System Service suggests a standard setting.
Figure 12.16 Diagnostic Session Save Location
Select: using this button, the specified save location for the diagnostic session data in the Windows file
system can be selected in the Target directory field under Diagnostic session details.
During a session, it is possible to save the session data to a different location using the Windows save
dialog.
Note:
The initial suggested save location will be kept as a default path in a separate field that is not visible
and that therefore cannot be changed.
Reference: see also chapter Diagnostic Session.
File name pattern: a naming pattern for the diagnostic session can be selected in this input field.
- 409 -
File name pattern: a naming pattern for the diagnostic session can be selected in this input field.
In the example shown, the file name consists of the VIN, order number „1234“, date with four-digit year
and two-digit month and day and the exact time 1234_WVW12345678901234_2009-08-12_16-27-
15.ses.
The following inputs are possible:
 %YYYY→for the current year

 %MMM→for the current month
 %DD→for the current day of the month
 %hh→for the current time of day in 24-hour format
 %mm→for the current minute in the hour
 %ss→for the current second in the minute
 %VIN→Vehicle Identification Number of the vehicle being diagnosed
 %JOB→The order number of the currently selected order
 free text that may consist of the following characters:
 capital and lower case letters
 all numbers from 0 - 9
 the following characters: _(underscore) -(minus) .(period)
the Discard button.
Notice:
There must be a save location to save session data.
12.3.3 Flash Path

In this area, the file paths through which Offboard Diagnostic Information System Service loads flash
files are set.
- 410 -
Figure 12.17 Flash paths view
Select: in Flash path details under Flash paths, this button is used to set the path to the flash files in
the Windows file system for Path 1 (CDROM) and Path 2 (hard drive). Local flash files can be stored
under these paths and prepared for flashing.
the Discard button.
The path entered manually must conform to Windows specifications:
CDROM drive letter:\Flash data or
Drive letter:\Folder name\Flash data
- 411 -
Notice:
If there are not valid paths entered here, local access to flash files is not possible.
12.3.4 Diagnostic Log

The save location and the name for the Guided Fault Finding logs in the Windows file system are estab-
lished in this area. Offboard Diagnostic Information System Service suggests a default setting for
both logs.
Figure 12.18 Diagnostic log view
Select: in diagnostic log details, the save location for the log can be entered under Guided Fault Find-
ing log as well as under OBD log in the target directory field.
During a session, it is possible to save the log data to a different location using the Windows save dialog.
- 412 -
Note:
The initial suggested save locations will be kept as default paths in separate fields that are not visible
and that therefore cannot be changed.
Reference: see also chapter 13.1.1.
File name pattern: a naming pattern for the log can be selected in this input field. In the example, the
file name for the Guided Fault Finding log is made up of the VIN, order number „1234“, the date with
a four-digit year, a two-digit month and day and the exact time 1234_WVW12345678901234_2009-08-
10_14-32-34_dprot.
The following inputs are possible:
 %YYYY→for the current year

 %MMM→for the current month
 %DD→for the current day of the month
 %hh→for the current time of day in 24-hour format
 %mm→for the current minute in the hour
 %ss→for the current second in the minute
 %VIN→Vehicle Identification Number of the vehicle being diagnosed
 %JOB→The order number of the currently selected order
 free text that may consist of the following characters:
 capital and lower case letters
 all numbers from 0 - 9
 the following characters: _(underscore) -(minus) .(period)
the Discard button.
Note:
With default settings, the log is saved with the VIN in the file name to prevent confusion.
Auto save: this is where you can choose the intervals, in which the Guided Fault Finding log should be
saved in a specified location automatically. The default value is every 5 minutes.
When OFF is selected from the list, then the diagnostic log is not automatically saved.
- 413 -
- 414 -
12.3.5 Support
The directory that should be used for saving support requests is specified in this area.
Figure 12.19 Support view
Select: clicking this button will display a dialog for selecting the directory.
Save when sending?: this checkbox can be used to specify if the support request should be saved after
sending.
Note: in accordance with the General Data Protection Regulation (GDPR / DSGVO), the ODIS appli-
cation will delete saved support inquiries after 30 days. However, this will only happen in the initial
default directory. If a directory other than the initial setting is selected, the user must ensure himself
that the DSGVO is enforced. Corresponding notes will appear below the input fields.
the Discard button.
- 415 -
12.4 Support Area
12.4.1 Contact Data
The data for the support contact person is entered here.
Figure 12.20 Support view
The contact person and his or her address for support feedback is entered here in Contact data details
under Contact data for feedback.
Possible information includes:
 First name
 Last name
 E-mail address (required)
 Phone number (required)
The program will check for valid entries in the E-mail address and Phone number fields. If the infor-
mation in these fields is missing or invalid, the field will be marked with a red asterisk and the Save
button will be inactive.
- 416 -
the Discard button.
Note:
This information is necessary so that support can contact the right person if there are questions or re-
sponses.
Reference:
12.4.2 E-mail Outgoing Server

The feedback mail connection to support is configured here.
Figure 12.21 E-mail Outbox Server View
- 417 -
Use the operating system's default e-mail client: if this option is activated, the e-mail program that is
specified as the default program will be used to send e-mail. The connection parameters for this e-mail
program are used.
To use Offboard Diagnostic Information System Service to send e-mails, select the following options
in the "Outgoing mail server" section under Connection parameters:
 Connection:
o An e-mail is sent with every feedback - Mail settings,
o The feedback is saved locally temporarily - QUEUE settings.
o If you switch from QUEUE settings to Mail settings, Offboard Diagnostic Infor-
mation System Service sends the e-mails that were saved temporarily with the next
feedback.
 Mail server: name of the mail server.
 Mail server port: the port for the mail server.
 Mail server login: a checkmark can be entered here if a login to the mail server is necessary.
 Access name: the access name for the mail box that is entered here is assigned in the login
window when logging in.
 Password usage:
o The password is saved until Offboard Diagnostic Information System Service is
ended. If the password should be stored until Offboard Diagnostic Information Sys-
tem Service is closed, a login window in which the user name and password are entered
will open when sending a feedback.
o The password only applies to the next time feedback is sent.
o The password will be stored permanently each time it is transferred successfully. The
password field in the login window is then populated with this password. The password
is encrypted when it is stored permanently.
 Secure connection: here you can switch between the STARTLS and TLS/SSL secure connec-
tion types, depending on what the mail server requires.
 E-mail sender address: you can enter your own sender address here. This is necessary if sup-
port needs to reply to the address.
the Discard button.
If the e-mail is sent through the mail server from a provider, the provider specifications must be en-
tered. The provider will provide the necessary data such as mail server address, SMTP port and security
settings. The user name for the mailbox and the specified password must be used to log in.
- 418 -
If a network with its own mail server is used, it must be configured for SMTP (Simple Mail Transfer
Protocol). An older mail server that does not support this protocol (such as older versions of Microsoft
Exchange) cannot be used. The mail server administrator will provide the specifications required for
configuring the outbox server.
Cross-reference:
Notice:
The mail server configuration entries must conform exactly to the specifications. Free text such as mail
server information and the mail sender address is not checked. Incorrect entries will cause errors when
sending feedback.
The e-mail outgoing server does not support a proxy server for accessing the Internet.
If using security software such as a firewall or anti-virus protection, make sure it does not block the
mail sever or the ports that are used.
The size restriction for e-mails that is set in the mail server must be followed. The provider or mail
server administration can provide information about this. The size restriction should be changed, if nec-
essary, if that is possible. If an e-mail exceeds the size restriction, it will not be sent. Feedback e-mails
with data attached can reach sizes of 2 MB to 5 MB.
Back end mail is sent through the JavaMail software standard library. If an error occurs within this
software when sending an e-mail, the error messages will only display the original text in English. In
this case, the original text in the error message will be referenced. There are exceptions to this:
If the mail server is entered incorrectly, the login appears with error message ODS9102E with a note
about the unknown mail server.
- 419 -
Figure 12.22 Error message about an incorrect mail server
The user name and password can be entered again.
Transfer: user name and password are transferred.
Cancel: the login is canceled.
If a sender address is spelled incorrectly, the login appears with error message ODS9105E with a note
about the invalid sender e-mail address.
Figure 12.23 Error message about an incorrect sender address
The user name and password can be entered again.
Transfer: user name and password are transferred.
- 420 -
Cancel: the login is canceled.
12.4.3 Hardware and Software

This section provides information about the hardware and software of the used diagnostic device.
Figure 12.24 Hardware and software view
The diagnostic device hardware is displayed under Hardware:
Processor: installed processor
Working memory: size of the installed working memory
Hard drive “x” availability/size: hard drive “x” size and usage
The software used on the diagnostic device is displayed under Software:
Operating system: operating system name and version
Bluetooth driver (version): Bluetooth driver name and version
Bluetooth stack: Bluetooth stack name and version
Bluetooth adapter „x“: Bluetooth adapter „x“ name and hardware/software version
- 421 -
Wi-Fi driver: Wi-Fi driver name
Wi-Fi adapter „x“: Wi-Fi adapter „x“ name
Java version: Java version
Information in this view cannot be changed. It only provides information.
12.5 Connections Area

12.5.1 Brand Settings
In this field, you can set the way each group brand connects to the group system, via CPN or Internet.
Figure 12.25 Brand Settings View
Brand to be configured: the brand whose settings will be configured in the Connection types tab in
the following views is selected in the Selection list. Only the brands that are licensed for the tester are
available in this brand selection.
- 422 -
Connection types: here you can select if a group system service is called up via CPN or an Internet
address. This setting can be specified individually for each brand.
the Discard button.
Notice:
The preset addresses for group system services can only be changed with agreement from support for
the affected brand. Otherwise, access is not possible.
12.5.2 Group System: Logon

The connection address to DSS is configured in this field.
Figure 12.26 Group system view: Logon
All addresses being used for DSS authentication services are listed in the group system details: Login
view.
 DSS View
- 423 -
the Discard button.
Notice:
The authentication to the GFF and/or infomedia is not possible and these services cannot be used if an
incorrect address is entered here.
12.5.3 Group System: GFF

Network addresses for group services that Offboard Diagnostic Information System Service accesses
can be set in this field.
Figure 12.27 Group System: GFF
The Group system details: GFF view lists all service addresses that are used in GFF test programs
whose URLs can be entered:
 Pin Service
 SVMService
- 424 -
 RepairHints
 ProtoService / ProtMgmtService
Additional group systems may be listed depending on the brand and connection type.
the Discard button.
Notice:
If an incorrect address is entered here, GFF test programs cannot access the required group systems and,
so they will not run correctly.
12.5.4 Group System: ElsaPro

The access data for services in the group system ElsaPro are configured in this field.
Figure 12.28 Group system ElsaPro view
- 425 -
To be able to display data from ElsaPro in Offboard Diagnostic Information System Service, the
URLs in group system details: ElsaPro for
 Vehicle history
 Repair manuals
 Technical service bulletins
 Wiring diagrams
 Campaigns
entered in the Macro50.
The data required for logging into group systems
 Brand (1 character)
 Country (3 characters)
 Dealer ID (5 characters)
are taken from the license and are only displayed here.
the Discard button.
Notice:
If these entries are not correct, either ElsaPro data cannot be accessed or the required login to the group
systems will fail.
12.5.5 Group System: Carport

The connection address to Carport is configured in this field. Offboard Diagnostic Information Sys-
tem Service provides an address.
- 426 -
Figure 12.29 Carport View
The URL for vehicle data through which this service is reached is entered under Group System De-
tails: Carport.
the Discard button.
Notice:
If the URL is not entered correctly, the Carport service cannot be reached and vehicle data cannot be
accessed.
12.5.6 Group System: DISS

The connection address to DISS is configured in this field. Offboard Diagnostic Information System
Service provides an address.
- 427 -
Figure 12.30 DISS View
The DissUrl for DISS, which is used to determine concerns, is entered under Group System Details:
DISS.
the Discard button.
Clicking the Save button saves the changes made
Notice:
If there is no correct DISS URL, concerns cannot be displayed from the DISS system or associated
TSBs.
12.5.7 Group System: eShop

The connection address to the eShop is configured in this field. Offboard Diagnostic Information
System Service provides an address.
- 428 -
Figure 12.31 Group system eShop view
The URL for the eShop service for automatic extensions of licenses obtained through the eShop is en-
tered under Group system details: eShop.
the Discard button.
Notice:
Without a correct URL for the eShop license update service, licenses cannot be extended automatically
from Offboard Diagnostic Information System Service. Without an automatic extension, the expired
license must be ordered in the eShop.
12.5.8 Group System: Login

Network addresses for various login services that Offboard Diagnostic Information System Service
uses can be set in this field.
- 429 -
Figure 12.32 Group system view: Login
All addresses being used for Login, DSS, GRP authentication services are listed in the group system
details: Login view.
 GRP
 GRP Retail
 GRPDSS
 DSS Logon
 Logon
the Discard button.
- 430 -
Notice:
If incorrect addresses are entered here, the necessary authentications will not be completed successfully.
It is normally not necessary to change these network addresses.
12.5.9 Mirror Server 2

Offboard Diagnostic Information System Service gets the files for update from Mirror Server 2.
Figure 12.33 Mirror server 2 view
The address of the local mirror server as it was set up on location for the workshop is entered in the
mirror server URL field.
The mirror server user and mirror server password fields only need to be filled out if the local mirror
server was set up with a login. The local administrator can confirm if this is the case.
Timeout [s]: this is where the maximum wait time for answers from the Mirror Service are set. The
default value is 5 seconds.
the Discard button.
- 431 -
12.5.10 Support application

The support application is used for support requests via the support application.
Figure 12.34 Support application view
The address of the support application to which support requests will be sent is entered in the URL
field.
12.6 Certificates Area

Certificates that are needed for an encrypted SSL communication to the group system via the Internet,
can be accessed and managed in the certificate field in the Administration mode. The certificates apply
to all brands.
Two types of certificates are available. The following describes how to manage them:
1. Client certificate
2. Trust certificate.
12.6.1 Client certificate

Client certificates have a public and private key. They are needed to authenticate the testers with the
group system servers using Offboard Diagnostic Information System Service.
- 432 -
Figure 12.35 Client certificates view
Client certificates can be imported in client certificate details view. Details can be displayed and re-
moved here.
Client certificates are imported in the import certificates field:
Certificate: clicking on searches and selects the client certificate using the Windows
file manager. Client certificates have the file extension *.pfx or *.p12. The import button activates when
a certificate is selected.
Password: the client certificate password must be entered here.
Clicking on adds the client certificate to the Offboard Diagnostic Information Sys-
tem Service certificate memory.
The following errors can occur while importing client certificates:
- 433 -
1. The hardware ID in the client certificate does not match the tester ID.
Figure 12.36 The hardware ID in the client certificate does not match
2. The client certificate has expired.
Figure 12.37 The validity period has expired.
3. The client certificate format is not supported. X.509 format is required.
- 434 -
Figure 12.38 The format is not supported.
The client certificate can be viewed in detail in the available certificates field.
Name: certificate alias name.
Valid starting: validity start date.
Valid through: validity end date.
The detailed view can be opened by selecting the client certificate and clicking on .
- 435 -
Figure 12.39 Client certificate detail view
The following contents is displayed in the Details field:
Name: Client certificate alias name. CN=Name, OU= Organizational Unit, O= Organization, L=City,
ST= State/Province, C=country.
Owner: owner of the client certificate.
Issuer: issuer of the client certificate.
- 436 -
Type: Client certificate format.
Issue Date: issue date (import date) when the certificate was imported into the certificate memory.
MD5 fingerprint: the fingerprint in MD5 format.
SHA-1 fingerprint: the fingerprint in SHA-1 format.
Serial number: the client certificate serial number.
The certificate chain is displayed hierarchically in the certification path field. The selected client cer-
tificate is the last one in the chain. Valid certificates are in green, invalid ones in red.
Clicking on leaves the detailed view and returns to the overview list.
If a client certificate is no longer needed, highlight it and click on to delete. It is necessary

to confirm one more time when you erase a certificate.
12.6.2 Trust Certificate

Trust certificates have a public key. A group system server identifies itself in the Offboard Diagnostic
Information System Service tester as belonging to the VW corporation.
- 437 -
Figure 12.40 Trust certificate view
Trust certificates can be imported in trust certificate details view. Details can be displayed and re-
moved here. All trust certificates appearing in gray can be viewed in detail but cannot be removed. They
are stored in the certificate memory. Self-imported trust certificates appear in black and can be removed.
Trust certificates are imported in the import certificates field:
Certificate: Clicking on searches and selects the trust certificate using the Windows
file manager. Trust certificates have file extensions *.cer, *.der or *.pem. The import button activates
when a certificate is selected.
Clicking on adds the trust certificate to the Offboard Diagnostic Information Sys-
tem Service certificate memory.
Notice:
The following errors can occur while importing trust certificates:
- 438 -
1. The trust certificate has expired.
Figure 12.41 The validity period has expired.
2. The trust certificate format is not supported. X.509 format is required.
Figure 12.42 The format is not supported.
The trust certificate can be viewed in detail in the available certificates field.
Name: certificate alias name.
The detailed view can be opened by selecting the trust certificate and clicking on .
- 439 -
Figure 12.43 Trust certificate detailed view
The following contents is displayed in the Details field:
Name: trust certificate alias name. CN=Name, OU= Organizational Unit, O= Organization, L=City,
ST= State/Province, C=country, DC=Domain Components
Owner: owner of the trust certificate.
Issuer: issuer of the trust certificate.
- 440 -
Type: trust certificate format.
Issue Date: issue date (import date) when the certificate was imported into the certificate memory.
MD5 fingerprint: the fingerprint in MD5 format.
SHA-1 fingerprint: the fingerprint in SHA-1 format.
Serial number: the trust certificate serial number.
The certificate chain is displayed hierarchically in the certification path field. The selected trust certif-
icate is the last one in the chain. Valid certificates are in green, invalid ones in red.
Clicking on leaves the detailed view and returns to the list view.
If a trust certificate is no longer needed, highlight it and click on to delete. Confirm one
more time to delete the certificate.
12.7 Test Baseline Area

A test environment can be configured in the Test baseline area of Administration mode. You can
specify here if tests should be based on productive data or test baseline data.
This function is only available for all users.
- 441 -
12.7.1 Data Configuration
Figure 12.44 Data configuration view
In the Test baseline area, you determine if productive data or test baseline files should be used. The
corresponding option should be selected here.
The path to the productive data is fixed and cannot be changed. The path to the test baseline data can
either be entered directly in the text field or selected from a file selection dialog using the Select button.
If the path is invalid because the folder does not exist, the text field will be marked with a red x.
Check for updates: if this is checked off, the system will check if there is a more current version of the
data when using a test baseline. If yes, the user will be asked if the new version should be downloaded.
Use vehicle projects: if this is checked off, vehicle projects from the directory specified below will be
used.
Vehicle projects: you can specify an alternative folder here that contains one or more vehicle projects
that are not part of the productive or test baseline data. This path can also either be entered directly or
selected from a file selection dialog using the Open button.
If alternative vehicle projects are activated, the vehicle projects from the selected folder in the base
features dialog or the configuration of the test will be displayed and can be loaded. All other data such
- 442 -
as VRT, VPT, XML reference tables, networking diagrams, service references or DIDB depend on the
specified data source.
the Discard button.
If changes are made during an active diagnostic session, they will go into effect only after the diagnostic
session ends and there is a new diagnostic entry. Outside of a diagnostic session, they go into effect
immediately.
The changes made here are also displayed when opening the dialog with version information.
Cross-reference:
Also refer to the chapter Troubleshooting.
13 Additional Program Functions

This chapter describes the functions that are available through the various operating modes.
These additional program functions or standard functions are divided into four menus:
 the menu Log

 the menu Data
 the menu Extras
 the menu Help
 the menu Info
 the menu Trace
 the menu Legal
13.1 Log
The Protocol menu has three function areas:
 General
 Diagnostic Log
- 443 -
 OBD Log
Figure 13.1 Screen button log
Here, actions can be performed in connection with the Guided Fault Finding diagnostic log and with the
OBD log.
13.1.1 General
This section applies likewise to the Guided Fault Finding diagnostic log as well as to the OBD log.
The current diagnostic log can be saved by clicking on this button after se-
lecting the scope of the log. The Windows dialog for saving files opens.
The sub-folder DiagnosticProtocols in the Offboard Diagnostic Information System Service direc-
tory is suggested as a save location for the Guided Fault Finding diagnostic log. SelfDiagnosticLogs is
- 444 -
the suggested directory for the OBD log. The diagnostic log is saved in HTML format and can be opened
in a web browser. This button is active after performing a diagnosis.
Note:
The data will be stored in all cases in the respective default path. If a different directory is selected, the
data will then also be stored there.
Notice:
Logs saved in the default paths will be automatically deleted after 30 days.
The Guided Fault Finding diagnostic log is automatically saved in regular intervals. The interval can be
set in the Admin area.
Cross-reference:
Refer to Save Locations Area in the chapter Administration Mode.
The current diagnostic log can be printed using this button after selecting
the scope of the protocol. A print menu opens and the printer can be selected. This button is active after
performing a diagnosis.
There are three different formats for the saved log for sending, saving and printing the Guided Fault
Finding diagnostic log.
1. The long log format contains all data from a diagnostic session.
2. The short log format contains all session data from the vehicle-side with no GFF data.
3. The function test log format contains the GFF data from the diagnostic session.
These option fields are not available in the OBD operating mode. They are displayed as inactive.
The OBD log can also be selected if a OBD was performed.
- 445 -
Figure 13.2 Diagnostic log selection
OK: the selected log type is printed or saved.
Cancel: the log type selection is canceled and the window closes.
13.1.2 Diagnostic Log

The buttons for the diagnostic log are only active when the Diagnosis operating mode is being per-
formed.
The current diagnostic log can be sent by clicking this button. An online
network connection and a login to the group systems are required. If there is currently no connection,
the data are stored temporarily and will be send the next time the group system is available after logging
into the group systems. The diagnostic log is also saved with the extension .b64 in the diagnostic log
save location for sending externally.
Cross-reference:
Refer to the chapter Logging in to Group Systems.
Translated diagnostic logs will be saved if Offboard Diagnostic Information System Service has been
configured to do so. They will end with .b64_translated.
The status of the log shipping is shown to the user in the dialog.
- 446 -
If all parameterized logs are sent successfully, the user will receive confirmation of this in a dialog.
Figure 13.3 Successfully sent diagnostic log
OK: closes the message
If an error occurred with at least one of the parameterized logs when sending, a message will be dis-
played.
Figure 13.4 Error when sending diagnostic log
Clicking this button opens a window in the folder with the saved diagnostic
logs. A diagnostic log that was already saved with in HTML or XML format or with the file extension
.b64 or .b64_translated can be copied. A b64 file can be copied from another tester this way to an exter-
nal storage device such as a USB stick for sending.
Clicking this button opens a Windows file window for opening *.b64,*
.b64_ translated files. Using this function, a diagnostic log in b64 format can be loaded from an external
storage device, such as a USB stick, and then sent if the group system connection is not available on the
original tester. This button is available immediately after starting the application.
- 447 -
The status of the log sending is shown to the user in the dialog. If exactly one file was selected, one of
the two previous messages will be displayed depending on the status. If multiple files are selected, the
following messages will be used:
If all parameterized logs are sent successfully, the user will receive confirmation of this in a dialog.
Figure 13.5 Successful diagnostic log transmission multiple selection
If an error occurred with at least one of the parameterized logs when sending, a message will be dis-
played.
Figure 13.6 Faulty diagnostic log transmission multiple selection
13.1.3 OBD Log

The buttons for the OBD log are only active when OBD is being performed.
Clicking on these screen buttons generates a new OBD log. It is not nec-
essary to generate a new log at the beginning of a diagnostic session since this happens automatically
for each diagnostic entry. New OBD logs can be generated however, during the diagnostic session.
- 448 -
Caution: when a new log is generated, the log before it is not saved automatically.
Clicking on this screen button adds the information to the current log
taken from the current OBD view.
Saves the current OBD log in XML or HTML using the Admin area
under save locations/diagnostic log settings and shows it in the system standard browser.
Cross-reference:
Refer to chapter Diagnostic Log under Administration Mode.
This screen button is active only when the current view of the OBD gen-
erates data periodically. When it is selected, the data is written periodically into the current OBD log.
- 449 -
Note:
Since a large amount of data can be generated when adding periodically, this functionality is limited to
10000 values. The user receives a dialog when this limit is exceeded asking either to end the periodic
update or to continue in a new log. In both cases the existing log is saved beforehand.
Figure 13.7 Maximum number of values exceeded
OK: saves the existing OBD log. Depending on the selection, the period recording is ended or continued
in a new log.
Ends the periodic recording of generated data. This screen button is ac-
tive only when Periodic adds was confirmed.
Cross-reference:
Refer to the chapter OBD Mode.
13.2 Data
There are three function areas in the Data menu:
 Current Tab
 Diagnostic Session
- 450 -
 Hotfix
Figure 13.8 Data button
Notice:
After an Offboard Diagnostic Information System Service software or data update, diagnostic ses-
sions from a previous version cannot be loaded because the software and DIDB versions are different.
To continue a paused diagnostic session by loading the diagnostic session data, the versions of the
software and DIDB must match.
Reference:
Refer to chapter System Environment under Administration Mode.
13.2.1 Current Tab

Current tab:
Clicking on this button creates and prints a complete view of the data for
the tab this open. For example, when printing in the control module list, a table with the displayed control
- 451 -
modules will print. The standard operating system window opens to select the printer. If the view is
empty, for example there is a tab with no content, that button will be grayed out.
Note:
An instance of Internet Explorer (IE) will be used for printing. In order to display background colors
and images correctly, IE must be configured correctly:
In the File menu - Page setup…, activate the "Print background colors and images" checkbox.
If the menu is not visible, you can also reach “Page setup…” using the “gear” in the upper right,
and then Print - Page setup…
13.2.2 Diagnostic Session

Diagnostic session:
Clicking this button can save the current diagnostic session in the sessions
subfolder so it can be continued later. This button is active after performing a diagnosis.
Note:
The session data will be stored in all cases in the default path. If a different directory is selected, the data
will then also be stored there.
Notice:
Logs saved in the default paths will be automatically deleted after 30 days.
- 452 -
Cross-reference:
Refer to the following chapter Repair Interruption.
Clicking this button can load a previously-saved diagnostic session in Off-

board Diagnostic Information System Service. This button is only available directly after starting the
application but before beginning a diagnosis.
Cross-reference:
Refer to the following chapter Continuing a Repair.
13.2.2.1 Repair Interruption
Diagnostic sessions can be paused and resumed again when there is a repair interruption. The menu
with the buttons is described in greater detail above.
Cross-reference:
Notice:
The vehicle status, meaning the status of the control modules (ability to be addressed, identification
data and DTC memory entries) must not be changed between saving and loading the diagnostic session
data.
This button pauses the diagnostic session. Offboard Diagnostic Infor-

mation System Service then opens the Stop prompt.
Figure 13.9 Query when canceling a diagnostic session
- 453 -
Save: the diagnostic session ends and the session data is saved. The save location specified in the ad-
ministration settings is suggested.
Save online: the diagnostic session ends without saving the session data.
Cancel: the dialog closes without ending the diagnostic session.
Figure 13.10 Saving a diagnostic session
Diagnostic session data has the file extension *.ses.
Save: the diagnostic session is saved.
Cancel: the diagnostic session is not saved.
Notice:
If a diagnostic session was continued and then the diagnosis is completed successfully, the diagnostic
session data that was loaded previously will be deleted.
If the VIN was entered manually, the user will be informed of any issues with continuing the repair.
- 454 -
Figure 13.11 Warning when VIN was entered manually
After saving, Offboard Diagnostic Information System Service asks if a feedback should be sent.
Figure 13.12 Feedback after Saving a Diagnostic Session
Cancel: the support request is canceled.
Send support request: the support request is sent.
The system then returns to the start location.
- 455 -
Cross-reference:
Refer to the chapter Administration Mode, Save Locations Area.
Note:
In the standard settings, diagnostic sessions are saved on the tester so a diagnostic session can also be
resumed or paused during road test mode. If a network path is entered in the settings, data is stored
temporarily during mobile operation and is compared when there is a network connection. Storage set-
tings can be changed in the Admin mode.
13.2.2.2 Continuing a Repair
To continue a repair, the diagnostic session data can be resumed. The menu with the buttons is described
in greater detail above.
Cross-reference:
More than one diagnostic session cannot be run at a time, so this button is grayed out if another session
is already running. Diagnostic sessions can only be continued if diagnostic entry was not performed.
When you click the Next button, the Windows dialog for loading a file appears.
- 456 -
Figure 13.13 Loading a diagnostic session file
Select the desired diagnostic session file.
Open: the diagnostic session is loaded.
Cancel: the diagnostic session is not loaded.
Notice:
Diagnostic sessions can only be loaded if a vehicle is currently connected and the battery has sufficient
voltage. Otherwise, loading will stop. If the diagnostic session contains a diagnostic log, it is still possi-
ble to print, send, or save it.
The user will see a message depending on whether a vehicle with battery voltage is connected.
- 457 -
Figure 13.14 No vehicle with battery voltage connected
The functionality of the buttons is identical to the following dialog and will be described there.
Notice:
After an Offboard Diagnostic Information System Service update, diagnostic sessions from a pre-
vious version cannot be loaded because the software and DIDB versions are too different. To continue
an interrupted diagnostic session by loading the diagnostic session data, the DIDB versions must
match to a large extent. The diagnostic session may also not load correctly if the structure of the session
file has changed.
Data updates to a brand only affect the loading behavior of diagnostic sessions that were created for this
brand.
In the event of a malfunction, if the diagnostic session contains a diagnostic log, it is still possible to
print, send, or save it.
The user will see a message depending on whether an out-of-date diagnostic session will be used.
- 458 -
Figure 13.15 Out-of-date diagnostic session
Closes the note window and sends the diagnostic log.
Closes the note window and opens the file selection dialog where you can select the save
location for the diagnostic log.
Closes the note window and opens the print dialog to print the diagnostic log.
OK: closes the dialog and ends loading the diagnostic session.
Cross-reference:
For additional information on printing, saving and sending diagnostic logs, refer to the chapter Log.
Notice:
The vehicle status, meaning the status of the control modules (ability to be addressed, identification
data and DTC memory entries) must not be changed between saving and loading the diagnostic session
data.
If the vehicle status changed, Offboard Diagnostic Information System Service gives an error mes-
sage indicating the changed data.
- 459 -
Figure 13.16 Error when loading a diagnostic session
In the example above, the VIN for the saved vehicle is different from the vehicle that is currently con-
nected.
The login to the group systems is activated to load a diagnostic session.
Figure 13.17 Login when loading a diagnostic session
If the data from the group systems should be used when continuing a session, a login is necessary.
- 460 -
Transfer: the login data that was entered (global user ID and password) are transferred and you are
logged into the system.
Cancel: the login to the group systems is canceled. Group system information is not available in the
session that loads.
Cross-reference:
13.2.2.3 Logging
Both the stopping and continuing of the diagnosis are recorded in the diagnostic log as their own test
steps with date and time.
If the diagnostic session is interrupted and continued on another diagnostic device, the test step for
continuing the diagnosis also contains the information about the change and the hardware ID for the
new tester.
13.2.3 Hotfix
As long as no diagnostic session was started or loaded, clicking on this button

makes it possible to import a hotfix or a workshop patch on the local hard drive from a directory. A hot
fix is available to a dealer (or workshop) individually.
The following data can be imported via a hotfix:
Equipment network objects
Knowledge base objects
Function tests
General tests
Traversal tests
Measured values tables
Specified curves
Additional documents
- 461 -
XML templates
Notice:
If a Diagnostic object is available in the Database and in the Hotfix, then the diagnostic object from
the Hotfix is always used by the processing system.
Hotfixes that are already active can be overwritten by newer ones.
A directory selection dialog opens after activating the Get screen button. The user can select a directory
here that contains the hot fix, notably the installation_index.xml file.
Figure 13.18 Selecting the hotfix directory
OK: selects the directory.
Cancel: the hotfix is not loaded.
If a hotfix was previously loaded, you are asked if it should be overwritten.
- 462 -
Figure 13.19 Hotfix already loaded
Yes: replaces the hotfix that was already loaded.
No: cancels loading the hotfix and closes the dialog.
After the Yes screen button is activated, Offboard Diagnostic Information System Service checks if
the workshop patch is in the specified directory. It not, an error message is displayed:
Figure 13.20 Error while loading the hotfix
OK: closes the dialog and ends loading the patch.
If the hotfix is available, the Offboard Diagnostic Information System Service checks if the baseline
version, on which the hotfix is based, matches with the Offboard Diagnostic Information System
Service baseline. It not, an error message is displayed:
- 463 -
Figure 13.21 Hotfix baseline version error
OK: closes the dialog and ends loading the patch. The error message that the workshop data patch could
not be performed is displayed.
Note:
If an update is performed with a loaded hot fix, the Offboard Diagnostic Information System Service
checks again after restarting if the hotfix baseline version matches the baseline version of the Offboard
Diagnostic Information System Service. It not, the error message is also displayed.
If the hotfix matches the correct format, it is copied into the application:
Figure 13.22 Copying the hotfix
It is installed then:
- 464 -
Figure 13.23 Installing the hotfix
If an error occurs, the user sees an error message:
Figure 13.24 Error while installing the hotfix
OK: closes the dialog and ends loading the patch.
Note:
If overwriting an already loaded hotfix fails, then no hotfix is active.
If the hotfix was loaded and installed successfully, the user sees:
- 465 -
Figure 13.25 Hotfix installation successful
The symbol will be displayed in the application’s status bar to indicate that a hotfix is active. Click-
ing on this symbol opens a dialog with additional information about the hotfix that was loaded.
If the hotfix is imported while a diagnostic session is active, GFF must be initialized again. The user is
notified about this with a note window.
Figure 13.26 Reinitializing GFF after loading a hotfix
Ok: ends the dialog and restarts GFF.
As soon as a hotfix is active, that is, before it was installed successfully, the
Delete button is active. This makes it possible to delete an installed hot fix or a workshop data patch. A
message appears after ending the deletion process:
- 466 -
Figure 13.27 Hotfix deleted successfully
If the hotfix was deleted while a diagnostic session is active, GFF must be initialized again.
Figure 13.28 Reinitializing GFF after deleting a hotfix
Ok: ends the dialog and restarts GFF.
Note:
The hotfix update date is not saved.
Note:
It is not possible to load diagnostic sessions that were saved with an active hotfix in Offboard Diag-
nostic Information System Session Viewer since this application does not support hotfixes.
This button enables loading a new test baseline from a source direc-
tory from Offboard Diagnostic Information System Service. It is only active outside of a diagnostic
session. This function is only available for all users.
- 467 -
If the button is pressed, a dialog window in which the source and target directory can be entered.
Figure 13.29 Loading test baseline
Source directory: the new test baseline can be selected here using the Open button.
Target directory: the location where the test baseline should be saved can be selected here. By default,
the location is the "Testbaseiline" folder in the installation directory.
Load: proceeds with the loading process.
Cancel: closes the dialog without loading the test baseline.
Before loading, the user must confirm again that the test baseline should be loaded.
Figure 13.30 Confirming loading the test baseline
Yes: begins loading the test baseline.
No: cancels the loading process and closes the dialog.
The loading is performed in the background. A symbol is shown in the status bar during the duration of
the loading process.
- 468 -
Figure 13.31 Loading in the background
A progress indicator opens if you click on the symbol:
Figure 13.32 Loading the test baseline
Close: closes the dialog and continues the loading process in the background.
Cancel: cancels the loading process and closes the dialog. A note window appears to confirm the pro-
cess.
Figure 13.33 Loading test baseline canceled by user
- 469 -
If an error occurs when loading, an error message appears, such as:
Figure 13.34 Error when loading the test baseline
OK: closes the dialog. Loading the test baseline is canceled.
If the loading the test baseline ended correctly, the user will be notified with a message.
Figure 13.35 Test baseline loaded correctly
If the test baseline loaded correctly and was activated in the Administration, the symbol will be
displayed in the application’s status bar. This will be displayed until the test baseline is deactivated
again. If you click on the symbol, a dialog with additional information about the test baseline will be
opened.
If the test environment was configured in the admin area so that there is a check for updates and if the
test baseline was activated there, then the system will search for updates during diagnostic entry.
Cross-reference:
Also refer to the chapter Test Baseline Area.
A dialog will appear if updates are found.
- 470 -
Figure 13.36 Updating the test baseline
Yes: starts the update.
No: closes the dialog without starting the update.
If a test baseline is used, diagnostic logs that are created are not sent. If sending is started using the Send
or Send ext. button, a message appears.
Figure 13.37 Sending a diagnostic log with test baseline
13.3 Extras
The following functionalities are available in the default functions Extras menu:
- 471 -
Figure 13.38 Extras Menu Content
 Search function
 Diagnostic Interface
 Test drive
 Update
 Connection Test
13.3.1 Search
The Search button opens the search function.
The search function can also be opened from the Test Overview using the magnifying glass
symbol.
Cross-reference:
Clicking the button or magnifying glass symbol opens the search template, which is empty the first time
it opens in a diagnostic session. After that, it will show the results from the previous search each time it
opens.
- 472 -
Figure 13.39 Search function form
Search terms: one or more search terms can be entered in this field. Separate multiple search terms
with commas.
Object types: the search can be restricted here to certain types such as test programs, documents,
diagnostic objects, general functions and Guided Functions. At least one object type must be selected.
Cross-reference:
Refer also to the chapters Working with GFF, Documents, DISS / TPI, Test Plan and Special Func-
tions and OBD Mode.
Search: this button is activated once a search term is entered and at least one object type is selected.
After activating, the search results are displayed under Search results.
- 473 -
Figure 13.40 Search function results display
The results are sorted according to Object type and Location.
Go to: an entry must be marked to access a result or attach the object type to the test plan. This
button is activated after that. Clicking Go to opens the marked objects.
A Document is displayed in the document view.
A Guided Function is started in the process.
A Test Program is attached to the test plan.
With a Diagnostic object, an available test is attached to the test plan.
A special function is added to the special functions.
The following illustration shows the results of a search.
- 474 -
Figure 13.41 Search result example
The user marked the test program "Connection to A/C control module" in the search results and clicked
Go to. Offboard Diagnostic Information System Service attached the affected test program to the test
plan and switches to the test plan view.
Notice:
The search function is only active after diagnostic entrance. The button or
magnifying glass is active and you cannot search for object types if there has been no diagnostic
entry.
Note:
If the search function is started from Component selection it can only search for the Diagnostic Object
object type.
13.3.2 Diagnostic Interface

It is possible to change the diagnostic hardware.
- 475 -
Note:
If no specific diagnostic interface was specified after a reinstallation, the user will be notified of this
when the application starts. The user can then specify an instance of the diagnostic interface to use in
the dialog that is described below.
Notice:
Offboard Diagnostic Information System Service supports the use of Pass-thru boxes. The driver
for the pass-thru interface will need to be installed.
Clicking diagnostic interface in the standard functions Extras

menu will call up the dialog for changing the diagnostic hardware.
The Specify VCI dialog opens. If a diagnostic interface was already specified for use and it can currently
be reached, it will be shown highlighted. The cells in the “Available” column are only filled for
VAS6154(A) diagnostic interfaces. They indicate if the devices are already being used or are available.
This is necessary because these diagnostic interfaces may also be available through Wi-Fi.
Figure 13.42 Specifying the diagnostic interface
Filter: a filter expression can be used to restrict the number of diagnostic interfaces that are displayed.
A diagnostic interface will be filtered out if the attribute value in the filter is not contained as a partial
string (not case sensitive).
- 476 -
Update: repeats the diagnostic interface recognition if the diagnostic device just connected is not dis-
played yet, for example.
VCI configuration: this button is only active only if a diagnostic interface that can be configured is
connected. When this is confirmed, a new window opens, in which the configuration of the web interface
for the diagnostic interface can be performed. Additional information regarding the configuration can
be found in the documentation for each diagnostic interface.
Use selected VCI: the selected diagnostic interface will be used in the diagnostic procedures that follow,
until the user manually changes it. The dialog will be closed.
Close: closes the dialog without switching to a new diagnostic interface (the last change remains in
effect).
Details: displays the detail information for the selected diagnostic interface. It is not possible to make
any changes in this dialog.
Figure 13.43 Detailed information regarding the current diagnostic interface
- 477 -
In the upper section of the window, the current topology relating to the diagnostic tester and diagnostic
interface and the possible access point are displayed. In the case of Wi-Fi, the Wi-Fi connection quality
is also displayed. Only the current status is displayed when the dialog opens. The values are not updated.
If a VAS6154(A) is selected, the VCI information window will also display the remaining activation
time for the Wi-Fi certificate.
If there are problems when changing the diagnostic hardware, support must be switched on.
Cross-reference:
Refer to the chapter Starting Diagnosis.
If Wi-Fi diagnostic hardware is used, Offboard Diagnostic Information System Service will indicate
the current connection quality in the Info area. One to four bars will be displayed, depending on the
quality.
Figure 13.44 Wi-Fi connection quality display
A poor connection is indicated with a red bar.
A suitable connection is indicated with two yellow bars.
A good connection is indicated with three light green bars.
An excellent connection is indicated with four dark green bars.
If there is no Wi-Fi connection to the diagnostic hardware, the symbol will be crossed out.
Figure 13.45 No Wi-Fi connection
If the diagnostic hardware is not connected by Wi-Fi, there will be no symbol under the vehicle symbol.
- 478 -
13.3.3 Test drive
A road test mode is integrated into Offboard Diagnostic Information System Service. This mobility
mode must be activated if a road test will be performed with the vehicle, resulting the tester not having
a network connection.
Notice:
Mobile operation can only be started and ended when a network connection is available.
The Road test button has two functions that depend on the current situation and its appearance changes
accordingly:
If the application is not in road test mode, this button starts the mode.
If the application is in road test mode, this button ends the mode.
13.3.3.1 Starting Road Test Mode
This button must be clicked to start road test mode.
The following message appears:
Figure 13.46 Activating the road test mode
Activate road test mode: when this button is clicked, all necessary data is copied to the tester.
Cancel: road test mode is not activated.
- 479 -
Notice:
If the diagnostic interface currently being used is a VAS6154(A) with the connection type "Wi-Fi infra-
structure", then a certain procedure is performed that can cause the switch to road test mode to fail. Refer
to the chapter 13.3.3.2.
After the copying process, a message appears indicating that the road test mode is now active.
Figure 13.47 Confirming the activated road test mode
Ok: clicking this button confirms the message.
This symbol now appears in the information area and indicates that road test mode is active.
The data generated in mobile mode is stored temporarily on the tester. Sending feedback is also possible.
Feedbacks are saved temporarily until the road test mode ends and a connection to the network is reestab-
lished. Then the system sends them.
13.3.3.2 Special Case VAS6154(A) with Connection Type "Wi-Fi Infrastruc-

ture"
If the diagnostic interface currently being used is a VAS6154(A) with the connection type "Wi-Fi infra-
structure", a message will appear indicating this.
- 480 -
Figure 13.48 Request to switch to “Wi-Fi access point”
Using the button on the VAS6154(A), the user can now switch to the connection type "Wi-Fi access
point".
Next: closes the message window.
If the switch to the connection type "Wi-Fi access point" does not occur, then the switch over to road
test mode is canceled and this message window appears.
Figure 13.49 Message about the switch to road test mode being canceled
- 481 -
13.3.3.3 Ending Road Test Mode
This button must be clicked to end road test mode.
Road test mode can be either canceled or ended.
Figure 13.50 End road test mode
Cancel road test mode: if this button is clicked, mobile data is not compared with the workshop net-
work. The data generated in road test mode is deleted.
End road test mode: clicking this button ends the road test mode and Offboard Diagnostic Infor-
mation System Service compares the mobile data with the data in the workshop network.
Cancel: road test mode is not canceled. The diagnostic session remains in road test mode.
- 482 -
Notice:
If the diagnostic interface currently being used is a VAS6154(A) with the connection type "Wi-Fi access
point" and the diagnostic interface was a VAS6154(A)with the connection type "Wi-Fi infrastructure"
before switching to road test mode, then a certain procedure is performed. Refer to the chapter 13.3.3.4.
Figure 13.51 Confirming the canceled road test mode
Ok: confirms the cancellation of road test mode.
Figure 13.52 Confirming the ended road test mode
Ok: confirms the ending of road test mode.
Symbols then appear in the Offboard Diagnostic Information System Service information area that
indicate the status of the network connection and road test mode.
Network connection is available. Road test mode can be activated.
Network connection is interrupted. Road test mode cannot be activated. A network connection
must be established first.
- 483 -
Road test mode is activated.
Road test mode is activated but the network connection is interrupted.
Notice:
If the directory in which the global configuration is stored on the server is renamed or deleted during
road test mode, a message indicating this will NOT appear when ending road test mode. Offboard
Diagnostic Information System Service will continue working with the local copy of the configura-
tion. Those responsible for the network will ensure Offboard Diagnostic Information System Service
is configured correctly in the event of any changes to the workshop infrastructure.
Access to group systems is not possible during road test mode. If the user tries to access group systems
when road test mode is active, a message will appear indicating this.
Figure 13.53 Group system access in road test mode
Continue: closes the note window and continues with road test mode. Access to group systems is still
not possible.
Cancel: cancels road test mode without comparing mobile data with the facility network and closes the
dialog.
End: ends road test mode and compares the mobile data with the facility network.
In the second two cases, the log-in dialog for the group systems appears.
- 484 -
Cross-reference:
Refer to the chapter Logging in to Group Systems.
Road test mode can only be ended if there is a network connection. If the End option was selected and
there is no network connection available, the user must decide if the road test mode should be canceled
or continued.
Figure 13.54 Ending road test mode without a network connection
Cancel: cancels road test mode without comparing mobile data with the facility network and closes the
dialog.
Continues: continues road test mode.
13.3.3.4 Special Case VAS6154(A) with Connection Type "Wi-Fi Access

Point"
If the diagnostic interface currently being used is a VAS6154(A) with the connection type "Wi-Fi access
point" and the diagnostic interface was a VAS6154(A) with the connection type "Wi-Fi infrastructure"
before switching to road test mode, then this message window appears.
- 485 -
Figure 13.55 Request to switch to “Wi-Fi infrastructure”
Using the button on the VAS6154(A), the user can now switch to the connection type "Wi-Fi infrastruc-
ture".
Next: closes the message window.
If the switch to the connection type "Wi-Fi infrastructure" does not occur, then this message window
appears.
Figure 13.56 Message about canceling the switch to infrastructure mode
OK: closes the message window.
13.3.4 Update
The software and data update made by Offboard Diagnostic Information System Service can also be
started manually for an automatic periodic check.
- 486 -
This screen button starts checking the update.
Notice:
The manual update can be performed if Offboard Diagnostic Information System Service is not in a
diagnostic session. If a diagnostic session is active, the screen button will be deactivated.
The following message appears:
Figure 13.57 Notes when starting a manual update
Yes: clicking on this button checks for updates. If there are, the Offboard Diagnostic Information
System Service closes and starts again so that the update can be performed. If there are no updates, then
there are no other steps to be performed.
No: checking for updates is stopped.
If the Yes screen button is pressed, the check is started and if necessary, updates are installed as de-
scribed in the "Update" chapter.
Cross-reference:
Also refer to the chapter Update.
13.3.5 Connection Test

Offboard Diagnostic Information System Service offers the possibility to check the connection to the
group systems.
This screen button opens the dialog for configuring the connection
test.
- 487 -
If a diagnostic entry was not performed, then a brand must first be selected. Based on this selecting,
which group system is available for the test.
Figure 13.58 Selecting a brand for the connection test
Figure 13.43. Selecting a brand for the connection test
Select: applies the selected brand.
The following dialog appears:
- 488 -
Figure 13.59 Connection test configuration
All group systems are listed in the table, for which a connection test can be performed.
Comment: depending on the parameters set, ProtoService or ProtMgmtService may be available for
sending the diagnostic log.
Place a check mark in the left column to select a group system for the test. The test result is shown in
the right column with a symbol. The following is possible:
A connection test for this group system was still not performed.
The connection test was successful.
The connection test failed.
At the beginning, all entries have the symbol .
Select all: selects all group systems available for the connection test.
- 489 -
Deselect all: remove the selection for all group systems.
No: checking for updates is stopped.
Close: closes the window.
Start: performs the connection test for all control modules selected.
If a login to the group systems for the selected brands was still not performed, then dialog to login to the
group system appears, otherwise the connection test begins directly.
During the connection test, a dialog is displayed, showing the progress.
Figure 13.60 Connection test is being performed
Cancel: cancels the test.
After the connection to all the group systems selected is checked, the dialog closes automatically and
the connection test dialog is displayed again. The test result is shown in the right column with a symbol.
13.3.6 DoIP Connection Test

Offboard Diagnostic Information System Service offers the option to check the DoIP communication
path.
This button starts the DoIP communication path test. This

button is only enabled outside of diagnosis.
To perform a self-test, a connectible, DoIP-capable diagnostic interface must be configured. If this is

not the case, one of the two error messages that follow will be displayed and the actual test will not be
performed.
- 490 -
Figure 13.61 No DoIP diagnostic interface selected
Figure 13.62 DoIP diagnostic interface cannot be connected
The test runs in two stages. If at least one DoIP vehicle that can be reached is found in the first test stage,
then the user will see a dialog indicating that the DoIP connection test was performed successfully. This
differentiates if exactly one DoIP vehicle or more were found. The test will then end.
Figure 13.63 Successful DoIP connection test
- 491 -
Figure 13.64 Successful DoIP connection test with multiple DoIP vehicles as the result
If no DoIP vehicle that could be reached was found in this stage, then a detailed diagnosis will be per-
formed in the second stage. Its results will be compiled and displayed in a dialog.
Figure 13.65 Result of second stage of DoIP connection test
If there is an error during execution in the second stage, an error message will be displayed to the user.
It will indicate that the connection test could not be completed.
- 492 -
Figure 13.66 Error during DoIP connection test
A progress dialog will be displayed for the duration of the test steps. The test steps cannot be canceled.
Figure 13.67 DoIP connection test progress dialog
13.4 Help
The Help menu contains the following function areas that provide the user with assistance if there are
problems:
 Online Help
- 493 -
 Support...
 Troubleshooting (troubleshooting guide)
Figure 13.68 Help menu
13.4.1 Online Help
After clicking on this button, online help opens in a separate window where
the help text is displayed.
Online Help can be accesses at any time when using Offboard Diagnostic Information System Ser-
vice. It opens in read mode first.
- 494 -
Figure 13.69 Online Help
If the mouse is moved into the help window, a simple navigation menu appears:
Figure 13.70 Navigation menu
Opens a Save dialog that allows you to save the help document in any location.
Opens a Print dialog to print the help document or sections of it.
Minimizes the display.
Maximizes the display.
Expands the help window with an additional menu and other display options.
- 495 -
The expanded help window is described in the information that follows.
If a help document that was prepared accordingly was installed during installation of Offboard Diag-
nostic Information System Service, the help texts can be displayed in the context of the application.
Example: if you are in the Test plan tab while performing Guided Fault Finding and click the Help
symbol, Online Help will open the Test Plan and Special Functions chapter.
Figure 13.71 Context-Based Online Help
The following information provides a more detailed explanation of the Online Help window.
- 496 -
Figure 13.72 The Online Help window
Help is displayed in Adobe Reader, which is embedded in the window. The following information
explains only the most important controls. For a more detailed description, refer to Adobe Reader help
(can be accessed with the F1 button in the help window).
The Table of contents opens which allows you to navigate through the document easily.
Opens the search window. If the term to be searched was entered in the field, the search is started
by clicking on Search.
- 497 -
Figure 13.73 Searching in Online Help
The desired information is displayed after selecting a chapter or performing a search.
Additional actions are available in the menu bar, which are described briefly below. For a more
detailed explanation of the functions, refer to Adobe Reader help.
Figure 13.74 Menu bar in Online Help
The help document can be saved, printed or sent by e-mail here.
- 498 -
This is the navigation area. You can scroll to the next/previous page with the arrow buttons. You
can also enter the desired page number directly and confirm with the Enter key.
The size of the display is increased or decreased with the + and - symbols. You can also enter the
desired zoom factor directly in the box and confirm with the Enter key.
Switches back to read mode described initially with no menu and navigation area.
Note:
The description of the online help window is based on how it is displayed using the embedded Adobe
Reader. If a different program for displaying PDFs is installed on the system as the default program,
the online help display may differ. If this is the case, it may not be possible to display the help texts in
context.
Context-based display of help also depends on whether the Offboard Diagnostic Information System
Service installation was installed with a prepared help document. If that is not the case, the first page of
the document will always appear when help is opened.
13.4.2 Support
There are several ways to send a support request or feedback or to store it locally from Offboard Diag-
In the standard functions that are always visible, a support request can be sent or stored at any time
using the Support button.
The prompt asking if a feedback should be sent is part of the process for ending a diagnostic or flash
session.
Cross-reference:
Refer to the chapter End Diagnosis.
See also chapter Flash Mode.
When the application has ended, it is also possible to send or save a feedback.
This button will open a dialog for the support request.
The options “support request via email” and “support request via support application” are available. The
system determines internally which version is offered.
- 499 -
If a dialog for a different version of support request is already open when the button is pressed, it must
first be ended. Only then will the new dialog be opened when the button is pressed again.
Figure 13.75 Open support request in a different version
13.4.2.1 Support Request via Email
Figure 13.76 Support Request via Email
This button can be used to send a screenshot of the error message

or problem with the support request. Clicking the Attach current view button attaches the current view
from Offboard Diagnostic Information System Service to the text field as a graphic.
- 500 -
Clicking the Cancel button cancels the support inquiry and does not send it. The win-
dow closes. A prompt must be confirmed to cancel the support request.
Figure 13.77 End support request
Yes: the support request is canceled and it ends.
No: the support request is not canceled.
This can be used to save a feedback with the diagnostic session, diagnostic log, screen-
shots and free text locally. Pressing the button saves the support request in the administration in the save
location defined in the target directory. The feedback file including all attachments is saved in the di-
rectory as a ZIP file. If the external tool ODIS LogHelper is installed in the loghelper folder, additional
expanded log files will be archived in the log-extended local folder.
- 501 -
Note:
When operating the Off-Board Diagnostic Information System Service application, all saved support
requests that are older than fourteen days are deleted from the save location specified in the Administra-
tion area.
Note:
In accordance with the General Data Protection Regulation (GDPR / DSGVO), the Offboard Diagnos-
tic Information System Service application deletes all support inquiries saved in the default directory
that are more than 30 days old. This occurs when the application is started and ended, as well as daily if
the application is not ended for long periods of time.
This deletion process also includes the data managed by the ODIS LogHelper.
Cross-reference:
Refer to Save Locations Area in the chapter Administration Mode.
If the selected file path cannot be accessed when saving, a message will be displayed.
Figure 13.78 Error while saving a support request.
Save under...: using this button, you can select a new target directory for support requests using a file
selection dialog.
Cancel: the process of saving the support request is canceled.
Repeat: the system will try to save again.
If there is an error when setting up or saving the archive folder, a message is displayed.
- 502 -
Figure 13.79 Error while saving a support request (2)
Save under...: using this button, you can select a new target directory for support requests using a file
selection dialog.
Cancel: the process of saving the support request is canceled.
Repeat: the system will try to save again.
Note:
A support request can be saved again. The previous generated files are deleted when saving, if necessary.
In this way, there is a maximum of one file per support request.
This button sends the support request. A support message can only be sent when the
fields "first name", "last name", "e-mail" and "telephone" are correctly filled in and an entry was selected
in the "manufacturer" selection box. Missing or invalid values are highlighted in red. If the external tool
ODIS LogHelper is installed in the loghelper folder, additional expanded log files will be archived in
the log-extended local folder.
Online Help for managing feedback is available through this button.
The Feedback sender information is located in the top left of the support window.
Figure 13.80 Information about feedback sender
- 503 -
The
 First name,
 Last name,
 E-mail address and
 Telephone number
are entered here.
If the information about the feedback sender was entered in Administration under the Support area,
this information will already be filled in. The data can be overwritten in the Send support request
dialog. If the data that overwrites the default information should be used for the next support request, it
can be changed in the Administration section under Support area.
If the user is not in a diagnostic session, then the first brand/manufacturer in the license will be auto-
matically selected in the “Manufacturer” selection box. If the license contains multiple brands, the user
can change the selection. Within a diagnostic session, the applicable manufacturer is pre-selected and
cannot be changed.
Cross-reference:
Refer to Support Area in the chapter Administration Mode.
In addition to the sender's information, the brand of the diagnostic data being used must be selected in
the Manufacturer field, even if no diagnostic session is currently running. Otherwise, the field is al-
ready prefilled according to the vehicle brand.
The error classification error classification section assigns the error to an area in the application.
Figure 13.81 Error classification feedback
Here you specify if the error involves hardware, software, a content error or a translation error or if the
error cannot be assigned to any of these errors. Only one selection is possible.
The priority section indicates how urgently the error must be corrected.
- 504 -
Figure 13.82 Error priority feedback
For information is activated when there is feedback in the form of comments and suggestions. That is
the default setting.
Limited order editing functions possible must be activated if there are inconsistencies and error mes-
sages that interfere with the procedure.
Order editing not possible is activated when this error prevents work with Offboard Diagnostic In-
formation System Service
The Attach current diagnostic session checkbox must be selected to add the current diagnostic session.
Figure 13.83 Additional attachments
Attach current diagnostic session: the current diagnostic session contains information that makes it
easier for the Offboard Diagnostic Information System Service development team to reproduce the
user feedback. The current diagnostic log is automatically attached to every feedback.
Attach current OBD log: if an OBD log was generated, then it can be added here to the feedback. This
option is deactivated if there is no OBD log.
VCI log files (VAS 6154/A only): log files from the active VCI can be prepared for the ODIS LogHelper
here. When saving the feedback, this log file is added to the feedback. This option is deactivated if no
VAS 6154/A is active.
- 505 -
Notice:
The checkbox Attach current diagnostic session must always be selected if contacting Support regard-
ing problems with GFF performance.
In the case of errors, a screenshot must be sent to ensure the error is evaluated and corrected as quickly
as possible.
If the mail server login is activated in the support/e-mail outbox server administration, the dialog to log
into the mail server appears after clicking the Send button.
Figure 13.84 Logging into the mail server for feedback
Transfer: the application logs into the mail server using the user name and password that was entered
and sends the feedback.
Cancel: the feedback is not canceled.
If incorrect access data, user name or password are entered, the Error message ODS9106E appears
with a notification about the incorrect access data.
- 506 -
Figure 13.85 Incorrect login to mail server
Transfer: the application logs into the mail server using the user name and password that was entered
and sends the feedback.
Cancel: the feedback is not canceled.
- 507 -
Cross-reference:
Refer to the chapter E-mail Outgoing Server under Administration Mode.
Notice:
If there is currently no online connection, the support inquiry is saved temporarily in the system and will
be sent the next time an online connection is available.
Figure 13.86 Feedback message with an offline connection
Ok: the message is confirmed and closed.
13.4.2.2 Support Request via the Support Application
Figure 13.87 Support Request via the Support Application
The behavior is similar to “Support request via email”.
- 508 -
The behavior is similar to “Support request via email”.
The behavior is largely the same as “Support request via email” with “Attach current
diagnostic session” and “Attach OBD log” selected. The ODIS LogHelper tool is not taken into consid-
eration here. No data is generated for that either.
This button sends the support request to the support application. It is still enabled even
if all required fields are not completed. Missing or invalid values are highlighted in red. If this button is
pressed when the required fields are not completed, an error message about the missing data will appear.
The following situations are possible:
The error description field is not one of the required fields that is missing.
Figure 13.88 Required fields in the support application not completed
Only the error description field is missing.
Figure 13.89 Error description missing in the support application
The error description field and at least one other required field are missing.
- 509 -
Figure 13.90 Required fields in the support application including error description are missing
The following message will confirm when the request is sent successfully:
Figure 13.91 Support application sent successfully
An error code/description will be provided if the request was not sent successfully:
Figure 13.92 Support application not sent successfully
General internal errors when creating the request will generate the following message:
- 510 -
Figure 13.93 Support application error when creating the request
Online Help for managing feedback is available through this button.
A suitable context must be entered in the “Subject” field. The rest of the information about the feedback
sender is the same as when using “Send support request via email”.
The error source section assigns the error to an area in the application.
Figure 13.94 Support application error source
The system pre-populates the error source depending on the mode in which the support request can be
started, and the error source can be changed.
The error priority is set in the priority section.
Figure 13.95 Support application priority
The system pre-populates the error priority with the default “For information”.
The error description is the same as the free text field when using “Support request via email”.
- 511 -
Notice:
If there is currently no online connection, the support inquiry is saved temporarily in the system and will
be sent the next time an online connection is available.
Figure 13.96Support application feedback message when there is an offline connection
Ok: the message is confirmed and closed.
13.4.3 Troubleshooting
The troubleshooting or troubleshooting guide contains suggestions for resolving common problems.
This guide is provided centrally and viewed with the operating system’s default external browser.
The troubleshooting guide can be opened in normal mode if the “Troubleshooting” item is pressed in
the help menu. The new window that opens contains additional categories for the various topics.
- 512 -
Figure 13.97 Troubleshooting guide: sample content
After logging in successfully, you will be shown the language selection before you reach the trouble-
shooting content.
13.5 Info
The Info area contains various information functions.
- 513 -
Figure 13.98 Information Area
13.5.1 New
This button opens the release notes with information about new functions that were not in the previous
version of Offboard Diagnostic Information System Service and about errors that were corrected.
The window displays automatically whenever a new installation of Offboard Diagnostic Information
System Service is started.
13.5.2 Versions
This button opens the Version information window. It contains information about the versions of Off-
board Diagnostic Information System Service that are installed, the diagnostic data, the MCD server,
the PDU API, the ECP and the ODX projects.
The version information window contains the version of the main features, among other things. In con-
trast to the product version, this version number changes with each update and clearly identifies the
software version of Offboard Diagnostic Information System Service.
- 514 -
Figure 13.99 Version information window
The window is only for displaying. Changes are not possible.
OK: closes the window.
13.5.3 Disclaimer
This button opens the Disclaimer window.
The window shows general warnings and notes that must be observed when using the Offboard Di-
agnostic Information System Service.
The disclaimer will be shown immediately each time Offboard Diagnostic Information System Ser-
vice starts.
The following illustration show the window in the various scroll bar positions.
- 515 -
Figure 13.100 Disclaimer – Table of Contents
The table of contents is not displayed in the disclaimer if it was automatically displayed when the appli-
cation started. In this case, the title of the window will be Warnings and Notes.
In addition, the “OK” button will only be active once you have scrolled or browsed all the way to the
bottom of the text.
Figure 13.101 Disclaimer – Chapter 1
- 516 -
Figure 13.102 Disclaimer – Chapter 2 (Part 1)
- 517 -
- 518 -
- 519 -
- 520 -
Figure 13.111 Disclaimer – Chapter 8.1
- 521 -
- 522 -
13.6 Trace
Various options for the Trace function are available in the Trace area.
When recording Bus traces, CAN and KLINE are logged. If there is a DoIP connection, the UDS level
(Payload Type 0x8001 "Diagnostic- Message") and the network traffic through port 13400 will be
logged according to DoIP.
The following buttons are used for this:
Starts or continues recording.
Stops recording.
- 523 -
Ends recording.
If one of the trace types cannot be activated, the other trace types will be activated. For example, if the
CAN bus trace cannot be started, the system will try to start the DoIP and the KLINE bus trace.
The trace files are stored in the trace_logs sub-folder in the Offboard Diagnostic Information System
Service directory.
The trace control sets up the file name so that existing files will not be overwritten. The file name is
composed as follows:
CAN bus trace: <VIN>_<Timestamp>_CAN.vmt
DoIP trace: <VIN>_<Timestamp>_DoIP.vmt
Kline bus trace: <VIN>_<Timestamp>_KLINE.vmt
The time stamp is in the format <YYYMMDD>T<HHMMSS>, for example "20100229T184556".
The current default directory for traces in ODIS Service is: "…\Offboard_Diagnostic_Information_Sys-
tem_Service\trace_logs". Trace files that are older than 30 days are automatically deleted by ODIS Ser-
vice in accordance with DSGVO. ODIS Service deletes all oder DoIP traces, CAN traces, and KLINE
traces. The system checks for and deletes older trace files when starting and when the application is
ended. If the application is not closed for a long period of time, then there will be an additional check
and deletion of older trace files 24 hours after the applications started and in a 24-hour cycle after that.
13.7 Legal
The Legal area provides the option of displaying the privacy policy.
Figure 13.117 Legal menu
A dialog will open for displaying the privacy policy. You can continue working with the application
while this dialog is open.
- 524 -
13.8 Missing Translations
Despite careful inspection, a particular translation may not be available in the selected language.
Missing translations in the basic information dialog are specifically marked by indicating the orig-
inal language in square brackets:
Figure 13.118 Example of missing translations in the basic information dialog
Missing translations outside of a test program are also marked by indicating the original language:
Figure 13.119 Example of missing translations in a test plan
Missing translations within a test program are also marked by indicating the original language and
a yellow highlighting:
- 525 -
Figure 13.120 Example of missing translations when performing a test program
General interface texts that have no translation are displayed in the German language.
Note:
If you notice a missing translation, create a support request.
14 Error Messages
When using Offboard Diagnostic Information System Service, error messages may be generated for
different reasons. Error messages contain information that are important for classification and the rest
of the process.
- 526 -
Figure 14.1 Error message explanations
Error ID: the ID that is assigned to the error.
Topology name: the name of the area in the application where the error occurred.
Error description: the description of the error behavior.
Ok: closes the error message.
You can search for the error message in the table Error IDs using the error ID. The right Notes column
will describe what to do next.
Notice:
The most frequent error messages occur when there are problems with the connection to the vehicle and
to the network. Checking the connection and restarting the system is recommended.
- 527 -
14.1 Error IDs
ID Displayed Error Note
This message can appear on the Orders, Vehi-

cles and PR Numbers tabs.
without ID No vehicle data was found
Check the network connection and contact Sup-
port.
The current network status is displayed in the

Info area of the user interface.
without ID The page cannot be displayed.
Check the network connection and contact Sup-
port.
If a tab was activated when there was a network

connection but it then disconnects, the following
There is no network connection availa- error message will appear:
without ID
ble.
Reestablish the network connection or contact
Support.
The sensor is not connected to the logical

ODS0001E Please contact Support.
connection.
Executing in current condition is not per-

mitted.
ODS0003E Object is in poor condition. Please contact Support.
The configuration does not match the

connected device.
An error occurred in the oscilloscope dis-

play module.
- 528 -
A trigger channel was not established for

the triggered measurement.
The GDI versions of GDI components do

not match.
ODS0008E A GDI error has occurred. Please contact Support.
An error occurred in the GDI coordina-

tor: ... (error code: ...
An error occurred in the GDI driver: ...

(error code: ...
ODS0011E A conflict with the DCD has occurred. Please contact Support.
A failure occurred when installing the de-

vice driver.
The measuring device is not established

in the GDI driver.
An error occurred when parsing the spec-

ified curve ....
No knowledge base is available for the Please check if there are updates to the software
selected model. or data.
ODS0501E
The "Flashing" mode cannot be per- If the problem persists, please contact Support
formed for this model. immediately.
- 529 -
The existing software installation is in- Please check if there are updates to the software
complete. or data.
ODS0502E
formed with the existing software. immediately.
The current brand ... is not supported by

Please check if there are updates to the software
the "Flashing" operating mode at this
or data.
time.
ODS0503E
If the problem persists, please contact Support
The "Flashing" mode cannot be per-
immediately.
formed for this brand.
There are inconsistencies within the di- Please check if there are updates to the software
agnostic data for the current brand ... . or data.
ODS0504E
formed for this brand. immediately.
There are ambiguities within the diag- Please check if there are updates to the software
nostic data for the current brand ... . or data.
ODS0505E
formed for this brand. immediately.
The selected version of the flash con-

tainer is not more current than the avail-
ODS05100 able version. To enable flashing anyway,
deactivate version control in Administra-
tion.
The flash container version could not be

determined. To enable flashing anyway,
ODS05101
deactivate version control in Administra-
tion.
- 530 -
No valid flash session could be deter-

ODS05102 mined for the current control module ... Please contact Support.
in the selected flash container ... .

ODS05103 mined for the base version used ... in the Please contact Support.
selected flash container ... .

mined in the flash container ... for the
current control module ... . To enable
ODS05104
flashing of an older version, deactivate
the EXPECTED-IDENTS in Admin-
istration.
The flash session ... could not be deter-

ODS05105 mined in the selected flash container ... Please contact Support.
for the control module ... .
The flash container ... is not available for

ODS05106 Please contact Support.
the control module ... .
An error occurred when parsing the con-

trol file ... .
Line: ... Error: ...
ODS05108 The control file ... could not be read in. Please contact Support.
The following flash requirements were

violated by control module ... : ...
ODS05110 The selected flash container ... could not Please contact Support.
be loaded. The format does not meet the
- 531 -
requirements in specification 'VW

80128-3' for ODX FLASH Container.
The flash binary files ... could not be

found.
ODS1001E Not available - timeout after ... seconds. Please contact Support.
Please restart the program.

ODS1002E The session for account ... has expired.
If the problem persists, please contact Support
immediately.
Incorrect connection and server data have been

The connection to VehicleBaseServ- entered in the administration area.
ODS1003E
iceV15 could not be established.
Please contact Support.
Please try again. If it is still not possible to login,

ODS1004E The connection to ... ended.
contact Support.
A transmission error ... occurred when

connecting to ....
ODS1005E Please try again or contact Support.
The connection was interrupted.
The address is not responding at this time.

A connection could not be established
ODS1006E
with the URI/URL.
Please try again later or contact Support.
Negative response from the server. The

error ID is ...
- 532 -
ODS1008E Negative response from the server: Please contact Support.
The error ... with the following error de-

ODS1009E scription occurred during VDS commu- Please contact Support.
nication: ...
An error occurred when configuring the

SSL connection.
There is no network connection availa-

ODS1011E
ble.
Negative response from the server. The

Please contact Support, or save or print the di-
ODS1012E error ID is ... Please save or print the di-
agnostic log manually.
agnostic log.
The version of the selected session ... is

ODS1501E not compatible with the current program Please contact Support.
version ... . The session cannot be loaded.
The type of the selected session ... is not

ODS1502E compatible with the current product ... Please contact Support.
The session cannot be loaded.
The type of selected session cannot be

identified. The session cannot be loaded.
Problems occurred when saving the diag-

nostic session. Please send a support
message via the integrated support func-
ODS1504W
tion so that the problem can be analyzed.
The diagnostic session could still be suc-
cessfully saved.
- 533 -
ODS2001E The password for account ... is invalid. Please contact Support.
ODS2002E The password for account ... has expired. Please contact Support.
ODS2003E No authentication available. Please contact Support.
ODS2004E The account ... is unknown. Please contact Support.
ODS2005E Authentication is required to access .... Please contact Support.
A login was attempted with a tester whose hard-

The hardware with ID ... is marked as ware ID was locked on the server side.
ODS2006E
locked. Please contact support.
Please obtain a new flat rate if you are an inde-

pendent market operator.
Your flat rate has expired. Please obtain
ODS2007E
a new flat rate from erWin.
Please contact Support if you are an authorized
dealer.
The maximum number of simultaneous

users sessions for your flat rate has been
ODS2008E Please log in again later.
reached. A login is only available once a
current user session ends.
Please try again. If it is still not possible to login,

ODS2009E The login was canceled.
contact Support.
The group system has reported an error:

...
- 534 -
No MCD system was found. Please

ODS2501F Please contact Support.
check the MCD system installation.
Possible causes are:
- Missing or faulty vehicle project

ODS2502E No data available.
- No suitable MCD Server runtime data
- The control module is not designed for this

function
Make sure there is a connection to the vehicle

ODS2503E The VIN could not be read or detected.
and the ignition is switched on.
ODS2504F No MCD/DTS system was found. Please contact Support.
The printer could not be accessed
The user canceled the print job.

ODS2506E Printing could not be completed.
Please check the printer settings or contact the
system administrator.
The print layout for the graphic could not

be generated.
Possible causes are:
1. The MCD server is not installed. Please install

Important MCD server libraries were not
ODS2508F the current MCD server to correct this.
found.
2. The system path does not contain the MCD
sever working directory.
- 535 -
3. The MCD server working director cannot be

accessed.
Please install the current ECF version to correct

The ECF framework for access to the this.
ODS2510F
MCD system could not be found.
There are several possible causes.
1. Another application that uses the MCD server

is active. Close those applications and restart the
application.
ODS2511F The MCD system could not be found.
2. Another application that uses the MCD server
cannot be closed. Restart the computer and try
again.
Please check if Offboard Diagnostic Infor-

The system is powering down. All activ- mation System Service functions correctly af-
ODS2512F
ities in progress will be ended. ter starting. If it does not function correctly, con-
tact Support.
Check the configuration of your diagnostic

The MCD system diagnostic interface is
ODS2513E hardware in the PDU API and modify if neces-
not configured clearly.
sary.
Error when accessing the Logical Link

Monitor for the MCD system.
ODS2515E Error when opening the MCD project. Please contact Support.
- 536 -
Please install the current MCD server to correct

There are differences between the in-
this.
ODS2519F stalled and expected version of the nec-
essary VW MCD server libraries.
The help system is not complete.

Help information cannot be displayed.
The help file ... in ... cannot be opened.

Make sure the help file is in specified location
ODS2521E
Help information cannot be displayed and there is read access to it, or contact support.
(…).
Use a supported hardware device for the vehicle

interface or contact Support.
The vehicle interface hardware used here
You can switch to supported hardware by re-
ODS2522E is not supported. Please change the diag-
moving the current hardware and then selecting
nostic interface.
a supported diagnostic interface using the “Di-
agnostic interface” button in the modes and
standard functions area.
The selected vehicle project does not

contain a vehicle for CAN-FD diagnosis.
The connected diagnostic interface does

not support a CAN-FD diagnosis.
The connected diagnostic interface does

not support a DoIP diagnosis.
The selected vehicle project does not

contain a vehicle for DoIP diagnosis.
- 537 -
Make sure the correct path was entered or con-

ODS3001E The file ... was not found.
tact Support.
Account ... does not have read authoriza- You do not have the necessary authorization.
ODS3002E
tion for the file ... Please contact Support.
Account ... does not have write authori- You do not have the necessary authorization.
ODS3003E
zation for the file ... Please contact Support.
The data storage location is full. Please contact

ODS3004E No space to write the file ...
your system administrator or Support.
Make sure the correct path was entered or con-

ODS3005E The file folder ... was not found.
tact Support.
Incorrect file name format for file ... The

format ... was expected.
The file ... in the folder ... cannot be writ-

ten.
The file ... in the folder ... cannot be

opened or read.
ODS3009E The file ... cannot be copied to .... Please contact Support.
Filter file for HexService is not available

or cannot be read.
The HexService function cannot be per-
formed.
- 538 -
An error occurred when displaying the

results of the equipment level check.
An error occurred when generating the

HTML results log.
An error occurred during the Html trans-

formation for the current vehicle project.
An error occurred when unpacking the

file.
The selected data set does not contain a

control file.
The environment variable … is incorrect,

the assigned temporary directory cannot Please contact Support or check the specified
ODS3016E
be used…… Please correct this specifi- environment variable in your user profile
cation in your user profile.
ODS3017E The data structure of the log ... is invalid. Please contact Support.
The data structure of the log data is inva-

lid.
The license does not contain the tester's

hardware ID.
The file ... in the folder ... cannot be de-

leted.
- 539 -
ODS3021E The selected data set does not contain a Please contact Support.
flash container ... .
ODS3022E The flash container ... cannot be loaded. Please contact Support.
Connection data to group systems incor-

ODS3501E rect or not available. Please contact Sup- Please contact Support.
port.
Processing the odisDiagSetupCon-

ODS3502E fig.xml has caused an error. A diagnostic Please contact Support.
interface could not be identified.
The data structure ... could not be created

or converted. Please contact support.
ODS4002E The software library ... was not found. Please contact Support.
The software library ... could not be

opened.
The parameters received for the request

from ... are incorrect.
ODS4005F Incorrect Java installation. Please contact Support.
ODS4006E The service module ... is not available. Please contact Support.
ODS4007E The service ... could not be configured. Please contact Support.
- 540 -
The session for vehicle ... could not be Please check the connection to the vehicle or
ODS4008E
reestablished. contact Support.
An internal system error has occurred.

The system is unstable. Please send a Please restart the system. If the error is not cor-
ODS4009E
feedback and contact support. Close the rected, contact Support.
system and restart.
The file structure ... contains content er-

rors.
ODS4011E The system does not support the code .... Please contact Support.
ODS4012E No session data available for saving. Please contact Support.
ODS4013E Session data cannot be reconstructed. Please contact Support.
ODS4014E Session data cannot be saved. Please contact Support.
An error occurred when entering one of

the parameters.
The entry cannot be converted into the
parameter type.
An error occurred when entering one of

the parameters.
The parameter type is not supported.
The road test mode could not be acti-

vated.
- 541 -
The license file cannot be opened or read.

Road test mode was not activated.
The license file could not be copied.

Road test mode was not activated.
The road test mode could not be deac-

tivated.
ODS5001E Test program/step ... cannot be loaded. Please contact Support.
Measurement connection is not availa-

ble.
A fatal internal test program error has oc-

curred. Test canceled. Error type: ...
Details: ...
Internal test program error. A user action

ODS5004E was attempted that is not permitted Please perform the test again or contact Support.
within a test step. Test canceled.
ODS5005E The document ... could not be loaded. Please contact Support.
The knowledge bank for the vehicle

could not be determined. Guided Fault
Finding is not possible for this vehicle.
Details: ...
A version problem was detected with the

... test.
- 542 -
Decompression of the ... test program

ODS5008E failed due to missing or invalid compres- Please contact Support.
sion. The test program could not load.
Decryption of the ... test program failed

ODS5009E due to missing or invalid encryption. The Please contact Support.
test program could not load.
Signature validation of the ... test pro-

gram failed due to a missing or manipu-
lated signature. The test program could
not load.
An error occurred during control module

communication. Because the GFF pro-
ODS5011E gram has locked the user interface, a de- Please contact Support.
cision about continuing the GFF program
cannot be retrieved.
ODS5501E Control module ... could not be found. Please contact Support.
ODS5502E Connection ... could not be opened. Please contact Support.
ODS5503E Connection ... could not be established. Please contact Support.
Unexpected result of control module

communication, method ...
Control module communication could

not be performed, method ...
- 543 -
Error ... during control module commu-

ODS5506E nication, job ..., control module ..., ECF Please contact Support.
error text: ...
Communication descriptive file ... could

not be found.
Error when reading the communication

description file.
Content of the communication descrip-

tion file invalid.
Communication job ... for control mod-

ODS5510E ule ... could not be found in the descrip- Please contact Support.
tive file.
Faulty description in method ... ... in the

descriptive file.
Error when compiling parameters for

class ...
Communication job ... for connection ...

could not be created.
Fault job description for ... in descriptive

file.
Error when providing results of control

module communication.
- 544 -
Internal error in test program: Method ...

for job ... not found.
Connection name for control module ...

could not be found.
Communication job ... could not be es-

tablished.
Request parameters for communication

job ... could not be established.
No valid value could be determined for

ODS5554E the request parameter ... in the communi- Please contact Support.
cation job ....
Unknown request parameter ... for com-

munication job ... .
The value ... for the request parameter ...

could not be changed to type ...
The value of type ... for the request pa-

rameter ... cannot be changed to type ...
The value ... for the request parameter ...

could not be entered.
Control module communication could

ODS5559E not be performed, communication job ... Please contact Support.
.
- 545 -
Error ... during control module commu-

ODS5560E nication, job ..., control module connec- Please contact Support.
tion ... .
No valid flash session for … available.

ODS5561E The flash job could not be initialized and Please contact Support.
run.
Multiple valid flash sessions for … avail-

ODS5562E able. The flash job could not be initial- Please contact Support.
ized and run.
ODS5570E Measure value table ... was not found. Please contact Support.
Entry ... in measured value table ... not

found.
Control module ... from measured value

table ... not found.
No valid entries found in measured value

table ... .
A background module has tried to access

ODS5801E forbidden methods ... in interface ... in Please contact Support.
the background.
The brand ... for the installed diagnostic

ODS6003F data is different from the brands in the Please contact Support.
certificate: ...
- 546 -
The installed software version ... is dif-

ODS6004F ferent from the version in the certificate: Please contact Support.
...
The hardware key in the certificate ...

ODS6005F does not match the hardware key for Please contact Support.
hardware ....
ODS6007F The certificate ... has already expired. Please contact Support.
ODS6008F The certificate becomes valid on ... . Please contact Support.
An error occurred when determine the dealer's

A valid contract status could not be es-
contract status from the license.
ODS6009F tablished. The diagnostic session is end-
ing.
An attempt was made to load a diagnostic ses-

You do not have authorization for the se-
sion with an unlicensed brand.
ODS6010E lected brand. Canceling the diagnostic
session loading.
An attempt was made to load a diagnostic ses-

sion when the stored contract status did not
The contract status of the diagnostic ses-
match the current contract status for the brand in
ODS6011E sion does not match your contract status.
use.
Canceling the diagnostic session loading.
Brand-based information could not be

ODS6012F determined because no current brand is Please contact Support.
available.
- 547 -
There is no information in the license for

the ... brand.
Creation or access to certificate memory

failed.
Import of the certificate file failed.

The file format is not supported.

The certificate file does not contain only
X.509 certificates.

The private key could not be determined.
Please check the password.

The validity period for the certificate
does not include the current date.

The certificate chain to be imported is not
valid.
ODS6107E The certificate hardware ID does not Please contact Support.

match the hardware ID in the current
ODIS license.
- 548 -

The certificate could not be added to the
certificate memory.
Deleting the certificate failed.

The certificate could not be deleted from
the certificate memory.
Access to the certificate memory for cli-

ent certificates failed due to a different
hardware ID.
The certificate memory will be created
again.
DIDB cannot be used due to encryption

ODS6201E or compressing. An unencrypted, un- Please contact Support.
compressed DIDB must be used.
The test baseline index file was not Please use a directory that contains a valid test
ODS6301E
found. baseline or contact Support.
Incorrect structure in test baseline index Please use a directory that contains a valid test
ODS6302E
file. baseline or contact Support.
The test baseline contains ... . This is Please use a test baseline that matches the cur-
ODS6303E
missing in the productive DIDB. rent DIDB or contact Support.
The test baseline has ... the version ... .

Please use a test baseline that matches the cur-
ODS6304E This does not match the version of the
rent DIDB or contact Support.
productive DIDB ... .
- 549 -
The test baseline is incomplete. The fol-

Please use a directory that contains a valid test
ODS6305E lowing file is missing in the storage loca-
baseline or contact Support.
tion: ... .
No description file (component delivery

manifest) found.
Please use a directory that contains a valid test
ODS6306E
baseline or contact Support.
Check the test baseline directory struc-
ture.
Copying the test baseline failed. The file Please use a directory that contains a valid test
ODS6310E
... was not found. baseline or contact Support.
Copying the test baseline failed. The file Check if there is enough memory space or if the
ODS6311E
... could not be copied. file is currently in use, or contact Support.
Copying the test baseline failed. The di- Check if there is enough memory space or if the
ODS6312E
rectory ... could not be created. directory is currently in use, or contact Support.
Copying the test baseline failed. The di- Check if the directory is currently in use, or con-
ODS6313E
rectory ... could not be deleted. tact Support.
Copying the test baseline failed. The di- Please select a different target directory or con-
ODS6314E
rectory ... already exists. tact Support.
Copying the test baseline failed. The file Check if there is enough memory space or con-
ODS6315E
could not be unpacked. tact Support.
Copying the test baseline failed. The file Check if the file is currently in use, or contact
ODS6316E
... could not be deleted. Support.
- 550 -
Please end the application and check the instal-

The database ... required for the applica- lation.
ODS6501E
tion was not found.
Error when determining the metadata for

the data adapter ....
The database ... could not be opened.

ODS6503E If the error persists, please contact Support.
Please end the application and restart.
No data adapter was found so no data- Correct or update the installation.

ODS6504E base is available. Diagnosis is not possi-
ble. Please contact Support.
Hotfix:
You cannot use the hotfix, because it was

created for another program version. Please contact Support to receive a newer or cor-
ODS6601E
rected hotfix version if necessary.
The Guided Fault Finding contained in
the hotfix may already be included in the
current program version.
The system name ... is ambiguous. The

constraints must be configured.
The base version is being used due to

ODS6901E missing diagnostic data. Address: ... - Please update the DIDB.
System name ... .
ODS6901F Check of DoIP usage canceled. Please contact Support.
- 551 -
Verification of preferred communication

channel canceled.
The diagnostic function is not supported

for this control module … .
Unknown ODX parameter … on the

MCD service ….
ODS6904F Invalid adaptation channel …. Please contact Support.
A LT3 coding string name could not be

determined.
Invalid multiple assignment of binary

ODS6906F and text coding for the control module … Please contact Support.
/ system ….
Invalid multilink control module handle.

Address: ….
ODS6908F Invalid measurement name …. Please contact Support.
ODS6909F Incorrect MCD job status: … Please contact Support.
The control module … could not be iden-

ODS6910F tified during a multi-link check in diag- Please contact Support.
nostic entry.
- 552 -
The DTC memory for the control module

ODS6911F … could be detected during a multi-link Please contact Support.
check in diagnostic entry.
No control module has responded to the

functional request.
The result of the determined SFD inquiry

structure is incorrect.
The execution of this SFD function is

only permitted with the role '<Role>’.
The SFD activation could not be success-

fully performed.
Error status: <Status>
The SFD reset could not be successfully

performed. Status: …
No offline token could be found for the

role ... and activation duration ... .
No time stamp could be determined from

the token ... .
An error occurred while reading the com-

ponents list '… (…). Details: …
An error occurred while writing the spec-

ified components list. Details: …
- 553 -
ODS6921E LL "..." not found in the vehicle project. Please contact Support.
The consistency check for the written

data set yielded a negative result.
The selected control file does not contain

data for the current control module.
An error occurred while reading the soft-

ware components list … (…). Details: …
An error occurred while writing the spec-

ODS6930E ified software composition list. Details: Please contact Support.
…
The functional call could not be executed

ODS6945E due to missing SFD activation for the fol- Please contact Support.
lowing control modules:
The functional call could not be executed

ODS6946E because the automatic SFD activation Please contact Support.
failed for the following control modules:
The functional cue will be repeated. The

automatic SFD activation was not suc-
ODS6947E cessful for all control modules. SFD acti- Please contact Support.
vation failed for the following control
modules:
ODS6953E The control module with the address

<Address> is not available in the current Please contact Support.
vehicle.
- 554 -
ODS6954E An error occurred when deactivating the

diagnostic filters.
ODS6955E An error occurred when activating the

VPE signals.
ODS6956E An error occurred when deactivating the

VPE signals.
ODS6957E An error occurred when configuring or

activating the SOD connection.
ODS6958E The SOD connection setup is not sup-

ported by the current vehicle/communi- Please contact Support.
cation path.
ODS6959E The SOD connection to RPC+ could not

be established. Error message: <Error Please contact Support.
text>
ODS6915E The SFD activation could not be success-

fully performed. Error status: <Error Please contact Support.
text>
ODS7001E The database ... cannot be opened. Please contact Support.
ODS7002E The database ... cannot be closed. Please contact Support.
ODS7003E The database ... cannot be read. Please contact Support.
ODS7004E The database ... cannot be written. Please contact Support.
- 555 -
ODS7005E The database structure is faulty. Please contact Support.
Internal database access error - no pri-

mary key defined for table ....
An increment for updating could not be

ODS7007E determined. The input directory may not Please contact Support.
have been entered correctly,
The version comparison has found an in-

ODS7008E compatibility. The specified test baseline Please contact Support.
does not match the existing environment.
The Diagnostic Information Database

(DIDB) is not available.
Diagnostic Information Database

(DIDB) inquiry failed.
The diagnostic database update failed.

ODS7503E Diagnosis performed with the old diag- Please contact Support.
nostic data. Please contact Support.
Communication with the vehicle can- Please check the connection to the vehicle or
ODS8001E
celed. contact Support.
Communication to the control module

with control address ... was faulty.
The operation on the control module with

control address ... was faulty.
- 556 -
Error message: ...
Communication to the vehicle could not Please check the connection to the vehicle or
ODS8004E
be established. contact Support.
The following error occurred during

communication with the MCD system: ...
Diagnostic hardware not found. Make Please check the connection to the vehicle and
ODS8006F
sure the hardware is connected correctly. the diagnostic hardware or contact Support.

communication with the MCD system:
Error code: ...
Error code description: ...

communication with the vehicle:
Error code: ...
The DTC memory could not be read dur-

ing communication with the control
ODS8009E module ... Please contact Support.
Error description: ...
The control module canceled the opera-

tion. Possible causes are:
incorrect or missing login
- 557 -
other
The control module with control address

... is not installed or is not responding.
An error occurred during communication

with the vehicle:
The control module response contains
implausible data.
An error occurred when loading/filter-

ing/checking the flash session. A possi-
ble cause could be incompatibility be-
tween ODX data and flash data.
The diagnostic project ...is not available.

ODS8014E Please check the installation of your soft- Please contact Support.
ware.
Communication to the vehicle could not

be reset.
Possible cause: there may be active diag-
nosis jobs.

with the vehicle:
Check if the ignition is switched on.
An error occurred when initializ-

ing/deinitializing the hardware on: ...: ...
- 558 -
with the following manufacturer error

description: ...

with the vehicle:
The control module response contains
implausible data.

with the vehicle:
The control module did not accept the
code.

with the vehicle:
The operation on the control module was
faulty.

with the vehicle:
The control module ended the operation.

with the vehicle:
The entry is outside the valid value range.
An error occurred when entering or inter-

preting data. Possible causes are:
One of the entries is outside the valid
value range.
- 559 -
The control module is delivering implau-

sible data.
The MCD system is reporting the follow-

ing error:
Error code: ...

with the MCD system:
The MCD job ... did not deliver any re-
sults after completion.
Access to the communication parameters

ODS8025E for control module ... is not possible be- Please contact Support.
fore the connection is established.
The communication to the vehicle was

interrupted.
Possible causes: vehicle is not connected

or the battery is not connected.
Error code: ...
Note: ...
The connection to the control module ...

- ... could not be established due to exist-
ing communication orders.
You can attempt to connect again once
communication with this control module
ends.
- 560 -
Communication protocol ... is not sup-

ported.
ODS8029E No Gateway is available. Please contact Support.
ODS8030E No Bus master is available. Please contact Support.
There is an error in the available diagnos-

tic data.
Diagnostic entrance cannot be per-
formed.
The selected mode cannot be used.

There are no other modes available to
continue diagnostic entrance.
The selected mode cannot be used.

Diagnostic entrance must continue with a
different mode.
There is no information available for the

internally identified vehicles.
Diagnostic entrance canceled.
Communication to the control module

with control address ... was faulty.
The attempt to connect is being blocked
by another control module.
- 561 -
No suitable OBD data are available in the

vehicle project.
The vehicle is not responding to OBD

functions.
The software and database content is in-

correct.
An error occurred when downloading the

software and database.
An error occurred when uploading the

software and database.
A connection to the MirrorServer2 can-

not be established.
There is not enough memory space for

ODS9005E the update. ... KB are needed. Only ... KB Please contact Support.
are available.
The update requires Administrator rights.

ODS9006E Please contact the Administrator and Please contact Support.
then perform the update.
ODS9007E The update has failed or was canceled. Please contact Support.
Updates were encountered that are not

Reinstall the current version of Offboard Diag-
compatible with the version installed.
ODS9008E nostic Information System Service or contact
Please reinstall using the updated ver-
Support.
sion.
- 562 -
The current update could not be down-

loaded within the last X days. Make sure
Make sure there is a network connection or con-
ODS9009W the diagnostic tester is connected to the
tact Support.
Internet or to the CPN and the update
server is configured correctly.
Insufficient disk space to download. X

Select a different directory on a different hard
kB is needed, but only Y kB is available.
ODS9010E drive disc or partition or clean the hard drive
Please select a different to directory
disc to create more disk space.
download.
The update is not complete. All required

ODS9011E updates are not available. Please contact Please contact Support.
Support.

not be established. An error occurred Make sure there is a network connection and
ODS9012E when reading the local update configura- that the network settings are configured cor-
tion. Please check the settings for Mir- rectly or contact Support.
rorServer2.
The update contains errors in the data

structure. Please contact Support.
An error occurred when installing the up- Please try to download and install again or con-
ODS9014E
date. Please try again. tact Support.

Make sure there is a network connection and
not be established. An error occurred
ODS9015E that the network settings are configured cor-
when reading the removed update con-
rectly or contact Support.
figuration. Please contact Support.
The specified version for update … is in-

valid.
- 563 -
The specified version of the update ... is

not provided by the mirror server.
When downloading the update, the fol-

Please change the mirror server or contact Sup-
ODS9018E lowing files cannot be download without
port.
errors.
The selected mirror server has no availa- Please change the mirror server or contact Sup-
ODS9019E
ble languages. port.
The installation language cannot be dese-

ODS9020E Please select at least one installation language.
lected.
Maximum {...} languages can be se- Please select only the maximum number of se-
ODS9021E
lected. lectable languages.
ODS9022E No installation language was selected. Please select an installation language.
The following languages are not availa- Please change the mirror server or contact Sup-
ODS9023E
ble on the mirror server. port.
The mirror server … requires an authen-

ODS9024E tication. Please enter the user name and Use a user name and password when logging in.
password.
The mirror server … is reporting a faulty

query. Please contact Support.
The mirror server … is reporting an in-

ternal error. Please contact Support.
- 564 -
The mirror server … does not answer Please repeat the action later. If the error occurs
ODS9027E within the prescribed time. Please repeat over a longer period of time, please contact Sup-
the action later. port.
Unexpected HTTP return value … from

the mirror server. Please contact Support.
Check the mirror server specification; the mirror

Error during post setup for the product ...
ODS9029E server being used may not have information for
No components were found.
the product available.
A serious error occurred when updating

ODS9030E the application. Please uninstall the ap-
plication and then reinstall it.
The computer must be restarted to update

ODS9031E
the application. Please restart.
There is a new version of the application

available. The new version cannot be in-
stalled via an update. Please uninstall this
ODS9032E
version and then
reinstall with the latest version.
The local computer name could not be

identified.
The configured mail server ... is un- Please contact the mail server administrator or
ODS9102E
known. your provider.
ODS9103E No mail server specification configured. Please add the specification or contact Support.
- 565 -
E-mail(s) failed to send.

Make sure there is a network connection or con-
ODS9104E
tact Support.
The original error message text is: ...
Error when generating e-mail.

Please contact the mail server administrator or
ODS9105E
your provider.
Invalid sender e-mail address ... found.
Message to the mail server ... failed.

Please correct the user name or password or con-
ODS9106E tact the mail server administrator or your pro-
Please check the user name and/or pass-
vider.
word.
No standard e-mail program is defined or The use of an external e-mail program was con-
installed. For this reason the e-mail could figured, but was not made available.
ODS9107E not be created.
Please install an e-mail program, or ask your ad-
ministrator to install an e-mail program.
ODS9201E Dealer portal not available. Please try again later or contact Support.
ODS9202E Procedures could not be loaded. Please try again later or contact Support.
Creating test plan without customer

ODS9203E Please try again later or contact Support.
code.
ODS9204E DISS codes could not be loaded. Please try again later or contact Support.
ODS9205E Wiring diagram list cannot be displayed. Please try again later or contact Support.
ODS9206E Wiring diagram cannot be loaded. Please try again later or contact Support.
- 566 -
ODS9207E Vehicle data cannot be loaded. Please try again later or contact Support.
System for immobilizer adaptation sys-

tem (FAZIT) not available.
ODS9209E Possible errors cannot be loaded. Please try again later or contact Support.
ODS9210E Coding system (System42) not available. Please try again later or contact Support.
Flashing system (System42) not availa-

ble.
Login could not be completed. No access

to dealer portal.
The procedure cannot be completed. The

group system is not available.
The data are stored temporarily and sent

automatically when the group system is
available again and the Offboard Diag-
nostic Information System Service is
started on this computer.
Key transponder reception system cannot

be reached.

- 567 -
Diagnostic log reception system cannot

be reached.

The diagnostic log cannot be saved. The

storage location is not available.
The log is encrypted and automatically

stored temporarily once the save location
is available again and Offboard Diagnos-
tic Information System Service is started
on this computer.
Current equipment level reception sys-

tem cannot be reached.

The template ... is missing in the GFF

data. The test is canceled.
No URL was found in the configuration

data for the alias ...
The test is canceled.
- 568 -
Could not check for open campaigns for

the identified vehicle. Please check on Please check on the "Campaigns" tab in the
ODS9301E
the "Campaigns" tab in the "Info" area "Info" area for open campaigns.
for open campaigns.
ODS1013E The error '{...}’ occurred during AVx Please try again later or contact Support.
communication. Error description: {...}
The error '{...}' occurred during the ODX

ODS1014E update communication. Error descrip- Please try again later or contact Support.
tion: {...}
During the ODX update communication

ODS1015E for data package '{...}’, the error '{...}' Please try again later or contact Support.
occurred. Error description: {...}
ODS1016E The authorization for {...} has failed. Please try again later or contact Support.
ODS1017E The registration in the portal has failed Please try again later or contact Support.
with the following error: '{...}'.
The response from the portal '{...}’ is in-

ODS1018E complete and cannot be used. Missing Please try again later or contact Support.
'{...}’.
ODS1019E Internal error during authorization. Please contact Support.

No suitable car dealership context could

ODS1020E be determined in the portal '{...}’ based Please contact Support.
on the license information. Please contact
Support.
- 569 -
Not all configurations parameters could

ODS1021E be determined for the use of the SoftPSE Please try again later or contact Support.
certificate.
ODS1022E No valid '{...}' certificate could be found. Please try again later or contact Support.
The login could not be completed suc-

ODS1023E cessfully. Error description: {...} Error Please try again later or contact Support.
code: {...}, Location: {...} Time: {...}
There are differences between the in-

ODS2509F stalled and expected version of necessary Please try again later or contact Support.
Softing libraries. Please install the cur-
rent Softing version to correct this.
ODS2527E Web interface cannot be accessed. Please try again later or contact Support.
ODS3023E Error when accessing the file folder {...} Please try again later or contact Support.
Reason for access: {...}
The following data cannot be erased in

ODS3024E file folder {...}: {...} Reason for erasing: Please try again later or contact Support.
{...}
Only {...} free bytes are available on the

ODS3025E drive {...}. {...} free bytes are needed for Please try again later or contact Support.
unzipping.
ODS9220E The NAS-OE assist cannot be reached. Please try again later or contact Support.
Check your connection settings.
The vehicle project does not contain any

ODS05112 variants for the defined diagnostic ad- Please try again later or contact Support.
dress(es) '{...}' in the JSON control file.
- 570 -
The diagnostic address '{...}’ is a compo-

ODS05113 nent of a connected system. Please first Please try again later or contact Support.
load a JSON control file.
No flash data for the mandatory unit(s)

ODS05114 '{...}’ is available. Please load the flash Please try again later or contact Support.
data for this unit/these units.
The selected JSON control file '{...}'

ODS05115 could not be loaded. The format does not Please try again later or contact Support.
match the JSON schema '{...}'.
The selected JSON control file '{...}’

ODS05116 contains the control module '{...}’, which Please try again later or contact Support.
is contained in another loaded JSON con-
trol file.
ODS05117 The selected JSON control file '{...}' Please try again later or contact Support.
does not exist.
ODS05118 No control module present for the flash Please try again later or contact Support.
container '{...}’
ODS05119 Multiple control modules present for the Please try again later or contact Support.
flash container '{...}'
ODS05120 Importing of flash control files was can- Please try again later or contact Support.
celed.
ODS05121 The zip file does not contain any flash Please try again later or contact Support.
sessions for the current vehicle project.
ODS05122 The flash container '{...}’ cannot be re- Please try again later or contact Support.
named to an FRF file.
- 571 -
Not all required diagnostic data can be

ODS5563E determined for the access authorization. Please try again later or contact Support.
The flash job '{...}' could not be per-
formed.
ODS6902E The diagnostic function is not supported Please try again later or contact Support.
for this control module '{...}’.
ODS6903E Unknown ODX parameter '{...}’ on the Please try again later or contact Support.
MCD service'{...}’.
ODS6904E Invalid adaptation channel '{...}’. Please try again later or contact Support.
ODS6905E A LT3 coding string name could not be Please try again later or contact Support.
determined.
Invalid multiple assignment of binary

ODS6906E and text coding for the '{...}’ control Please try again later or contact Support.
module / '{...}’ system.
ODS6907E Invalid multilink control module handle. Please try again later or contact Support.
Address: '{...}’ / link name: '{...}’.
ODS6908E Invalid measurement name '{...}’. Please try again later or contact Support.
ODS6909E Incorrect MCD job status: '{...}’ Please try again later or contact Support.
The '{...}’ control module could not be

ODS6910E identified during a multi-link check in di- Please try again later or contact Support.
agnostic entry.
The DTC memory for the '{...}’ control

ODS6911E module could be detected during a multi- Please try again later or contact Support.
link check in diagnostic entry.
- 572 -
Offline activation was not executed suc-

ODS6924E cessfully due to an invalid reload protec- Please try again later or contact Support.
tion in the offline token that was used.
The expired offline tokens were deleted.
ODS6925E The SFD function is not supported. Error Please try again later or contact Support.
status: {...}
ODS6926E End-to-end encryption could not be Please try again later or contact Support.
started. Error status: {...}
ODS6927E End-to-end encryption could not be com- Please try again later or contact Support.
pleted. Error status: {...}
The amount of data to be secured is too

ODS6928E large. Only one data set per cycle is sup- Please try again later or contact Support.
posed at this time.
ODS6931E The use case '{...}’ is not supported by Please try again later or contact Support.
the end-to-end encryption.
The selected offline token does not con-

ODS6932E tain all required data identifiers for the Please try again later or contact Support.
end-to-end encryption. Missing data
identifiers: {...}
The selected offline token contains all

additional data identifiers for the end-to-
ODS6933E end encryption that were not selected in Please try again later or contact Support.
the diagnostic function. Additional data
identifiers: {...}
Offline token selection for end-to-end

ODS6934E encryption was canceled. The selected Please try again later or contact Support.
data will not be written.
- 573 -
ODS6935E End-to-end encryption was canceled. Please try again later or contact Support.
The selected data will not be written.
Not all diagnostic data from the offline

ODS6936E token is available for the current control Please try again later or contact Support.
module. The loading process was can-
celed.
ODS6937E No end-to-end offline token available. Please try again later or contact Support.
No end-to-end secured diagnostic data

ODS6938E was selected. The offline token was not Please try again later or contact Support.
saved.
The current OBD function is not sup-

ODS6939E ported by the selected offline token. The Please try again later or contact Support.
loading process was canceled.
The selected control file contains a mix

that is not permitted from the applicative
ODS6940E data sets with secured RFIDs and Boot- Please try again later or contact Support.
loader data sets for the current control
module. The selected data will not be
written.
No respective offline token is present for

ODS6941E the OBD function and the data to be writ- Please try again later or contact Support.
ten. The writing process was canceled.
The following upload requirements were

ODS6942E violated by the '{...}’control module: Please try again later or contact Support.
{...}
The saved offline token for the dummy

ODS6943E VIN '{...}’ is not permitted. A unique Please try again later or contact Support.
VIN is required.
- 574 -
ODS6944E The vehicle SFD activation was can- Please try again later or contact Support.
celed.
ODS6948E The maximum number of 8 multiple Please try again later or contact Support.
identifications is exceeded.
ODS6949E The diagnostic data '{...}’ could not be Please try again later or contact Support.
determined.
ODS6950E The action was faulty. HTTP status Please try again later or contact Support.
'{...}’.
ODS6951E The answer from RPC+ does not contain Please try again later or contact Support.
any data in the ‘data’ field.
The answer from RPC+ contains data ob-

ODS6952E jects the error status in the ‘data’ field. Please try again later or contact Support.
{...}
ODS6960E Error when parsing the JSON-Response Please try again later or contact Support.
from the RPC+.
ODS6961E Error when creating the JSON-Requests Please try again later or contact Support.
for the RPC+.
ODS6962E Error when sending the requests to the Please try again later or contact Support.
RPC+.
No UUID extractable from the ‘location’

ODS6963E header data attribute from the RPC+ Re- Please try again later or contact Support.
sponse. location: '{...}’
ODS6964E Error when starting the file servers. Please try again later or contact Support.
- 575 -
ODS6966E The JSON file '{...}' could not be saved. Please try again later or contact Support.
ODS6967E Performing the SFD activation was can- Please try again later or contact Support.
celed.
ODS6968E The '{...}’ web method is not supported Please try again later or contact Support.
by the current '{...}’ web service.
ODS6969E Error when requesting the RPC+ URL. Please try again later or contact Support.
Table 14.1 Error IDs table
14.2 Additional Error Messages

14.2.1 Firewall Messages
When performing updates from Offboard Diagnostic Information System Service, there may be a
firewall message.
- 576 -
Figure 14.2 Windows firewall message
Click the Do not block button to confirm this message.
Notice:
If the Continue blocking button is clicked, the firewall will block the update from being performed and
the program cancels the attempt.
14.2.2 Browser Messages

Browser security warnings may appear in some cases. These messages appear after starting Offboard
Diagnostic Information System Service and calling up certain tabs for the first time that access a web
group interface.
- 577 -
Figure 14.3 Browser security warning
Figure 16.3. Browser security warning
Click the Yes button to confirm this message so the page can be displayed correctly.
If the No button is clicked, the page can only be displayed correctly after restarting Offboard Diagnostic
Information System Service and clicking the Yes button.
15 Keyword Index
Actual installation........................................................................................................................ 120, 127

Actuator code ...................................................................................................................................... 289
Adaptation ........................................................................................................................................... 236
Add in cycles, OBD log .................................................................................................................. - 449 -
Add, OBD log.................................................................................................................................. - 449 -
Admin .................................................................................................................................................... 67
Administration ................................................................................................................................. - 389 -
Anti-virus protection ....................................................................................................................... - 419 -
Basic Setting ........................................................................................................................................ 273
Binary coding ...................................................................................................................................... 254
Bluetooth interface ................................................................................................................................ 29
Brand Design ................................................................................................................................... - 393 -
Browser error message .................................................................................................................... - 577 -
Bus master ........................................................................................................................................... 244
Cancel diagnosis .................................................................................................................................... 88
Certificate .............................................................................................................................................. 30
- 578 -
Certificate selection ............................................................................................................................... 30
Change diagnostic hardware ................................................................................................................. 88
Change display format......................................................................................................................... 127
Change system language ................................................................................................................. - 395 -
Client Area ............................................................................................................................................ 66
Client certificate .............................................................................................................................. - 432 -
Code ...................................................................................................................................................... 64
coded ................................................................................................................................................... 122
Coding ................................................................................................................................................. 250
Coding assistant................................................................................................................................... 148
Coding Bus Master .............................................................................................................................. 244
Coding status ....................................................................................................................................... 122
Complete System DTC Memory ......................................................................................................... 311
Complete test ....................................................................................................................................... 158
Component Selection .......................................................................................................................... 186
Components List.......................................................................................................................... 118, 316
Concerns .............................................................................................................................................. 147
Contact Data .................................................................................................................................... - 416 -
Control Module List ............................................................................................................................ 124
Control module, installed .................................................................................................................... 123
Control modules .......................................................................................................... 124, 127, 138, 227
Control Module-Specific Functions .................................................................................................... 235
Copying, diagnostic log................................................................................................................... - 447 -
Creating a Test Plan ............................................................................................................................ 144
Customer code ..................................................................................................................................... 148
Cycle, update ......................................................................................................................................... 40
Data menu ............................................................................................................................................. 70
Database save location .................................................................................................................... - 407 -
Dealer Data ...................................................................................................................................... - 406 -
Dealers ................................................................................................................................................... 64
Design.............................................................................................................................................. - 393 -
Diagnosis ............................................................................................................................................... 67
Diagnostic connection ........................................................................................................................... 64
Diagnostic connection, legal ............................................................................................................... 326
Diagnostic Interface .............................................................................................................................. 27
Diagnostic interface selection ............................................................................................................... 27
Diagnostic Log ................................................................................................................................ - 412 -
Diagnostic Object ........................................................................................................................ 153, 337
Diagnostic quick entrance ................................................................................................................... 203
Diagnostic session save location ..................................................................................................... - 409 -
Display format ..................................................................................................................................... 127
Display, OBD log ............................................................................................................................ - 449 -
DISS concerns ..................................................................................................................................... 147
Documents ................................................................................................................................... 212, 219
DTC Memory .............................................................................................................................. 134, 269
DTC memory entry ............................................................................................................................. 134
DVD ...................................................................................................................................................... 24
Elimination counter ............................................................................................................................. 136
E-mail Outgoing Server................................................................................................................... - 417 -
E-mail outgoing server, setting........................................................................................................ - 417 -
E-mail size restriction ...................................................................................................................... - 419 -
End Diagnosis........................................................................................................................................ 88
End module ......................................................................................................................................... 198
- 579 -
Engine Select ......................................................................................................................................... 92
Equipment ........................................................................................................................................... 139
Equipment List .................................................................................................................................... 139
Equipment versions ............................................................................................................................. 139
Erasing DTC memory entries .............................................................................................................. 134
Erasing the DTC memory.................................................................................................................... 311
Error classification .......................................................................................................................... - 499 -
Error Messages ................................................................................................................................ - 526 -
Event code ................................................................................................................................... 134, 269
Event text............................................................................................................................................. 134
Extras menu ........................................................................................................................................... 70
Feedback............................................................................................................................. - 416 -, - 499 -
Firewall................................................................................................................... 40, 48, - 419 -, - 576 -
Flash entrance ...................................................................................................................................... 324
Flashing ......................................................................................................................................... 67, 323
Frequency counter ............................................................................................................................... 136
Fullscreen .............................................................................................................................................. 73
Function description ............................................................................................................................ 181
Gateway ............................................................................................................................... 118, 178, 244
Gateway Coding .................................................................................................................................. 178
Gateway components list..................................................................................................................... 118
GFF.............................................................................................................................................. 141, 158
Global Configuration....................................................................................................................... - 403 -
Guided Fault Finding................................................................................................................... 141, 158
Guided function ................................................................................................................................... 133
Hardware part number ......................................................................................................................... 283
Hardware version ................................................................................................................................ 283
Help menu ............................................................................................................................................. 71
Hotfix .............................................................................................................................................. - 461 -
Identification ....................................................................................................................................... 282
Identifying Control Modules ............................................................................................................... 118
Ignition .................................................................................................................................................. 64
Importer ................................................................................................................................................. 64
Independent market operators ............................................................................................................... 97
Info .................................................................................................................................................. 64, 67
Info area................................................................................................................................................. 64
Info menu ........................................................................................................................................ 71, 72
Installation status ................................................................................................................................. 118
Installation, offline ................................................................................................................................ 24
Installation, online ................................................................................................................................. 23
Interface ................................................................................................................................................. 57
K line adapter ...................................................................................................................................... 107
Keyboard ............................................................................................................................................... 74
KWP .................................................................................................................... 236, 246, 251, 273, 287
Language ......................................................................................................................................... - 395 -
Load, diagnostic session .................................................................................................................. - 453 -
Mail server....................................................................................................................................... - 417 -
Manufacturer ......................................................................................................................................... 92
Maximum installation.................................................................................................................. 124, 127
Measured Value Block ................................................................................................................ 284, 308
Measured Values ................................................................................................................. 173, 284, 308
Measuring Equipment ............................................................................................................... 67, - 389 -
Memory status ..................................................................................................................................... 134
- 580 -
Mileage ................................................................................................................................................ 136
Mirror Server 2 ................................................................................................................... - 431 -, - 432 -
Missing Translations ....................................................................................................................... - 525 -
Model .................................................................................................................................................... 92
Model year............................................................................................................................................. 92
Modes .............................................................................................................................................. 63, 67
Mouse .................................................................................................................................................... 74
Network ................................................................................................................................................. 64
Networking Diagram ........................................................................................................................... 127
New, OBD log ................................................................................................................................. - 448 -
not coded ............................................................................................................................................. 122
Notes................................................................................................................................................ - 515 -
OBD .................................................................................................................................................... 317
On Board Diagnostic, Context Menu Button ...................................................................................... 133
Online Help ..................................................................................................................................... - 494 -
Operating Modes menu ......................................................................................................................... 67
Operation ............................................................................................................................................... 74
Output Diagnostic Test Mode ............................................................................................................. 287
Part number ......................................................................................................................................... 283
Pass-thru ................................................................................................................................................ 27
Perform test ......................................................................................................................................... 158
Performing a complete test .................................................................................................................. 158
Performing a test program ................................................................................................................... 158
Platform ................................................................................................................................................. 27
Platform selection .................................................................................................................................. 27
PostSetup ............................................................................................................................................... 33
Print ................................................................................................................................................. - 451 -
Print, diagnostic logs ....................................................................................................................... - 445 -
Priority ............................................................................................................................................. - 499 -
Protocol menu........................................................................................................................................ 69
Provider ........................................................................................................................................... - 417 -
Proxy server..................................................................................................................................... - 417 -
Quick Entrance .................................................................................................................................... 203
Read DTC memory again .................................................................................................................... 133
Readiness code .................................................................................................................................... 199
Reading/Entering the VIN ..................................................................................................................... 92
Readout plan ........................................................................................................................................ 123
Remote diagnostic head......................................................................................................................... 29
Remote diagnostic head documentation ................................................................................................ 29
SAE code ............................................................................................................................................. 269
Save, diagnostic session .................................................................................................................. - 452 -
Screenshot ............................................................................................................................................. 74
Search .............................................................................................................................................. - 472 -
Select version ...................................................................................................................................... 127
Selective output diagnostic test mode ................................................................................................. 289
Self-diagnosis ................................................................................................................................ 67, 227
Sending externally, diagnostic log .................................................................................................. - 447 -
Sending, diagnostic log ................................................................................................................... - 446 -
Sequential output diagnostic test mode ............................................................................................... 289
SMTP .............................................................................................................................................. - 417 -
Software part number .......................................................................................................................... 283
Software version .................................................................................................................................. 283
Special Functions ................................................................................................................................ 157
- 581 -
Specified installation ........................................................................................................................... 120
Sporadic/static ..................................................................................................................................... 136
Standard functions ................................................................................................................................. 63
Standard order ..................................................................................................................................... 109
Status area ............................................................................................................................................. 73
Status Line ............................................................................................................................................. 73
Support ............................................................................................................................... - 415 -, - 499 -
Support request ................................................................................................................................ - 499 -
Symptom ............................................................................................................................................. 134
System Environment ....................................................................................................................... - 401 -
System identification ........................................................................................................................... 283
System name........................................................................................................................................ 283
System Requirements ............................................................................................................................ 22
Tab bar................................................................................................................................................... 66
Table of Contents .................................................................................................................................. 19
Task ..................................................................................................................................................... 109
Test Baseline ................................................................................................................................... - 441 -
Test cancellation .................................................................................................................................. 158
Test plan .............................................................................................................................................. 158
Test program........................................................................................................................................ 158
Touchscreen........................................................................................................................................... 74
Trace ................................................................................................................................................ - 523 -
Transport Mode ................................................................................................................................... 314
Trust certificate................................................................................................................................ - 437 -
UDS ..................................................................................................................... 239, 248, 253, 275, 290
Update ....................................................................................................................................... 40, - 397 -
User interface ........................................................................................................................................ 63
VAS5054 ............................................................................................................................................... 29
vehicle basic features............................................................................................................................. 92
Vehicle engine ....................................................................................................................................... 92
Vehicle features, flashing .................................................................................................................... 328
Vehicle ID ............................................................................................................................................. 64
Vehicle status ........................................................................................................................................ 88
Vehicle-Specific Functions ................................................................................................................. 311
Version .................................................................................................................................................. 92
Warnings ......................................................................................................................................... - 515 -
Wi-Fi certificate .................................................................................................................................... 61
Windows security warning .............................................................................................................. - 576 -
Work area .............................................................................................................................................. 66
16 Glossary
Amplitude
The maximum value that the amount of deflection of an oscillation in an alternating current (for exam-
ple, in AC voltage) can reach.
Adaptation
- 582 -
This service enables interactive changing of parameters in the control system that is being addressed.
The changed values (for example, correction values for idle speed) can be stored permanently in the
control modules. The user has the option to change the value and to transfer it into the temporary memory
(RAM) to check on the control module. The control module applies the new values to its outputs and
the user can check the system's reaction. If the right correction value is found, the tester causes the
control module to transfer the value and the workshop code into the writable hard drive (EEPROM).
In contrast to basic setting, the affected control circuit is closed. With the adaptation, system-specific
parameters are determined and stored in the vehicle system.
ASAM-ODX
Association for Standardization of Automation and Measuring Systems (http://www.asam.net)
Open Diagnostic Data Exchange
Baseline
A complete version of a DIDB. It contains all required artifacts, tests programs and databases.
Mode
Each of the tester's basic functions that can be accessed from the start screen: "Flashing", "Diagnosis",
"Information" and "Admin". Each operating mode is divided into a range of individual functions.
Bluetooth
An industry standard for wireless transmission between devices over short distances.
Client
A program on the PC that enables the connection to a server. A network client is, for example, a program
to that establishes the connection to a server in the network so that the PC can be used as a work station
in the network.
Diagnosis
Diagnostic connection
Connection socket for the diagnostic cable on the tester or in the vehicle.
Diagnostic Object
Collective term for functions, build groups or components that can be diagnosed and are represented in
the diagnostic object tree. Not to be confused with diagnostic bus object (definition in DES-VW A11.0
owner's manual) An object (function, component or build group) on which the diagnostic function is
used.
- 583 -
Diagnostic objects should be named based on the Mutterliste. Even if this is not currently the case, it
must be done in the future so that wiring diagrams on the tester can be requested according to Mutterliste
terms from Elsa.
Diagnostic Log
The diagnostic log contains a list of control modules with corresponding DTC memory entries, DISS
codes and text created manually.
DIDB
Direct current measurement (inline current measurement)
Current measurement in which the tester is inserted directly into the circuit like an ampere meter. Op-
posite: inductive current measurement via a clamp connected to the cable.
DISS
The DISS system (Direct Information System Service) is used to record vehicle concerns and support
the service core process.
- Recording concerns
- Reporting existing concerns
DTC
Diagnostic Trouble Code. An entry in the fault memory. It consists of the fault location, fault types and
ambient conditions, if necessary.
ECU
Electronic Control Unit: electronic control module.
Self-diagnosis
Vehicle systems are OBD-capable. This means they have the ability to continually check their own
functions, connected sensors and actuators. A malfunction results in the entry of an error code in the
vehicle system DTC memory. The tester contains all malfunctions in its knowledge base so that it can
allocate the error code to an error type and location after reading the DTC memory and then create a test
sample based on that.
Own test plan
Diagnostic strategy where the user selects possible faulty functions or components. If faults in the vehi-
cle systems are detected during the diagnostic sessions or a concern is entered, the test plan always
differentiates between the system test plan and the user's own test plan.
End module
- 584 -
An end module can consist of several function tests that start automatically when exiting Guided Fault
Finding. For example, feedback may be sent to the vehicle manufacturer.
Event code
Event location
DTC Memory
Rules of thumb
Logical relationship based on noticeable symptoms and/or symptoms from the fault memory model,
among each other or with each other. A rule of thumb can be evaluated according to its reliability and
assigned to one or more diagnostic objects.
eShop
eShop is the system for ordering and licensing software and diagnostic data within the Volkswagen
Offboard Diagnostic Information System.
Vehicle identification
The vehicle is identified by determining the vehicle basic features (type, model year, version, engine
code) that can be detected automatically or partially automatically when a Gateway is present. Based on
this data, a list of control modules and equipment that may be installed is created and the vehicle system
test checks if these are installed or not.
Feedback
Error classification
Flash data
The flash data are sections of the programs that can be loaded for a vehicle system.
Flash memory
Hard drive whose data remains intact even when there is no power supply. In contrast to permanently
programmed memory modules, a flash memory can be updated with a corresponding update program
(using the Flash CD).
Function
Function test
Gateway components list
A Gateway control module knows the vehicle systems installed in the vehicle. It monitors the vehicle
systems and manages a status list. By checking the Gateway components list, for example, a vehicle
- 585 -
system can be queried if its DTC memory is set, if it is coded or if communication is possible. The
components list is evaluated during vehicle identification and leads to a more effective identification
process.
Guided Fault Finding
In Guided Fault Finding, the diagnostic approach is integrated into an optimized process of vehicle
identification, vehicle system test, test plan and function tests.
Guided Functions
Performing a vehicle specific function outside of GFF, for example, measuring
Basic Setting
In basic setting, control modules are adapted to the peripheral devices.
Basic features
A vehicle is identified based on the type, model year, version and engine code. Its equipment is then
determined through a vehicle system test.
Hardware key, Hardware ID
Hardware features that are coded as a string of characters. The Hardware ID is a component of the
device-based licensing.
Hotfix
IP address
Abbreviation for "Internet protocol address." Each computer that is connected to a computer network
(TCP/IP) has its own unique IP address. It consists of four groups of numbers that are separated by
periods (for example, 194.0.0.135). DHCP servers can assign IP addresses automatically.
Actual installation
Calibration
Precise adaptation of a tester (for example, current clamp) based on specifications and the correction of
a measuring deviation through compensation of a systematic error.
Maximum installation
Measuring Equipment
In measurements, you can complete measurements yourself whose results are displayed numerically or
graphically on the tester. A multimeter and oscilloscope (DSO) are available.
- 586 -
Measured Value Block
A fixed group of measured values that are read from a vehicle system.
Mirror server
A software package that is stored locally on the dealer server, for example, and that maintains data for
the VAS 505x update programs there. The dealer server is connected centrally and receives current
updates from there. Within the workshop, each tester connected to the LAN retrieves the current pro-
grams automatically when switched on or explicitly when the "Network update" function in Administra-
tion is run.
Offline
There is no active connection to a communication network.
Online
Active connection with a communication network such as the workshop network, the Volkswagen dealer
network or the Internet. See all Online connection.
Online log
A log that is sent to the vehicle manufacturer via the online connection.
Online connection
External connection such as one to the Internet or VW server.
Oscilloscope
Measurement and display unit for electrical signals that displays the progression of the signal strength
over time (for example, oscillations).
D-PDU-API
The D-PUD-API is a standardized software interface for connecting diagnostic interfaces to the diag-
nostic software.
Platform
Protocols KW1281, KW2000, KW6000, UDS
The keyword protocols determine the exact process for exchanging data between a control module and
the tester. Older control modules communication with KW1281. Newer control modules work with
KW2000 or KW6000 (CAN diagnosis). ASAM control modules work with UDS. In vehicle OBD, the
tester determines the control module's keyword protocol version automatically before selecting diagnos-
tic functions for the control module.
- 587 -
Provider
A service provider that offers communication services such as telephone, wireless communication or
Internet.
Proxy server
A proxy server is an exchange between clients and another network. It accepts requests from the client
and forwards their data (sometimes modified or anonymously) to the original source (in another network
such as the Internet). Proxies can temporarily store the data locally (cache) for additional access.
Test plan
Weighted sequence of test programs that the operating system suggests to the service technician for
repairing the vehicle.
Test step
A self-contained unit in a function test.
RDID
Record Data Identifier. The Record Data Identifier decides on the data type. Via the Record Data Iden-
tifier, it is determined which data should be transferred.
Readiness code
8-digit binary code that indicates if all emissions- and safety-related diagnoses were run by engine man-
agement.
Release Notes
Version notes that accompany a software version. The version notes describe functions that are new or
have changed in comparison to the previous version.
Screenshot
Copy of the current screen content in a picture file.
Sensor
Device that receives measured values.
Server
In computer technology, a server refers to a central network computer. The server makes the services or
data available to the clients.
SFD
- 588 -
Schutz der Fahrzeug-Diagnose (vehicle diagnostic protection)
Definitely installed (control module)
Specified installation
Start module
A start module can consist of one or more function tests that start automatically after the vehicle system
test. They are used to check if new flash data is available for a vehicle system.
Control module
Electronic device for controlling and monitoring vehicle functions such as engine control module. Refer
to ECU, vehicle system.
Test Baseline
The developer version of a DIDB. It can be used either to expand or completely replace the productive
data in the installation.
Touchscreen
A screen that also serves as an input device. By touching the contents of the screen, the device (such as
a computer or cell phone) can be controlled.
TPS
Traversal test
This type of test identifies control modules and derives information from them that enables automatic
vehicle identification. The test automatically cycles through the equipment network structures.
UDS
Unified Diagnostic Services; a standardized protocol in accordance with ISO 14229 for control module
communication. Based on KW2000 for ASAM-ODX control modules.
Update
Software modification package for updating existing software to a higher version.
1. New version of the operating system that is downloaded from the CD-ROM.
2. New programming version of a vehicle system that is downloaded from the tester.
URL
- 589 -
Abbreviation for "Uniform Resource Locator". A URL is the address of an Internet resource such as a
website, file, etc. Example: http://www.volkswagen.de
Versions, version rule
The term is used in conjunction with the vehicle system equipment. Some equipment such as an airbag
may appear in different versions for an identified control module. The basic task of the vehicle system
test is to find out which version is actually installed. If the version cannot be detected automatically, the
system will ask yes/no question about the equipment such as "Automatic transmission?" The mecha-
nisms for determining the versions are called version rules. Their results determine which diagnostic
data will be made available.
VCI
The Vehicle Communication Interface is used to communicate with the vehicle
Components List
List of the control modules installed in the vehicle.
Installation status
Verification
Workshop code
Certificate
License document that contains all authorizations, areas and characteristics of the software and diagnos-
tic data. The certificate is required to use the tester software and is checked each time the application
starts.
- 590 -

Manual Service-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 Service-En US

Uploaded by

Copyright:

Available Formats

Offboard Diagnostic Information

System Service User Guide

ODIS Service 11.0.0

Copyright © 2007-2022 VOLKSWAGEN AG

1.2 Structure of the User Guide

Figure 1.1 Example of an active link in the table of contents

This symbol is used for supplementary information and useful tips.

The following chapter, Name of Chapter, contains additional information.

Figure 1.2 Example of the Diagnosis Procedure

Figure 1.3 Example of a section of a procedure with individual steps

- Multi-core CPU 2GHz or higher recommended

RAM >= 4 GB (8 GB recommended)

Supported tester hardware

Windows 10, 64-bit

Libraries (DLL) for Microsoft Visual Studio 2019

Internet Explorer 11.0

Adobe Acrobat Reader Version 11 or Adobe Acrobat Reader DC

There are two possible installation options.

The first option is online installation:

Open the e-mail received from the eShop.

Download the license certificate through the eShop.

Save setup.exe in any directory.

Double click the saved setup.exe to start the installation wizard.

The section option is offline installation:

Download the license certificate through the eShop.

Click the correct setup.exe to start the installation wizard.

The installation wizard starts.

Figure 3.1 Starting installation

The preferred language for the installation must be selected.

Figure 3.2 Installation language selection

OK: The selection is confirmed.

Cancel: the installation is canceled.

Next: the installation of Offboard Diagnostic Information System Service continues.

Cancel: the installation is canceled.

The default target folder is C:\Program Files (x86)\Offboard_Diagnostic_Information_System_Service

The path may differ if the operating system is in another language.

For example, C:\Program Files\Offboard_Diagnostic_Information_System_Service

Figure 3.4 Platform selection

Back: the installation goes back one step.

Next: the installation of Offboard Diagnostic Information System Service continues.

Cancel: the installation is canceled.

Back: the installation goes back one step.

Next: the installation of Offboard Diagnostic Information System Service continues.

Cancel: the installation is canceled.

Back: the installation goes back one step.

Next: the installation of Offboard Diagnostic Information System Service continues.

Cancel: the installation is canceled.

Figure 3.7 License Selection

An example of the location of the certificate is:

The standard installation folder for the license file is:

Back: the installation goes back one step.

Next: the installation of Offboard Diagnostic Information System Service continues.

Cancel: the installation is canceled.

Figure 3.8 Start menu folder selection

Back: the installation goes back one step.

Cancel: the installation is canceled.

Cancel: the installation is canceled.

This installation procedure cannot be influenced.

URL: mirror server address (depending on the importer).

User name: user name for accessing the mirror server

Password: password for accessing the mirror server.

Cancel: the PostSetup is canceled.

Figure 3.12 Client certificate

Also refer to the chapter Client certificate in Administration Mode.