Jump to content
The simFlight Network Forums

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


Recommended Posts

Posted

Good evening,
I am currently building a buttons box for MSFS2020, using your licensed FSUIPC 7 software, 2 BBI-64 boards from Leo Bodnar and have a question.
I think it is possible to assign to a rotary encoder actions such as the zoom of the map on the Garmin G1000 (RANGE button) or the brightness of the dashboard for example.
I did not find the events that correspond to these types of functions, can you help me please.
Sorry for my rough English, I use google trad 😉
Thanks
Cordially.
Lawrence

Posted

John,
I see the two AS1000 presets that are suitable for the events in question but none of the presets are taken into account, I don't know why.
do i have to install the wasm client?
Cordially

Posted

John,
I don't understand where my mistake is and to allow you to remove some doubts I allow myself to attach a screenshot.
I note that the presets for switch or rotary encoder are not interpreted by FS2020.
Switch 0 = NOK
Rotary 132 = NOK
Rotary 133 = NOK

All other events are operational:
FLAPS_INCR / FLAPS_DECR on switches 26/27.
The HEADING_BUG_INC / HEADING_BUG_DEC on the rotary encoder 146/147.

Preset: https://zupimages.net/viewer.php?id=22/32/b01z.jpg

WASM Enabled : https://zupimages.net/viewer.php?id=22/32/gszw.jpg

File.ini https://zupimages.net/viewer.php?id=22/32/jbn4.jpg

Thanks for your help

Posted (edited)
On 8/13/2022 at 6:53 PM, ZOUZAC-L said:

do i have to install the wasm client?

Yes, you have to install and enable the WASM module - which you seem to have done.

Are you using the default G1000 or the one from Working Title?
Your assignments look ok, so I am not sure why it isn't working. I will take a look and get back to you, but as the range presets just activate a hvar,  could you try setting these manually to see if that works. Use the menu option Add-ons->WASM->Execute Calculator Code... and enter 
    (>H:AS1000_MFD_RANGE_INC)
to increase the range and
    (>H:AS1000_MFD_RANGE_DEC)
to decrease the range, and let me know if those have any affect.

John

Edited by John Dowson
Activate Hvar changed to Execute Calculator Code
Posted
1 hour ago, ZOUZAC-L said:

Unfortunately the method indicated does not change anything.
1/ I enter H:AS1000_MFD_RANGE_INC
2/ I click on Activate
3/ I enter HH:AS1000_MFD_RANGE_DEC
4/ I click on Activate

5/ I click on Done
Is this the correct method?

No! Sorry, you need to use the Add-ons->WASM->Execute Calculator Code.. option, and enter
    (>H:AS1000_MFD_RANGE_INC)
to increase the range and
    (>H:AS1000_MFD_RANGE_DEC)
to decrease the range. The Activate Hvar menu item is for hvars known to FSUIPC only (via *.hvar files). Sorry about that - I will correct my previous post...

55 minutes ago, ZOUZAC-L said:

I downloaded the WASM client v0.4.8
Launched and connected but no improvement.

You don't need that - that is  just a test client and everything that does you can do from the Add-ons->WASM menu.

As I said, I will take a look, probably tomorrow...

John

Posted

Ok John,

I will take the test tonight and let you know the result.

Thank you for the time you spend to solve our user problems and especially for the development of this great tool.

There is no rush and I am naturally patient, no problem.

Have a good evening

Thank you.

Lawrence.

Posted

John,

I confirm that for me it does not work at all.
To make it easier the video below shows the action.
I wanted to know one thing,
does the code calculator execute the command exactly like a button?
to do a test I entered the code that activates the pitot and it does not work either.
does the computer execute only the presets or absolutely all the codes?

 

 

Maybe I did not understand the role of the code calculator!

 

Posted
16 minutes ago, ZOUZAC-L said:

does the code calculator execute the command exactly like a button?

Executing calculator code does just that - it executes the calculator code you enter. If you assign a button to a preset, then pressing that button would execute the calculator code of that preset exactly the same as done using the Execute Calculator Code window.

