Search NASASearch

Engineering topics

Hinkel, Heather

Publications and source records attributed to Hinkel, Heather.

Cislunar Near Rectilinear Halo Orbit for Human Space Exploration

In order to conduct sustained human exploration beyond Low Earth Orbit (LEO), spacecraft systems are designed to operate in a series of missions of increasing complexity. Regardless of the destination, Moon, Mars, asteroids or beyond, there is a substantial set of common objectives that must be met. Many orbit characterization studies have endeavored to evaluate the potential locations in cislunar space that are favorable for meeting common human exploration objectives in a stepwise approach. Multiple studies, by both NASA and other international space agencies, have indicated that Earth-­‐moon libration point orbits are attractive candidates for staging operations in the proving ground and beyond. In particular, the Near Rectilinear Orbit (NRO) has been demonstrated to meet multi-­‐mission and multi-­‐destination architectural constraints. However, a human mission to a selected NRO presents a variety of new challenges for mission planning. While a growing number of robotic missions have completed successful operations to various specific libration point orbits, human missions have never been conducted to orbits of this class. Human missions have unique challenges that differ significantly from robotic missions, including a lower tolerance for mission risk and additional operational constraints that are associated only with human spacecraft. In addition, neither robotic nor human missions have been operated in the NRO regime specifically, and NROs exhibit dynamical characteristics that can differ significantly as compared to other halo orbits. Finally, multi-­‐body orbits, such as libration point orbits, are identified to exist in a simplified orbit model known as the Circular Restricted Three Body Problem (CRTBP) and must then be re-­‐solved in the full ephemeris model. As a result, the behavior of multi-­‐body orbits cannot be effectively characterized within the classical two-­‐body orbit dynamics framework more familiar to the human spaceflight community. In fact, a given NRO is not identified by a set of Keplerian orbit parameters, and a valid epoch specific state vector must be first obtained from a multi-body dynamical model. In this paper, the significant performance and operational challenges of conducting human missions to the NRO are evaluated. First, a systematic process for generating full ephemeris based ballistic NROs of various families is outlined to demonstrate the relative ease in which a multi-­‐revolution orbit can be found for any epoch and for various orbit geometries. In the Earth-­‐Moon system, NROs, which are halo orbits with close passage over a lunar pole, can exist with respect to libration point 1 (L1) or libration point 2 (L2) and are either from a North or South family orbit class with respect to the ecliptic. Second, the ability to maintain the orbit over the lifetime of a habitat mission by applying a reliable station-keeping strategy is investigated. The NRO, while similar to the quasi-­‐halo orbits that the Artemis mission flew, requires an updated station keeping strategy. This is due to several dynamical differences such as the increased relative stability of the NRO compared to other halo orbits and the close passage over the lunar surface as shown in Figure 1. Multiple station-keeping strategies are being investigated to ensure a human spacecraft remains on a predictable path. As the NRO is not described in simple two-­‐body parameters, analysis must determine the best strategy for targeting a reference NRO as well as how closely a future state should be constrained. In addition, costs will be minimized by determining maneuver directionality based on an identified pattern in the optimal station-keeping solutions or an analytically derived relationship. The candidate station-keeping algorithm must be stable and robust to environmental and vehicle uncertainties as well to navigation estimation and flight control execution errors. To that end, navigation accuracies, the impact on the station-keeping execution errors as well as other vehicle uncertainties need to be assessed. Starting with Orion, current navigation accuracies are evaluated and then navigation requirements are derived assuming a desired station-keeping propellant budget. Third, the performance requirements to and from the NRO are evaluated. Important parameters for developing expected propellant costs include epoch of operation, size and type of NRO, Earth departure and return constraints, as well as abort or early-­‐return capability. Finally, rendezvous and proximity operations are vital aspects of multi-­‐mission human exploration endeavors. The ability to conduct rendezvous and the associated propellant costs are assessed as well as the impacts of various profile assumptions including the location within the NRO the rendezvous is performed. The results of these studies will influence plans for international cooperation on both nearer term proving ground missions and beyond.

Whitley, Ryan

Technology Development of Automated Rendezvous and Docking/Capture Sensors and Docking Mechanism for the Asteroid Redirect Crewed Mission

