Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 703 records · Page 39

GN and C Design Overview and Flight Test Results from NASA's Max Launch Abort System (MLAS)

The National Aeronautics and Space Administration (NASA) Engineering and Safety Center (NESC) designed, developed and flew the alternative Max Launch Abort System (MLAS) as risk mitigation for the baseline Orion spacecraft launch abort system (LAS) already in development. The NESC was tasked with both formulating a conceptual objective system (OS) design of this alternative MLAS as well as demonstrating this concept with a simulated pad abort flight test. The goal was to obtain sufficient flight test data to assess performance, validate models/tools, and to reduce the design and development risks for a MLAS OS. Less than 2 years after Project start the MLAS simulated pad abort flight test was successfully conducted from Wallops Island on July 8, 2009. The entire flight test duration was 88 seconds during which time multiple staging events were performed and nine separate critically timed parachute deployments occurred as scheduled. Overall, the as-flown flight performance was as predicted prior to launch. This paper provides an overview of the guidance navigation and control (GN&C) technical approaches employed on this rapid prototyping activity. This paper describes the methodology used to design the MLAS flight test vehicle (FTV). Lessons that were learned during this rapid prototyping project are also summarized.

Dennehy, Cornelius J.↗

Present Challenges, Critical Needs, and Future Technological Directions for NASA's GN and C Engineering Discipline

The National Aeronautics and Space Administration (NASA) is currently undergoing a substantial redirection. Notable among the changes occurring within NASA is the stated emphasis on technology development, integration, and demonstration. These new changes within the Agency should have a positive impact on the GN&C discipline given the potential for sizeable investments for technology development and in-space demonstrations of both Autonomous Rendezvous & Docking (AR&D) systems and Autonomous Precision Landing (APL) systems. In this paper the NASA Technical Fellow for Guidance, Navigation and Control (GN&C) provides a summary of the present technical challenges, critical needs, and future technological directions for NASA s GN&C engineering discipline. A brief overview of the changes occurring within NASA that are driving a renewed emphasis on technology development will be presented as background. The potential benefits of the planned GN&C technology developments will be highlighted. This paper will provide a GN&C State-of-the-Discipline assessment. The discipline s readiness to support the goals & objectives of each of the four NASA Mission Directorates is evaluated and the technical challenges and barriers currently faced by the discipline are summarized. This paper will also discuss the need for sustained investments to sufficiently mature the several classes of GN&C technologies required to implement NASA crewed exploration and robotic science missions.

Dennehy, Cornelius J.↗

Accelerating NASA GN&C Flight Software Development

When the guidance, navigation, and control (GN&C) system for the Orion crew vehicle undergoes Critical Design Review (CDR), more than 90% of the flight software will already be developed - a first for NASA on a project of this scope and complexity. This achievement is due in large part to a new development approach using Model-Based Design.

Tamblyn, Scott↗

Multiple Kernel Learning for Heterogeneous Anomaly Detection: Algorithm and Aviation Safety Case Study

The world-wide aviation system is one of the most complex dynamical systems ever developed and is generating data at an extremely rapid rate. Most modern commercial aircraft record several hundred flight parameters including information from the guidance, navigation, and control systems, the avionics and propulsion systems, and the pilot inputs into the aircraft. These parameters may be continuous measurements or binary or categorical measurements recorded in one second intervals for the duration of the flight. Currently, most approaches to aviation safety are reactive, meaning that they are designed to react to an aviation safety incident or accident. In this paper, we discuss a novel approach based on the theory of multiple kernel learning to detect potential safety anomalies in very large data bases of discrete and continuous data from world-wide operations of commercial fleets. We pose a general anomaly detection problem which includes both discrete and continuous data streams, where we assume that the discrete streams have a causal influence on the continuous streams. We also assume that atypical sequence of events in the discrete streams can lead to off-nominal system performance. We discuss the application domain, novel algorithms, and also discuss results on real-world data sets. Our algorithm uncovers operationally significant events in high dimensional data streams in the aviation industry which are not detectable using state of the art methods

Das, Santanu↗

Propellant Sloshing Parameter Extraction from CFD Analysis

