Jump to content
SAU Community

Recommended Posts

Hey guys I talked to ATP turbo and they said they will soon have the GTX2860 as a bolt in for the skyline. I am looking for 450-500whp in my S30 240z. I know that kind of power is typically the GT2860-5 which has 76 .64 a/r turbine. the -7(n1) and -9 (gtss) have 62 trim .64 a/r. Do you think by extrude honing the -7/-9 .64 a/r housing that would have any benefit to the turbo still using the smaller .62 trim wheel? or is the wheel what is keeping this turbine back in power?

Thanks.

lee

lol hold up - you know what it'll be. Just a milled housing to suit.

It won't be a proper Garrett one, and will likely mean rubbish performance as we've seen in the past.

Do you think by extrude honing the -7/-9 .64 a/r housing that would have any benefit to the turbo still using the smaller .62 trim wheel? or is the wheel what is keeping this turbine back in power?

The -5 turbine and the -9 turbine are the same size... They both use the 76 trim wheel.

The -7 uses the smaller trim.

All honing will do, is hurt the blistering response - which is why you make that turbo selection in the first place.

On garret website turbo 2859r (707160-9) shows a 62 trim .64 a/r

the -7 ( (N1) 707160-7) 2860r shows 62 trim .64 a/r

the 2860-5 (707160-5) show a 76 trim .64 a/r

the site is sort of misleading because 2860r are listed as 2860r (1) 2860r (2) 2860r (3). the GTSS is the 2859r so there is 4. i believe the 2860 (3) is essentially a disco potato, its part number is 739548-9 so dont confuse the to -9 turbos.

Hold up. Any more info on this?

From ATP email today.

"They would be just like the -7 and -10 turbos. You won't get the GTX comp housings with built in anti-surge though and so these will have the skyline style compressor housings with 2 bolt inlet and 2 bolt outlet and no way to integrate the anti-surge machining.

Works like this , you have the basic T28 turbine in I think 62 trim and a few turbos got the nice GT28 NS111 turbine in 62 trim as well . It has fewer more open blades than the normal GT28 turbine and in performance apps is a good thing .

I don't have time to look ATM but off the top of my head the GT2854R/GT2859R/GT2860R (707160-7) turbos got the 62T NS111 turbine .

If you see a GT28 based turbo with a 76 trim turbine its the larger trim version of the NS111 like say HKS spec Garrett "GT2530s" get .

Many won't agree but my take on turbine and housing size choices is more about where you want the boost and torque to be than maximum power output up high - in a roadie anyway .

Also I doubt theres room on an RB26 style compressor housings to incorporate port shrouding and make it work with a GTRs inlet plumbing .

You also take the risk of going out on a limb with GTX compressors and plain comp housings .

Its one thing to increase a compressors pumping capacity and another to bank on it not surging . The only way to know is to try and its an expensive exercise if it does surge .

The factry style turbo layout on an RB26 was designed for a purpose and the tight packaging doesn't leave much room to make major alterations . IMO you need to try and get them right the first time and if it was me I'd go conservatively with something known like -9s .

A .

Not the exhaust manifold porting, the turbine housing for the turbo. I really would like the -9 I think but I havent seen any rwd numbers close to the 500 mark. Thats why im wondering if you ported the housing of the -9 turbo from a .64 A/R to something like a .72 A/R or something (light extrude hone), if it would gain any up top, I know you would probably loose a touch of spool though.

Turbines and their housings are always a compromise , where you gain at the top you lose at the bottom . AFAIK Garrett and HKS only made RB26 specific turbine housings in 0.64 A/R and its questionable that porting them would make much difference .

I think the way to make an RB26 wider ranging without increasing its capacity is to give it some form of variable cam timing and play with fuel octane and static CRs . Ideally more cubes but thats expensive to do as well .

A .

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
    • Holy hell! That is absolutely stunning! Great work!!!
×
×
  • Create New...