Jump to content
SAU Community

Recommended Posts

Please e-mail me if you're interested in having your car remapped while I'm in brisbane....

Dates are 10th and 11th April

Will be held at DynoSource in Nerang.

LIMITED PLACES - Book Now!

E-Mail Only PLEASE - [email protected]

Link to comment
https://www.sau.com.au/forums/topic/109983-retune-your-factory-ecu-10-110406/
Share on other sites

I remap most Nissan ECU's and the result is often better that most aftermarket computers and the total cost is substantially less. Significant gains can even be made on standard engines.

I would like to suggest that ALL vehicles have upgraded fuel pumps (standard are way bad), full tanks of whatever petrol you want the car tuned on, maintained vehicles (serviced, good spark plugs etc).

Remap Prices cover initial ECU modifications, and loading of pre-tuned maps to suit, these will then need 1-1.5 hours of dyno time tuned specifically to your vehicle and fuel. Dyno time as mentioned will be around $180/hr. ECU modification and Base Maps priced as follows:

S13 CA18 - $330

S13 SR20 - $450

S14 SR20 - $660

S15 SR20 - $660

R32 RB20 - $330

R32 RB26 - $330

R33 RB25 - N/A

R34 RB25 - $660

Z32 VG30 - $330

Chaos - Sure Why not, if it saves me a few hours of stress trying to get a micro guess right.... What loom is in the car?

Dave - S2 and S1 are the same.... I do have a package where I can offer a remapped R32 ECU and use an external VCT controller (like buddy club for $85 I heard)

Just quick one for RB20 people. I had mine done last time Sam was up. Worth every cent hey. And I didnt need the dyno time, just did a quick test and afr almost straight line on 12. Not saying you wont need dyno time, but if you have minimal mods, and it comes out ok, its really good value for money.

I would highly recomend it.

Chaos - Sure Why not, if it saves me a few hours of stress trying to get a micro guess right.... What loom is in the car?

Dave - S2 and S1 are the same.... I do have a package where I can offer a remapped R32 ECU and use an external VCT controller (like buddy club for $85 I heard)

Its an R32 loom, but doubt the car will be back on the road in time, and if it is i wont be able to afford the tune. Maybe next time your up.

Dave - S2 and S1 are the same.... I do have a package where I can offer a remapped R32 ECU and use an external VCT controller (like buddy club for $85 I heard)

Are you sure?? I have recently had to replace my factory ECU on a R33 S2 (1996) and we tried four Series 1 ECU's and they wouldn't even talk to the car. Borrowed one out of a R34 GTT (1998) and it was perfect. Same sticker and serial numbers also.

Moot point for me anyway as I now have a haltech. Thanks for your time though.

Dave

I stand corrected, if you still have your ECU can you take a photo with it's lid off so i can see the board? I may be able to remap them like the 34's :(

Sam.

Edited by Dr_Drift

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...