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! 

05/03/2024 - This forum is read-only

The community support for MobiFlight has moved exclusively over to our Discord server. Register for free and enjoy more interactive functions like image and video upload, voice chat. More than 7,000 registered users around the world make it a great experience!

See you on our MobiFlight Community Discord server.

A HUGE Thank You to everyone who participated in the forum, especially obviously to Pizman and Stephan who did an outstanding job over so many years providing an incredible service to the MobiFlight community.

The forum is still providing a lot of good content, hence we keep this information accessible.

icon
Avatar
jabad
Posts: 1
Hello everybody.

After my fisrts steps with mobiflight and the parking brake tutorial I have a question.

I started with the FSX in a presaved situation and starts with parking brake OFF, if I move the switch to ON, the parking brake led brights, and the parking brake announcement is showed, but if I maintain the switch ON, and the flight it's reseted the led goes off, but the switch it's still ON, and the parking brake it's not applied on simulator. It seems that the switch position it's not readed, the same happens if I restart the simulator with the switch ON, If i press the reset button on arduino all goes ok again.

What can I do in order that the arduino reads the initial switch position
2018-01-17 21:58
Avatar
jjvelar
Posts: 47
I am also interested in that.
2018-01-18 11:13
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
This is not possible directly.....

Mobiflight NOT read a initial position..... it just resume a "change" of a switch and then execute the needed command ( Release or press )

To solve this you have some systems....

1. the internal Mobiflight synchro function !
You can set a button somewhere in the cockpit that is set in Mobiflight for the SYNC Funtion..... If you push it then Mobiflight will start a sequence where EVERY Input is READ the State of switch and will ececute 1 time the command.
Problem here.... This work fine for all ON/OFF Switches but it can´t set ON/OFF/ON Switches. ( ON-OFF-ON only can synchro in OFF and the First ON Position .... if it´s in the second ON Position a Synchro will occure in a wrong input)

But i think THIS is a good solution.... In that case you only need to set all ON-OFF-ON switches to OFF before you sync..... Maby just 5-10 switches in a full cockpit. All other is automaticly. Alternate you use a little more expensive ON-ON-ON switches.... They workwith sync 100% perfect.

***

2. Using a startup state OR a "Live state"
Some Cockpitbuilders work with a "live state" ..... Means you SAVE the state when you leave the simulator ( Then Virtual state is 1:1 to the real state... for example your brake is set.... switch is on..... When you save now and not touch the switch then in next season you RELOAD the state and its 1:1 like now )
THIS is like in Real.... Here you can´t "load" something and the aircraft is still in same condition as you leave it last time.


Alternate is a basic startup state..... Here you load every time the SAME Basic Startup file.... and you have a checklist in what position every switch should be in this situation.
You have to check all switches before you start Mobiflight if they are in correct position.

Reverse technic is to set AFTER your flight all back to startup state ( for example cold and dark) .... Then in next season all switches are already correct.
Good Luck !
2018-01-18 12:59
Avatar
Hannes
From: Austria
Posts: 164
Supporter
Hallo, Variante 1 würde mir gut gefallen. Wo ist diese Sync Funktion in Mobiflight, bzw. wie legt man diese an? Vielen Dank
www.modellbau-technik.at
hannes.dobersberger@modellbau-technik.at
2019-01-02 13:35
Avatar
StephanHo
From: EDDG, Germany
Posts: 1867
Supporter
Hi,

If you always shut down a cockpit at the end of a session in Cold & Dark mode, you always have a defined status. That would be equivalent to the variant 2 of pizman. However, this does not apply after a system crash or similar.
Then variant 1 would make sense (as far as possible)
Grüße,
Stephan (Time: UTC+2)
2019-01-02 18:50
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
The "Function" of Variant 1 is simple....

Create a Input... Use a Button. ( For example set a little button somewhere in the cockpit for this "Sync" )
Then in TYP Field you not choose EventID or Offset like normaly.... You will use "Mobflight Sync"
Sorry... Have no access to MF at the moment. Not sure whats the correct name is.... Something with Syncro pretty sure.

Finaly... If you run Mobiflight and you push this button it will start the sequence.

Note:
1. Sequence takes time.... Even longer as more buttons are in your cockpit.
2. ON-OFF-ON Buttons will not work correctly in some situations. ( Only 100% in Middle Position)
3. Multiposition Roatrys work also not correctly if you use a Release Logic. ( Normaly nobody do that... i just want to tell you)

****
Summary. I Personaly recommend to work with a Startupt State. As i know most Homecockpit Builders do that. Thats the most profitable workflow i think. I talked to a cockpitbuilder in the past.... He mean thats just a queston of training. If you use the Cockpit for longer time you not need a checklist anymore. You know all positions and prepare your cockpit for startup in less then a minute !
Good Luck !
2019-01-03 05:26
icon