4 Cylinder Turbo Automatic Air Condition Leather Power Roof Loaded 1 Owner on 2040-cars

Auto blog

2018 Chrysler Pacifica Hybrid Long-Term Update | Recall!

Our long-term 2018 Chrysler Pacifica Hybrid has been in the fleet for about six months now and is quickly accumulating more miles than most of our long-term vehicles do in a full year. Thanks to a couple of recent road trips, one to New England and one to Florida, our Ocean Blue Metallic minivan has racked up about 15,000 miles. I personally hope we can cross the 25,000-mile mark before we're finished. The Pacifica Hybrid has garnered near universal praise from the Autoblog staff, especially those of us who have kids or pets. While it's mostly been hiccup free, one recall had us a bit on edge. NHTSA campaign number 18V740000 was issued last fall, but we didn't get the notification until early this year. Blame the delay on the weird ownership situation of long-term vehicles. NHTSA's basic description is short. "After the vehicle has been operating in PHEV propulsion mode, the gas-fueled engine may not restart properly resulting in unburned fuel entering the exhaust catalyst." Basically, the engine may not restart correctly after running in EV mode, and the fuel being fed to the engine could make its way past the exhaust manifold to the catalytic converters and ignite, possibly starting a fire. Obviously, that's bad. We scheduled a visit to the dealer as soon as we got the news. Chrysler's fix is to update the computer, visually inspect the cats and replace them if needed. We hadn't noticed any issues with the Pacifica's powertrain, and the inspection came back clean, so our Pacifica was back in our hands in a few hours. The service sheet says the left and right cats were inspected by borescope and the powertrain control module was updated. All in, the Pacifica was out of our hands for about half a day. Related Video:

NHTSA releases updated Takata airbag recalled cars list, but it still has errors

Unfortunately, the government's list still contains errors.
The National Highway Traffic Safety Administration has issued an updated list of vehicle models that it's urging owners to repair under the mushrooming Takata airbag inflator recall. The latest version adds vehicles from new automakers like Subaru and Ford that are missing from the original announcement, and it also removes erroneous entries from General Motors, leaving only the 2005 Saab 9-2X (a reskinned Subaru WRX), and the 2003-2005 Pontiac Vibe, a joint project with Toyota.

Supplier says Jeep Cherokee hack only affects FCA cars

Harman doesn't think that drivers need to worry about any further hacks of its products. The company supplies FCA's Uconnect infotainment system where a software vulnerability is responsible for a 1.4-million vehicle recall. "This experimental hack is unique to Chrysler," Harman CEO Dinesh Paliwal said to Automotive News. "This does not exist, to our assessment, in any other vehicle." The reason that the company wouldn't be involved is that automakers aren't simply plugging in the existing infotainment systems into new vehicles. According to Paliwal, Harman supplies the unit, but FCA and other automakers are able to make additional modifications for their vehicles. The National Highway Traffic Safety Administration has also recently taken up the question of broader software vulnerabilities in Harman's products. On July 29, the agency began investigating the company to check for similarities between Uconnect and the infotainment systems supplied to other automakers. The Jeep hack became national news when two researchers were remotely able to take control of a Cherokee. The vulnerability in the cellular connection even gave control over the brakes. "Once people get in the car and get into the CAN bus, then you can start to mimic and mess up many, many things in the car," Paliwal said to Automotive News. Politicians immediately responded with legislation to create federal standards in hopes of protecting drivers better. NHTSA also opened an investigation to make sure the automaker's software update actually solved the problem. Related Video: