Search NASA⌕ Search

SEARCH · Search NASA

Results for “Cassini Project”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1985

Project Cassini - A potential collaborative ESA/NASA Saturn Orbiter and Titan Probe mission

Project Cassini is concerned with a potential collaborative mission to Saturn and Titan. The project has been the subject of a joint ESA/NASA Technical Assessment Study from April 1984 to July 1985. The spacecraft consists of a Saturn Orbiter and a Titan entry Probe. Science objectives with respect to Titan include a determination of the abundances of atmospheric constituents and isotope ratios, a study of the distribution of trace gases, cloud physics, and a determination of the state of the surface. Other science objectives are related to Saturn, the rings, icy satellites, the magnetosphere of Saturn, and asteroids. Attention is given to mission design, the spacecraft, and future prospects.

Beckman, J.↗
NASA NTRS2008

Communicating Navigation Data Inside the Cassini-Huygens Project: Visualizations and Tools

The Cassini-Huygens Saturn tour poses an interesting navigation challenge. From July 2004 through June 2008, the Cassini orbiter performed 112 of 161 planned maneuvers. This demanding schedule, where maneuvers are often separated by just a few days, motivated the development of maneuver design/analysis automation software tools. Besides generating maneuver designs and presentations, these tools are the mechanism to producing other types of navigation information; information used to facilitate operational decisions on such issues as maneuver cancellation and alternate maneuver strategies. This paper will discuss the navigation data that are communicated inside the Cassini-Huygens Project, as well as the maneuver software tools behind the processing of the data.

maneuver↗
NASA NTRS1993

Distributed science operations for JPL planetary missions

Advances in spacecraft, flight instruments, and ground systems provide an impetus and an opportunity for scientific investigation teams to take direct control of their instruments' operations and data collection while at the same time, providing a cost effective and flexible approach in support of increasingly complex science missions. Operations of science instruments have generally been integrated into planetary flight and ground systems at a very detailed level. That approach has been successful, but the cost of incorporating instrument expertise into the central mission operations system has been high. This paper discusses an approach to simplify planetary science operations by distributing instrument computing and data management tasks from the central mission operations system to each investigator's home center of observational expertise. Some early results of this operations concept will be presented based on the Mars Observer (MO) Project experience and Cassini Project plans.

Benson, Richard D.↗
NASA NTRS2016

The Last Orbit: Planning Cassini's Plummet into Saturn

Cassini’s final orbit around Saturn will culminate in a dramatic ending as the spacecraft plunges into the ringed planet’s atmosphere, never to escape or be heard from again. The last hours of the mission prior to the final loss of signal have some of the most unique and valuable science to date. Cassini will take a unique trajectory to dive deep into the atmosphere on its approach to final disposal and no spacecraft, Cassini included, has entered these depths of Saturn’s atmosphere. The science community has placed heavy emphasis onthis once-in-a-lifetime opportunity to inspect these deeper regions of Saturn’s atmosphere. The Cassini project specifically aims to collect the very last bits of data during the final plunge to get samples of the deepest regions before the spacecraft is lost forever. The desire to collect the final bits of data presents several challenges. Cassini’s Mission Planning (MP) team has developed an End of Mission (EOM) scenario to tackle these demands. The EOM scenario outlines the framework for the entire last orbit of the mission and details thestrategy for data collection and transmission. Attaining near real-time transmission is key for the acquisition of the very last bits of data. The Cassini spacecraft will use a new mode of operations to successfully achieve this real-time transmission. In addition to this primary investigation and planning for telecommunications, key risks have been studied within the realm of the last orbit. Ultimately, this paper shows how the Cassini Project plans to ensurethe return of every last bit of data before the spacecraft is consumed by Saturn forever.

Bittner, Molly E.↗
NASA NTRS1993

Cassini Program Update

The Cassini Project is NASA's next mission the outer planets. Managed at the Jet Propulsion Laboratory and with the joint participation of the European Space Agency (ESA) and Agenzia Spatiale Italiana (ASI), Cassini will accomplish a comprehensive survey of the planet Saturn, Titan and the icy satellites of the Saturnian system, the rings, and the Saturnian magnetosphere. Early in 1992, the Project experienced significant change as the realities of the national economy and budget pressures forced a NASA-wide review of its programs. The Comet Rendezvous/Asteroid Flyby (CRAF) mission was deleted from the CRAF/Cassini Project and the remaining Cassini project was further rescoped to reduce cost. Many of the cost-savings measures involved reducing the capabilities of the spacecraft system. This paper examines the features of the redesigned spacecraft at the time of the rescope in Spring 1992 and compares it to today's design 18 months later.

C.P. Jones↗
NASA NTRS2003

Operational thermal control of Cassini Titan flybys

