John Dowson

You could try the HidScanner utility, available here: Then that would confirm it is a problem with your hub. I agree and also use powered hubs, but make sure that the hub has enough power for all the attached devices.

That is because it is not a standard MSFS control/event, but a custom event. Presumably its from a 3rd party add-on, do you know which one? It doesn't look like a MobiFlight event/preset, or an FBW one - the corresponding FBW event is A32NX.FCU_ALT_PUSH - do you mean that? To use such events in FSUIPC, you need to make an event file (*,evt) to make them known to FSUIPC. Please see the Advamnced User Manual. A bunch of event files are included in the EventFiles sub-folder of your FSUIPC7 installation. If the event is the FBW A32NX.FCU_ALT_PUSH (and not A32NK_FCU_ALT_PUSH), then you can make this (and other FBW events) known to FSUIPC7 by moving the file flybywire-aircraft-a320-neo.evt from the EventFiles sub-folder to the main installation folder (i.e. up one level). John

No, as letters have now been assigned to your controllers - if you changed that back it just wouldn't assign letters to newly detected controllers, it wouldn't make any difference to your current set-up. If you are not manually assigning letters, best to keep this set to 'Yes'. John

To check if its a USB problem, try switching to a different (powered) USB hub, if available. Also, if its on a USB-3 port, try with a USB-2. Otherwise it does sound like a faulty device... John

That is weird....! Can you attach (if possible - better than pasting) your latest FSUIPC4.ini, .log and .JoyScan.csv files.

If you are using the MF events (rather than calculator code via lua) then you can change the calc. code by editing the file Community\mobiflight-event-module\modules\events.txt If you take a look at that file it should be obvious what you need to change.

Check the power management settings on your USB hubs - make sure that the Allow the computer to turn off this device to save power checkbox is unchecked. John

Checked further and the following calculator code works for R Pitot Off: 2 0 (>K:2:PITOT_HEAT_SET) 0 (>L:DEICE_Pitot_2) I've also updated my previous comment with this correction. John

