Fault code

Description

Various control units

B184C00

Protection of vehicle diagnostics, actuation
active

Main control unit for gateway
HCP5 (J1273)

U17A000

Diagnostic filter, access protection deactivated

Drive and chassis main
control unit HCP1 (J1312)

C140DF0

Vehicle Protected Environment (VPE), vehicle
protection activated

For other valid fault codes, see ⇒ Technical Information '9X10IN Valid fault codes after update to the
incremented software network VR28.13'
8.1

Press •F7“ to call up the additional menu on the Porsche Tester.

8.2

Select and confirm the menu item “Read/delete all fault memories” and confirm.

AfterSales

Feb 9, 2026
Page 7 of 18

9

Service
WSJ0

ENU

8.3
9

Technical Information

2025

Press •F8“ to delete the displayed fault memory entries.

For new vehicles only – commission the vehicle; for this, carry out the “Vehicle handover” routine in full
according to the Porsche Tester instructions.

10 Create a Vehicle Analysis Log (VAL) using the Porsche Tester. To do this, press •F7“ to access the
additional menu and select the creation of the protocol.
Mark the created vehicle analysis log with the attribute “Post-VAL” and return it using the Porsche Tester
after the campaign has been carried out.
11 Carry out a plausibility check of the battery capacity according to the instructions of the Porsche Tester.
11.1

Open high-voltage battery control unit (J1120).

11.2

Open “Service/Maintenance” menu.

11.3

Select the menu item “Plausibility check of battery capacity” and carry it out.
•

If no abnormalities were detected during the plausibility check of the battery capacity, end
the procedure with •F12“ and continue with work step 13.

•

If the plausibility check of the battery capacity results in a deviation, repeat the test as
described and follow the guided Tester procedure. If it was not possible to re-initialize the
calculation of the battery capacity, it is not necessary to create the Vehicle Analysis Log at
this point; ignore the corresponding instructions of the Tester.

Information
If the plausibility check of the battery capacity has resulted in a deviation and the Tester
procedure has been carried out to reset the battery capacity learning values, scope 2 of this
campaign will then need to be invoiced.
In addition, the customer must be informed about the temporary deviation of the range display
based on the FAQs for this campaign when returning the vehicle.
12 Read out the fault memory again and erase it.
For other valid fault codes, see ⇒ Technical Information '9X10IN Valid fault codes after update to the
incremented software network VR28.13'
12.1

Press •F7“ to call up the additional menu on the Porsche Tester.

12.2

Select and confirm the menu item “Read/delete all fault memories” and confirm.

12.3

Press •F8“ to delete the displayed fault memory entries.

13 Create a Vehicle Analysis Log (VAL) using the Porsche Tester. To do this, press •F7“ to access the
additional menu and select the creation of the protocol.
Mark the created vehicle analysis log with the attribute “Post-VAL” and, after carrying out the campaign,
return it using the Porsche Tester

Feb 9, 2026
Page 8 of 18

AfterSales

Service

Technical Information

2025

ENU

WSJ0

9

Note: 2 different Post-VALs are required. The first Post-VAL is to analyze the programming sequence
and the second Post-VAL is to analyze the plausibility check of the battery capacity.
14 End the diagnostic application. Switch off the ignition. Disconnect the Tester from the vehicle.
15 Switch off and disconnect the battery charger.
Information
During the test drive, the GPS is reconnected, and the tire settings must be checked and, if necessary,
adjusted again.
After the test drive, individual customer settings must be restored.
The activities performed during the test drive and after the test drive do not have to be carried out by
the technician.
16 Carry out the test drive, then restore the customer settings.
17 Check that all four doors are locked correctly:
17.1

Lock the vehicle using the hand-held transmitter

17.2

Remove hand-held transmitter from the proximity of the vehicle (> 10m)

17.3

Check that all four doors are locked properly by pulling the door handle

18 Attach the completed checklist to the PQIS process line. ⇒ Technical Information '9X10IN Checklist'
19 Enter the campaign in the Warranty and Maintenance logbook.

Warranty processing
Information
The specified labor times were determined specifically for carrying out this campaign and include all
necessary preliminary and subsequent rework. The labor times may differ from those published in the Labor
Operation List in the PCSS.

AfterSales

Feb 9, 2026
Page 9 of 18

9

Service
WSJ0

Scope 1:

ENU

Technical Information

2025

Update to software network VR28.13

Labor time:
Update to software network VR28.13
Includes:
Connect and disconnect the battery charger
Connect and disconnect Porsche Tester
Standardize the side windows
Check readiness for driving
Perform a plausibility check of battery capacity
Read out and delete the fault memory
Create the Vehicle Analysis Log (VAL) before and after the
campaign

Labor time: 197 TU

Þ Damage number WSJ0 066 000 1
⇒
Scope 2:

Run an update on software network VR28.13 and re-initialize the calculation of the battery capacity
Labor time:
Update to software network VR28.13
Includes:
Connect and disconnect the battery charger
Connect and disconnect Porsche Tester
Standardize the side windows
Check readiness for driving
Carry out the plausibility check of the battery capacity and
reset the values
Read out and delete the fault memory
Create the Vehicle Analysis Log (VAL) before and after the
campaign
Re-initialize the calculation of the battery capacity

Labor time: 231 TU

Þ Damage number WSJ0 066 000 1
⇒

Overview of the new features of the software update
Overview:

Feb 9, 2026
Page 10 of 18

Function

Description

Drive and chassis

•
•
•

Optimization of vehicle starting behavior
Improvement in air suspension adjustment speed
Optimization of the e-sound display to avoid unintentional
warning messages

Battery charge

•
•

Improvement of preconditioning availability
Increased robustness of charging behavior

AfterSales

Service

Technical Information
Infotainment system

2025
•
•
•
•

My Porsche app

•
•

Driver assistance systems

•

•
•

ENU

WSJ0

9

Numerous stability, robustness and comfort improvements.
Optimization of passenger display touch input
Optimization of the passenger display for an improved display
when using third-party apps
Increased robustness of Bluetooth connectivity
Improvement of the microphone function for voice messages
through Apple CarPlay and Android Auto. Improved contacts
synchronization between vehicle and mobile device
New function for opening and locking the charge port door
directly from the app
Improvement of data transmission for a more accurate display of
the remaining range in the My Porsche app
Numerous stability, robustness and comfort improvements.
Increased system stability to avoid unintended white and
yellow warning messages, e.g. for fatigue warning, “Assistance
systems not available” warning message, “Clean sensor” warning
message
Optimization of traffic sign recognition
Expansion of the Porsche voice assistant to include Google
Search for more convenient and quicker information retrieval
while driving

Navigation system

•

Improved 5G connectivity

Comfort systems

•
•

Optimization of vehicle key recognition
Improved ParkAssist stability

Air-conditioning system

•

Optimization of the dehumidification function to more effectively
prevent misted windows

High-voltage system

•

Numerous stability and robustness improvements

Back to introduction ⇒ Technical Information '9X10IN Introduction ' ⇒ Technical Information '9X10IN Introduction'

Additional information on control unit programming and coding
Information
If individual programming or rework procedures could not be carried out correctly, please refer to the
Workshop Manual for the basic procedure for control unit programming with the PIWIS tester. ⇒ Technical
Information '9X10IN Basic information and procedure for control unit programming with the PIWIS tester.
Information':
In the event of a fault, always create a log with the PIWIS tester during programming with •P2“.

AfterSales

Feb 9, 2026
Page 11 of 18

9

Service
WSJ0

Work
Procedure:

ENU

Technical Information

2025

General:
Fault indication

Cause

Source of
fault

Remedial action

After the first update
cycle, one or more
control units with
coding are required
or programming is
required

The affected control unit
was not successfully
programmed or coded

Vehicle

•

Cause

Source of
fault

Remedial action

VCI has
poor Wi-Fi
connection

•

Source of
fault

Remedial action

Diagnostic
application

•

•

Restart update by pressing
•F8“
After successful
implementation, continue
with work step 5

Before the update:
Fault indication
Diagnostic application
crashes or the VCI
connection has been
aborted (the diagnosis
has no information on
battery voltage – see
the battery symbol
at the top right on the
Tester display)

•

Restart tester, connect VCI
with cable and try again
or: ensure that Wi-Fi
connection is stable, moving
vehicle to a suitable position
in workshop if necessary

During the update:
Fault indication

Cause

Diagnostic application
crashes or the VCI
connection has been
aborted (the diagnosis
has no information on
battery voltage – see
the battery symbol
at the top right on the
Tester display)

•
•

•

Feb 9, 2026
Page 12 of 18

AfterSales

Checking the update
progress in the vehicle is
mandatory
No ignition change during
update
Do not restart the Tester
until the update has been
completed in the vehicle (tile
“Messages” --> Installation
“successful”)
When the update is
concluded in the vehicle,
verify that the update
is complete. For this
purpose, start control

Service

Technical Information

2025

ENU

WSJ0

9

unit programming in the
integration test using the
‘Campaign’ function •F5“
on the Porsche Tester
Implementation
of vehicle update
immediately after
starting not successful,
Vehicle update failed
error message

Date/time in vehicle
after disconnecting/reconnecting 12-V battery
(terminal 30) incorrect.
As a result, no software
update can be performed

Vehicle

Correct the date/time in the
vehicle:
•
•
•
•

HCP2 driver assistance
main control unit
(J1274) reports a “Code
signing fault” and a
communication error for
the Sub System Driver
Assistance control unit
in the results view

The affected control unit
was not successfully
programmed

Vehicle

Select “Special function” in the
additional menu
Enter campaign code:
HCP2_ERROR_KD2
and follow the Tester instructions
•

•

TheMain control unit
for gateway HCP5
(J1273) logs into the
programming checksum
calculation with a
hardware check and the
value “NEGRESP”

Affected control unit
was not successfully
programmed,
programming aborted