One cause & fix for "VSC TRAC" & "VSC OFF" lights, Zero Point Calibration

[Canada 4 Runner]

I have a 2003 Toyota 4 Runner Limited. a couple of days ago, VSC TRAC + VSC Off & Engine Lights all came ON at the same time.

I live in Canada and it is pretty cold, but I have used this same car the whole past winter without issues.

I have replaced my tires about a month ago, but it was fine right after that..

I have read many of the threads, and they are useful, but is there anyone who could help me with what should be done to this specific case (3 lights!!).

I had VSC Off + VSC TRAC + CEL (Check Engine Light) ON.

I disconnected the +ve terminal of the battery over night and this morning reconnected it and all lights are gone.

I drove the vehicle for more than 1 Hour and no lights came ON. I checked the Traction and it is working as well as the ABS.

I will drive it for another day or two and see what happens. I may take it to my mechanic to have him look at it as well.

This site is so helpful.. Thanks all for sharing your experience.

 

[glebov88]

So I did this test like 4 months ago with my brother in law and nothing worked the lights stayed on BUT I just checked the instructions and had noticed that he didn't read the last part so what do I do I grab a stereo and a paper clip follow the instruction and wam bam thank you mam I am all fre of the VCS LIGht YEAHH. I am very very happy thanks Guys. Just finished installing an HID kit will post pic soon. had a slight problem but figured out it was a polarity problem switched the switch upside down and wam their shell be light man 6000k looks good arty:

 

[rotten1]

toyota 4 runner vsc light

Hey I just wanted to thank micablue for his detailed information on the zero point calibration. I brought my wifes truck in for inspection and here in New Hampshire the hook up to the diag connector. Now although I know the vsc light may come on at anytime it just didnt seem right. I performed the recalibration according to procedure and low and behold off the light goes. You learn something new everyday with vehicles

 

[V-bOnE]

VSC TRAC, VSC OFF, and ABS on ONLY when headlights on?!?!?!

I'm hoping someone can help...I get all three lights, but ONLY when the headlights are turned on. In fact, it only takes turing the parking lamps on to trigger the lights. I did do the ZPC last night, and in fact the lights cleared...but then this morning as soon as I turned the headlights on, there were the lights to greet me. Anyone got any ideas? Please help!!!

 

[RORYRRFA5]

WOW!!! I recently found this forum due to the Dealership wanting to charge me $100 for my VSA/TRAC lights being on. I too went through emissions, and they told me that it was like that before I came in. Well I tried the Procedure, and to my avail it worked!!! I just want to that everyone who has done some reserch and figured this out. THANK YOU!!!

 

[CJ3Flyr]

I'm hoping someone can help...I get all three lights, but ONLY when the headlights are turned on. In fact, it only takes turing the parking lamps on to trigger the lights. I did do the ZPC last night, and in fact the lights cleared...but then this morning as soon as I turned the headlights on, there were the lights to greet me. Anyone got any ideas? Please help!!!

Somebody (maybe you) just posted a very similar issue. They pulled the plug and shot some contact cleaner and replugged the cluster and the problem is gone.

 

[V-bOnE]

Somebody (maybe you) just posted a very similar issue. They pulled the plug and shot some contact cleaner and replugged the cluster and the problem is gone.

Wasn't me who posted but thanks for the tip...I just put it on the charger, and so far it hasn't happened again yet...(fingers crossed)...could it be the battery? I've got a pretty beefy amp powering my subwoofer...

 

[FinRxDoc]

Question about setup for the fix

If I am reading this correctly, I will take two wires (my plan is 12G romex) and insert them into the correct spots in the OBD II connection port. I will stand outside of the vehicle and touch the opposite ends of both wires together "4-8 times". I will go through a series of on and off procedures and this should work.

My question is, is my devices, a set of two wires plugged into the correct pin positions, then touching the opposite ends the correct procedure. I want to be sure before I attempt this and destroy my truck.

 

[FinRxDoc]

bump!

 

[darktiger]

