Jump to content
The simFlight Network Forums

Phantom button activations at button midpoint


mryan75

Recommended Posts

Hi all,

I've just gotten an updated piston twin airplane, and most of the buttons on my Honeycomb Bravo did not need updating. But the fuel pumps don't work (they did with the previous version of the plane). What's odd is that when I'm in FSUIPC7 and flip the fuel pump switch up and down, there is a phantom button activation exactly at the midpoint. They button I am moving is button 65 1 & 2 (1 is up, 2 is down). As I flip the switch up and down, in the middle, two buttons are activated: D133 and D134.

I have nothing else bound, nothing else assigned to this button in MSFS itself. What gives? Also, the button that I'm trying to use (65 1 & 2 for the fuel pump) does not work.

Thanks!

Link to comment
Share on other sites

Buttons 134 a 135 are for the left most switch, and there is no button 65 - see 

 

Button numbers in FSUIPC go from 0-31, 32-39 are for the POV, and then from 132-227.

Can you please set logging for Buttons & Keys and Events, generate a log file showing your issue, and then attach your FSUIPC7.log file as well as your FSUIPC7.ini.

John

 

Link to comment
Share on other sites

You posted a continuation log - please don't do this, always attach a full log file as there is information I need to see. You should also exit FSUIPC7 before attaching a log file.

But your ini shows that you are still using the lua hidAlphaButtons and hidBravoButton scripts. These have not been needed for a long time, as FSUIPC has supported up to 128 buttons since v7.1.0. You should remove these scripts and update your assignments to use the actual button numbers rather than the virtual ones.

However, you do not have to do this, but you will see both the virtual and real button presses - the ones that you call  phantom. But this is not an issue as long as you are only assigning to the virtual ones.

As to your actual issue (fuel pumps not working) i would need to see a full log file, if you want to continue using the lua scripts.

Note also you should update your profiles to use substring matching, so change

Quote

[Profile.GA Single]
1=Cessna 152 Asobo Blue and Light Blue
2=Cessna 152 Asobo
3=Just Flight PA28 Warrior II F-GEDO
4=Cessna Skyhawk G1000 Asobo
5=Cessna Skyhawk 172Sp G1000 01 Livery
6=Cessna Skyhawk G1000 Swift Red and Sky Blue
7=Cessna Skyhawk G1000 Swift Blue and Green
8=Cessna Skyhawk G1000 WAT
9=Just Flight PA28 Warrior II Custom
10=Just Flight PA28 Warrior II LN-AAM
11=Just Flight PA28 Warrior II G-BOZI
 

to

Quote

[Profile.GA Single]
1=Cessna 152
2=Just Flight PA28 Warrior
3=Cessna Skyhawk

and

Quote

[Profile.Piston Twin]
1=Britten Norman Islander BN2BA TransAnguilla
2=Britten Norman Islander BN2BA TransAnguilla
3=Britten Norman Islander BN2BA VP-AAC
4=Asobo Baron G58
5=DA62 Asobo

to

Quote

[Profile.Piston Twin]
1=Britten Norman Islander BN2BA
2=Asobo Baron G58
3=DA62 Asobo

 

and

Quote

[Profile.TBM930]
1=TBM 930 GrayBlueBlack
2=TBM 930 Asobo TUNER4
3=TBM 930 Asobo TUNER3
4=TBM 930 Metallic Burgundy
5=TBM 930 Asobo WAT
6=TBM 930 Asobo
7=TBM 930 N930MR
 

to

Quote

[Profile.TBM930]
1=TBM 930

and

Quote

[Profile.C208 Grand Caravan]
1=Cessna 208B Grand Caravan EX - St Barth Commuter

to

Quote

[Profile.C208 Grand Caravan]
1=Cessna 208B Grand Caravan

John

Link to comment
Share on other sites

FSUIPC7.logThis is the log of me trying to set the buttons, along with my updated .ini file. I deleted the lua scripts, then deleted the virtual button presses, and tried to create new button presses. They seem to register in the .ini file, but nothing happens in the sim when I press them. I've tried toggles, I've tried the on/off's. I can't get the Avionics masters 1 and 2 to work, either, for that matter, but I'm guessing the same thing is wrong in both cases.

FSUIPC7.ini

