Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “GCS”

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 73 records · Page 4

An Interoperability Concept for Detect and Avoid and Collision Avoidance Systems: Results from a Human-In-The-Loop Simulation

The integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) poses a variety of technical challenges to UAS developers and aviation regulators. In response to growing demand for access to civil airspace in the United States, the Federal Aviation Administration (FAA) has produced a roadmap identifying key areas requiring further research and development. One such technical challenge is the development of a "detect and avoid" system (DAA) capable of providing a means of compliance with the "see and avoid" requirement in manned aviation. The purpose of the DAA system is to support the pilot, situated at a ground control station (GCS), in maintaining "DAA well clear" of nearby aircraft through the use of GCS displays and alerts. In addition to its primary function of aiding the pilot in maintaining well clear, the DAA system must also safely interoperate with existing NAS systems and operations, such as the airspace management procedures of air traffic controllers (ATC) and Collision Avoidance (CA) systems currently in use by manned aircraft, namely the Traffic alert and Collision Avoidance System (TCAS) II. It is anticipated that many UAS architectures will integrate both a DAA system and a TCAS II. It is therefore necessary to explicitly study the integration of DAA and TCAS II alerting structures and maneuver guidance formats to ensure that pilots understand the appropriate type and urgency of their response to the various alerts. This paper presents a concept of interoperability for the two systems. The concept was developed with the goal of avoiding any negative impact on the performance level of TCAS II while retaining a DAA system that still effectively enables pilots to maintain DAA well clear.

unmanned aircraft systems↗

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↗

Developing an Adaptable NextGen Interface for the UAS Ground Control Station

Motivation: NextGen traffic infrastructure is in place to support manned aircraft operations. However, the UAS ground control station (GCS) adds a data interface requirement that is not yet fully accounted for in the NextGen data service architecture. Existing NextGen data service is focused on aircraft, not the GCS. Smaller UAS may not have the payload or power capacity to support the additional equipment. Innovation: Provide a mechanism for a UAS regardless of size, payload, bandwidth, and power capacity to gain access to NextGen data-sourced traffic information in real-time.

LVC↗

Overview of Thermal Design and Challenges for the Comet Astrobiology Exploration SAmple Return (CAESAR) Mission

The Comet Astrobiology Exploration SAmple Return (CAESAR) mission is one of two candidates selected by NASA in response to the New Frontiers 4 Announcement of Opportunity. If selected, CAESAR will fly to comet 67P/Churyumov-Gerasimenko (the same comet studied by ESA’s Rosetta mission) using solar electric propulsion. After some time in orbit around 67P collecting and analyzing images of 67P, a location for collecting a sample will be determined. Up to three “touch-and-go” maneuvers, similar to NASA’s OSIRIS-REx mission, can be attempted with the requirement of collecting at least 80 g of comet sample. Once the sample has been collected, it will be stored in the Sample Containment Subsystem (SCS) and the comet volatiles will be transferred into the Gas Containment System (GCS) for the return cruise back to Earth. As CAESAR approaches Earth, the Sample Return Capsule (SRC), containing the GCS and SCS will separate from the spacecraft and return back to Earth. The sample will be recovered and placed into cold storage for future studies and investigations. CAESAR presents a number of thermal challenges including significantly different power configurations and orientation constraints throughout the mission as well as a large number of mechanisms and configurations that must function at very cold temperatures. The temperature requirements for preserving the sample also present a challenge. This paper presents some of the high level thermal requirements and describes how the CAESAR thermal design was driven by these requirements.

Peabody, Hume L.↗

TPSAS-NF1676L-14864-DND

Objective 1: Develop a research test-bed and database to provide data/proof of concept for Ground Control Station (GCS) NAS operations. Objective 2: Coordinate with standards organizations to develop human factors guidelines for GCS operation in the NAS.

Anna Trujillo↗

TPSAS-NF1676L-14989-DND

Objective 1: Develop a research test-bed and database to provide data/proof of concept for Ground Control Station (GCS) NAS operations. Objective 2: Coordinate with standards organizations to develop human factors guidelines for GCS operation in the NAS. Interest in UAS routine access: 1) Federal government – DHS, NOAA, Commerce, Interior, FBI, DOT 2) Military 3) Local governments – police, fire, port authority 4) Commercial – utilities, news agencies, private security, photographers, hobbyists

Anna Trujillo↗

m:N ConOps/R&R Remote Simulation

This presentation details the experimental design of an investigation of small unmanned aircraft system (sUAS) operations involving multiple vehicle management by a remote operator. The study is part of an ongoing effort to explore multiple vehicle control by multiple operators, i.e., the control of N vehicles by m operators (m:N operations). For this effort, NASA and collaborators have developed prototypes of a concept of operations (ConOps), roles and responsibilities (R&R) for operators and supervisors, and a ground control station (GCS), including software displays and interfaces. Participants in this study acted as the pilot-in-command of twelve aircraft flying pre-approved routes in a simulation of a food delivery operation utilizing sUAS in the San Diego, CA area. Each participant experienced four experimental trials. Twice within the course of each trial, participants were responsible for responding to a sudden, unanticipated, and high-priority contingency: an airspace restriction for sUAS operations known as a UAS Volume Reservation (UVR). Upon issuance of a UVR, pilots were expected to reroute affected vehicles around the airspace. The level of automation (LoA) and workload of the flight rerouting task were varied. The LoA was manipulated by providing reroute suggestions ("auto" condition) for aircraft or by requiring pilots to manually reroute ("manual" condition) affected vehicles. Workload was varied as a function of the number of vehicles affected by the UVR contingencies: 2 vehicles ("low workload" condition) versus 4 vehicles ("high workload" condition). Additionally, some vehicles required pilots to adjust for terrain conflicts while avoiding the UVR region. Due to the COVID-19 pandemic, in-person data collection for this study was not possible. Researchers adapted to this circumstance through the development of remote data collection protocol. Participants were able to view adapted GCS displays using the Microsoft Teams teleconferencing platform and responded to events by using a verbal protocol developed for the experiment. Using this protocol, participants provided instructions for actions to a researcher, referred to as the surrogate, to carry out on their behalf. This presentation describes the experiment design, including special details for remote data collection via a subject-surrogate configuration, and concludes with planned data analysis and results to be presented at a later date.

multi-UAS↗

A Cognitive Walkthrough of Multiple Drone Delivery Operations

Advances of early twenty-first century aviation and transportation technologies provide opportunities for enhanced aerial projects, and the overall integration of unmanned aircraft systems (UAS) into the National Airspace System (NAS) has applications across a wide range of operations. Through these, remote operators have learned to manage several UAS at the same time in a variety of operational environments. The present work details a component piece of an ongoing body of research into multi-UAS operations. Beginning in early 2020, NASA has collaborated with Uber Technologies to design and develop concepts of operations, roles and responsibilities, and ground control station (GCS) concepts to enable food delivery operations via multiple, small UAS (sUAS). A cognitive walkthrough was chosen as the method for data collection. This allowed information to be gathered from UAS subject matter experts (SMEs) that could further mature designs for future human-in-the-loop (HITL) simulations; in addition, it allowed information to be collected remotely during the stringent restrictions of the COVID-19 pandemic. Consequently, the described cognitive walkthrough activity utilized remote data collection protocols mediated through the usage of programs designed for presentation and telecommunications. Scenarios were designed, complete with airspace, contingencies, and remedial actions, to be presented to the SMEs. Information was collected using a combination of rating scales and open-ended questions. Results received from the SMEs revealed expected hazards, workloads, and information concerns inherent in the contingency scenarios. SMEs also provided insight into the design of GCS tools and displays as well as the duties and relationships of human operators (i.e., monitors) and automation (i.e., informers and flight managers). Implications of these findings are discussed.

unmanned aircraft systems↗

A Cognitive Walkthrough of Multiple Drone Delivery Operations

Advances of early twenty-first century aviation and transportation technologies provide opportunities for enhanced aerial projects, and the overall integration of unmanned aircraft systems (UAS) into the National Airspace System (NAS) has applications across a wide range of operations. Through these, remote operators have learned to manage several UAS at the same time in a variety of operational environments. The present work details a component piece of an ongoing body of research into multi-UAS operations. Beginning in early 2020, NASA has collaborated with Uber Technologies to design and develop concepts of operations, roles and responsibilities, and ground control station (GCS) concepts to enable food delivery operations via multiple, small UAS (sUAS). A cognitive walkthrough was chosen as the method for data collection. This allowed information to be gathered from UAS subject matter experts (SMEs) that could further mature designs for future human-in-the-loop (HITL) simulations; in addition, it allowed information to be collected remotely during the stringent restrictions of the COVID-19 pandemic. Consequently, the described cognitive walkthrough activity utilized remote data collection protocols mediated through the usage of programs designed for presentation and telecommunications. Scenarios were designed, complete with airspace, contingencies, and remedial actions, to be presented to the SMEs. Information was collected using a combination of rating scales and open-ended questions. Results received from the SMEs revealed expected hazards, workloads, and information concerns inherent in the contingency scenarios. SMEs also provided insight into the design of GCS tools and displays as well as the duties and relationships of human operators (i.e., monitors) and automation (i.e., informers and flight managers). Implications of these findings are discussed.

