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.

Message #20745

simo77

Posts: 15

Hello
I have a problem, I use two mega cards, one for switches and the other for announciators
suddenly the annunciator card does not receive data,
in the test work but in run mode no here is the debug:
note the first two lines are the same aunnunciator at 22.46.47 (697) and 'the test at 22.26.52 (832) and 22:26:52 (832) the run mode

01/11/2020 22:26:52 (832): Command: SetPin <2,3,0;>
01/11/2020 22:26:47 (697): Command: SetPin <2,3,255;>
01/11/2020 22:26:14 (183): ExecutionManager.AutoConnectStart: Started auto connect timer
01/11/2020 22:26:14 (172): No updates necessary. Your version: 7.10.0.0, Latest version: 7.10.0
01/11/2020 22:26:13 (961): ExecutionManager.autoConnectTimer_Tick (): AutoConnect Sim
01/11/2020 22:26:13 (937): Command: SetPin <2,16,0;>
01/11/2020 22:26:13 (927): Command: SetPin <2,3,0;>
01/11/2020 22:26:13 (917): Command: SetPin <2,22,0;>
01/11/2020 22:26:13 (906): Command: SetPin <2,19,0;>
01/11/2020 22:26:13 (896): Command: SetPin <2,18,0;>
01/11/2020 22:26:13 (886): Command: SetPin <2,17,0;>
01/11/2020 22:26:13 (875): Command: SetPin <2,26,0;>
01/11/2020 22:26:13 (865): Command: SetPin <2,15,0;>
01/11/2020 22:26:13 (855): Command: SetPin <2,14,0;>
01/11/2020 22:26:13 (845): Command: SetPin <2,12,0;>
01/11/2020 22:26:13 (834): Command: SetPin <2,11,0;>
01/11/2020 22:26:13 (825): Command: SetPin <2,10,0;>
01/11/2020 22:26:13 (815): Command: SetPin <2,9,0;>
01/11/2020 22:26:13 (805): Command: SetPin <2,8,0;>
01/11/2020 22:26:13 (796): Command: SetPin <2,7,0;>
01/11/2020 22:26:13 (786): Command: SetPin <2,6,0;>
01/11/2020 22:26:13 (776): Command: SetPin <2,5,0;>
01/11/2020 22:26:13 (766): Command: SetPin <2,4,0;>
01/11/2020 22:26:13 (756): ExecutionManager.TestModeStop: Stopped test timer

and there's this message: Preventing entering EnergySaving Mode: KeepAlive!

2020-11-01 22:56

Message #20749

pizman82

Moderator

From: ETSI, Germany

Posts: 6010

Supporter

The Logging shows that THIS Pin is controlled.

Quote:
01/11/2020 22:26:52 (832): Command: SetPin <2,3,0;>
01/11/2020 22:26:47 (697): Command: SetPin <2,3,255;>

While the Test at 22.26.47 it was ON ..... 5 seconds later it would be set to OFF. Thats look ok.
On first view i will say.... If MF is in RUN Mode that time then simply the config from this LED is currently sending a "0" OR there is no active config that controll the LED:

Please check the Configs Itself.
1. Is Mobiflight RUN and you have conncetion to FSUIPC ( Green hook down left)
2. Is the needed Config ACTIVE (Checkmark left of the Config)
3. What is the FSUIPC and the OUTPUT Value in that Config Line ? If Value is "0" its logical the LED must be OFF.

Good Luck !

2020-11-02 11:25

Message #20774

simo77

Posts: 15

Thank you for reply and sorry for the delay of the answer
I solved the problem, there were simply multiple configurations with the same offset conflicting
thanks

2020-11-05 05:01