Engineering PapersSearch

Engineering topics

Spehar, Pete

Publications and source records attributed to Spehar, Pete.

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

Control Requirements to Support Manual Piloting Capability

The manual piloting requirements specified under the NASA Constellation Program involved Cooper-Harper ratings, which are a qualitative and subjective evaluation from experienced pilots. This type of verification entails a significant investment of resources to assess a completed design and is not one that can easily or meaningfully be applied upfront in the design phase. The evolution of the Multi-Purpose Crew Vehicle Program to include an independently developed propulsion system from an international partner makes application of Cooper-Harper based design requirements inadequate. To mitigate this issue, a novel solution was developed to reformulate the necessary piloting capability into quantifiable requirements. A trio of requirements was designed which specify control authority, precision, and impulse residuals enabling propulsion design within specified guidance and control boundaries. These requirements have been evaluated against both the existing Orion design and the proposed ESA design and have been found to achieve the desired specificity. The requirement set is capable of being applied to the development of other spacecraft in support of manual piloting.

Merancy, Nujoud

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

Orion Handling Qualities During ISS Proximity Operations and Docking

NASA's Orion spacecraft is designed to autonomously rendezvous and dock with many vehicles including the International Space Station. However, the crew is able to assume manual control of the vehicle s attitude and flight path. In these instances, Orion must meet handling qualities requirements established by NASA. Two handling qualities assessments were conducted at the Johnson Space Center to evaluate preliminary designs of the vehicle using a six degree of freedom, high-fidelity guidance, navigation, and control simulation. The first assessed Orion s handling qualities during the last 20 ft before docking, and included both steady and oscillatory motions of the docking target. The second focused on manual acquisition of the docking axis during the proximity operations phase and subsequent station-keeping. Cooper-Harper handling qualities ratings, workload ratings and comments were provided by 10 evaluation pilots for the docking study and 5 evaluation pilots for the proximity operations study. For the docking task, both cases received 90% Level 1 (satisfactory) handling qualities ratings, exceeding NASA s requirement. All ratings for the ProxOps task were Level 1. These evaluations indicate that Orion is on course to meet NASA's handling quality requirements for ProxOps and docking.

Stephens, John-Paul

Orion Rendezvous, Proximity Operations, and Docking Design and Analysis

The Orion vehicle will be required to perform rendezvous, proximity operations, and docking with the International Space Station (ISS) and the Earth Departure Stage (EDS)/Lunar Landing Vehicle (LLV) stack in Low Earth Orbit (LEO) as well as with the Lunar Landing Vehicle in Low Lunar Orbit (LLO). The RPOD system, which consists of sensors, actuators, and software is being designed to be flexible and robust enough to perform RPOD with different vehicles in different environments. This paper will describe the design and the analysis which has been performed to date to allow the vehicle to perform its mission. Since the RPOD design touches on many areas such as sensors selection and placement, trajectory design, navigation performance, and effector performance, it is inherently a systems design problem. This paper will address each of these issues in order to demonstrate how the Orion RPOD has been designed to accommodate and meet all the requirements levied on the system.

D'Souza, Christopher