Hi Folks.

I am trying to assign the DA62 aircraft  ELT switch Test event to an SD+ button. I have used the AAO Watch simulator events and I get this...[SAFETY_ELT_1]: 1 (>IE:SAFETY_ELT_1)

I have also looked at Behaviours in the FS2020 and I see lots of information, including a mention of an ELT_TEST : 3. Unfortunately, I don't have the knowledge to decipher all of that information. I can see that it is in the SAFETY Root Components and there is an ASOBO_SAFETY_ELT_SubTemplate with 37 lines of information.

I don't need to activate the ELT to ON, hopefully, 🙂. I would like to see the TEST led light up though, when I press a button in my SD+ .

Any thoughts on how to set it up would be a great help.

Regards...Kenny.

p.s. I would need to be able to Toggle the switch back to the ARMED position after the TEST. Thanks.

 

Edited October 31, 20232 yr by kenny584
Afterthought.

The input events (IE), that are valid for this aircraft, are listed in the normal event selection treelist in AAO in the group "MSFS Input Events". You can just use them like everything else, on the Streamdeck too (IE: should be in the dropdown)

But unless you are in the MSFS Beta, IEs only work properly when MSFS devel mode is on (Asobo fixed that in the SU14 beta)

Edited October 31, 20232 yr by Lorby_SI

Example: simple "Event" Action on the StreamDeck

With InputEvents:

Key Down: IE: SAFETY_ELT_1
Event Value: 2

Key Up IE: SAFETY_ELT_1
Event Value: 1

-> If you are not in the Beta, I suggest using BVars instead.

Key Down: B: SAFETY_ELT_1_Set
Event Value: 2

Key Up B: SAFETY_ELT_1_Set
Event Value: 1

This will move the switch into the "Test" position while you press the button and reset it to "Armed" when you release it

Edited October 31, 20232 yr by Lorby_SI

And here are scripts that toggle through all three positions:

2·1·0·1·(IE:SAFETY_ELT_1)·(L:DA62ELT)·4·iseq·(>IE:SAFETY_ELT_1)·(>L:DA62ELT)

or

2·1·0·1·(B:SAFETY_ELT_1)·(L:DA62ELT)·4·iseq·(>B:SAFETY_ELT_1_Set)·(>L:DA62ELT)

Hello again Lorby.

Thanks once again for the prompt reply. I'll need to read the AAO documentation again to figure out what to do with the scripts you posted. At present, I am simply cherry picking the various Key events from the list in the Scripting section of AAO, if you know what I mean by that. My knowledge is still quite limited and there are so many different 'options' for events, at least to my inexperienced eye.

The B Var options that you posted work a treat. Thanks. It is very quick, is there a way to have a slight delay in the switch action? I'm thinking that a pilot would perhaps hold the test for aprox one or two seconds. The pc processor is way faster. If no delay option, then fine, I'm happy with it working as it is.

Cheers...Kenny.

p.s... I don't see IE in the Key Down/Up event  dropdown box. I have K: H: L: A: S: B: CMD:  I have 6.4.1.19697 of the Stream Deck software.

 

Edited October 31, 20232 yr by kenny584
Afterthought.

7 hours ago, kenny584 said:

I don't see IE in the Key Down/Up event  dropdown box. I have K: H: L: A: S: B: CMD:

Then you have an old version of the AAO StreamDeck plugin

7 hours ago, kenny584 said:

The B Var options that you posted work a treat. Thanks. It is very quick, is there a way to have a slight delay in the switch action? I'm thinking that a pilot would perhaps hold the test for aprox one or two seconds. The pc processor is way faster. If no delay option, then fine, I'm happy with it working as it is.

Sorry, but I don't understand what you mean by that. As the SD action handles key down and key up separately, the switch remains in "Test" for as long as you keep that button pressed. That was just a choice I made, nothing more. If you don't want it to work that way, figure out a different solution, like with the toggle script.

Edited November 1, 20232 yr by Lorby_SI

7 hours ago, kenny584 said:

different 'options' for events,

There are only two types: those from the MSFS SDK and those that were invented by the aircraft developer. The former you can find in AAO and the MSFS SDK documentation, the latter you have to find yourself. And you find them by using the MSFS developer mode (Tools->Behaviors), or by copying scripts or templates that others made - who looked into the MSFS behavior debug for you. Or ask the aircraft developer, some of them even provide extra documentation. In the future hopefully the new InputEvents will take hold and all this will be behind us.

 

Edited November 1, 20232 yr by Lorby_SI

7 hours ago, kenny584 said:

figure out what to do with the scripts

That is a required skill. Sticking to single events or variables won't cut it, you won't be able to do what you want to do without scripting.

Hello again.

You were correct, I did have an older version of the plugin. I now have 30_03, complete with IE in the dropdown. When I said that there were so many options, I meant that as a beginner, looking at the Behaviours page in the sim can be quite daunting as there is so much information to look at and decide which part is correct for what I am trying to achieve. To a newbie, it can all look quite similar.

I will get to grips with scripting, it's baby steps at the moment.

Best Regards...Kenny.