![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
g1000_eng writes:
1) All avionics software implements internal isolation to prevent one part of the system from taking down another part. Except the G1000, apparently. 2) A faulty fuel reading cannot cause the system to reboot. In addition to testing every possible faulty fuel value, I've tested every combination of faulty sensor readings related to this thread and am unable to get anything out of the ordinary to happen. Since the system did reboot, there is obviously a combination of circumstances that will cause it to reboot. It should never reboot. 3) When the system reboots due to a software error, a very obvious message with a very obvious color is displayed on the screen prior to the reboot. Was this seen? I have seen no mention of it. How does an obvious message help? -- Transpose mxsmanic and gmail to reach me by e-mail. |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
AOPA Stall/Spin Study -- Stowell's Review (8,000 words) | Rich Stowell | Aerobatics | 28 | January 2nd 09 02:26 PM |
UAV's and TFR's along the Mexico boarder | John Doe | Piloting | 145 | March 31st 06 06:58 PM |
Air Force One Had to Intercept Some Inadvertent Flyers / How? | Rick Umali | Piloting | 29 | February 15th 06 04:40 AM |
Nearly had my life terminated today | Michelle P | Piloting | 11 | September 3rd 05 02:37 AM |
Logging approaches | Ron Garrison | Instrument Flight Rules | 109 | March 2nd 04 05:54 PM |