15 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH40th Anv ??
Leading reported evidence
Run %^$ out of my 3.4
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
I ran the %^$ out of my 3.4 before swapping for a 3.6 X51 and both have been perfect.
Leading evidence: 'Run %^$ out of my 3.4' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Run %^$ out of my 3.4' (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
When I had it in for svc, they ran the computer, no error codes at all, wierd.
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 obviously feels like there's more room up top and the limiter has been set for engine life requirements.
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 · Original poster
Not really but I do use every last rev lap after lap.
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.
15 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: 20261026T161109Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Tach face shows it at 7200 rpm. It's very easy to hit the limiter as the engine pulls hard all the way to the top. It obviously feels like there's more room up top and the limiter has been set for engine life requirements. I have seen the tach sail past 7200 rpm shifting just before the limiter to 3rd gear on the T4-5 straight at Laguna Seca, but I'm off the throttle when this happens.
Lee, I thought type II was over-downshifting and blowing past the rev limiter?
FYI...I hit the rev limiter for the first time this past weekend. Not proud of it and actually down-right pissed at myself for letting it happen. It was a wierd thing. I actually think I lost time b/c of it. The limiter kicks in and the car feels like gas is starved for a split second.....total momentum killer.
BTW....diggin that new pic
I got the answer from Loren. The rev-limiter on an X51 is 7300. The same as a standard 3.6.
I wouldn't worry too much about bumping the limiter from time to time. I use mine as a shift indicator when racing.
Not really but I do use every last rev lap after lap. These engines can take a lot of abuse.
Thanks,
Jim
Agree with you on the engine and what it can take. I think I spend the entire day between 6-7K RPMs all day when I am on the track and the car seems to love it! I do as well
Dell, I think you are the "people" that Lee is worried about.
Just kidding of course. I really think these engines love to be run. I ran the %^$ out of my 3.4 before swapping for a 3.6 X51 and both have been perfect.
Remember, the rev-limiter is your friend.
Jim
I think it is the PST2 that will read it not the OBD2 scanner. Either way,as Jim said, you should be fine.
Now if we could just figure out a way to read and "fix" the computer without the help of the PST2
