Technical Service Bulletin
Topic

Electronic Parking Brake (EPB) control unit cannot be coded

Market area

Bentley: worldwide (2WBE),China 723 Volkswagen (Anhui) Automotive CO (6723),China 796
VW Import Comp. Ltd (Vico), Beijing (6796)

Brand

Bentley

Transaction
2071089/4
No.
Level

EH

Status

Released for publishing

Release
date

Dec 16, 2025

New customer code

Object of complaint

Complaint type

chassis -> brakes, brake regulation -> electronic parking brake (EPB) ->
emergency brakes (EPB)

functionality -> no
function

chassis -> brakes, brake regulation

component,
automotive fluids

Vehicle data
Continental GT/C and Flying Spur
Sales types

Type MY

Brand Designation Engine code Gearbox code Final drive code

393* 2012 E

*

*

*

393* 2013 E

*

*

*

393* 2014 E

*

*

*

394* 2012 E

*

*

*

394* 2013 E

*

*

*

394* 2014 E

*

*

*

3W* 2004 E

*

*

*

3W* 2005 E

*

*

*

3W* 2006 E

*

*

*

3W* 2007 E

*

*

*

Position

3W* 2008 E

*

*

*

3W* 2009 E

*

*

*

3W* 2010 E

*

*

*

3W* 2011 E

*

*

*

3W* 2012 E

*

*

*

3W* 2013 E

*

*

*

4W* 2014 E

*

*

*

Documents
Document name
master.xml

Technical Service Bulletin
Electronic Parking Brake (EPB) control unit cannot be coded

Transaction No.: 2071089/4
Release date: Dec 16, 2025

Condition
The Electronic Parking Brake (EPB) control unit cannot be coded when using a diagnostic machine with
Windows 10/11 in conjunction with a VAS 6154 dongle. As such the EPB coding application must be utilized
to complete the procedure.

Hint: The following part numbers are affected:

3W0 907 801F (or previous suffix)

3W0 907 801G

3W0 907 801H

CAUTION
The following part number (introduced at 15MY) is not affected and can be coded using Windows 10 with
the VAS 6154 dongle:
Part number 4W0 907 801

Technical Background
NOTICE
The EPB can only be coded using Windows 7 with a VAS 5054 dongle
Do not attempt to code the EPB with ODIS whilst running Windows 10 as damage may occur to the EPB
module

Should Windows 7 and/or VAS 5054 no longer be available the retailer must conduct the following:
•

Refer to the measure section for completion of coding with EPB coding application.

Production Solution
Not applicable

Service

EPB coding application - Introduction
ODIS Service is unable to complete the final variant encoding stage of the Electro-mechanical parking brake
(EPB) replacement process. As such the EPB coding application must be utilized to complete the procedure.
The initial stages of the replacement process are carried out via ODIS Service. Ensure the ODIS Service
EPB process has been carried out before following these instructions, failure to do so will cause the
application to be unsuccessful.

Installation
To download the application, use the FMC code: 61X62XEPBCODING

Ensure you have a “volume selected”
Enter the Part Name
Select Search > Select Download >
The USB Stick will eject automatically, you will have to remove it and place it back into your PC

The USB Stick should look like this:

Double Click on the EPB coding setup wizard
Follow the on screen instructions for the EPB coding setup wizard

Hint:

Ensure the Program is saved to the C:/ drive, rather than the USB stick, then the USB stick can be re-used

Follow any further installation and setup instructions provided in the FMC Manual (available in English and
German) from one of the following sources:
•

Bentley Hub

•

Mirror Server: mirror server/dav/FMC

Alternatively, the application can be requested from Bentley Product Support via DISS.

Process

1. Run the Electronic Parking Brake (EPB) replacement test using ODIS. Ensure ODIS is updated to version
2.35.11 (or higher). The guided process will then lead you to this TPI.

2. Close ODIS-Service if it has not been closed.

3. Ensure the ignition remains ON and the VAS 6154 interface is connected.

4. Launch the EPB Coding application.

5. The application will automatically connect to the VAS 6154 interface. The process can only be continued
once the application has detected the ignition is switched ON.

Figure 1. Waiting for ignition detection

Figure 2 Ignition Detected

6. Once the ignition has been detected click the Done/Continue button to initiate communications with the
vehicle.

Figure 3. Establishing vehicle communications

7. After communications with the vehicle have been established, you will be prompted to enter the vehicle
appropriate Variant code as specified in the Variant code matrix, which can be found in the ‘Variant Code
Matrix’ Section at the bottom of this TPI.
Click the Apply button once the correct code has been inputted.

Figure 4. Variant code entry

Figure 5. Coding in progress

After the coding is complete the application will automatically read the Variant code from the control module
to verify the result of the coding.
Click the Done/Continue button to continue after the code has been displayed.

Figure 6. Reading Variant code

Figure 7. Variant code displayed

8. The application will now interrogate the control module for DTCs.
a. If no DTCs are found the application will report the end of the test.
Click the Exit button to close the application.
b. If DTCs are found an option will be given to clear them.
Select Yes to clear the DTCs.
Select to end the test without clearing the DTCs.

Figure 8. End of test

Figure 9. Clear DTCs question

Figure 10. Clearing DTCs

Figure 11. End of test

9. If Yes was selected the application will attempt to clear the DTCs. The result of the clear will next be
displayed.

Figure 12. DTCs cleared

Figure 13. DTCs not cleared

10. Select Done/Continue and the application will report the end of the test and the application can be closed
via the Exit button.

Figure 14. End of test

11. Restart ODIS Service and start a new diagnostic session. Perform a full Diagnostic trouble code (DTC)
sweep. Review and process any DTCs found, taking appropriate actions.

Variant Code Matrix

Model

Model year

Regional specification

Engine

Transmission

Variant
code

Continental GT

2004 - 2009

North America

n/a

n/a

22401

Continental GT

2004 - 2009

Rest of the world

n/a

n/a

22413

Continental GT

2010 - 2011

n/a

n/a

n/a

22413

Continental GT

2012 - 2014

n/a

V8

n/a

23513

Continental GT

2012 - 2014

n/a

W12

6 speed

22413

Continental GT

2012 - 2014

n/a

W12

8 speed

22513

Flying Spur

2005 - 2009

North America

n/a

n/a

32401

Flying Spur

2005 - 2009

Rest of the world

n/a

n/a

32413

Flying Spur

2010 - 2011

n/a

n/a

n/a

22413

Flying Spur

2012 - 2014

n/a

n/a

n/a

22513

NOTICE
If you encounter an issue within this procedure, please raise a Technical DISS and attach the trace logs.

Trace log
Trace logs can be found in the following location:
C:/ProgramData/OS/EbpLog