This paper will describe the technology development efforts NASA has underway for Automated Rendezvous and Docking/Capture (AR&D/C) sensors and a docking mechanism and the challenges involved. The paper will additionally address how these technologies will be extended to other missions requiring AR&D/C whether robotic or manned. NASA needs AR&D/C sensors for both the robotic and crewed segments of the Asteroid Redirect Mission (ARM). NASA recently conducted a commonality assessment of the concept of operations for the robotic Asteroid Redirect Vehicle (ARV) and the crewed mission segment using the Orion spacecraft. The commonality assessment also considered several future exploration and science missions requiring an AR&D/C capability. Missions considered were asteroid sample return, satellite servicing, and planetary entry, descent, and landing. This assessment determined that a common sensor suite consisting of one or more visible wavelength cameras, a three-dimensional LIDAR along with long-wavelength infrared cameras for robustness and situational awareness could be used on each mission to eliminate the cost of multiple sensor developments and qualifications. By choosing sensor parameters at build-time instead of at design-time and, without having to requalify flight hardware, a specific mission can design overlapping bearing, range, relative attitude, and position measurement availability to suit their mission requirements with minimal non-recurring engineering costs. The resulting common sensor specification provides the union of all performance requirements for each mission and represents an improvement over the current systems used for AR&D/C today. These sensor specifications are tightly coupled to the docking system capabilities and requirements for final docking conditions. The paper will describe NASA's efforts to develop a standard docking system for use across NASA human spaceflight missions to multiple destinations. It will describe the current design status and the considerations and technologies involved in developing this docking mechanism.

Hinkel, Heather

Technology Development of Automated Rendezvous and Docking/Capture Sensors and Docking Mechanism for the Asteroid Redirect Crewed Mission

This paper will describe the technology development efforts NASA has underway for Automated Rendezvous and Docking/Capture (AR&D/C) sensors and a docking mechanism and the challenges involved. The paper will additionally address how these technologies will be extended to other missions requiring AR&D/C whether robotic or manned. NASA needs AR&D/C sensors for both the robotic and crewed segments of the Asteroid Redirect Mission (ARM). NASA recently conducted a commonality assessment of the concept of operations for the robotic Asteroid Redirect Vehicle (ARV) and the crewed mission segment using the Orion crew vehicle. The commonality assessment also considered several future exploration and science missions requiring an AR&D/C capability. Missions considered were asteroid sample return, satellite servicing, and planetary entry, descent, and landing. This assessment determined that a common sensor suite consisting of one or more visible wavelength cameras, a threedimensional LIDAR along with long-wavelength infrared cameras for robustness and situational awareness could be used on each mission to eliminate the cost of multiple sensor developments and qualifications. By choosing sensor parameters at build time instead of at design time and, without having to requalify flight hardware, a specific mission can design overlapping bearing, range, relative attitude, and position measurement availability to suit their mission requirements with minimal nonrecurring engineering costs. The resulting common sensor specification provides the union of all performance requirements for each mission and represents an improvement over the current systems used for AR&D/C today. These sensor specifications are tightly coupled to the docking system capabilities and requirements for final docking conditions. The paper will describe NASA's efforts to develop a standard docking system for use across NASA human spaceflight missions to multiple destinations. It will describe the current design status and the considerations and technologies involved in developing this docking mechanism.

Hinkel, Heather

Technology Development of Automated Rendezvous and Docking/Capture Sensors and Docking Mechanism for the Asteroid Redirect Crewed Mission

