Jump to content
SAU Community

Recommended Posts

I am working on my mate's R34 RB25de NEO car and he has a really strange issue.

I have confirmed via Nissan FAST that his car is indeed a non Turbo automatic and I have also confirmed his actual ECU is for a non Turbo r34 automatic.

The issue is this;

when I connect via consult port with Nissan datascan or ecutalk or conzult etc they all say that his timing is 10deg btdc and it jumps around to as low as 3 or 4deg and as high as 12 to 15deg at idle. Tps voltage is perfect. The engines timing was set to 10deg also. His car was randomly dieing while on the move.

The r34 fsm says it is supposed to be 15deg btdc and I've set it to that but why does ecu expect 10deg?

Any ideas?

Do I need another ecu?

If so, anyone have a non Turbo r34 auto ecu to give away?

Link to comment
https://www.sau.com.au/forums/topic/416050-help-very-weird-r34-ecu-problem/
Share on other sites

Also, what are the consequences of having the ECU expecting 10deg btdc and actually setting the engine at 15deg btdc??

Could the issue actually be a Nissan ECU programming mistake???

The engine is actually a 2.5L NA Neo engine which the R34 FSM says has to be set at 15deg btdc.

you can't actually check the timing via a consult cable unless you actually have a timing light as well. and to set the timing you need to put the car into base idle mode, which locks the timing (generally at 15 degrees). at idle it is normal for the timing to jump around a bit.

but as long as the timing that you see with a timing light and the timing you are seeing on the consult are the same then there is nothing to worry about.

Oops, I should have also mentioned that with a timing light the timing had been set to 10deg and there ecu also said 10deg.

Now I know the ecu is static and can't be altered. So the ecu saying 10deg in base timing mode for a 2.5L Rb feels wrong due to all the Nissan service manuals saying that all 2.0L RBs should be set to 10deg, all 2.5LRBs should be 15deg and all 2.6L RBs should be 20deg at stock.

So this ecu seems wrong. But if someone had an Auto r34 ecu non turbo I could borrow or have our even buy in Melbourne that would help me heaps

Yes I had it base idle mode/timing mode and rpm was at 600 as per manual. Quite literally by the book. That's what is weird, The ECU seems to think normal is 10deg. Its got me stumped

Edited by THRLLR

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