6 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCode P1508
Reported or suspected cause
car is a 3.4 non turbo
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
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 report identifying a cause
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.
Leading evidence: 'car is a 3.4 non turbo' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'car is a 3.4 non turbo' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Replace component based' (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.
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 performed work without a confirmed outcome
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.
Performed · outcome unconfirmed · Original poster
220 miles down to the ramble, 200 miles driving around the Cape and the car ran flawlessly.
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 · Original poster
I really dislike just replacing a component based on a code.
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 · Original poster
I can pretty much guarantee I won't be replacing the DME for this unless it starts happening more frequently.
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.
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.
6 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.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
A quick cycle of the key and everything was back to normal.
This past weekend I took my car to the PCA ramble on Cape Cod. 220 miles down to the ramble, 200 miles driving around the Cape and the car ran flawlessly. Left for home yesterday morning and about 5 miles in, took a left turn and rolled on the throttle in second gear. Next thing you know car loses all power from the motor. I pushed the clutch in and the engine idled but would not take any throttle. The check engine light was not illuminated either. A quick cycle of the key and everything was back to normal. I drove the rest of the way home with no issues and drove the car to work today with no issues. While I am inclined to chalk it up as a fluke and not worry too much about it happening again, it scared the ever living crap out of my wife when it happened, so I should probably see what could be the trouble. I did a scan and retrieved code P1508-08, function monitoring torque signal implausible. I can find very little diagnostic information on it and searching the interwebs shows it to be a code predominantly seen on the turbo cars. Problem is my car is a 3.4 non turbo. My car does have a K&N intake and a Romulus exhaust system, but to the best of my knowledge everything else is stock. Does anybody have some insight as to what may have caused this? My fuel trims are almost spot on, all readiness monitors are complete, and there are no performance issues at all with the car. Thanks for any insight anybody can provide.
Per the DME7.2 diagnostic manual, the problem is in the DME itself.
I suggest doing the e-gas re-calibration (the last 4 steps below) and see if the fault comes back.
"P1508
408 Torque Comparison Function Monitor � Signal Implausible
Function
Monitoring the DME control module.
Diagnosis conditions
� Engine speed > 1120 rpm
DTC No. Fault conditions Fault area
P1266 Fault detected during function monitoring. � DME control module
P1508
Diagnosis Procedure
Replace DME control module.
1 Perform adaptation.
End
1 Perform adaptation.
1. Switch on the ignition.
2. Wait one minute.
Do not press the accelerator.
3. Switch off the ignition for at least 10 seconds.
4. Read out the fault memory."
That was more or less what I found for diagnostics also. I really dislike just replacing a component based on a code. I did an e-gas recalibration a couple of weeks ago but will do one again. I can pretty much guarantee I won't be replacing the DME for this unless it starts happening more frequently.
