iFly B737 Max and Mobiflight Presets

[TheAviationFox]

Have you tried looking up the variables through MSFS "developer mode"?

If not, start the MSFS developer mode, then open menu "Tools" and select "Behaviors" from the list. You can get a glimpse of the code behind a switch by hovering the mouse over a button or lever in the cockpit and then pressing "CTRL+G".

Try this with the autobrake switch and find out what LVAR will actually move it and the LVAR that will activate each mode.

[Cuantreau]

4 minutes ago, TheAviationFox said:

Have you tried looking up the variables through MSFS "developer mode"?

If not, start the MSFS developer mode, then open menu "Tools" and select "Behaviors" from the list. You can get a glimpse of the code behind a switch by hovering the mouse over a button or lever in the cockpit and then pressing "CTRL+G".

Try this with the autobrake switch and find out what LVAR will actually move it and the LVAR that will activate each mode.

Yes, that's exactly what I've done, the values are the same, as I explained, so I don't get why the disarm amber light is not working with the preset configured.

[John Dowson]

39 minutes ago, Cuantreau said:

I couldn't see it because the console is giving me constant repetitive event "BLEED_AIR_SOURCE_CONTROL_SET and MASTER_BATTERY_SET", so I can't read anything else, maybe I'm not doing it right but that is what it throws at me.

You can use the ini parameter DontLogThese to ignore those, best used in your profile section. See the Advanced User guide for details on this ini parameter.

39 minutes ago, Cuantreau said:

Within msfs behavior I could verify that the current value from switching the AB rotary switch with the mouse, is the same as switching it with physical rotary switch assigned with fsuipc presets. So AB disconnect amber light should work as expected but it doesn't, strange.

Yes, strange, However there is an issue with some external controls in that they don't work in the same manner as the internal one. This has been reported to Asobo (a long time ago), but I guess it has not yet been fully addressed. Is there another lvar that holds/controls the light state? If so, you could try using that....

John

 

[John Dowson]

15 minutes ago, John Dowson said:

However there is an issue with some external controls in that they don't work in the same manner as the internal one. This has been reported to Asobo (a long time ago), but I guess it has not yet been fully addressed.

...but this shouldn't apply when using presets/calc code as that is executed via the Gauge API, so I don't understand this either...

[Cuantreau]

Yes, it's strange, it should be working with presets.

[TheAviationFox]

Hello again!

I am a bit stuck with another task on the iFly 737 MAX8, After your help with the Dome lights and runway turnoff lights, I am now trying to improve the operation of the NAV and STROBE lights.

I am using a Honeycomb Alpha yoke with 2 separate flip switches for

• NAV (button numbers 26 up, 27 down) and
• STROBE (button numbers 28 up, 29 down) lights

In the aircraft, however, there is only one switch for these functions. The LVAR is called VC_POSITION_LIGHT_SW and its values are

• 0=STROBES and NAV ON
• 10=OFF
• 20=NAV STEADY ON

The switch position can be changed by our good old VC_Miscellaneous_trigger_VAL and we need to call

• 30 to move it UP
• 31 to move it DOWN

 

I am trying to program a logic where

• when the yoke NAV switch is UP and the STROBE switch is DOWN => VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)
• when the yoke NAV switch is DOWN and the STROBE switch is DOWN => VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF)
• when the yoke NAV switch is DOWN and the STROBE switch is UP => VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON)

 

I am trying to create a LUA script to implement this logic, but I failed in reading the switch positions, how exactly do I do this? Or is better to go ahead and use an FSUIPC Preset? CP and CU won't work, since it is not a "press" or "release" event, but rather flipping the NAV-handle from position 26 to 27.

 

Clueless greetings, Andreas

[John Dowson]

27 minutes ago, TheAviationFox said:

n the aircraft, however, there is only one switch for these functions. The LVAR is called VC_POSITION_LIGHT_SW and its values are

• 0=STROBES and NAV ON
• 10=OFF
• 20=NAV STEADY ON