unmanned aircraft systems↗

Is the M81 fast radio burst host globular cluster special?

We use multiband archival Hubble Space Telescope (HST) observations to measure the photometric and structural parameters of the M81 globular cluster (GC) that hosts the fast radio burst FRB 20200120E. Our best-fitting King model has an effective radius rh = 3.06 pc with a moderate King model concentration of c = 53, and an inferred core radius of 0.81 pc. We revisit the exact astrometric location of the FRB within the cluster, and find that FRB 20200120E is located 1.92 pc from the center, but within the projected half-light radius. We estimate the relative encounter rate of the FRB host, along with the corresponding rates of 210 other GCs in M81, and compare these values with the encounter rates of Galactic GCs. The FRB resides in a GC with an encounter rate that is moderately higher than the median stellar encounter rate in our two comparison samples. While the estimated encounter rate of the FRB host cluster (e.g., ∼50% of a cluster like 47 Tuc) is sufficient to allow the possibility that the FRB formed dynamically, our results do not place strong constraints on this scenario due to the limitations of the available HST data and the possible systematic uncertainties and selection effects in the comparison data.

Kristen C. Dage↗

Overview

The creation of a spherical model in cylindrical geometry is discussed. The model requires a radial body force to simulate gravity. This force is achieved by dielectric effects on a liquid in the presence of a large voltage, but in the terrestrial laboratory it cannot be made large enough to overwhelm gravity. However, in an orbiting vehicle like Spacelab, this dielectric force will dominate. The behavior of a stripped down general circulation system (GCS) is a salient omission of GCM. It is suggested that the system will contribute to global weather and climate studies.

Fowlis, W. W.↗

Application of the Hardman methodology to the Army Remotely Piloted Vehicle (RPV)

The application of the HARDMAN Methodology to the Remotely Piloted Vehicle (RPV) is described. The methodology was used to analyze the manpower, personnel, and training (MPT) requirements of the proposed RPV system design for a number of operating scenarios. The RPV system is defined as consisting of the equipment, personnel, and operational procedures needed to perform five basic artillery missions: reconnaissance, target acquisition, artillery adjustment, target designation and damage assessment. The RPV design evaluated includes an air vehicle (AV), a modular integrated communications and navigation system (MICNS), a ground control station (GCS), a launch subsystem (LS), a recovery subsystem (RS), and a number of ground support requirements. The HARDMAN Methodology is an integrated set of data base management techniques and analytic tools, designed to provide timely and fully documented assessments of the human resource requirements associated with an emerging system's design.

Source record↗

Software reliability studies

The longterm goal of this research is to identify or create a model for use in analyzing the reliability of flight control software. The immediate tasks addressed are the creation of data useful to the study of software reliability and production of results pertinent to software reliability through the analysis of existing reliability models and data. The completed data creation portion of this research consists of a Generic Checkout System (GCS) design document created in cooperation with NASA and Research Triangle Institute (RTI) experimenters. This will lead to design and code reviews with the resulting product being one of the versions used in the Terminal Descent Experiment being conducted by the Systems Validations Methods Branch (SVMB) of NASA/Langley. An appended paper details an investigation of the Jelinski-Moranda and Geometric models for software reliability. The models were given data from a process that they have correctly simulated and asked to make predictions about the reliability of that process. It was found that either model will usually fail to make good predictions. These problems were attributed to randomness in the data and replication of data was recommended.

Wilson, Larry W.↗

An evaluation of a DO-178A software development process

The guidance and control software (GCS) experiment is an effort to generate realistic software failure data by developing three implementations of a guidance and control software application according to the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines. The authors describe their approach for evaluating the DO-178A guidelines and give results from the development and verification process for the Pluto implementation. The other names are Mercury and Earth. The preliminary analysis of the Pluto implementation has already yielded some results that will be interesting to track for the other implementations.

Shagnea, Anita M.↗

Statistical modeling of software reliability

This working paper discusses the statistical simulation part of a controlled software development experiment being conducted under the direction of the System Validation Methods Branch, Information Systems Division, NASA Langley Research Center. The experiment uses guidance and control software (GCS) aboard a fictitious planetary landing spacecraft: real-time control software operating on a transient mission. Software execution is simulated to study the statistical aspects of reliability and other failure characteristics of the software during development, testing, and random usage. Quantification of software reliability is a major goal. Various reliability concepts are discussed. Experiments are described for performing simulations and collecting appropriate simulated software performance and failure data. This data is then used to make statistical inferences about the quality of the software development and verification processes as well as inferences about the reliability of software versions and reliability growth under random testing and debugging.

Miller, Douglas R.↗

Autonomous control

KSC has been developing the Knowledge-Based Autonomous Test Engineer (KATE), which is a tool for performing automated monitoring, diagnosis, and control of electromechanical devices. KATE employs artificial intelligence computing techniques to perform these functions. The KATE system consists of a generic shell and a knowledge base. The KATE shell is the portion of the system which performs the monitoring, diagnosis, and control functions. It is generic in the sense that it is application independent. This means that the monitoring activity, for instance, will be performed with the same algorithms regardless of the particular physical device being used. The knowledge base is the portion of the system which contains specific functional and behavorial information about the physical device KATE is working with. Work is nearing completion on a project at KSC to interface a Texas Instruments Explorer running a LISP version of KATE with a Generic Checkout System (GCS) test-bed to control a physical simulation of a shuttle tanking system (humorously called the Red Wagon because of its color and mobility). The Autonomous Control System (ACS) project supplements and extends the KATE/GCS project by adding three other major activities. The activities include: porting KATE from the Texas Instruments Explorer machine to an Intel 80386-based UNIX workstation in the LISP language; rewriting KATE as necessary to run on the same 80386 workstation but in the Ada language; and investigating software and techniques to translate ANSI Standard Common LISP to Mil Standard Ada. Primary goals of this task are as follows: (1) establish the advantages of using expert systems to provide intelligent autonomous software for Space Station Freedom applications; (2) determine the feasibility of using Ada as the run-time environment for model-based expert systems; (3) provide insight into the advantages and disadvantagesof using LISP or Ada in the run-time environment for expert systems; and (4) compare the performance of the 80386 processor to a symbolic processor as a delivery vehicle for expert systems.

Brown, Barbara↗

The Discovery of a Second Luminous Low Mass X-ray Binary in the Globular Cluster M15

We report an observation by the Chandra X-ray Observatory of 4U2127+119, the X-ray source identified with the globular cluster M15. The Chandra observation reveals that 4U2127+119 is in fact two bright sources, separated by 2.7". One source is associated with AC21 1, the previously identified optical counterpart to 4U2127+119, a low mass X-ray binary (LMXB). The second source, M15-X2, is coincident with a 19th U magnitude blue star that is 3.3" from the cluster core. The Chandra count rate of M15-X2 is 2.5 times higher than that of AC211. Prior to the 0.5" imaging capability of Chandra the presence of two so closely separated bright sources would not have been resolved, The optical counterpart, X-ray luminosity and spectrum of M15-X2 are consistent with it also being an LMXB system. This is the first time that two LMXBS have been seen to be simultaneously active in a globular cluster. The discovery of a second active LMXB in M15 solves a long standing puzzle where the properties of AC211 appear consistent with it being dominated by an extended accretion disk corona, and yet 4U2127+119 also shows luminous X-ray bursts requiring that the neutron star be directly visible. The resolution of 4U2127+119 into two sources suggests that the X-ray bursts did not come from AC211, but rather from M15X2. We discuss the implications of this discovery for understanding the origin and evolution of LMXBs in GCs as well as X-ray observations of globular clusters in nearby galaxies.

White, Nicholas E.↗

X-Ray Emission from the Halo of M31

Our goal was to use short (10 ksec) observations of selected fields in the halo of M31, to determine the size and characteristics of its X-ray population and to study the connection between globular clusters and X-ray sources. The program of observations has yet to be successfully completed. We received acceptable data from just 2 of the 5 approved fields. Nevertheless, the results were intriguing and we have submitted a paper based on this data to Nature. We find that the X-ray source density is significantly enhanced in the vicinity of one GC, providing the first observational evidence supporting the ejection hypothesis. We also find additional X-ray sources, including some which are very soft, in large enough numbers to suggest that not all could have been formed in GCs. That is, some must be descended from the same primordial halo population that produced any compact stars comprising part of the halo's dark matter. Extrapolating fiom the X-ray source population, we estimate that stellar remnants and dim old stars in the halo could comprise as much as 25% of the estimated mass (approx. 10(exp 12) Solar Mass) of the halo. These results suggest that the other approved fields should be observed soon and also provide strong motivation for the future XMM-Newton programs.

Mushotzky, Richard↗