John Dowson

It could be a faulty button that is continually firing. You can try the IngnoreThese ini parameter, from the Advanced User Guide:

There i the following additional data in the PMDG_777X_Data data structure. This is now written to the 2nd PMDG data offset area, from 0x6C00

Yes

Can you try the attached version please - its untested as I don't have any PMDG aircraft: FSUIPC6.dll

Does that hvar exist in the TBM 930? Have you added it by adding a hvar file for the TBM 930? What does FSUIPC7 show when you list hvars (from the WASM-> Lisy Hvars menu entry)? Not that, up to now, FSUIPC7 only installs a hvar file for the A320, although there is also one available for the DA40-NG (although I haven't tried this). If you have an hvar file available for the TBM 930, maybe you could share it? Oh - and there are no values associated with hvars (as far as I know). You just activate or trigger them (which is what the Set command does).

Here's a reasonable description on the various varialbe types on the Asobo forums (https://forums.flightsimulator.com/t/demo-lvar-write-access-for-any-aircraft-control/353443/19?u=impolitegem5317😞 H variables can be used via the Panels execute_calculator_code function (which is what is used by FSUIPC7 for these variable types), so it may also be possible to do this with O: variables. However, as there is no direct support for O: variables in FSUIPC7 (as there is for H: and L: type variables), the only way to try would be to use the ipc.execCalcCode() function.

To use the lvars you have to use lua or a macro file. You can then assign to the macro (or lua, if not auto-running). As for the AS 1000 MFD RANGE INC control, maybe it takes a parameter (other than 0)? But it puzzles me why you are shoeing this as you were asking about master caution/warning...

Ah, you are using MobiFlight events... Presumably you have the MobiFlight WASM installed, no? Which FBW mod are you using? Maybe try switching mods, otherwise, as these are MobiFlight events, you will need MobiFlight support for this. However, most MobiFlight just trigger lvars or hvars. You could look at the available lvars/hvars for the A320 and see if there are any you can use instead of the MF events. And, BTW, the log you attached was a continuation log, so doesn't tell me much (not even the aircraft you were using). In future, when I ask for logs, please attach the full log.

This was an error in my config - I had updates turned off in both the WASM and the Client (LvarUpdateFrequency ini parameter). Working fine now.

Just tried these and they seem to work, setting 1 to activate and 0 to clear. However, when reading the values back, I am only getting 0 for each lvar. Not sure why at the moment - I will look into it.

Have you tried the following lvars: Generic_Master_Caution_Active Generic_Master_Warning_Active ? Here's the full list of lvars that FSUIPC7 finds for the TBM 930:

This is the complete list of event for the G3000 from the latest cip file (https://bitbucket.org/mobiflight/mobiflightfc/src/master/Presets/msfs2020_eventids.cip😞 If the events aren't working, you could ask over on the Mobiflight discord channel (https://discord.com/channels/608690978081210392/804777121255915562).

You can just attach it here.

I'm not sure what you mean... Do you mean the assignments to your buttons 162-179 are not working? Or that you cannot assign to those in MSFS? (and by keys, I presume you mean buttons, no? If the former (assignments not working), please activate logging for Buttons & Keys as well as Events, and produce a short log file where you press those buttons, then show me your FSUIPC7.log file as well as your FSUIPC7.ini file. If its the latter, then thats more a question for Asobo, but why do you need to assign in MSFS if they can be seen and assigned in FSUIPC7?

Has the SDK been updated for this? When was this update released? Could you send me the header file and I'll check it against the one we are using, to see if an update is needed. Thanks, John

Is FSUIPC running? If so, check your FSUIPC7.log file to see if /linda is being started, or post it here. If Linda is starting but can't find FSUIPC7 (and FSUIPC7 is running), then you need the Linda support forums.

The mapping from joy letters to joystick IDs is held in your FSUIPC7.ini file, in the [JoyNames] section. However, you should prefer to use letters over ids, as shown by Roman, as these will be fixed but the joystick IDs may change. If the IDs do change, its easy to update the mapping section to re-enable your assignments when using the Joy Letters facility. There is a section on Joy Letters in the User Guide (P20). This facility was also made active by default in FSUIPC7 - in previous versions it was off by default.

The first EXE.xml file is corrupt and is not even an xml file! It looks like it was updated by AFC Bridge, which I think is something to do with the Honeycomb Bravo (to fix the lights?). Do you use this? The second EXE.xml you posted looks fine, and should auto-start FSUIPC7. Is it now working for you? Is PACX now able to connect? If you want to add AFC Bridge back to your EXE.xml, you can try replacing its contents with the following:

FSUIPC7 is not auto-starting due to this error in your log file: This is usually due to another product corrupting the EXE.xml file (usually some logitech add-on for MSFS, but could be others). You can either remove that file and re-install (as suggested in the log), or post it here and I will correct it for you (if you also want whatever corrupted it also to be started).

I don't know PACX, but is FSUIPC7 installed and running (can you see its icon in your system tray)? If its not running, download the latest version from www.fsuipc.com and re-install (no need to uninstall). Then start MSFS and if FSUIPC7 is installed correctly and running you will see a splash screen and an icon in your system tray. If you don't, show me your InstallFSUIPC7.log file.

I think you need to add a delay between the write the read. The write takes a round-trip to MSFS, and then the updated values need to be sent back to FSUIPC7. If you write, then read directly, you will be getting the old value back as the internal values have not yet been received from the server. It shouldn't take too long for this, but this also depends on the update frequency set for the lvar values (defaults on every frame at the moment). Anyway, as you have just written the value, if its a writeable lvar then you can just set eCon to that value (40). Otherwise, try adding an ipc.sleep call between the writing and reading, starting with 100ms and adjust as needed.

If you have filed a flight plan, he GPS aircraft destination airport ID is in offset 0x6137. Other than that, I think you would need to get the location of the current flight plan (from offset 0x0130) and parse the file yourself (using lua) to extract the ICAO parameter from the [Departure] and [Arrival] sections. You may find the origin in the previous waypoint offset (0x6081) if you have a flight plan, as reported here: John

For using the Xbox One/360 controller with FSUIPC, you could look into using this for the time being (although it looks rather complicated to set-up): https://github.com/samuelgr/Xidi. I'll take a look at this on more detail when I get a chance. - this would be an interim solution (if it works) to use before I add direct support in FSUIPC.

For using the Xbox One/360 controller with FSUIPC, you could look into using this for the time being (although it looks rather complicated to set-up): https://github.com/samuelgr/Xidi. I'll take a look at this on more detail when I get a chance...and this would be an interim solution (if it works) to use before I add direct support in FSUIPC.

Sorry, I have no idea what O: variables are or how to use them. If you know how to use them, you could try in lua using the ipc.execCalcCode function. John