This bird was working fine the first few times I flew it.  Now after setting up the MDCU and everything as usual when I take off and down arrow the rate of climb, speed, and heading eveything stays stuck at zero.  From every Airbus I've flown virtually (FBW included) you toggle these switches right after takeoff to lock in the AOA, speed, and heading before you turn on the autopilot (that's of course if you doing something more complicated letting AP get you right on the SID after takeoff based on what you have programmed in the MCDU).  Everything was working fine initially now I have this weird problem.  Thanks in advance for any help with this nagging problem. 🥴🙃

"you toggle these switches right after takeoff to lock in the AOA" do you?

What!!!

Never done that.

----------

Positive rate..gear up

1,000ft AP ON

ON Speed Thrust to CL

PACK 1 ON

RWY turn off lights and Nose lights OFF

PACK 2 ON

ON speed retact flaps

Ground spoilers OFF

...............so just why are you messing around like that "right after takeoff"? your setting open climb right after takeoff? your not even on AP.

When your cleared to a new FLXXXX  you can go open climb, BA use open climb as there preferred climb over managed. 

Edited July 5, 20223 yr by Nyxx

It's a fly-by-wire aircraft. It will follow the climb and attitude you set with the side-stick (up to 33° bank and pitch). Once the desired attitude is achieved, you can release the side-stick and the plane will remain in the desired path.

You don't click on anything, it's not a Boeing.

Edited July 5, 20223 yr by airlinejets

48 minutes ago, airlinejets said:

It's a fly-by-wire aircraft. It will follow the climb and attitude you set with the side-stick (up to 33° bank and pitch). Once the desired attitude is achieved, you can release the side-stick and the plane will remain in the desired path.

You don't click on anything, it's not a Boeing.

I'll give it a try. 😏🙃

3 hours ago, Dillon said:

This bird was working fine the first few times I flew it.  Now after setting up the MDCU and everything as usual when I take off and down arrow the rate of climb, speed, and heading eveything stays stuck at zero.  From every Airbus I've flown virtually (FBW included) you toggle these switches right after takeoff to lock in the AOA, speed, and heading before you turn on the autopilot (that's of course if you doing something more complicated letting AP get you right on the SID after takeoff based on what you have programmed in the MCDU).  Everything was working fine initially now I have this weird problem.  Thanks in advance for any help with this nagging problem. 🥴🙃

Yeah this sounds very wrong. Where did you get that from? This sounds more like something you would do on the CRJ, if at all.

3 hours ago, Nyxx said:

"you toggle these switches right after takeoff to lock in the AOA" do you?

What!!!

Never done that.

----------

Positive rate..gear up

1,000ft AP ON

ON Speed Thrust to CL

PACK 1 ON

RWY turn off lights and Nose lights OFF

PACK 2 ON

ON speed retact flaps

Ground spoilers OFF

...............so just why are you messing around like that "right after takeoff"? your setting open climb right after takeoff? your not even on AP.

When your cleared to a new FLXXXX  you can go open climb, BA use open climb as there preferred climb over managed. 

Something must be wrong with my install.  Taking off and pressing the 'AP' 1,000ft after takeoff (wheels and flaps up) drops the nose back down to 0 and the throttle reduces to 100kts.😕  It doesn't hold the speed and AOA the plane is at during manual climb out.

Edited July 5, 20223 yr by Dillon

Did u set a target altitude in the window before TO?

The speed window and heading window and altitude window must be blank and have a dot next to them before TO

Edited July 5, 20223 yr by TrevorS

13 minutes ago, TrevorS said:

Did u set a target altitude in the window before TO?

Thats what it sounds like.

9 minutes ago, Nyxx said:

Thats what it sounds like.

Found the problem.🧐😏  All is fine if I use the 'Cold Dark' startup option.  Anything else the autopilot doesn't respond to commands after takeoff. Thanks for the help guys even though from the sounds of it I wasn't explaining my problem correctly.👍

I have used the Turnaround state for weeks now, never a problem.

1 hour ago, Dillon said:

Found the problem.🧐😏  All is fine if I use the 'Cold Dark' startup option.  Anything else the autopilot doesn't respond to commands after takeoff. Thanks for the help guys even though from the sounds of it I wasn't explaining my problem correctly.👍

A suggestion, I would watch some of the great tutorial videos on Youtube. Sounds to me like you are skipping steps that are important. 

18 minutes ago, Bobsk8 said:

A suggestion, I would watch some of the great tutorial videos on Youtube. Sounds to me like you are skipping steps that are important. 

I agree 100% but what's odd usually this applies in reverse meaning a step is missed from a 'Cold Dark' state that's otherwise accounted for in the 'Turnaround State'.  You usually never see a situation where most systems are 'On/Set' and something different needs to be accounted for versus powering up from a 'Cold Dark' state where many steps could get overlooked without a checklist.  Either way you're correct, I must be missing something.

Edited July 5, 20223 yr by Dillon

2 hours ago, TrevorS said:

The speed window and heading window and altitude window must be blank and have a dot next to them before TO

Water under the bridge by now but in case anyone might read this in the future: 1. the speed window and heading window show three hyphens ( - - - ) plus a dot in managed mode, they are never totally blank (and show numbers in selected mode without the dot), and 2. the altitude window never ever is 'blank' and ALWAYS shows the set altitude (plus a dot in managed mode or no dot in selected mode).

54 minutes ago, Dillon said:

I agree 100% but what's odd usually this applies in reverse meaning a step is missed from a 'Cold Dark' state that's otherwise accounted for in the 'Turnaround State'.  You usually never see a situation where most systems are 'On/Set' and something different needs to be accounted for versus powering up from a 'Cold Dark' state where many steps could get overlooked without a checklist.  Either way you're correct, I must be missing something.

Follow my link in my sig and use turnaround.🙂