Lexus Chameleon Show Car Widebody Jdm Sc300 Lexussc300 Vertex Ridge on 2040-cars

Auto blog

Toyota recalling 20k 2014 and 2015 cars and CUVs with 3.5L engines

Toyota has announced a recall of roughly 20,000 vehicles covering the 2014 Avalon, Camry, Highlander (pictured) and Sienna, as well as the 2015 Lexus RX luxury crossover. The affected vehicles are all powered the 2GR-FE engine, which in layman's terms, is Toyota's well-regarded 3.5-liter V6.
According to Toyota's statement, a parts supplier might not have welded "the end cap on the right-hand fuel delivery pipe in the engine compartment" correctly, meaning fuel could leak. Leaking fuel, of course, increases the chance of an engine fire. That said, no fires, crashes or injuries have been reported due to the issue.
Owners will be notified to report to dealers, where techs will check the fuel delivery pipe and fit a replacement part as necessary.

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.

Bosch builds an infotainment system that just might not suck

As far as we've come with in-car infotainment and interfaces over the past decade or so, we still have a long way to go — as most current systems show. Whether it's high-end brands like Mercedes-Benz with its kludgy COMAND system, which we hope will be replaced with the MBUX platform revealed at CES, or more mainstream vehicles like Hondas (with their frustrating, knobless Display Audio interface), getting the kind of content and ease of use in the car that we're used to having on other connected devices is far too complex and sometimes costly. While Apple and Google have tried to ride to the rescue with CarPlay and Android Auto, respectively, they're limited solutions. No automaker or tech supplier has been able to deliver an easy, economical, flexible and non-distracting infotainment solution. But Bosch could be closing in on this elusive goal, given the digital cockpit concept demo I recently received at CES. Displayed in a Cadillac Escalade, the concept featured five interconnected color screens: one in the instrument cluster, two in the center console, and two more in the front-seat headrest for second-row passengers. The digital cockpit concept demo had cool features such as haptic-feedback touch-screen controls that created an edge-like feeling similar to a physical button, facial recognition to confirm driver credentials, and the intelligence to know the location of a phone in the car to lock it out to keep the driver from texting. The most significant aspect of the Bosch digital cockpit concept wasn't visible — but shows the company's vision for a future of seamless, convenient, cost-effective and safe in-car infotainment. It's powered by a single electronic control unit (ECU) that can simultaneously run multiple operating systems and also separates vehicle and infotainment controls for critical safety and cybersecurity reasons. Most modern cars can have as many as 100 separate ECUs, Philip Ventimiglia, product manager for Bosch Car Multimedia North America, explained at CES, and several just for infotainment functions. "The goal is to reduce that to about 10 so that we can save cost throughout the vehicle and enable new technologies," he added. "OEMs want to put more technology into cars, but it costs money," Ventimiglia said.