Search NASA⌕ Search

SEARCH · Search NASA

Results for “GNC”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2024

Looking to the Future: A Call to Action for Advanced GNC Algorithm Verification and Validation

Future space systems will rely on autonomous Guidance, Navigation, and Control (GNC) functions to efficiently manage safe and precise self-directed operations in uncertain complex environments. Fundamentally, the GNC system plays a key role in mission performance and safety because it computes the ideal trajectory (Guidance), determines the actual trajectory (Navigation), and executes the ideal trajectory (Control) of a vehicle’s position and attitude. Our current GNC systems are highly automated and already have a high degree of complexity. As missions become more ambitious, GNC systems for launch vehicles and space platforms (e.g., spacecraft, probes, and landers) will require higher levels of performance and autonomous operation than previously encountered, for example, this includes GNC for optimizing aerodynamic and/or propulsion performance during planetary entry. This GNC Verification and Validation (V&V) paper highlights concerns with what undoubtedly will be a trend towards increased complexity as fully autonomous GNC systems are developed for future space missions. Clearly, complex GNC systems pose challenges in the prelaunch V&V phase, which is a relatively expensive part of a mission’s life cycle. Essentially the V&V phase is focused on checking that the system effectively meets all the design and operational requirements for the mission. The authors of this paper (i.e., the Inter-Agency Working Group of GNC subject matter experts) focused on this fundamental question over the past few years: Will the GNC engineering community of practice be sufficiently prepared to perform the necessary V&V on evolving GNC architectures that are driven by very demanding requirements for autonomy, resiliency, reconfigurability, adaptability, and mission cost-benefit balance? It is the viewpoint of our Inter-Agency team that the GNC V&V approaches and processes needed to address the next generation of complex GNC systems, which likely will employ various forms of modern GNC technology, are not currently established to the level the community will need in the future. While researchers and practitioners have made some progress in developing new GNC V&V methods for modern GNC systems, a good deal of work remains to be done to codify such methods in a comprehensive and systematic manner. Thus, the Inter-Agency team’s partner organizations [the National Aeronautics and Space Administration (NASA), the European Space Agency (ESA), the National Centre for Space Studies (CNES), the German Aerospace Center (DLR), the French Aerospace Lab (ONERA), and ISAE-SUPAERO] have conducted preliminary investigations into advancing GNC V&V techniques, which resulted in the identification of the need for education, new V&V tools, and benchmark problems for the GNC community. The necessary proactive steps to be taken to meet the challenges and fill the gaps in GNC V&V are summarized in this paper. The first steps include identifying advanced analysis tools, developing a GNC V&V roadmap, and expanding education and training programs for GNC practitioners. This paper is a call to action and proposes a comprehensive set of recommended actions for all our stakeholders: space agencies, researchers, and industry.

Samir Bennani↗
NASA NTRSDate not supplied

Cross-Calibration of GNC and OLA LIDAR Systems Onboard OSIRIS-REx

The Origins, Spectral Interpretation, Resource Identification, and Security–Regolith Explorer (OSIRIS-REx) mission carried two distinct light detection and ranging (LIDAR) systems: A scanning LIDAR called OSIRIS-REx Laser Altimeter (OLA) as part of the science payload, and a flash LIDAR system has part of the Guidance, Navigation, & Control (GNC) subsystem to serve as a navigation sensor during TAG. This presents a unique opportunity to compare the performance of the two LIDAR systems in close proximity to a small asteroid body. During the Orbital B mission phase, between June to August 2019, the OSIRIS-REx spacecraft orbited Bennu in a near-circular terminator orbit during which the altitude above the surface varied between 645 m to 740 m. Over five-week period observations were recorded with the OLA instrument that were subsequently used to construct a global digital terrain map (DTM) with a resolution of 5 cm and accuracy of ±20 cm. This model provides an excellent reference for assessing the performance of the GNC LIDAR system. Two different GNC LIDAR checkout activities were also conducted during the Orbital B phase: A limb-crossing check-out featured a series of slews to collect GNC LIDAR data across varying ranges and phase angles and operate the automatic gain control modes of the device; An OLA-GNC LIDAR cross calibration was designed to collect data from both the OLA and GNC LIDAR devices with overlapping footprints while the spacecraft was pointed nadir. This paper compares the on-orbit performance observed during the cross-calibration activity. The OLA-based global DTM and point clouds are used to evaluate the GNC LIDAR not available during previous analysis. The GNC LIDAR measurements were found to be well within accuracy and precision specified for the instrument, but much noisier than the measurements from OLA within this operating regime.

