MarkStallen

With a few buttons on my VrInsight combo I receive the following message : 292062 VRI command APLAPP- trapped as Joy 257 Btn 5 Release (Off) and no further action. (in Linda I assigned nothing) After that first push on the next pushes it acts like I wanted via the FSUIPC.ini 80=P257,5,C32866,0 -{:MobiFlight.A32NX.FCU_APPR_PUSH}- 81=U257,5,C32866,0 -{:MobiFlight.A32NX.FCU_APPR_PUSH}- I got the same with my LOC button and a few others. The other buttons on the VrInsight react immediately. How can I skip that first push without doing nothing.

In mobyflight the're also using kvars. Like K:A32NX.FCU_HDG_INC Can you use those too? What name should I use for the A32NX FBW .hvar file an the section for lvars in the ini file ?

Can't wait to access with FSUIPC 7

The offset 0C46 does not work with A320 FBW nor 0C47

I get a non-permission as I click on the announcement, oh wait via announcements it works

Can I download it somewhere. I would love to test it

Eureka, this really works. One small change in the LUA : LastAutoBrakePos = ipc.readUB("66D0") if ipcPARAM == LastAutoBrakePos then ipc.writeUB("2F80",1) ipc.writeUB("66D0",0) ipc.control(32802) elseif ipcPARAM == 1 then ipc.writeUB("2F80",0) ipc.writeUB("66D0",1) ipc.control(32803) elseif ipcPARAM == 2 teen ipc.writeUB("2F80",0) ipc.writeUB("66D0",2) ipc.control(32804) elseif ipcPARAM == 3 then ipc.writeUB("2F80",0) ipc.writeUB("66D0",3) ipc.control(32805) end

My first try with a LUA : in the ini file : 225=P258,23,CL4:R,3 226=U258,23,CL4:R,3 227=P258,22,CL4:R,2 228=U258,22,CL4:R,2 229=P258,21,CL4:R,1 230=U258,21,CL4:R,1 [LuaFiles] 1=ipcReady 2=LINDA 3=Geluid 4=Autobrake Lua autobrake : LastAutoBrakePos = ipc.readUB("66D0") if ipcPARAM = LastAutoBrakePos then ipc.writeUB("02F8",1) ipc.writeUB("66D0",0) ipc.control(32802) elseif ipcPARAM = 1 then ipc.writeUB("02F8",0) ipc.writeUB("66D0",1) ipc.control(32803) elseif ipcPARAM = 2 then ipc.writeUB("02F8",0) ipc.writeUB("66D0",2) ipc.control(32804) elseif ipcPARAM = 3 then ipc.writeUB("02F8",0) ipc.writeUB("66D0",3) ipc.control(32805) end

Yes, probably you can also create a lua for it, but I'm not fully proficient on that yet

What I also found is that setting the autobrake you push offset 02F8 from 1 to 0. Only then it works. After T/O and gear up this one is going back to 1. In that case you have to switch your custom offset back to 0 so that your lights go off. So I added also this offset (see 300-311). Now there's a problem. As soon as you hit your brakes 02F8 goes also to 1. As a solution I programmed in the ini that as I release my brakes 02F8 goes back to 0 (see 313 and 315) 300=B66D0>0 P258,21,Cx01002F80,x00 -{offset byte set, offset 2F80}- 301=B66D0=0 P258,21,Cx01002F80,x01 -{offset byte set, offset 2F80}- 302=B66D0>0 U258,21,Cx01002F80,x00 -{offset byte set, offset 2F80}- 303=B66D0=0 U258,21,Cx01002F80,x01 -{offset byte set, offset 2F80}- 304=B66D0>0 P258,22,Cx01002F80,x00 -{offset byte set, offset 2F80}- 305=B66D0=0 P258,22,Cx01002F80,x01 -{offset byte set, offset 2F80}- 306=B66D0>0 U258,22,Cx01002F80,x00 -{offset byte set, offset 2F80}- 307=B66D0=0 U258,22,Cx01002F80,x01 -{offset byte set, offset 2F80}- 308=B66D0>0 P258,23,Cx01002F80,x00 -{offset byte set, offset 2F80}- 309=B66D0=0 P258,23,Cx01002F80,x01 -{offset byte set, offset 2F80}- 310=B66D0>0 U258,23,Cx01002F80,x00 -{offset byte set, offset 2F80}- 311=B66D0=0 U258,23,Cx01002F80,x01 -{offset byte set, offset 2F80}- 313=PA,1,Cx01002F80,x00 -{offset byte set, offset 2F80}- 315=UA,1,Cx01002F80,x00 -{offset byte set, offset 2F80}-

