Search NASASearch

SEARCH · Search NASA

Results for “Displays”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 37 records · Page 2

An evaluation of some display parameters for an advanced landing display

This paper discusses the results of a series of tests conducted to better understand some of the design parameters related to presenting an aircraft landing display on a cathode ray tube (CRT). The study was conducted on an aircraft simulator and the results were evaluated in terms of touchdown performance, pilot control activity, and scanning behavior, that is, how the pilot used the display. The results of the study indicate that magnification, presentation of symbols representing aircraft state, and whether the display is presented in a conventional CRT head-down configuration or a collimated head-up configuration, all play a role in the pilot's performance.

Waller, M. C.

Effect of display update interval, update type, and background on perception of aircraft separation on a cockpit display on traffic information

The concept of a cockpit display of traffic information (CDTI) includes the integration of air traffic, navigation, and other pertinent information in a single electronic display in the cockpit. Concise display symbology was developed for use in later full-mission simulator evaluations of the CDTI concept. Experimental variables used included the update interval motion of the aircraft, the update type, (that is, whether the two aircraft were updated at the same update interval or not), the background (grid pattern or no background), and encounter type (straight or curved). Only the type of encounter affected performance.

Jago, S.

Roll-Out and Turn-Off Display Software for Integrated Display System

This report describes the software products, system architectures and operational procedures developed by Lockheed-Martin in support of the Roll-Out and Turn-Off (ROTO) sub-element of the Low Visibility Landing and Surface Operations (LVLASO) program at the NASA Langley Research Center. The ROTO portion of this program focuses on developing technologies that aid pilots in the task of managing the deceleration of an aircraft to a pre-selected exit taxiway. This report focuses on software that produces a system of redundant deceleration cues for a pilot during the landing roll-out, and presents these cues on a head up display (HUD). The software also produces symbology for aircraft operational phases involving cruise flight, approach, takeoff, and go-around. The algorithms and data sources used to compute the deceleration guidance and generate the displays are discussed. Examples of the display formats and symbology options are presented. Logic diagrams describing the design of the ROTO software module are also given.

Johnson, Edward J., Jr.

Evaluation of a Head-Worn Display System as an Equivalent Head-Up Display for Low Visibility Commercial Operations

Research, development, test, and evaluation of fight deck interface technologies is being conducted by the National Aeronautics and Space Administration (NASA) to proactively identify, develop, and mature tools, methods, and technologies for improving overall aircraft safety of new and legacy vehicles operating in the Next Generation Air Transportation System (NextGen). One specific area of research was the use of small Head-Worn Displays (HWDs) to serve as a possible equivalent to a Head-Up Display (HUD). A simulation experiment and a fight test were conducted to evaluate if the HWD can provide an equivalent level of performance to a HUD. For the simulation experiment, airline crews conducted simulated approach and landing, taxi, and departure operations during low visibility operations. In a follow-on fight test, highly experienced test pilots evaluated the same HWD during approach and surface operations. The results for both the simulation and fight tests showed that there were no statistical differences in the crews' performance in terms of approach, touchdown and takeoff; but, there are still technical hurdles to be overcome for complete display equivalence including, most notably, the end-to-end latency of the HWD system.

Arthur, Jarvis (Trey) J., III

Skylab indicators (event timer) (secondary display) (four-digit metabolic display)

The effort expended in developing the following indicators is summarized: (1) event timer; (2) secondary display; and (3) 4 digit display (metabolic). The mechanical design, vibration analysis, and thermal analysis of all these units are identical, and descriptions pertain to all three units. All problems incurred during the program are discussed along with the recommendations, conclusions, and actions taken to rectify the situations.

Tiberg, W.

Diverter - Perspectives on the integration and display of flight critical information using an expert system and menu-driven displays

An expert system prototype, called Diverter, was developed which evaluates, integrates, and displays flight plan recommendations to the pilot during the planning of an inflight diversion. The system integrates information from many sources to provide a comprehensive description of the flight planning alternatives available to the pilot. Diverter evaluates all applicable constraints to arrive at a flight plan to make efficient use of manpower, fuel, and time. The use of an expert system automates much of the integration and evaluation of variables impacting the flight. The use of hierarchical menu-driven displays and direct manipulation interface techniques may reduce workload.

