I can program actions in the PMDG 738 FMC using AAO, but I can't find anything to use to program FS Actions

(the other main part of the CDU), such as Pushback, etc.  (I use AAO for EVERYTHING else, essentially.)

I don't see any sim events triggered when I push the buttons in FS Actions.  Is this 

something that's possible to do from AAO (in MSFS2020)?  Any pointers would be much appreciated!!

Thanks,

Erik Goodman (MooneyDrover)

2 minutes ago, MooneyDrover said:

something that's possible to do from AAO

Don't think so. Unless they trigger simulator events (from the MSDS SDK), these items are PMDGs own features, built (only) into their aircraft logic. To my best knowledge, not even the PMDG SDK has events for that (SDK doc is usually installed into the aircraft folder like so: Community\pmdg-aircraft-737\Documentation\SDK)

There are two work-arounds that I know of. A while ago I made a bridge program for the PMDG EFB tablet, and one can operate some of those feature from the outside with that (=you can click on the buttons on the EFB using joysticks or StreamDecks). The other option is to scripts that navigate throught the FMC menus for you by sending the appropriate FMC button events in sequence with the proper delays in between.

Thanks a lot for clarifying the situation.  I just downloaded the PMDG tablet bridge from your website, and am delighted to

find that it hass complete instructions and even an example in the readme1  Y  I'll let you

know how it comes out!  Thanks again,

Erik Goodman

Was just about to say, "You have made my day, and also my week!" when I accidentally hit "post" .  I am truly impressed with

the kind of support you provide for the AAO user community... l can't say enough!  I'm sure it will be a key contributor to the

future growth of the AAO community1

Erik Goodman

12 minutes ago, MooneyDrover said:

Thanks a lot for clarifying the situation.  I just downloaded the PMDG tablet bridge from your website, and am delighted to

find that it hass complete instructions and even an example in the readme1  Y  I'll let you

know how it comes out!  Thanks again,

Erik Goodman

To be honest, personally I prefer the "CDU automation" method. It just means stringing the right Menu/LSK commands together, leaving a small gap inbetween.

Example: Toggle the chocks via script:

1·(>K:#70183)·(WAIT:100)·1·(>K:#70176)·(WAIT:100)·1·(>K:#70172)·(WAIT:100)·1·(>K:#70177)·(WAIT:1000)·1·(>K:#70183)

This sequence is - press "MENU" -> press LSK R5 -> press LSK R1 -> press LSK R6 -> press MENU again. It all happens on the left CDU - but you could use the right hand CDU too, so your main FMC screen doesn't change.

I am using the custom events from the PMDG SDK here, you will find those in the event selection treelist on the tab "Aircraft SDKs" You can also use the ROTOR_BRAKE codes from the behavior instead.

Thanks, Oliver!  I have taken your advice and started implementing my scripts concerning ground services by using the CDU button

pushes, as you suggested, easily found under the PMDG_737 tab with the scripting editor.  Clearly labeled... Menu button called Menu,

first right-hand button called R1... I'd encourage anyone to try it out.  Then, after you land, you don't need to poke around on a CDU to

get your jetway to come out and your chocks to be set and your ground power attached... you just ask your AAO first officer to request

those things, and she (programmatically) pushes the buttons to make it happen.  It's very much easier than I had even expected!  I've

been able to get all of my "usual" requests to ground handled by my AAO First Officer via this scripting, and it all seems and sounds

very natural, now!  I'm a happy camper! (And I have also used events from the PMDG SDK.)  

 

I do still have one question:  How does one indicate that the commands are for the FO's CDU instead of the Captain's?  I didn't come

across that in my meanderings.

 

I sure appreciate all the great support you provide to the whole AAO community (long may they

prosper)...

Erik Goodman

1 hour ago, MooneyDrover said:

How does one indicate that the commands are for the FO's CDU instead of the Captain's?  I didn't come

across that in my meanderings.

Different buttons have different events with different names (EVT_CDU_R for "right" instead of EVT_CDU_L ("= left")

Mind you, these are the event numbers from the PMDG SDK, I didn't invent them. They are just listed in AAO for your convenience, normally you find them in the PMDG SDK documentation.

Edited April 9, 20251 yr by Lorby_SI