Propellant slosh is a potential source of disturbance critical to the stability of space vehicle. The sloshing dynamics is typically represented by a mechanical model of spring mass damper. This mechanical model is then included in the equation of motion of the entire vehicle for Guidance, Navigation and Control analysis. The typical parameters required by the mechanical model include natural frequency of the sloshing, sloshing mass, sloshing mass center coordinates, and critical damping coefficient. During the 1960 s US space program, these parameters were either computed from analytical solution for simple geometry or by experimental testing for the sub-scaled configurations. The purpose of this work is to demonstrate the soundness of a CFD approach in modeling the detailed fluid dynamics of tank sloshing and the excellent accuracy in extracting mechanical properties for different tank configurations and at different fill levels. The validation studies included straight cylinder against analytical solution, and sub-scaled Centaur LOX and LH2 tanks with and without baffles against experimental results. This effort shows that CFD technology can provide accurate mechanical parameters for any tank configuration, and is especially valuable to the future design of propellant tanks, as there is no previous experimental data available for the same size and configuration.

Yang, H. Q.↗

ARES I-X: The First Test Flight of a New Era

On October 28th, 2009, the National Aeronautics and Space Administration (NASA) launched the Ares I-X Flight Test Vehicle (FTV) from pad 39B, providing the first set of flight test data for NASA's Ares I vehicle design team. This test was critical in providing insight into areas were significant design challenges existed. This paper discusses the objectives of the mission and how they were satisfied. It discusses the overall results of the flight test and look at the data retrieved from the flight. Ares I-X was highly instrumented with over 700 channels of Developmental Flight Instrumentation (DFI). Significant insight was gained in the areas of thrust oscillation, vibro-acoustics, predicting jet interactions and slag ejection from solid rocket systems with submerged nozzles. The paper outlines results from the Guidance Navigation & Control (GN&C), Thermal, Vibro-acoustic, Structures, Aero, Aero-Acoustic and Trajectory teams.

Smith, R. Marshall↗

ISWHM: Tools and Techniques for Software and System Health Management

This presentation presents status and results of research on Software Health Management done within the NRA "ISWHM: Tools and Techniques for Software and System Health Management." Topics include: Ingredients of a Guidance, Navigation, and Control System (GN and C); Selected GN and C Testbed example; Health Management of major ingredients; ISWHM testbed architecture; and Conclusions and next Steps.

Schumann, Johann↗

ISS GN and C - First Year Surprises

Assembly of the International Space Station (ISS) began in late 1998 with the joining of the first two US and Russ ian elements. For more than two years, the outpost was served by two Russian Guidance, Navigation, and Control (GN&C) systems. The station requires orbital translation and attitude control functions for its 100+ configurations, from the nascent two-module station to the half million kilogram completed station owned and operated by seventeen nations. With the launch of the US Laboratory module in February 2001, the integration of the US GN&C system with its Russian counterpart laid the foundation for such a robust system. In its first year of combined operation, the ISS GN&C system has performed admirably, even better than many expected, but there have been surprises. Loss of command capability, loss of communication between segments, a control system force-fight, and "non-propulsive vents" that weren't - such events have repeatedly underscored the importance of thorough program integration, testing, and operation, both across subsystem boundaries and across international borders.

Begley, Michael↗

Space Vehicle Powerdown Philosophies Derived from the Space Shuttle Program

In spaceflight, electrical power is a vital but limited resource. Almost every spacecraft system, from avionics to life support systems, relies on electrical power. Since power can be limited by the generation system s performance, available consumables, solar array shading, or heat rejection capability, vehicle power management is a critical consideration in spacecraft design, mission planning, and real-time operations. The purpose of this paper is to capture the powerdown philosophies used during the Space Shuttle Program. This paper will discuss how electrical equipment is managed real-time to adjust the overall vehicle power level to ensure that systems and consumables will support changing mission objectives, as well as how electrical equipment is managed following system anomalies. We will focus on the power related impacts of anomalies in the generation systems, air and liquid cooling systems, and significant environmental events such as a fire, decrease in cabin pressure, or micrometeoroid debris strike. Additionally, considerations for executing powerdowns by crew action or by ground commands from Mission Control will be presented. General lessons learned from nearly 30 years of Space Shuttle powerdowns will be discussed, including an in depth case-study of STS-117. During this International Space Station (ISS) assembly mission, a failure of computers controlling the ISS guidance, navigation, and control system required that the Space Shuttle s maneuvering system be used to maintain attitude control. A powerdown was performed to save power generation consumables, thus extending the docked mission duration and allowing more time to resolve the issue.

