MobiFlight Community Support

Hello!

With 7.10, I would like to move my test bed from one Win10 PC to a new one built for MSFS. So I moved a 2560 and Max7219 board over, but the testing the display does not work. Everything appears to be connected properly and the PC sees the 2560 so I'm at a loss as to why this hardware works on the old PC, but not on the new.

Any suggestions?

Thanks,

Mike

Hi Mike

Like always.... we need more detailed information !

Everything appears to be connected properly and the PC sees the 2560

Who is the "PC" ?? Does Windows see the Board as a Arduino Mega.... or do you mean still Mobiflight see the Board as a Mobiflight Board ?
(So modules symbol lower left is green?)

How do you "test" the Display.... Via TEST in Display Tab or via a Sim Output ?


You see.... So many Questions.... We can not help if we not know 100% what you doing and what you expect to do.

So tell us step by step when the problem occure and what is already working !

Oops should have seen that response coming!

So
- both PC's are running the same version of MF
- both PC's are running the same Arduino code
- yes MF sees the board as an Arduino Mega
- yes the new PC sees the Mega on the correct COM port
- the test is done from the Display Tab
- when the test is done from the Main panel, the panel line and board blink rapidly; the display is always dark
- the wiring between the Mega and the display does not change when you move between PC's

Anything else you'd like to see?

Is the wirework already finished and solder? Or is this a improvisonal breadboard system with jumper wires.

The most easy test would be.... Take your board including the display back to PC1 and test it there.

If you realy can confirm system work perfect on the Old PC again but n ot on the new one we got a strange problem. For me it sounds more as you got a bad connection ( an case of touching the System and carry it to the new spot. Those Max9219 are verry sensitive. without perfect solder work just the touching of the table can occure in a error.


Another idea to confirm.... Create a simple In or Output on the Board and test on the new Computer.... Like a Button or a LED. We need to know if Board technical work 100%

It's just loose wired. However, I can move it back to old PC - works fine. New PC - nothing. Is there a way to purge the Mega?

Technical Yes.... But i realy wondering. If you can choose in Diplay Tab the correct Mega and also the Display Device on it and there is no Error warning like "orphand module found".
Then it should work.
Do you test a new LED or Button to 100% confirm the Board itself is detected on the new Computer ?



If you like to reset the Mega.... Go into your Arduino IDE..... Choose from the example List the premade sketch "EEPROM CLEAR" and upload it to the board. Then reset the Board ( By button on it or via "disconnect- wait 5 seconds - reconnect" This runnnig of that sketch will delete all MF settings including the firmware and devices.

NOTE: You need to flash firmware new,and you also must create all devices for new !

So a bit more - I did get an LED working on the new PC - so I'm going to work with both Mega's on that new PC for now.

The other thing is that the following error has shown up 2-3 times. I ignored it the first time because I was multi-tasking and thought it was something I was doing at the same time. However, this showed up when I was just starting MF. I can't replicate it.

Unhandled Exception

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.OrphanedSerialsDialog.updateOrphanedList()
at MobiFlight.OrphanedSerialsDialog..ctor(List`1 serials, DataTable dataTable, DataTable inputDataTable)
at MobiFlight.MainForm._checkForOrphanedSerials(Boolean showNotNecessaryMessage)
at MobiFlight.MainForm.orphanedSerialsFinderToolStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.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.ToolStripDropDown.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.ToolStripDropDown.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.8.4220.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MFConnector
Assembly Version: 7.10.0.0
Win32 Version: 7.10.0
CodeBase: file:///D:/MobiFlight/MFConnector.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4200.0 built by: NET48REL1LAST_C
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.8.4200.0 built by: NET48REL1LAST_C
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.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4220.0 built by: NET48REL1LAST_C
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.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4200.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
AutoUpdater.NET
Assembly Version: 1.6.0.0
Win32 Version: 1.6.0.0
CodeBase: file:///D:/MobiFlight/AutoUpdater.NET.DLL
----------------------------------------
FSUIPCClient
Assembly Version: 3.1.18.324
Win32 Version: 3.1.18.324
CodeBase: file:///D:/MobiFlight/FSUIPCClient.DLL
----------------------------------------
ArcazeHid
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/MobiFlight/ArcazeHid.DLL
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
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:///D:/MobiFlight/CommandMessenger.DLL
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
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.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.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 have seen this message before. Have you enabled beta-updates? Please do so if not. I will later double check but i think i have addressed this in the current beta.

EDIT: Yes, see https://bitbucket.org/mobiflight/mobiflightfc/issues/264/exception-thrown-in-orphaned-modules

and one more thing. Your boards all store their config locally on the board. They can't forget the configuration when moving them from one PC to another. The MobiFlight config can be simply copied and it will 100% work.

If you have a new PC it is easy to forget to install the basic board drivers. There are different board chips that all require a specific driver: Arduino Original vs. FTDI vs CH-340.

For upload of the MobiFlight you need Arduino IDE installed and you have to set the path to it.

That's it. There can't be more things that you'd have to do. Promise.

Added the beta update setting - got newest version (7.10.0.6) However, now when I try and start MF, nothing happens - even running MF as admin - huh?

Nothing happens. What does that mean?
Admin permissions are typically not required.

Exactly that...nothing. No evidence that the app starts. Not even showing up in task manager.

I think I've seen this before on my old PC. Ended up re-installing, but it would be nice to find out just what is (or isn't) going on.

To fix it, I 2click on the installer - MobiFlightSetup-7.10.0.6.exe. Then MF starts. Then MF starts normally with MFConnector.exe.

Hello!

With 7.10, I would like to move my test bed from one Win10 PC to a new one built for MSFS. So I moved a 2560 and Max7219 board over, but the testing the display does not work. Everything appears to be connected properly and the PC sees the 2560 so I'm at a loss as to why this hardware works on the old PC, but not on the new.

Any suggestions?

Thanks,

Mike

Maybe your new laptop has any restrictions or is blocking some actions.

Hi Tomasine
Welcome to Mobiflight !

Whatever we are thankfull to every single comment who like to help other people.....

Please check the date.

This problem was reported 2 Years ago !
And its related to Version 7.10 ..... We meanwhile are on Version 9.3.0
So pretty sure the user solve the problem years ago or we fixed it within one of the 20 Versions between that day and now.

But again. Thank you. Feel free to support other people. But please not refresh topics older then some months !