John Dowson

Please download and install the latest release of FSUIPC7, v7.2.13. The dll wasn't updated in this version (I will update), but I have just tried it and it seems to work fine. John

Where is this lever? Is it the one with the tooltip 'ENGINE CONDITION'? There are a few lvars that look they relate to this lever: Condition_Lever_CutOff_1 PC6_IDLECTRL_LOCK PC6_IDLECTRL_LEVER And I can see that a FUEL_SELECTOR_ALL event is also logged with a parameter of 1 when you move to a certain position - then its logged with value 0 straight afterwards (this event seems to be continually logged!). I've tried setting those lvars but that didn't seem to have any affect. It may be possible with a combination of setting lvars and sending events (via calculator code), but first you need to determine the lvar changes and events sent when you move in the UI and then try and replicate. Otherwise, there seem to be quite a few events that don't seem to have any affect when sent via Simconnect (e.g. using FSUIPC) but do when assigned in the sim. If you find a control/event in the MSFS control assignments that works, you can assign this to a key press (in MSFS) and then assign to that keypress in FSUIPC7. I am pretty busy at the moment with various issues with the latest SU7 and FSUIPC7 updates so don't have time to look into this any further at the moment. I can maybe take a further look later in the week, once things have settled down a bit.... John

So the lever just acts as an on/off button, no? Then why do you want to assign it as an axis? You can assign to that control to any button or switch. If you really want to assign to an physical axis, you can initially assign the axis to an unused axis control (left hand side of axis assignments dialog) and then assign to the Set Fuel Valve Eng1 in the right hand side of the assignments panel, with a parameter of 1 when going into a certain range and a parameter of 0 when exiting. Otherwise, please explain exactly what you are trying to achieve, i.e. what are you trying to assign to this? Have you tried assigning something to that control? Having download/update issues with SU7 so can't take a look at the PC-6 yet, will do later if you can provide further info on what you are actually trying to do. Thanks, John

It should be ok under this folder (although I see I have missed the 'Work' folder in the documentation - I will add/update). Do you see your FSUIPC_WASM.log files there? The FSUIPC_WASM.ini needs to be in the same location as these files. Can you try changing the LogLevel to Debug in the ini file in that location, to see if that has any affect? It will work there but that file will get overwritten when you next update, so better to add to the other location really... John

Sorry, looks like I forgot to update the FSUIPC_WAPID.dll. Can you try the attached please - drop it into your FSUIPC utils folder, replacing the version already there. John FSUIPC_WAPID.dll

Thanks, and sorry I can't help further. This is a very strange problem - please report back if/when you have found the cause and/or a solution. John

Looking at this again, the log extract shows that the Sim has stopped, so you weren't in a flight, which is why it wouldn't connect. Was that not the case? Please use the v7.2.13 released version (download if not done already). Please try one last time with this version. There really should be no difference between when auto-started and manually started (except maybe with permissions). John

I'm sorry but I am getting confused as you said it is now showing in the system tray...it helps me a lot if you could be a bit clearer... Is this correct: You start FSUIPC7.exe by double clicking it, you see a splash screen which disappears after a few seconds, you then see the FSUIPC7 icon in the system tray for a brief period, but it then disappears, and when you go back to the installation folder the FSUIPC7.exe has been removed. ? If that is not the case, please explain. If that is what is happening, then sorry but I have no idea what can be doing that, but it must be something like an anti-virus program. FSUIPC is not crashing - if it was there should be something logged somewhere (i.e. in the Windows event viewer), and it certainly isn't 'deleting itself' - that must be done by another program or service.

Is this actually an axis control then? i.e. the parameters to that control are over a range and not 1/0 (on/off)? Please confirm, and if that is the case then yes I can flag them as axes controls. I will post a version here for you to test once confirmed. John

What happens when you click the 'Set' button? It should change to 'Reset' and show the buttons to enable calibration. If that is not the case, can you tell me what happens and/or attach a screenshot of the calibration window. Also attach your FSUIPC7.ini file so I can take a look. Can you start MSFS/FSUIPC7, activate axes logging, load an aircraft, apply and release your toe brakes, then exit FSUIPC7 and show me your FSUIPC7.log file as well. Thanks, John

