SUA - Here we go again

^^ Thank you for (indirectly) answering my previous question. You are not familiar with Regression Testing.

This is one of those ancient lessons that keeps getting re-learned over and over again.
... and again.
... and again.
... and again.
... and again.
... and again.
[posting truncated]

 

The Old Programmer Says:
"Software means never having to say you're finished."

 

Because it's a developmental engineering test result. Dude, give it up. There's nothing here.

 

Every time we discover, RARELY discover, a new flaw in our software or the FPGA firmware we fix it and then add a post-production test to be sure that area of the design gets more thoroughly tested.

You're welcome to drop by and monitor at any time.

 

Read the failure mode again...

The ACC was in the process of slowing the vehicle, braking, when the gas pedal was fully depressed.....AND....the ACC reacted, improperly so, by releasing the brakes..!!

But you are correct, this was NOT an SUA incident, testing was probably being carried out with the subject vehicle FIRMLY strapped down on a dyno.

The test was CERTAIN proof that the subject vehicle's firmware was flawed in such a way that SUA incidents might well result if the firmware reached production. That raised concern, obviously, that other product lines sharing the same base firmware source code might also exhibit the flaw so the testing for the specific design flaw was extended to those.

 

NO it is not Certain proof of anything. This is simply your personal opinion of what you read 2nd and 3rd hand then your personal opinion based on no actual facts. You continue to push this BS in every thread on the subject without prefacing your remarks with the disclaimer....

"The following comments are based soley on my personal opinions. I have no facts from any source to support my opinions."

When you have hard data and facts from the actual events then you can do away with that disclaimer.