Search NASA⌕ Search

SEARCH · Search NASA

Results for “Voyager 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.

346 records · Page 20

Voyager Interstellar Mission: Challenges of Flying a Very Old Spacecraft on a Very Long Mission

Two Voyager spacecraft were launched in 1977. After the successful flybys of Jupiter and Saturn by both Voyagers and Uranus and Neptune by Voyager 2, the mission has been extended for another 30 years in search of the transition region between the dominance of the solar energy and interstellar energy. The Voyager Interstellar Mission (VIM) started on January 1, 1990. It can be characterized by several factors including extremely long communication distances, aging hardware, reduced staffing levels and difficulty in obtaining Deep Space Network (DSN) resources necessitated by the increasing distance between the spacecraft and Earth. The mission was redesigned to compensate for such factors while maximizing the science return. After 25 years of VIM and several significant science discoveries, both Voyager spacecraft are still functioning well and the Voyager flight team is preparing for an even longer mission - until the year 2025 and beyond. In order to work around the challenges and to continue the mission even further, the team has been implementing numerous changes, mainly through flight software modifications and hardware reconfiguration. The major drivers for the changes are two-fold: resource constraints (such as decreasing power output and difficulty in obtaining the necessary DSN coverage) and anomalies due to the aging hardware. The majority of changes occur through flight software modifications so the state of the on-board responses is appropriate for the changing space environment and mission phase, and the flight software is compatible in allowing the maximum data gathering. The on-board flight software routines such as baseline sequence, fault protection routines, the High Gain Antenna POINTing to Earth (HPOINT) table, and long-term events table need to be maintained through flight software updates. The changes also occur through hardware reconfiguration such as selecting the backup Hybrid Buffer Interface Circuits (HYBIC) or attitude propulsion thrusters. This paper will describe the challenges of VIM and what has been done to overcome or mitigate those challenges. The primary focus will be the major flight software changes made during VIM and the changes that are in store for the near future in preparation for continuing the extended mission, from the originally projected year of 2020 out to the year 2025 and possibly beyond.

Matsumoto, Sun Kang↗

U.S. Space Radioisotope Power Systems and Applications: Past, Present and Future

Radioisotope power systems (RPS) have been essential to the U.S. exploration of outer space. RPS have two primary uses: electrical power and thermal power. To provide electrical power, the RPS uses the heat produced by the natural decay of a radioisotope (e.g., plutonium-238 in U.S. RPS) to drive a converter (e.g., thermoelectric elements or Stirling linear alternator). As a thermal power source the heat is conducted to whatever component on the spacecraft needs to be kept warm; this heat can be produced by a radioisotope heater unit (RHU) or by using the excess heat of a radioisotope thermoelectric generator (RTG). As of 2010, the U.S. has launched 41 RTGs on 26 space systems. These space systems have ranged from navigational satellites to challenging outer planet missions such as Pioneer 10/11, Voyager 1/2, Galileo, Ulysses, Cassini and the New Horizons mission to Pluto. In the fall of 2011, NASA plans to launch the Mars Science Laboratory (MSL) that will employ the new Multi-Mission Radioisotope Thermoelectric Generator (MMRTG) as the principal power source. Hundreds of radioisotope heater units (RHUs) have been launched to provide warmth to Apollo 11, used to provide heating of critical components in a seismic experiment package, Pioneer 10/11, Voyager 1/2, Galileo, Cassini, Mars Pathfinder, MER rovers, etc. to provide temperature control to critical spacecraft electronics and other mechanical devices such as propulsion system propellant valves. A radioisotope (electrical) power source or system (RPS) consists of three basic elements: (1) the radioisotope heat source that provides the thermal power, (2) the converter that transforms the thermal power into electrical power and (3) the heat rejection radiator. Figure 1 illustrates the basic features of an RPS. The idea of a radioisotope power source follows closely after the early investigations of radioactivity by researchers such as Henri Becquerel (1852-1908), Marie Curie (1867-1935), Pierre Curie (1859-1906) and R. J. Strut. Almost 100 years ago, in 1913, English physicist H. G. J. Moseley (1887-1915) constructed the first nuclear battery using a vacuum flask and 20 mCi of radium (Corliss and Harvey, 1964, Proceedings of the Royal Society, 1913). After World War II, serious interest in radioisotope power systems in the U.S. was sparked by studies of space satellites such as North American Aviation s 1947 report on nuclear space power and the RAND Corporation s 1949 report on radioisotope power. (Greenfield, 1947, Gendler and Kock, 1949). Radioisotopes were also considered in early studies of nuclear-powered aircraft (Corliss and Harvey, 1964). In 1951, the U.S. Atomic Energy Commission (AEC) signed several contracts to study a 1-kWe space power plant using reactors or radioisotopes. Several of these studies, which were completed in 1952, recommended the use of RPS. (Corliss and Harvey, 1964). In 1954, the RAND Corporation issued the summary report of the Project Feedback military satellite study in which radioisotope power was considered (Lipp and Salter, 1954, RAND). Paralleling these studies, in 1954, K. C. Jordan and J. H. Birden of the AEC s Mound Laboratory conceived and built the first RTG using chromel-constantan thermocouples and a polonium-210 (210Po or Po-210) radioisotope heat source (see Figure 2). While the power produced (1.8 mWe) was low by today s standards, this first RTG showed the feasibility of RPS. A second thermal battery was built with more Po-210, producing 9.4 mWe. Jordan and Birden concluded that the Po-210 thermal battery would have about ten times the energy of ordinary dry cells of the same mass (Jordan and Birden, 1954). The heat source consisted of a 1-cm-diameter sphere of 57 Ci (1.8 Wt) of Po-210 inside a capsule of nickel-coated cold-rolled steel all inside a container of Lucite. The thermocouples were silver-soldered chromel-constantan. The thermal battery produced 1.8 mWe.

