goggi

PMDG 737NGX missing/ineffective commands?

Recommended Posts

First of all, thank you very much for such a great program. I'm a relatively new user, still experimenting, and I am in love with it.
I am running P3Dv4.2 and PMDG 737NGX.

Following your advice (from a previous ticket) here is a list of NGX controls/keys/buttons for which commands seem either missing or ineffective (I tried/searched the available commands in the documentation, plus verbiage variations, without success). Some generate a voice reply, but no action follows.
For two of them (#9, #13) there could be a workaround via VoxKey and the FMC, but for the others I (we) need your help….

Apologies if I was mistaken on some of them, in which case advice (applicable verbiage) will be most useful !
Thanks for all you do in helping us enjoying this amazing software,
Giorgio

Forward OVHD Panel:

1- Displays Panel (“Source” set to Auto, “Control Panel” set to Normal): commands not recognised or do not exist   [checked in SOP C&D Startup flow]
2- DC voltmeter knob: operates correctly for turning knob CW, just “DC voltmeter set” reply but NO action for commands turning knob CCW
3- APU Gen On: unable to switch it on (by voice command)
4- What are the commands for Transfer bus and Equipment Cooling switches?
5- There is no separate command for Retractable Landing lights (3 positions: Off, Extended, On). Used in some SOPs at T/O and Landing.

EFIS Panel:
6- Requests to Press EFIS Buttons (FPV, TFC, TERR, WPT..): Reply “EFIS display xxx Button has been pressed”, but NO action
7- Minimums: request to set DH __  or DA__  commands (On ground or in flight). Replies: “no idea”, “can’t find switch …”. NO action

MCP Panel:
8- ALT can be set at a minimum value of 800’. IAS to 113 kts. Some SOPs require setting them at 100 at Shutdown. (Is it worth it?)

FWD Panel:
9- “Start Timer” (or “Clock”) starts elapsed time. “Start Chronometer” (for timed procedures) is NOT recognised (key available in FMC Setup for VoxKey, though)
10- Used fuel counters: Reset operates but switch remains stuck in the Up position   (it should be a temporary-action spring-loaded switch)
11- “MFD select ENG” (or SYS) commands work and are acknowledged a first time, but a second ENG or SYS command (e.g. to blank the lower DU after ENG Start) have NO effect
12- It would be nice if FO could state “Autobrake disengaged” or “Manual Brakes” on manual braking, when the A/B disengage-light turns on  [he already states “Brakes Active” on landing roll]

Center Pedestal:
13- “Spoilers/Speedbrakes up/deploy”: command acknowledged (not on GND) (“got it, spoilers extended”), but NO action (on GND or in-flight)   [Keys Available for VoxKey]. This would be also useful for a 3-step (BOEING recommended) abort procedure (Retard, Spoilers, Reverse)

AFT Pedestal:
14- NO “Test Radar” (or equivalent) command
15- “Set Xponder TA”: replies “Traffic Advisory” but NO action (on GND or in flight). FO replies “AUTO” and positions to TA/RA only

 

 

 

 

 

Share this post


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

Posted (edited)
4 hours ago, goggi said:

First of all, thank you very much for such a great program. I'm a relatively new user, still experimenting, and I am in love with it.
I am running P3Dv4.2 and PMDG 737NGX.

Following your advice (from a previous ticket) here is a list of NGX controls/keys/buttons for which commands seem either missing or ineffective (I tried/searched the available commands in the documentation, plus verbiage variations, without success). Some generate a voice reply, but no action follows.
For two of them (#9, #13) there could be a workaround via VoxKey and the FMC, but for the others I (we) need your help….

Apologies if I was mistaken on some of them, in which case advice (applicable verbiage) will be most useful !
Thanks for all you do in helping us enjoying this amazing software,
Giorgio

Forward OVHD Panel:

1- Displays Panel (“Source” set to Auto, “Control Panel” set to Normal): commands not recognised or do not exist   [checked in SOP C&D Startup flow]

Will be fixed
2- DC voltmeter knob: operates correctly for turning knob CW, just “DC voltmeter set” reply but NO action for commands turning knob CCW

Will be fixed

3- APU Gen On: unable to switch it on (by voice command)

Use "connect apu generator", "disconnect apu generator". Or alias your preferred commands to these

4- What are the commands for Transfer bus and Equipment Cooling switches?

Use "transfer bus off", "transfer bus auto" (other variants like "transfer bus switch off" or "transfer bus to off" will work as well.


5- There is no separate command for Retractable Landing lights (3 positions: Off, Extended, On). Used in some SOPs at T/O and Landing.

They do exist since last year (someone requested them for Aerosoft Airbus). Just need to be enabled for this aircraft. Consider it done.

      retactable landing lights extend
      retactable landing lights retract
      retactable landing lights out
      retactable landing lights in
      retract the landing lights
      retract landing lights
      extend the landing lights
      extend landing lights
      landing lights extend
      landing lights retract
      landing lights raise
      landing lights lower
      landing lights out
      landing lights in
      raise landing lights
      lower landing lights

EFIS Panel:
6- Requests to Press EFIS Buttons (FPV, TFC, TERR, WPT..): Reply “EFIS display xxx Button has been pressed”, but NO action

They seem to be completely broken. Thanks for that


7- Minimums: request to set DH __  or DA__  commands (On ground or in flight). Replies: “no idea”, “can’t find switch …”. NO action

MCP Panel:

8- ALT can be set at a minimum value of 800’. IAS to 113 kts. Some SOPs require setting them at 100 at Shutdown. (Is it worth it?)

To prevent Fo screwing a stable final approach on autopilot, by design, Fo won't dial anything lower than 800 feet. Will probably change it to prompt whether it was really intended.

FWD Panel:
9- “Start Timer” (or “Clock”) starts elapsed time. “Start Chronometer” (for timed procedures) is NOT recognised (key available in FMC Setup for VoxKey, though)

It was an oversight. There is such command. Probably not enabled with this aircraft.


10- Used fuel counters: Reset operates but switch remains stuck in the Up position   (it should be a temporary-action spring-loaded switch)

OK, will be checked


11- “MFD select ENG” (or SYS) commands work and are acknowledged a first time, but a second ENG or SYS command (e.g. to blank the lower DU after ENG Start) have NO effect

Confirmed inconsistent.


12- It would be nice if FO could state “Autobrake disengaged” or “Manual Brakes” on manual braking, when the A/B disengage-light turns on  [he already states “Brakes Active” on landing roll]

Center Pedestal:
13- “Spoilers/Speedbrakes up/deploy”: command acknowledged (not on GND) (“got it, spoilers extended”), but NO action (on GND or in-flight)   [Keys Available for VoxKey]. This would be also useful for a 3-step (BOEING recommended) abort procedure (Retard, Spoilers, Reverse)

AFT Pedestal:
14- NO “Test Radar” (or equivalent) command

We use "test weather radar", "check weather radar", "verify weather radar". Could easily add "Test radar" to the pool of built-in commands.

Also "weather radar to test"

Something's not right here. Commands not enabled.


15- “Set Xponder TA”: replies “Traffic Advisory” but NO action (on GND or in flight). FO replies “AUTO” and positions to TA/RA only

Confirmed setting TA-RA when it should be TA only.

 

 

 

 

Thanks for reporting these.

Some were working and it appears broken for some reason.

They will be fixed this week.

Find MCE verbiage for items embedded. And don't forget, you can use your own speech commands and alias them to the built-in ones.

Meanwhile, feel free to update to latest MCE (V2.7.6.2) which adds support for QW 787

 

Edited by FS++

Share this post


Link to post
Share on other sites
6 hours ago, goggi said:

4- What are the commands for Equipment Cooling switches?

 

Forgot these. Couldn't edit original reply.

Use commands, "equipment cooling to alternate", "equipment cooling to override", "Equipment cooling to normal", "Equipment cooling to auto"

Share this post


Link to post
Share on other sites

Simply unbelievable: a complete reply on a long list of queries within few hours and on a Sunday day !
MCE Support stands at the VERY TOP of anything I experienced before. Thanks a lot.

Giorgio

Share this post


Link to post
Share on other sites
On ‎5‎/‎27‎/‎2018 at 8:22 PM, goggi said:

Simply unbelievable: a complete reply on a long list of queries within few hours and on a Sunday day !
MCE Support stands at the VERY TOP of anything I experienced before. Thanks a lot.

Giorgio

Thank you.

As they say over here, the proof is in the pudding.😃

All NGX specific issues should be sorted in latest release V2.7.6.3

The other two suggestions (Autobrake disarm and spoilers) might be implemented later. 

Share this post


Link to post
Share on other sites

Thanks for the update and the new version 2.7.6.3.
The pudding is almost done and working fine, save for three remaining points (see my previous message #s):

#2-DC Voltmeter: replies are OK, but it refuses to turn Counterclockwise
#7-Minimums: replies are given ("DH..."), but no action (e.g. "cannot find switch", "have to do it yourself ...")
#10- Reset Fuel counters: switch no more stuck, but it moves to the opposite direction (i.e. it now displays Used Fuel). Of course both settings are necessary.
Please state appropriate commands when fixed.

Thanks again,
Giorgio

Share this post


Link to post
Share on other sites
On ‎6‎/‎2‎/‎2018 at 10:22 AM, goggi said:

Thanks for the update and the new version 2.7.6.3.
The pudding is almost done and working fine, save for three remaining points (see my previous message #s):

#2-DC Voltmeter: replies are OK, but it refuses to turn Counterclockwise
#7-Minimums: replies are given ("DH..."), but no action (e.g. "cannot find switch", "have to do it yourself ...")
#10- Reset Fuel counters: switch no more stuck, but it moves to the opposite direction (i.e. it now displays Used Fuel). Of course both settings are necessary.
Please state appropriate commands when fixed.

Thanks again,
Giorgio

Download this patch

Unzip and manually replace a couple of files as per folder structure.

DC voltmeter control should work (CCW) as expected.

FO resets both FF and fuel used. Command is also secured against accidental trigger. When at least one engine is running and command isn't scripted, Fo will want confirmation to reset before going ahead.

Share this post


Link to post
Share on other sites

Thanks, it works fine.

Just 4 more points to make the PMDG 737NGX cockpit fully controllable by MCE:
1- the command: "check flight data recorder" gets the answer " testing cockpit voice recorder"
2- I cannot find a command for "Display used fuel" (or equivalent)
3- Same for setting/checking the Pressurisation mode selector (e.g. to Auto)
4- The command "Test (or check) extinguishers" (squibs) tests only the switch to the Left side, not to the Right side

I guess this is all....and thanks once more,
Giorgio

Share this post


Link to post
Share on other sites

Hi,
Continuing on the PMDG 737NGX refinements and corrections:

The "set/release parking brake" command has just a toggle logic. It does not check for the actual state of the parking brake lever. In some situations, this leads to either a wrong “the parking brake is already <state>” reply, or wrong outcomes (i.e. it being switched to the reversed state).

It is highly desirable that that the ACTUAL state be monitored, if possible, so as to have the appropriate response and action

Thanks,
Giorgio

Share this post


Link to post
Share on other sites
2 hours ago, goggi said:

Hi,
Continuing on the PMDG 737NGX refinements and corrections:

The "set/release parking brake" command has just a toggle logic. It does not check for the actual state of the parking brake lever. In some situations, this leads to either a wrong “the parking brake is already <state>” reply, or wrong outcomes (i.e. it being switched to the reversed state).

It is highly desirable that that the ACTUAL state be monitored, if possible, so as to have the appropriate response and action

Thanks,
Giorgio

It's definitely not a simple toggle.

He checks the status first, then applies the desired setting.

In fact if it's already ON and you ask him to set it, he should reply "Already ON".

Unless MCE isn't reading data from the sim for some reason...

As a reminder, MCE runs as an external program for better stability of the sim.

To guarantee smooth communication between "mce.exe" and "Prepar3D.exe" (via gfsInsider64.dll), we recommend the following.

- Keep Windows UAC at default 2 notches up the slider and not override folders permissions.

- Install MCE to default C:\Program Files (x86)\Multi Crew Experience\ folder and NOT FSX or P3D folder.

- Set "Prepar3D.exe" to run as admin. And if using a launcher app to start the sim, the launcher app must be set to run  as admin as well.

Be aware, with all PMDG aircraft, due to the need for those aircraft to initialize over 20 seconds or so, always wait until aircraft has completed loading, countdown to zero, then start MCE.

Auto-starting MCE with PMDG aircraft may not always work as expected. Like FO dialing wrong values because he isn't reading current HDG or ALT.

You can get away with it using other aircraft though.

 

 

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