Rudolph, Frederick M.

Maintenance Procedure Display: Head Mounted Display (HMD) Evaluations

A viewgraph presentation describing maintenance procedures for head mounted displays is shown. The topics include: 1) Study Goals; 2) Near Eye Displays (HMDs); 3) Design; 4) Phase I-Evaluation Methods; 5) Phase 1 Results; 6) Improved HMD Mounting; 7) Phase 2 -Evaluation Methods; 8) Phase 2 Preliminary Results; and 9) Next Steps.

Whitmore, Milrian

The Weather Analysis Display (WAND) Tool: Developing a Meteorological Data Display Tool for Situational Awareness During Day-Of-Launch of Space Launch Vehicles Using Python

Atmospheric conditions are an important driver in the design and operation of space launch vehicles. The Profile Envision and Splicing Tool (PRESTO) was developed by NASA’s Marshall Space Flight Center (MSFC) Natural Environments Branch (NE) to generate vertically complete atmospheric profiles from various data sources at NASA’s Kennedy Space Center (KSC), co-located on the United States Air Force (USAF) Eastern Range (ER), for NASA’s Space Launch System (SLS) day-of-launch (DOL) loads and trajectory analysis. PRESTO was designed solely to generate a vertically complete atmospheric profile (Orcutt et al., 2017). However, NE has also been tasked to provide a quality assessment of meteorological data examined on DOL, which goes beyond PRESTO’s utility. Thus, NE developed the Weather Analysis Display (WAND) to visualize data from all available observation systems in conjunction with climatological databases. WAND can display data from various sources in multiple ways, including Skew-T Log-P plots, time-height cross sections, and time series. WAND was developed in Python 3 taking advantage of common packages, such as NumPy for data handling, SciPy for mathematical functions, Matplotlib for data visualization, and Tkinter for the execution of the Graphical User Interface (GUI).

Orcutt, John M.

Reduced-thickness backlighter for autostereoscopic display and display using the backlighter

A reduced-thickness backlighter for an autostereoscopic display is disclosed having a lightguide and at least one light source parallel to an edge of the lightguide so as to be substantially coplanar with the lightguide. The lightguide is provided with a first surface which has a plurality of reflective linear regions, such as elongated grooves or glossy lines, parallel to the illuminated edge of the lightguide. Preferably the lightguide further has a second surface which has a plurality of lenticular lenses for reimaging the reflected light from the linear regions into a series of thin vertical lines outside the guide. Because of the reduced thickness of the backlighter system, autostereoscopic viewing is enabled in applications requiring thin backlighter systems. In addition to taking up less space, the reduced-thickness backlighter uses less lamps and less power. For accommodating 2-D applications, a 2-D diffuser plate or a 2-D lightguide parallel to the 3-D backlighter is disclosed for switching back and forth between 3-D viewing and 2-D viewing.

Eichenlaub, Jesse B

Validation of Minimum Display Requirements for a UAS Detect and Avoid System

