I'm trying to make an FO script for an emergency descent where among other things, I have the FO dial in 10,000 feet (in NGX) before hitting lvl change.

 

The FO has no problem dialing in Altitude settings on the MCP when commanded directly, using a variety of grammar.

 

The problem is it won't do this inside the script.  I've tried every variation I can think of: "Set Altitude ten thousand", "Altitude ten thousand feet", etc.  I get a script error every time.  So I either have to set this myself of give the command outside of the script.

 

Same thing with speed.  No problem commanding "Set speed two nine zero" or mach or whatever directly.  But it won't do it inside a script.

 

So is there a different syntax I need to use, or is this a bug?

 

Currently, scripted commands that include digits aren't supported.

 

A few commands such as "set speed v two" will make it because FO would know the V2 to dial.

I'm trying to make an FO script for an emergency descent where among other things, I have the FO dial in 10,000 feet (in NGX) before hitting lvl change.

 

The FO has no problem dialing in Altitude settings on the MCP when commanded directly, using a variety of grammar.

 

The problem is it won't do this inside the script.  I've tried every variation I can think of: "Set Altitude ten thousand", "Altitude ten thousand feet", etc.  I get a script error every time.  So I either have to set this myself of give the command outside of the script.

 

Same thing with speed.  No problem commanding "Set speed two nine zero" or mach or whatever directly.  But it won't do it inside a script.

 

So is there a different syntax I need to use, or is this a bug?

 

 

I'm trying to make an FO script for an emergency descent where among other things, I have the FO dial in 10,000 feet (in NGX) before hitting lvl change.

 

The FO has no problem dialing in Altitude settings on the MCP when commanded directly, using a variety of grammar.

 

The problem is it won't do this inside the script.  I've tried every variation I can think of: "Set Altitude ten thousand", "Altitude ten thousand feet", etc.  I get a script error every time.  So I either have to set this myself of give the command outside of the script.

 

Same thing with speed.  No problem commanding "Set speed two nine zero" or mach or whatever directly.  But it won't do it inside a script.

 

So is there a different syntax I need to use, or is this a bug?

 

Would you like commands such as

 

Select emergency descent altitude fourteen thousand

Select emergency descent altitude ten thousand

 

So that FO can dial altitude?

Well, not quite, but I'm not sure I fully understand the question.

 

I think it would be useful for the FO to simply be able to recognize numeric commands from within a Vox Script, which, as you say, is not currently implemented.  Another example of such a script that would benefit would be "Going Around Flaps Five" which would look like

 

Notify = Roger, going around

pause = 2

Flaps Five

Disarm Spoiler

pause =2

 

If, on the other hand, you are saying that you are thinking about allowing a voxcript that accepts an input variable such as "Going Around [input command]"

 

and then the script is

 

Notify = roger going around

pause = 2

[input command]  where input command could be or anything, but would typically be "Flaps Five"

Disarm Spoiler

pause = 2

 

Then that might be useful in certain situtations, because you could also say "Going Around flaps 10" or "Going around Gear Up" or "Going Around Flight Attendant bring coffee" and it would carry out the variable command, without having to have a separate and specific voxscript for the particular task.

 

Edit--another variation that I just thought of, perhaps most similar to your example above, would be "Set Missed Approach Altitude xxxxx", where the script looks like

 

Notify = "setting missed approach altitude"

pause = 2

Set Altitude xxxxx

pause =2

After writing the above, and then thinking about it over lunch, I can easily see how adding the ability to process variables could easily spiral in complexity, and then naturally leads to a request for conditional brances, and on and on.   I think the original suggestion to simply expand the capability to process explicit commands with numerical values from within a script is probably the best way to keep things simple :lol: