Jump to content
Secondator

Managed speed issues

Recommended Posts

5 hours ago, noahharget said:

Description of the issue:

Either loosing speed during climb or at cruise ...

Hi,

did you try to disable the "checklist" in the 2nd MCDU?

Disabling "Checklist" in my case has solved the speed issue in both climb and cruise phases. BTW, my version is 1.2.3.0.

Paul

Share this post


Link to post
8 minutes ago, Paul St Laurent said:

Hi,

did you try to disable the "checklist" in the 2nd MCDU?

Disabling "Checklist" in my case has solved the speed issue in both climb and cruise phases. BTW, my version is 1.2.3.0.

Paul

I have not, so you mean to tell me that disabling the first officer checklist could be a temporary fix?

Share this post


Link to post
1 hour ago, Paul St Laurent said:

Hi,

did you try to disable the "checklist" in the 2nd MCDU?

Disabling "Checklist" in my case has solved the speed issue in both climb and cruise phases. BTW, my version is 1.2.3.0.

Paul

hmmmm....could the aircraft be entering approach mode prematurely?  That's the only interaction I believe the first officer has with the A/T?  

Share this post


Link to post
2 hours ago, Paul St Laurent said:

Hi,

did you try to disable the "checklist" in the 2nd MCDU?

Disabling "Checklist" in my case has solved the speed issue in both climb and cruise phases. BTW, my version is 1.2.3.0.

Paul

Interesting, this would explain why a friend of mine, who does not use the checklist, has never had the speed bug, and so many other people and developers...

So the first question is:

is there someone who suffered the bug that was not using the auto checklist?

Share this post


Link to post
4 hours ago, klisura said:

Interesting, this would explain why a friend of mine, who does not use the checklist, has never had the speed bug, and so many other people and developers...

So the first question is:

is there someone who suffered the bug that was not using the auto checklist?

 

I don't use the auto checklist and still have this issue.. 

Share this post


Link to post
vor 3 Stunden , aleksanderl sagte:

 

I don't use the auto checklist and still have this issue.. 

 

Same here!

Share this post


Link to post

I haven't been using the checklist/copilot and I have had the bug several times (though not since updating to 1.2.3.0).  However, I do have those features turned on in the MCDU3 Options, I just haven't been initiating them at any time (I use FS2Crew).  I don't believe I've changed options settings since the update.

Share this post


Link to post

Thanks for all the reports so far!

We have been able to get some clues what kind of other anomalies people are having while the issue happens. Those who are experiencing the issue, could you please take some screenshots of various PERF pages (preferably with PFD in view as well) and report if you see any anomalies there (especially on distances). Also let us know what speed the drop fall into for you and if DES/CLB is still working somewhat correctly with the selected speed or is it calculating the aircraft below profile.

Videos, where all this is shown, would be best if you are able to take them. 

We understand how frustrating this is for some of you. It's one of our top priority issues to get our head around. Since users experiencing this issue are really the only source we have for investigation right now, we are thankful for all details you can provide so that we can get an idea what is causing this and how to fix it.

Share this post


Link to post
1 hour ago, Secondator said:

Thanks for all the reports so far!

We have been able to get some clues what kind of other anomalies people are having while the issue happens. Those who are experiencing the issue, could you please take some screenshots of various PERF pages (preferably with PFD in view as well) and report if you see any anomalies there (especially on distances). Also let us know what speed the drop fall into for you and if DES/CLB is still working somewhat correctly with the selected speed or is it calculating the aircraft below profile.

Videos, where all this is shown, would be best if you are able to take them. 

We understand how frustrating this is for some of you. It's one of our top priority issues to get our head around. Since users experiencing this issue are really the only source we have for investigation right now, we are thankful for all details you can provide so that we can get an idea what is causing this and how to fix it.

 

Share this post


Link to post
17 minutes ago, Jose Zubillaga said:

hello everyone upload problem video when descending

83F6FB5E-56F9-4A58-A5F3-A28805E0612B.MOV


Hello Jose! Steep dive issue is whole another issue and not related to this one. There is already a thread open about this one, and we are aware of it and already working for a fix.
 

 

11 minutes ago, aleksanderl said:


Thanks for the video. We are especially interested in what various PERF pages show while the issue is present. So if possible, could you take one which shows different FMGC perf pages. Thanks! :)

Share this post


Link to post

OS: Win 10 Pro

4790K

16GB RAM

GTX 1070FTW

P3D v 4.4 (most current one)

Airbus version 1.2.2.0

ASP4, ORBX, Flightbeam

 

KDEN-KPDX, Route: FOOOT4.RLG..EKR..BOI..JOTBA.HHOOD4

FL360

 

Running fine in managed speed mode at .79 Mach.  I did switch to some exterior views using the default commands in P3D bound to my TM 1600M, came back into cockpit view and speed dropped to 219 kts approaching BOI intersection.  Went to manual speed mode until TOD.

 

Could changing views cause the managed speed mode to drop?

2019-2-3_10-38-17-542.jpg

Share this post


Link to post

As luck would have it, just did test flight #2 for myself, and was all ready to take the videos, but no issues!

 

KBUF - KDTW

A319CFM

FL360

Route:  DONEO  CUUGR1

 

Engaged AP/AT around 2000' AGL in managed mode, flew the entire flight just fine. No speed issues noted, and descent profile was correctly calculated. Each speed/alt restriction along the STAR was met with no problem.

 

I'll try a third test flight later today and report back.

Share this post


Link to post

@BuddyDog You are using an outdated version. Please uninstall your current Airbus, remove any remaining folders, reboot your PC, install the latest version 1.2.3, reboot and try again.

Share this post


Link to post
16 hours ago, BuddyDog said:

OS: Win 10 Pro

4790K

16GB RAM

GTX 1070FTW

P3D v 4.4 (most current one)

Airbus version 1.2.2.0

ASP4, ORBX, Flightbeam

 

KDEN-KPDX, Route: FOOOT4.RLG..EKR..BOI..JOTBA.HHOOD4

FL360

 

Running fine in managed speed mode at .79 Mach.  I did switch to some exterior views using the default commands in P3D bound to my TM 1600M, came back into cockpit view and speed dropped to 219 kts approaching BOI intersection.  Went to manual speed mode until TOD.

 

Could changing views cause the managed speed mode to drop?

2019-2-3_10-38-17-542.jpg

 

Just read this.....

Back in December I made several flights with the A320 using airways that crossed the BOI waypoint.

I had speed control issues somewhere around that point as well.

Wondering if there are potential Navigraph issues?

Share this post


Link to post

Ok, so test flight number two yesterday (KDEN-KSLC) and I had no issues.

 

Just encountered the issue now on test flight number 3:

KPHX-KLAX

FL300

A319CFM

ROUTE: KEENS2 MESSI ESTWD HLYWD1

 

Takeoff and climb were rather uneventful, and the first part of cruise as well.  While cruising at FL300, just before the MCGWN waypoint, the commanded speed (magenta indications on PFD) suddenly dropped to 198 KIAS. The speeds next to the waypoints on the flight plan page continued to show appropriate cruise speed and altitude, but the A/THR had other plans. (If you look at the DES page, you can see that the 198 commanded appears to be the descent speed, although it doesn't match the mach number also listed for descent.) I gave it a few minutes to see what it would do. It was very content flying that speed, and thus entered ALPHA FLOOR protection mode, while continuing to try and command 198 knots, which also resulted in a slow gradual descent (this doesn't seem right, from everything I read online when A/FLOOR mode is engaged, the A/THR should immediately command TOGA thrust? Which it didn't do.)

 

After several attempts at disconnected and reconnecting both A/P and A/THR in order to recover from A/FLOOR mode, I was able to dial in a selected speed, which it followed.  If I tried to re-engage managed speed, the wrong speed was again commanded, so I just left it an selected mode.

 

I've attached a link to the video (too big to upload), as well as a .zip file; the zip file contains all log files, flight plan, saved flight files from after pre-flight (before takeoff), after takeoff (when everything was fine), while the problem was occurring, and then after I recovered.

 

Hopefully this can help you shed some light on the issue.

 

Thank you!

 

Video Link:  

 

KPHX-KLAX.zip

Share this post


Link to post

@med11043 Hi. Help me get some more insight. How did you get to A.Floor? Did ATHR command THR IDLE on FMA? Was there any change on the FMA? How did the thrust levers behave?

 

There will be an update soon with more detailed logging for this issue. I am not able to reproduce this issue on any of my PCs so please if possible reproduce it with new update and send over the same set of files. I hope to narrow it down a lot with your help.

Share this post


Link to post
26 minutes ago, RobsonM said:

@med11043 Hi. Help me get some more insight. How did you get to A.Floor? Did ATHR command THR IDLE on FMA? Was there any change on the FMA? How did the thrust levers behave?

 

There will be an update soon with more detailed logging for this issue. I am not able to reproduce this issue on any of my PCs so please if possible reproduce it with new update and send over the same set of files. I hope to narrow it down a lot with your help.

Yes, sorry.

As soon as the commanded speed dropped to 198 on PFD, A/THR commanded idle thrust (apparently) in an attempt to slow to that speed. Once it did, the thrust seemed to stay at idle, hence the A/FLOOR and then a gradual descent as, I assume, the only way it could maintain that speed without stalling?

 

As soon as it went into A/FLOOR moving the throttles would not do anything, no matter what I did. (It looks like this may be somewhat normal airbus behavior, but it should command full TOGA thrust?)

 

I disconnected the autopilot, then tried to disconnect the autothrottle so I could recover from A/FLOOR, but the auto-throttle would not disconnect. I then reconnected autopilot and tried again.  After doing that several times, while moving the throttle levers all over the place, the throttle levers finally started responding.  The thrust mode changed to THR/LOCK, which I was then able to override by disconnected then reconnecting auto throttle (after moving thrust levers to idle), then I moved the lever back to the CLB detent, at which point I was able to go into selected mode, select a speed (in this case I did 290 knots), which the auto-throttle then increased the thrust until meeting that, and I was able to hold 290 knots in selected mode.

Share this post


Link to post

Thank you for your help!

Yes as soon as the update is out I will download it, then try to re-create this flight and send over the same files.

 

Thank you

Share this post


Link to post

I have had this issue in all released versions since I first downloaded the product on October 30, 2018.  The issue has occurred on every flight either during climb or cruise and I have not successfully flown a single flight so I can understand some of the frustration being expressed here.  The issue has occurred with and without checklist and with and without co-pilot.  I have no add-on weather package or anything else.

It is not clear if the development/debugging team has received enough customer input on the issue - but under the theory that too much is better than too little I am attaching a saved flight that always results in the issue and a log file up to the point where things start to go wrong.

The specifications of my configuration are as follows:

A320-A321 Professional version 1.2.3.0

Prepar3d version 4.3.29.25520

Windows 10.0.17134

Hardware i7-7790k, 16 gb memory, m.2 SSD

 

Very much looking forward to resolution of this issue

 

dberkele managed speed issue.zip

Share this post


Link to post
4 hours ago, dberkele said:

I have had this issue in all released versions since I first downloaded the product on October 30, 2018.  The issue has occurred on every flight either during climb or cruise and I have not successfully flown a single flight so I can understand some of the frustration being expressed here.  

 

 

I understand this is frustrating, But as you will have seen here there are dozens of reports of people NOT seeing any problems in flights and it took us weeks to find the conditions that made it reliably reproducible on our test machines. If it happens in every flight on your machine there simply HAVE to be additional factors.

Share this post


Link to post

Hello, I have still the issue with loosing mangaed flight speed now only at cruise. I just flew some days not with the aerosoft so i wantet to do a flight again with the aerosoft airbus. I flew from EDDH to LIRF with the A320 CFM. i was doing some thing in my home and suddenly i heard the sound from Airbus and i saw that the Airbus was only 140 fast in stall speed with toga lk activatet and already lightly stalling the managed speed droped in the mid of the cruise to 120 knots. on climb was all good. That bug become for me more and more frustrating it make no fun to fly this plane with this bug.

 

I have a clean reinstall of Windows 10

(GTX 970

CPU: Intel 6700 k at 4.5

16 gb ram

 

i use p3d v4.4 ( clean reinstall too)

The airbus has the newerst version 1.2.3.0 and i have installed it with administrator rights and antivirus was off.

 

i had this problem few weeks ago too see my older post. But there was the problem already on climb in this flight only on cruise.

 

Share this post


Link to post

I reinstalled 1230. Flew SAN-PHX.

This time before pushback, I moved my joystick slider full forward(max power), kept them there and used my keyboard for throttles. No speed problems. However using Nav Data Pro the speed target would not change for speed contraints until crossing the waypoint so I would always be to fast.

Greg

Share this post


Link to post

I, too, am having speed issues with version 1.2.3.0.  So, how does one "turn on logging."  And then, where do I find these logs to view afterwards?

 

Just an aside question, when the bus hits the top of climb, is the indication on the ECAM supposed to turn from "CLB" to "CRZ?"  Or, is that just an indication of the throttle detent setting?

 

Thanks!

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...