On Jan 28, 5:14 pm, Mxsmanic wrote:
Neil Gould writes:
I don't think that's possible. There is no provision for the display
system to reboot the hardware; that just isn't done via software, or even
by physical switches located on the display unit(s). The display unit(s)
can't turn on or off the individual modules either, so a software glitch
of any kind -- or even total failure of the display -- isn't able to be
the cause of a system-wide reboot.Virtually any bug can cause a reboot. Anything that produces a
hardware exception can cause a reboot if it is unexpected,
particularly if the system is doing privileged work at the time. A
reboot is the typical response to any unhandled exception. The
alternative is to let the system run hither and yon uncontrolled
through the code, which is even worse than a reboot in most cases.

Of course, in safety-of-life applications, there must not be any
unexpected exceptions; if there are, it's a flaw in the design.
Unfortunately, people from PC-land tend to take the system down
whenever there's a spot in the code that they don't want to design or
analyze in detail.

A reboot of an individual display would not surprise me (although I've
never seen it happen). A reboot of both would surprise me. However,
NW_pilot's issue was a software bug associated with the long range
tanks that were installed. I guess the computer failed working out the
fuel calculations. Since both sides run the same software, both sides
probably had the same fault.

-Robert, CFII, FITS TAA instructor.