Morse Code Identification Signal
-
@weptburrito, I saw similar behavior when I tested the default C172, including the inability to turn the volume knobs or hear anything, which then seemed to just randomly start working. Also, in the C172 you can only hear the ID beeps if you press and hold down the ID/Volume knobs, and also only at idle or by using headphone simulation mode... I don't know if this is how the real world GNS530/430 works?
I think these are bugs in the MSFS default GNS530/430 units, and not the Arrow III...
-
This is something that N6722C brought up on the PMS50 GTN750 Discord: start a flight in the Arrow at rwy 1R of KIAD (Washington Dulles Intl), tune to 110.10 on NAV1, listen to the Morse, it identifies the station as IDQZ.
The correct identifier is IIAD, and you can hear that on NAV2.The same happens with the local VOR AML on 113.50: on NAV2 you'll hear the morse for AML, on NAV1, you'll hear the morse for IDQZ.
Try this with the default C172/G1000 and you'll get the correct identifier on both NAV radios.
Could this be related to the issues discussed in this thread? @Martyn
(I tested this with 0.5.1 and the GPS 100 cockpit layout and Navigraph Navdata.)
-
@RetiredMan93231 weird, I had also compared to the 172, and aside from the random volume thing, it worked fine. Pressing the nav 1/2 on the panel worked as did holding in the ident button .
I think it got lost in my long rambling, but I’m getting no Morse with gns 530/430 units. Unless I start it with a different unit and switch. But then can’t turn it off. -
Actually scratch some of that. I went to check it out again, and pushing and holding the ident on the 530/430 I can get the morse. This is regardless of the audio switch position though. So not as messed up as I thought lol
Oh...I am getting a different code between nav1 and nav2. Nav2 is what I as expecting This happens with all combinations. Turns out nav1 one is identing the localizer at the airport and not the vor I was tuned to. This did NOT happen in the 172
edit: Nope, nav 1 was not identing the localizer. I assumed it was as that was what I dialed in and was swapping between that and a vor. But it wasn't the correct morse.
Went to another airport and nav1 morse didn't work at all.
Went to a third, KDAB. ILS 109.7 Same freq. for either end of the runway 25R or 7L. Little nav map is showing a different morse for each side though. Parked in the SE corner Nav 2 is giving me the morse for 25R. Nav 1 isn't beeping either one
Also noticed the reason the dme switch would send out morse, I was tuned to a VOR DME lol
-
Yes, im still messing around with this lol
It looks like the jplogistics 152 mod is conflicting. It was causing nav1 morse to not work unless I dialed in the frequency on the dme also. I thought they had sorted some of that out awhile back. I renamed the file structure and associated files and that seems to have fixed the conflict.
So heres the list of what I have been able to repeatedly confirm.
Nav volume knobs are flakey. But I think this an asobo thing as it happens in other planes. Not working for a few minutes, hearing them turn (I actually saw one doing it) when you flip the switch on the audio panel. This is very random though.
Nav1 morse is not correct. Does not match what is documented. Nav2 is fine. This is Piper only as I also checked in the 172 and 152. Stock 152 has its own issues, but with the mod makes the audio panel useable.
Audio panel with the gns units 530/430. Audio panel nav1/nav2 has no function. Must hold the ident buttons. Similar situation as the new nav/gps cdi. Though might be to buried in Asobo code to do anything with. By comparison in the 172, they both work. Backward if the panel button is on and pressing the ident on the 530.
-
-
The morse code idents are also difficult to hear in some of the default aircraft... so, this is more of a problem in MSFS than a specific aircraft bug.