Willsey, Mark↗

Space Shuttle Ascent Flight Design Process: Evolution and Lessons Learned

The Space Shuttle Ascent Flight Design team is responsible for defining a launch to orbit trajectory profile that satisfies all programmatic mission objectives and defines the ground and onboard reconfiguration requirements for this high-speed and demanding flight phase. This design, verification and reconfiguration process ensures that all applicable mission scenarios are enveloped within integrated vehicle and spacecraft certification constraints and criteria, and includes the design of the nominal ascent profile and trajectory profiles for both uphill and ground-to-ground aborts. The team also develops a wide array of associated training, avionics flight software verification, onboard crew and operations facility products. These key ground and onboard products provide the ultimate users and operators the necessary insight and situational awareness for trajectory dynamics, performance and event sequences, abort mode boundaries and moding, flight performance and impact predictions for launch vehicle stages for use in range safety, and flight software performance. These products also provide the necessary insight to or reconfiguration of communications and tracking systems, launch collision avoidance requirements, and day of launch crew targeting and onboard guidance, navigation and flight control updates that incorporate the final vehicle configuration and environment conditions for the mission. Over the course of the Space Shuttle Program, ascent trajectory design and mission planning has evolved in order to improve program flexibility and reduce cost, while maintaining outstanding data quality. Along the way, the team has implemented innovative solutions and technologies in order to overcome significant challenges. A number of these solutions may have applicability to future human spaceflight programs.

Picka, Bret A.↗

Natural Language Interface for Safety Certification of Safety-Critical Software

Model-based design and automated code generation are being used increasingly at NASA. The trend is to move beyond simulation and prototyping to actual flight code, particularly in the guidance, navigation, and control domain. However, there are substantial obstacles to more widespread adoption of code generators in such safety-critical domains. Since code generators are typically not qualified, there is no guarantee that their output is correct, and consequently the generated code still needs to be fully tested and certified. The AutoCert generator plug-in supports the certification of automatically generated code by formally verifying that the generated code is free of different safety violations, by constructing an independently verifiable certificate, and by explaining its analysis in a textual form suitable for code reviews.

Denney, Ewen↗

GENIE Flight Test Results and System Overview

NASA has envisioned a suite of lander test vehicles that will be flown in Earth s atmosphere to incrementally demonstrate applicable lunar lander performance in the terrestrial environment. As each terrestrial rocket progresses in maturity, relevant space flight technology matures to a higher technology readiness level, preparing it for inclusion on a future lunar lander design.. NASA s "Project M" lunar mission concept flew its first terrestrial rocket, RR1, in June 2010 in Caddo Mills, Texas. The Draper Laboratory built GENIE (Guidance Embedded Navigator Integration Environment) successfully demonstrated accurate, real time, embedded performance of Project M navigation and guidance algorithms in a highly dynamic environment. The RR1 vehicle, built by Armadillo Aerospace, performed a successful 60 second free flight and gave the team great confidence in Project M s highly reliable and robust GNC system design and implementation. This paper provides an overview of the GENIE system and describes recent flight performance test results onboard the RR1 terrestrial rocket.

Brady, Tye↗

Docking Offset Between the Space Shuttle and the International Space Station and Resulting Impacts to the Transfer of Attitude Reference and Control