If this is the case, then I can't see how you can control the strobe and nav lights independently with two switches. For example, if the nav lights were off and you wanted to switch only the strobe lights on, the value would go from 10 to 0 and so the nav lights would also be on, regardless of the position of your nav light switch. 

27 minutes ago, TheAviationFox said:

I am trying to program a logic where

• when the yoke NAV switch is UP and the STROBE switch is DOWN => VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)
• when the yoke NAV switch is DOWN and the STROBE switch is DOWN => VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF)
• when the yoke NAV switch is DOWN and the STROBE switch is UP => VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON)

You are missing UP/UP....?
But the logic should determine what happens when you move a switch, so you need:
   Nav switch Down, Strobe Switch Down: current state?
         Move nav switch up: new state?
         Move strobe switch up: new state?
   Nav switch Down, Strobe Switch Up: current state?
         Move Nav switch up: new state?
         Move strobe switch down: new state?
   Nav switch Up, Strobe switch down: current state?
        Move Nav switch down: new state?
        Move strobe switch up: new state?
   Nav switch up, strobe switch up: current state?
        Move nav switch down: new state?
        Move strobe switch down: new state?

i.e. the logic needs to encompass all possible states and state changes. And it can be okay for no state change on a switch position change, as long as its consistent.

If you can fill that in consistently, then you should be able to achieve what you want by overloading your assignments (i.e. having multiple assignments to the same switch/button) and using a combination of offset conditions (where the actual assignment triggered depends on the value held in an offset) and/or maybe compound conditions (where the assignment triggered on a button/switch press is determined by the state/position of another button/switch) - you don't have to use lua.
You need to add VC_POSITION_LIGHT_SW to an offset (as unsigned byte or UB).

If you can fill in those states above, I can help you further with this.

John

[John Dowson]

Here is the table with the state changes:

Nav switch Down, Strobe Switch Down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF)
    Move nav switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)
    Move strobe switch up: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON)

Nav switch Down, Strobe Switch Up: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON)
    Move Nav switch up: new state?
    Move strobe switch down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF)

Nav switch Up, Strobe switch down: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)
    Move Nav switch down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF)
    Move strobe switch up: new state?

Nav switch up, strobe switch up: current state?
    Move nav switch down: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON)
    Move strobe switch down: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)

What do you expect when both switches are up? Makes sense to have this as nav off, strobes on - but that is not possible.....

But you need to define what happens in this position, even if you don't intend to use those actual positions. If you can define what you would like in that position, the assignments should be relatively straightforward....
 

Edited Monday at 02:41 PM by John Dowson
more info added

[John Dowson]

1 hour ago, TheAviationFox said:

CP and CU won't work, since it is not a "press" or "release" event, but rather flipping the NAV-handle from position 26 to 27.

CP will work, as you get a press on 26 moving up, and a press on 27 moving down. Can't remember if you get a release, but this is not important or needed when you get a press in each position. So you just assign to the press events.

John

[TheAviationFox]

Hi John,

thanks for your quick reply. Yes, I omitted the case "UP, UP", because I hoped that I could simply ignore this case and thus the logic would "do nothing", not move any switch. Obviously, I cannot omit this condition, thanks for pointing this out.

3 hours ago, John Dowson said:

If this is the case, then I can't see how you can control the strobe and nav lights independently with two switches. For example, if the nav lights were off and you wanted to switch only the strobe lights on, the value would go from 10 to 0 and so the nav lights would also be on, regardless of the position of your nav light switch. 

Okay, probably I did not write it precisely enough. Technically the STROBES can never be ON without NAV lights being ON. The upper switch position (0) switches both types of lights on. The lower position (20) will switch NAV lights only ON. The middle position (10) means that NAV and STROBES are OFF. I guess you understood this well, I only wanted to be precise on this. In other words: when I turn the STROBE light switch from the lower position to the upper position, I want the switch in the VC to go to the upper position to have both NAV and STROBES - no matter what the NAV light switch on my joystick is doing. My logic is only that the NAV light switch would remain in the ON position and that switching STROBES to ON would simply flick the light switch in the VC to the upper position. For the case "UP, UP" I now decided to make the NAV light switch on the joystick some kind of master key - if it's not down, the STROBES cannot be switched ON, it's a compromise.

