FSUIPC7, msfs2020 and pmdg 737 newbie question

[Rob_R]

Hi

BLUF: I can't get fsuipc7 to work in pmdg 737.

So I have build a homecockpit using old controllers and desktop aviator circuit boards. The problem I am having is that Fsuipc7 recognizes all the buttons and switches but when I assign a preset from the list, it will not actuate the assigned switch.

For instance, I assigned the battery on/off preset from the drop down menu for buttons and switches using the preset pmdg 737 list. Fsuipc sees the switch and assigns  it the correct controller ID. Yet nothing happens in the cockpit.

 

I know fsuipc7 works cuz when I do the same for the CJ4, the batt switch does work when I assign it thru fsuipc7.

I read that I need to assign it using custom events. But I cannot find the pmdg 737 sdk.h file anywhere or the .ini file. I did enable the folder views to show hidden files.

I have the pmdg installed in its default folder.

Fsuipc7 is installed at C:\fsuipc

Wasm is enabled.

What am I doing wrong? 

 

[John Dowson]

3 minutes ago, Rob_R said:

I read that I need to assign it using custom events. But I cannot find the pmdg 737 sdk.h file anywhere or the .ini file. I did enable the folder views to show hidden files.

The presets use calculator code, and much of the calculator code uses the custom events, as well as lvars. The custom events/controls for the PMSG 737 in MSFS use the Rotor Brake control, with the parameter indicating the actual control/event. You can see the parameters used by looking at the calculator code for the presets (in the events.txt file, or, better, on the MF HubHob site https://hubhop.mobiflight.com/presets/). PMDG have not published the SDK yet - this should come in the next update, due any day now.

11 minutes ago, Rob_R said:

What am I doing wrong? 

I don't know. You need to work out if its not configured properly (i.e. the preset calculator code is not being sent to the FS) or if it is the preset/calculator code that isn't working correctly. For the former, I need to see your FSUIPC7.ini and FSUIPC7.log files, the latter with Event and Extras logging activated, and with Debug logging enabled in the WAPI (add the line LogLevel=Debug to the [WAPI] section of your FSUIPC7.ini file). If its the latter, you need to ask about this on the MF Discord server.

Note also that there is an FSUIPC7 beta out with the additional offsets for the PMDG 737 populated (for read-only). See 

John

 

[Rob_R]

Thanks! I'll do what you suggested and post the logs.

[Rob_R]

So I feel stupid here but your "rotor brake" comment finally clicked this morning. 

Layman's term procedure...in button and switches, select the rotor brake option in the dropdown list. Have the log window open and see what it logs when you click on the switch you want to manipulate in the cockpit. The log will show you the name of the switch (I.e. yaw damper) and it will show a 6 digit number such as 26502.  That's the number you put in the "parameter" box underneath the drop down list. 

And that is it. 

Again, it was all there in your explanation. It just took a while for me to grasp it. 🤦‍♂️

[John Dowson]

Logging is one way to determine the parameter, otherwise you can use the SDK header file. This has not been published yet, but you can use the P3D737 header file if you have that. The SDK for the MSFS PMDG 737 should be published in the next update. There is a guide in the FAQ section on how yo calculate the Rotor Brake parameter codes:

John