4

We own a Nissan 350 Z and this morning it would not start. It would turn over but it wouldn't fire. After pulsing the gas a little bit it would start but then letting off the gas would cause it to die. I held it down long enough to get it to stay started. After that I had no issue starting it and assumed I got some bad gas. However, when I went to pull away I noticed that three lights on the dash were on and the car would not accelerate. It would move at idle speeds only, pressing the gas would not cause it to accelerate.

The lights that are on seem completely unrelated and are thoroughly confusing me. The lights are "Check engine soon", "TCS OFF", and "SLIP". None of those seem related to one another and I'm unsure why a light such as "SLIP" would be on in our parking lot in the middle of summer.

There could still be some bad fuel, but I'm pretty confused about the rest of it.

Any suggestions?

3 Answers 3

2

The Check Engine code could be related to the other two. Pull it and see. It might give additional clues to the cause. Attack this issue first.

The traction control and SLIP sound related to each other. Look into what causes the SLIP light to stay on.

Bad fuel typically should not keep the car from accelerating if it is idling fine. There might be a sensor that is detecting a problem with the fuel or something else and disregarding your accelerator pedal position.

4
  • I disconnected the negative terminal on the battery and waited ten minutes before re-attaching it. This reset the computer and all lights except the check engine light went off and the car resumed normal acceleration. Do you think turning it on and off so much trying to get it to start could have caused the computer to freak out?
    – CatDadCode
    Jul 5, 2011 at 16:38
  • Possibly, but the check engine code might shed some light.
    – jzd
    Jul 5, 2011 at 16:58
  • I'm getting it checked out right now. I'll let you know what I find :)
    – CatDadCode
    Jul 5, 2011 at 16:59
  • I can't quite remember what was wrong, but I never came back to update. It was definitely a sensor of some kind that just needed replaced. Pulling the check engine code was all they needed to do and they were able to replace the faulty sensor.
    – CatDadCode
    Jun 2, 2014 at 17:23
2

I believe there is a procedure to deciper OBD faults on the VQ35DE motor without any additional hardware - this allows you to count the # of times the CEL blinks to determine a wide variety of fault codes. I'll try to post it when i find it.

Also, there are inexpensive OBD2 bluetooth dongles that will let you pull faults very easily.

Until you do this, we're all taking shots in the dark.

-2

check your crankshaft sensor. worked with me 100%

1
  • 4
    Martin - can you give a bit more detail in your answer. As it stands, this is not very useful.
    – Rory Alsop
    Jun 1, 2014 at 15:16

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .