Search NASA⌕ Search

SEARCH · Search NASA

Results for “Guidance Navigation and Controls Hardware”

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

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

At least 37 records · Page 2

The Space Operations Simulation Center (SOSC) and Closed-loop Hardware Testing for Orion Rendezvous System Design

The Space Operations Simulation Center (SOSC) at the Lockheed Martin (LM) Waterton Campus in Littleton, Colorado is a dynamic test environment focused on Autonomous Rendezvous and Docking (AR&D) development testing and risk reduction activities. The SOSC supports multiple program pursuits and accommodates testing Guidance, Navigation, and Control (GN&C) algorithms for relative navigation, hardware testing and characterization, as well as software and test process development. The SOSC consists of a high bay (60 meters long by 15.2 meters wide by 15.2 meters tall) with dual six degree-of-freedom (6DOF) motion simulators and a single fixed base 6DOF robot. The large testing area (maximum sensor-to-target effective range of 60 meters) allows for large-scale, flight-like simulations of proximity maneuvers and docking events. The facility also has two apertures for access to external extended-range outdoor target test operations. In addition, the facility contains four Mission Operations Centers (MOCs) with connectivity to dual high bay control rooms and a data/video interface room. The high bay is rated at Class 300,000 (. 0.5 m maximum particles/m3) cleanliness and includes orbital lighting simulation capabilities.

D'Souza, Christopher↗

Streamlining GNC Architecture Development and FSW Integration forthe Mars Ascent Vehicle

The Mars Ascent Vehicle (MAV) will be the first vehicle to perform an ascent from the surface ofanother atmospheric planetary body outside of the Earth-Moon system. Significant light-time delayrequires complete autonomy of flight throughout ascent, and naturally a high level of reliability isdesired in both MAV’s hardware and software subsystems. The MAV Guidance, Navigation and Controls(GNC) team and the MAV Flight Software (FSW) team have partnered together to improve the efficiencyof algorithm integration onto the MAV flight processor, and to increase confidence that said integrationis successful and without human error. An interface architecture is proposed for the GNC suite thatallows both the guidance and navigation subsystems to provide code algorithms directly in C++, and thecontrols subsystem to provide MATLAB Simulink auto-coded algorithms. Several continuous integration/deployment (CI/CD) methodologies have been considered for ease of transition of algorithm code fromthe GNC team to the FSW team. The GNC/FSW teams also worked together to develop a cFS-friendlywrapper which abstracts the integration of the GNC algorithm code into an interface-level API that iscompatible with cFS. Several iterations of vehicle GNC code have been produced between the GNC/FSWteam’s partnership, and this strong interface between these two teams have allowed the GNC/FSWteams to greatly increase confidence of efficient and error-free implementation of the GNC code ontoMAV for a successful flight.

GNC↗

Streamlining GNC Architecture Development and FSW Integration for the Mars Ascent Vehicle

The Mars Ascent Vehicle (MAV) will be the first vehicle to perform an ascent from the surface of another atmospheric planetary body outside of the Earth-Moon system. Significant light-time delay requires complete autonomy of flight throughout ascent, and naturally a high level of reliability is desired in both MAV’s hardware and software subsystems. The MAV Guidance, Navigation and Controls (GNC) team and the MAV Flight Software (FSW) team have partnered together to improve the efficiency of algorithm integration onto the MAV flight processor, and to increase confidence that said integration is successful and without human error. An interface architecture is proposed for the GNC suite that allows both the guidance and navigation subsystems to provide code algorithms directly in C++, and the controls subsystem to provide MATLAB Simulink auto-coded algorithms. Several continuous integration/deployment (CI/CD) methodologies have been considered for ease of transition of algorithm code from the GNC team to the FSW team. The GNC/FSW teams also worked together to develop a cFS-friendly wrapper which abstracts the integration of the GNC algorithm code into an interface-level API that is compatible with cFS. Several iterations of vehicle GNC code have been produced between the GNC/FSW team’s partnership, and this strong interface between these two teams have allowed the GNC/FSW teams to greatly increase confidence of efficient and error-free implementation of the GNC code onto MAV for a successful flight.

Engineering↗

Mars Ascent Vehicle GNC Targeting Routines with Considerations for Flight Software Development

The Mars Ascent Vehicle (MAV) will be the first vehicle to perform an ascent from the surface of another atmospheric planetary body outside of the Earth-Moon system. Significant light-time delay requires complete autonomy of flight throughout ascent, and naturally a high level of reliability is desired in both MAV’s hardware and software subsystems. The MAV Guidance, Navigation and Controls (GNC) team and the MAV Flight Software (FSW) team have partnered together to improve the efficiency of algorithm integration onto the MAV flight processor, and to increase confidence that said integration is successful and without human error. An interface architecture is proposed for the GNC suite that allows both the guidance and navigation subsystems to provide code algorithms directly in C++, and the controls subsystem to provide MATLAB Simulink auto-coded algorithms. Several continuous integration/deployment (CI/CD) methodologies have been considered for ease of transition of algorithm code from the GNC team to the FSW team. The GNC/FSW teams also worked together to develop a cFS-friendly wrapper which abstracts the integration of the GNC algorithm code into an interface-level API that is compatible with cFS. Several iterations of vehicle GNC code have been produced between the GNC/FSW team’s partnership, and this strong interface between these two teams have allowed the GNC/FSW teams to greatly increase confidence of efficient and error-free implementation of the GNC code onto MAV for a successful flight.

Jason Everett↗

Understanding International GNC Hardware Trends

An industry-wide survey of guidance, navigation and control (GNC) sensors, namely star trackers, gyros, and sun sensors was undertaken in 2014, in which size, mass, power, and various performance metrics were recorded for each category. A multidimensional analysis was performed, looking at the spectrum of available sensors, with the intent of identifying gaps in the available capability range. Mission types that are not currently well served by the available components were discussed, as well as some missions that would be enabled by filling gaps in the component space. This paper continues that study, with a focus on reaction wheels and magnetometers, as well as with updates to the listings of star trackers, gyros, and sun sensors. Also discussed are a framework for making the database available to the community at large, and the continued maintenance of this database and the analysis of its contents.

Greenbaum, Adam↗

Testing the Preliminary X-33 Navigation System

The X-33 Reusable Launch Vehicle (RLV) must meet the demanding requirements of landing autonomously on a narrow landing strip following a flight that reaches an altitude of up to 200,000 feet and a speed in excess of Mach 9 with significant in-flight energy bleed-off maneuvers. To execute this flight regimen a highly reliable avionics system has been designed that includes three LN-100G Inertial Navigation System/Global Positioning System (INS/GPS) units as the primary navigation system for the X-33. NASA's Marshall Space Flight Center (MSFC) tested an INS/GPS system in real-time simulations to determine the ability of this navigation suite to meet the in flight and autonomous landing requirements of the X-33 RLV. A total of sixty-one open loop tests were performed to characterize the navigation accuracy of the LN-100G. Twenty-seven closed-loop tests were also performed to evaluate the performance of the X-33 Guidance, Navigation and Control (GN&C) algorithms with the real navigation hardware. These closed-loop tests were also designed to expose any integration or operational issues with the real-time X-33 vehicle simulation. Dynamic road tests of the INS/GPS were conducted by Litton to assess the performance of differential and nondifferential INS/GPS hybrid navigation solutions. The results of the simulations and road testing demonstrate that this novel solution is capable of meeting the demanding requirements of take-off, in-flight navigation, and autonomous landing of the X-33 RLV. This paper describes the test environment developed to stimulate the LN-100G and discusses the results of this test effort. This paper also presents recommendations for a navigation system suitable to an operational RLV system.

Lomas, James J.↗

Autonomous Deep-Space Optical Navigation Project

