MSFS2020 and FSUIPC 7 - Event on Garmin G1000 / rotary encoder

[ZOUZAC-L]

John,

Yes it's strange, moreover the WASM menu is grayed out and that's certainly why the FSUIPC_WASM.ini file does not exist in the FSUIPC7 folder.
How do I regain access to this menu?
Question:
Should the two subfolders [include] and [lib] of the FSUIPC_WAPI folder be in a particular folder?
if yes which ?

I am using MSFS version 1.26.5.0

EDIT
I closed then relaunched FSUIPC and the WSAM menu is OK...

InstallFSUIPC7.log

[John Dowson]

9 minutes ago, ZOUZAC-L said:

Should the two subfolders [include] and [lib] of the FSUIPC_WAPI folder be in a particular folder?
if yes which ?

Sorry, I don't understand this question...what is the FSUIPC_WAPI folder (and where is this located)? That isn't part of FSUIPC - the WAPI is an API that FSUIPC uses (as well as maybe other 3rd party clients).

9 minutes ago, ZOUZAC-L said:

I closed then relaunched FSUIPC and the WSAM menu is OK...

But I thought that was always ok (i.e. options available) - you were using that to execute calculator code (which wasn't working)...I'm confused even more now...

John

[ZOUZAC-L]

John,
You found,
now the rotary assigned to the range map of the MDF is operational
I continue to experiment with other functions....
THANK YOU VERY MUCH.

FSUIPC_WASM.ini

[ZOUZAC-L]

John,
Ok that was short lived
after running List Lvars and List Hvars
it doesn't work anymore!

Lawrence.🤔

[ZOUZAC-L]

John,
Here are the files after this very short success 🙂

John,
Here are the files after this very short success 🙂

these 3 commands worked 1 time
12=PD,132,CPAS1000_MFD_RANGE_INC,0      -{Preset Control}-
13=PD,133,CPAS1000_MFD_RANGE_DEC,0     -{Preset Control}-
14=PD,0,CPAS1000_MFD_MENU_Push,0         -{Preset Control}-

Lawrence

FSUIPC_WASM.log FSUIPC_WASM.ini FSUIPC7.log FSUIPC7.ini

[ZOUZAC-L]

John,
We are progressing and we are progressing well....
I restarted MSFS and FSUIPC and it works fine again.
on the other hand if I execute the code calculator it has no effect
and in addition it stops the proper functioning of the 3 actions
For it to work again, you have to restart MSFS and FSUIPC.
now I know what to do and I also know what he was not doing.

Lawrence

[ZOUZAC-L]

John,

I found that everything works fine for a few seconds.
I assumed that the number 45 of the line LvarScanDelay=45 is related to this observation.
I modified the line to LvarScanDelay=120 and of course it works for two minutes.
I tried with LvarScanDelay=999999 and it worked for a few minutes but didn't time out.
If I remove the line LvarScanDelay=......... it doesn't work anymore.
I imagine that there is a parameter so that the delay is infinite?

Lawrence

[John Dowson]

10 hours ago, ZOUZAC-L said:

I imagine that there is a parameter so that the delay is infinite?

No - the default (without the parameter specified) is 5 seconds. This is the number of seconds the WASM waits after the aircraft is loaded and ready-to-fly before it scans for lvars. Once this lvar scan is complete, config data containing the lvar/hvar names is passed to FSUIPC7, and the WAPI is then useable (and the WASM menu items are enabled for use).

10 hours ago, ZOUZAC-L said:

I modified the line to LvarScanDelay=120 and of course it works for two minutes.

I don't understand this - setting to 120 means that the lvars/havrs aren't available until after two minutes after the aircraft is ready. So, what do you mean by work in this context?

I will take a look at the log files a bit later to see if I can see anything... 

John

[John Dowson]

12 hours ago, ZOUZAC-L said:

Here are the files after this very short success 🙂

these 3 commands worked 1 time
12=PD,132,CPAS1000_MFD_RANGE_INC,0      -{Preset Control}-
13=PD,133,CPAS1000_MFD_RANGE_DEC,0     -{Preset Control}-
14=PD,0,CPAS1000_MFD_MENU_Push,0         -{Preset Control}-

The logs you posted are very strange and don't seem to match...the WASM log file shows the following calculator code was received and executed but before lvar scan took place:

Quote

Thu Aug 18 18:48:21 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_INC)'
Thu Aug 18 18:48:21 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_INC)'
Thu Aug 18 18:48:21 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_INC)'
Thu Aug 18 18:48:22 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_DEC)'
Thu Aug 18 18:48:22 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_DEC)'
Thu Aug 18 18:48:22 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_DEC)'
Thu Aug 18 18:48:23 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_DEC)'
Thu Aug 18 18:48:23 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_DEC)'
Thu Aug 18 18:48:24 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_MENU_Push)'

