Jump to content
SAU Community

Recommended Posts

Hey guys, i've had some problems with my old ecu and it finally gave out. It was a MEC-R212B and i bought one from a friend that is a MEC-R132. First off would that cause any problems? Next thing, when i put it in the car and turn the ignition on (not starting the car) the ecu light consistantly blinks, exactly like the long flash when you enter diagnostic mode, it just flashes over and over, no short flashes. Also, i cannot enter diag mode, it just flashes no matter what. So then i figured what the hell crank it and see what it does. Well the car cranks but it won't rev if i give it anything over 50% throttle, below 50% it will rev fine and produce boost. if i try to give over 50% throttle it just stops revving period, no noise it just doesn't go anymore. If anyone has any info regarding the flashing ecu light, or the way the motor is acting, please let me know, i have a volt meter and am capable of testing sensors if i need to, just let me know. Thanks in advance. (btw this is a rb20 in a S13, i live in america.)

Link to comment
https://www.sau.com.au/forums/topic/77381-r32-gts-t-ecu-help/
Share on other sites

Sounds like the ECU might be from a N/A engine. Have you made sure the diagnostics dial is returned to a "normal" position?

What's the actual part number on both ECUs? (next to the "NISSAN" on the label). It will be like 23710 04U60 (that's the ECU from my GTS4 / RB20DET).

yes the dail is returned, i turn it and it doesn't enter diag mode, it just continues to flash. My old one was a 23710 11U00 MEC R212 B and the one i bought is a 23710-04U02 MEC-R132. Both are from MT RB20DET's they are just from different years, the r132 is a early r32 and the r212b is a late model r32. I am so frustrated because i feel like the ecu is trying to tell me something by flashing the light but i just don't know what it means. Any help is appreciated!

It's telling you it's the wrong ecu! :(

There are some differences in the engine loom that i know of between early and late model r32 gtst's and i have heard that there are differences inside the ecu as well but cant confirm.

I was talking to a bloke a while back who was saying he had swapped ecus and popped the new one. On opening there were a fair few differences between his old one and the popped one.

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