Free Republic
Browse · Search
News/Activism
Topics · Post Article

To: sgtbono2002; PAR35

It wasn't a computer malfunction, but a sensor malfunction, apparently due to a problem with the system handbook.


16 posted on 06/09/2005 6:29:54 PM PDT by expatpat
[ Post Reply | Private Reply | To 2 | View Replies ]


To: expatpat
apparently due to a problem with the system handbook.

No, it was caused by a lack of electricity. If a battery (or as another poster pointed out, a capacitor) had been wired into the system, there would not have been a power loss in the brief period of time between engine shutdown and apu takeover.

The problem might be solvable by either a manual or computer driven cut-over to the APU before the engine is shut down.

21 posted on 06/09/2005 6:46:26 PM PDT by PAR35
[ Post Reply | Private Reply | To 16 | View Replies ]

To: expatpat

Sensor , Computer , its all part and parcel of the system.


22 posted on 06/09/2005 6:55:02 PM PDT by sgtbono2002
[ Post Reply | Private Reply | To 16 | View Replies ]

To: expatpat
I'd call it a software design drop-out. Such sequence after unsual circumstance contingencies can be caught by astute designers or testers. However many aren't. I caught some on an F/B eject sequence wherein a system failover occurred. They had been there, latent, for years and years.

But I am not representative of the average sw engineer. Sui generis.

24 posted on 06/09/2005 7:00:30 PM PDT by bvw
[ Post Reply | Private Reply | To 16 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson