The Deep Space Positioning System (DPS) – Navigator Concept for the Lunar Gateway
UNKNOWN
Vaughan, Andrew T.↗
Engineering topics
Vaughan, Andrew T.
Publications and source records attributed to Vaughan, Andrew T..
The Deep Space Positioning System (DPS) - navigator concept for the Lunar Gateway
For the lunar Gateway, the optical only version is sufficient given the abundance of optical targets in the form of lunar surface landmarks.
Vaughan, Andrew T.↗
The Deep-Space Positioning System Concept: Automating Complex Navigation Operations Beyond the Earth
There is no equivalent of GPS in “deep space,” that is beyond the Earth Moon system (and use of GPS beyond LEO and MEO is already problematic.) NASA has been awarded a patent on the concept of the “Deep-space Positioning System” (DPS) which is a self-contained instrument concept that would use in-situ observations to provide an automated and autonomous means of determining its position in the Solar System, and at least as important, its position relative to a target, whether that target is a planet, asteroid, moon or comet. In addition, the DPS system computes trajectory change parameters, as necessary to keep a spacecraft on a planned trajectory. Implementation options include the use of a radio receiver to receive a frequency beacon from a non-in-situ source for additional navigation information over and above that which can be provided by the cameras that are the principal data source of DPS. This paper discusses the DPS instrument concept, and its potential use in deep space.
Guinn, Joseph R.↗
Deep Space Positioning System
A single, compact, lower power deep space positioning system (DPS) configured to determine a location of a spacecraft anywhere in the solar system, and provide state information relative to Earth, Sun, or any remote object. For example, the DPS includes a first camera and, possibly, a second camera configured to capture a plurality of navigation images to determine a state of a spacecraft in a solar system. The second camera is located behind, or adjacent to, a secondary reflector of a first camera in a body of a telescope.
Vaughan, Andrew T.↗
Autonomous GN and C for Spacecraft Exploration of Comets and Asteroids
A spacecraft guidance, navigation, and control (GN&C) system is needed to enable a spacecraft to descend to a surface, take a sample using a touch-and-go (TAG) sampling approach, and then safely ascend. At the time of this reporting, a flyable GN&C system that can accomplish these goals is beyond state of the art. This article describes AutoGNC, which is a GN&C system capable of addressing these goals, which has recently been developed and demonstrated to a maturity TRL-5-plus. The AutoGNC solution matures and integrates two previously existing JPL capabilities into a single unified GN&C system. The two capabilities are AutoNAV and GREX. AutoNAV is JPL s current flight navigation system, and is fairly mature with respect to flybys and rendezvous with small bodies, but is lacking capability for close surface proximity operations, sampling, and contact. G-REX is a suite of low-TRL algorithms and capabilities that enables spacecraft operations in close surface proximity and for performing sampling/contact. The development and integration of AutoNAV and G-REX components into AutoGNC provides a single, unified GN&C capability for addressing the autonomy, close-proximity, and sampling/contact aspects of small-body sample return missions. AutoGNC is an integrated capability comprising elements that were developed separately. The main algorithms and component capabilities that have been matured and integrated are autonomy for near-surface operations, terrain-relative navigation (TRN), real-time image-based feedback guidance and control, and six degrees of freedom (6DOF) control of the TAG sampling event. Autonomy is achieved based on an AutoGNC Executive written in Virtual Machine Language (VML) incorporating high-level control, data management, and fault protection. In descending to the surface, the AutoGNC system uses camera images to determine its position and velocity relative to the terrain. This capability for TRN leverages native capabilities of the original AutoNAV system, but required advancements that integrate the separate capabilities for shape modeling, state estimation, image rendering, defining a database of onboard maps, and performing real-time landmark recognition against the stored maps. The ability to use images to guide the spacecraft requires the capability for image-based feedback control. In Auto- GNC, navigation estimates are fed into an onboard guidance and control system that keeps the spacecraft guided along a desired path, as it descends towards its targeted landing or sampling site. Once near the site, AutoGNC achieves a prescribed guidance condition for TAG sampling (position/orientation, velocity), and a prescribed force profile on the sampling end-effector. A dedicated 6DOF TAG control then implements the ascent burn while recovering from sampling disturbances and induced attitude rates. The control also minimizes structural interactions with flexible solar panels and disallows any part of the spacecraft from making contact with the ground (other than the intended end-effector).
Carson, John M.↗
Optical Navigation Plan and Strategy for the Lunar Lander Altair
This paper reviews the currently planned Altair Optical Navigation (OpNav) system. The discussion includes description of the OpNav camera manifest. The Altair OpNav plan envisions one, OpNav camera assembly, with perhaps a functional backup that includes a wide angle-imager (of 40 deg to 60 deg field of view - FOV), and a narrow angle imager (of 1 to 3 deg FOV) co-mounted on a 2-degree-of-freedom gimbal. Both imagers are assumed to be relatively wide aperture and large dynamic range to provide excellent short-exposure images at mid-latitudes, and adequate images of longer-exposure near the poles. Landmark modeling and tracking methodology is discussed, including the stereophotoclinometry method assumed to be used to obtain high-accuracy terrain maps at lunar landing sites of 1 - 2 m, and 50 - 100 m elsewhere, using the images expected to be obtained from the Lunar Reconnaissance Orbiter (LRO). Characteristics of the OpNav navigation system are discussed and architecture and results from landing simulations presented, showing expected landing accuracies of better than 10m.
TAG↗
AutoGNC Testbed
A simulation testbed architecture was developed and implemented for the integration, test, and development of a TRL-6 flight software set called Auto- GNC. The AutoGNC software will combine the TRL-9 Deep Impact AutoNAV flight software suite, the TRL-9 Virtual Machine Language (VML) executive, and the TRL-3 G-REX guidance, estimation, and control algorithms. The Auto- GNC testbed was architected to provide software interface connections among the AutoNAV and VML flight code written in C, the G-REX algorithms in MATLAB and C, stand-alone image rendering algorithms in C, and other Fortran algorithms, such as the OBIRON landmark tracking suite. The testbed architecture incorporates software components for propagating a high-fidelity truth model of the environment and the spacecraft dynamics, along with the flight software components for onboard guidance, navigation, and control (GN&C). The interface allows for the rapid integration and testing of new algorithms prior to development of the C code for implementation in flight software. This testbed is designed to test autonomous spacecraft proximity operations around small celestial bodies, moons, or other spacecraft. The software is baselined for upcoming comet and asteroid sample return missions. This architecture and testbed will provide a direct improvement upon the onboard flight software utilized for missions such as Deep Impact, Stardust, and Deep Space 1.
Carson, John M., III↗
Reactive Sequencing for Autonomous Navigation Evolving from Phoenix Entry, Descent, and Landing
Virtual Machine Language (VML) is an award-winning advanced procedural sequencing language in use on NASA deep-space missions since 1997, and was used for the successful entry, descent, and landing (EDL) of the Phoenix spacecraft onto the surface of Mars. Phoenix EDL utilized a state-oriented operations architecture which executed within the constraints of the existing VML 2.0 flight capability, compatible with the linear "land or die" nature of the mission. The intricacies of Phoenix EDL included the planned discarding of portions of the vehicle, the complex communications management for relay through on-orbit assets, the presence of temporally indeterminate physical events, and the need to rapidly catch up four days of sequencing should a reboot of the spacecraft flight computer occur shortly before atmospheric entry. These formidable operational challenges led to new techniques for packaging and coordinating reusable sequences called blocks using one-way synchronization via VML sequencing global variable events. The coordinated blocks acted as an ensemble to land the spacecraft, while individually managing various elements in as simple a fashion as possible. This paper outlines prototype VML 2.1 flight capabilities that have evolved from the one-way synchronization techniques in order to implement even more ambitious autonomous mission capabilities. Target missions for these new capabilities include autonomous touch-and-go sampling of cometary and asteroidal bodies, lunar landing of robotic missions, and ultimately landing of crewed lunar vehicles. Close proximity guidance, navigation, and control operations, on-orbit rendezvous, and descent and landing events featured in these missions require elaborate abort capability, manifesting highly non-linear scenarios that are so complex as to overtax traditional sequencing, or even the sort of one-way coordinated sequencing used during EDL. Foreseeing advanced command and control needs for small body and lunar landing guidance, navigation and control scenarios, work began three years ago on substantial upgrades to VML that are now being exercised in scenarios for lunar landing and comet/asteroid rendezvous. The advanced state-based approach includes coordinated state transition machines with distributed decision-making logic. These state machines are not merely sequences - they are reactive logic constructs capable of autonomous decision making within a well-defined domain. Combined with the JPL's AutoNav software used on Deep Space 1 and Deep Impact, the system allows spacecraft to autonomously navigate to an unmapped surface, soft-contact, and either land or ascend. The state machine architecture enabled by VML 2.1 has successfully performed sampling missions and lunar descent missions in a simulated environment, and is progressing toward flight capability. The authors are also investigating using the VML 2.1 flight director architecture to perform autonomous activities like rendezvous with a passive hypothetical Mars sample return capsule. The approach being pursued is similar to the touch-and-go sampling state machines, with the added complications associated with the search for, physical capture of, and securing of a separate spacecraft. Complications include optically finding and tracking the Orbiting Sample Capsule (OSC), keeping the OSC illuminated, making orbital adjustments, and physically capturing the OSC. Other applications could include autonomous science collection and fault compensation.
asteroid↗
Flying by Titan
The Cassini spacecraft encounters the massive Titan about once every month. These encounters are essential to the mission as Titan is the only satellite of Saturn that can provide enough gravity assist to shape the orbit tour and allow outstanding science for many years. From a navigation point of view, these encounters provide many challenges, in particular those that fly close enough to the surface for the atmospheric drag to perturb the orbit. This paper discusses the dynamics models developed to successfully navigate Cassini and determine its trajectory. This includes the moon's gravity pull with its second degree zonal harmonics J2, the attitude thrust control perturbations and the acceleration of drag.
Pelletier, Frederic J.↗
Navigational Use of Cassini Delta V Telemetry
Telemetry data are used to improve navigation of the Saturn orbiting Cassini spacecraft. Thrust induced delta V's are computed on-board the spacecraft, recorded in telemetry, and downlinked to Earth. This paper discusses how and why the Cassini Navigation team utilizes spacecraft delta V telemetry. Operational changes making this information attractive to the Navigation Team will be briefly discussed, as will spacecraft hardware and software algorithms responsible for the on-board computation. An analysis of past delta V telemetry, providing calibrations and accuracies that can be applied to the estimation of future delta V activity, is described.
Roth, Duane C.↗
Deep Impact Autonomous Navigation : the trials of targeting the unknown
On July 4, 2005 at 05:44:34.2 UTC the Impactor Spacecraft (s/c) impacted comet Tempel 1 with a relative speed of 10.3 km/s capturing high-resolution images of the surface of a cometary nucleus just seconds before impact. Meanwhile, the Flyby s/c captured the impact event using both the Medium Resolution Imager (MRI) and the High Resolution Imager (HRI) and tracked the nucleus for the entire 800 sec period between impact and shield attitude transition. The objective of the Impactor s/c was to impact in an illuminated area viewable from the Flyby s/c and capture high-resolution context images of the impact site. This was accomplished by using autonomous navigation (AutoNav) algorithms and precise attitude information from the attitude determination and control subsystem (ADCS). The Flyby s/c had two primary objectives: 1) capture the impact event with the highest temporal resolution possible in order to observe the ejecta plume expansion dynamics; and 2) track the impact site for at least 800 sec to observe the crater formation and capture the highest resolution images possible of the fully developed crater. These two objectives were met by estimating the Flyby s/c trajectory relative to Tempel 1 using the same AutoNav algorithms along with precise attitude information from ADCS and independently selecting the best impact site. This paper describes the AutoNav system, what happened during the encounter with Tempel 1 and what could have happened.
impactor spacecraft↗