AKC1 – Hazard Warning Lights May Not Activate – 2020 Porsche 911 Carrera

“This site contains affiliate links for which OEMDTC may be compensated”

December 11, 2019 NHTSA CAMPAIGN NUMBER: 19V878000

Hazard Warning Lights May Not Activate

If the hazard warning lights cannot be activated, there is an increased risk of a crash in a hazard situation.

 

NHTSA Campaign Number: 19V878

Manufacturer Porsche Cars North America, Inc.

Components EXTERIOR LIGHTING

Potential Number of Units Affected 1,928

 

Summary

Porsche Cars North America, Inc. (Porsche) is recalling certain 2020 911 Carrera S Coupe, Cabrio, Coupe, 4 Coupe, 4S Coupe, 4 Cabrio, 4S Cabrio, and S Cabrio vehicles. Due to a software error, the hazard warning lights may not function may when activated by an operator. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 108, “Lamps, Reflective Devices, and Associated Equipment.”

 

Remedy

Porsche will notify owners, and dealers will reprogram the control unit, free of charge. The recall began February 7, 2020. Owners may contact Porsche customer service at 1-800-767-7243. Porsche’s number for this recall is AKC1.

 

Notes

Owners may also contact the National Highway Traffic Safety Administration Vehicle Safety Hotline at 1-888-327-4236 (TTY 1-800-424-9153), or go to www.safercar.gov.

 

Check if your Porsche has a Recall

 


AKC1 – Re-programming Operator Control Unit in Front Center Console and Updating Software for Various Control Units (Stop Delivery/Recall Campaign)

Important: 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
Model Year: 2020
Vehicle type: 911 (992)
Subject:

* Depending on equipment (battery sensor will only be programmed if a Lithium starter battery (I-no. J2A) is installed.)

Information: Due to a software error, there is a possibility that the hazard warning lights will not be activated after pressing the button in the center console in certain situations on the affected vehicles. Failure of the hazard warning lights can result in an increased risk if the vehicle is not perceived as an obstacle.
Remedial Action: Re-program operator control unit in front center console and update software for the following control units using the PIWIS Tester with test software version 39.000.020 (or higher) installed:

Information

The following control units are re-programmed and then re-coded automatically during the campaign using three separate programming codes.

Control unit Programming code
  • Operator control unit in front center console
X5R1R
  • Battery sensor*
  • Selector lever control unit
  • Instrument cluster
  • Brake electronics (PSM incl. parking brake) control unit
  • Front axle lift system control unit*
  • Control unit for chassis control (PASM)
V9Q8Z
T7G1A

 

* Depending on equipment (battery sensor will only be programmed if a Lithium starter battery (I-no. J2A) is installed.)

The time required for programming and coding the control units is up to approx. 70 minutes, depending on equipment.

Affected Vehicles: Only vehicles assigned to the campaign (see also PCSS Vehicle Information). This campaign affects 1,928 vehicles in North America.

 

Required tools

Information

The new 911 (992) comes with either a lithium starter battery (I-no. J2A) or an AGM starter battery (I-no. J0V, J4K) as standard.

This depends on the following:

  • Country version
  • Model type
  • Vehicle equipment

Lithium starter batteries must only be charged using a suitable battery charger that has a current and voltage-controlled charge map.

For further information about the battery chargers to be used, seeWorkshop Manual ‘270689 Charging battery/vehicle electrical system’.

 

Tools:

  • Battery charger with a current rating of at least 90 A and – if required – also with a current and voltage-controlled charge map for lithium starter batteries, e.g. VAS 5908 – Battery charger 90A
  • 9900 – PIWIS Tester 3 with PIWIS Tester software version 000.020 (or higher) installed

 

Preparatory work

NOTICE

Fault entry in the fault memory and control unit programming aborted due to low voltage.

  • 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 in the area in front of the storage compartment under the armrest (emergency start tray) in order to guarantee a permanent radio link between the vehicle and driver’s key.

 

NOTICE

Programming interrupted

  • Malfunctions in control unit
  • Risk of damage to control unit

⇒ Route the line between the vehicle communication module (VCI) and diagnostic socket on the vehicle without tension and make sure that the connector is inserted fully into the diagnostic socket.

