Search the Community
Showing results for tags 'ats'.
Found 4 results
-
I have now completed a few dozen flights with the Challenger. I notice that during descent, the ATS speed control is quite erratic in maintaining the FCP selected speed. For example, speed set to 240 under FL100, from current speed of 290: upon reaching 240 after the deceleration, the throttles get increased a few knots before reaching 240 and push the aircraft to ~248, then throttles get reduced by the ATS. Again, upon reaching between 243 and 240, the throttles engage again, pushing the aircraft to ~248, and back down again. I believe the ATS needs some fine tuning, as it is currently too aggressive, pushing the nose up and down, into a clear oscillation pattern. This is happening no matter what the weather is, and annoys me to a point where I often take manual control of the throttles. One thing I also notice, relating to all this, is the amber GND Spoilers alert on the MFD, as soon as you overspeed by as little as 3 or 4 knots; is this also happening in the real thing? I reckon there might be some settings related to those sensitivities somewhere in the settings, of which I am not aware; so I will be happy if someone can point me in the right direction. Thanks in advance for any help in resolving this.
-
Upon landing cannot regain throttle control after disconecting the ATS. Tried everything. Using the keyboard binds work to reduce thrust but throttle still spool to max with ATS off. Any help appreciated. (Ps. I cannot move the throttle to the popups location. No manual movement whatsoever.)
-
I have finally been able to capture an unexpected issue with ATS disengagement quickly after pushing the throttles forward after engaging TO/GA mode on takeoff. What is not so easy to see as it occurs very quickly, is a second or two after pushing the throttles forward, the ATS LED's on either side of the button "blink" and simultaneously the ATS 2-line textual display goes blank, and then I'm back to manual throttle control. In this case I pushed the throttles full forward. Most of the time, pushing them full forward (with TO/GA engaged) works perfectly as ATS engages, stays engaged and the takeoff sequence is as expected /designed. I typically use a saved state (all of my states were created on a freshly created airframe with the latest release, 1.6.1 I believe). I then reset FMS, set up the flight plan, PERF INIT, PERF TAKEOFF (from which I SEND V speeds which are correctly displayed on the PFD). I have reproduced this behavior with TO/GA engaged either before or after sending the takeoff V speeds, no difference in behavior. So I don't think when I send V speeds impacts this issue with respect to when I push the TO/GA button before takeoff roll. I have tried a variety of things in order to isolate the cause, each time thinking that I figured it out and then it recurred. Things like the timing of when FD is turned off (relative to sending V speeds for example), and TO/GA not engaged until after the V speeds are loaded, and lined up on the runway (normal procedure). Other notes: - I usually load new FMS information into the CDU (flight plan, PERF INIT, PERF TAKEOFF) and SEND V speeds before engaging TO/GA. My comment on the video about having V speeds loaded with the saved state is not relevant for this reason, so disregard that part). - No, I am not accidentally pressing an ATS DISC button, it actually is one of the buttons on the back of the Honeycomb Bravo throttle quadrant. I do have Airbus throttles on the way as they have 2 ATS-disconnect buttons (one on each throttle), and I'll make the pilot side one TO/GA, but this is not relevant for this issue. Note (edit to the above on July 25): - I have evaluated whether pushing the throttles full forward (before ATS auto-engages) could be a cause or contributor to this behavior. I believe I have proven that this is not the case / not the cause. ATS engages (as a result of TO/GA armed) before the manual throttle push can exceed the N1 limit, as far as I can tell, which makes sense to me. - I changed my airport location from KDTW (where my pre-taxi state is saved) to KORD (and used the state, but without location). The first takeoff attempt had this issue occur. Made me wonder if using a saved state without location could be related to this issue. I'll have to see if I can reproduce that behavior or not. I do not think this consistently leads to the issue. Feedback on this would be highly valued! To see the detail in the video, click the Youtube settings and select the highest video quality.
-
Hello everyone, the A.T.S. team is proudly to announce our next project for X-Plane: the McDonnell Douglas MD-11 & MD-11F. First of all let us say that we understand very well your concerns and doubts about a new project declaration when our first and actual project about the MD-82/83 is still to hit the market, so why we're doing so? Because the graphical part of the MD-82/83 is 99.9% complete: of course we keep that 0.1% for last minute fixes (if needed) resulting from the beta test phase and further upgrades, but there's absolutely no reasons to keep an excellent graphical artist doing nothing while I'm developing and testing the final pieces of code... looking at previous posted images all of you are now aware about the graphical level we want to achieve, and looking at the declaration date of the MD-82/83 project (April 2013) you can imagine how much time and effort is needed to reach that level. Other than that, for this new project we’re going to have a new resource for the art department and if things goes well we’ll have even a new resource that will help me with the code. Absolutely no time and no development efforts are, has been or will be taken away from the MD-82/83 project: MD82/83 has 100% of our time, now and mainly after we'll hit the market, so totally no worries about something such less support and/or loss of interest because a new project... for all of you should be now crystal clear that we at A.T.S. are not interested to hit the market as soon as possible with unsatisfactory products, our priority is to develop study level products and giving 100% support to our customers. Back to the MD-11, we already retrieved a good amount of official documentation and we're in touch with some active and retired MD-11 pilots that are interested to collaborate with us, so this is something whose foundations were already started not something that will start from now on... obviously there're no images to show right now and Parsec will need some time before to show something, but in this very moment we believe it's important to let all of you aware of what we'll create right after, and somewhat alongside, the MD-82/83. Thank you for your kind attention. Best regards The A.T.S. team.
.thumb.jpg.4f65b9da63688cb36ecd00649cedfd38.jpg)
