GIT - do the GoFlight LEDs light up when switches are set?

RayProudfoot · February 2019

Hello all,

Please forgive the perhaps silly question. As a long-time user of GoFlight modules I'm disappointed at the limited number of commands available to me in the GF Config software when trying to program certain functions of 3rd party aircraft in particular the PMDG737-800.

Currently I am using a mixture of the GoFlight commands plus the PMDG SDK to program switches via FSUIPC5. For the most part they work but in order for the LED to light up there has to be an associated action selected in the GF Config software.

One action that is driving me mad is Master Battery. In a Cold and Dark PMDG737-800 the Battery light remains on on my GF-T8. However, if I delete that command in the GF software the LED doesn't illuminate when the battery is switched on. So in order to keep the LEDs on I have to have a selection associated with all my T8 switches. This limits me to what GF offer.

Does the GIT software overcome this problem? I'm primarily interested in it as I have the MCP-Pro and EFIS units which I haven't touched since Project Magenta days and would like to use those as well.

admin_pps · February 2019

Hello Ray,

There is no need to assign something to all T8 switches in GIT. You can configure the switches and lights independently of each other. So long as the PMDG events and variables exist for the Master Battery you should have no trouble with getting it going in GIT.

GIT auto configures the MCP PRO and EFIS for the PMDG NGX, 747 and 777. All you need to do is enable the devices in GIT.

Best wishes
Steve

RayProudfoot · February 2019

Thanks for your reply Steve. I can understand the mapping onto the MCP would be straight-forward as the controls are fixed.

Regarding assigning something to ALL T8 switches that was poorly worded by me. For the Battery I use a single switch. But unless I assign it to BATTERY in the GF Config software it doesn't illuminate when activated using the PMDG commands via FSUIPC Button presses. It stays off whether the battery is on or off.

What I need to know is does the LED light up on a T8 unit when asignments are made exclusively via your software?

Thanks,
Ray.

RayProudfoot · February 2019

Sorry Steve, one more question. The PMDG737-800 had dual Probe Heat switches. Using FSUIPC5 I can map both to a single GoFlight T8 switch. Is that possible with your GIT software?

admin_pps · February 2019

Hello Ray,

I have just checked the GIT source code and there is a variable for the battery switch called DATA_FWDOH_ELEC_SWITCH_BAT. Assigning that to the T8 LED will light it up when the switch is up.

There are a few built in events that control multiple switches - they are called Cluster events. The one you are after is called EVT_CLUSTER_PROBE_HEAT and this will flick both switches on or off. If a Cluster event does not exist for the switches you wish to use, then you can write a very short Lua script to do the job and use that in GIT.

Best wishes
Steve

RayProudfoot · February 2019

Hi Steve. Thanks for your reply. I’m not familiar with LUA so that’s another hurdle to overcome. Are the variables you mention related purely to the PMDG737 or all aircraft? Do you use PMDG’s SDK at all for their variable names to be associated with GIT?

Sorry if these seem odd questions. I’m just trying to get my head around how the whole process works. I had planned to buy GIT purely for the 737MCP but it seems it can do a whole lot more.

It’s just a case of understanding how the whole process works. Can you recommend any tutorials to beginners?

admin_pps · February 2019

Hi Ray,

The PMDG SDK is built into GIT for the NGX, 777 and 747. The PMDG events and variables have been given slightly different names as detailed here: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/19-operating/36-configuring-goflight-devices-additional-information-pmdg-ngx-77x-747x.html

GIT also has SDK support built in for iFly aircraft and the Majestic Q400.

The MCP PRO, MCP, EFIS, LGT, GF46, MESM are all auto configured for the PMDG and iFly.

For other aircraft Simconnect events and variables can be used, however you can create your own events called Bespoke Events. You build these for non Simconnect complaint aircraft so you can connect your GoFlight hardware to them. There is a facility called Detective that allows you to track down what variables (lvars) and custom events are changing when say a switch is flicked in the virtual cockpit. You then build a Bespoke Event to change the custom variables and/or events.

There is a beginners guide with videos by Rob Ainscough here: https://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/46-beginners-start-here/151-beginners-guide.html

Best wishes
Steve

RayProudfoot · February 2019

Thanks Steve. The integration of GIT with the PMDG SDK would appear to make life a whole lot easier.

I only fly a couple of other aircraft - Xtreme Prototype’s Lear25 and Carenado PC-12 and both of those are reasonably straight-forward. The love of my life is Concorde but until FS Labs bring out a 64-bit version I’ll have to stick with subsonic aircraft. In any case the GoFlight MCP is not compatible with that aircraft anyway.

I’ll watch Rob’s video, thanks.

admin_pps · February 2019

Hi Ray,

With GIT you may be able to get the Concorde to work by using Detective and creating Bespoke Events.

Best wishes
Steve

RayProudfoot · February 2019

Maybe with a few commands like Lights, p/brake etc but certainly not for the main autopilot unit which is completely different to Boeing and Airbus.

GIT - do the GoFlight LEDs light up when switches are set?

Comments