Jump to content
SAU Community

Recommended Posts

Just thought I'd share with you some very handy info I was given tonight (by a Nissan tech).

Its easy to check the ecu fault codes - something I didn't realise.

I believe the below would also be in the manual...

(btw MIL = Malfunction Indicator Lamp - otherwise known as CEL / Check Engine Light - its orange and on the right hand side of the dash in the M35).

ACCESSING:

NOTE: To access trouble codes, accelerator pedal position (APP) sensor must be functioning correctly.

  • Ensure accelerator pedal is fully released
  • Switch ignition ON. DO NOT start engine
  • Wait 3 seconds
  • Within 5 seconds, repeat the following 5 times:
  • > Fully depress accelerator pedal.
  • > Fully release accelerator pedal.
  • Wait 7 seconds.
  • Fully depress accelerator pedal and hold.
  • After approximately 10 seconds MIL will start flashing.
  • Fully release accelerator pedal.
  • Trouble codes are now displayed by MIL.
  • Count MIL flashes.
  • Compare to trouble code table.
  • Each trouble code consists of four groups of one or more flashes.
  • Ten flashes in a group indicate '0'.
  • The first group of flashes indicate the 'thousands' of the trouble code.
  • The second group of flashes indicate the 'hundreds' of the trouble code.
  • The third group of flashes indicate the 'tens' of the trouble code.
  • The fourth group of flashes indicate the 'units' of the trouble code.
  • A short pause separates each trouble code group.
  • A long pause separates each trouble code.
  • Switch ignition OFF.

ERASING:

  • Ensure accelerator pedal is fully released.
  • Ensure ignition switched OFF for at least 10 seconds.
  • Switch ignition ON - DO NOT start engine.
  • Wait 3 seconds.
  • Within 5 seconds, repeat the following 5 times:
  • > Fully depress accelerator pedal.
  • > Fully release accelerator pedal.
  • Wait 7 seconds.
  • Fully depress accelerator pedal and hold.
  • After approximately 10 seconds MIL will start flashing.
  • Fully release accelerator pedal.
  • Trouble codes are now displayed by MIL.
  • Fully depress accelerator pedal for more than 10 seconds.
  • Fully release accelerator pedal.
  • Trouble code 0000 should be displayed.

Mine showed the code 0000 (10 flashes x 4 times) so didn't solve the problem I was looking for but at least I know all the sensors are working etc. :D

Edited by pixel8r
Link to comment
https://www.sau.com.au/forums/topic/261557-ecu-fault-codes-the-easy-way/
Share on other sites

Just realised the above is all in the manual. For those who dont know, you can find all of this an much more related info in the infinit G35 service manual which you can find online - do a google search. The infiniti G35 is what we know as the skyline V35. :pirate:

There's also more diagnostics for checking fault codes on other systems in the car too.

I managed to get it to work eventually for me and got 0000 also.

No closed to knowing why idle is 150rpm too high but I will start looking for leaks around the throttle body and a few other areas.

Cheers

Andy

it was weird i tried that so many times and it didnt work on mine

Did you get it to the point where the MIL start flashing?

Read below for the plain english version...(by me)...

You may need to use a stopwatch or something to count the seconds.

Turn ignition to ON (dont start engine).

Wait 3 seconds

Then over the next 5 seconds, push the accelerator all the way to the floor and then release it fully - do this 5 times quickly within these 5 seconds.

Then wait a further 7 seconds.

Now push the accelerator all the way to the floor again and hold it for 10 seconds until the MIL starts flashing.

When you see it start to flash after 10 seconds, release the accelerator straight away

the light should then keep blinking - giving you the fault codes. it will flash up 4 codes, pausing between each. it will blink slowly for the first group, then fast for the next 3 groups. 10 flashes in a group = '0'.

ie. code 0123 would be 10 flashes, pause, 1 flash, pause, 2 flashes, pause, 3 flashes, long pause, repeat...

turn the ignition to OFF when you're done - this will exit the diagnostic mode.

next time you start the car it will be back in the normal driving mode.

I just gave it a go myself, first time I didn't get it to work.

Then I closed the driver's door incase that had anything to do with it and when I counted the seconds I used the old school method (1001, 1002, 1003 etc.)

It worked and I also got a return code of 0000 :D

This is a good thing I assume!

  • 1 year later...

Hi all,

