[Managed speed issues]

Just had an event today after many flights with no issues......

 

Operating System:

Windows 10 Pro Ver 1803 Build 17134.472
 

Simulator version:

P3D v4.4  (4.416.27077)

Airbus version:

Updater: 1.3.0.1

A320 1.2.3.1

 

Add-ons in use:

FSUIPC5 (FS-Products ACARS), Navigraph 1902, ORBX SC/NC/NRM/PNW  (Note: Clear Skies ASP4 is installed/available but not enabled on this flight)

 

System specs:

Asus Maximus IX Hero,i7-7700k CPU @4.2 GHz, 32GB Ram, EVGA GTX1080, SSD's. System build April 2017. All recent updates applied.

Description of the issue:

Flight Plan Extended: YPPH N0120F360 KEELS5 MERIB T12 XMX G209 TKG CARL1A WIII

 

During the Descent phase the PFD speed dropped to 190 although it should have been B280 according to the STAR. It almost looks like it decided to use the Approach speed. I also noticed that the speed select indicator on the PFD kept jumping up and back down as if it wanted to go up but was being told to keep down during this period. I changed to using the manual speed knob during the descent and all was well. I switched to managed speed when the speed was to be at 190. The rest of the flight was normal.

Are you able to reproduce the issue? If so, what are the exact steps you are taking for this issue to happen?

After at least 8 flights with no issues this happened.

Additional information (route, weights, special area where the issue occurred etc.):

I have attached the logs, flight plan and load sheet use for this flight all in one zip file. I could only grab a screen shot of the vc at the time.

 

A320_Data_DRW_2019-Feb-19.zip

 

 

[Managed speed issues]

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?

 

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?

[Managed speed issues]

Now getting back after my manually entered constraints.

YSSYYMML01

64LOC ANKUB SBKWI KADOM A576 PKS Q94 CANTY ARBE2A

Each of the first four departure waypoints were given different altitudes and speeds.

AP was engaged before 64LOC.

All speeds and altitudes were maintained. This is something that I had yet to see with the new bus.

The ND markers also seemed to match the plan.

 

I will now have a look at injecting weather to see if that has any effect.

 

[Managed speed issues]

Hello again,

I have now completed two more flights with the A320 United. The last flight was from Brisbane to Sydney at FL340

HUUG06 HUUGO H62 CORKY H12 BOREE BORE9P

Rwy 19 to 16R

Weather was CAVOK with no external weather engine.

I used Navigraph 1902.

I did use my multiplayer JoinFS (simconnect) and my ACARS (FSUIPC) with flight saves every 30 minutes.

I had full logging turned on.

The SID contained a speed restriction while the STAR had both BxxxxAxxxx and specific altitudes. It also had a speed restriction at one STAR waypoint.

This seemed to have everything in it that had not worked in previous versions.

In full managed mode for the entire flight every speed restriction was met as were all of the altitudes.

It is hard to complain when everything seems to be working.

 

My next flight will use manual restrictions for speed and altitude to see if there is a difference between Navigraph generated characteristics and manually entered ones.

 

One thing that I continue to see is the MCDU showing an altitude that does not match the one that is being flown.

Image attached showing two mcdu views for the same waypoint.

 

 

[Managed speed issues]

Greetings,

I have waited quietly in the wings in anticipation of the new "full" version.

I removed both of the full installs (A318/319) & (A320.321). I also removed all folders in "My Documents" that had anything to do with Aerosoft.

I then purged all remnants using CCleaner followed by a defrag. A reboot was completed.

I then installed the new versions and rebooted. I then updated my Navigraph.

I added no paints.

 

Today I tried my first flight with the A319. A plan was created in Australia YPDNYPTN14 with SID LAKUP4 and a ILS-Y OM14 approach. The level was FL190.

The departure had an altitude restriction A3000 and B5000 at different waypoints along with a 600 foot intersection turn after takeoff. A bit of a task.

After take off the AP was turned on just before the A600 waypoint. The copilot and flight system worked flawlessly.

I watched with hands off and the plane climbed to 5000 and stayed there until it passed the ALT restriction. Just after passing the plane started to climb to 10000.

It levelled off a bit at 10000 and allowed the speed to reach 300 then began a feisty ascent to FL190.

At TOD it started to descend and also reduced speed to ~280 (had to add some speed brakes here).

After ILS Loc captured I still got the wing wave after a bit. Close to GS I enabled App. The plane flew in like a happy bird with no wing wave near the airport.

 

So far so good....more to come later.

[Managed speed issues]

I have just completed a return flight from CYVR to KDVT. The flight from KDVT to CYVR yesterday had no problems.

On this occasion the speed problem occured. (Has happened on other flights but not all)

 

Operating System:

Windows 10 Pro Ver 1803 Build 17134.472
 

Simulator version:

P3D v4.4  (4.416.27077)

Airbus version:

Updater: 1.2.2.0

A320 1.2.2.1

Add-ons in use:

FSUIPC5 (FS-Products ACARS), Navigraph 1813, ORBX SC/NC/NRM/PNW  (Note: Clear Skies ASP4 is installed/available but not enabled on this flight)

System specs:

Asus Maximus IX Hero,i7-7700k CPU @4.2 GHz, 32GB Ram, EVGA GTX1080, SSD's. System build April 2017. All recent updates applied.

Description of the issue:

After a normal take-off and climb to Cruise the sim decided to change the cruise speed to 222. This resulted in a loss of altitude and the need to disengage AP, change to manual speed. Once recovered AP speed ,NAV and ALT were re-established. Managed speed was never recovered. Upon final approach speed was engaged for landing and all check list actions by copilot worked without issue. 

Are you able to reproduce the issue? If so, what are the exact steps you are taking for this issue to happen?

An attempt to save all logs and a special video was tried on a previous flight but no issues occurred. Today the flight was the reverse of the previous one but no video was captured and the speed issue occurred. Other flights along a similar route have also presented this issue

Additional information (route, weights, special area where the issue occurred etc.):

I have attached the logs, flight plan and load sheet use for this flight all in one zip file. I could only grab a screen shot of the vc at the time.

 

a320troublefile1.zip

[BeaverX - Any new Versions/Updates since 320 ?]

I have recently re-loaded the FSX Beaver and used my existing files to upgrade the install to version 320.

I am trying to see if there are any further updates since Version 320.

Many thanks,

Darryl Wightman