Just to make sure we are on the same page: this is what the switches on the yoke look like:

They are both shown in the down position. Below is a photo the switch in a 737:

This my NAV switch on the yoke would be in the lower position to move the switch in the VC to the lower (STEADY) position, activating the NAV lights only. If I then moved the STROBE switch on the yoke to the upper position, the switch in the VC would move to the upper position "STROBE & STEADY", turning both NAV and STROBE lights on.

The logic would look like this, if I am not mistaken:

IF NAV light switch is 26 AND STROBE light switch is 29 THEN set VC_POSITION_LIGHT_SW =10
ELSE IF NAV light switch is 26 AND STROBE light switch is 28 THEN set VC_POSITION_LIGHT_SW =10
ELSE IF NAV light switch is 27 AND STROBE light switch is 29 THEN set VC_POSITION_LIGHT_SW =20
ELSE IF NAV light switch is 27 AND STROBE light switch is 28 THEN set VC_POSITION_LIGHT_SW =0

It's probably not the most efficient and I also need to know how to request these switch position values, that's why I am here 🙂

For a Preset in FSUIPC I need to create an offset

[LvarOffsets.iFly B737 MAX8]
2=L:VC_POSITION_LIGHT_SW=UB0xA002

The offset UB0*A000 is already taken by the Dome Light Switch (1=L:VC_Dome_Light_Display_VAL=UB0xA000) from my first Preset that you kindly created for me earlier on. I hope that UB0xA002 is a valid offset, at least that's what I understood from the FSUIPC user manual.

Can I make a preset that checks for the offset value AND for the switch positions on my yoke, that then sets the VC_POSITION_LIGHT_SW to the requested value 0, 10 or 20 ?

Regarding the required code for FSUIPC.ini I have reached the limits of my knowledge to complete it.

[John Dowson]

49 minutes ago, TheAviationFox said:

Okay, probably I did not write it precisely enough. Technically the STROBES can never be ON without NAV lights being ON. The upper switch position (0) switches both types of lights on. The lower position (20) will switch NAV lights only ON. The middle position (10) means that NAV and STROBES are OFF. I guess you understood this well,

Yes, I understood. Just trying to point out that when using two switches, one for each light, its never going to work in the same way as one 3-position switch to control the lights. The honeycomb light switches are designed for on/off of each of the lights, so however you implement this is going to be a fudge, but maybe ne that you can live with.

And no need for the pictures either...

52 minutes ago, TheAviationFox said:

I hope that UB0xA002 is a valid offset, at least that's what I understood from the FSUIPC user manual.

Yes, that's fine.

52 minutes ago, TheAviationFox said:

Can I make a preset that checks for the offset value AND for the switch positions on my yoke, that then sets the VC_POSITION_LIGHT_SW to the requested value 0, 10 or 20 ?

No, but you can assign to a preset and then make that assignment conditional on an offset value. Or just also add the lvar VC_Miscellaneous_trigger_VAL to an offset, and just use assignments with offset conditions, as I advised.

If you can just tell me what you want the switch position to be in the UP/UP state I can show you how to do this - its easier to do it this way than in lua.

[TheAviationFox]

8 minutes ago, John Dowson said:

If you can just tell me what you want the switch position to be in the UP/UP state I can show you how to do this - its easier to do it this way than in lua.

UP/UP should be NAV/STROBE OFF, VC_Miscellaneous_trigger_VAL=10

[John Dowson]

Ok, then we have:

Nav switch Down, Strobe Switch Down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF)
    Move nav switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)
    Move strobe switch up: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON)

Nav switch Down, Strobe Switch Up: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON)
    Move Nav switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)
    Move strobe switch down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF)

Nav switch Up, Strobe switch down: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)
    Move Nav switch down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF)
    Move strobe switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)

Nav switch up, strobe switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)
    Move nav switch down: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON)
    Move strobe switch down: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF)

Re-arrange these by switch movement:

Button 26 (nav switch up): 
    set VC_POSITION_LIGHT_SW = 10 when VC_POSITION_LIGHT_SW = 20
    set VC_POSITION_LIGHT_SW = 10 when VC_POSITION_LIGHT_SW = 0
Button 27 (nav switch down)
    set VC_POSITION_LIGHT_SW = 20 when VC_POSITION_LIGHT_SW = 10 & strobe switch down
    set VC_POSITION_LIGHT_SW = 0 when VC_POSITION_LIGHT_SW = 10 & & strobe switch up
Button 28 (strobe switch up)
    set  VC_POSITION_LIGHT_SW = 0 when VC_POSITION_LIGHT_SW = 20
    set VC_POSITION_LIGHT_SW = 10 when VC_POSITION_LIGHT_SW = 10 (i.e. no change)
Button 29 (strobe switch down):
    set VC_POSITION_LIGHT_SW = 20 when VC_POSITION_LIGHT_SW = 0
    set VC_POSITION_LIGHT_SW = 10 when VC_POSITION_LIGHT_SW = 10 (i.e. no change)

Note that button 27 is the only state change that needs a dependency on the state of another button as the VC_POSITION_LIGHT_SW value condition is the same.

The next thing to determine if you can write to the lvar VC_POSITION_LIGHT_SW ti change the position? If so, this makes things easier, as you can then just write to the offset holding the lvar to change the position. But, as you said you need to use VC_Miscellaneous_trigger_VAL (with 30 for up and 31 for down) we will use that, So, define 4 presets (in your myEvents.txt file):

//iFly/737-Max8/Lights
Nav_Strobe_Switch_Up:30 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Down:31 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Up_Two:30 (>L:VC_Miscellaneous_trigger_VAL,number) 30 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Down_Two:31 (>L:VC_Miscellaneous_trigger_VAL,number) 31 (>L:VC_Miscellaneous_trigger_VAL,number)

I am not 100% sure about the _Up_Two and _Down_Two presets: we need to move the switch two positions for some assignments, but setting the same value to an lvar twice in the same calculator code string may not allow this. If not there are a few other things to try (see below).

Now we can define our assignments:
For Button 26,
      send switch-up when when VC_POSITION_LIGHT_SW = 20, and switch down when  VC_POSITION_LIGHT_SW = 0
to send a switch up, using B as your Bravo device letter and starting the indices from 1 will give the following assignment entry:
    1=PB,26,CPNav_Strobe_Switch_Up,0     -{Preset Control}-
then add the offset condition on the value of VC_POSITION_LIGHT_SW held in offset 0xA002
    1=BA002=20 PB,26,CPNav_Strobe_Switch_Up,0     -{Preset Control}-
Next, we can duplicate that, change the index number, the preset and the offset condition for the switch down when  VC_POSITION_LIGHT_SW = 0:
    2=BA002=0 PB,26,CPNav_Strobe_Switch_Down,0     -{Preset Control}-

Doing this for each button 27, we get:
    3=BA002=10 PB,27,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
    4=BA002=10 PB,27,CPNav_Strobe_Switch_Up,0     -{Preset Control}-
and then we need to add the additional condition on the strobe switch position (buttons 28 and 29):
    3=BA002=10 (+B, 29)PB,27,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
    4=BA002=10 (+B, 28)PB,27,CPNav_Strobe_Switch_Up,0     -{Preset Control}-

Doing this for all buttons, we end up with:

    1=BA002=20 PB,26,CPNav_Strobe_Switch_Up,0     -{Preset Control}
    2=BA002=0 PB,26,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
    3=BA002=10 (+B, 29)PB,27,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
    4=BA002=10 (+B, 28)PB,27,CPNav_Strobe_Switch_Up,0     -{Preset Control}-
    5=BA002=20 PB,28,CPNav_Strobe_Switch_Up_Two,0     -{Preset Control}
    6=BA002=0 PB,29,CPNav_Strobe_Switch_Down_Two,0     -{Preset Control}-

