Programming Unknown Commands

[gcortes]

I have the PMDG 747-400X and the full version of FSUIPC4 (4.53). I found the events are mostly different for this plane. Most of them are ROTOR_BRAKE with different parameters, which I can program. Some of them are listed as in the log. The have varying Cntrl numbers, for example 72123 for the left auto-pilot. How would I program it to a button?

Thanks for any help,

Curt

[mtjoeng]

search poster guenseli examples:

Lvars LUA:

ipc.writeLvar("L:pmdg_hide_yoke", 0)

ipc.writeLvar("L:pmdg_hide_yoke", 1)

ipc.writeLvar("L:HIDE_OVERHEAD_SWITCHES_var", 1)

or

button example '66587' = ROTORBRAKE , PMDG ND Map Mode selector for dial button:

110=117,26,x510066C0,x00040001 ;ND Mode increase start 117,26 Ctrl+Tab+F6

111=B66C0=0 117,26,66587,71132

112=B66C0=1 117,26,66587,71133

113=B66C0=2 117,26,66587,71134

114=B66C0=3 117,26,66587,71135

115=B66C0=4 117,26,66587,71136 ;ND Mode increase end

116=115,26,x610066C0,x00040001 ;ND Mode decrease start 115,26 Ctrl+Tab+F4

117=B66C0=0 115,26,66587,71132

118=B66C0=1 115,26,66587,71133

119=B66C0=2 115,26,66587,71134

120=B66C0=3 115,26,66587,71135

121=B66C0=4 115,26,66587,71136 ;ND Mode decrease end

for a regular button this would be:

110=117,26,66587,71132 (button,button,rotorbrake,one-of-the-parameters)

mt

[guenseli]

@mt:

These commands are not valid for the 747!!!

They are valid for the MD11!

..just to make this clear.

@curt:

have you had a look into this tutorial:

http://forums.simflight.com/viewtopic.php?f=54&t=78335

should answer your questions...

[mtjoeng]

not valid for the 747

well, the example is MD11

but Ive the 747 here and the debug console give the same kind of stream for the pmdg 747

and either Events or Button logging givs Lvars or Offsets&parameter when pressing something in VC

mt

[mtjoeng]

double

[gcortes]

@mt:

@curt:

have you had a look into this tutorial:

http://www.forums.simflight.com/viewtopic.php?f=54&t=78335&sid=f635cd4c97791fb83d72e172a1f2a56e

should answer your questions...

The link didn't work for me.

[guenseli]

sorry, link updated

here again, too:

http://forums.simflight.com/viewtopic.php?f=54&t=78335

[gcortes]

sorry, link updated

here again, too:

http://forums.simflight.com/viewtopic.php?f=54&t=78335

Thanks for the good link. Interesting information, but I don't thinks that's my problem. I did a little digging and found the advanced manual and the ini file. So I think I had it. Not quite

When I press the left auto pilot button using the mouse, I get this entry in the log:

811844 *** EVENT: Cntrl= 72123 (0x000119bb), Param= 0 (0x00000000)

The file contained a section for my 747. I added the last line. The complete section is this:

[buttons.PMDG747-400 UNITED AIRLINES]

0=P0,6,C66587,72120

1=P0,8,C66587,72119

2=P0,13,C66587,72111

3=P0,11,C66587,72112

4=P0,10,C66587,72105

5=P0,12,C66587,72104

6=P0,2,C72123,0

I saved and closed the ini file, restarted FSX, and got this in the log.

The log showed:

32313 Aircraft="PMDG747-400 UNITED AIRLINES"

32313 [buttons] now aircraft-specific:

32313 1=P0,8,C66587,72119

32313 2=P0,13,C66587,72111

32313 3=P0,11,C66587,72112

32313 4=P0,10,C66587,72105

32313 5=P0,12,C66587,72104

32313 [buttons] now aircraft-specific:

32313 0=P0,6,C66587,72120

32313 1=P0,8,C66587,72119

32313 2=P0,13,C66587,72111

32313 3=P0,11,C66587,72112

32313 4=P0,10,C66587,72105

32313 5=P0,12,C66587,72104

It's not reading my entry or doesn't like it. Is there a parameter that I have to increase to say there are seven entries? I've also turned off the programming of the button by FSX itself.

A unrelated bug I got while trying to figure this out was that if I left the 'Send to console window' option checked when I exited FSX, the main window wouldn't display when I selected the saved flight and clicked 'Fly Now'. If I clicked alt-enter to go to full-screen, it would appear on the second monitor. I could then move the display back to the primary monitor, but the window for the CDU no longer functioned. Turning off the 'Send to console window' option, exiting, and reentering FSX fixes the problem. I suspect this is a PMDG problem, but I wanted to ask here as I figured fellow PMDG uses may have come across it. I'm running Windows 7 64 bit with FSX Deluxe, SP1, and SP2 installed.

[gcortes]

Update: I tried replacing the first command. The log then looked like this:

35406 Aircraft="PMDG747-400 UNITED AIRLINES"

35421 [buttons] now aircraft-specific:

35421 1=P0,8,C66587,72119

35421 2=P0,13,C66587,72111

35421 3=P0,11,C66587,72112

35421 4=P0,10,C66587,72105

35421 5=P0,12,C66587,72104

35421 [buttons] now aircraft-specific:

35421 0=P0,6,C72123,0

35421 1=P0,8,C66587,72119

35421 2=P0,13,C66587,72111

35421 3=P0,11,C66587,72112

35421 4=P0,10,C66587,72105

35421 5=P0,12,C66587,72104

So it processed it, but it still didn't work.

[mtjoeng]

in the log:

811844 *** EVENT: Cntrl= 72123 (0x000119bb), Param= 0 (0x00000000)

perhaps when it's it wont work ('unknown' isnt in the commands drop-down, is it, so it isnt a command)

for a L CMD of the PMDG747, you can use a MouseMacro, though, thats what I do

all 747 2Dpanel buttons work with mouse macro's (not the FMC unfortunately)

mt

[Pete Dowson]

in the log:

811844 *** EVENT: Cntrl= 72123 (0x000119bb), Param= 0 (0x00000000)

perhaps when it's it wont work ('unknown' isnt in the commands drop-down, is it, so it isnt a command)

Correct -- it isn't a known FS command. But it is a way for add-on writers to create new commands -- just use numbers Microsoft have not assigned, as in this case.

Unfortunately, FSUIPC's assignment system doesn't allow assignment to unlisted and unknown / unnamed commands. But perhaps there are two possible ways around this:

1. Assign to "Offset dword set", with offset x3110 and with the parameter set to the command number (72123 or x119bb in this case). This should work with any added commands not needing a parameter value.

or

2. Write a small Lua plug-in which sends the Command number and Parameters via the "ipc.control" library function.

Regards

Pete

[gcortes]

1. Assign to "Offset dword set", with offset x3110 and with the parameter set to the command number (72123 or x119bb in this case). This should work with any added commands not needing a parameter value.

Thanks Pete for the suggestion. You lost me with "Offset dword set". I can't find a mention of it. You can just refer me to the appropriate user guide page.

Curt

[mtjoeng]

"Offset dword set". I can't find a mention of it.

"Offset dword set" is in the fsuipc Dropdown menu in Buttons: 'Select for FX control', or in Key presses the 'Control sent ..' beneath the button 'Set'

the command menu's are alphabetical, so just hit 'o'(ffset) and that'll get you there

mt

[gcortes]

"Offset dword set". I can't find a mention of it.

"Offset dword set" is in the fsuipc Dropdown menu in Buttons: 'Select for FX control', or in Key presses the 'Control sent ..' beneath the button 'Set'

the command menu's are alphabetical, so just hit 'o'(ffset) and that'll get you there

mt

Thanks, I was just going to post about something I found in the manual that may be the same thing.

I tried programming a differt function that I would be sure to see the effect. Here are the log entries:

1664672 *** EVENT: Cntrl= 72025 (0x00011959), Param= 0 (0x00000000)

1667265 Button changed: bRef=0, Joy=0, Btn=2, Pressed

1667265 [buttons.PMDG747-400 UNITED AIRLINES] 6=P0,2,Cx03003110,x00011959

1667265 IPC Offsets Control: Ctrl=x0300, Length=4, Offset=3110, Param=x11959

1667406 Button changed: bRef=0, Joy=0, Btn=2, Released

The first line is me clicking a control on the screen. The rest is the programmed joystick button. Unfortunately, it doesn't work.

Curt

[mtjoeng]

1664672 *** EVENT: Cntrl= 72025 (0x00011959), Param= 0 (0x00000000)

thats the POS button of the EFIS-ND I'd say

perhaps like the CDU-buttons of the MD11, they just cannot be triggered - bad PMDG

mt

[Pete Dowson]

The first line is me clicking a control on the screen. The rest is the programmed joystick button. Unfortunately, it doesn't work.

Ah, my error, sorry. For true FSX events I use SimConnect to action it. I forgot that SimConnect only accepts events it recognises (or user ones pre-registered), so this strange "unknown" one never gets through.

I have modified FSUIPC4 to send events not registered with SimConnect directly to FS, bypassing that filter. Try this version:

http://fsuipc.simflight.com/beta/FSUIPC4556.zip

Regards

Pete

[gcortes]

1664672 *** EVENT: Cntrl= 72025 (0x00011959), Param= 0 (0x00000000)

thats the POS button of the EFIS-ND I'd say

perhaps like the CDU-buttons of the MD11, they just cannot be triggered - bad PMDG

mt

It may be a PMDG problem. It has a feature to assign functions to keyboard keys. I can't get that to work either.

[gcortes]

The first line is me clicking a control on the screen. The rest is the programmed joystick button. Unfortunately, it doesn't work.

Ah, my error, sorry. For true FSX events I use SimConnect to action it. I forgot that SimConnect only accepts events it recognises (or user ones pre-registered), so this strange "unknown" one never gets through.

I have modified FSUIPC4 to send events not registered with SimConnect directly to FS, bypassing that filter. Try this version:

http://fsuipc.simflight.com/beta/FSUIPC4556.zip

Regards

Pete

Pete,

That did the trick. Thanks for the quick fix.

Curt Rowe