Your forum account is not the same as the account used in the shop. They are completely separate accounts.
Problem programming LED on GF166
Hi,
I have a GF166A VRP (black model, with the double rotary knowb).
What I have that for a PMDG aircraft, the right button switches between COM1 and COM2, and if I press the left button, the selected COM radio is selected for transmission. To accomplish that I have 2 configurations, where in config1 the right button switches to config2 and vice versa. In config1 the left button sends event EVT_ACP_CAPT_MIC_VHF1 and in config2 ..VHF2. This works fine.
Now I would like the left LED to be lit if and only if the selected COM radio is also selected for transmission. So, in config1 the LED should be on if COM_TRANSMIT1 is true, and in config2 only if COM_TRANSMIT2 is true.
My assumption was that when the input is BUTTON_LEFT1, then the Light/Disp Data and Light Action fields would refer to the left LED in config1, and when BUTTON_LEFT2 is selected similarly for config2. However, this does not work. It looks like the LED's always refer to config1.
Can someone help me with this? (I hope the problem is clear, if not I will elaborate).
Thanks!
-Emile.
Comments
Assuming your are using the NGX, this variable is used for the Captains selected Mic:
DATA_CTLSTD_LIGHT_MIC_SELECTOR_LEFTwith values: 0=VHF1 1=VHF2 2=VHF3 3=HF1 4=HF2 5=FLT 6=SVC 7=PA
Best wishes
Steve
Indeed, that variable can be used too. However, the problem remains: there is no difference in light behavior between config1 and config2. Am I right in assuming that the input selector BUTTON_LEFT1 makes the Light Data and Light Action fields refer to the left LED in config1?
-Emile.
To summarize, my bindings are
BUTTON_LEFT1 -> DATA_CTLSTD_LIGHT_MIC_SELECTOR_LEFT -> ON -> 0
BUTTON_LEFT2 -> DATA_CTLSTD_LIGHT_MIC_SELECTOR_LEFT -> ON -> 1
BUTTON_RIGHT1 -> GF166_CONTROLS2
BUTTON_RIGHT2 -> GF166_CONTROLS1
DISPLAY_LEFT1 -> COM_ACTIVE_FREQUENCY1
DISPLAY_LEFT2 -> COM_ACTIVE_FREQUENCY2
I can verify that switching between configs works because the frequency in the left display changes from COM1 to COM2 but the LED does not change.
I'll have to look into over the weekend and see how to do what you want.
Best wishes
Steve
Hi Emile,
Looks like it cannot be done. PMDG have mapped COM TRANSMIT 1 and 2 to the MIC Selector buttons. The provided COMM variables provided by PMDG don't provide data for the COMM transmit buttons e.g.
DATA_CLTLSTD_LIGHT_MIC_SELECTOR_LEFT = MIC Selectors;
DATA_CLTLSTD_SWITCH_COMM_RECEIVER_LEFT = circular comm buttons.
Best wishes
Steve
Thanks for the investigation, but I do not agree with your findings.
I did some more experiments and found that the problem is not related to the COM functions at all. If I set the Light Data and Actions to show e.g. the NAV_SOUND1 or 2 activation, it only shows the NAV_SOUND1 activation, even if I switch to config2.
So I believe that either I don't understand the principle of the different GF166 configurations in combination with the Lights, or there is a bug in the GIT.
See the screenshots.
Best regards.
-Emile.
Hi Emile,
Even if there is a bug, which I will double check, the relevant data does not exist so you cannot do what you want to do with the NGX!
Best wishes
Steve
Hi Emile,
Having just tested the lights on different configs there is a bug.
In the next release, I'll fix the above and add a variable that will indicate which config is loaded. This will allow you to light an LED based on the config loaded and will emulate what you need to do with the NGX.
Best wishes
Steve
Thanks!
-Emile.
Hi Emile,
GF166 issues should be fixed now. See change log for details.
Best wishes
Steve
Thanks Steve, it works fine! However, I do get errors when starting GIT2.1.13.0 but I'll start a new topic for that.
-Emile.