New Mobiflight WASM

[MarkStallen]

It's now possible to write to LVARS with FSUIPC via the Mobiflight WASM. Here my .evt file in the FSUIPC directory :

[Events]
0=MobiFlight.A320_Neo_PFD_BTN_LS_1_
1=MobiFlight.A320_Neo_MFD_BTN_CSTR_1_
2=MobiFlight.A320_Neo_MFD_BTN_WPT_1_
3=MobiFlight.A320_Neo_MFD_BTN_VORD_1_
4=MobiFlight.A320_Neo_MFD_BTN_NDB_1_
5=MobiFlight.A320_Neo_MFD_BTN_ARPT_1_
6=MobiFlight.A320_Neo_MFD_BTN_TERRONND_1_
7=MobiFlight.A320NX_AUTOPILOT_LOC_MODE_ON_RELEASE
8=MobiFlight.A320NX_AUTOPILOT_LOC_MODE_ON_PRESS
9=MobiFlight.A320NX_AUTOPILOT_APPR_MODE_ON_RELEASE
10=MobiFlight.A320NX_AUTOPILOT_APPR_MODE_ON_PRESS
11=MobiFlight.XMLVAR_NAV_AID_SWITCH_L1_State_Off
12=MobiFlight.XMLVAR_NAV_AID_SWITCH_L1_State_ADF
13=MobiFlight.XMLVAR_NAV_AID_SWITCH_L1_State_VOR
14=MobiFlight.XMLVAR_NAV_AID_SWITCH_L2_State_Off
15=MobiFlight.XMLVAR_NAV_AID_SWITCH_L2_State_ADF
16=MobiFlight.XMLVAR_NAV_AID_SWITCH_L2_State_VOR
17=MobiFlight.XMLVAR_Baro1_Mode_QFE
18=MobiFlight.XMLVAR_Baro1_Mode_QNH
19=MobiFlight.XMLVAR_Baro1_Mode_STD
20=MobiFlight.A320_Neo_MFD_NAV_MODE_1_LS
21=MobiFlight.A320_Neo_MFD_NAV_MODE_1_VOR
22=MobiFlight.A320_Neo_MFD_NAV_MODE_1_NAV
23=MobiFlight.A320_Neo_MFD_NAV_MODE_1_ARC
24=MobiFlight.A320_Neo_MFD_NAV_MODE_1_PLAN
25=MobiFlight.A320_neo_MFD_Range_1_10
26=MobiFlight.A320_neo_MFD_Range_1_20
27=MobiFlight.A320_neo_MFD_Range_1_40
28=MobiFlight.A320_neo_MFD_Range_1_80
29=MobiFlight.A320_neo_MFD_Range_1_160
30=MobiFlight.A320_neo_MFD_Range_1_320
31=MobiFlight.A320_Neo_EXPEDITE_MODE_
32=MobiFlight.A320NX_METRIC_ALT_TOGGLE_ON_RELEASE
33=MobiFlight.A320NX_METRIC_ALT_TOGGLE_ON_PRESS
34=MobiFlight.XMLVAR_Autobrakes_Level_OFF
35=MobiFlight.XMLVAR_Autobrakes_Level_LOW
36=MobiFlight.XMLVAR_Autobrakes_Level_MED
37=MobiFlight.XMLVAR_Autobrakes_Level_MAX
38=MobiFlight.A32NX_BTN_TOCONFIG_OFF
39=MobiFlight.A32NX_BTN_TOCONFIG_ON

[John Dowson]

8 minutes ago, MarkStallen said:

It's now possible to write to LVARS with FSUIPC via the Mobiflight WASM. Here my .evt file in the FSUIPC directory :

Thats interesting! However, it looks like they are using individual events to update each lvar, no? And some have multiple events. e.g.

Quote

34=MobiFlight.XMLVAR_Autobrakes_Level_OFF
35=MobiFlight.XMLVAR_Autobrakes_Level_LOW
36=MobiFlight.XMLVAR_Autobrakes_Level_MED
37=MobiFlight.XMLVAR_Autobrakes_Level_MAX

Does this mean that the events don't take a parameter? Otherwise you could just have event MobiFlight.XMLVAR_Autobrakes_Level and determine the state by the parameter....

I haven't been keeping up on the latest MobiFlight developmets - I'll take a look at the weekend.

Thanks for reporting,

John

[MarkStallen]

You're true. You can't read the LVARS only write them. I keep a custom offset updated so that I can switch and use it for my homepanel like :

217=B66D0=3 P258,23,Cx010066D0,x04     -{offset byte set, offset 66D0}-
218=B66D0=2 P258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
219=B66D0=1 P258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
220=B66D0=0 P258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
221=B66D0=3 U258,23,Cx010066D0,x04     -{offset byte set, offset 66D0}-
222=B66D0=2 U258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
223=B66D0=1 U258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
224=B66D0=0 U258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
225=B66D0=3 P258,23,C32805,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_MAX}-
226=B66D0=3 U258,23,C32805,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_MAX}-
227=B66D0=4 P258,23,C32802,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}-
228=B66D0=4 U258,23,C32802,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}-
229=B66D0=4 P258,23,Cx010066D0,x00     -{offset byte set, offset 66D0}-
230=B66D0=4 U258,23,Cx010066D0,x00    -{offset byte set, offset 66D0}-

[MarkStallen]

Or with the EFIS knobs :

100=P256,11,Cx510066C0,x00070001     -{offset byte cyclic inc, offset 66C0 (Incr=1, Limit=7)}-
101=B66C0=0 P256,11,C32793,0     -{:MobiFlight.A320_neo_MFD_Range_1_10}-
102=B66C0=1 P256,11,C32794,1     -{:MobiFlight.A320_neo_MFD_Range_1_20}-
103=B66C0=2 P256,11,C32795,2     -{:MobiFlight.A320_neo_MFD_Range_1_40}-
104=B66C0=3 P256,11,C32796,3     -{:MobiFlight.A320_neo_MFD_Range_1_80}-
105=B66C0=4 P256,11,C32797,4     -{:MobiFlight.A320_neo_MFD_Range_1_160}-
106=B66C0=5 P256,11,C32798,5     -{:MobiFlight.A320_neo_MFD_Range_1_320}-
107=B66C0=6 P256,11,C32798,6      -{:MobiFlight.A320_neo_MFD_Range_1_320}-
108=B66C0=7 P256,11,Cx010066C0,x06     -{offset byte set, offset 66C0}-
110=P256,12,Cx610066C0,x00070001     -{offset byte cyclic dec, offset 66C0 (Decr=1, Limit=7)}-
111=B66C0=0 P256,12,C32793,0     -{:MobiFlight.A320_neo_MFD_Range_1_10}-
112=B66C0=1 P256,12,C32794,1     -{:MobiFlight.A320_neo_MFD_Range_1_20}-
113=B66C0=2 P256,12,C32795,2     -{:MobiFlight.A320_neo_MFD_Range_1_40}-
114=B66C0=3 P256,12,C32796,3     -{:MobiFlight.A320_neo_MFD_Range_1_80}-
115=B66C0=4 P256,12,C32797,4     -{:MobiFlight.A320_neo_MFD_Range_1_160}-
116=B66C0=5 P256,12,C32798,5     -{:MobiFlight.A320_neo_MFD_Range_1_320}-
117=B66C0=6 P256,12,C32798,6     -{:MobiFlight.A320_neo_MFD_Range_1_320}-
118=B66C0=7 P256,12,Cx010066C0,x00     -{offset byte set, offset 66C0}-