Originally Posted by KingPrat

Maybe YOUR gas cap is loose....

This is awesome. Thanks! STICKY!

Originally Posted by justinsmnz

Hi all - first post here and just want to thanks everyone for the awesome info and insight on the forum! I'm currently on my second 4Runner after recently trading my '05 SR5 V6 2wd to a local older gentleman for his '03 Limited V8 4wd (I'm moving to the NE from Florida next month and figured it would be best to get a southern-owned 4wd prior to the move.) The truck I'm working with now is the '03 with 201k on the clock.

Before the trade, the owner told me that the 4 lights (VSC TRAC, VSC OFF, ABS, and BRAKE) had come on a month or so prior after an independent shop replaced both front hubs. The shop did not give him a firm answer on what it could be, and he had not followed up since. Although the 4 lights have stayed illuminated the entire time I've had it, I have not seen a check engine light for any reason in the 2k miles I've put on the truck so far.

I replaced the front brakes (calipers, rotors, pads) prior to bringing it in to the dealership – not as a potential solution for the lights, but I figure I should mention it anyways. After swapping the brakes, I took the truck to the dealership for a dashboard swap and also had them flush and bleed the brake system while I was there. They pulled a code, but only wrote on the paperwork that it was a faulty front ABS sensor. I was in a hurry, and forgot to ask them for the actual code that it threw. Because of previous owner mentioned that the lights showed up after a hub replacement, my first thought was that a mech dropped one of the hubs and damaged a wiring harness on one side or another. When I got home, I ordered new harnesses for both sides and a pair of new speed sensors (OEM harnesses, 3rd party sensors)

All that to lead up to today: I replaced both front speed sensors and wiring harnesses. I disconnected the battery for an hour or so after installing, but before cranking, hoping that the new parts would clear out the codes on their own. Of course, it couldn't be that simple, and the lights stayed on like usual when I cranked it again.

I knew that there was a possibility that I would need to do a zero point calibration to get the codes to clear, so that was my next step. I parked in my garage, which is as flat as I can get around here, and did the calibration procedure. All went to plan, and everything seemed fine: the lights acted how they were supposed to (stayed on for 15sec then went off after clearing, then blinked while I reset, then stayed off when I turned off/on the third time.)

However, when I went to test drive after the zero point calibration, the VSC system engaged as soon as I hit the gas and before I could even get out of the driveway. I couldn't press the gas more than 10% or so before the VSC system engaged and lurched the car (in drive and reverse.) Of course, I couldn't drive it like that, so I shut it off and took the steps to clear the zero point calibration (touch paperclips 4 times then turn off.)

After clearing the calibration, the VSC TRAC and VSC OFF lights remained on after cranking, but the ABS and BRAKE lights remained off. The truck drives like normal again, but unfortunately after less than a quarter mile drive, the ABS and BRAKE lights came on again and have stayed on for several crank cycles.

Now I'm at a loss for my next step. I have an appointment with the dealership Thursday a.m. to pull the code again and have them do a zero point calibration in case I am screwing something up in the process, but besides that I'm not sure what other steps I need to be taking to clear out these lights.

Any thoughts or ideas would be greatly appreciated!

One more note: my driveway curves coming out of my garage, so I have to make a relatively sharp turn as soon as I back out. My driveway is also somewhat sloped to get out to the road. I don't know if either of those factors might be playing a part in the VSC system engaging immediately after the zero pt calibration.

Originally Posted by soula_ollie

2004 4runner has the same problem, the check engine light came on and the VSC TRAC and VSC OFF are lit up.

The OBD reader gave back 4 codes:
1. C1201 - engine control system malfunction
2. C1241 - Low battery positive voltage or abnormal high battery positive charge
3. C1246 - Malfunction in master cylinder pressure sensor
4. P0420 - Catalytic efficiency below threshold bank 1

I have checked the gas cap...DIDN'T fix it. HOWEVER disconnecting the battery for 15 seconds are reconnecting turns the lights off (temporarily). Month later lights are back on. I am assuming the battery fix is temporary. Is there any way to know what the root problem could be?

