On 2/13/2024 at 5:09 AM, scmtech said:

Hello MCE community and support team.

I am a new user to MCE. I was recommended to check out the forums, and I have been searching and reviewed many of the “beginner” posts, but I still had a few questions for flows I am trying to build in MCE.

1. I was working on building and testing custom flows. I wanted to complete a command in the flow where the FO toggles the Flight Recorder switch to test and then back to the normal and guarded position. I know there is a “test CVR” command, but that command is for the cockpit voice recorder on the forward overhead (push green test switch). I am trying to test the Flight Recorder as shown in the screenshot on the AFT overhead.

2. I noticed when running some of the commands for some of the guarded switches are being opened to set them to what would be their normal guarded position. I added them to my flow as making sure they are in the guarded position is part of the flow - and ideally I would want to check this - so if it were not the case it would be put back to the correct position. These included the alternate flaps, standby power, and bus transfer switches (screenshot below). Is there a way that if a switch is already set in correct position, that the guard will not being opened?

3. In relation to the last question, I also wanted to check the alternate flaps position switch to the right of the guarded arm switch, to make sure it is set to off and not in the up position (down should “spring load” back to off).

4. Is there a way to check a variable or value of a gauge or a switches position within a MCE flow (not necessarily an checklist) and if it is out of bounds alert the user? I am imagining a potential failure case - where an annunciator is illuminated, a gauge is above or below a certain value, etc. Examples: Landing gear down - 3 green, Crew oxygen > x psi, oil level, hydraulic quantity, ac/dc voltmeters within range, etc. Some flows call for checking such instances, so it would be nice to be able to handle this through MCE.

5. Is there any way to have a condition for a step based on another value / switch etc. - or script such a case? One example use case would be - if there is fuel in the center tanks - turn on the center pumps. Conversely, it would also be nice to automatically have the FO shut off the center tank pumps when they are empty (low pressure lights illuminated) - maybe this happens already and I just haven’t experienced it yet? Another example use case I thought of is checking the flaps position to the flaps lever and correcting a disagreement (example: aircraft is de-energized during cockpit preparation - flaps indicate 5, but lever is set to 0, FO sets the flap lever to 5). I realize these might be more complicated use cases.

6. In the flow I was building I noticed a weird issue where duplicates were being added to the drop down list to the available completed task statements. I tried removing all of these items and saving but when I returned to this menu they were back. Screenshot below for reference.

7. I was going through the various lists of tests in the drop down, I did see an option for the master lights switch test, but I could not find an option to perform a test for the CPT or FO side AP, A/T, FMC indicator lights (set test to 1, set test to 2). Is there a command for this? Screenshot below for reference.

8. When I was going through and testing, I tried to command an engine start via speaking “start engine two”. The FO then prompted me to confirm start. I tried various commands “yes, confirm, etc.” but I could not get the FO to begin the engine start via voice. I was able to use the “button” commands to select the start process through the drop down, and the FO went through the start process. How do I command the engine start via voice commands? As a note, I have completed the various recommended voice training processes.

9. In one of my test flights, I was testing a few of the flaps commands and the FO would announce “speed checked flaps __”, however there were several test instances where I was significantly above the maximum deployment speed for these settings. Does the FO in MCE check speeds?

Sorry for the extensive list of questions, but I thought it would be better to prepare a comprehensive list versus several different posts. Thank you in advanced for assistance.

Get the patch here

Most items have been addressed.

Download file, unzip and manually replace all files. Don't forget to replace "Availale_Commands.dat" for newly introduced speech commands.

There are tons of speech commands for each item and only a few are listed.

 

5 hours ago, FS++ said:

Get the patch here

Most items have been addressed.

Download file, unzip and manually replace all files. Don't forget to replace "Availale_Commands.dat" for newly introduced speech commands.

There are tons of speech commands for each item and only a few are listed.

 

Thank you. I look forward to working on my flows with this new update this weekend. 

On 2/22/2024 at 1:30 AM, scmtech said:

