MobiFlight Community Support

Hi! I'm having a problem with MFConnector v7.1.3, maybe someone can help?

I'm using the OSEPP Mega 2560 R3 Plus board, and installed my IDE (1.8.1) to C:\Program Files (x86)\Arduino . When I run MFConnector, it does not find the IDE, and when I go to settings and browse, it does not appear to do anything either.

The Mega has no problems connecting to the Arduino IDE, and I can upload sketches and execute them with no issues. Any ideas? Below is a copy of the debug log. According to Device Manager, under "Ports (COM & LPT) > USB Serial Port (COM3)" the instance path is "FTDIBUS\VID_0403+PID_6001+AL00YUCGA\0000". I do see "VID_0403+PID_6001" in the below log, so I'm wondering if there is an issue with the way Windows 10 is recognizing the Mega?

Thanks!

1/22/2017 1:37:29 AM: MobiFlightCache.connect: Clearing modules
1/22/2017 1:37:29 AM: ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
1/22/2017 1:37:24 AM: MobiFlightCache.connect: Clearing modules
1/22/2017 1:37:24 AM: ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
1/22/2017 1:37:21 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" />
1/22/2017 1:37:19 AM: MobiFlightCache.connect: Clearing modules
1/22/2017 1:37:19 AM: ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
1/22/2017 1:37:14 AM: MobiFlightCache.connect: Clearing modules
1/22/2017 1:37:14 AM: ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
1/22/2017 1:37:13 AM: Set Debug in ComboBox: logLevelComboBox
1/22/2017 1:37:09 AM: MobiFlightCache.connect: Clearing modules
1/22/2017 1:37:09 AM: ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
1/22/2017 1:37:04 AM: MobiFlightCache.connect: Clearing modules
1/22/2017 1:37:04 AM: ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
1/22/2017 1:36:59 AM: ExecutionManager.AutoConnectStart:Started auto connect timer
1/22/2017 1:36:59 AM: MobiFlightCache.connect: Clearing modules
1/22/2017 1:36:59 AM: ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
1/22/2017 1:36:59 AM: ExecutionManager.AutoConnectStart:Started auto connect timer
1/22/2017 1:36:59 AM: MobiFlightCache.connect: Clearing modules
1/22/2017 1:36:59 AM: MobiFlightCache.connect: Clearing modules
1/22/2017 1:36:59 AM: Checking for compatible module: VID_9886&PID_0001&MI_03
1/22/2017 1:36:59 AM: Incompatible module skipped: ASTRO Wireless Transmitter - VID/PID: VID_9886&PID_0001&MI_00
1/22/2017 1:36:59 AM: Checking for compatible module: VID_9886&PID_0001&MI_00
1/22/2017 1:36:59 AM: Checking for compatible module: VID_9886&PID_0001
1/22/2017 1:36:59 AM: Checking for compatible module: VID_8087&PID_8008
1/22/2017 1:36:59 AM: Checking for compatible module: VID_8087&PID_8000
1/22/2017 1:36:59 AM: Checking for compatible module: VID_174C&PID_3074
1/22/2017 1:36:59 AM: Checking for compatible module: VID_174C&PID_2074
1/22/2017 1:36:59 AM: Checking for compatible module: VID_1532&PID_0203&MI_02
1/22/2017 1:36:59 AM: Checking for compatible module: VID_1532&PID_0203&MI_01
1/22/2017 1:36:59 AM: Checking for compatible module: VID_1532&PID_0203&MI_00
1/22/2017 1:36:59 AM: Checking for compatible module: VID_1532&PID_0203
1/22/2017 1:36:59 AM: Checking for compatible module: VID_1532&PID_0044&MI_02
1/22/2017 1:36:59 AM: Checking for compatible module: VID_1532&PID_0044&MI_01
1/22/2017 1:36:59 AM: Checking for compatible module: VID_1532&PID_0044&MI_00
1/22/2017 1:36:59 AM: Checking for compatible module: VID_1532&PID_0044
1/22/2017 1:36:59 AM: Incompatible module skipped: Scarlett 2i2 USB - VID/PID: VID_1235&PID_8202
1/22/2017 1:36:59 AM: Checking for compatible module: VID_1235&PID_8202
1/22/2017 1:36:59 AM: Incompatible module skipped: Akai APC40 - VID/PID: VID_09E8&PID_0073&MI_00
1/22/2017 1:36:59 AM: Checking for compatible module: VID_09E8&PID_0073&MI_00
1/22/2017 1:36:59 AM: Checking for compatible module: VID_09E8&PID_0073
1/22/2017 1:36:59 AM: Checking for compatible module: VID_06A3&PID_0836
1/22/2017 1:36:59 AM: Incompatible module skipped: Prolific USB-to-Serial Comm Port (COM8) - VID/PID: VID_067B&PID_2303
1/22/2017 1:36:59 AM: Checking for compatible module: VID_067B&PID_2303
1/22/2017 1:36:59 AM: Checking for compatible module: VID_05E3&PID_0612
1/22/2017 1:36:59 AM: Checking for compatible module: VID_05E3&PID_0610
1/22/2017 1:36:59 AM: Checking for compatible module: VID_05A7&PID_1020&MI_02
1/22/2017 1:36:59 AM: Incompatible module skipped: Bose USB Audio - VID/PID: VID_05A7&PID_1020&MI_00
1/22/2017 1:36:59 AM: Checking for compatible module: VID_05A7&PID_1020&MI_00
1/22/2017 1:36:59 AM: Checking for compatible module: VID_05A7&PID_1020
1/22/2017 1:36:59 AM: Incompatible module skipped: Samsung Galaxy S7 - VID/PID: VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android
1/22/2017 1:36:59 AM: Checking for compatible module: VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android
1/22/2017 1:36:59 AM: Incompatible module skipped: SAMSUNG Mobile USB Modem - VID/PID: VID_04E8&PID_6860&Modem
1/22/2017 1:36:59 AM: Checking for compatible module: VID_04E8&PID_6860&Modem
1/22/2017 1:36:59 AM: Checking for compatible module: VID_04E8&PID_6860
1/22/2017 1:36:59 AM: Checking for compatible module: VID_0403&PID_6001
1/22/2017 1:36:59 AM: Checking for compatible module: VID_0000&PID_0003
1/22/2017 1:36:59 AM: Checking for compatible module: ROOT_HUB30
1/22/2017 1:36:59 AM: Checking for compatible module: ROOT_HUB20
1/22/2017 1:36:59 AM: ^(VID_1B4F&PID_9206|VID_2341&PID_0042|VID_2341&PID_0010|VID_8087&PID_0024|VID_1A86&PID_7523|VID_2A03&PID_0042)
1/22/2017 1:36:59 AM: ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
1/22/2017 1:36:59 AM: No updates necessary. Your version: 7.1.3.0, Latest version: 7.1.3
1/22/2017 1:36:59 AM: Checking for updates
1/22/2017 1:36:59 AM: MainForm() : Logger initialized Debug

Hello

In the past sometimes users report simular problems with other "Mega Clones"

If i remeber right, Mobiflight Admin will set the "ID" if this Clone Megas into Mobiflight Code and after a update-patch this Boards would be find and can conected.
Looks like Arduino IDE itself have no problems with those Boards .... Most useres report that there boards work fine with Arduino but not in MF.

Please wait for a respond of Sebastian. Shure he can solve this by an short hotfix.

Ah, thank you for the feedback-- I will wait and hope it gets added, otherwise I'll put it on the shelf and order an original Arduino Mega.

In the Arduino IDE you have to select the COM port by yourself and you also have to tell which board type you got.
I try my best to make it super easy and therefore I need to know what kind of board is on which COM port.

I will have to add VID_0403&PID_6001 information with the next release. not a big deal.

Hi Sebastian,

I think I have the Arduino IDE set correctly for my board, as shown in the screenshot here (using COM3, which I also have selected in MFConnector):

http://i.imgur.com/meN8uYy.png

Vielen danke! (I hope I remembered that correctly-- my Deutsche class was over 20 years ago now)