Jump to content
SAU Community

Recommended Posts

Am thinking of doing this instead of aftermarket ecu.

Will be running Z32 Afm with FMIC and exhaust everything else will be standard.

Will probably use one of nistunes boards for tuning eventually, but till then.

I have just a few questions.

- Does it matter what type of ECU (16 or 8 Bit).

- Are The stock z32 maps suitable for RB25

- Will Z32 ecu run the standard boost control soleniod.

- Can I run an external ignitor with my exhisting coils.

- Are my exhisting knock sensors suitable.

Any Help would be greatly appreciated.

Link to comment
https://www.sau.com.au/forums/topic/179120-z32-ecu-into-r33-series-2/
Share on other sites

well you would probably have to re-wire most of the ecu. then if things like injectors are different size then that will mess with how well it runs, as will the afm, as will the fact that 1 is a 3.0L and one is a 2.5L so the amount of air and fuel that each uses at idle (and the whole way through the rev range) will be different.

so in short, it could be a lot of work only to find that the car won't run.

Thanks guys.

Will probably use an older Z32 Ecu (8 bit). Probably install nistune daugtherboard at same time to iron out any problems.

is there anyone who can shed some light on the factory boost control eg. does it work from the z32 ecu?

Yeah the Z32 does control VCT, which is why I am choosing it over a RB20 ecu. Standard switching point is 5900 rpm on z32.

Also z32 injectors are 370cc same as r33 i think.

Anyone got any info on the stndrd boost control thing?

The main purpose for using the Z32 ecu is that Nisstune have daughter boards that allow real time tuning with map tracing and they support wide band AF sensors (Tech edge i think). All this for approx 400$ + Install and a tune.

I am going to use a Z32 AFM as I felt this would allow me to use the Z32 ECU maps untill I had the Nisstune daughter board installed.

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

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
×
×
  • Create New...