Target Messages |
The Target Messages editor is opened by selecting the 'Messages' tab from the Target Editor.
Frozen messages are displayed in BLUE. Non-frozen messages are displayed in GREEN. A frozen message is always associated with the target. A non-frozen message is one that does not exist until it is derived when it is needed (and 'Auto-derive msgs' is checked).
Lets you view the messages. Clicking on the 'Time' button will sort the messages in alphanumeric order. Clicking on 'Host', 'Device', or 'Text' will sort them in alphanumeric order. Clicking on any of these buttons twice will reverse the order of the display.
Opens the flight plan message template to create a new message.
Opens a generic message dialog to create a new message.
Opens the CMS message dialog to create a new message.
Opens the dialog message template.
Opens the generic dialog message template.
Removes the message from the messages list.
Allows derived messages to be generated for the target.
For each target in auto-derive mode, GSGT will generate non-radar messages to enter a flight plan, start tracking, and handoff control of the flight between controllers and/or facilities as needed.
NOTE: Once a target enters a 'live' sector, derived messages will no longer be generated.
Parameters controlling the creation of auto-derived messages can be set in the scenario Preferences.
When the 'Auto-derive msgs' box is checked, GSGT will export target information to the ATCoach engine so that it can generate derived messages for the target. This may take several minutes, during which a 'Deriving msgs, please wait...' message window is displayed and all user input is disabled.
When the ATCoach simulation is complete and all messages have been derived, the derived messages will appear in GREEN in the Target Messages List Box and normal program usage can resume.
When the 'Auto-derive msgs' box is un-checked, the following dialog box is displayed to confirm whether the derived msgs should be saved.
When the 'Auto-derive msgs' box is un-checked and the target is Mode3a equipped but does not have an assigned beacon code, the following warning is displayed to alert the user that a beacon code will not be inserted in the FP msg. In order to assign a beacon code, 'No' should be clicked and a beacon code assigned in the Attributes tab of the target editor. The 'Auto-derive msgs' box can be checked and then un-checked to re-derive and freeze the messages.
The 'FP Message Editor' is displayed when a FP msg is highlighted and 'Edit-> Use Default Dialog' is selected from the Target Editor. It is also displayed when 'New-> Use FP dialog' is selected from the Target Editor.
The FP Edit window allows each of the displayed attributes of a FP message to be changed. Required fields are colored YELLOW until they are filled in.
NOTE: Changes made in the FP Edit window do NOT affect the target attributes set in the target attributes editor.
The fields in the FP Edit - Advanced page are identical to those in the System Commands editor - Advanced page.
Accepts the message and closes the window. The message will be listed in the 'Messages' window. To view the messages, click on 'derive messages'.
Closes the window and returns you to the message editor.
The 'Generic Message Editor' is displayed when any message is highlighted and 'Edit-> Use Generic Dialog' or any non-FP message is highlighted and 'Edit-> Use Default Dialog' is selected from the Target Editor. It is also displayed when 'New-> Use generic dialog' is selected from the Target Editor.
The fields in the Message Editor are identical to those in the System Commands editor.
The 'CMS Message Editor' is displayed when any CMS message is highlighted and 'Edit-> Use Default Dialog' is selected from the Target Editor. It is also displayed when 'New-> Use CMS dialog' is selected from the Target Editor.
The fields in the CMS Message Editor are identical to those in the CMS System Commands editor.