This paper will describe the technology development efforts NASA has underway for Automated Rendezvous and Docking/Capture (AR and D/C) sensors and a docking mechanism and the challenges involved. The paper will additionally address how these technologies will be extended to other missions requiring AR and D/C whether robotic or manned. NASA needs AR&D/C sensors for both the robotic and crewed segments of the Asteroid Redirect Mission (ARM). NASA recently conducted a commonality assessment of the concept of operations for the robotic Asteroid Redirect Vehicle (ARV) and the crewed mission segment using the Orion crew vehicle. The commonality assessment also considered several future exploration and science missions requiring an AR and D/C capability. Missions considered were asteroid sample return, satellite servicing, and planetary entry, descent, and landing. This assessment determined that a common sensor suite consisting of one or more visible wavelength cameras, a threedimensional LIDAR along with long-wavelength infrared cameras for robustness and situational awareness could be used on each mission to eliminate the cost of multiple sensor developments and qualifications. By choosing sensor parameters at build time instead of at design time and, without having to requalify flight hardware, a specific mission can design overlapping bearing, range, relative attitude, and position measurement availability to suit their mission requirements with minimal nonrecurring engineering costs. The resulting common sensor specification provides the union of all performance requirements for each mission and represents an improvement over the current systems used for AR and D/C today. These sensor specifications are tightly coupled to the docking system capabilities and requirements for final docking conditions. The paper will describe NASA's efforts to develop a standard docking system for use across NASA human spaceflight missions to multiple destinations. It will describe the current design status and the considerations and technologies involved in developing this docking mechanism.

Hinkel, Heather

NASA's Automated Rendezvous and Docking/Capture Sensor Development and Its Applicability to the GER

This paper will address how a common Automated Rendezvous and Docking/Capture (AR&D/C) sensor suite can support Global Exploration Roadmap (GER) missions, and discuss how the model of common capability development to support multiple missions can enable system capability level partnerships and further GER objectives. NASA has initiated efforts to develop AR&D/C sensors, that are directly applicable to GER. NASA needs AR&D/C sensors for both the robotic and crewed segments of the Asteroid Redirect Mission (ARM). NASA recently conducted a commonality assessment of the concept of operations for the robotic Asteroid Redirect Vehicle (ARV) and the crewed mission segment using the Orion crew vehicle. The commonality assessment also considered several future exploration and science missions requiring an AR&D/C capability. Missions considered were asteroid sample return, satellite servicing, and planetary entry, descent, and landing. This assessment determined that a common sensor suite consisting of one or more visible wavelength cameras, a three-dimensional LIDAR along with long-wavelength infrared cameras for robustness and situational awareness could be used on each mission to eliminate the cost of multiple sensor developments and qualifications. By choosing sensor parameters at build time instead of at design time and, without having to requalify flight hardware, a specific mission can design overlapping bearing, range, relative attitude, and position measurement availability to suit their mission requirements with minimal nonrecurring engineering costs. The resulting common sensor specification provides the union of all performance requirements for each mission and represents an improvement over the current systems used for AR&D/C today. NASA's AR&D/C sensor development path could benefit the International Exploration Coordination Group (ISECG) and support the GER mission scenario by providing a common sensor suite upon which GER objectives could be achieved while minimizing development costs. The paper will describe the concepts of operations of these missions and how the common sensors are utilized by each mission. It will also detail the potential partnerships and contribution of the International community in the development of this common AR&D/C sensor suite.

Hinkel, Heather

Comparison of Orion Vision Navigation Sensor Performance from STS-134 and the Space Operations Simulation Center

The Orion Multi-Purpose Crew Vehicle is a new spacecraft being designed by NASA and Lockheed Martin for future crewed exploration missions. The Vision Navigation Sensor is a Flash LIDAR that will be the primary relative navigation sensor for this vehicle. To obtain a better understanding of this sensor's performance, the Orion relative navigation team has performed both flight tests and ground tests. This paper summarizes and compares the performance results from the STS-134 flight test, called the Sensor Test for Orion RelNav Risk Mitigation (STORRM) Development Test Objective, and the ground tests at the Space Operations Simulation Center.

Christian, John A.

Guidance, Navigation, and Control Program