2. In the 737 the "displays source set to auto" command does not trigger when the knob is set in the "ALL ON 1" position.
Also, the issue is the same for the "displays control panel switch to normal position" when set to the "BOTH ON 1" position.
Both are on the DISPLAYS section of the NAVGATION panel on the forward overhead.

First, thanks again for the update.

I am not sure if you got to this one or not yet but I'm still having some issues with my displays controls on the PMDG 737-900 (MSFS).

• When the SOURCE knob is set to ALL ON 1, I cannot get it to set to AUTO.
• When the CONTROL PANEL switch is set to BOTH ON 1, I cannot get it to set to NORMAL.

Please let me know if there is anything else I can provide to troubleshoot this.

Thank you so much for all the work on the new guard commands, I went through and tested them with my flows. All capped guards are working as expected. With majority of the guards, if the switches are guarded they should be in their normal and expected position.

I did discover the commands "guard switch eec one set to secured", and "cover switch eec two switch to closed" are only checking the guard and not the push button state. I'm wondering if since you can visually check the state of the switch through the clear guard cap, if these could have logic to check to see if the push button is set to ON (by checking the ENG_EECSwitch_0 and ENG_EECSwitch_1 variables set to 1)? If they are set to OFF (value 0), the FO would complete the ON operation and close the guard. If they are already ON (EEC value 1) nothing would happen (guard would not be opened or the button pressed). I know these are kind of an edge case because all of the other guards set their switches to the normal position when they are closed.

Thanks again for all your efforts and support, I am really enjoying the app.

9 hours ago, scmtech said:

First, thanks again for the update.

I am not sure if you got to this one or not yet but I'm still having some issues with my displays controls on the PMDG 737-900 (MSFS).

• When the SOURCE knob is set to ALL ON 1, I cannot get it to set to AUTO.
• When the CONTROL PANEL switch is set to BOTH ON 1, I cannot get it to set to NORMAL.

Please let me know if there is anything else I can provide to troubleshoot this.

Thank you so much for all the work on the new guard commands, I went through and tested them with my flows. All capped guards are working as expected. With majority of the guards, if the switches are guarded they should be in their normal and expected position.

I did discover the commands "guard switch eec one set to secured", and "cover switch eec two switch to closed" are only checking the guard and not the push button state. I'm wondering if since you can visually check the state of the switch through the clear guard cap, if these could have logic to check to see if the push button is set to ON (by checking the ENG_EECSwitch_0 and ENG_EECSwitch_1 variables set to 1)? If they are set to OFF (value 0), the FO would complete the ON operation and close the guard. If they are already ON (EEC value 1) nothing would happen (guard would not be opened or the button pressed). I know these are kind of an edge case because all of the other guards set their switches to the normal position when they are closed.

Thanks again for all your efforts and support, I am really enjoying the app.

You're welcome.

Unable to replicate behavior with SOURCE and Control panel knobs. Total control with 737-700. I don't have other variants.

Eventually contact support as we may need more info regarding the 900 and the right re-circulating fan

The new set of speech commands are intended as such. To put the guard down (not lift it). Usefule to reset from a "failures scenario".

And if you give the comman verbally (as opposed to testing it in Voxscript panel)), you'll be prompted to confirm you definitely want switching to happen.

On the need to confirm topic, be aware, confirmation speech commands are dynamically enabled when a prompt is needed and disabled after the timeout for reply. Therefore, it may take half or up to a second for them to be ready to recognize following a prompt.

Since they are very short, like "yes", "no", if this scheme wwasn't implemented, you would constantly have the mike randomly picking-up those short words.

In general, when a switch is commanded to ON, OFF, Auto, override, if it has a guard switch it is automatically lifted, then if it's an override state that is requested, the guard switch stays up. If it's "set to normal", the guard is automatically set to closed.

The eec switches have their own speech commands. There are tons of speech variations and only going to list 2.

eec engine one set to alternate

eec two switch to normal.

With commands above, guards are handled automatically.

The "guard switch eec one to closed" will just ensure the guard is put down.

 

Thanks for the explanations.

