MobiFlight Community Support

Hi all,
I already had some p&p devices but with MSFS i can't use them, so i decided to build from scratch my home cockpit.

Fist panel is the BRAKE PANEL (i have to backlight it)





Mounted


So i have some problem with offsets/eventid

1. Landing Gear status : I can match all offsets for LandingGear extended , but if i try to assign LandingGear moving (for UNLK lights) when i push "USE" set LangingGear (extracted), any idea (it seems the offsets are the same)?

2. ABRAKE push button : i use event id "SET_AUTOBRAKE_CONTROL" . Using fsuipc console i found this is the event fired when i push one of the abrake button in sim.
The event fired by sim as param 0 = ON , 1 = OFF.. I read fsuipc manual and i found some about offsets of the Autobrake Set : 0=RTO, 1=OFF, 2 = Brake1, 3=Brake2, 4 = Brake3, 5 = Brake MAX.

I try to assign params in this way :

ABRAKE MAX, EventID SET_AUTOBRAKE_CONTROL, params 4
ABRAKE MED, EventID SET_AUTOBRAKE_CONTROL, params 3
ABRAKE LO, EventID SET_AUTOBRAKE_CONTROL, params 2

The Abrake Max works , it set MAX Abrake in sim, Abrake MED and LO doesn't work.
Any idea ?

3. I can't found Offsets or EventID for the HotBrake and TerrON, can you help me?

4. ASKID ON/OFF works using eventid "ANTISKID_BRAKES_TOGGLE" with params 1 for the ON , and 0 for OFF

Regards

At first Complimet !!!
Nice Hardware work. Nearly perfect Panels and a tidy wire system.
May you like to think about Arduino shields in the future to have just one conncetor and not a lot of Duponts on the Mega.


About Problem.

Do we talk about Stock Airbus A320 in FS2020 ?
Here pretty sure we still get in trouble in case all these new functions are not already implement by Pete Dowson in his FSUIPC!

Simply Rule: Mobiflight can only Read or Write Data if FSUIPC support that stuff.

I not own 2020..... so i can not test for you. Technical we could tet it with shared screen in some weeks.... Thats the only i can offer to you.

What you can do now.... Check all the Hardware by testing with other functions if LED and Switches work. If YES the simply wait until all the Systems are implement and then use it.

At first Complimet !!!
Nice Hardware work. Nearly perfect Panels and a tidy wire system.
May you like to think about Arduino shields in the future to have just one conncetor and not a lot of Duponts on the Mega.

Hi pizman , thanks.
Wich Arduino shields do you indicate?

At first Complimet !!!
About Problem.

Do we talk about Stock Airbus A320 in FS2020 ?
Here pretty sure we still get in trouble in case all these new functions are not already implement by Pete Dowson in his FSUIPC!

Simply Rule: Mobiflight can only Read or Write Data if FSUIPC support that stuff.

I not own 2020..... so i can not test for you. Technical we could tet it with shared screen in some weeks.... Thats the only i can offer to you.

What you can do now.... Check all the Hardware by testing with other functions if LED and Switches work. If YES the simply wait until all the Systems are implement and then use it.

Yes, i want to connect the default A320Neo because JH is not compatible yet with fs2020.

I found a workaround in another post in this forum to try to fire the UNLK led.
"The Transit should work between UP and DOWN .
UP means "0" Down means "16383"
In case "0" is still OFF we simply say if($=16383,0,$) . So If 16383 it is set to 0 .... If its UP its also 0 .... between it is 1-16382 and will light."

Can be a solution? Is if($=16383,0,$) the between function?

Hi.

About shield.... Here exist a lot of Solutions.

Our user Karl (Helimech) for example use those.... https://www.aliexpress.com/i/32922971128.html
Here you solder all the wires from devices to that PCB.... And on backside of PCB you solder Pin rows that fit into the Mega.
The big trick here is.... The holes are desigend for the Mega. A regulary empty Breadboard platine will not work cause some of the Connectors on the mega are a little out of the middle. Also a advantage is you not need to use the same hole for both..... On that PCB there are onboard lines that connect the inner holes ( you solder the devices) with the outer holses ( you solder the Pin connector to Mega) .

A more comfortable solution is this.... https://www.amazon.de/ARCELI-Prototyp-Schraube-Klemmenblock-Arduino/dp/B07CQW5WSX
Just to show you.... This link is way to expensive. From China you get them much more cheaper.
Here the Arduino Side is the same.... With soldered Pins..... But the Device Side use here screwed terminals !

****************

About The Formula:

Here you must know... A LED in Mobiflight knows 2 different Status.... ON or OFF ( So Pin is High or low .... Simply Boolean)
From Code side it is easy.... Value "0" means OFF .... All other Values means ON. So whatever 1, 2 , 5 or 99999999. LED will light always if Offset is not equal to zero.

if($=16383,0,$) Means... IF Value is exactly "16383" THEN change it to "0" ELSE ( in all other situations value is not 16383) show the original Value "$".
At Gear UP the Original Value is used and it´s Zero .... so LED is OFF. At Gear DOWN our formula set Value to Zero Again. So LED is OFF again.
Between the Value is increase within some seconds from 1-16382 . And as i said before.... LED is ON that time cause Value is not zero that moment.

For better understanding..... You could also use.... if($=0,0,if($=16383,0,1)) Here you say If Value is 0 then set 0 .... ELSEIF value is 16383 then set 0 ... ELSE set to 1.
Also a OR is possible..... if($=0||$=16383,0,1) .... Here we say If value is 0 OR 16383 then set to 0 Else set to 1.

You see.... Lots of Ways.... All do the same!

Hi.

About shield.... Here exist a lot of Solutions.

Our user Karl (Helimech) for example use those.... https://www.aliexpress.com/i/32922971128.html
Here you solder all the wires from devices to that PCB.... And on backside of PCB you solder Pin rows that fit into the Mega.
The big trick here is.... The holes are desigend for the Mega. A regulary empty Breadboard platine will not work cause some of the Connectors on the mega are a little out of the middle. Also a advantage is you not need to use the same hole for both..... On that PCB there are onboard lines that connect the inner holes ( you solder the devices) with the outer holses ( you solder the Pin connector to Mega) .

A more comfortable solution is this.... https://www.amazon.de/ARCELI-Prototyp-Schraube-Klemmenblock-Arduino/dp/B07CQW5WSX
Just to show you.... This link is way to expensive. From China you get them much more cheaper.
Here the Arduino Side is the same.... With soldered Pins..... But the Device Side use here screwed terminals !

****************

Ah ok, i understand.
Maybe, this is the best solution for little panels
https://www.amazon.it/ARCELI-Arduino-Embedded-ATmega2560-Elettronica/dp/B07MQ1J9MR/

About The Formula:

Here you must know... A LED in Mobiflight knows 2 different Status.... ON or OFF ( So Pin is High or low .... Simply Boolean)
From Code side it is easy.... Value "0" means OFF .... All other Values means ON. So whatever 1, 2 , 5 or 99999999. LED will light always if Offset is not equal to zero.

if($=16383,0,$) Means... IF Value is exactly "16383" THEN change it to "0" ELSE ( in all other situations value is not 16383) show the original Value "$".
At Gear UP the Original Value is used and it´s Zero .... so LED is OFF. At Gear DOWN our formula set Value to Zero Again. So LED is OFF again.
Between the Value is increase within some seconds from 1-16382 . And as i said before.... LED is ON that time cause Value is not zero that moment.

For better understanding..... You could also use.... if($=0,0,if($=16383,0,1)) Here you say If Value is 0 then set 0 .... ELSEIF value is 16383 then set 0 ... ELSE set to 1.
Also a OR is possible..... if($=0||$=16383,0,1) .... Here we say If value is 0 OR 16383 then set to 0 Else set to 1.

You see.... Lots of Ways.... All do the same!

Ok, it's clear. (i kwnow what formula means , i'm a c# programmer so it's familiar hehehe).

Regards

Annunciators work!

Landing Gear Nose Extracted , Offset 0BEC, params : if($=16383,1,0) (16383=full extracted) = GREEN LIGHT WHEN EXTRACTED
Landing Gear Nose Moving , Offset 0BEC, params : if($=0||$=16383,0,1) = RED LIGHT WHEN MOVING
Landing Gear Left Extracted , Offset 0BF4, params : if($=16383,1,0) (16383=full extracted) = GREEN LIGHT WHEN EXTRACTED
Landing Gear Left Moving , Offset 0BF4, params : if($=0||$=16383,0,1) = RED LIGHT WHEN MOVING
Landing Gear Right Extracted , Offset 0BF0, params : if($=16383,1,0) (16383=full extracted) = GREEN LIGHT WHEN EXTRACTED
Landing Gear Right Extracted , Offset 0BF0, params : if($=0||$=16383,0,1) = RED LIGHT WHEN MOVING

Thanks for suggestions...

Now only abrak mid and lo doesn't work yet...

I´m Sorry.....

