EP2 User Interface
EP2 User Interface
Rockwell Collins
400 Collins Road NE
Cedar Rapids, IA 52498-0503
http://www.rockwellcollins.com
This program has not been published by the copyright owner, and has been disclosed to
other parties only under license, prohibiting unauthorized disclosure, copying, or use. Any
unauthorized copying, use, or disclosure is strictly prohibited under such license by the
software owner in accordance with the Trade Secret Act of Utah.
The technical data in this document (or file) is controlled for export under the Export
Administration Regulations (EAR), 15 CFR Parts 730-774. Violations of these export laws
may be subject to fines and penalties under the Export Administration Act.
APPROVALS
(For most recent revision)
Figures
Figure 1-1. EP2 UI with Standard Layout ................................................ 1-2
Figure 1-2. Configuration Menu ............................................................. 1-4
Figure 1-3. Quick Access Toolbar........................................................... 1-4
Figure 1-4. Script File Controls .............................................................. 1-5
Figure 1-5. Real-Time Controls ............................................................. 1-5
Figure 1-6. User Guides and Help Controls ............................................. 1-6
Figure 1-7. Shortcut Toolbar ................................................................. 1-6
Figure 1-8. Windows Docked as Documents ............................................ 1-9
Figure 1-9. Docking ........................................................................... 1-10
Figure 1-10. Script Editor Window ....................................................... 1-11
Figure 1-11. Cloud/Vis/Fog Window ..................................................... 1-14
Figure 1-21. Map Window Showing World Vector, European Large Rivers,
Custom Airports, Custom Airports Page Range, Paged Generic Airports,
Paged Custom Airports and Airport Tooltips Layers .......................... 1-27
Figure 1-22. Saved Positions Window .................................................. 1-28
Figure 1-23. Position Editor Dialog....................................................... 1-29
Figure 1-24. Model Positions Window ................................................... 1-30
Figure 1-25. Statistics Favorites Window (Desktop) ............................... 1-31
Figure 1-26. Statistics Favorites Window (EP-80 with 3 SPs and 1 MFE) ... 1-32
Figure 1-27. Statistics Window and Statistics Selection Dialog ................ 1-33
Figure 1-28. Memory Window ............................................................. 1-34
Figure 1-29. Memory Window with Detail Column .................................. 1-35
Figure 1-30. HAT Window ................................................................... 1-37
Figure 1-31. Configuration Window ...................................................... 1-38
Figure 1-32. Viewport Properties Dialog ............................................... 1-40
Figure 1-33. NLIM Configuration Dialog ................................................ 1-42
Figure 1-34. Edge Blend Dialog ........................................................... 1-42
Figure 1-35. Post Processor Properties Dialog ....................................... 1-44
Figure 1-36. Post Processor Properties Dialog for XG ............................. 1-45
Figure 1-37. Post Processor Properties Dialog for EXG ............................ 1-45
Figure 1-38. PostProcessor AcCoupling Properties Window...................... 1-46
Figure 1-39. DAFIF Data Update Process .............................................. 1-47
Figure 1-40. DAFIF Data Update Facility ............................................... 1-48
Figure 1-41. OpcodeDecode Properties Window..................................... 1-54
Figure 1-42. Logger Window ............................................................... 1-56
Document Conventions
This manual uses these conventions:
• Computer prompts and messages that appear on the screen are
in typewriter font.
• Commands that you select on-screen, such as menus and dialog
boxes, or buttons/keys that you select, such as, dials, buttons
and keys, are italicized.
• Commands such as Help About are lowercase bold with
Initial Caps.
• Individual keys that you press on the keyboard are enclosed in
angle brackets: <Enter> means to press the Enter key; <z>
means to press z.
• Combinations of keys that you press simultaneously are enclosed
1.1 Introduction
The EP2 application provides control of the IG without a host
computer connected or running. It can be used to control any
EP-8000 product IG real-time system, configure viewports, load
models, control environment parameters, aircraft and runway
lighting, and execute reset files.
The EP2 application uses the EP Application Programmer Interface
(epAPI) to communicate with the real-time system. The EP2
application typically runs on the RT computer.
Shortcut
Toolbar
RT Status
Message Area Configuration Logger CLI Statistics UI Status
Selecting one of these tabs shows the menu items that are
available in the selected category.
− Menu Items – These menu items change depending on the
currently selected tab.
• Title – Displays the title of the application and the currently
loaded configuration file, if applicable.
• User Guide & Help – Provides access to EP2 Software User’s
Guide, EP2 User Interface Manual and EP2 version information.
• RT Status Message Area – Shows any relevant epAPI status
messages.
• UI Status Message Area – Shows any relevant UI status
messages.
• Shortcut Toolbar
− Host communication status indication.
− Video status indication.
− Time-of-day selections (day, dusk, night, dawn).
• Configuration Window – The configuration window is part of the
standard window layout. It displays a tree showing the RT
modules that have been loaded, the screen types and their
associated screens, the viewports that have been created, and
configuration properties. See section 1.9.1, Configuration
Window, for more information about the configuration window.
• Logger Window – The logger window is part of the standard
window layout. It logs RT messages. Messages can be
categorized as status, warning, or error. See section 1.9.2,
Logger Window, for more information about the logger window.
• CLI Window – Provides ability to input Command Line Interface
See section 1.9.4, Layout – Save, Save As and Restore, for more
information on window layouts.
1.7.1 Clouds/Vis/Fog
The Clouds/Vis/Fog window (see Figure 1-11) provides controls for
ground fog, three cloud layers, broken clouds and visibility.
The system visibility can be control with the Visibility slider in the
range of 0 to 1,320,000 feet (0-250 miles). The runway visual
range (RVR) of the ground fog can be set with the RVR slider.
Changing the RVR has no effect unless ground fog is enabled.
The visual category can be set using the Visual Category combo
box. Visual categories change settings for system visibility, RVR,
cloud layer 0, and ground fog. Cloud layers 1 and 2 are disabled
when a visual category is selected. Visual categories are defined by
the VisualCategoryData.txt file in the
C:\EP2\IGSetup\IGTuning\Viscal directory. Table 1-5 lists the
default settings for each visual category.
Table 1-5. Visual Category Default Settings
System
Visual Category RVR Cloud Layer 0 Ground Fog
Visibility
CAVOK 100 miles 0 ft Disabled Disabled
CAVU 250 miles 0 ft Disabled Disabled
System
Visual Category RVR Cloud Layer 0 Ground Fog
Visibility
Enabled
300 m 300 m Enabled Height
CAT III Top 6000 ft
984 ft 984 ft 70 ft
Bottom 70 ft
Enabled
200 m 200 m Enabled
CAT IIIa Top 6000 ft
656 ft 656 ft Height 75 ft
Bottom 75 ft
Enabled
125 m 125 m Enabled
CAT IIIb (125 m) Top 6000 ft
410 ft 410 ft Height 50 ft
Bottom 50 ft
Enabled
75 m 75 m Enabled
CAT IIIb (75 m) Top 6000 ft
246 ft 246 ft Height 35 ft
Bottom 35 ft
The All Taxiway Lights combo box can be used to change the
intensities of all the lights on all the taxiways.
1.7.9 Keypad
The Keypad window allows the user to monitor and control the
position of moving models. Models can move in six degrees of
freedom – heading, pitch, roll, x (left/right), y (forward/reverse),
and z (up/down). Models can be moved by either using the
numeric keypad on the keyboard or by clicking the representative
buttons on the Keypad window. If the keyboard is used, Num Lock
must be turned off.
The rate at which models move can be adjusted using the rate
scalars for translation or rotation. The rotation rate affects
heading, pitch and roll changes, whereas the translation rate
affects x, y and z changes.
A model can be repositioned by entering the moving model and
submodel number and entering a new position in the Position group
box.
While editing the moving model/submodel numbers, the position,
or the rate scalars, updates from the RT for the respective fields
will not be done. This is indicated by a shaded background color in
the respective area. To enable updates after editing, click outside
of the shaded area.
1.7.10 Map
The Map window allows the user to position the eyepoint anywhere
in the world by double-clicking the left mouse button on a location
on the map. Double-clicking on the map also centers the map on
the position that was double-clicked. Double-clicking on a custom
airport will position the eyepoint on the glideslope of the first
runway of the custom airport.
The world map consists of many different layers that can be
enabled or disabled by checking the box in the Layers list to the left
of the map. The layers are rendered in priority order according to
their order in the Layers list. To re-order the rendering order of the
layers, simply drag and drop the layers within the Layers list.
The Airports of Interest layer contains some of the most widely
known airports in the world. DAFIF data is available for these
airports which consists of the airport name, ICAO/IATA airport
codes, latitude, longitude, elevation, and runway information.
When simulation is not running, the Custom Airports layer is
composed of airports that have been custom-installed on the
system running EP2. A custom airport is defined by an Airport of
Interest airport (see previous paragraph) with a Creator flight file
(*.flt) within the C:\EP2\SceneData hierarchy that begins with the
three-letter IATA code of the airport.
If simulation is running, the Custom Airports layer consists of
airports that have been loaded by the RT.
There are layers to display the page ranges for custom airports and
paged generic airports. The Paged Generic Airports (including their
labels and page range) and the Paged Custom Airports layers’
content are determined by the RT system, and are only enabled
while simulation is running.
Panning is done by dragging the map with the left mouse button.
As an alternative, panning can also be done by holding the <Ctrl>
key down and dragging with the right mouse button.
To select a particular area of the map, rubber banding can be used.
Hold down the <Alt> key and drag with the left mouse button
around the area of interest. You will see a red rectangle
surrounding the area. When the mouse button is released, the
map becomes centered on the area and zoomed to show the
selected area. To cancel the selection, release the <Alt> key prior
to releasing the mouse button.
Use the Reset Map button to reset the map transformations back to
their original state.
Figure 1-20. Map Window Showing Raster Map, Lat/Lon Lines, World
Vector, Custom Airports, Paged Custom Airports, Airport Tooltips,
Airport Plans and Eyepoint Indicator Layers
The dialog will show the current data from the saved positions
window. If the real-time software is currently running, the Current
Eyepoint Position button is enabled. Clicking on this button will
load the current eye point position into the dialog box.
1.9.1.1 Modules
The Modules section of the configuration tree contains a list of the
RT modules that have been loaded. If a module is an optional
module it will have either a or a to the left of the module
name. Required modules do not have an icon to the left of their
names.
1.9.1.2 Screens
Screens are configured using the System Manager application on
EP-8000 hardware. Other hardware will be configured with a single
screen. Screens are displayed as ancestors of the Screen Types
node in the configuration tree.
1.9.1.3 Viewports
A default viewport called ‘Viewport0’ is created as part of the
creation of a new configuration. See Figure 1-32. Additional
viewports may be created by right-clicking the Viewports node.
Viewports may be deleted by right-clicking the applicable viewport
node and choosing Delete from the context menu.
The Previous and Next buttons will cycle through viewports. This is
useful if you would like to configure multiple displays using a single
Edge Blending dialog.
Selecting the Enable check box will apply the blend on the display.
This will allow you to see how your changes affect the actual
display.
The Reset All button will snap all of the edges back to the sides of
the display, while the Reset button will only snap back the selected
edge.
If the Link Adjacent Points check box is checked, points move in
unison, where appropriate. Otherwise, the points move
independently.
The Selected Edge radio buttons are used to select an edge in the
display to modify. You can also select a desired edge by holding
down <Ctrl> and pressing the arrow key associated to the edge
that you wish to select, i.e., <Ctrl-right arrow> will select the right
edge.
Once an edge is selected, you can select individual points along
that edge to adjust. You can do this by either clicking on the point
that you wish to select, or using the arrow keys to shift the
selected point.
Once you have the point selected, you can adjust the point and
associated line by clicking on the arrow buttons in the Adjust
Selected Line button group, or by using the arrow keys.
On horizontal edges, points may only be adjusted up or down. On
vertical edges points can only be moved right or left.
Changing the value in the Cursor Step Size control will either
1.9.1.7 Properties
RT modules can register configuration parameters specific to
their module. By default, properties are persisted and editable
while the RT is not running. Properties have a number of
attributes that can override this default behavior:
• Read-only–control(s) are disabled for modifications.
• Run-editable–control(s) are enabled for modifications
while RT is running.
• Non-persistent–property is not persisted to the
configuration file; control(s) are indicated by a shaded
background color.
• Advanced–control(s) are hidden unless the Show
Advanced checkbox is checked.
ARINC Data
If ARINC data is available, it can be merged with the existing DAFIF
data; this will update any existing ICAO entries in the DAFIF data
with the corresponding data from the ARINC file and will add new
ICAO entries where the entries exist in the ARINC data but not in
the DAFIF data.
Please note that if there is data for an ICAO in the ARINC file, then
it will be used to completely replace any existing data for this ICAO
in the DAFIF data. The customer will need to supply the ARINC
data. It is recommended that the ARINC data file be placed on the
IG under the IGTuning\AirportData directory. The file can then be
selected using the ARINC data file’s browse button as described
above
Airport Data
If the user wants to modify an existing airport, or add a new airport,
then an airport update file must be created. Note that an airport
update file is not needed for an existing airport if only the runways
need to be modified. The airport data update file is a text file which
must conform to the format used within the existing DAFIF airport
data text file:
Runway Data
If the user wants to modify an existing runway, or add a new runway,
then a runway update file must be created. The runway data update
file is a text file which must conform to the format used within the
existing DAFIF runway data text file (runway data lines must exist in
pairs – primary end and secondary end).
Primary end (first line of the runway data pair)
Field chars
Airport ICAO [00]-[03]
Blank space [04]
Runway length [05]-[09]
Blank space [10]
Runway width [11]-[13]
Blank space [14]
Runway ID [15]-[17]
Blank space [18]
Runway latitude [19]-[28]
Blank space [29]
Runway longitude [30]-[40]
Blank space [41]
Runway elevation [42]-[48]
Blank space [49]
Runway heading [50]-[54]
Blank space [55]
Lighting_1 [56]-[57]
Blank space [58]
Lighting_2 [59]-[60]
Blank space [61]
Lighting_3 [62]-[63]
Blank space [64]
Lighting_4 [65]-[66]
Deletion of Data
If the user wants to delete an existing airport or runway, a data
deletion file can be applied to the airport and/or runway data –
removing either entire entries or just specific runways. To remove
an entire entry (airport and corresponding runway data) the ICAO
must be entered on its own line, for example:
Field chars
ICAO [00]-[03]
KDFW
These contain all the height of terrain returns for each of the test
points 0, 1, 2 and 3.
the clutter information used for this airport, and the clutter file
itself which will be used by the real-time to generate the clutter.
Method Two
The second way to use the tool is required when there is no model
tag file available, and the user has to generate tags manually.
Once the manual tags are created they can then be used in the
same manner as the automatically generated tags.
A lot of set up can be done without the real-time running, but it is
recommended that the real-time is running to create/modify tags
and clutter.
The following entries are set up in the model tag file created when
the airport model is built.
• Airport Name:
• Airline Hub:
• ICAO:
• IATA:
5. Right-click on the clutter tag in the tree and select Add Tag.
8. Initially the tag model is above ground. Click on the new tag
and select Bind keypad to tag.
10. Use the keypad to move the tag model to the correct position.
The eyepoint is placed directly over the selected tag. If the aircraft
needs to be moved right-click on the aircraft and select Bind
keypad to model.
The keypad radio button group now shows that the selected model
is being controlled by the keypad.
This change the icon to a red cross. Any clutter at this gate is
removed from display but remains present in the GUI. This
allows the disabled tag to be double-clicked again which re-
enables the tag and causes the model to be displayed.
Method Two
In order to permanently delete the model, select the model and
press the Delete key.
The Generate Clutter Files function generates two files; both are
written to the C:\EP2\IGSetup\IGTuning\Clutter directory.