NASA Summoned To Fix Prius Problems
coondoggie writes "If you want to solve a major engineering mystery, why not bring in some of the world's best engineers? The US Department of Transportation's National Highway Traffic Safety Administration today said it was doing just that by bringing in NASA engineers with expertise in areas such as computer controlled electronic systems, electromagnetic interference, and software integrity to help tackle the issue of unintended vehicle acceleration in Toyotas. The NHTSA review of the electronic throttle control systems in Toyotas is to be completed by late summer." We're really in trouble when NASA has no choice but to call Bruce Willis.
How many engineers does it take to fix a Toyota?
I guess today's NASA is a good call...
"Waste not one watt!" - CZ
So, this is an admission that sticking pedals and faulty floormats had nothing to do with the problem, and that the recalls to fix pedal and floormat "problems" were simply a smokescreen to hide the actual cause of the problem (albeit, unknown cause)?
Driving a car is rocket science.
Working as a developer at a tiny shop just out of college. Any time the CEO had troubles figuring out how to access a website I would be summoned to "just fix it" for him.
I'm a good cook. I'm a fantastic eater. - Steven Brust
The movie Herbie was prophetic.
Don't forget to tell them the Japanese use the metric system please.
Considering the government now has a vested interest and billions of dollars invested in the success of GM and Chrysler, who's to say the NASA evaluators won't be influence in relation to their final report?
Didn't Chrysler have a similar problem several years ago that ended up being user error? For some reason, I don't remember Congress and NASA deciding they needed to weigh in on that.
Wait, so when a private corporation fubars something, you gotta roll in the government funded engineers to fix it? Interesting, interesting...
Ubi solitudinem faciunt, pacem appellant.
Bruce Willis? They'd better call Chuck Norris to fix the pedals with a roundhouse kick or I'm selling my Toyota!
If the problems with the shuttles were related to floor mats then perhaps NASA could help. Otherwise, it's just another set of computer scientists looking over a few million lines of code they didn't write, trying to find a defect that has supposedly manifest itself less than a few hundred times out of million of cars and probably billions of miles driven.
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
The budget cuts at NASA apparently keep them earthbound and working on earth crawlers
It must suck to be a NASA engineer nowadays. You used to work on systems to send men to the moon. Now you're wiping grease off of oil-soaked brake disks and sticking your probes into 12v automotive stuff to find some crappy car problem that other people are too stupid to figure out.
and when it is all said & done, they will conclude people are hitting the GAS instead of the BRAKE.
First, the government kills 13,000 NASA jobs and destroys any hope for future progress with the American space program.
Then, the government relagates NASA's duties to exclusively focusing on global warming.
Now, the government further belittles NASA by making them fix a non-american-company's private affairs.
I can haz NASA engineers to re-roof my house?
this *IS* one of those problems that requires a rocket scientist to figure out. I never thought I'd see the day. My life is now complete.
I think this is a stunt on 2 levels:
1. Public relations need to be fixed somehow, so calling in NASA shows that the company is 'dead serious' about fixing this problem and they are going for the best people to do it, right?
2. A small token of appreciation to the government of USA by hiring NASA people, creating some employment, probably this is done with an involvement of a senator or two, some governor maybe, whatever, some politicians will get involved and this is probably important for Toyota now.
3. Something else, again not really related to the actual car problem, but trying to save the company's ass.
You can't handle the truth.
rocket science...
What is truly ironic here is that NASA regularly summons external panels to fix their problems.
Slashdot's first reaction to VMware
With electric vehicles (Mars and Lunar Rover)
I've heard a lot of rumors in recent years about poor technical abilities at NASA. I wonder if this is primarily meant to give NASA some street cred.
I swear I heard Steve Wozniak say in an interview abut his book a while back that he knew of this problem and could reproduce it in his own prius? I can't find the video on it anymore, but would any of you now of it or where to find it?
How is it that NPR had the last two stories (NASA & Prius as well as the Magnet influencing morality) on LAST NIGHT'S broadcast, and they're *just now* showing up here? Slashdot has lost its way.
My Sig Sucks
This is Slashdot and we suggest the most insane stuff be Open Source (e.g. "Why isn't my Microwave under GPL?"). But yet when we have an absolutely perfect opportunity to suggest that cars should be REQUIRED to be Open Source for public safety we drop the ball. Come on guys, we can use the power of Open Source and "many eyes" to literally save lives. You could be the geek that finds that piece of code!
Yes. Toyota decided the least convoluted way of admitting to software issues...
What makes you think these "corner events" are software related? With the scale and precision of the chips today, who knows. Electromagnetic interference? Sun spots? Something as simple as a 0 turning into a 1...
If you want news from today, you have to come back tomorrow.
Bruce Willis? The bigger issue is that they'll have to break Steven Tyler out of rehab.
"The total cost of the two studies is expected to come to approximately $3 million, including the cost of purchasing cars that have allegedly experienced unintended acceleration to be studied." I guess they don't have to bother looking at the Car Fax. What does "unintended acceleration" do to the KBB value?
"I'm not a quack, I'm a mad scientist! There's a difference." - Dr. Cockroach
I guess today's NASA is a good call...
I don't know if I want NASA to fix my Toyota problem...NASA has a reputation for crashing and burning.
Toyota's engineers needed a challenger.
There's no -1 for "I don't get it."
I think this more appropriate for Keanu Reeves... Speed 3: Hybrid Control
> We're really in trouble when NASA has no choice but to call Bruce Willis.
Oooh... do we get to see him blow up a Prius? With him inside?
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
I'd really like to see how the computer in the car manages to consistently only enter this mysterious state when the driver is 60 or older (or maybe in the late 50s). Because normally, if you have a ton of examples of something failing, all of which involve people of an age famed for acquired inattentiveness or confusion, and which look just like many other reported and documented cases of elderly folks getting confused and hitting the gas pedal thinking it's the brakes, you'd not assume it was the computer.
My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
So does Toyota, maybe it'll cancel out?
Mod me down, my New Earth Global Warmingist friends!
So none of Toyota's engineers could figure out what the problem is?
Toyota's reputation just took a nose dive.
Toyota: "Yo, I hear NASA ppl R smrt!"
US: "Ya they R clevr! lets get they're help!"
NASA Rocket Scientist - Xzhibit: "Yo dawg, we heard you like stopping, so we put retro rockets in your Prius, so you can stop while you accelerate!"
G.D. on a popsicle stick!
NASA can't fix stupid drivers.
There is nothing wrong with these cars. It is driver error.
NASA has a reputation for crashing and burning.
Does Toyota work in metric or imperial? Because we might all be screwed.
A billion dollars later and my Prius will be a Chevy pickup.
...Richard Feynman. Oh wait.
I think NASA wants a few dozen cars to test drive ... engineers like new cars to take home after the experiment too!
I believe NASA is the government agency that handles "incidents" in the aviation world. Incidents are wrong things that happened that do not rise to the level of accidents. The sudden acceleration reported in cars is very much the auto equivalent of what they have looked into for decades on the aviation side.
--
Perpenso Calc for iPhone and iPod touch, scientific and bill/tip calculator, fractions, complex numbers, RPN
They should have called Microsoft instead.
Hell yeah. Everbody knows putting the engine on TOP of the rocket works so well. They abandoned that when no one could get launch rights from China.
Dumass. You gonna complain that they also put lots and lots of burnable stuff under them too, right?
deleting the extra space after periods so i can stay relevant, yeah.
Since they aren't going to the moon any more.
As we move to electric cars and other advances cars will be more like a 80mph laptop.
We will need to have safe guards at all level. Another computer should have been watching the system and saying...what the hell are we accelerating for anyways.
Why the hell can cars run this fast anyways. Do we really need a car that will run over 90mph for more than a few seconds during a pass. Are we all so brainwashed by action movies we pretend we might need to run away from a maniac we probably couldn't outrun anyways.
Toyota will learn what went wrong with its software, and NASA will find out how to get a vehicle into space.
Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
Yes, I think people are idiots. lots of accidents are cause by poorly maintained floormats, doing your lipstick, texting, etc. This isn't the problem here. There are way too many incidents of various natures to be accounted for by this.
Yes, I think electromagnetic radiation exists. Yes, it can produce measurable effects. This, is also, not the problem here. EMF does not cause motors to turn with any appreciable torque. Modern electronics are sufficiently robust to this type of sporadic interference to account for this.
The problem here is in the code. I have written embedded software. It is WAAAY too easy to make a subtle mistake in an embedded environment that has limited processing power, highly asynchronous processing and a multitude of cooperating software and hardware modules. Further more, it can be a total bitch to debug these environments and the faults that they can exhibit can be nearly impossible to reproduce. And in EVERY case where I've seen "Hey, it shouldn't do that. The code doesn't have it doing that!" it turns that yes, it was doing exactly what the code had it do under those circumstances.
So, Want to save time and money? Ignore looking at anything other than code. Analyze the hell out of the software and you will find the culprit lurking there. You can put me on record for predicting this. (if they even 'fess up to the cause once found.)
I will never live for sake of another man, nor ask another man to live for mine.
Honestly, given the miles that Toyota has on land vs. the miles NASA has in space... Toyota might have the most 'accident free' record of the two. (Not including drivers who are just ignorant)
He never put the transmission in neutral.
IF there was an real problem, his lack of competence as a driver turned a mechanical/electronic glitch into an evolutionary failure.
Hasn't NASA's Mars Rover etc been subject to near fatal bugs? What good will bringing them on board really do?
Don't you see whats happening here?
The computer in the car is evolving "AI" !
I think therefor I accelerate.
IS commercial radio !
In one hour:
35 minutes of pundits talking drivel
15 mintues of band "news" about bands you've never heard about and will never want to hear.
10 minutes of "this segment" sponsored by Spork, Spark, and Spirk Law Firm.
Yours In Ulyanovsk,
Kilgore T.
If Jamie and Adam can't figure out what's going wrong, who can?
And if they can't figure it out, they'll pack the test Prius with C4 and hurl it into a quarry. Win-win.
Prisencolinensinainciusol. Ol Rait!
First, having worked in safety critical software systems (aviation) for a number of years, and Level A at that (the highest level the FAA requires), the thing that many of these posts fail to recognize that automotive software systems ARE getting incredibly complex. When these problems first arose, my gut reaction was that if we keep seeing issues like this, the NTSB was going to investigate imposing FAA like standards. In my opinion, that isn't a bad thing. But I don't think it will happen any time soon, as the cost per car will increase to account for all the extra software testing that must be done.
Second, just because a piece of software has complete code coverage does not mean that if an error is there, it is because of some "cosmic" effect. You also have to define what level of code coverage you are talking about. Statement coverage, decision coverage, modified condition/decision coverage, condition coverage? Even in the eyes of the FAA, this is a tricky area. You may have 100% MC/DC (the requirement for Level A software), but you can and will still have bugs. Anyone hear of bad requirements? That is one reason you have reviews for all areas, not just code (requirements, design, code, test, coverage, test results, etc).
Third, of course you should have an independent team look into the bug. Why so many people think that having a set of eyes look at code when they have never seen it before have never had to have independent verification. When you are dealing with structured software development for the FAA, the testers are never the ones who wrote the code. They (should) only know requirements and functionality. Design and code mean nothing at that stage. The tests are then written to robustly test those requirements, and then only done once you feel you have 100% requirement based testing complete, you look and see what your coverage is. If you have reached 100% coverage, then you can probably feel confident that your requirements were good and your tests were good. But even then, you still need to have reviews done (ideally by an independent team).
Lastly, just because this is "special" code, does not mean that there will be very few conditional branches in the code. Only with special code compilation tools can you create code that is linear. And as with avionics, automobiles are complex machines. They have many inputs to determine what should be done in a circumstance (right tire slipping, brakes applied, what should the engine do?). Therefore, not only will you have many conditional branches, but you will have complex conditional branches, which makes the software that much more difficult to test and debug.
In the end, just as with avionics, safety should be the number one concern. If it requires us as a society to say that software in cars that keep you safe (brakes, acceleration, engine control, etc) needs to be regulated, and that the NTSB will create FAA like standards (just like nuclear and railroads have done), so be it. If we didn't have FAA standards, the planes would be cheaper, tickets would probably be cheaper, etc...but do any of us really want that?
All the bolts I have dealt with on my Toyota are in metric...this can only end badly.
APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
NASA don't forget imperial vs metric in your analysis.
Where can I get that firmware update?!?! Does it work on '96 toyotas?
(You sir, are a genius!)
All the 'best engineers' left NASA after the Apollo program was canceled by the bean-counting Bozos of Congress.
Nothing's left but third-stringers and bureaucrats. Mostly the latter.
Regards;
Of Feynman's passing, Feynman's main contribution was to explain that engineers knew of the problem, but the management misunderstood the seriousness of the problem. In fact, Feynman speculated that he was fed the all of the information from a whistleblower via General Kutyna.
This may be the biggest issue for finding out what really happened. Someone really needs to seek out the disgruntled whistleblower inside of Toyota that knows what the real problem is and feels good about feeding it to someone with enough stature who can "discover" the problem. I doubt anyone at NASA-Langly has that level of independence that a Toyota whistle blower will trust them to not be political. And then you have the language problem and the fact that the most of the real NASA engineers are actually sub-contractors.
It would probably be better to send this problem to Argonne or Sandia, than NASA. But even if you chose NASA, it would have probably been better to pick NASA-IV&V (which specializes in mission critical software and was setup after the challenger disaster) instead of NASA-Langly (based in virgnina near all the pork barrel politicians in DC). This just smells of politics and that's why they may never get to the real answer (maybe they don't want to)...
The Japanese use the metric system. We don't want a repeat of that Mars Climate Orbiter fuck up...
One "Aw, Shit!" is worth 100 "Ata boys!"
Why the hell can cars run this fast anyways. Do we really need a car that will run over 90mph for more than a few seconds during a pass
Yes, we do. Here, you may if you wish take your car up to whatever it'll manage. The passing lane is commonly, 150mph+.
Funnily enough, accidents are no more common than on motorways of any other country, not only that, accidents are no more common on the unrestricted sections than the various restricted sections, and the lane discipline is a damned sight better. Why would you want to do 150mph? Well, your journey takes half the time going at 70mph, why don't you try 30mph or 15mph instead, why not walk.
[1] About 1/4 of the motorways are unrestricted.
Deleted
Speaking as an ex-engineer at GM's proving grounds:
Auto companies are basically systems integrators. It is almost always cheaper to outsource the parts design and spend your labor on making everything play nice. GM literally does not have an analog electronics department. Can't speak for Toyota, but they probably don't even have a guy on hand qualified to say whether EMI could be the culprit. Hence the NASA.
Reliable EMI failures are not new to the auto industry. There was a Cadillac that would shut off the engine if you drove under power lines at a certain speed. There was a rash of cars exploding at gas pumps because the gas tank WASN'T GROUNDED and static discharge igniting gas vapors.
Meanwhile, the code is a mess to look through and nobody knows the whole system. Almost none of the final code is actually written by hand. Everything is optimized automatically with autocode. This turns the code into unreadable spaghetti. If it passes the test bench, you call it good, and those test benches are definitely not exhaustive. I'll betcha nobody is waggling the windshield wiper voltage and seeing if it causes an acceleration upset.
IMHO, could be either.
Actually, they probably should be calling in old Bell Labs people who pioneered fault tolerant design. I, myself, worked on numerous EMI/ESD/Power idiosyncrasies that impacted complex switching systems. I even wrote software to de-bounce a switch until opto-isolator hardware was designed to eliminate some ESD effects. This may sound biased ... but many Asians had trouble working on fault tolerance. Many could not accept the simple fact that "we design systems to fail" and how they fail is what we can control. A lot of people have trouble accepting "hardware glitches" and software bugs. A simple ground wire making poor contact can drive some hardware bananas! The results are not predictable; often, not repeatable.
Columbia was destroyed on re-entry when wing damage allowed hot gas to compromise the wing structure leading to structural failure of the vehicle. The damage was caused on launch by a piece of external fuel tank insulation broke away and damaged the wing leading edge. This was not a main engine failure.
There are three Shuttle Main Engines. These are directly mounted to the aft sectTion of the Shuttle. Also 2 Solid Rocket Boosters used for launch only, mounted alongside the external tank.
The Challenger accident was caused by a failed o-ring in one of the SRBs caused apparently by low temperatures and failed to properly seal. This permitted hot gas to burn a hole through the external fuel tank and cause an explosion, with the resultant high-speed accleration of the crew compartment and eventual crash to the ocean with significant g-force, causing the death of the crew at some point during or after the explosion.
Neither of these accidents were caused by the 'main engine (sic)'.
It is unlikely that even mounting the Shuttle atop a launch vehicle would have saved it from an accident similar to that of Challenger. The explosion would likely either envelope the vehicle, or accelerate it beyond crew survival. Needless to say, vehicle stack has nothing to do with failures on re-entry, save that in a fully stacked configuration the wings would not be subject to damage from external fuel tank insulation loss.
Mercury, Gemini, and Apollo escape systems all would have probably been unable to save the capsules in the event of a catastrophic launch vehicle failure. If launch control was able to detect an impending failure they might have been able to get the abort off in time to get the capsule away from the explosion, but that's not assured.
Indeed, the escape systems were intended to (obviously) save the capsule from launchpad failures, facilitate aborts under fairly manageable conditions - launch vehicle off-course, loss of thrust beyond minimums for even emergency splashdowns, and of course other failures that permitted time to make the decision. There were onboard systems to detect a launch vehicle failure and trigger an escape on Mercury test launches, so I suspect they were on manned launches and probably similar systems on Gemini and Apollo. I wonder if they would have saved an Apollo capsule. That Saturn V is a lot of fuel. Maybe Gemini with the service module in the way. Mercury was truly spam-in-a-can, and I bet it was considered a gamble, but they did make an effort to save the astronaut, which is good sense. Astronauts are the most expensive part of the mission, usually. (Intentional understatement)
I'm actually standing by the 'dumass' remark. So far, the Shuttle Main Engines are not at fault for any accident, though by extension the external tank has been the contributing factor in both, weather and the SRB in one, and fragile (relatively) wing edges in another, sort of. But I didn't mean to be so harsh. Sorry. Maybe make that into 'not'. Better?
deleting the extra space after periods so i can stay relevant, yeah.
They can't stop Toyota from selling the cars because from my understanding the latest issue has not been re-producible. So The NHTSA is trying to find out what is wrong, for the sake of those that have purchased this car since highway safety is their job, so that they can tell Toyota and make Toyota stop selling the defective cars, until the issue is resolved. However, I would hope that they do not release the technical information to Toyota until they pay the bill plus interest for doing their leg work.
Couldn't just use a bunch of resistors and transistors to de-bounce your switches?
make the acceleration on the Prius purely mechanical? I mean you have all this fancy electronic stuff that has to go on to make the hybrid work correctly. How do you use traditional accelerator designs in such a thing? I don't think you can.
Of course, that doesn't mean traditional cars which are purely gas-powered should have DBW systems....
LedgerSMB: Open source Accounting/ERP
Why are we wasting American tax dollars to solve a foreign auto company's technical error!? To further drive American auto industries out of business? We should just ban Japan's defective lead-foot autos like we ban China's lead-filled products.
I wouldn't be surprised if this wasn't coming from NASA's already diminished budget.
NASA has to call Chuck Norris.
Steve Wozniak sez he can repeat the problem at will. Article:
It's easier to be a result of the past, but more fun to be a cause of the future! http://www.spacefinancegroup.com/
I'm not too sure they called the right folks to *fix* a "sudden acceleration issue". I mean, doesn't NASA try to cause sudden accelerations?
Great....so the US government has to flip the bill and fix the problem instead of Toyota.
An undeserved one, really. Soyuz has had as many crew-loss incidents as Shuttle, with considerably fewer flights than Shuttle.
"I do not agree with what you say, but I will defend to the death your right to say it"
In all this commotion, there is one thing I have been unable to find: numbers on sudden unintended acceleration from outside the USA. I know that Toyota has recalled vehicles around the world, but I haven't seen data on incidents outside the USA. Can anyone provide links to such, just to satisfy my curiosity?
Please correct me if I got my facts wrong.
and the role he played in investigating the Challenger disaster.
It's too bad he's not around to help out with the Toyota mystery.
All I have seen is some unknown acceleration CLAIM, and a lot of evidence (including study over many hundred of people) that OLD Folk tend to confuse acceleration pedal and brake. heck I nearly got killed that way : some old folk wanted to aprk and instead of hitting the brake on their expansive audi, they hit the freaking acceleration pedal. Thanks god, there was a tree between THEM and ME. I have yet to have evidence that this is not the same shit, and that some other which lost control of their vehicule just decided to assign it on toyota, and ride the blame wave.
I guess Prius tapped into dark energy field..
NASA, and the DOD, do buy a lot of the code, not all by any means. But, they do have a huge amount of experiencing *managing* the development of extremely reliable code and the computers that are needed to run them.
No matter who writes the code it is the management structure, including how specs are written, how testing is done, what methodology is used... you know the list,,, that result in reliable testable code.
Yeah, good programmers make it easier to get good code, but with out an excellent management system in place you do not get reliable code.
I just realized that the first flame I'm going to get is some thing "oh yeah? Then why is open source software so reliable? There's no management controlling that. You insensitive jerk." The answer is that every open source project I have looked at, or done, use peer review, or the fear of peer review as the way to insure good code. That is coupled with the use of trusted committers who ensure that even excellent code only goes in to the code base if it meets the specifications for that section of code. The specification may only exist in the committers head and a few emails or //FIX ME lines in the code. But the committer system, coupled with peer review, results in reliable code.
What this management system isn't very good at is keeping to schedules. While I've brought in software development projects within hours of the original schedule I could only do that because I was able to write the schedule for each section of the project only after completing, and evaluating the previous section. And, I had a usable data base of time-to-complete data for functions of different complexity levels. That and upper level management that allowed us to do a detailed function level design.
Stonewolf
It's important to note that this is not the same problem upon which the fatalities are being blamed. Woz basically indicated that he could reproduce a problem wherein the cruise control flips out and continues to accelerate when it shouldn't. But in his scenario, when he hits the brakes, the car appropriately disengages the cruise control and the car stops accelerating.
I just wanted to make that clear, but yes, that would seem to indicate at least one instance in which Toyota's software caused a vehicle to malfunction. It wouldn't be completely unfair to expect that there are more bugs.
NASA works in metric too.
There is no substitute for common sense. Especially, no body of rules will do.
We're more in trouble when they call Liv Tyler. That means the situation is so bad they just want to watch one more really hot car wash before we all die.