MobiFlight Community Support

Hi,

I've configured MobiFlight and LED for the Parking Brake example as well as a 7-Segment MAX7219 re the COM1 example. Everything works as it should (tests 100%) except when I run FSX to test the interface between the sim and hardware. I've run MF as admin and it registers Modules and FSUIPC Status with a green tick.

FSUIPC Value and Output Value remains 0 (Not pulling through the value from the Sim).

Feels like I'm missing something obvious. Please help me if possible.

Tx.

Gary

Hi Gary,

welcome to MobiFlight.

Did you use the original Airplanes of the FSX oder did you use any add on?

Which Aircraft do you mean with your description above?

If you test with the sim, did you start the logging of MF - did you receive any error-messages or what is the reaction of MF?

You see, a lot of questions to figure out, what kind of error you have.

Be so kind and report the EventIDs and Offsets you use for the ParkingBrake (LED/Switch) and the MAX7219.

Hi Stephan,

Thanks so much for your response and will try to be as comprehensive as possible.

I am busy building 1:1 scale 737NG and use ProSim737 and mainly FDS-SYS I/O boards as my interface mechanisms. Your MobiFlight solution appeals to me much more than my current TQ phidget configuration as it appears to be much more accessible and supported from an FS perspective. I hope to use MF for my Radio Stack and automated TQ.

I am using FSX with Wideserver and FSUIPC 4.2.

My 737NG model is the ProSim737 Jetstream-Boeing 737-800 add-on. I have tried the stock FSX 737-800 as well.

Yes I had the "Logging" function checked and that generated the following:

2017/10/17 09:37:38 PM(351): Command: SetModule <1,0,0,10000,124;>
2017/10/17 09:37:38 PM(21): Command: SetModule <1,0,0, ,255;>
2017/10/17 09:37:38 PM(21): Preventing entering EnergySaving Mode: KeepAlive!
2017/10/17 09:37:38 PM(21): ExecutionManager.TestModeStop:Stopped test timer
2017/10/17 09:37:36 PM(481): MobiflightModule.connect: Connected to Default at COM5 of Type MobiFlight Mega (DTR=>True)
2017/10/17 09:37:36 PM(471): No updates necessary. Your version: 7.4.0.0, Latest version: 7.4.0
2017/10/17 09:37:35 PM(971): Checking for updates
2017/10/17 09:37:35 PM(931): MobiflightModule.disconnect: Disconnected MobiFlight Mega at COM5
2017/10/17 09:37:34 PM(300): MobiflightModule.connect: Connected to Default at COM5 of Type Arduino Mega 2560 (DTR=>True)
2017/10/17 09:37:34 PM(150): MainForm() : Logger initialized Info

It did not display any error-message that I could see.

