Sign in to follow this  
Graham Nicol

737 NGX Auto Throttle Disconnect Question

Recommended Posts

Hi,

 

Having just updated my 737-600/700/800/900 today from SP1C to SP1D and I have noticed one change so far, that I'm not sure is intended....?

 

When the 737 auto throttle was disconnected before the update, it required two pushes; 1. to disconnect 2. to supress the flashing A/T warning light.

 

After updating to 1D, the warning light flashes once then extinguishes after only one press of the switch.

 

Have only tried it so far on my current test flight in the -800, but wondered is this a change, or is it now a configurable items tucked away somewhere? Is anyone else noticing this?

 

Many thanks in advance,

 

Graham.

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

As far as I know for P3D and the latest version of the NGX the AT works as you described above requiring two presses. How are you disconnecting the AT? Interfaced through FSUIPC or keyboard assignment or something else? 

Share this post


Link to post
Share on other sites

Hi Angelo

 

Disconnect is being done on a button key assignment (set in FSUIPC and matching the PMDG key assignment), but it also does this when clicking the A/T disconnect button on the panel with the mouse.

 

It also happens when doing the key presses on the keyboard...so no FSUIPC involved at that stage.

 

That's how I've always done it, but now after SP1d, a single push and no on-going warning light flash.

 

Graham.

Share this post


Link to post
Share on other sites

The AP requires two pushes of the button, one to disconnect AP and the second to silence the alarm. The AT only requires one to disconnect. NO alarm other than a light which quickly goes out. Doesn't matter if you activate the switch either via a mouse or key assignment, result is the same.

Share this post


Link to post
Share on other sites

Bob,

 

I agree that's what happens, but before the AT kept flashing to highlight the fact that AT had disconnected. No aural alerts before either, hence checking whether this is an intentional change. Having flown a full motion 737 recently, even that had the AT warning flash that required a second press to extinguish the warning light (no aural alert  just the light and hence the double press, which after SP1d is no more it seems...).

Share this post


Link to post
Share on other sites

I recall the 737 behaving this way as well. I know these are different airplanes but the 777 is in the same family, the MD11 and 777 both had you press AT Discon twice to clear the visual warning. 

Share this post


Link to post
Share on other sites

Bob,

 

I agree that's what happens, but before the AT kept flashing to highlight the fact that AT had disconnected. No aural alerts before either, hence checking whether this is an intentional change. Having flown a full motion 737 recently, even that had the AT warning flash that required a second press to extinguish the warning light (no aural alert  just the light and hence the double press, which after SP1d is no more it seems...).

 

It's definitely still there. Perhaps you have your FSUIPC button set up to repeat while pressed.

 

Full names in the forum, too, please - first and last.

Share this post


Link to post
Share on other sites

Kyle,

Def not a FSUIPC issue as the keystroke command does the very same thing. Also, the FSIUIPC has no repeat ticked.

Share this post


Link to post
Share on other sites

Kyle,

Def not a FSUIPC issue as the keystroke command does the very same thing. Also, the FSIUIPC has no repeat ticked.

 

You definitely have to press it twice to cancel the flashing.

 

Also - the forum name thing is a requirement for the body of your text, as you can see here:

 

\/ \/ \/ \/ \/ \/ \/ \/ \/ \/

Share this post


Link to post
Share on other sites

Name changes duly made, but problem still exists AFTER upgrading to SP1d.

 

But I guess what you're really saying is, there is no answer. I know what it is meant to do, the whole point is it doesn't.

 

Back to 1c it is then...waste of a day.

Share this post


Link to post
Share on other sites

 

 


Name changes duly made

 

Thank you.

 

 

 


But I guess what you're really saying is, there is no answer. I know what it is meant to do, the whole point is it doesn't.

 

On your computer...

 

 

 


Back to 1c it is then...waste of a day.

 

Sorry, but that's not something that was caused by SP1d.

Share this post


Link to post
Share on other sites

It's only my computer I'm concerned with...and it was only performing the 1d upgrade that caused the issue.

 

But I now understand that there's no support for such things, so no problem, I thought I'd give it a go.

 

You can delete the thread now as it's of zero value to anyone :)

Share this post


