12 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHNew engine for 1999/996
Reported or suspected cause
need
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
biggest problem is the need for controlling the second part of the
Leading evidence: 'need' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'need' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Run poorly' (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 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
If you did this -- I wonder if you would actually loose power or run poorly.
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.
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
If there was an option to save a 3.4 engine using a 3.6 block
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
it is wired differently, uses different instrument cluster, and uses a different ABS control unit.
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.
12 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Pelican Parts: 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: 20261026T120458Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Is it possible to upgrade the engine if you have to replace it anyway. ie go from the 3.4 to the 3.6. Are there other interesting options? theres a 996 sans engine and was just curious? Thanks
I'm working on a 996-specific article, but in the meantime, check out the Boxster version:
Pelican Technical Article: Boxster Engine Conversion Project - 986 Boxster (1997-04) - 987 Boxster (2005-08)
-Wayne
I was just thinking that if someone had a 3.4 996 and they had a blown motor (ims/rms issue). Is it possible to buy a 3.6 engine and drop that in rather then a 3.4.
Possible yes.
realistic no.
been discussed many times.
biggest problem is the need for controlling the second part of the
dual variocam. you need a 7.8 DME to do that.
it is wired differently, uses different instrument cluster, and uses a different ABS control unit. you would also need to have it programmed to match your IMMOB control unit.
I'm not even sure if you could run it as a "big" 3.4 and just tie off the control to the
second vario cam solenoids. Use the 3.4 wiring harness.
I'm sure some of the sensors on the 3.6 are different.
If you did this -- I wonder if you would actually loose power or run poorly.
Mike
will 3.4 heads et all fit on a 3.6 block?
The 3.4s suffer from cracked cylinder liners
and if you had a 3.6 block -- is that a possible work around?
mike
Only the very early 3.4 blocks suffered from cracked liners. From what I can gather, the later 3.4's were improved in that area. One almost never hears of that failure these days. In fact, my daily driver 2000 996 (with the 3.4) has 117,000 trouble free miles on it.
I don't know if there are any differences in the 2002+ cases to allow the VarioCam + that would prevent a direct bolt-on of the earlier heads. I prefer the LNeng. sleeve install upgrades to get to 3.6
Yes but at $4k that starts putting most rebuilds out of budget.
That's about $3k adder relative to a rebuild with new rings.
Granted you get a bullet proof block and pistons, but u
You'd be surprised how many folks aren't willing to spend that kind of money.
If there was an option to save a 3.4 engine using a 3.6 block
There would be a good bit of interest.
Mike
It can be done. I have a 2002 3.6 X51(actually its now a 3.8) in my 99 chassis. The upgrade is not for the faint of heart. The ECU needs some work and you need to control the V Cam with outboard devices. For other rebuild options checkout Flat 6 Innovations.
This is a source reference. Confirm exact model applicability in the original material.