When I did a Test, the Brake LED lit up and the COM1 7-Segment displayed 123.45 as your tutorial explains. The FSUIPC Value reads 0 and the Output value reads 10000 (which I assume is the result from the Transform : $+10000 value. The 7-Segment then reads 100.00

At this point, Modules and FSUIPC Status have green ticks and "Running....." is displayed on the right of the same bar.

COM1 Active
Offset - 0x034E
Value Type - Int
Bytes - 2
Mask - 0xFFFF
BCD - Checked
Transform - $+10000

At this point, logically, the moment I activate (select "active") the selection and Run, the FSUIPC Value and Output Value should be read directly from the Sim? But it does not. This is where I'm stuck.

Hope this is sufficient info to give you a base to start with.

Much appreciated.

Baie dankie.

Gary

I am using FSX with Wideserver and FSUIPC 4.2.

Hi!

Please at first confirm THIS was a issue..... FSUIPC is currently in version 4.9xx 4.2 is from before 2010 and older than 7 Years !!!
If you realy use that just update to current Version and test again.

By the Way....

The ProSim ( Congratulation for this high professional Software) NOT use Standard Offsets... You have to define most of the Data yourself inside the Prosim Interface,
But Whatever the Radio Frequency normaly should work, too.
Please check the follow.... If you create a Config and try to run directly after there can be a issue to "sync" with the Sim Data.... That normaly not exist when you Restart Mobiflight! But you simply can solve this when you click the EDIT Button of the Config one time while it is running..... Directly Close the Config Wizzard again.... that occures in a Update of FSUIPC data.

*****
Summary.... Please check your FSUIPC Version and confirm you are UptoDate.... If Problem still exist we can talk again.

Have Fun !

Hi Stephan,

I updated FSUIPC to the latest version. Unfortunately it still presents the same issues.

Tx.

Gary

Hi Stephan,

Do you have any additional thoughts on the reason why the fsuipc values are not being read from the sim?

Tx.

Gary

Hi Gary,

did you update to FSUIPC 4.99xx or to V5.xx? The 5.xx is only for P3D! So I think for your configuration you need the 4.99xx.

If MF reads out the sim-values (your Offset 0x034E is correct for active Frequency - 0x311A is for the Standby-Frq) the MF-input value should be the same as in the sim (without the leading 1).
Did you take the EventID 75752 for the Parking Brake(with 0 (unset) and 1 (set))?

What happend in the MF-logging area if you move the encoder for COM1 STBY? Is there activitiy? Same if you set the Parking Brake.
Or if you use the active COM1-Frq. is it in the MF-output Area and communicated in the logging area?

If MF does not display any changes, it will not recognize any change. There may be no active connection to the FSUIPC.
So be so kind to test the configuration first only with a standard aircraft. If these works, we can try other ones.
Please report your expieriences.

Hi Stephan,

Tx. I picked that up and updated to 4.971.

There's no activity when I move the encoder or switch from STBY to Active or when turning the rotary.

I've used both Active and STBY and still no input from FSUIPC.

I loaded the stock C172 with still no luck.

I'm convinced, despite MF indicating it is linked to FSUIPC, etc that it is not. Does your program interrogate the link by internally testing the communication between FSUIPC in FSX and MF before it confirms it is actually linked and running?

Has anyone else experienced this?

I'm stumped.

Tx.

Gary

Did your MF runs on the same Computer like FSX and FSUIPC? That is the Condition!

Hi again....

I think you got a issue in your setup basicly.... This problem was never report in this form..... so i pretty shure the problem is in your system.

Please do it like Stephan request...... Try to get a Complete Neutral Testing situation !

Simply use a MEGA..... Set TWO Devices ( 1x Button or Switch and 1x LED Output )
In Config please use the "Parking Brake Tutorial" .... Set the LED for the ParkingBrake Output and the Sitch/Button for the Input.
Now Run FSX and Mobiflight and use a STANDARD Aircraft like the Stock Cessna.
Push the button... So the Brake must Toggle....
Observe the LED... If brake is set it must bi ON if brake is NOT set it must be OFF.

If THIS is working THEN we know Mobiflight, Your Hardware and all the Comunication is working fine.
When your Prosim for example not work correct we can say 100% that you make a issue in your config !

Summary... Please use this standard testing to confirm the System is OK.... then we can help you with the config or can better research a technical issue !

Thanks !

Hi pizman82,

Thanks for your input. I did as you suggested and the moment I threw the switch I got a " The connection to FSUIPC got lost" error. The log below:

2017/10/30 01:24:49 PM(315): Error on config execution. FSUIPC Error #9: FSUIPC_ERR_NOTOPEN. The connection to class instance 00 of WideClient.exe is not open.
2017/10/30 01:24:11 PM(349): Preventing entering EnergySaving Mode: KeepAlive!
2017/10/30 01:24:11 PM(349): ExecutionManager.TestModeStop:Stopped test timer
2017/10/30 01:24:09 PM(799): MobiflightModule.connect: Connected to Default at COM5 of Type MobiFlight Mega (DTR=>True)
2017/10/30 01:24:09 PM(769): No updates necessary. Your version: 7.4.0.0, Latest version: 7.4.0
2017/10/30 01:24:08 PM(289): Checking for updates
2017/10/30 01:24:08 PM(239): MobiflightModule.disconnect: Disconnected MobiFlight Mega at COM5
2017/10/30 01:24:06 PM(626): MobiflightModule.connect: Connected to Default at COM5 of Type Arduino Mega 2560 (DTR=>True)
2017/10/30 01:24:06 PM(393): MainForm() : Logger initialized Info

All's fine up to the testing point. The moment I set each component to "active" it should pull through the FSUIPC setting immediately and this does not happen.

I'm convinced it has something to do with the actual configuration and settings of the machine I'm working on as opposed to MF or FSUIPC.

Let me reset using my actual Sim machines and not my development computer. I'll give further input once I've done that.

Much appreciated.

Gary

Hi !

2017/10/30 01:24:49 PM(315): Error on config execution. FSUIPC Error #9: FSUIPC_ERR_NOTOPEN. The connection to class instance 00 of WideClient.exe is not open.

Not shure if this is a standard Error message but the "wideclient" info confusing me....
As Stephan ask you some postings ago..... Do you install and run mobiflight on the SAME computer, where FSX is installed ??
If you use a client for Mobiflight you need a Registred (Payware) Version Of FSUIPC AND "Wideclient" from pete Dowson !
AND Wideclient must be configured correct before you start working with mobiflight !

Please Confirm This !

*****

Other thing i see....

All's fine up to the testing point. The moment I set each component to "active" it should pull through the FSUIPC setting immediately and this does not happen.

Thats Wrong ! ....
The "Active" Checkbox is not used to enable or disable configs WHILE Mobiflight is still running.... THAT not work in most cases.
If you like to activate/deactivate a funktion then please STOP mobiflight ( if its running at the moment) THEN Activate the stuff you need .... and THEN click to RUN again.
I recommend basic Rule.... Aslong Mobiflight Connector is running ( RUN Button on Top) do never any changings in the Software !

Shure this is not forbidden and you can do that.... BUT This occures in Problems sometimes.... If you Restart Mobiflight that not happend.
Simple example is that a value of a Output config you activate WHILE MF is still RUN then it have no value aslong you klick this config manualy..... If You Restart Mobiflight it will have normaly all values automaticly that are active WHILE Startup !

For the future.... If you do changes in Mobiflight i recommend to do Restarts of Software ( when you change something in the config) or Restart of Arduino if you change something in the Firmware or devices. ... If you just Activate/ Disable a Config Line you not need a restart of the hole software... but a STOP and RUN of connector again is high recommend !