I operate on the opposite principle - the information needs to flow FROM the devices with small glass screens TO the device with big glass. I run an IFD440 because after programming the route, everything else happens on the HDX - no need to pay for more glass on the IFD that won't get used.I'd like the HDX to be able to send fuel computer information to my Avidyne IFD540. Maybe I'm just missing how to properly configure this, but I think this is currently missing.
I operate on the opposite principle - the information needs to flow FROM the devices with small glass screens TO the device with big glass. I run an IFD440 because after programming the route, everything else happens on the HDX - no need to pay for more glass on the IFD that won't get used.
I operate on the opposite principle - the information needs to flow FROM the devices with small glass screens TO the device with big glass. I run an IFD440 because after programming the route, everything else happens on the HDX - no need to pay for more glass on the IFD that won't get used.
You mean adopt OnSpeed AOA tones…. The winner of the 2021 EAA AirVenture Grand Championship Award for flight safety.I would like the configuration screen to allow the user to optionally specify another tone schedule for the aural AOA tone. Just like the config settings allow for specifying various bands for the on-screen engine sensor displays. for example,
1. Below x% of stall: Silent (No-tone)
2. Between x% and y% of stall: below gradually increasing as AOA increases Pulse Repetition Frequency (PRF), from 1.5 Pulses per second (PPS) to 8.2 PPS), 900 Hz tone
3. Between y% and z%: , solid (continuous) 900 Hz tone tone
4. Above z% of stall: very high PRF (~5 pulse/sec) 1600 Hz tone
Where the percentages can be set in configuration as is currently possible in Skyview version 15 ...
The example above is drawn from the design and operation of the AOA tone schedule in the F-4C/D/E Phantom, and as anyone who flew this jet can tell you, it made an enormous difference, not just for avoiding the stall, but for flying the aircraft (irrespective of airspeed, gross weight, bank angle etc.) at the optimum AOA for what you were doing, without monitoring instruments. Flying approaches was especially affected. You could fly an overhead traffic pattern, using a wide range of airspeeds, configurations, at any gross weight, and using whatever bank angles were needed in the turns, without looking inside the cockpit at the airspeed indicator. You just needed to monitor the aural AOA tone and keep it on the steady tone that was set to optimum approach AOA. This allowed you to maintain more continuous visual contact with the runway environment and other aircraft in the airport traffic pattern than would be possible if checking airspeed every few seconds.
Trying to use the existing (Skyview version 15) AOA schedule to do this (without looking inside the cockpit), is helpful, (better than nothing), but not optimal, because I have to set the threshold between the beeping and the continuous tone at the AOA I want to maintain for approaches, and then I need to adjust trim/back stick pressure to maintain the tone on this threshold.. i.e., I need to continually oscillate stick pressure so I am hearing the beeping, and the steady tone, switching back and forth, to know I am at the AOA where the transition occurs.
You mean like the SkyView Video Input Adapter described on page 15-7 of Revision AT of the Skyview Installation Guide?1) Ability to have a video feed from a nose mounted camera on the screen for taxiing.
1) Ability to have a video feed from a nose mounted camera on the screen for taxiing.
Camera located inside the air scoop of my T-51 Mustang
I would like to add that I'd like to see enroute VNAV with the Garmin GTN 750
- As mentioned before, I'd like to see enroute VNAV working with the Avidyne IFD.
- Dynon integrated Nav/Comm.
- Dynon certified pitch trim, not just the controller for 3rd party servos.
- I'd also like to be able to have the PFD on the right side for a screen configured as the primary display. Currently, for a certified installation, the primary display must have reversion mode enabled and the screen role set to PFD. I don't recall which setting forced the primary side to be left with these settings, but I'd like mine to be on the right. The right side of the screen is directly in front of me with the rest of the screen offset to the left. I'm not sure why this wouldn't be configurable.