If It's Just a Software Fix, Why the Delay?

If the software developer created a patch didn't work, did it kill anybody?

Keith

 

I am aware and realize that they did make a production change about a month ago. However, with the tens of thousands of 2010 Prius automobiles on the road, this anomaly only occurs very, very infrequently. Consequently I can understand their position of not issuing a recall notice which frequently causes more headaches than it solves with the news media going postal on every minor event. For this particular Prius anomaly, a service bulletin with a repair at the next scheduled maintenance would suffice.

Keith

 

We all like Prius that is why we bought it. We understand there is not a perfect product ever existed and there is always something can be improved. Thus I don't mind if a product has a defect. I think the point here is that Toyota claimed a fix already on the assembly line back in January. If they have the fix, why delay the response to the public? As a owner, I want to know what is the fix? When it can be applied to the current owner that have the problem. I want to know the fact.

 

wouldn't they need time to make sure the dealer can properly install the new map in the toyota OBD scan tool and that it flashes properly?

i do know it you stop a reflash in midstream the ecu will have to be changed out. (i've reflashed a wrx i once owned with good results)

maybe this is why it's "late" in getting to the dealerships.

 

If they knew exactly what they would be doing and when then I would imagine and hope that they would announce it, particularly once it was clear that it was of widespread concern. There are however a number of reasons that changes to existing cars would lag the factory change and they might be uncertain of timing. Reasons and possibilities include:

1. The time required for documentation and training would make field implimentation lag factory implimentation.
2. They would need to decide whether update at time of service or recall was more appropriate
3. They may have responses to other related issues in the works but not quite ready for release (eg braking in reverse) and they may feel that it would be safer and less disruptive for their customers to implement them as a single fix on existing cars

 

Originally Posted by duffasaurus
NEILZ: Yesterday I drove my 2010 Prius through the most crueling weather conditions, heavy rain & flooding, bumpy roads and all; did not experience even a hint of braking problems or hesitation. Felt extremly safe & secure. Why do you find it necessary to bad mouth such a wonderful product & responsive company such as Toyota??

As an addendum to my previous post, if I were to go over a seam in a driveway and loose my brakes for a second, I would either slow down or hit the brakes harder next time. Duh!

 

I would add

4) It may really be a sensor issue. The software should have been robust enough to handle this, and the fix intends to correct. Testing for more bad sensor behavior in different modes is difficult. They may not be confident in the fix. They also may not want to go through one recall for software, then have to recall to change out the sensors.

5) Those that do not want to take the financial hit may be dragging there feet. The recall will likely be more expensive than the lawsuits. I hope that this is not the real reason.

 

You'd might actually be better off not braking at all while going over that bump..that is what I do.

 

I haven't read through this thread, but does anyone think it is possible Toyota will be giving pre-January 2010 Prius's a different fix than the one currently implemented?

They said it there was a software lag between items switching..To me that sounds less like a software problem, and more like a hardware problem. Maybe they added faster components, Communication BUS, etc to the new Prius and didn't update the software at all.

Any thoughts?

 

The problem is NONE of us know what Toyota did to make the change in Jan.
Was it software? Most are "guessing" it was.
Was it hardware?
Was it a combination of both?
We really don't know at this time.

 

"...I would expect..."
In a few days we will know.

 

Furthermore, implementing a software patch, even if its just plugging in their scantool to the obdii port, is very different than changing what it installed at the factory.

For example:
Establishing and testing exact procedures to TEST each car to ensure the fix 'took'
Establishing and testing training of techs in implementing the fix and the above procedures in how many languages around the world
Training those techs
Consulting with NHTSA and similar organizations around the world to increase chance of solving everything to everyone's satisfaction
etc

 

Where do you think the 'software' lives in a car?

 

It is distributed, in many control units.
Hopefully, one "main" ECU can rewrite the software (firmware) to all the other ECUs.

The real problen is finding the "bug" and creating a suitable "fix".

If the vehicle was designed for an "easy update" (I suspect it was not),
one would not really need the dealer to "install" the "fix".