The Space Shuttle does not dock at an exact 90 degrees to the International Space Station (ISS) x-body axis. This offset from 90 degrees, along with error sources within their respective attitude knowledge, causes the two vehicles to never completely agree on their attitude, even though they operate as a single, mated stack while docked. The docking offset can be measured in flight when both vehicles have good attitude reference and is a critical component in calculations to transfer attitude reference from one vehicle to another. This paper will describe how the docking offset and attitude reference errors between both vehicles are measured and how this information would be used to recover Shuttle attitude reference from ISS in the event of multiple failures. During STS-117, ISS on-board Guidance, Navigation and Control (GNC) computers began having problems and after several continuous restarts, the systems failed. The failure took the ability for ISS to maintain attitude knowledge. This paper will also demonstrate how with knowledge of the docking offset, the contingency procedure to recover Shuttle attitude reference from ISS was reversed in order to provide ISS an attitude reference from Shuttle. Finally, this paper will show how knowledge of the docking offset can be used to speed up attitude control handovers from Shuttle to ISS momentum management. By taking into account the docking offset, Shuttle can be commanded to hold a more precise attitude which better agrees with the ISS commanded attitude such that start up transients with the ISS momentum management controllers are reduced. By reducing start-up transients, attitude control can be transferred from Shuttle to ISS without the use of ISS thrusters saving precious on-board propellant, crew time and minimizing loads placed upon the mated stack.

Helms, W. Jason↗

Orion Entry Handling Qualities Assessments

The Orion Command Module (CM) is a capsule designed to bring crew back from the International Space Station (ISS), the moon and beyond. The atmospheric entry portion of the flight is deigned to be flown in autopilot mode for nominal situations. However, there exists the possibility for the crew to take over manual control in off-nominal situations. In these instances, the spacecraft must meet specific handling qualities criteria. To address these criteria two separate assessments of the Orion CM s entry Handling Qualities (HQ) were conducted at NASA s Johnson Space Center (JSC) using the Cooper-Harper scale (Cooper & Harper, 1969). These assessments were conducted in the summers of 2008 and 2010 using the Advanced NASA Technology Architecture for Exploration Studies (ANTARES) six degree of freedom, high fidelity Guidance, Navigation, and Control (GN&C) simulation. This paper will address the specifics of the handling qualities criteria, the vehicle configuration, the scenarios flown, the simulation background and setup, crew interfaces and displays, piloting techniques, ratings and crew comments, pre- and post-fight briefings, lessons learned and changes made to improve the overall system performance. The data collection tools, methods, data reduction and output reports will also be discussed. The objective of the 2008 entry HQ assessment was to evaluate the handling qualities of the CM during a lunar skip return. A lunar skip entry case was selected because it was considered the most demanding of all bank control scenarios. Even though skip entry is not planned to be flown manually, it was hypothesized that if a pilot could fly the harder skip entry case, then they could also fly a simpler loads managed or ballistic (constant bank rate command) entry scenario. In addition, with the evaluation set-up of multiple tasks within the entry case, handling qualities ratings collected in the evaluation could be used to assess other scenarios such as the constant bank angle maintenance case. The 2008 entry assessment was divided into two sections (see Figure 1). Entry I was the first, high speed portion of a lunar return and Entry II was the second, lower speed portion of a lunar return, which is similar (but not identical) to a typical ISS return.

Bihari, B.↗

COMPASS Final Report: Enceladus Solar Electric Propulsion Stage

The results of the NASA Glenn Research Center (GRC) COllaborative Modeling and Parametric Assessment of Space Systems (COMPASS) internal Solar Electric Propulsion (SEP) stage design are documented in this report (Figure 1.1). The SEP Stage was designed to deliver a science probe to Saturn (the probe design was performed separately by the NASA Goddard Space Flight Center s (GSFC) Integrated Mission Design Center (IMDC)). The SEP Stage delivers the 2444 kg probe on a Saturn trajectory with a hyperbolic arrival velocity of 5.4 km/s. The design carried 30 percent mass, 10 percent power, and 6 percent propellant margins. The SEP Stage relies on the probe for substantial guidance, navigation and control (GN&C), command and data handling (C&DH), and Communications functions. The stage is configured to carry the probe and to minimize the packaging interference between the probe and the stage. The propulsion system consisted of a 1+1 (one active, one spare) configuration of gimbaled 7 kW NASA Evolutionary Xenon Thruster (NEXT) ion propulsion thrusters with a throughput of 309 kg Xe propellant. Two 9350 W GaAs triple junction (at 1 Astronomical Unit (AU), includes 10 percent margin) ultra-flex solar arrays provided power to the stage, with Li-ion batteries for launch and contingency operations power. The base structure was an Al-Li hexagonal skin-stringer frame built to withstand launch loads. A passive thermal control system consisted of heat pipes to north and south radiator panels, multilayer insulation (MLI) and heaters for the Xe tank. All systems except tanks and solar arrays were designed to be single fault tolerant.

Oleson, Steven R.↗

Evolution of the Space Shuttle Primary Avionics Software and Avionics for Shuttle Derived Launch Vehicles

As a result of recommendation from the Augustine Panel, the direction for Human Space Flight has been altered from the original plan referred to as Constellation. NASA s Human Exploration Framework Team (HEFT) proposes the use of a Shuttle Derived Heavy Lift Launch Vehicle (SDLV) and an Orion derived spacecraft (salvaged from Constellation) to support a new flexible direction for space exploration. The SDLV must be developed within an environment of a constrained budget and a preferred fast development schedule. Thus, it has been proposed to utilize existing assets from the Shuttle Program to speed development at a lower cost. These existing assets should not only include structures such as external tanks or solid rockets, but also the Flight Software which has traditionally been a "long pole" in new development efforts. The avionics and software for the Space Shuttle was primarily developed in the 70 s and considered state of the art for that time. As one may argue that the existing avionics and flight software may be too outdated to support the new SDLV effort, this is a fallacy if they can be evolved over time into a "modern avionics" platform. The technology may be outdated, but the avionics concepts and flight software algorithms are not. The reuse of existing avionics and software also allows for the reuse of development, verification, and operations facilities. The keyword is evolve in that these assets can support the fast development of such a vehicle, but then be gradually evolved over time towards more modern platforms as budget and schedule permits. The "gold" of the flight software is the "control loop" algorithms of the vehicle. This is the Guidance, Navigation, and Control (GNC) software algorithms. This software is typically the most expensive to develop, test, and verify. Thus, the approach is to preserve the GNC flight software, while first evolving the supporting software (such as Command and Data Handling, Caution and Warning, Telemetry, etc.). This can be accomplished by gradually removing the "support software" from the legacy flight software leaving only the GNC algorithms. The "support software" could be re-developed for modern platforms, while leaving the GNC algorithms to execute on technology compatible with the legacy system. It is also possible to package the GNC algorithms into an emulated version of the original computer (via Field Programmable Gate Arrays or FPGAs), thus becoming a "GNC on a Chip" solution where it could live forever to be embedded in modern avionics platforms.

Ferguson, Roscoe C.↗

High-Payoff Space Transportation Design Approach with a Technology Integration Strategy

A general architectural design sequence is described to create a highly efficient, operable, and supportable design that achieves an affordable, repeatable, and sustainable transportation function. The paper covers the following aspects of this approach in more detail: (1) vehicle architectural concept considerations (including important strategies for greater reusability); (2) vehicle element propulsion system packaging considerations; (3) vehicle element functional definition; (4) external ground servicing and access considerations; and, (5) simplified guidance, navigation, flight control and avionics communications considerations. Additionally, a technology integration strategy is forwarded that includes: (a) ground and flight test prior to production commitments; (b) parallel stage propellant storage, such as concentric-nested tanks; (c) high thrust, LOX-rich, LOX-cooled first stage earth-to-orbit main engine; (d) non-toxic, day-of-launch-loaded propellants for upper stages and in-space propulsion; (e) electric propulsion and aero stage control.

McCleskey, C. M.↗

Flight Simulation Model Exchange

The NASA Engineering and Safety Center Review Board sponsored an assessment of the draft Standard, Flight Dynamics Model Exchange Standard, BSR/ANSI-S-119-201x (S-119) that was conducted by simulation and guidance, navigation, and control engineers from several NASA Centers. The assessment team reviewed the conventions and formats spelled out in the draft Standard and the actual implementation of two example aerodynamic models (a subsonic F-16 and the HL-20 lifting body) encoded in the Extensible Markup Language grammar. During the implementation, the team kept records of lessons learned and provided feedback to the American Institute of Aeronautics and Astronautics Modeling and Simulation Technical Committee representative. This document contains the results of the assessment.

Murri, Daniel G.↗