11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHABS, PSM, and now CEL.
Reported or suspected cause
improperly installed front intake plenum
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.
Reported cause
I recently had a 507 code and it was due to an improperly installed front intake plenum.
Leading evidence: 'improperly installed front intake plenum' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'improperly installed front intake plenum' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Install by my indy recently' (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 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.
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
I did have the UAOS installed by my Indy recently, but he's in NC and I'm now in NS Canada...
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
I recently had a 507 code and it was due to an improperly installed front intake plenum.
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
I replaced the MAF and started her up today, apr 1, for the first time since November.
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
Any codes that point to misfiring will at some point (accumulated in a set time frame within 1 ignition-on cycle) lead the DME to set a DTC whereupon PSM considers the DME as no longer reliable enough to achieve torque targets set by the PSM and switches on the according warning lights and is no longer active.
Set time frame within 1 ignition-on cycle) lead the dme
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
Any codes that point to misfiring will at some point (accumulated in a set time frame within 1 ignition-on cycle) lead the DME to set a DTC whereupon PSM considers the DME as no longer reliable enough to achieve torque targets set by the PSM and switches on the according warning lights and is no longer active.
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.
11 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.
A few drives ago my car started lighting up the PSM and ABS lights, after driving for .5 mile or so. My odblink showed me the 118 and 117 codes on the screenshot. Today, after the car was warmed up, I got the CEL and the new Po507 error. The car never settles into the 950rpm idle, and on the highway I can feel it hesitate very slightly, through my butt. Clearly the ecu is working overtime and I'm probably running rich... Vacuum leak maybe? Can anyone suggest a good smoke test unit for our cars and point me to their favourite tutorial?
thanks. This car, seriously, it's one thing after another. And it's not like I haven't lavished money and labor on it....grrr
I've got a durametric on the way, just got my shipping confirmation today..
I recently had a 507 code and it was due to an improperly installed front intake plenum. Obviously a massive air intake leak, running rich with a high idle. The plenums are fiddly as hell, and despite doing it a dozen times over the years, I still managed to mess it up being tired and in a hurry. Have you had any recent work done? If so, I would start there and check that the plenum is sealed.
I would also make sure it is not a weak battery or alternator. They can sometimes trip up all of it. Happened to me. Quick battery refresh and boom all cleared.
worth a look before diving too deep into ordering laboring through multiple components.
I looked at the intake and everything appears ok. I did have the UAOS installed by my Indy recently, but he's in NC and I'm now in NS Canada... His install like all his work is quality, he's a skilled guy, but maybe something came loose.
Good suggestion, thanks. I have a new high quality battery, installed in early 2022, and a new OEM alternator installed at the same time. I keep the battery on a ctek charger when parked. But I'll test the battery and alternator to be sure. Thanks again.
Still not able to sort this. I received my Durametric but it won't connect to my ECU, I think it's the VRTune. I'm going to flash back to stock.
I Did find this on the Durametric site, specific to 996;
"ABS/PSM triggers fault from DMESome fault codes stored in the DME will trigger a fault in the ABS/PSM system. When the DME is not able to correctly deliver the engine current torque to the PSM system it will trigger an ABS/PSM fault. After correcting the DME fault simply clear the fault codes in the ABS/PSM module."
Does anyone know what would cause a failure like this? What sensor is involved in DME to PSM Communication?
Help appreciated.
Fyi, I ordered that MAF from RockAuto, what, weeks ago now, and the order just says 'processing'. I can't even cancel the order and source the part elsewhere, there is no way to get support or an update from rock Auto. No Web chat, no support email, and no phone support. Be aware ...
Not so much a sensor but the CAN-bus communication between the two could be flaky causing this.
The 'current torque' is not measured as such but calculated/estimated in the DME based on available signals like MAF, rpm, injector time, intake temps etc. and then sent to PSM through the CAN(-bus).
In case PSM intervenes to maintain vehicle stability by means of reducing engine torque, it sends a target torque value to the DME which in turn adjusts ignition angle (quick response but limited reductionof torque) or cuts out single injectors for a couple of crank revolutions to achieve this torque target. This requires reliable ignition and injection. Any codes that point to misfiring will at some point (accumulated in a set time frame within 1 ignition-on cycle) lead the DME to set a DTC whereupon PSM considers the DME as no longer reliable enough to achieve torque targets set by the PSM and switches on the according warning lights and is no longer active.
So any detected misfiring or such codes to.lead to the problem your car suffers from.
Is the ABS actually no longer active as in you lock your (front) wheels when you emergency brake?
@hardtailer
thanks. Tomorrow I'll flash my ECU back to stock, interrogate with the Durametric, and do some simple vacuum leak tests. I think if I remove the oil filter cap, and there's no change in engine note, it points to a vacuum leak. If not, I'll pull the MAF and tape it over, clear the errors and cross my fingers. I did finally hear back from Rockauto and they cancelled the order for me. I'm looking for a good source in Canada for a new one. I miss the ease of shopping in the USA. There's good and bad I suppose. You gotta do what you gotta do.
@theprf
we have a bingo! I replaced the MAF and started her up today, apr 1, for the first time since November. No more warning lights even after a thorough post hibernation drive. I'm seriously overjoyed that the issue is sorted. Now it's time for a really good bath for the girl. She survived the winter in the garage, the only sign of mice was a slightly chewed cloth bag that I store my brass air pressure sensor in. Every car should have a proper 60 psi gauge in the boot. I use this JACO ElitePro Tire Pressure Gauge - 60 PSI
https://a.co/d/30oevnt
.
This is a source reference. Confirm exact model applicability in the original material.