Jason M Leonard↗
NASA NTRSDate not supplied

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↗
NASA NTRSDate not supplied

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↗
NASA NTRSDate not supplied

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↗
NASA NTRS2006

GNC Architecture Design for ARES Simulation. Revision 3.0

The purpose of this document is to describe the GNC architecture and associated interfaces for all ARES simulations. Establishing a common architecture facilitates development across the ARES simulations and provides an efficient mechanism for creating an end-to-end simulation capability. In general, the GNC architecture is the frame work in which all GNC development takes place, including sensor and effector models. All GNC software applications have a standard location within the architecture making integration easier and, thus more efficient.

Gay, Robert↗
NASA NTRS2009

Apollo Guidance, Navigation, and Control (GNC) Hardware Overview

This viewgraph presentation reviews basic guidance, navigation and control (GNC) concepts, examines the Command and Service Module (CSM) and Lunar Module (LM) GNC organization and discusses the primary GNC and the CSM Stabilization and Control System (SCS), as well as other CSM-specific hardware. The LM Abort Guidance System (AGS), Control Electronics System (CES) and other LM-specific hardware are also addressed. Three subsystems exist on each vehicle: the computer subsystem (CSS), the inertial subsystem (ISS) and the optical subsystem (OSS). The CSS and ISS are almost identical between CSM and LM and each is designed to operate independently. CSM SCS hardware are highlighted, including translation control, rotation controls, gyro assemblies, a gyro display coupler and flight director attitude indicators. The LM AGS hardware are also highlighted and include the abort electronics assembly and the abort sensor assembly; while the LM CES hardware includes the attitude controller assembly, thrust/translation controller assemblies and the ascent engine arming assemble. Other common hardware including the Orbital Rate Display - Earth and Lunar (ORDEAL) and the Crewman Optical Alignment Sight (COAS), a docking aid, are also highlighted.

Interbartolo, Michael↗
NASA NTRS2002

Ground Operations of the ISS GNC Babb-Mueller Atmospheric Density Model

The ISS GNC system was updated recently with a new software release that provides onboard state determination capability. Prior to this release, only the Russian segment maintained and propagated the onboard state, which was periodically updated through Russian ground tracking. The new software gives the US segment the capability for maintaining the onboard state, and includes new GPS and state vector propagation capabilities. Part of this software package is an atmospheric density model based on the Babb-Mueller algorithm. Babb-Mueller efficiently mimics a full analytical density model, such as the Jacchia model. While lacchia is very robust and is used in the Mission Control Center, it is too computationally intensive for use onboard. Thus, Babb-Mueller was chosen as an alternative. The onboard model depends on a set of calibration coefficients that produce a curve fit to the lacchia model. The ISS GNC system only maintains one set of coefficients onboard, so a new set must be uplinked by controllers when the atmospheric conditions change. The onboard density model provides a real-time density value, which is used to calculate the drag experienced by the ISS. This drag value is then incorporated into the onboard propagation of the state vector. The propagation of the state vector, and therefore operation of the BabbMueller algorithm, will be most critical when GPS updates and secondary state vector sources fail. When GPS is active, the onboard state vector will be updated every ten seconds, so the propagation error is irrelevant. When GPS is inactive, the state vector must be updated at least every 24 hours, based on current protocol. Therefore, the Babb-Mueller coefficients must be accurate enough to fulfill the state vector accuracy requirements for at least one day. A ground operations concept was needed in order to manage both the on board Babb-Mueller density model and the onboard state quality. The Babb-Mueller coefficients can be determined operationally in two ways. The first method is to calibrate the coefficients in real-time, where a set of custom coefficients is generated for the real-time atmospheric conditions. The second approach is to generate pre-canned sets of coefficients that encompass the expected atmospheric conditions over the lifetime of the vehicle. These predetermined sets are known as occurrences. Even though a particular occurrence will not match the true atmospheric conditions, the error will be constrained by limiting the breadth of each occurrence. Both methods were investigated and the advantages and disadvantages of each were considered. The choice between these implementations was a trade-off between the additional accuracy of the real-time calibration and the simpler development for the approach using occurrences. The operations concept for the frequency of updates was also explored, and depends on the deviation in solar flux that still achieves the necessary accuracy of the coefficients. This was determined based on historical solar flux trends. This analysis resulted in an accurate and reliable implementation of the Babb-Mueller coefficients and how flight controllers use them during realtime operations.

Brogan, Jonathan↗
NASA NTRSDate not supplied

Vertical Motion Simulator -- A Unique Facility for Piloted GNC Research

This material is for presentation at the annual meeting of the NASA Engineering and Safety Center (NESC) Guidance, Navigation, and Control (GNC) Technical Discipline Team (TDT), on 22 July 2020. The briefing is entitled “Vertical Motion Simulator – A Unique Facility for Piloted GNC Research.” It provides a technical description of key VMS features and a high-level overview of some large bodies of work conducted in the VMS over the past 40 years.

Vertical Motion Simulator↗
NASA NTRSDate not supplied

Integrated GNC Modifications and Performance Assessments for the Mars Ascent Vehicle, Spin-Stabilized Upper Stage Configuration

The objective of the Mars Ascent Vehicle (MAV), an element of the Mars Sample Return (MSR) campaign, is to successfully transport Martian surface samples from the Martian surface to a stable Low-Martian Orbit. Complete autonomy is required throughout ascent, and orbital insertion is constrained by tight dispersion boundaries. Given mass requirements to merely transport the MAV onto the Martian surface, reducing the total mass of the MAV reduces stress on all other campaign elements. An unguided, spin-stabilized second stage MAV allows for lower overall vehicle mass, at the cost of reduced GNC capability. This paper presents GNC modifications developed and employed to improve the performance of an unguided, spin-stabilized second stage MAV configuration. These updates include a predictive calculation scheme to solve the spin-stabilized attitude necessary for successful orbital insertion, and a spin-stabilized control law for a preliminary low-rate first stage spin-up. Trades were conducted focusing on first and second stage low-rate and high-rate spin rates (and other factors) in MSFC's MANTIS toolkit through 6-degree-of-freedom simulation and Monte Carlo analysis, and are presented here.

Dane Erickson↗
NASA NTRS2021

Mars 2020 Perseverance Edl Gnc Safe Target Selection Reconstruction

On February 18th, 2021, NASA landed Perseverance on the Jezero crater (on Mars) using a new Terrain Relative Navigation (TRN) capability. TRN is com-prised of a new sensor, the Lander Vision System (LVS), and a new GNC algo-rithm, the Safe Target Selection (STS). LVS localized the descent vehicle with respect to a map. STS selected the safe landing target within a reachable region from the on-board Safe Targets Map (STM). The landing target was then handed to the Mars Science Laboratory (MSL) heritage powered descent GNC system to execute the landing. This paper describes the design and the as-flown performance of the STS algorithm.

Dutta, Soumyo↗
NASA NTRS2005

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.↗
NASA NTRS2009

Automation Interfaces of the Orion GNC Executive Architecture

This viewgraph presentation describes Orion mission's automation Guidance, Navigation and Control (GNC) architecture and interfaces. The contents include: 1) Orion Background; 2) Shuttle/Orion Automation Comparison; 3) Orion Mission Sequencing; 4) Orion Mission Sequencing Display Concept; and 5) Status and Forward Plans.

Hart, Jeremy↗
NASA NTRS2013

Orion GNC Mitigation Efforts for Van Allen Radiation

The Orion Crew Module (CM) is NASA's next generation manned space vehicle, scheduled to return humans to lunar orbit in the coming decade. The Orion avionics and GN&C architectures have progressed through a number of project phases and are nearing completion of a major milestone. The first unmanned test mission, dubbed "Exploration Flight Test One" (EFT-1) is scheduled to launch from NASA Kennedy Space Center late next year and provides the first integrated test of all the vehicle systems, avionics and software. The EFT-1 mission will be an unmanned test flight that includes a high speed re-entry from an elliptical orbit, which will be launched on an expendable launch vehicle (ELV). The ELV will place CM and the ELV upper stage into a low Earth orbit (LEO) for one revolution. After the first LEO, the ELV upper stage will re-ignite and place the combined upper stage/CM into an elliptical orbit whose perigee results in a high energy entry to test CM response in a relatively high velocity, high heating environment. While not producing entry velocities as high as those experienced in returning from a lunar orbit, the trajectory was chosen to provide higher stresses on the thermal protection and guided entry systems, as compared against a lower energy LEO entry. However the required entry geometry with constraints on inclination and landing site result in a trajectory that lingers for many hours in the Van Allen radiation belts. This exposes the vehicle and avionics to much higher levels of high energy proton radiation than a typical LEO or lunar trajectory would encounter. As a result, Van Allen radiation poses a significant risk to the Orion avionics system, and particularly the Flight Control Module (FCM) computers that house the GN&C flight software. The measures taken by the Orion GN&C, Flight Software and Avionics teams to mitigate the risks associated with the Van Allen radiation on EFT-1 are covered in the paper. Background on the Orion avionics subsystem is provided, as well as an overview of the GN&C software architecture. The measures taken to handle radiation induced failure of the one or both of the FCM's are presented, and finally simulation and actual hardware-in-the-loop (HWIL) results are shown confirming the validity of the implementation. The paper presents an overview of the Orion avionics architecture describing the GNC sensors, onboard data network as well as the flight control computers and their planned restart capabilities. GN&C sensors include two Orion Inertial Measurement Units (OIMU's), a Vision Processing Unit (VPU) to process camera images, three barometric altimeters and a single GPS receiver. All of the sensors communicate to one of two Power and Data Units (PDU's). The PDU's multiplex analog and serial data from the sensors and write the data to the Orion Data Network (ODN). The OIMU s write measurement messages directly as onto the ODN, but they are routed through PDU network switches.

King, Ellis T.↗
NASA NTRS2013

Simple Sensitivity Analysis for Orion GNC

The performance of Orion flight software, especially its GNC software, is being analyzed by running Monte Carlo simulations of Orion spacecraft flights. The simulated performance is analyzed for conformance with flight requirements, expressed as performance constraints. Flight requirements include guidance (e.g. touchdown distance from target) and control (e.g., control saturation) as well as performance (e.g., heat load constraints). The Monte Carlo simulations disperse hundreds of simulation input variables, for everything from mass properties to date of launch.We describe in this paper a sensitivity analysis tool (Critical Factors Tool or CFT) developed to find the input variables or pairs of variables which by themselves significantly influence satisfaction of requirements or significantly affect key performance metrics (e.g., touchdown distance from target). Knowing these factors can inform robustness analysis, can inform where engineering resources are most needed, and could even affect operations. The contributions of this paper include the introduction of novel sensitivity measures, such as estimating success probability, and a technique for determining whether pairs of factors are interacting dependently or independently. The tool found that input variables such as moments, mass, thrust dispersions, and date of launch were found to be significant factors for success of various requirements. Examples are shown in this paper as well as a summary and physics discussion of EFT-1 driving factors that the tool found.

Monte Carlo Simulation↗
NASA NTRS2014

Evolution of MPCV Service Module Propulsion and GNC Interface Requirements

The Orion Multi-Purpose Crew Vehicle Service Module Propulsion Subsystem provides propulsion for the integrated Crew and Service Module. Updates in the exploration architecture between Constellation and MPCV as well as NASA's partnership with the European Space Agency have resulted in design changes to the SM Propulsion Subsystem and updates to the Propulsion interface requirements with Guidance Navigation and Control. This paper focuses on the Propulsion and GNC interface requirement updates between the Constellation Service Module and the European Service Module and how the requirement updates were driven or supported by architecture updates and the desired use of hardware with heritage to United States and European spacecraft for the Exploration Missions, EM-1 and EM-2.

spacecraft propulsion↗
NASA NTRS2015

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↗
NASA NTRS2019

Seeker Free-Flying Inspector GNC System Overview

Seeker is an ultra-low cost approach to highly automated extravehicular inspection of crewed or uncrewed spacecraft that has been designed and built in-house at the NASA Johnson Space Center (JSC). The first version of Seeker is intended to be an incremental development towards an advanced inspection capability. This effort builds on past free-flying inspector development efforts such as the Autonomous Extravehicular Activity Robotic Camera Sprint (AERCam Sprint) and Mini AERCam. Seeker was funded as an International Space Station (ISS) "X-by" Project, which required delivery of the vehicle approximately one year after authority to proceed and within the budget of $1.8 million. Seeker will fly onboard the NG-11 Cygnus mission in 2019 and will deploy after Cygnus' primary mission is completed. Seeker will perform inspection-like maneuvers within 50 meters of the target vehicle (Cygnus) and then dispose itself. The Seeker Guidance, Navigation, and Control (GNC) system is composed entirely of commercial off-the-shelf (COTS) and space-rated COTS items, an inertial-relative Multiplicative Extended Kalman Filter (MEKF), point-to-point guidance (with various additional modes such as stationkeeping), proportional-integral translational control, phase plane rotational control, and a state machine for automated mission moding with minimal ground input.

Navigation↗