⇒ Check that the rechargeable battery for the PIWIS Tester is charged sufficiently. Connect the PIWIS Tester to the power supply unit if necessary.

 

Information

To carry out the campaign, the PIWIS Tester must be online and logged into the Porsche Partner Network (PPN).

 

Information

The procedure described here is based on the PIWIS Tester 3 software version 39.000.020.

The PIWIS Tester instructions take precedence and in the event of a discrepancy, these are the instructions that must be followed.

A discrepancy may arise with later software versions for example.

Procedure:

1.  Connect a suitable battery charger, e.g. VAS 5908 – Battery charger 90A, to the jump-start terminals in the luggage compartment and switch it on.

2. Place the driver’s key with the back facing down in the area in front of the storage compartment under the armrest (emergency start tray) in order to guarantee a permanent radio link between the vehicle and driver’s keyEmergency start tray.

3. Connect the 9900 – PIWIS Tester 3 to the Vehicle Communication Module (VCI) via the USB cable.

Then, connect the Communication Module to the vehicle and switch on the PIWIS Tester.

Due to the long programming time, connect the PIWIS Tester to the power supply during the operation.

 

Information

Use the new PIWIS Tester data cable for carrying out the campaign. The difference between the old ⇒  PIWIS Tester data cable -1- and new ⇒ PIWIS Tester data cable -2- data cable is shown in the illustration.

If the connection between the vehicle and PIWIS

Tester is interrupted, check the data cable for the PIWIS Tester for signs of damage. If the data cable is damaged, it must be replaced. To do this, follow the instructions in the PPN for “Returning faulty USB cable caps” (PPN portal > Dr Ing. h.c. F. Porsche AG > Aftersales > Workshop > PIWIS > Documents).

4. Switch on the ignition.

5.

On the PIWIS Tester start screen, call up the ‘Diagnostics’ application.

The vehicle type is then read out, the diagnostic application is started and the control unit selection screen is populated.

6. Log the PIWIS Tester into the PPN.

 

Re-programming front operator control unit

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.

Work Procedure:

1. The basic procedure for control unit programming is described in the Workshop ManualWorkshop 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: 39.000.020 (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: X5R1R
Programming sequence: Read and follow the information and instructions on the PIWIS Tester during the guided programming sequence.

Do not interrupt programming and coding.

A backup documentation process for the re-programmed software versions starts as soon as programming and coding is complete.

Programming time (approx): 3 minutes

 

Software version programmed during this campaign: 1420
Following control unit programming, the software version can be read out of the control unit for the operator control unit in front center console in the ‘Extended identifications’ menu using the PIWIS Tester.
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.
  • 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. Continue with Updating software for various control units ⇒ Technical Information ‘9X00IN Updating software for various control units’.

 

Updating software for various control units

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.

 

Information

The fan runs several times for a few seconds during the programming sequence.

 

Information

The PIWIS Tester automatically performs the programming sequence described below. This does not require any interaction with the PIWIS Tester.

Control units that are not installed are skipped automatically.

The time required for the update depends on the respective vehicle equipment and can be up to 65 minutes.

The following control units are re-programmed and then re-coded in the specified sequence:

  • Battery sensor*
  • Selector lever control unit
  • Instrument cluster
  • Front axle lift system control unit*
  • Brake electronics (PSM incl. parking brake) control unit
  • Control unit for chassis control (PASM)

* Depending on equipment (battery sensor will only be programmed if a Lithium starter battery (I-no. J2A) is installed.)

 

Work Procedure:

1. The basic procedure for control unit programming is described in the Workshop ManualWorkshop 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: 39.000.020 (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: V9Q8Z
Programming sequence: Read and follow the information and instructions on the PIWIS Tester during the guided programming sequence.

Do not interrupt programming and coding.

A backup documentation process for the re-programmed software versions starts as soon as programming and coding is complete.

Programming time (approx): up to 70 minutes*

* The time required for the update depends on the respective vehicle equipment.

Software versions programmed during this campaign:
  • Selector lever control unit – 0240
Following control unit programming, the software version can be read out of the relevant control unit in the ‘Extended identifications’ menu using the PIWIS Tester.
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.
  • 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. Continue with Re-programming control unit for Tire Pressure Monitoring (TPM) Technical Information ‘9X00IN Re-programming control unit for Tyre Pressure Monitoring (TPM)’.

 

Re-programming control unit for Tire Pressure Monitoring (TPM)

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.

 

Procedure:

1. The basic procedure for control unit programming is described in the Workshop ManualWorkshop 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: 39.000.020 (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: T7G1A
Programming sequence: Read and follow the information and instructions on the PIWIS Tester during the guided programming sequence.

Do not interrupt programming and coding.

A backup documentation process for the re-programmed software versions starts as soon as programming and coding is complete.

Programming time (approx): 2 minutes
Software version programmed during this campaign: 0220
Following control unit programming, the software version can be read out from the control unit for Tire Pressure Monitoring (TPM) in the ⇒ ‘Extended identification’ menu using the PIWIS Tester.
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.
  • 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”‘.

 

Concluding work

WARNING

Electrically moved 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.

Procedure:

1. Read out and erase the fault memories of all control units.

1.1 Press •F7“ in the control unit selection screen (‘Overview’ menu) to call up the Additional menu.

1.2 Select the function “Read all fault memories and erase if required” and press •F12“ (‘Next’) to confirm your selection Erasing fault memories.

The fault memories of the control units are read out.

1.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.

1.4 Press •F8“ to delete fault memory entries.

1.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.

 

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.

 

1.6 Once you have erased the fault memories, select the ‘Overview’ menu to return to the control unit selection screen ⇒ Control unit selection.

2. Manually retract the rear spoiler that was extended automatically during programming.

For this purpose, select the menu ‘C AR’ ‘DRIVE’ in the PCM, then select the ‘Spoiler’ function and press and hold the spoiler button until the rear spoiler is fully retracted.

3. Switch off the ignition.

4. Disconnect the PIWIS Tester from the vehicle.

5. Switch off and disconnect the battery charger.

6. Enter the campaign in the Warranty and Maintenance booklet.

 

Warranty processing

Scope 1:

Working time:

Re-programming operator control unit in front center console and updating software for various control units Includes:

Connecting and disconnecting battery charger

Connecting and disconnecting PIWIS Tester

Re-programming operator control unit in front center console

Re-programming instrument cluster

Re-programming selector lever control unit

Re-programming battery sensor

Re-coding front axle lift system control unit

Re-coding control unit for chassis control (PASM) Re-coding brake electronics (PSM incl. parking brake) control unit

Re-programming control unit for Tire Pressure Monitoring

(TPM)

Teaching wheel electronics

Reading out and erasing fault memories

⇒Damage Code AKC1 099 000 1

Labor time: 83 TU

 


Stop Delivery Remedial Measure

911 Carrera (992), MY 2020

AKC1 Stop Delivery –Reprogramming control unit for the front center console and updating software for various control units

 

Reason:

Due to a software error, if a specific sequence is followed, the hazard warning lamps may not activate when the hazard warning lamp switch is activated.

 

Remedial action:

Re-programming control unit for the front center console and updating software software for various control units using the PIWIS Tester with test software version 39.050.012 (or higher) installed.

During the campaign, all affected control units will be re-programmed with three different Tester sequences and then recoded automatically.

Control units Re-programming Coding Programming code:
  • Front center console
X X X5R1R
  • Selector lever control unit
  • Instrument cluster
  • Front axle lift system control unit*
  • Brake electronics (PSM incl. parking brake) control unit
  • Control unit for chassis control (PASM)
X

X

X

 

 

 

X

X

X

X

X

X

V9Q8Z
X X T7G1A

 

* Depending on equipment

 

The time required for programming and coding the control units is up to approx. 70 minutes, depending on equipment.

 

Required tools:

The new 911 (992) comes with either a lithium starter battery (I-no. J2A) or an AGM starter battery (I-no. J0V, J4K) as standard.

This depends on the following:

  • Country version
  • Model type
  • Vehicle equipment

Lithium starter batteries must only be charged using a suitable battery charger that has a current and voltage-controlled charge map.

For further information about the battery chargers to be used, see× Workshop Manual ‘270689 Charging battery/vehicle electrical system’.

  • Battery charger with a current rating of at least 90 A and – if required – also with a current and voltage-controlled charge map for lithium starter batteries, e.g. VAS 5908 – Battery charger 90A
  • 9900 – PIWIS Tester 3 with PIWIS Tester test software version 050.012 (or higher) installed

 

Preliminary work

To carry out the campaign, the PIWIS Tester must be online and logged into the Porsche Partner Network (PPN).

The procedure described here is based on the PIWIS Tester 3 software version 39.050.012.

The PIWIS Tester instructions take precedence and in the event of a discrepancy, these are the instructions that must be followed. A discrepancy may arise with later software versions for example.

  1. Connect a suitable battery charger, e.g. VAS 5908 – Battery charger 90A, to the jump-start terminals in the luggage compartment and switch on.
  2. Place the driver’s key with the back facing down in the area in front of the storage compartment under the armrest (emergency start tray) in order to guarantee a permanent radio link between the vehicle and driver’s key. ⇒ Emergency start tray

 

  1. Connect the 9900 – PIWIS Tester 3 to the Vehicle Communication Module (VCI) via the USB cable. Then, connect the Communication Module to the vehicle and switch on the PIWIS Tester. Due to the long programming time, connect the PIWIS Tester to the power supply during the operation.
  1. Switch on the ignition.
  2. On the PIWIS Tester start screen, call up the ‘Diagnostics‘ application.

The vehicle type is then read out, the diagnostic application is started and the control unit selection screen is populated.

  1. Log the tester into the PPN.

 

Re-programming control unit for the front center console and updating software software for various control units

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.

  1. Control unit programming using the “Campaign“ function in the Additional menu on the PIWIS Tester by entering a programming code. 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’.
  2. Re-programming control unit for the front center console.
Programming code: X5R1R
Programming time (approx): 3 minutes
Software version programmed during this campaign: 1420

 

  1. Re-programming battery sensor, selector lever control unit and Instrument cluster.
Programming code: V9Q8Z
Programming time (approx): up to 65 minutes
Software version programmed during this campaign:

0152

0240

0206

 

  1. Re-programming Control unit for Tire Pressure monitoring.
Programming code: T7G1A
Programming time (approx): 2 minutes
Software version programmed during this campaign: 0220

 

  1. Re-teach wheel electronics ⇒ Workshop Manual ‘443225 Teaching wheel electronics’.

 

Subsequent work

  1. Read out and erase the fault memories of all control units.
  2. Manually retract the rear spoiler that was extended automatically during programming.
  1. For this purpose, select the menu ‘CAR’ ‘DRIVE’ in the PCM, then select the ‘Spoiler‘ function and press and hold the spoiler button until the rear spoiler is fully retracted.
  2. Switch off the ignition.
  3. Disconnect the PIWIS Tester from the vehicle.
  4. Switch off and disconnect the battery charger.
  5. If the parking brake switch is flashing rapidly, activate and deactivate the switch until the functionality returns.

 

Warranty processing

Scope 1:

Working time:

Re-programming control unit for the front center console and updating software software for various control units Includes: Connecting and disconnecting battery charger

Connecting and disconnecting PIWIS Tester

Re-programming control unit for the front center console

Re-programming instrument cluster

Re-programming selector lever control unit Re-programming battery sensor

Re-coding front axle lift system control unit

Re-coding chassis control (PASM) control unit

Re-coding brake electronics (PSM incl. parking brake) control unit

Re-programming control unit for Tire Pressure Monitoring (TPM) Teaching wheel electronics Reading out and erasing fault memory

Invoicing:  Damage Code AKC1 99 000, Repair Code 1

Working time: 83 TU

 


February 07, 2020

 

This notice applies to your vehicle:

 

URGENT SAFETY RECALL

 

This is an important Safety Recall. The remedy will be performed FREE OF CHARGE to you.

 

IMPORTANT SAFETY RECALL

 

Certain 2020 Model Year Porsche 911 Vehicles Control Unit Reprogramming for Hazard Warning NHTSA Recall 19V 878

 

Dear Mr.

This notice is sent to you in accordance with the National Traffic and Motor Vehicle Safety Act. Porsche has decided that certain 2020 Model Year Porsche 917 . vehicles fail to conform to Federal Motor Vehicle Safety Standard No. 108 “Lamps, reflective devices and associated equipment ”

 

You received this notice because our records indicate that you are the current owner of a vehicle affected by this recall.

 

What should you do?

 

Please contact any authorized Porsche dealer to schedule an appointment to have the remedy performed as soon as possible and to arrange for alternate transportation during the repair period, if needed .

 

To find your nearest authorized Porsche dealer, visit: www.porsche.com/usa

 

What is the issue?

Under certain specific conditions, there is a possibility that the hazard warning lights may not activate after pressing the switch in the center console. If the hazard warning cannot be activated, this may increase the risk of a crash in a hazard situation.

 

What will Porsche do?

Porsche is conducting a safety recall to reprogram the control unit to eliminate this issue.

 

In addition to the recall remedy, Porsche will take advantage of this service opportunity to update additional software in your vehicle to the latest specification.

 

 

What if you are not the owner or operator of this vehicle?

If you are the lessor and registered owner of the vehicle identified in this action, the law requires you to forward this letter immediately via first-class mail to the lessee within ten days of receipt of this notice.

 

If you have changed your address or sold the vehicle, please fill out the enclosed prepaid Owner Reply Card and mail it to us so we can update our records.

 

Can we assist you further? 

Please be aware that if you require any assistance in making an appointment to have this recall performed, please call or write:

Porsche Cars North America, Inc.
Attn: Customer Commitment Department
One Porsche Drive
Atlanta, GA 30354 1-800-PORSCHE
customer.commitment@porsche.us

 

If you believe that the dealer or Porsche has failed or is unable to perform the remedy without charge or within a reasonable amount of time, you may file a complaint to the Administrator, National Highway Traffic Safety

Administration, 1200 New Jersey Avenue, S.E., Washington, D.C. 20590 or call the toll-free Vehicle Safety Hotline at 1-888-327-4236 (TTY: 1-800-424-9153) or go to: https://www.safercar.gov

 

We apologize for any inconvenience this matter may cause you. We are taking this action to help ensure your safety and continued satisfaction with your vehicle.

 

 

Very truly yours,

Porsche Cars North America, Inc.

 


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.

 


1 Affected Product

Vehicle

MAKE MODEL YEAR
PORSCHE 911 CARRERA 2020

 


11 Associated Documents

Recall Quarterly Report

RCLQRT-19V878-9823.PDF 211.149KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [206.20 KB]

 


Recall Quarterly Report #2, 2020-2

RCLQRT-19V878-0813.PDF 211.248KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [206.30 KB]

 


Remedy Instructions and TSB

RCRIT-19V878-1030.pdf 178.163KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [173.99 KB]

 


ISSUED Owner Notification Letter(Part 577)

RCONL-19V878-5900.pdf 96.956KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [94.68 KB]

 


Part 577 Owner Notification Envelope

RONE-19V878-2824.pdf 44.162KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [43.13 KB]

 


Remedy Instructions and TSB

RCRIT-19V878-6305.pdf 310.289KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [303.02 KB]

 


Manufacturer Notices(to Dealers,etc)

RCMN-19V878-1902.pdf 140.061KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [136.78 KB]

 


Non-Compliance Notice 573 Report

RCLRPT-19V878-3152.PDF 216.763KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [211.68 KB]

 


Recall Acknowledgement

RCAK-19V878-9058.pdf 320.78KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [313.26 KB]

 


Manufacturer Reimbursement Plan

RMRP-19V878-0148.pdf 4067.841KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [3.88 MB]

 


Recall Quarterly Report #3, 2020-3

RCLQRT-19V878-1281.PDF 211.332KB

Loader Loading...
EAD Logo Taking too long?

Reload Reload document
| Open Open in new tab

Download [206.38 KB]

 


Latest Recalls Documents

For the Latest and Most Recent Recalls Information Visit the link below…

https://www-odi.nhtsa.dot.gov/acms/cs/documentList.xhtml?docId=19V878&docType=RCL

 


 

Reprogramming

For reprogramming and flashing Porsche vehicles without a factory diagnostic device, Porsche recommends the following devices:

Recommended Pass Thru Devices:

 

J2534 Device

CarDAQ-Plus 3 All Makes J2534 Reprogramming Tool
RAP2 OEM J2534 Remote Reprogramming Tool
CarDAQ-Plus 2 Diagnostic Code Reader and J2534 Programming Tool
Drew Technologies (DRWCDPLUSKIT) CarDAQ-Plus J2534 Flash Reprogramming Kit
Bosch Automotive Tools MTECH2 Mastertech II J2534 VCI with Wired/Wireless Capability for OEM Reprogramming and Diagnostics on GM, Ford, FCA, Nissan/Infiniti, Honda/Acura, and Toyota/Lexus Vehicles
Autel MaxiFlash Elite VCI J2534 Pass-Thru ECU Programming Tool
Autel MaxiFlash VCI Vehicle Communication Interface J2534 PassThru ECU Programming Device Bluetooth Connection Internet Update Support CAN FD, 4 CAN Channels, DoIP, D-PDU Works with PC or Autel MS909
VXDIAG VCX Nano Compatible for GM/OPEL with GDS2 and Tech2WIN System Diagnostic Tool
GODIAG J2534

 

Porsche is not responsible for any content on these two external sites

 


Pass Thru - Check ECU

Pass Thru - ECU Check verifies the vehicle compliance with the latest air polution restrictions of the following organisations:

- Environmental Protection Agency (EPA)
- California Air Resources Board (CARB).

 

Pass Thru - Check ECU checks the Vehicle Identification Number (VIN) stored in the vehicles Digital Motor Electronic (ECU) against the PAG database.

Pass Thru - Check ECU is free of charge and does not require any login.

 

How to perform a Pass Thru - ECU Check:

  • Enter the Vehicle Identification Number (VIN).
  • In case of EPA offical enter the CVN ID.
  • In case of CARB offical enter the Cal ID.
  • Click the "CHECK ECU Version" button.

If the VIN is valid you see:

VIN IS VALID - User has the latest Update

 

How to find the VIN:

The VIN is labeled inside the windscreen at the bottom right side: see sample.

 

How to get the CVN ID / Cal ID:

CVN / Cal IDs can be retrieved with a generic scan tool device.

 

techinfo2.porsche.com

 


 

Bestseller No. 1
CarDAQ-Plus 3 All Makes J2534 Reprogramming Tool
  • ALL OF THE J2534 PROTOCOLS - This single unit has all of the protocols you need for your OEM J2534 reprogramming and diagnostics including the latest in DoIP and CanFD
  • J2534 TECHNICAL SUPPORT - FREE for the life of the tool. Staffed by technicians who understand vehicle repair and J2534 Pass‑thru
  • TOOLBOX WITH OEM APPLICATION DESCRIPTIONS - educational video tutorials and real-time news – Giving you the confidence and up-to-date knowledge to get the job done
  • J2534 v05.00 API - The newest version of J2534 to give you the latest in pass-thru technology
  • FUTURE PROOF WITH 4 CAN CHANNELS - Going beyond the 3 required by select Chrysler/FCA models, CarDAQ-Plus 3 also provides a 4th to meet the needs of future OEM applications
SaleBestseller No. 2
VNCI J2534 for Nano Diagnostic Tools,Support J2534 for Automatic Switch Mode Fast Communication
  • Application:Support most all of J2534 compatible software, most all of for software, ECU reprogramming in J2534 mode with programming voltage, supply software for diagnosing J1979 compatible vehicles.
  • Material:VNCI (Vehicle network communication interface) is a device that works between diagnostic software and vehicle. It is compatible with J2534 Passthru and for .
  • Advantage:Support J2534 and for mode in one device, and has automatic switch mode, more speedup, faster communication and reprogramming.VNCI J2534 for Nano protocol configuration include, for ISO15765, for ISO9141, for ISO14230, for J1850 PWM( supports IFR and 2X speed modes), for J1850 VPW (supports 4x speed mode).
  • Easy to install:More stability, never let you down while reprogramming, portable and convenient, small package and easy to carry.
  • Best Experience :We strive to provide you with the best quality products and the best customer experience.We try our best to meet your requirements.Please check the product information carefuly berore buying to aviod making mistakes.
Bestseller No. 3
LAUNCH X431 PRO5 Elite,J2534 Reprogramming Tool, Topology Mapping OBD2 Scanner Diagnostic Tool, CAN/CAFD/DoIP/HD/FCA SGW,Bidirectional Scan Tool, ECU Coding, 50+ Reset, All Systems Scanner
  • 🆚LAUNCH X431 PRO5 scan tool Upgrade all functions of X431 PRO3/X-431 Throttle III/X431-TorqueIII/X431 V+, PROS V+, PAD3. ⓵ J2534 ECU Programming &Online functions directly connect to OEM server, 50+ reset same as X-431 Throttle;⓶Bi-directional control and All system diagnostics as Snap-on scanner; ⓷ Support 150+ brands Vehicles (include CAN/CAFD/DoIP/HD protocols and AutoAuth for FCA SGW) ⓸Powered by 8-core processor(1.8GHz), Android9.0 OS, 2.4 & 5GHz WiFi connection.
  • 🚜[J2534 Reprogramming With FREE SMARTBOX 3.0】Save more than $2000, LAUNCH X431 PRO5 support J2534/DOIP/CANFD/HD protocols (Needn’t buy HDIII Module,Manufacture software and non-16pin adaptors need to be purchased separately.) Download OEM software from the manufacturer’s server to 1) program data to blank/used ECUs; 2) Reflash ECUs with data loss; 3)Upgrade ECU software version. As a wireless VCI allowing the vehicle to transmit data to the diagnostic tablet without a physical connection.
  • 👏[50+ Reset, Continuously Updated Reset Functions]: With the LAUNCH diagnostic tool, You will never be bothered by tricky vehicle issues and keep pace with newer technology. 50 commonly reset functions ( in the quick page ) reaching into the smallest parts to root out the problems. Extra 300+ repair functions ( in-vehicle catalog) for specific models extend the capability to reset, regeneration, initiation, matching, etc. (Functions vary by models, configurations, and systems.)
  • 🌐[One stop Intelligent Diagnostic Tool]: LAUNCH X431 PRO5 obd2 scanner Bluetooth provides Repair Tips, Repair Assist, Component Measurement, TSB, Relevant Cases DTC Analysis to simplify complex diagnostic and achieve the trouble-free repair. 🤩[One Scanner For Multiple Uses]: LAUNCH diagnostic tool PRO5 collaborates with add-on modules (ADAS, Videoscope, TSGUN, X-ProG3, WiFi Pinter, Battery Tester) to expand business applications and improve diagnostic accuracy.
  • 👍【2024 New OE Level Online Functions 】Bidirectional Scan Tool offers you various high-end online functions, which enable you to access the online data to do fast & complicated vehicle repairs, e.g. 1) ECU Coding for replacing, match, relearn, recode new ECU modules; 2) Online Coding for BMW, Audi, VW, Porsche, Benz to surf OEM data; 3) VAG Guided functions ease complex issues; 4) Personalization & ADAS improving car performance and driving safety.
