Announcement

Collapse

PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

Having trouble with auto throttle

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Having trouble with auto throttle

    So everything is good all the way to takeoff. AT is arm, I have heading set and VNav. When I take off, I engage TOGA and N1 is displayed. But then goes off and AT not armed anymore. I was not able to arm AT after takeoff, kept going off. Never had this issue in P3D so I must doing something wrong on takeoff. Preflight was executed and nothing seems wrong. Any suggestions. This doesn’t always happen and AT stays armed so maybe some in the way I set the MPC could be wrong

    FD on pilot
    AT arm
    lnav and vnav set
    Dean Salman
    Tags: None
    #2
    Originally posted by dsalman1 View Post
    So everything is good all the way to takeoff. AT is arm, I have heading set and VNav. When I take off, I engage TOGA and N1 is displayed. But then goes off and AT not armed anymore. I was not able to arm AT after takeoff, kept going off. Never had this issue in P3D so I must doing something wrong on takeoff. Preflight was executed and nothing seems wrong. Any suggestions. This doesn’t always happen and AT stays armed so maybe some in the way I set the MPC could be wrong

    FD on pilot
    AT arm
    lnav and vnav set
    The A/T will disengage if the engine thrusts are not stabilized and closely (doesn't have to be exact) match. Move the throttles to aim for 40-50 %N1 (I aim for 45%) and do nothing but watch. When the engines have stablized (N1 not changing) then and only then press TO/GA.

    This explains why sometime your A/T is holding as expected. Don't rush it, you're not traveling very far during this.
    Dan Downs KCRP
    i7-10700K 32GB 3600MHz 3080Ti

    Comment

      #3
      Thanks, Dan. I will check that. I did another flight and was more careful this time, so that must have been it. more reading
      Last edited by dsalman1; 07May2023, 00:25.
      Dean Salman

      Comment

        #4
        I found out that msfs 2020 also had the throttle setup there as well. I have a profile for the 737 that disables that. However the king air I am using only works with fs 2020 profile and I forgot to change it the 737 one. This is why I don’t like to set controls in fs 2020 and use Spad or fsuipc
        Dean Salman

        Comment

          #5
          Originally posted by dsalman1 View Post
          I found out that msfs 2020 also had the throttle setup there as well. I have a profile for the 737 that disables that. However the king air I am using only works with fs 2020 profile and I forgot to change it the 737 one. This is why I don’t like to set controls in fs 2020 and use Spad or fsuipc
          I don't think that's a good reason, in my opinion. It only takes 20 sec at the most to change from Boeing Twinjet to DC-6 control assignments. I also have assignment for the Fenix A320 but I've only flown it once. When we get the quad jet B744/8 I'll just add a new set of assignments. Come on, it takes 20 sec at the most!
          Dan Downs KCRP
          i7-10700K 32GB 3600MHz 3080Ti

          Comment

            #6
            Originally posted by dsalman1 View Post
            I found out that msfs 2020 also had the throttle setup there as well. I have a profile for the 737 that disables that. However the king air I am using only works with fs 2020 profile and I forgot to change it the 737 one. This is why I don’t like to set controls in fs 2020 and use Spad or fsuipc
            The trouble with this is that both SPAD.neXt and FSUIPC are external programs. If whichever one you are using decides to crash while you are on short final, well there go all of your controls with it. If you have your pitch/roll/yaw/throttle configured directly in the sim, then you will still have those controls even if all of your other configured controls disappear.
            Tim Lincoln
            My YouTube Channel
            • Likes 1

            Comment

              #7
              Thanks for the feedback, dan and Time. My sim is a little complex.
              I have 21 devices and 11 Saitek 5 panels and 6 instrument panels that I have program each button each aircraft with which includes pushing any of the aircraft buttons or switches. in Spad, I have conditions and multiple steps to execute a task, I do not like using a keyboard or mouse. Spad.Next loads a profile automatically when I switch aircrafts, FSUIPC does the same. I have never had these programs crash in the many years I have used them. However, that is always possible so I would be dead in the water. That all said, I agree it is very easy to name the profiles in MSFS 2020 and then just load the controls selecting the correct profile. I was happy to see MSFS 2020 do that, that was pretty clever.

              One point I really wanted to say, it can be a issue when using more than one way of programming controls, conflicts can happen assigning a throttle in 2 places for example. That is really why I throw everything at SPAD. Thanks...
              Dean Salman

              Comment

                #8
                Hi Dean,

                I just want to make sure that you didn't misunderstand me. I use SPAD.neXt as well to set up my various hardware devices. However, I have my pitch, roll, yaw, throttle, and brake axes all set in MSFS itself. If SPAD.neXt crashes, I can still fly the aircraft. I can't use my other controls until I restart SPAD.neXt, but all of the really important controls will still work. I'm not recommending configuring all of your controls within MSFS, just the critical axes that will allow you to still control the aircraft if you lose SPAD.neXt or FSUIPC. As long as the sim keeps running, you will still be able to control the aircraft.

                As for SPAD.neXt's stability, I have had two flights where SPAD.neXt quietly shut down and I didn't realize it until I tried to use one of the controls on my yoke and nothing happened. Neither occurrence happened during a critical phase of the flight, and I was able to restart it and it ran fine for the rest of the flight. No idea what happened in either case.
                Tim Lincoln
                My YouTube Channel

                Comment

                  #9
                  Originally posted by Want2BFlyin View Post

                  The trouble with this is that both SPAD.neXt and FSUIPC are external programs. If whichever one you are using decides to crash while you are on short final, well there go all of your controls with it. If you have your pitch/roll/yaw/throttle configured directly in the sim, then you will still have those controls even if all of your other configured controls disappear.
                  This is no argument, sorry.
                  I use Axis And Ohs for my assignment, in MSFS i have only empty profiles for all controllers.
                  In 1 1/2 years that i use this setup AAO has not crashed one time. So the chance that the FS crashes is way higher.
                  The biggest advantage of AAO for me is, that i have a template for every single aircraft i use and when i load any of these aircraft, the right template loads automaticaly.
                  ​​​​​And of course that you can assign functions that use other variables than the FS standard.
                  Regards from EDKF,
                  Markus Hardt

                  Comment

                    #10
                    Originally posted by HaMa View Post

                    This is no argument, sorry.
                    I use Axis And Ohs for my assignment, in MSFS i have only empty profiles for all controllers.
                    In 1 1/2 years that i use this setup AAO has not crashed one time. So the chance that the FS crashes is way higher.
                    The biggest advantage of AAO for me is, that i have a template for every single aircraft i use and when i load any of these aircraft, the right template loads automaticaly.
                    ​​​​​And of course that you can assign functions that use other variables than the FS standard.
                    This is most certainly a valid argument. There is absolutely no such thing as a perfect piece of software. With any modest amount of complexity, the chances of problems with the software increase tremendously. Add in the need to communicate with another piece of software, and it goes up much more. Include the need to communicate with one or more pieces of hardware as well, and you have just vastly increased the possibility of problems once again. Yes, software like FSUIPC, SPAD.neXt, and AAO are generally fairly stable, but you can never be absolutely certain that they won't disappear on you in the middle of your flight.

                    You trust AAO, and that's fine. I use SPAD.neXt, and I generally trust it as well, but I don't have my pitch, roll, yaw, brake, and throttle axes configured in SPAD.neXt. Those axes configure just fine within MSFS, are generally the same for all aircraft (except for the throttle axes), and I am 100% certain that if SPAD.neXt were to disappear during a critical phase of flight, I can still fly the aircraft. That would not be the case if those axes were configured in SPAD.neXt. In fact, the aircraft would be completely uncontrollable if SPAD.neXt happened to disappear during takeoff or landing (or even during taxi) if I had those axes configured within SPAD.neXt. I trust SPAD.neXt, but not that much.
                    Last edited by Want2BFlyin; 10May2023, 03:32.
                    Tim Lincoln
                    My YouTube Channel

                    Comment

                    Previous template Next
                    Working...
                    X