It won't, as its a WASM ini parameter, not a WAPI one. You need to add it to your FSUIPC_WASM.ini file, either under your Community/fsuipc-lvar-module folder or under your AppData folder, which is better as it then will not be overwritten when you update - please see the Advanced User guide for details. John

If this happens also when assigning directly via P3D, how do the aircraft makers tell you how to configure the throttle? Have you checked or asked about this on the Aerosoft or Milviz forums? I see Pete has also just replied... Sounds lie you are assigning in P3D and then calibrating (not assigning) in FSUIPC. I am surprised this works, as this can cause issues due to priority levels, as Pete has said. I currently don't have any of those add-ons to check - but I'll see if I can get one to take a look... John

Ok, so you can open the FSUIPC main window from the system tray icon, or by pressing Alt + F? What do you actually mean by this? That he FSUIPC7.exe file is actually deleted from the folder where it was installed? If so, then this can only possibly be done by some sort of anti-virus program, and you should have a notification somewhere that this was done. You could try searching for the FSUIPC7.exe using Everything (available from https://www.voidtools.com/downloads/) - this may show you where it is if it has been quarantined by an anti-virus program. Or please explain what you mean by 'keeps deleting'. If FSUIPC7 is running, which it must be doing if its in your system tray, I cannot see how it can be deleted. John

You do not have to list the lvars before using them. Lvars are automatically loaded 5 seconds (by default, changeable using the LvarScanDelay WASM ini parameter) after the aircraft is 'ready-to-fly'. And listing lvars doesn't reload them - it just lists those available (in memory), that have already been received. This sounds strange as lua scripts are not started unless the lvars have been loaded...Maybe they were loaded (do you see any lvars?), but the ones you are using aren't available? Note that with more complex aircraft, not all lvars are available with the default LvarScanDelay of 5seconds and this may need to be increased. I have mine set to 45 seconds, which is tuned for the airliners as they seem to take a long time before they are available, especially in the FBW A320. I also have the Just Flight Arroe III/IV and have no issues with lvars, so maybe try increasing that parameter. You could add Debug level logging to to the WAPI, which will log further messages so that you can see when the lvars are available. If you are still having issues, activate that debug logging and show me your FSUIPC7.log file. Also, make sure you are using the latest version of FSUIPC7, v7.2.13, released a few hours ago (and recompiled against the latest SDK released with SU7). John

Are you using the Working Title mod? There is a report in the Asobo forums that this is no longer working correctly since SU7 with the lesson scripts - may be related? https://forums.flightsimulator.com/t/su7-new-lessons-ifr-vor-issues-with-workingtitle-g1000nxi/472878 John

Your installation log looks fine, except that you are installing quite an old version. Please download the latest version, v7.2.13, and try again. Why do you think this? Your log shows the FSUIPC7.exe was installed ok: John

FSUIPC just uses the AP Alt Var Set English control/event. No idea why this has changed. Are you using the stick G1000NXi or a mod? Btw, just release FSUIPC7 v7.2.13, which has been recompiled against the latest MSFS SDK for SU7 (0.16.0.0), as well as containing a few bug-fixes + additional offsets/features. John

You need to install the x64 ones, and make sure its the combined package (2015, 2017, 2019 and also now 2022 I think...). And its the IctallFSUIPC7.log file I need to see about the install problems, if you still have them after installing the VC++ restribs. John

One thing you can do to try and track this down is to activate logging for IPC Reads and IPC Writes, using the FSUIPC7 Log menu. Also Open the logging console (from the same menu). When you get that error, take a note of the timestamp of the last message logged, then acknowledge the message and then exit FSUIPC7, and show me your FSUIPC7.log file. John

So you not have your original lua anywhere that you can use? I'm sorry but I cannot help you with this. If you did this before, surely you can do it again, if you can't find your original script. As well as not being sure what you want to achieve, I have never looked into voice commands in lua... Not sure what you mean by this. If you found the information that you needed previously, it will still be there... John

@kingm56 I can maybe add these to some FSUIPC offsets - possibly the same ones if its an either/or situation. I could possibly also make them writeable by triggering the Fuel System Pump Toggle event when written to. I will put this on my list to investigate, hopefully later this week. I have now added these. The 747 has 16 pumps, so I have added 16 indexed variables for each of these, so 32 new offsets in total. I am not sure how useful the FUELSYSTEM PUMP ACTIVE simvar is - seems to be used in the 747 bit not in the 787. I have added it anyway as rad-only. The FUELSYSTEM PUMP SWITCH simvar has been made writable, and will trigger the FUELSYSTEM_PUMP_ON/OFF controls. I have teted this in both the 747 and 787 and you can control all pumps writing to these offsets. The new offsets are (not not all contiguous!) the following, all 1 byte: 0x0B02 FUELSYSTEM PUMP ACTIVE:1 0x0B03 FUELSYSTEM PUMP SWITCH:1 0x0B04 FUELSYSTEM PUMP ACTIVE:2 0x0B05 FUELSYSTEM PUMP SWITCH:2 0x0B06 FUELSYSTEM PUMP ACTIVE:3 0x0B07 FUELSYSTEM PUMP SWITCH:3 0x0B08 FUELSYSTEM PUMP ACTIVE:4 0x0B09 FUELSYSTEM PUMP SWITCH:4 0x0B0A FUELSYSTEM PUMP ACTIVE:5 0x0B0B FUELSYSTEM PUMP SWITCH:5 0x0B10 FUELSYSTEM PUMP ACTIVE:6 0x0B11 FUELSYSTEM PUMP SWITCH:6 0x0B12 FUELSYSTEM PUMP ACTIVE:7 0x0B13 FUELSYSTEM PUMP SWITCH:7 0x0B14 FUELSYSTEM PUMP ACTIVE:8 0x0B15 FUELSYSTEM PUMP SWITCH:8 0x0B16 FUELSYSTEM PUMP ACTIVE:9 0x0B17 FUELSYSTEM PUMP SWITCH:9 0x0AEE FUELSYSTEM PUMP ACTIVE:10 0x0AEF FUELSYSTEM PUMP SWITCH:10 0x0AF0 FUELSYSTEM PUMP ACTIVE:11 0x0AF1 FUELSYSTEM PUMP SWITCH:11 0x0AF2 FUELSYSTEM PUMP ACTIVE:12 0x0AF3 FUELSYSTEM PUMP SWITCH:12 0x0AF6 FUELSYSTEM PUMP ACTIVE:13 0x0AF7 FUELSYSTEM PUMP SWITCH:13 0x0AFA FUELSYSTEM PUMP ACTIVE:14 0x0AFB FUELSYSTEM PUMP SWITCH:14 0x0AFC FUELSYSTEM PUMP ACTIVE:15 0x0AFD FUELSYSTEM PUMP SWITCH:15 0x0AFE FUELSYSTEM PUMP ACTIVE:16 0x0AFF FUELSYSTEM PUMP SWITCH:16 I have also added the new indexed simvar FUELSYSTEM ENGINE PRESSURE to the same offset as the GENERAL ENG FUEL PRESSURE simvar, with units kpa (not psf, as the original simvar for this offset). These new offsets are available in the attached version, v7.2.13e, if you would like to try them. After I release this I will revise the MSFS SDK documentation to document the newly available simvars in the FSUIPC offset documentation. I won't be adding these to offsets unless requested - I will add them to the end of the document as 'available upon request'. Regards, John FSUIPC7.exe

Are you saying that offset 0x3366 is correctly showing the engines on fire, but PM cannot detect it? If so, then, as FSUIPC is working as expected, and you need PM support. Or is the offset not correctly showing which engines are currently on fire? If you are not sure, try logging the value in that offset (as a UB in hex) to see if they change as expected. John

Answering my questions would help... Ok, so FSUIPC7 has definitely crashed, but there is no related windows event. Very strange... Can you please try try-installing your VC++ redistributables, as I have now advised several times. Have you extracted the installer from the zip file before running? If so, I need to see your InstallFSUIPC7.log file. But not before you have updated your VC++ redistibutables, as advised, so do that first and try again.

Then the error is with that program, which I don't know and cannot help with. You need to contact the support for that program.

Ok. I'll check this and see if I can automatically reload on USB device reconnections if/when in a flight. However, better to try and stop the re-connection if possible. Is the trim wheel connected to this hub? If so try moving it. In fact, try changing it regardless of the hub you are currently using. John