Hello,

I am using the Logitech G Saitek Pro Radio Panel with the Fenix A320, via AAO.  The radios work perfectly, but I cannot get the transponder and QNH to work properly (on the XPDR position).

If I change the transponder code or QNH in the Sim, they update on the Radio Panel, but I cannot set them via the Panel.

AAO 2.81 b05

Saitek panels enabled, single click setting.

Thanks for any advice.

 

Most likely (=as usual) the Fenix is probably not reacting to the default events. See if you can find a script collection on flightsim dot to for the Fenix. Those are usually part of StreamDeck profiles or X-Touch templates. Disregard the assets that you don't need, all you want is a script file to import into AAO. Then you can assign the necessary scripts to the buttons on the RadioPanel.

I'm in exactly the same situation and came across this thread. I have the Streamdeck and have a working set of baro buttons there courtesy of AAO, so located the commands that are used in that script, FENIX_A3XX-EFIS_baro_INC & FENIX_A3XX-EFIS_baro_DEC and added them to the Saitek Panel Config Radio Panel events mapping them to RP_KOHL_UP and RP_KOHL_DOWN. Changing the QNH in the sim does change the value on the Saitek panel, but not vice versa. In the Edit RPN Scripts section under Fenix are the scripts

EFIS_baro_DEC

(L:E_FCU_EFIS1_BARO,·Number)·--·(>L:E_FCU_EFIS1_BARO,·Number)

and
EFIS_baro_INC

(L:E_FCU_EFIS1_BARO,·Number)·++·(>L:E_FCU_EFIS1_BARO,·Number)

which I presume are the instructions to send the input from the streamdeck buttons to the Fenix- question, is, how do I need to adapt these so they work on the Logitech radio panel as well?

 

(I haven't even contemplated the Transponder value yet as the variables look very different, given the touch pad on the Fenix and the dials on the radio Panel! Small steps first and the baro ref looks easier to solve!)

1 hour ago, AceAirstream said:

how do I need to adapt these so they work on the Logitech radio panel as well?

No need to adapt them, just assign the the scripts instead of the default events to RP_KOHL_UP and RP_KOHL_DOWN on the "Assign events for Radio Panel" dialog. Do this while you are in the cockpit, then save this change for the current aircraft using the "Apply to aircraft only" button. Do not use "Apply Globally", as this will override the events for good, and the baro will no longer work for other aircraft.

Personally I don't think that the transponder of the Fenix can be mapped to a rotary encoder. This aircraft doesn't allow access to internal variables, so the push-buttons are the only means of interaction. Trying to make a script that presses those buttons in the correct order for an incresing or decreasing XPDR digit is either hideously complex or completely impossible. One could try setting the transponder code directly, but I'm not sure that the plane will even react to that change (I guess not, because if it did, it would recognize the default events too).

Edited December 23, 20223 yr by Lorby_SI

OK, so about the transponder. It is obviously possible to tune the MSFS transponder with the Radio Panel even when the Fenix doesn't show this value. But it is not too hard to write scripts that will "type in" the MSFS transponder code into the Fenix transponder. I just tested this, and it works, but a lot can go wrong with this method. The moment you interfere by pressing XPDR - buttons in the cockpit with the mouse, the script will fail.

So the general idea is to use an autoscript that checks if the XPDR code has been changed, and if that is the case, it synchronizes the value with the Fenix. Or you do it with a button, after changing the code on the RadioPanel you click on a button or keyboard combo to fire that script.

The scripts themselves are quire simple:

First the script that is used for typing, called "Fenix-PressXpdrKey" (Group "Fenix", Scriptname "PressXpdrKey")
(L:Fenix-PressXpdrKey)·s0·
l0·1·==·if{·1·(>L:S_PED_ATC_1,·Number)·(WAIT:100)·0·(>L:S_PED_ATC_1,·Number)·}·
l0·2·==·if{·1·(>L:S_PED_ATC_2,·Number)·(WAIT:100)·0·(>L:S_PED_ATC_2,·Number)·}·
l0·3·==·if{·1·(>L:S_PED_ATC_3,·Number)·(WAIT:100)·0·(>L:S_PED_ATC_3,·Number)·}·
l0·4·==·if{·1·(>L:S_PED_ATC_4,·Number)·(WAIT:100)·0·(>L:S_PED_ATC_4,·Number)·}·
l0·5·==·if{·1·(>L:S_PED_ATC_5,·Number)·(WAIT:100)·0·(>L:S_PED_ATC_5,·Number)·}·
l0·6·==·if{·1·(>L:S_PED_ATC_6,·Number)·(WAIT:100)·0·(>L:S_PED_ATC_6,·Number)·}·
l0·7·==·if{·1·(>L:S_PED_ATC_7,·Number)·(WAIT:100)·0·(>L:S_PED_ATC_7,·Number)·}·
l0·0·==·if{·1·(>L:S_PED_ATC_0,·Number)·(WAIT:100)·0·(>L:S_PED_ATC_0,·Number)·}·

Second, the script that reads the MSFS transponder code and then types it. You can call this script whatever you want, but the first one MUST have exactly those group and script names.
(A:TRANSPONDER·CODE:1,·Seconds)·s0·
l0·1000·/·flr·(>K:Fenix-PressXpdrKey)·(WAIT:100)·
l0·1000·%·100·/·flr·(>K:Fenix-PressXpdrKey)·(WAIT:100)·
l0·100·%·10·/·flr·(>K:Fenix-PressXpdrKey)·(WAIT:100)·
l0·10·%·flr·(>K:Fenix-PressXpdrKey)·

Edited December 23, 20223 yr by Lorby_SI

49 minutes ago, Lorby_SI said:

No need to adapt them, just assign the the scripts instead of the default events to RP_KOHL_UP and RP_KOHL_DOWN on the "Assign events for Radio Panel" dialog. Do this while you are in the cockpit, then save this change for the current aircraft using the "Apply to aircraft only" button. Do not use "Apply Globally", as this will override the events for good, and the baro will no longer work for other aircraft.

 

Thanks for reply- tried this, both the simpler EFIS_baro_DEC and the more complex (L:E_FCU_EFIS1_BARO,·Number)·--·(>L:E_FCU_EFIS1_BARO,·Number). Both were able to display the transponder value from the sim, and change it when changed in the sim or on the Streamdeck AAO controlled buttons, but the rotary dials still can't change the transponder value in the sim.

I'm not too worried as I tend to use the Streamdeck more, but it would be good to have it working as the rotary dials are a little quicker. However others may be keen to get the Radio Panel fully working.

3 hours ago, AceAirstream said:

tried this

Tried what exactly? You are jumping from baro to transponder and back. I'm afraid you lost me there. What did you do exactly and how? There is no trick and no secret to the Baro, just assign the scripts to the proper RadioPanel events, using the Saitek Panel Setup dialogs described in the AAO manual.

As I've written above, it is not possible to change the transponder digits of the Fenix that easily. Using the default events, you are changing the actual simulator transponder code. But the Fenix developers simply forgot to read it back into their logic when it is changed from the outside. I am pretty sure that you are actually sqwaking what you have set on the Radio Panel, and the display in the Fenix is simply wrong. So you can only change it with the 0-7 buttons in the cockpit, either with the mouse or through my script that I posted above. 

 

Edited December 23, 20223 yr by Lorby_SI