5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHHelp me chase a misfire code please...long post
Leading reported evidence
Clean with detoxit
Performed · outcome unconfirmed
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 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
After finally getting my UAOS installed (thanks Doc!), and pulled both the cam position sensor plugs and cleaned with Detoxit.
Leading evidence: 'Clean with detoxit' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check oil pressure bypass valve' (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
After finally getting my UAOS installed (thanks Doc!), and pulled both the cam position sensor plugs and cleaned with Detoxit.
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 changed a leaky manifold adaptor (brake booster), but didn’t have a replacement o-ring (picked up today).
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.
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.
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.
5 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: 20261026T113718Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
So let me start by saying this is a 2003 C2 Cab, and apologize for the LONG post. Stock motor, with new LN IMS bearing about 2 yrs ago. Presently at 130,000 kms (~80K miles).
So last week I took the car on a couple of long business trips. First 500 mile run, flawless. Second day it was drizzling but warm. About 300 miles into the trip, on cruise, steady throttle, I was almost at my first stop, when I felt a stutter, then smoothed out, then stutter, then CEL light flicked on and flashed once or twice, then went out. Intermittent misfire for the next minute or two, then I stopped and shut car off for maybe 30 mins to make my meeting. Came out, started up, no CEL, no misfire. Ran normal. When I got to the hotel for the night, I did a quick scan with my phone app.
5 pending codes:
P1341 Manufacturer defined,
P0300 Random/multiple cylinder misfire,
P0304 Misfire Cylinder 4,
P0305 Misfire Cylinder 5,
P0306 Misfire Cylinder 6
Monitored carefully on the drive home, but no misfires, no codes, all smooth.
Fast forward to the weekend. After finally getting my UAOS installed (thanks Doc!), and pulled both the cam position sensor plugs and cleaned with Detoxit. After sitting for several hours, I started the car up in the garage. Felt a little rough, then a CEL (solid, not flashing). Pulled codes from phone app again. 1 confirmed, 3 pending:
P0300 - confirmed
P1341 - pending
P0302 - misfire cylinder 2
P0303 - misfire cylinder 3...seems the issue moved to the other side of the car.
Back to the computer to do some research on these codes. Much seem to point to vario-cam actuator slow or failure (but I could find no info on Vario-cam Plus, which mine is). It was late so I left it to work at it when I got home tonight.
So, tonight I break out the Durametric, and run a diagnostic.
scan with engine off
I then started the engine and took some active readings of cam deviation, below:
Before clearing codes
I then cleared the codes with Durametric, started engine and got these readings:
After clearing codes. The deviation numbers stayed rock solid when revs applied.
I also ran the Ready Status and got this:
Not sure if this is related or not, but not sure why these all show as “fail”?
I’m a complete dummy with regards to all this stuff, but trying to learn. I “thought” clearing a code, simply meant clearing the memory, but can a fault code effect operation? I may be WAY off, and likely am, but the intermittent nature makes me think it’s an an electrical thing, like a cam position sensor, but moving from one bank to the other, makes me wonder. Maybe crank position sensor giving a bad signal? I would “think” (and as my knowledge is so limited, I’m likely wrong) that something mechanical (like a tensioner pad) would be more consistent??
Any suggestions from the collective?
When I see a 1341 code With a 3 chain engine, the first thing I do is change the oil.
You can�t put stock in the misfires. When the engine starts running rough you�ll register phantom misfires from cylinders that don�t have an issue.
Your cam timing is all over the place, which can cause the misfires.. Vane cell adjusters that are seeing dirty oil can cause this, and so can low oil pressure. Check the oil pressure bypass valve for a broken/ weak spring.
The last pic is basically showing the rediness of the monitored systems. Since u reset the ecu not of the monitors have been set, u need drive cycles to get them to process. No need to worry about them.
also follow jakes advise, he knows these engines
Thanks so much! I am coming due for an oil change, so will get on that right away. I change at 5000 kms (3000 miles) usually, and have UOA done. I was planning to change over to Motul this change. Should I stick with the same oil that’s in it for consistency and lack of adding variables, or does it even matter?
I actually changed my oil pressure bypass piston and spring back three years ago (30,000 kms ago), as a precautionary measure (updated piston), but I will check again. Just as a reference, and I know the dash gauge is sketchy, but I saw no unusual oil pressure readings. I watch it like a hawk out of paranoia. I believe Durametric gives oil pressure, so may also try a drive with it hooked up to verify.
I am surprised that clearing the codes would result in the cam deviation changing so radically. Does the code cause the computer to compensate, then once cleared, go back to normal running? Sorry for the dumb question, I’m trying to better understand how these things work.
Thanks again!
Well, fresh oil change, new filter and codes cleared. All seems to be working fine. I’m going to do another smoke test tomorrow, as I suspect I have another vacuum leak. I changed a leaky manifold adaptor (brake booster), but didn’t have a replacement o-ring (picked up today). Oil filter was spotless, so that was a nice find. I’ve never experienced an engine that would misfire due to dirty oil (with only just over 5000 kms on it), but this thing continues to amaze me on many levels.
This is a source reference. Confirm exact model applicability in the original material.