MarkStallen Posted January 26, 2021 Report Share Posted January 26, 2021 Just found these : (not tested yet) [Events] 0=MobiFlight.XMLVAR_Baro_Selector_HPA_1 1=MobiFlight.A320_Neo_MFD_BTN_LS_1 2=MobiFlight.A320_Neo_MFD_BTN_CSTR_1 3=MobiFlight.A320_Neo_MFD_BTN_WPT_1 4=MobiFlight.A320_Neo_MFD_BTN_VORD_1 5=MobiFlight.A320_Neo_MFD_BTN_NDB_1 6=MobiFlight.A320_Neo_MFD_BTN_ARPT_1 7=MobiFlight.A320_Neo_MFD_NAV_MODE_1 8=MobiFlight.A320_neo_MFD_Range_1 9=MobiFlight.XMLVAR_NAV_AID_SWITCH_L1_State 10=MobiFlight.XMLVAR_NAV_AID_SWITCH_L2_State 11=MobiFlight.AP_MANAGED_SPEED_IN_MACH_TOGGLE 12=MobiFlight.A320_Neo_CDU_MODE_MANAGED_SPEED 13=MobiFlight.A320_Neo_CDU_MODE_SELECTED_SPEED 14=MobiFlight.A320_Neo_CDU_MODE_MANAGED_SPEED 15=MobiFlight.A320_Neo_FCU_MODE_MANAGED_SPEED 16=MobiFlight.A320_Neo_CDU_MODE_SELECTED_SPEED 17=MobiFlight.A32NX_TRK_FPA_MODE_ACTIVE 18=MobiFlight.A320NX_AUTOPILOT_LOC_MODE 19=MobiFlight.A320NX_AUTOPILOT_APPR_MODE 20=MobiFlight.A320_Neo_EXPEDITE_MODE 21=MobiFlight.A320NX_METRIC_ALT_TOGGLE 22=MobiFlight.XMLVAR_Autopilot_Altitude_Increment 23=MobiFlight.XMLVAR_Baro_Selector_HPA_2 24=MobiFlight.A320_Neo_MFD_BTN_LS_2 25=MobiFlight.A320_Neo_MFD_BTN_CSTR_2 26=MobiFlight.A320_Neo_MFD_BTN_WPT_2 27=MobiFlight.A320_Neo_MFD_BTN_VORD_2 28=MobiFlight.A320_Neo_MFD_BTN_NDB_2 29=MobiFlight.A320_Neo_MFD_BTN_ARPT_2 30=MobiFlight.A320_Neo_MFD_NAV_MODE_2 31=MobiFlight.A320_neo_MFD_Range_2 32=MobiFlight.XMLVAR_NAV_AID_SWITCH_R1_State 33=MobiFlight.XMLVAR_NAV_AID_SWITCH_R2_State 1 Link to comment Share on other sites More sharing options...
MarkStallen Posted January 26, 2021 Author Report Share Posted January 26, 2021 And these: [Events] 0=MobiFlight.A320_Neo_CDU_1_BTN_DIR 1=MobiFlight.A320_Neo_CDU_1_BTN_PROG 2=MobiFlight.A320_Neo_CDU_1_BTN_PERF 3=MobiFlight.A320_Neo_CDU_1_BTN_INIT 4=MobiFlight.A320_Neo_CDU_1_BTN_DATA 5=MobiFlight.A320_Neo_CDU_1_BTN_FPLN 6=MobiFlight.A320_Neo_CDU_1_BTN_RAD 7=MobiFlight.A320_Neo_CDU_1_BTN_FUEL 8=MobiFlight.A320_Neo_CDU_1_BTN_SEC 9=MobiFlight.A320_Neo_CDU_1_BTN_ATC 10=MobiFlight.A320_Neo_CDU_1_BTN_MENU 11=MobiFlight.A320_Neo_CDU_1_BTN_AIRPORT 12=MobiFlight.A320_Neo_CDU_1_BTN_UARROW 13=MobiFlight.A320_Neo_CDU_1_BTN_DARROW 14=MobiFlight.A320_Neo_CDU_1_BTN_LARROW 15=MobiFlight.A320_Neo_CDU_1_BTN_RARROW 16=MobiFlight.A320_Neo_CDU_1_BTN_L1 17=MobiFlight.A320_Neo_CDU_1_BTN_L2 18=MobiFlight.A320_Neo_CDU_1_BTN_L3 19=MobiFlight.A320_Neo_CDU_1_BTN_L4 20=MobiFlight.A320_Neo_CDU_1_BTN_L5 21=MobiFlight.A320_Neo_CDU_1_BTN_L6 22=MobiFlight.A320_Neo_CDU_1_BTN_R1 23=MobiFlight.A320_Neo_CDU_1_BTN_R2 24=MobiFlight.A320_Neo_CDU_1_BTN_R3 25=MobiFlight.A320_Neo_CDU_1_BTN_R4 26=MobiFlight.A320_Neo_CDU_1_BTN_R5 27=MobiFlight.A320_Neo_CDU_1_BTN_R6 28=MobiFlight.A320_Neo_CDU_1_BTN_A 29=MobiFlight.A320_Neo_CDU_1_BTN_B 30=MobiFlight.A320_Neo_CDU_1_BTN_C 31=MobiFlight.A320_Neo_CDU_1_BTN_D 32=MobiFlight.A320_Neo_CDU_1_BTN_E 33=MobiFlight.A320_Neo_CDU_1_BTN_F 34=MobiFlight.A320_Neo_CDU_1_BTN_G 35=MobiFlight.A320_Neo_CDU_1_BTN_H 36=MobiFlight.A320_Neo_CDU_1_BTN_I 37=MobiFlight.A320_Neo_CDU_1_BTN_J 38=MobiFlight.A320_Neo_CDU_1_BTN_K 39=MobiFlight.A320_Neo_CDU_1_BTN_L 40=MobiFlight.A320_Neo_CDU_1_BTN_M 41=MobiFlight.A320_Neo_CDU_1_BTN_N 42=MobiFlight.A320_Neo_CDU_1_BTN_O 43=MobiFlight.A320_Neo_CDU_1_BTN_P 44=MobiFlight.A320_Neo_CDU_1_BTN_Q 45=MobiFlight.A320_Neo_CDU_1_BTN_R 46=MobiFlight.A320_Neo_CDU_1_BTN_S 47=MobiFlight.A320_Neo_CDU_1_BTN_T 48=MobiFlight.A320_Neo_CDU_1_BTN_U 49=MobiFlight.A320_Neo_CDU_1_BTN_V 50=MobiFlight.A320_Neo_CDU_1_BTN_W 51=MobiFlight.A320_Neo_CDU_1_BTN_X 52=MobiFlight.A320_Neo_CDU_1_BTN_Y 53=MobiFlight.A320_Neo_CDU_1_BTN_Z 54=MobiFlight.A320_Neo_CDU_1_BTN_1 55=MobiFlight.A320_Neo_CDU_1_BTN_2 56=MobiFlight.A320_Neo_CDU_1_BTN_3 57=MobiFlight.A320_Neo_CDU_1_BTN_4 58=MobiFlight.A320_Neo_CDU_1_BTN_5 59=MobiFlight.A320_Neo_CDU_1_BTN_6 60=MobiFlight.A320_Neo_CDU_1_BTN_7 61=MobiFlight.A320_Neo_CDU_1_BTN_8 62=MobiFlight.A320_Neo_CDU_1_BTN_9 63=MobiFlight.A320_Neo_CDU_1_BTN_DOT 64=MobiFlight.A320_Neo_CDU_1_BTN_PLUSMINUS 65=MobiFlight.A320_Neo_CDU_1_BTN_SP 66=MobiFlight.A320_Neo_CDU_1_BTN_SLASH 67=MobiFlight.A320_Neo_CDU_1_BTN_OVFY 68=MobiFlight.A320_Neo_CDU_1_BTN_CLR Link to comment Share on other sites More sharing options...
MarkStallen Posted January 26, 2021 Author Report Share Posted January 26, 2021 And offcourse: [Events] 0=MobiFlight.A320_Neo_CDU_2_BTN_DIR 1=MobiFlight.A320_Neo_CDU_2_BTN_PROG 2=MobiFlight.A320_Neo_CDU_2_BTN_PERF 3=MobiFlight.A320_Neo_CDU_2_BTN_INIT 4=MobiFlight.A320_Neo_CDU_2_BTN_DATA 5=MobiFlight.A320_Neo_CDU_2_BTN_FPLN 6=MobiFlight.A320_Neo_CDU_2_BTN_RAD 7=MobiFlight.A320_Neo_CDU_2_BTN_FUEL 8=MobiFlight.A320_Neo_CDU_2_BTN_SEC 9=MobiFlight.A320_Neo_CDU_2_BTN_ATC 10=MobiFlight.A320_Neo_CDU_2_BTN_MENU 11=MobiFlight.A320_Neo_CDU_2_BTN_AIRPORT 12=MobiFlight.A320_Neo_CDU_2_BTN_UARROW 13=MobiFlight.A320_Neo_CDU_2_BTN_DARROW 14=MobiFlight.A320_Neo_CDU_2_BTN_LARROW 15=MobiFlight.A320_Neo_CDU_2_BTN_RARROW 16=MobiFlight.A320_Neo_CDU_2_BTN_L1 17=MobiFlight.A320_Neo_CDU_2_BTN_L2 18=MobiFlight.A320_Neo_CDU_2_BTN_L3 19=MobiFlight.A320_Neo_CDU_2_BTN_L4 20=MobiFlight.A320_Neo_CDU_2_BTN_L5 21=MobiFlight.A320_Neo_CDU_2_BTN_L6 22=MobiFlight.A320_Neo_CDU_2_BTN_R1 23=MobiFlight.A320_Neo_CDU_2_BTN_R2 24=MobiFlight.A320_Neo_CDU_2_BTN_R3 25=MobiFlight.A320_Neo_CDU_2_BTN_R4 26=MobiFlight.A320_Neo_CDU_2_BTN_R5 27=MobiFlight.A320_Neo_CDU_2_BTN_R6 28=MobiFlight.A320_Neo_CDU_2_BTN_A 29=MobiFlight.A320_Neo_CDU_2_BTN_B 30=MobiFlight.A320_Neo_CDU_2_BTN_C 31=MobiFlight.A320_Neo_CDU_2_BTN_D 32=MobiFlight.A320_Neo_CDU_2_BTN_E 33=MobiFlight.A320_Neo_CDU_2_BTN_F 34=MobiFlight.A320_Neo_CDU_2_BTN_G 35=MobiFlight.A320_Neo_CDU_2_BTN_H 36=MobiFlight.A320_Neo_CDU_2_BTN_I 37=MobiFlight.A320_Neo_CDU_2_BTN_J 38=MobiFlight.A320_Neo_CDU_2_BTN_K 39=MobiFlight.A320_Neo_CDU_2_BTN_L 40=MobiFlight.A320_Neo_CDU_2_BTN_M 41=MobiFlight.A320_Neo_CDU_2_BTN_N 42=MobiFlight.A320_Neo_CDU_2_BTN_O 43=MobiFlight.A320_Neo_CDU_2_BTN_P 44=MobiFlight.A320_Neo_CDU_2_BTN_Q 45=MobiFlight.A320_Neo_CDU_2_BTN_R 46=MobiFlight.A320_Neo_CDU_2_BTN_S 47=MobiFlight.A320_Neo_CDU_2_BTN_T 48=MobiFlight.A320_Neo_CDU_2_BTN_U 49=MobiFlight.A320_Neo_CDU_2_BTN_V 50=MobiFlight.A320_Neo_CDU_2_BTN_W 51=MobiFlight.A320_Neo_CDU_2_BTN_X 52=MobiFlight.A320_Neo_CDU_2_BTN_Y 53=MobiFlight.A320_Neo_CDU_2_BTN_Z 54=MobiFlight.A320_Neo_CDU_2_BTN_1 55=MobiFlight.A320_Neo_CDU_2_BTN_2 56=MobiFlight.A320_Neo_CDU_2_BTN_3 57=MobiFlight.A320_Neo_CDU_2_BTN_4 58=MobiFlight.A320_Neo_CDU_2_BTN_5 59=MobiFlight.A320_Neo_CDU_2_BTN_6 60=MobiFlight.A320_Neo_CDU_2_BTN_7 61=MobiFlight.A320_Neo_CDU_2_BTN_8 62=MobiFlight.A320_Neo_CDU_2_BTN_9 63=MobiFlight.A320_Neo_CDU_2_BTN_DOT 64=MobiFlight.A320_Neo_CDU_2_BTN_PLUSMINUS 65=MobiFlight.A320_Neo_CDU_2_BTN_SP 66=MobiFlight.A320_Neo_CDU_2_BTN_SLASH 67=MobiFlight.A320_Neo_CDU_2_BTN_OVFY 68=MobiFlight.A320_Neo_CDU_2_BTN_CLR Link to comment Share on other sites More sharing options...
John Dowson Posted January 26, 2021 Report Share Posted January 26, 2021 Please note that many of the new events you initially listed are not yet released, according to the spreadsheet available here: https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454 Link to comment Share on other sites More sharing options...
roarkr Posted January 26, 2021 Report Share Posted January 26, 2021 I am a little confused. Can someone enlighten me to understand. With these new events in the lists above. Do I need an updated WASM module? Where can I find that? Or is the already released WASM compatible with this new events? Link to comment Share on other sites More sharing options...
John Dowson Posted January 26, 2021 Report Share Posted January 26, 2021 12 minutes ago, roarkr said: I am a little confused. Can someone enlighten me to understand. With these new events in the lists above. Do I need an updated WASM module? Where can I find that? Or is the already released WASM compatible with this new events? If they are new, I would think that there would be an updated WASM module release. Have you (or anyone) checked? As I said, those new events may not yet be released, according to the spreadsheet. Maybe you will find more information on this on the MobiFlight forums? John Link to comment Share on other sites More sharing options...
asessa Posted January 26, 2021 Report Share Posted January 26, 2021 Good news we have custom event for the A320NX. 15 minutes ago, roarkr said: I am a little confused. Can someone enlighten me to understand. With these new events in the lists above. Do I need an updated WASM module? Where can I find that? Or is the already released WASM compatible with this new events? You can use in different way : directly via MF or via wasm if you want use fsuipc events Link to comment Share on other sites More sharing options...
asessa Posted January 26, 2021 Report Share Posted January 26, 2021 6 minutes ago, John Dowson said: If they are new, I would think that there would be an updated WASM module release. Have you (or anyone) checked? As I said, those new events may not yet be released, according to the spreadsheet. Maybe you will find more information on this on the MobiFlight forums? John This events are also listed by MF , in MSFS2020 events . You have to download 7.0.16 beta Link to comment Share on other sites More sharing options...
MarkStallen Posted January 26, 2021 Author Report Share Posted January 26, 2021 2=MobiFlight.A320_Neo_MFD_BTN_CSTR_13=MobiFlight.A320_Neo_MFD_BTN_WPT_14=MobiFlight.A320_Neo_MFD_BTN_VORD_15=MobiFlight.A320_Neo_MFD_BTN_NDB_16=MobiFlight.A320_Neo_MFD_BTN_ARPT_1 are working Also the CDU-buttons are working. All other no luck yet. Like the mentioned spreadsheet 1 Link to comment Share on other sites More sharing options...
MarkStallen Posted January 27, 2021 Author Report Share Posted January 27, 2021 I would like to work ahead and trying to figure out how I can implement some events when they are released. Maybe you can help me to get started, because I tried to understand your advanced quide and tutorials. But I don't know how to start. Must it be done in the ini-file, via a macro or a lua script. For instance : 8=MobiFlight.A320_neo_MFD_Range_1 will be an event with parameters from 0 to 6 I use a vrinsight MCP combo with a rotary-switch for this range turning to the right/and left is in the ini 32=P256,11,C32776,0 -{:MobiFlight.A320_neo_MFD_Range_1}- 33=P256,12,C32776,0 -{:MobiFlight.A320_neo_MFD_Range_1}- Is it true that if i knew the offset (example WXXXX) of the current range setting (0-6) that i could program in the ini something like : 32=WXXXX=0 P256,11,C32776,1 33=WXXXX=1 P256,11,C32776,2 34=WXXXX=2 P256,11,C32776,3 etc XX=WXXXX=5 P256,11,C32776,6 and 36=WXXXX=6 P256,12,C32776,5 37=WXXXX=5 P256,12,C32776,4 38=WXXXX=4 P256,12,C32776,3 etc XX=WXXXX=1 P256,12,C32776,0 Or is there an sollution without knowing the offset. I hope somebody can help me out. Link to comment Share on other sites More sharing options...
MarkStallen Posted January 27, 2021 Author Report Share Posted January 27, 2021 Could this work in the ini? 100=P256,11,Cx510066C0,x00060001 101=B66C0=0 P256,11,C32776,0 102=B66C0=1 P256,11,C32776,1 103=B66C0=2 P256,11,C32776,2 104=B66C0=3 P256,11,C32776,3 105=B66C0=4 P256,11,C32776,4 106=B66C0=5 P256,11,C32776,5 107=B66C0=6 P256,11,C32776,6 110=P256,12,Cx610066C0,x00060001 111=B66C0=0 P256,12,C32776,0 112=B66C0=1 P256,12,C32776,1 113=B66C0=2 P256,12,C32776,2 114=B66C0=3 P256,12,C32776,3 115=B66C0=4 P256,12,C32776,4 116=B66C0=5 P256,12,C32776,5 117=B66C0=6 P256,12,C32776,6 Link to comment Share on other sites More sharing options...
John Dowson Posted January 27, 2021 Report Share Posted January 27, 2021 1 hour ago, MarkStallen said: Is it true that if i knew the offset (example WXXXX) of the current range setting (0-6) that i could program in the ini something like : 32=WXXXX=0 P256,11,C32776,1 33=WXXXX=1 P256,11,C32776,2 34=WXXXX=2 P256,11,C32776,3 etc Yes, that should work - two buttons, one cycling up through the values and the other down. 16 minutes ago, MarkStallen said: Could this work in the ini? 100=P256,11,Cx510066C0,x00060001 101=B66C0=0 P256,11,C32776,0 Looks ok - did you try it? That (i.e. the offset cycle control) is new to me as well - had to look it up! Another way of achieving this would be to use a lua script, where you can maintain a local variable to hold the current state and then send the appropriate command and parameter on a button press depending upon this state. Link to comment Share on other sites More sharing options...
MarkStallen Posted January 27, 2021 Author Report Share Posted January 27, 2021 This works perfectly 100=P256,11,Cx510066C0,x00070001 -{offset byte cyclic inc, offset 66C0 (Incr=1, Limit=7)}- 101=B66C0=0 P256,11,C32776,0 -{:MobiFlight.A320_neo_MFD_Range_1}- 102=B66C0=1 P256,11,C32776,1 -{:MobiFlight.A320_neo_MFD_Range_1}- 103=B66C0=2 P256,11,C32776,2 -{:MobiFlight.A320_neo_MFD_Range_1}- 104=B66C0=3 P256,11,C32776,3 -{:MobiFlight.A320_neo_MFD_Range_1}- 105=B66C0=4 P256,11,C32776,4 -{:MobiFlight.A320_neo_MFD_Range_1}- 106=B66C0=5 P256,11,C32776,5 -{:MobiFlight.A320_neo_MFD_Range_1}- 107=B66C0=6 P256,11,C32776,6 -{:MobiFlight.A320_neo_MFD_Range_1}- 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,C32776,0 -{:MobiFlight.A320_neo_MFD_Range_1}- 112=B66C0=1 P256,12,C32776,1 -{:MobiFlight.A320_neo_MFD_Range_1}- 113=B66C0=2 P256,12,C32776,2 -{:MobiFlight.A320_neo_MFD_Range_1}- 114=B66C0=3 P256,12,C32776,3 -{:MobiFlight.A320_neo_MFD_Range_1}- 115=B66C0=4 P256,12,C32776,4 -{:MobiFlight.A320_neo_MFD_Range_1}- 116=B66C0=5 P256,12,C32776,5 -{:MobiFlight.A320_neo_MFD_Range_1}- 117=B66C0=6 P256,12,C32776,6 -{:MobiFlight.A320_neo_MFD_Range_1}- 118=B66C0=7 P256,12,Cx010066C0,x00 -{offset byte set, offset 66C0}- I made it go up to 7 and if it does go back to 6 or 0 so it doesn't cycle back. I can use the same trick for the NAV_MODE. Now we only have to wait until Mobiflight releases these events Link to comment Share on other sites More sharing options...
MarkStallen Posted January 27, 2021 Author Report Share Posted January 27, 2021 For the NAV_MODE 200=P256,9,Cx510066FF,x00050001 -{offset byte cyclic inc, offset 66FF (Incr=1, Limit=5)}- 201=B66FF=0 P256,9,C32775,0 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 202=B66FF=1 P256,9,C32775,1 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 203=B66FF=2 P256,9,C32775,2 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 204=B66FF=3 P256,9,C32775,3 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 205=B66FF=4 P256,9,C32775,4 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 208=B66FF=5 P256,9,Cx010066FF,x04 -{offset byte set, offset 66FF}- 210=P256,10,Cx610066FF,x00050001 -{offset byte cyclic dec, offset 66FF (Decr=1, Limit=5)}- 211=B66FF=0 P256,10,C32775,0 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 212=B66FF=1 P256,10,C32775,1 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 213=B66FF=2 P256,10,C32775,2 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 214=B66FF=3 P256,10,C32775,3 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 215=B66FF=4 P256,10,C32775,4 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 218=B66FF=5 P256,10,Cx010066FF,x00 -{offset byte set, offset 66FF}- Link to comment Share on other sites More sharing options...
Simmy5001 Posted January 27, 2021 Report Share Posted January 27, 2021 Hi Mark I was able to get the new FBW A32NX events to work using a VRInsight CDUII via FSUPIC and the VRinsight mapping software. The majority of the new events work. The following ones didn't seem to function, with the zero being the most problematic. Is there way to get them to work, or do we need to wait for a update from mobiflight? 12=MobiFlight.A320_Neo_CDU_1_BTN_UARROW13=MobiFlight.A320_Neo_CDU_1_BTN_DARROW14=MobiFlight.A320_Neo_CDU_1_BTN_LARROW15=MobiFlight.A320_Neo_CDU_1_BTN_RARROW 62=MobiFlight.A320_Neo_CDU_1_BTN_0 66=MobiFlight.A320_Neo_CDU_1_BTN_SLASH Link to comment Share on other sites More sharing options...
MarkStallen Posted January 27, 2021 Author Report Share Posted January 27, 2021 Rename _SLASH with _DIV in the events.txt off the mobiflight WASM module. BTN_0 should also be there. I found this and more on the Discord-Channel of Mobiflight. Updates Will be discussed on this channel 1 Link to comment Share on other sites More sharing options...
Simmy5001 Posted January 27, 2021 Report Share Posted January 27, 2021 Thanks Mark, I'll try that tomorrow Any ideas on the arrow keys? Link to comment Share on other sites More sharing options...
MarkStallen Posted January 28, 2021 Author Report Share Posted January 28, 2021 Yep Change them in the events.txt and in the .evt files of FSUIPC to : A320_Neo_CDU_1_BTN_UP A320_Neo_CDU_1_BTN_DOWN A320_Neo_CDU_1_BTN_PREVPAGE A320_Neo_CDU_1_BTN_NEXTPAGE Link to comment Share on other sites More sharing options...
Simmy5001 Posted January 28, 2021 Report Share Posted January 28, 2021 Thanks Mark, works perfectly. Link to comment Share on other sites More sharing options...
ylevesque Posted January 29, 2021 Report Share Posted January 29, 2021 Hi Mark. I saw your previous posts. Is MobiFlight.A320_neo_MFD_Range_1 works with a parameter? I add it to mobiflight WASM module events.txt and to FUIPC evt file. Even with a parameter I cannot change the EFIS range. MobiFlight.A320_neo_MFD events without parameters works well. Any idea to make events with parameter to work? Thanks Yves Link to comment Share on other sites More sharing options...
MarkStallen Posted January 30, 2021 Author Report Share Posted January 30, 2021 Yves, we have to wait untill Mobiflight releases these events. After that you can use my entries for the fsuipc.ini file. Link to comment Share on other sites More sharing options...
MarkStallen Posted February 1, 2021 Author Report Share Posted February 1, 2021 How do you set-up Linda to use these Mobiflight events. I can make a lua with functions like : function XXXXXX () ipc.control( xxxxx, p ) end end Is it possible to call the mobiflight events like this? Link to comment Share on other sites More sharing options...
John Dowson Posted February 1, 2021 Report Share Posted February 1, 2021 6 hours ago, MarkStallen said: Is it possible to call the mobiflight events like this? It should be possible to do that in FSUIPC, so should also be possible in Linda. First, you need to add the events to FSUIPC7 using event files. Then, you need to determine what control number FSUIPC7 has assigned to the events. You can do this either by temporarily assigning the event to a button, activate event logging and then press the button to see what event number is logged. You can also work it out by the the number of evt files you have and the index number - the control number will be: 32768 + (256*fileIndex) + controlIndex where fileIndex is the order the file is loaded (starting with 0) and controlIndex is the index number of the event in the file. If you are only using one event file, this is then just: 32768 + controlIndex John Link to comment Share on other sites More sharing options...
MarkStallen Posted February 17, 2021 Author Report Share Posted February 17, 2021 I've found two new A320NX events that work : 33=MobiFlight.A320_Neo_MFD_BTN_TERRONND_1 34=MobiFlight.A320_Neo_PFD_BTN_LS_1 (this one instead of 34=MobiFlight.A320_Neo_MFD_BTN_LS_1) Add them in your xxxx.evt in the FSUIPC dir. and your events.txt in your mobiflight WASM module Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now