MobiFlight Community Support

hi, during the flight, the window, anti ice announcer and lcd display are on (I use 737 pmdg with FSX), sometimes the announcers turn off
and the message "preventing access to saving mode: keep alive" appears in the message windows
how to solve?
thanks

Hi Simo,

just turn off the logging mode in MF. This message is only to tell you that MF is polling the line so that it not went into the sleep mode.
The logging mode is only for testing purposes not for the normal operation.

Is this the option?


Logging

enable log level "debug"


sorry I don't know how an pic fits

Correct. The logging mode is only for testing purposes. In logging mode there are also delays in signal processing, which is normal. Therefore do not use the logging mode in real operation

I have disabled the "logging" mode
but the problem persists
during the flight the annunciators turn off to turn them back on I have to press off then on on the swicthes,
anyway here is the log
7/12/2020 16:41:50(712): Preventing entering EnergySaving Mode: KeepAlive!
27/12/2020 16:36:50(675): Preventing entering EnergySaving Mode: KeepAlive!
27/12/2020 16:31:50(634): Preventing entering EnergySaving Mode: KeepAlive!
27/12/2020 16:30:04(634): Command: SetPin <2,42,0;>
27/12/2020 16:30:04(627): Command: SetPin <2,43,0;>
27/12/2020 16:30:04(619): Command: SetPin <2,44,0;>
27/12/2020 16:30:04(612): Command: SetPin <2,41,0;>
27/12/2020 16:30:04(606): Command: SetPin <2,40,0;>
27/12/2020 16:30:04(599): Command: SetPin <2,39,0;>
27/12/2020 16:30:04(591): Command: SetPin <2,38,0;>
27/12/2020 16:30:04(584): Command: SetPin <2,37,255;>
27/12/2020 16:30:04(577): Command: SetPin <2,36,255;>
27/12/2020 16:30:04(570): Command: SetPin <2,35,255;>
27/12/2020 16:30:04(563): Command: SetPin <2,34,255;>
27/12/2020 16:30:04(556): Command: SetPin <2,33,255;>
27/12/2020 16:30:04(549): Command: SetPin <2,32,255;>
27/12/2020 16:30:04(542): Command: SetPin <2,31,255;>
27/12/2020 16:30:04(535): Command: SetPin <2,30,0;>
27/12/2020 16:30:04(493): Command: SetPin <2,29,0;>
27/12/2020 16:30:04(486): Command: SetPin <2,28,0;>
27/12/2020 16:30:04(480): Command: SetPin <2,27,0;>
27/12/2020 16:30:04(474): Command: SetPin <2,26,0;>
27/12/2020 16:30:04(466): Command: SetPin <2,2,0;>
27/12/2020 16:30:04(460): Command: SetPin <2,25,0;>
27/12/2020 16:30:04(454): Command: SetPin <2,24,0;>
27/12/2020 16:30:04(448): Command: SetPin <2,23,0;>
27/12/2020 16:30:04(441): Command: SetPin <2,7,0;>
27/12/2020 16:30:04(435): Command: SetPin <2,6,0;>
27/12/2020 16:30:04(429): Command: SetPin <2,5,0;>
27/12/2020 16:30:04(423): Command: SetPin <2,4,0;>
27/12/2020 16:30:04(417): Command: SetPin <2,3,0;>
27/12/2020 16:30:04(409): Command: SetPin <2,17,0;>
27/12/2020 16:30:04(403): Command: SetPin <2,19,0;>
27/12/2020 16:30:04(397): Command: SetPin <2,18,0;>
27/12/2020 16:30:04(391): Command: SetPin <2,22,0;>
27/12/2020 16:30:04(385): Command: SetPin <2,16,0;>
27/12/2020 16:30:04(379): Command: SetPin <2,15,0;>
27/12/2020 16:30:04(373): Command: SetPin <2,14,0;>
27/12/2020 16:30:04(368): Command: SetPin <2,12,0;>
27/12/2020 16:30:04(362): Command: SetPin <2,11,0;>
27/12/2020 16:30:04(354): Command: SetPin <2,10,0;>
27/12/2020 16:30:04(349): Command: SetPin <2,9,0;>
27/12/2020 16:30:04(343): Command: SetPin <2,8,0;>
27/12/2020 16:30:04(337): Command: SetLcdDisplayI2C <25,0,FTL ALT: 35000LAND ALT: 50;>
27/12/2020 16:30:02(850): Command: SetPin <2,37,0;>
27/12/2020 16:30:02(845): Command: SetPin <2,36,0;>
27/12/2020 16:30:02(838): Command: SetPin <2,35,0;>
27/12/2020 16:30:02(832): Command: SetPin <2,34,0;>
27/12/2020 16:30:02(826): Command: SetPin <2,33,0;>
27/12/2020 16:30:02(821): Command: SetPin <2,32,0;>
27/12/2020 16:30:02(815): Command: SetPin <2,31,0;>
27/12/2020 16:29:52(985): Serialized Arcaze Extension Module Settings: <?xml version="1.0" encoding="utf-16"?>
<ArrayOfArcazeModuleSettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />

Hi

This is a more complex thematic.

Basicly Stephans idea is correct.... Logging Mode got some disadvantage ( slow Encoders and delays in Displays) ..... So it´s high recommend to use it only while building the configs or to find a issue.... NOT while running the cockpit until a real flight !

Whatever.... Thats pretty sure not the reason of your Problem.

1. The logging NOT show a command. But it also not show me the "reset" of the LED´s in case you using the virtual ( or real) switch.
Pretty sure you did the INput you tell us after the Copy/Paste of the logging you puiplish above.

7/12/2020 16:41:50(712): Preventing entering EnergySaving Mode: KeepAlive!
27/12/2020 16:36:50(675): Preventing entering EnergySaving Mode: KeepAlive!
27/12/2020 16:31:50(634): Preventing entering EnergySaving Mode: KeepAlive!
27/12/2020 16:30:04(634): Command: SetPin <2,42,0;>
27/12/2020 16:30:04(627): Command: SetPin <2,43,0;>

Means at 16.36 The LED´s are SET ..... At 16.31 and 16.36 and 16.41 there was a "wakeup Call". BUT there was no setting of the LED´s by Mobiflight ( Not to OFF and also not to ON by a input of yourself.)


2. The "keep alive" call is correct and should looks like this. thats no Bug.... Its a important feature to hande 7.Seg Displays. without that function they would get dark after some minutes without a posibility to use them again !
*********************************


3. The Problem!
LED normaly can not get to OFF by itself.... If they are ON and nobodey tell them to go off they will light for the next 100 Years !
Also MF have no official Funtion to do this.... So we talk about a PRoblem on the MEGA.

This issue is rare.... But i still see this 2 times in the past. Both was a electrical Problem !
The logging show me you use many many LED´s . If these are not Low Current you pretty sure overdrive the Power Limit. Also remember the LCD need Power !!
If not on the Limit maybe the Power of your Computer is still on the end. Finaly also a bad USB Cable can be the problem !
Basicly.... Disabled LED´s are a indice for low power.

To solve:
1. Confirm you not have more then 500mA on that board. ( ALL Devices together !)
2. Try to external power the Board.... Best way with a powerd USB Hub

3. If you like you can reduce the number of LED Devices ( For testing or also finaly in your project.
If you also need e.g. 40 Buttons / Switches then try to split it.... So each Mega use 20 LED and 20 Switches e.g.

4. If all not helps.... Maybe a Firmware Bug.... I don´t think so. But the last option is a EEPROM Clear and a fresh flash of firmware. SAVE your devices prior.... So you can use them again without creating new.

PLEASE Report experience. I think 99% this is the reason !

Thanks for info
During the flight 8 LEDs and LCD display are on
MEGA cards are connected to a USB HUB along with other peripherals, could it be that?
I try to connect the Mega with the announcers directly to the USB port of the PC
or to power with an external power supply unit, in this case what characteristics must the power supply unit have?

I not know the exact issue spot.... I´m also not sure if my idea is correct ( As i said... I´m not the programmer. Im just a user with some eperience)

So Yes.... It can be a "bad" USB Hub.... It can be a problem if the other devices on the Hub need Power.
Is your USB Hub powered ? If not and it is a option there... connect a Power suply on the Hub.

About specifications.....

In Theory the Mega can handle 800mA. But USB supports only 500mA
I personaly not recommend to set a Suply to the Mega and work with >500mA then.
The most save and easy way is to calculate the devices for 500mA max.... And power the Mega via USB.
And Sure.... You must get sure the USB support perfect 500mA. Means a powerd Hub is mostly a good idea.

As said in last posting.... If you like make testings to confirm my idea is good. Simply disconnect for testing e.g. 50% of your LED from the Mega..... Delete the Devices for testing and run your flight. No issue means you find the problem.

Hello and happy new year
i think i solved the problem,
first of all the card is not original, and it was connected with an extension cable, I replaced the cable and connected it directly to the USB of the PC without using the external hub and now it works

Thanks for your help

I really like what Mobiflight is doing here. I like their way of saving energy during flights and I like that they found a way to save energy without harming their customers or putting their lives at risk. I have seen a similar proposal on simplyswitch.com where they suggest a way similar to this one of saving energy. There are also companies that suggest green energy as an alternative but I think their idea could work only when it is hot outside. I don't understand why people like such an unstable alternative that needs a lot of perfecting but it is their choice.