MobiFlight Community Support

Hello, I have been using my Arduino setup with another link program for FSX and now P3Dv3. I found your software and wanted to test it and see how it works.

After much testing and trying different things, MobiFlight does not see my Mega 2560 R3. The Connector debug shows

11/12/2015 1:04:37 AM: No arduino device -skipping: VID_8087&PID_0024
11/12/2015 1:04:37 AM: No arduino device -skipping: VID_413C&PID_2005
11/12/2015 1:04:37 AM: No arduino device -skipping: VID_2341&PID_0042

However, in my device manager (Windows 7 64-bit), in Ports (COM & LPT), it shows Arduino Mega 2560 R3 (COM1)
The driver provider is "Arduino LLC (www.arduino.cc)" and version "5.1.2600.0". Driver date "11/15/2007". Seems old, I'll check on that.
In the driver -> Details -> Hardware Ids, it shows
USB\VID_2341&PID_0042&REV_0001
USB\VID_2341&PID_0042

Anything more I can provide to help with this? I saw a similar post but it was with WinXP. My O/S is Windows 7.

Thanks!
Mike
PS: The buttons on the forums are in another language. I am trying to navigate as best as I can.

Hi Mike,

first: Welcome to MobiFlight and the forum. I am glad that you want to try out my software

MobiFlight has been tested with WinXP,Win7 and Win10. The board that you have should really work nicely because I own one a similar one with the same PID VID combination.
I improved Arduino detection and it does not rely anymore solely on PID/VID but also checks the name of the attached module... I am really wondering why it cannot connect to yours.

Are you using the most current version of MobiFlight?

Thank you for the reply.

I am using MobiFlight Connector Tool v6.1.5 Build 20151010