This project will advance the Autonomous Deep-space navigation capability applied to Autonomous Rendezvous and Docking (AR&D) Guidance, Navigation and Control (GNC) system by testing it on hardware, particularly in a flight processor, with a goal of limited testing in the Integrated Power, Avionics and Software (IPAS) with the ARCM (Asteroid Retrieval Crewed Mission) DRO (Distant Retrograde Orbit) Autonomous Rendezvous and Docking (AR&D) scenario. The technology, which will be harnessed, is called 'optical flow', also known as 'visual odometry'. It is being matured in the automotive and SLAM (Simultaneous Localization and Mapping) applications but has yet to be applied to spacecraft navigation. In light of the tremendous potential of this technique, we believe that NASA needs to design a optical navigation architecture that will use this technique. It is flexible enough to be applicable to navigating around planetary bodies, such as asteroids.

D'Souza, Christopher↗

Aerocapture: An Enabling Technology for Flagship-Class Uranus Orbiter and Probe Mission

Introduction: The current decadal survey published by the National Academies of Sciences has informed National Aeronautics and Space Administration (NASA) to prioritize the study of the Ice Giants, especially Uranus. To gather the required data that addresses the science questions raised in this survey, a mission to Uranus with an orbiter and atmospheric probe must be designed. The Uranus Orbiter and Probe (UOP) study, which the survey identified as the flagship mission of this decade, proposes a 2031 launch to take advantage of a Jupiter fly-by and utilizes a fully propulsive orbit insertion design with an Earth-to-Uranus transit times ranging from 13 to 15 years. This fully propulsive orbit insertion at Uranus will be very fuel expensive (wet mass percentages of around 60-70\%) thereby leaving less mass for the scientific payload and additional planetary probes. In addition, scientists are more interested in visiting Uranus before 2049, when the Spring Equinox will occur, as it allows studying Uranus seasons not seen during Voyager 2's flyby in 1987. A NASA Flagship-Class mission would require at least 10 years of lead time prior to launch thereby making the 2031 launch to take advantage of the Jupiter fly-by extremely challenging. The consequence of missing the Jupiter fly-by and launching in the late 2030s is the challenge of a fully-propulsive mission like UOP to have a feasible alternative interplanetary trajectory that reaches Uranus before 2050. As an alternative, to address the shortcomings of the fully propulsive mission, one can design a mission to Uranus using aerocapture. What is aerocapture: Aerocapture is an atmospheric maneuver that uses aerodynamic forces generated by flight within a planetary atmosphere to decelerate and achieve orbit insertion. Using aerocapture allows one to provide the change in velocity (Delta V) needed to slow down from the approach hyperbolic trajectory to achieve the desired captured orbit around the target planet using aerodynamic forces of the vehicle (lift and drag). Using aerodynamic forces instead of fully-propulsive maneuvers results in significant savings in the fuel. Furthermore, aerocapture can also allow one to consider interplanetary trajectories with higher approach hyperbolic velocities, thus reducing the mission transit times. Aerocapture as an enabling technology: To use aerocapture as an enabling technology for the Uranus exploration mission, one would require an integrated system-level design, including a Thermal Protection System (TPS), hardware needed for aerodynamic modulation, and autonomous Guidance, Navigation, and Control (GNC) systems. Aerocapture has yet to be demonstrated, despite considering it for several past missions. Recent advancements in TPS and GNC capabilities show the potential for using rigid, heritage entry vehicle configurations already flown at other planetary bodies for Uranus aerocapture. Aerocapture can be a robust technology that can deliver spacecraft to Uranus science orbits while substantially increasing on-orbit payload mass (more than 40\%) that can enable robust atmospheric entry probes. Additionally, the aerocapture maneuver would reduce the interplanetary transit time by 2–5 years (15-30\%) relative to fully-propulsive orbit insertion. Recent work has shown that one can conduct a flagship-class mission in a shorter period than fully-propulsive missions if using aerocapture. What does aerocapture bring in for a Uranus Mission: Using aerocapture for a Uranus orbiter and atmospheric probe mission can provide one with considerable propellant savings. Spacecraft in interplanetary trajectories to Uranus typically need an Delta V in orders of kilometers per second to insert into science orbit. One would require thousands of kilograms of fuel to achieve such a Delta V using a traditional fully propulsive maneuver, leaving less mass for payload during the mission launch. Aerocapture can reduce the propulsion needs by dissipating energy in the sizable atmosphere of Uranus without a significant mass increase due to the need for an aeroshell. One can use the mass savings achieved using the aerocapture to reduce the launch vehicle requirements. In addition, one can also have additional science instruments on the orbiter or create a robust instrumentation suite on an atmospheric probe that can significantly increase the science outcome of the Uranus exploration mission. Furthermore, since aerocapture performance is relatively insensitive to increases in hyperbolic excess velocity, one can design the interplanetary trajectory to arrive at Uranus faster, reducing the interplanetary transit time and operations cost. All these savings, achieved using aerocapture, could help fit a larger class mission, such as the Uranus mission within a smaller capital, e.g., a Flagship-class orbiter mission in a New Frontiers class capital. Summary: This talk will provide an overview of how aerocapture can enable the Uranus exploration mission. Specifically, this talk will discuss the latest advancements made in the Uranus aerocapture study, such as investigating interplanetary trajectories with higher hyperbolic approach velocities and their implications on the aero heating and the TPS design, incorporating FNPAG (an advanced numerical-predictor guidance) and comparison of multiple navigation approaches. In addition, this talk will focus on mechanical design that can house more than one atmospheric probe and the six degrees of freedom simulation of aerocapture at Uranus. Findings from a recent NASA Space Technology Mission Directorate (STMD)-funded activity studying the aerocapture as an enabling technology for a Uranus orbiter will be presented. Using the science payload recommended by the Decadal Survey for Uranus exploration, this work shows many improvements over the baseline fully-propulsive mission. These improvements include a shorter cruise phase, flexibility in launch opportunities late into the 2030s while reaching Uranus before the 2050 equinox for the desired science opportunities, and lower propellant mass needs. This talk will highlight how aerocapture can be utilized for Uranus science orbit insertion using a lower-risk, heritage entry vehicle configuration used extensively as a Mars entry, descent, and landing vehicle. Furthermore, this talk will explore how the demonstration of aerocapture at Earth can benefit the aerocapture-enabled Uranus mission.

