SEARCH · Engineering Papers

Results for “GN&C”

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.

SourceResearch connectionFrom yearThrough year

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

At least 19 records

All sources NASA NTRS DOE OSTI

NASA NTRS2007

NASA CEV On-Orbit GN&C Analysis

The Orion spacecraft orbit GN&C system will be required to perform both ISS servicing missions and Lunar sortie and outpost crew transportation. While certain aspects of these two missions are complementary, the two missions are also distinct in many ways. Common between the missions is a Low Earth Orbit (LEO) rendezvous, one with the ISS And the other with the LSAM/EDS stack prior to trans-lunar insertion. The lunar missions will additionally require Orion to perform orbit maintenance in LLO, perform contingency lunar orbit operations including RPOD with the LSAM, perform the TEI maneuver sequence, and execute the trans-Earth cruise. The NASA-led team developed a reference configuration orbit GN&C system capable of executing all of these activities with the same navigation sensor suite and control effectors while fully meeting the requirements being developed for System Requirements Review in advance of prime contractor selection. This paper will present an overview of the analyses performed to support system trade studies, demonstrate the feasibility of the NASA reference configuration, and validate the Orion system requirements. These analyses include linear covariance techniques, 3-DOF Monte Carlo simulations, 6-DOF Monte Carlo simulations, and analytical evaluations of GN&C systems performed by the NASA-led Orion team to characterize the sensitivities of Orion s various missions and assess the unique challenges of each. The first part of this paper will describe the trade studies that were performed in order to characterize the RPOD system performance for both the ISS and the lunar missions including development of an RPOD operations concept, RPOD trajectories, contingency scenarios, docking mechanism and associated contact conditions, post-contact thrust issues, relative navigation sensors, relative navigation sensor target infrastructure. The paper will also discuss concepts for both manually-piloted and automatically executed scenarios, as well as the remotely-piloted contingency scenario in LLO. The second part of the paper will discuss the analyses performed for lunar and cislunar GN&C performance including the accuracy of the post-insertion lunar orbit, the ability of Orion to hit a particular Earth return entry corridor, attitude control solutions for long-duration surface operations, and autonomous navigation in support of TEI without ground tracking.

DSouza, Chris↗

NASA NTRS1999

Evolution of International Space Station GN&C System Across ISS Assembly Stages

The Guidance Navigation and Control (GN&C) system for the International Space Station is initially implemented by the Functional Cargo Block (FGB) which was built by the Khrunichev Space Center under direct contract to Boeing. This element (Stage 1A/R) was launched on 20 November 1998 and is currently operating on-orbit. The components and capabilities of the FGB Motion Control System (MCS) are described. The next ISS element, which has GN&C functionality will be the Service Module (SM) built by Rocket Space Corporation-Energia. This module is scheduled for launch (Stage 1R) in early 2000. Following activation of the SM GN&C system, the FGB MCS is deactivated and no longer used. The components and capabilities of the SM GN&C system are described. When a Progress vehicle is attached to the ISS it can be used for reboost operations, based on commands provided by the Mission Control Center-Moscow. When a data connection is implemented between the SM and the Progress, the SM can command the Progress thrusters for attitude control and reboosts. On Stage 5A, the U.S. GN&C system will become activated when the U.S. Laboratory is de loyed and installed (launch schedule is currently TBD). The U.S. GN&C system provides non-propulsive control capabilities to support micro-gravity operations and minimize the use of propellant for attitude control, and an independent capability for determining the ISS state vector, attitude, attitude rate. and time.. The components and capabilities of the U.S. GN&C system are described and the interactions between the U.S. and Russian Segment GN&C systems are also described.

Lee, Roscoe↗

NASA NTRS1995

AIAA spacecraft GN&C interface standards initiative: Overview

The American Institute of Aeronautics and Astronautics (AIAA) has undertaken an important standards initiative in the area of spacecraft guidance, navigation, and control (GN&C) subsystem interfaces. The objective of this effort is to establish standards that will promote interchangeability of major GN&C components, thus enabling substantially lower spacecraft development costs. Although initiated by developers of conventional spacecraft GN&C, it is anticipated that interface standards will also be of value in reducing the development costs of micro-engineered spacecraft. The standardization targets are specifically limited to interfaces only, including information (i.e. data and signal), power, mechanical, thermal, and environmental interfaces between various GN&C components and between GN&C subsystems and other subsystems. The current emphasis is on information interfaces between various hardware elements (e.g., between star trackers and flight computers). The poster presentation will briefly describe the program, including the mechanics and schedule, and will publicize the technical products as they exist at the time of the conference. In particular, the rationale for the adoption of the AS1773 fiber-optic serial data bus and the status of data interface standards at the application layer will be presented.

