Service

Technical Information

123/23 ENU

APB1

9

APB1 - Re-Programming Gateway Control Unit (Stop Delivery/Recall Campaign)

Model Line:

Cayenne (9YA/9YB)

Model Year:

2024

Concerns:

Gateway control unit

Cause:

Due to a software fault in the gateway control unit, the rear hazard lights are not activated when
the hazard warning light switch is operated within 10 seconds of the bus idle of the gateway
control unit being activated.
This means that specific legal requirements for the functionality of the hazard warning lights are not met.

Actions:

•
•

Checklist:

Due to the high number of programming steps incorrectly carried out as part of the last software
update, a checklist was created to improve the overview of the work to be carried out. The checklist
must be completed, signed and attached to the PQIS quality line in the PCSS.
For checklist, see  Technical Information 'Checklist'

Affected
Vehicles:

Only vehicles assigned to the campaign (see also PCSS Vehicle Information)

Re-program the control units with the latest PIWIS Tester software release.
Minimum requirement: Release 42.100.035

Required tools
Tools:

•
•

Battery charger with a current rating of at least 90 A, e.g. VAS 5908 battery charger 90 A
P90999 - P90999 - PIWIS Tester 4

Software update to VR10 software network including the gateway control unit
Work
Procedure:

Information
Before starting programming, the battery charger must necessarily be:
•

Operated in SUPPLYMODE with a 14.6 Volt setpoint and 90 A current limit..

Verify the settings of your VAS 5908 power supply before applying power to the vehicle.
NOTE: The vehicle electrical system must never exceed 14.8 Volts. Use a quality DMM/DVOM to verify
voltage at the power supply connection points of the vehicle.
Electrical resistance in the power supply cables and the clamp connection points greatly affect power
supplied to the vehicle. For example, resistance of 0.015 Ohm in the cable set results in a 1.35 V drop in

AfterSales

Aug 18, 2023
Page 1 of 11

9

Service

Technical Information

ENU 123/23

APB1

the cables when a 90 A current is required. Perform a CABLE CHECK / Cable Compensation periodically,
approximately once per month, to ensure proper power supply.
•

The vehicle must be on a level surface.

•

Air suspension must be at normal level.

•

There must be an active PPN connection.

1

The basic procedure for control unit programming is described in the Workshop Manual 
Workshop Manual 'Basic Instructions and Procedure for Control Unit Programming Using the PIWIS
Tester'.
Place vehicle key remote in rear of left cupholder (emergency start position).

2

After the "Creating Documentation Updates" process, the integration test is started automatically.
The result must first be ignored.

3

Create Vehicle Analysis Log (VAL) using the PIWIS Tester. Mark the vehicle analysis log you have just
created with the attribute “Pre-VAL” and after carrying out the campaign, return it using the PIWIS
Tester.

4

Update software for various control units to VR10.
For specific information on control unit programming during this campaign, see the table
below.

Information
If programming or coding is aborted, the programming must be carried out again. In order to be able to
invoice for the new programming in scope 2, a screenshot of the general overview must be created at
the end of the programming.

Aug 18, 2023
Page 2 of 11

Required PIWIS Tester software release:

42.100.035 (or higher)

Type of control unit programming:

Control unit programming using the “Campaign”
function in the additional menu on the PIWIS
Tester by entering a programming code.

Programming code:

E3P1A

AfterSales

Service

Technical Information

123/23 ENU

APB1

9

Read and follow the information and instructions
on the PIWIS Tester during the guided
programming sequence.

Programming sequence:

Do not interrupt programming and coding.
After programming has been carried out, the
result of the programming must be checked
and, in the event of deviations from individual
control units, the corresponding control unit
must be re-programmed or re-coded.
A backup documentation process for the
re-programmed software releases starts once
programming and coding is complete.
Programming time (up to):

•
•

270 minutes
The duration of the programming the control
units depends on the build status and can
differ from the specified time.

Control units programmed in this campaign:

•

See  Technical Information 'Overview of
control units VR10'

Procedure in the event of error messages
appearing during the programming sequence:

 Workshop Manual '9X00IN Basic instructions

Procedure in the event of a termination in the
control unit programming:

Continue the campaign sequence to the end,
then carry out the integration test again when
the test is complete and start programming
from the integration test.

and procedure for control unit programming using
the PIWIS Tester - section on “Fault finding”'

Create a screenshot of the overview menu at the
end of programming if one or more control units
have not been successfully programmed or coded.
Additional instructions for aborted programming

 Technical Information '9X00IN Additional
instructions if programming is aborted'
5

Select Instrument cluster control unit.
5.1

Select “Drive links checks”.

5.2

Perform the routine “Reset user and guest accounts”.

AfterSales

Aug 18, 2023
Page 3 of 11

9

Service

Technical Information

ENU 123/23

APB1

This may be listed as "Benutzerkonten und Gastkonten zurücksetzen" in the PIWIS Tester
depending upon tester software Successful execution of the routine is indicated by "Routine
Info: Routine Results: 1."
6

Select Assistance systems control unit.
6.1

Select “Drive links checks”.

6.2

Perform the routine “Coding step 2”.
Successful execution of the routine is indicated by "Routine Results: 1".

6.3

Wait 20 seconds.

6.4

Perform the routine “Front camera, download calibration result”.
Successful execution of the routine is indicated by "Routine Results: 1".

7

8

Select Front-end electronics (BCM1) control unit.
7.1

Select “Maintenance repairs”.

7.2

Perform the “Teach headlight beam adjustment” procedure.
"Adjust headlights mechanically" in the sequence can be skipped.

Select "Central headlights" in the control unit list (only vehicles with I-No. 8IU "HD-Matrix Design
LED Headlights" or 8JU "HD-Matrix Design LED Headlights in Black").
8.1

Select “Maintenance repairs”.

8.2

Perform the "HD matrix headlights, calibration" procedure.
The value “Production” must be used when selecting the Activation value.
Successful execution of the routine is indicated by "Result: 1".

9

Select "Diff. lock" control unit (only vehicles with I-No. GH3 Porsche Torque Vectoring Plus
(PTV+)).
9.1

Select “Maintenance repairs”.

9.2

Perform the “Commissioning” procedure.

10 Perform PSM position detection by operating the brake and P (Park) button. Follow the PCM Central
Display instructions for detecting brake position.
11 Standardize side windows. Teaching the basic window limit positions using the power window
switches.
Information
The wheel electronics must be taught during the test drive and need not be carried out by the technician.

Aug 18, 2023
Page 4 of 11

AfterSales

Service

Technical Information

123/23 ENU

APB1

9

12 Remove the PIWIS Tester (VCI) from the vehicle.
12.1

Lock the vehicle.

12.2

Establish bus idle for at least 5 minutes.

12.3

Re-connect the PIWIS Tester (VCI) after bus idle.

13 Read out all fault memories. If necessary, work through existing faults and delete them.
Information
If control units are found to have faults that are not caused by control unit programming, these
must first be found and corrected. This work cannot be invoiced under the workshop campaign
number.

Information
Faults pertaining to 'Diagnostic access protection', e.g. PSM fault "B184C00 - Vehicle diagnostics
protection - activation activated" are normal side-effects of the security for vehicle diagnosis (SFD)
function and can be ignored.
14 Press •F3“ to start the integration test in the control unit selection.
All affected control units should now be successfully programmed or checked in the control unit
overview and their status.
Information
If a deviation in the integration test is still indicated despite programming being carried out,
programming must be repeated. If the deviation persists, contact Technical Support.
15 Create a Vehicle Analysis Log (VAL) - Service (Serv.) VAL using the PIWIS Tester
Mark the vehicle analysis log you have created with the attribute “Post-VAL” and after carrying out
the campaign, return it using the PIWIS Tester.
16 End the diagnostic application and switch off the vehicle ignition. Before the diagnostic application
closes, the PT4G may again verify the PPN User has sufficient rights for security of vehicle diagnostics and documentation updates.
17 Switch off and disconnect the battery charger.
18 Attach the completed checklist to the PQIS process line.  Technical Information '9X00IN Checklist'
19 Enter the campaign in the Warranty and Maintenance logbook.

AfterSales

Aug 18, 2023
Page 5 of 11

9

Service
APB1

Technical Information

ENU 123/23

Warranty processing
Scope 1:

Re-programming gateway control unit
Labor time:
Re-programming gateway control unit
Includes:
Connecting and disconnecting battery charger
Connecting and disconnecting PIWIS Tester
Updating various control units to software release VR10
Carrying out rework
Reading out and deleting fault memories
Creating Vehicle Analysis Logs (VALs) before and after the
campaign

Labor time: 157 TU

 Damage Number APB1 099 000 1
Scope 2:

Re-programming gateway control unit
Information
Scope 2 may only be invoiced if an error occurred during the first implementation.
For documentation, a screenshot of the programming and coding overview must be uploaded to the
PCSS. It must be clear here that one or more control units have not been successfully programmed or
coded.
The documentation is checked as part of the PSA (Porsche Service Audit).
Labor time:
Re-programming gateway control unit
Includes:
Connecting and disconnecting battery charger
Connecting and disconnecting PIWIS Tester
Updating various control units to software release VR10
Carry out software campaign again due to faulty
programming or coding
Carrying out rework
Reading out and deleting fault memories
Creating Vehicle Analysis Logs (VALs) before and after the
campaign
 Damage Number APB1 099 000 1

Aug 18, 2023
Page 6 of 11

AfterSales

Labor time: 177 TU

Service

Technical Information

123/23 ENU

APB1

9

Overview of VR10 control units
Overview:

Overview of VR10 control units to be programmed
Programming time including coding
of all control units

Control unit

The number of control units to be programmed
depends on the build status and may differ.

Combined software update of various control units
(Update via PIWIS Tester)

Up to 270 minutes

Includes:
Inductive charger for mobile devices

up to 3 minutes

Instrument cluster

up to 30 minutes

PSM

up to 5 minutes

Central headlights

up to 25 minutes

Connect

up to 26 minutes

OBC 11 kW

up to 7 minutes

Assistance systems (zFAS)

up to 90 minutes

Door control unit

up to 36 minutes

Power steering

up to 2 minutes

Front-end electronics

up to 5 minutes

Steering column lock

up to 1 minute

Power electronics

up to 2 minutes

Transverse lock

up to 2 minutes

Airbag

up to 3 minutes

Gateway

Up to 15 minutes

Automatic coding of all control units