Search NASA⌕ Search

SEARCH · Search NASA

Results for “NAVIGATION AND GUIDANCE”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS2000

Supporting Development of Satellite's Guidance Navigation and Control Software: A Product Line Approach

The NASA Goddard Space Flight Center Flight Software Branch (FSB) is developing a Guidance, Navigation, and Control (GNC) Flight Software (FSW) product line. The demand for increasingly more complex flight software in less time while maintaining the same level of quality has motivated us to look for better FSW development strategies. The GNC FSW product line has been planned to address the core GNC FSW functionality very similar on many recent low/near Earth missions in the last ten years. Unfortunately these missions have not accomplished significant drops in development cost since a systematic approach towards reuse has not been adopted. In addition, new demands are continually being placed upon the FSW which means the FSB must become more adept at providing GNC FSW functionality's core so it can accommodate additional requirements. These domain features together with engineering concepts are influencing the specification, description and evaluation of FSW product line. Domain engineering is the foundation for emerging product line software development approaches. A product line is 'A family of products designed to take advantage of their common aspects and predicted variabilities'. In our product line approach, domain engineering includes the engineering activities needed to produce reusable artifacts for a domain. Application engineering refers to developing an application in the domain starting from reusable artifacts. The focus of this paper is regarding the software process, lessons learned and on how the GNC FSW product line manages variability. Existing domain engineering approaches do not enforce any specific notation for domain analysis or commonality and variability analysis. Usually, natural language text is the preferred tool. The advantage is the flexibility and adapt ability of natural language. However, one has to be ready to accept also its well-known drawbacks, such as ambiguity, inconsistency, and contradictions. While most domain analysis approaches are functionally oriented, the idea of applying the object-oriented approach in domain analysis is not new. Some authors propose to use UML as the notation underlying domain analysis. Our work is based on the same idea of merging UML and domain analysis. Further, we propose a few extensions to UML in order to express variability, and we define precisely their semantics so that a tool can support them. The extensions are designed to be implemented on the API of a popular industrial CASE tool, with obvious advantages in cost and availability of tool support. The paper outlines the product line processes and identifies where variability must be addressed. Then it describes the product line products with respect to how they accommodate variability. The Celestial Body subdomain is used as a working example. Our results to date are summarized and plans for the future are described.

McComas, David↗
NASA NTRS2017

Guidance, Navigation and Control for the Entry, Descent, and Landing of the Mars 2020 Mission

This paper presents an overview of the Guidance, Navigation and Control (GNC) system for the Entry, Descent, and Landing (EDL) phases of the Mars 2020 Mission. The EDL GNC system adds Terrain Relative Navigation to the MSL EDL GNC system1 to enable landing on landing sites with landing hazards within the landing ellipse. This paper describes the GNC architecture, including sensors, actuators and algorithms, for the entry, parachute descent, and powered flight phases of the mission.

Brugarolas, Paul↗
NASA NTRS1970

Guidance, navigation, and control systems performance analysis: Apollo 13 mission report

The conclusions of the analyses of the inflight performance of the Apollo 13 spacecraft guidance, navigation, and control equipment are presented. The subjects discussed are: (1) the command module systems, (2) the lunar module inertial measurement unit, (3) the lunar module digital autopilot, (4) the lunar module abort guidance system, (5) lunar module optical alignment checks, and (6) spacecraft component separation procedures.

Source record↗
NASA NTRS2021

Mars 2020 Perseverance Entry Descent and Landing Guidance Navigation and Control

On February 18th, 2021, NASA landed Perseverance on the Jezero crater (Mars). This paper presents an overview of the Guidance, Navigation and Control (GNC) system for the Entry, Descent, and Landing (EDL) phases of the Mars 2020 Mission. It describes the GNC architecture, including sensors, actuators and algorithms. It takes the perspective of the GNC mode commander and shows its as-flown performance.

Brugarolas, Paul↗
NASA NTRS1975

NASA Office of Aeronautics and Space Technology Summer Workshop. Volume 3: Navigation, guidance and control panel

