Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncements
Discussion Groups
By Brand
BMWChevroletDodgeFordGMHondaLexusMercedes-BenzNissanPeugeotToyotaVolkswagenOther Brands
By Topic
4x4 CarsRVsDrivingMaintenance & RepairCar AudioCollectible Cars
Country Specific
Australian ForumsUK Forums
ArticlesAuto InsuranceBuyingCars & TechnologyMaintenanceMiscellaneousSafety
DMV Resources
Related Topics
MotorcyclesBoatsMore Topics ...

Car Forum / Nissan / Nissan Cars / May 2005

Tip: Looking for answers? Try searching our database.

OBD2 and ECU code reset '01 Xetrra

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
dover52 - 19 May 2005 06:45 GMT
I’m a newbie. I have an ’01 Xterra. Last year at 30k my check engine soon
light came on. I took it to the zone and all 4 codes were for O2 sensors
(0135,141,155,161,) O2 Sensor Heater Circuit Malfunction. Now all 4
sensors can’t have the same problem like this at 30K can they? Anyway,
last year I didn’t need an I/M test. This year when I took it to get
smogged the tech said it’s an auto fail. A racket to force us to spend
money at the dealer. Money that I don’t have right now. Now on the 2000
Xterra you could manually clear the codes on the ECU. The repair manual I
have even shows you how. With ’01 and newer it says you can’t. last night
at another forum a participant said you could still do manual reset on the
ECU.

Now my question. First, is it indeed possible to manually reset the codes
on the “01? Secondly, where is the ECU/PCM modual In the ’01? The repair
manual I picked up makes no mention of where its located. It’s almost like
this is top secret stuff.
Help!!!!!!!!
Sly - 19 May 2005 11:13 GMT
doesnt disconnecting the battery for a period of vtime clear the codes? most
vehicles it does

> I'm a newbie. I have an '01 Xterra. Last year at 30k my check engine soon
> light came on. I took it to the zone and all 4 codes were for O2 sensors
[quoted text clipped - 13 lines]
> this is top secret stuff.
> Help!!!!!!!!
djmcreynolds1@bellsouth.net - 19 May 2005 12:05 GMT
try disconnecting the battery for 5 minutes and pressing the brake pedal for
about 10 secs during that time..if that doesnt work then pull all fuses
labeled ecm for 5 minutes if that doesnt do it then go to the zone and see
if they will clear them for you
> doesnt disconnecting the battery for a period of vtime clear the codes? most
> vehicles it does
[quoted text clipped - 16 lines]
> > this is top secret stuff.
> > Help!!!!!!!!
NissTech - 20 May 2005 01:24 GMT
Just a little FYI for y'all

On OBD2 systems, removing the battery cable will not clear the codes.

The first thing you need to do is check ALL the fuses

> try disconnecting the battery for 5 minutes and pressing the brake pedal for
> about 10 secs during that time..if that doesnt work then pull all fuses
[quoted text clipped - 27 lines]
> > > this is top secret stuff.
> > > Help!!!!!!!!
dover52 - 20 May 2005 05:35 GMT
Thanks Nisstech
dover52 - 20 May 2005 01:12 GMT
Thanks guys. I've tried pulling the + Bat cable for about an hour. The
engine light went out but after about 30 min of driving it came back on. I
haven't tried the + cable w/ brake depressed or pulling the fuses so I'll
give them a try. If anybody else has some words of wisdom i'm open to
learning.
xarquinn@gmail.com - 24 May 2005 21:14 GMT
This is from "Xterrabull" in the xterraownersclub.com message group:

Actually, on 2000 Xterras there is a way to do it via the ECU.
The procedure is as follows:
First, turn the ignition key to the on position.
Then, locate the recessed miniature-phillips head screw on the
passenger side of the ECU (you probably will have to move a bulky,
taped up bunch of wires & punch through or remove a clear plastic cover
on the ECU over the screw).
Once this recessed phillips head screw is located, use a micro phillips
head screwdriver to rotate the screw fully clockwise (it will rotate
approximately 180 degrees or so); then, wait at least 2 seconds, &
rotate it back fully counter-clockwise to the position it was
originally in.
Now, if you have any fault codes, the SES light should blink a series
of slow flashes followed by a series of rapid flashes to give the code
of the fault (non-OBDII standardized codes). If there are no faults,
the SES light blinks 5 long pulses, then 5 rapid pulses.
Now, with the key switch still in the on position, repeat the rotation
of the small phillips head screw as in the above step (once again, the
procedure is as follows: fully clockwise, wait >2 seconds, then fully
counter-clockwise).
Now, turn the key switch off. The next time you start the car, the SES
light should not be on (if it is, then it is still detecting faults).
Also, I believe this may reset the learned behavior of the ECU in terms
of managing air/fuel under load vs. RPM, so there may be slightly
rough-running of the engine for some small period of time (i.e. 15
minutes) when the truck is first driven after reseting the codes (I am
not 100% sure of this, though).

> Thanks guys. I've tried pulling the + Bat cable for about an hour. The
> engine light went out but after about 30 min of driving it came back on. I
> haven't tried the + cable w/ brake depressed or pulling the fuses so I'll
> give them a try. If anybody else has some words of wisdom i'm open to
> learning.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.