Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

A custom frequency flip-flop for the GF166

martin.smartin.s
in GoFlight Interface Tool - Technical Support
Hi Steve,

One more question for today :)

I have been experimenting with a custom NAV1 frequency flip-flop BE that uses the G166 BUTTON_CENTRE1 and incorporates some cockpit animations.

Here is the custom event:
BE_SAAB340A_NAV1_XFR_MEM_SWITCH (<==BE name)

JGX/SAAB/PLII_NAV1/ANM/xfr_mem_switch=1  (this animates the transfer switch to flick up)
Send 66271 (sim/radios/nav1_standby_flip)
Sleep 250
JGX/SAAB/PLII_NAV1/ANM/xfr_mem_switch=0 (animation to spring back after 250 ms)

This works perfectly with "Test Bespoke Event"

However it does not work when BE_SAAB340A_NAV1_XFR_MEM_SWITCH is mapped to the GF166's BUTTON_CENTRE1.

Not sure why.

Comments

  • admin_ppsadmin_pps

    That's weird. Are you sure you haven't got the GF166 in another mode so its actually sending CENTRE2 for example? Quit GIT, restart it and check the correct bespoke event has been assigned to the button. Watch what happens in Detective when you press the centre button to confirm its running.

    Best wishes

    Steve

  • martin.smartin.s
    I pretty sure its not in any other mode.

    In fact when I remap BUTTON_CENTRE1 back to sim/radios/nav1_standby_flip it immediately starts to work with activity in "Detective". Then when remapping BUTTON_CENTRE1 to the custom BE_SAAB340A_NAV1_XFR_MEM_SWITCH, nothing happens and there is no activity in "Detective". I have restarted GIT and the mapping to BE_SAAB340A_NAV1_XFR_MEM_SWITCH persists so its definitely set.
  • martin.smartin.s
    Perhaps I am not understanding what BUTTON_CENTRE1 - BUTTON_CENTRE4 actually means.

    This is my second GF166 (Device1) which "Identifies" with the correct LEDs lighting up. If I want to achieve something with NAV1 flip-flop I was of the assumption I map BUTTON_CENTRE1. For NAV2 its BUTTON_CENTRE2.

    If so, then what is the purpose of BUTTON_CENTRE3 and BUTTON_CENTRE4, when the GF166 can only emulate NAV1 through GF166_CONTROLS1 and NAV2 through GF166_CONTROLS2?
  • SlayerSlayer
    edited August 2016
    the additional buttons slots are used when you use the GF166_CONTOL_TOGGLE1_2 and 3_4 events.

    Basically it allows you to control up to 4 things and switch the displays and all of the buttons over to a completely different virtual device so you could say switch it to an ADF, a NAV2 or whatever.

    If you are only going to use 1 bank of that then you need to setup your display_left1 and display_right1  and all the associated buttons for that and just delete anything else in all the other slots.

    The best way to see how it all works it to load up the provided default radio profile and use a default aircraft and see how it all works together.   You don't have to stick to that format but it should teach you how all those additional slots work.
    Steve McNitt
  • martin.smartin.s
    Thank you for clearing that up Slayer.

    Getting back to the first comment in this thread, I have tried assigning BE_SAAB340A_NAV1_XFR_MEM_SWITCH to Button1 of the RP48B and it works perfectly.

    However, BE_SAAB340A_NAV1_XFR_MEM_SWITCH assigned to BUTTON_CENTRE1 of the GF166 has no effect. Other custom BEs I have defined also have no effect when mapped to this button.

    The GF166 button CENTER button appears to always default to the flip-flop role (sim/radios/nav1_standby_flip) regardless of what is actually assigned. It behaves as if that is hardcoded behaviour (or at least unable to be modified once the default config is accepted through the NAV button).
  • SlayerSlayer
    If center 2 3 4 etc have that control toggle function assignment you need to clear them otherwise it won't work . I did it like you are trying to do on the ixeg
    Steve McNitt
  • martin.smartin.s
    I don't quite understand why any settings for center 2,3,4 would impact how center 1 works when I am in mode 1. If I am in mode 1 and use the center button of the GF166 I assume I am invoking CENTER 1 (not center 2, 3 or 4).
  • SlayerSlayer
    I say to do that because if you don't clear them and you started with a default profile it would switch over to the other mode on the 2nd 3rd etc keypresses with no way to go back to your original  first bank of commands.
    Steve McNitt
Sign In or Register to comment.

© Vanilla Keystone Theme 2025