DME Audio ID Not Working in v0.6.0
-
@sdvpilot Sorry, I missed your reply initially. In the mean time I arrived at the same conclusion. Although I had an extra twist. In my case the NAV1 volume was set to zero, so what I had to do was to switch to the GNS530, turn up the NAV1 volume, select the GPS100, enable ADF and NAV1 audio on the audio selector and, finally, I had the ADF morse code. Currently I only have to enalbed ADF and NAV1 audio on the selector, and that's it.
I did file a support ticket for this, did you do the same?
-
@corvus5624
I was not previously aware of ADF audio being dependent on NAV1 selection and volume level. I will certainly look for that ASAP. The ticket I submitted only described the issue with NAV1
and DME audio ID. -
@corvus5624
I also found the ADF audio behavior to vary with the selection of GPS equipment. In each case the ADF frequency was set to one nearby NDB and the direction indicator was responding correctly while sitting on the ground in a fixed position in the Turbo Arrow III. I believe the sim, the aircraft, the GNS530, and GTN750 addons were up to date at the time of this test. Note that in no case did the ADF volume control position actually change the ADF audio level heard.For ADF audio Morse code ID to be heard the following was necessary:
GPS 100
- Audio panel NAV1 and ADF switch in either speaker or phone position.
- NAV1 volume control in any position but off (full counter clockwise). ADF audio level heard did not change with control position.
- ADF Function Switch in any position but off.
GNS530 or GNS Dual
- Only the audio panel ADF switch was required to be in speaker or phone position.
- ADF audio level heard is dependent upon NAV1 volume control position.
- ADF Function Switch in any position but off.
GTN750
- Audio panel ADF switch on.
- No NAV1 volume control exists and ADF audio level remains fixed.
- ADF Function switch in any position including off. When repositioning the ADF Function switch the ADF audio panel
switch appeared to switch off and it had be turned back on.
I have no reason to believe that the order of GPS selection is relevant.
-
@sdvpilot This pretty much supports my findings, which I detailed in the ticket I made. Somehow the GNS530 NAV1 volume control sets the ADF audio volume. So, to set the ADF volume if you are using the GPS100, you first have to switch to GNS530, set the volume there, then switch back to GPS100. For some reason my NAV1 volume was set to zero (despite the NAV1 volume setting on the old KX175B radio). So enabling NAV1 and ADF on the audio selector panel was not enough for me, I really had to switch to the GNS530 to turn up the volume. Very weird, but I'll take any work-around over no work-around at all.
-
@corvus5624
Very interesting about having to preset the GNS530 NAV1 volume control before hearing ADF audio with the GPS 100. I will have to look for that specific behavior on my end also. When I tested with the GPS 100 I have no idea where the GNS 530 NAV1 volume control was set. Another strange thing is that when I first switch to the GNS 530 or GNS Dual setup I can't seem to get the NAV1 volume control to respond to the mouse. If I come back and try again sometime later it does respond.
Please post again if you get any useful response to your ticket. Just Flight Support simply closed mine out saying they would be looking into it. My hope is that they will fix these issues if they have the hooks into the sim to do so. If sim code limitations are in the way I do hope they pass on such issues to the sim developers. Presently it seems like none of these bogus NAVAID audio ID behaviors are getting much attention. -
@corvus5624
I found the ADF audio behavior with the GPS 100 as I described previously and completely independent of where the NAV1 volume control is preset on the GNS 530 including its off position. -