Challoner, A. Dorian↗

NASA NTRS2007

NASA CEV Reference GN&C Architecture

The Orion Crew Exploration Vehicle (CEV) will be the first human spacecraft built by NASA in almost 3 decades and will be the first vehicle to perform both Low Earth Orbit (LEO) missions and lunar missions since Apollo. The awesome challenge of designing a Guidance, Navigation, and Control (GN&C) system for this vehicle that satisfies all of its various mission requirements is countered by the opportunity to take advantage of the improvements in algorithms, software, sensors, and other related GN&C technology over this period. This paper describes the CEV GN&C reference architecture developed to support the overall NASA reference configuration and validate the driving requirements of the Constellation (Cx) Architecture Requirements Document (CARD, Reference 1) and the CEV System Requirements Document (SRD, Reference 2). The Orion GN&C team designed the reference architecture based on the functional allocation of GN&C roles and responsibilities of CEV with respect to the other Cx vehicles, such as the Crew Launch Vehicle (CLV), Earth Departure Stage (EDS), and Lunar Surface Area Module (LSAM), across all flight phases. The specific challenges and responsibilities of the CEV GN&C system from launch pad to touchdown will be introduced along with an overview of the navigation sensor suite, its redundancy management, and flight software (FSW) architecture. Sensors will be discussed in terms of range of operation, data utility within the navigation system, and rationale for selection. The software architecture is illustrated via block diagrams, commensurate with the design aspects.

Tamblyn, Scott↗

NASA NTRS1982

Evaluation of the Shuttle GN&C during powered ascent flight phase

An overview of the ascent trajectory and GN&C (guidance, navigation, and control) system design is followed by a summary of flight test results for the ascent phase of STS-1. The most notable variance from nominal pre-flight predictions was the lofted trajectory observed in first stage due to an unanticipated shift in pitch aerodynamic characteristics from those predicted by wind tunnel tests. The GN&C systems performed as expected on STS-1 throughout powered flight. Following a discussion of the software constants changed for Flight 2 to provide adequate performance margin, a summary of test results from STS-2 and STS-3 is presented. Vehicle trajectory response and GN&C system behavior were very similar to STS-1. Ascent aerodynamic characteristics extracted from the first two test flights were included in the data base used to design the first stage steering and pitch trim profiles for STS-3.

Olson, L.↗

NASA NTRS2010

Observations on the State of NASA's GN&C Engineering Discipline: Results of an Independent Non-Advocate Study

The NASA Technical Fellows periodically conduct State-of-the-Discipline assessments. The GN&C Technical Fellow contracted Harlan Brown & Company in 2007 and 2009 to conduct independent, third party studies to gain unbiased insight and understanding into the attitudes and beliefs of NASA's GN&C Community of Practice (CoP). The paper first outlines the background, objectives and methodology of the studies. The paper then summarizes key study results of the 2007 baseline study, as well as the 2009 update. The update was then used to track and monitor perceptions, identify performance trends, identify areas where further improvement needs to be made in NASA's GN&C discipline. It also generated feedback on the recently developed GN&C CoP online knowledge capture and learning site.

Pawlikowski, Gerald J.↗

NASA NTRSDate not supplied

NESC GN&C TDT Workshop on 2D Image Motion Optical Transfer Functions, Pointing Performance Analysis, and Requirements

This course was prepared by the author in support of the NASA GN&C Technical Discipline Team (TDT). The purpose of this two-day course is to inform practicing GN&C engineers, and other system and subsystem engineers, including payload engineers and mission analysts, of methodologies to analyze the pointing performance of spacecraft and to write unambiguous pointing requirements that are relevant to optical payload performance. It is hoped that the seminar will contribute to a best-practices manual and contribute to accepted and uniform means of requirements definition, validation, and verification. The course material is designed to address the needs of not only practicing GN&C engineers, but also system and subsystem engineers of other disciplines, payload engineers, mission analysts, and even astronomers who need to understand how they interface to a GN&C subsystem. Much revision is the direct result of active student participation during the presentations and from feedback obtained through course evaluation forms.

2D Image↗

NASA NTRS2016

Orion GN&C Detection and Mitigation of Parachute Pendulosity

New techniques being employed by Orion guidance, navigation, and control (GN&C) using a reaction control system (RCS) under parachutes are described. Pendulosity refers to a pendulum-oscillatory mode that can occur during descent under main parachutes and that has been observed during Orion parachute drop tests. The pendulum mode reduces the ability of GN&C to maneuver the suspended vehicle resulting in undesirable increases to structural loads at touchdown. Parachute redesign efforts have been unsuccessful in reducing the pendulous behavior necessitating GN&C mitigation options. An observer has been developed to estimate the pendulum motion as well as the underlying wind velocity vector. Using this knowledge, the control system maneuvers the vehicle using two separate strategies determined by wind velocity magnitude and pendulum energy thresholds; at high wind velocities the vehicle is aligned with the wind direction and for cases with lower wind velocities and large pendulum amplitudes the vehicle is aligned such that it is perpendicular to the swing plane. Pendulum damping techniques using RCS thrusters are discussed but have not been selected for use onboard the Orion spacecraft. The techniques discussed in this paper will be flown on Exploration Mission 1 (EM-1).

Kane, Mark A.↗

NASA NTRS2016

Orion GN&C Detection and Mitigation of Parachute Pendulosity

New techniques being employed by Orion guidance, navigation, and control (GN&C) using a reaction control system (RCS) under parachutes are described. Pendulosity refers to a pendulum-oscillatory mode that can occur during descent under main parachutes and that has been observed during Orion parachute drop tests. The pendulum mode reduces the ability of GN&C to maneuver the suspended vehicle resulting in undesirable increases to structural loads at touch-down. Parachute redesign efforts have been unsuccessful in reducing the pendulous behavior necessitating GN&C mitigation options. An observer has been developed to estimate the pendulum motion as well as the underlying wind velocity vector. Using this knowledge the control system maneuvers the vehicle using two separate strategies determined by a wind velocity magnitude threshold; at high wind velocities the vehicle is aligned with the wind direction and for cases with lower wind velocities the vehicle is aligned such that it is perpendicular to the swing plane. Pendulum damping techniques using RCS thrusters are discussed but have not been selected for use onboard the Orion spacecraft. The techniques discussed in this paper will be flown on Exploration Mission 1 (EM-1).

Kane, Mark A.↗

NASA NTRS1990

Statistical analysis of AFE GN&C aeropass performance

Performance of the guidance, navigation, and control (GN&C) system used on the Aeroassist Flight Experiment (AFE) spacecraft has been studied with Monte Carlo techniques. The performance of the AFE GN&C is investigated with a 6-DOF numerical dynamic model which includes a Global Reference Atmospheric Model (GRAM) and a gravitational model with oblateness corrections. The study considers all the uncertainties due to the environment and the system itself. In the AFE's aeropass phase, perturbations on the system performance are caused by an error space which has over 20 dimensions of the correlated/uncorrelated error sources. The goal of this study is to determine, in a statistical sense, how much flight path angle error can be tolerated at entry interface (EI) and still have acceptable delta-V capability at exit to position the AFE spacecraft for recovery. Assuming there is fuel available to produce 380 ft/sec of delta-V at atmospheric exit, a 3-sigma standard deviation in flight path angle error of 0.04 degrees at EI would result in a 98-percent probability of mission success.

Chang, Ho-Pen↗

NASA NTRS2007

NASA CEV Reference Entry GN&C System and Analysis

As part of its overall objectives, the Orion spacecraft will be required to perform entry and Earth landing functions for Low Earth Orbit (LEO) and Lunar missions. Both of these entry scenarios will begin with separation of the Service Module (SM), making them unique from other Orion mission phases in that only the Command Module (CM) portion of the Crew Exploration Vehicle (CEV) will be involved, requiring a CM specific Guidance, Navigation and Control (GN&C) system. Also common to these mission scenarios will be the need for GN&C to safely return crew (or cargo) to earth within the dynamic thermal and structural constraints of entry and within acceptable accelerations on the crew, utilizing the limited aerodynamic performance of the CM capsule. The lunar return mission could additionally require an initial atmospheric entry designed to support a precision skip and second entry, all to maximize downrange performance and ensure landing in the United States. This paper describes the Entry GN&C reference design, developed by the NASA-led team, that supports these entry scenarios and that was used to validate the Orion System requirements. Description of the reference design will include an overview of the GN&C functions, avionics, and effectors and will relate these to the specific design drivers of the entry scenarios, as well as the desire for commonality in vehicle systems to support the different missions. The discussion will also include the requirement for an Emergency Entry capability beyond that of the nominal performance of the multi-string GNC system, intended to return the crew to the earth in a survivable but unguided manner. Finally, various analyses will be discussed, including those completed to support validation efforts of the current CEV requirements, along with those on-going and planned with the intention to further refine the requirements and to support design development work in conjunction with the prime contractor. Some of these ongoing analyses will include work to size effectors (jets) and fuel budgets, to refine skip entry concepts, to characterize navigation performance and uncertainties, to provide for SM disposal offshore and to identify requirements to support target site selection.

