John Dowson

There are a bunch of hvars exposed by MobiFlight to control the CDU in the A320Neo: "(>H:A320_Neo_CDU_1_BTN_0)", "(>H:A320_Neo_CDU_1_BTN_1)", "(>H:A320_Neo_CDU_1_BTN_2)", "(>H:A320_Neo_CDU_1_BTN_3)", "(>H:A320_Neo_CDU_1_BTN_4)", "(>H:A320_Neo_CDU_1_BTN_5)", "(>H:A320_Neo_CDU_1_BTN_6)", "(>H:A320_Neo_CDU_1_BTN_7)", "(>H:A320_Neo_CDU_1_BTN_8)", "(>H:A320_Neo_CDU_1_BTN_9)", "(>H:A320_Neo_CDU_1_BTN_A)", "(>H:A320_Neo_CDU_1_BTN_B)", "(>H:A320_Neo_CDU_1_BTN_C)", "(>H:A320_Neo_CDU_1_BTN_D)", "(>H:A320_Neo_CDU_1_BTN_E)", "(>H:A320_Neo_CDU_1_BTN_F)", "(>H:A320_Neo_CDU_1_BTN_G)", "(>H:A320_Neo_CDU_1_BTN_H)", "(>H:A320_Neo_CDU_1_BTN_I)", "(>H:A320_Neo_CDU_1_BTN_J)", "(>H:A320_Neo_CDU_1_BTN_K)", "(>H:A320_Neo_CDU_1_BTN_L)", "(>H:A320_Neo_CDU_1_BTN_M)", "(>H:A320_Neo_CDU_1_BTN_N)", "(>H:A320_Neo_CDU_1_BTN_O)", "(>H:A320_Neo_CDU_1_BTN_P)", "(>H:A320_Neo_CDU_1_BTN_Q)", "(>H:A320_Neo_CDU_1_BTN_R)", "(>H:A320_Neo_CDU_1_BTN_S)", "(>H:A320_Neo_CDU_1_BTN_T)", "(>H:A320_Neo_CDU_1_BTN_U)", "(>H:A320_Neo_CDU_1_BTN_V)", "(>H:A320_Neo_CDU_1_BTN_W)", "(>H:A320_Neo_CDU_1_BTN_X)", "(>H:A320_Neo_CDU_1_BTN_Y)", "(>H:A320_Neo_CDU_1_BTN_Z)", "(>H:A320_Neo_CDU_1_BTN_DIR)", "(>H:A320_Neo_CDU_1_BTN_PROG)", "(>H:A320_Neo_CDU_1_BTN_PERF)", "(>H:A320_Neo_CDU_1_BTN_INIT)", "(>H:A320_Neo_CDU_1_BTN_DATA)", "(>H:A320_Neo_CDU_1_BTN_FPLN)", "(>H:A320_Neo_CDU_1_BTN_NAVRAD)", "(>H:A320_Neo_CDU_1_BTN_FUEL)", "(>H:A320_Neo_CDU_1_BTN_SEC)", "(>H:A320_Neo_CDU_1_BTN_ATC)", "(>H:A320_Neo_CDU_1_BTN_MENU)", "(>H:A320_Neo_CDU_1_BTN_AIRPORT)", "(>H:A320_Neo_CDU_1_BTN_UP)", "(>H:A320_Neo_CDU_1_BTN_DOWN)", "(>H:A320_Neo_CDU_1_BTN_PREVPAGE)", "(>H:A320_Neo_CDU_1_BTN_NEXTPAGE)", "(>H:A320_Neo_CDU_1_BTN_L1)", "(>H:A320_Neo_CDU_1_BTN_L2)", "(>H:A320_Neo_CDU_1_BTN_L3)", "(>H:A320_Neo_CDU_1_BTN_L4)", "(>H:A320_Neo_CDU_1_BTN_L5)", "(>H:A320_Neo_CDU_1_BTN_L6)", "(>H:A320_Neo_CDU_1_BTN_R1)", "(>H:A320_Neo_CDU_1_BTN_R2)", "(>H:A320_Neo_CDU_1_BTN_R3)", "(>H:A320_Neo_CDU_1_BTN_R4)", "(>H:A320_Neo_CDU_1_BTN_R5)", "(>H:A320_Neo_CDU_1_BTN_R6)", "(>H:A320_Neo_CDU_1_BTN_PLUSMINUS)", "(>H:A320_Neo_CDU_1_BTN_SP)", "(>H:A320_Neo_CDU_1_BTN_DIV)", "(>H:A320_Neo_CDU_1_BTN_OVFY)", "(>H:A320_Neo_CDU_1_BTN_CLR)", "(>H:A320_Neo_CDU_1_BTN_BRT_S1)", // Experimental brightness increase (INOP) "(>H:A320_Neo_CDU_1_BTN_DIM_S2)", // Experimental brightness decrease (INOP). "(>H:A320_Neo_CDU_1_BTN_DOT)", However, I don't think its possible to use these yet. I am currently working on a WASM module for FSUIPC7 that should be able to handle these (and also lvars), but this is still a few weeks away. John

No mouse macros yet in FSUIPC7. If there are no controls in the dropdown, it means that there aren't any provided by MSFS. You can check to see if MobiFlight provide additional events for this, and if so you can install the MobiFlight WASM module and add the events to FSUIPC using event files. See and

What aircraft are you using? The magnetos seem to behave differently depending upon the aircraft. Did you try activating logging to see what controls are being sent? There are many controls for magnetos (set, off,, right, left, both, etc). Maybe try those to see if any work for the aircraft that you are using. FSUIPC only provides access to these controls that are exposed via SimConnect. If they are not working for a particular aircraft, then you can check the Asobo forums and maybe raise a bug report with Asobo. Some controls are momentary though (i.e. they take affect but then go back to the previous state), but this is also aircraft dependent.

The separate engine autostart controls are FSUIPC-added controls that use various offsets (depending on the aircraft type) to auto-stat the engine. Those offsets, or the controls/events sent when using those offsets, may no be working in the vanilla A320. I'll make a note and look into this at some point, but it may take a few weeks to get around to this. You could try one of the FBW mods to see if its working there. John

If you want to write to an offset, say 0892, then assign to Offset Word Set (0892 is 2 bytes or 1 word) and give the parameter a value of 2 (which is Magneto Left). Sorry, not sure what you mean by this. What controls are you using? Maybe activate logging of events (and open the FSUIPC console), and you can then see what controls (and parameters) are being used when you activate the buttons or the controls in the UI.

Sorry, but that seems to contradict itself! What 'works' if FSUIPC6 is not showing in the Add-ons menu? You can, but I wouldn't install directly there if I were you. You can create a Modules folder and install under that. If you P3D isn't loading the add-ons correctly, it may also be worth just uninstalling and re-installing the P3D client as this only takes a minute or two.

That is strange! You can try manually activating by editing your C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v5\add-ons.cfg file. Find the FSUIPC6 entry and change to 'ACTIVE=true'. If that doesn't work, I would re-install: - uninstall FSUIPC6, by using the uninstaller located in the installation folder (or using the windows Apps panel) - run P3D once: just start it and exit - re-install FSUIPC6. This time, select to install in a folder other than your P3D add-ons folder (which is the default location) - run P3D, and this time when it asks you to enable the add-on, select Yes

Sorry, what does this mean? What is 'hook'? If you activate it, don't you see the FSUIPC entry in your add-ons menu? Or are you saying that you can activate FSUIPC, but the next time you start P3D it is again not active? There is no "Modules" folder any more, although you can still install there if you so wish. I see that you installed FSUIPC6 in your P3D add-ons folder. It is better to just use this location for yout add-on.xml file and install FSUIPC6 in a separate location (e.g. C:\FSUIPC6 or C:\P3D Add-ons\FSUIPC6).

Try with the Rotoe Brake control first with the parameters mentioned in that post: There is also a spreedsheet (2nd comment in that link) with more control codes that may be useful.

Check the following post in the Asobo forums: https://forums.flightsimulator.com/t/thrustmaster-tca-quadrant-still-not-completely-working/309593/695 This seems to be saying that the autobrake is working in the vanilla A320 but not working correctly in the FBW mods as they are using lvars. The offset status document says offset 0x2F80 is working in the vanilla A320Neo but returns to 0 once set (i.e. is momentary). Is this not the case anymore (i.e does the document need an update for this)?

If you didn't activate it when asked, it won't ask again. Just go to the Options->Add-ons panel and activate/enable it from there. John

If you activate logging for events, can see the event being sent? if so, and its its not working, then it should be reported to MobiFlight.

Nothing! When you install a new add-on via the xml method, P3D asks you to activate the first time it is ran. Just click Yes and you are done. John

As we don't have the FSLabs A320, you are probably better of asking on the FSLabs forums. For example, this post has some parameter codes that can be used with the Rotor Brake control to control various lights: https://forums.flightsimlabs.com/index.php?/topic/10548-some-early-parameters-for-those-of-us-using-hardware-controls/ John

