Hello everybody,

I’m completing a remote control panel for the PMDG 737 using an app called Matric for the visual setting of switches and buttons and AAO to bridge the commands from Matric deck and MSFS. Another application called Simconnect2Matric is the interface between MSFS and Matric so any switch or button movement in the VC is replicated in Matric using Lvars. 

Everything works fine and all the positions of switches  and buttons are synchronized between the Matric deck and the VC of MSFS. 

The only variables I didn’t found using the Lvars read function of AAO are those regarding the state of landing, runway and position light.

Anyone can give me a suggestion about this matter?

Thank you in advance.

Andrea

Suggestion: use the official PMDG SDK instead of LVars and ROTOR_BRAKE codes. There is a chapter in the AAO manual about how to do that. The PMDG Variables and custom Events are in the AAO lists, but data transmisdion has to be configured before they start working.

Data transmission is active but when I try to read a PMDG: vars with Simconnect2Matric this crashes. 

This doesn't happen with lvars.

12 hours ago, whityini said:

when I try to read a PMDG: vars with Simconnect2Matric this crashes

(PMDG: variables are a AAO internal asset, you can't read them anywhere else. You would have to run an autoscript in AAO that copies the value from the PMDG var into your own LVar.

I'm just saying that the LVars from the behavior code in general are not meant to be used that way. You have no guarantee that they will even have the same name after a PMDG update.

Edited September 20, 20241 yr by Lorby_SI

Ok it's clear now. Unfortunatly I'm a newbie on this matter and I don't really know how to run such an autoscript in AAO. Could you please give me an example?

 

Create a script like this:

(PMDG:somevariable) (>L:mylvar, Number)

Save it and configure it as an Aircraft Automated Script (menu Scripting), repeating, with a frequency that is suitable for the use case (=for me, it doesn't make sense to query a light setting every 100ms. I can live with a half-second delay.

That being said, aren't those light switches connected to the actual simulator "(A:" variables? 

And: do you know how to look at the behavior code in MSFS developer mode? In most cases that will tell you everything about a switch in the cockpit.

Edited September 20, 20241 yr by Lorby_SI

On 9/19/2024 at 2:06 PM, whityini said:

those regarding the state of landing, runway and position light.

Landing light switches
(L:switch_113_73X, Number)
(L:switch_114_73X, Number)

Runway light switches

(L:switch_115_73X, Number)
(L:switch_116_73X, Number)

Position (three state switch!):

(L:switch_123_73X, Number)

Be mindful that LVars tell you the state of the animation of the switch, nothing else. They don't tell you if the lights are actually on or off.

How to find this:
Activate MSFS developer mode -> open "Tools->Behaviors" -> click back into the sim, hover the mouse over the switch that you are interested in, press Ctrl G. This will bring up the behavor code of the switch and you can look for the Lvars and ROTOR_BRAKE codes in there.

Edited September 20, 20241 yr by Lorby_SI

Thank you Lorby I have found all the variables I need. My deck is almost done.