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

Zero point calibration procedure

The zero point calibration procedure listed in this thread worked like a charm, Wife is happy again :dancin:
 
Hello Team,


I got my 2004 4Runner 4.0 VSC TRAC & VSC OFF lights on. I have read through the detailed explanation below and will like do a 0 point calibration.

it all started when my battery went flat, strangely, the water in the battery had drained etc. long story short the battery was serviced and its been working since. the light came on when the mechanic used a diagnostic tool on the vehicle :redface::redface::redface:, something i didnt ask him to do.

I have read the information below about 6x, :) , cos i have not tech knowledge when it comes to this

  1. where do i get to download the referenced manual? i did a search and found another thread but cannot open the files from here. can you please share via dropbox if you it?
  2. Is there a step by step guide to do the calibration? i found this YouTube video, is it OK? is there a better video

i will be glad if i can get a little help here to fix this issue.

images

4LPvj






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]
 

Attachments

  • IMG_0280.jpg
    IMG_0280.jpg
    128.7 KB · Views: 9,120
vsc light

Nice info in thread. But m 2004 my 2004 has a different pic confiquration. pins 4,5,7,13,14,15,16, are populated. any recomedations for this ? Thanks Ray
 
Just got my '04 SR5 V8 last week and so far very happy with it.

This morning after starting the VSC TRAC & ABS light remained illuminated. I went forward and they shut off. I thought nothing of it at first. After work I started it up and the lights came on again, went off, and on again several times then remained on.

Came home and did a search and found this thread.

I remembered yesterday I took the 4R to emissions inspection where they most likely hooked up something to the OBDII port, erasing the zero point.

I preformed the zero point calibration as instructed on the thread link above and VOILA! lights went out. Went for a test drive and lights stayed off.

:thanks: A big THANK YOU for this forum and for people sharing their knowledge!
 
well, I realized this happened during the 31 degree morning here. I tried the paperclip thing over and over again. Finally pulled the negative lead and wiped down my SE rims. Back to normal.
_________________
2007 SE V6 titanium
 
It popped again, this morning was only 44 and rain (garaged). pulled batt.
________________________________
2007 SE V6 Titanium
 
It dropped to 34 this morning, happened again. Just pulling battery negative now. Guess I should look for a code one of these times.
_______________
2007 SE V6
 
Hello Team,


I got my 2004 4Runner 4.0 VSC TRAC & VSC OFF lights on. I have read through the detailed explanation below and will like do a 0 point calibration.

it all started when my battery went flat, strangely, the water in the battery had drained etc. long story short the battery was serviced and its been working since. the light came on when the mechanic used a diagnostic tool on the vehicle :redface::redface::redface:, something i didnt ask him to do.

I have read the information below about 6x, :) , cos i have not tech knowledge when it comes to this

  1. where do i get to download the referenced manual? i did a search and found another thread but cannot open the files from here. can you please share via dropbox if you it?
  2. Is there a step by step guide to do the calibration? i found this YouTube video, is it OK? is there a better video

i will be glad if i can get a little help here to fix this issue.

images

4LPvj

Well the ports that were used in the previous picture works. As if you may needed another one I have detailed them below. Done exactly how following video describes using the ports displayed below and worked great. Even did it two separate times for the giggles. Also the best description of how to do this is via this YouTube link: https://youtu.be/0GZS_Nqub1U

Counting from driver door (left to right)
Top port it #3
Bottom port is #5
Good luck!
 

Attachments

  • 06F6902A-7C37-4261-8FC5-18AEAFA46901.jpg
    06F6902A-7C37-4261-8FC5-18AEAFA46901.jpg
    106.8 KB · Views: 3,452
I'm new to using forums but I have the same issue. I bought a new gas cap drove for a while and lights stayed on I was told to disconnect the battery for 10 min I do so and it started but riddled weird shut off now it won't start
 
i was hoping my lights were on due to the "drive" light on the dash cluster was out due to some circuitry cause...

but it turns out that after replacing that bulb, nothing was resolved & this wasn't a fix..

i have tried the zero point calibration many times without success so this was my next attempt to fix this issue
 
After emission testing (WA State), the CEL, the VSC OFF and VSC trac lights were all ON in my 2004 Limited V8.

I disconnected the negative terminal of the battery for 15 minutes and all the lights went OFF and have stayed off for 2 weeks! I thought I was also going to have to do the Zero Calibration procedure, but disconnecting the battery did the trick without the procedure (so far).

Just thought I'd add to the data here.
 
No Luck

Hey guys I have tried clearing my lights via the zero point calibration with no such luck. I can get the ABS and VSC lights to blink (as at the end of step 1) but then when I switch off the ignition to move on to the next step nothing happens. Can some one help me with this annoying issue please.
 
Any chance you had this lifted recently ? If so may have stretched abs sensor wire ! Won't matter how zpc you do .

I actually did just have a 2 inch lift done on it, but the light came on before then. We had new tires put on and then two days later it appeared. We also had an rear axel seal replaced so I'm not sure if that might have messed up the sensor or not. I did clean out the sensor just in case.
 
Doesn't take much to mess the wires up on these ! Very weak . Usually something minor so don't freak , check & just work backwards , you'll get it !
 
My son's 05 has had a weird deal when driving thru snow/ice last yr going back to school , then last week we had good 2 days of rain & lights/xmas tree came back on ! Believe it must be in one of 2 front sensors themselves ! i used my computer spray like I use for MAF cleaning & a shitload of water came out , the did zpc but like an idiot pulled into driveway to give me some xtra room , then went duh soon as I leveled back down cleared all lights ! :whoo:
 
This has been plaguing my 04 SR5. I've done the gas cap, done the battery disconnect, done the zero point recalibration and still the lights come back on within 10 seconds. Also even though the CEI light is on my scan tool shows no codes? what's left?
 
Goggle search stoplight switch ! A lot of guys had the above problems & a simple (in my case 25$ amazon buy) ! Behind brake pedal 1 plug & done just a thought .
 

Members online

Forum statistics

Threads
278,316
Messages
3,554,120
Members
248,016
Latest member
Advally Service

Trending content

Back
Top