Can you activate logging for Buttons & Switches and Events, and produce a short log file with your aircraft loaded, press the button assigned to the macro then exit, and attach the log file together with your ini file and I'll take a look.

From the Advanced User manual: Up to 32 “AlsoManage” lines can be given, numbered 1 to 32. Your entries with numbers 33 and above will be ignored. Your FSUIPC is also out-of-date - the latest version is 5.157. John

The error is given (on line 7): [E] *** LUA Error: C:\Prepare3D v5 Add-ons\FSUIPC6\A2AB17_MixAdj_1.lua:7: attempt to call global 'adjust_mix_1' (a nil value) So its this call: adjust_mix_1 () This is calling a function before it is defined. There are also other issues with that script, such as the conditional in the adjust_mix_1() function has a dangling 'else', and variables being tested without being defined or set anywhere, and other variables being set and never used. It couldn't have ran without a hitch - the script must have changed. Do you mean the Linda main script or that script? Anyway, If using Linda, you should use their support forum. And your FSUIPC is out-of-date - the latest version is 6.0.12.

Thats fine, but you should delete the contents of the [General] section and let that get rebuilt, as many of the parameters no longer apply. You can manually remove any aircraft from profiles if you like, or remove profiles completely if you are no longer going to use them. But they do no harm. Sorry, but don't know what that file/link is you posted, but its not your FSUIPC7.ini file.

Have you installed the MobiFlight WASM module?

No, as that is for MSFS only. You say you have purchased FSUIPC5, which is for P3Dv4, so use that. I don't know Pilot2ATC, but I suspect it works with the unregistered/free version of FSUIPC anyway.

FSUIPC is only an interface to pass controls that it receives to the FS. How the FS responds is outside of our control. Yes...unfortunately. Many events sent to the sim can result in different events received, which also don't include the actual event sent. I'm not that familiar with the A320, or the MB events or this aircraft/mod, but maybe your question should be asked on the MB AS320 mod forums, if that is what you are using. Other that, I would at least need to see your FSUIPC log and ini files to comment further. John

This is about the 100th time this has been reported...please, if you have an issue, first check the documentation and then check for previous posts of the same problem before you post. The solution can be found in the provided README.txt: Not also that you should not install as admin, unless you installed MSFS as admin for some reason. Please read the provided README.txt (as the name implies!) and also the Installing and Registering FSUIPC document provided. John

They didn't get replaced. You specify the [Auto] section. FSUIPC writes the [LuaFiles] section with the .lua files it finds in your installation folder. If wasn't obvious that it should have been 1=Lua HidDemo and not !1=HidDemo.lua then I don't know what to say....perhaps I should give up providing user manuals...😞 This script has been available for many years and should work without too much trouble really...You should check the vid and pid are set correctly, and you can set the logging flag (in the script itself) as well as activating logging for lua plugins (from FSUIPC) so that you can see if it is running or not and perhaps what the error is. But as you have already stated that you will not be purchasing a license, and this functionality requires a license - and I am also very busy, I don't think there is much point assisting you with this any further, sorry. John

There are no hot keys in FSUIPC7, apart from the hot key to display/hide FSUIPC7 itself. Offset 0x0C1A was previously reported as working (as its marked in green in the offset spreedsheet) but I've just taken a look and it doesn't seem correct. I can see the value change occasionally, but it jumps back to 0, but sometimes shows other values (32, 64, 128). There are also no controls exposed via simconnect to control the sim rate, although there are some MSFS controls to increase and decrease (as well as set the sim rate). You can assign these to keys (in MSFS) and then assign buttons to these key presses in FSUIPC. However, there is no control to return to normal speed, and it difficult to know when you are at normal speed without that offset working! Here are some Asobo references to the issue, where another tool for this is mentioned that you could try: https://forums.flightsimulator.com/t/bug-changes-in-simulation-rate-are-not-displayed/8698 https://forums.flightsimulator.com/t/simulations-rate/351296/10 I will look into offset 0x0C1A to see what is happening with this, but this will take a while. I'm concentrating on providing lvar access at the moment, and am making a note of such issues and will look into them once I've released a beta of the WASM lvar access module. John

Yes, I know, thanks. I provide manuals so that I don't continually have to answer these type of questions... Your ini file has this: + The Advanced User Guide says: So, isn't it obvious that your ini's [Auto] section should be: [Auto] 1=Lua HidDemo ?