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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2022

Night Sky Testing of the Lunar Flashlight Star Tracker

Lunar Flashlight (LF) is a 6U, 14 kg spacecraft being built by the NASA Jet Propulsion Laboratory (JPL). The mission will use IR laser technology to search for volatiles and surface water ice deposits in the permanently shadowed regions (PSR) of the moon in preparation for future human lunar exploration. The fine pointing provided by the Guidance, Navigation and Control (GNC) system is crucial for the spacecraft to successfully reach the moon, enter a lunar orbit, and acquire scientific data. At the center of the GNC system’s ability to determine the spacecraft’s attitude is a star tracker. The LF star tracker is a commercial-off-the-shelf (COTS) unit built into the integrated GNC system provided by Blue Canyon Technologies. Blue Canyon tested the star tracker in a lab environment for basic functionality and attitude estimation capabilities; upon delivery of the hardware to JPL, further testing with a real night sky was desired to determine expected in-flight operational characteristics. JPL maintains the Table Mountain Facility with its suite of ground telescopes, including a 0.6m telescope with an equatorial mount. This stable platform provided a highly accurate method of providing slews and attitude holds akin to what the spacecraft will perform in flight. Therefore, by analyzing the data from these representative night-sky ground tests performed in March, 2021, it is possible to acquire expected flight performance of the star tracker, particularly in regard to the ability of the star tracker to maintain lock on the starfield during planned maneuver types. This paper presents the various tests that have been performed to ensure that the LF star tracker will function as part of the overall GNC system and integrated spacecraft once launched. Test data is included for several key tests, and a path forward towards future integration and testing at the spacecraft level is described.

Baker, John↗
NASA NTRS2008

Guidance, Navigation, and Control System Design in a Mass Reduction Exercise

Early Orion GN&C system designs optimized for robustness, simplicity, and utilization of commercially available components. During the System Definition Review (SDR), all subsystems on Orion were asked to re-optimize with component mass and steady state power as primary design metrics. The objective was to create a mass reserve in the Orion point of departure vehicle design prior to beginning the PDR analysis cycle. The Orion GN&C subsystem team transitioned from a philosophy of absolute 2 fault tolerance for crew safety and 1 fault tolerance for mission success to an approach of 1 fault tolerance for crew safety and risk based redundancy to meet probability allocations of loss of mission and loss of crew. This paper will discuss the analyses, rationale, and end results of this activity regarding Orion navigation sensor hardware, control effectors, and trajectory design.

Crain, Timothy↗
NASA NTRS1989

Evolutionary growth for Space Station Freedom electrical power system

Over an operational lifetime of at least 30 yr, Space Station Freedom will encounter increased space station user requirements and advancing technologies. The space station electrical power system is designed with the flexibility to accommodate these emerging technologies and expert systems and is being designed with the necessary software hooks and hardware scars to accommodate increased growth demand. The electrical power system is planned to grow from the initial 75 kW up to 300 kW. The Phase 1 station will utilize photovoltaic arrays to produce the electrical power; however, for growth to 300 kW, solar dynamic power modules will be utilized. Pairs of 25 kW solar dynamic power modules will be added to the station to reach the power growth level. The addition of solar dynamic power in the growth phase places constraints in the initial space station systems such as guidance navigation and control, external thermal, truss structural stiffness, computational capabilities and storage which must be planned-in in order to facilitate the addition of the solar dynamic modules.

Marshall, Matthew F.↗
NASA NTRS1989

Evolutionary growth for Space Station Freedom electrical power system

Over an operational lifetime of at least 30 yr, Space Station Freedom will encounter increased Space Station user requirements and advancing technologies. The Space Station electrical power system is designed with the flexibility to accommodate these emerging technologies and expert systems and is being designed with the necessary software hooks and hardware scars to accommodate increased growth demand. The electrical power system is planned to grow from the initial 75 kW up to 300 kW. The Phase 1 station will utilize photovoltaic arrays to produce the electrical power; however, for growth to 300 kW, solar dynamic power modules will be utilized. Pairs of 25 kW solar dynamic power modules will be added to the station to reach the power growth level. The addition of solar dynamic power in the growth phase places constraints in the initial Space Station systems such as guidance, navigation, and control, external thermal, truss structural stiffness, computational capabilities and storage, which must be planned-in, in order to facilitate the addition of the solar dynamic modules.

Marshall, Matthew Fisk↗
NASA NTRS1991

An overview of autonomous rendezvous and docking system technology development

The Centaur upper stage was selected for an airborne avionics modernization program. The parts used in the existing avionics units were obsolete. Continued use of existing hardware would require substantial redesign, yet would result in the use of outdated hardware. Out of date processes, with very expensive and labor intensive technologies, were being used for manufacturing. The Atlas/Centaur avionics were to be procured at a fairly high rate that demanded the use of modern components. The new avionics also reduce size, weight, power, and parts count with a dramatic improvement in reliability. Finally, the cost leverage derived from upgrading the avionics as opposed to any other subsystem for the existing Atlas/Centaur was a very large consideration in the upgrade decision. The upgrade program is a multiyear effort that began in 1989. It includes telemetry, guidance and navigation, control electronics, thrust vector control, and redundancy levels.

Nelson, Kurt D.↗
NASA NTRS2008

ULTOR(Registered TradeMark) Passive Pose and Position Engine For Spacecraft Relative Navigation

The ULTOR(Registered TradeMark) Passive Pose and Position Engine (P3E) technology, developed by Advanced Optical Systems, Inc (AOS), uses real-time image correlation to provide relative position and pose data for spacecraft guidance, navigation, and control. Potential data sources include a wide variety of sensors, including visible and infrared cameras. ULTOR(Registered TradeMark) P3E has been demonstrated on a number of host processing platforms. NASA is integrating ULTOR(Registerd TradeMark) P3E into its Relative Navigation System (RNS), which is being developed for the upcoming Hubble Space Telescope (HST) Servicing Mission 4 (SM4). During SM4 ULTOR(Registered TradeMark) P3E will perform realtime pose and position measurements during both the approach and departure phases of the mission. This paper describes the RNS implementation of ULTOR(Registered TradeMark) P3E, and presents results from NASA's hardware-in-the-loop simulation testing against the HST mockup.

Hannah, S. Joel↗
NASA NTRS2019

Adaptations of guidance, navigation, and control verification and validation philosophies for small spacecraft

Decades of experience developing increasingly capable and more complex space-craft have resulted in a set of accepted practices and philosophies to verify and validate (V&V) guidance, navigation, and control (GN&C) subsystems. Until recently, small, low-cost spacecraft have had very simple or non-existent GN&C subsystems requiring minimal or no subsystem testing. As the next generation of small spacecraft take on more challenging GN&C requirements, the GN&C community is struggling with how to scale the subsystem V&V effort to produce spacecraft approaching the reliability of flagship-class missions while staying within the reduced resources of a small satellite project.For this paper, we will examine five aspects of GN&C V&V (requirements definition, software testing and analysis, hardware component testing, integrated vehicle testing, and in-flight V&V) and compare the V&V campaign of a flagship-class mission (Mars 2020) to that of two recent, successful CubeSat missions: ASTERIA and MarCO. Experiences from the development of these CubeSats yield valuable lessons learned and guidelines for future small spacecraft designers.

Chen, George T.↗
NASA NTRS2019

Adaptations of Guidance, Navigation and Control Verification and Validation Philosophies for Small Spacecraft

Decades of experience developing increasingly capable and more complex space-craft have resulted in a set of accepted practices and philosophies to verify and validate (V&V) guidance, navigation, and control (GN&C) subsystems. Until recently, small, low-cost spacecraft have had very simple or non-existent GN&C subsystems requiring minimal or no subsystem testing. As the next generation of small spacecraft take on more challenging GN&C requirements, the GN&C community is struggling with how to scale the subsystem V&V effort to produce spacecraft approaching the reliability of flagship-class missions while staying within the reduced resources of a small satellite project. For this paper, we will examine five aspects of GN&C V&V (requirements definition, software testing and analysis, hardware component testing, integrated vehicle testing, and in-flight V&V) and compare the V&V campaign of a flagship-class mission (Mars 2020) to that of two recent, successful CubeSat missions: ASTERIA and MarCO. Experiences from the development of these CubeSats yield valuable lessons learned and guidelines for future small spacecraft designers.

