Environmental control system of Apollo spacecraft worked O.K. thanks to redesigned hardware
Apollo command and service modules environmental control system, discussing redesign of faulty hardware
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.
Apollo command and service modules environmental control system, discussing redesign of faulty hardware
The present consideration of recent advancements in the nonlinear guidance of spacecraft, using feedback linearization and decoupling to generate exact nominal commands, gives attention to the correction of saturation effects and oscillation prevention in saturated operating regimes. In the case of spacecraft maneuvered by momentum-transfer devices, real time command generation is possible by means of pointwise minimization of the sum of the squares of the norms of the 'next state error' for the equivalent system and the linear system input. It is also possible to track a nominal trajectory, such as a critically damped harmonic oscillator response, by minimizing the square of the norm of the error between the actual and the tracked states.
In January of 2004 both of the Mars Exploration Rover spacecraft landed safely, initiating daily surface operations at the Jet Propulsion Laboratory for what was anticipated to be approximately three months of mobile exploration. The longevity of this mission, still ongoing after ten years, has provided not only a tremendous return of scientific data but also the opportunity to refine and improve the methodology by which robotic Mars surface missions are commanded. Since the landing of the Mars Science Laboratory spacecraft in August of 2012, this methodology has been successfully applied to operate a Martian rover which is both similar to, and quite different from, its predecessors. For MER and MSL, daily uplink operations can be most broadly viewed as converting the combined interests of both the science and engineering teams into a spacecraft-safe set of transmittable command files. In order to accomplish these ends a discrete set of mission-critical software tools were developed which not only allowed for conformation to established JPL standards and practices but also enabled innovative technologies specific to each mission. Although these primary programs provided the requisite capabilities for meeting the high-level goals of each distinct phase of the uplink process, there was little in the way of secondary software to support the smooth flow of data from one phase to the next. In order to address this shortcoming a suite of small software tools was developed to aid in phase transitions, as well as to automate some of the more laborious and error-prone aspects of uplink operations. This paper describes the evolution of this software suite, from its initial attempts to merely shorten the duration of the operator's shift, to its current role as an indispensable tool enforcing workflow of the uplink operations process and agilely responding to the new and unexpected challenges of missions which can, and have, lasted many years longer than originally anticipated.
NASA’s Psyche mission will launch in 2022 and begin a 3.6-year cruise to the metallic asteroid Psyche, the largest metal asteroid in the solar system. The baseline spacecraft design is a hybrid of JPL’s deep-space heritage subsystems with commercial partner Maxar’s electric propulsion, power, and structure subsystems. The Psyche mission will feature the first use of Hall thrusters for a NASA mission, and the first use of Hall thrusters beyond cis-lunar space. This paper will provide an overview of the electric propulsion subsystem and details of the flight system implementation for the Psyche mission. The concept of operations is discussed including subsystem-level operations, the initial checkout after launch, and cruise and orbital operations. Command and control interfaces with the spacecraft and fault protection design are presented. Finally, the status of subsystem assembly and test is described.
This paper will describe the results that have been obtained to date concerning MMS formation flying. The MMS spacecraft spin at a rate of 3.1 RPM, with spin axis roughly aligned with Ecliptic North. Several booms are used to deploy instruments: two 5 m magnetometer booms in the spin plane, two rigid booms of length 12.5 m along the positive and negative spin axes, and four flexible wire booms of length 60 m in the spin plane. Minimizing flexible motion of the wire booms requires that reorientation of the spacecraft spin axis be kept to a minimum: this is limited to attitude maneuvers to counteract the effects of gravity-gradient and apparent solar motion. Orbital maneuvers must therefore be carried out in essentially the nominal science attitude. These burns make use of a set of monopropellant hydrazine thrusters: two (of thrust 4.5 N) along the spin axis in each direction, and eight (of thrust 18 N) in the spin plane; the latter are pulsed at the spin rate to produce a net delta-v. An on-board accelerometer-based controller is used to accurately generate a commanded delta-v. Navigation makes use of a weak-signal GPS-based system: this allows signals to be received even when MMS is flying above the GPS orbits, producing a highly accurate determination of the four MMS orbits. This data is downlinked to the MMS Mission Operations Center (MOC) and used by the MOC Flight Dynamics Operations Area (FDOA) for maneuver design. These commands are then uplinked to the spacecraft and executed autonomously using the controller, with the ground monitoring the burns in real time.
A digital tape recorder was used on the Mariner Mars 1971 spacecraft to record television and scientific data. Data were recorded at 132 kilobits/sec and were reproduced at one of five available rates (16.2, 8.1, 4.05, 2.05, or 1.0125 kilobits/sec) selected by ground command to be congruous with the spacecraft-to-earth communications link performance. The transport mechanism contained 167 m of 1.2 cm magnetic recording tape. A single motor was used to drive the peripheral drive transport. During development of the design, stick slip problems were encountered. A design life of 2400 tape passes was achieved during the mission.
At NASA Goddard, the role of the command management system (CMS) is to transform general requests for spacecraft opeerations into detailed operational plans to be uplinked to the spacecraft. The CMS is part of the NASA Data System which entails the downlink of science and engineering data from NASA near-earth satellites to the user, and the uplink of command and control data to the spacecraft. Presently, it takes one to three years, with meetings once or twice a week, to determine functional requirements for CMS software design. As an alternative approach to the present technique of developing CMS software functional requirements, an expert system prototype was developed to aid in this function. Specifically, the knowledge base was formulated through interactions with domain experts, and was then linked to an existing expert system application generator called 'Knowledge Engineering System (Version 1.3).' Knowledge base development focused on four major steps: (1) develop the problem-oriented attribute hierachy; (2) determine the knowledge management approach; (3) encode the knowledge base; and (4) validate, test, certify, and evaluate the knowledge base and the expert system prototype as a whole. Backcasting was accomplished for validating and testing the expert system prototype. Knowledge refinement, evaluation, and implementation procedures of the expert system prototype were then transacted.
Footage shows the U.S Air Force Aircraft "Air Mobility Command" approaching, and landing at the Cape Canaveral Air Station Skid Strip (CCAS). The truck carrying the Delta XTE Spacecraft is also shown as it leaves the Air Mobility Command.
The control of deep mission spacecraft by computing and signaling to the spacecraft a series of propulsive, velocity correction commands which maneuver the craft to its desired course is examined. The technical elements of the global navigation system (measurement, communications, computation, and propulsion) are described. The ground-computing facilities used to navigate spacecraft on deep space missions consist of computer and software systems used to compute orbits from radio tracking and on-board optical image data (radio, Doppler, and VLBI measurements). The accuracy of these measurements is evaluated, and the modeling of the data is discussed. Examples concerned with the navigation of Voyager and Galileo are presented.
The National Aeronautics and Space Administration (NASA) invests millions of dollars in spacecraft and ground system development, and in mission operations in the pursuit of scientific knowledge of the universe. In recent years, NASA sent a probe to Mars to study the Red Planet's upper atmosphere, obtained high resolution images of Pluto, and it is currently preparing to find new exoplanets, rendezvous with an asteroid, and bring a sample of the asteroid back to Earth for analysis. The success of these missions is enabled by mission assurance. In turn, mission assurance is backed by information assurance. The information systems supporting NASA missions must be reliable as well as secure. NASA - like every other U.S. Federal Government agency - is required to manage the security of its information systems according to federal mandates, the most prominent being the Federal Information Security Management Act (FISMA) of 2002 and the legislative updates that followed it. Like the management of enterprise information technology (IT), federal information security management takes a "one-size fits all" approach for protecting IT systems. While this approach works for most organizations, it does not effectively translate into security of highly specialized systems such as those supporting NASA missions. These systems include command and control (C&C) systems, spacecraft and instrument simulators, and other elements comprising the ground segment. They must be carefully configured, monitored and maintained, sometimes for several years past the missions' initially planned life expectancy, to ensure the ground system is protected and remains operational without any compromise of its confidentiality, integrity and availability. Enterprise policies, processes, procedures and products, if not effectively tailored to meet mission requirements, may not offer the needed security for protecting the information system, and they may even become disruptive to mission operations. Certain protective measures for the general enterprise may not be as efficient within the ground segment. This is what the authors have concluded through observations and analysis of patterns identified from the various security assessments performed on NASA missions such as MAVEN, OSIRIS-REx, New Horizons and TESS, to name a few. The security audits confirmed that the framework for managing information system security developed by the National Institute of Standards and Technology (NIST) for the federal government, and adopted by NASA, is indeed effective. However, the selection of the technical, operational and management security controls offered by the NIST model - and how they are implemented - does not always fit the nature and the environment where the ground system operates in even though there is no apparent impact on mission success. The authors observed that unfit controls, that is, controls that are not necessarily applicable or sufficiently effective in protecting the mission systems, are often selected to facilitate compliance with security requirements and organizational expectations even if the selected controls offer minimum or non-existent protection. This paper identifies some of the standard security controls that can in fact protect the ground system, and which of them offer little or no benefit at all. It offers multiple scenarios from real security audits in which the controls are not effective without, of course, disclosing any sensitive information about the missions assessed. In addition to selection and implementation of controls, the paper also discusses potential impact of recent legislation such as the Federal Information Security Modernization Act (FISMA) of 2014 - aimed at the enterprise - on the ground system, and offers other recommendations to Information System Owners (ISOs).
Since the Mars Exploration Rovers (MER), Spirit and Opportunity, began their travels across the Martian surface in January of 2004, orbiting spacecraft such as the Mars 2001 Odyssey orbiter have relayed the majority of their collected scientific and operational data to and from Earth. From the beginning of those missions, it was evident that using orbiters to relay data to and from the surface of Mars was a vastly more efficient communications strategy in terms of power consumption and bandwidth compared to direct-to-Earth means. However, the coordination between the various spacecraft, which are largely managed independently and on differing commanding timelines, has always proven to be a challenge. Until recently, the ground operators of all these spacecraft have coordinated the movement of data through this network using a collection of ad hoc human interfaces and various, independent software tools. The Mars Relay Operations Service (MaROS) has been developed to manage the evolving needs of the Mars relay network, and specifically to standardize and integrate the relay planning and coordination data into a centralized infrastructure. This paper explores the journey of developing the MaROS system, from inception to delivery and acceptance by the Mars mission users.
The Command and Data Subsystem (CDS) is an RCA 1802microprocessor based subsystem that acts as the central nervous system for the Galileo Orbiter Spacecraft. All communication between the ground and spacecraft flows through the CDS. The CDS also distributes commands in real time, algorithmetrically expanded from a data base loaded from the ground and in response to spacecraft alarms. The distributed microprocessor system is configured as a redundant set of hardware with three microprocessors on each half. The microprocessors are surrounded by a group of special purpose hardware components which greatly enhance the ability of the software to perform its task. It is shown how the software architecture makes a distributed system of six microprocessors appear to each user as a single virtual machine, and collectively as a set of cooperating virtual machines that prevent the simultaneous presence of the several users from interfering destructively with each other.
The Tropical Rainfall Measuring Mission (TRMM) spacecraft was launched in November of 1996 in order to obtain unique three dimensional radar cross sectional observations of cloud structures with particular interest in hurricanes. The TRMM mission life was recently extended with current estimates that operations will continue through the 2012-2013 timeframe. Faced with this extended mission profile, the project has embarked on a technology refresh and re-engineering effort. TRMM has recently implemented a re-engineering effort to expand a middleware based messaging architecture to enable fully redundant lights-out of flight operations activities. The middleware approach is based on the Goddard Mission Services Evolution Center (GMSEC) architecture, tools and associated open-source Applications Programming Interface (API). Middleware based messaging systems are useful in spacecraft operations and automation systems because private node based knowledge (such as that within a telemetry and command system) can be broadcast on the middleware messaging bus and hence enable collaborative decisions to be made by multiple subsystems. In this fashion, private data is made public and distributed within the local area network and multiple nodes can remain synchronized with other nodes. This concept is useful in a fully redundant architecture whereby one node is monitoring the processing of the 'prime' node so that in the event of a failure the backup node can assume operations of the prime, without loss of state knowledge. This paper will review and present the experiences, architecture, approach and lessons learned of the TRMM re-engineering effort centered on the GMSEC middleware architecture and tool suite. Relevant information will be presented that relates to the dual redundant parallel nature of the Telemetry and Command (T and C) and Front-End systems and how these systems can interact over a middleware bus to achieve autonomous operations including autonomous commanding to recover missing science data during the same spacecraft contact.
In the twenty-first century, National Aeronautics and Space Administration (NASA) Enterprises envision frequent low-cost missions to explore the solar system, observe the universe, and study our planet. Satellite autonomy is a key technology required to reduce satellite operating costs. The Guidance, Navigation, and Control Center (GNCC) at the Goddard Space Flight Center (GSFC) currently sponsors several initiatives associated with the development of advanced spacecraft systems to provide autonomous navigation and control. Autonomous navigation has the potential both to increase spacecraft navigation system performance and to reduce total mission cost. By eliminating the need for routine ground-based orbit determination and special tracking services, autonomous navigation can streamline spacecraft ground systems. Autonomous navigation products can be included in the science telemetry and forwarded directly to the scientific investigators. In addition, autonomous navigation products are available onboard to enable other autonomous capabilities, such as attitude control, maneuver planning and orbit control, and communications signal acquisition. Autonomous navigation is required to support advanced mission concepts such as satellite formation flying. GNCC has successfully developed high-accuracy autonomous navigation systems for near-Earth spacecraft using NASA's space and ground communications systems and the Global Positioning System (GPS). Recently, GNCC has expanded its autonomous navigation initiative to include satellite orbits that are beyond the regime in which use of GPS is possible. Currently, GNCC is assessing the feasibility of using standard spacecraft attitude sensors and communication components to provide autonomous navigation for missions including: libration point, gravity assist, high-Earth, and interplanetary orbits. The concept being evaluated uses a combination of star, Sun, and Earth sensor measurements along with forward-link Doppler measurements from the command link carrier to autonomously estimate the spacecraft's orbit and reference oscillator's frequency. To support autonomous attitude determination and control and maneuver planning and control, the orbit determination accuracy should be on the order of kilometers in position and centimeters per second in velocity. A less accurate solution (one hundred kilometers in position) could be used for acquisition purposes for command and science downloads. This paper provides performance results for both libration point orbiting and high Earth orbiting satellites as a function of sensor measurement accuracy, measurement types, measurement frequency, initial state errors, and dynamic modeling errors.
The research completed for this NASA Graduate Student Research Program Fellowship sought to enhance the current state-of-the-art dynamic models and control laws for Momentum Exchange Electrodynamic Reboost satellite systems by utilizing command generation, specifically Input Shaping. The precise control of tethered spacecraft with flexible appendages is extremely difficult. The complexity is magnified many times when the satellite must interact with other satellites as in a momentum exchange via a tether. The Momentum Exchange Electronic Reboost Tether (MXER) concept encapsulates all of these challenging tasks [l]. Input Shaping is a command generation technique that allows flexible spacecraft to move without inducing residual vibration [2], limit transient deflection [3] and utilize fuel-efficient actuation [4]. Input shaping is implemented by convolving a sequence of impulses, known as the input shaper, with a desired system command to produce a shaped input that is then used to drive the system. This process is demonstrated in Figure 1. The shaped command is then use to drive the system without residual vibration while meeting many other performance specifications. The completed work developed tether control algorithms for retrieval. A simple model of the tether response has been developed and command shaping was implemented to minimize unwanted dynamics. A model of a flexible electrodynamic tether has been developed to investigate the tether s response during reboost. Command shaping techniques have been developed to eliminate the tether oscillations and reduce the tether s deflection to pre-specified levels during reboost. Additionally, a model for the spin-up of a tethered system was developed. This model was used in determining the parameters for optimization the resulting angular velocity.
An overview of the telemetry, command, and data handling features of four spacecraft developed under GSFC management is presented. Two of these spacecraft ATS and SMS, are designed for geostationary orbit; the other two OSO and ERTS, are designed for low earth orbits. The program time spans for these spacecraft are as shown. The programs are seen to be near contemporary, especially in the 1973, 1974 period. All of the spacecraft listed were developed under GSFC control and are thus subject to the standards set forth in the Aerospace Data System Standard developed by GSFC. These standards must be adhered to by all spacecraft programs under GSFC control or utilizing STDN unless waivers have been granted. The standards were developed to maximize the utilization of the large amount of standard equipment at each STDN ground facility. The standards impose bounds on both the command and telemetry formats to be compatible with the STDN ground station unless valid and acceptable reasons are raised to deviate from these restraints.
A coherent uplink array consisting of up to three 34-meter antennas of NASA's Deep Space Network has been developed for the primary purpose of increasing EIRP at the spacecraft. Greater EIRP ensures greater reach, higher uplink data rates for command and configuration control, as well as improved search and recovery capabilities during spacecraft emergencies. It has been conjectured that Doppler-delay radar imaging of lunar targets can be extended to planetary imaging, where the long baseline of the uplink array can provide greater resolution than a single antenna, as well as potentially higher EIRP. However, due to the well known R-4 loss in radar links, imaging of distant planets is a very challenging endeavor, requiring accurate phasing of the Uplink Array antennas, cryogenically cooled low-noise receiver amplifiers, and sophisticated processing of the received data to extract the weak echoes characteristic of planetary radar. This article describes experiments currently under way to image the planets Mercury and Venus, highlights improvements in equipment and techniques, and presents planetary images obtained to date with two 34 meter antennas configured as a coherently phased Uplink Array.
A coherent Uplink Array consisting of two or three 34-meter antennas of NASA's Deep Space Network has been developed for the primary purpose of increasing EIRP at the spacecraft. Greater EIRP ensures greater reach, higher uplink data rates for command and configuration control, as well as improved search and recovery capabilities during spacecraft emergencies. It has been conjectured that Doppler-delay radar imaging of lunar targets can be extended to planetary imaging, where the long baseline of the uplink array can provide greater resolution than a single antenna, as well as potentially higher EIRP. However, due to the well known R4 loss in radar links, imaging of distant planets is a very challenging endeavor, requiring accurate phasing of the Uplink Array antennas, cryogenically cooled low-noise receiver amplifiers, and sophisticated processing of the received data to extract the weak echoes characteristic of planetary radar. This article describes experiments currently under way to image the planets Mercury and Venus, highlights improvements in equipment and techniques, and presents planetary images obtained to date with two 34 meter antennas configured as a coherently phased Uplink Array.