Check the descriptive text in the MF preset app. For the Prop DeIce and Inertial separator, there is some descriptive text that explains why the animation isn't working since SU5 and a workaround. For example, here's what it says about Prop Deice On (TBM930_PROP_DE_ICE_ON): Similar fixes for Prop DeIce Off and Inertial Separator on/off. For the windshield, using the control Windshield Deice Toggle works, including animation, for both on and off, and also the control Windshield Deice Set with a parameter of 1 for on and 0 for off. For the R Pitot Heat Off, there looks to be an error in the calculator code: 1 0 (>K:2:PITOT_HEAT_SET) 0 (>L:DEICE_Pitot_1) should (most probably) be 1 0 (>K:2:PITOT_HEAT_SET) 0 (>L:DEICE_Pitot_2) (** Update: should be "2 0 (>K:2:PITOT_HEAT_SET) 0 (>L:DEICE_Pitot_2)" which works!**) However, that also doesn't work. Also, the toggle function is documented as no longer working since SU5. So, I'm not sure about the animation for R Pitot off. I suggest that you ask about this (and maybe mention the problem in the calc code) with MobiFlight on their discord channel (https://discord.com/channels/608690978081210392/804426413000097824). Later: I was just double checking this, and the calc code for the MF preset for R pitot off has now changed to this: 0 (>L:XMLVAR_Pitot_2) (L:XMLVAR_Pitot_1) ! (L:XMLVAR_Pitot_2) ! and (A:PITOT HEAT, bool) == if{ (>K:PITOT_HEAT_TOGGLE) } This sort of works.... If L and R are pitot heat are both on, it will turn both off. However, if R is on and L is off, it turns L on. Strange. Changing this to: 0 (>L:XMLVAR_Pitot_2) ! (L:XMLVAR_Pitot_2) ! and (A:PITOT HEAT, bool) == if{ (>K:2:PITOT_HEAT_SET) } works for turning R pitot heat off, but also turns off L Pitot heat. Maybe worth checking with MF what the correct calc code should be (I'm no expert in this unfortunately - something I need to learn more about!). John

Simconnect text facilities are completely broken in the current release of MSFS and shouldn't be used. Can you please show me your lua script + FSUIPC7.ini and I can take a look. To read the offset, use ipc.readUW(0x0D0C). You then need to use the lua logic library to extract the value of the bit you need, so something like: lights = ipc.readUW(0x0D0C) navLightsState = logic.And(lights, 0x0001) beaconLightsState = logic.And(lights, 0x0002) landingLightsState = logic.And(lights, 0x0004) ... cabinLightsState = logic.And(lights, 0x0200) John

No hay una version beta de FSUIPC7 - esa fue la versión inicial lanzada hace más de un año. La funcionalidad de rueda del mouse se eliminaron de FSUIPC7 ya que no había funcionalidad para implementar esto en el SDK de MSFS. Voy a echar un vistazo para ver si la funcionalidad están ahora disponibles para esto y si puedo restorar esta funcionalidad. John

Did you try both the TBM930_PITOT_R_OFF and TBM930_Pitot_R_TOG presets? And also try executing the calc code using the Add-ons->WASM->Execute Calculator Code... menu option, with the following code: 0 (>L:XMLVAR_Pitot_2) (L:XMLVAR_Pitot_1) ! (L:XMLVAR_Pitot_2) ! and (A:PITOT HEAT, bool) == if{ (>K:PITOT_HEAT_TOGGLE) } Maybe there are some hvars that control the animation, but if so I would have expected them to be used in the MF preset calc code. There are some presets for TBM930_ICE_LIGHT_ON/OFF but I guess that is not the same. I'll take a look later to see if I can see anything. John

You are using a very old version of FSUIPC7, v7.0.5 - can you first please update to the latest version, v7.2.10, and try again. Only the latest version of FSUIPC7 is supported - you should always check for an update before posting for support. Do you have a throttle and a stick? FSUIPC is only recognising one device, which rather strange. Do you have any saitek drivers or software installed? If so, please remove/uninstall and let windows install the default drivers. Once thats done, if you still have issues, please show me your update ini, log and JoyScan.csv files.

No, WideFS is a separate product and requires its own license. WideFS is composed of two components - WideServer, built into FSUIPC7, and WideClient, which is the application that you run in the client PCs. The WideServer component is part of FSUIPC7, but needs a WideFS7 license to be activated. John

Yes, shouldn't be a problem... Maybe start by reading the following topic: If you want to assign the 4 engine throttles to 1 lever, try with the Throttle Axis Set Ex1 control rather than the individual Throttle 1/2/3/4 Axis Sert Ex 1 controls, and similarly for the prop. That should work, but if there are any issues you can always overload the assignments and have 4 assignments (one for each engine) to the same lever. John

Debe leer los manuales, pero solo están disponibles en inglés... Si haa instalado FSUIPC7 correctamente, debería iniciarse automáticamente con MSFS y estar en la bandeja del sistema. Ábralo desde allí o pruebe la tecla de acceso rápido predeterminada: Alt + F.

Not sure what that means, or why that matters... The FSUIPC WASM or the MF WASM? To use the MF presets, you need the MF WASM also installed. There are a bunch of event files for the MF WASM module that are included in your FSUIPC installation, in a sub-folder called EventFiles. To use them, if you have the MF WASM installed, just move the files that you want to use into the main FSUIPC7 installation folder (i.e. up one level). The presets should then be listed in the controls drop-down in the assignment panels. Note I created those event files a while ago now, so they may be slightly out of date. You can always update them as required.

Sorry, but I am not sure what you mean. I gave the link the to MobiFlight preset list in my previous comments - did you take a look? You can use the MobiFlight presets directly if you wish, but you need to install the MobiFlight WASM module for them to work, together with an event file (or more) to make the MF events known to FSUIPC. There are various support topics on this. Otherwise you can use the MF preset list to see what lvars/hvars/events are available and use them in your FSUIPC assignments. John

Yes, its still active, See the other topics in this forum (not comments in this post). For lvar.havr access, see this thread: John

R pitot heat is listed in the MF preset list as using the following calculator code (see https://hubhop.mobiflight.com/#/presetview/06827297-b5d9-45e9-a692-6f8573cdd47f) 2 1 (>K:2:PITOT_HEAT_SET) 1 (>L:DEICE_Pitot_2) Have you tried that? It is using the Pitot Heat Set control, together with the DEICE_Pitot_2 lvar. On fact, the following MF presets are available: And for windshield heat there are: So windshield ice on is 1 (>K:WINDSHIELD_DEICE_SET) which can be achieved directly in FSUIPC7 using the event/control Windshield Deice Set with a parameter of 1 (K variables equate to MSFS/FSUIPC events or controls).

Can you please attach your FSUIPC7.log, FSUIPC7.ini and FSUIPC7.JoyScan.csv files please and I will take a look.

To access lvars (+ hvars and ability to execute any calculator code) from c#, you can use the FSUIPC WASM module with the WAPI dll wrapper, available here: http://www.fsuipc.com/. The dll is just a C wrapper around the .lib. Both are also available on github - see FSUIPC WASM API library: https://github.com/jldowson/FSUIPC_WAPI DLL wrapper: https://github.com/jldowson/FSUIPC_WDLL test client: https://github.com/jldowson/WASMClient I will also put the WASM on github at some point.... You should also take a look at Paal Henty's .Net dll client - this uses the FSUIPC WAPI (as well as the FSUIPC SDK) - see https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ John P.S. You can also just download FSUIPC7, install it and look in the SDK folder. All programming features are free to use (no license required). However, as you are already using Simconnect and jyst require access to lvars/hvars, its probably only the WAPI / WAPID inrterface that you may want ti use, but that may be easier to access via Paul's .net client dll (see http://fsuipc.paulhenty.com/#home)

Yes - it seems to me that the problem isn't that they have changed which weight is in each index, which isn't an actual issue, but that they are not actually updating the indexed simvar PAYLOAD STATION WEIGHT with the correct values/weights, which is why the FSUIPC offsets are reporting 0 for each of the offsets associated/mapped to this simvar. John

I have just taken a look at what the offsets hold for both the stock A320 and the FBS A320 (development). This is what I see in the offsets for the stock A320: The strings are pretty useless as they are the internationalized version which has been truncated. I will make a note and look into correcting these. There are 6 payloads provided, although the final one is 0. For the FBW A320 (development) I see the following: So it is providing 10 payload weights, but they are all 0. You really need to raise this with the FBW team. John

👍