I am having this exact issue after the Texas emissions test....

 

[CJ3Flyr]

My question is, is my devices, a set of two wires plugged into the correct pin positions, then touching the opposite ends the correct procedure.

Yes, 14ga or 16ga is adequate and easier to stuff in the pin receptacles.

 

[ZITOMAN]

Ok, I've read all the threads and the dash lights that light up on my '06 4Runner LTd are the following;
- VSC OFF, VSC TRAC, ABS, Slip indicator light

I've performed a hard reset on ECU by disconnecting the negative battery terminal, waiting 5 mins and re-connect. I replaced the gas cap with an OEM replacement, all with the same result .
The lights come on while I'm driving intermittently and stay on until the vehicle is turned off. When re-started, the lights stay off but eventually turn on again.

There were NO codes stored in the ECU even while driving and the lights turn on! What a strange problem, definitely a bug somewhere in the firmware or software since it's not triggering a code.

Any help would be appreciated by members of the forum.

BTW: I contacted my local toyota dealership and they have experienced this problem with other 4Runner but would not give me the solution except to bring in the vehicle.

 

[CJ3Flyr]

Ok, I've read all the threads and the dash lights that light up on my '06 4Runner LTd are the following;
- VSC OFF, VSC TRAC, ABS, Slip indicator light

I've performed a hard reset on ECU by disconnecting the negative battery terminal, waiting 5 mins and re-connect. I replaced the gas cap with an OEM replacement, all with the same result .
The lights come on while I'm driving intermittently and stay on until the vehicle is turned off. When re-started, the lights stay off but eventually turn on again.

There were NO codes stored in the ECU even while driving and the lights turn on! What a strange problem, definitely a bug somewhere in the firmware or software since it's not triggering a code.

Any help would be appreciated by members of the forum.

BTW: I contacted my local toyota dealership and they have experienced this problem with other 4Runner but would not give me the solution except to bring in the vehicle.

Did you perform the reset procedure or just disconnect the battery for 5 minutes?

Try the procedure outlined in this thread.

 

[ibcp]

Results of reset

Had these lights appear after I took my 2004 in for service at a local shop. They told me things go wrong and break all the time and it wasn't their problem even if they did come on while the vehicle was in their shop at the time. They said they didn't do it. Now I know what happened!

Looked up the symptoms, found this thread, followed the instructions on pg. 7 of the TSB using a 2' section of speaker wire.

Worked like a charm!!!

FYI, when I made the 4+ contacts per the instrcuctions, the ABS started flashing too. no problems. Guess this is normal.

Thanks!!!!

 

[Brads 04 4RUNR]

04 4-Runner VSC Trac and VSC off lights

Thanks a ton for taking your time to post this fix. I had my 4-Runner at Auto Zone last night and thought that the MX light was a service engine soon light. The AutoZone guy hooked up the tester and then noticed it was maintenance and un-hooked the diagnostics unit. The lights came on after you move the vehicle and go off at start up but as soon as you move the vehicle again they come back. I have not tried your fix yet, but this has to be the problem. I even took the vehicle back to AutoZone and they said it was a conicidence and that they did nothing wrong. Of course they were wrong.

Thanks again,
Brad

If you suddenly have the "VSC TRAC" and "VSC OFF" lights in your dash, this post may help you fix the problem yourself. The information here applies to 4th gen 4Runners that use the ISO protocol rather than the newer CAN protocol for their OBDII interfaces to code readers, ECU programmers, hand-held testers, etc. The OBDII interface includes several different protocols (methods of digital communication) and they all use the same physical connector, though with some different pins. The connector is located at the bottom of the dash on the driver's side and in the 4Runner it's covered by a small black cap.

4Runners switched from ISO to CAN around 2005 though this information may also apply to newer 4Runners with some modification. That is, newer 4Runners may display trouble codes and reset sensor calibration values in response to the connection of different (than earlier 4Runners) pins together than the ones described below.

Several posters have discussed similar problems, described in several different threads. I'm reluctantly starting a new one, with a more specific title (including the exact name of the two trouble indicator lights), in the hope that searchers will more easily find a solution.

