Morse Code Identification Signal
-
@Tigerclaw I repeated your testing and I do get the same results as you now for NAV1 and NAV2, except that I don't get Morse with the NAV1 rotary switch in the IDENT position regardless of which position the NAV1 audio switch is in.
At EGKA, tuned to 332.00 on the ADF receiver I can now hear Morse with the audio panel switch in the speaker and phone positions (which I couldn't before), so that is working.
I don't know if I was doing something wrong before but at least I can hear it now, albeit as you say it needs a bit of tweaking.
I didn't see this issue in the changelog for the update so I'll do a ticket explaining what I'm seeing now.
Thanks @Tigerclaw for your input and for taking the time to test.
EDIT: Just did the same testing again and now I can't get any Morse at all on NAV2, not even using the IDENT switch position. There appears to be some inconsistency.
-
We're using the default audio system. Can you hear the NAV 1 ident in the default aircraft?
We are waiting to hear back from Asobo about increasing the volume levels for audio idents. Currently they should be as loud as the default aircraft but bear in mind differences in engine noise.
-
Putting the NAV1 and NAV2 audio panel switches to Speaker or Microphone and the NAV1 and NAV2 rotary switches to Ident, the NAV1 and NAV2 idents now work for me since the update. I can hear both at the same volume (albeit a bit quieter than I would like but I guess that's an Asobo issue).
-
Setting the sound to headphones rather than default will make the ident sounds louder. Or turn down the engine sounds in settings?
-
Tried the JFK VOR (115.90) and I've been getting different Morse codes on NAV1 and NAV2 (NAV2 getting the correct one). Used the old school avionics with GPS100 for the test, for some reason the ident volume control on the 430 and 530 doesn't work
There's something strange going on with Asobo's database. -
I am receiving Morse code ID on both NAV1 and NAV2 but the code from NAV1 does not correspond to that of the received NAV aid. Instead it remains fixed to that of a NAV aid with a frequency of 110.5 MHz which is the initial NAV frequency the receivers are set at the start of a flight. The code from NAV2 is correct.
This behavior is unlike that found on the default 172s where the correct Morse ID can be heard on NAV2 but absolutely nothing is heard from NAV1. That problem appears to be fixed for the steam gauge Cessna 172 using the GNS 530/430 mod, pms50-gns530. However that mod has absolutely no effect on the NAV1 code problem with the Just Flight PA28 Arrow.
-
Currently we only have control over the NAV frequency, whether the audio ident for the corresponding NAV radio is active and the audio volume. If the NAV frequency is changing as commanded and the HSI/OBS are responding correctly to the tuned VOR then that'd confirm that our logic is correct but unfortunately the MSFS functionality is broken.
Martyn
-
@Martyn
I understand what you are saying about what you have control over but as I pointed out the strange behavior observed with the NAV1 Morse code ID appears to be unique to this aircraft. The default MSFS aircraft I have tested may or may not yield Morse ID on NAV1 on any given sim session, but when it is heard it is always the same as that received on NAV2 when it is tuned to the same frequency.
As I pointed out there may be a clue to the source of this behavior in the fact that for any NAVAID received on NAV1, and correctly being responded to by the HSI/OBS, the Morse ID heard belongs to some other NAVAID with a frequency of 110.5 MHz which just happens to be the the frequency setting of both NAV receivers on start up. For this to happen there must be some bug in the coding for NAV1 that is controlling something other than what you intend to be controlling. This is why I don't believe that this is simply a MSFS issue and it should receive your further investigation. I would suggest comparing the coding for NAV1 for this aircraft with that for NAV2 to start.
That is why I have taken the time to investigate and submit a ticket to your support team. -
@sdvpilot
I have since found on the default MSFS aircraft I have tested that reception of Morse code ID on NAV1 is appears to be inconsistent from one session to another but when heard the code is the same as that heard on NAV2 when it is tuned to the same NAVAID. -
-
So I just spent a couple hours running through all combinations of radios, and boy is there some odd behavior.
This was done with all mods removed, then adding in gns530 mod then the 750. Latest versions as of today. All behavior was the same. I was parked at the same airport every time, with both nav1 and 2 tuned to the same frequency.
Sound is quite low over the engine volume, but it is there. I could hear it at idle, or by going into the sound setting and selecting headphone simulation, which I guess just reduces the engine volume.
Right...
So with the 2 old radios, all was fine when flipping the switches on the audio panel. Only thing not working was the volume, which did nothing till turned all the way down and clicked off then no beeps.
Now when I did flip the switches, from middle to up or down, or back to the middle, I can hear the sound of a knob turning rapidly. This is the same sound from the vol knobs on the gns 530/430. I also hear that sound at some point within a few minutes of loading in.
With the duel gns, no sounds. At first, the volume knobs won’t even turn. But after a few minutes, I hear as mentioned before, knobs turning. Then they work move, but still no beeps. I some point I accidentally hit the dme switch, and had beeping! Turned out this was on nav 1 as the only way to stop it was flip the dme switch off (btw the actual dme was off the whole time) or change the frequency.
With the 530 as nav1 and an old radio as nav 2, nav.2 worked fine. Well same as before anyway. Nothing from the 530. Unless I flipped the dme switch.
To experiment, I pulled up the 2 old radios, flipped nav1 down. Got the beeps. While leaving that as it was, switched to duel gns. Still had beeping, but couldn’t turn it off. At some point the volume knob would start working and I could in fact adjust the volume, but the switches on the audio panel had no effect.
With the 750 and old radio for nav2, everything was actually mostly fine. I don’t know if the 750 has a page somewhere to adjust the nav volume, I didn’t look and there’s just a com volume knob. Also in the 750 audio panel page, pressing the nav 2 button won’t turn it off or on. You have to do it on the old radio. Similar situation as the cdi and new switch I guess?
-
@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.
