| Issue ID | 757184 |
| Internal NHTSA # | 10302030 |
| Manufacurer | TOYOTA MOTOR CORPORATION |
| Brand | TOYOTA |
| Model | HIGHLANDER HEV |
| Model Year | 2006 |
| File date | 10/01/10 |
| Component | TRACTION CONTROL SYSTEM |
| Product type code | VEHICLE |
| Description of the problem | This input will show the commonality between complaints #10139802, 10194711, 10256617, 10259470, 10280157, & 10289084 which are for multiple toyota/lexus models. All these complaints say same thing in different words. Problem is a vsc alarm which sets off indicators for skid, abs, and other systems with the ecu computer causing an audible alarm and message to check vsc system. Alarm seems to partially disable braking system. Brakes become mushy and i believe front brakes are disabled. I know rear brakes still operate mechanically, and because abs is disabled, rear brakes can lock up and skid if brake pedal is pushed hard enough. Standard response from toyota/lexus is to replace ecu computer. However, as you can see from above complaints, this does not always solve the problem. My own complaint is for my 2006 toyota highlander hybrid 4wd-i with approximately 54,000 miles. I experienced a one time vsc alarm over 1 year ago when the engine start battery was dying. Toyota dealer told me to replace battery and see if problem continued. I replaced battery and also had all four tires rotated. Immediately after i started experiencing more vsc alarms at a higher rate. This has occurred while driving on highway as well as at low speed. It has also occurred both with and without applying the brake. 2 different toyota dealers have attempted to "adjust" system to stop alarms without success. I have gone as long as 4 months without an alarm and then for no reason (no skid event) alarm recurs. Solution both dealers have now given is to replace ecu. Due to finances, i can not afford new computer, so i had a toyota mechanic with 25 years experience install two different used computers with neither one solving problem. After examining the internet and your complaint board i now realize that this problem occurs across toyota's product line and that there is no clear solution. I believe toyota is aware of the problem and is not acknowledging that they have an ecu computer problem. |
| Vehicle Mileage at Failure | 54000 |
| Number of Occurences | 1 |
| Source of the issue | NHTSA WEB SITE |
| City and State | SAN CLEMENTE, CA |
| VIN pattern | JTEEW21A660XXXXXX |
| Was vehicle invloved in a crash? | N |
| Was vehicle involved in a fire? | N |
| Was incedent reported to police? | N |
| Was medical attention required? | |
| Was part original equipment? | |
| No. of injured persons | |
| No. of fatalities | |
| Date of purchase | 07/08/26 |
| Was original owner? | N |
| Anti-lock brakes | N |
| Cruise control | N |
| Number of cylinders | |
| Drive train type | |
| Transmission type | |
| Vehicle speed | 65 |
| DoT tire identifier | |
| Tire size | |
| Location of tire code | |
| Type of tire failure code | |
| Was defective tire repaired? | |
| Date of manufacture | |
| Type of child seat code | |
| Type of restraint | |
| Dealer's name | |
| Dealer's telephone number | |
| Dealer's city | |
| Dealer's state code | |
| Dealer's ZIP code |