Originally Posted by
Peter H
Nice find. I'm still having problems interpreting things though, any ideas on:
The deliberately broken microprocessor had become overwhelmed with data from the flight control system.
- If its "broken", how is it still working.
- If its "crippled" by how much.
- Or is it "restarting" after some sort of interrupt/reboot.
- Finally is the "overload" a transient effect, or the new status quo.
Re my question.
I now feel that the new "glitch" occurred when the tester faulted the "active" processor in the FCC, triggering a fail-over to the "standby" processor.
This gives obvious opportunities for disruption of normal service.