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.
The objectives, functions, and organization of the Deep Space Network are summarized. The Deep Space Instrumentation Facility, the Ground Communications Facility, and the Space Flight Operations Facility are described.
The Deep Space Network (DSN) activities in support of Project Apollo during the period of 1971 and 1972 are reported. Beginning with the Apollo 14 mission and concluding with the Apollo 17 mission, the narrative includes, (1) a mission description, (2) the NASA support requirements placed on the DSN, and, (3) a comprehensive account of the support activities provided by each committed DSN deep space communication station. Associated equipment and activities of the three elements of the DSN (the Deep Space Instrumentation Facility (DSIF), the Space Flight Operations Facility (SFOF), and the Ground Communications Facility (GCF)) used in meeting the radio-metric and telemetry demands of the missions are documented.
The mathematical model considers a large particle (m sub 1), such as a space station, and a smaller particle (m sub 2), connected by an ideal, massless tether, i.e., one incapable of sustaining other than tensile loads. The problem situation described offers a practical solution which should be quite useful in certain space flight operations, especially for the transfer of cargo and personnel and for retrieval and rescue operations. The idea is simple in its application and does not appear to require sophisticated hardware. An appealing advantage is that it is infinitely reusable, i.e., it could be rewound and used over and over again.
Methods for detecting and analyzing biological agents suitable for space flight operations were studied primarily by literature searches which were conducted of cell separation techniques. Detection methods discussed include: photometrometric, electric, radiometric, micrometry, ultrasonic, microscopic, and photographic. A bibliography, and a directory of vendors are included along with an index of commercial hardware.
A sequence of events, occurring over the last 25 years, are described that chronicle the evolution of ion-bombardment electric propulsion technology. Emphasis is placed on the latter phases of this evolution, where special efforts were made to pave the way toward the use of this technology in operational space flight systems. These efforts consisted of a planned program to focus the technology toward its end applications and an organized process that was followed to transfer the technology from the research-technology NASA Center to the user-development NASA Center and its industry team. Major milestones in this evolution, which are described, include the development of thruster technology across a large size range, the successful completion of two space electric rocket tests, SERT I and SERT II, development of power-processing technology for electric propulsion, completion of a program to make the technology ready for flight system development, and finally the technology transfer events.
An infrared imaging photometer employing a monolithic 32 x 32 pixel bismuth doped silicon charge injection device array is described. The device is primarily useful in the 8-13-micron atmospheric window. The detector is sufficiently sensitive to provide good performance on ground-based telescopes and promises to be very good for low background space flight operation.
The Space Flight Operations Center (SFOC) is described with attention given to historical and technical aspects. The SFOC is designed to support each new JPL mission with all of its mission-unique processing as a ready adaptation of some set of baseline capabilities. Another goal of the SFOC is to allow the migration of current older JPL missions from their current systems that use aging and costly hardware and software to newer systems with similar functionality. Upon its completion, the planned support includes both downlink and uplink processing for a projected six mission set.
The Space Flight Operations Center (SFOC) is a generic suite of ground data systems software. One main subsystem of SFOC is the Telemetry Input Subsystem (TIS). Utilizing techniques for the abstract representation of data, the TIS has provided a flexible software base that can be used as a baseline for multiple spacecraft missions.
An overview of a self contained Direct Energy Transfer (DET) Power System which was developed to provide power to the Long Duration Exposure Facility (LDEF) Heat Pipe Experiment Package (HEPP) Experiment. A brief synopsis of the flight characteristics of the power system are presented to illustrate the system's capability to function successfully in a low Earth orbit (LEO) space environment. The successful space flight operations of the battery, solar arrays, and power system electronics during the flight period of almost six years (approximately 32,000 LEO cycles) are discussed.
The Consultative Committee for Space Data Systems (CCSDS) has adopted three Recommendations dealing with telemetry for conventional missions: Packet Telemetry, Telemetry Channel Coding and Time Code Formats. The currently flying JPL spacecraft were designed prior to the adoption of these Recommendations. Future JPL missions will be compatible, as will the Deep Space Network and Space Flight Operations Center. This paper discusses ways in which application of the Recommendations causes or allows functions to be done differently from previous JPL projects, including the impact on timing and on telemetry adaptability.
The planetary spacecraft mission OPS as applied to SHARP is studied. Knowledge systems involved in this study are detailed. SHARP development task and Voyager telecom link analysis were examined. It was concluded that artificial intelligence has a proven capability to deliver useful functions in a real time space flight operations environment. SHARP has precipitated major change in acceptance of automation at JPL. The potential payoff from automation using AI is substantial. SHARP, and other AI technology is being transferred into systems in development including mission operations automation, science data systems, and infrastructure applications.
In the early days of JPL's solar system exploration, each spacecraft mission required its own dedicated data system with all software applications written in the mainframe's native assembly language. Although these early telemetry processing systems were a triumph of engineering in their day, since that time the computer industry has advanced to the point where it is now advantageous to replace these systems with more modern technology. The Space Flight Operations Center (SFOC) Prototype group was established in 1985 as a workstation and software laboratory. The charter of the lab was to determine if it was possible to construct a multimission telemetry processing system using commercial, off-the-shelf computers that communicated via networks. The staff of the lab mirrored that of a typical skunk works operation -- a small, multi-disciplinary team with a great deal of autonomy that could get complex tasks done quickly. In an effort to determine which approaches would be useful, the prototype group experimented with all types of operating systems, inter-process communication mechanisms, network protocols, packet size parameters. Out of that pioneering work came the confidence that a multi-mission telemetry processing system could be built using high-level languages running in a heterogeneous, networked workstation environment. Experience revealed that the operating systems on all nodes should be similar (i.e., all VMS or all PC-DOS or all UNIX), and that a unique Data Transport Subsystem tool needed to be built to address the incompatibilities of network standards, byte ordering, and socket buffering. The advantages of building a telemetry processing system based on emerging industry standards were numerous: by employing these standards, we would no longer be locked into a single vendor. When new technology came to market which offered ten times the performance at one eighth the cost, it would be possible to attach the new machine to the network, re-compile the application code, and run. In addition, we would no longer be plagued with lack of manufacturer support when we encountered obscure bugs. And maybe, hopefully, the eternal elusive goal of software portability across different vendors' platforms would finally be available. Some highlights of our prototyping efforts are described.
The Space Flight Operations Center inaugurated the concept of a central data repository for spacecraft data and the distribution of computing power to the end users for that data's analysis at the Jet Propulsion Laboratory. The Advanced Multimission Operations System is continuing the evolution of this concept as new technologies emerge. Constant improvements in data management tools, data visualization, and hardware lead to ever expanding ideas for improving the analysis of spacecraft health in an era of budget constrained mission operations systems. The foundation of this evolution, its history, and its current plans will be discussed.
This analysis defines a complete set of ground support functions based on those practiced in real space flight operations during the on-orbit phase of a mission. These functions are mapped against ground support functions currently in use by NASA and DOD. Software components to provide these functions can be hosted on RISC-based work stations and integrated to provide a modular, integrated ground support system. Such modular systems can be configured to provide as much ground support functionality as desired. This approach to ground systems has been widely proposed and prototyped both by government institutions and commercial vendors. The combined set of ground support functions we describe can be used as a standard to evaluate candidate ground systems. This approach has also been used to develop a prototype of a modular, loosely-integrated ground support system, which is discussed briefly. A crucial benefit to a potential user is that all the components are flight-qualified, thus giving high confidence in their accuracy and reliability.
The film describes the Lunar Orbiter's mission to photograph landing areas on the Moon. The Orbiter will be launched from Cape Kennedy using an Atlas Agena booster rocket. Once it is boosted in a trajectory toward the Moon, the Orbiter will deploy two-way earth communication antennas and solar panels for electricity. Attitude control jets will position the solar panels toward the sun and a tracker for a fix on its navigational star. The Orbiter will be put in an off-center orbit around the Moon where it will circle from four to six days. Scientists on Earth will study the effects of the Moon's gravitational field on the spacecraft, then the orbit will be lowered to 28 miles above the Moon's surface. Engineers will control the Orbiter manually or by computer to activate two camera lenses. The cameras will capture pictures of 12,000 square miles of lunar surface in 25 and 400 square mile increments. Pictures will be sent back to Earth using solar power to transmit electrical signals. The signals will be received by antennas at Goldstone, CA, and in Australia and Spain. Incoming photographic data will be electronically converted and processed to produce large-scale photographic images. The mission will be directed from the Space Flight Operations Facility in Pasadena, CA by NASA and Boeing engineers. After the photographic mission, the Orbiter will continue to circle the Moon providing information about micrometeoroids and radiation in the vicinity.
NASA's Human Research Program Integrated Research Plan (HRP-47065) serves as a road-map identifying critically needed information for future space flight operations (Lunar, Martian). VO2max (often termed aerobic capacity) reflects the maximum rate at which oxygen can be taken up and utilized by the body during exercise. Lack of in-flight and immediate postflight VO2max measurements was one area identified as a concern. The risk associated with not knowing this information is: Unnecessary Operational Limitations due to Inaccurate Assessment of Cardiovascular Performance (HRP-47065).
During the 1980s, a community of artificial intelligence researchers became interested in formalizing problem solving methods as part of an effort called "second generation expert systems" (2nd GES). How do the motivations and results of this research relate to building tools for the workplace today? We provide an historical review of how the theory of expertise has developed, a progress report on a tool for designing and implementing model-based automation (Brahms), and a concrete example how we apply 2nd GES concepts today in an agent-based system for space flight operations (OCAMS). Brahms incorporates an ontology for modeling work practices, what people are doing in the course of a day, characterized as "activities." OCAMS was developed using a simulation-to-implementation methodology, in which a prototype tool was embedded in a simulation of future work practices. OCAMS uses model-based methods to interactively plan its actions and keep track of the work to be done. The problem solving methods of practice are interactive, employing reasoning for and through action in the real world. Analogously, it is as if a medical expert system were charged not just with interpreting culture results, but actually interacting with a patient. Our perspective shifts from building a "problem solving" (expert) system to building an actor in the world. The reusable components in work system designs include entire "problem solvers" (e.g., a planning subsystem), interoperability frameworks, and workflow agents that use and revise models dynamically in a network of people and tools. Consequently, the research focus shifts so "problem solving methods" include ways of knowing that models do not fit the world, and ways of interacting with other agents and people to gain or verify information and (ultimately) adapt rules and procedures to resolve problematic situations.
The Work Coordination Engine (WCE) is a Java application integrated into the Service Management Database (SMDB), which coordinates the dispatching and monitoring of a work order system. WCE de-queues work orders from SMDB and orchestrates the dispatching of work to a registered set of software worker applications distributed over a set of local, or remote, heterogeneous computing systems. WCE monitors the execution of work orders once dispatched, and accepts the results of the work order by storing to the SMDB persistent store. The software leverages the use of a relational database, Java Messaging System (JMS), and Web Services using Simple Object Access Protocol (SOAP) technologies to implement an efficient work-order dispatching mechanism capable of coordinating the work of multiple computer servers on various platforms working concurrently on different, or similar, types of data or algorithmic processing. Existing (legacy) applications can be wrapped with a proxy object so that no changes to the application are needed to make them available for integration into the work order system as "workers." WCE automatically reschedules work orders that fail to be executed by one server to a different server if available. From initiation to completion, the system manages the execution state of work orders and workers via a well-defined set of events, states, and actions. It allows for configurable work-order execution timeouts by work-order type. This innovation eliminates a current processing bottleneck by providing a highly scalable, distributed work-order system used to quickly generate products needed by the Deep Space Network (DSN) to support space flight operations. WCE is driven by asynchronous messages delivered via JMS indicating the availability of new work or workers. It runs completely unattended in support of the lights-out operations concept in the DSN.