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! 

Go to page 1Go to page 012Go to page 2Go to page 2
Avatar
TarsoSousa
From: SBNT
Posts: 46
Yesterday after i end config of 9 MF boards with a total of more than 350 pins in use i saved project and closed mobiflight for restarting the computer to start testing in the simulator but after PC restart MF does not open anymore with all boards connected.

It starts normal with no boards and with 2 boards but not with more than 2 boards, what is going on?
2016-07-28 03:40
Avatar
TarsoSousa
From: SBNT
Posts: 46
More info about the problem.

I deleted the config file from Documents folder and MF opened normal with my 9 boards connected, and then i load the config from the file that i have backup.

Everything works fine 100%, BUT big problem is that if i close MF i can`t open it again.

Actual status: everytime i have to delete the config file and open MF and then load the config to MF work.

Please help me!
2016-07-29 00:41
Avatar
TarsoSousa
From: SBNT
Posts: 46
When i start without config file and load my config i get this window and this text below:

Consulte o final desta mensagem para obter detalhes sobre como chamar a
depuração just-in-time (JIT) em vez desta caixa de diálogo.

************** Texto de Exceção **************
System.NullReferenceException: Referência de objeto não definida para uma instância de um objeto.
em MobiFlight.OrphanedSerialsDialog.updateOrphanedList()
em MobiFlight.OrphanedSerialsDialog..ctor(List`1 serials, DataTable dataTable, DataTable inputDataTable)
em MobiFlight.MainForm._checkForOrphanedSerials(Boolean showNotNecessaryMessage)
em MobiFlight.MainForm._loadConfig(String fileName)
em MobiFlight.MainForm.loadToolStripMenuItem_Click(Object sender, EventArgs e)
em System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
em System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
em System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
em System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
em System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
em System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
em System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
em System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
em System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
em System.Windows.Forms.Control.WndProc(Message& m)
em System.Windows.Forms.ScrollableControl.WndProc(Message& m)
em System.Windows.Forms.ToolStrip.WndProc(Message& m)
em System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
em System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
em System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
em System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Assemblies Carregados **************
mscorlib
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1080.0 built by: NETFXREL3STAGE
Base de Código: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MFConnector
Versão do Assembly: 7.0.5.0
Versão do Win32: 7.0.5
Base de Código: file:///C:/Users/SIMULADOR%201/Downloads/MFConnector.exe
----------------------------------------
System.Windows.Forms
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1038.0 built by: NETFXREL2
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1081.0 built by: NETFXREL3STAGE
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1078.0 built by: NETFXREL3STAGE
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Data
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1082.0 built by: NETFXREL3STAGE
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1038.0 built by: NETFXREL2
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1064.2 built by: NETFXREL3STAGE
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1038.0 built by: NETFXREL2
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Windows.Forms.resources
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1038.0 built by: NETFXREL2
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_pt-BR_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
System.Numerics
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1038.0 built by: NETFXREL2
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
FSUIPCClient
Versão do Assembly: 2.0.4008.2
Versão do Win32: 2.0.4008.2
Base de Código: file:///C:/Users/SIMULADOR%201/Downloads/FSUIPCClient.DLL
----------------------------------------
ArcazeHid
Versão do Assembly: 1.0.0.0
Versão do Win32: 1.0.0.0
Base de Código: file:///C:/Users/SIMULADOR%201/Downloads/ArcazeHid.DLL
----------------------------------------
Microsoft.GeneratedCode
Versão do Assembly: 1.0.0.0
Versão do Win32: 4.6.1064.2 built by: NETFXREL3STAGE
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.GeneratedCode
Versão do Assembly: 1.0.0.0
Versão do Win32: 4.6.1064.2 built by: NETFXREL3STAGE
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
AutoUpdater.NET
Versão do Assembly: 1.3.1.0
Versão do Win32: 1.3.1.0
Base de Código: file:///C:/Users/SIMULADOR%201/Downloads/AutoUpdater.NET.DLL
----------------------------------------
CommandMessenger
Versão do Assembly: 1.0.0.0
Versão do Win32: 1.0.0.0
Base de Código: file:///C:/Users/SIMULADOR%201/Downloads/CommandMessenger.DLL
----------------------------------------
mscorlib.resources
Versão do Assembly: 4.0.0.0
Versão do Win32: 4.6.1038.0 built by: NETFXREL2
Base de Código: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_pt-BR_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------

************** Depuração JIT **************
Para habilitar a depuração just-in-time (JIT), o arquivo .config deste
aplicativo ou computador (machine.config) deve ter o valor
jitDebugging definido na seção system.windows.forms.
O aplicativo também deve ser compilado com a depuração
habilitada.

Por exemplo:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Quando a depuração JIT está habilitada, qualquer exceção sem tratamento
será enviada ao depurador JIT registrado no computador,
em vez de ser tratada nesta caixa de diálogo.
2016-07-30 20:46
Avatar
TarsoSousa
From: SBNT
Posts: 46
Cant send my image that contain the message above

The same message appears when i click in manage orphaned serials, what is going on? Could be fixed?
2016-07-30 20:50
Avatar
TarsoSousa
From: SBNT
Posts: 46
opened my .mcc file and start to look for something that causes a crash.

and i found it!

when i remove the lines of 2 input switches everything get back to normal, but the most strange thing is that this 2 was disabled in the config.
2016-07-31 02:05
Avatar
DocMoebiuz
Moderator
From: NW of KPWK, United States
Posts: 1470
I will note this down as a bug and if I can reproduce it I'll fix it in one of the upcoming releases.
Have a great day!
Sebastian

MobiFlight - Simply build your own home cockpit for your favorite flight sim - MSFS2020, FSX, Prepar3D (FSUIPC), X-Plane (XPUIPC)
2016-08-22 04:57
Avatar
TarsoSousa
From: SBNT
Posts: 46
It still happening when i leave couple of lines disabled in MF connector.

Apreciate your hardwork
2016-08-23 04:25
Avatar
DocMoebiuz
Moderator
From: NW of KPWK, United States
Posts: 1470
I have moved this topic to the english section
Have a great day!
Sebastian

MobiFlight - Simply build your own home cockpit for your favorite flight sim - MSFS2020, FSX, Prepar3D (FSUIPC), X-Plane (XPUIPC)
2016-08-31 04:27
Avatar
MASTERP
Posts: 55
My problem is every start up computer, I have to go to Windows Hardware Manager to disable both Arduino COMs, then enable them again.
After that Mobiflight can start and runs properly
I am not sure something wrong with voltage or something which I have no idea, but at least it is the work-around for me.
I am using 3 Arduino Mega 2560 in Windows 7 Ultimate x64
2016-09-16 08:55
Avatar
fireballfly762
Posts: 6
Hey Sebastian,

I'm having a similar problem as the other two;

Windows 7 x64
Arduino Mega 2560
firmware 1.6.1
Mobiflight 7.1.2

After a bit of testing and playing with Mobiflight, it randomly stops starting while the Arduino is connected. The solution to that I've found is like MasterP's solution, disable the port in Device Manager, start Mobiflight, then re-enable the port. The problem I have is when I do that, Mobiflight doesn't recognize my Arduino anymore at all (Mobiflight Modules - none). The fix I found for that is opening the Arduino IDE software and uploading a blank program (essentially wiping the board), and Mobiflight starts just fine and autodetects the board as a new arduino and uploads the Mobiflight firmware. Everytime I close Mobiflight though, I have to wipe the board and re-upload the firmware. Don't know if this helps.

Cheers,
Andrew
2016-12-21 16:29
Avatar
DocMoebiuz
Moderator
From: NW of KPWK, United States
Posts: 1470
Hi Andrew,

do you have many devices configured on the board? Maybe there is something strange with the config, it might be very long or so which could maybe lead to the described problem.
Have a great day!
Sebastian

MobiFlight - Simply build your own home cockpit for your favorite flight sim - MSFS2020, FSX, Prepar3D (FSUIPC), X-Plane (XPUIPC)
2016-12-21 16:51
Avatar
fireballfly762
Posts: 6
Hey,

Sorry, holidays got really busy and I didn't really get chance to play around with it until recently. I'm progressively adding switch configs to mobiflight from my overhead panel I made; when I posted last, I had six switches hooked up and configured in mobiflight. As of right now, I have 23 two position switches, 3 three position, and 1 four position switch connected and configured. It wasn't having the starting issue yesterday, but I gave up for the night when the Mega board stopped registering a pin state change on the last switches that I added. This was fixed by rebooting mobiflight and fsx in the morning and the start issue has come back. Now it is having the start issue plus a number of switches are registering on the board (Tx light flashes when the switch position changes) but mobiflight does not register anything. I've checked the wiring multiple times, the pins are wired correctly and assigned correctly, (they are wired to change from high to low when a button/switch is pressed). I currently have 38 "button" inputs configured in mobiflight, no outputs, and no analog inputs.

Cheers,
Andrew
2017-01-10 17:07
Avatar
DocMoebiuz
Moderator
From: NW of KPWK, United States
Posts: 1470
Hi Andrew,

let's get this solved... but I need some more infos:
* Can you turn DEBUG Mode on and see if the Event is received by MobiFlight Connector? It should tell something about OnPress, OnRelease events.
* Do you use longer descriptive names for the buttons? Do you use any special characters or spaces in the names?
Have a great day!
Sebastian

MobiFlight - Simply build your own home cockpit for your favorite flight sim - MSFS2020, FSX, Prepar3D (FSUIPC), X-Plane (XPUIPC)
2017-01-10 19:37
Avatar
fireballfly762
Posts: 6
Hey Sebastian,

iconDocMoebiuz:


* Can you turn DEBUG Mode on and see if the Event is received by MobiFlight Connector? It should tell something about OnPress, OnRelease events.


Yes, I've had debug on since I started playing with mobiflight, it does not show any event or error for 6 or 7 of the inputs I have configured, the only reason I know they work is the Mega board Tx light flashes.

iconDocMoebuiz:


* Do you use longer descriptive names for the buttons? Do you use any special characters or spaces in the names?


Some of the device names are a little longer, the only characters I use though are letters, numbers, spaces, and dashes ( - ). The longest "name" I have is 15 characters long (not counting spaces), "LH Ldg Rtct Extend". I can take the spaces and dashes out if you think that's the issue (I happen to be fluent in compact gibberish B) ). There's only a couple names with dashes in them though, "Eng 1 Anti-ice".

Cheers,
Andrew
2017-01-10 21:45
Avatar
DocMoebiuz
Moderator
From: NW of KPWK, United States
Posts: 1470
Hi Andrew,

please store your board config in the mobiflight modules dialog as a file and send it to me via email. Thanks! info@mobiflight.com
Have a great day!
Sebastian

MobiFlight - Simply build your own home cockpit for your favorite flight sim - MSFS2020, FSX, Prepar3D (FSUIPC), X-Plane (XPUIPC)
2017-01-11 04:06
Go to page 1Go to page 012Go to page 2Go to page 2