fullymatted.
Back to search
Rennlist

Got a call from Porsche last week...

Add to repair workspace
Open repair workspace
Original source
3 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHGot a call from Porsche last week...

Leading reported evidence

Repair order number

Suggestion or failed attempt

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context

Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.

Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion

2.10 Enter the repair order number.

Got a call from Porsche last week...
Read full discussion summary

Leading evidence: 'Repair order number' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Repair order number' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.

Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.

Read captured replies

1 matching discussions · 3 captured posts examined · 0 partial discussions

Compare 3 other evidence results

Test by pcna, attach a third copy

Suggestion or failed attempt

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context

Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.

Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion

^ If an emission part was replaced is and requested for testing by PCNA, attach a third copy to it.

Got a call from Porsche last week...

Use following procedure

Suggestion or failed attempt

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context

Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.

Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion

Use the following procedure to retrieve and print OBD II data.

Got a call from Porsche last week...

Use porsche system tester 2

Suggestion or failed attempt

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context

Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.

Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion

All OBD II faults and associated information must be retrieved and printed using the Porsche System Tester 2.

Got a call from Porsche last week...
Frequently discussed actions (4)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Repair order number

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion

2.10 Enter the repair order number.

Got a call from Porsche last week...

Test by pcna, attach a third copy

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion

^ If an emission part was replaced is and requested for testing by PCNA, attach a third copy to it.

Got a call from Porsche last week...

Use following procedure

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion

Use the following procedure to retrieve and print OBD II data.

Got a call from Porsche last week...

Use porsche system tester 2

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion

All OBD II faults and associated information must be retrieved and printed using the Porsche System Tester 2.

Got a call from Porsche last week...
Coverage and how to read this overview

Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.

3 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.

  • Rennlist: 1 discussions

0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.

0 acknowledgements have no verified action link; they do not establish a repair result.

Generation: 20261026T130754Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

The local dealer Service Mgr called to inform me that my VIN number had been identified with an "unacceptable number of check engine lights" ( I had about 3 episodes in the first 2 years, but nothing in quite a while- nearly a year). I will need to bring my car in for a "reprogramming" of the DME/Motronic which should take about 15". Anyone else received such a call? I think it is pretty damn good customer service that they are addressing this problem before the car is off warranty. Doug

POST 2Original post

