Search NASASearch

Engineering topics

Clark, Fred

Publications and source records attributed to Clark, Fred.

Orbit Maintenance and Navigation of Human Spacecraft at Cislunar Near Rectilinear Halo Orbits

Multiple studies have concluded that Earth-Moon libration point orbits are attractive candidates for staging operations. The Near Rectilinear Halo Orbit (NRHO), a member of the Earth-Moon halo orbit family, has been singularly demonstrated to meet multi-mission architectural constraints. In this paper, the challenges associated with operating human spacecraft in the NRHO are evaluated. Navigation accuracies and human vehicle process noise effects are applied to various station keeping strategies in order to obtain a reliable orbit maintenance algorithm. Additionally, the ability to absorb missed burns, construct phasing maneuvers to avoid eclipses and conduct rendezvous and proximity operations are examined.

Davis, Diane

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

FLASH LIDAR Based Relative Navigation

Relative navigation remains the most challenging part of spacecraft rendezvous and docking. In recent years, flash LIDARs, have been increasingly selected as the go-to sensors for proximity operations and docking. Flash LIDARS are generally lighter and require less power that scanning Lidars. Flash LIDARs do not have moving parts, and they are capable of tracking multiple targets as well as generating a 3D map of a given target. However, there are some significant drawbacks of Flash Lidars that must be resolved if their use is to be of long-term significance. Overcoming the challenges of Flash LIDARs for navigation-namely, low technology readiness level, lack of historical performance data, target identification, existence of false positives, and performance of vision processing algorithms as intermediaries between the raw sensor data and the Kalman filter-requires a world-class testing facility, such as the Lockheed Martin Space Operations Simulation Center (SOSC). Ground-based testing is a critical step for maturing the next-generation flash LIDAR-based spacecraft relative navigation. This paper will focus on the tests of an integrated relative navigation system conducted at the SOSC in January 2014. The intent of the tests was to characterize and then improve the performance of relative navigation, while addressing many of the flash LIDAR challenges mentioned above. A section on navigation performance and future recommendation completes the discussion.

Brazzel, Jack

The Rendezvous Monitoring Display Capabilities of the Rendezvous and Proximity Operations Program

The Rendezvous and Proximity Operations Program (RPOP) is a laptop computer- based relative navigation tool and piloting aid that was developed during the Space Shuttle program. RPOP displays a graphical representation of the relative motion between the target and chaser vehicles in a rendezvous, proximity operations and capture scenario. After being used in over 60 Shuttle rendezvous missions, some of the RPOP display concepts have become recognized as a minimum standard for cockpit displays for monitoring the rendezvous task. To support International Space Station (ISS) based crews in monitoring incoming visiting vehicles, RPOP has been modified to allow crews to compare the Cygnus visiting vehicle s onboard navigated state to processed range measurements from an ISS-based, crew-operated Hand Held Lidar sensor. This paper will discuss the display concepts of RPOP that have proven useful in performing and monitoring rendezvous and proximity operations.

Brazzel, Jack

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