Search the Community

Hi, Can't find any topic about my problem so i created this one. I bought FSUIPC7 to use it with MSFS 2020 and PMDG 737. I own Opencockpit MCP and EFIS, drived by new Oi4FS PMGD driver. When i use only Oi4FS, the response of MCP/EFIS buttons / switches is almost immediate. When i Start FSUIPC7 to control landing lights, cutoff levers, etc, the response of OC devices is more than 2/3 seconds... just unusable (each button step takes 2 seconds....) Is there any setting to activate or is it a bug between MSFS/PMDG/SimConnect/FSUiPC/OI4FS chain ? Thanks for your help, Pascal, Nantes, France

NOTE: This guide references an out-dated method for controlling the PMDG aircraft in MSFS. While it might still work, a better method is explained in this linked FAQ: Background PMDG Aircraft for MSFS do not use the normal controls provided by the flight sim. This means that many of the aircraft's switches cannot be assigned to buttons and keys using the list of controls in the FSUIPC dropdown boxes. Assigning a standard control in FSUIPC will likely do nothing in the PMDG aircraft when the button or key is pressed. Solution Instead of using the standard list of controls shown in the FSUIPC dropdown box, users must send codes as a parameter to the standard MSFS 'Rotor Brake' control. The parameter code specifies which switch to operate and what type of mouse click to simulate. The control numbers vary for each aircraft and are listed in the SDK that is installed alongside the aircraft. This guide will show you, step-by-step: How to find the SDK files How to calculate the 'Rotor Brake' parameter codes How to assign the code to buttons/keys in FSUIPC The specific examples shown will be taken from the PMDG 737-700, but the same method works for any PMDG aircraft with an SDK. 1. Locating the SDK From your main Flight Sim install folder, open the PMDG folder. Then select the folder belonging to the aircraft you want to use. e.g. PMDG 737 NGXu Then select the SDK folder Locate the file with the .h extension. For the 737 it's called PMDG_NG3_SDK.h You can open this file with Notepad or your favourite text editor. As an example, the document you need for the 737 will be: [FlightSimInstallFolder]\PMDG\PMDG 737 NGXu\SDK\PMDG_NG3_SDK.h 2. Calculating the 'Rotor Brake' Parameter Code 2.1. Find the control you want to use. Search for the control by name, or look through the listed controls to find the one you want. They are helpfully grouped together by panel. The controls are listed under a comment: // Control Events You can search for this to find where the list of control numbers starts. As an example we'll use the "Autopilot CMD A" switch on the MCP. This is the relevant line in the 737 SDK: #define EVT_MCP_CMD_A_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 402) To calculate the control number for this switch we ignore THIRD_PARTY_EVENT_ID_MIN and take the number after it. In this case 402. NOTE: Some controls reference other controls. For example: #define EVT_EFB_L_BACK (EVT_EFB_L_START + 1) For this you need to find the value of EVT_EFB_L_START and add 1. Searching for EVT_EFB_L_START we find this: #define EVT_EFB_L_START (THIRD_PARTY_EVENT_ID_MIN + 1700) As before, THIRD_PARTY_EVENT_ID_MIN is always ignored. So we get the value of 1700. Adding 1 to this will give us the value for EVT_EFB_L_BACK. Therefore EVT_EFB_L_BACK would be 1700 + 1 = 1701. We have now calculated the control number. 2.2. Adding the Mouse Action Code You now need to add a number to tell the aircraft what kind of mouse interaction you want to simulate. (e.g. left click, right click, scroll wheel up). First multiply the control number you have so far by 100. In our example for EVT_MCP_CMD_A_SWITCH we get: 402 * 100 = 40200 Now you ADD the following number, depending on the mouse operation you want: 1 for left mouse click 2 for right mouse click 3 for mouse move 4 for left mouse button release 5 for right mouse button release 6 for middle mouse button click 7 for mouse wheel up 8 for mouse wheel down For our example, we'll have our key assignment simulate the left mouse button clicking on the CMD A autopilot button. So we'll need to add 1: 40200 + 1 = 40201 Now we have the final code number. 3. Assigning the control to a button or key in FSUIPC Select [Assignments] -> [buttons + switches] or [key presses] in the FSUIPC7 menu. Then select the button or key to program. From the "control sent..." dropdown select Rotor Brake In the Parameter field below type in your calculated code number from the previous step. For our 'Autopilot CMD A' example, we enter 40201 If you're programming a key press, remember to press the [confirm] button. Here is our example control assigned to a button in FSUIPC: Your button or key press should now operate the switch in your PMDG aircraft.

Hello, before writing to you I did several searches on the subject but I can't manage to make what I'm looking for work. I recently saw your documentation on FSUIPC offsets for the PMDG737. However I don't understand where I have to insert the OFFSET command to make the switch work. I tried in FSUIPC the Offset Byte Set, on the other hand with the Rotor Brake method it actually works, but I don't have all the commands that you published on Hubhop. When I listen to the value in Byte, I have the info in the FS title bar, but no action is happening in the cockpit of the PMDG 737. Thank you for your answer.

Background PMDG Aircraft for FSX and P3D do not typically use the normal controls provided by the flight sim. This means that many of the aircraft's switches cannot be assigned to buttons and keys using the list of controls in the FSUIPC dropdown boxes. Assigning a standard control in FSUIPC will likely do nothing in the PMDG aircraft when the button or key is pressed. Solution Instead of using the standard list of controls shown in the FSUIPC dropdown box, users must use a different set of controls provided by PMDG for the specific aircraft. These are known as custom controls (or custom events). The custom controls vary for each aircraft and are listed in the SDK that is installed alongside the aircraft. This guide will show you, step-by-step: How to find the SDK files How to calculate the custom control numbers How to work out the parameter value How to assign the control to buttons/keys in FSUIPC The specific examples shown will be taken from the PMDG 737NGX, but the same method works for any PMDG aircraft with an SDK and custom controls (e.g. 777, 747). 1. Locating the SDK From your main Flight Sim install folder, or your MSFS Community folder, and open the PMDG aircraft folder Then select the folder belonging to the aircraft you want to use. e.g. PMDG 737 NG3 or pmdg-aircraft-737 Then select the SDK folder or Documentation\SDK folder for MSFS2020 Locate the file with the .h extension. For the 737 it's called PMDG_NG3_SDK.h (or maybe PMDG_NGX_SDK.h, depending on the sim and variant you are using) You can open this file with Notepad or your favourite text editor. As an example, the document you need for the 737 in MSFS2020 will be: [Community]\pmdg-aircraft-737\Documentation\SDK\PMDG_NG3_SDK.h 2. Calculating the control numbers 2.1. Find THIRD_PARTY_EVENT_ID_MIN The first thing to find is the definition of THIRD_PARTY_EVENT_ID_MIN. Search for the following text: #define THIRD_PARTY_EVENT_ID_MIN You will find a line like this (from the 737 file): #define THIRD_PARTY_EVENT_ID_MIN 0x00011000 // equals to 69632 Note the decimal value at the end. In the case above it's 69632. You will need this value to calculate the control number in the next step. 2.2. Find the control you want to use. Search for the control by name, or look through the listed controls to find the one you want. They are helpfully grouped together by panel. The controls are listed under a comment: // Control Events You can search for this to find where the list of control numbers starts. As an example we'll use the Autopilot CMD A swtich on the MCP. This is the relevant line in the 737 SDK: #define EVT_MCP_CMD_A_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 402) To calculate the control number for this switch we just add 402 to the value of THIRD_PARTY_EVENT_ID_MIN we found earlier. 69632 + 402 = 70034 We have now calculated the control number. We will use this in step 4 to program the button/key. 3. Finding the parameter value PMDG controls need a parameter value. These can one of type types: 3.1. Mouse Click Codes (Shown in the example) You can use these to simulate a mouse click on the particular switch. Mainly it will be the left mouse button, but other clicks types are available (e.g. Right button, left double click etc). To find the codes for each type of click, search for MOUSE_FLAG You'll find a block of #define statements for each type of mouse click. Here are a couple of examples from the 737 sdk: #define MOUSE_FLAG_RIGHTSINGLE 0x80000000 #define MOUSE_FLAG_LEFTSINGLE 0x20000000 Find the click that you want to simulate and get the code. For example, we'll have our key assignment simulate the left mouse button clicking on the CMD A autopilot button. So we'll need 0x20000000 as the parameter value for the control. 3.2. Direct Values (Not shown in the example) Alternatively, some controls can accept a direct value to set the switch to a specific position. To find the direct values you need to look at the top part of the .h file to find the switch definition. These are named differently than the events so you need to search. Taking the battery selector switch as an example, we find the control: #define EVT_OH_ELEC_BATTERY_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 1) For the parameter value we can find the same switch in the top part of the .h file: unsigned char ELEC_BatSelector; // 0: OFF 1: BAT 2: ON This tells us that in addition to mouse clicks, we can also send direct values. In this case: 0 for the OFF position, 1 for the BAT position and 2 for the ON position. It's possible to make a key or button set the Battery Selector directly to the ON position by setting the parameter value to 2 instead of a mouse click code. Simple ON/OFF switches will not have values listed (and will be declared as 'bool'). For these types of switches you can just pass the value 0 for OFF and 1 for ON. 4. Assigning the control to a button or key in FSUIPC Select the [buttons + swtiches] or [key presses] tab in FSUIPC and select the button or key to program. From the "control sent..." dropdown select <custom control> (it's near the top of the list) A popup window appears asking for the control number. Type in the control number you calculated in step 2. For our 'autopilot CMD A' example, we enter 70034 and click OK. The controls dropdown box will now show the control number in angled brackets. In the "parameter" box (below the controls dropdown), enter the parameter value from step 3. This can be a mouse click code or a direct value. Mouse Click Codes: Do not include the first 0 from the number listed in the PMDG SDK. Start with the x. With our example, we would enter x20000000 for the left-button single-click. Note that this code is in hexadecimal. FSUIPC will convert it to the equivalent decimal value. This is nothing to worry about. It's the same number. Entering the value in Hex is more convenient. Direct Values: Just enter the value as a number. Do not add the x at the start like mouse codes. If you're programming a key press, remember to press the [confirm] button. Here is our example control assigned to a button in FSUIPC: Your button or key press should now operate the switch in your PMDG aircraft.