Here is an interesting TSB (dated October 2001). Seems Porsche was/is interested in DME reports. I would love to see these reports for my car. ---------------------------------------------- OBD II - New Report Submission Procedure All 0101 0335 Binder - Group 0 This bulletin supersedes bulletin 9801, dated 12-3-98. 10/05/01 New Format of OBD II Reports Vehicle Type: All Model Year: As of 1996 (T) Concern: New procedure for submission of OBD II reports Information: Whenever an OBD II equipped vehicle (model year 1996 and later) enters the workshop with the check engine light illuminated, an OBD II report must be generated before any work commences. Reports are required if the check engine light is illuminated, drive train replacements (engine and transmission), and driveability problems that do not illuminate the check engine light. There are two report formats that will be accepted: 1. 993, 993 Turbo (ME 5.2 systems) - Manual selection of fault codes and actual values (as required previously). This printout starts with 1.0 in the work procedure. 2. Boxster, 996 and 996 Turbo (ME 5.2.2, ME7.2, and ME 7.8 systems) - The PST2 has the capability of creating an OBD II log (printout), which contains all the vehicle information, fault codes, and actual values. This report starts with step 2.0 in the work procedure. It is essential that copies of the OBD II report be filed respectively. ^ One copy of the OBD II printout along with a completed cover sheet should be faxed or mailed to: Porsche Cars North America, Inc. 980 Hammond Drive Atlanta, Ga. 30328 Fax Number: [phone removed] ATTN: Technical Services ^ A second copy should be kept in the vehicle service file. ^ If an emission part was replaced is and requested for testing by PCNA, attach a third copy to it. Note: When compiling an OBDII report for Boxster, 996, and 996 Turbo, it is not necessary to duplicate the customer complaint and corrective action taken on the cover sheet. This is already included in the PST2 report. Failure to submit a properly printed OBD II report will result in denial of the warranty claim, and the parts being returned. All OBD II faults and associated information must be retrieved and printed using the Porsche System Tester 2. Use the following procedure to retrieve and print OBD II data. Do Not erase fault memory until a valid printout has been made! Work Procedure: The following PST2 keys are represented on the new keyboard as follows: >>is now F12 (Continue) >>is now F11 (Back) Alt is now Print Screen (Print Menu) Arrow up and down, left and right remains the same (Scroll / highlight to select) 1.0 Generating a Printout for 993, 993 Turbo (ME 5.2 systems). 1.1 Connect the keyboard and printer to the PSJ2 before turning it on. The new keyboard functions are indicated in parenthesis. 1.2 Connect the PST2 to the vehicle. Start engine. Switch on the PST2. 1.3 Select the appropriate vehicle. Press continue (F12) again to scan all control modules. 1.4 Extremely Important!! Any previously stored information in the work log must be deleted or it will be included with the current report. Press F6 ("Erase work log") key, and confirming with F7 ("Yes") and then (F12). 1.5 Select the "DME" control module and continue (F12) to the DME Function selection menu. Select "Vehicle data" and continue (F12). Press F4 to "Save". Go back (F11) to the DME Function selection menu. 1.6 Note: The engine must be idling without any consumers on, and at operating temperature. Select "Actual values", and continue with (F12). Using the cursor keys (arrows), select and highlight the following Actual values: Range 1 Cylinder 1-3 (TRA) Range 1 Cylinder 4-6 (TRA 2) Range 2 Cylinder 1-3 (FRA) Range 2 Cylinder 4-6 (FRA 2) Oxygen sensing (FR) Oxygen sensing (FR2) Hot film MAF Ambient pressure When all eight of the above actual values have been selected, continue with (F12). Press F4 to "Save". Press the "Back" key (F11) twice to return to the DME Function selection menu. 1.7 Select "Fault memory", and continue with (F12). Press F4 to save a summary of all recorded faults. Next, verify that the first recorded fault is highlighted and then press F8. Now press F4 to "Save" the detail of the first recorded fault. Go "Back" with the (F11) key. Continue in the same manner until all fault details have been saved. 1.8 After all faults have been saved, connect the PST2 to a compatible printer. Print the "Working log" as follows: Press the "ALT" key. From the "Printout" menu, select "Working log". When "Working log" is highlighted, press the (F12) key. The printout will immediately follow. 1.9 Verify that the VIN printed on the printout is identical to that of the vehicle. Correct if necessary. Write the RO number and vehicle mileage in the upper right hand corner of the first page of the printout. This will assist with vehicle information if the cover sheet is lost. 2.0 Generating an OBDII log (printout) for Boxster, 996 and 996 Turbo (ME 5.2.2, ME7.2, and ME 7.8) 2.1 Connect the keyboard and printer to the PST2. 2.2 Connect the PST2 to the vehicle. Start engine. Switch on the PST2. 2.3 Extremely Important!! Any previously stored information in the OBDII log must be deleted or it will be included with the current report. You will be prompted to delete the OBDII log after it is selected (Step 2.7). Deleting the Working Log (F6) will not delete the OBDII log. 2.4 Note: The engine must be idling without any consumers on, and at operating temperature. 2.5 Press F5 (log button) and select OBDII log. Confirm with the (F12) button to start. 2.6 Read message and continue with (F12). 2.7 Press F8 to start the function. 2.8 You are now asked wether you want to delete the OBDII log. Select Yes (F7) then confirm with (F12). 2.9 You are now at the Warranty claim # screen. It is not necessary to input the number. Press the (F12) button to continue. 2.10 Enter the repair order number. Press the (F12) button to continue. 2.11 A control unit search will now be performed. 2.12 Enter the customer complaint, Press the (F12) button to continue. 2.13 Enter findings and fault cause (if they are known at this time). Press the (F12) button to continue. 2.14 Enter the affected / related components. Press the (F12) button to continue. 2.15 Enter fault recurrence (If the fault has come back). Press the (F12) button to continue. 2.16 The data is now determined. Press (F12) to continue. Note: The data is automatically saved. Do not press the save button. Doing so will save a duplicate copy in the print menu causing the report to be printed out twice. 2.17 Print the OBDII log as follows: Press the (Print Screen) key. From the printout menu, select OBDII log. When OBDII log is highlighted, press the (F12) key. An OBDII preview is now displayed. 2.18 Press F5 to print. Working Time: Labor OperationTime Units Description OBDII 099 30TU Complete OBDII printout with cover sheet as shown. Submit to PC NA.

POST 3Original post

Seems like they could be looking for evidence of ECM or intake/MAF aftermarket " tweaking" - of course they will say they need to log OBDII data to appease the EPA !

This is a source reference. Confirm exact model applicability in the original material.