I've used A&O to set up all kinds of functions, as you may remember my previous requests for support and they all work fine. Up to now my Honeycomb throttle buttons and switches have always worked through MSFS default and that hasn't been a problem. But I bought the FlightSim Studios E170 and none of my buttons work. The landing gear, throttle, speed brake, and flaps work fine, but no buttons or switches. For example, when I dial HDG and press the HDG button, it flashes for a half second then goes out. Of course when I turn the increase or decrease dial to change the heading, nothing happens. I assume I need a script or series of scripts to do this, but I have no idea how to do that. Could you give me the steps involved for setting up just the HDG button so when implemented the heading will go up and down (1 degree at a time would be fine). If I see that then I hope I could duplicate that with other values to make the others work.

Thanks very much.

Fortunately, FSS is starting to use Input Events.

Example for AP heading:

When you create your button assignment, find the group "MSFS Input Events" in the treelist. In there you will find EVT_AP_HDG_SEL_DEC and EVT_AP_HDG_SEL_INC. Assign those to the rotary encoders left/right button events.
To make sure that it only "fires" when the left hand rotary selector is in the correct position, assign that button event as the "Combo" for both button assignments.

The result would be two assignments:
One to Button <12> (right turn of the right hand encoder), Key Down Event "EVT_AP_HDG_SEL_INC" and "Combo" is Button <18>
The other to Button <13> (left turn of the right hand encoder), Key Down Event "EVT_AP_HDG_SEL_DEC" and "Combo" is Button <18>

That is pretty much it.

To make the LEDs on the Bravo light up, you will indeed need a script though. On flightsim.to you will find a package that I made containing the necessary scripts to control the LEDs. There are two automated scripts as well that already contain controls for all LEDs, but those are not for the EJets. You will have to duplicate the default autoscript and adjust the simulator variables within so the LEDs show the correct status.

AxisAndOhs Scripts for the Honeycomb Bravo LEDs for Microsoft Flight Simulator | MSFS

To add - if there is no Input Events, then the button is probably accessible with an LVar. That process is more involved though. You may also need FSS LVars for the LED status. 

You will probably have to use the MSFS developer mode to find out what is what (in devel mode, open "Tools->Behaviors", then click back into the sim, hover the mouse over the button you are interested in and press Ctrl - G. This will bring up the behavior code which is executed when you use the mouse on the control. That should help with finding out about what makes a button or lever "tick". Also on the behavior dialog there are lists of the Input Events and the Local Variables with values. That might help to figure out what is needed for the LEDs.

I'm not going to lie, it will require a fair amount of effort to get every detail right. But unfortunately no other simmer has done it before and/or shared his template.

Thank you very much! I had no idea to look at the Input Events. I used your Heading examples and they worked fine. I'll begin to work through and see what I can do. Thanks for the insight into that and the developer mode to find the guts behind the buttons.

13 minutes ago, CaptainDunsel said:

I had no idea to look at the Input Events

Note how many there are - they are all valid for this specific aircraft, and not only for buttons, for axis too. For another plane the IEs can have different names (or not exist at all) that is the choice of the developer. But if IEs are there, I very much recommend using them. AFAIK they are Asobos preferred default now.