VOR/ILS
- Thread starter edstepec
- Start date
Tim Fitz
Member
- Joined
- Dec 25, 2019
- Messages
- 62
Not sure what you are looking for. I have a classic skyview with a Val Avionics Nav 2000 which feeds into the skyview and gives me all ILS indicators. I think the nav2000 takes up 1 inch by 6 inches of panel space. If you are looking for something that can be controlled through the skyview and remote mounted there is nothing I am aware of.
Thanks Tim. I'm looking for VOR and ILS capabilities on my HDX without an external OBS. I have no panel space and looking to see if some kind of integration hardware can be used behind the panel.
John Lucas
New Member
- Joined
- Feb 24, 2022
- Messages
- 16
Ed,
Are you looking for a remotely controlled NAV radio like the VHF radio or are you simply asking if the HDX displays the relevant LOC/Glideslope info? If the former, you’re SOL, but assuming the latter the HDX has no need for an external OBS. All of that functionality is built in to the HDX.
John
John, thank you for response. I would like to have VOR and ILS capabilities on my Dynon HDX without adding more hardware. Are you saying I have ILS capabilities?
John Lucas
New Member
- Joined
- Feb 24, 2022
- Messages
- 16
Once properly connected to your Nav radio (assuming it has ILS reception) the Dynon HDX will allow you to select the ILS as your nav source for the HSI and provide you with glideslope guidance. What NAV radio are you using?
If I understand what you're asking, the nearest, (and smallest), thing would be the MGL Vega control head ($265), hooked up to the MGL remote Nav radio N16 ($790). It hooks up to a Skyview RS-232 port and you can see VOR, localizer, and ILS glide slope indications on the Dynon HDX or Skyview screen.
CanardMulti
Active Member
- Joined
- Apr 1, 2021
- Messages
- 111
I have that system in my plane. The entire remote nav radio is the size of a medium paperback book and has NAV / GS splitter built in. The Vega tuning head needs a 2 1/4" hole. As mentioned, it talks to Skyview via one of the RS232 ports by emulating an SL30. Both VOR and ILS display perfectly on the PFD HSI. I've shot autopilot coupled approaches, including GS, just fine.
Ken
CanardMulti
Active Member
- Joined
- Apr 1, 2021
- Messages
- 111
It's been a while since I tried that. I seem to recall it did, but can't guarantee it. Since I installed my IFD540 a couple of years ago, with its own database & auto switch (GPS approach to ILS final) the NAV 16 became a back up. The one thing I never figured out how to do was to get the standby bearing to display on the Skyview #2 bearing pointer. The bearing numbers were correct on the tuning head, but either the SL30 emulation wasn't smart enough or I missed a configuration setting somewhere.
One connectivity setup that definitely falls into the belt-and-suspenders mindset: I have the switchology set up such that I can port the SL30 signal to either Skyview or my G5 standby attitude indicator. I could theoretically shoot an ILS with the IFD540 feeding Skyview and the N16 feeding the G5. Two independent nav radios each with their own display. Gotta try that someday
.....Ken
Attachments
Ken,
As I think I understand it, I think what you were trying is not possible. The Vega/N16 system, in Scan mode, can still only send one signal, (from the primary nav source), over the SL30 interface to Skyview. The scan mode just causes the N16 to rapidly switch back and forth from the primary frequency to the backup frequency, and display the data from primary on the upper half if the Vega while the backup freq data is delayed on the bottom half of the Vega display. It still continuously outputs the primary freq data over the SL30 interface to whatever EFIS it is hooked up to.
That makes sense, otherwise, the downstream EFIS would have to somehow be programmed to properly process a signal that was oscillating back and forth between two disparate NAV radio sources.
As I think I understand it, I think what you were trying is not possible. The Vega/N16 system, in Scan mode, can still only send one signal, (from the primary nav source), over the SL30 interface to Skyview. The scan mode just causes the N16 to rapidly switch back and forth from the primary frequency to the backup frequency, and display the data from primary on the upper half if the Vega while the backup freq data is delayed on the bottom half of the Vega display. It still continuously outputs the primary freq data over the SL30 interface to whatever EFIS it is hooked up to.
That makes sense, otherwise, the downstream EFIS would have to somehow be programmed to properly process a signal that was oscillating back and forth between two disparate NAV radio sources.
Last edited: