John Dowson

It seems that the Fuel Selector Set Command works with the following parameters: 0 - turns left and right off 1 - turns left and right on 2 - turns left on, right off 3 - turns right on, left off So, turn one off without changing the state of the other, the command to send would depend on the state of the other. So, if left and right were both on and you wanted to turn left off, use parameter 3, and parameter 2 turn right off. If left was on and right was off, to turn off right you would use parameter 0 (both off). etc So you need to know the actual state and send different controls if you want individual control. I haven't checked any of the many other Fuel Selector controls. Activating logging and flipping the switch in the UI shows the Turbine Ignition Switch Set Ex1 control being triggered, with a parameter of 2 for On and 1 auto Auto. However, sending these controls via SimConnect/FSUIPC doesn't have any effect. I've had a quick look at the available lvars as well and there doesn't seem to be anything there that works either. You could try to see if you can assign for this to a key press (or key press combination) om MSFS itself. If this works, you can then assign your button/switch to the MSFS assigned keypress. Have you tried the Avionics Master 1/2 On/Off/Set controls? Is anything logged when you switch them in MSFS? The general method is the same - see if anything is logged and try them. If they don't work, try the various available controls. If non work, see if they work via MSFS assignments, and if so, assign to a keypress in MSFS and then assign your button to that key press in FSUIPC. Also, check available lvars and try setting those (initially using the Add-ons->WASM->Set Lvar... menu option to see if they work). Note also that many stock MSFS aircraft are missing quite a bit of functionality. There are various mods available for this aircraft (and most others) that improve on the stock functionality. Check for any available mods (SU6 compatible) that may improve on these functions. John

Try activating logging for both events and axes controls and open the console window. This may help show you what is sending the throttle control commands. You can also attach your FSUIPC7.log and FSUIPC7.ini files and I'll take a look to see if I can see anyhing. If assigning in MSFS, it is best to create a new empty profile in MSFS for that controller. John

Ok, thanks: **** FindWindowEx error 1400 (578) **** Error 1400 is 'Invalid window handle', which means it just can find the window with the class name 'AceApp', which is what the MSFS main window class name should be. You can delete/remove that version now and revert to the previous version I posted. I will release that version in a few days. Cheers, John

Ok, that is interesting.... sounds like that thread is somehow preventing the main thread from closing... ...hmm, then maybe not! You could also try renaming that file and uncommenting the ipc.runLua command so that it is re-created, and see if that provokes the crash, or not, as the case may be. Anyway, I will wait for further information. I am not sure if the changes in those above versions will be kept for the next release or not, we'll see how it goes with your tests. John

Yes, it looks like this is no longer working, if it ever was....! The lvar L:XMLVAR_ElecGen doesn't even exist anymore! You can just use the Toggle Alternator1 control to toggle between off an main, and offset 0x3B9C will hold the state, but only main (1) or off (0). It looks like the standby state is currently missing. You should ask about this on the Asobo forums. For the starter, bind to Set Starter1 Held, with a parameter if 1. That is what is monitored when you log the events, and also works if I bind that to a switch/button....later, tried it again and it no longer works...very strange. There are various mods available for the TBM930, which should fix/improve the stock functionality. If I were you, I would look for the latest SU6 approved mod and try with that (e.g. https://flightsim.to/file/8288/tbm930-improvement-mod) to see if that helps. I cannot comment on these products. However, they will rely on the underlying SDK that MSFS provides, so if you cannot do what you want to achieve in FSUIPC, I very much doubt that it can be done with any other products. If you are new to lvars/hvars/calculator code, it may be easier to installer the MobiFlight WASM module (via the MFConnector app) and use the provided event files. However, as the MF presets just execute the calc. code defined for that preset, if the calc code doesn't work, neither will the preset. Sorry I can't be of more help. I'm pretty sure I looked into the TBM930 starter previously, so maybe this got broken in a subsequent update. I'm pretty busy at the moment, but when I get more time I will look into the this in more detail. You can also try looking on the Asobo forums for information on how to control the TBM930, or the MobiFlight discord channel. John

I am sorry but I cannot give you step-by-step instructions. There are plenty of posts on how to use MobiFlight and the FSUIPC7 event files if you want to go down that route. And, as I said, if you want to use that calculator code directly (instead of via a MobiFlight preset), then you have to use in a lua script via the lua ipc.execCalcCode script. You should first test the code to see if it works. You can do this using the Add-ons->WASM->Execute Calculator Code... menu entry. If you want to use lua, see the provided documentation.

Please replace the contents of your EXE.xml file with what I posted earlier. Why have you attached that other file? Have you tried starting FSUIPC7 manually? At least try that to make sure it can run.

@chrisal and @Fordson04: could you both please do me a favor and try the attach version. Please disable the new DisableMSFSMonitor ini parameter first (remove or set to No). This will fail, as before, but should hopefully log a windows error number which may help me track down the issue. You can revert to your current FSUIPC7.exe afterwards and re-enable the ini parameter. Either attach your FSUIPC7.log or just paste the following line: **** FindWindowEx error n (X) **** Thanks, John FSUIPC7.exe

Its calculator code, so can currently only be used via the lua ipc.execCalcCode function. If you are not familiar with lvars, hvars or calculator code, it may be easier to use the MobiFlight presets. To use these, you need to install the MobiFlight WASM module, and make the MobiFlight events/presets known to FSUIPC7 via event files. Many MF event files are included under the EventFiles sub-folder of your FSUIPC7 installation folder. See the Advanced User guide. Under your FSUIPC7 installation folder. If you don't know where that is, use FSUIPC7's File->Open Installation Folder... menu option. John

Sorry, you had already done this! Your EXE.xml is a complete mess. It should look like this: Replace with that and you should be ok. John

And you are using FSUIPC7 v7.2.10. Please download and install the latest version, v7.2.11. When you run the installer, it will first uninstall the current version, and then install the latest version. When you install, can you PLEASE choose an installation location outside of your Documents folder (e.g. C:\FSUIPC7).

If you check your installation log, you will see this: I suspect that your EXE.xml file has been corrupted by another application. Please show me this file: C:\Users\stali\AppData\Roaming\Microsoft Flight Simulator\EXE.xml John

In your FSUIPC7 installation folder. If you do not know where that is, you can use the FSUIPC7 File -> Open Installation folder... menu item. John

What is this supposed to mean? If you want me to help you, please show me your files (FSUIPC7.log, FSUIPC7.ini, InstallFSUIPC7.log. John

Sorry, but I cannot understand what you are trying to say...(google translate?). Gate information is part of the (airport) scenery files. FSUIPC doesn't do anything with these. However, as I said, we provide an additional program called MakeRunwys, which extracts runway (and gate) information and provides text files so that these can be read by other programs. Why don't yo take a look at that. Otherwise, I am really not sure what you are asking. Maybe you could explain by an example? John

Sorry, but I have no idea what 'Flight Multi Panel is, or how connecting a phone to your PC has anything to do with this (my phone always connects to my PC automatically, without issues). If you are having problems with FSUIPC7, just please state what they are. If it is running, I need, as a minimum, to see your FSUIPC7.log file. If it is not running automatically, show me your InstallFSUIPC7.log file, and try to start it manually - it that doesn't work, show me the error (and check the README.txt - maybe you need to reinstall the VC++ redistributables...) John

Ok, thanks for reporting back. I would really like to understand the underlying issue though. I will post on StackOverflow to see if any others are having this issue or know the cause. John

And also maybe try this version, where the lua is killed as soon as the 'Sim stopped' message is received: FSUIPC7.exe

Could you also try the following version - only some extra logging added and I've added some extra code to exit the crashed lua thread to see if this will prevent FSUIPC from hanging: FSUIPC7.exe

Could you try the following version please, which has some additional logging added. The lua will still crash, hopefully/maybe FSUIPC will continue (but probably not!) but some ectra logging should be avaiable - please show me your full FSUIPC7.log. You inly need to show me your lua & ini scripts again if they change. Thanks, John PS. You can turn off lua debug logging for the time being - I will advise if/when it needs to be activated again

The best place to determine what to use for such functions is the MobiFlight preset list at https://hubhop.mobiflight.com/. So, for the TBM930 generator, you need the following calculator code (from https://hubhop.mobiflight.com/#/presetview/950b5ca5-43eb-493b-92fc-f4bcff4572c3 😞 To set the master AP to trim only (https://hubhop.mobiflight.com/#/presetview/0742d4d1-0f5e-4495-8c8d-f2d873166b37 Not sure about this one, but try the available hvars (there is a G3000.havr file included in under your HvarFiles folder - to use the hvars, you need to copy this file to either the FSUIPC WASM folder or the MSFS working folder for WASMs, and rename to have a substring match on your aircraft - see the Advanced User manual for details). Once you have installed the *.hvar file, the follwoing hvars should be available for you to try: John

Ok, now I understand. However, what threw me i that in your FSUIPC7.ini you have: UseProfiles=Yes and not UseProfiles=Files So your main FSUIPC7.ini is not configured to use profiles as separate files. So I am confused to how your JS145.ini is being used, and thus how the JS145.lua is being started. John

No, this was added to FSUIPC7 only. I can look into adding for FSUIPC6 if needed. I can post a version for you here to check once done. John

Ok, thats good to know. Presume that is with using the new ini parameter set. It is very strange that this fix/hack is needed though. I don't understand why that windows API call is not working on some Windows 11 systems. It must be due to some windows system libraries somewhere, but if its not the VC++ redistributables I don't know where the issue could be. John

Btw, how are you starting this lua? There is no [Auto] section (or [Auto.xxx] sections), and no ipcInit.lua or ipcReady.lua. In fact, you have various profiles set-up, but nothing that uses them (i.e. no profile sections for axes, buttons, keys, calibration, autos,...).