Hello All, I am trying to read data form my sim to improve my home built TQ and ran into some problems reading data from FSUIPC. here is my setup. FSUIPC 5.153 ( I plan to upgrade to FSUIPC 6 soon) P3D 4.3.29.25520 with PMDG 777 Aircraft SimConnect 4.3.0.0 I am trying to identify the correct offsets specially in AP mode. See below output from FSInterrogate2std.exe program. I can see the value from the joystick input(3330, 3332) and I can also see the values from the throttle lever(088C, 0924). However I am not able to see any of the other values, with AP On or Off they don't update at all. What am I doing wrong? I have the PMDG aircraft .ini file set to broadcast=1 as well. My goal is to send this data to a Com port via a LUA script and before go down this path, I want to make sure I am pinging the correct offsets. I am not a expert programmer, so trying to do simple things to get this working. Thank You for any help you can offer. Anthony

Hi, I searched the forum before I post and I saw that someone tried to communicate the Lua script and Arduino. We're sharing the same purposes. Let me say the problem I deal: For PMDG 737, I can control any button, switch in the simulation by sending data from Arduino to Lua script. Also, I have no problem to send data from Lua script to Arduino by using Lvar list in FSUIPC documents. However, I can't read the state of any warning light as Overheat Lights in the overhead panel. Only need to know, what should be the way of reading the state of lights in PMDG 737. If there is a small example or showing a way to go, I will be grateful 🙂

Hello I have the latest version of FSUIPC installed (5.15). My sim has Opencockpits 737 rudder pedals. everything has been working fine up to a few days ago when I discovered the toe brakes were no longer working. I first checked that the wiring was all right (it is) and I performed a new calibration thinking that would solve the problem, but it hasn't The calibration is correct but for some reason the toe brakes are inoperable in the sim. I've checked everything, and even ran P3Dv4 repair, and PMDG repair from the installation packages, but although FSUIPC shows that the physical Opencockpits pedals are properly connected and functioning, the toe brakes on the pedals do not seem to be connecting to the sim. The rudder works, but not the toe brakes. It there any reason you can think of why the toe brakes should have stopped working in the sim? I push the toe brakes and absolutely nothing happens. I also checked to see if there was a fault in the PMDG failure settings, but that it clear. I have a suspicion that it is something very simple that my thick brain is overlooking, so could you put me out of my misery, please? Many thanks Father Dane

Hello, First, as I have written in the title, I own the X52Pro. My main question is to ask, if it is possible to move the slider on the throttle to move the speedbrakes, escpecially in the B738 or B772 from PMDG? In FSUIPC5 the axis is known as axis S. I'm too inexperienced of these tons of buttons to make them move the speedbrake lever, although hoping that it is possible? Does anybody have a clue? Any answer is appreciated. Regards, Ralf

Moved to Main Forum. Please ask questions related to FSUIPC always in Main Forum. Hello - I have the latest FSUIPC release (5.124) is this capable of macros at all? I know the earlier release isn't but I'm not clear about the latest version. And if not, I need a way to turn on the IRS switches in PMDG-NGX 737 (P3Dv4.2) - either by a push button or a physical switch ... any suggestions? Many thanks Father Dane

Hi I've got a WP6 module from GoFlight. I'd like to use it to simulate some warnings and push buttons in PMDG 737NGX, like for example FIRE WARN, MASTER CAUTION or FMC P/RST. Any idea about how I could start it? Thanks! José

Hi, I tried to use the logging feature of FSUIPC5 to show the elevator trim value (i.e. the same one that is shown when you move the trim wheel) without success. Any clue/advise would be really appreciate. I am using Prepar3D v4.1. Thanks in advance for your help. Best regards, Jose

Moved to Main Forum, where questions should be posted! Pleas post always to Main Forum. Evening all, I am a member of Delta Virtual Airlines (deltava.org) and we have been having issues with the latest FSUIPC 5.xxx in P3Dv4.1 and the PMDG 747 QOTSII in regards to the fuel quantities, when FSUIPC is reporting the fuel to our ACARS system (developed by Luke Kolin). Ever since updating to the latest FSUIPC in P3Dv4.1, FSUIPC either reports to ACARS that there is 0lbs fuel, +2,447,447,447lbs of fuel, or -2,447,447,447lbs of fuel. It also reports that in flight refueling is detected, although I am not sure how much of an issue that is with the ACARS system using what FSUIPC reports, or both, or FSUIPC. In any case, Luke Kolin told me that the only way this could be fixed would be to have Pete make a fix for it. I know he is away till the 2nd, tomorrow, so figured I would post it now.

PROBLEM SOLVED Hello, this is my first post.I had just installed P3Dv4 and PMDG 737NGX and I have some issues with the connection.It recognizes FSUIPC5 but no input or output! (FSUIPC version is 5.121a and says it is a BETA and needs no registration) I placed the .lua file in the modules folder but nothing. i suppose it has to do that FSX and P3Dv3 were 32bit and this 64bit? Is there a solution? Thanks for your attention!