15 hours ago, ZOUZAC-L said:

To make it easier the video below shows the action.

This doesn't make it easier, just confirms that it isn't working for you, as you said. I do believe you! But it is working, and we need to determine why it isn't for you.
I need to see your log files, with appropriate logging activated. Can you therefore please activate Debug level logging for the WAPI, by adding the following line to your FSUIPC7.ini file under the [WAPI] section (when FSUIPC7 is not running)):
     LogLevel=Debug
Also activate Debug level logging in the WASM by adding/changing the following line in your FSUIPC_WASM.ini file (see the Advanced User guide for the locations/details)):
    LogLevel=Debug
Then run MSFS/FSUIPC7 and try executing that calculator code again. Then exit and show me your FSUIPC7.log and FSUIPC_WASM.log files - attach the complete files please. If the calculator code is being sent correctly, then you should see the following logged in the WASM:

Quote

...
Wed Aug 17 09:20:19 2022    [INFO]: 1760 lvars loaded for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data config area set with 17 CDAs (1 hvar, 13 lvar, 3 lvar values) [requestID=87]
Wed Aug 17 09:20:19 2022   [DEBUG]:    HVAR CDA 'FSUIPC_HSkyhawk0' with size=2632
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME8' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME9' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME10' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME11' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME12' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME13' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME14' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME15' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME16' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME17' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME18' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME19' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME20' with size=448
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR Values CDA 'FSUIPC_lvalues0' with size=8192
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR Values CDA 'FSUIPC_lvalues1' with size=8192
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR Values CDA 'FSUIPC_lvalues2' with size=8192
Wed Aug 17 09:21:23 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_INC)'
Wed Aug 17 09:22:04 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_INC)'
Wed Aug 17 09:23:14 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_INC)'
Wed Aug 17 09:23:16 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_DEC)'
Wed Aug 17 09:23:26 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_DEC)'
Wed Aug 17 09:23:33 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_DEC)'
Wed Aug 17 09:23:45 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_INC)'
Wed Aug 17 09:23:56 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_DEC)'
Wed Aug 17 09:23:57 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_INC)'
Wed Aug 17 09:26:31 2022   [DEBUG]: Calculator code executed: '(>H:AS1000_MFD_RANGE_INC)'
Wed Aug 17 09:29:36 2022   [DEBUG]: Calculator code executed: '(>K:PITOT_HEAT_TOGGLE)'
...

 

John

Posted

Did you try executing any calculator code when producing those logs? If so, nothing was received by the WASM.
I don't know what can be preventing this, but your FSUIPC7.log shows that you are using LINDA. This could be interfering - can you disable LINDA for the time being and re-test (e.g. just temporarily rename your ipcReady.lua file to ipcReady.lua.unused). You can also assign a button or key to the AS1000 MFD range inc/dec presets and try them, with logging for Buttons & Keys as well as Events activated. Do this and show me those files again, as well as your FSUIPC7.ini file.

John

Posted
1 hour ago, ZOUZAC-L said:

I have the impression that the simulator does not interpret any code from the code calculator!

Yes, the WASM is not picking up the calculator code from the CDA, although the FSUIPC7.log shows the WAPI is connected, and the lvar/hvar data has been received.
Do you know if you are running any other WAPI clients? What else do you have installed in your MSFS' Community folder?

There are a few other things to try...

1. Try setting an lvar value using the Add-ons->WASM->Set Lvar... menu item. Doesn't really matter which one, but maybe try with L:XMLVAR_YokeHidden1 or L:XMLVAR_YokeHidden2 ones, as changing these from 1->0 and 0->1 should show/hide the yokes, so you can see the affect without having to check the logs. Perform a Add-ons->WASM->List Lvars first, as this will also rescan for lvars (as your LvarScanDelay parameter is probably set to the default of 5 seconds).

2. Try the Add-ons->WASM->Execute Calculator Code function again (or buttons assigned to presets), but using the latest FSUIPC7 beta. There is a fix in this version that can prevent issues when using multiple WASM clients. This beta is available here: 

 

