VSC / VSC OFF Lights
03-07-17, 05:56 PM
#77
Lexus Test Driver
i also know the TechStream 2.0.4 cable will not work on my 2002 SC430 but it will work on my relatives 2010 Camry. I have to use the 1.4.1 cable for my 2002 SC430 and it will always set the VSC lights.
this may explain the lights...found it on another website many moons ago but it applies to our cars.
I found a long but good explanation of why the VSC lights come on...
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]
Last edited by Bgw70; 03-07-17 at 06:04 PM.
The following users liked this post:
Trick1978 (12-13-23)
03-08-17, 02:28 PM
#78
Pole Position
Open up each trouble code and press the erase button.
I think I found out that if you do the bulk erase you have to reset the VSC, but if you erase each code individually, it keeps the ZP settings.
03-09-17, 09:11 AM
#79
Lexus Test Driver
just to be clear, will the car generate a code when I connect techstream? Otherwise, I don't believe I have anycodes at the moment.
04-02-17, 06:09 AM
#80
Found the solution written by Speedemon from Lexus Owners Club
http://us.lexusownersclub.com/forums...4&#entry367124
The problem is solved by putting a jumper on 2 pins in the OBD-II connector under the dash. I think a lot of owners have this problem especially after being scanned for code. Some scanners are not built the same-- that seems to be the explanation. Anyhow, here it is, with a little bit of modification as it suits the SC430.
1. Turn off ignition.
2. Look for the OBD-II connector under the dash, it has a black plastic cover which can be pulled out.
3. Using a 4-inch wire, insert ends on two pins (holes) of the OBD-II connector. Which ones? The connector has two rows of holes with pins inside. The connector's shape is basically rectangle but there's a little wedge shape to it. Like this:
______
/---------\
/-----------\
(see picture below)
I will call the narrower side of the connector the top row, and the wider side to be the lower row. Jump the following pins:
a) on the top row, counting from the left, where the first pin is 1, insert on pin number 3
b) on the bottom row, counting from the left, insert on pin
number 5.
4. Turn ON the ignition, do not start.
5. VSC and Check Engine lights turn ON. That's normal.
6. Wait for the VSC light to rapidly flash.
7. Turn OFF ignition.
8. Pull jumper wire out, cover the OBD-II connector.
9. Turn ignition ON, don't start, wait about 15 seconds to make sure everything has initialized.
10. Start car. Test drive. You've just saved yourself couple of thousand dollars.
Speedemon's car is an LS430. This may therefore be applicable to GS430 and all the UZ-FE family of engines.
http://us.lexusownersclub.com/forums...4&#entry367124
The problem is solved by putting a jumper on 2 pins in the OBD-II connector under the dash. I think a lot of owners have this problem especially after being scanned for code. Some scanners are not built the same-- that seems to be the explanation. Anyhow, here it is, with a little bit of modification as it suits the SC430.
1. Turn off ignition.
2. Look for the OBD-II connector under the dash, it has a black plastic cover which can be pulled out.
3. Using a 4-inch wire, insert ends on two pins (holes) of the OBD-II connector. Which ones? The connector has two rows of holes with pins inside. The connector's shape is basically rectangle but there's a little wedge shape to it. Like this:
______
/---------\
/-----------\
(see picture below)
I will call the narrower side of the connector the top row, and the wider side to be the lower row. Jump the following pins:
a) on the top row, counting from the left, where the first pin is 1, insert on pin number 3
b) on the bottom row, counting from the left, insert on pin
number 5.
4. Turn ON the ignition, do not start.
5. VSC and Check Engine lights turn ON. That's normal.
6. Wait for the VSC light to rapidly flash.
7. Turn OFF ignition.
8. Pull jumper wire out, cover the OBD-II connector.
9. Turn ignition ON, don't start, wait about 15 seconds to make sure everything has initialized.
10. Start car. Test drive. You've just saved yourself couple of thousand dollars.
Speedemon's car is an LS430. This may therefore be applicable to GS430 and all the UZ-FE family of engines.
The following users liked this post:
QLex300 (12-28-21)
04-02-17, 06:24 AM
#81
Had this problem. The check engine light was on, took it to the dealer and they said a hose was disconnected. They fixed it, not much money... Then on the way home, the VSC/VSC OFF came on. I did exactly as this post said. Worked like a charm!!!! Thanks so much for this post. I have been using this board for years now, it is the best!
04-04-17, 03:43 PM
#82
Coleroad, I am not sure, but I will check it out... I will get back to you. I checked, it was not one of these... I feel pretty certain that the scanner used at the Toyota dealer where I took the car triggered the light as mentioned in the posts above.
Last edited by Moondog; 04-04-17 at 04:04 PM.
04-05-17, 08:13 AM
#83
Scanners will trigger the VSC lights ON plus some.
Hence we have developed our own “VSC Lights On” re-set device or else use the paper clip method.
Hence we have developed our own “VSC Lights On” re-set device or else use the paper clip method.
The following users liked this post:
QLex300 (12-28-21)
08-20-17, 12:46 PM
#84
Driver School Candidate
Join Date: Jun 2017
Location: Texas
Posts: 10
Likes: 0
Received 0 Likes
on
0 Posts
Super old topic I know but I just encountered the random appearance of the check engine and both VSC lights. I took a whole 600 mile trip with no performance issues. I just hooked up my Actron OBD II compliant code reader and it showed P0456. I cleared the code and it turned off all lights. They haven't tripped again (yet).
08-21-17, 10:15 AM
#85
Pole Position
Super old topic I know but I just encountered the random appearance of the check engine and both VSC lights. I took a whole 600 mile trip with no performance issues. I just hooked up my Actron OBD II compliant code reader and it showed P0456. I cleared the code and it turned off all lights. They haven't tripped again (yet).
That is the easiest thing to fix (A new gas cap) so it is what most people recommend you start with. The next most common suggestion are the vacuum hoses under the plastic cover of your engine. They dry out and crack and that causes the same code.
08-21-17, 10:20 AM
#86
Driver School Candidate
Join Date: Jun 2017
Location: Texas
Posts: 10
Likes: 0
Received 0 Likes
on
0 Posts
If the problem hasn't returned, it is most likely your gas cap wasn't on tight.
That is the easiest thing to fix (A new gas cap) so it is what most people recommend you start with. The next most common suggestion are the vacuum hoses under the plastic cover of your engine. They dry out and crack and that causes the same code.
That is the easiest thing to fix (A new gas cap) so it is what most people recommend you start with. The next most common suggestion are the vacuum hoses under the plastic cover of your engine. They dry out and crack and that causes the same code.
03-07-18, 01:11 PM
#88
Rookie
Join Date: Sep 2017
Location: Nj
Posts: 53
Likes: 0
Received 0 Likes
on
0 Posts
I tried jumping the wires, but it didn't work for me.guess it might need the sensor replaced? Anything else I can try before buying more parts that I don't need. BTW it's both my vsc and abs light on.
03-07-18, 05:26 PM
#89
Pole Position
Start a new thread and tell us what your problem is. I bet we can solve it. Also, I am not sure the jumper pins are the same in all lexuses, so make sure you have a sc430
03-07-18, 05:27 PM
#90
Rookie
Join Date: Sep 2017
Location: Nj
Posts: 53
Likes: 0
Received 0 Likes
on
0 Posts