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.
Flight dynamics, experiment operational phase sequence, and support operations for Applications Technology Satellite /ATS/ MISSION
Successful planetary exploration missions have been completed by unmanned Mariner spacecraft, which were designed at the Jet Propulsion Laboratory. Mariner II completed a 109-day flyby mission to Venus on December 14, 1962. This mission was followed by the flyby of Mars and return of 21 historic photographs of its surface by Mariner IV in July 1965. Further successful missions followed: Mariner V to Venus in 1967, Mariners VI and VII to Mars in 1969. In all of these missions, a Central Computer and Sequencer onboard the spacecraft was used to provide on-board control functions, although complete ground backup was also available.
The development of the hoop/column spacetenna reflector is discussed. Schedules, mission configurations, systems compatibility, deployment sequence, cable development, and ground model fabrication and assembly are discussed.
The Comet Rendezvous Asteroid Flyby (CRAF) mission is now being designed and planned to perform detailed studies of a typical short period comet as it moves around its orbit, building on the data gained from the Giotto, Vega, and Suisei fast flybys of Comet Halley in 1986. CRAF will be launched in Aug. 1995 and will match orbits with short period Comet Kopff in July 2000, 850 days before perihelion at a heliocentric distance of 5.05 AU. After a series of close, slow flybys, the spacecraft will be placed in orbit around the nucleus for a better than 1 m/line-pair imaging resolution on the nucleus surface. Earth based observations of the target comet, either by ground based facilities or Earth orbiting satellites, can provide essential data for CRAF mission planning, and are needed in support of the rendezvous mission. Estimates of the nucleus size, albedo, shape, rotation period, and rotation pole orientation are needed for preliminary mission planning, resource allocation, and sequence design.
The NERVA/Rover Enabler technology enables to go on a low risk, short-term program to meet the requirements of the Mars mission and maybe some lunar missions. The following subject areas are covered: NERVA technology - the foundation for tomorrow's space missions; NERVA/Rover reactor system test sequence; NERVA engine development program; nuclear thermal reactor capability based on many related Westinghouse technology programs; investment in Rover/Nerva technology; synergistic applications of NERVA technology; flow schematic of the NDR engine; the NERVA nuclear subsystem; and technology evolution.
The STS-55 initial launch attempt of Columbia (OV102) was terminated on KSC launch pad A March 22, 1993 at 9:51 AM E.S.T. due to violation of an ME-3 (Engine 2011) Launch Commit Criteria (LCC) limit exceedance. The event description and timeline are summarized. Propellant loading was initiated on 22 March, 1993 at 1:15 AM EST. All SSME chill parameters and launch commit criteria (LCC) were nominal. At engine start plus 1.44 seconds, a Failure Identification (FID) was posted against Engine 2011 for exceeding the 50 psia Oxidizer Preburner (OPB) purge pressure redline. The engine was shut down at 1.50 seconds followed by Engines 2034 and 2030. All shut down sequences were nominal and the mission was safely aborted. The OPB purge pressure redline violation and the abort profile/overlay for all three engines are depicted. SSME Avionics hardware and software performed nominally during the incident. A review of vehicle data table (VDT) data and controller software logic revealed no failure indications other than the single FID 013-414, OPB purge pressure redline exceeded. Software logic was executed according to requirements and there was no anomalous controller software operation. Immediately following the abort, a Rocketdyne/NASA failure investigation team was assembled. The team successfully isolated the failure cause to the oxidizer preburner augmented spark igniter purge check valve not being fully closed due to contamination. The source of the contaminant was traced to a cut segment from a rubber O-ring which was used in a fine clean tool during valve production prior to 1992. The valve was apparently contaminated during its fabrication in 1985. The valve had performed acceptably on four previous flights of the engine, and SSME flight history shows 780 combined check valve flights without failure. The failure of an Engine 3 (SSME No. 2011) check valve to close was sensed by onboard engine instruments even though all other engine operations were normal. This resulted in an engine shutdown and safe sequential shutdown of all three engines prior to ignition of the solid boosters.
Robotic spacecraft are controlled by sets of commands called 'sequences.' These sequences must be checked against mission constraints. Making our existing constraint checking program faster would enable new capabilities in our uplink process. Therefore, we are rewriting this program to run on a parallel computer. To do so, we had to determine how to run constraint-checking algorithms in parallel and create a new method of specifying spacecraft models and constraints. This new specification gives us a means of representing flight systems and their predicted response to commands which could be used in a variety of applications throughout the command process, particularly during anomaly or high-activity operations. This commonality could reduce operations cost and risk for future complex missions. Lessons learned in applying some parts of this system to the TOPEX/Poseidon mission will be described.
The STS-51 initial launch attempt of Discovery (OV-103) was terminated on KSC launch pad 39B on 12 Aug. 1993 at 9:12 AM E.S.T. due to a sensor redundancy failure in the liquid hydrogen system of ME-2 (Engine 2033). The event description and time line are summarized. Propellant loading was initiated on 12 Aug. 1993 at 12:00 AM EST. All space shuttle main engine (SSME) chill parameters and Launch Commit Criteria (LCC) were nominal. At engine start plus 1.34 seconds a Failure Identification (FID) was posted against Engine 2033 for exceeding the 1800 spin intra-channel (A1-A2) Fuel Flowrate sensor channel qualification limit. The engine was shut down at 1.50 seconds followed by Engines 2032 and 2030. All shut down sequences were nominal and the mission was safely aborted. SSME Avionics hardware and software performed nominally during the incident. A review of vehicle data table (VDT) data and controller software logic revealed no failure indications other than the single FID 111-101, Fuel Flowrate Intra-Channel Test Channel A disqualification. Software logic was executed according to requirements and there was no anomalous controller software operation. Immediately following the abort, a Rocketdyne/NASA failure investigation team was assembled. The team successfully isolated the failure cause to an open circuit in a Fuel Flowrate Sensor. This type of failure has occurred eight previous times in ground testing. The sensor had performed acceptably on three previous flights of the engine and SSME flight history shows 684 combined fuel flow rate sensor channel flights without failure. The disqualification of an Engine 2 (SSME No. 2033) Fuel Flowrate sensor channel was a result of an instrumentation failure and not engine performance. All other engine operations were nominal. This disqualification resulted in an engine shutdown and safe sequential shutdown of all three engines prior to ignition of the solid boosters.
The Cassini Program's challenge is to fly a large, complex mission with a reduced operations budget. A consequence of the reduced budget is elimination of the large, centrally located group traditionally used for uplink operations. Instead, responsibility for completing parts of the uplink function is distributed throughout the Program. A critical strategy employed to handle this challenge is the use of Virtual Uplink Operations Teams. A Virtual Team is comprised of a group of people with the necessary mix of engineering and science expertise who come together for the purpose of building a specific uplink product. These people are drawn from throughout the Cassini Program and participate across a large geographical area (from Germany to the West coast of the USA), covering ten time zones. The participants will often split their time between participating in the Virtual Team and accomplishing their core responsibilities, requiring significant planning and time management. When the particular uplink product task is complete, the Virtual Team disbands and the members turn back to their home organization element for future work assignments. This time-sharing of employees is used on Cassini to build mission planning products, via the Mission Planning Virtual Team, and sequencing products and monitoring of the sequence execution, via the Sequence Virtual Team. This challenging, multitasking approach allows efficient use of personnel in a resource constrained environment.
This paper describes the innovative numerical algorithm and the command sequence simulation of the MER mission for surface operations.
The Origins Spectral Interpretation Resource Identification Security Regolith Explorer (OSIRIS-REx) mission is a NASA New Frontiers mission launching in 2016 to rendezvous with the near-Earth asteroid (101955) 1999 RQ36 in late 2018. After several months in formation with and orbit about the asteroid, OSIRIS-REx will fly a Touch-And-Go (TAG) trajectory to the asteroid s surface to obtain a regolith sample. This paper describes the mission design of the TAG sequence and the propulsive maneuvers required to achieve the trajectory. This paper also shows preliminary results of orbit covariance analysis and Monte-Carlo analysis that demonstrate the ability to arrive at a targeted location on the surface of RQ36 within a 25 meter radius with 98.3% confidence.
The Origins Spectral Interpretation Resource identification Security Regolith Explorer (OSIRIS-REx) mission is a NASA New Frontiers mission launching in 2016 to rendezvous with the near-Earth asteroid (101955) Bennu in late 2018. Following an extensive campaign of proximity operations activities to characterize the properties of Bennu and select a suitable sample site, OSIRIES-REx will fly a Touch-And-Go (TAG) trajectory to the asteroid's surface to obtain a regolith sample. The paper summarizes the mission design of the TAG sequence, the propulsive required to achieve the trajectory, and the sequence of events leading up to the TAG event. The paper will summarize the Monte-Carlo simulation of the TAG sequence and present analysis results that demonstrate the ability to conduct the TAG within 25 meters of the selected sample site and +-2 cms of the targeted contact velocity. The paper will describe some of the challenges associated with conducting precision navigation operations and ultimately contacting a very small asteroid.
The Origins Spectral Interpretation Resource Identification Security Regolith Explorer (OSIRIS-REx) mission is a NASA New Frontiers mission launching in 2016 to rendezvous with the near-Earth asteroid (101955) Bennu in late 2018. Following an extensive campaign of proximity operations activities to characterize the properties of Bennu and select a suitable sample site, OSIRIS-REx will fly a Touch-And-Go (TAG) trajectory to the asteroid's surface to obtain a regolith sample. The paper summarizes the mission design of the TAG sequence, the propulsive maneuvers required to achieve the trajectory, and the sequence of events leading up to the TAG event. The paper also summarizes the Monte-Carlo simulation of the TAG sequence and presents analysis results that demonstrate the ability to conduct the TAG within 25 meters of the selected sample site and 2 cm/s of the targeted contact velocity. The paper describes some of the challenges associated with conducting precision navigation operations and ultimately contacting a very small asteroid.
The Rover Sequencing and Visualization Program (RSVP) is the software tool for use in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight-code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover-predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (IDD) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities. Thus, RSVP, being highly data driven, may be tailored to other missions with minimal effort. In addition, RSVP uses a distributed, message-passing architecture to allow multitasking, and collaborative visualization and sequence development by scattered team members.
The Cassini Spacecraft will soon journey to Saturn to perform a close-up study of the Saturnian system; its rings, moons, magneto-sphere, andf the planet itelf. Sequences of commands will be sent to the spacecraft by ground personnel to control every aspect of the mission. To validate and verify these command sequences, a bit-level, high-speed simulator (HSS) has been developed.
In today's operations environment, the teams are smaller and need to be more efficient while still ensuring the safety and success of the mission. In addition, teams often begin working on a mission in its early development phases and continue on the team through actual operations. For these reasons the operations teams want to be presented with a software environment that integrates multiple needed software applications as well as providing them with context sensitive editing support for entering commands and sequences of commands. At Jet Propulsion Laboratory, the Multi-Mission Planning and Sequencing (MPS) Editor provided by the Multi-Mission Ground Systems and Services (MGSS) supports those operational needs.
As the nation embarks on a new and bold journey to Mars, significant work is being done to determine what that mission and those architectural elements will look like. The Evolvable Mars Campaign, or EMC, is being evaluated as a potential approach to getting humans to Mars. Built on the premise of leveraging current technology investments and maximizing element commonality to reduce cost and development schedule, the EMC transportation architecture is focused on developing the elements required to move crew and equipment to Mars as efficiently and effectively as possible both from a performance and a programmatic standpoint. Over the last 18 months the team has been evaluating potential options for those transportation elements. One of the key aspects of the EMC is leveraging investments being made today in missions like the Asteroid Redirect Mission (ARM) mission using derived versions of the Solar Electric Propulsion (SEP) propulsion systems and coupling them with other chemical propulsion elements that maximize commonality across the architecture between both transportation and Mars operations elements. This paper outlines the broad trade space being evaluated including the different technologies being assessed for transportation elements and how those elements are assembled into an architecture. Impacts to potential operational scenarios at Mars are also investigated. Trades are being made on the size and power level of the SEP vehicle for delivering cargo as well as the size of the chemical propulsion systems and various mission aspects including Inspace assembly and sequencing. Maximizing payload delivery to Mars with the SEP vehicle will better support the operational scenarios at Mars by enabling the delivery of landers and habitation elements that are appropriately sized for the mission. The purpose of this investigation is not to find the solution but rather a suite of solutions with potential application to the challenge of sending cargo and crew to Mars. The goal is that, by building an architecture intelligently with all aspects considered, the sustainable Mars program wisely invests limited resources enabling a long-term human Mars exploration program.
This paper will address the science planning and sequencing aspects of the command generation process for the scientifically diverse Cassini Mission. The mission's prime objectives are to study the Saturnian system and deliver the Huygens Probe to the moon Titan. Together, the spacecraft and probe will be the largest and most complicated craft ever launched to another planet. The presentation will begin with an overview of the Cassini spacecraft and its scientific instrumentation. This will be followed with a description of the Oct. 1997 mission. Next, the structure of the science planning and sequencing process, with special emphasis on science's role, will be outlined. Finally, this presentation will conclude with a discussion of some of the unique challenges faced by the Ground System during Cassini's four-year orbital tour.