John Dowson

The FSUIPC WASM module is automatically started by MSFS on start-up, You cannot manually start this. if it is correctly installed in your MSFS2024 Community folder. Is it installed? If so, why do you think it is not started? Why would you think this would do anything, using an unknown/not revognised parameter? FSUIPC7 and the FSUIPC7 are two distinct applications - starting one will not start the other - and you cannot manually start the WASM. As I said, this is started by MSFS. Can you please clarify what your issue is. If the WASM isn't started, it isn't installed - show me / attach your InstallFSUIPC7.log file so that I can verify it is installed correctly. John

You should really raise this as a separate issue as this is not related to the trial license. You can't type into that field until you have pressed the button to assign and that is registered, and then have selected for the control type (e.g. 'Select for FS control' for lua scripts). It should be in the menu - just click on the menu, wait for it to load and then type 'l' (for 'lua') - the menu should position at the first entry with an l/L. Then scroll down to find 'Lua <yourLuaFilename>' and select that. Any further questions/issues, please raise a separate thread/topic. This topic is only for trial license requests, not issues. John

Also, when clicking to release the parking brake, I hear a clunck sound but the parking brake doesn't seem to be released....and the default key assignment ctrl +num decimal doesn't seem to work. Any ideas?

I have assigned now to get the throttles moving, but I don't think they are actually working, i.e. no sound and no movement in the aircraft. If you could let me know how to actually use the throttles with the mouse (so I can get the aircraft moving), this may help me... To move the throttles, I assign your axis using 'Send to FSUIPC Offset', select Offset Dword Set and give an offset - I am using xA030, xA034 and xA038. If you use other offsets, you will need to update the lua script. Then save the attached lua script to your FSUIPC7 installation folder (or Lua script folder if you have this set differently). You then need to start the lua - best to have it auto-started by adding this to your ini: The script uses the input events to move the throttle lever. I have also tried adding the sending of the Throttle1/2/3_Set control to see if this is also needed (both as a standard control and via calculator code), but I still don't seem to get any thrust. I will look into this on Friday, and after I have been able to update. If you can provide me the info on how to use the throttles in the VC, that would be helpful. I really don't want to have to go through the documentation to learn how to move this.....! John FSS-727Throttle.lua

Just took a quick look - I have quite an old version of this aircraft (1.0.7 - latest is 1.1.3) and can't seem to update. I will try and update to the latest version - I have raised a support ticket for this an am awaiting a response. In the meantime, I am not familiar with this aircraft. If I advance the throttles in the UI, using the mouse, they jump back to idle. Do you know why this is? Is there some sort of throttle lock that I have to disengage first?

Please attach files only, not screenshors (unless specifically requested). The lvars are not listed in the log you provided. Please show me a log file that lists the lvars. However, your log does show some input events that may be of interest: Not sure there is no ENGINE_Throttle_Reverser_2 though.... Looking at the log of the ENGINE_Throttle_1/2/3 input events, it seems that these take a value between 0 (for idle) and 100 (for full thrust). You could try using these for your assignments. To do this, you need to assign your throttle to update an FSUIPC offset, then have a lua script that monitors this offset, calibrates the axis value to the 0-100 range, and then send this value using the appropriate Input Event. I have just realised that I actually have the FSS 727, so I will look into this (and the lvars) and get back to you - but it may take a day or two as I am busy until Friday. John

Which FS and version of FSUIPC are you using? Try setting logging for Events (non-axis controls), open the logging console and activate the switches in the virtual cockpit - what do you see logged? Try assigning to the control (and parameter) that is logged. You will probably see custom controls logged. These are maybe the custom controls needed: To use those (for a toggle control), you would assign to the Rotor Brake control, with a parameter of 52001 (for engine 1) and 52101 (for engine 2). See the following FAQ entry on how to use custom controls when using mouse operations: If you want separate events for cut-off / idle, better to use the custom controls directly (i.e. with a parameter indicating the state, not the mouse operation) - this post shows how to do this: John N.B. If using MSFS2020/2024, then you can also use the available (MobiFlight) presets - and you have posted in the wrong forum!

Your log shows many Throttle 1/2/3 Set controls logged, but for some reason this is using 2 parameters and both are 0. Very strange as these controls only take one parameter... Can you please re-read my earlier posts carefully and look into what I have advised. Namely: - check the EFB throttle configuration - log Input Events (also list them) and see if any are applicable - list the lvars to see if any of them look applicable The log file you attached shows no lvars or input events. Also, please remove any throttle assignments (and calibration) you currently have and just move the throttle in the VC (i.e. using the mouse) for the time being. John

Yes - the trial license is exactly the same as a purchased/full license except that it is time-limited. John

Also, check the EFB to see if there is a throttle calibration page - you may need to configure there first...

How have you assigned the throttle axis? Which controls have you tried? e.g. have you tried the *_EX1 throttle controls? If assigning using 'Send direct to FSUIPC calibration' doesn't work, switch to using 'Send to FS as normal axis' and try the various throttle controls there. Best to remove any calibration when trying this, at least until you find an axes control that works. If you find one that works, you can then try to see if this can be calibrated. You can also try logging Axes Controls, move the throttle in the VC, and see what control is logged. You can then try that assignment, but there is still no guarantee that this will work. You can also try setting logging for Input Events and move the throttle, to see if any Input Events are logged. If so, I can how you how to assign an axis to control an Input Event. Also list the available lvars - do any of them look like they control the throttle? If so, there are various methods that you can use to assign an axis to control an lvar. Finally, if the standard controls don't work when assigned outside of MSFS, it may be possible to define a preset to control the throttle. I can also help with this, but I need to know what control is logged when you move the throttle in the VC (with logging for Axes Controls set in FSUIPC). I don't have any FSS aircraft, so cannot look into this here. Try the above and report back what you find (attaching any relevant log files) and I can possibly help further. John

To add lvars to offsets, see the Advanced User guide, page 47. The Python wrapper around the FSUIPC was provided as a user contribution, and as such comes as-is and I cannot support this. In fact, it is quite old now and may need updating to be compatible with MSFS2020/MSFS2024, as otherwise it may not recognise the FS version. It may work as-is - I just don't know as I have not used this wrapper. I have attached the README.txt. John README.txt

No, I do nut use or support MobiFlight. If you are using MobiFlight, try MobiFlight support (via their discord server). If they are standard lvars, you can also use FSUIPC to read/write these, and use the python wrapper of the FSUIPC SDK. However, the python wrapper is quite old and will not use the WAPI/WASM, which is the API that I provide to access lvars. You will therefore only be able to access lvars via FSUIPC offsets, which means that you would need to add the lvars you want to use to spare/free FSUIPC offsets before they can be read/updated. John

I don't understand how this can be unless you are changing the either the Platform toolset (which is VS 2022 v143) or the Windows SDK Version (which is 10.0). It is a complete VS project and should compile as-is if you have the correct toolset installed. That message would seem to indicate that you are changing the toolset for the project, when compiling the UIPCHeelo.c file, which then makes it different than the one used to compile the lib, which is VS 2022 v143. No. I mean that you should try to see if the lua com libary recognises your device. From my very first comment in this topic: FSUIPC will only recognise HID joystick type devices. If it is a HID device but not a joystick, you should be able to access via the lua com library. The HidDemo.lua script is an example of how to do this. John

Yes. You need to copy the GUIDs from the newly assigned letter entries (as well as the names, but only if they have changed) to the old letter entries, and delete then delete the new entries. If you have any issues or difficulties, show me / attach your FSUIPC7.ini and an FSUIPC7.log file and I can help. John.

For COM frequencies, you can use FenixQuartz (https://github.com/Fragtality/FenixQuartz) which provides the lvars "FNX2PLD_com1Active", "FNX2PLD_com1Standby", "FNX2PLD_com2Active" and "FNX2PLD_com2Standby" - although these may be read-only. This post indicates that these hold the correct values in MSFS2020, but not in MSFS2024: The OP of that topic also indicated that he has found a way without using FenixQuartz - I have asked if he can provide any further information on this. John

@Mark van Wissen How do you read the COM/NAV frequencies without using FenixQuartz? What do you use to set/change these, in MSFS2020 and/or MSFS2024? I am asking as another Fenix user is having difficulties with this - see

Then we need to determine why - it should run ok. Are you running P3D as admin? If so, you would need to run any connecting problem as admin. Here is a VS project for the UIPCHello - try building and running from this: https://fsuipc.com/download/UIPCHello.zip I am asking if you have tried the lua com library (the HidDemo.lua program) to see if that can recognise your buttons/switches/axes. If it can, then you can use that to assign directly in FSUIPC - no need to write your own program to interface to the hardware, John

Please read the Installation and Registration guide, section Invalid Key Problems. All reports on this issue are due to one of three things: - not entering your key details correctly. All 3 parts must match (Name, Address/email & /key). It is recommended to copy and paste these from your purchase email or from your key details in your SimMarket account. - not having the correct VC++ redistributables installed. Download and install the latest combined VC++ redistributable package for both x64 and x86. - anti-virus software blocking the registration check. check your ant-virus software for details. John

👍😎

What is FSUIPCuser64.h and why are you including this? As I keep saying, first get the sample program compiled and working. Once you have that working, then adapt that to your needs. John

This is not correct - it is working correctly. The issue is that you do not have a license to use WideFS: You need to purchase and/or register your WideFS license. If you do not have one, you can try the trial license. John

It looks like WideServer is not being enabled in unlicensed versions of FSUIPC7. I will look into this. For now, can you download the trial license (available in the first post in this sub-forum) and use a licensed version of FSUIPC. I will look into why WideServer isn't being started with an unlicensed version and get back to you. You shouldn't need an FSUIPC7 license to use WideServer. John

Then WideServer isn't running. Please attach a full FSUIPC7.log file.

Can you please exit FSUIPC7 / WideClient before attaching log files. Your FSUIPC7.log file ends after 5 seconds and shows that WideServer was not even yet started. Also, please attach your WideServer.log file. Also try with ServerName instead of ServerIPAddr, and also set Protocol=TCP. Do you see the WideFS menu in FSUIPC7?