Bestseller No. 4
Mongoose-Plus J2534 OEM Vehicle Interface Cable - GM OEM Reprogramming and Diagnostics
  • Industry-leading J2534 Pass-Thru Technology: Enabling diagnostics, reprogramming and security functions for dealerships and the independent repair facility. Economical and compact pass-thru devices provides an easy-to-use interface that allows you to repair complex vehicles with OE applications in your shop. Each type (see single branded types above) Mongoose-Plus is engineered to work with one of the following OEM's J2534 applications for Chrysler, Ford, GM, Nissan, Toyota, Subaru, & VW/Audi.
  • Supports Current GM Vehicles: Now includes CAN-FD, DoIP (Diagnostics over Internet Protocol - as defined in J2534-2) and support for J2534 version 5.0. This is the tool that GM dealerships use for diagnostics and reprogramming.
  • NEW Bluetooth Wireless Options Available: Providing wireless connectivity between your laptop and the Mongoose-Plus
  • Expert Product Support: Staffed by technicians who understand vehicle repair and J2534 Pass‑Thru applications to help you with any technical setup questions
  • Key Registration and Immobilizer Support: Using NASTF Vehicle Security Professional credentials
Bestseller No. 5
Autel MaxiFlash Elite VCI J2534 Pass-Thru ECU Programming Tool, Multi-Protocol PassThru Interface, Work with Autel MaxiSYS Elite II, Elite, MS908, MS908S Pro, MS908CV, MK908P, MK908 Pro II and PC
  • 🌐【Works with Autel MK908, MS908(S/Pro), MK908P, MaxiSys Elite】Autel J2534 work with these tools to program ECUs on specific BMW/ BENZ for specific functions. ★★NOTE: J2534 CANNOT directly work with these single devices. After you received the J2534, you HAVE TO send us both the S/N(12 digits) of your scanner MS908S(etc.) and J2534. So, technically, Autel engineers can help you bind J2534 with your devices. If need any supports, contact us via: 🚘auteldirect @ outlook. com🚘.
  • 🌐【SAE J2534-1 & J2534-2 Standards】Autel MaxiFlash Elite J2534 is a fully compliant SAE J2534-1 & SAE J2534-2 (March 2006) device, which performs standard PassThru J2534 functionality: Compatible with for Toyota Techstream, Volvo VIDA, Honda HDS, Jaguar-Land Rover IDS and BMW 3G for OEM diagnostics. Autel MaxiFlash J2534 is also specially designed to provide users with P-C communication and ECU reprogramming capabilities on any modern vehicle diagnostic bus, reliability and flexibility.
  • 🌐【High-speed Transmission Speed】Autel MaxiFlash Elite Reprogramming Device J2534 supports simultaneous communication definition in J2534-1, running 3 protocols at the same time, which greatly improves reprogramming and diagnostic speed. Embedded with the ARM9 Dual-core processor (clocked up to 500MHz), which further boosts the communicating speed to save more times and win more business.
  • 🌐【Multiple Devices Connected with PC】Autel MaxiFlash Elite J2534 also supports multiple device connections to the PC, which can operate diagnostic and reprogramming functions on more than one vehicle at the same time. Autel MaxiFlash Elite J2534 built-in wireless and data storage, which can update via Internet. It also ensures quickly reprogramming even the newest controllers.
  • 🌐【Extensive Compatibility】Autel MaxiFlash J2534 is compatible with Toyota Techstream, Volvo VIDA, Honda HDS, Jaguar-Land Rover IDS and BMW 3G for OEM diagnostics. To check compatibility, please contact 🚘auteldirect @ outlook . com🚘 directly for satisfaction-guaranteed support!
