John Dowson

Yes, but you cannot use that if not using WideFS/WideClient. There is no Modules folder in either FSUIPC6 or FSUIPC7. If you see a reference to this folder, just use your FSUIPC7 installation folder (if you don't know where that is, you can use the File -> Open Installation Folder... menu option). No, you just need a lua script on the client computer. The lua should be auto-started from the [Auto] section of the FSUIPC7.ini on the client computer. In the script, you can start P2ATC using the ext.run library function. Then have an event waiting for a key (ir keys) press/release using event.key function. In the handling function, you can then send the key press/release to the P2A application using the ext.sendkeys function. However, there is no way to send a separate press and release using ext.sendkeys. If P2A uses press for PTT on and release for PTT off, this won't work as this would turn PTT on momentarily and then off, but try this first. If a separate press and release is needed, then you would need to use the ext.postmessage function, which is more complicated. If PTT is just toggled by a key press/release combination (or you can assign PTT on with one key press and off with another), you should be fine. I can look into this in more detail if you have issues, maybe later today or most probably tomorrow. John

@ON4KN I understand that setting up lvars to access via offsets can be quite confusing, especially for non-native English speakers. The latest version of FSUIPC (v7.3.1) supports the use of MobiFlight presets which should be easier to use. Check the MobiFlight hub-hob resource (https://hubhop.mobiflight.com/) for the aircraft you are using and search for a preset for the function you want to implement. So, for example, for the A320 BAT1 I see this preset: A32NX_OH_ELEC_BAT1_TOG. That will be listed under the controls menu as 'Preset: A32NX Oh Elec Ba1 Tog' (providing you have the WASM installed and enabled, and have also installed the MF preset file, called events.txt). You can assign your button directly to that preset. John

Yes, in the calibration tab. If you assign an axis with 'Send direct to FSUIPC Calibration' then you must also calibrate the axis. Here you set the axis min/max ranges, any null zones (if applicable) and can also reverse. John

Ok. I suspect that its too much logging not giving other threads time to react, or maybe a threading issue when multiple threads are logging and one (the lua thread) is hogging the log - I have noticed strange behavior on other occasions when logging is being thrashed. I'll take a look when I get time (as I've been meaning to try the RAAS script anyway), but I'm not sure if I can do anything, except maybe throttle the logging.... I can also add a note to the documentation to the effect that if you are logging lua plugins and this logs fast and/or produces a large log, then you should also enable Log Lua Separately. John

Ok. I will check this at some point, but it will be low priority. Maybe check, otherwise the user's issue is somewhere else....

But I thought it was working for you, but wasn't working for another user who didn't have Lua Plugins log option activated, so how can this be the issue? Maybe something is overflowing, I don't know. Maybe continual logging is having an affect - I have noticed this in MSFS with other logging on occasion. I can take a look at some point but not for the next few days (re-organising my office at the moment...). But how can it be if the user had an issue before he activated lua plugin logging? Or are you saying that he already had Lua Plugin logging activated, and it works for him when this is disabled? if thats the case, then there probably isn't an issue - just get him to disable the lua plugun logging!

No idea, sorry. That error is from P2A and looks like it cannot detect FSUIPC. I suggest you try P2A support for this. John

Then how is this working - how have you configured this? Are you using an offset or an (axis) event/control? You say this worked fine with a different TQ. Was the offset changing with that throttle? I think you need help with this from either ProSim or MobiFlight. As I don't use either, I cannot advise on how to set this up. John

To send the key press to P2ATC, you would have to use the lua function ext.sendkeys, and either start P2ATC via the lua EXT library ot use ext.gethandle to get the P2ATC window handle. John

Yes, FSUIPC7 on the client machine receives the key presses from the FS machine. However, P2ATC will not see that key press, only FSUIPC.

You cannot use KeySend - that is for WideFS. What makes you think that would work? Using FSUIPC7 on a client PC is not the same as using WideClient/WideFS. So 'shift + A' works from the client PC. Does this also now work from the MSFS PC? FSUIPC7 on the client PC should receive the key presses from the FS machine via SimConnect, although I haven't verified this (I can check later). John

The easiest way is to assign one event to button press and the other to button release. However, the general mechanism to assign multiple actions to a button press is by editing the FSUIPC7.ini file. You do this as follows: - assign your button to the first control and press 'OK' to save the assignment. Then, open the button assignment panel again. - open your FSUIPC7.ini file in an editor (e.g. Notepad++). Find the assignment line you just added and comment it out. You do this by inserting a ';' after the '=' sign for that assignment. Save the file. - in the button assignment dialog, reload your button assignments. After doing this, you can then assign the second action to your button. - You can repeat this a smany times as you like, to add multiple assignments to the same button - Once you have all your assignments, open the button assignment panel again, go back to the editor and remove the ';' you previously added to re-activate these assignments and save. - Finally, reload your assignments from the button assignment panel. You will now have multiple assignments to that button. Note that you will only see one assignment in the UI panel, and this will be grayed-out and not modifiable. You have to edit the ini manually if you want to change or remove these assignments. Yes, many times, e,g, Also explained in the Advanced User guide, although it is not that clear from the description there. I will add a new section with clear instructions for this in the next update (not that many people actually consult the documentation....!) John

Why are you cross-posting in a different topic when you raised your issues in this new topic: ? The letter should be the same, as this is what the assignments use. The ids that map to the letter may have changed - this is the whole point of using JoyLetters, so the letter maps to the correct joy id number. If the GUIDs have changed, you need to update your original letter mapping to use the new GUIDs. However, if that was the log/ini files you posted (in the other topic) from both PCs, it looks like the GUIDs haven't changed. This surprises me, as they should change on a new PC. Naybe you didm'y show me the correct files in that topic? I am closing this topic now. Please use the other topic, and do not post in multiple topics for the same issue. John

Sorry, I have no idea - I do not use ProSim or Arduino. What happens when you manually activate the spoilers - does this work? If so, how is that assigned? And does that change the values in offset 0x0BD0?

So you are using ProSim....you could have mentioned this earlier, and it is always a good idea to include ProSim in the title as this may attract other ProSim users that can help. To me it looks like FSUIPC is working as expected, although I cannot confirm as you have still not activated button and event logging, which would tell you if FSUIPC is sending the assigned events. So I suspect your issue is with your ProSim configuration. As you are using both an unsupported version of FSUIPC and ProSim, I really can't help you with this any further, sorry. John

Get the user to set logging for Lua Plugins and take a look at his log. I don't see how this can occur, or what would be causing it if this was the reason. The logging should tell. John

Look similar. Do you see the assignments to the buttons in the button assignment panel (profile specific) when you press a button there? If so, try logging button presses and events, and see what is logged when you press an assigned button (you can also attach here).

Just run the sim... Log file looks ok, although I am not familiar with FSUIPC3/FS2004. There is no logging of your devices, but maybe that wasn't implemented in FSUIPC3... What exactly is your issue? You say that your switches don't work? The aircraft that you loaded (B737-800 Ryanair - Winglets) should be covered by your Boing 737 profile. Do you see the assignments to the buttons in the button assignment panel (profile specific)? Also try logging button presses and events, and see what is logged when you press an assigned button (and attach here). Maybe the log from the old PC would help me, as there' seems to be a lot missing from the new one you attached, but that maybe because the additional logging was added later (and I am not familiar with FSUIPC3). Also, please remember that FSUIPC3 is no longer supported (and hasn't been for several years now), although I will try to help you... John