Aerocapture↗

A Plug and Play GNC Architecture Using FPGA Components

The goal of Plug and Play, or PnP, is to allow hardware and software components to work together automatically, without requiring manual setup procedures. As a result, new or replacement hardware can be plugged into a system and automatically configured with the appropriate resource assignments. However, in many cases it may not be practical or even feasible to physically replace hardware components. One method for handling these types of situations is through the incorporation of reconfigurable hardware such as Field Programmable Gate Arrays, or FPGAs. This paper describes a phased approach to developing a Guidance, Navigation, and Control (GNC) architecture that expands on the traditional concepts of PnP, in order to accommodate hardware reconfiguration without requiring detailed knowledge of the hardware. This is achieved by establishing a functional based interface that defines how the hardware will operate, and allow the hardware to reconfigure itself. The resulting system combines the flexibility of manipulating software components with the speed and efficiency of hardware.

KrishnaKumar, K.↗

An Integrated Vision-Based System for Spacecraft Attitude and Topology Determination for Formation Flight Missions

With the space industry's increasing focus upon multi-spacecraft formation flight missions, the ability to precisely determine system topology and the orientation of member spacecraft relative to both inertial space and each other is becoming a critical design requirement. Topology determination in satellite systems has traditionally made use of GPS or ground uplink position data for low Earth orbits, or, alternatively, inter-satellite ranging between all formation pairs. While these techniques work, they are not ideal for extension to interplanetary missions or to large fleets of decentralized, mixed-function spacecraft. The Vision-Based Attitude and Formation Determination System (VBAFDS) represents a novel solution to both the navigation and topology determination problems with an integrated approach that combines a miniature star tracker with a suite of robust processing algorithms. By combining a single range measurement with vision data to resolve complete system topology, the VBAFDS design represents a simple, resource-efficient solution that is not constrained to certain Earth orbits or formation geometries. In this paper, analysis and design of the VBAFDS integrated guidance, navigation and control (GN&C) technology will be discussed, including hardware requirements, algorithm development, and simulation results in the context of potential mission applications.