On 3/3/2024 at 9:43 AM, FS++ said:

Eventually contact support as we may need more info regarding the 900 and the right re-circulating fan

Okay, contact via email?

Is GSX supported for the PMDG in MSFS with MCE? I tried some of the commands listed in the included "ground_cmd.rtf" document and it was not using GSX.

I also saw the config option 

[MECHANIC]
PushWithGSXandAES=0

I tried this both as 0 and 1 with no luck in triggering GSX.

I know this is another sort of a trivial "novelty" interaction, similar to the sun visor stow/unstow (thanks for adding that 😀 btw), but are there any interactions for the ATTEND or GRD call buttons? I was going to include these in some of my flows for additional immersion such as having the FO "call the ground crew" by turning on the service interphone (which works already) and ring the ground crew via the GRD CALL button. The ATTEND would just be a single push and release, but the GRD CALL should probably hold it for a couple seconds.

 

Another question, does / would it be possible for Voxkey to support joystick button presses?

On 3/5/2024 at 5:39 AM, scmtech said:

I know this is another sort of a trivial "novelty" interaction, similar to the sun visor stow/unstow (thanks for adding that 😀 btw), but are there any interactions for the ATTEND or GRD call buttons? I was going to include these in some of my flows for additional immersion such as having the FO "call the ground crew" by turning on the service interphone (which works already) and ring the ground crew via the GRD CALL button. The ATTEND would just be a single push and release, but the GRD CALL should probably hold it for a couple seconds.

 

Another question, does / would it be possible for Voxkey to support joystick button presses?

Interaction with Ground mechanic and cabin crew are mostly spech based, rather than a speech command that triggers a button call.

What you need to be aware of is whjat they can do.

Goround mechanic can.

First, before you can interact with ground mechanic, you need to establish contact with any of these

cockpit to ground

ground from flight deck

mechanic from flight deck

... many other variations.

The mechanic will be ale to...

