Search NASA⌕ Search

SEARCH · Search NASA

Results for “Jet Propulsion Laboratory (JPL)”

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 631 records · Page 35

Physics-Based Simulator for NEO Exploration Analysis & Simulation

As part of the Space Exploration Analysis and Simulation (SEAS) task, the National Aeronautics and Space Administration (NASA) is using physics-based simulations at NASA's Jet Propulsion Laboratory (JPL) to explore potential surface and near-surface mission operations at Near Earth Objects (NEOs). The simulator is under development at JPL and can be used to provide detailed analysis of various surface and near-surface NEO robotic and human exploration concepts. In this paper we describe the SEAS simulator and provide examples of recent mission systems and operations concepts investigated using the simulation. We also present related analysis work and tools developed for both the SEAS task as well as general modeling, analysis and simulation capabilites for asteroid/small-body objects.

Dshell↗

Stardust Blazes MOA Trail

Mission Operations Assurance (MOA) started at the Jet Propulsion Laboratory (JPL) with the Magellan and Galileo missions of the late 80's. It continued to develop and received a significant impetus with the failures of two successive missions to Mars in the late 90's. MOA continued to evolve with each successive project at JPL achieving its current maturity with the Stardust sample return to Earth.

operations assurance mission↗

Reconciling Scientific Aspirations and Engineering Constraints for a Lunar Mission via Hyperdimensional Interpolation

Virtually every NASA space-exploration mission represents a compromise between the interests of two expert, dedicated, but very different communities: scientists, who want to go quickly to the places that interest them most and spend as much time there as possible conducting sophisticated experiments, and the engineers and designers charged with maximizing the probability that a given mission will be successful and cost-effective. Recent work at NASA's Jet Propulsion Laboratory (JPL) seeks to enhance communication between these two groups, and to help them reconcile their interests, by developing advanced modeling capabilities with which they can analyze the achievement of science goals and objectives against engineering design and operational constraints. The analyses conducted prior to this study have been point-design driven. Each analysis has been of one hypothetical case which addresses the question: Given a set of constraints, how much science can be done? But the constraints imposed by the architecture team-e.g., rover speed, time allowed for extravehicular activity (EVA), number of sites at which science experiments are to be conducted- are all in early development and carry a great deal of uncertainty. Variations can be incorporated into the analysis, and indeed that has been done in sensitivity studies designed to see which constraint variations have the greatest impact on results. But if a very large number of variations can be analyzed all at once, producing a table that includes virtually the entire trade space under consideration, then we have a tool that enables scientists and mission architects to ask the inverse question: For a given desired level of science (or any other objective), what is the range of constraints that would be needed? With this tool, mission architects could determine, for example, what combinations of rover speed, EVA duration, and other constraints produce the desired results. Further, this tool would help them identify which technology-improvement investments would be likely to produce the largest or most important return. However, the number of variations that need to be considered for such analysis quickly balloons to an unwieldy size. If three variations are considered for each of six constraints-a very modest example-there are a total of 243 variations to consider. If it takes 40 minutes to compute each variation, as it does with HURON, our automated optimization system, then it would take 162 hours or nearly 7 days of round-the-clock computing to calculate the results. Adding further constraints or variations exponentially increases the amount of time that is needed.

Weisbin, Charles R.↗

The Deep Space Network Advanced Systems Program

The deep space network (DSN)--with its three complexes in Goldstone, California, Madrid, Spain, and Canberra, Australia--provides the resources to track and communicate with planetary and deep space missions. Each complex consists of an array of capabilities for tracking probes almost anywhere in the solar system. A number of innovative hardware, software and procedural tools are used for day-to-day operations at DSN complexes as well as at the network control at the Jet Propulsion Laboratory (JPL). Systems and technologies employed by the network include large-aperture antennas (34-m and 70-m), cryogenically cooled receivers, high-power transmitters, stable frequency and timing distribution assemblies, modulation and coding schemes, spacecraft transponders, radiometric tracking techniques, etc. The DSN operates at multiple frequencies, including the 2-GHz band, the 7/8-GHz band, and the 32/34-GHz band.