Rogers, Aaron↗

A Hardware-in-the-Loop Testbed for Spacecraft Formation Flying Applications

The Formation Flying Test Bed (FFTB) at NASA Goddard Space Flight Center (GSFC) is being developed as a modular, hybrid dynamic simulation facility employed for end-to-end guidance, navigation, and control (GN&C) analysis and design for formation flying clusters and constellations of satellites. The FFTB will support critical hardware and software technology development to enable current and future missions for NASA, other government agencies, and external customers for a wide range of missions, particularly those involving distributed spacecraft operations. The initial capabilities of the FFTB are based upon an integration of high fidelity hardware and software simulation, emulation, and test platforms developed at GSFC in recent years; including a high-fidelity GPS simulator which has been a fundamental component of the Guidance, Navigation, and Control Center's GPS Test Facility. The FFTB will be continuously evolving over the next several years from a too[ with initial capabilities in GPS navigation hardware/software- in-the- loop analysis and closed loop GPS-based orbit control algorithm assessment to one with cross-link communications and relative navigation analysis and simulation capability. Eventually the FFT13 will provide full capability to support all aspects of multi-sensor, absolute and relative position determination and control, in all (attitude and orbit) degrees of freedom, as well as information management for satellite clusters and constellations. In this paper we focus on the architecture for the FFT13 as a general GN&C analysis environment for the spacecraft formation flying community inside and outside of NASA GSFC and we briefly reference some current and future activities which will drive the requirements and development.

Leitner, Jesse↗

Demonstration of automated proximity and docking technologies

An autodock was demonstrated using straightforward techniques and real sensor hardware. A simulation testbed was established and validated. The sensor design was refined with improved optical performance and image processing noise mitigation techniques, and the sensor is ready for production from off-the-shelf components. The autonomous spacecraft architecture is defined. The areas of sensors, docking hardware, propulsion, and avionics are included in the design. The Guidance Navigation and Control architecture and requirements are developed. Modular structures suitable for automated control are used. The spacecraft system manager functions including configuration, resource, and redundancy management are defined. The requirements for autonomous spacecraft executive are defined. High level decisionmaking, mission planning, and mission contingency recovery are a part of this. The next step is to do flight demonstrations. After the presentation the following question was asked. How do you define validation? There are two components to validation definition: software simulation with formal and vigorous validation, and hardware and facility performance validated with respect to software already validated against analytical profile.

Anderson, Robert L.↗

A Flight Dynamics Perspective of the Orion Pad Abort One Flight Test

The Orion Crew Exploration Vehicle is America s next generation of human rated spacecraft. The Orion Launch Abort System will take the astronauts away from the exploration vehicle in the event of an aborted launch. The pad abort mode of the Launch Abort System will be flight-tested in 2009 from the White Sands Missile Range in New Mexico. This paper examines some of the efforts currently underway at the NASA Dryden Flight Research Center by the Controls & Dynamics group in preparation for the flight test. The concept of operation for the pad abort flight is presented along with an overview of the guidance, control and navigation systems. Preparations for the flight test, such as hardware testing and development of the real-time displays, are examined. The results from the validation and verification efforts for the aerodynamic and atmospheric models are shown along with Monte Carlo analysis results.

Idicula, Jinu↗

NASA SPLICE Project: Development and Testing of Precision Landing GN&C Technologies

NASA's technology advancement needs for entry, descent and landing call for high-precision, high-rate sensors that can improve navigation accuracy and vehicle control performance. Higher landing accuracy is required for any future human lander missions, and likely, for most robotic missions 1,2. Sensors and algorithms that significantly reduce navigation errors and can image the local terrain will enable landing at locations of high scientific interest that would otherwise pose significant risk to the vehicle. The Safe and Precise Landing-Integrated Capabilities Evolution project, or SPLICE, is developing precision landing and hazard avoidance (PL&HA) technologies for NASA and for potential commercial space flight missions. SPLICE technologies include sensors, algorithms, advanced space flight computing capabilities, and simulation tools used to integrate and study guidance, navigation, and control (GN&C) system performance. SPLICE efforts include hardware-in-the-loop (HWIL) simulation testing, ground testing, and flight testing, including reuse of hardware from the CoOperative Blending of Autonomous Landing Technologies (COBALT) suborbital flight-test payload3,4. Two of the precise navigation sensors that are being developed and matured within SPLICE are LiDARs. Since 2006, NASA Langley has been developing a Navigation Doppler LiDAR (NDL) for precise velocity measurements, and SPLICE is building an NDL engineering test unit (ETU) that will be brought up to TRL 6 following environmental and high-speed1,2 testing. NASA Goddard is developing a Hazard Detection LiDAR (HD LiDAR) engineering development unit (EDU) for SPLICE that has relevance to future human and robotic lander missions. The HD LiDAR will be flight test and matured to TRL 5.

