SEARCH · Search NASA
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 Jet Propulsion Laboratory (JPL), a goal of providing easy and simple data access to the mission engineering data using web-based standards to a wide variety of users is now possible by the RAMPAGE development.
This paper describes analysis of the Space Shuttle Main Engine (SSME) sensor data using Beacon-based exception analysis for multimissions (BEAM), a new technology developed for sensor analysis and diagnostics in autonomous space systems by the Jet Propulsion Laboratory (JPL).
For many years the diverse scientific community that supports JPL's wide variety ofinterplanetary space missions has needed a tool in order to plan and develop their experiments. The tool needs to be easily adapted to various mission types and portable to the user community. The Science Opportunity Analyzer, SOA, now in its third year of development, is intended to meet this need. SOA is a java-based application that is designed to enable scientists to identify and analyze opportunities for science observations from spacecraft. It differs from other planning tools in that it does not require an in-depth knowledge of the spacecraft command system or operation modes to begin high level planning. Users can, however, develop increasingly detailed levels of design. SOA consists of six major functions: Opportunity Search, Visualization, Observation Design, Constraint Checking, Data Output and Communications. Opportunity Search is a GUI driven interface to existing search engines that can be used to identify times when a spacecraft is in a specific geometrical relationship with other bodies in the solar system. This function can be used for advanced mission planning as well as for making last minute adjustments to mission sequences in response to trajectory modifications. Visualization is a key aspect of SOA. The user can view observation opportunities in either a 3D representation or as a 2D map projection. The user is given extensive flexibility to customize what is displayed in the view. Observation Design allows the user to orient the spacecraft and visualize the projection of the instrument field of view for that orientation using the same views as Opportunity Search. Constraint Checking is provided to validate various geometrical and physical aspects of an observation design. The user has the ability to easily create custom rules or to use official project-generated flight rules. This capability may also allow scientists to easily impact the cost to science if flight rule changes occur. Data Output generates information based on the spacecraft's trajectory, opportunity search results or based on a created observation. The data can be viewed either in tabular format or as a graph. Finally, SOA is unique in that it is designed to be able to communicate with a variety of existing planning and sequencing tools. From the very beginning SOA was designed with the user in mind. Extensive surveys of the potential user community were conducted in order to develop the software requirements. Throughout the development period, close ties have been maintained with the science community to insure that the tool maintains its user focus. Although development is still in its early stages, SOA is already developing a user community on the Cassini project, which is depending on this tool for their science planning. There are other tools at JPL that do various pieces of what SOA can do; however, there is no other tool which combines all these functions and presents them to the user in such a convenient, cohesive, and easy to use fashion.
An advanced network interface was designed and implemented by a team from the Jet Propulsion Lab with support from the European Space Operations Center. This poster shows the requirements for the interface, the design, the topology, the testing and lessons learned from the whole implementation.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
The obvious advantages of small spacecraft - their lower cost structure and the rapid development schedule - have enabled a large number of missions in the past. However, most of these missions have been focused on Earth observation from low Earth orbits. In 2006, the Small Spacecraft Division at the NASA Ames Research Center began the development of the Modular Common Bus, a spacecraft capable of delivering scientifically and technically useful payloads to a variety of destinations within 0.1 AU around the Earth. The core technologies used in the Common Bus design are a composite structure with body-mounted solar cells, an integrated avionics unit, and a high performance bipropellant propulsion system. Due to its modular approach, the Common Bus can be adapted to fit specific mission needs while still using a standardized and qualified set of components. Additionally a number of low cost launch vehicles are supported, resulting in overall mission costs of around $150M including the launch vehicle but excluding the science payloads. This significant reduction in cost and the shorter development time would enable NASA to conduct more frequent exploration missions within its budget and timeframe constraints, compared to the status quo. In this paper the suitability of the Common Spacecraft Bus for four different exploration scenarios is analyzed. These scenarios include a lunar orbiter, a lunar lander, a mission to a Sun-Earth Libration Point, and a rendezvous mission to a Near Earth Object. For each scenario, a preliminary design reference mission is developed and key design parameters for the spacecraft are determined.
No abstract available
No abstract available
No abstract available
No abstract available
No abstract available
The majority of today's CubeSat fleet consists of Earth-orbiting missions that mostly use existing ground systems developed by universities because of availability, simplicity, and low-cost. The Interplanetary NanoSpacecraft Pathfinder In Relevant Environment (INSPIRE) mission is a revolutionary CubeSat mission that will launch a pair of CubeSats into deep space to study the feasibility of CubeSats beyond low-Earth orbit. This uncovers a new set of systems and software engineering challenges to the development of a robust and reliable ground system in a low-cost environment. In this paper, we discuss the approach to these challenges by using the Jet Propulsion Laboratory's (JPL) Advanced Multimission Operation System (AMMOS) Ground Data System (GDS) as well as the methodologies used to engineer the flight system to work with an existing ground system developed for large-scale missions. Specifically we will focus on the command and telemetry subsystem of AMMOS, the Multimission Data Processing and Control System. We conclude with a retrospective on the challenges encountered and a brief discussion on our efforts to provide AMMOS to support future deep space CubeSat missions.
No abstract available
Conveying spacecraft health and status information to mission engineering personnel during various mission phases, including mission operations, is a requirement to achieve a successful mission. For NASA/JPL spacecraft, that often means displaying hundreds of telemetry channels from a variety of sensors and components emitting data at rates varying from 1hz-100hz (and faster) in a way that allows the operations team to quickly evaluate the health of the vehicle, identify any off-nominal states and resolve any issues. In this paper we will discuss the system design, requirements and use cases of three telemetry processing and visualization systems recently developed and deployed by our team for NASA's Low Density Supersonic Decelerator (LDSD) test vehicle, NASA's Soil Moisture Active/Passive (SMAP) orbiter, and JPL's Sampling Lab Universal Robotic Manipulator (SLURM) test bed.