Mitsubishi Montero Sudden Acceleration Accidents [MERGED]

**jick.cejoco** · November 24th, 2015 02:12 PM

Slim possibility of program bugs. Maybe hardware problem, driver fatigue, accelerator/brake pedal ergonomics, driver error. At one point, jeep Cherokees had ergonomics problem-the floor hump above the transmission bell housing was wide making the accelerator pedal scoot to the left and had the driver's right foot apply both accelerator and brake pedal during panic stops. Same thing with HMMWV(hummer)

**oj88** · November 24th, 2015 02:20 PM

Agree that the ECM/PCM setup of an A/T model is a lot more complex. And many victims insists that the engine went to WOT as soon as the gear shift was set to R or D without touching the gas pedal. A few even mentioned that the engine remained at WOT even after they've evacuated the vehicle.

That could indicate a hardware or software transient fault.

(Transient Fault - A short term - non periodic fault - after which the process returns to a normal running state.)

**Monseratto** · November 24th, 2015 02:25 PM

Originally Posted by Syuryuken

Bakit sa MT wala namang SUA

nanggugulo lang po

You have control over the engine power entering the transmission. You can easily drop the clutch when the engine suddenly goes berserk... Unlike ATs where the computer controls the clutch...

- - - - - - - - - - - - - - - - - - - - - -

Originally Posted by Syuryuken

Bakit sa MT wala namang SUA

nanggugulo lang po

You have control over the engine power entering the transmission. You can easily drop the clutch when the engine suddenly goes berserk... Unlike ATs where the computer controls the clutch...

**car_fan** · November 24th, 2015 02:34 PM

Just reposting this article from EDN where toyota settled out of court with SUA class suit. Toyota's killer firmware: Bad design and its consequences | EDN

An independent inspection of toyota's firmware says that stack overflow can cause SAUs and that the quality of the firmware was "unreasonable". So we cannot outright rule out a software bug unless someone independent inspects the software code. Kung baga sa chess mas magaling ang miron kaysa sa player. Kaya it's a standard across almost all industries ang independent validation/check ng kung anu man critical task na ginawa/tinrabaho mo.

**CVT** · November 24th, 2015 02:37 PM

Originally Posted by car_fan

Sa MT, probably lesser routines to do/monitor yun ecm. I.e. Gear shifting in auto is mostlikely controlled by the ecm based on driver input and sensor feedback from the engine. Unlike in mt, the gear shifting is controlled manually. So probably, the firmware for MTs are relatuvely less compkicated compared to those for ATs. In turn, makikng it less likely to committ mistakes in the codes.

The main ingredient in the SUA is the high revving engine. Now, my simple mind tells me that it should be independent on whether the variant is AT or MT....

Shifting the AT to D,- could have a trigger on the engine, as it "electrically engages" the FBW accelerator,- but to what extent,- we do not know for certain, vs. shifting the M/T to 1st gear,- which also BTW "electrically engages" the FBW accelerator....

"The measure of a man is what he does with power" LJIOHF!

28.2K _/_/_/_/_/:fish:_/_/_/_/_/

**CVT** · November 24th, 2015 02:48 PM

[

Originally Posted by car_fan

Just reposting this article from EDN where toyota settled out of court with SUA class suit. Toyota's killer firmware: Bad design and its consequences | EDN

An independent inspection of toyota's firmware says that stack overflow can cause SAUs and that the quality of the firmware was "unreasonable". So we cannot outright rule out a software bug unless someone independent inspects the software code. Kung baga sa chess mas magaling ang miron kaysa sa player. Kaya it's a standard across almost all industries ang independent validation/check ng kung anu man critical task na ginawa/tinrabaho mo.

That is the critical function of the quality and reliability checks, plus the actual run-ins for x amount of hours.... So, absolutely, there should be no shortcuts here.

Now, stack usage [normally used in jumps/returns - push and pop routines] is critical, and its memory address should be assigned where there are a lot of [memory] room to spare. Plus, if at all possible, should be independent of the main memory so that it will not crawl into the main program, where it will wreak havoc in the program. It is a programmer's lack of foresight and anticipation on its actual use and so it should be caught downstream during the development/testing stages.

"The measure of a man is what he does with power" LJIOHF!

28.2K _/_/_/_/_/:fish:_/_/_/_/_/

**car_fan** · November 24th, 2015 02:52 PM

We wont know how different the firmware designs are for both MTs and ATs. We can only pray that our car manufacturers do not take SUA reports for granted be it fact or farce.

Mitsubishi has probably taken steps internally, since wala naman yatang SUA claims for newer models? And did they add the brake override feature on the newer models? Parang ang marketing is to prevent and control the brakes if ever there was misapplication of the accelerator. That's how they arr marketing it 😁

**anonemus** · November 24th, 2015 02:54 PM

Published last March 30 pa

The truth about Sudden Unintended Acceleration - The Inside Man http://www.autoindustriya.com/the-in...eleration.html

**car_fan** · November 24th, 2015 03:02 PM

With all the money and internal deadlines, a shortcut is a possibility. Considering a day of delay sa roll out ng new model can cause manufacturers millions.
as long as nadaanan yun process of testing, larga na. Plus human oversight and the test cases that one can think of can also be a source of imperfection.