!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content
jackjoe

A330 GO AROUND FMA Shows G/S LOC

Recommended Posts

Hi,

 

after setting THR LVRs to TOGA detent it does not change to MAN TOGA and remains in G/S LOC.

 

Regards
JJ

 

A330-GA.thumb.png.6d89a8c3a3d9df4c6e0e431413b4c67c.png

Share this post


Link to post
Share on other sites

Something else has to be wrong because you are in TOGA LK.

Can please show a screenshot during Appr before you apply GA?

We need to see PFD, FCU and PERF page.

Second screenshot when you perform the GA.

 

Share this post


Link to post
Share on other sites

Thanks for the reply!

Here are the screenshots of another try. In this case its not TOGA LK its MAN TOGA.

Regards

 

 

PFD.png.7d130a63a3406eb24a3ef7b9fea7080e.png

PERF.png

FCU.png

MAN_TOGA.png

Share this post


Link to post
Share on other sites

Thanks, I have to test myself. But will take some time, I’m in holiday.
How does it react if you approach with managed speed?

Share this post


Link to post
Share on other sites

Its just the same Bob.

Reason for not using managed mode is just another issue - I get a constant SPEED, SPEED warning.

 

Best regards
JJ

 

 FCU.thumb.png.41b74b8eb970d00656dd312ff7b17082.png

PFD.png

CDU.png

Share this post


Link to post
Share on other sites
1 hour ago, jackjoe said:

Its just the same Bob.

Reason for not using managed mode is just another issue - I get a constant SPEED, SPEED warning.

 

Best regards
JJ

 

 FCU.thumb.png.41b74b8eb970d00656dd312ff7b17082.png

PFD.png

CDU.png

Last time I did a GA all was working fine. Will get back after holiday.

Instead selected you can also enter manually a higher VAPP at the appr page.

Share this post


Link to post
Share on other sites

Hi,

 

I'm still having this issue regardless of the kind of APP or the FMA Modes at setting the THR Levers to TOGA.

Is there any solution to it or did somebody experience the same?

 

Regards

Share this post


Link to post
Share on other sites

I made a go-around and I it was quite normal

My Throttle was in CLIMB mode and I pushed it fully forward to MAN TOGA

SRS and NAV is visible and go-around altitude is blue

 

It seems that You are not fully in TOGA mode as GS and LOC are still visible and 

go-around altitude is white..

 

What type of Throttle are You using...??

Go around.png

Share this post


Link to post
Share on other sites

Its the "CH Throttle Quadrant".

 

If I get the "MAN TOGA" as in your screenshot the rest of the FMA modes remain in whatever mode it was before pushing the throttles to TOGA.

Share this post


Link to post
Share on other sites

Have You checked that Throttle on Piedestal moves to TOGA when You make go-around......

 

I found This

 

"Please check the following:

- Your Airbus Configurator: if you have 1 or 2 throttle tickbox checked.

- Calibrate your CH TQ through the CH Manager and assign the throttle via P3D menu instead fsuipc.

I have the AS320 in P3D v3.2.5 with CH Throttle Quadrant configured as said above with no issues at all. Hope it helps."

Share this post


Link to post
Share on other sites

Thank you!

Calibrating the CHTQ was the right hint, now the GA is OK with SRS & NAV.

 

BUT each time after starting a new SIM session and a 330 flight I have to PAUSE the SIM and CALIBRATE AGAIN!

How could that be? 

 

I never would have thought of this since I never had to calibrate in over 5 years with numerous addon aircraft.

Share this post


Link to post
Share on other sites

 "Calibrate your CH TQ through the CH Manager and assign the throttle via P3D menu instead fsuipc.

I have the AS320 in P3D v3.2.5 with CH Throttle Quadrant configured as said above with no issues at all. Hope it helps."

 

Copy the text above and search on the Net by pasting it and I think You can find a solution out there...:))

 

Share this post


Link to post
Share on other sites

I forgot in the previous post to mention that I had tried to "assign the throttle via P3D menu instead fsuipc". 

That was a real mess - throttle 2 didn't move at all. Looks like something is wrong with my CHTQ. I'll check that.

 

