[LVARs]

Hey John!

If I change aircraft from the FBWA320 to Asobo 787, all the latter LVARS are still visible when I scan for LVARs.  After reading the advanced user documentation, I think the LvarScanDelay option may help.  

[LVARs]

Apologize upfront is this has been posted elsewhere; however, I could not find a resolution in my search.  In short, are you tracking a problem with loading/reading LVARs when switching aircraft?  For example, if I switch between the FBW A320 and Aerosoft CRJ, some of the latters LVARS (e.g. altitude, landing elevation, heading values) won't load.  This problem is correctable by reinstalling FSUIPC 7; however, I'm wondering if it's possible for FSUIPC to flush the LVARs each time it's launched? Thank you in advance!

Matt 

[XMLVAR and Aircraft variables (A:)]

Afternoon, Paul!

I'm curious if its possible to manipulate XMLVAR, Event (K:), and Aircraft (A:) variables via your .dll; or, are we limited to SIMVARs and LVARS?  

[Fuel Pumps]

Incredibly helpful...thank you, John. 

[Fuel Pumps]

Has anyone had luck manipulating the fuel pumps on any of the Airliners (e.g. 747, 787 or A320) in MSFS?  I've tried offsets 3104 and 3125; although, they're reported as working in the v.28.ods, I could not get them accurately report the setting, or manipulate the controls.  I've also tried simvar TOGGLE_ELECT_FUEL_PUMP, to no avail.  Any advice would be greatly appreciated.  

[A320.hvar file (request)]

Thank you very much, John!  These HVARs replaced H:A320_Neo_FCU_HDG_INC and H:A320_Neo_FCU_HDG_DEC; you can probably remove those...

[A320.hvar file (request)]

John,

Any chance we can get the following hvars added to the A320.hvar file in the FUSIPC-Lvar-module folder? 

H:A320_Neo_FCU_HDG_INC_TRACK
H:A320_Neo_FCU_HDG_DEC_TRACK
H:A320_Neo_FCU_HDG_INC_HEADING
H:A320_Neo_FCU_HDG_DEC_HEADING