tracking↗

A Discussion of the Software Quality Assurance Role

The basic idea underlying this paper is that the conventional understanding of the role of a Software Quality Assurance (SQA) engineer is unduly limited. This is because few have asked who the customers of a SQA engineer are. Once you do this, you can better define what tasks a SQA engineer should perform, as well as identify the knowledge and skills that such a person should have. The consequence of doing this is that a SQA engineer can provide greater value to his or her customers. It is the position of this paper that a SQA engineer providing significant value to his or her customers must not only assume the role of an auditor, but also that of a software and systems engineer. This is because software engineers and their managers particularly value contributions that directly impact products and their development. These ideas are summarized as lessons learned, based on my experience at Jet Propulsion Laboratory (JPL).

experience↗

Challenges of Integrating NASAs Space Communication Networks

The transition to new technology, innovative ideas, and resistance to change is something that every industry experiences. Recent examples of this shift are changing to using robots in the assembly line construction of automobiles or the increasing use of robotics for medical procedures. Most often this is done with cost-reduction in mind, though ease of use for the customer is also a driver. All industries experience the push to increase efficiency of their systems; National Aeronautics and Space Administration (NASA) and the commercial space industry are no different. NASA space communication services are provided by three separately designed, developed, maintained, and operated communications networks known as the Deep Space Network (DSN), Near Earth Network (NEN) and Space Network (SN). The Space Communications and Navigation (SCaN) Program is pursuing integration of these networks and has performed a variety of architecture trade studies to determine what integration options would be the most effective in achieving a unified user mission support organization, and increase the use of common operational equipment and processes. The integration of multiple, legacy organizations and existing systems has challenges ranging from technical to cultural. The existing networks are the progeny of the very first communication and tracking capabilities implemented by NASA and the Jet Propulsion Laboratory (JPL) more than 50 years ago and have been customized to the needs of their respective user mission base. The technical challenges to integrating the networks are many, though not impossible to overcome. The three distinct networks provide the same types of services, with customizable data rates, bandwidth, frequencies, and so forth. The differences across the networks have occurred in effort to satisfy their user missions' needs. Each new requirement has made the networks more unique and harder to integrate. The cultural challenges, however, have proven to be a significant obstacle for integration. Over the past few decades of use, user missions and network personnel alike have grown accustomed to the processes by which services are provided by the NASA communications and navigation networks. The culture established by each network has created several challenges that need to be overcome in order to effectively integrate the networks. As with any change, there has been resistance, an apprehension to explore automation of existing processes, and a working environment that attempts to indirectly influence change without mandating compliance. Overcoming technical and cultural challenges is essential to successfully integrating the networks and although the challenges are numerous, the integration of the networks promises a more efficient space communications network for NASA and its customers, as well as potential long-term cost savings to the agency. This paper, Challenges of Integrating NASA Legacy Communications Networks, will provide a brief overview of the current NASA space communications networks as well as the an overview of the process implemented while performing the SCaN Trade Studies and an introduction to the requirements driving integration of the SCaN Networks. This paper will describe in detail the challenges experienced, both technical and cultural, while working with NASA space communications network-specific personnel. The paper will also cover lessons learned during the performance of architecture trade studies and provide recommendations for ways to improve the process.

Reinert, Jessica M.↗

Identification and Classification of Common Risks in Space Science Missions

Due to the highly constrained schedules and budgets that NASA missions must contend with, the identification and management of cost, schedule and risks in the earliest stages of the lifecycle is critical. At the Jet Propulsion Laboratory (JPL) it is the concurrent engineering teams that first address these items in a systematic manner. Foremost of these concurrent engineering teams is Team X. Started in 1995, Team X has carried out over 1000 studies, dramatically reducing the time and cost involved, and has been the model for other concurrent engineering teams both within NASA and throughout the larger aerospace community. The ability to do integrated risk identification and assessment was first introduced into Team X in 2001. Since that time the mission risks identified in each study have been kept in a database. In this paper we will describe how the Team X risk process is evolving highlighting the strengths and weaknesses of the different approaches. The paper will especially focus on the identification and classification of common risks that have arisen during Team X studies of space based science missions.

