Tesla’s P85D Will Get Even Faster Thanks to a Software Update
techcrunch.com
techcrunch.com
Yes, that is awesome.
But on the other hand, in the past I've had updates to my TiVo and my PS3 where I turned it on and it said "Oh! Hey. I'm shittier than I was yesterday. Suck it."
And someday, that could happen with Teslas, too. Updates are a mixed bag.
"This car is now property of pWnz0r. Pay 20btc to {address} to reclaim your car"
"This car will only fill up at TSA approved electric stations"
"This car will not turn on for anyone with a recent DUI"
"This car will not turn on during the Snow Emergency"
Some of these are probably not risks given the current capabilities of Tesla's, but future cars might have enough cameras and sensors to enforce such updates.
to them we'll be bad-asses who lived danger ever minute of every day on our terms. The way we make movies about the future they'll make movies about our time. And the few of us still remaining we'll make up all sorts of stories to make it sound like everyone alive was an action star. They will be repulsed by what they have become.
that or...
to them we'll be wreckless and inefficient neanderthals. They'll be just happy to have their governments. Like having this monolithic antivirus installed on society, to keep everyone 'safe'.
You can walk away from the treadmill.......and still have cash, security, and not die from a healthcare issue. Live below your means, save, invest, and then move somewhere nice but with a lower cost of living (Costa Rica, Panama, and Uruguay are my short list).
This will not happen if you live somewhere paying $3K/month for a studio though ;)
Just run faster that's the ticket.
You can also just get off. Lower your spending and you don't need to work a full time job 48 weeks a year.
ex: If you want to live in a cabin in the woods, the forst service pays some people to watch for fires in some really remote areas.
Does the current society view the people in the past as wreckless and inefficient neanderthals? On average, no. Sure, we view their lives as more dangerous, but we do not view them as wreckless or inefficient neanderthals.
Survivor bias is real.
When I was a kid there was no nerf-padded society (late 70's into the 80's). If you made a stupid move on a bike, you bled on the ground and thought it over for a while. From that you got a very real sense of the implications of your actions and relied on your wits more, as not doing so would get you really screwed up.
I think the awareness campaigns of the 80's, as well as generally "growing up", in addition to quite a few near-deadly accidents, have changed my (in hindsight, ridiculously stupid) viewpoint on helmets.
In the last 12 months two friends have broken helmets, but survived. If they weren't wearing them, who knows...
http://www.wsj.com/articles/drone-maker-to-disable-some-d-c-...
http://www.forbes.com/sites/kashmirhill/2014/09/25/starter-i...
This one's already happening.
The only think is, no OEM does this officially. It is only done by more or less shady third parties. Officially it is done eg. by Brabus for Mercedes, Alpine for BMW, …. But then not part of a retrofit but you have to buy the whole car from them. You can buy it as retrofit from some Russian or other alike.
It is also very common in the industry that the very same engine is used with different algorithms resulting in different PS. Like my Volvo S60 2001 Model uses an engine which was available with 140PS, 170PS and 210PS. The very same engine was used by Ford at that time in different Models with different PS.
For comparison, think about BIOS updates or camera firmware updates. Sure it would be kind of neat if these happened auto-magically. But would I see it as a big plus if my motherboard was able to fetch and install BIOS updates all by itself? Not really, I would in fact be concerned that it's fixing stuff that is not broken, and doing it behind my back.
Just look at the CVT Ford Fiesta / Ford Fusion. In the 2012 model of the cars, the transmission would "slip" under certain conditions. I know because my friend Pete owns one. He went to the dealership. The mechanic there drove it with him in the passenger seat. Sure enough, this was a problem. They call Ford and they adamantly denied there was a problem of any sort. Fast forward about eight months and the dealership calls Pete. Apparently, there's been a software update. Pete went to the dealership. The transmission slips no longer happen.
I guess the point I am making is that it really sucks when Ford denies there being a problem when there is clearly a problem. I am not saying the software was the problem but they had a fix for it in software. I don't think Ford even publicly announced this software update. For sure, I understand that you should be able to decide when and which updates happen to your device. However, I see a positive change if they come up with a good change list with each update. Someone above noted that until recently Toyota didn't even have a bug tracking system for its software.
As for throttling the engine to sell at a different price point: in many countries this relates to government taxation on horsepowers. I don't see this as particularly nefarious by the car manufacturers.
Edit: same for Mountune USA
"Traditional vendors" routinely update their cars to give better performance where it doesn't cost them anything and brings other benefits e.g. safety. Especially if the components are reused during multiple generations e.g. MY14/MY15.
I am buying a used LandRover now where I will get more than a 0.1s performance improvement when I take it into the dealership for a transmission software update.
Of course if you know that certain things are not going to be a problem(like you are not planning on driving to Russia or filling up at shady stations) then you can manually tweak the ECU for shorter timings or whatever, to get more performance out.
Also transmissions can only take so much power before they have to be upgraded too. It wouldn't make any sense to ship an economy car with a sports car transmission because you might juice up the power with an update later.
Not to mention only upgrading power is no fun at all if you don't upgrade the brakes and suspension. All the power in the world does nothing if you can't put it down on the pavement or can't stop before hitting a wall.
Car manufacturers generally aim for their cars to be mostly identical regardless of the country they are sold. Hence they are often targeting lowest common denominator country emissions levels.
And I've done ECU remaps before. You definitely do NOT need to upgrade brakes and suspension.
Example: http://www.bluesparkautomotive.com
(Which I think you acknowledge in your second paragraph, just seems worth it to be explicit about it)
And your issues about reliability/emissions aren't necessarily true (spend time on any car forum and you will see better rebuttals to these issues). It isn't necessarily true for reliability since engines are often reused between models/manufacturers and so safe mappings are known.
And yes you may exceed emissions regulations but not necessarily. Again manufacturers aim to sell the same car in multiple countries and so depending on how relaxed your country is your car may still be legal with increased emissions.
Think about this. If these devices were so bad why do most insurance companies when you tell them about it either (a) don't increase premiums or (b) do so with a negligible increase. It's because they are never the cause for safety or reliability issues. Car companies use engine power as a key product differentiator.
It doesn't matter what colour your car is, nor what colour you change it to, when you change the car colour your insurance premiums go up.
I suppose I'm assuming a correlation between speed and crash-rate, which may not be a thing. But given that premiums ∝ engine power, you'd have thought that there might be.
Dealerships have been doing this for YEARS.
There are many dealerships who sell ECU remaps/devices that significantly increase performance of the car. And the biggest joke is that some manufacturers e.g. Mercedes actually turn a blind eye to it in many situations.
It may help if you think of your car as just another server. Any connection between the server and client can be encrypted of course, using well-known tools. Besides that, the car can be made to not accept updates that are not signed by the manufacturer, so your only exposure is to the manufacturer.
Of course someone may have physical access to your car and be able to write new software locally, but then they may also be able to do mechanical sabotage, so it's not a new risk.
So you basically have to trade off one kind of security (the manufacturer can update my car remotely) with another (security bug announced in the software my car runs, I am now a sitting duck).
It definitely takes a shift in perspective, but in the brave new world where cars (and other things) run millions of lines of code, over-the-air updates are a necessity. (but of course I'd say that).
I've written a bit more about this conundrum here - https://resin.io/blog/you-cant-secure-what-you-cannot-update...
[1] https://www.usenix.org/system/files/conference/usenixsecurit...
Device has a per-device key burned in at the factory and the private keys sit in a manufacturer HSM. Updates are signed by the manufacturer and also encrypted with the per-device key for each device. The device itself will have tamper-proof (well, as tamper resistant as they can be) chips and a secure boot-loader that will do all the dirty work.
Nothing is ever 100% secure, but you shouldn't believe it is something similar to a piece of software on your computer where it is just "hit this https URL for the executable and run it". Or maybe you should believe that and force manufacturers to come out and state otherwise :)
I'm not saying your comment is ungrounded, I'm just saying that a process locking up or sending wrong information is not likely, or even possible, to net you 100% loss of use in your brakes.
Cars are the most highly regulated consumer product on earth. Brake systems nor Tesla fly under the radar here.
I felt that way too, til I watched few of the talks from the people that were doing the testing of Toyota electronics after all of the unintended acceleration problems.[1]
Did you realize, for example, that while there are coding standards that one should adhere to while doing embedded systems-critical stuff (like MISRA guidelines), there are no requirements for automotive companies to adhere to any such software standardization, and that it's left up to the individual manufacturers to decide upon standards?
The US automotive industry is unique in that it doesn't have a rigor requirement for software. Planes and heavy equipment do have such requirements within the states.
Toyota didn't even use bug tracking or source management, and used their own software guidelines. That's scary given the complexity is so high that the entire system cannot be fully tested in a feasible way.
Atop the software issues, the hardware ECM was made in such a way so as to make the secondary 'cross-checking' processor basically useless. Both CPUs were checking the same I/O, if that was the fault then BOTH would read bad data, and the hardware was made in such a way as to make that impossible to work around.
An old Camry isn't anywhere near as complex as a modern electric car, and I personally have more faith in Tesla than I do Toyota, but it makes me want to push US legislation into requiring US auto manufacturers into following the strict software guidelines that are available to them.
Fun trivia: MISRA guidelines were originally pushed by the automotive industry in the early 90s/late 80s, and now they are one of the only critical systems groups to not follow them.
[1]:http://users.ece.cmu.edu/~koopman/pubs/koopman14_toyota_ua_s...
As far as Toyota is concerned, right now I'd trust them as much, of not more, than Tesla. Tesla has been doing great things and doesn't have much, if any, of a bad track record for failures. However, you have to realize that Toyota has also been making cars far longer than Tesla, produce more, and has one of the best reliability ratings in the industry.
I believe Tesla can achieve this or better. However, it's hard to compare when Tesla doesn't have the numbers that Toyota has.
I have no idea how Tesla does this, but in most cases you're deal with deterministic software or real time OS's, massive testing suites, coding guidelines that guarantee positive outcomes, etc.
JPL published its guidelines. Do you think Google and Apple are this stringent with their mobile toys? Of course not. They have zero economic interest to do so. They just have to make things good enough that kids and housewives won't complain too much.
http://spinroot.com/gerard/pdf/P10.pdf
or more specific to autos
http://en.wikipedia.org/wiki/MISRA_C
Mistakes will always happen, but Apple or Google are not good examples of what well written software is.
Which is fine, but I'm unnerved hearing the people who seem to consider Tesla infallible. 'They'll never make a mistake like that, they're Tesla!'
Errors probably means errors here. As in yeah, most recently trying to land a booster on a barge and missing.
Mistakes happen. The wrong number in a configuration somewhere and everyone's car suddenly has a vampire that sucks down the battery 50% faster, or causes a misreading of wheel speed for anti-lock braking, or etc.
Once you trust you trust, and if you don't, you don't update. Not much space between (for me) ...
Imagine having such a software-powered car and being unable to get into it because it was stolen: https://translate.google.com/translate?sl=auto&tl=en&u=http%...
Imagine some company without Google's software engineering expertise building a self driving car, allowing hackers to take it over and create mayhem.
That's OK because the mobile access provider will know where it is - he always does, wherever you go...
Software mappings for engine performance are often modified by hobbyists, performance tuners, etc., it just normally takes plugging in a tool or swapping a control chip.
Can I block Tesla from delivering updates.
But with seriousness, it's a good question. I would be surprised if the purchase agreement for the car doesn't somewhere include a clause that you agree to allow the car to make updates.
In 2012 when the pushed the first big update, Wired indicated owners couldn't opt-out [1]. Looking at their legal website [2], I see that under Rights & Choices you can turn off the collection of Telemetric Data, which may disable periodic software and firmware updates.
But no, on a casual Googling, I don't see it outlined anywhere how they manage opting out of those updates.
[1] http://www.wired.com/2012/09/tesla-over-the-air/ [2] https://www.teslamotors.com/about/legal
In the case of the Tesla there is no emissions change but are there safety changes that need to be retested?
I was a bit confused initially as to how a mechanical problem can be solved by a software update, but then someone explained in one of the comments that it's about fuel-injection tables and stuff.
Incredible, but just a bit scary too.
I really hope they test that software to the hilt - I mean like NASA style, slow but steady kind of stuff. I wouldn't want to go 1 feet near the car if the quality is in the same quality vicinity as 99% other software (and that includes software that we generally consider "good quality").
Anyone knows what their software development process is to get that kind of confidence?
Another look at how to get "NASA like" confidence is provided by Richard Feynman[2] and Diane Vaughan[3].
[1] http://www.fastcompany.com/28121/they-write-right-stuff [2] http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/roger... [3] http://www.amazon.com/The-Challenger-Launch-Decision-Technol...
And the software development process is pretty standard waterfall. And yes they absolutely test that software to the hilt. Generally though the software is architecturally quite basic i.e. they don't do anything too fancy.
If it's NASA confidence, waterfall every time :)
Having worked in that sort of environment (everything about the system has been analysed on paper before a text editor is launched), don't knock it until you've tried it. This wasn't rocket science either, it was export refund batch jobs. In the 21st century.
Good point. Slamming full torque as fast as possible on a Tesla might physically break things and should only be pushed out as an update after appropriate testing. I'm assuming they were not even getting the highest possible torque out of it though. Electric motors are a fairly interesting problem and most of the work goes into dealing with limiting cases. Most of the literature doesn't even deal with some of the fundamental problems and most people just avoid them by leaving a little performance on the table.
You can see why a gearbox is a disadvantage in this video here:
http://youtu.be/0e-jquwHKtI?t=30s
During the first 2 gear changes you can see the lambo fall behind during gear changes.
http://www.teslamotors.com/blog/engineering-update-powertrai...
Some earlier electric cars had multi-speed gearboxes, but that was back when electric cars had brush-type DC motors. Once high-power semiconductors got really good, electric cars went to polyphase AC motors with variable-frequency drive. That technology is now in everything from better R/C drones to electric locomotives. AC motors can be made to synchronize, which allows the Tesla 2-motor car to have all-wheel drive with no front/back differential. One motor per wheel is probably next.
The big win for this technology turns out to be Diesel-electric locomotives. All the wheels on all the locomotives can be synched up, eliminating wheel slip. The locomotives can even be distributed through the train. Here's a 3.5 mile long train run as a test by Union Pacific in 2010. https://www.youtube.com/watch?v=jdIzRFOaTCY There have been longer trains, but mostly in flat areas. This was from LA to Texas at speeds to 70mph.
And saying a Tesla would have no benefit of a gearbox is a bit strong. There are reasons to believe [1] it would increase efficiency at the cost of more complexity.
[1] http://www.gizmag.com/new-multi-speed-electric-vehicle-trans...