Link to post
Share on other sites

You definitely have to press it twice to cancel the flashing.

 

Also - the forum name thing is a requirement for the body of your text, as you can see here:

 

\/ \/ \/ \/ \/ \/ \/ \/ \/ \/

 

If I use the mouse to turn off AT switch, the AT light continues to blink until I click on the light. If I use the joystick via FSUIPC ( sends AT Arm command, not set to repeat), the light goes off immediately. 

Share this post


Link to post
Share on other sites

It's only my computer I'm concerned with...

 

Right, but if it was a problem with our code, it would be a problem on more than just your computer.

 

The implied issue there was "there is something on your computer preventing our software from working properly." In other words: "it isn't a problem with our code."

 

 

 

But I now understand that there's no support for such things

 

Not sure what you're saying with this.

 

 

If I use the mouse to turn off AT switch, the AT light continues to blink until I click on the light. If I use the joystick via FSUIPC ( sends AT Arm command, not set to repeat), the light goes off immediately. 

 

The sim AT Arm? That isn't the AT disconnect set in the FMC Menu, so that would make sense.

Share this post


Link to post
Share on other sites

Well, I'd suggest there's certainly potential for code or other issues, given the precarious nature of the Sp1c to SP1d update. Having read all the issues that came out of that on these forums, a process that subsequently requires manual file deletes in addition to the normal uninstall routine leaves some questions as to how well that routine was tested.

 

As to the "no support" comment; You've demonstrated my point with your previous statement in the post above. In essence saying, you (the customer) has a problem, it's your machine, your problem and not PMDG's.

Share this post


Link to post
Share on other sites

 

 


Well, I'd suggest there's certainly potential for code or other issues, given the precarious nature of the Sp1c to SP1d update. Having read all the issues that came out of that on these forums, a process that subsequently requires manual file deletes in addition to the normal uninstall routine leaves some questions as to how well that routine was tested.

 

It was a suggestion to be absolutely sure there wouldn't be any issues. It's not necessary, but it's something we recommend to our beta teams to be sure older files aren't hanging around. I'm failing to see how it is "precarious." Sounds more like there's an agenda here for some reason...

 

 

 


As to the "no support" comment; You've demonstrated my point with your previous statement in the post above. In essence saying, you (the customer) has a problem, it's your machine, your problem and not PMDG's.

 

Correct. If this were truly an issue with our code, it would occur on more than just your computer. The fact that this isn't all over the forum, and not on my computer, suggests that the fact of the matter is that something is interfering on your computer, or something in your setup.

 

We cannot realistically write code that is specific to each and every possible processor, hardware, and third-party add-on that exists out there. A little bit of troubleshooting is going to be required in simming, regardless of who writes the software.

Share this post


Link to post
Share on other sites

No agenda whatsoever, other than trying to get something working that used to work.

 

I've not asked for PMDG support before, but thought I would try today...

 

Agree about troubleshooting and asking the question here seemed reasonable to me.

 

Regardless, I have now "solved" the problem by regressing to my working image which uses SP1C, where once again it all works.

 

As I said, feel free to delete the thread as no-one will learn anything about solving this issue if they experience it.

Share this post


Link to post
Share on other sites

Kyle, All,

 

Just an update to let you know that a simple uninstalling and reinstalling the PMDG updates worked this time (from my good baseline).... i.e. the A/P disconnect now works exactly as before.

 

the difference? The only thing I didn't do is delete the various files mentioned in the Sp1d upgrade threads. This may be coincidence or, it may have been a factor on my individual installation...no idea, but either way it now works.

 

Update: oops, spoke too soon. AT disconnect flashes just once on turning off using AT Disconnect sw, no 2nd press needed; Turning AT Arm off flashes continuously until AT Dis is pressed. again So still not right for some reason :-/

 

Regards,

Graham.

Share this post


Link to post
Share on other sites

This looks to be a conflict with FSUIPC. Try a clean reinstall with no old files.

 

Reading Bob's posts he is not configured correctly either. He states that using the mouse he clicks once on the A/T disconnect and once more on the A/T blinking red light to extinguish. That equates to two pushes on the controller button. The way it should be.

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
Sign in to follow this