So try that - just paste those entries into your profile buttons section, and change the joystick letter to the one you are using (also in the compound condition) and also make sure the index numbers are unique in your section.

If the presets to move two positions don't work, you could try the following instead:

    1=BA002=20 PB,26,CPNav_Strobe_Switch_Up,0     -{Preset Control}
    2=BA002=0 PB,26,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
    3=BA002=10 (+B, 29)PB,27,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
    4=BA002=10 (+B, 28)PB,27,CPNav_Strobe_Switch_Up,0     -{Preset Control}-
    5=BA002=20 PB,28,CPNav_Strobe_Switch_Up,0     -{Preset Control}
    6=BA002=20 PB,28,C1152,5     -{pause (ms)}-
    7=BA002=20 PB,28,CPNav_Strobe_Switch_Up,0     -{Preset Control}
    8=BA002=0 PB,29,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
    9=BA002=0 PB,29,C1152,5     -{pause (ms)}-
    10=BA002=0 PB,29,CPNav_Strobe_Switch_Down,0     -{Preset Control}-

Here we are sending he preset twice, with a short pause between each one. The trick here is to get the pause large enough so that both presets are executed, but small enough so that the update of the lvar has not been received yet to update the value in the offset condition on  0xA002. I have used 5ms - you can use logging to determine if this needs to be increased or decreased (probably increased if anything - try 10ms next and so on).

Give those a try and let me know if either works as expected.

John

[TheAviationFox]

Hi John,

thanks a lot for taking your time with this.

FSUIPC shows my Alpha Yoke to be joystick "M". I modified your suggested Presets to look like this:

[Buttons.iFly B737 MAX8]
0=BA000=0 PH,5,CPiFly737MAX8_Dome_Light_Up,0 	-{Preset Control}-
1=BA000=1 PH,5,CPiFly737MAX8_Dome_Light_Up,0 	-{Preset Control}-
2=BA000=2 PH,5,CPiFly737MAX8_Dome_Light_Down,0 	-{Preset Control}-
3=BA000=2 PH,5,C1152,50 	-{pause (ms)}-
4=BA000=2 PH,5,CPiFly737MAX8_Dome_Light_Down,0 	-{Preset Control}-
5=BA002=20 PM,26,C0,0 	-{Custom control: <0>}-
6=BA002=0 PM,26,C0,0 	-{Custom control: <0>}-
7=BA002=10 (+B, 29)PM,27,CPNav_Strobe_Switch_Down,0
8=BA002=10 (+B, 28)PM,27,CPNav_Strobe_Switch_Up,0
9=BA002=20 PM,28,C0,0 	-{Custom control: <0>}-
10=BA002=20 PM,28,C1152,50 	-{pause (ms)}-
11=BA002=20 PM,28,C0,0 	-{Custom control: <0>}-
12=BA002=0 PM,29,C0,0 	-{Custom control: <0>}-
13=BA002=0 PM,29,C1152,50 	-{pause (ms)}-
14=BA002=0 PM,29,C0,0 	-{Custom control: <0>}-

 

The section LvarOffsets just below it:

[LvarOffsets.iFly B737 MAX8]
1=L:VC_Dome_Light_Display_VAL=UB0xA000
2=L:VC_POSITION_LIGHT_SW=UB0xA002

 

For completeness, MyEvents.txt looks like this:

//iFly/737MAX/Lights
iFly737MAX8_Dome_Light_Up#39 (>L:VC_Miscellaneous_trigger_VAL,number)
iFly737MAX8_Dome_Light_Down#38 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Up:30 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Down:31 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Up_Two:30 (>L:VC_Miscellaneous_trigger_VAL,number) 30 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Down_Two:31 (>L:VC_Miscellaneous_trigger_VAL,number) 31 (>L:VC_Miscellaneous_trigger_VAL,number)

