Jump to content
SAU Community

Recommended Posts

R34 Neo Turbo

Car wont start now unless I give it a small bit of 'Start ya Bastard' then it fires 1st go and idles fine.

It has been taking longer and longer to start over the last month and today it wouldnt start at all without some help. Car was having this problem before, but I have just changed, turbo, injectors, ECU, coilpacks x2.

I do get code 21, ignition, but that was when I had a missfire. I changed coilpacks and it now runs fine when started. I haven't rechecked to see if Im still getting code 21.

Link to comment
https://www.sau.com.au/forums/topic/425625-r34-hard-to-startnot-starting/
Share on other sites

Have you checked to see if you have any new codes? Link to codes

Just on the issue of hard starting

- Plugs fouled or incorrect gap

- Battery - Cranking power (no dead cells)

When you were changing the turbo, injectors and coilpacks - did you move/unplug the TPS, TCS etcetera ... have you reset the ECU since then and checked for new codes.

Maybe the quickest way to identify your issue/s.

So bit of an update,

Changed spark plugs, no change.

Showing Code 55 (no faults)

I can restart the car if I have had it running within 30 seconds otherwise I have to give it another spray of start ya bastard.

Im starting to thing vacuum leak. I say this because if I give it a rev it drops to 500rpm after and then goes back to idle at 1000rpm. It doesnt catch the revs on the way back down, if that makes any sense.

I had this once, after doing pretty much everything in this thread, and it turns out that it was caused by the ECU not giving any timing when starting the car.. even though once started it would run fine...

I had this once, after doing pretty much everything in this thread, and it turns out that it was caused by the ECU not giving any timing when starting the car.. even though once started it would run fine...

Ive got a spare ECU ill change it and try again but I have just replaced the ECU. Had the problem before and after. Ill give the CAS a swap and AFM and after that im offically out of ideas.

My ECU was fixed by the tuner who was like "uh oops" but there were plenty other issues at the time. ECU has since been changed and this was quite some time ago. I do recall the problem quite annoying at the time!

In my case it was a piggyback ECU sitting ontop of a normal ECU. You didnt mention what ECU you changed but I'd imagine no stock ecu would ever have a problem like this..

Checked all vac lines? Even under the charcoal canister, sometimes the vac hose coming out the bottom comes off. I had this happen on my 34. You can't see that its come off unless you specifically feel the underside of the canister.

Edited by RB25DETC33
  • 2 weeks later...

So problem solved thanks to Jaustech.

The ECU gets start signal, and it has an inline fuse. The fuse had gone. Im not sure what the ECU does when it gets a start signal, possibly a bit more fuel to help kick it over im not sure.

To diagnose this you need to print off an ECU pinout diagram, find the 1 relating to starting and check to see if its getting a signal when cracking.

Now im not sure if the fuse is away from the normal fuse panels (drivers side engine bay/Drivers foot well) or not, but apparently that was the issue and it start like a dream now and runs great.

Moral of the story, check your fuses and if they are all good. Get the pinout for the ECU, find 1 relating to start signal, test.

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