Jump to content
SAU Community

Recommended Posts

So just wondering why everyone lashes out for 2 pods when they could just use one? I have tried looking around for kits/converters, but must not be using the right lanuage.

Anyway, currently have stock AFM, will upgrade to Z32 at some point down the track. I am assuming it is really just as easy as a y pipe of some sort?

What turbo setup? If twins then forget about it from the start. The ECU reads DUAL input from both AFM's.

One turbo might be sucking less air, this needs to be measured individually.

Unless you are going single turbo - and even then you usually need dual simply because you need the resolution. One Z32 with a big single (EG a T04Z) isn't enough.

You can "split" the signal and use one AFM, however this is far from an ideal solution and not recommended.

Stock setup. I realise you need the 2 AFM however I intend to have the split *before* the AFMs.

IE:

(turbo -> pipe -> afm -> connector -> filter) x2

instead:

(turbo -> pipe -> afm) x2 -> connector -> filter

Edited by Thelen

^ exactly.

Plus the splitting of airflow could potentially cause issues with the AFMs for a start.

Anyway, pod's hurt performance - not increase it.

Putting the stock airbox back in with a $100 K&N filter that is washable will last 5-10 years... Can't see how you are going to beat that for the ... money concious GTR owner...

Yea wasn't quite a do-it-on-the-cheap thing, just wondered why no one ever bothered to do it when it is kindof an obvious thing :D I figured getting the small Y piece would cost only 1 filter worth, so it'd pay off after a year or two. Of course if you have to fab it, costs more but figured it would be a kit :D

I realise stock + panel is the way to go, I'll hunt around for a stock airbox when I have time :D

I did this when i had the gtr turbo setup on my 25, meant i could have both turbos fed through the one z32. Had no problems running that way. I had one big pod, one big afm then it split to the front and rear turbos. still have the pipework but i guess its the opposite of what you were thinking

Eventually moved the z32 to the cooler piping so i could run 2 pods, but never really had reason to do that. Just wanted to look more like a 26 in there.

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

    • 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!!!
    • It does when you start adding everything else in. But it's not just compute. It's the logic. Getting your timing right (I'm not meaning ignition timing for the engine). Making sure of your memory mappings, seeing your interrupts. Microcontroller devices only have so much capacity. For the most part, you want all those timers and interrupts in use on your engine control, which means you're left with less than ideal methods for timing and management of other control functions.   Let's put it this way, my job is all about building custom hardware, that goes into cars, and integrates with them. We're also waiting on a media confirmation from SpaceX too fora world first we've just completed with them in NZ too. It's not just the little toys I play with. But you know, you can think and believe what you want.
×
×
  • Create New...