Issues with Speedometer/Odometer/Cruise Control Failure

kirkbogle's picture

hello.
I have intermittent times when my speedometer will drop to zero, no matter what speed I'm traveling. During the time it's off, the odometer doesn't turn and the cruise control will not work.

Sometimes the needle bounces up and down a bit before it drops and stays at zero. Other times it works fine. When it fails it is usually after driving for a while.

No repair manuals that are worth anything are available for Quest or Villager (bought Haynes - a waste of money)

It does reference a speed sensor, supposedly on the side of the transmission, but I sure can't see it.

I opened the tranny fluid pan and replaced the fluid, but didn't see anything that looked like a speed sensor with pan and filter removed either.

Any help or suggestions will be greatly appreciated!

Thanks,
Kirk

margarita808's picture

2007 Quest Speedometer problems

I am on a list as well who have this problem. It will be 5 miles off of what i am driving. Sometimes I go 15miles and registers 5 miles. Other times I drive 60 and registers at 80. My car is newer than all posted here. So how is it that this continues to be a problem. To top it off my door just stoped working!! Imagine a terrible accident where car catches on fire and no one can get out. I have to do something fast. Never again will I buy a nissan.
Looking to buy a new car.

ricebike's picture

the fix is to get a new vehicle speed sensor

i answered this on another thread... wasn't a bad job either!

ricebike's picture

great, i'm in the same boat now...

once my odometer hit around 108,ooo miles, it started to do the same thing...

there's another site that has the service manual on accessing transmission trouble codes w/out a scanner tool...

another clue is the O/D light will flash on/off when you put the key to on, engine not started yet

http://www.nicoclub.com/FSM/quest/

i'm leaning towards the sensor on the trans as well so i'm gonna see if it's unplugged

my problem also is making it go into failsafe mode & won't go past a certain speed

mark's picture

my 2001 quest

my van is acting the same way. all the same symptoms.
was it the speed sensor on the trani? and where is it located?

prospe7's picture

Odometer issues

Please let
me know how you fix this problem if you had.....tks....

Mike S's picture

Speedometer/Odometer Intermittent Failure

2001 Quest Owner
I am new to this site. I came here due to the speedometer and odometer problem. Mine started after I took my Quest in for its 100,000 mile major maintenance (timing belt/chain replacement, etc). Has anyone gotten a response on this problem? Or, can you tell me how to use this site to find a repair solution? Thanks!

2001 Quest Owner

labamigo's picture

speedometer issues

I have the same problem with the needle bouncing up and down from 0 to 100. When it happens, the cruise control does not work.

It started a few weeks after the extended warranty expired.

patburrier's picture

speedometer,odometer and cruise control

Hi,
I have the same problems with my speedometer, odometer and cruise control on my 1999 Quest Van. I also can not see my clock or time.

Is this a chronic problem?
Thank you.
Pat

dantexmar's picture

I have the same problem.If

I have the same problem.If you find where the speed sensor is plz post it.I also need to find the knock sensor.Any help you can give would be great.Thanx Dan

ricebike's picture

i posted the link to the FSM

Factory Service Manual

it'll show it there

basically, i raised the front end up... it's in the back of the trans/engine area, closer to the driver side, held by a bolt

i believed i answered this same question a while back in another thread

onfloat's picture

Mine is having problems too!!

I'm having the same problem in my 2000 Quest. The speedometer is intermitant and the cruise does not work when the speedometer is reading zero. As I was driving down the road today when the speedometer came back on the cruise light began to flash on and off until I turned the cruise control off then back on. Once I did that, all worked as expected.