3 ms·
Because proper design for a safety-critical process shouldn't assume anything. Shouldn't assume that an accelerator pedal will have full range of motion when at
by ineedasername 9y ago
Because proper design for a safety-critical process shouldn't assume anything. Shouldn't assume that an accelerator pedal will have full range of motion when attempting to disengage, and should be programmed to route around unexpected inputs (or lack thereof)
- toast0 9y agoThis isn't reasonable. A traditional mechanically linked accelerator pedal has the same failure condition. If the pedal becomes stuck during a journey, I don't see how you can distinguish between that and user intentionally holding the pedal steady. Having the brakes override the accelerator is a reasonable safety advance that's more possible with direct computer control of the throttle, however.
- steve19 9y agoSimply put a load cell in the pedal and if a certain amount of force is applied slow down regardless of position of the pedal. If the pedal is not stuck, there is a limit to the amount of force you could put on it over a period of time. If it is jammed, a adult could put a lot of force on it when it is not fully pressed.
- retSava 9y agoI think the problem was that the software didn't take into account the situation where the inputs were both the accelerator floored, and braked floored - it should of course result in "disregard the accelerator input, do brake". The user/driver would have to fully disengage the brake, then re-apply it, for the sw to actually brake. (if I remember correctly)