MobiFlight Community Support

Hi everybody,

I wanted to let you know that I built in support for the Arduino Uno and that I will release that with the next version soon. I hope that I can do it tomorrow or during the next week latest.

Also the Pro Micro will be again fully supported - with all features from the most recent firmware.

I hope you like that.

Do you have in the road map, analog ports?

Regards

JPG

My Arduino Unos that are just laying around doing nothing thank you very much, and so am I

Dear Sebastian

This is the best news for me, thank you very very veryyy much

You are great man, you make our dreams come true with this great software and also I want to donate but paypal is blocked from Turkey

Great! I bought 20 unos and I can use them right now so imw aiting for the update until my flight sim works

That's awesome news! I just bought an Uno to learn how to use the Arduino, and am very much looking forward to integrating it with X-Plane 11 and Falcon BMS!

Please check version 7.2.0 with the first UNO support

Hi Sebastian

I tried to connect the Uno, it recognizes it, and it uploads the code, but then when i add something (display, button or anything) and try to upload the code i get an error:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at MobiFlight.MobiFlightModule.SaveName()
at MobiFlight.MobiFlightModule.SaveConfig()
at MobiFlight.SettingsDialog.uploadToolStripButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1086.0 built by: NETFXREL4STAGE
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MFConnector
Assembly Version: 7.2.0.0
Win32 Version: 7.2.0
CodeBase: file:///C:/Users/Miri/Desktop/MobiFlight%2072/MFConnector.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1081.0 built by: NETFXREL3STAGE
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1078.0 built by: NETFXREL3STAGE
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1086.0 built by: NETFXREL4STAGE
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1084.0 built by: NETFXREL3STAGE
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1064.2 built by: NETFXREL3STAGE
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1038.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
FSUIPCClient
Assembly Version: 2.0.4008.2
Win32 Version: 2.0.4008.2
CodeBase: file:///C:/Users/Miri/Desktop/MobiFlight%2072/FSUIPCClient.DLL
----------------------------------------
ArcazeHid
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Miri/Desktop/MobiFlight%2072/ArcazeHid.DLL
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.6.1064.2 built by: NETFXREL3STAGE
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.6.1064.2 built by: NETFXREL3STAGE
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
CommandMessenger
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Miri/Desktop/MobiFlight%2072/CommandMessenger.DLL
----------------------------------------
AutoUpdater.NET
Assembly Version: 1.3.1.0
Win32 Version: 1.3.1.0
CodeBase: file:///C:/Users/Miri/Desktop/MobiFlight%2072/AutoUpdater.NET.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

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

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I am sorry to hear that it doesn't work for you.
Arduino UNO Support is kind of experimental because I only have one board which had this CH340 chip.

What happens after you close MobiFlight and start again? Is the confit then there?

Hi Sebastian.

I have the same Uno with a CH340 Chip on it. If i close Mobiflight an i open it again the settings are not saved because i can't even create anything. Every time i connect the Uno I get the message that there are new Mega cards connected and I have to upload the firmware first. Th Card will be first recognized as Uno.

.

After i upload the firmware, the name of the card changes to Unknown.



Once i try to change ne name or Add let's say a button and try to upload the firmware i get the error.



When i close Mobiflight and start it again than it starts everything from the beginning, I get the message that there are Arduino Mega boards connected and I need to upload the firmware. Is it only me having this problem or anyone else as well.

Regards
AlbEagle

Hi,

Thanks Sebastian for your support!

Did this problem get solved?... I'm going through the same issue with the UNO. It would
be nice to have my old board as a scratch pad.
My new Mega is on its way... Just in case.

Thanks!
Gabe

Hi Gabe,

you see, this topic is more than one year old. A lot of things have happend. So the support for the UNO is stopped. The causes are manifold.
Sebastian has decided to focus on the MEGA by further developing this software. The UNO (and others) would require too much time.

It's good that you ordered a MEGA. With that you will have a lot of fun with MF.