As for your Mx depiction of selected course, I’d have to look into it but I believe that is just the analog/OBS input, not the 429 input Processor) and MAP (Main Application Processor).
IFD, then report back your Aspen software information for the IOP (I/O You or your installer should check that you are configured for Honeywell EFIS on your Their ACU to drive an analog heading output, although I believe we are anĪll-digital setup and that label 0105 is there. It’s actually coming from a message intended for Support sending that data as it is an unofficial label we reverse engineered inĢ.6.2 of the Aspen software. Selected heading if you are configured for Honeywell EFIS.
We will only use the Aspen special label for That continue to send course data in VLOC, like the Sandel SN3308 EHSI.Īs for the Heading Bug, it has to do with how your installer hasĬonfigured the Aspen and your IFD. Selected course over 429 to us, so they don’t. Stops sending the selected course data in VLOC mode as it resolves the courseĮrror internally by taking the difference between 429 label 0222 (VOR You won’t get the VLOC course line using an Aspen. This might be a little too gobbly gook for you but here goes. In that release, if we don't have baro corrected altitude, we'll use GPS altitude instead.Īnd 27 on EFD to access EFD air data directlyĬongrats and thank you on the IFD540 purchase.Īs part of Release 10.1.0.0, I will be publishing a clearer description of the VOR course line integration with the various EFIS's out there - many are slightly different from each other in behavior based on what they do or do not transmit/accept. If you don't have an Aspen configuration that supports it now (one that sends baro corrected pressure altitude), don't fret, that capability will come along "for free" with Release 10.1.0.0 in the spring. The one that had most people wanting for more is Advisory Glideslope. You can see there are some configurations below that provide that data, and some that don't. The ACUs are essentially a "happy box" or signal interface box.įor features like VSR datablock and Winds datablock and Advisory Glideslope to work, the IFD540 needs baro input (baro corrected pressure altitude and TAS) among other things. EFD + ACU (I called this ACU1 in previous posts) You can see there are three basic configs:Ģ. I've tried to put together a summary table of the various Aspen configurations when connected to an IFD540. There are understandably a number of folks confused with why they do or do not have certain features on the IFD540 when connected to an Aspen EFD.
0 kommentar(er)