Link to comment
Share on other sites

You still have some assignments to virtual buttons that should be removed (although these should not be having any affect):

Quote

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=P65,1,C66237,1     -{FUEL_PUMP}-
2=P65,2,C66237,0     -{FUEL_PUMP}-
3=P65,3,C66072,0     -{PITOT_HEAT_ON}-
4=P65,4,C66073,0     -{PITOT_HEAT_OFF}-
5=R65,11,C65548,0     -{MINUS}-
6=R65,13,C65549,0     -{PLUS}-
7=P65,14,C1126,0     -{nothing: no action}-
8=P65,12,C1126,0     -{nothing: no action}-

 

Your log also shows an error in your Rotaries.lua:

Quote

   137922 LUA.1: beginning "C:\FSUIPC7\Rotaries.lua"
   137937 LUA.1: Could not open HID
 

Other than that, your log shows the events being sent as assigned, although its difficult to tell as you have obviously changed your assignments when doing this, and I can only see the assignments as they were when you exited. It is always better to provide a matching FSUIPC7.ini and FSUIPC7.log file for each test.

Could you switch to using the Baron G58 for your tests - it is in the same profile as your Britten Norman Islander, and I can check/verify that here. In fact, I have just tested and all of the avionics master controls work - Toggle Avionics Master, Avionics Master 1 On/Off/Set, Avionics Master Set. So please try in that aircraft, or is this problem specific to the Britten Norman Islander?

Link to comment
Share on other sites

  • 4 weeks later...
On 9/1/2022 at 5:05 AM, John Dowson said:

You still have some assignments to virtual buttons that should be removed (although these should not be having any affect):

Your log also shows an error in your Rotaries.lua:

Other than that, your log shows the events being sent as assigned, although its difficult to tell as you have obviously changed your assignments when doing this, and I can only see the assignments as they were when you exited. It is always better to provide a matching FSUIPC7.ini and FSUIPC7.log file for each test.

Could you switch to using the Baron G58 for your tests - it is in the same profile as your Britten Norman Islander, and I can check/verify that here. In fact, I have just tested and all of the avionics master controls work - Toggle Avionics Master, Avionics Master 1 On/Off/Set, Avionics Master Set. So please try in that aircraft, or is this problem specific to the Britten Norman Islander?

Hi John,

Thanks for your time here. Just to confirm, should I delete any button command that has "P65" in it? Those are virtual buttons? I removed the ones you noted above, but I have more of them in my ini file, and I want to be sure I'm cleaning it up fully:
 

Quote

 

48=P65,3,C66341,1     -{TOGGLE_ELECT_FUEL_PUMP2}-
49=P65,4,C66341,0     -{TOGGLE_ELECT_FUEL_PUMP2}-
50=P65,5,C66494,1     -{TOGGLE_FUEL_VALVE_ENG1}-
51=P65,6,C66494,0     -{TOGGLE_FUEL_VALVE_ENG1}-
52=P65,7,C66495,1     -{TOGGLE_FUEL_VALVE_ENG2}-
53=P65,8,C66495,0     -{TOGGLE_FUEL_VALVE_ENG2}-
54=P65,13,C67271,1     -{PARKING_BRAKE_SET}-
55=P65,14,C67271,0     -{PARKING_BRAKE_SET}-

60=P65,1,C66340,1     -{TOGGLE_ELECT_FUEL_PUMP1}-
61=P65,2,C66339,0     -{TOGGLE_ELECT_FUEL_PUMP}-

 

So essentially I should delete all of the ones with P65 and recreate the actions with the actual button? I will wait on your answer before doing that, and then I will test in the G58.

Link to comment
Share on other sites

And FYI, I tried it in the Baron, and the fuel pumps work fine. Still no go in the Islander.

I cleaned up the .ini file per your comments above, got back in the Islander, and tried to set up the fuel pumps. Nada. So then I got in the Baron to test it, and with the settings that had not worked in the Islander, the fuel pumps in the Baron worked just fine. So I'm guessing it is specific to the Islander.

FSUIPC7.log FSUIPC7.ini

Link to comment
Share on other sites

On 9/26/2022 at 12:36 AM, mryan75 said:

And FYI, I tried it in the Baron, and the fuel pumps work fine. Still no go in the Islander.

