Re: Disobeying jet engines - why?

I know some of the guys who do the engine control computer firmware
for the Pratt&Whitney engines. They use our gear to simulate engine
sensor signals to the control computer, and run weeks/months of
scripts to verify the firmware in all sorts of situations.

Their ECC's use no OS at all, just basic bare-metal state machines.

That's what one would expect, most people are sane after all.

I do wonder whether all involved have been sane enough to keep office
good only (well, almost good) systems completely out of the cockpit.
If the user (pilot) interface goes through even one such system
things are hopeless...

Dimiter

------------------------------------------------------
Dimiter Popoff Transgalactic Instruments

http://www.tgi-sci.com
------------------------------------------------------
http://www.flickr.com/photos/didi_tgi/sets/72157600228621276/

On Jan 24, 9:44 pm, John Larkin
<jjlar...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
On Thu, 24 Jan 2008 13:18:35 -0600, Damon Hill



<damon1S...@xxxxxxxxxxxxxx> wrote:
Didi <didi...@xxxxxxxxx> wrote in news:f121757f-1671-4ebe-892d-625ea1c236b6
@h11g2000prf.googlegroups.com:

http://news.bbc.co.uk/1/hi/england/london/7206596.stm

 Anyway, to me this sounds like some popular office OS has made its
way into the cockpit and was out for lunch with the HDD while the
pilot
was trying to talk it into delivering his commands to the engine
controllers...

Windoze is NOT qualified for critical applications like this.  It's
something pretty specialized and focused for the application.  I
suspect the investigation will either find a hardware fault or
operator error (misconfigured autopilot).  Airbus has had something
similiar happen, resulting in a crash and loss of life.

http://www.youtube.com/watch?v=-kHa3WNerjU

--Damon  Real life doesn't have a 'reset' button

I know some of the guys who do the engine control computer firmware
for the Pratt&Whitney engines. They use our gear to simulate engine
sensor signals to the control computer, and run weeks/months of
scripts to verify the firmware in all sorts of situations.

Their ECC's use no OS at all, just basic bare-metal state machines.

John

.

Quantcast