John Dowson

Well, using either 0x66C0 or "66C0" should work. This is a free user offset used by many folks (including me) for years without issue, so something else must be happening... Please activate logging for lua plugins, as well as offset logging for 0x66C0, and generate a log file running the lua, and show me that as well as your lua script.

No. Currently no access to weather information in MSFS using FSUIPC7.

Hi Ray, FSUIPC only holds the details of the nearest 96 AI aircraft. For ground traffic, you could monitor the additional AI ground aircraft data at offset D040, matching on the departure ICAO to your landing ICAO, and then check/match the runway (and/or maybe the runway designator?). For the state, you would need to read from E080. Any matches, you could then kill (via offset 2900). You could do this in lua. Interesting project.... There is also the 'Detecting runways in use' facility, at offset D000, but I don't think that provides AI details for you to kill. Pete may have other suggestions... Cheers, John

I have already told you: i.e. the folder in which you installed FSUIPC7, where the FSUIPC7.exe is located...

Ok, then try creating the A320.mcro file, as advised. Then go into your button assignments and click 'Reload all buttons'. That should pick up the .mceo file (if created while FSUIPC7 was running - if you started FSUIPC7 AFTER creating this file, it should already be recognised). Then if you turn you rotary, you should see each rotary position recognised as a button press. If you don't see your rotary buttons, I think you will need to use MobiFlight (or the lua com library....), If you do, you can assign to that lua script, and give the parameter for each button press that indicates the mode you would like to set with that button.

That is because you have lots of logging options enabled. Disable those for now. That log file also shows that FSUIPC7 closed down successfully as MSFS exited - FSUIPC7 didn't crash: Are you sure that is the log from your "crash"?