set wheel chocks (he'll do that automatically when you get in touch with him or about to pushback)

Open or close cargo doors. Either automatically when GSX carts arrive or boiarding is complete  for loading/unloading or on request with "mechanic open cargo doors", "ground engineer close cargo doors"

connect/disconnect ground power. Use commands "ground mechanic connect ground power", "mechanic remove ground power".

handle pushback. Depending on whether GSX is running in which case he transfers you to GSX operator, or will do that himself.

Do not forget to ask him to disconnect when you no longer need him. "ground you may disconnect", "ground you may leave"....etc

Therefore an example of a flow where the Fo extablishes contact with mechanic may look like this

service interphone on

Notify=ground from flight deck  (add a Notify statement so you can hear the Fo making the request. Not required though)

ground from flight deck   (the actual command that gets the mechanic's attention)

pause=10     (gives time to ground mechanic to repond)

Notify=ground connect gpu (again, this is so you can hear the Fo requesting gpu)

ground connect gpu    (the actual speech command to rrequest GPU)

pause=10  (need to insert some delay to give mechanic time to actually comnect GPU)

________________________

Regarding cabin crew...

They can open/close doors on request with

cabin crew open service doors

flight attendants close serive doors

cabin crew close all doors (to ensure no door is left open)

cabin crew open doors  (for boarding where they will typically open the front left door).

They can also respond to GSX request to open whatever door.

They also repond to flight deck crew notifications like

flight attendants prepare for gate departure

cabin crew get ready for takeoff

cabin crew prepare for landing.

cabin crew please proceed to flight deck.

The human recorded voice packs for pursers are limited so you cannot have them say anything else unless you assign a TTS voice to them and can build all sorts of verbal interactions.

Now keep in mind most people would probably not bother to memorize some of the trigger sentences I listed above.

Since MCE has a "built-in speech simulator" (not found in any similar product), you could interact with both mechanic and cabin crew in the most natural way by creating custtom verbiage that you tie to built-in commands. They will understand whatever speech you may come up with.

If required, could easily add speech commands to trigger the "ATTEND" & "GRD CALL" buttons to hear the chimes.

In Prepar3D or FSX, when you hit button "GRND CALL", MCE will detect the event and simulate a "cockpit to ground" command so the mechanic replies within seconds without you saying anything.

 

Edited April 27, 20242 yr by FS++
typos

Hello Gerald

737-700

MCE V3.0.7.0

I use CereProcTTS voice.  in Mechanic folder cockpit to ground, ground connect ground power.

[SCRIPT]
service interphone on
pause=2
Notify=cockpit to ground                               nothing from mec
pause=10     
Notify=ground connect ground power           nothing from mec
pause=10  
battery on
pause=10
standby power auto
transfer bus auto
isolation valve closed
a c meter set to ground power
position light steady
press master caution
pause=2

Edited March 7, 20242 yr by Burge
mce v3.0.7.3

2 hours ago, Burge said:

Hello Gerald

737-700

MCE V3.0.7.0

I use CereProcTTS voice.  in Mechanic folder cockpit to ground, ground connect ground power.

[SCRIPT]
service interphone on
pause=2
Notify=cockpit to ground                               nothing from mec
pause=10     
Notify=ground connect ground power           nothing from mec
pause=10  
battery on
pause=10
standby power auto
transfer bus auto
isolation valve closed
a c meter set to ground power
position light steady
press master caution
pause=2

The Notify=whatever_sentence are made by the FO so you can hear what he's requesting.

You need to add the actual commands that get Mechanic to respond or do things. Same sentence without "Notify".

 

Notify=cockpit to ground                               nothing from mec

cockpit to ground
pause=10     
Notify=ground connect ground power           nothing from mec

ground connect ground power

The Notify statements are there for realism.

You don't need them if you are yourself trying to extablish contact with mechanic with some elaborate speech that MCE doesn't expect,

You could then have a custom flow triggered by your unique way to establish contact with mechanic like "hi there we need some juice on the bird" (or whatever you want), and won't need the Notify statement since the mech is expected to perform those tasks that are part of the flow.

Gerald thanks for that mate working. Tell me mate what's the mechanic & purser scrip folders for.

19 hours ago, Burge said:

Gerald thanks for that mate working. Tell me mate what's the mechanic & purser scrip folders for.

In the case above, your flow would have worked just as well if it was in<Copilot> folder.

The <mechanic> and <Purser> folders are mostly for cases where you need to go beyond what is built-in.

Assign a TTS voice to mechanic (or Purser) and you could create virtual conversations and getting them to respond to any speech with whatever reply you want to hear.

We aren't responsible for any allegations of cheating or marriage break-ups that may result from the misuse of this feature with Pursers.😜

 

Edited March 8, 20242 yr by FS++

just a request  for pmdg737 fuel cutoff switches 1 2. be awesome to have for my fuel flow.

R RECIRC FAN-not working i think scmtech talk about this not sure, so much to read.

you boys are the best

Edited March 9, 20242 yr by Burge
msfs

6 hours ago, Burge said:

just a request  for pmdg737 fuel cutoff switches 1 2. be awesome to have for my fuel flow.

R RECIRC FAN-not working i think scmtech talk about this not sure, so much to read.

you boys are the best

There are already speech commands for fuel levers

fuel lever engine one cutoff

fuel lever one close

....many other variations.like...

open fuel lever engine one

close fuel lever two

Or even ...

Shutdown engine one

shutdown number two.

When spoken as direct commands FOwill want to confirm that first. Not so when part of a flow.

Let me know if I misunderstood the request.

 

Edited March 9, 20242 yr by FS++

On 3/6/2024 at 1:02 PM, FS++ said:

If required, could easily add speech commands to trigger the "ATTEND" & "GRD CALL" buttons to hear the chimes.

This would be nice for additional immersion, so I can include it as part of the flow.

I am still having issues with getting the GSX pushback to start via MCE, I have tried many of the commands for pushback described in the "ground_cmd.rtf" document in the "Multi Crew Experience\Docs" folder. I am using the latest version of GSX for MSFS as of today GSX Pro 2.9.4.

Thanks.