Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Deep Space Network”

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 1,747 records · Page 97

The U.S. Rosetta Project: Preparations for Prime Mission, 2014

In 2014, the International Rosetta mission will place a spacecraft in orbit around comet 67P/Churyumov-Gerasimenko and deliver a lander to the comet's surface. The National Aeronautics and Space Administration's (NASA) contribution to the International Rosetta mission, designated the U.S. Rosetta Project, includes several instruments, tracking support, and science support for some non-US payloads. In July 2011 the spacecraft was placed in a long-duration hibernation mode planned to last approximately 37 months to conserve electrical power. Rosetta will rendezvous with 67P/Churyumov-Gerasimenko in 2014. On the eve of the mission's arrival at its target, this paper highlights three issues related to Rosetta's looming prime mission: (A) measures taken in 2009 to prepare the US Rosetta Project for the long-duration hibernation mode; (B) risk reviews conducted in 2013 to prepare the US Rosetta Project for exit from hibernation; (C) ESA and NASA preparations for use of NASA Deep Space Network (DSN) assets related to keyword files.

hibernation↗

Use of Business Intelligence Tools in the DSN

JPL has operated the Deep Space Network (DSN) on behalf of NASA since the 1960's. Over the last two decades, the DSN budget has generally declined in real-year dollars while the aging assets required more attention, and the missions became more complex. As a result, the DSN budget has been increasingly consumed by Operations and Maintenance (O&M), significantly reducing the funding wedge available for technology investment and for enhancing the DSN capability and capacity. Responding to this budget squeeze, the DSN launched an effort to improve the cost-efficiency of the O&M. In this paper we: elaborate on the methodology adopted to understand "where the time and money are used"-surprisingly, most of the data required for metrics development was readily available in existing databases-we have used commercial Business Intelligence (BI) tools to mine the databases and automatically extract the metrics (including trends) and distribute them weekly to interested parties; describe the DSN-specific effort to convert the intuitive understanding of "where the time is spent" into meaningful and actionable metrics that quantify use of resources, highlight candidate areas of improvement, and establish trends; and discuss the use of the BI-derived metrics-one of the most fascinating processes was the dramatic improvement in some areas of operations when the metrics were shared with the operators-the visibility of the metrics, and a self-induced competition, caused almost immediate improvement in some areas. While the near-term use of the metrics is to quantify the processes and track the improvement, these techniques will be just as useful in monitoring the process, e.g. as an input to a lean-six-sigma process.

Metrics↗

Cassini Information Management System in Distributed Operations Collaboration and Cassini Science Planning

Launched on October 15, 1997, the Cassini-Huygens spacecraft began its ambitious journey to the Saturnian system with a complex suite of 12 scientific instruments, and another 6 instruments aboard the European Space Agencies Huygens Probe. Over the next 6 1/2 years, Cassini would continue its relatively simplistic cruise phase operations, flying past Venus, Earth, and Jupiter. However, following Saturn Orbit Insertion (SOI), Cassini would become involved in a complex series of tasks that required detailed resource management, distributed operations collaboration, and a data base for capturing science objectives. Collectively, these needs were met through a web-based software tool designed to help with the Cassini uplink process and ultimately used to generate more robust sequences for spacecraft operations. In 2001, in conjunction with the Southwest Research Institute (SwRI) and later Venustar Software and Engineering Inc., the Cassini Information Management System (CIMS) was released which enabled the Cassini spacecraft and science planning teams to perform complex information management and team collaboration between scientists and engineers in 17 countries. Originally tailored to help manage the science planning uplink process, CIMS has been actively evolving since its inception to meet the changing and growing needs of the Cassini uplink team and effectively reduce mission risk through a series of resource management validation algorithms. These algorithms have been implemented in the web-based software tool to identify potential sequence conflicts early in the science planning process. CIMS mitigates these sequence conflicts through identification of timing incongruities, pointing inconsistencies, flight rule violations, data volume issues, and by assisting in Deep Space Network (DSN) coverage analysis. In preparation for extended mission operations, CIMS has also evolved further to assist in the planning and coordination of the dual playback redundancy of highvalue data from targets such as Titan and Enceladus. This paper will outline the critical role that CIMS has played for Cassini in the distributed ops paradigm throughout operations. This paper will also examine the evolution that CIMS has undergone in the face of new science discoveries and fluctuating operational needs. And finally, this paper will conclude with theoretical adaptation of CIMS for other projects and the potential savings in cost and risk reduction that could potentially be tapped into by future missions.

Equils, Douglas J.↗

Orbit Determination Processes for the Navigation of the Cassini-Huygens Mission

Deep space navigation, particularly the Orbit Determination (OD) operations of Cassini at Saturn, cannot easily be automated due to the complex dynamical environment in which the spacecraft flies; however several sub-processes are automated. The Cassini OD operations are often faced with unique challenges that require more than routine procedures. The OD Team is staffed appropriately to meet the demanding schedules and allow some level of flexibility. This paper will discuss how the OD processes are developed and the seven-member OD team is scheduled to support efficient and accurate Cassini navigation operations. Also discussed will be the requirements of the radio-metric Doppler and range tracking data acquired via the Deep Space Network and the optical navigation images of the satellites to support the daily OD operations. Furthermore, the reliability of the OD solutions, which is ensured within the framework of the OD processes, will be explained.

Antreasian, P.G.↗

The NASA Phoenix 2007 Mars Lander Thruster Calibration Estimator: Design and Validation

The NASA Phoenix 2007 Mars Lander mission, launched in August 2007 on its mission to land near the north pole of Mars in May 2008, had a driving need for entry-corridor delivery precision, which parlayed into stringent requirements on deep space navigation accuracy. This, in turn, necessitated in-cruise calibration of the three-axis thrust force vectors produced by each of the vehicle's four reactioncontrol system (RCS) thrusters during frequent daily low-catalyst-bed-temperature firings done to maintain the 3-axis attitude deadbands. A novel recursive sigmapoint consider-covariance filter was designed, validated and ultimately utilized extensively during flight operations, to estimate the RCS force vectors, per individual thruster. The estimate was achieved through ground-based processing of Deep Space Network (DSN) and telemetered gyroscope data from the spacecraft's inertial measurement unit (IMU), using a novel sigma-point consider filter (SPCF) formulation. During early-cruise active calibration, the spacecraft was flown in attitudes chosen, using this filter, to maximize observability of all thruster axes, to an extent constrained by vehicle thermal and communication considerations. The design of the Phoenix thruster calibration filter, and its validation through processing of archived Mars Odyssey thruster calibration radiometric data, and simulated sets of data, are discussed in this paper. The paper concludes with the formulation of the thruster calibration campaign and a summary of the thruster calibration campaign results. The SPCF algorithm is summarized in the Appendix.

sigma-point filter↗

Mars Exploration Rover Spirit End of Mission Report

The Mars Exploration Rover (MER) Spirit landed in Gusev crater on Mars on January 4, 2004, for a prime mission designed to last three months (90 sols). After more than six years operating on the surface of Mars, the last communication received from Spirit occurred on Sol 2210 (March 22, 2010). Following the loss of signal, the Mars Exploration Rover Project radiated over 1400 commands to Mars in an attempt to elicit a response from the rover. Attempts were made utilizing Deep Space Network X-Band and UHF relay via both Mars Odyssey and the Mars Reconnaissance Orbiter. Search and recovery efforts concluded on July 13, 2011. It is the MER project's assessment that Spirit succumbed to the extreme environmental conditions experienced during its fourth winter on Mars. Focusing on the time period from the end of the third Martian winter through the fourth winter and end of recovery activities, this report describes possible explanations for the loss of the vehicle and the extent of recovery efforts that were performed. It offers lessons learned and provides an overall mission summary.

Callas, John L.↗

Communications During Critical Mission Operations: Preparing for InSight's Landing on Mars

Radio communications with deep space missions are often taken for granted due to the impressively successful records since, for decades, the technology and infrastructure have been developed for ground and flight systems to optimize telemetry and commanding. During mission-critical events such as the entry, descent, and landing of a spacecraft on the surface of Mars, the signal's level and frequency dynamics vary significantly and typically exceed the threshold of the budgeted links. The challenge is increased when spacecraft shed antennas with heat shields and other hardware during those risky few minutes. We have in the past successfully received signals on Earth during critical events even ones not intended for ground reception. These included the UHF signal transmitted by Curiosity to Marsorbiting assets. Since NASA's Deep Space Network does not operate in the UHF band, large radio telescopes around the world are utilized. The Australian CSIRO Parkes Radio Telescope supported the Curiosity UHF signal reception and DSN receivers, tools, and expertise were used in the process. In preparation for the InSight mission's landing on Mars in 2016, preparations are underway to support the UHF communications. This paper presents communication scenarios with radio telescopes, and the DSN receiver and tools. It also discusses the usefulness of the real-time information content for better response time by the mission team towards successful mission operations.

Radio Science↗

The Gravity Field of Mercury After the Messenger Low-Altitude Campaign

The final year of the MESSENGER mission was designed to take advantage of the remaining propellant onboard to provide a series of lowaltitude observation campaigns and acquire novel scientific data about the innermost planet. The lower periapsis altitude greatly enhances the sensitivity to the short-wavelength gravity field, but only when the spacecraft is in view of Earth. After more than 3 years in orbit around Mercury, the MESSENGER spacecraft was tracked for the first time below 200-km altitude on 5 May 2014 by the NASA Deep Space Network (DSN). Between August and October, periapsis passages down to 25-km altitude were routinely tracked. These periods considerably improved the quality of the data coverage. Before the end of its mission, MESSENGER will fly at very low altitudes for extended periods of time. Given the orbital geometry, however the periapses will not be visible from Earth and so no new tracking data will be available for altitudes lower than ~75 km. Nevertheless, the continuous tracking of MESSENGER in the northern hemisphere will help improve the uniformity of the spatial coverage at altitudes lower than ~150 km, which will further improve the overall quality of the Mercury gravity field.

Mercury↗

Global and Local Gravity Field Models of the Moon Using GRAIL Primary and Extended Mission Data

The Gravity Recovery and Interior Laboratory (GRAIL) mission was designed to map the structure of the lunar interior from crust to core and to advance the understanding of the Moon's thermal evolution by producing a high-quality, high-resolution map of the gravitational field of the Moon. The mission consisted of two spacecraft, which were launched in September 2011 on a Discovery-class NASA mission. Ka-band tracking between the two satellites was the single science instrument, augmented by tracking from Earth using the Deep Space Network (DSN).

Moon↗

Utilization of the Deep Space Atomic Clock for Europa Gravitational Tide Recovery

Estimation of Europa's gravitational tide can provide strong evidence of the existence of a subsurface liquid ocean. Due to limited close approach tracking data, a Europa flyby mission suffers strong coupling between the gravity solution quality and tracking data quantity and quality. This work explores utilizing Low Gain Antennas with the Deep Space Atomic Clock (DSAC) to provide abundant high accuracy uplink-only radiometric tracking data. DSAC's performance, expected to exhibit an Allan Deviation of less than 3e-15 at one day, provides long-term stability and accuracy on par with the Deep Space Network ground clocks, enabling one-way radiometric tracking data with accuracy equivalent to that of its two-way counterpart. The feasibility of uplink-only Doppler tracking via the coupling of LGAs and DSAC and the expected Doppler data quality are presented. Violations of the Kalman filter's linearization assumptions when state perturbations are included in the flyby analysis results in poor determination of the Europa gravitational tide parameters. B-plane targeting constraints are statistically determined, and a solution to the linearization issues via pre-flyby approach orbit determination is proposed and demonstrated.

Seubert, Jill↗

Thomas Leps Internship Abstract

An optical navigation system is being flown as the backup system to the primary Deep Space Network telemetry for navigation and guidance purposes on Orion. This is required to ensure Orion can recover from a loss of communication, which would simultaneously cause a loss of DSN telemetry. Images taken of the Moon and Earth are used to give range and position information to the navigation computer for trajectory calculations and maneuver execution. To get telemetry data from these images, the size and location of the moon need to be calculated with high accuracy and precision. The reentry envelope for the Orion EM-1 mission requires the centroid and radius of the moon images to be determined within 1/3 of a pixel 3 sigma. In order to ensure this accuracy and precision can be attained, I was tasked with building precise dot grid images for camera calibration as well as building a hardware in the loop test stand for flight software and hardware proofing. To calibrate the Op-Nav camera a dot grid is imaged with the camera, the error between the image dot location and the actual dot location can be used to build a distortion map of the camera and lens system so that images can be fixed to display truth locations. To build the dot grid images I used the Electro Optics Lab optical bench Bright Object Simulator System, and gimbal. The gimbal was slewed to a series of elevations and azimuths. An image of the collimated single point light source was then taken at each position. After a series of 99 images were taken at different locations the single light spots were extracted from each image and added to a composite image containing all 99 points. During the development of these grids it was noticed that an intermittent error in the artificial "star" locations occurred. Prior to the summer this error was attributed to the gimbal having glitches in it's pointing direction and was going to be replaced, however after further examining the issue I determined it to be a software issue. I have since narrowed the likely source of the error down to a Software Development Kit released by the camera supplier PixeLink. I have since developed a workaround in order to build star grids for calibration until the software bug can be isolated and fixed. I was also tasked with building a Hardware in the Loop test stand in order to test the full Op-Nav system. A 4k screen displays simulated Lunar and Terrestrial images from a possible Orion trajectory. These images are then projected through a collimator and then captured with an Op-Nav camera controlled by an Intel NUC computer running flight software. The flight software then analyzes the images to determine attitude and position, this data is then reconstructed into a trajectory and matched to the simulated trajectory in order to determine the accuracy of the attitude and position estimates. In order for the system to work it needs to be precisely and accurately aligned. I developed an alignment procedure that allows the screen, collimator and camera to be squared, centered and collinear with each other within a micron spatially and 5 arcseconds in rotation. I also designed a rigid mount for the screen that was machined on site in Building 10 by another intern. While I was working in the EOL we received a $500k Orion startracker for alignment procedure testing. Due to my prior experience in electronics development, as an ancillary duty, I was tasked with building the cables required to operate and power the startracker. If any errors are made building these cables the startracker would be destroyed, I was honored that the director of the lab entrusted such a critical component with me. This internship has cemented my view on public space exploration. I always preferred public sector to privatization because, as a scientist, the most interesting aspects of space for me are not necessarily the most profitable. I was concerned that the public sector was faltering however, and that in order to improve human space exploration I would be forced into private sector. I now know that, at least at JSC, human spaceflight is still progressing, and exciting work is still being done. I am now actively seeking employment at JSC after I complete my Ph.D and have met with my branch chiefs and mentor to discuss transitioning to a grad Co-op position.

Leps, Thomas↗

Seasonal and static Gravity Field of Mars from MGS, Mars Odyssey and MRO Radio Science