Good morning/afternoon to all, I have just purchased a VRinsight Multi-Switch panel and would like to do the following: - Assign the R1/R2 rotary buttons to the PMDG777 panel lights in order to control the cockpit lighting from that panel - Assign S1/S sliders to the PMDG777 ENG1/ENG2 fuel cut-off buttons. When I get to the max of the slider, the ENG1 switch will flip to on. When I slide to the mininum, the ENG1 switch flips to off. Any way to create events based on an axis actual value? I know for key press but not for specific events like above. Thanks, Fred

Hey! I'm having a problem, I bought the PMDG 747 2 weeks ago. Only when I load this in the P3D V4, he spawns with black screens and his joystick fully to the left and without gear. If I remove FSUIPC then everything will work. Same with the IVAP client. IVAO Traffic I only see black aircraft but when I uninstall FSUIPC, everything works back. Does anyone know a solution? It is the latest version of FSUIPC. Sincerely Glenn Callens

Hi Fabio Just about to purchase, I'd be grateful if you could answer a quick query. I can't see included on the list of animations features for v3.5, reverse thrusters for PMDG. Will your software eventually include this animation also? Thanks Dave Nash

Hello, I recently purchased FSUIPC 4 for P3D. Previously, I used FSUIPC for FS2004 and created the macros to command keys in the most complex aircraft, such as the 737 PMDG, Digital Aviation Cheyenne, FSD Navajo, etc. In P3D, I can not create the macros! When clicking on create the mouse macros, and when the key is pressed with the mouse in P3D, nothing happens (before, it appeared a green stripe with the codes). How do I assign the buttons and keys with this new FSUIPC, for example, a simple light taxi key of the 737 NGX PMDG? I read the .h file from the PMDG SDK, it speaks of the commands, but no listed command is in the list of FSUIPC commands. Is there a file to replace which includes these commands? Thank you!

Hello everyone and good day. I´m still with compatibility problem between FSUIPC5 and 747 PMDG, even with the last build 8370, but I tested just with 5.102 and 103; I readed many users that may use it with some versions of FSUIPC 5.101x, so then, anyone could share me any of 101 please? Thank you!

Second issue report - I'm not seeing a value for a specific PMDG777 offset when using FSUIPC5. I check offset 0x6C1D to get the PMDG equipment type code as a sanity check to ensure that I'm getting proper PMDG data. In P3Dv3 using FSUIPC 4.967, the code is non-zero (4) and it correctly detects the -200LR. When using FSUIPC5 and the same aircraft in P3Dv4, the offset is zero. I've checked my 777X_Options.ini file and the EnableDataBroadcast=1 setting is set under the SDK section, so it should be available to FSUIPC. Is this functionality enabled in P3Dv4, and how can I help determine whether the data is is making it to FSUIPC? (FWIW, it looks like the alloc/free count doesn't match here either, but I'm not getting a P3D crash on shutdown like I do with v3). Cheers! Luke FSUIPC5.log

This is the first of two issue reports - I just upgraded the P3D to the latest P3Dv3/P3Dv4 version, and I'm getting a consistent crash in PMDG_777X_2.dll on shutdown. Ordinarily, I'd report straight to PMDG, but I'm seeing the following issue in the FSUIPC log at the end: 89638 === Closing session: waiting for DLLStop to be called ... 114973 === DLLStop called ... 114973 === Closing external processes we started ... 115971 === About to kill any Lua plug-ins still running ... 116127 === Closing global Lua thread 117125 === About to kill my timers ... 117328 === Restoring window procs ... 117328 === Unloading libraries ... 117328 === stopping other threads ... 117328 === ... Button scanning ... 117422 === ... Axis scanning ... 117531 === Releasing joystick devices ... 117531 === Freeing macro memory 117531 === Removing any offset overrides 117531 === Clearing any displays left 117531 === Calling SimConnect_Close ... 118124 === SimConnect_Close done! 118124 === AI slots deleted! 118124 === Freeing button memory ... 118124 === Closing my Windows ... 118124 === Freeing FS libraries ... 119122 === Closing devices ... 119122 === Closing the Log ... Bye Bye! ... 119122 System time = 10/06/2017 11:12:29, Simulator time = 11:11:21 (16:11Z) 119122 *** FSUIPC log file being closed Minimum frame rate was 24.3 fps, Maximum was 31.4 fps Minimum available memory recorded was 32768Mb Average frame rate for running time of 47 secs = 28.2 fps Average weather filter write interval in that time = 831.2 msecs Maximum AI traffic for session was 9 aircraft Memory managed: 71 Allocs, 70 Freed ********* FSUIPC Log file closed *********** Note right at the end, we're got a mismatch between malloc() and free() counts. Do you think think this may be the cause, or shall I file a ticket with PMDG? This is FSUIPC 4.967, on Windows 7 x64. FWIW, I see the same mismatch in P3Dv4 with FSUIPC5 and the PMDG 777. Cheers! Luke FSUIPC4.log