John

Posted

John,

my community folder contains a lot of stuff (attachment).
I don't know which addon could disturb FSUIPC!

Maybe FlyByWire, Airbus H145, Seafront, ambitiouspilots-toolbar-pushback could interfere with the proper functioning?

Community: https://zupimages.net/viewer.php?id=22/33/qzuk.jpg

When I use Add-ons->WASM->Set Lvar + L:XMLVAR_YokeHidden1 + value 1 or 0 the simulator simply closes.
same result with Beta 7.3.8b version of FSUIPC

Lawrence.

Posted
17 hours ago, ZOUZAC-L said:

my community folder contains a lot of stuff (attachment).
I don't know which addon could disturb FSUIPC!

Yes, lots of stuff...
As a test, just to see if this issue is being caused by an add-on, could you temporarily remove (e.g. move up one folder) everything from your Community folder except for the fsuipc-lvar-module and see if that works and we can go from there....

John

Posted

Good morning, John
I emptied the community folder and left only the fsuipc-lvar-module subfolder but still the same result.
I limit the tests to the code calculator with these actions:
(>H:AS1000_MFD_RANGE_INC)
(>H:AS1000_MFD_RANGE_DEC)
(>K:PITOT_HEAT_TOGGLE)
(still with beta version 7.3.8b)
using Add-ons->WASM->Set Lvar + L:XMLVAR_YokeHidden1 + value 1 or 0 crashes the simulator even with this minimum community folder.
I really don't understand where the problem is.

Posted

Me neither, it is very strange...
Could you try re-installing FSUIPC7 in a different location. Create an FSUIPC7 folder on your Desktop, and then re-run the FSUIPC7 installer and change the installation location to the Desktop folder. You can skip registration and copy your FSUIPC7.key file from the old location to the new location.
Also, if running any antivirus/malware software (other than Windows Defender) then try temporarily disabling that to see if that is interfering somehow.

Posted

John,

(I'm using windows 11 antivirus and nothing else).
I did all these actions in this order:
- FSUIPC uninstall.
- Installing FSUIPC7 on my desktop.
- Launch MSFS2020.
- I assigned 3 or 4 buttons and rotary encoders.
- With the code calculator I ran the codes
         (>H:AS1000_MFD_RANGE_INC)
         (>H:AS1000_MFD_RANGE_DEC)
         (>K:PITOT_HEAT_TOGGLE)

still no improvement the simulator behaves the same way.
Add-ons->WASM->Set Lvar with L:XMLVAR_YokeHidden1 as changing these from 1->0 and 0->1  ==> crash simulator
I'm really sorry for taking your time with my very particular problem.😒
my .log and .ini files as attachments

Lawrence

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

Posted

Where is that FSUIPC_WASM.ini file located? It should be in the same folder as the FSUIPC_WASM.log file, but that log file has this:

Quote

Thu Aug 18 11:44:07 2022    [INFO]: Ini file loaded from add-on package
Thu Aug 18 11:44:07 2022    [INFO]: No ini file found in persistant storage at '\work\FSUIPC_WASM.ini'

So only the ini file from Community\fsuipc-lvar-module was loaded. The ini you attached has
    LogLevel=Debug
but there are no Debug level logging statements in your FSUIPC_WASM.log file. So something is certainly wrong somewhere. Note that your previous WASM log files did have Debug level logging enabled, so something must have changed.
Can you please make sure that there is an FSUIPC_WASM.ini file in your WASM persistent storage area - check the Advanced User manual (WASM section) to determine where this is (it depends on your install type, Steam or MS Store). Can you also show me your InstallFSUIPC7.log file.
Also, once you have debug level logging in the WASM properly activated, add the following line to your FSUIPC_WASM.ini:
    LvarScanDelay=45
Then try again and resend me the same files.
I find it hard to believe that only 126 lvars were found for the C172 - when I load this aircraft (with the G1000) I get 1779 lvars...

Also, please confirm that you are not using the latest MSFS beta...this is not supported....

John

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.