I have it connected to my USB hub (Location: Port_#0001, Hub_#0004) on COM1 and the port settings are 115200, 8-n-1. I have tried with and without FIFO buffers and the driver is provided by Arduino LLC, v5.1.2600.0 (11/15/2007), not digitally signed. If any of that makes a difference?

Mike

Hi Mike,

have you checked in the settings whether the Arduino Board gets really not listed?

It is listed under MobiFlight Modules -> Configured modules

It Shows "Arduino Mega 2560" (not the R3, though?)
Firmware n/a
Port COM1
Serial n/a
Type Arduino Mega 2560

I tried my other Arduino Mega 2560 which is on COM4 and same results.

Hi Mike,

that's actually allright then. Just right-click on the module and perform "update firmware". The Arduino then turns into a MobiFlight Board.
The steps are also documented under http://www.mobiflight.com/en/documentation/firmware.html

Let me know if it worked for you.

I will release an update where this is going to be a lot simpler, there will be an auto-update function.

Hello Sebastian.

I tried upgrading the firmware as you mentioned. Then I get this pop-up box:

"There was an error on uploading the firmware! Enable Debug Logging for more details."

The box below the main window doesn't show anything useful and isn't scrollable so I can't see if any debug information was logged during the failed firmware upgrade.

Here is the debug log:

11/15/2015 4:04:51 AM: 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" />
11/15/2015 4:02:06 AM: Something went wrong when flashing with command
"D:\Arduino_FSX\hardware\tools\avr\bin\avrdude" -C"D:\Arduino_FSX\hardware\tools\avr\etc\avrdude.conf" -patmega2560 -cwiring -P\\.\COM1 -b115200 -D -Uflash:w:"D:\Arduino_FSX\firmware\mobiflight_mega_1_4_0.hex":i
11/15/2015 4:02:06 AM: Exit Code: 1
11/15/2015 4:01:06 AM: RunAvrDude : -C"D:\Arduino_FSX\hardware\tools\avr\etc\avrdude.conf" -patmega2560 -cwiring -P\\.\COM1 -b115200 -D -Uflash:w:"D:\Arduino_FSX\firmware\mobiflight_mega_1_4_0.hex":i
11/15/2015 4:01:06 AM: RunAvrDude : "D:\Arduino_FSX\hardware\tools\avr\bin\avrdude"
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_8087&PID_0024
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_413C&PID_2005
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_2341&PID_0042
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_2341&PID_0010
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_18D1&PID_4EE7
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_18D1&PID_4E42&MI_01
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_18D1&PID_4E42&MI_00
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_18D1&PID_4E42
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_18D1&PID_4E41
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_16C0&PID_05BA
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_13FE&PID_1D00
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_10C4&PID_82C1
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_10C4&PID_82C0
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_1058&PID_0403
11/15/2015 4:00:52 AM: No arduino device -skipping: Vid_1038&Pid_0100
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0BDA&PID_0152&MI_01
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0BDA&PID_0152&MI_00
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0BDA&PID_0152
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0BC2&PID_50A1
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0971&PID_2005
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0955&PID_7330
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0930&PID_6545
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_07B4&PID_020D
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0781&PID_A3A4
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0781&PID_5151
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_068E&PID_00FF
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_068E&PID_00F2
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_05AC&PID_1260
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_058F&PID_6387
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_058F&PID_6366
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_050D&PID_8053
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_050D&PID_0304
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04E8&PID_6866&MS_COMP_MTP&SAMSUNG_Android
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04E8&PID_6866&ADB
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04E8&PID_6866
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04E8&PID_6860&Modem
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04E8&PID_6860&ADB
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04E8&PID_6860
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04E8&PID_3328
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04CA&PID_004F&MI_01
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04CA&PID_004F&MI_00
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_04CA&PID_004F
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_046D&PID_C24E&MI_01
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_046D&PID_C24E&MI_00
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_046D&PID_C24E
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_046D&PID_C218
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_046D&PID_C05A
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_046D&PID_082C&MI_02
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_046D&PID_082C&MI_00
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_046D&PID_082C
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_044F&PID_B305
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0425&PID_F102
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_03EB&PID_3301
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_03EB&PID_2FEF
11/15/2015 4:00:52 AM: No arduino device -skipping: VID_0000&PID_0000
11/15/2015 4:00:52 AM: No arduino device -skipping: VIA_ROOT_HUB
11/15/2015 4:00:52 AM: No arduino device -skipping: ROOT_HUB20
11/15/2015 4:00:49 AM: MainForm() : Logger initialized Debug

This usually happens, if avrdude cannot talk to your module - that means, that some other process has established a connection. This can be either MF (but it normally shuts down the connection before calling the firmware updater) or the Arduino IDE Serial Monitor.

Do you have any other program runnnig that might have a connection to your module?

There is nothing else running that would access the COM ports or my Arduino. I tried my other Arduino Mega 2560 R3 and got the same results.

I also tried using avrdude by itself outside of any program using the command line generated by MobiFlight (found it in the debug log). Also, I downloaded a GUI for avrdude and tried writing to the Arduino with that. Then, I tried to do this with FLIP 3.4.7 and it doesn't write to the Arduino cards either. I get and "Address is out of range" error when trying to load the mobiflight_mega_1_4_0.hex file in FLIP.

I am still trying different things.

It really shouldn't be that hard.
I can offer you a Teamviewer Session to have a look at it. Tonight I also release a new version which should work a lot easier.

Hello,
I just joined this group
I have installed the latest version of mobiflight and arduino.I bought arduino mega2560 r3 clon (contains ch 340)
mobiflight and arduino worked in my first work(I watch mobiflight getting started totarial).everything is normal no problem.But the next day mobiflight not recognize mega2560
I watched many videos and read articles but I could not find a solution.Then i bought new mega2560(without ch340)
new mega 2560 worked the first day. but didn't work the next day either
why my mobiflight first running no problem then not recognize mega2560
please help.


Alparslan Ozguc(Turkey)

Hi,

sometimes i have similar problems.

But it is not MF nor is it the Arduino.

What i found out is, that it is dependend of the USB-cable and even the USB Port on your computer.
Strange here: connected to lets name it Port-A my Arduino / MF worked for 4 weeks.
Nothing changed but suddenly it does not.
Pluggin into Port C it worked again. Same cable, same config

Just change cable, change ports....

And even if the Arduino IDE always finds your Mega, regardless of the cable or Port, MF does not.

Exlplanation? Sorry, none. There must be something very strange going on in deep Windows core.

Kai

thanks your answer.
System.ArgumentNullException:
Parametre name: value
konum: System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
konum: System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
konum: MobiFlight.UI.Panels.Settings.GeneralPanel.saveSettings()
konum: MobiFlight.UI.Dialogs.SettingsDialog.saveSettings()
konum: MobiFlight.UI.Dialogs.SettingsDialog.okButton_Click(Object sender, EventArgs e)
konum: System.Windows.Forms.Control.OnClick(EventArgs e)
konum: System.Windows.Forms.Button.OnClick(EventArgs e)
konum: System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
konum: System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
konum: System.Windows.Forms.Control.WndProc(Message& m)
konum: System.Windows.Forms.ButtonBase.WndProc(Message& m)
konum: System.Windows.Forms.Button.WndProc(Message& m)
konum: System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
konum: System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
konum: System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Hi Guys.
Please NOT Re-open a 6 Year old Topic..... Create a new One !!!