That looks ok....your devices seem to have the same GUIDs. Have you ran FSUIPC? What exactly isn't working? Also show me your FSUIPC.log file....

Ok, then show me/attach the ini file from your new PC...

I know about MobiFlight but do not use it. If your problem is with MobiFlight, have you tried their support? Your image also only shows offset 0x0BCC, the spoiler arm flag. But this is working, as far as I can tell, i.e. the spoilers are activated when you land. Your issue seems to be that this is not reflected in the movement of your lever, if I am understanding you correctly, so is with offset 0x0BD0 and not 0x0BCC. What vales? In offset 0x0BD0? If that isn't changing, then that will be your issue...maybe ProSim isn't using the SPOILERS HANDLE POSITION simvar, which is what that offset holds. If that is changing, then the issue will be with whatever software you are using to use that value to drive the motorized spoiler lever. If it isn't changing, you need to ask ProSim what drives the spoilers handle and use that instead.

But which airplane? You don't say.... Aircraft in MSFS can be quite different to those in P3D as far as controls/simvars/lvars/ etc are concerned. You need to fins out what works for the aircraft you are using, which you don't say so its difficult to advise. You can always try activating logging and see what controls are logged when you reverse in the UI - this should tell you what controls the aircraft is using. Note also that several new reverser controls were added in the latest MSFS SDK update and were added in the latest FSUIPC release (which is 7.3.1) - if not using that, please update. The new reverser controls added are: TOGGLE_THROTTLE1_REVERSE_THRUST TOGGLE_THROTTLE2_REVERSE_THRUST TOGGLE_THROTTLE3_REVERSE_THRUST TOGGLE_THROTTLE4_REVERSE_THRUST SET_THROTTLE1_REVERSE_THRUST_ON SET_THROTTLE2_REVERSE_THRUST_ON SET_THROTTLE3_REVERSE_THRUST_ON SET_THROTTLE4_REVERSE_THRUST_ON SET_THROTTLE1_REVERSE_THRUST_OFF SET_THROTTLE2_REVERSE_THRUST_OFF SET_THROTTLE3_REVERSE_THRUST_OFF SET_THROTTLE4_REVERSE_THRUST_OFF THROTTLE1_REVERSE_THRUST_HOLD THROTTLE2_REVERSE_THRUST_HOLD THROTTLE3_REVERSE_THRUST_HOLD THROTTLE4_REVERSE_THRUST_HOLD John

Changed what? The AutoAssignLetters ini parameter? If you are using the JoyLetters facility (which is the first step), then you still need to make some manual changes to the FSUIPC.ini on the new machine as your GUIDs will have changed. If you are using JoyLetters, attach the ini from your new PC and I can see what changes are needed. Of nor, go back to the old PC and enable JoyLetters dirst, then copy that to your new PC, run FSUIPC once then exit, then show me the ini file. John

Again, have you tried monitoring offset 0x0BD0 to check that the values in that offset are changing? If they are, then the problem must be in sending those values to the TQ. Not sure why you are attaching pictures of the spoiler arm offset...this is working, no? i.e. the spoilers are armed and activate on touch-down. It is just the spoiler movement that is not being reflected on your spoiler lever. Presumably that is driven by offset 0x0BD0, no? So why don't you try monitoring that offset to see if the values change when you touch down?

What airplane? So the spoilers are working as expected, and it is just that your spoiler lever doesn't move? Tried what? Did you log the values of off set 0x0BD0, and if so do they reflect the correct spoiler position? Or are you saying the values in that offset don't reflect the correct spoiler position? 0x0366 is the on-ground flag... So what is the difference now - a different aircraft?