The Cassini spacecraft will fly by Saturn's largest moon, Titan, forty-five times during its science tour. Twenty-five of the flybys will have a relatively low closest approach target altitude in Titan's atmosphere and are of thermal concern. The Thermal Devices Team on the Cassini Project in Mission Operations at the Jet Propulsion Laboratory has designed an operational thermal control strategy for these flybys. The challenge was to provide flyby operational thermal control that enabled science and remained within design limitations and Project constraints.

Cassini aeroheating Titan flyby thermal analysis↗
NASA NTRS1999

Cassini Environmental Test and Analysis Program Summary

This paper presents an overview of the Cassini Project's environmental test and analysis program during thc spacecraft development phase - October 1989 to launch on October 1997. It describes the program's objectives and requirements, summarizes the approach used to achieve them, and provides the margins that were achieved in the final design. Assembly and system level environmental tests that were performed included dynamic, thermal, electromagnetic compatibility (EMC), and magnetic tests. Analysis was used to verify that the environmental requirements of radiation, solid particles including micrometeoroids, and single event effects have been satisfied. The environmental program implemented on Cassini satisfied the spirit and intent of the requirements imposed by the Project during the spacecraft's development. The lessons learned from the Cassini environmental program are discussed.

Hoffman, Alan R.↗
NASA NTRS1986

The Cassini mission

An assessment study of a Saturn-Orbiter plus Titan-probe mission was made. The NASA Solar System Exploration Committee (SSEC) had recommended two separate missions to the Saturn system, in keeping with its charter to design low-cost, dedicated planetary missions. These were a Titan probe, to be carried by a small spacecraft that would include some type of radar mapping device, and a Saturn Orbiter that would be a more sophisticated spacecraft, to be launched separately. A Saturn orbiter and a Titan probe are combined in a single mission that would be carried out in collaboration with NASA. It is this proposal, called the Cassini Project, which was approved by NASA and ESA for an assessment study to be carried out over the next year and a half. Details of the Cassini mission are discussed.

Owen, Tobias↗
NASA NTRS1994

(abstract) Saturn Mini-Probes Mission

The original Cassini mission concept for intensive Saturn exploration included dual atmospheric probes - to Titan and Saturn. The Saturn probe was lost in Cassini Project cost reduction, but the Saturn atmospheric goals are still important to the planetary science community - especially it measurements can be acquired during synoptic coverage by the Cassini Orbiter. New advanced technology and design heritage from the Pluto Fast Flyby mission permit a low cost mission concept for launch early in the first decade of the 21st century, in time to take advantage of the Cassini spacecraft being in orbit around Saturn. This paper will describe such a concept. The mini-probe carrier can be a relatively simple design, depending on a solar array/battery power system design instead of Radioactive Thermoelectric Generators (RTGs) with their attendant programmatic complexities, costs, and constraints. The Atlas IIAS/Star 48B, Proton, and STS with upper stage are launch vehicle options which permit modest payload deliveries to Saturn with relatively short flight times (3 to 4 years) such that the mini-probes arrive in the time period when the Cassini Orbiter is operating at Saturn. The Cassini time-line with a compatible SMP mission sequence is described. An example mission concept includes a carrier spacecraft with three 10 to 20 kg mini-probes, launched in the late summer of 2001 by an Atlas IIAS/Star 48B on a 3.8 year trip to Saturn. Preliminary evaluation of the Cassini time-line suggests compatibility of the probe entries with collecting the data for Earth-return.

Saturn Cassini miniprobes cost Pluto Fast Flyby↗
NASA NTRS1996

Evaluation of the Cassini Resource Exchange

The Cassini Resource Exchange was developed to assist the Cassini Science Instrumenmt Manager with the management of the spacecraft's science payload. This system, unlike previous develpment approaches, allocated the entire mass, power, data rate, and budget resources for the science instruments to the Principal Investigators. The result removed the Cassini Project from solving instrument development issues. Problems that did occur were resolved through by the Principal Investigators themselves through the use of a resource exchange.

spacecraft↗
NASA NTRS1998

Distributed Operations for the Cassini/Huygens Mission

The cassini project employs a concept known as distributed operations which allows independent instrument operations from diverse locations, provides full empowerment of all participants and maximizes use of limited resources.

Cassini Huygens operations missions↗
NASA NTRS2006

Cassini distributed instrument operations – what we’ve learned since Saturn orbit insertion

The Cassini mission to Saturn is complex with 12 science teams conducting distributed operations across the United States and Europe. Each Team includes scientists from around the world who actively participate in operations, including observation design, instrument commanding, downlink processing, and archiving. This represents a change in how JPL complex deep-space missions have been operated. Since Saturn Orbit Insertion (SOI), the Cassini Project has spent 17 months conducting science operations and has gained realworld experience that has tested the assumptions and rationale for this approach. We have learned that many of the expected benefits have been realized, but there were numerous unexpected challenges as well. This paper will discuss the lessons learned from the Cassini Tour experience to date. It will revisit the assumptions and rationale behind the distributed instrument operations design and will describe the results, good and bad, of implementing this method of operations. We will describe how Instrument Teams are structured, their roles and responsibilities, what challenges they faced going into orbital operations (the “tour”) and what creative solutions were proposed when funding limitations and schedule milestones prevented optimum solutions. We will also discuss the problems that have been encountered both on the ground and with the instruments, how these problems and anomalies were overcome, and what was learned along the way about the characteristics of distributed instrument operations.