User technology requirements are identified in relation to needed technology advancement for future space missions in the areas of navigation, guidance, and control. Emphasis is placed on: reduction of mission support cost by 50% through autonomous operation, a ten-fold increase in mission output through improved pointing and control, and a hundred-fold increase in human productivity in space through large-scale teleoperator applications.

Source record↗
NASA NTRS2002

Contributions to the AIAA Guidance, Navigation and Control Conference

This report contains six papers presented by the Lincoln Laboratory Air Traffic Control Systems Group at the American Institute of Aeronautics & Astronautics (AIAA) Guidance, Navigation and Control (GNC) conference on 6-9 August 2001 in Montreal, Canada. The work reported was sponsored by the NASA Advanced Air Transportation Technologies (AATT) program and the FAA Free Flight Phase 1 (FFP1) program. The papers are based on studies completed at Lincoln Laboratory in collaboration with staff at NASA Ames Research Center. These papers were presented in the Air Traffic Automation Session of the conference and fall into three major areas: Traffic Analysis & Benefits Studies, Weather/Automation Integration and Surface Surveillance. In the first area, a paper by Andrews & Robinson presents an analysis of the efficiency of runway operations at Dallas/Ft. Worth using a tool called PARO, and a paper by Welch, Andrews & Robinson presents a delay benefit results for the Final Approach Spacing Tool (FAST). In the second area, a paper by Campbell, et al describes a new weather distribution systems for the Center/TRACON Automation System (CTAS) that allows ingestion of multiple weather sources, and a paper by Vandevenne, Lloyd & Hogaboom describes the use of the NOAA Eta model as a backup wind data source for CTAS. Also in this area, a paper by Murphy & Campbell presents initial steps towards integrating weather impacted routes into FAST. In the third area, a paper by Welch, Bussolari and Atkins presents an initial operational concept for using surface surveillance to reduce taxi delays.

Campbell, S. D.↗
NASA NTRS2002

Guidance, Navigation and Control Innovations at the NASA Goddard Space Flight Center

This presentation discusses NASA's role in sponsoring on-going research projects involving innovations in spacecraft guidance, navigation and control systems. Topics covered include: partnerships, ESE Spaceborne Missions, spacecraft systems supported and designed by NASA Goddard Flight Center, NASA's changing mission, Large Aperture Sensing Spectrum, Distributed Spacecraft Systems, Landsat-7/ Earth Observer-1 Co-observing Program, and Laser Interferometer Space Antenna program.

Ericsson, Aprille Joy↗
NASA NTRS2010

System Architectural Considerations on Reliable Guidance, Navigation, and Control (GN and C) for Constellation Program (CxP) Spacecraft

This final report summarizes the results of a comparative assessment of the fault tolerance and reliability of different Guidance, Navigation and Control (GN&C) architectural approaches. This study was proactively performed by a combined Massachusetts Institute of Technology (MIT) and Draper Laboratory team as a GN&C "Discipline-Advancing" activity sponsored by the NASA Engineering and Safety Center (NESC). This systematic comparative assessment of GN&C system architectural approaches was undertaken as a fundamental step towards understanding the opportunities for, and limitations of, architecting highly reliable and fault tolerant GN&C systems composed of common avionic components. The primary goal of this study was to obtain architectural 'rules of thumb' that could positively influence future designs in the direction of an optimized (i.e., most reliable and cost-efficient) GN&C system. A secondary goal was to demonstrate the application and the utility of a systematic modeling approach that maps the entire possible architecture solution space.

Dennehy, Cornelius J.↗
NASA NTRS2010

Configuring the Orion Guidance, Navigation, and Control Flight Software for Automated Sequencing