The Rendezvous and Proximity Operations Program (RPOP) is real-time guidance, navigation, and control (GN&C) domain piloting-aid software that provides 3D Orbiter graphics and runs on the Space Shuttle's Criticality-3 Payload and General Support Computer (PGSC) in the crew cockpit. This software provides the crew with Situational Awareness during the rendezvous and proximity operations phases of flight. RPOP can be configured from flight to flight, accounting for mission-specific flight scenarios and target vehicles, via initialization load (I-load) data files. The software provides real-time, automated, closed-loop guidance recommendations and the capability to integrate the crew s manual backup techniques. The software can bring all relative navigation sensor data, including the Orbiter's GPC (general purpose computer) data, into one central application to provide comprehensive situational awareness of the rendezvous and proximity operations trajectory. RPOP also can separately maintain trajectory estimates (past, current, and predicted) based on certain data types and co-plot them, in order to show how the various navigation solutions compare. RPOP s best estimate of the relative trajectory is determined by a relative Kalman filter processing data provided by the sensor suite s most accurate sensor, the trajectory control sensor (TCS). Integrated with the Kalman filter is an algorithm that identifies the reflector that the TCS is tracking. Because RPOP runs on PC laptop computers, the development and certification lifecycles are more agile, flexible, and cheaper than those that govern the Orbiter FSW (flight software) that runs in the GPC. New releases of RPOP can be turned around on a 3- to 6-month template, from new Change Request (CR) to certification, depending on the complexity of the changes.

Hinkel, Heather

The Sensor Test for Orion RelNav Risk Mitigation Development Test Objective

The Sensor Test for Orion Relative-Navigation Risk Mitigation (STORRM) Development Test Objective (DTO) ew aboard the Space Shuttle Endeavour on STS-134, and was designed to characterize the performance of the ash LIDAR being developed for the Orion. This ash LIDAR, called the Vision Navigation Sensor (VNS), will be the primary navigation instrument used by the Orion vehicle during rendezvous, proximity operations, and docking. This paper provides an overview of the STORRM test objectives and the concept of operations. It continues with a description of the STORRM's major hardware compo nents, which include the VNS and the docking camera. Next, an overview of crew and analyst training activities will describe how the STORRM team prepared for flight. Then an overview of how insight data collection and analysis actually went is presented. Key ndings and results from this project are summarized, including a description of "truth" data. Finally, the paper concludes with lessons learned from the STORRM DTO.

Christian, John A.

The Sensor Test for Orion RelNav Risk Mitigation (STORRM) Development Test Objective

The Sensor Test for Orion Relative-Navigation Risk Mitigation (STORRM) Development Test Objective (DTO) flew aboard the Space Shuttle Endeavour on STS-134 in May- June 2011, and was designed to characterize the performance of the flash LIDAR and docking camera being developed for the Orion Multi-Purpose Crew Vehicle. The flash LIDAR, called the Vision Navigation Sensor (VNS), will be the primary navigation instrument used by the Orion vehicle during rendezvous, proximity operations, and docking. The DC will be used by the Orion crew for piloting cues during docking. This paper provides an overview of the STORRM test objectives and the concept of operations. It continues with a description of STORRM's major hardware components, which include the VNS, docking camera, and supporting avionics. Next, an overview of crew and analyst training activities will describe how the STORRM team prepared for flight. Then an overview of in-flight data collection and analysis is presented. Key findings and results from this project are summarized. Finally, the paper concludes with lessons learned from the STORRM DTO.

Christian, John A.

NASA CEV Reference GN&C Architecture

The Orion Crew Exploration Vehicle (CEV) will be the first human spacecraft built by NASA in almost 3 decades and will be the first vehicle to perform both Low Earth Orbit (LEO) missions and lunar missions since Apollo. The awesome challenge of designing a Guidance, Navigation, and Control (GN&C) system for this vehicle that satisfies all of its various mission requirements is countered by the opportunity to take advantage of the improvements in algorithms, software, sensors, and other related GN&C technology over this period. This paper describes the CEV GN&C reference architecture developed to support the overall NASA reference configuration and validate the driving requirements of the Constellation (Cx) Architecture Requirements Document (CARD, Reference 1) and the CEV System Requirements Document (SRD, Reference 2). The Orion GN&C team designed the reference architecture based on the functional allocation of GN&C roles and responsibilities of CEV with respect to the other Cx vehicles, such as the Crew Launch Vehicle (CLV), Earth Departure Stage (EDS), and Lunar Surface Area Module (LSAM), across all flight phases. The specific challenges and responsibilities of the CEV GN&C system from launch pad to touchdown will be introduced along with an overview of the navigation sensor suite, its redundancy management, and flight software (FSW) architecture. Sensors will be discussed in terms of range of operation, data utility within the navigation system, and rationale for selection. The software architecture is illustrated via block diagrams, commensurate with the design aspects.

Tamblyn, Scott