Hi, first post!

I recently started using Axis and Ohs and I went all out and setup an arduino and rotary encoders as a midi device. It’s working great for altitude and speed because they have built in INC and DEC events. It feels really good, but I’m having trouble getting the heading bug to work.

Things I’ve tried:

- Looking for any kind of script that has a INC/DEC for heading instead of just a SET. Don’t seem to see anything

- Using a MIDI value coming out of the control as an axis. This works well except that I can only send values because 0-127, meaning I can’t do small changes

- Creating a RPN script and binding the LEFT and RIGHT events. Something like (PMDG:MCP_Heading) 1 +/- (>K:SET_HDG)

This last one is as close as I can get but because of the nature of the script, it doesn’t actually increment with each turn because of what I’m guessing is a lag between setting the heading and the variable updating.

A solution (maybe) could be setting up the script to only run one at a time which would be super slow but atleast be accurate? I’m not sure.

I’m also having the same issue with setting the altimeter except there does seem to be an event for kollsman inc/dec. Except they don’t work on PMDG, atleast the 737 :( Any direction here would also be greatly appreciated.

Hoping I did this right, thank for any help!

JP

What aircraft is that exactly? There are multiple ways to do this, and there definitely are INC and DEC events. But the items that you need have different IDs for the various PMDG aircraft models.  In AAO, use the Filter box to find them.

1. The default simulator heading events are 1 (>K:HEADING_BUG_INC) and  1 (>K:HEADING_BUG_DEC). In the SDK documentation they are hidden away in the section "Flight Assistance", not "Autopilot". In the past, the defaults used to work with PMDG.

2. If you want to use the custom events from the PMDG SDK, you will find them in the section "Aircraft SDKs" on the event selection dialog (provided that you are using the latest AAO version). To operate these you have to apply the PMDG mouse codes. See AAO manual.
Example: for the 777, the heading selector event is #71812|EVT_MCP_HEADING_SELECTOR. 
To utilize it, you need the codes for mouse wheel up and down from the "PMDG Mouse" group.
In a script that would look like this:
8192 (>K:#71812)
16384 (>K:#71812)
The first is mouse wheel up, the second is mouse wheel down. 
For the 737 the custom event number will be different.

3. You can use the ROTOR_BRAKE codes from the PMDG behavior code:
Again, for the 777 (737 is different)
218007 (>K:ROTOR_BRAKE)
218008 (>K:ROTOR_BRAKE)
First one is INC, second one is DEC

All this (1, 2, 3) can be assigned directly on the button dialog, no need for scripts. Select the event and then dial the numerical value into the box on the right.

Proper interaction with the PDMG SDK is described in the AAO manual, there is a separate chapter for them.

 

Edited October 20, 20241 yr by Lorby_SI

For the default altitude events, you have to supply a proper value, they cannot work with the default "1" or "0":
100 (>K:AP_ALT_VAR_INC)
1000 (>K:AP_ALT_VAR_INC)

Items 2 and 3 are the same as above, there are custom PMDG events and ROTOR_BRAKE codes.

Edited October 20, 20241 yr by Lorby_SI

Haha, yes, I found HEADING_BUG_INC/DEC. Good call on it being in Flight Assistance rather than Autopilot.

And for the altimeter I found the mouse up and mouse down commands, I didn’t even know you could do this! It makes a lot of sense. I must’ve missed the docs for it, this is perfect. For now I don’t have to explore the world of rotor brake commands 🤞. 

Thank you Lorby for the amazing replies as always. Appreciate you.