I have attempted to enable ADF #1 Ident sound in an otherwise working ADF radio gauge through use of a key event:

<Area Left="0" Top="0" Height="100" Width="100">   <Cursor Type="Hand"/>   <Click Event="RADIO_ADF_IDENT_ENABLE"/></Area>

which, when clicked, results in (A:ADF SOUND, bool) equal to 1, but for only one cycle. After the one cycle, it reverts to 0 where it started, and no ident sound is heard even though the ADF frequency is tuned to an NDB located adjacent to the airport.Any ideas how to enable ADF ident and ident sound? Or, am I just misunderstanding how ADF sound works?Thank you.

I have attempted to enable ADF #1 Ident sound in an otherwise working ADF radio gauge through use of a key event:

<Area Left="0" Top="0" Height="100" Width="100">   <Cursor Type="Hand"/>   <Click Event="RADIO_ADF_IDENT_ENABLE"/></Area>

which, when clicked, results in (A:ADF SOUND, bool) equal to 1, but for only one cycle. After the one cycle, it reverts to 0 where it started, and no ident sound is heard even though the ADF frequency is tuned to an NDB located adjacent to the airport.Any ideas how to enable ADF ident and ident sound? Or, am I just misunderstanding how ADF sound works?Thank you.

Does this behavior exist on all aircraft or just one? If just one, it could be that the particular aircraft has a gauge thatis repeatedly updating the ADF IDENT setting based on an internal L:Var that is set by a panel switch or some default value.Aside from that, I have no idea. Paul

Have you tried: (>K:RADIO_ADF_IDENT_TOGGLE) ??

Thank you both for the suggestions. You guys are experts and you're always willing to help. Everybody appreciates that.Fr. Bill - Yes I had tried RADIO_ADF_IDENT_TOGGLE, but, again, within a mouse Click Event:

<Area Left="0" Top="0" Height="100" Width="100">   <Cursor Type="Hand"/>   <Click Event="RADIO_ADF_IDENT_TOGGLE"/></Area>

No luck with this, either.Then, I thought about your suggestion (>K:RADIO_ADF_IDENT_TOGGLE) more carefully, pulled it out of the Mouse section, and stuck it in the Update section of my ADF radio gauge:

<Update>   1 (>K:RADIO_ADF_IDENT_ENABLE)   blah   blah   blah</Update>

And this works! (A:ADF SOUND, bool) now remains set to 1, and the NDB station ident is audible.Paul - could there still a conflict with another gauge in the panel that causes the reset of RADIO ADF IDENT back to 0 after one cycle when I use the mouse Click Event approach? Perhaps there is, but I am overwhelming that when I stick 1 (>K:RADIO_ADF_IDENT_ENABLE) in the Update section? I am not sure, but I will do a little experimenting. I have a full suite of FS9 vintage RXP gauges in this panel - is it possible that one of these is re-setting the ADF Ident value? I'll see.Thanks again!Bob

Bob, I use a gauge called "event logger" in both FS9 and FSX (2 different versions) to investigateproblems like what you were seeing.You simply install the gauge in a panel just like any other gauge and it will create a log fileof the events as they occur when you load/fly the aircraft. The event entries are time stampedso you can see how often a particular event is occurring.Look in the library here at Avsim for "event_logger.zip" and/or "fsx_event_logger.zip". Paul

Paul, you were exactly right. And it should have been obvious to me from the start.There is indeed a conflict with an existing gauge ... the RXP GMA340 Audio Panel. It has an ADF select button which, when pressed, enables ADF ident sound.So, I don't need to enable ADF sound in my ADF gauge to be able to hear the ident, Jean Luc already took care of that for me.Thanks again for your good detective instincts.Bob

There is indeed a conflict with an existing gauge ... the RXP GMA340 Audio Panel. It has an ADF select button which, when pressed, enables ADF ident sound.

Well, that's actually quite disturbing all by itself......as a properly coded GMA340 should NOT be "enforcing" anything at all. It should two two things only:1. monitor the state variable and illuminate the LED to indicate whether it is on or off2. toggle the event on or off based on user input (mouse click)It should not however force the event unless commanded to do so...Personally, I'd find another GMA340 or code/script my own (which of course I have). :(

Fr. Bill, In a real installation, the ADF receiver would control volume from inaudible to loud, but wiring to the cockpit speaker would route through the audio panel, would it not? So, I see your point that the RXP audio panel is not properly coded. But, I find that I am able to compensate for that by disabling ADF Ident ( 1 (>K:RADIO_ADF_IDENT_DISABLE) ) within my Update section whenever my ADF receiver power is OFF or the volume is set to LOW. Then, I force the Ident disable regardless of whether the ADF button is selected on the RXP audio panel.

I see your point that the RXP audio panel is not properly coded.

My apologies. Maybe I spoke too soon. RXP might have the right approach to this. If the audio panel is the last or only thing between the speaker and the ADF receiver, then if the audio panel ADF selector is pushed OFF, there should be no Ident sound regardless of any ADF receiver setting. In other words, the RXP audio panel gauge should force a RADIO_ADF_IDENT_DISABLE every cycle if it's ADF selector button is pushed OFF, and that's apparently just what it is doing.To accommodate my ADF receiver gauge that has a volume control, I find that I have to force a RADIO_ADF_IDENT_DISABLE every cycle within <Update> when the ADF receiver power or volume are off in order to prevent the RXP audio panel from sounding the Ident when it's ADF button is pushed in.

To accommodate my ADF receiver gauge that has a volume control, I find that I have to force a RADIO_ADF_IDENT_DISABLE every cycle within <Update> when the ADF receiver power or volume are off in order to prevent the RXP audio panel from sounding the Ident when it's ADF button is pushed in.

By doing so, you are (unknowingly perhaps) creating what is known as a "race condition" (continuous event firing) which will ultimately cause other gauge's or keyboard "Select" events to fail, such as selecting doors 2, 3 or 4, or engines 2, 3 or 4.For those with registered versions of Pete's FSUIPC, there is a specific option that will mitigate the "race condition," but it's a kludge fix for a problem that shouldn't exist in the first place!

By doing so, you are (unknowingly perhaps) creating what is known as a "race condition" (continuous event firing) which will ultimately cause other gauge's or keyboard "Select" events to fail, such as selecting doors 2, 3 or 4, or engines 2, 3 or 4.For those with registered versions of Pete's FSUIPC, there is a specific option that will mitigate the "race condition," but it's a kludge fix for a problem that shouldn't exist in the first place!

I'll add my concurrence to Fr. Bill's comments on the situation.In the past I have found a number of gauges that suffered from, for lack of a better description, "lazy programming".When I suspected that a gauge was emitting "KEY" events every cycle, needlessly, I tracked the gauge down using theevent logger utility and then either fixed the problem gauge, if it was an XML gauge, or disabled it and substituteda properly programmed gauge in it's place. Paul

Fr. Bill and Paul - Thanks for the enlightenment. I would have been oblivious to the race condition otherwise, and if something failed because of it, I would never have been able to figure out why.Fr. Bill, I'll take your advice and build my own audio panel.Thank you both again.

Fr. Bill, I'll take your advice and build my own audio panel.Thank you both again.

That would be the best option honestly.