mryan75
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by mryan75
-
-
-
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 -
Thanks John, I appreciate your thoughtful responses and your time, as always. I will try a few things and see if I can figure it out.
-
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.
-
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:
Quote48=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.
-
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.
-
Thanks for the response, John, I have made the updates re: the lua files and will make the changes with the buttons and see how we do. Will report back. Thank you!
-
Sure John, thank you!FSUIPC7.logFSUIPC7.ini
-
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!
-
9 hours ago, John Dowson said:
You can scale the axis values - add ,*0.5 to the end of the axis assignment line in your FSUIPC7.ini. You can adjust the scaling value as needed - see the section Additional parameters to scale input axis values on page 41 of the Advanced User guide.
John
Many thanks, John!
-
7 hours ago, John Dowson said:
Why are you using the right hand side? Axes are assigned on the left hand side...try that...
You didn't need to do this - this is what I did to see what control to use. I mentioned that as that is how you determine what control to assign an axis or button to.
Sorry for the confusion, now I get it. I was looking for the axis under Send direct to FSUIPC Calibration, rather than Send to FS as Normal Axis. Now I see Anti Ice Gradual Set Eng1, and I can assign it and it works! One little issue is that it only uses the bottom half of the range of the Bravo axis. In other words, the lever all the way down is correctly carb heat on, but as I push the lever up, it goes to full in (ie carb heat off) only halfway up the axis.
Not really that big a deal, but it would be great if it used the full range of the axis.
-
On 6/15/2022 at 4:41 AM, John Dowson said:
You can assign to the axis control Anti Ice Gradual Set Eng1. You can see this is when you activate logging for Axis Controls, open the logging console and move the carb ice lever in the cockpit UI.
Hi John,
I genuinely tried doing this, following your instruction above and using the manual, to no avail. I activated the logging for Axis Controls, opened the logging console and moved the lever. It registered. I then went into the axis assignments and moved the axis I want to use, that seemed to have registered. I used Send to FS as Normal Axis. Then on the right side of the Axis Assignments panel I selected Anti Ice Gradual Set Eng1. I tried different ranges, from -16384 to 16384, and also using smaller ones, but I get no movement visually of the carb heat lever, and I turned on the engine and tried to use it in case maybe it just doesn't show an animation, but the action itself works, and I get nothing. The lever doesn't move, and the carb heat doesn't open and close.
Here is the relevant part from the ini file, and the file itself is attached. I would greatly appreciate any help you could give me.
[Axes.GA Single]
RangeRepeatRate=10
0=BX,256,D,1,0,0,0 -{ DIRECT: Aileron }-
1=BY,256,D,2,0,0,0 -{ DIRECT: Elevator }-
2=AX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }-
3=AY,256,D,8,0,0,0 -{ DIRECT: RightBrake }-
4=AR,256,D,3,0,0,0 -{ DIRECT: Rudder }-
5=DX,256,D,4,0,0,0 -{ DIRECT: Throttle }-
7=DZ,B,-16384,16383,67012,0 -{ Entering=ANTI_ICE_GRADUAL_SET_ENG1 }-
8=DR,256,D,6,0,0,0 -{ DIRECT: Mixture }- -
On 6/15/2022 at 4:41 AM, John Dowson said:
You can assign to the axis control Anti Ice Gradual Set Eng1. You can see this is when you activate logging for Axis Controls, open the logging console and move the carb ice lever in the cockpit UI.
Many thanks, John! I figured out a workaround the other day, but this sounds much better. Will report back.
-
Hi all,
I know I have an account here, but I can't get the password reset email.
Anyway, has anyone figured this out? To clear a few things up: you can get carb ice from around 20 degrees C down to -5 degrees C. Flying around at -20 degrees C will not produce carb ice. In real aircraft it is an axis. If you have a carb temperature gauge you would use it to bring the carb temp above freezing. If you don't have a carb ice gauge (and most small piston singles don't), you would put it full on if you suspect carb ice.
Either way, I'd like to map the carb ice setting to an unused axis on my HC Bravo just because it's more realistic to have it as an axis, even if I only really get full on or full off. That's fine, I just do want an axis. Though maybe one has come to being for carb ice in MSFS since this thread was last active.
I don't see any way to set carb ice at all in FSUIPC7. Any help would be appreciated.
Phantom button activations at button midpoint
in FSUIPC7 MSFS
Posted
I just created a super-quick log so you could see the log itself. This is like 2 seconds' worth of data.