11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHMomentary power loss with CEL
Reported or suspected cause
ecu relay
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 had this problem on a VW and it turned out to be the ECU relay.
Leading evidence: 'ecu relay' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'ecu relay' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check camshaft deviations and they are at 0, -3' (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.
Reported cause · Original poster
I tried a Bluetooth obd connected to my phone and can record sensors but nothing significant from that except it stops recording RPMs while the issue is occurring.
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 also checked my camshaft deviations and they are at 0, -3.
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
Checked the code when I got home (I have a Foxwell) and found:
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.
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 · Original poster
I tried a Bluetooth obd connected to my phone and can record sensors but nothing significant from that except it stops recording RPMs while the issue is occurring.
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.
Hello all!
I have a '99 C2 with 123K miles - original engine. I have owned it since 80K miles about 10 years. Couple weeks ago had just started driving and noticed my CEL turned on for a moment then back off quickly. Next time I drove it, I was on the highway and had a sudden loss of power for just a second or 2 and the CEL came on only during the power loss. This happened several more times on my 15 minute drive home. It seemed if I put it in a lower gear to keep the revs up that this did not occur. It also seemed to happen when I let off the gas versus accelerating. Checked the code when I got home (I have a Foxwell) and found:
P0336 Crankshaft position sensor
P0102 Mass air flow sensor
I bought a new Bosch CPS (thanks FCP) and replaced with no issue. I did not do anything with the MAF. Cleared the codes, went for a short drive and all good. Next day went for a longer drive and while driving home on city street at about 30mph experienced the same momentary power loss with CEL that was only on during the power loss. Remainder of 5 minute drive home was normal. Checked codes and got the following:
P0336 Crankshaft position sensor
P1314 Misfire, cylinder 2, emission relevant
P1316 Misfire, cylinder 4, emission relevant
P1317 Misfire, cylinder 5, emission relevant
P1319 Misfire, emission relevant
I also checked my camshaft deviations and they are at 0, -3. Any thoughts on what to look at next with issue? Thanks, Brad!!
I'd suggest checking your ground, a black, heavy gauge cable from the chassis to the engine on the passenger side behind the rear wheel. Even if it looks intact it can be corroded under the insulation and cause the intermittent problems you are having. It's easy to clean your MAF with the specific electronic cleaner too.
I pulled off the ground wire and cleaned it today. Also cleaned the MAF. Same issues - loss of power for a couple seconds with CEL. Seems to happen when decelerating. So far does not happen when accelerating or holding higher (above 3k or so) RPM. Also noticed the RPM gauge was bouncing quickly from about 1 to 2 when the CEL was on. Got almost the same codes again today:
P0336 Crankshaft position sensor
P1318 Misfire, cylinder 6, emission relevant
P1316 Misfire, cylinder 4, emission relevant
P1317 Misfire, cylinder 5, emission relevant
P1319 Misfire, emission relevant
Any thoughts/help would be greatly appreciated!
So I am still having this issue. Quick recap - with warm engine only when decelerating I will experience a total loss of power. The CEL will momentarily flash and the RPM gauge will move erratically (see attached video). Once I take it out of gear and let it drop back down to idle it runs normally. Never have any issue while accelerating. I get a code for the crank position sensor which I just replaced (Bosch) and have the same symptoms. I sometimes get several misfire codes from both banks but I believe these are a result of whatever this issue is not the cause. I have also replaced the MAF. I removed the ground, checked the wires to the CPS and unplugged / reconnected the main harness connection. All made no difference.
I have a Foxwell scanner that I tried to use to record results but whenever this issue happens it locks up the scanner. I believe it is because the Foxwell is powered off the obd and this issue messes with that. I tried a Bluetooth obd connected to my phone and can record sensors but nothing significant from that except it stops recording RPMs while the issue is occurring.
Any thoughts? Should I try another CPS? Issues seems electrical but I don�t want to just start throwing parts at it. Voltage reported by the scanner usually sits from 13.8 - 14v but it looks to drop slightly to 13.5 sometimes. Would this be enough to cause this? Alternator/regulator/Y cable?
thanks!!!
I could only listen to the file. Frustrating for sure. The missfires are random so not likely coils or injectors and it doesn't sound like a vacuum issue. Also, since only on decel it could be g-force related. I'd say check all the connections you can. Re-seat the round engine harness connectors and ECU with dielectric grease. Swap out and re-seat fuses and relays, especially fuel related. If you do a search on the ignition switch there have been several reports of odd gremlins when it starts failing and there is an updated replacement (see Pelican article). Maybe when it happens again reach down and jiggle the key just to test. With the new CPS I doubt that is it but maybe the connectors and also the cam sensor too.
