MobiFlight Community Support

Welcome to the forum for MobiFlight! Feel free to reach out to the community in case you have questions, issues or just want to share great ideas or details about your latest home cockpit project.

You like MobiFlight? Donate via PayPal and support the MobiFlight development. Thanks! 

icon
Avatar
Druid
Posts: 7
I have made a simple test rig to display Airspeed, Hdg, Alt and VS with the standard Mega 2560 Arduino and 8 segment displays. When using the default Airbus the Airspeed and Hdg work from my rotary encoders fine using the FSUIPC offsets. The Alt displays the selected value when I push/pull the Alt knob in the sim. Sometimes showing 1 foot less ? It does not scroll in sympathy with the rotary knob on the in sim FCU ?
When I try this in the latest Flybywire A320 neither of my Airspeed or Hdg encoders will work. The Knobs on the Sim FCU however will change the values on the LED displays. Are there different FSUIPC offsets to control the Speed, Hdg, Alt and VS is this mod ? There is a list of other FCU buttons and knobs but the key ones to control the aircraft appear missing. Any help greatfully received. Others must have the same requirement to fly this FBW Airbus mod.
2021-04-12 23:58
Avatar
piesangtor
Posts: 7
i have just mapped my fcu buttonbox encoders to work with the a32nx (experimental version) but its using webasm events/variables. yesterday's msfs france update broke it so i'm back using the mouse again for now at least. once its fixed i'll share my settings here...
2021-04-14 10:23
Avatar
Druid
Posts: 7
Hi Thanks for reply. Using "webasm events/variables" is new to me so when you do the update please make it suitable for a newbie. Is this within mobiflight ?
2021-04-15 12:29
Avatar
piesangtor
Posts: 7
So I guess by now you've heard the good news! Latest MSFS patch (1.15.8.0) fixed the WASM issue!

Okay - please just keep in mind i'm using the experimental A32NX version, I'm not sure if these settings will work with stable or dev branches.
- Make sure the mobiflight WASM modules is installled (Mobiflight Menu > Extras > MFS2020 > Install WASM Module)
- A great tutorial/explanation on the MSFS custom variables (accessible through WASM) in this video:https://youtu.be/PKBjEl9E5A4
- Maybe at first it looks a bit involved in the video but it'll all make sense!

In any case here's whats currently in my events.user.txt file. This file is placed in your Packages\Community\mobiflight-event-module\modules folder
This works for my very basic button box which consists of just four push button encoders for SPD, HDG, ALT and VSP.

iconCode:
// use this file to add your user-defined events
// remove the .inactive extension
// afterwards, the file will not be touched by the next MobiFlight update

// A32X FBW FCU

// SPEED KNOB INCREMENT/DECREMENT
A320_Neo_FCU_SPEED_INC# (>H:A320_Neo_FCU_SPEED_INC)
A320_Neo_FCU_SPEED_DEC# (>H:A320_Neo_FCU_SPEED_DEC)

//SPEED KNOB PULL/PUSH 
A320_Neo_FCU_SPEED_PULL# (>H:A320_Neo_FCU_SPEED_PULL)
A320_Neo_FCU_SPEED_PUSH# (>H:A320_Neo_FCU_SPEED_PUSH)

//HDG KNOB PULL/PUSH
A320_Neo_FCU_HDG_PULL# (>H:A320_Neo_FCU_HDG_PULL)
A320_Neo_FCU_HDG_PUSH# (>H:A320_Neo_FCU_HDG_PUSH)

//HDG KNOB INCREMENT/DECREMENT
A320_Neo_FCU_HDG_INC# (L:A32NX_TRK_FPA_MODE_ACTIVE, bool) 1 == if{ (>H:A320_Neo_FCU_HDG_INC_TRACK) } els{ (>H:A320_Neo_FCU_HDG_INC_HEADING) }
A320_Neo_FCU_HDG_DEC# (L:A32NX_TRK_FPA_MODE_ACTIVE, bool) 1 == if{ (>H:A320_Neo_FCU_HDG_DEC_TRACK) } els{ (>H:A320_Neo_FCU_HDG_DEC_HEADING) }

//ALT INCR/DECR STILL CAN USE EVENTIDS 65893 & 65892

//ALT KNOB PULL/PUSH
A320_Neo_FCU_ALT_PULL# (>H:A320_Neo_FCU_ALT_PULL) (>H:A320_Neo_CDU_MODE_SELECTED_ALTITUDE)
A320_Neo_FCU_ALT_PUSH# (>H:A320_Neo_FCU_ALT_PUSH) (>H:A320_Neo_CDU_MODE_MANAGED_ALTITUDE)

//VSP KNOB INCREMENT
A320_Neo_FCU_VS_INC# (L:A32NX_TRK_FPA_MODE_ACTIVE, bool) 1 == if{ (>H:A320_Neo_FCU_VS_INC_FPA) } els{ (>H:A320_Neo_FCU_VS_INC_VS) }
A320_Neo_FCU_VS_DEC# (L:A32NX_TRK_FPA_MODE_ACTIVE, bool) 1 == if{ (>H:A320_Neo_FCU_VS_DEC_FPA) } els{ (>H:A320_Neo_FCU_VS_DEC_VS) }

//VSP KNOB PULL/PUSH
A320_Neo_FCU_VS_PULL# (>H:A320_Neo_FCU_VS_PULL)
A320_Neo_FCU_VS_PUSH# (>H:A320_Neo_FCU_VS_PUSH)


then in mobiflight, for example, for the speed knob pull event, choose "MSFS2020 Events" from action type, and type in the event name, but without the hash (#) like so:



Does this make sense? Hopefully it points you in right direction at least?:

edit: add example for VSP encoder
[Last edited by piesangtor, 2021-04-17 17:13]
2021-04-17 16:46
Avatar
Druid
Posts: 7
Hi. Many thanks for this. I'll have a go this week. Druid.
2021-04-18 21:17
Avatar
Druid
Posts: 7
Hi

I followed your guidance and watched the video several times. Unfortunately I have not got it to work yet.

I copied / pasted your file into my events.user.txt file.

Copied your set up for the input config wizard input screen for the speed encoder button. Nothing happens on the sim.

Copied your set up for the encoder using A320_Neo_FCU_SPEED_DEC. Again Nothing.

I see in your VSP encoder Input config wizzard there appears to be Group called User:A32X FBW - FCU I do not have this. I tried typing it but it dissappears. Is there a second file you edit to create this drop down list ?

The video shows editing two text files not the events.user.txt file. I assume your method is better as an update from mobiflight will probably overwrite it.

When I look at the events.user.txt file is still shows as INACTIVE File in properties is this correct ?

Sorry to be a pain but I am sure I cannot be far off this working. I have only 4 encoders as a test so we probably have similar setups bar pinouts

Finally 2 questions you may be able to answer.
Why does the Altitude read out on the 7 segment displays only update when you press / pull the toggle switch. It does not scroll in sympathy with the on screen FCU
Why is there not a VSI display when using the FBW A320 when it works on the default A320. Is there a different offset to read ?

Thanks for any further help on this.
Druid
2021-04-20 21:07
Avatar
JLD95
Posts: 1
Hi,
I just discover mobiflight module. I have installed mobiflight-event-module in Community folder and I have already installed X-Touch-Mini-FS2020
I have also FlyByWire docs


Before to create a new events.user.txt file, I would like to know if a complete file exists for last developpment A320NX ?
Jean-Luc
2021-04-27 11:46
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 4786
Supporter
Hi

As i know not a complete file..... For Mobiflight the users must find out each single variable and must create them...
BUT
Lots of users share there already found and working variables in DISCORD to "Rofl-er" . And HE finaly keep a Donloadfile UpTo Date once a week.
If you still use the Mobiflight BETA ( newest release) we inplement a tool to automaticly download the newest EventList by one click.

So....
At first Update the newest List.....
Then check if the Input you need is still included.
If Yes.... Use it
If No..... Build the Event and finaly share your result ( In Discord) ..... then we can put your confirmed working Element in the Preset-List and all other user can use it next week without trouble !
Good Luck !
2021-04-28 01:26
Avatar
Doon1
Posts: 20
Hi,
I am testing the default A320neo functionality with Mobiflight. I 'm doing this for some else as I fly the 172. All the buttons/encoders work in the 172. In the A320neo I've programed the VS inc, dec, push, and pull to buttons. Yet I can't seem to get any of the auto pilot functions to work with the A320neo.
I verified that the event.txt file has the the code that piesangtor posted here. running Mobiflight 8.2.0, FSUIPC is up to date. What am I missing?
2021-07-25 23:27
icon