If you want to assign in MobiFlight, then you need to go to MobiFlight support. I do not use MobiFlight (excpet the WASM, occasionally) and cannot adivise on how to assign using MobiFlight. To assign in FSUIPC, you can do this in two ways. 1. Using a macro file To use this method, create a macro file (e.g. A320.mcro) in your FSUIPC7 installation folder and add the following content: You can then assign your button/rotary to this, with the parameter indicating the mode, so assign to that for each "button" on your rotary with the appropriate parameter. 2. Using lua There are various ways to do this in lua. You could have an event.button call whose event function writes the value to the lvar. However, it may be easier (for a novice) to just have a simple script (e.g. mfdNavMode.lua that simply uses ipc.writeLvar to update the lvar with the provided (global) parameter. I can explain further if you assign in FSUIPC, but if you are assigning in MF, probably better to talk to MF support directly, either via their forums or Discord server (e.g. https://discord.com/channels/608690978081210392/749561530672087091)

To be clear, first try using those lvars directly (with the latest FSUIPC7.1.0 beta, soon to be released). If you want to use events, create a file in your FSUIPC7 installation folder, called (say) FBW.evt, and add the following: You can then see those events in FSUIPC's drop-down menus for assignment. If you want to use them externally, you will need to know which control numbers are assigned to the events. The control numbers for events in event files are determined as follows: control number = 32768 + (event file index)*256 + event index number where event file index is the index number of the event file (in your FSUIPC7.ini, under [EventFiles]) and event index number is the index number if the event in the event file. So, the first event in the first event file will have a control number of 32768, the second event 32769, first event in the second file as 33024. etc

The FBW events just control hvars/lvars. If you are writing a FSUIPC client program and wish to use lvars, you are better off using the FSUIPC WASM module _ the WAPI (the WASM API) which will give you an API to access and control hvars and lvars. This is a C++ API, but there is also a c# wrapper dll. See I'll let @Paul Henty comment if using this with his .net client dll. If you want to use custom events with FSUIPC, you can add these to FSUIPC by using event files (*.evt). There is a thread (or two) in the FSUIPC7 support forum on how to use the MobiFlight events/WASM with FSUIPC7 (but, as I said, you don't really need this for most things, as you can use the hvars/lvars directly). P.S. No idea what that image you attached is, and its too small to read,

Can you please supply more information. I need to at least see your FSUIPC7.log file, and a description of what you were doing when FSUIPC7 crashed would be helpful.... By thee way, have you installed FSUIPC7 into the MSFS folder: ? If so, please re-install into another folder, e.g. C:\FSUIPC7 or C:\MSFS-Add-ons\FSUIPC7. You should not install it into the MSFS folders or any windows protected folders (such as Program Files, etc.

Go to the Add-ons -> WASM->Set lvar... menu option. Then select that lvar from the drop down, and try changing its value to one of the following: Then try the same with A320_Neo_MFD_Range (again, using the values I posted earlier). What we are trying to achieve at the moment is to determine which lvars you need. So test them, to see if those are the ones you require. But it won't appear in the log if controlled by and lvar - that is events being logged. As I said, when you select 'rose arc', you should list the lvars again and see which lvar has changed, it won't be logged as an event if not controlled by an event.

I thought you wanted to control the mode and the nd range, which are, as I said earlier: otherwise please explain in more detail what you are trying to do. What do you mean by 'arc knob', and what does it do? I though that ARC was a nav mode, not a knob... I am not that familiar with the A320, or airliners in general, so you have to give more detail and explain what you are trying to achieve. What does the 'arc knob' actually do/change in the FS?

And the WASM menu now has Disable instead of Enable? Try restarting FSUIPC7, and if its still the same show me your FSUIPC7.ini file.

Use ipc.writeUB(0x66C0, 1)

That certainly shouldn't happen and is the first time I have heard this... You can only minimize the main FSUIPC window, and then it sits in the task bar like all other windows apps, until you open it. However, if you close the main window, FSUIPC7 will go to your system tray - did you look there? You can double click to open, or click/right-click for the context menu for direct access to some functions. You can also use Alt-F (default, can be changed) hot key to open/close FSUIPC7 to/from the system tray.

Do you have an aircraft loaded, i.e. not in the menu screens?

In the Add-ons menu, you should see a WASM entry. Under that, you first need to Enable (you only need to do this once). Then the other menu entries should be available, which let you explore (list, set, etc) lvars. Best to have you plane loaded and 'ready-to-fly) before you start experimenting. The menu entries under the WASM menu are just for exploring/testing. Once you tried some and found the ones you need, I can show you how to add them to offsets or use them in assignments.

Ok. Then we need to find if there are any lvars that control this. First, you need to download and install the latest beta of FSUIPC7 that has access to lvars, available here: Then you need to determine the name of the lvars that control the nd range and arc. For the mode itself, I think this is held in the lvar A320_Neo_MFD_NAV_MODE_1 (or possibly A320_Neo_MFD_NAV_MODE or A320_Neo_MFD_NAV_MODE_2 - you can try them all), with values: 0: LS 1: LOC 2: NAV 3: ARC 4: MAP For the range, try A320_Neo_MFD_Range_1 (and also A320_Neo_MFD_Range and A320_Neo_MFD_Range_2), with values: 0: 10 nm 1: 20 nm 2: 40 nm 3: 80 nm 4: 160 nm 5: 320 nm First try downloading the beta and see if you can see these and change their values by using the Add-ons->WASM Set Lvar / List Lvars menu entry. Once you have found the lvars that you need, I can help you use those either directly in lua or use lua to put the value of the lvars in a free user offset for you to use as needed (for read purposes). To update, you need to either use an lvar macro or again a lua script, which I can also help you with.

The position of these switches can be read (and written to/set) using the following lvars: XMLVAR_RMP_R_On XMLVAR_RMP_L_On with values 1 for on, 0 for off. You can write a short lua script to read those values and populate a user offset. Note that you need to download the latest beta of FSUIPC7 to use lvars (latest version currently 7.1.0g), although I am planning to release this officially in the next day or two.

Not necessarily... Well, if you are building your own AP panel, then that would be the difficult part (for me at least!). Lvars are not difficult to use, and I can help you using those or getting the values into offsets, if available. Which aircraft (and mod, if applicable) are you using?

Please repeat the test with the attached version, v6.1.1g, and show me the log. Also, please show/attach the full log, not a continuation log. Thanks. FSUIPC6.dll

First, please give your post an appropriate title, relating to your issue, not your name. I have updated it for you this time. You are looking at the offset status document. For FSUIPC7, this is old/out-of-date, and must be read in conjunction with the offset status spreadsheet that is included in the zip you downloaded. If you take a look at that spreadsheet, you will see these offsets are in red, i.e. not working. They are not working as they were populated from lvars in previous versions of FSUIPC. Even though we now have access to lvars in MSFS (via the v7.1.0 beta currently available and soon to be released officially), they won't be the same lvars as for other FSs. If there are lvars available with the information you need, you could try reading the lvar directly (using the latest beta), or have a simple lua script that writes the lvar value to a user offset for you to read. I've attached the latest offset spreadsheet for you. offsetStatus-v0.18.ods

Ok, thanks. However, the logging I was after (slope adjustment) doesn't seem to be present. I think I may have added that logging to FSUIPC7 only at the moment, so I'll add that to FSUIPC6 and post you another dll to try, to produce the same log.

Yes, sorry - you already have a calibration section in your ini. I missed it as there is no new line before it for some reason! Could you activate logging for Extras please, as well as Axes Controls, produce a short log file showing your issue (i.e. move each brake through its full axis range). and show me the log file. Thanks.

In the calibration tab (not the axis tab)? It shouldn't be, as you have no profile specific calibration, only profile specific axis assignment.