Wing42 Boeing 247D FSUIPC throttle binds

Discussion Hub Aircraft
, ,
21

Perfect explanation.
Yes the number one problem is to get the right Axis and Button settings (BZ in your screenshot)
This Joy# and Axis# setting is different between the joystick and controllers we use. even the USB-Port can change the Joy# value.

1 Like
22

You can also try EasyControls maybe at flightsim.to.

23

hi. I have been trying to set up my FSUIPC in the same way but for some reason the axis and offset doesn’t link up with the Lvars.
set lvar is working but it seems to be running on its default adress

[Profile.247]
1=Boeing 247D WAT

[LvarOffsets.Boeing]
0=L:ENG THROTTLE 1=UB0xA000
1=L:ENG THROTTLE 2=UB0xA001
2=L:ENG MIXTURE 1=UB0xA002
3=L:ENG MIXTURE 2=UB0xA003
4=L:ENG PROPELLER 1=UB0xA004
5=L:ENG PROPELLER 2=UB0xA005
6=L:LEVER OIL SHUTTER 1=UB0xA006
7=L:LEVER OIL SHUTTER 2=UB0xA007
8=L:LEVER CARBURETOR HEAT 1=UB0xA008
9=L:LEVER CARBURETOR HEAT 2=UB0xA008

[Axes.247]
RangeRepeatRate=10
0=AX,256,F,x0100A001,0,0,0,*0.0030518,+50	-{ FSUIPC: offset byte set, offset A001 }-
1=AY,256,F,x0100A000,0,0,0,*0.0030518,+50	-{ FSUIPC: offset byte set, offset A000 }-
2=AZ,256,F,x0100A003,0,0,0,*0.0030518,+50	-{ FSUIPC: offset byte set, offset A003 }-
3=AR,256,F,x0100A004,0,0,0,*0.0030518,+50	-{ FSUIPC: offset byte set, offset A004 }-
4=AU,256,F,x0100A002,0,0,0,*0.0030518,+50	-{ FSUIPC: offset byte set, offset A002 }-
5=AV,256,F,x0100A005,0,0,0,*0.0030518,+50	-{ FSUIPC: offset byte set, offset A005 }-
6=BX,256,D,8,0,0,0	-{ DIRECT: RightBrake }-
7=BY,256,D,7,0,0,0	-{ DIRECT: LeftBrake }-
8=BZ,256,D,3,0,0,0	-{ DIRECT: Rudder }-
9=CX,256,D,1,0,0,0	-{ DIRECT: Aileron }-
10=CY,256,D,2,0,0,0	-{ DIRECT: Elevator }-
11=EZ,256,F,x0100A007,0,0,0,*0.0030518,+50	-{ FSUIPC: offset byte set, offset A007 }-
12=ER,256,F,x0100A006,0,0,0,*0.0030518,+50	-{ FSUIPC: offset byte set, offset A006 }-
13=ES,256,F,x0100A008,0,0,0,*0.0030518,+50	-{ FSUIPC: offset byte set, offset A008 }-

[WAPI]
EnableWAPI=Yes

here is what I have.
The axis and offset were linked with FSUIPC. the issue is the Lvar offset doesn’t seem to be linking with the lvar and I dunno why.
if someone can help.
thanks

1 Like
24

Hi you have named the LVARS wrong [LvarOffsets.Boeing] must be changed to [LvarOffsets.247]
The name of your profile.

Also 9=L:LEVER CARBURETOR HEAT 2=UB0xA008 should be 9=L:LEVER CARBURETOR HEAT 2=UB0xA009
And the line
14=ES,256,F,x0100A009,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A009 }-
must be added for the LEVER CARBURETOR HEAT 2

25

thanks!!!

for the Level carburator heat 2 I did it on purpose as I want 1 axis for both lever.
not sure if it would work that way

26

Well I finally got the time to sit down and work it all out, and I’m pleased to say that I got it working, sort off…my axis are reverse but other than that it works.

Here’s my settings - note that I’m using separate profiles:

[Profile]
Created=31/01/2022 20:59:32

[LvarOffsets]
0=L:ENG THROTTLE 1=UB0xA000
1=L:ENG THROTTLE 2=UB0xA001
2=L:ENG PROPELLER 1=UB0xA002
3=L:ENG PROPELLER 2=UB0xA003
4=L:ENG MIXTURE 1=UB0xA004
5=L:ENG MIXTURE 2=UB0xA005

[Axes]
RangeRepeatRate=10
0=AX,256,D,7,0,0,0 -{ DIRECT: LeftBrake }-
1=AY,256,D,8,0,0,0 -{ DIRECT: RightBrake }-
2=AR,256,D,3,0,0,0 -{ DIRECT: Rudder }-
3=BX,256,D,1,0,0,0 -{ DIRECT: Aileron }-
4=BY,256,D,2,0,0,0 -{ DIRECT: Elevator }-
5=CX,256,F,x0100A001,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A001 }-
6=CY,256,F,x0100A000,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A000 }-
7=CZ,256,F,x0100A005,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A005 }-
8=CR,256,F,x0100A002,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A002 }-
9=CU,256,F,x0100A004,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A004 }-
10=CV,256,F,x0100A003,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A003 }-

[WAPI]
EnableWAPI=Yes

Anyone got any ideas why my axis are reversed?

27

Hi try this

1 Like
28

I used to think I was pretty good at this stuff but can’t get anything to move. :frowning:

LouP

29

So this is what I have so far. Just trying to get the throttles working to start but no go. I have a green check on the websocket server v0.3.4. When I go to MSFS variables, it says it is connected to MSFS but get 000 lvars what ever that means.

[INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.5.6 (WASM version 0.5.6)
[INFO]: Connected to MSFS
[INFO]: We have 000 lvars:

In FSUIPC7.ini:

[Profile.Boeing 247D]
1=Boeing 247D Lufthansa

[LvarOffsets.Boeing 247D]
0=L:ENG THROTTLE 1=UB0xA000
1=L:ENG THROTTLE 2=UB0xA001

[Axes.Boeing 247D]
RangeRepeatRate=10
0=AX,256,F,x0100A000,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A000 }-
1=AY,256,F,x0100A001,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A001 }-

[WAPI]
EnableWAPI=Yes

Thanks,
LouP

30

OK, got it all working. Decided to use SpadNext, much easier.

LouP

31

This looks very interesting but one thing I find strange is that everyone seems to be using an unsigned byte (UB) to hold the lvar value. This can only hold values 0-255 (which is why scaling is applied to the axis value). But is that really the range of values that these lvars hold? I suspect that at least some of them should be held and manipulated as word (2 bytes) or dword (4 bytes) values, and some maybe also signed…

John

32

Your right, but the axis are from 0 to 100 so Byte is all you need.
It’s a little bit of experiment to get the needed data type of the lvar you want to manipulate.

2 Likes
33

Yes, I think it depends on the aircraft/lvar being used. Just been looking at the HondaJet throttle lvars (confusingly named THROTTLE1_SET and THROTTLE2_SET) which take a range from -1 to +1, but as floating point numbers, so would need to be added as 4-byte F-type lvars…

John