I'm using the x55 rhino and on prepar3d v4 with the PMDG 747 v3. I'm able to bind axes but not buttons or keys. I follow the process normally but it just doesn't have any effect in the aircraft. Throttles, rudder, ailerons and elevators all work perfect. Thanks for helping. (I have a registered version of fsuipcv5.101j)

Pete, I appreciate the integration work you've done with the PMDG 737, 747 and 777 aircraft. We can extract a lot of useful data from them via the custom offsets. I'm running into a few cases where the SDK integration is turned on in the Options.ini file but I'm not getting data from the PMDG SDK. I check the "aircraft model" offset that comes from PMDG since that should never be zero if the SDK is passing data correctly to FSUIPC, but it appears to be. I'm curious how the integration works on your end. Do you make the SimConnect calls no matter what and just copy over any data that comes over, or are you searching for specific AIR files or other triggers to pull the data? Cheers! Luke

I want to report a bug with FSUIPC version 4.962 on Prepar3D v3.4 + HF3 The traffic limiter option interferes with the external lights of the new PMDG 747 v3 How to reproduce: Make sure setting are set to display air traffic and the traffic limiter is set to off (i.e 0) Load up 747 sitting on a runway at any airport at night (I tested at EGLL) Turn on the landing lights Now open FSUIPC and set the traffic limit to a number instead of zero (I set it at 100) After clicking okay the landing-lights of the PMDG no longer illuminate the ground, even though the switch is 'on' ?? Toggle the switch several times eventually restores the external lights, but sometimes it never comes back on? I'm sure this is a FSUIPC bug and not a PMDG one, because disabling FSUIPC from the dll.xml file fixes the problem completely.... I noticed some people on the PMDG forum were complaining of poor external lighting on the 747, maybe this is linked? Thanks

Hi, I am using the paid version of FSUIPC. I am using FSX. I am using desktop aviator circuit boards. The PMDG NGX 737-800 has 4 settings for the left wiper i.e. Park, INT. Low, High. I am having trouble getting all four settings assigned using mouse macro? I can get three settings. I can get all but the Low setting? When I click the mouse there is a window to assign the function at the top left of the page. I assign it but it does not assign to that position? Any ideas? Is there a better way to program this? Second question - I am using mechanical rotary switches - What is better to use, break before you make or make before you break mechanical rotary switches? Thanks for any help? Lee

MOVED FROM FAQ ("frequently asked questions") SUBFORUM! Hello there Pete, I recently acquired FSUIPC4 (the payware version) and ever since that installation my PMDG aircraft (737 NGX, 777 LRX) are experiencing Autoflight issues. LNAV and VNAV, AT and LVL CHG are not responding to whatever is programmed into the FMC. The speed indication on the PFD roughly follows the speed entered into the speedwindow. When I then open up Addons in the FSX taskbar and subsequently open the FSUIPC interface and press: Normal defaults everything responds normally again. Now it is nice to know that there is a cure to my problem, but what causes it? I don't want to have to stop the flight every time I depart from an airport to open up FSUIPC to press Normal defaults. Simulator: FSX Gold SP2 FSUIPC version: 4.959 Cheers, Marc