122-F7P8T-12
Service Bulletin Details
Public Details for: 122-F7P8T-12
Bulletin outlining a "white noise" message that appears in the dashboard for an emergency call function fault and how to eliminate it.
Models from 2020
2020 PORSCHE CAYENNE |
Models from 2019
2019 PORSCHE CAYENNE |
Service Technical Information 127/19 ENU 9196 9 Symptom - White Message in the Instrument Cluster "Emergency Call Function Fault Service Necessary" (SY 127/19) Model Line: Cayenne (9YA) Model Year: As of 2019 Equipment: (I-no.: IW3) Subject: Connect and instrument cluster control units Symptom: White error message in the instrument cluster "Emergency call function fault - Service necessary" Cause: Due to a software error, the message "Emergency call function fault - Service necessary" is incorrectly displayed in the instrument cluster in addition to the status LED in the roof console when there is no mobile phone network available. This is not an emergency call function fault. The availability of the emergency call system should only be indicated by the status LED in the roof console (green available/red not available). Remedial Action: Re-code the Connect and instrument cluster control units using the PIWIS Tester with test software version 38.750.015 (or higher) installed. Required tools 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, 90 A or equivalent 9900 - PIWIS Tester 3 with PIWIS Tester software version 38.750.015 (or higher) installed Re-coding Connect and instrument cluster control units NOTICE Fault entry in the fault memory and/or control unit coding aborted due to low-voltage. • Increased current draw during diagnosis or control unit coding can cause a drop in voltage, which can result in one or more fault entries and the abnormal termination of the coding process. Before starting control unit coding, connect a suitable battery charger with a current rating of at least 90 A to the vehicle. AfterSales Nov 21, 2019 Page 1 of 3 9 Service 9196 ENU Technical Information 127/19 NOTICE Coding 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, coding may be aborted. During control unit coding, always connect the PIWIS Tester to the vehicle communication module (VCI) via the USB cable. NOTICE Control unit coding will be aborted if the driver's key is not recognized • If the driver's key is not recognized in the vehicle, coding 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 Use of a PIWIS Tester software version that is older than the prescribed version • Measure is ineffective Always use the prescribed version or a higher version of the PIWIS Tester software for control unit coding. Information The procedure described here is based on the PIWIS Tester 3 software version 38.750.015. 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. Work Procedure: Re-code the Connect and instrument cluster control units automatically using the PIWIS Tester. Required PIWIS Tester software version: 38.750.015 (or higher) Type of control unit coding: Control unit coding using the 'Automatic coding' function for the control unit: Select the 'Connect' and 'Instrument cluster' control units in the control unit selection screen and re-code them using the 'Coding/Programming' menu and the 'Automatic coding' function. Nov 21, 2019 Page 2 of 3 AfterSales Service Technical Information 127/19 ENU 9196 9 Read and follow the information and instructions on the PIWIS Tester during the guided procedure. Coding sequence: Do not interrupt coding. When coding is complete, the message “Coding has been completed successfully” is displayed and a tick appears in the 'Status' box. Procedure if control unit coding is not successful: Repeat control unit coding. Invoicing Invoicing: For documentation and warranty invoicing, enter the labor operations and PQIS coding specified below in the warranty claim: APOS Labor operation 902540 Programming instrument cluster (31 TU) I No. PQIS coding: Location (FES5) 91960 Emergency call system Damage type (SA4) 1611 does not function 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. © 2019 Porsche Cars North America, Inc. AfterSales Nov 21, 2019 Page 3 of 3