MobiFlight Community Support

Hello all,

I use mega 2560 board. Its usb driver is CH341SER which can be found on internet. My board has connection problem with FSUIPC (newest version). Cant receive data from it. Aİrcraft PMDG737 and I did change the ini file and enable data broadcast=1. When I teste parking brake on tutorial 1, everything was perfect between board and mobiflight software. I can light the LED but cant do from pmdg aircraft or cessna.

Other problems is happenening while i try to firmware update. I think these 2 problems have the same core reason. I am sharing error text with you.

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

************** Exception Text **************
System.ArgumentNullException: Value cannot be null.
Parameter name: value
at System.Enum.EnumResult.SetFailure(ParseFailureKind failure, String failureParameter)
at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at MobiFlight.SettingsDialog.saveSettings()
at MobiFlight.SettingsDialog.okButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.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.0.30319.18444 built by: FX451RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MFConnector
Assembly Version: 7.5.0.0
Win32 Version: 7.5.0
CodeBase: file:///C:/Users/PC/Downloads/MFConnector.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34251 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34270 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
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.0.30319.18408 built by: FX451RTMGREL
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.0.30319.34234 built by: FX452RTMGDR
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.0.30319.18408 built by: FX451RTMGREL
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.0.30319.18408 built by: FX451RTMGREL
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/PC/Downloads/FSUIPCClient.DLL
----------------------------------------
ArcazeHid
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/PC/Downloads/ArcazeHid.DLL
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
AutoUpdater.NET
Assembly Version: 1.3.1.0
Win32 Version: 1.3.1.0
CodeBase: file:///C:/Users/PC/Downloads/AutoUpdater.NET.DLL
----------------------------------------
CommandMessenger
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/PC/Downloads/CommandMessenger.DLL
----------------------------------------
NCalc
Assembly Version: 1.3.8.0
Win32 Version: 1.3.8.0
CodeBase: file:///C:/Users/PC/Downloads/NCalc.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.

Hi.

Your Problme is verry confusing.

You say you do the tutorial for Parking Brake and it work fine.
Then you say it wont work with PMDG or Cessna . Do you mean the Standard C172 Cessna from FSX od a AddOn Cessna ??
Finaly you say you can not flash a Firmware..... But if you do the Parking Brake tutorial you MUST have flashed a firmware already.
(Board will not work for tutorial test if it not be already flashed to MF Board)

Whatever....
If your Parking Brake tutorial work then MF and Arduino work ok..... And it must also work for PMDG if you use correct Offsets !

****
About the flashing problem.
Please simply "reset" your Arduino to exlude a Software Problem on it.
Open your ARDUINO IDE and use the "EEPROM Clear Sketch" (Google that if you need instructions)
RUN the sketch .... Then your Arduino EEPROM is formated empty.
THEN it should be normaly no problem to install firmware by mobiflight !

Hello

I think theres a misunderstanding with my problem.

Problem is that fsuipc and mobiflight doesnt communicate with each other.

I am able to light a LED on test menu in mobiflight application.

But I cant do that on any airplane in simulator.

I am sure that offsets are correct.

I gave an wrong statement about firmware, since I couldt loaded firmware.

But when ı click to ok on mobiflight, ı have the errors.

Theres miscommunication between mobiflight and fsuipc.

Again i not understand....

1. firmware ....
What do you mean with :

I gave an wrong statement about firmware, since I couldt loaded firmware.

Is it fixed an you could load the firmware already ? If Yes do you use current Version 7.5 ??

***
2. What do you mean here ?

I am able to light a LED on test menu in mobiflight application.
But I cant do that on any airplane in simulator.

With a OUTPUT you will do nothing in the simmulator.... It will just READ a status and controll YOUR LED.... You will not be able to change something by a OUTPUT Config !
***

3. FSUIPC Connection

Problem is that fsuipc and mobiflight doesnt communicate with each other.

Simply check the Symbols down left of Mobiflight Window.... MODULE will tell you if your Arduino is connected.... FSUIPC Status will tell you if FSUIPC connection is ok.
If FSUIPC Symbol have a Green Mark then Mobiflight have a working FSUIPC Connection. If NOT then maby your Sim is not working correct or you have a outofdate FSUIPC.


4. Offsets.

I am sure that offsets are correct.

Are you sure ?
So tell us what Simulator ? FSX, P3D Xplane
Tell us what Aircraft you use ..... And please not say Cessna.... Tell me if its a AddOn... stock Cessna and so on.
tell me what testing function you like to use ( For example Autobrake)
Finaly tell your complete OUTPUT Config.... Offset, Typ, Size , Bitmask and if you use it all entrys in compare, Transform, interpolation and so on.


5.

But when ı click to ok on mobiflight, ı have the errors.

And what OK field of the 20-30 possible in MF do you mean.
On what situation you click OK and what exactly goes wrong then ?


****

apollogy for all this questions... But you report a Problem that is never reported before.... I can not reproduce it at the moment with this poor data. And i can not see your system or your screen. So YOU must give me much more informations.

Again i not understand....

1. firmware ....
What do you mean with :

I gave an wrong statement about firmware, since I couldt loaded firmware.

Is it fixed an you could load the firmware already ? If Yes do you use current Version 7.5 ??

There was a typo. I could upload firmware. But when click ok on EXTRA->SETTINGS-->MOBIFLIGHT MODULES I have the problem.

***
2. What do you mean here ?

I am able to light a LED on test menu in mobiflight application.
But I cant do that on any airplane in simulator.