[Added Support for LVars/HVars Access in MSFS via John Dowson's WASM Module.]

Paul,

I hope you're doing well, my friend.  I have a question pertaining to FBWA320 HVARs; specifically, I can manipulate all variable except for two:

H:A320_Neo_FCU_HDG_INC

H:A320_Neo_FCU_HDG_DEC

            FsHVar hvar = this.VS.HVars[H:A320_Neo_FCU_HDG_INC];
            if (hvar != null)
            {
                hvar.Set();
            }

Do you have any thoughts why these won't work?  They're included in the A320.hvar module file.  Any thoughts would be greatly appreciated   

[How to use custom events?]

John,

Sorry to resurrect a 3-month old thread; however, I have a related question.  First, all the HVARs work great with the exception of H:A320_Neo_FCU_HDG_INC and H:A320_Neo_FCU_HDG_DEC.  Do you know if these have been tested?  

[Added Support for LVars/HVars Access in MSFS via John Dowson's WASM Module.]

29 minutes ago, Paul Henty said:

Hi,

Yes, another use above has the same issue with a CRJ aircraft. I assume it's Aerosoft.

I think it's something to do with the high number of variable this aircraft has. It was too many for the limits baked into WASM module.

I can see in the GitHub project that John has expanded the capacity in version 0.5.3. I'm hoping that will fix the issue.

The fsuipc.com page still has 0.5.2 so we'll need to wait until John releases the new version to try it.

Paul

 

That's exactly what I was thinking too, Paul.  Thanks,buddy! 

[Added Support for LVars/HVars Access in MSFS via John Dowson's WASM Module.]

Hey Paul!  The updated dll seems to work great, with one exception; specifically, I continue to get crashes (faulty FSUIPC_WAPID.dll  module).  Interesting enough, the crash only occurs when using the Aerosoft CRJ; plus, the crash happens without initiated an FSUIPC connection; it happens seconds after vs.Start() is called. 

[Added Support for LVars/HVars Access in MSFS via John Dowson's WASM Module.]

That was the first thing I checked, my friend 

 

[Added Support for LVars/HVars Access in MSFS via John Dowson's WASM Module.]

On 7/6/2021 at 2:01 AM, Paul Henty said:

Hi,

If it's intermittent then it's going to be difficult to track down.

Are you using the latest versions of all the components?

My DLL: 3.2.7

WAPIID.dll: 0.5.0

Latest FSUIPC7 (for the latest wasm module)

Paul

Yes sir I am.  It's persistent now; I believe it's an access error but I can't nail it down.  

[Faulting module name: FSUIPC_WAPID.dll]

Good day, Mr Dowson. 

When trying to access the WAPID.dll via C# application, the appliction crashes with the error below.  I believe this is an access error; howerver, I'd be grateful for your opinion

 

        private void Dashboard_Load(object sender, EventArgs e)
        {
            try
            {
                vs.OnVariablesReadyChanged += VS_OnVariablesReadyChanged;
                vs.Init(this.Handle);
                vs.LVARUpdateFrequency = 10; // Get new lvar values 10 times per second (Hz)
                vs.Start();
            }
            catch (Exception) { }
        }
        private void VS_OnVariablesReadyChanged(object sender, EventArgs e)
        {
            try
            {
                if (vs.VariablesReady)
                {
                    Forms.Main.AppendMsgCtrText(Environment.NewLine + "WASM Module Started", Color.PaleGreen, true);
                }
                else
                {
                    Forms.Main.AppendMsgCtrText(Environment.NewLine + "WASM Module Stopped", Color.Orange, true);
                }
            }
            catch (Exception) { }

        }

Error

Faulting module name: FSUIPC_WAPID.dll, version: 0.0.0.0, time stamp: 0x60e59e60
Exception code: 0xc0000005
Fault offset: 0x000000000000722c
Faulting process id: 0x40d4
Faulting application start time: 0x01d77c0232fdc7ce

[Added Support for LVars/HVars Access in MSFS via John Dowson's WASM Module.]

Afternoon, Paul

I get a random error trying to access FSUIPC_WAPID.dll; it happens on occasions when I call VS.Start.  Any suggestions?

Faulting module name: FSUIPC_WAPID.dll, version: 0.0.0.0, time stamp: 0x60be530f
Exception code: 0xc0000005

[FBW A320]

Hey Mr. Dowson!

I can get all the LVARs and HVAR to work except for the XMLVAR_Momentary* variables.  They appear to write only for a second before being written over.   Any ideas?

 

Concerning your question, I downloaded the SPAD profile from here:

https://github.com/flybywiresim/a32nx/tree/master/docs#mapping-of-events-to-control-autopilot--autothrust

Is the user using the development version of the FBW?  Wasn't support added for those variables during a recent update?

[FBW A320]

I asked this question for the Asobo A320; so, I apologize for asking again for a different aircraft.  In regards to the FBW A320, I can bind almost every control with the exception of the batteries.  Has anyone found a LVAR, HVAR, Control or Offset that will toggle both batteries to the ON position.  As the documentation states, it's possible to toggle off via TOGGLE_MASTER_BATTERY control; however, it does not work in reverse.  ANY help would be greatly appreciated as this is the last hurdle to building a solid cockpit for MSFS.   

[A320 Battery]

Has anyone found an offset or control to manipulate the MSFS A320s batteries?  Offsets 3102 and 281C have no effect; interesting enough, control 66241 (TOGGLE_MASTER_BATTERY) can toggle batteries off, but not on.  I've tried all the other controls in the Controls List for MSFS Build 999.txt file too. I've event tried to set the LVAR "A320_Neo_BAT_State" to 2.0000; again no effect.  Hoping someone was able to find something that worked... 

[WASM module not installing]

Worked perfectly; thank you and I apologize for the duplicate post

[LVAR access with FSUIPC 7.1.0]

Evening Paul!

With John's latest release, is it now possible read LVARs via old method (e.g. FSUIPCConnection.ReadLvar(".....")?  

[WASM module not installing]

Afternoon, John

 

I just installed the latest FSUIPC7; however, even though I have selected WASM module for installation, it does not install.  It appears FSUIPC cannot find the community folder; however, it's in its default location.  Here's the  applicable exert from the log:

Installing FSUIPC7 WASM module in .
Create folder: \fsuipc-lvar-module
Output folder: \fsuipc-lvar-module
Skipped: layout.json
Skipped: manifest.json
Skipped: FSUIPC_WASM.ini
Create folder: \fsuipc-lvar-module\modules
Output folder: \fsuipc-lvar-module\modules
Skipped: FSUIPC7_WASM.wasm
Skipped: A320.hvar
Skipped: TBM.hvar
Skipped: DA40-NG.hvar
FSUIPC7 WASM module installation completed.

 

[WASMClient not collecting LVARs]

Hey Sir!

Is there a link to installing WASM?  I just run the exe and it connects.  Is there something more?

[WASMClient not collecting LVARs]

Hey John! I tried running your WASMClient.exe; the WASM Client connects perfectly, but does not collect any LVARS.  Here's the log entry:

 

Sun May 09 2021 17:17:35.385    [INFO]: Connected to MSFS
Sun May 09 2021 17:25:24.355    [INFO]: SimConnect_Close done

 

Can you offer suggestions on why that might be the case? 

[Added Support for LVars/HVars Access in MSFS via John Dowson's WASM Module.]

3 hours ago, jaxx said:

Have you tried not using LogLVars and instead simply accessing the LVars directly? Very simple WindowsForms example:

MSFSVariableServices VS;
private void Form1_Load(object sender, EventArgs e)
{
	VS = new MSFSVariableServices();
	VS.OnLogEntryReceived += VS_OnLogEntryReceived;
	VS.Init(this.Handle);
	VS.Start();
}

private void Button1_Click(object sender, EventArgs e)
{
	VS.RefreshData();
	string text = VS.LVars.Count + " LVARS\r\n";
	foreach (FsLVar lvar in VS.LVars)
	{
		text += lvar.Name + " = " + lvar.Value + "\r\n";
	}
	MessageBox.Show(text);
}

private void VS_OnLogEntryReceived(object sender, LogEventArgs e)
{}

 

Hey Jaxx!

It appears WASMClient isn't collect any LVARs.  Any thoughts, my friend? 

[Added Support for LVars/HVars Access in MSFS via John Dowson's WASM Module.]

4 hours ago, Paul Henty said:

Your code looks okay now.

Can you please try running John's WASMClient.exe program to check if that is returning any LVars. You can find it in the FSUIPC-WASMv0.4.10.Zip file.

Paul

Hey Paul! I tried running WASMClient.exe; the WASM Client connected, but does not collect any LVARS, which appears to be my culprit.  Here's the log entried:

 

Sun May 09 2021 17:17:35.385    [INFO]: Connected to MSFS
Sun May 09 2021 17:25:24.355    [INFO]: SimConnect_Close done