We present a spherical harmonic solution of the static gravity field of Mars to degree and order 120, GMM-3, that has been calculated using the Deep Space Network tracking data of the NASA Mars missions, Mars Global Surveyor (MGS), Mars Odyssey (ODY), and the Mars Reconnaissance Orbiter (MRO). We have also jointly determined spherical harmonic solutions for the static and time-variable gravity field of Mars, and the Mars k(sub 2) Love numbers, exclusive of the gravity contribution of the atmosphere. Consequently, the retrieved time-varying gravity coefficients and the Love number k(sub 2) solely yield seasonal variations in the mass of the polar caps and the solid tides of Mars, respectively. We obtain a Mars Love number k(sub 2) of 0.1697 +/- 0.0027 (3- sigma). The inclusion of MRO tracking data results in improved seasonal gravity field coefficients C(sub 30) and, for the first time, C 50. Refinements of the atmospheric model in our orbit determination program have allowed us to monitor the odd zonal harmonic C(sub 30) for approximately 1.5 solar cycles (16 years). This gravity model shows improved correlations with MOLA topography up to 15% larger at higher harmonics ( l = 60-80) than previous solutions.

Genova, Antonio↗

An Updated Process for Automated Deepspace Conjunction Assessment

There is currently a high level of interest in the areas of conjunction assessment and collision avoidance from organizations conducting space operations. Current conjunction assessment activity is mainly focused on spacecraft and debris in the Earth orbital environment [1]. However, collisions are possible in other orbital environments as well [2]. This paper will focus on the current operations of and recent updates to the Multimission Automated Deep Space Conjunction Assessment Process (MADCAP) used at the Jet Propulsion Laboratory for NASA to perform conjunction assessment at Mars and the Moon. Various space agencies have satellites in orbit at Mars and the Moon with additional future missions planned. The consequences of collisions are catastrophically high. Intuitive notions predict low probability of collisions in these sparsely populated environments, but may be inaccurate due to several factors. Orbits of scientific interest often tend to have similar characteristics as do the orbits of spacecraft that provide a communications relay for surface missions. The MADCAP process is controlled by an automated scheduler which initializes analysis based on a set timetable or the appearance of new ephemeris files either locally or on the Deep Space Network (DSN) Portal. The process then generates and communicates reports which are used to facilitate collision avoidance decisions. The paper also describes the operational experience and utilization of the automated tool during periods of high activity and interest such as: the close approaches of NASA's Lunar Atmosphere & Dust Environment Explorer (LADEE) and Lunar Reconnaissance Orbiter (LRO) during the LADEE mission. In addition, special consideration was required for the treatment of missions with rapidly varying orbits and less reliable long term downtrack estimates; in particular this was necessitated by perturbations to MAVEN's orbit induced by the Martian atmosphere. The application of special techniques to non-operational spacecraft with large uncertainties is also studied. Areas for future work are also described. Although the applications discussed in this paper are in the Martian and Lunar environments, the techniques are not unique to these bodies and could be applied to other orbital environments.

collision↗

On the Performance of Adaptive Data Rate over Deep Space Ka-Bank Link: Case Study Using Kepler Data

Future missions envisioned for both human and robotic exploration demand increasing communication capacity through the use of Ka-band communications. The Ka-band channel, being more sensitive to weather impairments, presents a unique trade-offs between data storage, latency, data volume and reliability. While there are many possible techniques for optimizing Ka-band operations such as adaptive modulation and coding and site-diversity, this study focus exclusively on the use of adaptive data rate (ADR) to achieve significant improvement in the data volume-availability tradeoff over a wide range of link distances for near Earth and Mars exploration. Four years of Kepler Ka-band downlink symbol signal-to-noise (SNR) data reported by the Deep Space Network were utilized to characterize the Ka-band channel statistics at each site and conduct various what-if performance analysis for different link distances. We model a notional closed-loop adaptive data rate system in which an algorithm predicts the channel condition two-way light time (TWLT) into the future using symbol SNR reported in near-real time by the ground receiver and determines the best data rate to use. Fixed and adaptive margins were used to mitigate errors in channel prediction. The performance of this closed-loop adaptive data rate approach is quantified in terms of data volume and availability and compared to the actual mission configuration and a hypothetical, optimized single rate configuration assuming full a priori channel knowledge.