There are no presets/calculator code requests seen by the WASM after the lvarscandelay was passed and the config data set.
Your FSUIPC7.log file doesn't show that calculator code being sent in that order. In fact, the log file doesn't start until 10minutes AFTER those log entries:

Quote

       62 System time = 18/08/2022 20:58:44

(assuming the two hours difference is due to one log using local time and the other GMT/Zulu time).
So it looks to me that these log files were not generated at the same time....could that be? Either way, I remain confused with this...

I also seems that you had this working at one point for a short period but then stopped:

13 hours ago, ZOUZAC-L said:

now the rotary assigned to the range map of the MDF is operational
I continue to experiment with other functions....

...

Ok that was short lived
after running List Lvars and List Hvars
it doesn't work anymore!

I really don't understand this at all....

I have also asked some questions that you have not answered - can you please respond to all my questions so that we can get to the bottom of this:

Are you, by any chance,  using the latest MSFS beta?
 

13 hours ago, ZOUZAC-L said:

Should the two subfolders [include] and [lib] of the FSUIPC_WAPI folder be in a particular folder?
if yes which ?

Could you explain this? There is no FSUIPC_WAPI folder...

Are you using any other software other than MSFS and FSUIPC7? If so, what? Maybe try without that...
What do you have in your MSFS Community folder (apart from the FSUIPC WASM folder fsuipc-lvar-module)?

Can you also check your Windows Event log (using Event Viewer) to see if any events for MSFS or FSUIPC are reported.

Thanks,

John

[ZOUZAC-L]

Hi John

If I answered your question about MSFS version
I am using MSFS version 1.26.5.0 and nothing else.
My Community folder contains ONLY the [fsuipc-lvar-module] folder and nothing else.
About the FSUIPC_WAPI file.
it was uploaded with the SFUIPC-WASMv0.4.8

In the [include] subfolder there are 4 files:
CDAIdBank.h
ClientDataArea.h
WASM.h
WASMIF.h

In the [lib] subfolder there are 2 files:
FSUIPC_WAPI.lib
FSUIPC_WAPI_debug.lib

I don't know if they have any importance it was a simple question.

my MSFS 2020 simulator is steam edition.
my FSUICP version is 7.3.7
I added the lines LogLevel=Debug where you asked me to.
I checked the logs of buttons & keys and events in the FSUIPC interface.

After reading in the windows 11 event viewer I note this at 08/17/2022 at 16:57:34:
-------------------------------------------------- -----------------------------
Faulting application name FlightSimulator.exe, version: 1.26.5.0, timestamp: 0x00000000
Faulting module name: me42ea365ec3d2163_0.dll, version: 0.0.0.0, timestamp: 0x62d01915
Exception code: 0xc000001d
Error offset: 0x00000000000099bb
Faulting Process ID: 0x307c
Faulting application start time: 0x01d8b24cc0965549
Faulting Application Path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Users\lzouz\AppData\Roaming\Microsoft Flight Simulator\packages\fsuipc-lvar-module\me42ea365ec3d2163_0.dll
Report ID: 7c56fa4e-8cc3-4a1f-a942-29c66c409a12
Faulting package full name:
Application ID relative to the failing package:
-------------------------------------------------- ---------------------------------
This error returns at 17:04:49 and then at 17:10:25

Lawrence

[John Dowson]

21 minutes ago, ZOUZAC-L said:

In the [include] subfolder there are 4 files:
CDAIdBank.h
ClientDataArea.h
WASM.h
WASMIF.h

In the [lib] subfolder there are 2 files:
FSUIPC_WAPI.lib
FSUIPC_WAPI_debug.lib

This is the WAPI API, used for developing FSUIPC WASM clients in C. You don't need this, unless you are writing your own FSUIPC WASM client...

22 minutes ago, ZOUZAC-L said:

it was uploaded with the SFUIPC-WASMv0.4.8

But why are toy using this? Unless you are a developer, everything you need coms with the DSUIPC7 installer. That package (without the version number in the file name) us also included in the FSUIPC7 SDK folder (called FSUIPC0WASM.zip). Thar separate downloadable  FSUIPC WASM package is intended for developers that don't use FSUIPC7.

26 minutes ago, ZOUZAC-L said:

After reading in the windows 11 event viewer I note this at 08/17/2022 at 16:57:34:
-------------------------------------------------- -----------------------------
Faulting application name FlightSimulator.exe, version: 1.26.5.0, timestamp: 0x00000000
Faulting module name: me42ea365ec3d2163_0.dll, version: 0.0.0.0, timestamp: 0x62d01915
Exception code: 0xc000001d
Error offset: 0x00000000000099bb
Faulting Process ID: 0x307c
Faulting application start time: 0x01d8b24cc0965549
Faulting Application Path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Users\lzouz\AppData\Roaming\Microsoft Flight Simulator\packages\fsuipc-lvar-module\me42ea365ec3d2163_0.dll
Report ID: 7c56fa4e-8cc3-4a1f-a942-29c66c409a12
Faulting package full name:
Application ID relative to the failing package:
-------------------------------------------------- ---------------------------------
This error returns at 17:04:49 and then at 17:10:25

That is a fault in MSFS, which can be causing issues, but I do not know if this is related. Please check the event viewer when MSFS CTDs to see if anything is reported.

I have still no idea what is causing your issue, and I don't understand how it can sometimes work and sometimes not. It may be a problem somewhere in either your MSFS or windows installation (most probably the former). Maybe worth checking the integrity of your MSFS steam installation 9available from the steam app). Be aware though that this can cause a complete re-download of the FS.

John

[ZOUZAC-L]

OK for different development tools
I don't actually need it.
I had downloaded the packages without knowing if it was going to be useful to me.
I am absolutely not an English speaker and the language barrier makes us poor French people do strange things.
I admire your patience.
Yes I know for verifying the integrity of steam files
I have already been a victim of this option in the past and I think I will not have a choice this time again.

Lawrence.

[John Dowson]

No problem. and I understand the language issue. This was just confusing me and wanted to clarify.

Your issue is very strange, and I can't understand why your system can be behaving in this manner, except for an underlying installation issue in MSFS (or maybe windows).
You could also try re-installing the latest VC++ redistributables, as I have seen strange problems sometimes with these not being correct. Uninstall any of the 2015, 2017, 2019 & 2022 VC++ redistributables from the Windows App management panel (any/all that are installed), and then install the latest combined redistributable packages (both the x86 and x64 versions recommended, although FSUIPC7 only requires the x64 version) from here:
       https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist

I am not sure this will help, but worth a try (before verifying integrity!).

John

[ZOUZAC-L]

OK John
I am not surprised between windows and MSFS the quantity of files is hallucinating and some elements can be corrupted.
I'll follow your advice and let you know when it's done.
really, thank you.

Lawrence.

[ZOUZAC-L]

John,

I'm back after a few actions, trials and observations.
I have checked integrity of MSFS 2020 files in STEAM.
I didn't have to re-download the 100GB, that's strange.
just a few updates but nothing major.
I uninstalled FSUIPC completely with deletion of all files then I reinstalled it on (FSUIPC7 v7.3.7)
I added the lines LogLevel=Debug
I restarted FS 2020, assigned some buttons and rotary.
So I have a clean and healthy install of FSUIPC7.
By reading the FSUIPC_WASM.log file located in the folder: C:\Users\lzouz\AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module\work
I see the following error:
Fri Aug 19 18:57:08 2022 [INFO]: No ini file found in persistent storage at '\work\FSUIPC_WASM.ini'
The SFUIPC_WASM.ini file is not in the correct folder but it is here:
C:\Users\lzouz\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\fsuipc-lvar-module
Is this normal?
How can this error be generated by MS FS2020?

How do you interpret this error?

Lawrence.

[John Dowson]

13 hours ago, ZOUZAC-L said:

I see the following error:
Fri Aug 19 18:57:08 2022 [INFO]: No ini file found in persistent storage at '\work\FSUIPC_WASM.ini'

That is not an error - it is an informational message [INFO].

13 hours ago, ZOUZAC-L said:

The SFUIPC_WASM.ini file is not in the correct folder but it is here:
C:\Users\lzouz\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\fsuipc-lvar-module
Is this normal?

Yes, this is normal. The default FSUIPC_WASM.ini is always located under your Community\fsuipc-lvar-module folder. This is the one installed by the FSUIPC7 installer when you install the WASM module. If you change that file, your changes will be overwritten the next time you re-install or update FSUIPC7. To prevent your changes from being lost, the WASM will also read an ini file from  your WASM persistent storage area - this does not exist by default, you need to create (or better, copy) this file yourself. Please see the section WASM module ini file and parameters in the Advanced User guide (page 48).

Can you try with another aircraft, so we can see if this is a general issue if specific to the C172. Maybe also set the logging lever in the WASM (and maybe also the WAPI, later) to Trace and resend the log file. It looks like the FSUIPC WASM module has crashed for some reason (or at least, its not available) as it doesn't seem to respond to any requests.

I am busy this weekend - I will come back to this on Monday.

John

[ZOUZAC-L]

Good morning, John,
Yes, I noticed the notion of info, so it is not very important.
Yesterday evening after writing this last message I added the line ''EnableWAPI=Yes'' to the FSUIPC7.ini and I found that it solved the problem and definitely since at this moment everything works very well exactly as I hoped so.
For me it's Christmas.
I will copy the SFUICP_WASM.ini file anyway to follow your advice.
I have to use it more often on the advanced user documentation.
I have a few more simple questions, I promise.
since last night the assignment of the keyboard code -{Key press: lalt+Enter}-
on a button of the AIrbus TCA Joystick has no reaction, yet until then it did not pose a problem.
It's really unimportant but if you have an idea I'm interested.
And about the Parking Brakes and RECOGNITION Lights commands
are in ''toggle'' mode, do you plan or is it possible to switch them to ON / OFF mode?
Have a nice week end
Regards
Lawrence

[John Dowson]

57 minutes ago, ZOUZAC-L said:

Yesterday evening after writing this last message I added the line ''EnableWAPI=Yes'' to the FSUIPC7.ini and I found that it solved the problem and definitely since at this moment everything works very well exactly as I hoped so.

I am confused now - you did have the WASM enabled! The Add-ons->WASM menu items (such as Execute Calculator Code or Set Lvar) are not available unless the WAPI is enabled.

59 minutes ago, ZOUZAC-L said:

since last night the assignment of the keyboard code -{Key press: lalt+Enter}-
on a button of the AIrbus TCA Joystick has no reaction, yet until then it did not pose a problem.
It's really unimportant but if you have an idea I'm interested.

Not without seeing your files again, with appropriate logging activated. Set FSUIPC7 logging for Buttons & Keys as well as Events, load your aircraft and press the assigned key. Note that the left/tight alt key modifiers are specific - i.e. your assignment is using the left alt key, not the right one.

1 hour ago, ZOUZAC-L said:

And about the Parking Brakes and RECOGNITION Lights commands
are in ''toggle'' mode, do you plan or is it possible to switch them to ON / OFF mode?

What events or presets are you using for this? If there are no specific on/off events (or presets) provided (I am pretty sure there are for Parking Brakes!), you can use the toggle event but with an offset condition in an offset that is holding the current state of the function you are trying to toggle.

I am finishing now for the weekend. Provide more information (and possibly your FSUIPC7.log and .ini files again), and i can look into this further on Monday.

Have a good weekend,

John

[John Dowson]

On 8/20/2022 at 12:41 PM, ZOUZAC-L said:

And about the Parking Brakes and RECOGNITION Lights commands
are in ''toggle'' mode, do you plan or is it possible to switch them to ON / OFF mode?

Have you tried the events/controls Parking Brake Set and Recognition Lights Set, with a parameter of 1 for on an 0 for off?

[ZOUZAC-L]

Good morning, John,

Indeed it is much simpler with this type of event.
Thanks again.
Regards