Anyhow I would never ever sim without FSUIPC.

Share this post


Link to post
Share on other sites
On 2/19/2020 at 1:05 AM, jackjoe said:

I forgot in the previous post to mention that I had tried to "assign the throttle via P3D menu instead fsuipc". 

That was a real mess - throttle 2 didn't move at all. Looks like something is wrong with my CHTQ. I'll check that.

 

Anyhow I would never ever sim without FSUIPC.

 

@jackjoe Can you remember if in your situation the Thrust Lever 1 reach TOGA detent, even that Lever 2 didnt move?

Share this post


Link to post
Share on other sites

I've helped correct a issues that several people have had with FSUIPC / P3D thrust lever setups.  I realize part of this may not make sense, but give this a try:

 

1. Rename, or cut and paste your FSUIPC.cfg file so that it is no longer recognized by FSUIPC.

2. Start P3D and remove and reassign the thrust levels, do not change the calibration settings, and then test in the aircraft. 

3. If you wish to have to use FSUIPC for the Airbus (not our recommendation), then first remove the P3D control bindings, close and restart P3D, and then close P3D again.  Then restart P3D and rebind the Airbus controls in FSUIPC. 

4. Close P3D, copy and past non-Airbus aircraft entries from your previous FSUIPC.cfg file to the new FSUIPC.cfg, except of course for the newly created FSUIPC Airbus bindings.

 

Let us know how you make out.

 

Share this post


Link to post
Share on other sites

Hi Dave,

 

I renamed the FSUIPC.cfg and assigned the throttle axis in P3D but the issue is the same. FMA shows MAN TOGA GS LOC.

But I think I found the cause of this. Calibrating the CH-THR-Qudrant with the CH-Utility then the FMA changes to SRS and NAV regardless of the axis assigned in P3D or FSUIPC.

And I don't have any other issues with FSUIPC and the throttle setup.

 

But then with the CH-Quadrant-Throttles in idle detent the engines are in REV-Thrust on the ground.

This is also true for the PMDG 37 and 47 and the QW 787. I have to advance the throttles a considerable way out of the idle detent for forward idle thrust.

There is no way out but using the CH-Delete-Utility to delete the throttle calibration. 

 

But why does the 330 not change to the TOGA-mode despite the throttles in the VC move all the way to the forward stop or TOGA detent and the FMA shows MAN TOGA?

 

Hope you have a solution for this.

Thanks

 

Share this post


Link to post
Share on other sites

The thrust levet3and modes wirk withmy Saitek, Thrustmaster, and are known to work with many other thrust levers so I really have no idea why they aren't working for you, though something like like this is usually calibration.

 

Perhaps asking CH Products?

 

Share this post


Link to post
Share on other sites

I contacted CH Products. So wait and see.

 

But nevertheless should not the 330 change to TOGA-mode with the throttles in the respective forward detent?

Share this post


Link to post
Share on other sites
13 hours ago, DaveCT2003 said:

something like like this is usually calibration.

 

Share this post


Link to post
Share on other sites

I did not mean the hardware or CH Throttle detent ...

 

On 24.2.2020 at 19:29, jackjoe sagte:

But why does the 330 not change to the TOGA-mode despite the throttles in the VC move all the way to the forward stop or TOGA detent and the FMA shows MAN TOGA?

 

 

looks like this is also an A330  issue - in 5 years of FSX and P3D with CH Throttle never any problem and never had to calibrate before

Share this post


Link to post
Share on other sites
10 minutes ago, jackjoe said:

I did not mean the hardware or CH Throttle detent ...

 

 

looks like this is also an A330  issue - in 5 years of FSX and P3D with CH Throttle never any problem and never had to calibrate before

 

It may look like this to you because of the calibration, but I never experience this with my thrust levers nor have I provided support to anyone who has had this issue.  Thus at this point I have to assume it's a calibration issue or bad pot, so I believe CH is the one to help you sort this out.  To be blunt, I do not believe nor do I see any indication this is caused by our software and nobody else has this issue my friend.

 

Please let us know how you make out with CH Products?

 

Best wishes.

 

 

Share this post


Link to post
Share on other sites

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...