1996 Lexus Ls 400 on 2040-cars

Auto blog

Toyota recalls pre-collision system on Avalon and ES models

Toyota is recalling 31,000 US examples of the 2013-2015 Avalon, Avalon Hybrid, Lexus ES350, and ES 300h because the Pre-Collision System could potentially cause an accident. According to the company, it's possible for the safety aid to misidentify a steel joint or plate in the road as a hazard and apply the brakes. The sudden, unexpected activation could lead to a crash. Toyota spokesperson Cindy Knight told Autoblog that the company has reports of two accidents in the US related to this issue, and there are also two alleged injuries. The company has no reports of fatalities. Toyota is taking a serious approach to deal with this problem. First, the company plans to disable the system on these sedans. Once the parts are available, dealers will replace the system with improved components. The company doesn't yet know when these repairs will begin, but owners should receive notification of the recall in November, according to Knight. Toyota isn't alone in needing to tweak safety equipment. Ford faced a similar issue when the company recalled 36,857 examples of the 2015 F-150 because passing a large, reflective semi could inadvertently activate the collision warning system. An update for the adaptive cruise control module software fixed the problem. TOYOTA RECALLS CERTAIN AVALON AND LEXUS ES VEHICLES TORRANCE, Calif., November 3, 2015 – Toyota Motor Sales, USA, Inc. today announced that it is conducting a safety recall of approximately 31,000 Model Year 2013-2015 Avalon, Avalon Hybrid, Lexus ES350 and ES300h sedans. In the involved vehicles, under certain situations, the PCS (Pre-Collision System) could interpret a steel joint or plate in the roadway as an object that triggers PCS activation. If this occurs, the PCS warning buzzer sounds and the system may apply the service brake automatically. Unexpected braking could increase the risk of a crash. For all involved vehicles, the PCS function will be disabled as an interim remedy. As the permanent remedy, Toyota dealers will replace PCS components with improved ones. Information about automotive recalls, including but not limited to the list of involved vehicles, is subject to change over time. For the most up-to-date Safety Recall information on Toyota, Lexus or Scion vehicles, customers should check their vehicle's status by visiting toyota.com/recall and entering the Vehicle Identification Number (VIN). Safety Recall inquiry by individual VIN is also available at the NHTSA site: safercar.gov/vin.

Lexus builds final LFA supercar

Lexus has officially built the very last LFA. The 500th Lexus supercar rolled from the company's Motomachi facility on December 14th wearing all of the goodies of the Nürburgring package and white paint. Toyota's Lexus division started production on the car exactly two years ago on December 15, 2010 and built just one unit per working day. A total of 170 workers were hand-picked to handle parts manufacturing, assembly and painting for the LFA project. While Lexus has made it clear it will produce no more LFA models, lessons gleaned from the vehicle's construction may translate into other future products.
Specifically, Toyota says it may employ its carbon fiber reinforced plastic experience moving forward. As you may recall, the LFA made extensive use of CFRP and carbon fiber, and Lexus even created a special rotary loom to stitch together the supercar's A-pillars. Take a look at the brief press release on the last LFA below.

Google shares more details on self-driving car accidents

Google has pledged to release monthly reports on the status of its self-driving car program, and says these updates will include information on accidents involving the vehicles. But the company won't release the actual accident reports, a sore point for activists who recently have clamored for the company to be more transparent in the way it tests this promising technology on public roads. "Google is dribbling out bits of information in the hope to silence legitimate calls for full transparency," said John Simpson, privacy director for Consumer Watchdog, a nonprofit that has asked Google to release reports from the 12 accidents the company says it has been involved in over the past six years. "They are testing on public roads, and the public has a right to know exactly what happened when something goes wrong." Under California law, the accident reports are not considered public records. Google has attributed all accidents to human error, and says drivers of the other cars involved caused 11 of the 12 accidents. In eight of those, the Google cars were rear-ended, and the autonomous vehicles were sideswiped in two other crashes. One of the accidents occurred at an intersection when a human driver failed to yield at a stop sign, and in one incident, a Google driver accidentally rear-ended another car while manually driving. Google had previously provided those details. The first monthly report installment sheds new light on which types of self-driving vehicles were involved, directions of travel, locations, and whether the cars were operating in autonomous or manual mode. Update: Google says this information comes directly from the OL 316 forms used to report accidents involving autonomous cars in California, though it has "edited the summaries lightly to protect other drivers' information." But Google still will not release the original OL 316 forms, nor the "traffic collision report" forms used in California to report accidents. Another company that has been involved in a single self-driving car accident, Delphi Automotive, has released this information, which verified its car was not at fault. Regarding Google, Simpson said, "We now know a few more details of what happened. The problem is that it's Google's version and they want us to take their word for it." The Google self-report adds information that goes beyond accidents, with further details on the company's overall program.