Annoying Morse Code Beeping Sounds

[Goatman24]

He only needs to press the "MKR" button

Ok, the next time it starts acting up I'll try that. That is one of the buttons that does work. For some reason, the "ADF 2" does not function as do any of the buttons listed as "Phone" or the "Hi - Lo" and "HF".

I thought I had tried each of these but will try the MKR on it's own again.

Is there anything I would be doing in flight that would cause this to suddenly start up as it does?

Thanks much,
Mitch

[THBatMan8]

Marker ident doesn't automatically tune on it's own. You most likely hit a keyboard command by mistake that turns that switch on/off, or it was left on when you loaded up the plane/panel and you didn't turn it off.

[deor]

[QUOTE=
Is there anything I would be doing in flight that would cause this to suddenly start up as it does?

[/QUOTE]

They start to beep when you are within range of the transmitter the particular radio is tuned to. The whole purpose of these idents is so that you can get a heads-up that you are within range of the navaid you want and so that, by listening to the morse pattern of the beeps, you can know that you are hearing the right beacon. You can see the patterns by clicking on the navaids on the FSX map; it's intricate stuff like this that makes steam-age navigation much more fun than programming the gps.

[f16jockey_2]

As said in a prev post, in the pic you're showing you have COM1, NAV1, NAV2, MKR, DME and ADF1 identity turned ON (button pressed IN).

One of both COM receivers (mostly COM1 needs to be ON).
MKR should stay ON, that will give you beeps when passing over the OMI markers on approach.
NAV1, NAV2 and ADF1 have to be turned OFF to get rid of the morse code beeps.
ADF2 is inoperative (in the OFF position) as the aircraft you're flying probably doesn't have two ADF receivers.
I have no idea what the DME identity does.

Wim

[deor]

"I have no idea what the DME identity does." - if you have tuned a nav radio to a DME beacon (rather than a VOR beacon - which includes
DME) it will will beep when the radio picks up signals on that frequency.

[f16jockey_2]

if you have tuned a nav radio to a DME beacon (rather than a VOR beacon - which includes
DME) it will will beep when the radio picks up signals on that frequency.

Thanks,

Didn't know FSX made the difference. IMO you get the morse from a DME with just NAV1/NAV2 ID as well.
Not all planes have a Bendix KMA24-like panel with the separate button for DME as in the above pic.

Wim

[Goatman24]

Thanks for the good information. I've now only got the Com1 and MKR turned on and will see how it goes.

Mitch

[Firekitten]

For the record, this topic amuses me.

[Goatman24]

Must be a glitch in my FSX or Carenado Bonanza. I've got the settings set as stated above and am again getting the annoying beeping. Even set the far right dial to "Off" with no success.

Problem seems to be intermittent.

Mitch

[IronHand]

I enjoyed reading this. Back when i was young i can remember tooling around texas in a few different planes. 150, 172, ercoupe. Since i am also a ham radio operator it was a blast to see how quickly i could copy and locate the vor's adf's etc etc by listening to the morse code abbreviation then looking at the map. On a few cross country trips hunting a new vor or adf station was all part of the flight plan as well locating train tracks, rivers, lakes, towns. It was all such a blast. In FSX depending what airport i landed at last and was taking off from it just happens that the frequency will be one you used on the last flight. (if you didnt reset fsx) I always click Nav 1 audio on so i know when i have the ILS. A few times this has helped as i accidently selected the wrong ILS frequency. After hearing the correct ident for the ils and seeing the pfd and mfd spring to life, i select nav 1 audio to off.

It's better to break ground and head into the wind than to break wind and head into the ground.