With a OUTPUT you will do nothing in the simmulator.... It will just READ a status and controll YOUR LED.... You will not be able to change something by a OUTPUT Config !
***
There is a connection between my board and mobifligt. I can run test without any problem.But I can't set parking brake on cessna and PMDG 737. This is the issue. And FSUIPC value & Output value are not changing when I RUN the mobiflight and set parking brake.

3. FSUIPC Connection

Problem is that fsuipc and mobiflight doesnt communicate with each other.

Simply check the Symbols down left of Mobiflight Window.... MODULE will tell you if your Arduino is connected.... FSUIPC Status will tell you if FSUIPC connection is ok.
If FSUIPC Symbol have a Green Mark then Mobiflight have a working FSUIPC Connection. If NOT then maby your Sim is not working correct or you have a outofdate FSUIPC.

I downloaded latest free version of FSUIPC from the website. I am sure it is newest version. And mobiflight software is also newest version.


4. Offsets.

I am sure that offsets are correct.

Are you sure ?
So tell us what Simulator ? FSX, P3D Xplane
Tell us what Aircraft you use ..... And please not say Cessna.... Tell me if its a AddOn... stock Cessna and so on.
tell me what testing function you like to use ( For example Autobrake)
Finaly tell your complete OUTPUT Config.... Offset, Typ, Size , Bitmask and if you use it all entrys in compare, Transform, interpolation and so on.


5.

But when ı click to ok on mobiflight, ı have the errors.

And what OK field of the 20-30 possible in MF do you mean.
On what situation you click OK and what exactly goes wrong then ?


****

apollogy for all this questions... But you report a Problem that is never reported before.... I can not reproduce it at the moment with this poor data. And i can not see your system or your screen. So YOU must give me much more informations.

Please check my answers above and I will upload I video for better undertanding.

Hi
Badly we both have a little comunication problem

****
In Point 3 i ask you about the green Checkmark of FSUIPC connection and your Versions.
But your awnser is already problematic !

You tell me just...

I downloaded latest free version of FSUIPC from the website. I am sure it is newest version. And mobiflight software is also newest version.

Why you not simply tell me if the green Checkmark i ask you is ON or OFF ??
And why do you tell me "I am sure its newest version"... Simply tell me what Sim you use and what version you download. Then I will tell you if this is correct.
Belive me.... All Users are sure they did correct things.... But in 9 of 10 cases the user make a error.... And its hard for me to find it aslong users not tell me what they do.

***
summary.
Make a Video.... OR Explane me in your next Posting EXACT what you need...
NOT tell me what you "think" you know sure Tell me FACTS !
NOT tell me that you use correct Offsets.... tell me The offset !
NOT tell me you have newest Version .... tell me number of Version !
NOT Say " I have then a Problem" ... Tell me exact WHAT the term of Problem is.

I want realy help you.... But my time is limmited to ask you 1000 things. You must report the problem in a good kind so i can understand and rebuild it without need of multiple re-questions to you !

Hello

I solved the problem by clearing EEPROM and reinstalling firmware. Somehow I have communication between mobiflight and FSUIPC.

Yet theres a video that shows my error and it still exits but it doesnt block anything, it is just an error and nothing else.

Maybe it will give you a hint.

https://vimeo.com/294959782

*Yes I had green checkmarks before.

Thanks again

Hello

Problem still continues, I was able to light YAW DAMPER light on PMDG737. Offset (0x6449)

But some how theres no dataflow between FSUIPC and mobiflight now. They connection problems with each other as in the first case.

I tried to restart and tried to load same or different settings such as MCP heading light but its not updating FSUIPC status on mobiflight.

Still theres connection green checkmark. But maybe communication between them hangs.

********* FSUIPC4, Version 4.974 (24th February 2018) by Pete Dowson *********

Can it be that the problem on the video is the root cause of the communication problem between mobiflight and FSUIPC ?

Thanks

Now we get closer. (thanks for the video)

The Error warning is not correct and show a problem. Whatever i can not see it. Here SEBASTIAN must have a look on it when he´s back from buisnes trip.
So finaly i can not reproduce this at the moment.

But i also can not see a context between this issue and the problem you not recive Data.
If Green Checkmark is OK and if Mobiflight RUN then Data must be recived.
Sure... Maby in case of the Problem your LED will not light ( we need to find out) BUT In connector Window (Output Tab) the value of Sim MUST be shown in the FSUIPC Collum.

So sorry i can not solve your problem.... But i´m 99% sure that THIS issue is not the reason for non reciving data.

First Aid:

In case that nobody rport this before i recommend to change testing situation if possible.
1. Reinstall Mobiflight Software.
2. Start Mobiflight and Sim as Admin
3. Use a "new" Mega Board . ( By the way i not know why you need "CH341SER" or what this is needed for. On my system i simply connect board and it work)
4. Do your testing at first ONLY with Standard FSX Aircraft (Cessna) and with absolutly basic Offsets like Flaps, parking Brake, Gear and so on.

I hope you can find the reasing by this testings !

Ok thanks, I will try to upload a second video that shows the communication problem.

Ok I will show it.

But please to prevent again comunication problems between you and me...

Please do also the recommend steps ...

1. Reinstall Mobiflight Software.
2. Start Mobiflight and Sim as Admin
3. Use a "new" Mega Board . ( By the way i not know why you need "CH341SER" or what this is needed for. On my system i simply connect board and it work)
4. Do your testing at first ONLY with Standard FSX Aircraft (Cessna) and with absolutly basic Offsets like Flaps, parking Brake, Gear and so on.

And report to us the detailed results....
Summary you not nee to make a video of a issue that would be solved with for example a reinstall.
In the time, you need to create the video, you can also make the reinstall and you can flash a new Mega Board.... That would be much more productive like to show me a Video of a issue i can not solve after all.