29 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH996 Error Codes after some Mods
Leading reported evidence
Replace so here is the part
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.
Leading evidence: 'Replace so here is the part' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'tune' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace cam shaft position sensor, bank 2 speed hall sensor' (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
I also noticed that the car ran a little rougher and seemed to have the rpm jumping up and down by 2-300 rpm.
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
They took the tune to stock and ran some diagnostics.
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
Again ran very good for a few days and the same warning came up with the following codes.
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 suspect 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.
Suspected cause · Original poster
They advised me not to put the tune back in, but I didnt listen to that as I dont think it was due to the tune.
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.
29 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
Hoping issue is resolved but will keep you guys posted.
Hey gang,
I have a 2003 C2 Cab that I have had for close to a year. Over the Christmas Break I did a few mods:
Bens Plenum
GT3 throttle Body
EVOMS Intake
Exhaust Removal and Fabspeed bypass pipes
Softronics ECU Tune
Car ran great the first two days and then some error codes popped up as well as the CEL light with warning to go to the nearest garage. I also noticed that the car ran a little rougher and seemed to have the rpm jumping up and down by 2-300 rpm. These were the error codes:// 1) 1109 1109
// 2) 0335 0335
// 3) 0346 0346
// 4) 0300 0300
// 5) 0301 0301
// 6) 0302 0302
// 7) 0303 0303
// 8) 0022 0022
// 9) 0103 0103
Then I cleared the codes and rechecked all the fittings and tightened up some of the clamps. Again ran very good for a few days and the same warning came up with the following codes. I notice that when the CEL cam on the car idle fluctuates between 600-800.
// 1) 1109 1109
// 2) 0346 0346
// 3) 0300 0300
// 4) 0301 0301
// 5) 0302 0302
// 6) 0303 0303
Tuner advised me that I have a vario cam error, could be from coils or plugs...,maybe a faulty cam positioning sensor... I will be going to check it out this week but wanted to see if any of the gurus out there had any thoughts. I was thinking of trying another throttle body (948.605.115.03) but seems like this could be a completely different issue that happened to pop up at the same time i completed the mods.
Thanks in advance
It would be kind of odd for it to be a random coincidence. You changed a lot of stuff...so you have a lot of independent variables to guess at. Maybe return it to stock, clear the codes, and see what happens after a few days. Then slowly add in the mods one at a time, a few days in between, and see if/when the error codes start popping up.
That's a lot of codes! The P0300's are random misfires on Bank 1, Cylinders 1, 2 and 3. Seems like you have a TB issue...see here
https://rennlist.com/forums/996-foru...rror-code.html
The best advice I can think of is to return it to stock. Seriously, there is not much left in the M96 motor as far as bolt ons go that measure any real power gain with out opening up the motor and getting a proper custom tune. If you still want to go through with throwing parts at it, do it one thing at a time and work the bugs out in steps.
So I removed the 997 GT3 throttle body and tried the 996 GT3 throttle body. I think the other TB may have had some issue but current codes seem to continue to show Bank 1 error:
1) 0349 0349
2) 0335 0335
3) 0300 0300
4) 0301 0301
5) 0302 0302
6) 0303 0303
7) 1325 1325
Heading to shop this afternoon....
Good luck. Hope it is easy to sort out and your shop gets it quickly.
I did a lot of software troubleshooting (debugging) in my career, and never found it easy to get to root cause when you are altering too many variables at one time. Cars aren't much different, except the parts are often physical, rather than virtual. The process is the same though (at least for me).
In my experience throwing parts (like a different GT3 throttle body) at a problem like this isn't the best troubleshooting method. I'd take it all the way back to stock (as it was prior to adding all those parts) and so you have an "apples to apples" comparison. If you do that, and still get new codes thrown that match the ones you're seeing now, at least you know where you stand. I'd rather troubleshoot from a known good baseline than a uncertain state with lots of variables.
Yeah...I enjoyed reading that thread and seeing it all work out. He did have the P1325 and various misfires, so I'm thinking/wondering if OP here might be headed in the same direction.
Thank you all for the links and info. The shop called me back. They took the tune to stock and ran some diagnostics. Looks like the Camshaft Position sensor has an issue. They replaced it yesterday and doing some road tests. Hoping issue is resolved but will keep you guys posted.
Revisiting a dead thread...I just bought a new to me 996 turbo and I am throwing P1325, did you ever find resolution? Was it the camshaft position sensor?
Thanks!
Hey guys, sorry for that. So here is the part that was replaced:
PC REMOVE AND REPLACE CAM SHAFT POSITION SENSOR, BANK 2 SPEED HALL SENSOR
Part # 99660610603
They advised me not to put the tune back in, but I didnt listen to that as I dont think it was due to the tune. Been running with the Softronics tune since then and no issues to report.
Let me know if you need any other info....
Thank you for the update. We are still in the diagnosis phase, so all related data points are great.
Did you by any chance have any indications of a problem (other than the check engine light and other codes)? Rough idle/power loss/etc.?
+1
Been down that road and the right decision for me was to use a resonator delete on the stock airbox. My car has the regular-size IPD plenum & it improves induction sound. Between the IPD and resonator delete you can get a lot of induction noise. Put the intake $ towards headers or sport cats.
I could see that, if I were having the IPD plenum. but Ben's plenum is much more reasonably priced. And I am really enjoying the way it is running now.
This is a source reference. Confirm exact model applicability in the original material.
