MobiFlight Community Support

Hi

Being totally new in this home-cockpit world I bought the Opencockpits front panel for the Airbus A320 FCU. The more I read about building this FCU the more complex this seems to be.

One thing I learned while reading and searching this forum is the fact that some of you don't like, or even hate, the A320. I hope you accept that we may have different opinions on this point.

I run Microsoft Flight Simulator 2020 on Windows 10 with FSUIPC7 an Mobiflight and gradually discovered the complexity in the logic and "programming" of those elements.

Sofar I saw some nice working A320 FCU examples on Youtube. However, until now I could not find somebody who was willing to share the Mobiflight code (mcc file) and a description of the specific parts used. It feels a bit like having to re-invent the wheel. I still hope that somebody is willing to share this or point me to the right place to find this.

I apologise in advance if I overlooked something in this forum.

Thanks a lot in advance.
Hans

Hi Hans, i love the A320
I have a little A320 home cockpit , and i schedule to review entire project to build diy devices.

I'm selling my CockpitSonic FCU and then i will build the FCU with arduino e mobiflight.
I already builded the A320 AutoBrake Panel.

You can read and re-use sets here
https://www.mobiflight.com/forum/topic/6193.html

Here there is a topic for the FCU of anther user, i hope it's useful for you
https://www.mobiflight.com/forum/topic/6192.html

In anycase i will be happy to share my mcc when i will be it for the fcu, but i think the mcc file could have some custom setting about boards and pins can't reusable

Regards

Thank you for your reaction Asessa.

That looks promising!

I realise that I would have to customise pin settings and hardware characteristics but that is OK. I will look into your links.

I will use an Arduino Mega.

Regards

Hi Hans,
Nothing is eaten as hot as it is cooked

I'm also not a fan of Airbus either, but that is due to many factors that speak against it for me, just as there are users where these factors speak in favor of it. It's just like with the car, some like VW, others BMW or Mercedes, the next one likes butter, different margarine and and and ... Let's be glad that there is this variety!

To the problem of sharing the or an mcc-file. Each mcc file is basically unique, as the order of the configs, the names of the configs and devices and their connection to the mega module is individual. It just doesn't make sense to type it 1: 1. Rather, it is more interesting to understand the meaning of a single config and to use and implement it for your own purposes. It starts with the naming. How I name a device or a config can be determined individually, there are no mandatory conventions that I have to adhere to. Where I connect the devices is also up to my personal well-being, there are no guidelines. In this respect, it is difficult to adopt an mcc file 1: 1, because it is important to understand what the user who created it meant by it.

But I agree with you, such a file can certainly serve as a template, perhaps also to understand one thing or the other. However, nothing is more intense than the experience of having found something out for yourself. The experience is then posted to the account.

Thanks, Stephan.

I couldn't agree more with you for the taste discussion. I'm a fan of European products. That may lead to certain preferences

It's not that I expect 1:1 usability of other people's mcc file but it became clear to me that quite some logic has to be "programmed" to create a realistic FCU that comes as close as possible to the real thing. I have all the buttons, rotary encoders and displays as suggested in other discussions in this forum but it's the logic that requires a lot of background which I don't have yet for this very specific field.

Any help is welcome and I will continue to explore this very useful forum.

Hi Guys.
Welcome Hans !

Pretty sure you mean myself.... I´m the Airbus Hater here
Yes i often say "Airbus sucks" and "I hate Airbus" ..... But hopefully i use always a Smilie behind and show its "ironic".
So i love Boeing and this have many many reasons.
Whatever..... Sure Also Airbus is a wonderfull piece of Technic. So enjoy it if you like it !


*******************
About MCC.

Here i can say.... For me it is the wrong way to copy it or learn from it. Use it as a example sounds good. But its much harder as it seems.

I see hundrets of MCC files from users while i make Support for MF.
(Without sounding arrogant ) ..... I will say i understand Mobiflight more then most of other Users here..... BUT If i see a MCC file from a new User.... And i still know it´s for e.g. a PMDG737.... And he also tell me basicly what he build......
Let me say i need 1-2 Hours before i beginn to understand what configline is used for what ( Whatever i still build those configs multiple times already myself)

Reason: As Stephan said.... Just for a simple thing like tha Parking Brake LED..... There exist 100 different ways to create this system. Each work ..... But if you NOT know what the guy is doing here ( and how his brain work) then you will not understand the MCC file directly..... You must first understand his logic.... Then you can see what he do.

Summary:
If its a help for you ( whatever i not think so) then use those files. But i will highly recommend.... LEARN the whole Thematic.
Like in the old Speach..... "Not give a Hungry Guy a fish..... Teach him to fishing" .....

If i guide you perfectly to build a Parking Brake LED ..... Then you get stuck again if you need the GEAR Status LED.
But if you learn how Output Configs Work.... What Offsets are for.... And finaly all aspects of Mobiflight..... Then you can Build every In- and Output you will ever Need.
So.... If you just need a FCU.... Copy it 1:1 from a User and be happy. If you like to build multiple own parts or a full cockpit..... Then invest time and learn "MF"completly!

Thanks a lot for your extensive reply pizman82. I am impressed with the response on my request and I am glad to read your remarks about Airbus.

Parking brake was very easy for me. Complexity lies more in the area where complex pre-conditions are required to get the FCU working as it should.

Thanks a lot for your suggestions. They are highly appreciated!