SEARCH · Search NASA

Results for “GNC 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.

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 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 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 NTRS1988

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

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

Trahan, W. H.↗

NASA NTRS2007

The Autonomous Precision Landing and Hazard Detection and Avoidance Technology (ALHAT)

As NASA plans to send humans back to the Moon and develop a lunar outpost, technologies must be developed to place humans and cargo safely, precisely, repeatedly, on the lunar surface with the capability to avoid surface hazards. Exploration Space Architecture Study requirements include the need for global lunar surface access with safe, precise landing without lighting constraints on terrain that may have landing hazards for human scale landing vehicles. Landing accuracies of perhaps 1,000 meters for sortie crew missions to 10 s of meters for Outpost class missions are required. The Autonomous precision Landing Hazard Avoidance Technology (ALHAT) project will develop the new and unique descent and landing Guidance, Navigation and Control (GNC) hardware and software technologies necessary for these capabilities. The ALHAT project will qualify a lunar descent and landing GNC system to a Technology Readiness Level (TRL) of 6 capable of supporting lunar crewed, cargo, and robotic missions. The (ALHAT) development project was chartered by NASA Headquarters in October 2006. The initial effort to write a project plan and define an ALHAT Team was followed by a fairly aggressive research and analysis effort to determine what technologies existed that could be developed and applied to the lunar landing problems indicated above. This paper describes the project development, research, analysis and concept evolution that has occurred since the assignment of the project. This includes the areas of systems engineering, GNC, sensors, sensor algorithms, simulations, fielding testing, laboratory testing, Hardware-In-The-Loop testing, system avionics and system certification concepts.

Epp, Chirold D.↗

NASA NTRS2013

In-Flight Performance of the Cassini Hemispherical Quartz Resonator Gyro Inertial Reference Units

The Cassini-Huygens mission is a flagship class NASA/ESA mission to the planet Saturn. Launched in 1997, Cassini is still successfully operating after 16 years of flight and the telemetry from the attitude control hardware on Cassini has produced an immense dataset that allows the Cassini operations team to report on the long-term performance of several commercially available GNC hardware components in the space environment. This investigation summarizes the in-flight performance of the two inertial reference units aboard Cassini. Each of the two Cassini inertial reference units contains four hemispherical quartz resonator gyros. The Cassini operations team previously reported on the performance of the inertial reference units in 2007, and this paper provides an update with an additional 6 years of flight experience at Saturn.

guidance, navigation, and control (GNC)↗

NASA NTRS2017

Precision Pointing for the Wide-Field Infrared Survey Telescope (WFIRST)

The Wide-Field Infrared Survey Telescope (WFIRST) mission, scheduled for a mid-2020's launch, is currently in its definition phase. The mission is designed to investigate essential questions in the areas of dark energy, exoplanets, and infrared astrophysics. WFIRST will use a 2.4-meter primary telescope (same size as the Hubble Space Telescope's primary mirror) and two instruments: the Wide Field Instrument (WFI) and the Coronagraph Instrument (CGI). In order to ad-dress the critical science requirements, the WFIRST mission will conduct large-scale surveys of the infrared sky, requiring both agility and precision pointing (11.6 milli-arcsec stability, 14 milli-arcsec jitter). This paper describes some of the challenges this mission profile presents to the GNC subsystem, and some of the design elements chosen to accommodate those challenges. The high-galactic-latitude survey is characterized by 3-minute observations separated by slews ranging from 0.025 deg to 0.8 deg. The need for observation efficiency drives the slew and settle process to be as rapid as possible. A description of the shaped slew profile chosen to minimize excitation of structural oscillation, and the handoff from star tracker-gyro control to fine guidance sensor control is detailed. Also presented is the fine guidance sensor (FGS), which is integral with the primary instrument (WFI). The FGS is capable of tracking up to 18 guide stars, enabling robust FGS acquisition and precision pointing. To avoid excitation of observatory structural jitter, reaction wheel speeds are operationally maintained within set limits. In addition, the wheel balance law is designed to maintain 1-Hz separation between the wheel speeds to avoid reinforcing jitter excitation at any particular frequency. The wheel balance law and operational implications are described. Finally, the candidate GNC hardware suite needed to meet the requirements of the mission is presented.

Stoneking, Eric↗

NASA NTRS2017

Precision Pointing for the Wide-Field Infrared Survey Telescope(WFIRST)