Pong, Christopher M.↗
NASA NTRS2024

Safe and Precise Landing Integrated Capabilities Evolution (SPLICE) Imagery of Sensors

Collection of imagery of SPLICE hardware and software visualization. Descent Landing Computer ETU Open Frame Chassis (OFC). ETU pictures of the GSFC Hazard Detection Lidar during assembly. Prototype picture of the delivered Psionic Navigation Doppler Lidar, including testing with a three-dimensional mobile target. Visualization of a lunar lander simulation using the Dual Quaternion Guidance, demonstrating pointing of a mounted hazard lidar, and then diverting to a selected safe site.

Guidance Navigation and Control↗
NASA NTRS1995

AIAA spacecraft GN&C interface standards initiative: Overview

The American Institute of Aeronautics and Astronautics (AIAA) has undertaken an important standards initiative in the area of spacecraft guidance, navigation, and control (GN&C) subsystem interfaces. The objective of this effort is to establish standards that will promote interchangeability of major GN&C components, thus enabling substantially lower spacecraft development costs. Although initiated by developers of conventional spacecraft GN&C, it is anticipated that interface standards will also be of value in reducing the development costs of micro-engineered spacecraft. The standardization targets are specifically limited to interfaces only, including information (i.e. data and signal), power, mechanical, thermal, and environmental interfaces between various GN&C components and between GN&C subsystems and other subsystems. The current emphasis is on information interfaces between various hardware elements (e.g., between star trackers and flight computers). The poster presentation will briefly describe the program, including the mechanics and schedule, and will publicize the technical products as they exist at the time of the conference. In particular, the rationale for the adoption of the AS1773 fiber-optic serial data bus and the status of data interface standards at the application layer will be presented.

Challoner, A. Dorian↗
NASA NTRS1999

Design Description of the X-33 Avionics Architecture

In this paper, we provide a design description of the X-33 avionics architecture. The X-33 is an autonomous Single Stage to Orbit (SSTO) launch vehicle currently being developed by Lockheed Martin for NASA as a technology demonstrator for the VentureStar Reusable Launch Vehicle (RLV). The X-33 avionics provides autonomous control of die vehicle throughout takeoff, ascent, descent, approach, landing, rollout, and vehicle safing. During flight the avionics provides communication to the range through uplinked commands and downlinked telemetry. During pre-launch and post-safing activities, the avionics provides interfaces to ground support consoles that perform vehicle flight preparations and maintenance. The X-33 Avionics is a hybrid of centralized and distributed processing elements connected by three dual redundant Mil-Std 1553 data buses. These data buses are controlled by a central processing suite located in the avionics bay and composed of triplex redundant Vehicle Mission Computers (VMCs). The VMCs integrate mission management, guidance, navigation, flight control, subsystem control and redundancy management functions. The vehicle sensors, effectors and subsystems are interfaced directly to the centralized VMCs as remote terminals or through dual redundant Data Interface Units (DIUs). The DIUs are located forward and aft of the avionics bay and provide signal conditioning, health monitoring, low level subsystem control and data interface functions. Each VMC is connected to all three redundant 1553 data buses for monitoring and provides a complete identical data set to the processing algorithms. This enables bus faults to be detected and reconfigured through a voted bus control configuration. Data is also shared between VMCs though a cross channel data link that is implemented in hardware and controlled by AlliedSignal's Fault Tolerant Executive (FTE). The FTE synchronizes processors within the VMC and synchronizes redundant VMCs to each other. The FTE provides an output-voting plane to detect, isolate and contain faults due to internal hardware or software faults and reconfigures the VMCs to accommodate these faults. Critical data in the 1553 messages are scheduled and synchronized to specific processing frames in order to minimize data latency. In order to achieve an open architecture, military and commercial off-the-shelf equipment is incorporated using common processors, standard VME backplanes and chassis, the VxWorks operating system, and MartixX for automatic code generation. The use of off-the-shelf tools and equipment helps reduce development time and enables software reuse. The open architecture allows for technology insertion, while the distributed modular elements allow for expansion to increased redundancy levels to meet the higher reliability goals of future RLVs.

Reichenfeld, Curtis J.↗
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 NTRS1991

An autonomous rendezvous and docking system using cruise missile technologies

In November 1990 the Autonomous Rendezvous & Docking (AR&D) system was first demonstrated for members of NASA's Strategic Avionics Technology Working Group. This simulation utilized prototype hardware from the Cruise Missile and Advanced Centaur Avionics systems. The object was to show that all the accuracy, reliability and operational requirements established for a space craft to dock with Space Station Freedom could be met by the proposed system. The rapid prototyping capabilities of the Advanced Avionics Systems Development Laboratory were used to evaluate the proposed system in a real time, hardware in the loop simulation of the rendezvous and docking reference mission. The simulation permits manual, supervised automatic and fully autonomous operations to be evaluated. It is also being upgraded to be able to test an Autonomous Approach and Landing (AA&L) system. The AA&L and AR&D systems are very similar. Both use inertial guidance and control systems supplemented by GPS. Both use an Image Processing System (IPS), for target recognition and tracking. The IPS includes a general purpose multiprocessor computer and a selected suite of sensors that will provide the required relative position and orientation data. Graphic displays can also be generated by the computer, providing the astronaut / operator with real-time guidance and navigation data with enhanced video or sensor imagery.

Jones, Ruel Edwin↗
NASA NTRS2007

SPARTAN: A High-Fidelity Simulation for Automated Rendezvous and Docking Applications

bd Systems (a subsidiary of SAIC) has developed the Simulation Package for Autonomous Rendezvous Test and ANalysis (SPARTAN), a high-fidelity on-orbit simulation featuring multiple six-degree-of-freedom (6DOF) vehicles. SPARTAN has been developed in a modular fashion in Matlab/Simulink to test next-generation automated rendezvous and docking guidance, navigation,and control algorithms for NASA's new Vision for Space Exploration. SPARTAN includes autonomous state-based mission manager algorithms responsible for sequencing the vehicle through various flight phases based on on-board sensor inputs and closed-loop guidance algorithms, including Lambert transfers, Clohessy-Wiltshire maneuvers, and glideslope approaches The guidance commands are implemented using an integrated translation and attitude control system to provide 6DOF control of each vehicle in the simulation. SPARTAN also includes high-fidelity representations of a variety of absolute and relative navigation sensors that maybe used for NASA missions, including radio frequency, lidar, and video-based rendezvous sensors. Proprietary navigation sensor fusion algorithms have been developed that allow the integration of these sensor measurements through an extended Kalman filter framework to create a single optimal estimate of the relative state of the vehicles. SPARTAN provides capability for Monte Carlo dispersion analysis, allowing for rigorous evaluation of the performance of the complete proposed AR&D system, including software, sensors, and mechanisms. SPARTAN also supports hardware-in-the-loop testing through conversion of the algorithms to C code using Real-Time Workshop in order to be hosted in a mission computer engineering development unit running an embedded real-time operating system. SPARTAN also contains both runtime TCP/IP socket interface and post-processing compatibility with bdStudio, a visualization tool developed by bd Systems, allowing for intuitive evaluation of simulation results. A description of the SPARTAN architecture and capabilities is provided, along with details on the models and algorithms utilized and results from representative missions.

Turbe, Michael A.↗
NASA NTRS2006

AERCam Autonomy: Intelligent Software Architecture for Robotic Free Flying Nanosatellite Inspection Vehicles

