Throw out all those black boxes and say hello to the software-defined car
Instead of dozens or hundreds of modules, a car will use four or five computers.
One of the auto industry trends I’m most excited about these days is the move to clean-sheet designs for car platforms and architectures. For decades, features have accumulated like cruft in new vehicles: a box here to control the antilock brakes, a module there to run the cruise control radar, and so on. Now engineers and designers are rationalizing the way they go about building new models, taking advantage of much more powerful hardware to consolidate all those discrete functions into a small number of domain controllers.
The behavior of new cars is increasingly defined by software, too. This is merely the progression of a trend that began at the end of the 1970s with the introduction of the first electronic engine control units; today, code controls a car’s engine and transmission (or its electric motors and battery pack), the steering, brakes, suspension, interior and exterior lighting, and more, depending on how new (and how expensive) it is. And those systems are being leveraged for convenience or safety features like adaptive cruise control, lane keeping, remote parking, and so on.
Of course, this only works if that software is any good. “There is absolutely no question that software has been treated like a stepchild—I always say the fifth wheel in the car. So like a necessity, but not something that has been managed with care,” said Maria Anhalt, CEO of the automotive supplier Elektrobit, which develops digital systems and software for OEMs.
Read 19 remaining paragraphs | Comments