The full integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS), a prerequisite for enabling a broad range of public and commercial UAS operations, presents several technical challenges to UAS developers, operators and regulators. A primary barrier is the inability for UAS pilots (situated at a ground control station, or GCS) to comply with Title 14 Code of Federal Regulations sections 91.111 and 91.113, which require pilots to “see and avoid” other aircraft in order to maintain well clear. UAS pilots’ removal from the flight deck of the aircraft necessitates the development of a UAS-specific system for detecting nearby traffic and displaying traffic information to the pilot to support their ability to maintain an objectively defined “DAA well clear” threshold from other aircraft. This new UAS-specific function of remaining DAA well clear is called traffic avoidance. The resulting Detect and Avoid (DAA) system, however, will be subject to a collection of requirements that manufacturers will be obligated to meet in order to certify their equipment. RTCA Special Committee 228 (SC-228), a consortium of representatives from government, industry and academia, is responsible for developing and documenting the Minimum Operational Performance Standards (MOPS) for UAS DAA systems. The present study is the final in a series of human-in-the-loop (HITL) experiments designed to explore and test the various display and alerting requirements being incorporated into the DAA MOPS. Whereas the prior DAA HITLs examined a wide variety of DAA display features and concepts, the current experiment aims to validate the latest minimum display requirements for Phase 1 of the DAA MOPS. Rather than test different display concepts, this study tests two configurations of a MOPS-compatible DAA display: a version that is integrated into the primary navigation and control display of the GCS and a version that is physically separated from the primary display. This manipulation tests the draft minimum requirement that allows the DAA traffic display to be a separate, or standalone, configuration. This type of configuration is a more achievable near-term technology solution since it does not stipulate additional certification or integration requirements on UAS manufacturers. However, a standalone display configuration has the potential to result in pilot performance issues resulting from the cognitive costs of switching between the primary DAA display and the primary navigation and control display. This configuration is also particularly susceptible to errors if the displays are in different orientations (e.g., north-up versus track-up). Both the integrated and standalone display configurations were presented to 16 active UAS pilots in a medium-fidelity simulation, which included confederate air traffic controllers and pseudo pilots operating simulated manned traffic. Pilots were tasked with navigating two different mission routes while maintaining DAA well clear with scripted conflicts. Pilot response times (i.e., measured response) and ability to remain DAA well clear are reported. Primary results indicate that both display configurations resulted in favorable response times and well clear rates. While there were clear trends of pilots objectively performing better in the integrated display condition, with several measured response metrics reaching statistical significance, the differences between the two displays were typically moderate. While the primary variable of DAA display location did not have an especially large impact on pilot performance on its own, when examined alongside the type of DAA threat the pilot was facing (a caution-level versus a warning-level alert), the response time benefits associated with the integrated display were amplified. The implications of these American Institute of Aeronautics and Astronautics 2 results on the Phase 1 DAA MOPS and the connection of this data to previous studies is also discussed.

detect and avoid

Development and Testing of Functionally Operative and Visually Appealing Remote Firing Room Displays and Applications

This internship provided an opportunity for an intern to work with NASA's Ground Support Equipment (GSE) for the Spaceport Command and Control System (SCCS) at Kennedy Space Center as a remote display developer, under NASA technical mentor Kurt Leucht. The main focus was on creating remote displays and applications for the hypergolic and high pressure helium subsystem team to help control the filling of the respective tanks. As a remote display and application developer for the GSE hypergolic and high pressure helium subsystem team the intern was responsible for creating and testing graphical remote displays and applications to be used in the Launch Control Center (LCC) on the Firing Room's computers. To become more familiar with the subsystem, the individual attended multiple project meetings and acquired their specific requirements regarding what needed to be included in the software. After receiving the requirements for the displays, the next step was to create displays that had both visual appeal and logical order using the Display Editor, on the Virtual Machine (VM). In doing so, all Compact Unique Identifiers (CUI), which are associated with specific components within the subsystem, were need to be included in each respective display for the system to run properly. Then, once the display was created it was to be tested to ensure that the display runs as intended by using the Test Driver, also found on the VM. This Test Driver is a specific application that checks to make sure all the CUIs in the display are running properly and returning the correct form of information. After creating and locally testing the display it needed to go through further testing and evaluation before deemed suitable for actual use. For the remote applications the intern was responsible for creating a project that focused on channelizing each component included in each display. The core of the application code was created by setting up spreadsheets and having an auto test generator, generate the complete code structure. This application code was then loaded and ran on a testing environment set to ensure the code runs as anticipated. By the end of the semester-long experience at NASA's Kennedy Space Center, the individual should have gained great knowledge and experience in various areas of both display and application development and testing. They were able to demonstrate this new knowledge obtained by creating multiple successful remote displays that will one day be used by the hypergolic and high pressure helium subsystem team in the LCC's firing rooms to service the new Orion spacecraft. The completed display channelization application will be used to receive verification from NASA quality engineers.

Display Devices