SPAD.neXT CDU Binding?

SteveKane

I think that the H: and other events will eventually get added to Spad.Next once cOnnex gets around to it. I added the Client Events for most of the autopilot functions, and created a single StreamDeck XL page to match the 10-button A/P panel.

I'm not sure if it's worth publishing Spad.Next snippets for functions that require Client Events, but I'll certainly publish mine. @dadgametime can you do the same for yours?

dadgametime

I will. I still haven’t gotten the ADF button to work, which I cannot understand. I use the variable from the manual and double-checked it with the behavior tool, but it’s the one button that won’t function for me on the CDU. Also trying to change the preselect altitude on the altimeter using my Honeycomb Bravo autopilot knob and it’s not working either. So I’m hoping there will be a snippet for that posted.

OrenJKaufman

There's a couple errors with the event configuration, that one has a typo in it: H:CDU_AfdButton_1

Black Square

Oops. Sorry. Fixed.

OrenJKaufman

The only other one I found is that LVAR:var_FirewallValveCover_L controls the extinguisher cover and LVAR:var_ExtinguisherCover_L controls the firewall cover. The right side LVARs are correct.

SteveKane

@dadgametime

I use ALT_AltitudeSelectKnob_Inc_1 (and Dec_1) on my alt knob. (had to create Client H events for these).

SteveKane

@dadgametime I just saw and grabbed your SD XL snippet, much appreciated...looks great, though lots not working since I only have a handful of Client Events set up.

However, I was pinging the Spad.Next forum: Les Orielly was able to grab the vars/events from the manual, and will see if he can get the dev to get these imported soon so that we don't have to create all of the Client Events.

neinnunb

I have put ALL the H and K events from the manual into an XML file that can be imported into Spad Next. I just have to double check it all to make sure it's all correct before I share that file for everyone to use.

neinnunb

I hear Spad now has all of the H and K events, so no need to do custom events anymore.

Randolf

Also, if anyone wondered, the CDU number button events look like this H:CDU_9_1, where the first number is the key number and the last number is 1 for pilot and 2 for co-pilot CDU.
Didn't find these in the manual, had to look through the code.