I just tried it in MSFS2020 and I cannot even find those new Events, nor from the dropdown list or from the function "Find preset", unlike the Dome Light switches that show up nicely.

 

I probably made a very simple mistake, but I could not spot it so far.

[John Dowson]

7 hours ago, TheAviationFox said:

FSUIPC shows my Alpha Yoke to be joystick "M". I modified your suggested Presets to look like this:

As you can see, the presets weren't recognised and changed to custom control 0. This is because I mistakenly used a colon for a divide between the preset name and the calculator code instead of a hash symbol - sorry about that... I don't have a hash symbol on  my keyboard and I forget sometimes!. The preset should be:

//iFly/737-Max8/Lights
Nav_Strobe_Switch_Up#30 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Down#31 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Up_Two#30 (>L:VC_Miscellaneous_trigger_VAL,number) 30 (>L:VC_Miscellaneous_trigger_VAL,number)
Nav_Strobe_Switch_Down_Two#31 (>L:VC_Miscellaneous_trigger_VAL,number) 31 (>L:VC_Miscellaneous_trigger_VAL,number)

So change those.

You also didn't change the conditional button to you M device. So, change to:

[Buttons.iFly B737 MAX8]
0=BA000=0 PH,5,CPiFly737MAX8_Dome_Light_Up,0 	-{Preset Control}-
1=BA000=1 PH,5,CPiFly737MAX8_Dome_Light_Up,0 	-{Preset Control}-
2=BA000=2 PH,5,CPiFly737MAX8_Dome_Light_Down,0 	-{Preset Control}-
3=BA000=2 PH,5,C1152,50 	-{pause (ms)}-
4=BA000=2 PH,5,CPiFly737MAX8_Dome_Light_Down,0 	-{Preset Control}-
5=BA002=20 PM,26,CPNav_Strobe_Switch_Up,0     -{Preset Control}
6=BA002=0 PM,26,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
7=BA002=10 (+M, 29)PM,27,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
8=BA002=10 (+M, 28)PM,27,CPNav_Strobe_Switch_Up,0     -{Preset Control}-
9=BA002=20 PM,28,CPNav_Strobe_Switch_Up,0     -{Preset Control}
10=BA002=20 PM,28,C1152,50     -{pause (ms)}-
11=BA002=20 PM,28,CPNav_Strobe_Switch_Up,0     -{Preset Control}
12=BA002=0 PM,29,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
13=BA002=0 PM,29,C1152,50     -{pause (ms)}-
14=BA002=0 PM,29,CPNav_Strobe_Switch_Down,0     -{Preset Control}-

John

[TheAviationFox]

Oh yeah, now I see that as well 🙂

I did not realize that (+M, 29) was a joystick assignment, dumb!

I have corrected the entries and it does not work yet. There is an error message at two of the line:

5=BA002=20 PM,26,CPNav_Strobe_Switch_Up,0     -{Preset Control}-
6=BA002=0 PM,26,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
7=BA002=10 (+M, 29)PM,27,CPNav_Strobe_Switch_Down,0 << ERROR 19! Line ignored >>
8=BA002=10 (+M, 28)PM,27,CPNav_Strobe_Switch_Up,0 << ERROR 19! Line ignored >>
9=BA002=20 PM,28,CPNav_Strobe_Switch_Up,0     -{Preset Control}-
10=BA002=20 PM,28,C1152,50     -{pause (ms)}-
11=BA002=20 PM,28,CPNav_Strobe_Switch_Up,0     -{Preset Control}-
12=BA002=0 PM,29,CPNav_Strobe_Switch_Down,0     -{Preset Control}-
13=BA002=0 PM,29,C1152,50     -{pause (ms)}-
14=BA002=0 PM,29,CPNav_Strobe_Switch_Down,0     -{Preset Control}-

ERROR 19 is The C.r Kor M needed for Control, Key or Macro is missing.