Bestseller No. 6
VXDIAG VCX Nano GDS2 and Tech2Win Diagnostic Tool Compatible for GM/OPEL with Global Diagnostic Programming System GDS & GDS2 Blue
  • 🚗[Technical assistance] If you have any installation problems, download the installation manual. Or please contact us at any time. We can provide technical support and help you install software online
  • 🚗[Vehicle Coverage] Installation Tips: Please turn off anti-virus software before install. VXDIAG VCX NANO fully compatible with SAE-J2534-1 & SAE-J2534-2. All current and most legacy vehicle protocols: CAN, UART, KW2000, Class2, GM LAN, etc.
  • 🚗[Functional] ●USB vehicle-to-PC connectivity●Supports Windows,XP●Supports Windows 7● CE and FCC compliance for hardware●Firmware Updatable. 【SPS】Service Programming System: ◎Passthrough programming on GM past model and Global A vehicles◎Increase reprogramming speed 20-70% and get ready to service new models.
  • 🚗[GDS] Global Diagnostic System: ◎New Diagnostic Application Software required for all GM Global Architecture (Global A) Vehicles. ◎GDS & GDS2 is software which runs on a specific PC. Updates received via TIS2Web.
  • 🚗[Efficient&Convenience] Quick access to vehicle data for maintenance or management reports.Quickly attaches to vehicle's diagnostic connector. Mixed fleet capabilities with broad protocol support.May be used with desktop PC or laptop. make sure your computer at least 4GB.Tech2win software only installed on 7 32bit computer and on physical system.Please download the latest vxmanager from vxdiag official website.

Last update on 2024-03-18 / Affiliate links / Images from Amazon Product Advertising API

This product presentation was made with AAWP plugin.

Leave a Comment

Share to...