Cataldo, Robert L.↗

DUKSUP: A Computer Program for High Thrust Launch Vehicle Trajectory Design and Optimization

From the late 1960s through 1997, the leadership of NASAs Intermediate and Large class unmanned expendable launch vehicle projects resided at the NASA Lewis (now Glenn) Research Center (LeRC). One of LeRCs primary responsibilities --- trajectory design and performance analysis --- was accomplished by an internally-developed analytic three dimensional computer program called DUKSUP. Because of its Calculus of Variations-based optimization routine, this code was generally more capable of finding optimal solutions than its contemporaries. A derivation of optimal control using the Calculus of Variations is summarized including transversality, intermediate, and final conditions. The two point boundary value problem is explained. A brief summary of the codes operation is provided, including iteration via the Newton-Raphson scheme and integration of variational and motion equations via a 4th order Runge-Kutta scheme. Main subroutines are discussed. The history of the LeRC trajectory design efforts in the early 1960s is explained within the context of supporting the Centaur upper stage program. How the code was constructed based on the operation of the AtlasCentaur launch vehicle, the limits of the computers of that era, the limits of the computer programming languages, and the missions it supported are discussed. The vehicles DUKSUP supported (AtlasCentaur, TitanCentaur, and ShuttleCentaur) are briefly described. The types of missions, including Earth orbital and interplanetary, are described. The roles of flight constraints and their impact on launch operations are detailed (such as jettisoning hardware on heating, Range Safety, ground station tracking, and elliptical parking orbits). The computer main frames on which the code was hosted are described. The applications of the code are detailed, including independent check of contractor analysis, benchmarking, leading edge analysis, and vehicle performance improvement assessments. Several of DUKSUPs many major impacts on launches are discussed including Intelsat, Voyager, Pioneer Venus, HEAO, Galileo, and Cassini.

Launch vehicle performance optimization↗

DUKSUP: A Computer Program for High Thrust Launch Vehicle Trajectory Design and Optimization

From the late 1960's through 1997, the leadership of NASA's Intermediate and Large class unmanned expendable launch vehicle projects resided at the NASA Lewis (now Glenn) Research Center (LeRC). One of LeRC's primary responsibilities --- trajectory design and performance analysis --- was accomplished by an internally-developed analytic three dimensional computer program called DUKSUP. Because of its Calculus of Variations-based optimization routine, this code was generally more capable of finding optimal solutions than its contemporaries. A derivation of optimal control using the Calculus of Variations is summarized including transversality, intermediate, and final conditions. The two point boundary value problem is explained. A brief summary of the code's operation is provided, including iteration via the Newton-Raphson scheme and integration of variational and motion equations via a 4th order Runge-Kutta scheme. Main subroutines are discussed. The history of the LeRC trajectory design efforts in the early 1960's is explained within the context of supporting the Centaur upper stage program. How the code was constructed based on the operation of the Atlas/Centaur launch vehicle, the limits of the computers of that era, the limits of the computer programming languages, and the missions it supported are discussed. The vehicles DUKSUP supported (Atlas/Centaur, Titan/Centaur, and Shuttle/Centaur) are briefly described. The types of missions, including Earth orbital and interplanetary, are described. The roles of flight constraints and their impact on launch operations are detailed (such as jettisoning hardware on heating, Range Safety, ground station tracking, and elliptical parking orbits). The computer main frames on which the code was hosted are described. The applications of the code are detailed, including independent check of contractor analysis, benchmarking, leading edge analysis, and vehicle performance improvement assessments. Several of DUKSUP's many major impacts on launches are discussed including Intelsat, Voyager, Pioneer Venus, HEAO, Galileo, and Cassini.

high thrust trajectory design↗