Jump to content
SAU Community

Recommended Posts

M35 won't fire

Evening, sorry about the long post but I'm trying to give as much info as possible.

I have recently acquired a 2001 M35 stagea (VQ25DET), the morning after driving it home it it would turn over  but not fire, after 10 minutes of trying it finally fired up but ran like crap. Next few starts it started and ran well. 

Saturday morning it started and drove fine. Come Saturday afternoon it wound over and over, after 20 minutes of trying it finally started, but ran terribly all the way home. Got it home and shut it off and tried to restart it and it just wouldn't fire. Sunday morning I tried and just keeps winding.

I have checked all the fuses, changed all the coils, the plugs, the immobiliser batteries and the CAS and it still won't fire, when turning over it will get the occasional cough but that's it. The cam sensors were changed with the recal but I'm not sure how long ago.

The car is running a Greddy Emanage and the MIL light is on all the time (owner said this and after searching it is a common thing with these ECU's) 

I have tried the self diagnostic thing with the key and the pedal but for the life of me I can't get the MIL to flash, I've used a stop watch to time everything and still can't, no sure if just me or emanage has something to do with it

I don't have a scan tool and can't start the car to take it anywhere, does anyone have any ideas or suggestions on why it won't fire?

Edited by Coullsy
Link to comment
https://www.sau.com.au/forums/topic/472151-m35-wont-fire/
Share on other sites

May be flooded. I would check to see if you have spark. If it does, dry the plugs and try some start ya bastard. Something obviously isn't right considering it runs well then it doesn't. Do you have the software for the emu so you can see what's going on? There was someone over in Adelaide that is pretty knowledgeable with m35 and emu. I think its BoostdR.

 

 

 

 

 

Link to comment
https://www.sau.com.au/forums/topic/472151-m35-wont-fire/#findComment-7851574
Share on other sites

Ive attached a quick video of the spark, to me it looks weak, as I believe it's meant to be a bright blue, but that could be from the gal I had in the tester.

i did manage to finally get it to throw codes which came up with the following.

0100 - AFM

1320 - ignition signal

0110 - intake air temp sensor

1705 (I counted 1805, but could of counted wrong, will confirm)- Throttle position sensor circuit A/T

The 0100 AFM fault may be because I disconnected it and tried to start it to eliminate it. I will reset the codes and see what it throws up again. 

Would the 0110 code be related to the above?

1320 code I don't know what it could be, as I've done the coils, plugs, CAS and rechecked all the plugs (possibly throwing the codes due to not resetting after changing them?)

Is it possible that the TPS is the issue that is preventing it from starting?

IMG_5996.MOV

Link to comment
https://www.sau.com.au/forums/topic/472151-m35-wont-fire/#findComment-7851631
Share on other sites

  • 4 months later...

So an update on this for those interested.

 

Turns out that the Emanage was dumping alot of fuel into the cylinders.

instead of dealing with the emanage, it was ripped out and now i have installed a Haltech Elite 2500. The car is together and has been tuned. Currently making a healthy 252AWKW.

Link to comment
https://www.sau.com.au/forums/topic/472151-m35-wont-fire/#findComment-7867880
Share on other sites

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