Vyking

Member
I have a panel with a single GRT EFIS HX, MGL ASX-1 digital ALT/ASI, TT DF II autopilot, and GRT EIS. In addition, I have stand-alone, battery-operated GPS capability.

Cruising to OSH in smooth air with the EFIS controlling the autopilot in roll and pitch, the nose began abruptly oscillating up and down. I pushed the autopilot's ALT button to stop EFIS pitch control and the oscillations immediately stopped. Several times later in the flight, I tried EFIS pitch control and was always rewarded with mild pitch transients. If the EFIS cannot smoothly control the autopilot in pitch (as it has not for years), I can terminate EFIS control. Break. Break.

On the return from OSH, I took off early Saturday in MVFR weather and was able to get on top 50 miles west. Ten minutes later, the EFIS backlight failed. It came back on for a few seconds about 1 minute later and then stayed off for the next 6 hours. Cycling EFIS power did not help.

With the sun at my back and shining directly on the screen, I was just able to interpret some symbols and words but for the most part, the EFIS was hard if not impossible to interpret. Later when the sun rose to the point that the EFIS was shadowed by the glare shield (as it would have been in IMC), I was only able to interpret parts of the display when holding an LED Maglite against the screen at a 45-degree angle. I navigated among EFIS screens using my memory of soft key functions because the menus were unreadable even with the flashlight. Twice, I had to soft boot the EFIS because I had pressed a wrong key and became lost someplace in the menu trees.

Think about all the data on the EFIS screen that would not have been available without a visible EIS for engine and fuel data, backup GPS for navigation, stand-alone autopilot* to hold the wings level and maintain vertical speed (perhaps a luxury in VMC but a necessity in IMC and a real work saver in an RV in choppy air), and separate ALT/ASI. Thanks to the non-EFIS sources, I really only missed easy access to corrected fuel quantity (but had a paper copy of the correction tables) and XM NEXRAD, TAF, and METAR information (very nice to have in any conditions but I was VMC). And, thanks to the Maglite, I had access to almost everything on the EFIS a square inch at a time.

* I have an older version of the TT DF control head, one with an internal magnetometer; so, if the GPS input from the EFIS were to fail, the control head would lose track information but its display would revert to magnetic heading. The newer (improved?) version of the DF head does not have a magnetometer and thus provides far less redundancy for the EFIS.

John Nystrom
Placitas, NM
RV-7A N7VD
RV-3B N3NU
 
On our trip back, our efis dropped connection to the A/P head at least five times. Separately the HX dropped all I/O and went blank for about 20 seconds and recovered with no more interaction from us than a sigh and a nod. I'm seeing a coorelation between heavy XM weather (radar) processing and these kinds of events. It sounds like you had hardware issues. Mine were software.
 
John, I am sure that got your heart going a little.

In my experience with electronics, 1-2 percent are DOA, and 1-percent die shortly after birth. But if they work for several hours, then they work reliably for a long time. (notebook market is currently seeing a 1.2% failure on the displays)

Hopefully you and others can relate the time in service for these types of failures.
 
Gracias Se?or Card

On our trip back, our efis dropped connection to the A/P head at least five times. Separately the HX dropped all I/O and went blank for about 20 seconds and recovered with no more interaction from us than a sigh and a nod. I'm seeing a coorelation between heavy XM weather (radar) processing and these kinds of events. It sounds like you had hardware issues. Mine were software.

Thanks for sharing Scott. That would bother me big time; mine have never gone TU like that. On the other hand, I have never gotten the EFIS to stay connected to the autopilot... Can't say as I have put much effort into troubleshooting it yet either.

Hans
 
TT dropouts

Scott,

I used to have the DF autonomously disconnect frequently in my -7A. A while back, I sent the circa 2005 control head back to TT to have the pitot-static connection replaced with a more robust connection. The repair ticket that accompanied the returned head indicated that TT added some "filters." Since then, unwanted disconnects have become rare. Uncertain, but suspect the filters blocked unwanted RMI from penetrating the DF circuits.

John Nystrom