I made an custom offset to trigger the lights (66D0). In my ini file like this : If this offset was the same as before then I set it to 4 and in the and back to zero (so you can push your autobrake settings on and off by pushing it twice. P258,23 and U258,23 is my MAX-button (with press and release I do the same) and P(U)258,22 is my MED and P(U)258,23 my LO 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}- 231=B66D0=2 P258,22,Cx010066D0,x04 -{offset byte set, offset 66D0}- 232=B66D0=3 P258,22,Cx010066D0,x02 -{offset byte set, offset 66D0}- 233=B66D0=1 P258,22,Cx010066D0,x02 -{offset byte set, offset 66D0}- 234=B66D0=0 P258,22,Cx010066D0,x02 -{offset byte set, offset 66D0}- 235=B66D0=2 U258,22,Cx010066D0,x04 -{offset byte set, offset 66D0}- 236=B66D0=3 U258,22,Cx010066D0,x02 -{offset byte set, offset 66D0}- 237=B66D0=1 U258,22,Cx010066D0,x02 -{offset byte set, offset 66D0}- 238=B66D0=0 U258,22,Cx010066D0,x02 -{offset byte set, offset 66D0}- 239=B66D0=2 P258,22,C32804,0 -{:MobiFlight.XMLVAR_Autobrakes_Level_MED}- 240=B66D0=2 U258,22,C32804,0 -{:MobiFlight.XMLVAR_Autobrakes_Level_MED}- 241=B66D0=4 P258,22,C32802,0 -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}- 242=B66D0=4 U258,22,C32802,0 -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}- 243=B66D0=4 P258,22,Cx010066D0,x00 -{offset byte set, offset 66D0}- 244=B66D0=4 U258,22,Cx010066D0,x00 -{offset byte set, offset 66D0}- 245=B66D0=1 P258,21,Cx010066D0,x04 -{offset byte set, offset 66D0}- 246=B66D0=3 P258,21,Cx010066D0,x01 -{offset byte set, offset 66D0}- 247=B66D0=2 P258,21,Cx010066D0,x01 -{offset byte set, offset 66D0}- 248=B66D0=0 P258,21,Cx010066D0,x01 -{offset byte set, offset 66D0}- 249=B66D0=1 U258,21,Cx010066D0,x04 -{offset byte set, offset 66D0}- 250=B66D0=3 U258,21,Cx010066D0,x01 -{offset byte set, offset 66D0}- 251=B66D0=2 U258,21,Cx010066D0,x01 -{offset byte set, offset 66D0}- 252=B66D0=0 U258,21,Cx010066D0,x01 -{offset byte set, offset 66D0}- 253=B66D0=1 P258,21,C32803,0 -{:MobiFlight.XMLVAR_Autobrakes_Level_LOW}- 254=B66D0=1 U258,21,C32803,0 -{:MobiFlight.XMLVAR_Autobrakes_Level_LOW}- 255=B66D0=4 P258,21,C32802,0 -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}- 256=B66D0=4 U258,21,C32802,0 -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}- 257=B66D0=4 P258,21,Cx010066D0,x00 -{offset byte set, offset 66D0}- 258=B66D0=4 U258,21,Cx010066D0,x00 -{offset byte set, offset 66D0}-

I've many buttons that must do the same on press and release, can you combine thoseso instead of 217=B66D0!3 P258,23,Cx010066D0,x03 -{offset byte set, offset 66D0}- 218=B66D0=3 P258,23,Cx010066D0,x04 -{offset byte set, offset 66D0}- 219=B66D0!3 U258,23,Cx010066D0,x03 -{offset byte set, offset 66D0}- 220=B66D0=3 U258,23,Cx010066D0,x04 -{offset byte set, offset 66D0}- replaced by 217=B66D0!3 UP258,23,Cx010066D0,x03 -{offset byte set, offset 66D0}- 218=B66D0=3 UP258,23,Cx010066D0,x04 -{offset byte set, offset 66D0}-

For the pop-outs I use Window Title changer and Win Layout manager. When I start-up I have to pop-out the panels all together after that pop-out apart and give them a name (1,2, 3--6) with Title changer. Then in lay-outmager I saved those names with their position and size so I can run that preset. Costs about one minut.

The chronometer and the landinggear and brake lights coming from a Visual Basic Program working with FSUIPC. Be sure that in your events.txt contains : XMLVAR_Autobrakes_Level_OFF#0 (>L:XMLVAR_Autobrakes_Level) XMLVAR_Autobrakes_Level_LOW#1 (>L:XMLVAR_Autobrakes_Level) XMLVAR_Autobrakes_Level_MED#2 (>L:XMLVAR_Autobrakes_Level) XMLVAR_Autobrakes_Level_MAX#3 (>L:XMLVAR_Autobrakes_Level) Then it works. (You can't give a parameter, but you have to use all the commands seperate)

Thanks

How to use the =not condition in the ini file. For instance : 217=B66D0=not3 P258,23,Cx010066D0,x04 217=B66D0not=3 P258,23,Cx010066D0,x04 217=B66D0not3 P258,23,Cx010066D0,x04 Don't work

Here they are : MSFS2020 - MobiFlight WASM Events - Google Spreadsheets for instance in events.txt in the community/mobiflight-event-module/modules: XMLVAR_Autobrakes_Level_MED#2 (>L:XMLVAR_Autobrakes_Level) A320_Neo_PFD_BTN_LS_1#(>H:A320_Neo_PFD_BTN_LS_1) in the evt-file call them with : XMLVAR_Autobrakes_Level_MED A320_Neo_PFD_BTN_LS_1 It's not possible to give a parameter by yourself. I'm using custom offsets to keep up. If you open op the aircraft behaviours in the developermode. Then you can find all LVars and Hvars used and put them in the events.txt and xxxx.evt als described above. Everything is now working on my DIY cockpit. All buttons, switches and roterary's. Lights like LDG gear and Auto brk etc. I programmed via Visual Basic and FSUIPC.

Put in mobiflight events.txt : A320_Neo_MFD_BTN_TERRONND_1#(>H:A320_Neo_MFD_BTN_TERRONND_1) and add A320_Neo_MFD_BTN_TERRONND_1 to your xxxx.evt

Got it : 297=PA,7,CL3:R,0 -{Lua Geluid}-

In my FSUIPC folder I got the file Geluid.lua : sound.play("Lufthansa",2) (Lufthansa.wav is also in the FSUIPC directory) In the FSUIPC ini I got under [LuaFiles]: 1=ipcReady 2=LINDA 3=Geluid and under [buttons] : 296=PA,7,L3:R It's probably not the right way, it doesn't work

Sorry found it in 0B46..

Transponderstate is a new event in MSFS 2020. How can I find this new event in FSUIPC (it's not in the list)

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}-

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}-

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