Munday, S.↗

NASA NTRS2008

Guidance, Navigation and Control (GN&C): Best Practices for Human-Rated Spacecraft Systems

In 2007 the NESC completed an in-depth assessment to identify, define and document engineering considerations for the Design Development Test and Evaluation (DDT&E) of human-rated spacecraft systems. This study had been requested by the Astronaut Office at JSC to help them to better understand what is required to ensure safe, robust, and reliable human-rated spacecraft systems. The 22 GN&C engineering Best Practices described in this paper are a condensed version of what appears in the NESC Technical Report. These Best Practices cover a broad range from fundamental system architectural considerations to more specific aspects (e.g., stability margin recommendations) of GN&C system design and development. 15 of the Best Practices address the early phases of a GN&C System development project and the remaining 7 deal with the later phases. Some of these Best Practices will cross-over between both phases. We recognize that this set of GN&C Best Practices will not be universally applicable to all projects and mission applications.

Lebsock, Ken↗

NASA NTRSDate not supplied

Linear Covariance Techniques to Analyze a Multi-Vehicle, Multi-GN&C System with Applications to Rendezvous in a Near Rectilinear Halo Orbit

Typically for a rendezvous and docking scenario, only a single vehicle is considered the active vehicle. As a result, the target vehicle’s GN&C system is typically not a factor in the integrated performance analysis as it assumes a passive role. However, for upcoming NASA Artemis missions the active vehicle is both the chaser and target spacecraft. In addition, both vehicles are cooperating with one another, sharing telemetry data, and relying on data extracted from the GN&C system of the other. The process also includes a team of ground support personnel in mission control are tracking and monitoring each spacecraft uplinking state estimates and targeting solutions to support mission operations and enhance the onboard flight system performance. Being able to quickly analyze the impact of both vehicles with two different GN&C systems that also interact with the ground that does its own navigation and targeting uploads is critical. This paper outlines how to perform this rapid analysis using linear covariance techniques and applies them to a rendezvous scenario initiated in low lunar orbit and completed in a Near Rectilinear Halo Orbit (NRHO) representative of the NASA Artemis III mission.

Linear Covariance Analysis↗

NASA NTRS2019

The SPLICE Project: Continuing NASA Development of GN&C Technologies for Safe and Precise Landing

Guidance, Navigation and Control (GN&C) technologies for precise and safe landing are essential for future robotic science and human exploration missions to solar system destinations with targeted surface locations that pose a signiﬁcant risk to successful landing and subsequent mission operations. These Entry, Descent and Landing (EDL) technologies are a part of the NASA domain called PL&HA (Precision Landing and Hazard Avoidance) and are considered high-priority capabilities within NASA space technology development roadmaps to promote and enable new mission concepts. The SPLICE (Safe & Precise Landing – Integrated Capabilities Evolution) project is a multi-center, multi-directorate NASA project focused on continuing the decade-plus of NASA investments and projects focused on PL&HA technology development and infusion. This paper highlights the GN&C technologies in development within SPLICE, along with the simulation and ﬁeld test plans for validation of the capabilities and Technology Readiness Level (TRL) maturation toward infusion into potential near-term robotic lunar landing missions.

Tse, Teming↗

NASA NTRS2010

Exploiting Expertise and Knowledge Sharing Online for the Benefit of NASA's GN&C Community of Practice

