Changes between Version 8 and Version 9 of GSGT/GSGT_TBFM

Timestamp:

2017-11-13T14:52:32-05:00 (8 years ago)

Author:

Ryan Hepp

Comment:

--

GSGT/GSGT_TBFM

@@ -36 +36 @@
 * Range and Flight Level (in hundreds of feet) can be changed.
 
-* Additional map elements for display 
+* Additional map elements for display: 
+1. Airports
+2. Fixes
+3. Airwars and adapted routes
+4. Neighbor facilities and non-US boundaries 
 
-== Target Commands and Target Attributes ==
+* Positions and distances between points can be identified using the mouse. While holding 'shift' down, 'left click' and drag on the airspace to create a measurement line. The distance, heading, and coordinates of the line can be found on the bottom of the screen.
+
+* The Find button can be used to search for airspace elements in the adaptation. A context box with additional information is displayed. 
+
+== Scenario Editor ==
+
+To launch the Scenario Editor, select 'Edit' from the 'Scenario' menu bar item or from the icon bar. In TBFM mode, the Scenario Editor has the following tabs:
+
+* Preferences
+
+* Targets
+
+* Adaptation
+
+* System Commands
+
+* Record Select Indicators(RSI)
+
+=== Target Editor === 
+
+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.
+
+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:
 
 ||  '''Name'''  ||  '''Command'''  ||  '''Description'''  ||
+|| Change Position || FIX or [+/-]dd:dd:dd:dd, [+/-]dd:dd:dd:dd || Target will fly to fix or coordinates entered ||
 || Change Altitude || ->A150 || Set targets altitude in hundreds of feet. ||
 || Change Speed || ->V255 || Set targets speed. Default is TAS ||
 || Change Heading || ->H090 || Set targets heading ||
 || Change Beacon || ->B4537 || Set targets beacon ||
-|| Drop Target || ->DROP || Set targets beacon ||
+|| Drop Target || ->DROP || Drops target ||
+|| Alt Restriction || altRestr:D:AT:dddd.d || Can also change D:AT to D:AOA or D:AOB for \\ at At or above and At or below respectively ||
+|| Speed Restriction || spdRestr:D:AT:ddd.d || Can also change D:AT to D:AOA or D:AOB for \\ at At or above and At or below respectively ||
 || Set Handoff Margin || ->set:hoMargin=20 || Set targets handoff in miles. 'set' is case sensitive. ||
 || Set Handoff Duration || ->set:hoDuration=90 || Set targets handoff duration in seconds. 'set' is case sensitive. ||
@@ -54 +85 @@
 || Confirm SMIF || ->set:confirmSMIF || A popup window will appear to confirm commands from SMIF 'set' is case sensitive. ||
 
-= Test Pictures = 
+
+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.
+
+Within the Messages tab, the Generic Message Editor and the CMS Message Editor have a new “Outgoing” check box.  This allows any CMS message of AIG flight data message to be manually scripted for direct injection.  Selecting the “Outgoing” check box reverses the Source and Destination devices.
+
+== Preview == 
 
 
+
+
+= Test Pictures =