The Orion Crew Exploration Vehicle is being designed with greater automation capabilities than any other crewed spacecraft in NASA s history. The Guidance, Navigation, and Control (GN&C) flight software architecture is designed to provide a flexible and evolvable framework that accommodates increasing levels of automation over time. Within the GN&C flight software, a data-driven approach is used to configure software. This approach allows data reconfiguration and updates to automated sequences without requiring recompilation of the software. Because of the great dependency of the automation and the flight software on the configuration data, the data management is a vital component of the processes for software certification, mission design, and flight operations. To enable the automated sequencing and data configuration of the GN&C subsystem on Orion, a desktop database configuration tool has been developed. The database tool allows the specification of the GN&C activity sequences, the automated transitions in the software, and the corresponding parameter reconfigurations. These aspects of the GN&C automation on Orion are all coordinated via data management, and the database tool provides the ability to test the automation capabilities during the development of the GN&C software. In addition to providing the infrastructure to manage the GN&C automation, the database tool has been designed with capabilities to import and export artifacts for simulation analysis and documentation purposes. Furthermore, the database configuration tool, currently used to manage simulation data, is envisioned to evolve into a mission planning tool for generating and testing GN&C software sequences and configurations. A key enabler of the GN&C automation design, the database tool allows both the creation and maintenance of the data artifacts, as well as serving the critical role of helping to manage, visualize, and understand the data-driven parameters both during software development and throughout the life of the Orion project.

Odegard, Ryan G.↗
NASA NTRS1971

A guide to onboard checkout. Volume 1: Guidance, navigation and control

The results are presented of a study of onboard checkout techniques, as they relate to space station subsystems, as a guide to those who may need to implement onboard checkout in similar subsystems. Guidance, navigation, and control subsystems, and their reliability and failure analyses are presented. Software and testing procedures are also given.

Source record↗
NASA NTRS1988

Independent Orbiter Assessment (IOA): Assessment of the guidance, navigation, and control subsystem FMEA/CIL

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA effort first completed an analysis of the Guidance, Navigation, and Control System (GNC) hardware, generating draft failure modes and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. The IOA results were then compared to the NASA FMEA/CIL baseline with proposed Post 51-L updates included. A resolution of each discrepancy from the comparison is provided through additional analysis as required. The results of that comparison for the Orbiter GNC hardware is documented. The IOA product for the GNC analysis consisted of 141 failure mode worksheets that resulted in 24 potential critical items being identified. Comparison was made to the NASA baseline which consisted of 148 FMEAs and 36 CIL items. This comparison produced agreement on all but 56 FMEAs which caused differences in zero CIL items.

Trahan, W. H.↗
NASA NTRS2005

Spacecraft guidance, navigation, and control requirements for an intelligent plug-n-play avionics (PAPA) architecture

The objective of this research is to design an intelligent plug-n-play avionics system that provides a reconfigurable platform for supporting the guidance, navigation and control (GN&C) requirements for different elements of the space exploration mission. The focus of this study is to look at the specific requirements for a spacecraft that needs to go from earth to moon and back. In this regard we will identify the different GN&C problems in various phases of flight that need to be addressed for designing such a plug-n-play avionics system. The Apollo and the Space Shuttle programs provide rich literature in terms of understanding some of the general GN&C requirements for a space vehicle. The relevant literature is reviewed which helps in narrowing down the different GN&C algorithms that need to be supported along with their individual requirements.

Kulkarni, Nilesh↗
NASA NTRS2019

Adaptations of Guidance, Navigation and Control Verification and Validation Philosophies for Small Spacecraft

Decades of experience developing increasingly capable and more complex space-craft have resulted in a set of accepted practices and philosophies to verify and validate (V&V) guidance, navigation, and control (GN&C) subsystems. Until recently, small, low-cost spacecraft have had very simple or non-existent GN&C subsystems requiring minimal or no subsystem testing. As the next generation of small spacecraft take on more challenging GN&C requirements, the GN&C community is struggling with how to scale the subsystem V&V effort to produce spacecraft approaching the reliability of flagship-class missions while staying within the reduced resources of a small satellite project. For this paper, we will examine five aspects of GN&C V&V (requirements definition, software testing and analysis, hardware component testing, integrated vehicle testing, and in-flight V&V) and compare the V&V campaign of a flagship-class mission (Mars 2020) to that of two recent, successful CubeSat missions: ASTERIA and MarCO. Experiences from the development of these CubeSats yield valuable lessons learned and guidelines for future small spacecraft designers.

Pong, Christopher M.↗
NASA NTRS2019

Adaptations of guidance, navigation, and control verification and validation philosophies for small spacecraft