Risk Identification↗

Lighting Condition Analysis for Mars Moon Phobos

A manned mission to Phobos may be an important precursor and catalyst for the human exploration of Mars, as it will fully demonstrate the technologies for a successful Mars mission. A comprehensive understanding of Phobos' environment such as lighting condition and gravitational acceleration are essential to the mission success. The lighting condition is one of many critical factors for landing zone selection, vehicle power subsystem design, and surface mobility vehicle path planning. Due to the orbital characteristic of Phobos, the lighting condition will change dramatically from one Martian season to another. This study uses high fidelity computer simulation to investigate the lighting conditions, specifically the solar radiation flux over the surface, on Phobos. Ephemeris data from the Jet Propulsion Laboratory (JPL) DE405 model was used to model the state of the Sun, the Earth, and Mars. An occultation model was developed to simulate Phobos' self-shadowing and its solar eclipses by Mars. The propagated Phobos' state was compared with data from JPL's Horizon system to ensure the accuracy of the result. Results for Phobos lighting condition over one Martian year are presented in this paper, which include length of solar eclipse, average solar radiation intensity, surface exposure time, total maximum solar energy, and total surface solar energy (constrained by incident angle). The results show that Phobos' solar eclipse time changes throughout the Martian year with the maximum eclipse time occurring during the Martian spring and fall equinox and no solar eclipse during the Martian summer and winter solstice. Solar radiation intensity is close to minimum at the summer solstice and close to maximum at the winter solstice. Total surface exposure time is longer near the north pole and around the anti- Mars point. Total maximum solar energy is larger around the anti-Mars point. Total surface solar energy is higher around the anti-Mars point near the equator. The results from this study and others like it will be important in determining landing site selection, vehicle system design and mission operations for the human exploration of Phobos and subsequently Mars.

Li, Zu Qun↗

RAPID: Collaboration Results from Three NASA Centers in Commanding/Monitoring Lunar Assets

Three NASA centers are working together to address the challenge of operating robotic assets in support of human exploration of the Moon. This paper describes the combined work to date of the Ames Research Center (ARC), Jet Propulsion Laboratory (JPL) and Johnson Space Center (JSC) on a common support framework to control and monitor lunar robotic assets. We discuss how we have addressed specific challenges including time-delayed operations, and geographically distributed collaborative monitoring and control, to build an effective architecture for integrating a heterogeneous collection of robotic assets into a common work. We describe the design of the Robot Application Programming Interface Delegate (RAPID) architecture that effectively addresses the problem of interfacing a family of robots including the JSC Chariot, ARC K-10 and JPL ATHLETE rovers. We report on lessons learned from the June 2008 field test in which RAPID was used to monitor and control all of these assets. We conclude by discussing some future directions to extend the RAPID architecture to add further support for NASA's lunar exploration program.

Torres, R. Jay↗

Interfacing Space Communications and Navigation Network Simulation with Distributed System Integration Laboratories (DSIL)

NASA's planned Lunar missions will involve multiple NASA centers where each participating center has a specific role and specialization. In this vision, the Constellation program (CxP)'s Distributed System Integration Laboratories (DSIL) architecture consist of multiple System Integration Labs (SILs), with simulators, emulators, testlabs and control centers interacting with each other over a broadband network to perform test and verification for mission scenarios. To support the end-to-end simulation and emulation effort of NASA' exploration initiatives, different NASA centers are interconnected to participate in distributed simulations. Currently, DSIL has interconnections among the following NASA centers: Johnson Space Center (JSC), Kennedy Space Center (KSC), Marshall Space Flight Center (MSFC) and Jet Propulsion Laboratory (JPL). Through interconnections and interactions among different NASA centers, critical resources and data can be shared, while independent simulations can be performed simultaneously at different NASA locations, to effectively utilize the simulation and emulation capabilities at each center. Furthermore, the development of DSIL can maximally leverage the existing project simulation and testing plans. In this work, we describe the specific role and development activities at JPL for Space Communications and Navigation Network (SCaN) simulator using the Multi-mission Advanced Communications Hybrid Environment for Test and Evaluation (MACHETE) tool to simulate communications effects among mission assets. Using MACHETE, different space network configurations among spacecrafts and ground systems of various parameter sets can be simulated. Data that is necessary for tracking, navigation, and guidance of spacecrafts such as Crew Exploration Vehicle (CEV), Crew Launch Vehicle (CLV), and Lunar Relay Satellite (LRS) and orbit calculation data are disseminated to different NASA centers and updated periodically using the High Level Architecture (HLA). In addition, the performance of DSIL under different traffic loads with different mix of data and priorities are evaluated.

Traffic Measuring and Monitoring↗

Deep Impact Extended Mission Challenges for the Validation and Verification Test Program

The Deep Impact Spacecraft was launched on January 12, 2005 as part of NASA's Discovery Program as a radical mission to excavate the interior of a comet. The Spacecraft consisted of two separate entities known as the Flyby and the Impactor, which were commanded to separate prior to comet rendezvous with comet 9P/Tempel 1. The overall mission was deemed a success on July 4, 2005, as the 370-kg Impactor collided with the comet at 10.2 km/s. This event was captured using the camera and infrared spectrometer on the Flyby spacecraft, along with ground-based observatories. Since this event, the Flyby spacecraft has been in hibernation mode and has received only a small amount of maintenance. The Deep Impact Program was managed by the Jet Propulsion Laboratory (JPL), led by Dr. Michael A'Hearn from the University of Maryland in College Park, and built by Ball Aerospace & Technologies Corp. in Boulder, Colorado.

Test Bench↗

Integrated Performance of Next Generation High Data Rate Receiver and AR4JA LDPC Codec for Space Communications

Low-density parity-check (LDPC) codes are the state-of-the-art in forward error correction (FEC) technology that exhibits capacity approaching performance. The Jet Propulsion Laboratory (JPL) has designed a family of LDPC codes that are similar in structure and therefore, leads to a single decoder implementation. The Accumulate-Repeat-by-4-Jagged- Accumulate (AR4JA) code design offers a family of codes with rates 1/2, 2/3, 4/5 and lengths 1024, 4096, 16384 information bits. Performance is less than one dB from capacity for all combinations.Integrating a stand-alone LDPC decoder with a commercial-off-the-shelf (COTS) receiver faces additional challenges than building a single receiver-decoder unit from scratch. In this work, we outline the issues and show that these additional challenges can be over-come by simple solutions. To demonstrate that an LDPC decoder can be made to work seamlessly with a COTS receiver, we interface an AR4JA LDPC decoder developed on a field-programmable gate array (FPGA) with a modern high data rate receiver and mea- sure the combined receiver-decoder performance. Through optimizations that include an improved frame synchronizer and different soft-symbol scaling algorithms, we show that a combined implementation loss of less than one dB is possible and therefore, most of the coding gain evidence in theory can also be obtained in practice. Our techniques can benefit any modem that utilizes an advanced FEC code.

Cheng, Michael K.↗

Delivery of Colloid Micro-Newton Thrusters for the Space Technology 7 Mission

Two flight-qualified clusters of four Colloid Micro-Newton Thruster (CMNT) systems have been delivered to the Jet Propulsion Laboratory (JPL). The clusters will provide precise spacecraft control for the drag-free technology demonstration mission, Space Technology 7 (ST7). The ST7 mission is sponsored by the NASA New Millennium Program and will demonstrate precision formation flying technologies for future missions such as the Laser Interferometer Space Antenna (LISA) mission. The ST7 disturbance reduction system (DRS) will be on the ESA LISA Pathfinder spacecraft using the European gravitational reference sensor (GRS) as part of the ESA LISA Technology Package (LTP). Developed by Busek Co. Inc., with support from JPL in design and testing, the CMNT has been developed over the last six years into a flight-ready and flight-qualified microthruster system, the first of its kind. Recent flight-unit qualification tests have included vibration and thermal vacuum environmental testing, as well as performance verification and acceptance tests. All tests have been completed successfully prior to delivery to JPL. Delivery of the first flight unit occurred in February of 2008 with the second unit following in May of 2008. Since arrival at JPL, the units have successfully passed through mass distribution, magnetic, and EMI/EMC measurements and tests as part of the integration and test (I&T) activities including the integrated avionics unit (IAU). Flight software sequences have been tested and validated with the full flight DRS instrument successfully to the extent possible in ground testing, including full functional and 72 hour autonomous operations tests. Delivery of the cluster assemblies along with the IAU to ESA for integration into the LISA Pathfinder spacecraft is planned for the summer of 2008 with a planned launch and flight demonstration in late 2010.

Precision Formation Flying↗

Lighting Condition Analysis for Mars' Moon Phobos

This study used high fidelity computer simulation to investigate the lighting conditions, specifically the solar radiation flux over the surface, on Phobos. Ephemeris data from the Jet Propulsion Laboratory (JPL) DE405 model was used to model the state of the Sun, Earth, Moon, and Mars. An occultation model was developed to simulate Phobos' self-shadowing and its solar eclipses by Mars. The propagated Phobos state was compared with data from JPL's Horizon system to ensure the accuracy of the result. Results for Phobos lighting conditions over one Martian year are presented, which include the duration of solar eclipses, average solar radiation intensity, surface exposure time, available energy per unit area for sun tracking arrays, and available energy per unit area for fixed arrays (constrained by incident angle). The results show that: Phobos' solar eclipse time varies throughout the Martian year, with longer eclipse durations during the Martian spring and fall seasons and no eclipses during the Martian summer and winter seasons; solar radiation intensity is close to minimum at the summer solstice and close to maximum at the winter solstice; exposure time per orbit is relatively constant over the surface during the spring and fall but varies with latitude during the summer and winter; and Sun tracking solar arrays generate more energy than a fixed solar array. A usage example of the result is also present in this paper to demonstrate the utility.

Li, Zu Qun↗

Benefits of Spacecraft Level Vibration Testing

NASA-HDBK-7008 Spacecraft Level Dynamic Environments Testing discusses the approaches, benefits, dangers, and recommended practices for spacecraft level dynamic environments testing, including vibration testing. This paper discusses in additional detail the benefits and actual experiences of vibration testing spacecraft for NASA Goddard Space Flight Center (GSFC) and Jet Propulsion Laboratory (JPL) flight projects. JPL and GSFC have both similarities and differences in their spacecraft level vibration test approach: JPL uses a random vibration input and a frequency range usually starting at 5 Hz and extending to as high as 250 Hz. GSFC uses a sine sweep vibration input and a frequency range usually starting at 5 Hz and extending only to the limits of the coupled loads analysis (typically 50 to 60 Hz). However, both JPL and GSFC use force limiting to realistically notch spacecraft resonances and response (acceleration) limiting as necessary to protect spacecraft structure and hardware from exceeding design strength capabilities. Despite GSFC and JPL differences in spacecraft level vibration test approaches, both have uncovered a significant number of spacecraft design and workmanship anomalies in vibration tests. This paper will give an overview of JPL and GSFC spacecraft vibration testing approaches and provide a detailed description of spacecraft anomalies revealed.

Spacecraft Vibration Test↗

Challenges of Integrating NASA's Space Communications Networks

The transition to new technology, innovative ideas, and resistance to change is something that every industry experiences. Recent examples of this shift are changing to using robots in the assembly line construction of automobiles or the increasing use of robotics for medical procedures. Most often this is done with cost-reduction in mind, though ease of use for the customer is also a driver. All industries experience the push to increase efficiency of their systems; National Aeronautics and Space Administration (NASA) and the commercial space industry are no different. NASA space communication services are provided by three separately designed, developed, maintained, and operated communications networks known as the Deep Space Network (DSN), Near Earth Network (NEN) and Space Network (SN). The Space Communications and Navigation (SCaN) Program is pursuing integration of these networks and has performed a variety of architecture trade studies to determine what integration options would be the most effective in achieving a unified user mission support organization, and increase the use of common operational equipment and processes. The integration of multiple, legacy organizations and existing systems has challenges ranging from technical to cultural. The existing networks are the progeny of the very first communication and tracking capabilities implemented by NASA and the Jet Propulsion Laboratory (JPL) more than 50 years ago and have been customized to the needs of their respective user mission base. The technical challenges to integrating the networks are many, though not impossible to overcome. The three distinct networks provide the same types of services, with customizable data rates, bandwidth, frequencies, and so forth. The differences across the networks have occurred in effort to satisfy their user missions' needs. Each new requirement has made the networks more unique and harder to integrate. The cultural challenges, however, have proven to be a significant obstacle for integration. Over the past few decades of use, user missions and network personnel alike have grown accustomed to the processes by which services are provided by the NASA communications and navigation networks. The culture established by each network has created several challenges that need to be overcome in order to effectively integrate the networks. As with any change, there has been resistance, an apprehension to explore automation of existing processes, and a working environment that attempts to indirectly influence change without mandating compliance. Overcoming technical and cultural challenges is essential to successfully integrating the networks and although the challenges are numerous, the integration of the networks promises a more efficient space communications network for NASA and its customers, as well as potential long-term cost savings to the agency. This paper, Challenges of Integrating NASA Legacy Communications Networks, will provide a brief overview of the current NASA space communications networks as well as the an overview of the process implemented while performing the SCaN Trade Studies and an introduction to the requirements driving integration of the SCaN Networks. This paper will describe in detail the challenges experienced, both technical and cultural, while working with NASA space communications network-specific personnel. The paper will also cover lessons learned during the performance of architecture trade studies and provide recommendations for ways to improve the process.

Systems Integration↗

Force Limited Random Vibration Test of TESS Camera Mass Model

The Transiting Exoplanet Survey Satellite (TESS) is a spaceborne instrument consisting of four wide field-of-view-CCD cameras dedicated to the discovery of exoplanets around the brightest stars. As part of the environmental testing campaign, force limiting was used to simulate a realistic random vibration launch environment. While the force limit vibration test method is a standard approach used at multiple institutions including Jet Propulsion Laboratory (JPL), NASA Goddard Space Flight Center (GSFC), European Space Research and Technology Center (ESTEC), and Japan Aerospace Exploration Agency (JAXA), it is still difficult to find an actual implementation process in the literature. This paper describes the step-by-step process on how the force limit method was developed and applied on the TESS camera mass model. The process description includes the design of special fixtures to mount the test article for properly installing force transducers, development of the force spectral density using the semi-empirical method, estimation of the fuzzy factor (C2) based on the mass ratio between the supporting structure and the test article, subsequent validating of the C2 factor during the vibration test, and calculation of the C.G. accelerations using the Root Mean Square (RMS) reaction force in the spectral domain and the peak reaction force in the time domain.

Karlicek, Alexandra↗

Lighting Condition Analysis for Mars' Moon Phobos

This study used high fidelity computer simulation to investigate the lighting conditions, specifically the solar radiation flux over the surface, on Phobos. Ephemeris data from the Jet Propulsion Laboratory (JPL) DE405 model was used to model the state of the Sun, Earth, Moon, and Mars. An occultation model was developed to simulate Phobos' self-shadowing and its solar eclipses by Mars. The propagated Phobos state was compared with data from JPL's Horizon system to ensure the accuracy of the result. Results for Phobos lighting conditions over one Martian year are presented, which include the duration of solar eclipses, average solar radiation intensity, surface exposure time, and radiant exposure for both sun tracking and fixed solar arrays. The results show that: Phobos' solar eclipse time varies throughout the Martian year, with longer eclipse durations during the Martian northern spring and fall seasons and no eclipses during the Martian northern summer and winter seasons; solar radiation intensity is close to minimum in late spring and close to maximum in late fall; exposure time per orbit is relatively constant over the surface during the spring and fall but varies with latitude during the summer and winter; and Sun tracking solar arrays generate more energy than a fixed solar array. A usage example of the result is also present in this paper to demonstrate the utility.

Li, Zu Qun↗