Gao, Jay L.↗

Navigation Strategies for Primitive Solar System Body Rendezvous and Proximity Operations

A wealth of scientific knowledge regarding the composition and evolution of the solar system can be gained through reconnaissance missions to primitive solar system bodies. This paper presents analysis of a baseline navigation strategy designed to address the unique challenges of primitive body navigation. Linear covariance and Monte Carlo error analysis was performed on a baseline navigation strategy using simulated data from a· design reference mission (DRM). The objective of the DRM is to approach, rendezvous, and maintain a stable orbit about the near-Earth asteroid 4660 Nereus. The outlined navigation strategy and resulting analyses, however, are not necessarily limited to this specific target asteroid as they may he applicable to a diverse range of mission scenarios. The baseline navigation strategy included simulated data from Deep Space Network (DSN) radiometric tracking and optical image processing (OpNav). Results from the linear covariance and Monte Carlo analyses suggest the DRM navigation strategy is sufficient to approach and perform proximity operations in the vicinity of the target asteroid with meter-level accuracy.

Getzandanner, Kenneth M.↗

Advanced Navigation Strategies For Asteroid Sample Return Missions

Flyby and rendezvous missions to asteroids have been accomplished using navigation techniques derived from experience gained in planetary exploration. This paper presents analysis of advanced navigation techniques required to meet unique challenges for precision navigation to acquire a sample from an asteroid and return it to Earth. These techniques rely on tracking data types such as spacecraft-based laser ranging and optical landmark tracking in addition to the traditional Earth-based Deep Space Network radio metric tracking. A systematic study of navigation strategy, including the navigation event timeline and reduction in spacecraft-asteroid relative errors, has been performed using simulation and covariance analysis on a representative mission.

Getzandanner, K.↗

Trajectory Design Considerations for Exploration Mission 1

Exploration Mission 1 (EM-1) will be the first mission to send an uncrewed Orion Multi-Purpose Crew Vehicle (MPCV) to cislunar space in the fall of 2019. EM-1 was originally conceived as a lunar free-return mission, but was later changed to a Distant Retrograde Orbit (DRO) mission as a precursor to the Asteroid Redirect Mission. To understand the required mission performance (i.e., propellant requirement), a series of trajectory optimization runs was conducted using JSC's Copernicus spacecraft trajectory optimization tool. In order for the runs to be done in a timely manner, it was necessary to employ a parallelization approach on a computing cluster using a new trajectory scan tool written in Python. Details of the scan tool are provided and how it is used to perform the scans and post-process the results. Initially, a scan of daily due east launched EM-1 DRO missions in 2018 was made. Valid mission opportunities are ones that do not exceed the useable propellant available to perform the required burns. The initial scan data showed the propellant and delta-V performance patterns for each launch period. As questions were raised from different subsystems (e.g., power, thermal, communications, flight operations, etc.), the mission parameters or data that were of interest to them were added to the scan output data file. The additional data includes: (1) local launch and landing times in relation to sunrise and sunset, (2) length of eclipse periods during the in-space portion of the mission, (3) Earth line of sight from cislunar space, (4) Deep Space Network field of view looking towards cislunar space, and (5) variation of the downrange distance from Earth entry interface to splashdown. Mission design trades can also be performed based on the information that the additional data shows. For example, if the landing is in darkness, but the recovery operations team desires a landing in daylight, then an analysis is performed to determine how to change the mission design to meet this request. Also, subsystems request feasibility of alternate or contingency mission designs, such as adding an Orion main engine checkout burn or Orion completing all of its burns using only its auxiliary thrusters. This paper examines and presents the evolving trade studies that incorporate subsystem feedback and demonstrate the feasibility of these constrained mission trajectory designs and contingencies.

Dawn, Timothy F.↗