Decades of experience developing increasingly capable and more complex space-craft have resulted in a set of accepted practices and philosophies to verify and validate (V&V) guidance, navigation, and control (GN&C) subsystems. Until recently, small, low-cost spacecraft have had very simple or non-existent GN&C subsystems requiring minimal or no subsystem testing. As the next generation of small spacecraft take on more challenging GN&C requirements, the GN&C community is struggling with how to scale the subsystem V&V effort to produce spacecraft approaching the reliability of flagship-class missions while staying within the reduced resources of a small satellite project.For this paper, we will examine five aspects of GN&C V&V (requirements definition, software testing and analysis, hardware component testing, integrated vehicle testing, and in-flight V&V) and compare the V&V campaign of a flagship-class mission (Mars 2020) to that of two recent, successful CubeSat missions: ASTERIA and MarCO. Experiences from the development of these CubeSats yield valuable lessons learned and guidelines for future small spacecraft designers.

Chen, George T.↗
NASA NTRS2009

Apollo 13 Guidance, Navigation, and Control Challenges

Combustion and rupture of a liquid oxygen tank during the Apollo 13 mission provides lessons and insights for future spacecraft designers and operations personnel who may never, during their careers, have participated in saving a vehicle and crew during a spacecraft emergency. Guidance, Navigation, and Control (GNC) challenges were the reestablishment of attitude control after the oxygen tank incident, re-establishment of a free return trajectory, resolution of a ground tracking conflict between the LM and the Saturn V S-IVB stage, Inertial Measurement Unit (IMU) alignments, maneuvering to burn attitudes, attitude control during burns, and performing manual GNC tasks with most vehicle systems powered down. Debris illuminated by the Sun and gaseous venting from the Service Module (SM) complicated crew attempts to identify stars and prevented execution of nominal IMU alignment procedures. Sightings on the Sun, Moon, and Earth were used instead. Near continuous communications with Mission Control enabled the crew to quickly perform time critical procedures. Overcoming these challenges required the modification of existing contingency procedures.

Goodman, John L.↗
NASA NTRS1993

Vehicle health management for guidance, navigation and control systems

The objective of the program was to architect a vehicle health management (VHM) system for space systems avionics that assures system readiness for launch vehicles and for space-based dormant vehicles. The platforms which were studied and considered for application of VHM for guidance, navigation and control (GN&C) included the Advanced Manned Launch System (AMLS), the Horizontal Landing-20/Personnel Launch System (HL-20/PLS), the Assured Crew Return Vehicle (ACRV) and the Extended Duration Orbiter (EDO). This set was selected because dormancy and/or availability requirements are driving the designs of these future systems.

Radke, Kathleen↗
NASA NTRS1985

Orbital maneuvering vehicle guidance, navigation and control

This paper describes the Orbital Maneuvering Vehicle (OMV) concept and its intended role. It recaps the past activities leading up to the current concept and summarizes the present status and plans. The various types of missions and operating modes required by the OMV are described as the basis of the guidance, navigation and control (GN&C) requirements. The general GN&C problem is outlined with potential hardware solutions.

Huber, W. G.↗
NASA NTRS2019

Guidance, Navigation, and Control for NASA Lunar Pallet Lander

The NASA Lander Technology project is leading the development and integration of the Lunar Pallet Lander (LPL) concept. The objective is to demonstrate precision landing by delivering a payload to the lunar surface within 100 meters of a landing target. Potential landing sites are selected near the lunar pole where water may be present in permanently shadowed regions that could enable future in-situ resource utilization. The LPL is part of a sequence of missions aimed at maturing the necessary technologies, such as lunar precision landing sensors, that will enable the next generation of multi-ton lunar payloads and human landers. This paper provides an overview of the Mission Design, Guidance Navigation and Control (GNC) algorithms, and sensor suite. The results show the LPL simulated trajectory and landing precision performance under nominal and dispersed conditions. The landing precision simulation confirms the need to rely on high-accuracy navigation techniques and sensors such as Terrain Relative Navigation (TRN) and the Navigation Doppler Lidar (NDL), currently being developed for space applications. The results also demonstrate the ability of the guidance and control system to perform a soft lunar touchdown by combining thrust vector control during the solid rocket motor deceleration phase, and pulse engine control, for the liquid powered descent phase.

Orphee, Juan↗