The Wide-Field Infrared Survey Telescope (WFIRST) mission, scheduled for a mid-2020's launch, is currently in its definition phase. The mission is designed to investigate essential questions in the areas of dark energy, exoplanets, and infrared astrophysics. WFIRST will use a 2.4-meter primary telescope (same size as the Hubble Space Telescope's primary mirror) and two instruments: the Wide Field Instrument (WFI) and the Coronagraph Instrument (CGI). In order to address the critical science requirements, the WFIRST mission will conduct large-scale surveys of the infrared sky, requiring both agility and precision pointing (11.6 milli-arcsec stability, 14 milli-arcsec jitter). This paper describes some of the challenges this mission profile presents to the Guidance, Navigation, and Control (GNC) subsystem, and some of the design elements chosen to accommodate those challenges. The high-galactic-latitude survey is characterized by 3-minute observations separated by slews ranging from 0.025 deg to 0.8 deg. The need for observation efficiency drives the slew and settle process to be as rapid as possible. A description of the shaped slew profile chosen to minimize excitation of structural oscillation, and the handoff from star tracker-gyro control to fine guidance sensor control is detailed. Also presented is the fine guidance sensor (FGS), which is integral with the primary instrument (WFI). The FGS is capable of tracking up to 18 guide stars, enabling robust FGS acquisition and precision pointing. To avoid excitation of observatory structural jitter, reaction wheel speeds are operationally maintained within set limits. In addition, the wheel balance law is designed to maintain 1-Hz separation between the wheel speeds to avoid reinforcing jitter excitation at any particular frequency. The wheel balance law and operational implications are described. Finally, the candidate GNC hardware suite needed to meet the requirements of the mission is presented.

Stoneking, Eric T.↗

NASA NTRSDate not supplied

Maneuverable Automated Tethered Space Tug Simulator

This TIP will develop autonomous capabilities for the space tugs in the Flat Floor Robotics Laboratory (FFRL) for use in support of In-Space Servicing, Assembly, and Manufacturing (ISAM) and future vehicles in the FFRL. The space tugs would be housed on larger spacecraft, such as ISS or Gateway, and deployed for various ISAM activities. When these activities are complete, the space tug can be reeled back to its host spacecraft.

Flat Floor Robotics Lab↗

NASA NTRS1986

Independent Orbiter Assessment (IOA): Analysis of the guidance, navigation, and control subsystem

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) is presented. The IOA approach features a top-down analysis of the hardware to determine failure modes, criticality, and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. The independent analysis results corresponding to the Orbiter Guidance, Navigation, and Control (GNC) Subsystem hardware are documented. The function of the GNC hardware is to respond to guidance, navigation, and control software commands to effect vehicle control and to provide sensor and controller data to GNC software. Some of the GNC hardware for which failure modes analysis was performed includes: hand controllers; Rudder Pedal Transducer Assembly (RPTA); Speed Brake Thrust Controller (SBTC); Inertial Measurement Unit (IMU); Star Tracker (ST); Crew Optical Alignment Site (COAS); Air Data Transducer Assembly (ADTA); Rate Gyro Assemblies; Accelerometer Assembly (AA); Aerosurface Servo Amplifier (ASA); and Ascent Thrust Vector Control (ATVC). The IOA analysis process utilized available GNC hardware drawings, workbooks, specifications, schematics, and systems briefs for defining hardware assemblies, components, and circuits. Each hardware item was evaluated and analyzed for possible failure modes and effects. Criticality was assigned based upon the severity of the effect for each failure mode.

Trahan, W. H.↗

NASA NTRS2019

Rapid Development of the Seeker Free-Flying Inspector Guidance, Navigation, and Control System

Seeker is an automated extravehicular free-flying inspector CubeSat designed and built in-house at the Johnson Space Center (JSC). As a Class 1E project funded by the International Space Station (ISS) Program, Seeker had a streamlined process to flight certification, but the vehicle had to be designed, developed, tested, and delivered within approximately one year after authority to pro-ceed (ATP) and within a $1.8 million budget. These constraints necessitated an expedited Guidance, Navigation, and Control (GNC) development schedule, development began with a navigation sensor trade study using Linear Covariance (LinCov) analysis and a rapid sensor downselection process, resulting in the use of commercial off-the-shelf (COTS) sensors which could be procured quickly and subjected to in-house environmental testing to qualify them for flight. A neural network was used to enable a COTS camera to provide bearing measurements for visual navigation. The GNC flight software (FSW) algorithms utilized lean development practices and leveraged the Core Flight Software (CFS) architecture to rapidly develop the GNC system, tune the system parameters, and verify performance in simulation. This pace was anchored by several Hardware-Software Integration (HSI) milestones, which forced the Seeker GNC team to develop the interfaces both between hardware and software and between the GNC domains early in the project and to enable a timely delivery.

Sullivan, Jacob↗

NASA NTRS2019

Rapid Development of the Seeker Free-Flying Inspector Guidance, Navigation, and Control System

Seeker is an automated extravehicular free-flying inspector CubeSat designed and built in-house at the Johnson Space Center (JSC). As a Class 1E project funded by the International Space Station (ISS) Program, Seeker had a stream-lined process to flight certification, but the vehicle had to be designed, developed, tested, and delivered within approximately one year after authority to proceed (ATP) and within a $1.8 million budget. These constraints necessitated an expedited Guidance, Navigation, and Control (GNC) development schedule. Development began with a navigation sensor trade study using Linear Covariance (LinCov) analysis and a rapid sensor down-selection process, resulting in the use of commercial off-the-shelf (COTS) sensors which could be procured quickly and subjected to in-house environmental testing to qualify them for flight. A neural network was used to enable a COTS camera to provide bearing measure-ments for visual navigation. The GNC flight software (FSW) algorithms utilized lean development practices and leveraged the Core Flight Software (CFS) architecture to rapidly develop the GNC system, tune the system parameters, and verify performance in simulation. This pace was anchored by several Hardware-Software Integration (HSI) milestones, which forced the Seeker GNC team to develop the interfaces both between hardware and software and between the GNC domains early in the project and to enable a timely delivery.

Sullivan, Jake↗

NASA NTRS2002

Simulation of Guidance, Navigation, and Control Systems for Formation Flying Missions

Concepts for missions of distributed spacecraft flying in formation abound. From high resolution interferometry to spatially distributed in-situ measurements, these mission concepts levy a myriad of guidance, navigation, and control (GNC) requirements on the spacecraft/formation as a single system. A critical step toward assessing and meeting these challenges lies in realistically simulating distributed spacecraft systems. The Formation Flying TestBed (FFTB) at NASA Goddard Space Flight Center's (GSFC) Guidance, Navigation, and Control Center is a hardware-in-the-loop simulation and development facility focused on GNC issues relevant to formation flying systems. The FFTB provides a realistic simulation of the vehicle dynamics and control for formation flying missions in order to: (1) conduct feasibility analyses of mission requirements, (2) conduct and answer mission and spacecraft design trades, and (3) serve as a host for GNC software and hardware development and testing. The initial capabilities of the FFTB are based upon an integration of high fidelity hardware and software simulation, emulation, and test platforms developed or employed at GSFC in recent years, including a high-fidelity Global Positioning System (GPS) simulator which has been a fundamental component of the GNC Center's GPS Test Facility. The FFTB will be continuously evolving over the next several years from a tool with capabilities in GPS navigation hardware/software-in-the-loop analysis and closed loop GPS-based orbit control algorithm assessment. Eventually, it will include full capability to support all aspects of multi-sensor, absolute and relative state determination and control, in all (attitude and orbit) degrees of freedom, as well as information management for satellite clusters and constellations. A detailed description of the FFTB architecture is presented in the paper.

Burns, Rich↗

NASA NTRS2014

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↗

NASA NTRS2014

A Ground Testbed to Advance US Capability in Autonomous Rendezvous and Docking Project

This project will advance the Autonomous Rendezvous and Docking (AR&D) GNC system by testing it on hardware, particularly in a flight processor, with a goal of testing it in IPAS with the Waypoint L2 AR&D scenario. The entire Agency supports development of a Commodity for Autonomous Rendezvous and Docking (CARD) as outlined in the Agency-wide Community of Practice whitepaper entitled: "A Strategy for the U.S. to Develop and Maintain a Mainstream Capability for Automated/Autonomous Rendezvous and Docking in Low Earth Orbit and Beyond". The whitepaper establishes that 1) the US is in a continual state of AR&D point-designs and therefore there is no US "off-the-shelf" AR&D capability in existence today, 2) the US has fallen behind our foreign counterparts particularly in the autonomy of AR&D systems, 3) development of an AR&D commodity is a national need that would benefit NASA, our commercial partners, and DoD, and 4) an initial estimate indicates that the development of a standardized AR&D capability could save the US approximately $60M for each AR&D project and cut each project's AR&D flight system implementation time in half.

D'Souza, Chris↗

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 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

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