Changes between Version 14 and Version 15 of GSGT/GSGT_TBFM

Timestamp:

2017-11-14T16:04:23-05:00 (8 years ago)

Author:

Ryan Hepp

Comment:

--

GSGT/GSGT_TBFM

@@ -79 +79 @@
 The Target Editor has several changes for TBFM mode.  In the Main tab, the Dynamics pane – including Aircraft Type (AChar), Speed and Flight Level (Flevel), and the Aircraft pane – including the number of aircraft and Heavy indicator, have been removed.  In the Dysim tab, the pilot Symbol text box and the PPEs and Prompts panes have been removed.  A new Dynamics tab replaces the Route and Events tabs.
 
-The new Dynamics tab is made up of three panes – Flight Plan, Flight Dynamics and Events.  The Flight Plan pane includes the AChar drop down, Speed and Flevel text boxes, as well as the Route text box.  The Flight Dynamics pane includes a new Macro text box and “Populate Macro from FP Route” and “Show Flight Path” buttons.  The Events pane can be used to create target events in the same way that was previously done in the Events tab.  The one major change regarding events is that accompanying NAS messages are not automatically generated, but can be manually scripted using the Messages tab.
+[[Image(TE_Main.jpg, 600px)]]
+
+[[Image(TE_Dynamics.jpg, 600px)]]
+
+The new Dynamics tab is made up of three panes – '''Flight Plan''', '''Flight Dynamics''' and '''Events'''.  The '''Flight Plan''' pane includes the AChar drop down, Speed and Flevel text boxes, as well as the Route text box.  The '''Flight Dynamics''' pane includes a new Macro text box and “Populate Macro from FP Route” and “Show Flight Path” buttons.  The '''Events''' pane can be used to create target events in the same way that was previously done in the Events tab.  The one major change regarding events is that accompanying NAS messages are not automatically generated, but can be manually scripted using the Messages tab.
 
 The Macro text box allows a target to deviate from the route that is used to generate the flight plan.  Furthermore, when adaptation is loaded that includes TBFM terminal waypoints in addition to the ERAM XML data, the Macro text box can be used to create a terminal route.  Along with terminal waypoints, the terminal route can include altitude and speed restrictions and Radius-to-Fix (RF) turn segments.  Valid Macro route elements are:
+
+
+||  '''Route Element'''  ||  '''Format'''  || 
+|| Position || FIX or [+/-]dd:dd:dd:dd, [+/-]dd:dd:dd:dd ||
+|| Altitude || /ddd[~ddd] || 
+|| Speed || ddd[~dddd] || 
+|| Heading || ->Hddd ||
+|| Drop Target || ->DROP || 
+|| Alt Restriction || [altRestr:D:AT:dddd.d] for "at altitude" \\ [altRestr:D:AOB:dddd.d] for "at or below" \\ [altRestr:D:AOA:dddd.d] for "at or above"  || 
+|| Speed Restriction || spdRestr:D:AT:ddd.d (always "at" speed) || 
+|| RF Turn || FIX1{flyOver} FIX2{rf:R:ddd.d} for right turns or \\ FIX1{flyOver} FIX2{rf:L:ddd.d} for left turns \\ and ddd.d is the outbound heading || 
+
+[[Image(TE_Messages.jpg, 600px)]]
 
 ||  '''Name'''  ||  '''Command'''  ||  '''Description'''  ||
@@ -101 +118 @@
 
 \\
-
-||  '''Route Element'''  ||  '''Format'''  || 
-|| Position || FIX or [+/-]dd:dd:dd:dd, [+/-]dd:dd:dd:dd ||
-|| Altitude || /ddd[~ddd] || 
-|| Speed || ddd[~dddd] || 
-|| Heading || ->Hddd ||
-|| Drop Target || ->DROP || 
-|| Alt Restriction || [altRestr:D:AT:dddd.d] for "at altitude" \\ [altRestr:D:AOB:dddd.d] for "at or below" \\ [altRestr:D:AOA:dddd.d] for "at or above"  || 
-|| Speed Restriction || spdRestr:D:AT:ddd.d (always "at" speed) || 
-|| RF Turn || FIX1{flyOver} FIX2{rf:R:ddd.d} for right turns or \\ FIX1{flyOver} FIX2{rf:L:ddd.d} for left turns \\ and ddd.d is the outbound heading || 
 
 The Messages tab of the Target Editor behaves as in standard mode except that only a very limited set of flight data messages are automatically generated.  The initial flight plans and departure messages, where needed, are created when auto-derive is selected.  When the scenario is executed with the DYSIM tbfmDriver, the NAS FP messages are converted into CMS FH and HX messages and AIG flight data messages for direct injection.  The NAS DM messages are converted into CMS AH and DH messages.  Also, any manually scripted NAS AM messages (with the exception of field 02 amendments) are automatically converted to CMS AH messages at runtime.  Updates to AIG flight data must be manually scripted.