I have found that for most of the TFDI buttons, they consist of two separate sim events.  For example:
The APU
1·(>K:#73728) pushes the APU button/switch.  If you send this command, the button itself stays pushed in
1·(>K:#73729) returns the APU button/switch to the out position
So in order to push the button and have it cycle both in and out as is proper I am using
1·(>K:#73728)·(WAIT:400)·1·(>K:#73729)
Now, if I assign this to a rocker on my HC Bravo, it turns on and off no matter where the rocker starts (up or down) as would be expected.  
Would the IS TOGGLE feature make this so the rockers visual position would indicate if the APU is on or off?  

Also, just updated to  4.30 b12, but on the last version I began to notice that scripts that worked during testing, sometimes do not do anything when actually used in the game.  Then sometimes they do.  In other words not very consistent.  Has this been an issue and if not what do you suspect could be wrong?

6 hours ago, Crabby said:

Now, if I assign this to a rocker on my HC Bravo, it turns on and off no matter where the rocker starts (up or down) as would be expected.  
Would the IS TOGGLE feature make this so the rockers visual position would indicate if the APU is on or off?  

You need to write scripts to force deterministic ON and OFF behavior

 

6 hours ago, Crabby said:

Also, just updated to  4.30 b12, but on the last version I began to notice that scripts that worked during testing, sometimes do not do anything when actually used in the game.  Then sometimes they do.  In other words not very consistent.  Has this been an issue and if not what do you suspect could be wrong?

Sorry, no idea. What kind of scripts are those, in what simulator and which aircraft? Any chance that the input hardware is at fault?

Well, lol, I guess I have reached the end of my ignorance.  I will wait till someone smarter than me and understands the scripting logic makes a set of scripts.  I read what you put above and it makes zero sense to me why it works.  I get it, it does work, I am sure. 

I am guessing that means that if you send 90112 and the LVAR is in the NAV state (1) then it turns it off and if in the OFF state (0) it turn it to NAV.  Am I in the ball park? 

On 7/8/2024 at 12:24 AM, Lorby_SI said:

Sorry, no idea. What kind of scripts are those, in what simulator and which aircraft? Any chance that the input hardware is at fault?

Pretty standard PMDG stuff like 

0·(>K:#70152) Eng1 Fuel lever on
1·(>K:#70152) Eng1 Fuel lever off

Assigned to a rocker on my HC Bravo.  I don't think it is hardware as this does not happen in the 737 for example.  Normally both fuel levers move to on no issue and then do not move to off when I arrive at the gate.  Now, I did assign them as button on/off commands and I am wondering if that may have something to do with this behavior.  

OFF assigned to switch 44 Pressed

ON assigned to switch 44 On release

I will try just assigning them individually to the up and down position of the rocker. 

 

5 hours ago, Crabby said:

Pretty standard PMDG stuff like 

0·(>K:#70152) Eng1 Fuel lever on
1·(>K:#70152) Eng1 Fuel lever off

I will have to check if they still work that way. The new 777 has developed a different behavior regarding the custom events, and one cannot be sure that this wont happen to the other models too (as PMDG claims they are using a form of standartized middleware?)

In any case, firstly I would script that too, to avoid duplicate assignments. Second, there is a checkbox on the button assignment dialog when you are operating an actual rocker switch. Maybe that would help too.

Edited July 10, 20241 yr by Lorby_SI

5 hours ago, Crabby said:

I am guessing that means that if you send 90112 and the LVAR is in the NAV state (1) then it turns it off and if in the OFF state (0) it turn it to NAV.  Am I in the ball park

Not really, no. You create the scripts in AAO, then you assign them to your buttons. Once created, scripts appear in the same event treelist as everything else.

There is nothing more to it that a bit of copy&paste.

That's what I do Crabby, this is my show/hide tablet on a rocker switch:

Rocker screenshot

15 hours ago, Crabby said:

Pretty standard PMDG stuff like 

0·(>K:#70152) Eng1 Fuel lever on
1·(>K:#70152) Eng1 Fuel lever off

Assigned to a rocker on my HC Bravo.  I don't think it is hardware as this does not happen in the 737 for example.  Normally both fuel levers move to on no issue and then do not move to off when I arrive at the gate.  Now, I did assign them as button on/off commands and I am wondering if that may have something to do with this behavior.  

OFF assigned to switch 44 Pressed

ON assigned to switch 44 On release

I will try just assigning them individually to the up and down position of the rocker. 

 

The rocker switches on the Bravo are actually two separate momentary buttons. 

I would use two separate assignments, one for button 43 and one for button 44. One operates the ON event, the other the OFF event. Key Down only, no Key Up required.

Also, please be mindful that the new PMDG 777 for MSFS does not play by the old rules. Do not expect the events to work like they used to, I found many that need the mouse codes to work (and scripts too).

Edited July 10, 20241 yr by Lorby_SI

1 hour ago, Lorby_SI said:

The rocker switches on the Bravo are actually two separate momentary buttons. 

I would use two separate assignments, one for button 43 and one for button 44. One operates the ON event, the other the OFF event. Key Down only, no Key Up required.

Also, please be mindful that the new PMDG 777 for MSFS does not play by the old rules. Do not expect the events to work like they used to, I found many that need the mouse codes to work (and scripts too).

Thank you, yes, it has been an interesting puzzle. I also found that FMC_DistanceToTOD does nothing and FMC_DistanceToDest gives the distance to TOD.

4 minutes ago, mrm0508 said:

I also found that FMC_DistanceToTOD does nothing and FMC_DistanceToDest gives the distance to TOD.

I know, There is more than one incorrect variable. I'm afraid that the underlying data structure needs another update. Things seem to have changed in the PMDG SDK at some point and I didn't catch that in time. This is on the list for AAO 4.40