Restrepo, Carolina I.↗

Evaluation of Precision Landing Performance Using A Generalized Aerospace Simulation in Simulink Framework

NASA’s science and exploration goals to return to the Moon and beyond will need to perform precision landings to place humans and cargo supplies near places of scientific interest, surface resources, or pre-established basecamps. With the maturation of new navigation technology, such as terrain relative navigation, precision landing is now feasible, enabling new exploration sites, such as the lunar poles. However, verification of precision landing performance becomes crucial since not reaching the designated landing site would have a high risk of loss of mission. Therefore, having a high-fidelity simulation platform to evaluate six degrees of freedom vehicle performance during high-risk phases of flight such landing is a fundamental part of the system verification and risk reduction. The NASA Marshall Space Flight Center has developed the GeneraLized Aerospace Simulation in Simulink® (GLASS) tool which incorporates guidance, navigation, and control algorithms, as well as vehicle and environmental models, such as gravity, vehicle mass properties, navigation sensors, propulsion, and terrain models. GLASS uses the MathWorks® Simulink® environment which provides a model-based design framework that allows the incorporation of vehicle models in a modular architecture. The Simulink® environment provides seamless integration with all the MathWorks® capabilities and toolboxes, such as control design toolboxes and Simscape™ Multibody™ dynamics toolbox. The MathWorks® environment also allows for guidance, navigation, and control algorithms to be auto coded in C language, enabling quick software and hardware in the loop testing. This paper provides an overview of GLASS capabilities for analyzing precision landing performance, including navigation trades applied to a NASA human lander reference design architecture.

Guidance↗

Hardware-In-The-Loop Testing of Continuous Control Algorithms for a Precision Formation Flying Demonstration Mission

A sample mission sequence is defined for a low earth orbit demonstration of Precision Formation Flying (PFF). Various guidance navigation and control strategies are discussed for use in the PFF experiment phases. A sample PFF experiment is implemented and tested in a realistic Hardware-in-the-Loop (HWIL) simulation using the Formation Flying Test Bed (FFTB) at NASA's Goddard Space Flight Center.

Naasz, Bo J.↗

Recent Developments in Hardware-in-the-Loop Formation Navigation and Control

The Formation Flying Test-Bed (FFTB) at NASA Goddard Space Flight Center (GSFC) provides a hardware-in-the-loop test environment for formation navigation and control. The facility is evolving as a modular, hybrid, dynamic simulation facility for end-tc-end guidance, navigation, and control (GN&C) design and analysis of formation flying spacecraft. The core capabilities of the FFTB, as a platform for testing critical hardware and software algorithms in-the-loop, are reviewed with a focus on many recent improvements. Two significant upgrades to the FFTB are a message-oriented middleware (MOM) architecture, and a software crosslink for inter-spacecraft ranging. The MOM architecture provides a common messaging bus for software agents, easing integration, arid supporting the GSFC Mission Services Evolution Center (GMSEC) architecture via software bridge. Additionally, the FFTB s hardware capabilities are expanding. Recently, two Low-Power Transceivers (LPTs) with ranging capability have been introduced into the FFTB. The LPT crosslinks will be connected to a modified Crosslink Channel Simulator (CCS), which applies realistic space-environment effects to the Radio Frequency (RF) signals produced by the LPTs.

Mitchell, Jason W.↗