The NASA Johnson Space Center has developed a nanosatellite-class Free Flyer intended for future external inspection and remote viewing of human spacecraft. The Miniature Autonomous Extravehicular Robotic Camera (Mini AERCam) technology demonstration unit has been integrated into the approximate form and function of a flight system. The spherical Mini AERCam Free Flyer is 7.5 inches in diameter and weighs approximately 10 pounds, yet it incorporates significant additional capabilities compared to the 35-pound, 14-inch diameter AERCam Sprint that flew as a Shuttle flight experiment in 1997. Mini AERCam hosts a full suite of miniaturized avionics, instrumentation, communications, navigation, power, propulsion, and imaging subsystems, including digital video cameras and a high resolution still image camera. The vehicle is designed for either remotely piloted operations or supervised autonomous operations, including automatic stationkeeping, point-to-point maneuvering, and waypoint tracking. The Mini AERCam Free Flyer is accompanied by a sophisticated control station for command and control, as well as a docking system for automated deployment, docking, and recharge at a parent spacecraft. Free Flyer functional testing has been conducted successfully on both an airbearing table and in a six-degree-of-freedom closed-loop orbital simulation with avionics hardware in the loop. Mini AERCam aims to provide beneficial on-orbit views that cannot be obtained from fixed cameras, cameras on robotic manipulators, or cameras carried by crewmembers during extravehicular activities (EVA s). On Shuttle or International Space Station (ISS), for example, Mini AERCam could support external robotic operations by supplying orthogonal views to the intravehicular activity (IVA) robotic operator, supply views of EVA operations to IVA and/or ground crews monitoring the EVA, and carry out independent visual inspections of areas of interest around the spacecraft. To enable these future benefits with minimal impact on IVA operators and ground controllers, the Mini AERCam system architecture incorporates intelligent systems attributes that support various autonomous capabilities. 1) A robust command sequencer enables task-level command scripting. Command scripting is employed for operations such as automatic inspection scans over a region of interest, and operator-hands-off automated docking. 2) A system manager built on the same expert-system software as the command sequencer provides detection and smart-response capability for potential system-level anomalies, like loss of communications between the Free Flyer and control station. 3) An AERCam dynamics manager provides nominal and off-nominal management of guidance, navigation, and control (GN&C) functions. It is employed for safe trajectory monitoring, contingency maneuvering, and related roles. This paper will describe these architectural components of Mini AERCam autonomy, as well as the interaction of these elements with a human operator during supervised autonomous control.

Fredrickson, Steven E.↗
NASA NTRS2017

Ground Demonstration on the Autonomous Docking of Two 3U CubeSats Using a Novel Permanent-Magnet Docking Mechanism

Small spacecraft autonomous rendezvous and docking is an essential technology for future space structure assembly missions. A novel magnetic capture and latching mechanism is analyzed that allows for docking of two CubeSats without precise sensors and actuators. The proposed magnetic docking hardware not only provides the means to latch the CubeSats but it also significantly increases the likelihood of successful docking in the presence of relative attitude and position errors. The simplicity of the design allows it to be implemented on many CubeSat rendezvous missions. A CubeSat 3-DOF ground demonstration effort is on-going at NASA Langley Research Center that enables hardware-in-the loop testing of the autonomous approach and docking of a follower CubeSat to an identical leader CubeSat. The test setup consists of a 3 meter by 4 meter granite table and two nearly frictionless air bearing systems that support the two CubeSats. Four cold-gas on-off thrusters are used to translate the follower towards the leader, while a single reaction wheel is used to control the attitude of each CubeSat. An innovative modified pseudo inverse control allocation scheme was developed to address interactions between control effectors. The docking procedure requires relatively high actuator precision, a novel minimal impulse bit mitigation algorithm was developed to minimize the undesirable deadzone effects of the thrusters. Simulation of the ground demonstration shows that the Guidance, Navigation, and Control system along with the docking subsystem leads to successful docking under 3-sigma dispersions for all key system parameters. Extensive simulation and ground testing will provide sufficient confidence that the proposed docking mechanism along with the choosen suite of sensors and actuators will perform successful docking in the space environment.

Pei, Jing↗
NASA NTRS1973

Astrionics system designers handbook, volume 1

Hardware elements in new and advanced astrionics system designs are discussed. This cost effective approach has as its goal the reduction of R&D and testing costs through the application of proven and tested astrionics components. The ready availability to the designer of data facts for applicable system components is highly desirable. The astrionics System Designers Handbook has as its objective this documenting of data facts to serve the anticipated requirements of the astrionics system designer. Eleven NASA programs were selected as the reference base for the document. These programs are: ATS-F, ERTS-B, HEAO-A, OSO-I, Viking Orbiter, OAO-C, Skylab AM/MDA, Skylab ATM, Apollo 17 CSM, Apollo 17 LM and Mariner Mars 71. Four subsystems were chosen for documentation: communications, data management, electrical power and guidance, navigation and control.

Source record↗