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
Astor1963
Posts: 23
Supporter
Hello, tonight I was so happy to have practically everything working in the absence of a pair of LEDs. I saved everything and went to dinner, then I returned to make a flight with my new autopilot and I could not start it, when loading Mobiflight it gives me this long error, I tried to reset with the button on the "MEGA 2560 R3" board but nothing, I don't get it, I'm very worried, do you think there will be a solution? cry: :cry: :cry: :cry:
Thanks for your interest, greetings

This is part of everything he tells me:




************** Exception text **************
System.ArgumentException: The version string part is too short or long.
en System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
en System.Version.TryParseVersion(String version, VersionResult& result)
en System.Version.Parse(String input)
en System.Version..ctor(String version)
en MobiFlight.MainForm.CheckForFirmwareUpdates()
en MobiFlight.MainForm.ExecManager_OnModuleLookupFinished(Object sender, EventArgs e)
en MobiFlight.ExecutionManager.mobiFlightCache_LookupFinished(Object sender, EventArgs e)
en MobiFlight.MobiFlightCache.<connectAsync>d__34.MoveNext()

--- End of stack trace of previous location where exception occurred ---
en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
en MobiFlight.ExecutionManager.<autoConnectTimer_TickAsync>d__97.MoveNext()

--- End of stack trace of previous location where exception occurred ---
en System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)


************** Assembled loaded **************
mscorlib
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4250.0 built by: NET48REL1LAST_C
Código base: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MFConnector
Versión del ensamblado: 7.10.0.0
Versión Win32: 7.10.0
Código base: file:///D:/_DESCARGAR__/______________CRI/_0%20FS2020/__ARDUINO/MobiFlight/MFConnector.exe
----------------------------------------
System.Windows.Forms
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4270.0 built by: NET48REL1LAST_C
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4200.0 built by: NET48REL1LAST_C
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4084.0 built by: NET48REL1
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4190.0 built by: NET48REL1LAST_B
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4270.0 built by: NET48REL1LAST_C
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4084.0 built by: NET48REL1
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4270.0 built by: NET48REL1LAST_C
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Windows.Forms.resources
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4084.0 built by: NET48REL1
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_es_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
System.Numerics
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4084.0 built by: NET48REL1
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Accessibility
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4084.0 built by: NET48REL1
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
AutoUpdater.NET
Versión del ensamblado: 1.6.0.0
Versión Win32: 1.6.0.0
Código base: file:///D:/_DESCARGAR__/______________CRI/_0%20FS2020/__ARDUINO/MobiFlight/AutoUpdater.NET.DLL
----------------------------------------
FSUIPCClient
Versión del ensamblado: 3.1.18.324
Versión Win32: 3.1.18.324
Código base: file:///D:/_DESCARGAR__/______________CRI/_0%20FS2020/__ARDUINO/MobiFlight/FSUIPCClient.DLL
----------------------------------------
ArcazeHid
Versión del ensamblado: 1.0.0.0
Versión Win32: 1.0.0.0
Código base: file:///D:/_DESCARGAR__/______________CRI/_0%20FS2020/__ARDUINO/MobiFlight/ArcazeHid.DLL
----------------------------------------
Microsoft.GeneratedCode
Versión del ensamblado: 1.0.0.0
Versión Win32: 4.8.4084.0 built by: NET48REL1
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
CommandMessenger
Versión del ensamblado: 1.0.0.0
Versión Win32: 1.0.0.0
Código base: file:///D:/_DESCARGAR__/______________CRI/_0%20FS2020/__ARDUINO/MobiFlight/CommandMessenger.DLL
----------------------------------------
Microsoft.GeneratedCode
Versión del ensamblado: 1.0.0.0
Versión Win32: 4.8.4084.0 built by: NET48REL1
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
mscorlib.resources
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4084.0 built by: NET48REL1
Código base: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_es_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
2020-11-12 01:02
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi.

As i said multiple times.... I personaly not understand all this Error text..... But i got a lot of experience within the years.... So i use a standard workflow.

At first.... Resetting the Megas while running MF never can help.... All Megas that was not work correctly in the moment MF start will not detect.... And also all Megas that will be connected ( or restartet) WHILE Mobiflight is run can also never be detected. MF simply only detect and see Megas that work 100% fine at the moment of first startup!
So a reset finaly make only sense if MF is NOT running that moment and if you startup mobiflight behind the restart of the Mega !


About Probem:

Mostly this is a issue in the MCC File.
To confirm this..... Remove the MCC file you currently use ( the file you last use before the problem start) . Best way is to RENAME the file or to move it into a other folder....
Important is... MF should NOT find the file on it´s old location ( or name) .
THEN Mobiflight will start with a standard file and "should" work.

If that is confirmed and MF now work perfect again then 100% your file is corrupt !
Good Luck !
2020-11-12 02:04
Avatar
Astor1963
Posts: 23
Supporter
Hello, unplug all devices except USB, remove all files so nothing will load, reinstall Mobiflght even FSUIPC, but there is no way it will recognize the card, half charging what you have inside the card gives the error.
I imagine that it would be in the last recording of the two files, that one of them went wrong.
I will have to buy another MEGA, what worries me is not knowing why it happened so as not to repeat it, because until that moment everything works perfectly, I only needed two LED programs.
Come greetings and good day to all :thumbup:
2020-11-12 14:19
Avatar
Astor1963
Posts: 23
Supporter
I just made a last attempt with something that I found "EEPROM Clear arduino" and although in W10 if it detects the board in COM3, arduino tells me that the firmware is wrong.
2020-11-12 14:52
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
I´m sorry but in case of translating i not realy understand what you tell us. Your awnser is verry confusing to me.
Maybe you can explane me more detailed via Voicecall in Discord.

About EEPROM
Yes this is the next step.... If the MCC file was not the reason and it still not work after replace it then the Board itself is the problem.
Then you need to make a EEPROM Clear by running this Sketch via Arduino IDE.
After that the Board is "virgin" and Mobiflight should detect it on next startup as a empty board and offert to upload firmware !

It can happen that a upload went wrong in rare cases.... this kill the firmware and board get no longer detected. a EEPROM Clear fix this.

Test this out. If it work then it´s fine. If it work 1 time but after creating the Settings and a restart it is crash again then we need to check your entrys.
Maybe you try do make something cvompletly wrong we not expect while programming then "maybe" you create a Bug we never plan for.
Good Luck !
2020-11-12 16:15
Avatar
Astor1963
Posts: 23
Supporter
Thank you Pizman for your patience, I tried again to make the CLEAR EEPROM and it worked well, this video was of great help to me, because I have only been with these issues for 3 or 4 days and I didn't know how to do it.
Here I leave it in case it can serve another newbie like me.
Greetings.

https://www.youtube.com/watch?v=SNPLHRPAWSo
2020-11-12 18:10
icon