Originally Posted by BlackWorksInc

Originally Posted by BlackWorksInc

So, this seems to be a constant source of confusion for many members as of late and since I have some time to kill, I figured I'd help clarify some things in an attempt to help members with this issue in the future.

On the 4th Generation 4Runners (this applies to a lot of Toyota SUVs, Minivans, and some cars as well) when an OBD-II DTC set and stored in the system, the MIL, TRAC, and VSC lights will always come on to indicate a fault in the OBDII System. If you have an ABS capable scantool you will see a DTC C1201-Engine Control System Malfunction, this DTC is always set when an OBDII DTC turns on the MIL; its the code that shuts off the VSC & TRAC systems and turns on the lights on the dash . Don't be worried about this DTC, when you correct the original DTC(s) that set the MIL on, the C1201 will erase along with the original codes with a scantool.

Before we delve into the how's and whys, lets first clarify some terminology;

MIL- The MIL or "Malfunction Indicator Lamp" is the SAE (Society of Automotive Engineers) term for the colloquially referred to "Check Engine Light (Sometimes abbreviated as "CEL") and is most often shown as a small engine block, sometimes "Check" is under the icon or in some other vehicles "Service Engine Soon" is used instead.

Examples of MIL Icons:


TRAC- TRAC is the abbreviation used by Toyota (and some other manufacturers) for Traction Control System. This is system is often used in combination with the VSC and ABS systems.

VSC- VSC is another acronym for Vehicle Stability Control and is often what you see when the vehicle is skidding/sliding as the vehicle tries to regain control; this is often in conjunction with the ABS and/or TRAC systems.

OBDII- This stands for OnBoard Diagnostics Generation II, this a standard of automotive self-diagnostic system(s) created in conjunction between SAE, EPA, and Vehicle Manufacturers. If you'd like to learn more about OBDII here's a helpful website; OBD-II - On-Board Diagnostic System

DLC- This is the 16 pin OBD-II mandated connector that all factory and aftermarket scantools communicate through and is mandated by OBD-II regulations to be mounted under the driver's side dash area. (On the 4the 4th generation 4Runner it is located underneath the access panel for the interior fuse block)

DTC- Another SAE term that stands for Diagnostic Trouble Code; these are designed to help aid diagnosis of a problem and identify a system that may have a problem, and example of a DTC would be a P0455- [Emissions, Gross Leak Detected] (A helpful break down of how to understand DTCs if you want OBD-II Codes Defined)

PCM- PowerTrain Control Module, the heart and brain of most modern vehicle's fuel injection, ignition, emissions, and sometimes transmission control systems. This puppy make your 4Runner go vroom vroom.

~

Now that we have some of the terminology explained, lets get into the two most common issues people run into:

MIL OFF, TRAC On, VSC On (and maybe ABS On IF an ABS code is set also)- There is a Non-OBDII Failure in the ABS/TRAC/VSC system and it requires an ABS Capable Scantool to pull accurate codes from, this is NOT an engine or emission related issue. Most Autoparts stores should have a capable scantool to get codes, but you may have to go to an independent shop and/or the dealer. An example of a failure of this type would be a speed sensor or failure in ABS wiring, ect. (Note that in 2003~2004 4th Gen 4Runners, low battery voltage and/or clearing DTCs can sometimes undo the ZPC (Zero Point Calibration) value stored in the ABS Module, this will result in the TRAC & VSC warning lamps turning back on despite having "fixed" your MIL condition.)

MIL is Blinking- This means there is a catalyst damaging misfire occurring (this is an OBDII mandated requirement and is present on all OBDII vehicles), you need to stop the vehicle and turn it off; failure to do so can result in permanent damage to your catalyst(s).

MIL On, TRAC On, and VSC ON- An OBDII failure has occurred in the vehicle that affects Engine Performance and/or Emission Control Systems and does not need a factory-capable scantool to pull codes (this means you can use a code reader from an autoparts store and get accurate codes) An example of this type of failure would be a Misfire, transmission issue, EVAP issue, ect.