The specific behavior: On startup, the "VSC TRAC" and "VSC OFF" lights come on and stay on. The ABS light may or may not come on. On subsequent starts the lights will come on temporarily as usual (as a bulb check) and then go off. They come on again and stay on as soon as the 4Runner is moved. The "check engine" light does not come on. This behavior begins after the vehicle has been hooked to some sort of OBDII code reader or engine tester or data logger, etc. Though the lights are on, no standard OBDII problem codes are detected by a regular code reader.

Cause: The code reader or other OBDII device has attempted to communicate with the 4Runner using the CAN protocol (involving pin #14) and this has caused the 4Runner to erase the "zero point calibration" numbers in its memory. Without these numbers it can't get accurate information from the yaw rate and deceleration sensors (in the center console near the gearshift) and so it disables traction and stability control functions.

The fix: Perform the "zero point calibration" procedure as described in TSB BR001-04. This procedure can be performed without special equipment such as a hand-held tester or OBDII reader. You only need the equivalent of a jumper wire to short together two pins of the OBDII connector at the right time and the right number of times between switching the 4Runner on and off. More detail is included below, leveraged from my other posts.

Why this doesn't happen every time a code reader is used: The code readers usually use the pins and protocol of the OBDII connector in a specific sequence, trying first to establish communication with the vehicle using the oldest protocol. They then try the pins and protocol of newer protocol standards. Usually the code reader would be successful in its first try at establishing contact with the 4Runner using the ISO 9141-2 protocol, and there would be no problem. However these communications schemes are not foolproof and occasionally the ISO protocol attempt fails. Then the code reader tries newer protocols including CAN (controller area network). It's this CAN attempt, which toggles pin #14 (the CAN data pin) that accidentally tells the 4Runner to erase the existing zero point calibration data. Since the 4Runner (this vintage anyway) can't communicate by CAN protocol the tester re-tries the older protocols again and eventually succeeds in setting up communication by the right ISO protocol. But by then the calibration data has been erased.

The calibration, by the way, is simply a matter of telling the 4Runner VSC/TRAC computer "your yaw rate and deceleration rate are currently zero" and to save the associated values. Then the output from the sensors can be interpreted correctly.

Detail (may be helpful if you're going to do the calibration procedure yourself): The SST (special service tool #09843-18040) specified in the service manual appears to be essentially a Y-shaped test lead and is variously called a "jumper wire" or "diagnostic check wire." It's used in this case to repeatedly connect and disconnect the chassis ground (CG, pin #4) and Ts (pin #14) terminals of the OBDII connector (referred to as DLC3 in Toyota-speak). The connection/disconnection sequence and timing are described in the service manual and in several TSBs. OBDII connector diagram and pin descriptions are in TSB BR005-03.

Since the OBDII connector is at the lower edge of the dash and pointing down (right above your left foot when you're sitting in the driver's seat) it's rather tough to reach in and do the shorting to the appropriate terminals of the OBDII connector with a test lead. Especially since you're supposed to avoid moving or shaking the vehicle when you're doing this. BTW, the OBDII connector usually has a black snap-on cover over it to keep out grit, etc.

Therefore I took a couple of pieces of insulated wire about 24" long each and taped them alongside each other, and stripped both ends. To make the wire fit securely in the (female) terminals of the OBDII connector I soldered a 3/8" length of metal (cut from a heavy paper clip) to one end of each of the wires. I chose a pin size so that would fit securely in the female terminals of the OBDII connector but wouldn't distort them. I used some heat shrink tubing around the solder joint to reduce any chance of accidental shorting.

After plugging the two pins into the OBDII connector (with the other ends held apart) I was able to hold the other ends of the two wires in my hands and touch them together at the appropriate times to connect the pins of the OBDII connector. I had a helper in the passenger seat to read the instructions from the TSB to me in sequence.

This is not very hard to do, and one need only be careful. It's easier to do with the Toyota OBDII tester, of course, and would only take 5 minutes. You might be able to get your dealer to do it gratis, but you might also be charged some minimum labor hour rate.

BTW #1: Doing the sulfur TSB or others that require the replacement or reprogramming of the engine computer or the VSC computer will also require this calibration.

BTW #2: I verified that when the lights are on the VSC and traction control are indeed inoperative. ABS is working, though.

BTW #3: Shorting other pins (such as #13 Tc) at the right time can cause the appropriate dash indicators to blink in sequence to reveal trouble codes other than the OBDII ones. A generic OBDII code reader won't give you this data, and you need the service manual (physical or online) to make sense of it. I believe there is a specific code to tell you that the zero point calibration data has been lost, but I didn't look for it.

BTW #4: In the 4Runner of this vintage the OBDII connector pins populated are 4, 5, 7, 9, 13, 14, 15, 16

[Sorry about the long post, but I wanted to include the kind of information I'd want if I encountered this problem and wanted to feel comfortable fixing it myself][/QUOTE]

 

[RosettaRock1]

Does this apply to a 2007 4runner? I brought my car in for a inspection sticker check and this morning my VSC TRAC, VSC OFF and CEL are all on.

Could someone confirm that they performed this fix on a 2007?

 

[CJ3Flyr]

Does this apply to a 2007 4runner? I brought my car in for a inspection sticker check and this morning my VSC TRAC, VSC OFF and CEL are all on.

Could someone confirm that they performed this fix on a 2007?

Yes it'll work on a 2007.

You must find the cause and get the CEL light to extinguish prior to performing the procedure.
:cheers:

 

[LC_4R]

I have also been through all this with my 04 4runner.

The problem was at first intermittant, and when I went to the dealer, the lights had gone out. They said its 60 bucks to check anything because there is no CEL.

Stupidly, I let the warranty run out. Then the CEL and VSC lights would always come on. I learned that disconnecting the neg terminal on the battery would clear the lights but after a short highway drive, they would return. I bought a OBDII tester and found the code for the rear O2 sensor (bank 2 sensor 2) was reported. But replacing this rear narrowband sensor did not make the problem go away. Very frustrating to say the least. The O2 sensors are very badly positioned by the way.

My next move is to swap the rear O2 sensors (the post O2 sensors) to see if I can troubleshoot the issue to the cat or possibly the front air-fuel sensors. I would expect the code to then jump to the other bank is my thinking.

I have been through the resetting of the VSC with a jumper and am fed up with this issue. The VSC is needed and the traction control (squiggly icon on dash) also seems to be de-activated from this silly O2 sensor code. Luckily the antilock brakes still work. This vehicle is now the 'baby-car' as we have the baby seat in the middle in the rear seats.

I wonder what can be done legally to report this software issue? Its my opinion this should be a recall. In my case, the rear O2 sensor is being tested on the fly by the ecu (to see if the cat is working) and if it doesnt detect the enriched mixture, then the CEL comes on and the VSC is disabled. Pure stupidity and poor engineering in my opinion.

 

[playerzworld79]

Awesome

Had my 04 4runner about 3 weeks now. lights came on 2 weeks after i bought it. Dealership wouldn't help me out even though i bought it from them. found me some speaker wire and printed off the directions and 5 min later was testing it out in in 24 inches of snow behind the house. everything is working awesome and the lights are off!

 

[DCFD04SR5]

VSC Trac Lights on, no diff lock, no 4wd

Hello everyone,

So far this site has been great. I am looking for some help and advice. My 04 SR5 was recently at the dealer (mistake) for examination of what I thought was a faulty TPMS sensor, oil change, and removal of cracked lock nut. When I picked the truck up I was not even out of the parking space when the VSC lights came on and would not turn off. The tech who ran the codes could not figure out the exact problem as to why. Needless to say the problem was "fixed" and the light went out.

I made a point when I arrived home to check my differential lock and 4wd - both not working. (VSC light still off)

My question is, would the VSC somehow create a condition where the differential lock and 4wd no longer engage?