Software Is Eating the Auto Industry (strategyanalytics.com)
Roger Lanctot, writing for research firm Strategy Analytics: There are many more opportunities in cars today for things to go wrong as software takes over an ever-expanding array of functionality from the car stereo to enhanced safety systems and the vehicle powertrain. There are software bugs, updates, conflicts and, lately, cybersecurity vulnerabilities to worry about so it is perhaps no surprise that software is figuring in vehicle recalls. In the latest update of software-based recalls from CX3 Marketing, software-based recalls crept up higher again in 2016, surpassing 6M vehicles. It's a small portion of the overall total but it is growing -- especially as a proportion of the total. This expanding crisis in vehicle recalls is both good news and bad news for the automotive industry. The good news is that software recalls can often be corrected with over-the-air software updates. The bad news is that auto makers are in the very earliest stages of deploying software updating technology and, particularly in the U.S., they have yet to sort out conflicts with state-level dealer franchise laws that require warranty service work such as software updates be handled by dealers. The expanding role of software and the growing number of software-related recalls reflects an emerging battleground in the industry. The creation of software is expensive and labor intensive and also poses an ownership question. Starting approximately 10 years ago with BMW and Intel's mutual effort to bring Linux into cars on a larger scale via the GenIVI Alliance, auto makers have been seeking to segregated hardware from software in such a manner that hardware could conceivably be relegated to sourcing from contract manufacturers (like Flextronics) and software development costs could be reduced by sharing code. At the same time, car makers have sought to take ownership of the code written for their vehicles. Car enthusiasts have taken issue with the ownership question, asserting their right to modify vehicle software as they see fit. That particular struggle is yet to be resolved but has gained new life as more tinkerers experiment with home-grown self-driving car technology.
Soon. It's time. Nobody needs obnoxious vendors who didn't even read their own fucking prospectus.
What we need is some showrooms and then we buy directly at the manufacturer's site online.
After all that's what the dealers are doing, besides those brands who have thousands of unsold cars laying around they the have to pay customers thousands to take off their hands.
... not stuffing cars to the gills with software, but, you know, let the fscking things be cars?
That'd be too simple, eh.
The other major issue is that manufacturers insist on tying safety and security updates to functionality changes.
For example, on my Tesla it was determined that if you connect your car to a rogue wifi AP and open the web browser an attacker can gain root access on the car. To solve that issue though I'd have to agree to Tesla nerfing autopilot and making the whole UI exponentially worse. I've chosen instead not to connect the car to random access points or use the web browser on unknown sites.
On an old fashioned car if there was a problem with the stereo, they'd never change the functionality of your cruise control and move all the interior switches around to solve it.
FAA regulates what kind of software can run on airplanes and it isn't a stretch to imagine deaths occurring due to poorly written software in cars. Of course car manufactures will make the consumers sign a document limiting liability as prerequisite to purchase.
Nope. No OTA updates for me. I don't trust companies to have access to my car (or computer, for that matter) any time they want. If I can't disable the communications channel, I'm not buying the car.
Yesterday it was JavaScripting eating the Internet, today it's software eating the auto industry. That's just the software. The hardware must be starving.
They probably don't realize that that manufacturing has been running on software since the 60's and when they do we'll get the FUD headline of "ZOMG!!! Software is eating the manufacturing industry!!!!!"
And then it will be "ZOMG!!! Software is eating the shipping industry!!!"
Followed by "ZOMG!!! Software is eating the mining industry!!!"
And then "ZOMG!!! Software is eating the power generation industry!!!"
etc. etc. etc.
I am Slashdot. Are you Slashdot as well?
Oh, I see, a new buzzword "eating". Javascript is eating the world. Software is eating the auto industry. Who is eaten by what next?
software updates be handled by dealers is way a way to make big profit. and stopping updates after 2-3 years can make for new car sales.
Just think of an $50-$100 labor change for that or even mark up parts like an HDD X2-X3 bestbuy rental prices.
... nearly any and every industry. Look what happened to Samsung. Or those people with the "security" cameras that phoned home, or pacemakers, or... or... or...
the VW Diesel-Cheat issue is why something FAA like is needed. Even more so with auto drive cars.
limiting liability will not stop an 3rd party victim from suing or getting out of an criminal case (say an very bad crash that kills a lot of people)
I do NOT want the ability to do any "hands off" update of a killer robot, er, I mean automobile.
If the good guys can do it, so can the bad guys.
Make me come in for service or send someone out to me, just as you would for faulty hardware.
Now, if you need to update a non-critical system such as the infotainment or air conditioning system that's fine, as long as there is no way for those systems to make changes to the critical systems. Yes, I know this isn't risk-free - a bad guy could make the radio go on full blast and distract the driver, causing a wreck, but at least that's "hacking the human" not "turning your car into a killer robot."
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
Look up ISO 26262 & ASPICE and other things related to 'functional safety'.
Not everything in the vehicle is, or needs to be, compliant but your powertrain and anything with life and safety is. This isn't fly by the night programmers coding a Radio GUI.
This stuff goes all the way down to the hardware level. With dual core CPUs running in lock step, dual memory banks and ECC memory. If there's a mismatch anywhere along the line an error is thrown.
http://www.nxp.com/products/pr...
https://www.renesas.com/en-us/...
The car I bought has a built-in touch-screen Android system as part of the entertainment system. It runs the audio, trip computer, phone address book, the (optional) navigation system, and even has an interface with the air conditioning. It's basically a built-in Android tablet with car-specific software installed that interfaces with the rest of the car. I thought "Wouldn't it be wonderful if I could install any Android program I want?" Nope. It's locked down with a whitelist program in the background that will not allow installation of anything but the vendor-approved programs, the files that control the whitelist are read-only, and developer mode is locked down with a passcode so you can't even connect to it (wireless or through usb). Part of me thinks "Oh well. I guess that means it will be harder for a black hat to hack. Good." As a design decision to prevent people from doing things that could mess with the car in undesired ways (e.g., circumventing regulations preventing use of some types of software while the car is moving, and worse), I can understand it, but on the other hand there are inevitably going to be vulnerabilities.
Within 6 months of buying it, it was no mere hypothetical. The Android version is old: 4.2.2 (first released 2013). Plenty of known vulnerabilities. People eventually found the hidden menu and code to break into developer mode, connect via USB using adb, and used the Dirtycow Android exploit to root the system via a setuid root program that was already installed. Then came modifying the whitelist to support whatever Android program you wanted.
It's a mixed result. On the negative side, someone with access to the car interior could definitely hack into this thing no problem and embed any software they wanted, or damage it in nasty ways. Thankfully, only physical access can enable the necessary debug mode to get started unless you are foolish enough to leave it turned on (i.e. wireless debug is locked down by default to OFF, thank god). On the plus side, thanks to the flaws I now have (free, open-source!) navigation software installed in my car that would have cost more than $1000 from the dealer because it only came with other car options I didn't want, and the software has better maps than the vendor's software anyway. Without the flaws, the lock-down attempt by the vendor would have worked.
I think many car manufacturers are facing a steep learning curve with this stuff. You've got the inertia and legitimate safety concerns of gigantic car companies in conflict with the natural desire of tech-savvy people to use the system to its full potential, all while keeping it secure, up-to-date, and cheap (hardware + software). Good luck with that!
I don't need 'infotainment' systems, 'bluetooth' everything, 'self driving', or any of that. 5-speed stickshift, AM/FM radio, air conditioning, cruise control, optionally electric windows and doorlocks, and of course a comfy bench seat that I can nap on when necessary. The rest of it is overpriced crap to break that you don't need.
If electric instead of ICE, then you can skip the 5-speed, won't need it anyway.
#SimpleCarsPlease
over the air updates of your anti lock break control system.
Over the air update of auto software is only slightly less stupid then over the air updated of avionics software.
Or if you prefer, fast and cheap software updates supporting cool new software for vehicles are much more important something as small and insignificant as human life.
âoeTolerance applies only to persons, but never to truth. Intolerance applies only to truth, but never to persons.
Donnie is that you?
Apart from being stupid, they seem to be nonsense as well...
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
I travel for work, and rent a lot of brand-spanking-new cars.
Car software is shit. It doesn't matter what brand of car, it's shit.
I get in the car, factory reset the radio, reboot the car, connect Bluetooth, sync contacts, and go. Most recently I did this in a Buick Endeavor. Enabling Android Auto locked up the car entertainment system and I had to reboot the car. Apple car play worked, but bluetooth phone calls only worked 25% of the time when the phone rang while Pandora was open.
That's not an isolated incident. I've locked up the infotainment system on a dozen other rentals. That's extremely frustrating. The best was a Ford Focus that wouldn't reset with a power-off/power-on reset. The system didn't recover until I left it off for an hour.
It's not just new cars, either. I own a Chevy Equinox that won't Bluetooth pair with an iPhone 6. At least it doesn't lock up.
Not surprising at all. They keep using unsafe languages like C, C++ or Java instead of time-tested safe ones for critical environments (ADA). They don't use EAL 5 (or higher) assurance levels, like avionics does, but stay with "it works, see?".
I was hoping that car software would start a revolution in computer programming, at long last fostering a new generation of languages and best coding practices: I was hoping we would move to the "this class of bugs cannot exist" kind of bug-free, instead of "hey, we can't see any bug from here" that software houses gives us today. Me deluded.
But maybe the recall catastrophe will force automakers to take software development more seriously. Maybe there is still hope...
In 1985 I was in grad school in a software engineering course. Coming from the hardware engineering side, I was looking at embedded system design and wrote a paper on the need for incorporating proof-of-correctness processes into software design where human safety is concerned. For example, making sure that software-controlled microwave cannot transmit when the door is open must be very well designed, and probably should always have a power safety interlock associated with the door latch. Likewise, automotive design needs careful attention to insure brakes, acceleration, steering, and other functions are controlled correctly. It saddens me that computers have come so far in the intervening 4 decades, but software accuracy really hasn't. I've interviewed young people coming right out of school that don't even really understand proof-of-correctness in software design, let alone recall having heard the term. And when my company hired H-1B workers, they barely had any real training at all.
And nearly everywhere software is in a car, it is actually NOT NEEDED, making things more fragile and less durable, plus introducing a slew of other problems
of auto industry being eaten by software: you can't repair your own car, or you violate the DMCA. Farmers Demand Right To Fix Their Own Dang Tractors Why American Farmers Are Hacking Their Tractors With Ukrainian Firmware