I not know if Users have experience in programing. So i try to explane it for "dummys" .

As a programmer you still know..... Those little script lines and if conditions are a verry small amount of Systemwork. So it´s not a real difference what formula we use.
Whatever i come from a long long forgotten time in Basic Programming when i was in school. And there with 386CPU and only 4-8 Mhz we get instructed to reduce amount of code as best as possible.

So as i wrote the OR is not realy needed..... Cause in that Offset we got the nice situation that Gear UP means Offset is "0" ---> the OFF Situation here is already fit without any IF-ELSE is needed. Thats why the most easy solution is if($=16383,0,$)
But again.... Who cares if your LED now light 1-2 milliseconds later like with the other formula And pretty sure the Mega chip will not overheat with this additional process .

*****************

About the linked Mega.
YES and NO.

Technical this is a MEGA like the other.... And you can use it same way.
But I personlay not recommend them..... Cause "Space" is not our Problem.... But Small Elements that are much more difficult to handle like bigger ones are (for me) a Problem.

Each Cockpit element got one thing nearly "endless". Space in the "deep" direction. Sure a EFIS is fixed in its length and high ..... But nobody cares if the box is 10, 20 or 30 cm long/deep. So there should always be enough space to mount the Mega "behind" the element or extremly you mount it in a Box 2 Meters away and use a 60 wire cable to it.

Here i recommend also Helimech´s Videos..... For example the Pedestal. https://www.youtube.com/watch?v=oPKrnKUcAxc
Here we got a big 40-50 cm high Box. No need to mount a small Mega within a little Radio Element if we simply can mount them on the bottom of that box.

He also often use a "dispatcher Board" .
For example a wooden plate behind the panel with hundrets of Screw Connectors like this..... https://m.media-amazon.com/images/I/41VNSN1M8RL._AC_.jpg
So you wire the Device to that Point and the other side is wired to the Mega..... So you can verry tidy use e.g. 52 those connectors from UptoDown that represent the Pins from 01-53 on the Mega. You can also Print that wooden plate with lables.... so there is written what element income on the left.... And what Pin on Mega is linout on output on the right.

Summary: For myself the master target is a tidy and 100% clear and logical system. And for myself it´s way more comfortable to have "bigger" parts instead of micro micro stuff.

Thanks to fsuipc support, i found problems with the A320FBW mod.
With default A320 i can set autobrakes for all values.

So i opened a talk with fbw guys to solve

Thanks to fsuipc support, i found problems with the A320FBW mod.
With default A320 i can set autobrakes for all values.

So i opened a talk with fbw guys to solve

Update, the FBW mod stable version works as well.
I had a conversation with FBW guy to inform them and they confirm the developer version has some logical changes in autobrake section.
So i hope they solve

Very nice panel !

Do you have a FCU working on MS2020 A320 ? I built one and have some trouble getting all button / indicator to work on mobiflight :/

I could use some help from someone you master mobiflight

Very nice panel !

Do you have a FCU working on MS2020 A320 ? I built one and have some trouble getting all button / indicator to work on mobiflight :/

I could use some help from someone you master mobiflight

Hi, the FCU will be the next project. I already ordered panels and hardware.
Then i will share all my job and settings here

Great thanks !

Update : DECEL Lights Works!

John Dowson of fsuipc, give me a beta version (https://forum.simflight.com/topic/91355-a320neo-autobrake-panel-offsets/?do=findComment&comment=554316) with 2 new offset
.
This offset give value for
0x0C46 1Byte AUTOBRAKES ACTIVE
0x0C47 1Byte LIGHT BRAKE ON

I used AUTOBRAKES ACTIVE in this way :

ABRK LO DECEL , Offset 0x0C46, params : if($=1,1,0) , Precondition ABRK LO ON (another output to light on the ON led) = 1
ABRK MID DECEL , Offset 0x0C46, params : if($=1,1,0) , Precondition ABRK MID ON = 1
ABRK MAX DECEL , Offset 0x0C46, params : if($=1,1,0) , Precondition ABRK MAX ON = 1

So it light on when AUTOBRAKES ACTIVE value is 1 and relative autobrake push button is selected

Regards

Any chance you could link / let us know the details of the push switches you've used ?
They seem a nice slim profile and very accurate!

Any chance you could link / let us know the details of the push switches you've used ?
They seem a nice slim profile and very accurate!

Hi, i bought push button here :

Korry push button
https://www.homecockpits.fr/en/home/420-korry-full.html

Korry annunciators
https://www.homecockpits.fr/en/home/233-korry-announciator.html

Good quality and low price.

Regards