I cleaned up the .ini file per your comments above, got back in the Islander, and tried to set up the fuel pumps. Nada. So then I got in the Baron to test it, and with the settings that had not worked in the Islander, the fuel pumps in the Baron worked just fine. So I'm guessing it is specific to the Islander.

Sounds like it - your log file shows that event being sent.

Try activating logging for Events, open the logging console window and switch the pumps in the virtual cockpit and see what is logged - if any event is logged, you can use that. If nothing is logged, you could try using lvars - list them to see what is available. If any look applicable, you could try using those.

Note that if you do find another method of controlling the fuel pumps, you would have to create a specific profile for this aircraft. To do this, manually remove the aircraft from the profile in the FSUIPC7.ini, then the next time you start MSFS/FSUIPC7 you can add the aircraft back to a new profile selecting 'new based on...' and then select its old profile. This will give you a new profile for that aircraft which will be a copy of the existing one, which you can then modify.

Note that here are quite a few issues with 7.3.8 since the release of SU10. I will be releasing 7.3.9 later today (hopefully!), and there is a beta currently available, 7.3.9i, over in the Announcements sub-forum.

John

Link to comment
Share on other sites

  • 2 weeks later...

Okay this is kind of odd. I created an Event log, which is too big to upload, and I think the reason is because it is just a constant stream of the following. If I open the console you see this, moving so fast you can't even really read it. So something odd is going on. So far as I know I don't have any of these events set up with FSUIPC. The "ELECT_FUEL_PUMP2_SET" event is me pressing the button on my Bravo (to no avail), the rest of it is just this endless stream of events.

3789453 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF
  3789453 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF
  3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE
  3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE
  3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE
  3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE
  3789453 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF
  3789453 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF
  3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE
  3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE
  3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE
  3789453 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE
  3789500 *** EVENT: Cntrl= 67053 (0x000105ed), Param= 0 (0x00000000) ELECT_FUEL_PUMP2_SET
  3789531 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF
  3789531 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF
  3789531 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE
  3789531 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE
  3789531 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE
  3789531 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE
  3789594 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF
  3789594 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF
  3789594 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE
  3789594 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE
  3789594 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE
  3789594 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE
  3789656 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF
  3789656 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF
  3789656 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE
  3789656 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE
  3789656 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE
  3789656 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE
  3789719 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF
  3789719 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF
  3789719 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE
  3789719 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE
  3789719 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE
  3789719 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE
  3789797 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF
  3789797 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF
  3789797 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE
  3789797 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE
  3789797 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE
  3789797 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE
  3789859 *** EVENT: Cntrl= 67193 (0x00010679), Param= 5 (0x00000005) FUELSYSTEM_PUMP_OFF
  3789859 *** EVENT: Cntrl= 67193 (0x00010679), Param= 6 (0x00000006) FUELSYSTEM_PUMP_OFF
  3789859 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 2 (0x00000002) FUELSYSTEM_VALVE_CLOSE
  3789859 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 1 (0x00000001) FUELSYSTEM_VALVE_CLOSE
  3789859 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 3 (0x00000003) FUELSYSTEM_VALVE_CLOSE
  3789859 *** EVENT: Cntrl= 67197 (0x0001067d), Param= 4 (0x00000004) FUELSYSTEM_VALVE_CLOSE

Link to comment
Share on other sites

15 hours ago, mryan75 said:

Okay this is kind of odd. I created an Event log, which is too big to upload, and I think the reason is because it is just a constant stream of the following. If I open the console you see this, moving so fast you can't even really read it. So something odd is going on. So far as I know I don't have any of these events set up with FSUIPC. The "ELECT_FUEL_PUMP2_SET" event is me pressing the button on my Bravo (to no avail), the rest of it is just this endless stream of events.

Many aircraft, especially add-ons, can continually emit such events (different for each aircraft) - these are just noise. You can ignore these by using the DontLogThese ini parameter, best used in your [Profile.xxx] section (where xxx is the name of the profile). See the Advanced User guide for details. Also check that you are using an empty profile in MSFS for you controllers in MSFS. You can mix-and-match assignments between MSFS and FSUIPC if you wish, but best to start with an empty profile in MSFS if assigning in FSUIPC.

 

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.