In 2004, NASA faced major knowledge sharing challenges due to geographically isolated field centers that inhibited engineers from sharing their experiences, expertise, ideas, and lessons learned. The necessity to collaborate on complex development projects and the reality of constrained project resources together drove the need for ensuring that personnel at all NASA centers had comparable skill sets and that engineers could find resources in a timely fashion. Mission failures and new directions for the Agency also demanded better collaborative tools for NASA's engineering workforce. In response to these needs, the online NASA Engineering Network (NEN) was formed by the NASA Office of the Chief Engineer to provide a multi-faceted system for overcoming geographic and cultural barriers. NEN integrates communities of practice with a cross-repository search and the Lessons Learned Information System. This paper describes the features of the GN&C engineering discipline CoP site which went live on NEN in May of 2008 as an online means of gathering input and guidance from practitioners. It allows GN&C discipline expertise captured at one field center to be shared in a collaborative way with the larger discipline CoP spread across the entire Agency. The site enables GN&C engineers to find the information they need quickly, to find solutions to questions from experienced engineers, and to connect with other practitioners regardless of geographic location, thus increasing the probability of project success.

control↗

NASA NTRS2020

GN&C Sequencing for Orion Rendezvous, Proximity Operations, and Docking

As part of the Artemis program to return humans to the lunar surface, the National Aeronautics and Space Administration is planning to use the Orion Multi- Purpose Crew Vehicle to transport crew to a small orbital platform called Gate- way in cislunar space. To facilitate this activity, Orion is required to perform Rendezvous, Proximity Operations, and Docking (RPOD) with both the Gate- way and the launch vehicle upper stage. The Orion spacecraft uses sequencing in the form of Phases, Segments, Activities, and Modes (PSAM) to configure Guidance, Navigation, & Control (GN&C) software during each portion of the mission. Significant updates to Orion PSAM definitions are required for RPOD. This paper describes the process of defining these new sequencing elements, implementing them in prototype flight software, and testing them in an integrated simulation environment. First, requirements are specified to determine the nominal and off-nominal sequencing behavior necessary to complete the mission. These requirements also specify which software functions should be fully autonomous and which functions require manual interactions from crew or ground operators. Next, the RPOD concept of operations is defined with detailed events listed in a mission timeline. Third, a state machine diagram is developed to show all PSAM states, including all possible transitions between them. After this, the PSAM states and transitions are entered into a sequencing software emulator and parameter values and modes are defined for GN&C software elements. Finally, the PSAM architecture is tested within an integrated simulation environment by connecting it with prototypes of relevant GN&C flight software elements and with detailed vehicle models. After the sequencing design has been finalized and tested, it is implemented in flight software.

Schulte, Peter Z.↗

NASA NTRS2010

The Value of Identifying and Recovering Lost GN&C Lessons Learned: Aeronautical, Spacecraft, and Launch Vehicle Examples

Within the broad aerospace community the importance of identifying, documenting and widely sharing lessons learned during system development, flight test, operational or research programs/projects is broadly acknowledged. Documenting and sharing lessons learned helps managers and engineers to minimize project risk and improve performance of their systems. Often significant lessons learned on a project fail to get captured even though they are well known 'tribal knowledge' amongst the project team members. The physical act of actually writing down and documenting these lessons learned for the next generation of NASA GN&C engineers fails to happen on some projects for various reasons. In this paper we will first review the importance of capturing lessons learned and then will discuss reasons why some lessons are not documented. A simple proven approach called 'Pause and Learn' will be highlighted as a proven low-impact method of organizational learning that could foster the timely capture of critical lessons learned. Lastly some examples of 'lost' GN&C lessons learned from the aeronautics, spacecraft and launch vehicle domains are briefly highlighted. In the context of this paper 'lost' refers to lessons that have not achieved broad visibility within the NASA-wide GN&C CoP because they are either undocumented, masked or poorly documented in the NASA Lessons Learned Information System (LLIS).

Dennehy, Cornelius J.↗

NASA NTRS1993

Cooperative GN&C development in a rapid prototyping environment

The Navigation, Control and Aeronautics Division (NCAD) at NASA-JSC is exploring ways of producing Guidance, Navigation and Control (GN&C) flight software faster, better, and cheaper. To achieve these goals NCAD established two hardware/software facilities that take an avionics design project from initial inception through high fidelity real-time hardware-in-the-loop testing. Commercially available software products are used to develop the GN&C algorithms in block diagram form and then automatically generate source code from these diagrams. A high fidelity real-time hardware-in-the-loop laboratory provides users with the capability to analyze mass memory usage within the targeted flight computer, verify hardware interfaces, conduct system level verification, performance, acceptance testing, as well as mission verification using reconfigurable and mission unique data. To evaluate these concepts and tools, NCAD embarked on a project to build a real-time 6 DOF simulation of the Soyuz Assured Crew Return Vehicle flight software. To date, a productivity increase of 185 percent has been seen over traditional NASA methods for developing flight software.

Bordano, Aldo↗