Now I want to go into detail a little on the above mentioned OBDII failure because MANY people on almost EVERY forum there is incorrectly associate the MIL with a "Loose Gas Cap" and it gets repeated over and over and over again like some sort of magical "get out of jail" card...

An MIL on condition means there is an OBDII Failure Present in your vehicle that affects Engine Performance and/or Emission Controls and a DTC has been stored in the PCM. A loose gas cap COULD be the cause of the issue, but it more often than not is not even close.

Helpful Hint- If you have a P0455 DTC and ONLY a P0455 DTC stored in your pcm, then the gas cap MIGHT be the issue. A P0455 indicates that the EVAP Control System has found a leak over .040" and could not pass its monitor. This means you can replace the gas cap and still have the same DTC set if the leak was not the gas cap but somewhere else. Please also note that it can take a couple drive cycles to reset the MIL (without using a scantool) if the issue was in fact a loose gas cap, this often means anywhere from a day to a week or more depending on driving habits.

Helpful Hint- TSB 0030-10 indicates a prematurely failing gas cap as the cause for DTCs P0441, P0455, and/or P0456. The easiest way to rule the gas cap (this isn't 100% accurate, but works the majority of the time) is to tighten the gas cap until it "clicks", the gently unscrew it. If the cap has no resistance and unscrews it requires replacement, if the cap takes some effort to unscrew it's most likely good.

If you do have an MIL On condition, I highly recommend you go to a local autoparts store and have them pull and write down the DTCs stored in the vehicle before you post on the forum. The first thing we need to help you out with an MIL On condition is what codes are stored in the PCM; no one can do anything for you until we know what we're dealing with. This will save you the trouble of waiting on us to tell you to get the codes pulled and will help you get accurate information in a timely manner rather than taking days to get to any real significant assistance or direction.

I will also mention that some people may have scantools that indicate "Current" and/or "History" DTCs, these mean that the DTC was set by an issue that is occurring right now (Current) or that the issue has occurred in the past and the vehicle recorded the DTC for later review (History.) Typically only Current DTCs will set a warning lamp and History DTCs will simply show up when you do a health check; its important to know this distinction as you could pull up a History DTC for a problem and end up wasting time and effort trying to diagnose an issue that is not even present. Another type of DTC category you may see is "Pending", a Pending DTC is part of the "Two-Trip Logic" that OBDII dictates and some other modules use as well. Two Trip Logic means that the problem has to occur twice before the vehicle will set a "Current" DTC and turn on the MIL, a "Pending" DTC means that it has only happened once and the vehicle will not set an MIL on condition until it trips a second time and the DTC matures to a Current DTC (for example a P0420 or P0430 "Current" DTC means that the ECM ran the catalytic converter tests at two different times and returned two failure results, where as a Pending P0420 and/or P0430 means that the ECM ran the test and got a failure once and is waiting to see if it happens again before it sets the MIL and matures it to a Current DTC). Some modules such as SRS and ABS/VSC/TRAC do not use Two Trip Logic and will instead set a warning lamp on the first sign of an issue, these systems are "Single Trip Logic".

But if it makes you feel better you're more than welcome to tighten the gas cap and wait a few days to a week to see if the lights go away if you want, we'll still be here anyways.

Post Note-

I realized I never explained why the VSC & TRAC systems are disabled when an MIL is turned on. The simple answer is because Toyota is conservative and decided that since 9/10 the MIL is turned on for an OBDII DTC (which, except for a small handful of EVAP related DTCs directly impacts engine performance) that it meant the engine is not working as designed and cannot be trusted to work correctly with the VSC & TRAC systems when demanded (VSC & TRAC modulate ABS and Engine Output to bring the vehicle under control at times.) So the easiest and conservative solution is that when an OBDII DTC is set (i.e. an MIL is turned on,) they disable the VSC & TRAC systems because half the system has an issue. A lot of manufacturers have started to do this in the last decade as these vehicles get more and more complicated.