Woncik, Pam↗
NASA NTRS2006

Cassini Distributed Instrument Operations: What We've Learned Since Saturn Orbit Insertion

The Cassini mission to Saturn is complex with 12 science teams conducting distributed operations across the United States and Europe. Each Team includes scientists from around the world who actively participate in operations, including observation design, instrument commanding, downlink processing, and archiving. This represents a change in how JPL complex deep-space missions have been operated. Since Saturn Orbit Insertion (SOI), the Cassini Project has spent 17 months conducting science operations and has gained real-world experience that has tested the assumptions and rationale for this approach. We have learned that many of the expected benefits have been realized, but there were numerous unexpected challenges as well. This paper will discuss the lessons learned from the Cassini Tour experience to date. It will revisit the assumptions and rationale behind the distributed instrument operations design and will describe the results, good and bad, of implementing this method of operations. We will describe how Instrument Teams are structured, their roles and responsibilities, what challenges they faced going into orbital operations (the 'tour') and what creative solutions were proposed when funding limitations and schedule milestones prevented optimum solutions. We will also discuss the problems that have been encountered both on the ground and with the instruments, how these problems and anomalies were overcome, and what was learned along the way about the characteristics of distributed instrument operations.

Cassini↗
NASA NTRS2006

Cassini Archive Tracking System

The Cassini Archive Tracking System (CATS) is a computer program that enables tracking of scientific data transfers from originators to the Planetary Data System (PDS) archives. Without CATS, there is no systematic means of locating products in the archive process or ensuring their completeness. By keeping a database of transfer communications and status, CATS enables the Cassini Project and the PDS to efficiently and accurately report on archive status. More importantly, problem areas are easily identified through customized reports that can be generated on the fly from any Web-enabled computer. A Web-browser interface and clearly defined authorization scheme provide safe distributed access to the system, where users can perform functions such as create customized reports, record a transfer, and respond to a transfer. CATS ensures that Cassini provides complete science archives to the PDS on schedule and that those archives are available to the science community by the PDS. The three-tier architecture is loosely coupled and designed for simple adaptation to multimission use. Written in the Java programming language, it is portable and can be run on any Java-enabled Web server.

Conner, Diane↗
NASA NTRS1993

Multi-band reflector antenna with double-ring element frequency selective subreflector

Frequency selective subreflectors (FSS) are often employed in the reflector antenna system of a communication satellite or a deep space exploration vehicle for multi-frequency operations. In the past, FSS's have been designed for diplexing two frequency bands. For example, the Voyager FSS was designed to diplex S and X bands and the TDRSS FSS was designed to diplex S and Ku bands. Recently, NASA's CASSINI project requires an FSS to multiplex four frequency (S/X/Ku/Ka) bands. Theoretical analysis and experimental verifications are presented for a multi-band flat pannel FSS with double-ring elements. Both the exact formulation and the thin-ring approximation are described for analyzing and designing this multi-ring patch element FSS. It is found that the thin-ring approximation fails to predict the electrically wide ring element FSS's performance. A single screen double-ring element FSS is demonstrated for the tri-band system that reflects the X-band signal while transmitting through the S- and Ku-band signals. In addition, a double screen FSS with non-similar double-ring elements is presented for the Cassini's four-band system which reflects the X- and Ka-band signals while passing the S- and Ku-band signals. To accurately predict the FSS effects on a dual reflector antenna's radiation pattern, the FSS subreflector's transmitted/reflected field variation as functions of the polarization and incident angles with respect to the local coordinates was taken into account. An FSS transmission/reflection coefficient table is computed for TE and TM polarizations at various incident angles based on the planar FSS model. Next, the hybrid Geometric Optics (GO) and Physical Optics (PO) technique is implemented with linearly interpolating the FSS table to efficiently determine the FSS effects in a dual reflector antenna.

Wu, Te-Kao↗
NASA NTRS2013

Cassini Solstice Mission Maneuver Experience: Year Three

The Cassini spacecraft is now in its second Saturn tour extension, the Solstice Mission. By emphasizing propellant preservation over minimizing maneuver cycles, the Cassini Project is meeting the challenge of mission completion in 2017. Since June 2012, 18 of 21 maneuvers were performed to closely maintain the prescribed trajectory, saving downstream propellant. These and other maneuvers during the third year of the Solstice Mission (June 2012 to August 2013) are highlighted in this paper: 31 planned maneuvers targeted to 11 Titan flybys and the last planned Rhea encounter. An assessment of the updated maneuver execution-error models will also be presented.

Cassini↗
NASA NTRS2002

Science opportunity analyzer - a multi-mission tool for planning

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.

SOA science planning mission operations sequence s↗