Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum
  1. Home
  2. Just Flight
  3. MSFS Products
  4. Black Square Add-Ons
  5. Starship
  6. Which variables can I use to read your custom variables Black Square?

Which variables can I use to read your custom variables Black Square?

Scheduled Pinned Locked Moved Starship
17 Posts 3 Posters 319 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • toby23T Offline
    toby23T Offline
    toby23
    wrote last edited by
    #2

    The image below shows an example from another profile that uses default Asobo variables.
    I need to 'read' the values to be able to display them in the row where the green X is.

    image.png

    1 Reply Last reply
    0
    • Black SquareB Offline
      Black SquareB Offline
      Black Square
      Black Square Developer
      wrote last edited by
      #3

      L:bksq_AltitudePreselect_1, for altitude, L:bksq_VerticalSpeedPreselect_1 for vertical speed, and then the rest are the SimVars that you're used to, so...

      A:AUTOPILOT HEADING LOCK
      A:AUTOPILOT MAX BANK > 22
      A:AUTOPILOT VERTICAL HOLD
      A:AUTOPILOT FLIGHT LEVEL CHANGE
      A:AUTOPILOT ALTITUDE LOCK
      A:AUTOPILOT APPROACH HOLD
      A:AUTOPILOT NAV1 LOCK
      A:AUTOPILOT FLIGHT DIRECTOR ACTIVE
      A:AUTOPILOT MASTER
      A:AUTOPILOT AIRSPEED HOLD

      There are a few more nuances that I could help you with, but that should be enough to get you started. Let me know if you need anything else!

      toby23T 1 Reply Last reply
      0
      • toby23T Offline
        toby23T Offline
        toby23
        wrote last edited by
        #4
        This post is deleted!
        1 Reply Last reply
        0
        • Black SquareB Black Square

          L:bksq_AltitudePreselect_1, for altitude, L:bksq_VerticalSpeedPreselect_1 for vertical speed, and then the rest are the SimVars that you're used to, so...

          A:AUTOPILOT HEADING LOCK
          A:AUTOPILOT MAX BANK > 22
          A:AUTOPILOT VERTICAL HOLD
          A:AUTOPILOT FLIGHT LEVEL CHANGE
          A:AUTOPILOT ALTITUDE LOCK
          A:AUTOPILOT APPROACH HOLD
          A:AUTOPILOT NAV1 LOCK
          A:AUTOPILOT FLIGHT DIRECTOR ACTIVE
          A:AUTOPILOT MASTER
          A:AUTOPILOT AIRSPEED HOLD

          There are a few more nuances that I could help you with, but that should be enough to get you started. Let me know if you need anything else!

          toby23T Offline
          toby23T Offline
          toby23
          wrote last edited by toby23
          #5

          @Black-Square - Thank you, is this the correct assignment for Autopilot buttons?

          555ed5ac-db0b-4dac-8442-ef6e83ed8d72-image.png

          1 Reply Last reply
          0
          • Black SquareB Offline
            Black SquareB Offline
            Black Square
            Black Square Developer
            wrote last edited by
            #6

            Ok, here come the nuanced ones straight from the RPN. The rest are as you've listed.

            Flight Director Off:
            (A:AUTOPILOT FLIGHT DIRECTOR ACTIVE, bool) (A:AUTOPILOT MASTER, bool) ! and

            IAS Profile:
            (A:AUTOPILOT FLIGHT LEVEL CHANGE, bool) (L:var_iasHoldMode, bool) ! and (A:INDICATED ALTITUDE:1, FEET) 250 - (A:AUTOPILOT ALTITUDE LOCK VAR:1, FEET) < and

            Descend:
            (A:AUTOPILOT FLIGHT LEVEL CHANGE, bool) (L:var_iasHoldMode, bool) ! and (A:INDICATED ALTITUDE:1, FEET) 250 + (A:AUTOPILOT ALTITUDE LOCK VAR:1, FEET) < and

            Airspeed hold:
            (A:AUTOPILOT AIRSPEED HOLD, bool)
            (A:AUTOPILOT FLIGHT LEVEL CHANGE, bool) (L:var_iasHoldMode, bool) and
            or

            1 Reply Last reply
            0
            • toby23T Offline
              toby23T Offline
              toby23
              wrote last edited by
              #7

              I really appreciate you sharing these variables, thank you.

              1 Reply Last reply
              0
              • Black SquareB Offline
                Black SquareB Offline
                Black Square
                Black Square Developer
                wrote last edited by
                #8

                Of course! Let me know what else I can do for you!

                1 Reply Last reply
                0
                • toby23T Offline
                  toby23T Offline
                  toby23
                  wrote last edited by toby23
                  #9
                  This post is deleted!
                  1 Reply Last reply
                  0
                  • toby23T Offline
                    toby23T Offline
                    toby23
                    wrote last edited by toby23
                    #10

                    I cannot find a way to read if IAS or DES mode is active using SimVars.

                    I am reading A:AUTOPILOT FLIGHT LEVEL CHANGE, Bool to turn the 'green light' on for either the IAS or DES switch. Currently it turns both lights on when either mode is activated.

                    How can I 'read' which mode is active?

                    I can use RPN scripts but I cannot write them myself.

                    Thank you

                    1 Reply Last reply
                    0
                    • Black SquareB Offline
                      Black SquareB Offline
                      Black Square
                      Black Square Developer
                      wrote last edited by
                      #11

                      That's what the (A:INDICATED ALTITUDE:1, FEET) 250 - (A:AUTOPILOT ALTITUDE LOCK VAR:1, FEET) < and... sections of the code above is meant to do. It simply looks at whether the preselected altitude is commanding a climb or descent from the current altitude.

                      1 Reply Last reply
                      0
                      • toby23T Offline
                        toby23T Offline
                        toby23
                        wrote last edited by toby23
                        #12

                        I thought so but adding it as a Script to the entry field doesn't work and I cannot figure out why. I use something similar to detect if 100 or 1000 ft is selected for the altitude dial in another profile, that uses this script.

                        image.png

                        but if I use your RPN code, it doesn't detect between IAS (IASP) or DES.

                        68327126-fc05-4f48-80e9-6c9daecc15bc-image.png

                        I will ask on the AAO forum and see if Lorby can help too. Thank you

                        1 Reply Last reply
                        0
                        • toby23T Offline
                          toby23T Offline
                          toby23
                          wrote last edited by toby23
                          #13

                          @Black-Square It is slowly coming together...

                          One question for you, how have you configured the V/S readout?

                          In the image below, 2.1 shows the A:Var AUTOPILOT VERTICAL HOLD VAR, Feet/minute
                          BUT this is only correctly displayed when V/S mode is active.

                          In reverse, when the ALT mode is active, the ALT readout does not change on the Stream Deck profile but it does in the sim.

                          Q. When I turn the dial, I can see the VSpeed change in the sim cockpit but the correct value is ONLY displayed on the Stream Deck when V/S mode is active, why?

                          N.B.The Starship is the only aircraft where my profiles don't seem to work 'normally'.

                          eeafd10a-1756-403a-af0a-3e0e1831584b-image.png

                          1 Reply Last reply
                          0
                          • Black SquareB Offline
                            Black SquareB Offline
                            Black Square
                            Black Square Developer
                            wrote last edited by
                            #14

                            For both of them, you could try this technique:

                            Vertical Speed Select:

                            (A:AUTOPILOT VERTICAL HOLD, bool) if{
                                (AUTOPILOT VERTICAL HOLD VAR:1, feet per minute)
                            }
                            els{
                                (L:bksq_VerticalSpeedPreselect_1, feet per minute)
                            }
                            

                            Altitude Select:

                            (A:AUTOPILOT ALTITUDE LOCK, bool) if{
                                (AUTOPILOT ALTITUDE LOCK VAR:1, feet)
                            }
                            els{
                                (L:bksq_AltitudePreselect_1, feet)
                            }
                            

                            I'm not sure why that should be necessary for the selected altitude, but if it works, it works.

                            toby23T 1 Reply Last reply
                            0
                            • S Offline
                              S Offline
                              SaabFAN86
                              wrote last edited by
                              #15

                              I'm also looking into getting data out of the starship, but for a different purpose: I want to use the WinWing MCDU or even a self-made CDU (the button-layout transfer from the MCDU to the Starship-CDU is way less intuitive than I thought) to interact with the starship CDU.
                              Best case, this includes the display of the Starship CDU being mirrored on the device.
                              I am using Mobiflight for this, so I need the data that is on screen in plain text form, including color information.

                              Is there any way to get that data? Or does it require an update of the Starship?

                              Black SquareB 1 Reply Last reply
                              0
                              • S SaabFAN86

                                I'm also looking into getting data out of the starship, but for a different purpose: I want to use the WinWing MCDU or even a self-made CDU (the button-layout transfer from the MCDU to the Starship-CDU is way less intuitive than I thought) to interact with the starship CDU.
                                Best case, this includes the display of the Starship CDU being mirrored on the device.
                                I am using Mobiflight for this, so I need the data that is on screen in plain text form, including color information.

                                Is there any way to get that data? Or does it require an update of the Starship?

                                Black SquareB Offline
                                Black SquareB Offline
                                Black Square
                                Black Square Developer
                                wrote last edited by
                                #16

                                @SaabFAN86 I have no idea what format that text and color information is supposed to be presented in, nor how to get it to you. Can you give me an idea of how these other units work? I suspect this is not something that's possible from the JavaScript context, but I will do it if it's remotely possible, or send you a custom solution if it's not something I want to include for all users.

                                1 Reply Last reply
                                0
                                • Black SquareB Black Square

                                  For both of them, you could try this technique:

                                  Vertical Speed Select:

                                  (A:AUTOPILOT VERTICAL HOLD, bool) if{
                                      (AUTOPILOT VERTICAL HOLD VAR:1, feet per minute)
                                  }
                                  els{
                                      (L:bksq_VerticalSpeedPreselect_1, feet per minute)
                                  }
                                  

                                  Altitude Select:

                                  (A:AUTOPILOT ALTITUDE LOCK, bool) if{
                                      (AUTOPILOT ALTITUDE LOCK VAR:1, feet)
                                  }
                                  els{
                                      (L:bksq_AltitudePreselect_1, feet)
                                  }
                                  

                                  I'm not sure why that should be necessary for the selected altitude, but if it works, it works.

                                  toby23T Offline
                                  toby23T Offline
                                  toby23
                                  wrote last edited by toby23
                                  #17

                                  @Black-Square Thank you so much for sharing this code.
                                  I still couldn't get this to work as as a script in Stream Deck software but I was able to get both dial readouts populated using the LVars (as you originally suggested). Thank you.

                                  1 Reply Last reply
                                  0
                                  Reply
                                  • Reply as topic
                                  Log in to reply
                                  • Oldest to Newest
                                  • Newest to Oldest
                                  • Most Votes


                                  • Login

                                  • Don't have an account? Register

                                  • Login or register to search.
                                  • First post
                                    Last post
                                  0
                                  • Categories
                                  • Recent
                                  • Tags
                                  • Popular
                                  • Users