Just reading this info, but wondering where to find the fault code info? The infinity G35 manuals I can find are all for the 3.5l v6 non turbo. Am I missing something?

I'm after code info for a m35. Sorry for the old post resurrection!

  • 1 month later...
Just thought I'd share with you some very handy info I was given tonight (by a Nissan tech).

Its easy to check the ecu fault codes - something I didn't realise.

I believe the below would also be in the manual...

(btw MIL = Malfunction Indicator Lamp - otherwise known as CEL / Check Engine Light - its orange and on the right hand side of the dash in the M35).

ACCESSING:

NOTE: To access trouble codes, accelerator pedal position (APP) sensor must be functioning correctly.

  • Ensure accelerator pedal is fully released
  • Switch ignition ON. DO NOT start engine
  • Wait 3 seconds
  • Within 5 seconds, repeat the following 5 times:
  • > Fully depress accelerator pedal.
  • > Fully release accelerator pedal.
  • Wait 7 seconds.
  • Fully depress accelerator pedal and hold.
  • After approximately 10 seconds MIL will start flashing.
  • Fully release accelerator pedal.
  • Trouble codes are now displayed by MIL.
  • Count MIL flashes.
  • Compare to trouble code table.
  • Each trouble code consists of four groups of one or more flashes.
  • Ten flashes in a group indicate '0'.
  • The first group of flashes indicate the 'thousands' of the trouble code.
  • The second group of flashes indicate the 'hundreds' of the trouble code.
  • The third group of flashes indicate the 'tens' of the trouble code.
  • The fourth group of flashes indicate the 'units' of the trouble code.
  • A short pause separates each trouble code group.
  • A long pause separates each trouble code.
  • Switch ignition OFF.

ERASING:

  • Ensure accelerator pedal is fully released.
  • Ensure ignition switched OFF for at least 10 seconds.
  • Switch ignition ON - DO NOT start engine.
  • Wait 3 seconds.
  • Within 5 seconds, repeat the following 5 times:
  • > Fully depress accelerator pedal.
  • > Fully release accelerator pedal.
  • Wait 7 seconds.
  • Fully depress accelerator pedal and hold.
  • After approximately 10 seconds MIL will start flashing.
  • Fully release accelerator pedal.
  • Trouble codes are now displayed by MIL.
  • Fully depress accelerator pedal for more than 10 seconds.
  • Fully release accelerator pedal.
  • Trouble code 0000 should be displayed.

Mine showed the code 0000 (10 flashes x 4 times) so didn't solve the problem I was looking for but at least I know all the sensors are working etc. :verymad:

Guy's I'm having problems with my Airbag light keeps flashing

Ive got a 2001 Stagea ARX4 and theres nothing wrong with the airbags but the light keeps flashing.

Is there a way for me too reset the light cause its possing a problem with me.

Will the ECU Fault Test reset the Airbag light or is there another way.

Im in need of Stagea Help

Dont Worry allready fixed the problem LOL :)

If it's the same problem I had it may return in a few weeks. Mine seems to set off now and again under boost going uphill (atleast that was when it went off last time).

I have a code but as of yet it has been of no use, I have taken pictures of the error screen(s) that came up and am waiting for them to be translated in the hope it sheds more light on the issue.

It has been suggested it could be the seat belt pretensioner but as of yet I have not investigated this as I had disconnected and reconnected the cables under the drivers seat and reset the ecu.

Let me know if you have further issues, we may need to discover the problem together.

I still have the airbag light up but it matches the Mil light that's constantly on.

The reset works for a while which is why I think the tensioner is the issue as they are known to fail, its a bad connection somewhere.

Bis-e-Bee, If you could send me the error screen and codes I will see if the nice Japanese lady at work will translate it, she did a wonderful job on the ecu pinouts.

I still have the airbag light up but it matches the Mil light that's constantly on.

The reset works for a while which is why I think the tensioner is the issue as they are known to fail, its a bad connection somewhere.

Bis-e-Bee, If you could send me the error screen and codes I will see if the nice Japanese lady at work will translate it, she did a wonderful job on the ecu pinouts.

have you tried to get the Error code on the Informeter? There is in the Setup menu a DTC option which brings up the code.

  • 2 months later...

still havent gotten it to work... will try again now.

im wondering if my aftermarket alarm has anything to do with it..as the alarm has a 30 second timer before it disables ignition and requires disarming for the engine to start.

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