Z32 MAF

Looking for 2 used z32 mass airflow sensors. Not looking to spend alot of money here. Any suggestions? Any difference between the TT and N/A sensors?

Thanks

No difference. N62 is what you are looking for. All USDM VG30DE(TT) are the same. But you’ll probably spend good money, every SR owner is looking for one.

True that, not to mention Z32TT owners looking to add a second one in parallel for a true dual-intake setup. Unfortunately even wreckers are asking crazy money for them.

If anyone finds a good cheap source for them, please let me know too. Thanks.

True that, not to mention Z32TT owners looking to add a second one in parallel for a true dual-intake setup. Unfortunately even wreckers are asking crazy money for them.

If anyone finds a good cheap source for them, please let me know too. Thanks.[/quote]
Thanks for the heads up on dual Z32 AFM for VG30DETT, I thought only RB26 owners did that.

No problem. I just hope I’m not killing my chances of obtaining one by posting that.

Anyway, what most people do is just go with the JWT Dual POP setup, which uses a dummy MAF on one side, which is basically just a piece of pipe that serves as a spacer to match the length of the real MAF. And on top of the price of the kit, you have to pay JWT about ~$100 to reprogram your EPROM to basically double the airflow value.

The other way to do it is to obtain a second MAF, and a second harness, and ADD the values of the two MAFs using an S-AFC. Cost wise its hard to say if its an advantage… you don’t have the reprogramming fee because you can keep your single-POP program, and you can buy kits cheaper than the JWT kit (the elbows and couplers, and one or two pop charger filters) but buying the second MAF will gouge you.

The main advantage of option 2 I think is better accuracy. Taking the two MAF signals and adding them should be a better number than doubling the signal of one MAF, as the intake tract is not exactly symetrical… close but not quite.

I haven’t decided what route I’m going to take yet… but I have some time since I’m not there yet in terms of need.

BTW why would the RB26DETT guys need to do this? Don’t they have everything in one single intake path (being that its an inline 6, not a V)?

the RB26DDETT has 2 MAF’s one for each turbo. Does anyone know the size of the RB25DET maf’s and would they work on an SR??

they are expensive like 300 bux or more, new that is http://www.superiornissanmotorsports.com/store/index.php?cPath=4_34_158 these guys have them. if you wanna spend a good amount of money. they are a nissan dealership in cali, that carries all types of aftermarket shit.

I will check for you in little while.

They are about 80mm as well, but are calibrated for higher flow than Z32. The Z32 has the highest caibration available from Nissan. They can be used in SR with S-AFC or ecu reprogram. GTR owners use dual Z32 when they going high horspower such as 600 hp up.

what kinda numbers are you looking at before upgrading your masf?I was looking into getting one of these but the price is up there for them.I am going to just upgrade to a MAP sensor with mine I think its going to be around the same since I will already be running a Apexi ecu.

Best price I can find is about $250 per sensor. Thats too much for me so I guess I’ll be sticking with stock.

Autodream sells them for about 200 give or take a little.

They are about 80mm as well, but are calibrated for higher flow than Z32. The Z32 has the highest caibration available from Nissan. They can be used in SR with S-AFC or ecu reprogram. GTR owners use dual Z32 when they going high horspower such as 600 hp up.[/quote]

That’s not exactly true, the Q45 90mm maf’s have a higher airflow range (‘resolution’)than the 80mm z32 ones. I have a 90mm maf I’ll be using on my RB20 soon :smiley:

That’s not exactly true, the Q45 90mm maf’s have a higher airflow range (‘resolution’)than the 80mm z32 ones. I have a 90mm maf I’ll be using on my RB20 soon :D[/quote]

You genious. I totally forgot about that.

That would be overkill though for my mostly stock gt-r. :slight_smile: