Jump to content
SAU Community

Recommended Posts

normally carry some changeovers in stock, but just waiting on new batch, should be here any day. Can also modify your actual ecu if preferred but takes a few days as I don''t have the smd work station yet. Normally looking around 2-3 hours drive in drive out for thorough tune with basic mods, obviously cam timing etc can take longer...

  • 1 month later...

Sorry to bring up and old thread, but I was wondering if you are putting a z32 ecu into an rb25 and u get the 16 bit version you need a daughterboard that I know and then would u need two chips in order to run the tune? Cause thats what I have to do caus eI got the z32 ecu that is 16 bit so they told me I need two chips in oder to run it.

You should be able to use a 16 bit Z32 daughterboard to run an RB25 still since the ECU pinouts are the same, Nissan upgraded to a different processor (probably because of the Motorola/Hitachi lawsuit stopped them using the HD6303 MCU midway through production of Z32)

I would lean towards the 8 bit Z32 because more VVT control parameters have been defined if you wish to tune those. However I went through the 16 bit Z32 ROM last month and identified some more parameters to adjust since a few owners run nistune with these

hey im in the middle of doing the rb20 ecu with a rb25 tune chip on a rb25 but ive connected the computer and the car runs fine but no tacho just wondering if you need to change the tacho wiring on the ecu from pin 7 to pin 5 to suit the rb20 ecu

  • 5 months later...
Maybe not that cheap @ approx $2000. :laugh:

should be half that, as of late have been doing the Z32 remps for $800 drive in drive out if you supply the z32 ecu ( or $950 if i supply it, as they are $150 at any wreckers)

there quite a bit of mis-information about exactly what needs dong but it is actually very simple and only requires simple pin swaps and the addition of a 02 sensor wire.

Edited by URAS
should be half that, as of late have been doing the Z32 remps for $800 drive in drive out if you supply the z32 ecu ( or $950 if i supply it, as they are $150 at any wreckers)

there quite a bit of mis-information about exactly what needs dong but it is actually very simple and only requires simple pin swaps and the addition of a 02 sensor wire.

IIRC I was thinking that that the 2K would include wideband etc etc.

Sure only requires a few pin swaps easy as.

EXCEPT the fuel temp sensor which needs a resistor wired to chassis ground. If this isn't done you get rich idle afr's and code 42.

Oh and cut wire at pin 33 or your exhaust temp light will come on with your air con.

Cheers.

Guys I'm a little lost here , are you saying that a modded R33 GTS25T computer can be made programmable and tuned via the Consult port just like any after market computer ?

I was under the impression that ROM chips had to be burnt and erased and reburnt time after time .

If all is now good is the software available for anyone to use ?

Cheers A .

Guys I'm a little lost here , are you saying that a modded R33 GTS25T computer can be made programmable and tuned via the Consult port just like any after market computer ?

I was under the impression that ROM chips had to be burnt and erased and reburnt time after time .

If all is now good is the software available for anyone to use ?

Cheers A .

Sure there are daughterboards out there that allow you to use nistune boards in the r33 ecu it's just that they're a liitle exy.

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

    • 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.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...