AKB4 – Air Bag ECU May Malfunction – 2016-2017 Porsche 911 & Boxster, 2016 Cayman & Panamera

SEOCONTENT-START

Technical Information Service 99/19 ENU AKB4 6 AKB4 – Re-programming Airbag Control Unit (Stop Delivery/Recall Campaign) Model Line: Model Year: Subject: Important: Information: Remedial Action: Panamera (970) Boxster (981)/Cayman (981) 718 Boxster (982)/718 Cayman (982) 911 (991) As of 2016 up to 2017 Airbag control unit CRITICAL WARNING – This campaign includes steps where control unit(s) in the vehicle will be programmed with the PIWIS Tester. The vehicle voltage must be maintained between 13.5 volts and 14.5 volts during this programming. Failure to maintain this voltage could result in damaged control unit(s). Damage caused by inadequate voltage during programming is not a warrantable defect. The technician must verify the actual vehicle voltage in the PIWIS Tester before starting the campaign and also document the actual voltage on the repair order. There is a possibility that an airbag control unit with a defective capacitor for maintaining power supply may have been installed on the affected vehicles. This defective capacitor in the airbag control unit can trigger the airbags and/or seat-belt pretensioners in the vehicle unexpectedly or can prevent them from triggering. Re-program the airbag control unit using the PIWIS Tester with test software version 38.950.010 (or higher) installed. Information The new software includes an additional check function for the power supply of the airbag control unit, which can be used to detect a faulty capacitor. The following procedure is therefore used for processing this campaign (brief overview): General procedure Result of check Additional measure required Warranty processing Only for 982 and 991 from model year 2017: Reading out software version of the airbag control unit • If the SW version is 2050 and the Porsche part number index is greater than 08 No action required Programming is no longer required in this case. Scope 11 AfterSales Jan 15, 2020 Page 1 of 14 Service 6 AKB4 ENU 99/19 Technical Information • Once the airbag warning light has been programmed and checked, no warning message is displayed in the instrument cluster and • no fault memory entry “Airbag triggering unit faulty” (Fault code: C11005) is displayed none Scope 1 (valid for all model lines) Re -program airbag control unit and then check airbag warning light • Once the airbag warning light has been programmed and checked, permanent warning message in the instrument cluster and • fault memory entry “Airbag triggering unit faulty” (Fault code: C11005) are displayed Replacing airbag control unit Scope 2 – 5 or 10 (depending on model line) Special case: Action required Warranty processing • Airbag warning light already active before programming the airbag control unit and • fault memory entry “Airbag triggering unit faulty” (Fault code: C11005) is displayed Replacing airbag control unit Programming is no longer required in this case. Scope 6 – 9 (depending on model line) Affected Vehicles: Only vehicles assigned to the campaign (see also PCSS Vehicle Information). This campaign affects 8,057 vehicles in North America. Required tools Tools: • 9900 – PIWIS Tester 3 with PIWIS Tester software version 38.950.010 (or higher) installed • Battery charger with a current rating of at least 90 A, e.g. VAS 5908 – battery charger 90A or equivalent Jan 15, 2020 Page 2 of 14 AfterSales Technical Information Service 99/19 ENU AKB4 6 • Increased current draw during diagnosis or control unit programming can cause a drop in voltage, which can result in one or more fault entries and the abnormal termination of the programming process.  Before starting control unit programming, connect a suitable battery charger with a current rating of at least 90 A to the vehicle. NOTICE Control unit programming will be aborted if the WLAN connection is unstable. • An unstable WiFi connection can interrupt communication between the PIWIS Tester and the vehicle communication module (VCI). As a result, control unit programming may be aborted.  During control unit programming, always connect the PIWIS Tester to the vehicle communication module (VCI) via the USB cable. NOTICE Control unit programming will be aborted if the driver’s key is not recognized • If the driver’s key is not recognized in the vehicle, programming cannot be started or will be interrupted.  Place the driver’s key with the back facing down into the front left storage compartment in the center console to guarantee a continuous radio link between the vehicle and the driver’s key. Work Procedure: 1 Carry out general preliminary work for control unit programming as described in  Workshop Manual ‘9X00IN Basic instructions and procedure for control unit programming using the PIWIS Tester’. 2 Read out the software version of the airbag control unit: Only for 982 and 991 from model year 2017 • If the SW version is 2050 and the Porsche part number index is greater than 08, programming of the airbag control unit is no longer required. Please close the campaign with a recall update. 3 Before programming the airbag control unit, create a vehicle analysis log (VAL) and mark it with the attribute “Before repair”. 4 Check whether the airbag warning light is displayed in the instrument cluster and the fault memory entry “Airbag triggering unit fault” (Fault code: C11005) is stored in the fault memory. • If this is not the case, continue with the section  Technical Information ‘9X00IN Re-programming the airbag control unit’. • If this is the case, the airbag control unit does not need to be programmed. The airbag control unit must be replaced. For details of procedure, see the section  Technical Information ‘9X00IN Replacing airbag control unit’. AfterSales Page 3 of 14 Preparatory work NOTICE Fault entry in the fault memory and control unit programming aborted due to low-voltage. Jan 15, 2020 Service 6 AKB4 ENU 99/19 Technical Information Information If the airbag warning light is displayed in the instrument cluster and other fault memory entries other than the one mentioned above are stored in the fault memory of the airbag control unit, the fault must be found and rectified separately. This work cannot be invoiced under the campaign number, but must be invoiced using a separate warranty or goodwill claim. In the event of correcting faults in the case of other than the above fault memory entry, it generally applies that: If the airbag control unit remains in the vehicle, programming is required in the context of this campaign. If the airbag control unit has to be replaced, programming is no longer required. Re -programming the airbag control unit and checking the airbag warning light WARNING Electrically moved side windows and rear spoiler • Danger of limbs being trapped or severed • Risk of damage to components  Do not reach into the danger area.  Keep third parties away from the danger area.  Do not move components or tools into the danger area.  Retract roll-up sun blinds on the rear side windows before starting programming or coding. Information The crash data in the airbag control unit is read out during the programming sequence. If crash data that was caused by triggering an airbag or seat-belt pretensioner is entered in an airbag control unit, the airbag control unit cannot be programmed and this will be indicated by the message “Crash data stored in airbag control unit” on the PIWIS Tester. Even if the message “Crash data stored in airbag control unit” is displayed, please try to startprogramming using F8 (Start). • If this is possible and programming was successful, follow the other instructions in the programming sequence and in the Technical Information. • If this is not possible, the airbag control unit must be replaced because of the stored crash data. This can be invoiced under scope 6-9 (depending on model line). There is no need to program the airbag control unit in this case. Jan 15, 2020 Page 4 of 14 AfterSales Technical Information Service 99/19 ENU AKB4 6 Information Each time the airbag control unit is programmed, an extended log (logging) must be created using the PIWIS Tester by pressing the key combination “Ctrl+L”. If problems arise when carrying out the programming sequence, please send the extended log (logging) and a current vehicle analysis log (VAL) to the contact person responsible for your market. The basic procedure for control unit programming is described in the Workshop Manual Workshop Manual ‘9X00IN Basic instructions and procedure for control unit programming using the PIWIS Tester’. For specific information on control unit programming during this campaign, see the table below: Required PIWIS Tester software version: 38.950.010 (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: • 970: D2Q6S • 981: E5K1G • 982: E5K1G • 991: E5K1G Programming sequence: Read and follow the information and instructions on the PIWIS Tester during the guided programming sequence. Do not interrupt programming. Programming time (approx): 4minutes Software version programmed during this campaign for each model line: Panamera (970): 3005 Boxster (981)/Cayman (981): 2045 718 Boxster (982)/718 Cayman (982): 2045 911 (991): 2045 Following control unit programming, the software version can be read out of the control unit for occupant protection in the ‘Extended identification’ menu using the PIWIS Tester. AfterSales Page 5 of 14 Work Procedure: 1 Re-program airbag control unit. Jan 15, 2020 Service 6 AKB4 ENU 99/19 Technical Information Procedure in the event of abnormal termination of control unit programming: • Switch ignition off and then on again. • Read out and erase fault memories Workshop Manual ‘9X00IN Basic instructions and procedure for control unit programming using the PIWIS Tester – section on “Subsequent work”‘. • Repeat control unit programming by entering the programming code again. Procedure in the event of error messages appearing during the programming sequence:  Workshop Manual ‘9X00IN Basic instructions and procedure for control unit programming using the PIWIS Tester – section on “Fault finding”‘. 2 Read out and erase the fault memories of all control units. 2.1 Press •F7“in the control unit selection screen (‘Overview’ menu) to call up the Additional menu. Erasing fault memories 2.2 Select the function “Read all fault memories and erase if required” and press •F12“ (‘Next’) to confirm. The fault memories of the control units are read out. 2.3 Once you have read out the fault memories, check the fault memory entries. 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. If there are faults in the airbag control unit that are not attributable to control unit programming, continue with Step 3. 2.4 Press •F8“ to delete fault memory entries. 2.5 Press •F12“ (‘Yes’) in response to the question as to whether you really want to delete all fault memory entries. The faults stored in the fault memories of the various control units are deleted. Jan 15, 2020 Page 6 of 14 AfterSales Technical Information Service 99/19 ENU AKB4 6 Information If fault memory entries for individual control units cannot be deleted, proceed as follows: • Switch off the ignition. • Disconnect the PIWIS Tester diagnostic connector from the diagnostic socket. • Lock the vehicle using the driver’s key. • Wait approx. 1 minute before unlocking the vehicle again. • Start the engine, leave it running for a short time and then stop it again. • Switch off the ignition and wait approx. 10 seconds before switching it back on again. • Plug the PIWIS Tester diagnostic connector into the diagnostic socket again and restore communication with the vehicle. • Read out the fault memory again and delete any fault memory entries that are stored. • Repeat this procedure if necessary. Control unit selection 2.6 Once you have erased the fault memories, select the ‘Overview’ menu to return to the control unit selection screen. Information The new software includes an additional check function for the power supply of the airbag control unit. For this reason, the airbag warning light must then be checked using the following description and the fault memory of the airbag control unit must be read out again using the PIWIS Tester. 3 Check airbag warning light. 3.1 Switch off the ignition. 3.2 Disconnect the PIWIS Tester diagnostic connector from the diagnostic socket. 3.3 Lock the vehicle using the driver’s key. 3.4 Wait approx. 1 minute before unlocking the vehicle again. 3.5 Start the engine, leave it running for a short time and then stop it again. 3.6 Switch off the ignition and wait approx. 10 seconds before switching it back on again. Observe the airbag warning light in the instrument cluster. This must go out after a short waiting time. 3.7 Also read out the fault memory of the airbag control unit using the PIWIS Tester. AfterSales Page 7 of 14 Jan 15, 2020 Service 6 AKB4 ENU 99/19 Technical Information Result of check Next steps • Airbag warning light in the instrument cluster goes out and • no fault memory entry “Airbag triggering unit faulty” (Fault code: C11005) is displayed Continue with  Technical Information ‘9X00IN Concluding work’. • Airbag warning light in the instrument cluster stays on and • fault memory entry “Airbag triggering unit faulty” (Fault code: C11005) is displayed The airbag control unit must be replaced. To do this, continue with  Technical Information ‘9X00IN Replacing airbag control unit’. Information If the airbag warning light is displayed in the instrument cluster and other fault memory entries other than the one mentioned above are stored in the fault memory of the airbag control unit, the fault must be found and corrected separately. This work cannot be invoiced under the campaign number, but must be invoiced by means of separate warranty or goodwill claim. Replacing airbag control unit Information If the airbag control unit must be replaced during the campaign, programming of the airbag control unit using the test software 2045 or 3005 is no longer required. Work Procedure: 1 Replace airbag control unit and commission it. For instructions, see:  Workshop Manual ‘695319 Removing and installing airbag triggering unit’  Workshop Manual ‘695355 Replacing airbag triggering unit’ Part No. Designation – Use Qty. Vehicles up to model year 2017: 00004399094  Airbag control unit – Boxster (981) / Cayman (981) – 911 (991) 1 ea. or 00004399095  Airbag control unit – Panamera (970) 1 ea. Jan 15, 2020 Page 8 of 14 AfterSales Technical Information Service 99/19 ENU AKB4 6 Vehicles from model year 2017: 00004399037  Airbag control unit – 718 Boxster (982) / 718 Cayman (982) – 911 (991) 1 ea. Concluding work 1 Create a Vehicle Analysis Log (VAL) and mark it with the attribute “Following repairs”. 2 Switch off the ignition. 3 Disconnect the PIWIS Tester from the vehicle. 4 Switch off and disconnect the battery charger. 5 Enter the campaign in the Warranty and Maintenance booklet. Warranty processing Scope 1: Airbag control unit programmed with new software – all model lines • No warning message in the instrument cluster and no fault memory entry” Airbag control unit faulty” (Fault code: C11005)” is stored in the fault memory. Working time: Re-programming airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Checking airbag control unit Creating Vehicle Analysis Log (VAL) Labor time: 81 TU  Damage Code AKB4 099 000 1 AfterSales Page 9 of 14 Jan 15, 2020 Service 6 AKB4 ENU 99/19 Technical Information Working time: Re-programming and replacing airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Removing and installing airbag control unit Commissioning airbag control unit Creating Vehicle Analysis Log (VAL) Labor time: 204 TU Parts required: 00004399095 Airbag control unit 1 ea.  Damage Code AKB4 099 000 2 Scope 3: Airbag control unit programmed with new software and then airbag control unit replaced. • Boxster (981)/Cayman (981) Working time: Re-programming and replacing airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Removing and installing airbag control unit Commissioning airbag control unit Creating Vehicle Analysis Log (VAL) Labor time: 224 TU Parts required: 00004399094 Airbag control unit 1 ea.  Damage Code AKB4 099 000 2 Jan 15, 2020 Page 10 of 14 AfterSales Scope 2: Airbag control unit programmed with new software and then airbag control unit replaced. • Panamera (970) Technical Information Service 99/19 ENU AKB4 6 Working time: Re-programming and replacing airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Removing and installing airbag control unit Commissioning airbag control unit Creating Vehicle Analysis Log (VAL) Labor time: 198 TU Parts required: 00004399037 Airbag control unit 1 ea.  Damage Code AKB4 099 000 2 Scope 5: Airbag control unit programmed with new software and then airbag control unit replaced. • 911 (991) • Vehicles up to model year 2017 Working time: Re-programming and replacing airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Removing and installing airbag control unit Commissioning airbag control unit Creating Vehicle Analysis Log (VAL) Labor time: 250 TU Parts required: 00004399094 Airbag control unit 1 ea.  Damage Code AKB4 099 000 2 AfterSales Page 11 of 14 Scope 4: Airbag control unit programmed with new software and then airbag control unit replaced. • 718 Boxster (982)/718 Cayman (982) Jan 15, 2020 Service 6 AKB4 ENU 99/19 Technical Information Working time: Replacing airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Removing and installing airbag control unit Commissioning airbag control unit Labor time: 165 TU Parts required: 00004399095 Airbag control unit 1 ea.  Damage Code AKB4 099 000 2 Scope 7: Airbag control unit replaced. • Boxster (981)/Cayman (981) Working time: Replacing airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Removing and installing airbag control unit Commissioning airbag control unit Labor time: 174 TU Parts required: 00004399094 Airbag control unit 1 ea.  Damage Code AKB4 099 000 2 Jan 15, 2020 Page 12 of 14 AfterSales Scope 6: Airbag control unit replaced. • Panamera (970) Technical Information Service 99/19 ENU AKB4 6 Working time: Replacing airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Removing and installing airbag control unit Commissioning airbag control unit Labor time: 148 TU Parts required: 00004399037 Airbag control unit 1 ea.  Damage Code AKB4 099 000 2 Scope 9: Airbag control unit replaced. • 911 (991) Working time: Replacing airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Removing and installing airbag control unit Commissioning airbag control unit Labor time: 185 TU Parts required: Vehicles up to model year 2017 00004399094 Airbag control unit 1 ea. Vehicles as of model year 2017 00004399037 Airbag control unit 1 ea.  Damage Code AKB4 099 000 2 AfterSales Page 13 of 14 Scope 8: Airbag control unit replaced. • 718 Boxster (982)/718 Cayman (982) Jan 15, 2020 Service 6 AKB4 ENU 99/19 Technical Information Working time: Re-programming and replacing airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out and erasing fault memory Removing and installing airbag control unit Commissioning airbag control unit Creating Vehicle Analysis Log (VAL) Labor time: 235 TU Parts required: 00004399037 Airbag control unit 1 ea.  Damage Code AKB4 099 000 2 Scope 11: Reading out software version of airbag control unit • 718 Boxster (982)/718 Cayman (982) • 911 (991) from model year 2017 Working time: Reading out software version of airbag control unit Includes: Connecting and disconnecting battery charger Connecting and disconnecting PIWIS Tester Reading out software version Creating Vehicle Analysis Log (VAL) Labor time: 48 TU  Damage Code AKB4 099 000 1 Important Notice: Technical Bulletins issued by Porsche Cars North America, Inc. are intended only for use by professional automotive technicians who have attended Porsche service training courses. They are written to inform those technicians of conditions that may occur on some Porsche vehicles, or to provide information that could assist in the proper servicing of a vehicle. Porsche special tools may be necessary in order to perform certain operations identified in these bulletins. Use of tools and procedures other than those Porsche recommends in these bulletins may be detrimental to the safe operation of your vehicle, and may endanger the people working on it. Properly trained Porsche technicians have the equipment, tools, safety instructions, and know-how to do the job properly and safely. Part numbers listed in these bulletins are for reference only. The work procedures updated electronically in the Porsche PIWIS diagnostic and testing device take precedence and, in the event of a discrepancy, the work procedures in the PIWIS Tester are the ones that must be followed. Jan 15, 2020 Page 14 of 14 AfterSales Scope 10: Airbag control unit programmed with new software and then airbag control unit replaced. • 911 (991) • Vehicles as of model year 2017 © 2020 Porsche Cars North America, Inc.

**************************************************************************************************************

AKB4 Recall campaign – Reprogramming airbag control unit Version 2 English (US)  Important Legal Reminder  DEALERS ARE PROHITIBED BY FEDERAL LAW FROM SELLING CERTAIN VEHICLES WITH AN OPEN RECALL PRIOR TO REMEDYING THEM. DEALERS WHO KNOWINGLY SELL AFFECTED VEHICLES BEFORE REMEDY FACE POTENTIAL FEDERAL PENALTIES OF OVER $22,000.00 PER VEHICLE SOLD AND MAY ALSO FACE STATE LAW PENALTIES. Dealers may also face potential litigation if an un-remedied vehicle is involved in a subsequent accident that causes an injury to vehicle occupants.  Overview  Parts required (only if needed)  Parts Ordering Procedure (only if needed) AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 1 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020 Overview DEALERS ARE FROM SELLING CERTAIN VEHICLES WITH AN OPEN RECALL PRIOR TO REMEDYING THEM. DEALERS WHO KNOWINGLY SELL AFFECTED VEHICLES BEFORE REMEDY Dealers may also face if an un-remedied vehicle is involved in a subsequent accident that causes an injury to vehicle occupants. PROHITIBED BY FEDERAL LAW . FACE POTENTIAL FEDERAL PENALTIES OF OVER $22,000.00 PER VEHICLE SOLD AND MAY ALSO FACE STATE LAW PENALTIES potential litigation Important Legal Reminder AKB4 Recall campaign – Reprogramming airbag control unit  Required software  Warranty processing  Scope 1: Airbag control unit programmed with new software – all model lines  Scope 2: Airbag control unit programmed with new software and airbag control unit then replaced.  Scope 3: Airbag control unit programmed with new software and airbag control unit then replaced.  Scope 4: Airbag control unit programmed with new software and airbag control unit then replaced.  Scope 5: Airbag control unit programmed with new software and airbag control unit then replaced.  Scope 6: Airbag control unit replaced  Scope 7: Airbag control unit replaced  Scope 8: Airbag control unit replaced  Scope 9: Replacing airbag control unit (991)  Scope 10: Airbag control unit programmed with new software and airbag control unit then replaced.  Further information There is a possibility that an airbag control unit with a capacitor for maintaining power supply, which is out of specification, may have been installed on the affected vehicles. If the capacitor in the airbag control unit is out of specification, it could potentially trigger the airbags and/or seat-belt pretensioners in the vehicle unexpectedly or can prevent them from triggering. AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 2 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020 To prevent this from happening, the airbag control unit must be programmed with new software, which contains an additional function for checking the power supply. Model type Panamera (970) Boxster (981) 718 Boxster (982) Cayman (981) 718 Cayman (982) 911 (991) Model year 2016 – 2017 Number 7,515 General information about the new software for the airbag control unit: The new software includes an additional check function for the power supply of the airbag control unit, which can be used to detect a faulty capacitor. The following procedure is therefore used for processing this campaign (brief overview): General procedure Result of check Additional action required Warranty processing Reprogram airbag control unit and check airbag warning light • No warning message in the instrument cluster and • no fault memory entry “Airbag triggering unit faulty” (Fault code: C11005) is displayed None (valid for all model lines) Scope 1 • Once the programming is complete, Replace airbag control unit or (depending on model line) Scope 2 – 5 10 AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 3 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020 General procedure Result of check Additional action required Warranty processing permanent warning message in the instrument cluster and • fault memory entry “Airbag triggering unit faulty” (Fault code: C11005) is displayed Special case Action required Warranty processing • Airbag warning light already active before the airbag control unit has been programmed and • fault memory entry “Airbag triggering unit faulty” (Fault code: C11005) is displayed Replacing airbag control unit Programming is no longer required in this case. (depending on model line) Scope 6 – 9 Important Note: The ACU will be checked during the reprogramming procedure for crash data. If there is any crash data stored on the ACU, the following information will be displayed on the PIWIS Tester: “Crash data is stored in the airbag control unit”. If this is found to be the case, please continue reprogramming by pressing (start) on F8 the PIWIS Tester. • If it is possible to reprogram the ACU, please follow the instructions on the PIWIS Tester and in the Technical Information. • If it is possible to reprogram the ACU, please replace the ACU and invoice the warranty claim scope 2-5, depending on the model type. not If the airbag control unit has to be replaced, a reprogramming of the airbag control unit with the campaign specific software 2045 or 3005 is not necessary anymore. Extended warranty: AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 4 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020 Parts required (only if needed) Vehicles affected by AKB4 will also be provided an extended warranty for the airbag control unit. The extended warranty will be displayed as an additional new vehicle warranty scope and contains the added information “Extended warranty airbag control unit” in the “coverage” section of PCSS. For more information, please see PPN News “Extended warranty for the airbag control unit – vehicles affected by recall campaign AKB4”. Pre-owned vehicle sales: A pre-owned vehicle with an open recall must not be used on public roads by a Porsche Dealer and therefore must not be handed over to customers. Likewise, a pre-owned car warranty can never be provided while a recall campaign is open. Part No. Designation Quantity/vehicle Parts return* Vehicles up to model year 2017 00004399094 Airbag control unit (981, 991) 1 unit No 00004399095 Airbag control unit (970) 1 unit No Vehicles as of model year 2017 00004399037 Airbag control unit (982, 991) 1 unit No *The parts must be stored until such a time as the in WWS. If a with the credit note, the affected part must be sent to Porsche AG as usual. If no barcode is generated with the credit note, the part can go directly into the genuine remanufactured parts process or be scrapped. related warranty or campaign claim has been credited barcode is generated AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 5 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020 Scope 1: Airbag control unit programmed with new software – all model lines Warranty processing Required software Parts Ordering Procedure (only if needed) • Expected Airbag Control Unit part failure rate (determined after reprogramming) is approximately 1%. • In order to ensure a fair distribution of parts, dealers will need to upload a VAL showing fault C11005 after programming to their PQIS job prior to creating the PRMS parts request in order to release the part. • If an active airbag light is illuminated when the vehicle arrives, a VAL upload showing fault code C11005 will be required for parts release. • VINs on the VIN List with scopes 8 or 9 listed (highlighted) may be ordered via PRMS parts request, without VAL. These vehicles do not require Control Unit reprogramming prior to replacement. PIWIS Tester 3 tester software version 38.950.010 (or higher) Please enter the campaign that was carried out in the Warranty and Maintenance booklet for the vehicle. • in the instrument cluster and “Airbag control unit faulty (Fault code: C11005)” is stored in the fault memory. No warning message no fault memory entry Damage code AKB4 99 000 AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 6 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020 Scope 5: Airbag control unit programmed with new software and airbag control unit then replaced. Scope 4: Airbag control unit programmed with new software and airbag control unit then replaced. Scope 3: Airbag control unit programmed with new software and airbag control unit then replaced. Scope 2: Airbag control unit programmed with new software and airbag control unit then replaced. Repair code 1 Working time 81 TU • Panamera (970) Damage code AKB4 99 000 Repair code 2 Working time 204 TU • Boxster (981)/Cayman (981) Damage code AKB4 99 000 Repair code 2 Working time 224 TU • 718 Boxster (982)/718 Cayman (982) Damage code AKB4 99 000 Repair code 2 Working time 198 TU • 911 (991) • Vehicles up to model year 2017 Damage code AKB4 99 000 Repair code 2 AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 7 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020 Scope 10: Airbag control unit programmed with new software and airbag control unit then replaced. Scope 9: Replacing airbag control unit (991) Scope 8: Airbag control unit replaced Scope 7: Airbag control unit replaced Scope 6: Airbag control unit replaced Working time 250 TU • Panamera (970) Damage code AKB4 99 000 Repair code 2 Working time 165 TU • Boxster (981)/Cayman (981) Damage code AKB4 99 000 Repair code 2 Working time 174 TU • 718 Boxster (982)/718 Cayman (982) Damage code AKB4 99 000 Repair code 2 Working time 148 TU • Vehicles on which the airbag control unit was replaced before the start of the campaign. Damage code AKB4 99 000 Repair code 2 Working time 185 TU • 911 (991) • Vehicles as of model year 2017 AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 8 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020 Categories: Recalls, 911 Carrera, Boxster, Cayman, Panamera, Stop Sale Tags : 991, 981, 970, 982, recall campaign, stop delivery, year k, akb4 522 Views AKB4 VIN List.xlsx 176.8 KB (15 views) STB 6 99-19 AKB4 Re-programming Airbag Control Unit.pdf 341.0 KB (56 views) Created by Ryan Cooney on Jan 15, 2020 5:03 PM. Last modified by Ryan Cooney on Jan 16, 2020 12:03 AM. Further information Damage code AKB4 99 000 Repair code 2 Working time 235 TU Work instruction TI No. /19, Group 99 6, Service, AKB4 Vehicle list and allocation See Attached VIN List Technical Information See PCSS or the attached TI for reference AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 9 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020 Content and Topics Personal Manage Create © 2020 Dr. Ing. h.c. F. Porsche AG. Legal notice. Copyright. Terms of use. Privacy Policy. Cookie Policy. 009 Your Groups  Your Content  Your Places  View Profile  Edit Profile  Preferences  Add-Ons  Change Password  Admin Console  PPN Administration Discussion  Files  Document  Collaboration Document  Blog Post  Poll  Message  Event  Photo Album  Idea  Space  AKB4 Recall campaign – Reprogramming airbag con… | PPN Portal Page 10 of 10 https://ppn.porsche.com/portal/docs/DOC-279041 1/17/2020

**************************************************************************************************************

General Reimbursement Plan of Porsche Cars North America Inc. Porsche Cars North America, Inc. (“PCNA”) submits the following general reimbursement plan in accordance with 49 U.S.C. S 80120(d) and 49 C.F.R S 573.6(c)(8)(i) to reimburse owners and purchasers for costs incurred for remedies in advance of PCNA’s notification of safety-related defects and noncompliance with Federal Motor Vehicle Safety Standards under subsection (b) or (c) of 49 U.S.C. S 301 18 (“the Plan”). 1. Reimbursement Period. a. The beginning date for reimbursement shall be determined as follows: (i) For a noncompliance with a Federal Motor Vehicle Safety Standard, the beginning date for reimbursement shall be the date of the first test or observation by either NHTSA or the manufacturer indicating that a noncompliance may exist. (ii) For a safety-related defect that is determined to exist following the opening of an Engineering Analysis (EA) by NHTSA’s Office of Defects Investigation (ODI), the beginning date for reimbursement shall be the date the EA was opened, or one (1) year before the date of PCNA’s notification to NHTSA pursuant to 49 C.F.R. S 573.6, whichever is earlier. (iii) For a safety-related defect that is determined to exist in the absence of the opening of an EA, the beginning date for reimbursement shall be one (1) year before the date of PCNA’s notification to NHTSA pursuant to 49 C.F.R S 578.6. b. The ending date for reimbursement shall be ten (10) calendar days after the date on which PCNA mailed the last of its owner notifications pursuant to 49 C.F.R. Part 577. c. PCNA may choose to extend the reimbursement periods for a particular recall in its discretion. 2. Reimbursement Conditions. PCNA will reimburse owners and purchasers for pre-notification repair or replacement subject to the following conditions: a. PCNA will not reimburse for costs incurred within the period during which a PCNA original or a PCNA issued extended warranty would have provided for a free repair without any payment by the consumer of the defect addressed by the recall unless (i) the customer submitted the vehicle to a franchised dealer or authorized representative of PCNA, who then denied warranty coverage or (ii) the repair made under warranty did not remedy the defect addressed by the recall. Any warranty covered by this subsection must be in writing. b. PCNA will not reimburse owners or purchasers: (i) If the pre-recall notification repair was not of the same type (repair, replacement or refund of purchase price) as the recall remedy; (ii) If the pre-recall notification repair did not address the defect or noncompliance that led to the recall or a manifestation of the defect or noncompliance; or (iii) If the pre-recall notification repair was not reasonably necessary to correct the defect or noncompliance that led to the recall or a manifestation of the defect or noncompliance. However, nothing stated in subsection 2.b shall require that the pre-recall notification repair be identical to the recall remedy. 3. Amount of Reimbursement. The amount of reimbursement shall be limited to out of pocket costs incurred by the owner of the vehicle at the time of the pre-recall notification repair as set forth below: a. For parts, labor, and miscellaneous fees such as disposal of waste and taxes for the pre-recall notification repair; b. Regardless of subsection 8.a., the reimbursed costs for labor shall be limited to the standard local labor rate at the time of the pre-recall notification repair charged by the nearest authorized Porsche dealership for such a repair. c. Regardless of subsection 8.a., the reimbursed costs for parts shall be limited to PCNA’s retail price for authorized parts at the time of the pre-recall notification repair. d. Any other costs, whether associated, consequential, or otherwise, will not be reimbursed. 4. Documentation Necessary to Obtain Reimbursement. The following documentation must be submitted to obtain reimbursement: a. Name and address of the claimant; b. Documentation establishing vehicle ownership by the claimant at the time of the pre-recall notification repair; c. Documentation establishing vehicle make, model, model year and Vehicle Identification Number (VIN); d. PCNA’s recall number or NHTSA’s recall number; e. A receipt, such as a dealership Repair Order, invoice, or payment information for the pre-recall notification repair. (i) Such documentation should provide sufficient information to reflect that the pre-recall notification repair addressed the same defect or noncompliance that is to be addressed by the recall. If the documentation does not do that, additional documentation should be provided by the claimant to make such connection clear. (ii) If reimbursement is sought for the replacement of a vehicle part, the receipt must identify the replaced part and state the total amount paid for the part that replaced the defective or noncompliant part. f. If the pre-recall notification remedy was obtained at a time when the vehicle could have been repaired or replaced at no charge under PCNA’s original or extended warranty program, the claimant must provide documentation indicating that (a) an authorized Porsche dealer or repair facility refused to remedy the problem addressed by the recall under the warranty or (b) the repair obtained under warranty did not correct the problem addressed by the recall. 5. Where Reimbursement Documents are to be Submitted. PCNA will not reimburse claimants who do not submit adequate documentation to PCNA at the following address: Porsche Cars North America, Inc. Attn: Customer Commitment Department One Porsche Drive Atlanta, GA 30354 6. Response to Request for Reimbursement. a. PCNA will act upon a claim for reimbursement within sixty (60) days of its receipt. If PCNA denies the claim, PCNA will send a notice to the claimant within sixty (60) days of receipt of the claim, which will contain a clear, concise statement of the reasons for the denial. b. If the claim for reimbursement was incomplete when originally submitted, PCNA will advise the claimant within sixty (60) days of receipt of the claim of the documentation that is needed and offer the claimant an opportunity in writing to resubmit the claim with complete documentation. c. Any disputes over the denial in whole or in part of a claim for reimbursement shall be resolved between the claimant and PCNA. PCNA acknowledges NHTSA’s statement that it will not mediate or resolve any disputes regarding the eligibility for, or the amount of, reimbursement. 7. Form of Reimbursement. If the claim is approved in whole or in part, reimbursement will be provided in the form of a check. 8. Non-application. Reimbursement for a pre-recall notification remedy shall not be provided to an owner pursuant to this Plan if the vehicle was bought by the first purchaser more than 15 calendar years before notice was given by PCNA under 49 U.S.C. S 301 18(c) or an order was issued under 49 U.S.C. S 301 181b). 9. Recalls Concerning Labels. PCNA will not reimburse owners or purchasers for recalls based solely on noncompliant or defective labels. 10. Reimbursement Plan Availability to the Public. PCNA will make a copy of this Plan available to members of the public upon request.

SEOCONTENT-END