0151

0016

0060

0067

0067

0067

0019

0411

0254

0561

0561

0023

0840

0853

0853

0853

0036

0571

0571

0571

0571 + ZDC*

0042

0561

0561

0563

0563 + ZDC*

0051

7246

7252

7260

7260

0052

0561

0561

0563

0563 + ZDC*

005F

3343

3626

3748

3748

006C

0464

0574

0574

0574

006C

-

0605

0685

0685

0075

0288

0554

0610

0610

0076

0514

0630

0630

0630

008C

1122

1141

1141

1141

00A5

5510

5556

5570

5570

00B7

0757

0757

0771

0771

00BB

0561

0561

0563

0563

00BC

0561

0561

0563

0563

00C0

0012

0015

0015

0015

00C6

5206

2207

3208

3208

00CE

8122

8123

8127

8127

060E

4043

4045

4047

4047

06D1

1112

1140

1140

1140

06D5

1112

1140

1140

1140

06D9

1112

1140

1140

1140

8116

0010

0012

0012

0012

8123

0411

0254

0561

0561

8124

0411

0254

0561

0561

8125

3343

3626

3748

3748

C002

0411

0254

0561

0561

C003

0411

0254

0561

0561

*ZDC (Target data container) – The ZDC of the control unit is updated to a new version within the ID.S 5.4.3
KD compound update. If the SW-version is already current, then only the ZDC is updated via the update
procedure without a SW-version change.

17. Support

The possible remedies listed below should only be applied when necessary for the specific errors listed if
such errors are encountered in the course of the software update given in this technical bulletin. Any other
use of these remedies is inappropriate and can lead to unexpected results or additional errors.

1.

ERP8064: Should ERP8064 occur during function restore in the function enabling system (FES), then
there is a connection problem with the backend license server.
Possible remedy: For the purpose of this remedy only, repeat function restore using code
0019S421014 and then repeat action code F543.

2.

ERP8065: During software flashing, should ERP8065 occur, then an action code was used that cannot
be used for the current vehicle and its current software compound / baseline.
Possible remedy: Check the action code used for validity.

3.

ERP8075: Should ERP8075 occur during software flashing, a repair suggestion cannot be determined,
as several identifiers are missing from identification of certain control units or entire diagnosis
addresses.
Possible remedy: Perform a terminal 30 reset (see in GFF test plan list: Important note when
disconnecting the 12V battery) then start a new diagnostic session, and reattempt software flashing.

4.

ERP8088: During software flashing, should ERP8088 occur, the software update or the online
reporting of the updated vehicle build status documentation failed.
Possible remedy: Carry out “5.2 ICAS1 factory reset” again and repeat action code F543.
Alternatively: Carry out a bus sleep with test program 0019 – Establish bus sleep mode. Then repeat
the action code used.

5.

ERP8113: During software flashing, if ERP8113 should occur, then not every update has yet been
successfully carried out.
Possible remedy: Switch off the ignition for 30 seconds. Then switch the ignition on again, wait 30
seconds and then repeat the action code used.

6.

ERP8118: Should tester error message ERP8118 occur during software flashing, then one or several
diagnosis addresses were not recognized during diagnosis entrance. The diagnostic tester generally
shows the affected diagnostic addresses. If no diagnostic addresses are shown, pay special attention
to diagnostic addresses 0075 and 8107, and sub-bus addresses (for example: 0601, 0602, 0616,
0618, 0631, 0637).
Possible remedy: Manually identify the missing control units in the control unit list or perform a
software configuration on the respective diagnostic addresses. In the case of an unrecognized sub-bus
address, perform the software configuration on the corresponding diagnostic address to which the subbus address reports and then repeat the action code used.
Hint: An earlier GFF log, when downloaded from GFF Paperless in HTML format, can be referenced to
compare installed diagnostic addresses and respective sub-bus addresses at an earlier time point
before the start of software flashing.
Should this procedure not resolve the problem, perform a terminal 30 reset (see in GFF test plan list:
Important note when disconnecting the 12V battery) then start a new diagnostic session, and reattempt
software flashing with the action code used.

7.

