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.

Exit Lights won't illuminate

RayProudfootRayProudfoot
in GoFlight Interface Tool - Technical Support
Hi Steve,

I'm programming door exits on the Carenado PC12. There are two. A smaller one for pax and a larger one for baggage. Shift+E 1 opens the smaller and Shift+E 2 opens the larger one.

I have programmed those key commands into Detective and created two Bespoke Events. I then assigned one of them to a T8 switch for the front door - Exit 1.

The switch operates the door correctly but I cannot get the LED to illuminate. In the Light Data dropdown I have selected EXIT_OPEN1, Light Action is ON and Light Value is 1.

Monitoring FSUIPC Offset 3367 it correctly shows the value of the exit that is open - 1 - so the selection above seems correct. Any ideas why the LED won't illuminate when the door is open?

I'm using the 32-bit version of GIT because the PC12 is a 32-bit aircraft but fine in P3D v4.5 HF2. The 64-bit GIT couldn't connect to SimConnect presumably for that reason.
Cheers,
Ray (Cheshire, England)
«13

Comments

  • RayProudfootRayProudfoot
    A bit more info. I managed to get the larger baggage door light to work but only when Exit1 is used for the light status. I can’t get the smaller door light to work at all.

    Is it possible Carenado have messed up these exits inside the mdl file? There are two exits - 0 and 1. 0 is the one controlled by Shift+E and the 1 by Shift +E 2. But the light only comes on for exit 1 when EXIT_OPEN1 is used rather than EXIT_OPEN2.
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    It could be that the data hasn't changed. GIT only updates data when it changes, so if you have the door open and then set the light in GIT it won't come on. You would need to close the door, then open it to see anything happen.

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    Hi Steve. I have tried that numerous times. I’ve spent close to three hours trying to solve this problem which is ridiculous considering how simple the action is. I’m wondering if it’s related to TOGGLE EXIT rather than EXIT_OPEN and EXIT_CLOSE which don’t exist.

    I’ve programmed other actions for this aircraft and they’re fine. Just the flamin’ door light won’t work.
    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    Steve, could you please confirm how you would Program two T8 switches to operate Exit.0 and Exit.1. Just want to check I’m doing it correctly. Thanks.
    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    Steve,

    I reverted to a default aircraft in P3D v4.5. The Commander, to try and get the LED on the T8 to illuminate when a door is opened. I just can't get it to work. I've programmed a bespoke event to toggle the left exit. Shift+E 1. The door opens but the LED does not come on. Can you please explain how to make such a simple action work? I've programmed far more complex actions and they work fine. Just the default doors won't work as they should.

    I'm also baffled by the number of events recorded when Shift+E 1 is pressed. This is what GIT is recording. Any idea why so many commands are executed?

    0000000040 Event: 066389 Event Data: 000000 Event Name: TOGGLE_AIRCRAFT_EXIT
    0000000041 Event: 066514 Event Data: 000000 Event Name: ATC_MENU_CLOSE
    0000000042 Event: 066514 Event Data: 000000 Event Name: ATC_MENU_CLOSE
    0000000043 Event: 066389 Event Data: 000000 Event Name: TOGGLE_AIRCRAFT_EXIT
    0000000044 Event: 066514 Event Data: 000000 Event Name: ATC_MENU_CLOSE
    0000000045 Event: 066514 Event Data: 000000 Event Name: ATC_MENU_CLOSE
    0000000046 Event: 065538 Event Data: 000000 Event Name: SELECT_1
    0000000047 Event: 066514 Event Data: 000000 Event Name: ATC_MENU_CLOSE
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    Hi Ray,

    Is the lvar changing in Detective and staying changed?

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    Hi Steve. There is no Lvar for the aircraft exits. They operate purely on Shift+E followed by a number, 1 for the first exit and 2 for the baggage exit. As you list Exit1 - Exit9 in Events I would expect that would trigger the LED.

    Any idea why so many commands would be triggered by Shift+E as shown above?
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    What Simconnect variable are you using if its not an Lvar?
  • admin_ppsadmin_pps
    Scrub that. Just found it EXIT OPEN:index. If FSUIPC is showing this variable as an offset and its going to one, it must be some weird bug in GIT. I will take a look.

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    admin_pps said:

    Scrub that. Just found it EXIT OPEN:index. If FSUIPC is showing this variable as an offset and its going to one, it must be some weird bug in GIT. I will take a look.

    Best wishes
    Steve

    Thanks Steve. I didn't want to point the finger but that seems the only reason the LED won't illuminate. I even monitored the FSUIPC offset 3367 and it shows 1 when exit 1 is open, 2 when exit 2 is open and 3 when both are open. Hope that helps.

    Incidentally Steve, you need to amend the link to this topic sent in the email. There's no . between www and pollypotsoftware.org.uk
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    edited October 2019
    Hi Ray,

    For some reason Simconnect is not pushing the data out. It does it once, when the variable is requested and then completely ignores any changes and thus does not notify GIT that its changed. I'm not sure I can do anything about this. I guess FSUIPC is reading the direct memory location and not relying on Simconnect.

    All I can suggest at this point is to create a Bespoke Event that can read the FSUIPC offset. Name it Start and it should contain something along the lines of this so it loops continuously:

    :Start
    BespokeVar0 = ReadOffset(FSUIPC offset number here)
    Sleep(1000)
    Goto :Start

    And then assign BespokeVar0 as the light data on your T8 LED.

    Note that start Bespoke Event only runs when GIT first loads the aircraft, so you will need to quit GIT and start it again to get the start event running.

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    Hi Steve,

    Thanks for finding the problem and suggestion. Could you talk me through the buttons to press to create a Bespoke Event please? I'm assuming those at the bottom-right of Detective but not sure which.
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    edited October 2019
    Yes thats right. Label, then ReadOffset, then Sleep, then Goto

    Best wishes
    Steve

    PS Before clicking ReadOffset, select the BespokeVar0 at the top of the screen under the Bespoke Vars tab.
  • RayProudfootRayProudfoot
    Thanks Steve. I shall try that tomorrow and report back.
    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    Hi Steve,

    I'm struggling. I've created a new Bespoke Event and named it Start. I then select Bespoke Var0 from the Lvars box and press Set. It prompts me to enter a numeric value. Doesn't seem logical when I look at your code above. I remove that entry.

    If I select Bespoke Var0 and then press Set= a message appears saying to Select a Variable/Dataref above. But which one? Readoffset is not listed anywhere. I remove that entry.

    Finally, if I select Bespoke Var0 and then press Readoffset the field used to enter data is blank but the tick mark is enabled. If I press that 0000 appears. If I then enter 3367 (the offset required) and hit OK the entry reads:-

    Bespoke Var 0 = Readmem(3367).

    That doesn't seem right either. Can't fathom what to do, sorry.
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    Hi Ray,

    It should display a drop down list of read types but they are all blank. I'm guessing code obfuscation and messed up the list. I'll look into now.

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    Thanks Steve. I did wonder about the blank drop-down.
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    Ok, its fixed. I will PM you a link to download. Please uninstall your old version first as I haven't changed the version numbers so it may not update if not uninstalled.

    Best wishes
    Steve
  • RayProudfootRayProudfoot
    Thanks very much Steve. Uninstalling now. More to follow soon...
    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    Hi Steve,

    Installed new version and selection of FSUIPC type now available. The critical line is

    Bespoke Var 0 = ReadMemUB(3367).

    However, despite assigning the T8 switch to Bespoke Var0 whilst the pax door opens the led status doesn't change. Do we need a condition setting? 0 = both exits closed. 1 = Exit1 open. 2 = Exit2 open. 3 = Both Exits open. Those are the values when monitoring that offset.

    If 3367=0 then led = off else led = on.

    Thoughts?
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    edited October 2019
    Yes, on your T8 ON GREATER THAN 1
  • RayProudfootRayProudfoot
    edited October 2019
    admin_pps said:

    Yes, on your T8 ON GREATER THAN 1

    Surely greater than zero? But setting that still won't turn the LED on when the door is open and offset 3367 shows 1 when monitored and displayed in P3D title bar.

    Is there a way of checking this procedure is reading that offset correctly? Can it be displayed at all?

    Also added Start procedure just so you can check it's okay.
    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    Here's the start procedure.
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    You have remembered to quit GIT and restart it? It is greater than 1 as a value of 0 would turn it on for exit 1 as well 2(1 = Exit1 open)
  • RayProudfootRayProudfoot
    Steve,

    Can't follow your last comment, sorry. Yes, I have restarted GIT but despite trying all options the LED will not come on whether exit 1 is open or closed.

    Are you basing this on theory or have you coded it as I have and assigned it to a switch?

    Just to confirm I want LED to come on when door is open and go off when door is closed.
    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    I thought there might be a clue in the log but it looks okay...

    14:20:41 GoFlight Connection Starting.....
    14:20:41 SimConnect Connection Starting.....
    14:20:42 SimConnect Message Processing Started
    14:20:42 GoFlight Connection Started
    14:20:42 SimConnect Connection Started
    14:20:42 Aircraft Connection Starting.....
    14:20:42 SimConnect: Event Received: Aircraft Loaded/Flight Loaded
    14:20:42 SimConnect: Event Received: SIM, 1
    14:20:42 SimConnect: Event Received: PAUSE, 0
    14:20:45 WinSock: Connected To localhost On Port 27015!
    14:20:45 LUA Processor: Started!
    14:20:49 FSUIPC: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:8385
    14:20:49 Aircraft Connection Started
    14:20:49 Simconnect Version: 3.4.0.0
    14:20:49 Aircraft FullName: Carenado PC12
    14:20:49 Synchronising Switches & Selectors .....
    14:20:49 LvarNamesUpdated!
    14:20:49 Creating Bespoke Vars
    14:20:49 Bespoke Vars Created
    14:20:49 Importing Bespoke Variables
    14:20:49 Bespoke Vars Assigned, Importing Bespoke Events
    14:20:49 Bespoke Events Temp Imported
    14:20:49 Bespoke Events Imported
    14:20:49 Loading Aircraft Settings
    14:20:49 GetXMLConfigData
    14:20:49 GotXMLConfigData
    14:20:49 Loading Power
    14:20:49 Loading MCPPRO
    14:20:49 Loading MCP
    14:20:49 Loading EFIS
    14:20:49 Loading P8
    14:20:49 Loading T8
    14:20:49 Loading RP48
    14:20:49 Loading MESM
    14:20:49 Loading WP6
    14:20:49 Loading LGT
    14:20:49 Loading LGT II
    14:20:49 Loading GF46
    14:20:49 Loading GF45
    14:20:49 Loading TQ6
    14:20:49 Loading DIO
    14:20:49 Loading GF166
    14:20:49 Loading SECM
    14:20:49 Loading Joysticks
    14:20:49 Clearing Displays
    14:20:49 Reset Data
    14:20:49 Aircraft Settings Loaded
    14:20:49 Calling Aircraft Changed
    14:20:50 Aircraft Changed
    14:20:50 LvarNamesUpdated!
    14:20:50 Creating Bespoke Vars
    14:20:50 Bespoke Vars Created
    14:20:50 Importing Bespoke Variables
    14:20:50 Bespoke Vars Assigned, Importing Bespoke Events
    14:20:50 Bespoke Events Temp Imported
    14:20:50 Bespoke Events Imported
    14:20:50 Loading Aircraft Settings
    14:20:50 GetXMLConfigData
    14:20:50 GotXMLConfigData
    14:20:50 Loading Power
    14:20:50 Loading MCPPRO
    14:20:50 Loading MCP
    14:20:50 Loading EFIS
    14:20:50 Loading P8
    14:20:50 Loading T8
    14:20:50 Loading RP48
    14:20:50 Loading MESM
    14:20:50 Loading WP6
    14:20:50 Loading LGT
    14:20:50 Loading LGT II
    14:20:50 Loading GF46
    14:20:50 Loading GF45
    14:20:50 Loading TQ6
    14:20:50 Loading DIO
    14:20:50 Loading GF166
    14:20:50 Loading SECM
    14:20:50 Loading Joysticks
    14:20:50 Clearing Displays
    14:20:51 Reset Data
    14:20:51 Aircraft Settings Loaded
    14:20:51 Calling Aircraft Changed
    14:20:51 Aircraft Changed
    14:20:52 Synchronising Switches & Selectors Complete
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    14:20:49 FSUIPC: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:8385

    That's the problem. GIT hasn't been able to connect to FSUIPC. Try disabling your firewall to see if the port needs opening.
  • RayProudfootRayProudfoot
    I've turned off both private and public firewalls but still the problem persists...

    16:09:32 GoFlight Connection Starting.....
    16:09:32 SimConnect Connection Starting.....
    16:09:33 SimConnect Message Processing Started
    16:09:33 GoFlight Connection Started
    16:09:33 SimConnect Connection Started
    16:09:33 Aircraft Connection Starting.....
    16:09:33 SimConnect: Event Received: Aircraft Loaded/Flight Loaded
    16:09:33 SimConnect: Event Received: SIM, 1
    16:09:33 SimConnect: Event Received: PAUSE, 0
    16:09:36 WinSock: Connected To localhost On Port 27015!
    16:09:36 LUA Processor: Started!
    16:09:40 FSUIPC: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:8385
    16:09:40 Aircraft Connection Started

    Silly question but if all the other switches work and FSUIPC itself works where is the problem? If something wants to access via the Firewall I usually get a prompt to allow or deny. No such prompt has been seen.
    Cheers,
    Ray (Cheshire, England)
  • RayProudfootRayProudfoot
    I googled that message and all references pointed back here. Reading one of them the discussion references DLL.XML so I checked mine. There were two entries, not one for the GIT dll. Presumably because uninstalling and installing a new version created a duplicate.

    I removed the duplicate and fired up P3D and GIT. Still the same message. I even created a new entry in the approved programs in the firewall for GIT and checked private network only. Still no joy.

    So if I understand the problem correctly GIT is trying to read the offset in FSUIPC and the firewall is denying access. But why am I not even seeing a message asking if I want to allow access? Been there, done that for lots of other fs-related software. It really is frustrating.
    Cheers,
    Ray (Cheshire, England)
  • admin_ppsadmin_pps
    edited October 2019
    It may be that localhost is not accessible. Edit the file GoFlight Interface Tool P3Dv4.config in the your GIT program directory and you will find towards the bottom an FSUIPCHost entry with a value of localhost. Change localhost to your actual IP address.

    For this to take root, you will need to delete all directories located in C:\Users\Your Username\AppData\Local\PollyPot_Software

    Best wishes
    Steve
Sign In or Register to comment.

© Vanilla Keystone Theme 2025