Some insights into the G1000

"Neil Gould" wrote in message
news
Recently, J. Severyn posted:

"Neil Gould" wrote in message
et...
Yesterday, I attended a 4-hour seminar on the G1000 presented by

snip

I understand, and it appears that this was done. On the one hand, this
system isn't all that complex; rather than feed numerous inputs into a
single interpreter module, which might result in the kind of event you're
anticipating, each module is a physically separate piece of hardware that
feeds its results to the integraged display. There is also redundancy
built into some modules (multiple components doing the same job), and any
ambiguities are either resolved by a "vote of the majority" or failed, but
won't result in a system-wide reboot.

I understand. But the integrated display might be the culprit. The
individual LRUs might be acting properly and feeding data to the display
system. If the display system (hardware or software) does not properly
handle the exceptions, then lots of unintended things can happen. Software
patches, compiler errors etc. only make the testing combinations all the
more difficult.

In any case, a pilot has got to be able to keep the dirty side down using
the backup steam guages.

snip
Neil


Regards,
John Severyn