ERP9999: Should tester error message ERP9999 occur during software flashing, then there are
problems with the connection to the D3 Edge Box dealer workshop server.
Possible remedy: Check the that the control units to be updated are identified in the control unit list,
then contact your IT support to check the URL configuration and software version of your D3 Edge Box.

8.

After the software update the OCU (diagnostic address 0075) is offline, the globe symbol (online
status) is not shown, or is grayed-out in the center display.
Perform GFF: Guided Functions > 0075 – Activating control module
After about 2 minutes the globe appears and is shown in white (online).

9.

Error message: “The CAN-FD/ DoIP communication path could not be set” – If this error message
occurs during the software update process (SVM) there may be several causes.

Possible remedies:
Check and adjust firewall settings with dealer IT network support (see under: “2. Review prerequisites
and perform preliminary work”).
Update Windows operating system of the diagnostic tester.
Ensure that only diagnostic interface VAS 6154A or 6154B is used and ensure the software of the
diagnostic interface VAS 6154A or 6154B is current.
For the purpose of this remedy only, temporarily reconfigure the diagnostic tester for DoIP-only
communication under “Admin > General > GFF Process > Communication path selection” and then
reattempt the action code used. Afterwards, restore setting for automatic detection.
If DoIP communication is still not possible, then check wiring at the diagnostic connection (U31) and
the ICAS1/Gateway (J533) according to the attached supplemental information
“tb_2080124_attachment_can_doip_checks.pdf”.
10. No terminal 15 / ignition cannot be switched on anymore after performing action code S4210F543. This
occurs when ICAS1 freezes in the bootloader. In the identification data of the diagnostic address 0019
the software version 9246 is shown.

Possible remedy:

PR number V7B: Pull fuse SC41 for 1 minute and, after insertion, carry out action code S4210521D.
PR numbers V7C or V7G: Pull fuse SC41 for 1 minute and, after insertion, repeat action code
S4210F543.
11. 0019: DSDL2 incorrect: The DSDL2 cannot be successfully written during the software configuration
(incorrect).

Possible remedy: Pull fuse SC41 for 1 minute and, after insertion, carry out the previously used action
code again.
12. 0051: Error message: Safe condition not created.

Possible remedy: Switch off the ignition, select 1. Create requirements and press Continue.
13. 0602: Adapting/calibration incorrect: The software configuration cannot be successfully carried out
(incorrect). The SFD (vehicle diagnostic protection) at the master (SAM/ diagnostic address 0009)
could not be activated.

Possible remedy: Carry out SFD authorization via Self-diagnosis (OBD) > 0009 > Access authorization
> Authorization manually online and repeat action code F543. A bus sleep may need to be carried out
in advance.
14. 8128: Error message: Active function not completed. The new instances from ICAS3 were not
completely loaded; the ID light is white on the ends.

Possible remedy: Carry out a bus sleep with test program 0019 – Establish bus sleep mode. The ID
light no longer lights white at both ends (the bus sleep mode may have to be carried out twice). Then
carry out action code F543 again.

NOTICE
In case of ERP errors during software flashing that cannot be resolved:
– Press the help / support button on the diagnostic tester to send ODIS feedback.
– If the help / support button cannot be pressed because of a crash of the diagnostic tester, restart the
tester and press the help / support button immediately upon restart. The data of the previous session is
then still available and can be transmitted.

NOTICE
In case of other errors during the software update that cannot be resolved:
– Contact VW Group Technical Assistance Center (TAC) and mention “TB 2080124 / ID.S 5.4.3KD
update” in the comments.
– If replacement of a control unit is necessary and is eligible for warranty reimbursement, it must be
submitted and coded separately from the software update claim.

Warranty
Information only.

NOTICE

No parts or labor may be claimed under this technical bulletin. If eligible for warranty reimbursement, a
claim may only be submitted according to the applicable technical bulletin that specifies performing this
software update.

Required Parts and Tools
No Special Parts required.
No Special Tools required.

Tool Description

Tool No:

12V Battery Charger / Maintainer

VAS 5908

VAS Diagnostic Tool

VAS 6150/X & VAS 6160/X with
ODIS Service with current online updates

Additional Information
All part and service references provided in this Technical Bulletin are subject to change and/or removal.
Always check with your Parts Dept. and Repair Manuals for the latest information.

© 2026 Volkswagen Group of America, Inc. All rights reserved. Information contained in this document is
based on the latest information available at the time of printing and is subject to the copyright and other
intellectual property rights of Volkswagen Group of America, Inc., its affiliated companies and its licensors.
All rights are reserved to make changes at any time without notice. No part of this document may be
reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical,
photocopying, recording, or otherwise, nor may these materials be modified or reposted to other sites,
without the prior expressed written permission of the publisher.

Public

Supplemental Information
Error: “The CAN-FD/DoIP communication path could not be set.”

VWGoA | December 17, 2025

Supplementary Information for Technical Bulletin 2080124/*

Error: “The CAN-FD/DoIP communication path could not be set.”

Procedure for checking CAN/ DoIP
switching and Ethernet lines
1. Access the diagnostic connection (U31) for inspection (see page 3-4).
2. Review the wiring diagram of the CAN/ DoIP switching and Ethernet
lines (see page 5).
3. Check behind diagnostic connection (U31) for aftermarket equipment
(see page 6), if necessary, disconnect.
4. Check control line behind diagnostic connection (U31) for damage (see
page 7), if necessary, repair.
5. Perform a resistance measurement of the control line (see wiring
diagram, page 5), if necessary, repair or replace the wire/terminals.
6. Check Ethernet lines at the gateway (J533) connector (see page 5 and
8), if necessary, reseat terminals.

Page 2
Supplementary Information for Technical Bulletin 2080124/*

Accessing the diagnostic
connection (U31)
• Remove the small access panel to the left of the
steering column.
• Gently press upper and lower retainer tabs (yellow
arrows) to release the bracket of the diagnostic
connector (U31).

Page 3
Supplementary Information for Technical Bulletin 2080124/*

Accessing the diagnostic
connection (U31)
• The bracket can then be CAREFULLY pulled downwards
into the footwell (yellow arrow) for inspection.
• The wires behind the diagnostic connection (U31) are
then visible for inspection.
• If necessary, the bracket can be removed by releasing
three additional retaining tabs on the diagnostic
connection (U31).

Seite 4
Supplementary Information for Technical Bulletin 2080124/*

CAN/ DoIP
Switching line

Wiring diagram of CAN/ DoIP
control line and Ethernet lines
Control line for CAN/ DoIP switching (red rectangle)
• T40a/28 Gateway (J533) <-> T16i/8 diagnostic connection (U31)
Ethernet data lines (DoIP/ blue rectangle)
• T40a/30 Gateway (J533) <-> T16i/12 diagnostic connection (U31)
• T40a/29 Gateway (J533) <-> T16i/13 diagnostic connection (U31)
• T40a/39 Gateway (J533) <-> T16i/3 diagnostic connection (U31)
• T40a/40 Gateway (J533) <-> T16i/11 diagnostic connection (U31)

Page 5
Supplementary Information for Technical Bulletin 2080124/*

Ethernet
lines (4)

Checking for aftermarket
equipment at the diagnostic
connection (U31)
• Check for a non-original diagnostic connection (U31) or
any aftermarket equipment or wiring connected to the
vehicle’s original diagnostic connection (U31).
• The diagnostic interface VAS 6154A or VAS 6154B must
be connected to the original diagnostic connection
(U31) for a stable connection and proper CAN/ DoIP
switching.

Page 6
Supplementary Information for Technical Bulletin 2080124/*

Checking CAN/ DoIP switching
control line
• Check the wire and terminal of pin 8 for
damage/fault/interruption (red circle).
• If no fault can be see upon visual inspection, perform a
resistance measurement through the wire and terminals
end-to-end between diagnostic connector (U31) and the
ICAS1/Gateway (J533) connector (see wiring diagram,
page 5), if necessary, repair.

Seite 7
Supplementary Information for Technical Bulletin 2080124/*

Checking the Ethernet lines

• Check the Ethernet wires at the gateway connector
for correct installation.
• If any are not fully seated (red arrow) seat the
connector fully, if necessary, repair.

Seite 8
Supplementary Information for Technical Bulletin 2080124/*