Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 37 records · Page 2

Seeker 1.0 GNC Flight Performance (presentation)

Seeker is an automated extravehicular inspection spacecraft that was designed and built in-house at the NASA Johnson Space Center (JSC) over approximate-ly 18 months with a budget of $1.8 million. This first version of Seeker is in-tended to be an incremental development towards an advanced inspection ca-pability. Seeker launched onboard the NG-11 Cygnus mission in 2019 and de-ployed from Cygnus on September 16, 2019. Downlinked telemetry, imagery from the chaser and target spacecraft, and onboard engineering data logs are used to provide an analysis of the system’s performance. This paper reviews the performance of the Seeker vehicle with a focus on the guidance, navigation, and control (GNC) system. The results are presented with a discussion of the re-lated system design to highlight how decisions and applied methods culminated in the observed performance.

Sam Pedrotty↗

In-flight pointing accuracy assessment and GNC commissioning overview for the dual-spinning SMAP (Soil Moisture Active Passive) spacecraft

NASA’s new SMAP (Soil Moisture Active Passive) spacecraft is a radar and radiometer- based climate monitoring mission that, for an earth-orbiting satellite, presented an uncommonly large engineering challenge for the spacecraft designers at NASA’s Jet Propulsion Laboratory. The primary engineering challenge of this mission was to design a three-axis stabilized dual-spinning spacecraft with the largest spinning flexible mesh reflector of any known spacecraft. This paper reports on the attitude control performance of this duel-spinning conicalscanning system during the first 18 months of science operations, and provides an overview of the Guidance, Navigation, and Control (GNC) subsystem performance for this climate monitoring asset.

Sung, Tina S.↗

Historical Retrospective on Orion GNC Design

On November 16, 2022, Artemis I successfully launched and began a nearly 26-day journey returning a human-rated spacecraft to the Moon for the first time in fifty years. The mission was a huge success and once again the world's attention was focused on the Moon. This paper will take a step back in time over the seventeen-plus years of design and development of the Orion Guidance Navigation and Control (GNC) system that carried the spacecraft 1.4 million miles around the Moon and landed safely back on earth off the coast of San Diego California. Key design decisions (good and not so good) and "first-ever" capabilities will be chronicled. This paper will explore such things as the most advanced on-board targeting system ever flown on a spacecraft, never-been-done-before autonomous planetary Optical Navigation, and the first-ever truly skip entry guided to the desired target within a few miles.

Guidance Navigation and Control↗

Historical Retrospective on Orion GNC Design

On November 16, 2022, Artemis I successfully launched and began a nearly 26-day journey returning a human-rated spacecraft to the Moon for the first time in fifty years. The mission was a huge success and once again the world's attention was focused on the Moon. This paper will take a step back in time over the seventeen-plus years of design and development of the Orion Guidance Navigation and Control (GNC) system that carried the spacecraft 1.4 million miles around the Moon and landed safely back on earth off the coast of San Diego California. Key design decisions (good and not so good) and "first-ever" capabilities will be chronicled. This paper will explore such things as the most advanced on-board targeting system ever flown on a spacecraft, never-been-done-before autonomous planetary Optical Navigation, and the first-ever truly skip entry guided to the desired target within a few miles.

Guidance Navigation and Control↗

Conceptual Inquiry of the Space Shuttle and International Space Station GNC Flight Controllers

The concept of Mission Control was envisioned by Christopher Columbus Kraft in the 1960's. Instructed to figure out how to operate human space flight safely, Kraft envisioned a room of sub-system experts troubleshooting problems and supporting nominal flight activities under the guidance of one Flight Director who is responsible for the success of the mission. To facilitate clear communication, MCC communicates with the crew through a Capsule Communicator (CAPCOM) who is an astronaut themselves. Gemini 4 was the first mission to be supported by such a MCC and successfully completed the first American EVA. The MCC seen on television is called the Flight Control Room (FCR, pronounced ficker) or otherwise known as the front room. While this room is the most visible aspect, it is a very small component of the entire control center. The Shuttle FCR is known as the White FCR (WFCR) and Station's as FCR-1. (FCR-1 was actually the first FCR built at JSC which was used through the Gemini, Apollo and Shuttle programs until the WFCR was completed in 1992. Afterwards FCR-1 was refurbished first for the Life Sciences Center and then for the ISS in 2006.) Along with supporting the Flight Director, each FCR operator is also the supervisor for usually two or three support personnel in a back room called the Multi-Purpose Support Room (MPSR, pronounced mipser). MPSR operators are more deeply focused on their specific subsystems and have the responsible to analyze patterns, and diagnose and assess consequences of faults. The White MPSR (WMPSR) operators are always present for Shuttle operations; however, ISS FCR controllers only have support from their Blue MPSR (BMPSR) while the Shuttle is docked and during critical operations. Since ISS operates 24-7, the FCR team reduces to a much smaller Gemini team of 4-5 operators for night and weekend shifts when the crew is off-duty. The FCR is also supported by the Mission Evaluation Room (MER) which is a collection of contractor engineers who provide analysis and long-term troubleshooting support. Each MER operator is an expert in a very small portion of a sub-system and each FCR console usually interfaces with several MER positions.

Kranzusch, Kara↗

A GNC Perspective of the Launch and Commissioning of NASA's SMAP (Soil Moisture Active Passive) Spacecraft

The NASA Soil Moisture Active Passive (SMAP) spacecraft was designed to use radar and radiometer measurements to produce global soil moisture measurements every 2-3 days. The SMAP spacecraft is a complicated dual-spinning design with a large 6 meter deployable mesh reflector mounted on a platform that spins at 14.6 rpm while the Guidance Navigation and Control algorithms maintain precise nadir pointing for the de-spun portion of the spacecraft. After launching in early 2015, the Guidance Navigation and Control software and hardware aboard the SMAP spacecraft underwent an intensive spacecraft checkout and commissioning period. This paper describes the activities performed by the Guidance Navigation and Control team to confirm the health and phasing of subsystem hardware and the functionality of the guidance and control modes and algorithms. The operations tasks performed, as well as anomalies that were encountered during the commissioning, are explained and results are summarized.

Brown, Todd S.↗

Rover Attitude and Pointing System Simulation Testbed

The MER (Mars Exploration Rover) Attitude and Pointing System Simulation Testbed Environment (RAPSSTER) provides a simulation platform used for the development and test of GNC (guidance, navigation, and control) flight algorithm designs for the Mars rovers, which was specifically tailored to the MERs, but has since been used in the development of rover algorithms for the Mars Science Laboratory (MSL) as well. The software provides an integrated simulation and software testbed environment for the development of Mars rover attitude and pointing flight software. It provides an environment that is able to run the MER GNC flight software directly (as opposed to running an algorithmic model of the MER GNC flight code). This improves simulation fidelity and confidence in the results. Further more, the simulation environment allows the user to single step through its execution, pausing, and restarting at will. The system also provides for the introduction of simulated faults specific to Mars rover environments that cannot be replicated in other testbed platforms, to stress test the GNC flight algorithms under examination. The software provides facilities to do these stress tests in ways that cannot be done in the real-time flight system testbeds, such as time-jumping (both forwards and backwards), and introduction of simulated actuator faults that would be difficult, expensive, and/or destructive to implement in the real-time testbeds. Actual flight-quality codes can be incorporated back into the development-test suite of GNC developers, closing the loop between the GNC developers and the flight software developers. The software provides fully automated scripting, allowing multiple tests to be run with varying parameters, without human supervision.

Vanelli, Charles A.↗

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

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