Re: [Flightgear-devel] FG1000 ADF/DME option

[Wayne B. <kil...@co...>]

Hi Stuart, hope you had a great vacation! Thank you for the information.

>It looks like the KR87 uses a different set of properties under /instrumentation/kr-87/

With your information I double checked and the kr87 is publishing the correct properties and they are active. 

    instrumentation/adf/frequencies/selected-khz
    instrumentation/adf/in-range
    instrumentation/adf/indicated-bearing-deg
    instrumentation/adf/volume-norm
    instrumentation/adf/operable

Looking at the fg1000 properties, they all line up. It’s something else.
The ADF arrow is not animated even though /instrumentation/adf/indicated-bearing-deg and all the other associated properties are registering correctly in the property tree and active.

I’ve started to follow the animation logic but it is a bit complex and I think it might take me an excessively long time to trace through it. If you get a chance, could you either take a look or guide me as to what files to look at?

Wayne

From: Stuart Buchanan
Sent: Wednesday, July 26, 2023 10:14 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] FG1000 ADF/DME option

Hi Wayne,

On Thu, Jul 20, 2023 at 5:06 PM Wayne Bragg wrote:
I think this is mainly for Stuart,
 
I notice the FG1000 does not include the ADF/DME option, it would be between the CDI and XPDR  buttons. Yet it does have the option in the BRG choices and it does popup a (non-animated) bearing needle on the rose when activated. I added the KR87 radio along side the fg1000 so you could tune the ADF. The ADF bearing is active in the property tree.
 
Can you shed some light on this for us. Is it available? Maybe our ADF property doesn’t match what the fg1000 needs? Isn’t finished?
 
If it is not finished, is there something I can do to help.

Apologies for the delayed response - I've been on vacation.

I had a quick look at the code for this.  I suspect I never finished it nor tested it.

I can see two immediate issues that you should be able to fix yourself:

1) The properties mapping is incorrect, as you noticed.

The FG1000 is reading from the following properties (in Aircraft/Instruments-3d/FG1000/Nasal/Interfaces/GenericNavComPublisher.nas, line 104-108):

    obj._triggeredPublisher.addPropMap("ADFSelectedFreq", "/instrumentation/adf/frequencies/selected-khz");
    obj._periodicPublisher.addPropMap("ADFInRange", "/instrumentation/adf/in-range");
    obj._periodicPublisher.addPropMap("ADFHeadingDeg", "/instrumentation/adf/indicated-bearing-deg");
    obj._triggeredPublisher.addPropMap("ADFVolume", "/instrumentation/adf/volume-norm");
    obj._triggeredPublisher.addPropMap("ADFServiceable", "/instrumentation/adf/operable");

It looks like the KR87 uses a different set of properties under /instrumentation/kr-87/ 

Given that the KR87 is the only supported ADF, I think the correct solution here is to modify the FG1000 to use the correct properties.  You can edit the file reference above and send me a diff for merging.

2) It doesn't look like any values are being sent back from the FG1000 into the property tree.  It's unclear to me whether there should be any aspect of the KR87 that is controlled from the FG1000, except perhaps the audio controls from the GMA1347?

If we do need to pass back any values it would require updating Aircraft/Instruments-3d/FG1000/Nasal/Interfaces/GenericNavComUpdater.nas to map the Emesary message to the property.

Hope this helps and let me know if you have any questions.

-Stuart