Expecting the Unexpected: Radiation Hardened Software

NASA Technical Reports Server (NTRS)

Penix, John; Mehlitz, Peter C.

2005-01-01

Radiation induced Single Event Effects (SEEs) are a serious problem for spacecraft flight software, potentially leading to a complete loss of mission. Conventional risk mitigation has been focused on hardware, leading to slow, expensive and outdated on-board computing devices, increased power consumption and launch mass. Our approach is to look at SEEs from a software perspective, and to explicitly design flight software so that it can detect and correct the majority of SEES. Radiation hardened flight software will reduce the significant residual residual risk for critical missions and flight phases, and enable more use of inexpensive and fast COTS hardware.

Using formal specification in the Guidance and Control Software (GCS) experiment. Formal design and verification technology for life critical systems

NASA Technical Reports Server (NTRS)

Weber, Doug; Jamsek, Damir

1994-01-01

The goal of this task was to investigate how formal methods could be incorporated into a software engineering process for flight-control systems under DO-178B and to demonstrate that process by developing a formal specification for NASA's Guidance and Controls Software (GCS) Experiment. GCS is software to control the descent of a spacecraft onto a planet's surface. The GCS example is simplified from a real example spacecraft, but exhibits the characteristics of realistic spacecraft control software. The formal specification is written in Larch.

Titan/Centaur D-1T TC-2, Helios A flight data report. [of space missions

NASA Technical Reports Server (NTRS)

1975-01-01

Background data of spacecraft launching and flight are presented. A system analysis of the space vehicles is included, specifically on: (1) electronic equipment, (2) hydraulic equipment, (3) telemetry, (4) propulsion systems, (5) software (computers), and (6) guidance. Spacecraft and launch vehicle configurations are shown and described.

Systems Architecture for Fully Autonomous Space Missions

NASA Technical Reports Server (NTRS)

Esper, Jamie; Schnurr, R.; VanSteenberg, M.; Brumfield, Mark (Technical Monitor)

2002-01-01

The NASA Goddard Space Flight Center is working to develop a revolutionary new system architecture concept in support of fully autonomous missions. As part of GSFC's contribution to the New Millenium Program (NMP) Space Technology 7 Autonomy and on-Board Processing (ST7-A) Concept Definition Study, the system incorporates the latest commercial Internet and software development ideas and extends them into NASA ground and space segment architectures. The unique challenges facing the exploration of remote and inaccessible locales and the need to incorporate corresponding autonomy technologies within reasonable cost necessitate the re-thinking of traditional mission architectures. A measure of the resiliency of this architecture in its application to a broad range of future autonomy missions will depend on its effectiveness in leveraging from commercial tools developed for the personal computer and Internet markets. Specialized test stations and supporting software come to past as spacecraft take advantage of the extensive tools and research investments of billion-dollar commercial ventures. The projected improvements of the Internet and supporting infrastructure go hand-in-hand with market pressures that provide continuity in research. By taking advantage of consumer-oriented methods and processes, space-flight missions will continue to leverage on investments tailored to provide better services at reduced cost. The application of ground and space segment architectures each based on Local Area Networks (LAN), the use of personal computer-based operating systems, and the execution of activities and operations through a Wide Area Network (Internet) enable a revolution in spacecraft mission formulation, implementation, and flight operations. Hardware and software design, development, integration, test, and flight operations are all tied-in closely to a common thread that enables the smooth transitioning between program phases. The application of commercial software development techniques lays the foundation for delivery of product-oriented flight software modules and models. Software can then be readily applied to support the on-board autonomy required for mission self-management. An on-board intelligent system, based on advanced scripting languages, facilitates the mission autonomy required to offload ground system resources, and enables the spacecraft to manage itself safely through an efficient and effective process of reactive planning, science data acquisition, synthesis, and transmission to the ground. Autonomous ground systems in turn coordinate and support schedule contact times with the spacecraft. Specific autonomy software modules on-board include mission and science planners, instrument and subsystem control, and fault tolerance response software, all residing within a distributed computing environment supported through the flight LAN. Autonomy also requires the minimization of human intervention between users on the ground and the spacecraft, and hence calls for the elimination of the traditional operations control center as a funnel for data manipulation. Basic goal-oriented commands are sent directly from the user to the spacecraft through a distributed internet-based payload operations "center". The ensuing architecture calls for the use of spacecraft as point extensions on the Internet. This paper will detail the system architecture implementation chosen to enable cost-effective autonomous missions with applicability to a broad range of conditions. It will define the structure needed for implementation of such missions, including software and hardware infrastructures. The overall architecture is then laid out as a common thread in the mission life cycle from formulation through implementation and flight operations.

Cassini Attitude Control Operations Flight Rules and How They are Enforced

NASA Technical Reports Server (NTRS)

Burk, Thomas; Bates, David

2008-01-01

The Cassini spacecraft was launched on October 15, 1997 and arrived at Saturn on June 30, 2004. It has performed detailed observations and remote sensing of Saturn, its rings, and its satellites since that time. Cassini deployed the European-built Huygens probe which descended through the Titan atmosphere and landed on its surface on January 14, 2005. Operating the Cassini spacecraft is a complex scientific, engineering, and management job. In order to safely operate the spacecraft, a large number of flight rules were developed. These flight rules must be enforced throughout the lifetime of the Cassini spacecraft. Flight rules are defined as any operational limitation imposed by the spacecraft system design, hardware, and software, violation of which would result in spacecraft damage, loss of consumables, loss of mission objectives, loss and/or degradation of science, and less than optimal performance. Flight rules require clear description and rationale. Detailed automated methods have been developed to insure the spacecraft is continuously operated within these flight rules. An overview of all the flight rules allocated to the Cassini Attitude Control and Articulation Subsystem and how they are enforced is presented in this paper.

The Core Flight System (cFS) Community: Providing Low Cost Solutions for Small Spacecraft

NASA Technical Reports Server (NTRS)

McComas, David; Wilmot, Jonathan; Cudmore, Alan

2016-01-01

In February 2015 the NASA Goddard Space Flight Center (GSFC) completed the open source release of the entire Core Flight Software (cFS) suite. After the open source release a multi-NASA center Configuration Control Board (CCB) was established that has managed multiple cFS product releases. The cFS was developed and is being maintained in compliance with the NASA Class B software development process requirements and the open source release includes all Class B artifacts. The cFS is currently running on three operational science spacecraft and is being used on multiple spacecraft and instrument development efforts. While the cFS itself is a viable flight software (FSW) solution, we have discovered that the cFS community is a continuous source of innovation and growth that provides products and tools that serve the entire FSW lifecycle and future mission needs. This paper summarizes the current state of the cFS community, the key FSW technologies being pursued, the development/verification tools and opportunities for the small satellite community to become engaged. The cFS is a proven high quality and cost-effective solution for small satellites with constrained budgets.

SDO FlatSat Facility

NASA Technical Reports Server (NTRS)

Amason, David L.

2008-01-01

The goal of the Solar Dynamics Observatory (SDO) is to understand and, ideally, predict the solar variations that influence life and society. It's instruments will measure the properties of the Sun and will take hifh definition images of the Sun every few seconds, all day every day. The FlatSat is a high fidelity electrical and functional representation of the SDO spacecraft bus. It is a high fidelity test bed for Integration & Test (I & T), flight software, and flight operations. For I & T purposes FlatSat will be a driver to development and dry run electrical integration procedures, STOL test procedures, page displays, and the command and telemetry database. FlatSat will also serve as a platform for flight software acceptance and systems testing for the flight software system component including the spacecraft main processors, power supply electronics, attitude control electronic, gimbal control electrons and the S-band communications card. FlatSat will also benefit the flight operations team through post-launch flight software code and table update development and verification and verification of new and updated flight operations products. This document highlights the benefits of FlatSat; describes the building of FlatSat; provides FlatSat facility requirements, access roles and responsibilities; and, and discusses FlatSat mechanical and electrical integration and functional testing.

Atmosphere Explorer control system software (version 1.0)

NASA Technical Reports Server (NTRS)

Villasenor, A.

1972-01-01

The basic design is described of the Atmosphere Explorer Control System (AECS) software used in the testing, integration, and flight contol of the AE spacecraft and experiments. The software performs several vital functions, such as issuing commands to the spacecraft and experiments, receiving and processing telemetry data, and allowing for extensive data processing by experiment analysis programs. The major processing sections are: executive control section, telemetry decommutation section, command generation section, and utility section.

Flight Software for the LADEE Mission

NASA Technical Reports Server (NTRS)

Cannon, Howard N.

2015-01-01

The Lunar Atmosphere and Dust Environment Explorer (LADEE) spacecraft was launched on September 6, 2013, and completed its mission on April 17, 2014 with a directed impact to the Lunar Surface. Its primary goals were to examine the lunar atmosphere, measure lunar dust, and to demonstrate high rate laser communications. The LADEE mission was a resounding success, achieving all mission objectives, much of which can be attributed to careful planning and preparation. This paper discusses some of the highlights from the mission, and then discusses the techniques used for developing the onboard Flight Software. A large emphasis for the Flight Software was to develop it within tight schedule and cost constraints. To accomplish this, the Flight Software team leveraged heritage software, used model based development techniques, and utilized an automated test infrastructure. This resulted in the software being delivered on time and within budget. The resulting software was able to meet all system requirements, and had very problems in flight.

Autonomous Performance Monitoring System: Monitoring and Self-Tuning (MAST)

NASA Technical Reports Server (NTRS)

Peterson, Chariya; Ziyad, Nigel A.

2000-01-01

Maintaining the long-term performance of software onboard a spacecraft can be a major factor in the cost of operations. In particular, the task of controlling and maintaining a future mission of distributed spacecraft will undoubtedly pose a great challenge, since the complexity of multiple spacecraft flying in formation grows rapidly as the number of spacecraft in the formation increases. Eventually, new approaches will be required in developing viable control systems that can handle the complexity of the data and that are flexible, reliable and efficient. In this paper we propose a methodology that aims to maintain the accuracy of flight software, while reducing the computational complexity of software tuning tasks. The proposed Monitoring and Self-Tuning (MAST) method consists of two parts: a flight software monitoring algorithm and a tuning algorithm. The dependency on the software being monitored is mostly contained in the monitoring process, while the tuning process is a generic algorithm independent of the detailed knowledge on the software. This architecture will enable MAST to be applicable to different onboard software controlling various dynamics of the spacecraft, such as attitude self-calibration, and formation control. An advantage of MAST over conventional techniques such as filter or batch least square is that the tuning algorithm uses machine learning approach to handle uncertainty in the problem domain, resulting in reducing over all computational complexity. The underlying concept of this technique is a reinforcement learning scheme based on cumulative probability generated by the historical performance of the system. The success of MAST will depend heavily on the reinforcement scheme used in the tuning algorithm, which guarantees the tuning solutions exist.

Avoiding Human Error in Mission Operations: Cassini Flight Experience

NASA Technical Reports Server (NTRS)

Burk, Thomas A.

2012-01-01

Operating spacecraft is a never-ending challenge and the risk of human error is ever- present. Many missions have been significantly affected by human error on the part of ground controllers. The Cassini mission at Saturn has not been immune to human error, but Cassini operations engineers use tools and follow processes that find and correct most human errors before they reach the spacecraft. What is needed are skilled engineers with good technical knowledge, good interpersonal communications, quality ground software, regular peer reviews, up-to-date procedures, as well as careful attention to detail and the discipline to test and verify all commands that will be sent to the spacecraft. Two areas of special concern are changes to flight software and response to in-flight anomalies. The Cassini team has a lot of practical experience in all these areas and they have found that well-trained engineers with good tools who follow clear procedures can catch most errors before they get into command sequences to be sent to the spacecraft. Finally, having a robust and fault-tolerant spacecraft that allows ground controllers excellent visibility of its condition is the most important way to ensure human error does not compromise the mission.

Lessons learned in creating spacecraft computer systems: Implications for using Ada (R) for the space station

NASA Technical Reports Server (NTRS)

Tomayko, James E.

1986-01-01

Twenty-five years of spacecraft onboard computer development have resulted in a better understanding of the requirements for effective, efficient, and fault tolerant flight computer systems. Lessons from eight flight programs (Gemini, Apollo, Skylab, Shuttle, Mariner, Voyager, and Galileo) and three reserach programs (digital fly-by-wire, STAR, and the Unified Data System) are useful in projecting the computer hardware configuration of the Space Station and the ways in which the Ada programming language will enhance the development of the necessary software. The evolution of hardware technology, fault protection methods, and software architectures used in space flight in order to provide insight into the pending development of such items for the Space Station are reviewed.

Modular Software for Spacecraft Navigation Using the Global Positioning System (GPS)

NASA Technical Reports Server (NTRS)

Truong, S. H.; Hartman, K. R.; Weidow, D. A.; Berry, D. L.; Oza, D. H.; Long, A. C.; Joyce, E.; Steger, W. L.

1996-01-01

The Goddard Space Flight Center Flight Dynamics and Mission Operations Divisions have jointly investigated the feasibility of engineering modular Global Positioning SYSTEM (GPS) navigation software to support both real time flight and ground postprocessing configurations. The goals of this effort are to define standard GPS data interfaces and to engineer standard, reusable navigation software components that can be used to build a broad range of GPS navigation support applications. The paper discusses the GPS modular software (GMOD) system and operations concepts, major requirements, candidate software architecture, feasibility assessment and recommended software interface standards. In additon, ongoing efforts to broaden the scope of the initial study and to develop modular software to support autonomous navigation using GPS are addressed,

The NASA Mission Operations and Control Architecture Program

NASA Technical Reports Server (NTRS)

Ondrus, Paul J.; Carper, Richard D.; Jeffries, Alan J.

1994-01-01

The conflict between increases in space mission complexity and rapidly declining space mission budgets has created strong pressures to radically reduce the costs of designing and operating spacecraft. A key approach to achieving such reductions is through reducing the development and operations costs of the supporting mission operations systems. One of the efforts which the Communications and Data Systems Division at NASA Headquarters is using to meet this challenge is the Mission Operations Control Architecture (MOCA) project. Technical direction of this effort has been delegated to the Mission Operations Division (MOD) of the Goddard Space Flight Center (GSFC). MOCA is to develop a mission control and data acquisition architecture, and supporting standards, to guide the development of future spacecraft and mission control facilities at GSFC. The architecture will reduce the need for around-the-clock operations staffing, obtain a high level of reuse of flight and ground software elements from mission to mission, and increase overall system flexibility by enabling the migration of appropriate functions from the ground to the spacecraft. The end results are to be an established way of designing the spacecraft-ground system interface for GSFC's in-house developed spacecraft, and a specification of the end to end spacecraft control process, including data structures, interfaces, and protocols, suitable for inclusion in solicitation documents for future flight spacecraft. A flight software kernel may be developed and maintained in a condition that it can be offered as Government Furnished Equipment in solicitations. This paper describes the MOCA project, its current status, and the results to date.

Schema for Spacecraft-Command Dictionary

NASA Technical Reports Server (NTRS)

Laubach, Sharon; Garcia, Celina; Maxwell, Scott; Wright, Jesse

2008-01-01

An Extensible Markup Language (XML) schema was developed as a means of defining and describing a structure for capturing spacecraft command- definition and tracking information in a single location in a form readable by both engineers and software used to generate software for flight and ground systems. A structure defined within this schema is then used as the basis for creating an XML file that contains command definitions.

Obtaining the Greatest Scientific Benefit from Observational Platforms by Consideration of the Relative Benefit of Observations

NASA Technical Reports Server (NTRS)

Chelberg, David; Drews, Frank; Fleeman, David; Welch, Lonnie; Marquart, Jane; Pfarr, Barbara

2003-01-01

One of the current trends in spacecraft software design is to increase the autonomy of onboard flight and science software. This is especially true when real-time observations may affect the observation schedule of a mission. For many science missions, such as those conducted by the Swift Burst Alert Telescope, the ability of the spacecraft to autonomously respond in real-time to unpredicted science events is crucial for mission success. We apply utility theory within resource management middleware to optimize the real-time performance of application software and achieve maximum system level benefit. We then explore how this methodology can be extended to manage both software and observational resources onboard a spacecraft to achieve the best possible observations.

Test Telemetry And Command System (TTACS)

NASA Technical Reports Server (NTRS)

Fogel, Alvin J.

1994-01-01

The Jet Propulsion Laboratory has developed a multimission Test Telemetry and Command System (TTACS) which provides a multimission telemetry and command data system in a spacecraft test environment. TTACS reuses, in the spacecraft test environment, components of the same data system used for flight operations; no new software is developed for the spacecraft test environment. Additionally, the TTACS is transportable to any spacecraft test site, including the launch site. The TTACS is currently operational in the Galileo spacecraft testbed; it is also being provided to support the Cassini and Mars Surveyor Program projects. Minimal personnel data system training is required in the transition from pre-launch spacecraft test to post-launch flight operations since test personnel are already familiar with the data system's operation. Additionally, data system components, e.g. data display, can be reused to support spacecraft software development; and the same data system components will again be reused during the spacecraft integration and system test phases. TTACS usage also results in early availability of spacecraft data to data system development and, as a result, early data system development feedback to spacecraft system developers. The TTACS consists of a multimission spacecraft support equipment interface and components of the multimission telemetry and command software adapted for a specific project. The TTACS interfaces to the spacecraft, e.g., Command Data System (CDS), support equipment. The TTACS telemetry interface to the CDS support equipment performs serial (RS-422)-to-ethernet conversion at rates between 1 bps and 1 mbps, telemetry data blocking and header generation, guaranteed data transmission to the telemetry data system, and graphical downlink routing summary and control. The TTACS command interface to the CDS support equipment is nominally a command file transferred in non-real-time via ethernet. The CDS support equipment is responsible for metering the commands to the CDS; additionally for Galileo, TTACS includes a real-time-interface to the CDS support equipment. The TTACS provides the basic functionality of the multimission telemetry and command data system used during flight operations. TTACS telemetry capabilities include frame synchronization, Reed-Solomon decoding, packet extraction and channelization, and data storage/query. Multimission data display capabilities are also available. TTACS command capabilities include command generation verification, and storage.

How Emerging Technologies are Changing the Rules of Spacecraft Ground Support

NASA Technical Reports Server (NTRS)

Boland, Dillard; Steger, Warren; Weidow, David; Yakstis, Lou

1996-01-01

As part of its effort to develop the flight dynamics distributed system (FDDS), NASA established a program for the continual monitoring of the developments in computer and software technologies, and for assessing the significance of constructing and operating spacecraft ground data systems. In relation to this, technology trends in the computing industry are reviewed, exploring their significance for the spacecraft ground support industry. The technologies considered are: hardware; object computing; Internet; automation, and software development. The ways in which these technologies have affected the industry are considered.

Development of the functional simulator for the Galileo attitude and articulation control system

NASA Technical Reports Server (NTRS)

Namiri, M. K.

1983-01-01

A simulation program for verifying and checking the performance of the Galileo Spacecraft's Attitude and Articulation Control Subsystem's (AACS) flight software is discussed. The program, which is called Functional Simulator (FUNSIM), provides a simple method of interfacing user-supplied mathematical models coded in FORTRAN which describes spacecraft dynamics, sensors, and actuators; this is done with the AACS flight software, coded in HAL/S (High-level Advanced Language/Shuttle). It is thus able to simulate the AACS flight software accurately to the HAL/S statement level in the environment of a mainframe computer system. FUNSIM also has a command and data subsystem (CDS) simulator. It is noted that the input/output data and timing are simulated with the same precision as the flight microprocessor. FUNSIM uses a variable stepsize numerical integration algorithm complete with individual error bound control on the state variable to solve the equations of motion. The program has been designed to provide both line printer and matrix dot plotting of the variables requested in the run section and to provide error diagnostics.

Modular, Autonomous Command and Data Handling Software with Built-In Simulation and Test

NASA Technical Reports Server (NTRS)

Cuseo, John

2012-01-01

The spacecraft system that plays the greatest role throughout the program lifecycle is the Command and Data Handling System (C&DH), along with the associated algorithms and software. The C&DH takes on this role as cost driver because it is the brains of the spacecraft and is the element of the system that is primarily responsible for the integration and interoperability of all spacecraft subsystems. During design and development, many activities associated with mission design, system engineering, and subsystem development result in products that are directly supported by the C&DH, such as interfaces, algorithms, flight software (FSW), and parameter sets. A modular system architecture has been developed that provides a means for rapid spacecraft assembly, test, and integration. This modular C&DH software architecture, which can be targeted and adapted to a wide variety of spacecraft architectures, payloads, and mission requirements, eliminates the current practice of rewriting the spacecraft software and test environment for every mission. This software allows missionspecific software and algorithms to be rapidly integrated and tested, significantly decreasing time involved in the software development cycle. Additionally, the FSW includes an Onboard Dynamic Simulation System (ODySSy) that allows the C&DH software to support rapid integration and test. With this solution, the C&DH software capabilities will encompass all phases of the spacecraft lifecycle. ODySSy is an on-board simulation capability built directly into the FSW that provides dynamic built-in test capabilities as soon as the FSW image is loaded onto the processor. It includes a six-degrees- of-freedom, high-fidelity simulation that allows complete closed-loop and hardware-in-the-loop testing of a spacecraft in a ground processing environment without any additional external stimuli. ODySSy can intercept and modify sensor inputs using mathematical sensor models, and can intercept and respond to actuator commands. ODySSy integration is unique in that it allows testing of actual mission sequences on the flight vehicle while the spacecraft is in various stages of assembly, test, and launch operations all without any external support equipment or simulators. The ODySSy component of the FSW significantly decreases the time required for integration and test by providing an automated, standardized, and modular approach to integrated avionics and component interface and functional verification. ODySSy further provides the capability for on-orbit support in the form of autonomous mission planning and fault protection.

Lessons Learned from Autonomous Sciencecraft Experiment

NASA Technical Reports Server (NTRS)

Chien, Steve A.; Sherwood, Rob; Tran, Daniel; Cichy, Benjamin; Rabideau, Gregg; Castano, Rebecca; Davies, Ashley; Mandl, Dan; Frye, Stuart; Trout, Bruce;

Pi-Sat: A Low Cost Small Satellite and Distributed Spacecraft Mission System Test Platform

NASA Technical Reports Server (NTRS)

Cudmore, Alan

2015-01-01

Current technology and budget trends indicate a shift in satellite architectures from large, expensive single satellite missions, to small, low cost distributed spacecraft missions. At the center of this shift is the SmallSatCubesat architecture. The primary goal of the Pi-Sat project is to create a low cost, and easy to use Distributed Spacecraft Mission (DSM) test bed to facilitate the research and development of next-generation DSM technologies and concepts. This test bed also serves as a realistic software development platform for Small Satellite and Cubesat architectures. The Pi-Sat is based on the popular $35 Raspberry Pi single board computer featuring a 700Mhz ARM processor, 512MB of RAM, a flash memory card, and a wealth of IO options. The Raspberry Pi runs the Linux operating system and can easily run Code 582s Core Flight System flight software architecture. The low cost and high availability of the Raspberry Pi make it an ideal platform for a Distributed Spacecraft Mission and Cubesat software development. The Pi-Sat models currently include a Pi-Sat 1U Cube, a Pi-Sat Wireless Node, and a Pi-Sat Cubesat processor card.The Pi-Sat project takes advantage of many popular trends in the Maker community including low cost electronics, 3d printing, and rapid prototyping in order to provide a realistic platform for flight software testing, training, and technology development. The Pi-Sat has also provided fantastic hands on training opportunities for NASA summer interns and Pathways students.

Galileo spacecraft autonomous attitude determination using a V-slit star scanner

NASA Technical Reports Server (NTRS)

Mobasser, Sohrab; Lin, Shuh-Ren

1991-01-01

The autonomous attitude determination system of Galileo spacecraft, consisting of a radiation hardened star scanner and a processing algorithm is presented. The algorithm applying to this system are the sequential star identification and attitude estimation. The star scanner model is reviewed in detail and the flight software parameters that must be updated frequently during flight, due to degradation of the scanner response and the star background change are identified.

Program Aids Design Of Fluid-Circulating Systems

NASA Technical Reports Server (NTRS)

Bacskay, Allen; Dalee, Robert

1992-01-01

Computer Aided Systems Engineering and Analysis (CASE/A) program is interactive software tool for trade study and analysis, designed to increase productivity during all phases of systems engineering. Graphics-based command-driven software package provides user-friendly computing environment in which engineer analyzes performance and interface characteristics of ECLS/ATC system. Useful during all phases of spacecraft-design program, from initial conceptual design trade studies to actual flight, including pre-flight prediction and in-flight analysis of anomalies. Written in FORTRAN 77.

IUS/TUG orbital operations and mission support study. Volume 4: Project planning data

NASA Technical Reports Server (NTRS)

1975-01-01

Planning data are presented for the development phases of interim upper stage (IUS) and tug systems. Major project planning requirements, major event schedules, milestones, system development and operations process networks, and relevant support research and technology requirements are included. Topics discussed include: IUS flight software; tug flight software; IUS/tug ground control center facilities, personnel, data systems, software, and equipment; IUS mission events; tug mission events; tug/spacecraft rendezvous and docking; tug/orbiter operations interface, and IUS/orbiter operations interface.

Landsat-7 Simulation and Testing Environments

NASA Technical Reports Server (NTRS)

Holmes, E.; Ha, K.; Hawkins, K.; Lombardo, J.; Ram, M.; Sabelhaus, P.; Scott, S.; Phillips, R.

1999-01-01

A spacecraft Attitude Control and Determination Subsystem (ACDS) is heavily dependent upon simulation throughout its entire development, implementation and ground test cycle. Engineering simulation tools are typically developed to design and analyze control systems to validate the design and software simulation tools are required to qualify the flight software. However, the need for simulation does not end here. Operating the ACDS of a spacecraft on the ground requires the simulation of spacecraft dynamics, disturbance modeling and celestial body motion. Sensor data must also be simulated and substituted for actual sensor data on the ground so that the spacecraft will respond by sending commands to the actuators as they will on orbit. And finally, the simulators is the primary training tool and test-bed for the Flight Operations Team. In this paper various ACDS simulation, developed for or used by the Landsat 7 project will be described. The paper will include a description of each tool, its unique attributes, and its role in the overall development and testing of the ACDS. Finally, a section is included which discusses how the coordinated use of these simulation tools can maximize the probability of uncovering software, hardware and operations errors during the ground test process.

REACH: Real-Time Data Awareness in Multi-Spacecraft Missions

NASA Technical Reports Server (NTRS)

Maks, Lori; Coleman, Jason; Hennessy, Joseph F. (Technical Monitor)

2002-01-01

NASA's Advanced Architectures and Automation Branch at the Goddard Space Flight Center (Code 588) saw the potential to reduce the cost of constellation missions by creating new user interfaces to the ground system health-and-safety data. The goal is to enable a small Flight Operations Team (FOT) to remain aware and responsive to the increased amount of ground system information in a multi-spacecraft environment. Rather than abandon the tried and true, these interfaces were developed to run alongside existing ground system software to provide additional support to the FOT. These new user interfaces have been combined in a tool called REACH. REACH-the Real-time Evaluation and Analysis of Consolidated Health-is a software product that uses advanced visualization techniques to make spacecraft anomalies easy to spot, no matter how many spacecraft are in the constellation. REACH reads numerous real-time streams of data from the ground system(s) and displays synthesized information to the FOT such that anomalies are easy to pick out and investigate.

Development of Autonomous Aerobraking - Phase 2

NASA Technical Reports Server (NTRS)

Murri, Daniel G.

2013-01-01

Phase 1 of the Development of Autonomous Aerobraking (AA) Assessment investigated the technical capability of transferring the processes of aerobraking maneuver (ABM) decision-making (currently performed on the ground by an extensive workforce and communicated to the spacecraft via the deep space network) to an efficient flight software algorithm onboard the spacecraft. This document describes Phase 2 of this study, which was a 12-month effort to improve and rigorously test the AA Development Software developed in Phase 1. Aerobraking maneuver; Autonomous Aerobraking; Autonomous Aerobraking Development Software; Deep Space Network; NASA Engineering and Safety Center

Knowledge Acquisition for the Onboard Planner of an Autonomous Spacecraft

NASA Technical Reports Server (NTRS)

Muscettola, Nicola; Rajan, Kanna

1997-01-01

This paper discusses the knowledge acquisition issues involved in transitioning their novel technology in to space flight software, developing the planer in the context of a large software projet and completing the work under a compressed development schedule.

Automated Flight Dynamics Product Generation for the EOS AM-1 Spacecraft

NASA Technical Reports Server (NTRS)

Matusow, Carla

1999-01-01

As part of NASA's Earth Science Enterprise, the Earth Observing System (EOS) AM-1 spacecraft is designed to monitor long-term, global, environmental changes. Because of the complexity of the AM-1 spacecraft, the mission operations center requires more than 80 distinct flight dynamics products (reports). To create these products, the AM-1 Flight Dynamics Team (FDT) will use a combination of modified commercial software packages (e.g., Analytical Graphic's Satellite ToolKit) and NASA-developed software applications. While providing the most cost-effective solution to meeting the mission requirements, the integration of these software applications raises several operational concerns: (1) Routine product generation requires knowledge of multiple applications executing on variety of hardware platforms. (2) Generating products is a highly interactive process requiring a user to interact with each application multiple times to generate each product. (3) Routine product generation requires several hours to complete. (4) User interaction with each application introduces the potential for errors, since users are required to manually enter filenames and input parameters as well as run applications in the correct sequence. Generating products requires some level of flight dynamics expertise to determine the appropriate inputs and sequencing. To address these issues, the FDT developed an automation software tool called AutoProducts, which runs on a single hardware platform and provides all necessary coordination and communication among the various flight dynamics software applications. AutoProducts, autonomously retrieves necessary files, sequences and executes applications with correct input parameters, and deliver the final flight dynamics products to the appropriate customers. Although AutoProducts will normally generate pre-programmed sets of routine products, its graphical interface allows for easy configuration of customized and one-of-a-kind products. Additionally, AutoProducts has been designed as a mission-independent tool, and can be easily reconfigured to support other missions or incorporate new flight dynamics software packages. After the AM-1 launch, AutoProducts will run automatically at pre-determined time intervals . The AutoProducts tool reduces many of the concerns associated with the flight dynamics product generation. Although AutoProducts required a significant effort to develop because of the complexity of the interfaces involved, its use will provide significant cost savings through reduced operator time and maximum product reliability. In addition, user satisfaction is significantly improved and flight dynamics experts have more time to perform valuable analysis work. This paper will describe the evolution of the AutoProducts tool, highlighting the cost savings and customer satisfaction resulting from its development. It will also provide details about the tool including its graphical interface and operational capabilities.

Assessment of in-flight anomalies of long life outer plant mission

NASA Technical Reports Server (NTRS)

Hoffman, Alan R.; Green, Nelson W.; Garrett, Henry B.

2004-01-01

Thee unmanned planetary spacecraft to the outer planets have been controlled and operated successfully in space for an accumulated total of 66 years. The Voyager 1 and 2 spacecraft each have been in space for more than 26 years. The Galileo spacecraft was in space for 14 years, including eight years in orbit about Jupiter. During the flight operations for these missions, anomalies for the ground data system and the flight systems have been tracked using the anomaly reporting tool at the Jet Propulsion Laboratory. A total of 3300 incidents, surprises, and anomaly reports have been recorded in the database. This paper describes methods and results for classifying and identifying trends relative to ground system vs. flight system, software vs. hardware, and corrective actions. There are several lessons learned from these assessments that significantly benefit the design and planning for long life missions of the future. These include the necessity for having redundancy for successful operation of the spacecraft, awareness that anomaly reporting is dependent on mission activity not the age of the spacecraft, and the need for having a program to maintain and transfer operation knowledge and tools to replacement flight team members.

Implications of Responsive Space on the Flight Software Architecture

NASA Technical Reports Server (NTRS)

Wilmot, Jonathan

2006-01-01

The Responsive Space initiative has several implications for flight software that need to be addressed not only within the run-time element, but the development infrastructure and software life-cycle process elements as well. The runtime element must at a minimum support Plug & Play, while the development and process elements need to incorporate methods to quickly generate the needed documentation, code, tests, and all of the artifacts required of flight quality software. Very rapid response times go even further, and imply little or no new software development, requiring instead, using only predeveloped and certified software modules that can be integrated and tested through automated methods. These elements have typically been addressed individually with significant benefits, but it is when they are combined that they can have the greatest impact to Responsive Space. The Flight Software Branch at NASA's Goddard Space Flight Center has been developing the runtime, infrastructure and process elements needed for rapid integration with the Core Flight software System (CFS) architecture. The CFS architecture consists of three main components; the core Flight Executive (cFE), the component catalog, and the Integrated Development Environment (DE). This paper will discuss the design of the components, how they facilitate rapid integration, and lessons learned as the architecture is utilized for an upcoming spacecraft.

Application of partial differential equation modeling of the control/structural dynamics of flexible spacecraft

NASA Technical Reports Server (NTRS)

Taylor, Lawrence W., Jr.; Rajiyah, H.

1991-01-01

Partial differential equations for modeling the structural dynamics and control systems of flexible spacecraft are applied here in order to facilitate systems analysis and optimization of these spacecraft. Example applications are given, including the structural dynamics of SCOLE, the Solar Array Flight Experiment, the Mini-MAST truss, and the LACE satellite. The development of related software is briefly addressed.

Demonstrating a Realistic IP Mission Prototype

NASA Technical Reports Server (NTRS)

Rash, James; Ferrer, Arturo B.; Goodman, Nancy; Ghazi-Tehrani, Samira; Polk, Joe; Johnson, Lorin; Menke, Greg; Miller, Bill; Criscuolo, Ed; Hogie, Keith

2003-01-01

Flight software and hardware and realistic space communications environments were elements of recent demonstrations of the Internet Protocol (IP) mission concept in the lab. The Operating Missions as Nodes on the Internet (OMNI) Project and the Flight Software Branch at NASA/GSFC collaborated to build the prototype of a representative space mission that employed unmodified off-the-shelf Internet protocols and technologies for end-to-end communications between the spacecraft/instruments and the ground system/users. The realistic elements used in the prototype included an RF communications link simulator and components of the TRIANA mission flight software and ground support system. A web-enabled camera connected to the spacecraft computer via an Ethernet LAN represented an on-board instrument creating image data. In addition to the protocols at the link layer (HDLC), transport layer (UDP, TCP), and network (IP) layer, a reliable file delivery protocol (MDP) at the application layer enabled reliable data delivery both to and from the spacecraft. The standard Network Time Protocol (NTP) performed on-board clock synchronization with a ground time standard. The demonstrations of the prototype mission illustrated some of the advantages of using Internet standards and technologies for space missions, but also helped identify issues that must be addressed. These issues include applicability to embedded real-time systems on flight-qualified hardware, range of applicability of TCP, and liability for and maintenance of commercial off-the-shelf (COTS) products. The NASA Earth Science Technology Office (ESTO) funded the collaboration to build and demonstrate the prototype IP mission.

The deep space 1 extended mission

NASA Astrophysics Data System (ADS)

Rayman, Marc D.; Varghese, Philip

2001-03-01

The primary mission of Deep Space 1 (DS1), the first flight of the New Millennium program, completed successfully in September 1999, having exceeded its objectives of testing new, high-risk technologies important for future space and Earth science missions. DS1 is now in its extended mission, with plans to take advantage of the advanced technologies, including solar electric propulsion, to conduct an encounter with comet 19P/Borrelly in September 2001. During the extended mission, the spacecraft's commercial star tracker failed; this critical loss prevented the spacecraft from achieving three-axis attitude control or knowledge. A two-phase approach to recovering the mission was undertaken. The first involved devising a new method of pointing the high-gain antenna to Earth using the radio signal received at the Deep Space Network as an indicator of spacecraft attitude. The second was the development of new flight software that allowed the spacecraft to return to three-axis operation without substantial ground assistance. The principal new feature of this software is the use of the science camera as an attitude sensor. The differences between the science camera and the star tracker have important implications not only for the design of the new software but also for the methods of operating the spacecraft and conducting the mission. The ambitious rescue was fully successful, and the extended mission is back on track.

Simulation of Attitude and Trajectory Dynamics and Control of Multiple Spacecraft

NASA Technical Reports Server (NTRS)

Stoneking, Eric T.

2009-01-01

Agora software is a simulation of spacecraft attitude and orbit dynamics. It supports spacecraft models composed of multiple rigid bodies or flexible structural models. Agora simulates multiple spacecraft simultaneously, supporting rendezvous, proximity operations, and precision formation flying studies. The Agora environment includes ephemerides for all planets and major moons in the solar system, supporting design studies for deep space as well as geocentric missions. The environment also contains standard models for gravity, atmospheric density, and magnetic fields. Disturbance force and torque models include aerodynamic, gravity-gradient, solar radiation pressure, and third-body gravitation. In addition to the dynamic and environmental models, Agora supports geometrical visualization through an OpenGL interface. Prototype models are provided for common sensors, actuators, and control laws. A clean interface accommodates linking in actual flight code in place of the prototype control laws. The same simulation may be used for rapid feasibility studies, and then used for flight software validation as the design matures. Agora is open-source and portable across computing platforms, making it customizable and extensible. It is written to support the entire GNC (guidance, navigation, and control) design cycle, from rapid prototyping and design analysis, to high-fidelity flight code verification. As a top-down design, Agora is intended to accommodate a large range of missions, anywhere in the solar system. Both two-body and three-body flight regimes are supported, as well as seamless transition between them. Multiple spacecraft may be simultaneously simulated, enabling simulation of rendezvous scenarios, as well as formation flying. Built-in reference frames and orbit perturbation dynamics provide accurate modeling of precision formation control.

Galileo Attitude Determination: Experiences with a Rotating Star Scanner

NASA Technical Reports Server (NTRS)

Merken, L.; Singh, G.

1991-01-01

The Galileo experience with a rotating star scanner is discussed in terms of problems encountered in flight, solutions implemented, and lessons learned. An overview of the Galileo project and the attitude and articulation control subsystem is given and the star scanner hardware and relevant software algorithms are detailed. The star scanner is the sole source of inertial attitude reference for this spacecraft. Problem symptoms observed in flight are discussed in terms of effects on spacecraft performance and safety. Sources of thse problems include contributions from flight software idiosyncrasies and inadequate validation of the ground procedures used to identify target stars for use by the autonomous on-board star identification algorithm. Problem fixes (some already implemented and some only proposed) are discussed. A general conclusion is drawn regarding the inherent difficulty of performing simulation tests to validate algorithms which are highly sensitive to external inputs of statistically 'rare' events.

Research on an expert system for database operation of simulation-emulation math models. Volume 1, Phase 1: Results

NASA Technical Reports Server (NTRS)

Kawamura, K.; Beale, G. O.; Schaffer, J. D.; Hsieh, B. J.; Padalkar, S.; Rodriguez-Moscoso, J. J.

1985-01-01

The results of the first phase of Research on an Expert System for Database Operation of Simulation/Emulation Math Models, is described. Techniques from artificial intelligence (AI) were to bear on task domains of interest to NASA Marshall Space Flight Center. One such domain is simulation of spacecraft attitude control systems. Two related software systems were developed to and delivered to NASA. One was a generic simulation model for spacecraft attitude control, written in FORTRAN. The second was an expert system which understands the usage of a class of spacecraft attitude control simulation software and can assist the user in running the software. This NASA Expert Simulation System (NESS), written in LISP, contains general knowledge about digital simulation, specific knowledge about the simulation software, and self knowledge.

Integrating CCSDS Electronic Data Sheets into Flight Software

NASA Technical Reports Server (NTRS)

Wilmot, Jonathan

2017-01-01

This presentation will describe the new CCSDS Spacecraft Onboard Interfaces Services (SOIS) Electronic Data Sheet (EDS) standards and how they are being applied to data interfaces in software frameworks, tool chains, and ground systems across a range of missions at NASA and other agencies.

Design, Fabrication, and Testing of a Hopper Spacecraft Simulator

NASA Astrophysics Data System (ADS)

Mucasey, Evan Phillip Krell

A robust test bed is needed to facilitate future development of guidance, navigation, and control software for future vehicles capable of vertical takeoff and landings. Specifically, this work aims to develop both a hardware and software simulator that can be used for future flight software development for extra-planetary vehicles. To achieve the program requirements of a high thrust to weight ratio with large payload capability, the vehicle is designed to have a novel combination of electric motors and a micro jet engine is used to act as the propulsion elements. The spacecraft simulator underwent several iterations of hardware development using different materials and fabrication methods. The final design used a combination of carbon fiber and fiberglass that was cured under vacuum to serve as the frame of the vehicle which provided a strong, lightweight platform for all flight components and future payloads. The vehicle also uses an open source software development platform, Arduino, to serve as the initial flight computer and has onboard accelerometers, gyroscopes, and magnetometers to sense the vehicles attitude. To prevent instability due to noise, a polynomial kalman filter was designed and this fed the sensed angles and rates into a robust attitude controller which autonomously control the vehicle' s yaw, pitch, and roll angles. In addition to the hardware development of the vehicle itself, both a software simulation and a real time data acquisition interface was written in MATLAB/SIMULINK so that real flight data could be taken and then correlated to the simulation to prove the accuracy of the analytical model. In result, the full scale vehicle was designed and own outside of the lab environment and data showed that the software model accurately predicted the flight dynamics of the vehicle.

Reconfigurable Software for Controlling Formation Flying

NASA Technical Reports Server (NTRS)

Mueller, Joseph B.

2006-01-01

Software for a system to control the trajectories of multiple spacecraft flying in formation is being developed to reflect underlying concepts of (1) a decentralized approach to guidance and control and (2) reconfigurability of the control system, including reconfigurability of the software and of control laws. The software is organized as a modular network of software tasks. The computational load for both determining relative trajectories and planning maneuvers is shared equally among all spacecraft in a cluster. The flexibility and robustness of the software are apparent in the fact that tasks can be added, removed, or replaced during flight. In a computational simulation of a representative formation-flying scenario, it was demonstrated that the following are among the services performed by the software: Uploading of commands from a ground station and distribution of the commands among the spacecraft, Autonomous initiation and reconfiguration of formations, Autonomous formation of teams through negotiations among the spacecraft, Working out details of high-level commands (e.g., shapes and sizes of geometrically complex formations), Implementation of a distributed guidance law providing autonomous optimization and assignment of target states, and Implementation of a decentralized, fuel-optimal, impulsive control law for planning maneuvers.

Virtual Machine Language

NASA Technical Reports Server (NTRS)

Grasso, Christopher; Page, Dennis; O'Reilly, Taifun; Fteichert, Ralph; Lock, Patricia; Lin, Imin; Naviaux, Keith; Sisino, John

2005-01-01

Virtual Machine Language (VML) is a mission-independent, reusable software system for programming for spacecraft operations. Features of VML include a rich set of data types, named functions, parameters, IF and WHILE control structures, polymorphism, and on-the-fly creation of spacecraft commands from calculated values. Spacecraft functions can be abstracted into named blocks that reside in files aboard the spacecraft. These named blocks accept parameters and execute in a repeatable fashion. The sizes of uplink products are minimized by the ability to call blocks that implement most of the command steps. This block approach also enables some autonomous operations aboard the spacecraft, such as aerobraking, telemetry conditional monitoring, and anomaly response, without developing autonomous flight software. Operators on the ground write blocks and command sequences in a concise, high-level, human-readable programming language (also called VML ). A compiler translates the human-readable blocks and command sequences into binary files (the operations products). The flight portion of VML interprets the uplinked binary files. The ground subsystem of VML also includes an interactive sequence- execution tool hosted on workstations, which runs sequences at several thousand times real-time speed, affords debugging, and generates reports. This tool enables iterative development of blocks and sequences within times of the order of seconds.

Flight Experiment Demonstration System (FEDS) analysis report

NASA Technical Reports Server (NTRS)

Shank, D. E.

1986-01-01

The purpose of the Flight Experiment Demonstration System (FEDS) was to show, in a simulated spacecraft environment, the feasibility of using a microprocessor to automate the onboard orbit determination functions. The software and hardware configuration used to support FEDS during the demonstration and the results of the demonstration are discussed.

SINBAD flight software, the on-board software of NOMAD in ExoMars 2016

NASA Astrophysics Data System (ADS)

Pastor-Morales, M. C.; Rodríguez-Gómez, Julio F.; Morales-Muñoz, Rafael; Gómez-López, Juan M.; Aparicio-del-Moral, Beatriz; Candini, Gian Paolo; Jerónimo-Zafra, Jose M.; López-Moreno, Jose J.; Robles-Muñoz, Nicolás. F.; Sanz-Mesa, Rosario; Neefs, Eddy; Vandaele, Ann C.; Drummond, Rachel; Thomas, Ian R.; Berkenbosch, Sophie; Clairquin, Roland; Delanoye, Sofie; Ristic, Bojan; Maes, Jeroen; Bonnewijn, Sabrina; Patel, Manish R.; Leese, Mark; Mason, Jon P.

2016-07-01

The Spacecraft INterface and control Board for NomAD (SINBAD) is an electronic interface designed by the Instituto de Astroffisica de Andalucfia (IAA-CSIC). It is part of the Nadir and Occultation for MArs Discovery instrument (NOMAD) on board in the ESAs ExoMars Trace Gas Orbiter mission. This mission was launched in March 2016. The SINBAD Flight Software (SFS) is the software embedded in SINBAD. It is in charge of managing the interfaces, devices, data, observing sequences, patching and contingencies of NOMAD. It is presented in this paper the most remarkable aspects of the SFS design, likewise the main problems and lessons learned during the software development process.

GFAST Software Demonstration

NASA Image and Video Library

2017-03-17

NASA engineers and test directors gather in Firing Room 3 in the Launch Control Center at NASA's Kennedy Space Center in Florida, to watch a demonstration of the automated command and control software for the agency's Space Launch System (SLS) and Orion spacecraft. The software is called the Ground Launch Sequencer. It will be responsible for nearly all of the launch commit criteria during the final phases of launch countdowns. The Ground and Flight Application Software Team (GFAST) demonstrated the software. It was developed by the Command, Control and Communications team in the Ground Systems Development and Operations (GSDO) Program. GSDO is helping to prepare the center for the first test flight of Orion atop the SLS on Exploration Mission 1.

Improving Flight Software Module Validation Efforts : a Modular, Extendable Testbed Software Framework

NASA Technical Reports Server (NTRS)

Lange, R. Connor

2012-01-01

Ever since Explorer-1, the United States' first Earth satellite, was developed and launched in 1958, JPL has developed many more spacecraft, including landers and orbiters. While these spacecraft vary greatly in their missions, capabilities,and destination, they all have something in common. All of the components of these spacecraft had to be comprehensively tested. While thorough testing is important to mitigate risk, it is also a very expensive and time consuming process. Thankfully,since virtually all of the software testing procedures for SMAP are computer controlled, these procedures can be automated. Most people testing SMAP flight software (FSW) would only need to write tests that exercise specific requirements and then check the filtered results to verify everything occurred as planned. This gives developers the ability to automatically launch tests on the testbed, distill the resulting logs into only the important information, generate validation documentation, and then deliver the documentation to management. With many of the steps in FSW testing automated, developers can use their limited time more effectively and can validate SMAP FSW modules quicker and test them more rigorously. As a result of the various benefits of automating much of the testing process, management is considering this automated tools use in future FSW validation efforts.

A Flight-Calibrated Methodology for Determination of Cassini Thruster On-Times for Reaction Wheel Biases

NASA Technical Reports Server (NTRS)

Sarani, Siamak

2010-01-01

This paper describes a methodology for accurate and flight-calibrated determination of the on-times of the Cassini spacecraft Reaction Control System (RCS) thrusters, without any form of dynamic simulation, for the reaction wheel biases. The hydrazine usage and the delta V vector in body frame are also computed from the respective thruster on-times. The Cassini spacecraft, the largest and most complex interplanetary spacecraft ever built, continues to undertake ambitious and unique scientific observations of planet Saturn, Titan, Enceladus, and other moons of Saturn. In order to maintain a stable attitude during the course of its mission, this three-axis stabilized spacecraft uses two different control systems: the RCS and the reaction wheel assembly control system. The RCS is used to execute a commanded spacecraft slew, to maintain three-axis attitude control, control spacecraft's attitude while performing science observations with coarse pointing requirements, e.g. during targeted low-altitude Titan and Enceladus flybys, bias the momentum of reaction wheels, and to perform RCS-based orbit trim maneuvers. The use of RCS often imparts undesired delta V on the spacecraft. The Cassini navigation team requires accurate predictions of the delta V in spacecraft coordinates and inertial frame resulting from slews using RCS thrusters and more importantly from reaction wheel bias events. It is crucial for the Cassini spacecraft attitude control and navigation teams to be able to, quickly but accurately, predict the hydrazine usage and delta V for various reaction wheel bias events without actually having to spend time and resources simulating the event in flight software-based dynamic simulation or hardware-in-the-loop simulation environments. The methodology described in this paper, and the ground software developed thereof, are designed to provide just that. This methodology assumes a priori knowledge of thrust magnitudes and thruster pulse rise and tail-off time constants for eight individual attitude control thrusters, the spacecraft's wet mass and its center of mass location, and a few other key parameters.

Proximity operations considerations affecting spacecraft design

NASA Technical Reports Server (NTRS)

Staas, Steven K.

1991-01-01

Experience from several recent spacecraft development programs, such as Space Station Freedom (SSF) and the Orbital Maneuvering Vehicle (OMV) has shown the need for factoring proximity operations considerations into the vehicle design process. Proximity operations, those orbital maneuvers and procedures which involve operation of two or more spacecraft at ranges of less than one nautical mile, are essential to the construction, servicing, and operation of complex spacecraft. Typical proximity operations considerations which drive spacecraft design may be broken into two broad categories; flight profile characteristics and concerns, and use of various spacecraft systems during proximity operations. Proximity operations flight profile concerns include the following: (1) relative approach/separation line; (2) relative orientation of the vehicles; (3) relative translational and rotational rates; (4) vehicle interaction, in the form of thruster plume impingement, mating or demating operations, or uncontrolled contact/collision; and (5) active vehicle piloting. Spacecraft systems used during proximity operations include the following: (1) sensors, such as radar, laser ranging devices, or optical ranging systems; (2) effector hardware, such as thrusters; (3) flight control software; and (4) mating hardware, needed for docking or berthing operations. A discussion of how these factors affect vehicle design follows, addressing both active and passive/cooperative vehicles.

A multimission three-axis stabilized spacecraft flight dynamics ground support system

NASA Technical Reports Server (NTRS)

Langston, J.; Krack, K.; Reupke, W.

1993-01-01

The Multimission Three-Axis Stabilized Spacecraft (MTASS) Flight Dynamics Support System (FDSS) has been developed in an effort to minimize the costs of ground support systems. Unlike single-purpose ground support systems, which attempt to reduce costs by reusing software specifically developed for previous missions, the multimission support system is an intermediate step in the progression to a fully generalized mission support system in which numerous missions may be served by one general system. The benefits of multimission attitude ground support systems extend not only to the software design and coding process, but to the entire system environment, from specification through testing, simulation, operations, and maintenance. This paper reports the application of an MTASS FDSS to multiple scientific satellite missions. The satellites are the Upper Atmosphere Research Satellite (UARS), the Extreme Ultraviolet Explorer (EUVE), and the Solar Anomalous Magnetospheric Particle Explorer (SAMPEX). Both UARS and EUVE use the multimission modular spacecraft (MMS) concept. SAMPEX is part of the Small Explorer (SMEX) series and uses a much simpler set of attitude sensors. This paper centers on algorithm and design concepts for a multimission system and discusses flight experience from UARS.

Ethernet for Space Flight Applications

NASA Technical Reports Server (NTRS)

Webb, Evan; Day, John H. (Technical Monitor)

2002-01-01

NASA's Goddard Space Flight Center (GSFC) is adapting current data networking technologies to fly on future spaceflight missions. The benefits of using commercially based networking standards and protocols have been widely discussed and are expected to include reduction in overall mission cost, shortened integration and test (I&T) schedules, increased operations flexibility, and hardware and software upgradeability/scalability with developments ongoing in the commercial world. The networking effort is a comprehensive one encompassing missions ranging from small University Explorer (UNEX) class spacecraft to large observatories such as the Next Generation Space Telescope (NGST). Mission aspects such as flight hardware and software, ground station hardware and software, operations, RF communications, and security (physical and electronic) are all being addressed to ensure a complete end-to-end system solution. One of the current networking development efforts at GSFC is the SpaceLAN (Spacecraft Local Area Network) project, development of a space-qualifiable Ethernet network. To this end we have purchased an IEEE 802.3-compatible 10/100/1000 Media Access Control (MAC) layer Intellectual Property (IP) core and are designing a network node interface (NNI) and associated network components such as a switch. These systems will ultimately allow the replacement of the typical MIL-STD-1553/1773 and custom interfaces that inhabit most spacecraft. In this paper we will describe our current Ethernet NNI development along with a novel new space qualified physical layer that will be used in place of the standard interfaces. We will outline our plans for development of space qualified network components that will allow future spacecraft to operate in significant radiation environments while using a single onboard network for reliable commanding and data transfer. There will be a brief discussion of some issues surrounding system implications of a flight Ethernet. Finally, we will show an onboard network architecture for a proposed new mission using Ethernet for science data transport.

Orbit determination and orbit control for the Earth Observing System (EOS) AM spacecraft

NASA Technical Reports Server (NTRS)

Herberg, Joseph R.; Folta, David C.

1993-01-01

Future NASA Earth Observing System (EOS) Spacecraft will make measurements of the earth's clouds, oceans, atmosphere, land and radiation balance. These EOS Spacecraft will be part of the NASA Mission to Planet Earth. This paper specifically addresses the EOS AM Spacecraft, referred to as 'AM' because it has a sun-synchronous orbit with a 10:30 AM descending node. This paper describes the EOS AM Spacecraft mission orbit requirements, orbit determination, orbit control, and navigation system impact on earth based pointing. The EOS AM Spacecraft will be the first spacecraft to use the TDRSS Onboard Navigation System (TONS) as the primary means of navigation. TONS flight software will process one-way forward Doppler measurements taken during scheduled TDRSS contacts. An extended Kalman filter will estimate spacecraft position, velocity, drag coefficient correction, and ultrastable master oscillator frequency bias and drift. The TONS baseline algorithms, software, and hardware implementation are described in this paper. TONS integration into the EOS AM Spacecraft Guidance, Navigation, and Control (GN&C) System; TONS assisted onboard time maintenance; and the TONS Ground Support System (TGSS) are also addressed.

Autonomic Computing for Spacecraft Ground Systems

NASA Technical Reports Server (NTRS)

Li, Zhenping; Savkli, Cetin; Jones, Lori

2007-01-01

Autonomic computing for spacecraft ground systems increases the system reliability and reduces the cost of spacecraft operations and software maintenance. In this paper, we present an autonomic computing solution for spacecraft ground systems at NASA Goddard Space Flight Center (GSFC), which consists of an open standard for a message oriented architecture referred to as the GMSEC architecture (Goddard Mission Services Evolution Center), and an autonomic computing tool, the Criteria Action Table (CAT). This solution has been used in many upgraded ground systems for NASA 's missions, and provides a framework for developing solutions with higher autonomic maturity.

Java for flight software

NASA Technical Reports Server (NTRS)

Benowitz, E. G.; Niessner, A. F.

2003-01-01

We have successfully demonstrated a portion of the spacecraft attitude control and fault protection, running on a standard Java platform, and are currently in the process of taking advantage of the features provided by the RTSJ.

SmallSat Innovations for Planetary Science

NASA Astrophysics Data System (ADS)

Weinberg, Jonathan; Petroy, Shelley; Roark, Shane; Schindhelm, Eric

2017-10-01

As NASA continues to look for ways to fly smaller planetary missions such as SIMPLEX, MoO, and Venus Bridge, it is important that spacecraft and instrument capabilities keep pace to allow these missions to move forward. As spacecraft become smaller, it is necessary to balance size with capability, reliability and payload capacity. Ball Aerospace offers extensive SmallSat capabilities matured over the past decade, utilizing our broad experience developing mission architecture, assembling spacecraft and instruments, and testing advanced enabling technologies. Ball SmallSats inherit their software capabilities from the flight proven Ball Configurable Platform (BCP) line of spacecraft, and may be tailored to meet the unique requirements of Planetary Science missions. We present here recent efforts in pioneering both instrument miniaturization and SmallSat/sensorcraft development through mission design and implementation. Ball has flown several missions with small, but capable spacecraft. We also have demonstrated a variety of enhanced spacecraft/instrument capabilities in the laboratory and in flight to advance autonomy in spaceflight hardware that can enable some small planetary missions.

Description and User Instructions for the Quaternion_to_Orbit_v3 Software

NASA Technical Reports Server (NTRS)

Strekalov, Dmitry V.; Kruizinga, Gerhard L.; Paik, Meegyeong; Yuan, Dah-Ning; Asmar, Sami W.

2012-01-01

For a given inertial frame of reference, the software combines the spacecraft orbits with the spacecraft attitude quaternions, and rotates the body-fixed reference frame of a particular spacecraft to the inertial reference frame. The conversion assumes that the two spacecraft are aligned with respect to the mutual line of sight, with a parameterized time tag. The software is implemented in Python and is completely open source. It is very versatile, and may be applied under various circumstances and for other related purposes. Based on the solid linear algebra analysis, it has an extra option for compensating the linear pitch. This software has been designed for simulation of the calibration maneuvers performed by the two spacecraft comprising the GRAIL mission to the Moon, but has potential use for other applications. In simulations of formation flights, one needs to coordinate the spacecraft orbits represented in an appropriate inertial reference frame and the spacecraft attitudes. The latter are usually given as the time series of quaternions rotating the body-fixed reference frame of a particular spacecraft to the inertial reference frame. It is often desirable to simulate the same maneuver for different segments of the orbit. It is also useful to study various maneuvers that could be performed at the same orbit segment. These two lines of study are more timeand labor-efficient if the attitude and orbit data are generated independently, so that the part of the data that has not been changed can be recycled in the course of multiple simulations.

NASA's Core Trajectory Sub-System Project: Using JBoss Enterprise Middleware for Building Software Systems Used to Support Spacecraft Trajectory Operations

NASA Technical Reports Server (NTRS)

Stensrud, Kjell C.; Hamm, Dustin

2007-01-01

NASA's Johnson Space Center (JSC) / Flight Design and Dynamics Division (DM) has prototyped the use of Open Source middleware technology for building its next generation spacecraft mission support system. This is part of a larger initiative to use open standards and open source software as building blocks for future mission and safety critical systems. JSC is hoping to leverage standardized enterprise architectures, such as Java EE, so that its internal software development efforts can be focused on the core aspects of their problem domain. This presentation will outline the design and implementation of the Trajectory system and the lessons learned during the exercise.

Development of the Spacecraft Materials Selector Expert System

NASA Technical Reports Server (NTRS)

Pippin, H. G.

2000-01-01

A specific knowledge base to evaluate the on-orbit performance of selected materials on spacecraft is being developed under contract to the NASA SEE program. An artificial intelligence software package, the Boeing Expert System Tool (BEST), contains an inference engine used to operate knowledge bases constructed to selectively recall and distribute information about materials performance in space applications. This same system is used to make estimates of the environmental exposures expected for a given space flight. The performance capabilities of the Spacecraft Materials Selector (SMS) knowledge base are described in this paper. A case history for a planned flight experiment on ISS is shown as an example of the use of the SMS, and capabilities and limitations of the knowledge base are discussed.

OpenSatKit Enables Quick Startup for CubeSat Missions

NASA Technical Reports Server (NTRS)

McComas, David; Melton, Ryan

2017-01-01

The software required to develop, integrate, and operate a spacecraft is substantial regardless of whether its a large or small satellite. Even getting started can be a monumental task. To solve this problem, NASAs Core Flight System (cFS), NASA's 42 spacecraft dynamics simulator, and Ball Aerospaces COSMOS ground system have been integrated together into a kit called OpenSatKit that provides a complete and open source software solution for starting a new satellite mission. Users can have a working system with flight software, dynamics simulation, and a ground command and control system up and running within hours.Every satellite mission requires three primary categories of software to function. The first is Flight Software (FSW) which provides the onboard control of the satellites and its payload(s). NASA's cFS provides a great platform for developing this software. Second, while developing a satellite on earth, it is necessary to simulate the satellites orbit, attitude, and actuators, to ensure that the systems that control these aspects will work correctly in the real environment. NASAs 42 simulator provides these functionalities. Finally, the ground has to be able to communicate with the satellite, monitor its performance and health, and display its data. Additionally, test scripts have to be written to verify the system on the ground. Ball Aerospace's COSMOS command and control system provides this functionality. Once the OpenSatKit is up and running, the next step is to customize the platform and get it running on the end target. Starting from a fully working system makes porting the cFS from Linux to a users platform much easier. An example Raspberry Pi target is included in the kit so users can gain experience working with a low cost hardware target. All users can benefit from OpenSatKit but the greatest impact and benefits will be to SmallSat missions with constrained budgets and small software teams. This paper describes OpenSatKits system design, the steps necessary to run the system to target the Raspberry Pi, and future plans. OpenSatKit is a free fully functional spacecraft software system that we hope will greatly benefit the SmallSat community.

Inflight Performance of Cassini Reaction Wheel Bearing Drag in 1997-2013

NASA Technical Reports Server (NTRS)

Lee, Allan Y.; Wang, Eric K.

2013-01-01

As the first spacecraft to achieve orbit at Saturn in 2004, Cassini has collected science data throughout its four-year prime mission (2004-08), and has since been approved for a first and second extended missions through September 2017. Cassini is a three-axis stabilized spacecraft. It uses reaction wheels to achieve high level of spacecraft pointing stability that is needed during imaging operations of several science instruments. The Cassini flight software makes in-flight estimates of reaction wheel bearing drag torque and made them available to the mission operations team. These telemetry data are being trended for the purpose of monitoring the long-term health of the reaction wheel bearings. Anomalous drag torque signatures observed over the past 15 years are described in this paper. One of these anomalous drag conditions is bearing cage instability that appeared (and disappeared) spontaneously and unpredictably. Cage instability is an uncontrolled vibratory motion of the bearing cage that can produce high-impact forces internal to the bearing that will cause intermittent and erratic torque transients. Characteristics of the observed cage instabilities and other drag torque "spikes" are described in this paper. In day-to-day operations, the reaction wheels' rates must be neither too high nor too low. To protect against operating the wheels in any undesirable conditions (such as prolonged low spin rate operations), a ground software tool named Reaction Wheel Bias Optimization Tool (RBOT) was developed for the management of the wheels. Disciplined and long-term use of this ground software has led to significant reduction in the daily consumption rate of the wheels' low spin rate dwell time. Flight experience on the use of this ground software tool as well as other lessons learned on the management of Cassini reaction wheels is given in this paper.

Ground Data System Risk Mitigation Techniques for Faster, Better, Cheaper Missions

NASA Technical Reports Server (NTRS)

Catena, John J.; Saylor, Rick; Casasanta, Ralph; Weikel, Craig; Powers, Edward I. (Technical Monitor)

2000-01-01

With the advent of faster, cheaper, and better missions, NASA Projects acknowledged that a higher level of risk was inherent and accepted with this approach. It was incumbent however upon each component of the Project whether spacecraft, payload, launch vehicle, or ground data system to ensure that the mission would nevertheless be an unqualified success. The Small Explorer (SMEX) program's ground data system (GDS) team developed risk mitigation techniques to achieve these goals starting in 1989. These techniques have evolved through the SMEX series of missions and are practiced today under the Triana program. These techniques are: (1) Mission Team Organization--empowerment of a closeknit ground data system team comprising system engineering, software engineering, testing, and flight operations personnel; (2) Common Spacecraft Test and Operational Control System--utilization of the pre-launch spacecraft integration system as the post-launch ground data system on-orbit command and control system; (3) Utilization of operations personnel in pre-launch testing--making the flight operations team an integrated member of the spacecraft testing activities at the beginning of the spacecraft fabrication phase; (4) Consolidated Test Team--combined system, mission readiness and operations testing to optimize test opportunities with the ground system and spacecraft; and (5). Reuse of Spacecraft, Systems and People--reuse of people, software and on-orbit spacecraft throughout the SMEX mission series. The SMEX ground system development approach for faster, cheaper, better missions has been very successful. This paper will discuss these risk management techniques in the areas of ground data system design, implementation, test, and operational readiness.

Customizing graphical user interface technology for spacecraft control centers

NASA Technical Reports Server (NTRS)

Beach, Edward; Giancola, Peter; Gibson, Steven; Mahmot, Ronald

1993-01-01

The Transportable Payload Operations Control Center (TPOCC) project is applying the latest in graphical user interface technology to the spacecraft control center environment. This project of the Mission Operations Division's (MOD) Control Center Systems Branch (CCSB) at NASA Goddard Space Flight Center (GSFC) has developed an architecture for control centers which makes use of a distributed processing approach and the latest in Unix workstation technology. The TPOCC project is committed to following industry standards and using commercial off-the-shelf (COTS) hardware and software components wherever possible to reduce development costs and to improve operational support. TPOCC's most successful use of commercial software products and standards has been in the development of its graphical user interface. This paper describes TPOCC's successful use and customization of four separate layers of commercial software products to create a flexible and powerful user interface that is uniquely suited to spacecraft monitoring and control.

GFAST Software Demonstration

NASA Image and Video Library

2017-03-17

NASA engineers and test directors gather in Firing Room 3 in the Launch Control Center at NASA's Kennedy Space Center in Florida, to watch a demonstration of the automated command and control software for the agency's Space Launch System (SLS) and Orion spacecraft. In front, far right, is Charlie Blackwell-Thompson, launch director for Exploration Mission 1 (EM-1). The software is called the Ground Launch Sequencer. It will be responsible for nearly all of the launch commit criteria during the final phases of launch countdowns. The Ground and Flight Application Software Team (GFAST) demonstrated the software. It was developed by the Command, Control and Communications team in the Ground Systems Development and Operations (GSDO) Program. GSDO is helping to prepare the center for the first test flight of Orion atop the SLS on EM-1.

Dynamic Control System Mode Performance of the Space Technology-7 Disturbance Reduction System

NASA Technical Reports Server (NTRS)

O'Donnell, James R., Jr.; Hsu, Oscar; Maghami, Peiman

2017-01-01

The Space Technology-7 (ST-7) Disturbance Reduction System (DRS) is an experiment package aboard the European Space Agency (ESA) LISA Pathfinder spacecraft, launched on December 3, 2015. DRS consists of three primary components: Colloidal MicroNewton Thrusters (CMNTs), an Integrated Avionics Unit (IAU), and flight-software implementing the Command and Data Handling (C&DH) and Dynamic Control System (DCS) algorithms. The CMNTs were designed to provide thrust from 5 to 30 micro Newton, with thrust controllability and resolution of 0.1 micro Newton and thrust noise of 0.1 micro Newton/(square root of (Hz)) in the measurement band from 1-30 mHz. The IAU hosts the C&DH and DCS flight software, as well as interfaces with both the CMNT electronics and the LISA Pathfinder spacecraft. When in control, the DCS uses star tracker attitude data and capacitive or optically-measured position and attitude information from LISA Pathfinder and the LISA Technology Package (LTP) to control the attitude and position of the spacecraft and the two test masses inside the LTP. After completion of the nominal ESA LISA Pathfinder mission, the DRS experiment was commissioned followed by its nominal mission. DRS operations extended over the next five months, interspersed with station keeping, anomaly resolution, and periods where control was handed back to LISA Pathfinder for them to conduct further experiments. The primary DRS mission ended on December 6, 2016, with the experiment meeting all of its Level 1 requirements. The DCS, developed at the NASA Goddard Space Flight Center, consists of five spacecraft control modes and six test mass control modes, combined into six 'DRS Mission Modes'. Attitude Control and Zero-G were primarily used to control the spacecraft during initial handover and during many of the CMNT characterization experiments. The other Mission Modes, Drag Free Low Force, 18-DOF Transitional, and 18-DOF, were used to provide drag-free control of the spacecraft about the test masses. This paper will discuss the performance of these DCS spacecraft and test mass control modes. Flight data will be shown from each mode throughout the mission, both from nominal operations and during various flight experiments. The DCS team also made some changes to controller, filter, and limit parameters during operations; the motivation and results of these changes will be shown and discussed.

Results from the First Two Flights of the Static Computer Memory Integrity Testing Experiment

NASA Technical Reports Server (NTRS)

Hancock, Thomas M., III

1999-01-01

This paper details the scientific objectives, experiment design, data collection method, and post flight analysis following the first two flights of the Static Computer Memory Integrity Testing (SCMIT) experiment. SCMIT is designed to detect soft-event upsets in passive magnetic memory. A soft-event upset is a change in the logic state of active or passive forms of magnetic memory, commonly referred to as a "Bitflip". In its mildest form a soft-event upset can cause software exceptions, unexpected events, start spacecraft safeing (ending data collection) or corrupted fault protection and error recovery capabilities. In it's most severe form loss of mission or spacecraft can occur. Analysis after the first flight (in 1991 during STS-40) identified possible soft-event upsets to 25% of the experiment detectors. Post flight analysis after the second flight (in 1997 on STS-87) failed to find any evidence of soft-event upsets. The SCMIT experiment is currently scheduled for a third flight in December 1999 on STS-101.

The changing nature of spacecraft operations: From the Vikings of the 1970's to the great observatories of the 1990's and beyond

NASA Technical Reports Server (NTRS)

Ledbetter, Kenneth W.

1992-01-01

Four trends in spacecraft flight operations are discussed which will reduce overall program costs. These trends are the use of high-speed, highly reliable data communications systems for distributing operations functions to more convenient and cost-effective sites; the improved capability for remote operation of sensors; a continued rapid increase in memory and processing speed of flight qualified computer chips; and increasingly capable ground-based hardware and software systems, notably those augmented by artificial intelligence functions. Changes reflected by these trends are reviewed starting from the NASA Viking missions of the early 70s, when mission control was conducted at one location using expensive and cumbersome mainframe computers and communications equipment. In the 1980s, powerful desktop computers and modems enabled the Magellan project team to operate the spacecraft remotely. In the 1990s, the Hubble Space Telescope project uses multiple color screens and automated sequencing software on small computers. Given a projection of current capabilities, future control centers will be even more cost-effective.

Sierra Nevada Corporation (SNC) Dream Chaser arrival at Armstron

NASA Image and Video Library

2017-01-25

Sierra Nevada Corporation’s Dream Chaser spacecraft arrives by truck at NASA’s Armstrong Flight Research Center in California, located on Edwards Air Force Base. The spacecraft will undergo several months of testing in preparation for its approach and landing flight on the base’s 22L runway. The test series is part of a developmental space act agreement SNC has with NASA’s Commercial Crew Program and will help SNC validate aerodynamic properties, flight software and control system performance. The Dream Chaser is also being prepared to deliver cargo to the International Space Station under NASA’s Commercial Resupply Services 2 contract beginning in 2019. The cargo Dream Chaser will fly at least six delivery missions to and from the space station by 2024.

Sierra Nevada Corporation (SNC) Dream Chaser arrival at Armstrong

NASA Image and Video Library

2017-01-25

Sierra Nevada Corporation’s Dream Chaser spacecraft arrives by truck at NASA’s Armstrong Flight Research Center in California, located on Edwards Air Force Base. The spacecraft will undergo several months of testing in preparation for its approach and landing flight on the base’s 22L runway. The test series is part of a developmental space act agreement SNC has with NASA’s Commercial Crew Program and will help SNC validate aerodynamic properties, flight software and control system performance. The Dream Chaser is also being prepared to deliver cargo to the International Space Station under NASA’s Commercial Resupply Services 2 contract beginning in 2019. The cargo Dream Chaser will fly at least six delivery missions to and from the space station by 2024.

Software Innovation in a Mission Critical Environment

NASA Technical Reports Server (NTRS)

Fredrickson, Steven

2015-01-01

Operating in mission-critical environments requires trusted solutions, and the preference for "tried and true" approaches presents a potential barrier to infusing innovation into mission-critical systems. This presentation explores opportunities to overcome this barrier in the software domain. It outlines specific areas of innovation in software development achieved by the Johnson Space Center (JSC) Engineering Directorate in support of NASA's major human spaceflight programs, including International Space Station, Multi-Purpose Crew Vehicle (Orion), and Commercial Crew Programs. Software engineering teams at JSC work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements for genuinely mission critical applications. The innovations described, including the use of NASA Core Flight Software and its associated software tool chain, can lead to software that is more affordable, more reliable, better modelled, more flexible, more easily maintained, better tested, and enabling of automation.

XML Flight/Ground Data Dictionary Management

NASA Technical Reports Server (NTRS)

Wright, Jesse; Wiklow, Colette

2007-01-01

A computer program generates Extensible Markup Language (XML) files that effect coupling between the command- and telemetry-handling software running aboard a spacecraft and the corresponding software running in ground support systems. The XML files are produced by use of information from the flight software and from flight-system engineering. The XML files are converted to legacy ground-system data formats for command and telemetry, transformed into Web-based and printed documentation, and used in developing new ground-system data-handling software. Previously, the information about telemetry and command was scattered in various paper documents that were not synchronized. The process of searching and reading the documents was time-consuming and introduced errors. In contrast, the XML files contain all of the information in one place. XML structures can evolve in such a manner as to enable the addition, to the XML files, of the metadata necessary to track the changes and the associated documentation. The use of this software has reduced the extent of manual operations in developing a ground data system, thereby saving considerable time and removing errors that previously arose in the translation and transcription of software information from the flight to the ground system.

Colloid Microthruster Flight Performance Results from Space Technology 7 Disturbance Reduction System

NASA Technical Reports Server (NTRS)

Ziemer, John; Marrese-Reading, Colleen; Dunn, Charley; Romero-Wolf, Andrew; Cutler, Curt; Javidnia, Shahram; Li, Thanh; Li, Irena; Franklin, Garth; Barela, Phil;

The flight robotics laboratory

NASA Technical Reports Server (NTRS)

Tobbe, Patrick A.; Williamson, Marlin J.; Glaese, John R.

1988-01-01

The Flight Robotics Laboratory of the Marshall Space Flight Center is described in detail. This facility, containing an eight degree of freedom manipulator, precision air bearing floor, teleoperated motion base, reconfigurable operator's console, and VAX 11/750 computer system, provides simulation capability to study human/system interactions of remote systems. The facility hardware, software and subsequent integration of these components into a real time man-in-the-loop simulation for the evaluation of spacecraft contact proximity and dynamics are described.

Development of Measures to Assess Product Modularity and Reconfigurability

DTIC Science & Technology

2010-03-01

mission needs. For example, a thermal blanket is the only “module” currently being used to control spacecraft temperature (i.e. no active cooling). If...infrastructure, and thermal control. The spacecraft components include the autonomous flight software; the quantity of high- performance computing; power... thermal requirements are satisfied using this thermal blanket , then there may not be a need for active cooling to improve the thermal range of the

Attitude Determination and Control Subsystem (ADCS) Preparations for the EPOXI Flyby of Comet Haley 2

NASA Technical Reports Server (NTRS)

Luna, Michael E.; Collins, Stephen M.

2011-01-01

On November 4, 2010 the already "in-flight" Deep Impact spacecraft flew within 700km of comet 103P/Hartley 2 as part of its extended mission EPOXI, the 5th time to date any spacecraft visited a comet. In 2005, the spacecraft had previously imaged a probe impact comet Tempel 1. The EPOXI flyby marked the first time in history that two comets were explored with the same instruments on a re-used spacecraft-with hardware and software originally designed and optimized for a different mission. This made the function of the attitude determination and control subsystem (ADCS) critical to the successful execution of the EPOXI flyby. As part of the spacecraft team preparations, the ADCS team had to perform thorough sequence reviews, key spacecraft activities and onboard calibrations. These activities included: review of background sequences for the initial conditions vector, sun sensor coefficients, and reaction wheel assembly (RWA) de-saturations; design and execution of 10 trajectory correction maneuvers; science calibration of the two telescope instruments; a flight demonstration of the fastest turns conducted by the spacecraft between Earth and comet point; and assessment of RWA health (given RWA problems on other spacecraft).

Remote Agent Experiment

NASA Technical Reports Server (NTRS)

Benard, Doug; Dorais, Gregory A.; Gamble, Ed; Kanefsky, Bob; Kurien, James; Millar, William; Muscettola, Nicola; Nayak, Pandu; Rouquette, Nicolas; Rajan, Kanna;

Sierra Nevada Corporation (SNC) Dream Chaser arrival at Armstron

NASA Image and Video Library

2017-01-25

Sierra Nevada Corporation’s Dream Chaser spacecraft is removed from its delivery truck after arriving at NASA’s Armstrong Flight Research Center in California, located on Edwards Air Force Base. The spacecraft will undergo several months of testing in preparation for its approach and landing flight on the base’s 22L runway. The test series is part of a developmental space act agreement SNC has with NASA’s Commercial Crew Program and will help SNC validate aerodynamic properties, flight software and control system performance. The Dream Chaser is also being prepared to deliver cargo to the International Space Station under NASA’s Commercial Resupply Services 2 contract beginning in 2019. The cargo Dream Chaser will fly at least six delivery missions to and from the space station by 2024.

R and T report: Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Soffen, Gerald A. (Editor)

1993-01-01

The 1993 Research and Technology Report for Goddard Space Flight Center is presented. Research covered areas such as (1) flight projects; (2) space sciences including cosmology, high energy, stars and galaxies, and the solar system; (3) earth sciences including process modeling, hydrology/cryology, atmospheres, biosphere, and solid earth; (4) networks, planning, and information systems including support for mission operations, data distribution, advanced software and systems engineering, and planning/scheduling; and (5) engineering and materials including spacecraft systems, material and testing, optics and photonics and robotics.

Software-Reconfigurable Processors for Spacecraft

NASA Technical Reports Server (NTRS)

Farrington, Allen; Gray, Andrew; Bell, Bryan; Stanton, Valerie; Chong, Yong; Peters, Kenneth; Lee, Clement; Srinivasan, Jeffrey

2005-01-01

A report presents an overview of an architecture for a software-reconfigurable network data processor for a spacecraft engaged in scientific exploration. When executed on suitable electronic hardware, the software performs the functions of a physical layer (in effect, acts as a software radio in that it performs modulation, demodulation, pulse-shaping, error correction, coding, and decoding), a data-link layer, a network layer, a transport layer, and application-layer processing of scientific data. The software-reconfigurable network processor is undergoing development to enable rapid prototyping and rapid implementation of communication, navigation, and scientific signal-processing functions; to provide a long-lived communication infrastructure; and to provide greatly improved scientific-instrumentation and scientific-data-processing functions by enabling science-driven in-flight reconfiguration of computing resources devoted to these functions. This development is an extension of terrestrial radio and network developments (e.g., in the cellular-telephone industry) implemented in software running on such hardware as field-programmable gate arrays, digital signal processors, traditional digital circuits, and mixed-signal application-specific integrated circuits (ASICs).

A New Definition for Ground Control

NASA Technical Reports Server (NTRS)

2002-01-01

LandForm(R) VisualFlight(R) blends the power of a geographic information system with the speed of a flight simulator to transform a user's desktop computer into a "virtual cockpit." The software product, which is fully compatible with all Microsoft(R) Windows(R) operating systems, provides distributed, real-time three-dimensional flight visualization over a host of networks. From a desktop, a user can immediately obtain a cockpit view, a chase-plane view, or an airborne tracker view. A customizable display also allows the user to overlay various flight parameters, including latitude, longitude, altitude, pitch, roll, and heading information. Rapid Imaging Software sought assistance from NASA, and the VisualFlight technology came to fruition under a Phase II SBIR contract with Johnson Space Center in 1998. Three years later, on December 13, 2001, Ken Ham successfully flew NASA's X-38 spacecraft from a remote, ground-based cockpit using LandForm VisualFlight as part of his primary situation awareness display in a flight test at Edwards Air Force Base, California.

SHINE Virtual Machine Model for In-flight Updates of Critical Mission Software

NASA Technical Reports Server (NTRS)

Plesea, Lucian

2008-01-01

This software is a new target for the Spacecraft Health Inference Engine (SHINE) knowledge base that compiles a knowledge base to a language called Tiny C - an interpreted version of C that can be embedded on flight processors. This new target allows portions of a running SHINE knowledge base to be updated on a "live" system without needing to halt and restart the containing SHINE application. This enhancement will directly provide this capability without the risk of software validation problems and can also enable complete integration of BEAM and SHINE into a single application. This innovation enables SHINE deployment in domains where autonomy is used during flight-critical applications that require updates. This capability eliminates the need for halting the application and performing potentially serious total system uploads before resuming the application with the loss of system integrity. This software enables additional applications at JPL (microsensors, embedded mission hardware) and increases the marketability of these applications outside of JPL.

Generalized Support Software: Domain Analysis and Implementation

NASA Technical Reports Server (NTRS)

Stark, Mike; Seidewitz, Ed

1995-01-01

For the past five years, the Flight Dynamics Division (FDD) at NASA's Goddard Space Flight Center has been carrying out a detailed domain analysis effort and is now beginning to implement Generalized Support Software (GSS) based on this analysis. GSS is part of the larger Flight Dynamics Distributed System (FDDS), and is designed to run under the FDDS User Interface / Executive (UIX). The FDD is transitioning from a mainframe based environment to systems running on engineering workstations. The GSS will be a library of highly reusable components that may be configured within the standard FDDS architecture to quickly produce low-cost satellite ground support systems. The estimates for the first release is that this library will contain approximately 200,000 lines of code. The main driver for developing generalized software is development cost and schedule improvement. The goal is to ultimately have at least 80 percent of all software required for a spacecraft mission (within the domain supported by the GSS) to be configured from the generalized components.

Changes and challenges in the Software Engineering Laboratory

NASA Technical Reports Server (NTRS)

Pajerski, Rose

1994-01-01

Since 1976, the Software Engineering Laboratory (SEL) has been dedicated to understanding and improving the way in which one NASA organization, the Flight Dynamics Division (FDD), develops, maintains, and manages complex flight dynamics systems. The SEL is composed of three member organizations: NASA/GSFC, the University of Maryland, and Computer Sciences Corporation. During the past 18 years, the SEL's overall goal has remained the same: to improve the FDD's software products and processes in a measured manner. This requires that each development and maintenance effort be viewed, in part, as a SEL experiment which examines a specific technology or builds a model of interest for use on subsequent efforts. The SEL has undertaken many technology studies while developing operational support systems for numerous NASA spacecraft missions.

The Deep Space Network

NASA Technical Reports Server (NTRS)

1979-01-01

Deep Space Network progress in flight project support, tracking and data acquisition, research and technology, network engineering, hardware and software implementation, and operations is cited. Topics covered include: tracking and ground based navigation; spacecraft/ground communication; station control and operations technology; ground communications; and deep space stations.

NASA integrated vehicle health management technology experiment for X-37

NASA Astrophysics Data System (ADS)

Schwabacher, Mark; Samuels, Jeff; Brownston, Lee

2002-07-01

The NASA Integrated Vehicle Health Management (IVHM) Technology Experiment for X-37 was intended to run IVHM software on board the X-37 spacecraft. The X-37 is an unpiloted vehicle designed to orbit the Earth for up to 21 days before landing on a runway. The objectives of the experiment were to demonstrate the benefits of in-flight IVHM to the operation of a Reusable Launch Vehicle, to advance the Technology Readiness Level of this IVHM technology within a flight environment, and to demonstrate that the IVHM software could operate on the Vehicle Management Computer. The scope of the experiment was to perform real-time fault detection and isolation for X-37's electrical power system and electro-mechanical actuators. The experiment used Livingstone, a software system that performs diagnosis using a qualitative, model-based reasoning approach that searches system-wide interactions to detect and isolate failures. Two of the challenges we faced were to make this research software more efficient so that it would fit within the limited computational resources that were available to us on the X-37 spacecraft, and to modify it so that it satisfied the X-37's software safety requirements. Although the experiment is currently unfunded, the development effort resulted in major improvements in Livingstone's efficiency and safety. This paper reviews some of the details of the modeling and integration efforts, and some of the lessons that were learned.

Radio astronomy Explorer-B postlaunch attitude operations analysis

NASA Technical Reports Server (NTRS)

Werking, R. D.; Berg, R.; Brokke, K.; Hattox, T.; Lerner, G.; Stewart, D.; Williams, R.

1974-01-01

The attitude support activities of the Radio Astronomy Explorer-B are reported. The performance of the spacecraft hardware and software are discussed along with details of the mission events, from launch through main boom deployment. Reproductions of displays are presented which were used during support activities. The interactive graphics proved the support function by providing the quality control necessary to ensure mission success in an environment where flight simulated ground testing of spacecraft hardware cannot be performed.

Use of the MATRIXx Integrated Toolkit on the Microwave Anisotropy Probe Attitude Control System

NASA Technical Reports Server (NTRS)

Ward, David K.; Andrews, Stephen F.; McComas, David C.; ODonnell, James R., Jr.

1999-01-01

Recent advances in analytical software tools allow the analysis, simulation, flight code, and documentation of an algorithm to be generated from a single source, all within one integrated analytical design package. NASA's Microwave Anisotropy Probe project has used one such package, Integrated Systems' MATRIXx suite, in the design of the spacecraft's Attitude Control System. The project's experience with the linear analysis, simulation, code generation, and documentation tools will be presented and compared with more traditional development tools. In particular, the quality of the flight software generated will be examined in detail. Finally, lessons learned on each of the tools will be shared.

Software Certification - Coding, Code, and Coders

NASA Technical Reports Server (NTRS)

Havelund, Klaus; Holzmann, Gerard J.

2011-01-01

We describe a certification approach for software development that has been adopted at our organization. JPL develops robotic spacecraft for the exploration of the solar system. The flight software that controls these spacecraft is considered to be mission critical. We argue that the goal of a software certification process cannot be the development of "perfect" software, i.e., software that can be formally proven to be correct under all imaginable and unimaginable circumstances. More realistically, the goal is to guarantee a software development process that is conducted by knowledgeable engineers, who follow generally accepted procedures to control known risks, while meeting agreed upon standards of workmanship. We target three specific issues that must be addressed in such a certification procedure: the coding process, the code that is developed, and the skills of the coders. The coding process is driven by standards (e.g., a coding standard) and tools. The code is mechanically checked against the standard with the help of state-of-the-art static source code analyzers. The coders, finally, are certified in on-site training courses that include formal exams.

Imaging Sensor Flight and Test Equipment Software

NASA Technical Reports Server (NTRS)

Freestone, Kathleen; Simeone, Louis; Robertson, Byran; Frankford, Maytha; Trice, David; Wallace, Kevin; Wilkerson, DeLisa

2007-01-01

The Lightning Imaging Sensor (LIS) is one of the components onboard the Tropical Rainfall Measuring Mission (TRMM) satellite, and was designed to detect and locate lightning over the tropics. The LIS flight code was developed to run on a single onboard digital signal processor, and has operated the LIS instrument since 1997 when the TRMM satellite was launched. The software provides controller functions to the LIS Real-Time Event Processor (RTEP) and onboard heaters, collects the lightning event data from the RTEP, compresses and formats the data for downlink to the satellite, collects housekeeping data and formats the data for downlink to the satellite, provides command processing and interface to the spacecraft communications and data bus, and provides watchdog functions for error detection. The Special Test Equipment (STE) software was designed to operate specific test equipment used to support the LIS hardware through development, calibration, qualification, and integration with the TRMM spacecraft. The STE software provides the capability to control instrument activation, commanding (including both data formatting and user interfacing), data collection, decompression, and display and image simulation. The LIS STE code was developed for the DOS operating system in the C programming language. Because of the many unique data formats implemented by the flight instrument, the STE software was required to comprehend the same formats, and translate them for the test operator. The hardware interfaces to the LIS instrument using both commercial and custom computer boards, requiring that the STE code integrate this variety into a working system. In addition, the requirement to provide RTEP test capability dictated the need to provide simulations of background image data with short-duration lightning transients superimposed. This led to the development of unique code used to control the location, intensity, and variation above background for simulated lightning strikes at user-selected locations.

Orbit Determination and Navigation of the Solar Terrestrial Relations Observatory (STEREO)

NASA Technical Reports Server (NTRS)

Mesarch, Michael A.; Robertson, Mika; Ottenstein, Neil; Nicholson, Ann; Nicholson, Mark; Ward, Douglas T.; Cosgrove, Jennifer; German, Darla; Hendry, Stephen; Shaw, James

2007-01-01

This paper provides an overview of the required upgrades necessary for navigation of NASA's twin heliocentric science missions, Solar TErestrial RElations Observatory (STEREO) Ahead and Behind. The orbit determination of the STEREO spacecraft was provided by the NASA Goddard Space Flight Center's (GSFC) Flight Dynamics Facility (FDF) in support of the mission operations activities performed by the Johns Hopkins University Applied Physics Laboratory (APL). The changes to FDF's orbit determination software included modeling upgrades as well as modifications required to process the Deep Space Network X-band tracking data used for STEREO. Orbit results as well as comparisons to independently computed solutions are also included. The successful orbit determination support aided in maneuvering the STEREO spacecraft, launched on October 26, 2006 (00:52 Z), to target the lunar gravity assists required to place the spacecraft into their final heliocentric drift-away orbits where they are providing stereo imaging of the Sun.

Orbit Determination and Navigation of the Solar Terrestrial Relations Observatory (STEREO)

NASA Technical Reports Server (NTRS)

Mesarch, Michael; Robertson, Mika; Ottenstein, Neil; Nicholson, Ann; Nicholson, Mark; Ward, Douglas T.; Cosgrove, Jennifer; German, Darla; Hendry, Stephen; Shaw, James

2007-01-01

This paper provides an overview of the required upgrades necessary for navigation of NASA's twin heliocentric science missions, Solar TErestrial RElations Observatory (STEREO) Ahead and Behind. The orbit determination of the STEREO spacecraft was provided by the NASA Goddard Space Flight Center's (GSFC) Flight Dynamics Facility (FDF) in support of the mission operations activities performed by the Johns Hopkins University Applied Physics Laboratory (APL). The changes to FDF s orbit determination software included modeling upgrades as well as modifications required to process the Deep Space Network X-band tracking data used for STEREO. Orbit results as well as comparisons to independently computed solutions are also included. The successful orbit determination support aided in maneuvering the STEREO spacecraft, launched on October 26, 2006 (00:52 Z), to target the lunar gravity assists required to place the spacecraft into their final heliocentric drift-away orbits where they are providing stereo imaging of the Sun.

Spacecraft fault tolerance: The Magellan experience

NASA Technical Reports Server (NTRS)

Kasuda, Rick; Packard, Donna Sexton

1993-01-01

Interplanetary and earth orbiting missions are now imposing unique fault tolerant requirements upon spacecraft design. Mission success is the prime motivator for building spacecraft with fault tolerant systems. The Magellan spacecraft had many such requirements imposed upon its design. Magellan met these requirements by building redundancy into all the major subsystem components and designing the onboard hardware and software with the capability to detect a fault, isolate it to a component, and issue commands to achieve a back-up configuration. This discussion is limited to fault protection, which is the autonomous capability to respond to a fault. The Magellan fault protection design is discussed, as well as the developmental and flight experiences and a summary of the lessons learned.

Spacecraft attitude control using a smart control system

NASA Technical Reports Server (NTRS)

Buckley, Brian; Wheatcraft, Louis

1992-01-01

Traditionally, spacecraft attitude control has been implemented using control loops written in native code for a space hardened processor. The Naval Research Lab has taken this approach during the development of the Attitude Control Electronics (ACE) package. After the system was developed and delivered, NRL decided to explore alternate technologies to accomplish this same task more efficiently. The approach taken by NRL was to implement the ACE control loops using systems technologies. The purpose of this effort was to: (1) research capabilities required of an expert system in processing a classic closed-loop control algorithm; (2) research the development environment required to design and test an embedded expert systems environment; (3) research the complexity of design and development of expert systems versus a conventional approach; and (4) test the resulting systems against the flight acceptance test software for both response and accuracy. Two expert systems were selected to implement the control loops. Criteria used for the selection of the expert systems included that they had to run in both embedded systems and ground based environments. Using two different expert systems allowed a comparison of the real-time capabilities, inferencing capabilities, and the ground-based development environment. The two expert systems chosen for the evaluation were Spacecraft Command Language (SCL), and NEXTPERT Object. SCL is a smart control system produced for the NRL by Interface and Control Systems (ICS). SCL was developed to be used for real-time command, control, and monitoring of a new generation of spacecraft. NEXPERT Object is a commercially available product developed by Neuron Data. Results of the effort were evaluated using the ACE test bed. The ACE test bed had been developed and used to test the original flight hardware and software using simulators and flight-like interfaces. The test bed was used for testing the expert systems in a 'near-flight' environment. The technical approach, the system architecture, the development environments, knowledge base development, and results of this effort are detailed.

Certification Processes for Safety-Critical and Mission-Critical Aerospace Software

NASA Technical Reports Server (NTRS)

Nelson, Stacy

2003-01-01

This document is a quick reference guide with an overview of the processes required to certify safety-critical and mission-critical flight software at selected NASA centers and the FAA. Researchers and software developers can use this guide to jumpstart their understanding of how to get new or enhanced software onboard an aircraft or spacecraft. The introduction contains aerospace industry definitions of safety and safety-critical software, as well as, the current rationale for certification of safety-critical software. The Standards for Safety-Critical Aerospace Software section lists and describes current standards including NASA standards and RTCA DO-178B. The Mission-Critical versus Safety-Critical software section explains the difference between two important classes of software: safety-critical software involving the potential for loss of life due to software failure and mission-critical software involving the potential for aborting a mission due to software failure. The DO-178B Safety-critical Certification Requirements section describes special processes and methods required to obtain a safety-critical certification for aerospace software flying on vehicles under auspices of the FAA. The final two sections give an overview of the certification process used at Dryden Flight Research Center and the approval process at the Jet Propulsion Lab (JPL).

Intelligence Applied to Air Vehicles

NASA Technical Reports Server (NTRS)

Rosen, Robert; Gross, Anthony R.; Fletcher, L. Skip; Zornetzer, Steven (Technical Monitor)

2000-01-01

The exponential growth in information technology has provided the potential for air vehicle capabilities that were previously unavailable to mission and vehicle designers. The increasing capabilities of computer hardware and software, including new developments such as neural networks, provide a new balance of work between humans and machines. This paper will describe several NASA projects, and review results and conclusions from ground and flight investigations where vehicle intelligence was developed and applied to aeronautical and space systems. In the first example, flight results from a neural network flight control demonstration will be reviewed. Using, a highly-modified F-15 aircraft, a NASA/Dryden experimental flight test program has demonstrated how the neural network software can correctly identify and respond to changes in aircraft stability and control characteristics. Using its on-line learning capability, the neural net software would identify that something in the vehicle has changed, then reconfigure the flight control computer system to adapt to those changes. The results of the Remote Agent software project will be presented. This capability will reduce the cost of future spacecraft operations as computers become "thinking" partners along with humans. In addition, the paper will describe the objectives and plans for the autonomous airplane program and the autonomous rotorcraft project. Technologies will also be developed.

VML 3.0 Reactive Sequencing Objects and Matrix Math Operations for Attitude Profiling

NASA Technical Reports Server (NTRS)

Grasso, Christopher A.; Riedel, Joseph E.

2012-01-01

VML (Virtual Machine Language) has been used as the sequencing flight software on over a dozen JPL deep-space missions, most recently flying on GRAIL and JUNO. In conjunction with the NASA SBIR entitled "Reactive Rendezvous and Docking Sequencer", VML version 3.0 has been enhanced to include object-oriented element organization, built-in queuing operations, and sophisticated matrix / vector operations. These improvements allow VML scripts to easily perform much of the work that formerly would have required a great deal of expensive flight software development to realize. Autonomous turning and tracking makes considerable use of new VML features. Profiles generated by flight software are managed using object-oriented VML data constructs executed in discrete time by the VML flight software. VML vector and matrix operations provide the ability to calculate and supply quaternions to the attitude controller flight software which produces torque requests. Using VML-based attitude planning components eliminates flight software development effort, and reduces corresponding costs. In addition, the direct management of the quaternions allows turning and tracking to be tied in with sophisticated high-level VML state machines. These state machines provide autonomous management of spacecraft operations during critical tasks like a hypothetic Mars sample return rendezvous and docking. State machines created for autonomous science observations can also use this sort of attitude planning system, allowing heightened autonomy levels to reduce operations costs. VML state machines cannot be considered merely sequences - they are reactive logic constructs capable of autonomous decision making within a well-defined domain. The state machine approach enabled by VML 3.0 is progressing toward flight capability with a wide array of applicable mission activities.

The Use of Modeling for Flight Software Engineering on SMAP

NASA Technical Reports Server (NTRS)

Murray, Alexander; Jones, Chris G.; Reder, Leonard; Cheng, Shang-Wen

2011-01-01

The Soil Moisture Active Passive (SMAP) mission proposes to deploy an Earth-orbiting satellite with the goal of obtaining global maps of soil moisture content at regular intervals. Launch is currently planned in 2014. The spacecraft bus would be built at the Jet Propulsion Laboratory (JPL), incorporating both new avionics as well as hardware and software heritage from other JPL projects. [4] provides a comprehensive overview of the proposed mission

NASA Tech Briefs, February 2004

NASA Technical Reports Server (NTRS)

2004-01-01

Topics include: Simulation Testing of Embedded Flight Software; Improved Indentation Test for Measuring Nonlinear Elasticity; Ultraviolet-Absorption Spectroscopic Biofilm Monitor; Electronic Tongue for Quantitation of Contaminants in Water; Radar for Measuring Soil Moisture Under Vegetation; Modular Wireless Data-Acquisition and Control System; Microwave System for Detecting Ice on Aircraft; Routing Algorithm Exploits Spatial Relations; Two-Finger EKG Method of Detecting Evasive Responses; Updated System-Availability and Resource-Allocation Program; Routines for Computing Pressure Drops in Venturis; Software for Fault-Tolerant Matrix Multiplication; Reproducible Growth of High-Quality Cubic-SiC Layers; Nonlinear Thermoelastic Model for SMAs and SMA Hybrid Composites; Liquid-Crystal Thermosets, a New Generation of High-Performance Liquid-Crystal Polymers; Formulations for Stronger Solid Oxide Fuel-Cell Electrolytes; Simulation of Hazards and Poses for a Rocker-Bogie Rover; Autonomous Formation Flight; Expandable Purge Chambers Would Protect Cryogenic Fittings; Wavy-Planform Helicopter Blades Make Less Noise; Miniature Robotic Spacecraft for Inspecting Other Spacecraft; Miniature Ring-Shaped Peristaltic Pump; Compact Plasma Accelerator; Improved Electrohydraulic Linear Actuators; A Software Architecture for Semiautonomous Robot Control; Fabrication of Channels for Nanobiotechnological Devices; Improved Thin, Flexible Heat Pipes; Miniature Radioisotope Thermoelectric Power Cubes; Permanent Sequestration of Emitted Gases in the Form of Clathrate Hydrates; Electrochemical, H2O2-Boosted Catalytic Oxidation System; Electrokinetic In Situ Treatment of Metal-Contaminated Soil; Pumping Liquid Oxygen by Use of Pulsed Magnetic Fields; Magnetocaloric Pumping of Liquid Oxygen; Tailoring Ion-Thruster Grid Apertures for Greater Efficiency; and Lidar for Guidance of a Spacecraft or Exploratory Robot.

Optical Navigation Preparations for New Horizons Pluto Flyby

NASA Technical Reports Server (NTRS)

Owen, William M., Jr.; Dumont, Philip J.; Jackman, Coralie D.

2012-01-01

The New Horizons spacecraft will encounter Pluto and its satellites in July 2015. As was the case for the Voyager encounters with Jupiter, Saturn, Uranus and Neptune, mission success will depend heavily on accurate spacecraft navigation, and accurate navigation will be impossible without the use of pictures of the Pluto system taken by the onboard cameras. We describe the preparations made by the New Horizons optical navigators: picture planning, image processing algorithms, software development and testing, and results from in-flight imaging.

Thrust vector control algorithm design for the Cassini spacecraft

NASA Technical Reports Server (NTRS)

Enright, Paul J.

1993-01-01

This paper describes a preliminary design of the thrust vector control algorithm for the interplanetary spacecraft, Cassini. Topics of discussion include flight software architecture, modeling of sensors, actuators, and vehicle dynamics, and controller design and analysis via classical methods. Special attention is paid to potential interactions with structural flexibilities and propellant dynamics. Controller performance is evaluated in a simulation environment built around a multi-body dynamics model, which contains nonlinear models of the relevant hardware and preliminary versions of supporting attitude determination and control functions.

SLS Flight Software Testing: Using a Modified Agile Software Testing Approach

NASA Technical Reports Server (NTRS)

Bolton, Albanie T.

2016-01-01

NASA's Space Launch System (SLS) is an advanced launch vehicle for a new era of exploration beyond earth's orbit (BEO). The world's most powerful rocket, SLS, will launch crews of up to four astronauts in the agency's Orion spacecraft on missions to explore multiple deep-space destinations. Boeing is developing the SLS core stage, including the avionics that will control vehicle during flight. The core stage will be built at NASA's Michoud Assembly Facility (MAF) in New Orleans, LA using state-of-the-art manufacturing equipment. At the same time, the rocket's avionics computer software is being developed here at Marshall Space Flight Center in Huntsville, AL. At Marshall, the Flight and Ground Software division provides comprehensive engineering expertise for development of flight and ground software. Within that division, the Software Systems Engineering Branch's test and verification (T&V) team uses an agile test approach in testing and verification of software. The agile software test method opens the door for regular short sprint release cycles. The idea or basic premise behind the concept of agile software development and testing is that it is iterative and developed incrementally. Agile testing has an iterative development methodology where requirements and solutions evolve through collaboration between cross-functional teams. With testing and development done incrementally, this allows for increased features and enhanced value for releases. This value can be seen throughout the T&V team processes that are documented in various work instructions within the branch. The T&V team produces procedural test results at a higher rate, resolves issues found in software with designers at an earlier stage versus at a later release, and team members gain increased knowledge of the system architecture by interfacing with designers. SLS Flight Software teams want to continue uncovering better ways of developing software in an efficient and project beneficial manner. Through agile testing, there has been increased value through individuals and interactions over processes and tools, improved customer collaboration, and improved responsiveness to changes through controlled planning. The presentation will describe agile testing methodology as taken with the SLS FSW Test and Verification team at Marshall Space Flight Center.

Software Analyzes Complex Systems in Real Time

NASA Technical Reports Server (NTRS)

2008-01-01

Expert system software programs, also known as knowledge-based systems, are computer programs that emulate the knowledge and analytical skills of one or more human experts, related to a specific subject. SHINE (Spacecraft Health Inference Engine) is one such program, a software inference engine (expert system) designed by NASA for the purpose of monitoring, analyzing, and diagnosing both real-time and non-real-time systems. It was developed to meet many of the Agency s demanding and rigorous artificial intelligence goals for current and future needs. NASA developed the sophisticated and reusable software based on the experience and requirements of its Jet Propulsion Laboratory s (JPL) Artificial Intelligence Research Group in developing expert systems for space flight operations specifically, the diagnosis of spacecraft health. It was designed to be efficient enough to operate in demanding real time and in limited hardware environments, and to be utilized by non-expert systems applications written in conventional programming languages. The technology is currently used in several ongoing NASA applications, including the Mars Exploration Rovers and the Spacecraft Health Automatic Reasoning Pilot (SHARP) program for the diagnosis of telecommunication anomalies during the Neptune Voyager Encounter. It is also finding applications outside of the Space Agency.

Model-Based Verification and Validation of Spacecraft Avionics

NASA Technical Reports Server (NTRS)

Khan, M. Omair; Sievers, Michael; Standley, Shaun

2012-01-01

Verification and Validation (V&V) at JPL is traditionally performed on flight or flight-like hardware running flight software. For some time, the complexity of avionics has increased exponentially while the time allocated for system integration and associated V&V testing has remained fixed. There is an increasing need to perform comprehensive system level V&V using modeling and simulation, and to use scarce hardware testing time to validate models; the norm for thermal and structural V&V for some time. Our approach extends model-based V&V to electronics and software through functional and structural models implemented in SysML. We develop component models of electronics and software that are validated by comparison with test results from actual equipment. The models are then simulated enabling a more complete set of test cases than possible on flight hardware. SysML simulations provide access and control of internal nodes that may not be available in physical systems. This is particularly helpful in testing fault protection behaviors when injecting faults is either not possible or potentially damaging to the hardware. We can also model both hardware and software behaviors in SysML, which allows us to simulate hardware and software interactions. With an integrated model and simulation capability we can evaluate the hardware and software interactions and identify problems sooner. The primary missing piece is validating SysML model correctness against hardware; this experiment demonstrated such an approach is possible.

Orion Powered Flight Guidance Burn Options for Near Term Exploration

NASA Technical Reports Server (NTRS)

Fill, Tom; Goodman, John; Robinson, Shane

2018-01-01

NASA's Orion exploration spacecraft will fly more demanding mission profiles than previous NASA human flight spacecraft. Missions currently under development are destined for cislunar space. The EM-1 mission will fly unmanned to a Distant Retrograde Orbit (DRO) around the Moon. EM-2 will fly astronauts on a mission to the lunar vicinity. To fly these missions, Orion requires powered flight guidance that is more sophisticated than the orbital guidance flown on Apollo and the Space Shuttle. Orion's powered flight guidance software contains five burn guidance options. These five options are integrated into an architecture based on a proven shuttle heritage design, with a simple closed-loop guidance strategy. The architecture provides modularity, simplicity, versatility, and adaptability to future, yet-to-be-defined, exploration mission profiles. This paper provides a summary of the executive guidance architecture and details the five burn options to support both the nominal and abort profiles for the EM-1 and EM-2 missions.

Orion's Powered Flight Guidance Burn Options for Near Term Exploration Missions

NASA Technical Reports Server (NTRS)

Fill, Thomas; Goodman, John; Robinson, Shane

2018-01-01

NASA's Orion exploration spacecraft will fly more demanding mission profiles than previous NASA human flight spacecraft. Missions currently under development are destined for cislunar space. The EM-1 mission will fly unmanned to a Distant Retrograde Orbit (DRO) around the Moon. EM-2 will fly astronauts on a mission to the lunar vicinity. To fly these missions, Orion requires powered flight guidance that is more sophisticated than the orbital guidance flown on Apollo and the Space Shuttle. Orion's powered flight guidance software contains five burn guidance options. These five options are integrated into an architecture based on a proven shuttle heritage design, with a simple closed-loop guidance strategy. The architecture provides modularity, simplicity, versatility, and adaptability to future, yet-to-be-defined, exploration mission profiles. This paper provides a summary of the executive guidance architecture and details the five burn options to support both the nominal and abort profiles for the EM-1 and EM-2 missions.

A Solar Sailcraft Simulation Application

ERIC Educational Resources Information Center

Celeda, Tomáš

2013-01-01

An application was created to encourage students' practical knowledge of gravitational fields, the law of conservation of energy and other phenomena, such as gravitational slingshots. The educational software simulates the flight of a solar sail spacecraft between two planets of the Solar System using the laws of gravity and radiation…

REACH: Real-Time Data Awareness in Multi-Spacecraft Missions

NASA Technical Reports Server (NTRS)

Maks, Lori; Coleman, Jason; Obenschain, Arthur F. (Technical Monitor)

2002-01-01

Missions have been proposed that will use multiple spacecraft to perform scientific or commercial tasks. Indeed, in the commercial world, some spacecraft constellations already exist. Aside from the technical challenges of constructing and flying these missions, there is also the financial challenge presented by the tradition model of the flight operations team (FOT) when it is applied to a constellation mission. Proposed constellation missions range in size from three spacecraft to more than 50. If the current ratio of three-to-five FOT personnel per spacecraft is maintained, the size of the FOT becomes cost prohibitive. The Advanced Architectures and Automation Branch at the Goddard Space Flight Center (GSFC Code 588) saw the potential to reduce the cost of these missions by creating new user interfaces to the ground system health-and-safety data. The goal is to enable a smaller FOT to remain aware and responsive to the increased amount of ground system information in a multi-spacecraft environment. Rather than abandon the tried and true, these interfaces were developed to run alongside existing ground system software to provide additional support to the FOT. These new user interfaces have been combined in a tool called REACH. REACH-the Real-time Evaluation and Analysis of Consolidated Health-is a software product that uses advanced visualization techniques to make spacecraft anomalies easy to spot, no matter how many spacecraft are in the constellation. REACH reads a real-time stream of data from the ground system and displays it to the FOT such that anomalies are easy to pick out and investigate. Data visualization has been used in ground system operations for many years. To provide a unique visualization tool, we developed a unique source of data to visualize: the REACH Health Model Engine. The Health Model Engine is rule-based software that receives real-time telemetry information and outputs "health" information related to the subsystems and spacecraft that the telemetry belong to. The Health Engine can run out-of-the-box or can be tailored with a scripting language. Out of the box, it uses limit violations to determine the health of subsystems and spacecraft; when tailored, it determines health using equations combining the values and limits of any telemetry in the spacecraft. The REACH visualizations then "roll up" the information from the Health Engine into high level, summary displays. These summary visualizations can be "zoomed" into for increasing levels of detail. Currently REACH is installed in the Small Explorer (SMEX) lab at GSFC, and is monitoring three of their five spacecraft. We are scheduled to install REACH in the Mid-sized Explorer (MIDEX) lab, which will allow us to monitor up to six more spacecraft. The process of installing and using our "research" software in an operational environment has provided many insights into which parts of REACH are a step forward and which of our ideas are missteps. Our paper explores both the new concepts in spacecraft health-and-safety visualization, the difficulties of such systems in the operational environment, and the cost and safety issues of multi-spacecraft missions.

Wake Cycle Robustness of the Mars Science Laboratory Flight Software

NASA Technical Reports Server (NTRS)

Whitehill, Robert

2011-01-01

The Mars Science Laboratory (MSL) is a spacecraft being developed by the Jet Propulsion Laboratory (JPL) for the purpose of in-situ exploration on the surface of Mars. The objective of MSL is to explore and quantitatively assess a local region on the Martian surface as a habitat for microbial life, past or present. This objective will be accomplished through the assessment of the biological potential of at least one target environment, the characterization of the geology and geochemistry of the landing region, an investigation of the planetary process relevant to past habitability, and a characterization of surface radiation. For this purpose, MSL incorporates a total of ten scientific instruments for which functions are to include, among others, atmospheric and descent imaging, chemical composition analysis, and radiation measurement. The Flight Software (FSW) system is responsible for all mission phases, including launch, cruise, entry-descent-landing, and surface operation of the rover. Because of the essential nature of flight software to project success, each of the software modules is undergoing extensive testing to identify and correct errors.

Simulation for Prediction of Entry Article Demise (SPEAD): An Analysis Tool for Spacecraft Safety Analysis and Ascent/Reentry Risk Assessment

NASA Technical Reports Server (NTRS)

Ling, Lisa

2014-01-01

For the purpose of performing safety analysis and risk assessment for a potential off-nominal atmospheric reentry resulting in vehicle breakup, a synthesis of trajectory propagation coupled with thermal analysis and the evaluation of node failure is required to predict the sequence of events, the timeline, and the progressive demise of spacecraft components. To provide this capability, the Simulation for Prediction of Entry Article Demise (SPEAD) analysis tool was developed. The software and methodology have been validated against actual flights, telemetry data, and validated software, and safety/risk analyses were performed for various programs using SPEAD. This report discusses the capabilities, modeling, validation, and application of the SPEAD analysis tool.

The NASA Integrated Vehicle Health Management Technology Experiment for X-37

NASA Technical Reports Server (NTRS)

Schwabacher, Mark; Samuels, Jeff; Brownston, Lee; Clancy, Daniel (Technical Monitor)

2002-01-01

The NASA Integrated Vehicle Health Management (IVHM) Technology Experiment for X-37 was intended to run IVHM software on-board the X-37 spacecraft. The X-37 is intended to be an unpiloted vehicle that would orbit the Earth for up to 21 days before landing on a runway. The objectives of the experiment were to demonstrate the benefits of in-flight IVHM to the operation of a Reusable Launch Vehicle, to advance the Technology Readiness Level of this IVHM technology within a flight environment, and to demonstrate that the IVHM software could operate on the Vehicle Management Computer. The scope of the experiment was to perform real-time fault detection and isolation for X-37's electrical power system and electro-mechanical actuators. The experiment used Livingstone, a software system that performs diagnosis using a qualitative, model-based reasoning approach that searches system-wide interactions to detect and isolate failures. Two of the challenges we faced were to make this research software more efficient so that it would fit within the limited computational resources that were available to us on the X-37 spacecraft, and to modify it so that it satisfied the X-37's software safety requirements. Although the experiment is currently unfunded, the development effort had value in that it resulted in major improvements in Livingstone's efficiency and safety. This paper reviews some of the details of the modeling and integration efforts, and some of the lessons that were learned.

An Internet Protocol-Based Software System for Real-Time, Closed-Loop, Multi-Spacecraft Mission Simulation Applications

NASA Technical Reports Server (NTRS)

Burns, Richard D.; Davis, George; Cary, Everett; Higinbotham, John; Hogie, Keith

2003-01-01

A mission simulation prototype for Distributed Space Systems has been constructed using existing developmental hardware and software testbeds at NASA s Goddard Space Flight Center. A locally distributed ensemble of testbeds, connected through the local area network, operates in real time and demonstrates the potential to assess the impact of subsystem level modifications on system level performance and, ultimately, on the quality and quantity of the end product science data.

TDRSS Onboard Navigation System (TONS) flight qualification experiment

NASA Technical Reports Server (NTRS)

Gramling, C. J.; Hart, R. C.; Folta, D. C.; Long, A. C.

1994-01-01

The National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) is currently developing an operational Tracking and Data Relay Satellite (TDRS) System (TDRSS) Onboard Navigation System (TONS) to provide realtime, autonomous, high-accuracy navigation products to users of TDRSS. A TONS experiment was implemented on the Explorer Platform/Extreme Ultraviolet Explorer (EP/EUVE) spacecraft, launched June 7, 1992, to flight qualify the TONS operational system using TDRSS forward-link communications services. This paper provides a detailed evaluation of the flight hardware, an ultrastable oscillator (USO) and Doppler extractor (DE) card in one of the TDRSS user transponders and the ground-based prototype flight software performance, based on the 1 year of TONS experiment operation. The TONS experiment results are used to project the expected performance of the TONS 1 operational system. TONS 1 processes Doppler data derived from scheduled forward-link S-band services using a sequential estimation algorithm enhanced by a sophisticated process noise model to provide onboard orbit and frequency determination and time maintenance. TONS 1 will be the prime navigation system on the Earth Observing System (EOS)-AM1 spacecraft, currently scheduled for launch in 1998. Inflight evaluation of the USO and DE short-term and long-term stability indicates that the performance is excellent. Analysis of the TONS prototype flight software performance indicates that realtime onboard position accuracies of better than 25 meters root-mean-square are achievable with one tracking contact every one to two orbits for the EP/EUVE 525-kilometer altitude, 28.5 degree inclination orbit. The success of the TONS experiment demonstrates the flight readiness of TONS to support the EOS-AM1 mission.

Evolutionary Telemetry and Command Processor (TCP) architecture

NASA Technical Reports Server (NTRS)

Schneider, John R.

1992-01-01

A low cost, modular, high performance, and compact Telemetry and Command Processor (TCP) is being built as the foundation of command and data handling subsystems for the next generation of satellites. The TCP product line will support command and telemetry requirements for small to large spacecraft and from low to high rate data transmission. It is compatible with the latest TDRSS, STDN and SGLS transponders and provides CCSDS protocol communications in addition to standard TDM formats. Its high performance computer provides computing resources for hosted flight software. Layered and modular software provides common services using standardized interfaces to applications thereby enhancing software re-use, transportability, and interoperability. The TCP architecture is based on existing standards, distributed networking, distributed and open system computing, and packet technology. The first TCP application is planned for the 94 SDIO SPAS 3 mission. The architecture enhances rapid tailoring of functions thereby reducing costs and schedules developed for individual spacecraft missions.

Spot: A Programming Language for Verified Flight Software

NASA Technical Reports Server (NTRS)

Bocchino, Robert L., Jr.; Gamble, Edward; Gostelow, Kim P.; Some, Raphael R.

2014-01-01

The C programming language is widely used for programming space flight software and other safety-critical real time systems. C, however, is far from ideal for this purpose: as is well known, it is both low-level and unsafe. This paper describes Spot, a language derived from C for programming space flight systems. Spot aims to maintain compatibility with existing C code while improving the language and supporting verification with the SPIN model checker. The major features of Spot include actor-based concurrency, distributed state with message passing and transactional updates, and annotations for testing and verification. Spot also supports domain-specific annotations for managing spacecraft state, e.g., communicating telemetry information to the ground. We describe the motivation and design rationale for Spot, give an overview of the design, provide examples of Spot's capabilities, and discuss the current status of the implementation.

Magellan spacecraft and memory state tracking: Lessons learned, future thoughts

NASA Technical Reports Server (NTRS)

Bucher, Allen W.

1993-01-01

Numerous studies have been dedicated to improving the two main elements of Spacecraft Mission Operations: Command and Telemetry. As a result, not much attention has been given to other tasks that can become tedious, repetitive, and error prone. One such task is Spacecraft and Memory State Tracking, the process by which the status of critical spacecraft components, parameters, and the contents of on-board memory are managed on the ground to maintain knowledge of spacecraft and memory states for future testing, anomaly investigation, and on-board memory reconstruction. The task of Spacecraft and Memory State Tracking has traditionally been a manual task allocated to Mission Operations Procedures. During nominal Mission Operations this job is tedious and error prone. Because the task is not complex and can be accomplished manually, the worth of a sophisticated software tool is often questioned. However, in the event of an anomaly which alters spacecraft components autonomously or a memory anomaly such as a corrupt memory or flight software error, an accurate ground image that can be reconstructed quickly is a priceless commodity. This study explores the process of Spacecraft and Memory State Tracking used by the Magellan Spacecraft Team highlighting its strengths as well as identifying lessons learned during the primary and extended missions, two memory anomalies, and other hardships encountered due to incomplete knowledge of spacecraft states. Ideas for future state tracking tools that require minimal user interaction and are integrated into the Ground Data System will also be discussed.

Magellan spacecraft and memory state tracking: Lessons learned, future thoughts

NASA Astrophysics Data System (ADS)

Bucher, Allen W.

1993-03-01

Numerous studies have been dedicated to improving the two main elements of Spacecraft Mission Operations: Command and Telemetry. As a result, not much attention has been given to other tasks that can become tedious, repetitive, and error prone. One such task is Spacecraft and Memory State Tracking, the process by which the status of critical spacecraft components, parameters, and the contents of on-board memory are managed on the ground to maintain knowledge of spacecraft and memory states for future testing, anomaly investigation, and on-board memory reconstruction. The task of Spacecraft and Memory State Tracking has traditionally been a manual task allocated to Mission Operations Procedures. During nominal Mission Operations this job is tedious and error prone. Because the task is not complex and can be accomplished manually, the worth of a sophisticated software tool is often questioned. However, in the event of an anomaly which alters spacecraft components autonomously or a memory anomaly such as a corrupt memory or flight software error, an accurate ground image that can be reconstructed quickly is a priceless commodity. This study explores the process of Spacecraft and Memory State Tracking used by the Magellan Spacecraft Team highlighting its strengths as well as identifying lessons learned during the primary and extended missions, two memory anomalies, and other hardships encountered due to incomplete knowledge of spacecraft states. Ideas for future state tracking tools that require minimal user interaction and are integrated into the Ground Data System will also be discussed.

Configuring the Orion Guidance, Navigation, and Control Flight Software for Automated Sequencing

NASA Technical Reports Server (NTRS)

Odegard, Ryan G.; Siliwinski, Tomasz K.; King, Ellis T.; Hart, Jeremy J.

2010-01-01

The Orion Crew Exploration Vehicle is being designed with greater automation capabilities than any other crewed spacecraft in NASA s history. The Guidance, Navigation, and Control (GN&C) flight software architecture is designed to provide a flexible and evolvable framework that accommodates increasing levels of automation over time. Within the GN&C flight software, a data-driven approach is used to configure software. This approach allows data reconfiguration and updates to automated sequences without requiring recompilation of the software. Because of the great dependency of the automation and the flight software on the configuration data, the data management is a vital component of the processes for software certification, mission design, and flight operations. To enable the automated sequencing and data configuration of the GN&C subsystem on Orion, a desktop database configuration tool has been developed. The database tool allows the specification of the GN&C activity sequences, the automated transitions in the software, and the corresponding parameter reconfigurations. These aspects of the GN&C automation on Orion are all coordinated via data management, and the database tool provides the ability to test the automation capabilities during the development of the GN&C software. In addition to providing the infrastructure to manage the GN&C automation, the database tool has been designed with capabilities to import and export artifacts for simulation analysis and documentation purposes. Furthermore, the database configuration tool, currently used to manage simulation data, is envisioned to evolve into a mission planning tool for generating and testing GN&C software sequences and configurations. A key enabler of the GN&C automation design, the database tool allows both the creation and maintenance of the data artifacts, as well as serving the critical role of helping to manage, visualize, and understand the data-driven parameters both during software development and throughout the life of the Orion project.

Flight performance of Skylab attitude and pointing control system

NASA Technical Reports Server (NTRS)

Chubb, W. B.; Kennel, H. F.; Rupp, C. C.; Seltzer, S. M.

1975-01-01

The Skylab attitude and pointing control system (APCS) requirements are briefly reviewed and the way in which they became altered during the prelaunch phase of development is noted. The actual flight mission (including mission alterations during flight) is described. The serious hardware failures that occurred, beginning during ascent through the atmosphere, also are described. The APCS's ability to overcome these failures and meet mission changes are presented. The large around-the-clock support effort on the ground is discussed. Salient design points and software flexibility that should afford pertinent experience for future spacecraft attitude and pointing control system designs are included.

Deep Space Networking Experiments on the EPOXI Spacecraft

NASA Technical Reports Server (NTRS)

Jones, Ross M.

2011-01-01

NASA's Space Communications & Navigation Program within the Space Operations Directorate is operating a program to develop and deploy Disruption Tolerant Networking [DTN] technology for a wide variety of mission types by the end of 2011. DTN is an enabling element of the Interplanetary Internet where terrestrial networking protocols are generally unsuitable because they rely on timely and continuous end-to-end delivery of data and acknowledgments. In fall of 2008 and 2009 and 2011 the Jet Propulsion Laboratory installed and tested essential elements of DTN technology on the Deep Impact spacecraft. These experiments, called Deep Impact Network Experiment (DINET 1) were performed in close cooperation with the EPOXI project which has responsibility for the spacecraft. The DINET 1 software was installed on the backup software partition on the backup flight computer for DINET 1. For DINET 1, the spacecraft was at a distance of about 15 million miles (24 million kilometers) from Earth. During DINET 1 300 images were transmitted from the JPL nodes to the spacecraft. Then, they were automatically forwarded from the spacecraft back to the JPL nodes, exercising DTN's bundle origination, transmission, acquisition, dynamic route computation, congestion control, prioritization, custody transfer, and automatic retransmission procedures, both on the spacecraft and on the ground, over a period of 27 days. The first DINET 1 experiment successfully validated many of the essential elements of the DTN protocols. DINET 2 demonstrated: 1) additional DTN functionality, 2) automated certain tasks which were manually implemented in DINET 1 and 3) installed the ION SW on nodes outside of JPL. DINET 3 plans to: 1) upgrade the LTP convergence-layer adapter to conform to the international LTP CL specification, 2) add convergence-layer "stewardship" procedures and 3) add the BSP security elements [PIB & PCB]. This paper describes the planning and execution of the flight experiment and the validation results.

Spitzer observatory operations: increasing efficiency in mission operations

NASA Astrophysics Data System (ADS)

Scott, Charles P.; Kahr, Bolinda E.; Sarrel, Marc A.

2006-06-01

This paper explores the how's and why's of the Spitzer Mission Operations System's (MOS) success, efficiency, and affordability in comparison to other observatory-class missions. MOS exploits today's flight, ground, and operations capabilities, embraces automation, and balances both risk and cost. With operational efficiency as the primary goal, MOS maintains a strong control process by translating lessons learned into efficiency improvements, thereby enabling the MOS processes, teams, and procedures to rapidly evolve from concept (through thorough validation) into in-flight implementation. Operational teaming, planning, and execution are designed to enable re-use. Mission changes, unforeseen events, and continuous improvement have often times forced us to learn to fly anew. Collaborative spacecraft operations and remote science and instrument teams have become well integrated, and worked together to improve and optimize each human, machine, and software-system element. Adaptation to tighter spacecraft margins has facilitated continuous operational improvements via automated and autonomous software coupled with improved human analysis. Based upon what we now know and what we need to improve, adapt, or fix, the projected mission lifetime continues to grow - as does the opportunity for numerous scientific discoveries.

Autonomous Aerobraking Development Software: Phase 2 Summary

NASA Technical Reports Server (NTRS)

Cianciolo, Alicia D.; Maddock, Robert W.; Prince, Jill L.; Bowes, Angela; Powell, Richard W.; White, Joseph P.; Tolson, Robert; O'Shaughnessy, Daniel; Carrelli, David

2013-01-01

NASA has used aerobraking at Mars and Venus to reduce the fuel required to deliver a spacecraft into a desired orbit compared to an all-propulsive solution. Although aerobraking reduces the propellant, it does so at the expense of mission duration, large staff, and DSN coverage. These factors make aerobraking a significant cost element in the mission design. By moving on-board the current ground-based tasks of ephemeris determination, atmospheric density estimation, and maneuver sizing and execution, a flight project would realize significant cost savings. The NASA Engineering and Safety Center (NESC) sponsored Phase 1 and 2 of the Autonomous Aerobraking Development Software (AADS) study, which demonstrated the initial feasibility of moving these current ground-based functions to the spacecraft. This paper highlights key state-of-the-art advancements made in the Phase 2 effort to verify that the AADS algorithms are accurate, robust and ready to be considered for application on future missions that utilize aerobraking. The advancements discussed herein include both model updates and simulation and benchmark testing. Rigorous testing using observed flight atmospheres, operational environments and statistical analysis characterized the AADS operability in a perturbed environment.

Gravity Probe B spacecraft description

NASA Astrophysics Data System (ADS)

Bennett, Norman R.; Burns, Kevin; Katz, Russell; Kirschenbaum, Jon; Mason, Gary; Shehata, Shawky

2015-11-01

The Gravity Probe B spacecraft, developed, integrated, and tested by Lockheed Missiles & Space Company and later Lockheed Martin Corporation, consisted of structures, mechanisms, command and data handling, attitude and translation control, electrical power, thermal control, flight software, and communications. When integrated with the payload elements, the integrated system became the space vehicle. Key requirements shaping the design of the spacecraft were: (1) the tight mission timeline (17 months, 9 days of on-orbit operation), (2) precise attitude and translational control, (3) thermal protection of science hardware, (4) minimizing aerodynamic, magnetic, and eddy current effects, and (5) the need to provide a robust, low risk spacecraft. The spacecraft met all mission requirements, as demonstrated by dewar lifetime meeting specification, positive power and thermal margins, precision attitude control and drag-free performance, reliable communications, and the collection of more than 97% of the available science data.

The Synergistic Engineering Environment

NASA Technical Reports Server (NTRS)

Cruz, Jonathan

2006-01-01

The Synergistic Engineering Environment (SEE) is a system of software dedicated to aiding the understanding of space mission operations. The SEE can integrate disparate sets of data with analytical capabilities, geometric models of spacecraft, and a visualization environment, all contributing to the creation of an interactive simulation of spacecraft. Initially designed to satisfy needs pertaining to the International Space Station, the SEE has been broadened in scope to include spacecraft ranging from those in low orbit around the Earth to those on deep-space missions. The SEE includes analytical capabilities in rigid-body dynamics, kinematics, orbital mechanics, and payload operations. These capabilities enable a user to perform real-time interactive engineering analyses focusing on diverse aspects of operations, including flight attitudes and maneuvers, docking of visiting spacecraft, robotic operations, impingement of spacecraft-engine exhaust plumes, obscuration of instrumentation fields of view, communications, and alternative assembly configurations. .

A demonstration of the value of spacecraft computers

NASA Astrophysics Data System (ADS)

Jenkins, R. E.

1984-09-01

The Transit Improvement Program TIP satellites were designed to upgrade the navigation satellite system. One of the improvements made in connection with these satellites is related to the employment of a general-purpose minicomputer. A description is provided of the uses of the TIP/Nova flight computer to overcome some early failures in the spacecraft development which, although later corrected, could have jeopardized the entire program. The flight computer and its software is discussed, taking into account the delayed command program, and the telemetry storage program. The effect of the failures is considered along with the post-launch operations. Attention is given to power management, spin-up operations, the firing of the orbit adjust rocket, the tumble-thrust program, a digital phase-locked loop for de-tumble, and the generation of a tumble motion.

KSC-98pc1382

NASA Image and Video Library

1998-10-24

KENNEDY SPACE CENTER, FLA. -- Lighting up the launch pad, a Boeing Delta II (7326) rocket propels Deep Space 1 through the morning clouds after liftoff from Launch Complex 17A, Cape Canaveral Air Station. The first flight in NASA's New Millennium Program, the spacecraft is designed to validate 12 new technologies for scientific space missions of the next century, including the ion propulsion engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

Attitude ground support system for the solar maximum mission spacecraft

NASA Technical Reports Server (NTRS)

Nair, G.

1980-01-01

The SMM attitude ground support system (AGSS) supports the acquisition of spacecraft roll attitude reference, performs the in-flight calibration of the attitude sensor complement, supports onboard control autonomy via onboard computer data base updates, and monitors onboard computer (OBC) performance. Initial roll attitude acquisition is accomplished by obtaining a coarse 3 axis attitude estimate from magnetometer and Sun sensor data and subsequently refining it by processing data from the fixed head star trackers. In-flight calibration of the attitude sensor complement is achieved by processing data from a series of slew maneuvers designed to maximize the observability and accuracy of the appropriate alignments and biases. To ensure autonomy of spacecraft operation, the AGSS selects guide stars and computes sensor occultation information for uplink to the OBC. The onboard attitude control performance is monitored on the ground through periodic attitude determination and processing of OBC data in downlink telemetry. In general, the control performance has met mission requirements. However, software and hardware problems have resulted in sporadic attitude reference losses.

An Internet Protocol-Based Software System for Real-Time, Closed-Loop, Multi-Spacecraft Mission Simulation Applications

NASA Technical Reports Server (NTRS)

Davis, George; Cary, Everett; Higinbotham, John; Burns, Richard; Hogie, Keith; Hallahan, Francis

2003-01-01

The paper will provide an overview of the web-based distributed simulation software system developed for end-to-end, multi-spacecraft mission design, analysis, and test at the NASA Goddard Space Flight Center (GSFC). This software system was developed for an internal research and development (IR&D) activity at GSFC called the Distributed Space Systems (DSS) Distributed Synthesis Environment (DSE). The long-term goal of the DSS-DSE is to integrate existing GSFC stand-alone test beds, models, and simulation systems to create a "hands on", end-to-end simulation environment for mission design, trade studies and simulations. The short-term goal of the DSE was therefore to develop the system architecture, and then to prototype the core software simulation capability based on a distributed computing approach, with demonstrations of some key capabilities by the end of Fiscal Year 2002 (FY02). To achieve the DSS-DSE IR&D objective, the team adopted a reference model and mission upon which FY02 capabilities were developed. The software was prototyped according to the reference model, and demonstrations were conducted for the reference mission to validate interfaces, concepts, etc. The reference model, illustrated in Fig. 1, included both space and ground elements, with functional capabilities such as spacecraft dynamics and control, science data collection, space-to-space and space-to-ground communications, mission operations, science operations, and data processing, archival and distribution addressed.

A Distributed Simulation Software System for Multi-Spacecraft Missions

NASA Technical Reports Server (NTRS)

Burns, Richard; Davis, George; Cary, Everett

2003-01-01

The paper will provide an overview of the web-based distributed simulation software system developed for end-to-end, multi-spacecraft mission design, analysis, and test at the NASA Goddard Space Flight Center (GSFC). This software system was developed for an internal research and development (IR&D) activity at GSFC called the Distributed Space Systems (DSS) Distributed Synthesis Environment (DSE). The long-term goal of the DSS-DSE is to integrate existing GSFC stand-alone test beds, models, and simulation systems to create a "hands on", end-to-end simulation environment for mission design, trade studies and simulations. The short-term goal of the DSE was therefore to develop the system architecture, and then to prototype the core software simulation capability based on a distributed computing approach, with demonstrations of some key capabilities by the end of Fiscal Year 2002 (FY02). To achieve the DSS-DSE IR&D objective, the team adopted a reference model and mission upon which FY02 capabilities were developed. The software was prototyped according to the reference model, and demonstrations were conducted for the reference mission to validate interfaces, concepts, etc. The reference model, illustrated in Fig. 1, included both space and ground elements, with functional capabilities such as spacecraft dynamics and control, science data collection, space-to-space and space-to-ground communications, mission operations, science operations, and data processing, archival and distribution addressed.

Mars Pathfinder Atmospheric Entry Navigation Operations

NASA Technical Reports Server (NTRS)

Braun, R. D.; Spencer, D. A.; Kallemeyn, P. H.; Vaughan, R. M.

1997-01-01

On July 4, 1997, after traveling close to 500 million km, the Pathfinder spacecraft successfully completed entry, descent, and landing, coming to rest on the surface of Mars just 27 km from its target point. In the present paper, the atmospheric entry and approach navigation activities required in support of this mission are discussed. In particular, the flight software parameter update and landing site prediction analyses performed by the Pathfinder operations navigation team are described. A suite of simulation tools developed during Pathfinder's design cycle, but extendible to Pathfinder operations, are also presented. Data regarding the accuracy of the primary parachute deployment algorithm is extracted from the Pathfinder flight data, demonstrating that this algorithm performed as predicted. The increased probability of mission success through the software parameter update process is discussed. This paper also demonstrates the importance of modeling atmospheric flight uncertainties in the estimation of an accurate landing site. With these atmospheric effects included, the final landed ellipse prediction differs from the post-flight determined landing site by less then 0.5 km in downtrack.

Spacecraft attitude calibration/verification baseline study

NASA Technical Reports Server (NTRS)

Chen, L. C.

1981-01-01

A baseline study for a generalized spacecraft attitude calibration/verification system is presented. It can be used to define software specifications for three major functions required by a mission: the pre-launch parameter observability and data collection strategy study; the in-flight sensor calibration; and the post-calibration attitude accuracy verification. Analytical considerations are given for both single-axis and three-axis spacecrafts. The three-axis attitudes considered include the inertial-pointing attitudes, the reference-pointing attitudes, and attitudes undergoing specific maneuvers. The attitude sensors and hardware considered include the Earth horizon sensors, the plane-field Sun sensors, the coarse and fine two-axis digital Sun sensors, the three-axis magnetometers, the fixed-head star trackers, and the inertial reference gyros.

Delivery of Colloid Micro-Newton Thrusters for the Space Technology 7 Mission

NASA Technical Reports Server (NTRS)

Ziemer, John K.; Randolph, Thomas M.; Franklin, Garth W.; Hruby, Vlad; Spence, Douglas; Demmons, Nathaniel; Roy, Thomas; Ehrbar, Eric; Zwahlen, Jurg; Martin, Roy;

Sequence System Building Blocks: Using a Component Architecture for Sequencing Software

NASA Technical Reports Server (NTRS)

Streiffert, Barbara A.; O'Reilly, Taifun

2005-01-01

Over the last few years software engineering has made significant strides in making more flexible architectures and designs possible. However, at the same time, spacecraft have become more complex and flight software has become more sophisticated. Typically spacecraft are often one-of-a-kind entities that have different hardware designs, different capabilities, different instruments, etc. Ground software has become more complex and operations teams have had to learn a myriad of tools that all have different user interfaces and represent data in different ways. At Jet Propulsion Laboratory (JPL) these themes have collided to require an new approach to producing ground system software. Two different groups have been looking at tackling this particular problem. One group is working for the JPL Mars Technology Program in the Mars Science Laboratory (MSL) Focused Technology area. The other group is the JPL Multi-Mission Planning and Sequencing Group . The major concept driving these two approaches on a similar path is to provide software that can be a more cohesive flexible system that provides a act of planning and sequencing system of services. This paper describes the efforts that have been made to date to create a unified approach from these disparate groups.

Sequencing System Building Blocks: Using a Component Architecture for Sequencing Software

NASA Technical Reports Server (NTRS)

Streiffert, Barbara A.; O'Reilly, Taifun

2006-01-01

Over the last few years software engineering has made significant strides in making more flexible architectures and designs possible. However, at the same time, spacecraft have become more complex and flight software has become more sophisticated. Typically spacecraft are often one-of-a-kind entities that have different hardware designs, different capabilities, different instruments, etc. Ground software has become more complex and operations teams have had to learn a myriad of tools that all have different user interfaces and represent data in different ways. At Jet Propulsion Laboratory (JPL) these themes have collided to require a new approach to producing ground system software. Two different groups have been looking at tackling this particular problem. One group is working for the JPL Mars Technology Program in the Mars Science Laboratory (MSL) Focused Technology area. The other group is the JPL Multi-Mission Planning and Sequencing Group. The major concept driving these two approaches on a similar path is to provide software that can be a more cohesive flexible system that provides a set of planning and sequencing system of services. This paper describes the efforts that have been made to date to create a unified approach from these disparate groups.

Demonstration of automated proximity and docking technologies

NASA Astrophysics Data System (ADS)

Anderson, Robert L.; Tsugawa, Roy K.; Bryan, Thomas C.

An autodock was demonstrated using straightforward techniques and real sensor hardware. A simulation testbed was established and validated. The sensor design was refined with improved optical performance and image processing noise mitigation techniques, and the sensor is ready for production from off-the-shelf components. The autonomous spacecraft architecture is defined. The areas of sensors, docking hardware, propulsion, and avionics are included in the design. The Guidance Navigation and Control architecture and requirements are developed. Modular structures suitable for automated control are used. The spacecraft system manager functions including configuration, resource, and redundancy management are defined. The requirements for autonomous spacecraft executive are defined. High level decisionmaking, mission planning, and mission contingency recovery are a part of this. The next step is to do flight demonstrations. After the presentation the following question was asked. How do you define validation? There are two components to validation definition: software simulation with formal and vigorous validation, and hardware and facility performance validated with respect to software already validated against analytical profile.

The MGS Avionics System Architecture: Exploring the Limits of Inheritance

NASA Technical Reports Server (NTRS)

Bunker, R.

1994-01-01

Mars Global Surveyor (MGS) avionics system architecture comprises much of the electronics on board the spacecraft: electrical power, attitude and articulation control, command and data handling, telecommunications, and flight software. Schedule and cost constraints dictated a mix of new and inherited designs, especially hardware upgrades based on findings of the Mars Observer failure review boards.

Program for Editing Spacecraft Command Sequences

NASA Technical Reports Server (NTRS)

Gladden, Roy; Waggoner, Bruce; Kordon, Mark; Hashemi, Mahnaz; Hanks, David; Salcedo, Jose

2006-01-01

Sequence Translator, Editor, and Expander Resource (STEER) is a computer program that facilitates construction of sequences and blocks of sequences (hereafter denoted generally as sequence products) for commanding a spacecraft. STEER also provides mechanisms for translating among various sequence product types and quickly expanding activities of a given sequence in chronological order for review and analysis of the sequence. To date, construction of sequence products has generally been done by use of such clumsy mechanisms as text-editor programs, translating among sequence product types has been challenging, and expanding sequences to time-ordered lists has involved arduous processes of converting sequence products to "real" sequences and running them through Class-A software (defined, loosely, as flight and ground software critical to a spacecraft mission). Also, heretofore, generating sequence products in standard formats has been troublesome because precise formatting and syntax are required. STEER alleviates these issues by providing a graphical user interface containing intuitive fields in which the user can enter the necessary information. The STEER expansion function provides a "quick and dirty" means of seeing how a sequence and sequence block would expand into a chronological list, without need to use of Class-A software.

SNC's Dream Chaser Arrives at NASA Armstrong

NASA Image and Video Library

2017-03-08

This 58-second video shows Sierra Nevada Corporation (SNC) delivering its Dream Chaser spacecraft on Jan. 25, 2017, to NASA's Armstrong Flight Research Center in California, located on Edwards Air Force Base. The spacecraft will undergo several months of testing at the Center in preparation for its approach and landing flight on the base's runway. The test series is part of a developmental space act agreement SNC has with NASA’s HYPERLINK Commercial Crew Program. The upcoming test campaign will help SNC validate the aerodynamic properties, flight software and control system performance of the Dream Chaser. The Dream Chaser is also being prepared to deliver cargo to the International Space Station under NASA’s Commercial Resupply Services 2 (CRS2) contract beginning in 2019. The data that SNC gathers from this test campaign will help influence and inform the final design of the cargo Dream Chaser, which will fly at least six cargo delivery missions to and from the Space Station by 2024.

Wireless Sensor Networks for Developmental and Flight Instrumentation

NASA Technical Reports Server (NTRS)

Alena, Richard; Figueroa, Fernando; Becker, Jeffrey; Foster, Mark; Wang, Ray; Gamudevelli, Suman; Studor, George

2011-01-01

Wireless sensor networks (WSN) based on the IEEE 802.15.4 Personal Area Network and ZigBee Pro 2007 standards are finding increasing use in home automation and smart energy markets providing a framework for interoperable software. The Wireless Connections in Space Project, funded by the NASA Engineering and Safety Center, is developing technology, metrics and requirements for next-generation spacecraft avionics incorporating wireless data transport. The team from Stennis Space Center and Mobitrum Corporation, working under a NASA SBIR grant, has developed techniques for embedding plug-and-play software into ZigBee WSN prototypes implementing the IEEE 1451 Transducer Electronic Datasheet (TEDS) standard. The TEDS provides meta-information regarding sensors such as serial number, calibration curve and operational status. Incorporation of TEDS into wireless sensors leads directly to building application level software that can recognize sensors at run-time, dynamically instantiating sensors as they are added or removed. The Ames Research Center team has been experimenting with this technology building demonstration prototypes for on-board health monitoring. Innovations in technology, software and process can lead to dramatic improvements for managing sensor systems applied to Developmental and Flight Instrumentation (DFI) aboard aerospace vehicles. A brief overview of the plug-and-play ZigBee WSN technology is presented along with specific targets for application within the aerospace DFI market. The software architecture for the sensor nodes incorporating the TEDS information is described along with the functions of the Network Capable Gateway processor which bridges 802.15.4 PAN to the TCP/IP network. Client application software connects to the Gateway and is used to display TEDS information and real-time sensor data values updated every few seconds, incorporating error detection and logging to help measure performance and reliability in relevant target environments. Test results from our prototype WSN running the Mobitrum software system are summarized and the implications to the scalability and reliability for DFI applications are discussed. Our demonstration system, incorporating sensors for life support system and structural health monitoring is described along with test results obtained by running the demonstration prototype in relevant environments such as the Wireless Habitat Testbed at Johnson Space Center in Houston. An operations concept for improved sensor process flow from design to flight test is outlined specific to the areas of Environmental Control and Life Support System performance characterization and structural health monitoring of human-rated spacecraft. This operations concept will be used to highlight the areas where WSN technology, particularly plug-and-play software based on IEEE 1451, can improve the current process, resulting in significant reductions in the technical effort, overall cost and schedule for providing DFI capability for future spacecraft. RELEASED -

Proven and Robust Ground Support Systems - GSFC Success and Lessons Learned

NASA Technical Reports Server (NTRS)

Pfarr, Barbara; Donohue, John; Lui, Ben; Greer, Greg; Green, Tom

2008-01-01

Over the past fifteen years, Goddard Space Flight Center has developed several successful science missions in-house: the Wilkinson Microwave Anisotropy Probe (WMAP), the Imager for Magnetopause-to-Aurora Global Exploration (IMAGE), the Earth Observing 1 (EO-1) [1], and the Space Technology 5 (ST-5)[2] missions, several Small Explorers, and several balloon missions. Currently in development are the Solar Dynamics Observatory (SDO) [3] and the Lunar Reconnaissance Orbiter (LRO)[4]. What is not well known is that these missions have been supported during spacecraft and/or instrument integration and test, flight software development, and mission operations by two in house satellite Telemetry and Command (T & C) Systems, the Integrated Test and Operations System (ITOS) and the Advanced Spacecraft Integration and System Test (ASIST). The advantages of an in-house satellite Telemetry and Command system are primarily in the flexibility of management and maintenance - the developers are considered a part of the mission team, get involved early in the development process of the spacecraft and mission operations-control center, and provide on-site, on-call support that goes beyond Help Desk and simple software fixes. On the other hand, care must be taken to ensure that the system remains generic enough for cost effective re-use from one mission to the next. The software is designed such that many features are user-configurable. Where user-configurable options were impractical, features were designed so as to be easy for the development team to modify. Adding support for a new ground message header, for example, is a one-day effort because of the software framework on which that code rests. This paper will discuss the many features of the Goddard satellite Telemetry and Command systems that have contributed to the success of the missions listed above. These features include flexible user interfaces, distributed parallel commanding and telemetry decommutation, a procedure language, the interfaces and tools needed for a high degree of automation, and instantly accessible archives of spacecraft telemetry. It will discuss some of the problems overcome during development, including secure commanding over networks or the Internet, constellation support for the three satellites that comprise the ST-5 mission, and geographically distributed telemetry end users.

IRIS Mission Operations Director's Colloquium

NASA Technical Reports Server (NTRS)

Carvalho, Robert; Mazmanian, Edward A.

2014-01-01

Pursuing the Mysteries of the Sun: The Interface Region Imaging Spectrograph (IRIS) Mission. Flight controllers from the IRIS mission will present their individual experiences on IRIS from development through the first year of flight. This will begin with a discussion of the unique nature of IRISs mission and science, and how it fits into NASA's fleet of solar observatories. Next will be a discussion of the critical roles Ames contributed in the mission including spacecraft and flight software development, ground system development, and training for launch. This will be followed by experiences from launch, early operations, ongoing operations, and unusual operations experiences. The presentation will close with IRIS science imagery and questions.

KSC-98pc1381

NASA Image and Video Library

1998-10-24

KENNEDY SPACE CENTER, FLA. -- A Boeing Delta II (7326) rocket hurls Deep Space 1 through the morning clouds after liftoff, creating sun-challenging light with its exhaust, from Launch Complex 17A, Cape Canaveral Air Station. The first flight in NASA's New Millennium Program, the spacecraft is designed to validate 12 new technologies for scientific space missions of the next century, including the ion propulsion engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1385

NASA Image and Video Library

1998-10-24

KENNEDY SPACE CENTER, FLA. -- In a view from Press Site 1 at Cape Canaveral Air Station, a Boeing Delta II (7326) rocket lights up the ground as it propels Deep Space 1 into the sky after liftoff from Launch Complex 17A. The first flight in NASA's New Millennium Program, the spacecraft is designed to validate 12 new technologies for scientific space missions of the next century, including the ion propulsion engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1383

NASA Image and Video Library

1998-10-24

KENNEDY SPACE CENTER, FLA. -- Lighting up the launch pad below, a Boeing Delta II (7326) rocket is silhouetted in the morning light as it propels Deep Space 1 into the sky after liftoff from Launch Complex 17A, Cape Canaveral Air Station. The first flight in NASA's New Millennium Program, the spacecraft is designed to validate 12 new technologies for scientific space missions of the next century, including the ion propulsion engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1384

NASA Image and Video Library

1998-10-24

KENNEDY SPACE CENTER, FLA. -- A Boeing Delta II (7326) rocket lights up the clouds of exhaust below as it propels Deep Space 1 into the sky after liftoff from Launch Complex 17A, Cape Canaveral Air Station. The first flight in NASA's New Millennium Program, the spacecraft is designed to validate 12 new technologies for scientific space missions of the next century, including the ion propulsion engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pa001

NASA Image and Video Library

1998-10-24

In a view from Press Site 1 at Cape Canaveral Air Station, a Boeing Delta II (7326) rocket is framed between the ghostly silhouettes of two press photographers as it launches Deep Space 1 on its mission from Launch Complex 17A. The first flight in NASA's New Millennium Program, the spacecraft is designed to validate 12 new technologies for scientific space missions of the next century, including the ion propulsion engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

Cost, capability, and risk for planetary operations

NASA Technical Reports Server (NTRS)

Mclaughlin, William I.; Deutsch, Marie J.; Miller, Lanny J.; Wolff, Donna M.; Zawacki, Steven J.

1992-01-01

The three key factors for flight projects - cost, capability, and risk - are examined with respect to their interplay, the uplink process, cost drivers, and risk factors. Scientific objectives are translated into a computer program during the uplink process, and examples are given relating to the Voyager Interstellar Mission, Galileo, and the Comet Rendezvous Asteroid Flyby. The development of a multimission sequence system based on these uplinks is described with reference to specific subsystems such as the pointer and the sequence generator. Operational cost drivers include mission, flight-system, and ground-system complexity, uplink traffic, and work force. Operational risks are listed in terms of the mission operations, the environment, and the mission facilities. The uplink process can be analyzed in terms of software development, and spacecraft operability is shown to be an important factor from the initial stages of spacecraft development.

Evolution of the Space Shuttle Primary Avionics Software and Avionics for Shuttle Derived Launch Vehicles

NASA Technical Reports Server (NTRS)

Ferguson, Roscoe C.

2011-01-01

As a result of recommendation from the Augustine Panel, the direction for Human Space Flight has been altered from the original plan referred to as Constellation. NASA s Human Exploration Framework Team (HEFT) proposes the use of a Shuttle Derived Heavy Lift Launch Vehicle (SDLV) and an Orion derived spacecraft (salvaged from Constellation) to support a new flexible direction for space exploration. The SDLV must be developed within an environment of a constrained budget and a preferred fast development schedule. Thus, it has been proposed to utilize existing assets from the Shuttle Program to speed development at a lower cost. These existing assets should not only include structures such as external tanks or solid rockets, but also the Flight Software which has traditionally been a "long pole" in new development efforts. The avionics and software for the Space Shuttle was primarily developed in the 70 s and considered state of the art for that time. As one may argue that the existing avionics and flight software may be too outdated to support the new SDLV effort, this is a fallacy if they can be evolved over time into a "modern avionics" platform. The technology may be outdated, but the avionics concepts and flight software algorithms are not. The reuse of existing avionics and software also allows for the reuse of development, verification, and operations facilities. The keyword is evolve in that these assets can support the fast development of such a vehicle, but then be gradually evolved over time towards more modern platforms as budget and schedule permits. The "gold" of the flight software is the "control loop" algorithms of the vehicle. This is the Guidance, Navigation, and Control (GNC) software algorithms. This software is typically the most expensive to develop, test, and verify. Thus, the approach is to preserve the GNC flight software, while first evolving the supporting software (such as Command and Data Handling, Caution and Warning, Telemetry, etc.). This can be accomplished by gradually removing the "support software" from the legacy flight software leaving only the GNC algorithms. The "support software" could be re-developed for modern platforms, while leaving the GNC algorithms to execute on technology compatible with the legacy system. It is also possible to package the GNC algorithms into an emulated version of the original computer (via Field Programmable Gate Arrays or FPGAs), thus becoming a "GNC on a Chip" solution where it could live forever to be embedded in modern avionics platforms.

Research & Technology Report Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Soffen, Gerald A. (Editor); Truszkowski, Walter (Editor); Ottenstein, Howard (Editor); Frost, Kenneth (Editor); Maran, Stephen (Editor); Walter, Lou (Editor); Brown, Mitch (Editor)

1995-01-01

The main theme of this edition of the annual Research and Technology Report is Mission Operations and Data Systems. Shifting from centralized to distributed mission operations, and from human interactive operations to highly automated operations is reported. The following aspects are addressed: Mission planning and operations; TDRSS, Positioning Systems, and orbit determination; hardware and software associated with Ground System and Networks; data processing and analysis; and World Wide Web. Flight projects are described along with the achievements in space sciences and earth sciences. Spacecraft subsystems, cryogenic developments, and new tools and capabilities are also discussed.

1998 IEEE Aerospace Conference. Proceedings.

NASA Astrophysics Data System (ADS)

The following topics were covered: science frontiers and aerospace; flight systems technologies; spacecraft attitude determination and control; space power systems; smart structures and dynamics; military avionics; electronic packaging; MEMS; hyperspectral remote sensing for GVP; space laser technology; pointing, control, tracking and stabilization technologies; payload support technologies; protection technologies; 21st century space mission management and design; aircraft flight testing; aerospace test and evaluation; small satellites and enabling technologies; systems design optimisation; advanced launch vehicles; GPS applications and technologies; antennas and radar; software and systems engineering; scalable systems; communications; target tracking applications; remote sensing; advanced sensors; and optoelectronics.

Galileo attitude and articulation control subsystem closed loop testing

NASA Technical Reports Server (NTRS)

Lembeck, M. F.; Pignatano, N. D.

1983-01-01

In order to ensure the reliable operation of the Attitude and Articulation Control Subsystem (AACS) which will guide the Galileo spacecraft on its two and one-half year journey to Jupiter, the AACS is being rigorously tested. The primary objectives of the test program are the verification of the AACS's form, fit, and function, especially with regard to subsystem external interfaces and the functional operation of the flight software. Attention is presently given to the Galileo Closed Loop Test System, which simulates the dynamic and 'visual' flight environment for AACS components in the laboratory.

Recent Developments in Hardware-in-the-Loop Formation Navigation and Control

NASA Technical Reports Server (NTRS)

Mitchell, Jason W.; Luquette, Richard J.

2005-01-01

The Formation Flying Test-Bed (FFTB) at NASA Goddard Space Flight Center (GSFC) provides a hardware-in-the-loop test environment for formation navigation and control. The facility is evolving as a modular, hybrid, dynamic simulation facility for end-tc-end guidance, navigation, and control (GN&C) design and analysis of formation flying spacecraft. The core capabilities of the FFTB, as a platform for testing critical hardware and software algorithms in-the-loop, are reviewed with a focus on many recent improvements. Two significant upgrades to the FFTB are a message-oriented middleware (MOM) architecture, and a software crosslink for inter-spacecraft ranging. The MOM architecture provides a common messaging bus for software agents, easing integration, arid supporting the GSFC Mission Services Evolution Center (GMSEC) architecture via software bridge. Additionally, the FFTB s hardware capabilities are expanding. Recently, two Low-Power Transceivers (LPTs) with ranging capability have been introduced into the FFTB. The LPT crosslinks will be connected to a modified Crosslink Channel Simulator (CCS), which applies realistic space-environment effects to the Radio Frequency (RF) signals produced by the LPTs.

Spacecraft operations automation: Automatic alarm notification and web telemetry display

NASA Astrophysics Data System (ADS)

Short, Owen G.; Leonard, Robert E.; Bucher, Allen W.; Allen, Bryan

1999-11-01

In these times of Faster, Better, Cheaper (FBC) spacecraft, Spacecraft Operations Automation is an area that is targeted by many Operations Teams. To meet the challenges of the FBC environment, the Mars Global Surveyor (MGS) Operations Team designed and quickly implemented two new low-cost technologies: one which monitors spacecraft telemetry, checks the status of the telemetry, and contacts technical experts by pager when any telemetry datapoints exceed alarm limits, and a second which allows quick and convenient remote access to data displays. The first new technology is Automatic Alarm Notification (AAN). AAN monitors spacecraft telemetry and will notify engineers automatically if any telemetry is received which creates an alarm condition. The second new technology is Web Telemetry Display (WTD). WTD captures telemetry displays generated by the flight telemetry system and makes them available to the project web server. This allows engineers to check the health and status of the spacecraft from any computer capable of connecting to the global internet, without needing normally-required specialized hardware and software. Both of these technologies have greatly reduced operations costs by alleviating the need to have operations engineers monitor spacecraft performance on a 24 hour per day, 7 day per week basis from a central Mission Support Area. This paper gives details on the design and implementation of AAN and WTD, discusses their limitations, and lists the ongoing benefits which have accrued to MGS Flight Operations since their implementation in late 1996.

Virtual Instrument Simulator for CERES

NASA Technical Reports Server (NTRS)

Chapman, John J.

1997-01-01

A benchtop virtual instrument simulator for CERES (Clouds and the Earth's Radiant Energy System) has been built at NASA, Langley Research Center in Hampton, VA. The CERES instruments will fly on several earth orbiting platforms notably NASDA's Tropical Rainfall Measurement Mission (TRMM) and NASA's Earth Observing System (EOS) satellites. CERES measures top of the atmosphere radiative fluxes using microprocessor controlled scanning radiometers. The CERES Virtual Instrument Simulator consists of electronic circuitry identical to the flight unit's twin microprocessors and telemetry interface to the supporting spacecraft electronics and two personal computers (PC) connected to the I/O ports that control azimuth and elevation gimbals. Software consists of the unmodified TRW developed Flight Code and Ground Support Software which serves as the instrument monitor and NASA/TRW developed engineering models of the scanners. The CERES Instrument Simulator will serve as a testbed for testing of custom instrument commands intended to solve in-flight anomalies of the instruments which could arise during the CERES mission. One of the supporting computers supports the telemetry display which monitors the simulator microprocessors during the development and testing of custom instrument commands. The CERES engineering development software models have been modified to provide a virtual instrument running on a second supporting computer linked in real time to the instrument flight microprocessor control ports. The CERES Instrument Simulator will be used to verify memory uploads by the CERES Flight Operations TEAM at NASA. Plots of the virtual scanner models match the actual instrument scan plots. A high speed logic analyzer has been used to track the performance of the flight microprocessor. The concept of using an identical but non-flight qualified microprocessor and electronics ensemble linked to a virtual instrument with identical system software affords a relatively inexpensive simulation system capable of high fidelity.

Spacecraft Onboard Interface Services: Current Status and Roadmap

NASA Astrophysics Data System (ADS)

Prochazka, Marek; Lopez Trescastro, Jorge; Krueger, Sabine

2016-08-01

Spacecraft Onboard Interface Services (SOIS) is a set of CCSDS standards defining communication stack services to interact with hardware equipment onboard spacecraft. In 2014 ESA kicked off three parallel activities to critically review the SOIS standards, use legacy spacecraft flight software (FSW), make it compliant to a preselected subset of SOIS standards and make performance and architecture assessment. As a part of the three parallel activities, led by Airbus DS Toulouse, OHB Bremen and Thales Alenia Space Cannes respectively, it was to provide feedback back to ESA and CCSDS and also to propose a roadmap of transition towards an operational FSW system fully compliant to applicable SOIS standards. The objective of the paper is twofold: Firstly it is to summarise main results of the three parallel activities and secondly, based on the results, to propose a roadmap for the future.

Risk analysis and management

NASA Technical Reports Server (NTRS)

Smith, H. E.

1990-01-01

Present software development accomplishments are indicative of the emerging interest in and increasing efforts to provide risk assessment backbone tools in the manned spacecraft engineering community. There are indications that similar efforts are underway in the chemical processes industry and are probably being planned for other high risk ground base environments. It appears that complex flight systems intended for extended manned planetary exploration will drive this technology.

Intelligent systems and advanced user interfaces for design, operation, and maintenance of command management systems

NASA Technical Reports Server (NTRS)

Potter, William J.; Mitchell, Christine M.

1993-01-01

Historically, command management systems (CMS) have been large and expensive spacecraft-specific software systems that were costly to build, operate, and maintain. Current and emerging hardware, software, and user interface technologies may offer an opportunity to facilitate the initial formulation and design of a spacecraft-specific CMS as well as to develop a more generic CMS system. New technologies, in addition to a core CMS common to a range of spacecraft, may facilitate the training and enhance the efficiency of CMS operations. Current mission operations center (MOC) hardware and software include Unix workstations, the C/C++ programming languages, and an X window interface. This configuration provides the power and flexibility to support sophisticated and intelligent user interfaces that exploit state-of-the-art technologies in human-machine interaction, artificial intelligence, and software engineering. One of the goals of this research is to explore the extent to which technologies developed in the research laboratory can be productively applied in a complex system such as spacecraft command management. Initial examination of some of these issues in CMS design and operation suggests that application of technologies such as intelligent planning, case-based reasoning, human-machine systems design and analysis tools (e.g., operator and designer models), and human-computer interaction tools (e.g., graphics, visualization, and animation) may provide significant savings in the design, operation, and maintenance of the CMS for a specific spacecraft as well as continuity for CMS design and development across spacecraft. The first six months of this research saw a broad investigation by Georgia Tech researchers into the function, design, and operation of current and planned command management systems at Goddard Space Flight Center. As the first step, the researchers attempted to understand the current and anticipated horizons of command management systems at Goddard. Preliminary results are given on CMS commonalities and causes of low re-use, and methods are proposed to facilitate increased re-use.

An AFDX Network for Spacecraft Data Handling

NASA Astrophysics Data System (ADS)

Deredempt, Marie-Helene; Kollias, Vangelis; Sun, Zhili; Canamares, Ernest; Ricco, Philippe

2014-08-01

In aeronautical domain, ARINC-664 Part 7 specification (AFDX) [4] provides the enabling technology for interfacing equipment in Integrated Modular Avionics (IMA) architectures. The complementary part of AFDX for a complete interoperability - Time and Space Partitioning (ARINC 653) concepts [1]- was already studied as part of space domain ESA roadmap (i.e. IMA4Space project)Standardized IMA based architecture is already considered in aeronautical domain as more flexible, reliable and secure. Integration and validation become simple, using a common set of tools and data base and could be done by part on different means with the same definition (hardware and software test benches, flight control or alarm test benches, simulator and flight test installation).In some area, requirements in terms of data processing are quite similar in space domain and the concept could be applicable to take benefit of the technology itself and of the panel of hardware and software solutions and tools available on the market. The Mission project (Methodology and assessment for the applicability of ARINC-664 (AFDX) in Satellite/Spacecraft on-board communicatION networks), as an FP7 initiative for bringing terrestrial SME research into the space domain started to evaluate the applicability of the standard in space domain.

GOES-R active vibration damping controller design, implementation, and on-orbit performance

NASA Astrophysics Data System (ADS)

Clapp, Brian R.; Weigl, Harald J.; Goodzeit, Neil E.; Carter, Delano R.; Rood, Timothy J.

2018-01-01

GOES-R series spacecraft feature a number of flexible appendages with modal frequencies below 3.0 Hz which, if excited by spacecraft disturbances, can be sources of undesirable jitter perturbing spacecraft pointing. To meet GOES-R pointing stability requirements, the spacecraft flight software implements an Active Vibration Damping (AVD) rate control law which acts in parallel with the nadir point attitude control law. The AVD controller commands spacecraft reaction wheel actuators based upon Inertial Measurement Unit (IMU) inputs to provide additional damping for spacecraft structural modes below 3.0 Hz which vary with solar wing angle. A GOES-R spacecraft dynamics and attitude control system identified model is constructed from pseudo-random reaction wheel torque commands and IMU angular rate response measurements occurring over a single orbit during spacecraft post-deployment activities. The identified Fourier model is computed on the ground, uplinked to the spacecraft flight computer, and the AVD controller filter coefficients are periodically computed on-board from the Fourier model. Consequently, the AVD controller formulation is based not upon pre-launch simulation model estimates but upon on-orbit nadir point attitude control and time-varying spacecraft dynamics. GOES-R high-fidelity time domain simulation results herein demonstrate the accuracy of the AVD identified Fourier model relative to the pre-launch spacecraft dynamics and control truth model. The AVD controller on-board the GOES-16 spacecraft achieves more than a ten-fold increase in structural mode damping for the fundamental solar wing mode while maintaining controller stability margins and ensuring that the nadir point attitude control bandwidth does not fall below 0.02 Hz. On-orbit GOES-16 spacecraft appendage modal frequencies and damping ratios are quantified based upon the AVD system identification, and the increase in modal damping provided by the AVD controller for each structural mode is presented. The GOES-16 spacecraft AVD controller frequency domain stability margins and nadir point attitude control bandwidth are presented along with on-orbit time domain disturbance response performance.

GOES-R Active Vibration Damping Controller Design, Implementation, and On-Orbit Performance

NASA Technical Reports Server (NTRS)

Clapp, Brian R.; Weigl, Harald J.; Goodzeit, Neil E.; Carter, Delano R.; Rood, Timothy J.

2017-01-01

GOES-R series spacecraft feature a number of flexible appendages with modal frequencies below 3.0 Hz which, if excited by spacecraft disturbances, can be sources of undesirable jitter perturbing spacecraft pointing. In order to meet GOES-R pointing stability requirements, the spacecraft flight software implements an Active Vibration Damping (AVD) rate control law which acts in parallel with the nadir point attitude control law. The AVD controller commands spacecraft reaction wheel actuators based upon Inertial Measurement Unit (IMU) inputs to provide additional damping for spacecraft structural modes below 3.0 Hz which vary with solar wing angle. A GOES-R spacecraft dynamics and attitude control system identified model is constructed from pseudo-random reaction wheel torque commands and IMU angular rate response measurements occurring over a single orbit during spacecraft post-deployment activities. The identified Fourier model is computed on the ground, uplinked to the spacecraft flight computer, and the AVD controller filter coefficients are periodically computed on-board from the Fourier model. Consequently, the AVD controller formulation is based not upon pre-launch simulation model estimates but upon on-orbit nadir point attitude control and time-varying spacecraft dynamics. GOES-R high-fidelity time domain simulation results herein demonstrate the accuracy of the AVD identified Fourier model relative to the pre-launch spacecraft dynamics and control truth model. The AVD controller on-board the GOES-16 spacecraft achieves more than a ten-fold increase in structural mode damping of the fundamental solar wing mode while maintaining controller stability margins and ensuring that the nadir point attitude control bandwidth does not fall below 0.02 Hz. On-orbit GOES-16 spacecraft appendage modal frequencies and damping ratios are quantified based upon the AVD system identification, and the increase in modal damping provided by the AVD controller for each structural mode is presented. The GOES-16 spacecraft AVD controller frequency domain stability margins and nadir point attitude control bandwidth are presented along with on-orbit time domain disturbance response performance.

Future Standardization of Space Telecommunications Radio System with Core Flight System

NASA Technical Reports Server (NTRS)

Hickey, Joseph P.; Briones, Janette C.; Roche, Rigoberto; Handler, Louis M.; Hall, Steven

2016-01-01

NASA Glenn Research Center (GRC) is integrating the NASA Space Telecommunications Radio System (STRS) Standard with the Core Flight System (cFS). The STRS standard provides a common, consistent framework to develop, qualify, operate and maintain complex, reconfigurable and reprogrammable radio systems. The cFS is a flexible, open architecture that features a plug-and-play software executive called the Core Flight Executive (cFE), a reusable library of software components for flight and space missions and an integrated tool suite. Together, STRS and cFS create a development environment that allows for STRS compliant applications to reference the STRS APIs through the cFS infrastructure. These APis are used to standardize the communication protocols on NASAs space SDRs. The cFE-STRS Operating Environment (OE) is a portable cFS library, which adds the ability to run STRS applications on existing cFS platforms. The purpose of this paper is to discuss the cFE-STRS OE prototype, preliminary experimental results performed using the Advanced Space Radio Platform (ASRP), the GRC Sband Ground Station and the SCaN (Space Communication and Navigation) Testbed currently flying onboard the International Space Station. Additionally, this paper presents a demonstration of the Consultative Committee for Space Data Systems (CCSDS) Spacecraft Onboard Interface Services (SOIS) using electronic data sheets inside cFE. This configuration allows for the data sheets to specify binary formats for data exchange between STRS applications. The integration of STRS with cFS leverages mission-proven platform functions and mitigates barriers to integration with future missions. This reduces flight software development time and the costs of software-defined radio (SDR) platforms. Furthermore, the combined benefits of STRS standardization with the flexibility of cFS provide an effective, reliable and modular framework to minimize software development efforts for spaceflight missions.

2014 Summer Series - Robert Carvalho - Pursuing the Mysteries of the Sun: The IRIS Mission

NASA Image and Video Library

2014-06-19

Pursuing the Mysteries of the Sun: The Interface Region Imaging Spectrograph (IRIS) Mission. Flight controllers from the IRIS mission will present their individual experiences on IRIS from development through the first year of flight. This will begin with a discussion of the unique nature of IRIS's mission and science, and how it fits into NASA's fleet of solar observatories. Next will be a discussion of the critical roles Ames contributed in the mission including spacecraft and flight software development, ground system development, and training for launch. This will be followed by experiences from launch, early operations, ongoing operations, and unusual operations experiences. The presentation will close with IRIS science imagery and questions.

Recent Flight Results of the TRMM Kalman Filter

NASA Technical Reports Server (NTRS)

Andrews, Stephen F.; Bilanow, Stephen; Bauer, Frank (Technical Monitor)

2002-01-01

The Tropical Rainfall Measuring Mission (TRMM) spacecraft is a nadir pointing spacecraft that nominally controls the roll and pitch attitude based on the Earth Sensor Assembly (ESA) output. TRMM's nominal orbit altitude was 350 km, until raised to 402 km to prolong mission life. During the boost, the ESA experienced a decreasing signal to noise ratio, until sun interference at 393 km altitude made the ESA data unreliable for attitude determination. At that point, the backup attitude determination algorithm, an extended Kalman filter, was enabled. After the boost finished, TRMM reacquired its nadir-pointing attitude, and continued its mission. This paper will briefly discuss the boost and the decision to turn on the backup attitude determination algorithm. A description of the extended Kalman filter algorithm will be given. In addition, flight results from analyzing attitude data and the results of software changes made onboard TRMM will be discussed. Some lessons learned are presented.

Flight Operations Analysis Tool

NASA Technical Reports Server (NTRS)

Easter, Robert; Herrell, Linda; Pomphrey, Richard; Chase, James; Wertz Chen, Julie; Smith, Jeffrey; Carter, Rebecca

2006-01-01

Flight Operations Analysis Tool (FLOAT) is a computer program that partly automates the process of assessing the benefits of planning spacecraft missions to incorporate various combinations of launch vehicles and payloads. Designed primarily for use by an experienced systems engineer, FLOAT makes it possible to perform a preliminary analysis of trade-offs and costs of a proposed mission in days, whereas previously, such an analysis typically lasted months. FLOAT surveys a variety of prior missions by querying data from authoritative NASA sources pertaining to 20 to 30 mission and interface parameters that define space missions. FLOAT provides automated, flexible means for comparing the parameters to determine compatibility or the lack thereof among payloads, spacecraft, and launch vehicles, and for displaying the results of such comparisons. Sparseness, typical of the data available for analysis, does not confound this software. FLOAT effects an iterative process that identifies modifications of parameters that could render compatible an otherwise incompatible mission set.

On-Orbit Performance of the TRMM Mission Mode

NASA Technical Reports Server (NTRS)

Robertson, Brent; Placanica, Sam; Morgenstern, Wendy; Hashmall, Joseph A.; Glickman, Jonathan; Natanson, Gregory

1999-01-01

This paper presents an overview of the Tropical Rainfall Measuring Mission (TRMM) Attitude Control System along with detailed in-flight performance results of the TRMM Mission mode. The TRMM spacecraft is an Earth-pointed, zero momentum bias satellite launched on November 27, 1997 from Tanegashima Space Center, Japan. TRMM is a joint mission between NASA and the National Space Development Agency of Japan designed to monitor and study tropical rainfall and the associated release of energy. Prior to calibration, the spacecraft attitude showed larger Sun sensor yaw updates than expected. This was traced to not just sensor misalignment but also to a misalignment between the two heads within each Sun sensor. In order to avoid alteration of the flight software, Sun sensor transfer function coefficients were determined to minimize the error due to head misalignment. This paper describes the design, on-orbit checkout, calibration and performance of the TRMM Mission Mode with respect to the mission level requirements.

The use of real-time, hardware-in-the-loop simulation in the design and development of the new Hughes HS601 spacecraft attitude control system

NASA Technical Reports Server (NTRS)

Slafer, Loren I.

1989-01-01

Realtime simulation and hardware-in-the-loop testing is being used extensively in all phases of the design, development, and testing of the attitude control system (ACS) for the new Hughes HS601 satellite bus. Realtime, hardware-in-the-loop simulation, integrated with traditional analysis and pure simulation activities is shown to provide a highly efficient and productive overall development program. Implementation of high fidelity simulations of the satellite dynamics and control system algorithms, capable of real-time execution (using applied Dynamics International's System 100), provides a tool which is capable of being integrated with the critical flight microprocessor to create a mixed simulation test (MST). The MST creates a highly accurate, detailed simulated on-orbit test environment, capable of open and closed loop ACS testing, in which the ACS design can be validated. The MST is shown to provide a valuable extension of traditional test methods. A description of the MST configuration is presented, including the spacecraft dynamics simulation model, sensor and actuator emulators, and the test support system. Overall system performance parameters are presented. MST applications are discussed; supporting ACS design, developing on-orbit system performance predictions, flight software development and qualification testing (augmenting the traditional software-based testing), mission planning, and a cost-effective subsystem-level acceptance test. The MST is shown to provide an ideal tool in which the ACS designer can fly the spacecraft on the ground.

General Purpose Data-Driven Monitoring for Space Operations

NASA Technical Reports Server (NTRS)

Iverson, David L.; Martin, Rodney A.; Schwabacher, Mark A.; Spirkovska, Liljana; Taylor, William McCaa; Castle, Joseph P.; Mackey, Ryan M.

2009-01-01

As modern space propulsion and exploration systems improve in capability and efficiency, their designs are becoming increasingly sophisticated and complex. Determining the health state of these systems, using traditional parameter limit checking, model-based, or rule-based methods, is becoming more difficult as the number of sensors and component interactions grow. Data-driven monitoring techniques have been developed to address these issues by analyzing system operations data to automatically characterize normal system behavior. System health can be monitored by comparing real-time operating data with these nominal characterizations, providing detection of anomalous data signatures indicative of system faults or failures. The Inductive Monitoring System (IMS) is a data-driven system health monitoring software tool that has been successfully applied to several aerospace applications. IMS uses a data mining technique called clustering to analyze archived system data and characterize normal interactions between parameters. The scope of IMS based data-driven monitoring applications continues to expand with current development activities. Successful IMS deployment in the International Space Station (ISS) flight control room to monitor ISS attitude control systems has led to applications in other ISS flight control disciplines, such as thermal control. It has also generated interest in data-driven monitoring capability for Constellation, NASA's program to replace the Space Shuttle with new launch vehicles and spacecraft capable of returning astronauts to the moon, and then on to Mars. Several projects are currently underway to evaluate and mature the IMS technology and complementary tools for use in the Constellation program. These include an experiment on board the Air Force TacSat-3 satellite, and ground systems monitoring for NASA's Ares I-X and Ares I launch vehicles. The TacSat-3 Vehicle System Management (TVSM) project is a software experiment to integrate fault and anomaly detection algorithms and diagnosis tools with executive and adaptive planning functions contained in the flight software on-board the Air Force Research Laboratory TacSat-3 satellite. The TVSM software package will be uploaded after launch to monitor spacecraft subsystems such as power and guidance, navigation, and control (GN&C). It will analyze data in real-time to demonstrate detection of faults and unusual conditions, diagnose problems, and react to threats to spacecraft health and mission goals. The experiment will demonstrate the feasibility and effectiveness of integrated system health management (ISHM) technologies with both ground and on-board experiments.

NASA's spacecraft data system

NASA Technical Reports Server (NTRS)

Cudmore, Alan; Flanegan, Mark

1993-01-01

The NASA Small Explorer Data System (SEDS), a space flight data system developed to support the Small Explorer (SMEX) project, is addressed. The system was flown on the Solar Anomalous Magnetospheric Particle Explorer (SAMPEX) SMEX mission, and with reconfiguration for different requirements will fly on the X-ray Timing Explorer (XTE) and the Tropical Rainfall Measuring Mission (TRMM). SEDS is also foreseen for the Hubble repair mission. Its name was changed to Spacecraft Data System (SDS) in view of expansions. Objectives, SDS hardware, and software are described. Each SDS box contains two computers, data storage memory, uplink (command) reception circuitry, downlink (telemetry) encoding circuitry, Instrument Telemetry Controller (ITC), and spacecraft timing circuitry. The SDS communicates with other subsystems over the MIL-STD-1773 data bus. The SDS software uses a real time Operating System (OS) and the C language. The OS layer, communications and scheduling layer, application task layer, and diagnostic software, are described. Decisions on the use of advanced technologies, such as ASIC's (Application Specific Integrated Circuits) and fiber optics, led to technical improvements, such as lower power and weight, without increasing the risk associated with the data system. The result was a successful SAMPEX development, integration and test, and mission using SEDS, and the upgrading of that system to SDS for TRMM and XTE.

Orbital Express Advanced Video Guidance Sensor: Ground Testing, Flight Results and Comparisons

NASA Technical Reports Server (NTRS)

Pinson, Robin M.; Howard, Richard T.; Heaton, Andrew F.

2008-01-01

Orbital Express (OE) was a successful mission demonstrating automated rendezvous and docking. The 2007 mission consisted of two spacecraft, the Autonomous Space Transport Robotic Operations (ASTRO) and the Next Generation Serviceable Satellite (NEXTSat) that were designed to work together and test a variety of service operations in orbit. The Advanced Video Guidance Sensor, AVGS, was included as one of the primary proximity navigation sensors on board the ASTRO. The AVGS was one of four sensors that provided relative position and attitude between the two vehicles. Marshall Space Flight Center was responsible for the AVGS software and testing (especially the extensive ground testing), flight operations support, and analyzing the flight data. This paper briefly describes the historical mission, the data taken on-orbit, the ground testing that occurred, and finally comparisons between flight data and ground test data for two different flight regimes.

Critical Software for Human Spaceflight

NASA Technical Reports Server (NTRS)

Preden, Antonio; Kaschner, Jens; Rettig, Felix; Rodriggs, Michael

2017-01-01

The NASA Orion vehicle that will fly to the moon in the next years is propelled along its mission by the European Service Module (ESM), developed by ESA and its prime contractor Airbus Defense and Space. This paper describes the development of the Propulsion Drive Electronics (PDE) Software that provides the interface between the propulsion hardware of the European Service Module with the Orion flight computers, and highlights the challenges that have been faced during the development. Particularly, the specific aspects relevant to Human Spaceflight in an international cooperation are presented, as the compliance to both European and US standards and the software criticality classification to the highest category A. An innovative aspect of the PDE SW is its Time- Triggered Ethernet interface with the Orion Flight Computers, which has never been flown so far on any European spacecraft. Finally the verification aspects are presented, applying the most exigent quality requirements defined in the European Cooperation for Space Standardization (ECSS) standards such as the structural coverage analysis of the object code and the recourse to an independent software verification and validation activity carried on in parallel by a different team.

Automated Transfer Vehicle Proximity Flight Safety Overview

NASA Astrophysics Data System (ADS)

Cornier, Dominique; Berthelier, David; Requiston, Helene; Zekri, Eric; Chase, Richard

2005-12-01

The European Automated Transfer Vehicle (ATV) is an unmanned transportation spacecraft designed to contribute to the logistic servicing of the ISS. The ATV will be launched by ARIANE 5 and, after phasing and rendezvous maneuvers, it autonomously docks to the International Space Station (ISS).The ATV control is nominally handled by the Guidance, Navigation and Control (GNC) function using computers, software, sensors and actuators. During rendezvous operations, in order to cover the extreme situations where the GNC function fails to ensure a safe trajectory with respect to the ISS, a segregated Proximity Flight Safety (PFS) function is activated : this function will initiate a collision avoidance maneuver which will place the ATV on a trajectory ensuring safety with respect to the ISS. The PFS function relies on segregated computers, the Monitoring and Safing Units (MSUs) running specific software, on four dedicated thrusters, on dedicated batteries and on specific interfaces with ATV gyrometers.The PFS function being the ultimate protection to ensure ISS safety in case of ATV malfunction, specific rules have been applied to its implementation, in particular for the development of the MSU software, which is critical since any failure of this software may result in catastrophic consequences.This paper provides an overview of the ATV Proximity Flight Safety function. After a short description of the overall ATV avionics architecture and its rationale, the second part of the paper presents more details on the PFS function both in terms of hardware and software implementation. The third part of the paper is dedicated to the MSU software validation method that is specific considering its criticality. The last part of the paper provides information on the different operations related to the use of the PFS function during an ATV flight.

Flight Software Implementation of the Beacon Monitor Expreiment On the NASA New Millennium Deep Space 1 (DS-1) Mission

NASA Technical Reports Server (NTRS)

Foster, R.; Schlutsmeyer, A.

1997-01-01

A new technology that can lower the cost of mission operations on future spacecraft will be tested on the NASA New Millennium Deep Space 1 (DS-1) Mission. This technology, the Beacon Monitor Experiment (BMOX), can be used to reduce the Deep Space Network (DSN) tracking time and its associated costs on future missions.

Engineering of the LISA Pathfinder mission—making the experiment a practical reality

NASA Astrophysics Data System (ADS)

Warren, Carl; Dunbar, Neil; Backler, Mike

2009-05-01

LISA Pathfinder represents a unique challenge in the development of scientific spacecraft—not only is the LISA Test Package (LTP) payload a complex integrated development, placing stringent requirements on its developers and the spacecraft, but the payload also acts as the core sensor and actuator for the spacecraft, making the tasks of control design, software development and system verification unusually difficult. The micro-propulsion system which provides the remaining actuation also presents substantial development and verification challenges. As the mission approaches the system critical design review, flight hardware is completing verification and the process of verification using software and hardware simulators and test benches is underway. Preparation for operations has started, but critical milestones for LTP and field effect electric propulsion (FEEP) lie ahead. This paper summarizes the status of the present development and outlines the key challenges that must be overcome on the way to launch.

Mechanisms test bed math model modification and simulation support

NASA Technical Reports Server (NTRS)

Gilchrist, Andrea C.; Tobbe, Patrick A.

1995-01-01

This report summarizes the work performed under contract NAS8-38771 in support of the Marshall Space Flight Center Six Degree of Freedom Motion Facility and Flight Robotics Laboratory. The contract activities included the development of the two flexible body and Remote Manipulator System simulations, Dynamic Overhead Target Simulator control system and operating software, Global Positioning System simulation, and Manipulator Coupled Spacecraft Controls Testbed. Technical support was also provided for the Lightning Imaging Sensor and Solar X-Ray Imaging programs. The cover sheets and introductory sections for the documentation written under this contract are provided as an appendix.

Vehicle System Management Modeling in UML for Ares I

NASA Technical Reports Server (NTRS)

Pearson, Newton W.; Biehn, Bradley A.; Curry, Tristan D.; Martinez, Mario R.

2011-01-01

The Spacecraft & Vehicle Systems Department of Marshall Space Flight Center is responsible for modeling the Vehicle System Management for the Ares I vehicle which was a part of the now canceled Constellation Program. An approach to generating the requirements for the Vehicle System Management was to use the Unified Modeling Language technique to build and test a model that would fulfill the Vehicle System Management requirements. UML has been used on past projects (flight software) in the design phase of the effort but this was the first attempt to use the UML technique from a top down requirements perspective.

A Real-Time Telemetry Simulator of the IUS Spacecraft

NASA Technical Reports Server (NTRS)

Drews, Michael E.; Forman, Douglas A.; Baker, Damon M.; Khazoyan, Louis B.; Viazzo, Danilo

1998-01-01

A real-time telemetry simulator of the IUS spacecraft has recently entered operation to train Flight Control Teams for the launch of the AXAF telescope from the Shuttle. The simulator has proven to be a successful higher fidelity implementation of its predecessor, while affirming the rapid development methodology used in its design. Although composed of COTS hardware and software, the system simulates the full breadth of the mission: Launch, Pre-Deployment-Checkout, Burn Sequence, and AXAF/IUS separation. Realism is increased through patching the system into the operations facility to simulate IUS telemetry, Shuttle telemetry, and the Tracking Station link (commands and status message).

Planning Orbiter Flights

NASA Technical Reports Server (NTRS)

Harris, H. M.; Bergam, M. J.; Kim, S. L.; Smith, E. A.

1987-01-01

Shuttle Mission Design and Operations Software (SMDOS) assists in design and operation of missions involving spacecraft in low orbits around Earth by providing orbital and graphics information. SMDOS performs following five functions: display two world and two polar maps or any user-defined window 5 degrees high in latitude by 5 degrees wide in longitude in one of eight standard projections; designate Earth sites by points or polygon shapes; plot spacecraft ground track with 1-min demarcation lines; display, by means of different colors, availability of Tracking and Data Relay Satellite to Shuttle; and calculate available times and orbits to view particular site, and corresponding look angles. SMDOS written in Laboratory Micro-systems FORTH (1979 standard)

A Flight-Calibrated Methodology for Determination of Cassini Thruster On-Times for Reaction Wheel Biases

NASA Technical Reports Server (NTRS)

Sarani, Sam

2010-01-01

The Cassini spacecraft, the largest and most complex interplanetary spacecraft ever built, continues to undertake unique scientific observations of planet Saturn, Titan, Enceladus, and other moons of the ring world. In order to maintain a stable attitude during the course of its mission, this three-axis stabilized spacecraft uses two different control systems: the Reaction Control System (or RCS) and the Reaction Wheel Assembly (RWA) control system. In the course of its mission, Cassini performs numerous reaction wheel momentum biases (or unloads) using its reaction control thrusters. The use of the RCS thrusters often imparts undesired velocity changes (delta Vs) on the spacecraft and it is crucial for Cassini navigation and attitude control teams to be able to, quickly but accurately, predict the hydrazine usage and delta V vector in Earth Mean Equatorial (J2000) inertial coordinates for reaction wheel bias events, without actually having to spend time and resources simulating the event in a dynamic or hardware-in-the-loop simulation environments. The flight-calibrated methodology described in this paper, and the ground software developed thereof, are designed to provide the RCS thruster on-times, with acceptable accuracy and without any form of dynamic simulation, for reaction wheel biases, along with the hydrazine usage and the delta V in EME-2000 inertial frame.

Magnetospheric Multiscale Mission (MMS) Phase 2B Navigation Performance

NASA Technical Reports Server (NTRS)

Scaperoth, Paige Thomas; Long, Anne; Carpenter, Russell

2009-01-01

The Magnetospheric Multiscale (MMS) formation flying mission, which consists of four spacecraft flying in a tetrahedral formation, has challenging navigation requirements associated with determining and maintaining the relative separations required to meet the science requirements. The baseline navigation concept for MMS is for each spacecraft to independently estimate its position, velocity and clock states using GPS pseudorange data provided by the Goddard Space Flight Center-developed Navigator receiver and maneuver acceleration measurements provided by the spacecraft's attitude control subsystem. State estimation is performed onboard in real-time using the Goddard Enhanced Onboard Navigation System flight software, which is embedded in the Navigator receiver. The current concept of operations for formation maintenance consists of a sequence of two maintenance maneuvers that is performed every 2 weeks. Phase 2b of the MMS mission, in which the spacecraft are in 1.2 x 25 Earth radii orbits with nominal separations at apogee ranging from 30 km to 400 km, has the most challenging navigation requirements because, during this phase, GPS signal acquisition is restricted to less than one day of the 2.8-day orbit. This paper summarizes the results from high-fidelity simulations to determine if the MMS navigation requirements can be met between and immediately following the maintenance maneuver sequence in Phase 2b.

Advanced Autonomous Systems for Space Operations

NASA Astrophysics Data System (ADS)

Gross, A. R.; Smith, B. D.; Muscettola, N.; Barrett, A.; Mjolssness, E.; Clancy, D. J.

2002-01-01

New missions of exploration and space operations will require unprecedented levels of autonomy to successfully accomplish their objectives. Inherently high levels of complexity, cost, and communication distances will preclude the degree of human involvement common to current and previous space flight missions. With exponentially increasing capabilities of computer hardware and software, including networks and communication systems, a new balance of work is being developed between humans and machines. This new balance holds the promise of not only meeting the greatly increased space exploration requirements, but simultaneously dramatically reducing the design, development, test, and operating costs. New information technologies, which take advantage of knowledge-based software, model-based reasoning, and high performance computer systems, will enable the development of a new generation of design and development tools, schedulers, and vehicle and system health management capabilities. Such tools will provide a degree of machine intelligence and associated autonomy that has previously been unavailable. These capabilities are critical to the future of advanced space operations, since the science and operational requirements specified by such missions, as well as the budgetary constraints will limit the current practice of monitoring and controlling missions by a standing army of ground-based controllers. System autonomy capabilities have made great strides in recent years, for both ground and space flight applications. Autonomous systems have flown on advanced spacecraft, providing new levels of spacecraft capability and mission safety. Such on-board systems operate by utilizing model-based reasoning that provides the capability to work from high-level mission goals, while deriving the detailed system commands internally, rather than having to have such commands transmitted from Earth. This enables missions of such complexity and communication` distances as are not otherwise possible, as well as many more efficient and low cost applications. In addition, utilizing component and system modeling and reasoning capabilities, autonomous systems will play an increasing role in ground operations for space missions, where they will both reduce the human workload as well as provide greater levels of monitoring and system safety. This paper will focus specifically on new and innovative software for remote, autonomous, space systems flight operations. Topics to be presented will include a brief description of key autonomous control concepts, the Remote Agent program that commanded the Deep Space 1 spacecraft to new levels of system autonomy, recent advances in distributed autonomous system capabilities, and concepts for autonomous vehicle health management systems. A brief description of teaming spacecraft and rovers for complex exploration missions will also be provided. New on-board software for autonomous science data acquisition for planetary exploration will be described, as well as advanced systems for safe planetary landings. A new multi-agent architecture that addresses some of the challenges of autonomous systems will be presented. Autonomous operation of ground systems will also be considered, including software for autonomous in-situ propellant production and management, and closed- loop ecological life support systems (CELSS). Finally, plans and directions for the future will be discussed.

Trusted Autonomy for Space Flight Systems

NASA Technical Reports Server (NTRS)

Freed, Michael; Bonasso, Pete; Ingham, Mitch; Kortenkamp, David; Perix, John

2005-01-01

NASA has long supported research on intelligent control technologies that could allow space systems to operate autonomously or with reduced human supervision. Proposed uses range from automated control of entire space vehicles to mobile robots that assist or substitute for astronauts to vehicle systems such as life support that interact with other systems in complex ways and require constant vigilance. The potential for pervasive use of such technology to extend the kinds of missions that are possible in practice is well understood, as is its potential to radically improve the robustness, safety and productivity of diverse mission systems. Despite its acknowledged potential, intelligent control capabilities are rarely used in space flight systems. Perhaps the most famous example of intelligent control on a spacecraft is the Remote Agent system flown on the Deep Space One mission (1998 - 2001). However, even in this case, the role of the intelligent control element, originally intended to have full control of the spacecraft for the duration of the mission, was reduced to having partial control for a two-week non-critical period. Even this level of mission acceptance was exceptional. In most cases, mission managers consider intelligent control systems an unacceptable source of risk and elect not to fly them. Overall, the technology is not trusted. From the standpoint of those who need to decide whether to incorporate this technology, lack of trust is easy to understand. Intelligent high-level control means allowing software io make decisions that are too complex for conventional software. The decision-making behavior of these systems is often hard to understand and inspect, and thus hard to evaluate. Moreover, such software is typically designed and implemented either as a research product or custom-built for a particular mission. In the former case, software quality is unlikely to be adequate for flight qualification and the functionality provided by the system is likely driven largely by the need to publish innovative work. In the latter case, the mission represents the first use of the system, a risky proposition even for relatively simple software.

Flight Software Math Library

NASA Technical Reports Server (NTRS)

McComas, David

2013-01-01

The flight software (FSW) math library is a collection of reusable math components that provides typical math utilities required by spacecraft flight software. These utilities are intended to increase flight software quality reusability and maintainability by providing a set of consistent, well-documented, and tested math utilities. This library only has dependencies on ANSI C, so it is easily ported. Prior to this library, each mission typically created its own math utilities using ideas/code from previous missions. Part of the reason for this is that math libraries can be written with different strategies in areas like error handling, parameters orders, naming conventions, etc. Changing the utilities for each mission introduces risks and costs. The obvious risks and costs are that the utilities must be coded and revalidated. The hidden risks and costs arise in miscommunication between engineers. These utilities must be understood by both the flight software engineers and other subsystem engineers (primarily guidance navigation and control). The FSW math library is part of a larger goal to produce a library of reusable Guidance Navigation and Control (GN&C) FSW components. A GN&C FSW library cannot be created unless a standardized math basis is created. This library solves the standardization problem by defining a common feature set and establishing policies for the library s design. This allows the libraries to be maintained with the same strategy used in its initial development, which supports a library of reusable GN&C FSW components. The FSW math library is written for an embedded software environment in C. This places restrictions on the language features that can be used by the library. Another advantage of the FSW math library is that it can be used in the FSW as well as other environments like the GN&C analyst s simulators. This helps communication between the teams because they can use the same utilities with the same feature set and syntax.

Future Standardization of Space Telecommunications Radio System with Core Flight System

NASA Technical Reports Server (NTRS)

Briones, Janette C.; Hickey, Joseph P.; Roche, Rigoberto; Handler, Louis M.; Hall, Charles S.

2016-01-01

NASA Glenn Research Center (GRC) is integrating the NASA Space Telecommunications Radio System (STRS) Standard with the Core Flight System (cFS), an avionics software operating environment. The STRS standard provides a common, consistent framework to develop, qualify, operate and maintain complex, reconfigurable and reprogrammable radio systems. The cFS is a flexible, open architecture that features a plugand- play software executive called the Core Flight Executive (cFE), a reusable library of software components for flight and space missions and an integrated tool suite. Together, STRS and cFS create a development environment that allows for STRS compliant applications to reference the STRS application programmer interfaces (APIs) that use the cFS infrastructure. These APIs are used to standardize the communication protocols on NASAs space SDRs. The cFS-STRS Operating Environment (OE) is a portable cFS library, which adds the ability to run STRS applications on existing cFS platforms. The purpose of this paper is to discuss the cFS-STRS OE prototype, preliminary experimental results performed using the Advanced Space Radio Platform (ASRP), the GRC S- band Ground Station and the SCaN (Space Communication and Navigation) Testbed currently flying onboard the International Space Station (ISS). Additionally, this paper presents a demonstration of the Consultative Committee for Space Data Systems (CCSDS) Spacecraft Onboard Interface Services (SOIS) using electronic data sheets (EDS) inside cFE. This configuration allows for the data sheets to specify binary formats for data exchange between STRS applications. The integration of STRS with cFS leverages mission-proven platform functions and mitigates barriers to integration with future missions. This reduces flight software development time and the costs of software-defined radio (SDR) platforms. Furthermore, the combined benefits of STRS standardization with the flexibility of cFS provide an effective, reliable and modular framework to minimize software development efforts for spaceflight missions.

Modeling SMAP Spacecraft Attitude Control Estimation Error Using Signal Generation Model

NASA Technical Reports Server (NTRS)

Rizvi, Farheen

2016-01-01

Two ground simulation software are used to model the SMAP spacecraft dynamics. The CAST software uses a higher fidelity model than the ADAMS software. The ADAMS software models the spacecraft plant, controller and actuator models, and assumes a perfect sensor and estimator model. In this simulation study, the spacecraft dynamics results from the ADAMS software are used as CAST software is unavailable. The main source of spacecraft dynamics error in the higher fidelity CAST software is due to the estimation error. A signal generation model is developed to capture the effect of this estimation error in the overall spacecraft dynamics. Then, this signal generation model is included in the ADAMS software spacecraft dynamics estimate such that the results are similar to CAST. This signal generation model has similar characteristics mean, variance and power spectral density as the true CAST estimation error. In this way, ADAMS software can still be used while capturing the higher fidelity spacecraft dynamics modeling from CAST software.

The research and practice of spacecraft software engineering

NASA Astrophysics Data System (ADS)

Chen, Chengxin; Wang, Jinghua; Xu, Xiaoguang

2017-06-01

In order to ensure the safety and reliability of spacecraft software products, it is necessary to execute engineering management. Firstly, the paper introduces the problems of unsystematic planning, uncertain classified management and uncontinuous improved mechanism in domestic and foreign spacecraft software engineering management. Then, it proposes a solution for software engineering management based on system-integrated ideology in the perspective of spacecraft system. Finally, a application result of spacecraft is given as an example. The research can provides a reference for executing spacecraft software engineering management and improving software product quality.

SPCC- Software Elements for Security Partition Communication Controller

NASA Astrophysics Data System (ADS)

Herpel, H. J.; Willig, G.; Montano, G.; Tverdyshev, S.; Eckstein, K.; Schoen, M.

2016-08-01

Future satellite missions like Earth Observation, Telecommunication or any other kind are likely to be exposed to various threats aiming at exploiting vulnerabilities of the involved systems and communications. Moreover, the growing complexity of systems coupled with more ambitious types of operational scenarios imply increased security vulnerabilities in the future. In the paper we will describe an architecture and software elements to ensure high level of security on-board a spacecraft. First the threats to the Security Partition Communication Controller (SPCC) will be addressed including the identification of specific vulnerabilities to the SPCC. Furthermore, appropriate security objectives and security requirements are identified to be counter the identified threats. The security evaluation of the SPCC will be done in accordance to the Common Criteria (CC). The Software Elements for SPCC has been implemented on flight representative hardware which consists of two major elements: the I/O board and the SPCC board. The SPCC board provides the interfaces with ground while the I/O board interfaces with typical spacecraft equipment busses. Both boards are physically interconnected by a high speed spacewire (SpW) link.

Remote Software Application and Display Development

NASA Technical Reports Server (NTRS)

Sanders, Brandon T.

2014-01-01

The era of the shuttle program has come to an end, but only to give rise to newer and more exciting projects. Now is the time of the Orion spacecraft, a work of art designed to exceed all previous endeavors of man. NASA is exiting the time of exploration and is entering a new period, a period of pioneering. With this new mission, many of NASAs organizations must undergo a great deal of change and development to support the Orion missions. The Spaceport Command and Control System (SCCS) is the new system that will provide NASA the ability to launch rockets into orbit and thus control Orion and other spacecraft as the goal of populating Mars becomes ever increasingly tangible. Since the previous control system, Launch Processing System (LPS), was primarily designed to launch the shuttles, SCCS was needed as Kennedy Space Center (KSC) reorganized to a multiuser spaceport for commercial flights, providing a more versatile control over rockets. Within SCCS, is the Launch Control System (LCS), which is the remote software behind the command and monitoring of flight and ground system hardware. This internship at KSC has involved two main components in LCS, including Remote Software Application and Display development. The display environment provides a graphical user interface for an operator to view and see if any cautions are raised, while the remote applications are the backbone that communicate with hardware, and then relay the data back to the displays. These elements go hand in hand as they provide monitoring and control over hardware and software alike from the safety of the Launch Control Center. The remote software applications are written in Application Control Language (ACL), which must undergo unit testing to ensure data integrity. This paper describes both the implementation and writing of unit tests in ACL code for remote software applications, as well as the building of remote displays to be used in the Launch Control Center (LCC).

Zero-Propellant Maneuver[TM] Flight Results for 180 deg ISS Rotation

NASA Technical Reports Server (NTRS)

Bedrossian, Nazareth; Bhatt, Sagar; Lammers, Mike; Nguyen, Louis

2007-01-01

This paper presents results for the Zero Propellant Maneuver (ZPM) TradeMark attitude control concept flight demonstration. On March 3, 2007, a ZPM was used to reorient the International Space Station 180 degrees without using any propellant. The identical reorientation performed with thrusters would have burned 110lbs of propellant. The ZPM was a pre-planned trajectory used to command the CMG attitude hold controller to perform the maneuver between specified initial and final states while maintaining the CMGs within their operational limits. The trajectory was obtained from a PseudoSpectral solution to a new optimal attitude control problem. The flight test established the breakthrough capability to simultaneously perform a large angle attitude maneuver and momentum desaturation without the need to use thrusters. The flight implementation did not require any modifications to flight software. This approach is applicable to any spacecraft that are controlled by momentum storage devices.

Orion Launch Abort System Performance on Exploration Flight Test 1

NASA Technical Reports Server (NTRS)

McCauley, R.; Davidson, J.; Gonzalez, Guillermo

2015-01-01

This paper will present an overview of the flight test objectives and performance of the Orion Launch Abort System during Exploration Flight Test-1. Exploration Flight Test-1, the first flight test of the Orion spacecraft, was managed and led by the Orion prime contractor, Lockheed Martin, and launched atop a United Launch Alliance Delta IV Heavy rocket. This flight test was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety. This test included the first flight test of the Launch Abort System preforming Orion nominal flight mission critical objectives. NASA is currently designing and testing the Orion Multi-Purpose Crew Vehicle (MPCV). Orion will serve as NASA's new exploration vehicle to carry astronauts to deep space destinations and safely return them to earth. The Orion spacecraft is composed of four main elements: the Launch Abort System, the Crew Module, the Service Module, and the Spacecraft Adapter (Fig. 1). The Launch Abort System (LAS) provides two functions; during nominal launches, the LAS provides protection for the Crew Module from atmospheric loads and heating during first stage flight and during emergencies provides a reliable abort capability for aborts that occur within the atmosphere. The Orion Launch Abort System (LAS) consists of an Abort Motor to provide the abort separation from the Launch Vehicle, an Attitude Control Motor to provide attitude and rate control, and a Jettison Motor for crew module to LAS separation (Fig. 2). The jettison motor is used during a nominal launch to separate the LAS from the Launch Vehicle (LV) early in the flight of the second stage when it is no longer needed for aborts and at the end of an LAS abort sequence to enable deployment of the crew module's Landing Recovery System. The LAS also provides a Boost Protective Cover fairing that shields the crew module from debris and the aero-thermal environment during ascent. Although the Orion Program has tested a number of the critical systems of the Orion spacecraft on the ground, the launch environment cannot be replicated completely on Earth. A number of flight tests have been conducted and are planned to demonstrate the performance and enable certification of the Orion Spacecraft. Exploration Flight Test 1, the first flight test of the Orion spacecraft, was successfully flown on December 5, 2014 from Cape Canaveral Air Force Station's Space Launch Complex 37. Orion's first flight was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety, such as heat shield performance, separation events, avionics and software performance, attitude control and guidance, parachute deployment and recovery operations. One of the key separation events tested during this flight was the nominal jettison of the LAS. Data from this flight will be used to verify the function of the jettison motor to separate the Launch Abort System from the crew module so it can continue on with the mission. The LAS nominal jettison event on Exploration Flight Test 1 occurred at six minutes and twenty seconds after liftoff (See Fig. 3). The abort motor and attitude control motors were inert for Exploration Flight Test 1, since the mission did not require abort capabilities. A suite of developmental flight instrumentation was included on the flight test to provide data on spacecraft subsystems and separation events. This paper will focus on the flight test objectives and performance of the LAS during ascent and nominal jettison. Selected LAS subsystem flight test data will be presented and discussed in the paper. Exploration Flight Test -1 will provide critical data that will enable engineering to improve Orion's design and reduce risk for the astronauts it will protect as NASA continues to move forward on its human journey to Mars. The lessons learned from Exploration Flight Test 1 and the other Flight Test Vehicles will certainly contribute to the vehicle architecture of a human-rated space launch vehicle.

Challenges of the Cassini Test Bed Simulating the Saturnian Environment

NASA Technical Reports Server (NTRS)

Hernandez, Juan C.; Badaruddin, Kareem S.

2007-01-01

The Cassini-Huygens mission is a joint NASA and European Space Agency (ESA) mission to collect scientific data of the Saturnian system and is managed by the Jet Propulsion Laboratory (JPL). After having arrived in Saturn orbit and releasing the ESA's Huygens probe for a highly successful descent and landing mission on Saturn's moon Titan, the Cassini orbiter continues on its tour of Saturn, its satellites, and the Saturnian environment. JPL's Cassini Integrated Test laboratory (ITL) is a dedicated high fidelity test bed that verifies and validates command sequences and flight software before upload to the Cassini spacecraft. The ITL provides artificial stimuli that allow a highly accurate hardware-in-the-loop test bed model that tests the operation of the Cassini spacecraft on the ground. This enables accurate prediction and recreation of mission events and flight software and hardware behavior. As we discovered more about the Saturnian environment, a combination of creative test methods and simulation changes were necessary to simulate the harmful effect that the optical and physical environment has on the pointing performance of Cassini. This paper presents the challenges experienced and overcome in that endeavor to simulate and test the post Saturn Orbit Insertion (SOI) and Probe Relay tour phase of the Cassini mission.

[Development of fixed-base full task space flight training simulator].

PubMed

Xue, Liang; Chen, Shan-quang; Chang, Tian-chun; Yang, Hong; Chao, Jian-gang; Li, Zhi-peng

2003-01-01

Fixed-base full task flight training simulator is a very critical and important integrated training facility. It is mostly used in training of integrated skills and tasks, such as running the flight program of manned space flight, dealing with faults, operating and controlling spacecraft flight, communicating information between spacecraft and ground. This simulator was made up of several subentries including spacecraft simulation, simulating cabin, sight image, acoustics, main controlling computer, instructor and assistant support. It has implemented many simulation functions, such as spacecraft environment, spacecraft movement, communicating information between spacecraft and ground, typical faults, manual control and operating training, training control, training monitor, training database management, training data recording, system detecting and so on.

Formal Analysis of the Remote Agent Before and After Flight

NASA Technical Reports Server (NTRS)

Havelund, Klaus; Lowry, Mike; Park, SeungJoon; Pecheur, Charles; Penix, John; Visser, Willem; White, Jon L.

2000-01-01

This paper describes two separate efforts that used the SPIN model checker to verify deep space autonomy flight software. The first effort occurred at the beginning of a spiral development process and found five concurrency errors early in the design cycle that the developers acknowledge would not have been found through testing. This effort required a substantial manual modeling effort involving both abstraction and translation from the prototype LISP code to the PROMELA language used by SPIN. This experience and others led to research to address the gap between formal method tools and the development cycle used by software developers. The Java PathFinder tool which directly translates from Java to PROMELA was developed as part of this research, as well as automatic abstraction tools. In 1999 the flight software flew on a space mission, and a deadlock occurred in a sibling subsystem to the one which was the focus of the first verification effort. A second quick-response "cleanroom" verification effort found the concurrency error in a short amount of time. The error was isomorphic to one of the concurrency errors found during the first verification effort. The paper demonstrates that formal methods tools can find concurrency errors that indeed lead to loss of spacecraft functions, even for the complex software required for autonomy. Second, it describes progress in automatic translation and abstraction that eventually will enable formal methods tools to be inserted directly into the aerospace software development cycle.

Global Ultraviolet Imaging Processing for the GGS Polar Visible Imaging System (VIS)

NASA Technical Reports Server (NTRS)

Frank, L. A.

1997-01-01

The Visible Imaging System (VIS) on Polar spacecraft of the NASA Goddard Space Flight Center was launched into orbit about Earth on February 24, 1996. Since shortly after launch, the Earth Camera subsystem of the VIS has been operated nearly continuously to acquire far ultraviolet, global images of Earth and its northern and southern auroral ovals. The only exceptions to this continuous imaging occurred for approximately 10 days at the times of the Polar spacecraft re-orientation maneuvers in October, 1996 and April, 1997. Since launch, approximately 525,000 images have been acquired with the VIS Earth Camera. The VIS instrument operational health continues to be excellent. Since launch, all systems have operated nominally with all voltages, currents, and temperatures remaining at nominal values. In addition, the sensitivity of the Earth Camera to ultraviolet light has remained constant throughout the operation period. Revised flight software was uploaded to the VIS in order to compensate for the spacecraft wobble. This is accomplished by electronic shuttering of the sensor in synchronization with the 6-second period of the wobble, thus recovering the original spatial resolution obtainable with the VIS Earth Camera. In addition, software patches were uploaded to make the VIS immune to signal dropouts that occur in the sliprings of the despun platform mechanism. These changes have worked very well. The VIS and in particular the VIS Earth Camera is fully operational and will continue to acquire global auroral images as the sun progresses toward solar maximum conditions after the turn of the century.

Prototype Common Bus Spacecraft: Hover Test Implementation and Results. Revision, Feb. 26, 2009

NASA Technical Reports Server (NTRS)

Hine, Butler Preston; Turner, Mark; Marshall, William S.

2009-01-01

In order to develop the capability to evaluate control system technologies, NASA Ames Research Center (Ames) began a test program to build a Hover Test Vehicle (HTV) - a ground-based simulated flight vehicle. The HTV would integrate simulated propulsion, avionics, and sensors into a simulated flight structure, and fly that test vehicle in terrestrial conditions intended to simulate a flight environment, in particular for attitude control. The ultimate purpose of the effort at Ames is to determine whether the low-cost hardware and flight software techniques are viable for future low cost missions. To enable these engineering goals, the project sought to develop a team, processes and procedures capable of developing, building and operating a fully functioning vehicle including propulsion, GN&C, structure, power and diagnostic sub-systems, through the development of the simulated vehicle.

Mesh Network Architecture for Enabling Inter-Spacecraft Communication

NASA Technical Reports Server (NTRS)

Becker, Christopher; Merrill, Garrick

2017-01-01

To enable communication between spacecraft operating in a formation or small constellation, a mesh network architecture was developed and tested using a time division multiple access (TDMA) communication scheme. The network is designed to allow for the exchange of telemetry and other data between spacecraft to enable collaboration between small spacecraft. The system uses a peer-to-peer topology with no central router, so that it does not have a single point of failure. The mesh network is dynamically configurable to allow for addition and subtraction of new spacecraft into the communication network. Flight testing was performed using an unmanned aerial system (UAS) formation acting as a spacecraft analogue and providing a stressing environment to prove mesh network performance. The mesh network was primarily devised to provide low latency, high frequency communication but is flexible and can also be configured to provide higher bandwidth for applications desiring high data throughput. The network includes a relay functionality that extends the maximum range between spacecraft in the network by relaying data from node to node. The mesh network control is implemented completely in software making it hardware agnostic, thereby allowing it to function with a wide variety of existing radios and computing platforms..

Smarter Software For Enhanced Vehicle Health Monitoring and Inter-Planetary Exploration

NASA Technical Reports Server (NTRS)

Larson, William E.; Goodrich, Charles H.; Steinrock, Todd (Technical Monitor)

2001-01-01

The existing philosophy for space mission control was born in the early days of the space program when technology did not exist to put significant control responsibility onboard the spacecraft. NASA relied on a team of ground control experts to troubleshoot systems when problems occurred. As computing capability improved, more responsibility was handed over to the systems software. However, there is still a large contingent of both launch and flight controllers supporting each mission. New technology can update this philosophy to increase mission assurance and reduce the cost of inter-planetary exploration. The advent of model-based diagnosis and intelligent planning software enables spacecraft to handle most routine problems automatically and allocate resources in a flexible way to realize mission objectives. The manifests for recent missions include multiple subsystems and complex experiments. Spacecraft must operate at longer distances from earth where communications delays make earthbound command and control impractical. NASA's Ames Research Center (ARC) has demonstrated the utility of onboard diagnosis and planning with the Remote Agent experiment in 1999. KSC has pioneered model-based diagnosis and demonstrated its utility for ground support operations. KSC and ARC are cooperating in research to improve the state of the art of this technology. This paper highlights model-based reasoning applications for Moon and Mars missions including in-situ resource utilization and enhanced vehicle health monitoring.

Simulation of a tethered microgravity robot pair and validation on a planar air bearing

NASA Astrophysics Data System (ADS)

Mantellato, R.; Lorenzini, E. C.; Sternberg, D.; Roascio, D.; Saenz-Otero, A.; Zachrau, H. J.

2017-09-01

A software model has been developed to simulate the on-orbit dynamics of a dual-mass tethered system where one or both of the tethered spacecraft are able to produce propulsive thrust. The software simulates translations and rotations of both spacecraft, with the visco-elastic tether being simulated as a lumped-mass model. Thanks to this last feature, tether longitudinal and lateral modes of vibration and tether tension can be accurately assessed. Also, the way the spacecraft motion responds to sudden tether tension spikes can be studied in detail. The code enables the simulation of different scenarios, including space tug missions for deorbit maneuvers in a debris mitigation context and general-purpose tethered formation flight missions. This study aims to validate the software through a representative test campaign performed with the MIT Synchronized Position Hold Engage and Reorient Experimental Satellites (SPHERES) planar air bearing system. Results obtained with the numerical simulator are compared with data from direct measurements in different testing setups. The studied cases take into account different initial conditions of the spacecraft velocities and relative attitudes, and thrust forces. Data analysis is presented comparing the results of the simulations with direct measurements of acceleration and Azimuth rate of the two bodies in the planar air bearing test facility using a Nylon tether. Plans for conducting a microgravity test campaign using the SPHERES satellites aboard the International Space Station are also being scheduled in the near future in order to further validate the simulation using data from the relevant operational environment of extended microgravity with full six degree of freedom (per body) motion.

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

NASA Technical Reports Server (NTRS)

Dubon, Lydia P.

2006-01-01

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

NASA Technical Reports Server (NTRS)

Dubon, Lydia P.

2006-01-01

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Deep Space 1 arrives at KSC and processing begins in the PHSF

NASA Technical Reports Server (NTRS)

1998-01-01

NASA's Deep Space 1 spacecraft waits in the Payload Hazardous Servicing Facility for prelaunch processing. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

KSC-98pc1050

NASA Image and Video Library

1998-09-11

The first stage of Boeing's Delta 7326 rocket, which will be used to launch the Deep Space 1 spacecraft, arrives at Pad 17A at Cape Canaveral Air Station. Targeted for launch on Oct. 15, 1998, this first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1051

NASA Image and Video Library

1998-09-11

The first stage of Boeing's Delta 7326 rocket, which will be used to launch the Deep Space 1 spacecraft, arrives at Pad 17A at Cape Canaveral Air Station. Targeted for launch on Oct. 15, 1998, this first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc933

NASA Image and Video Library

1998-08-17

KENNEDY SPACE CENTER, FLA. -- Wearing special protective suits, workers ready NASA’s Deep Space 1 spacecraft for prelaunch processing in the Payload Hazardous Servicing Facility at KSC. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA’s New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc931

NASA Image and Video Library

1998-08-17

KENNEDY SPACE CENTER, FLA. -- NASA’s Deep Space 1 spacecraft waits in the Payload Hazardous Servicing Facility for prelaunch processing. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA’s New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc934

NASA Image and Video Library

1998-08-17

KENNEDY SPACE CENTER, FLA. -- Wearing special protective suits, workers ready NASA’s Deep Space 1 spacecraft for prelaunch processing in the Payload Hazardous Servicing Facility at KSC. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA’s New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1049

NASA Image and Video Library

1998-09-11

The first stage of Boeing's Delta 7326 rocket, which will be used to launch the Deep Space 1 spacecraft, arrives at Pad 17A at Cape Canaveral Air Station. Targeted for launch on Oct. 15, 1998, this first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

Agent Based Software for the Autonomous Control of Formation Flying Spacecraft

NASA Technical Reports Server (NTRS)

How, Jonathan P.; Campbell, Mark; Dennehy, Neil (Technical Monitor)

2003-01-01

Distributed satellite systems is an enabling technology for many future NASA/DoD earth and space science missions, such as MMS, MAXIM, Leonardo, and LISA [1, 2, 3]. While formation flying offers significant science benefits, to reduce the operating costs for these missions it will be essential that these multiple vehicles effectively act as a single spacecraft by performing coordinated observations. Autonomous guidance, navigation, and control as part of a coordinated fleet-autonomy is a key technology that will help accomplish this complex goal. This is no small task, as most current space missions require significant input from the ground for even relatively simple decisions such as thruster burns. Work for the NMP DS1 mission focused on the development of the New Millennium Remote Agent (NMRA) architecture for autonomous spacecraft control systems. NMRA integrates traditional real-time monitoring and control with components for constraint-based planning, robust multi-threaded execution, and model-based diagnosis and reconfiguration. The complexity of using an autonomous approach for space flight software was evident when most of its capabilities were stripped off prior to launch (although more capability was uplinked subsequently, and the resulting demonstration was very successful).

Automated Diagnosis and Control of Complex Systems

NASA Technical Reports Server (NTRS)

Kurien, James; Plaunt, Christian; Cannon, Howard; Shirley, Mark; Taylor, Will; Nayak, P.; Hudson, Benoit; Bachmann, Andrew; Brownston, Lee; Hayden, Sandra;

Design, Assembly, Integration, and Testing of a Power Processing Unit for a Cylindrical Hall Thruster, the NORSAT-2 Flatsat, and the Vector Gravimeter for Asteroids Instrument Computer

NASA Astrophysics Data System (ADS)

Svatos, Adam Ladislav

This thesis describes the author's contributions to three separate projects. The bus of the NORSAT-2 satellite was developed by the Space Flight Laboratory (SFL) for the Norwegian Space Centre (NSC) and Space Norway. The author's contributions to the mission were performing unit tests for the components of all the spacecraft subsystems as well as designing and assembling the flatsat from flight spares. Gedex's Vector Gravimeter for Asteroids (VEGA) is an accelerometer for spacecraft. The author's contributions to this payload were modifying the instrument computer board schematic, designing the printed circuit board, developing and applying test software, and performing thermal acceptance testing of two instrument computer boards. The SFL's cylindrical Hall effect thruster combines the cylindrical configuration for a Hall thruster and uses permanent magnets to achieve miniaturization and low power consumption, respectively. The author's contributions were to design, build, and test an engineering model power processing unit.

VERSE - Virtual Equivalent Real-time Simulation

NASA Technical Reports Server (NTRS)

Zheng, Yang; Martin, Bryan J.; Villaume, Nathaniel

2005-01-01

Distributed real-time simulations provide important timing validation and hardware in the- loop results for the spacecraft flight software development cycle. Occasionally, the need for higher fidelity modeling and more comprehensive debugging capabilities - combined with a limited amount of computational resources - calls for a non real-time simulation environment that mimics the real-time environment. By creating a non real-time environment that accommodates simulations and flight software designed for a multi-CPU real-time system, we can save development time, cut mission costs, and reduce the likelihood of errors. This paper presents such a solution: Virtual Equivalent Real-time Simulation Environment (VERSE). VERSE turns the real-time operating system RTAI (Real-time Application Interface) into an event driven simulator that runs in virtual real time. Designed to keep the original RTAI architecture as intact as possible, and therefore inheriting RTAI's many capabilities, VERSE was implemented with remarkably little change to the RTAI source code. This small footprint together with use of the same API allows users to easily run the same application in both real-time and virtual time environments. VERSE has been used to build a workstation testbed for NASA's Space Interferometry Mission (SIM PlanetQuest) instrument flight software. With its flexible simulation controls and inexpensive setup and replication costs, VERSE will become an invaluable tool in future mission development.

Automatic Parameter Tuning for the Morpheus Vehicle Using Particle Swarm Optimization

NASA Technical Reports Server (NTRS)

Birge, B.

2013-01-01

A high fidelity simulation using a PC based Trick framework has been developed for Johnson Space Center's Morpheus test bed flight vehicle. There is an iterative development loop of refining and testing the hardware, refining the software, comparing the software simulation to hardware performance and adjusting either or both the hardware and the simulation to extract the best performance from the hardware as well as the most realistic representation of the hardware from the software. A Particle Swarm Optimization (PSO) based technique has been developed that increases speed and accuracy of the iterative development cycle. Parameters in software can be automatically tuned to make the simulation match real world subsystem data from test flights. Special considerations for scale, linearity, discontinuities, can be all but ignored with this technique, allowing fast turnaround both for simulation tune up to match hardware changes as well as during the test and validation phase to help identify hardware issues. Software models with insufficient control authority to match hardware test data can be immediately identified and using this technique requires very little to no specialized knowledge of optimization, freeing model developers to concentrate on spacecraft engineering. Integration of the PSO into the Morpheus development cycle will be discussed as well as a case study highlighting the tool's effectiveness.

Science Benefits of Onboard Spacecraft Navigation

NASA Technical Reports Server (NTRS)

Cangahuala, Al; Bhaskaran, Shyam; Owen, Bill

2012-01-01

Primitive bodies (asteroids and comets), which have remained relatively unaltered since their formation, are important targets for scientific missions that seek to understand the evolution of the solar system. Often the first step is to fly by these bodies with robotic spacecraft. The key to maximizing data returns from these flybys is to determine the spacecraft trajectory relative to the target body-in short, navigate the spacecraft- with sufficient accuracy so that the target is guaranteed to be in the instruments' field of view. The most powerful navigation data in these scenarios are images taken by the spacecraft of the target against a known star field (onboard astrometry). Traditionally, the relative trajectory of the spacecraft must be estimated hours to days in advance using images collected by the spacecraft. This is because of (1)!the long round-trip light times between the spacecraft and the Earth and (2)!the time needed to downlink and process navigation data on the ground, make decisions based on the result, and build and uplink instrument pointing sequences from the results. The light time and processing time compromise navigation accuracy considerably, because there is not enough time to use more accurate data collected closer to the target-such data are more accurate because the angular capability of the onboard astrometry is essentially constant as the distance to the target decreases, resulting in better "plane-of- sky" knowledge of the target. Excellent examples of these timing limitations are high-speed comet encounters. Comets are difficult to observe up close; their orbits often limit scientists to brief, rapid flybys, and their coma further restricts viewers from seeing the nucleus in any detail, unless they can view the nucleus at close range. Comet nuclei details are typically discernable for much shorter durations than the roundtrip light time to Earth, so robotic spacecraft must be able to perform onboard navigation. This onboard navigation can be accomplished through a self- contained system that by eliminating light time restrictions dramatically improves the relative trajectory knowledge and control and subsequently increases the amount of quality data collected. Flybys are one-time events, so the system's underlying algorithms and software must be extremely robust. The autonomous software must also be able to cope with the unknown size, shape, and orientation of the previously unseen comet nucleus. Furthermore, algorithms must be reliable in the presence of imperfections and/or damage to onboard cameras accrued after many years of deep-space operations. The AutoNav operational flight software packages, developed by scientists at the Jet Propulsion Laboratory (JPL) under contract with NASA, meet all these requirements. They have been directly responsible for the successful encounters on all of NASA's close-up comet-imaging missions (see Figure !1). AutoNav is the only system to date that has autonomously tracked comet nuclei during encounters and performed autonomous interplanetary navigation. AutoNav has enabled five cometary flyby missions (Table!1) residing on four NASA spacecraft provided by three different spacecraft builders. Using this software, missions were able to process a combined total of nearly 1000 images previously unseen by humans. By eliminating the need to navigate spacecraft from Earth, the accuracy gained by AutoNav during flybys compared to ground-based navigation is about 1!order of magnitude in targeting and 2!orders of magnitude in time of flight. These benefits ensure that pointing errors do not compromise data gathered during flybys. In addition, these benefits can be applied to flybys of other solar system objects, flybys at much slower relative velocities, mosaic imaging campaigns, and other proximity activities (e.g., orbiting, hovering, and descent/ascent).

Development of a Radio Frequency Space Environment Path Emulator for Evaluating Spacecraft Ranging Hardware

NASA Technical Reports Server (NTRS)

Mitchell, Jason W.; Baldwin, Philip J.; Kurichh, Rishi; Naasz, Bo J.; Luquette, Richard J.

2007-01-01

The Formation Flying Testbed (FFTB) at the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) provides a hardware-in-the-loop test environment for formation navigation and control. The facility is evolving as a modular, hybrid, dynamic simulation facility for end-to-end guidance, navigation and. control (GN&C) design and analysis of formation flying spacecraft. The core capabilities of the FFTB, as a platform for testing critical hardware and software algorithms in-the-loop, have expanded to include S-band Radio Frequency (RF) modems for inter-spacecraft communication and ranging. To enable realistic simulations that require RF ranging sensors for relative navigation, a mechanism is needed to buffer the RF signals exchanged between spacecraft that accurately emulates the dynamic environment through which the RF signals travel, including the effects of medium, moving platforms, and radiated power. The Path Emulator for RF Signals (PERFS), currently under development at NASA GSFC, provides this capability. The function and performance of a prototype device are presented.

Development of an autonomous video rendezvous and docking system, phase 2

NASA Technical Reports Server (NTRS)

Tietz, J. C.; Richardson, T. E.

1983-01-01

The critical elements of an autonomous video rendezvous and docking system were built and used successfully in a physical laboratory simulation. The laboratory system demonstrated that a small, inexpensive electronic package and a flight computer of modest size can analyze television images to derive guidance information for spacecraft. In the ultimate application, the system would use a docking aid consisting of three flashing lights mounted on a passive target spacecraft. Television imagery of the docking aid would be processed aboard an active chase vehicle to derive relative positions and attitudes of the two spacecraft. The demonstration system used scale models of the target spacecraft with working docking aids. A television camera mounted on a 6 degree of freedom (DOF) simulator provided imagery of the target to simulate observations from the chase vehicle. A hardware video processor extracted statistics from the imagery, from which a computer quickly computed position and attitude. Computer software known as a Kalman filter derived velocity information from position measurements.

Operational radiological support for the US manned space program

NASA Technical Reports Server (NTRS)

Golightly, Michael J.; Hardy, Alva C.; Atwell, William; Weyland, Mark D.; Kern, John; Cash, Bernard L.

1993-01-01

Radiological support for the manned space program is provided by the Space Radiation Analysis Group at NASA/JSC. This support ensures crew safety through mission design analysis, real-time space environment monitoring, and crew exposure measurements. Preflight crew exposure calculations using mission design information are used to ensure that crew exposures will remain within established limits. During missions, space environment conditions are continuously monitored from within the Mission Control Center. In the event of a radiation environment enhancement, the impact to crew exposure is assessed and recommendations are provided to flight management. Radiation dosimeters are placed throughout the spacecraft and provided to each crewmember. During a radiation contingency, the crew could be requested to provide dosimeter readings. This information would be used for projecting crew dose enhancements. New instrumentation and computer technology are being developed to improve the support. Improved instruments include tissue equivalent proportional counter (TEPC)-based dosimeters and charged particle telescopes. Data from these instruments will be telemetered and will provide flight controllers with unprecedented information regarding the radiation environment in and around the spacecraft. New software is being acquired and developed to provide 'smart' space environmental data displays for use by flight controllers.

Methodology for Software Reliability Prediction. Volume 1.

DTIC Science & Technology

1987-11-01

SPACECRAFT 0 MANNED SPACECRAFT B ATCH SYSTEM AIRBORNE AVIONICS 0 UNMANNED EVENT C014TROL a REAL TIME CLOSED 0 UNMANNED SPACECRAFT LOOP OPERATINS SPACECRAFT...software reliability. A Software Reliability Measurement Framework was established which spans the life cycle of a software system and includes the...specification, prediction, estimation, and assessment of software reliability. Data from 59 systems , representing over 5 million lines of code, were

Simulating Descent and Landing of a Spacecraft

NASA Technical Reports Server (NTRS)

Balaram, J.; Jain, Abhinandan; Martin, Bryan; Lim, Christopher; Henriquez, David; McMahon, Elihu; Sohl, Garrett; Banerjee, Pranab; Steele, Robert; Bentley, Timothy

2005-01-01

The Dynamics Simulator for Entry, Descent, and Surface landing (DSENDS) software performs high-fidelity simulation of the Entry, Descent, and Landing (EDL) of a spacecraft into the atmosphere and onto the surface of a planet or a smaller body. DSENDS is an extension of the DShell and DARTS programs, which afford capabilities for mathematical modeling of the dynamics of a spacecraft as a whole and of its instruments, actuators, and other subsystems. DSENDS enables the modeling (including real-time simulation) of flight-train elements and all spacecraft responses during various phases of EDL. DSENDS provides high-fidelity models of the aerodynamics of entry bodies and parachutes plus supporting models of atmospheres. Terrain and real-time responses of terrain-imaging radar and lidar instruments can also be modeled. The program includes modules for simulation of guidance, navigation, hypersonic steering, and powered descent. Automated state-machine-driven model switching is used to represent spacecraft separations and reconfigurations. Models for computing landing contact and impact forces are expected to be added. DSENDS can be used as a stand-alone program or incorporated into a larger program that simulates operations in real time.

Auxiliary propulsion system flight package

NASA Technical Reports Server (NTRS)

Collett, C. R.

1987-01-01

Hughes Aircraft Company developed qualified and integrated flight, a flight test Ion Auxiliary Propulsion System (IAPS), on an Air Force technology satellite. The IAPS Flight Package consists of two identical Thruster Subsystems and a Diagnostic Subsystem. Each thruster subsystem (TSS) is comprised of an 8-cm ion Thruster-Gimbal-Beam Shield Unit (TGBSU); Power Electronics Unit; Digital Controller and Interface Unit (DCIU); and Propellant Tank, Valve and Feed Unit (PTVFU) plus the requisite cables. The Diagnostic Subsystem (DSS) includes four types of sensors for measuring the effect of the ion thrusters on the spacecraft and the surrounding plasma. Flight qualifications of IAPS, prior to installation on the spacecraft, consisted of performance, vibration and thermal-vacuum testing at the unit level, and thermal-vacuum testing at the subsystem level. Mutual compatibility between IAPS and the host spacecraft was demonstrated during a series of performance and environmental tests after the IAPS Flight Package was installed on the spacecraft. After a spacecraft acoustic test, performance of the ion thrusters was reverified by removing the TGBSUs for a thorough performance test at Hughes Research Laboratories (HRL). The TGBSUs were then reinstalled on the spacecraft. The IAPS Flight Package is ready for flight testing when Shuttle flights are resumed.

A Common DPU Platform for ESA JUICE Mission Instruments

NASA Astrophysics Data System (ADS)

Aberg, Martin; Hellstrom, Daniel; Samuelsson, Arne; Torelli, Felice

2016-08-01

This paper describes the resulting hardware and software platform based on GR712RC [1] LEON3-FT that Cobham Gaisler developed in accordance with the common system requirements of the ten scientific instruments on-board the ESA JUICE spacecraft destined the Jupiter system [8].The radiation hardened DPU platform features EDAC protected boot, application memory and working memory of configurable sizes and SpaceWire, FPGA I/O-32/16/8, GPIO, UART and SPI I/O interfaces. The design has undergone PSA, Risk, WCA, Radiation analyses etc. to justify component and design choices resulting in a robust design that can be used in spacecrafts requiring a total dose up to 100krad(Si). The prototype board manufactured uses engineering models of the flight components to ensure that development is representative.Validated boot, standby and driver software accommodates the various DPU platform configurations. The boot performs low-level DPU initialization, standby handles OBC SpaceWire communication and finally the loading and executing of application images typically stored in the non-volatile application memory.

JPL control/structure interaction test bed real-time control computer architecture

NASA Technical Reports Server (NTRS)

Briggs, Hugh C.

1989-01-01

The Control/Structure Interaction Program is a technology development program for spacecraft that exhibit interactions between the control system and structural dynamics. The program objectives include development and verification of new design concepts - such as active structure - and new tools - such as combined structure and control optimization algorithm - and their verification in ground and possibly flight test. A focus mission spacecraft was designed based upon a space interferometer and is the basis for design of the ground test article. The ground test bed objectives include verification of the spacecraft design concepts, the active structure elements and certain design tools such as the new combined structures and controls optimization tool. In anticipation of CSI technology flight experiments, the test bed control electronics must emulate the computation capacity and control architectures of space qualifiable systems as well as the command and control networks that will be used to connect investigators with the flight experiment hardware. The Test Bed facility electronics were functionally partitioned into three units: a laboratory data acquisition system for structural parameter identification and performance verification; an experiment supervisory computer to oversee the experiment, monitor the environmental parameters and perform data logging; and a multilevel real-time control computing system. The design of the Test Bed electronics is presented along with hardware and software component descriptions. The system should break new ground in experimental control electronics and is of interest to anyone working in the verification of control concepts for large structures.

Software for Simulating Air Traffic

NASA Technical Reports Server (NTRS)

Sridhar, Banavar; Bilimoria, Karl; Grabbe, Shon; Chatterji, Gano; Sheth, Kapil; Mulfinger, Daniel

2006-01-01

Future Air Traffic Management Concepts Evaluation Tool (FACET) is a system of software for performing computational simulations for evaluating advanced concepts of advanced air-traffic management. FACET includes a program that generates a graphical user interface plus programs and databases that implement computational models of weather, airspace, airports, navigation aids, aircraft performance, and aircraft trajectories. Examples of concepts studied by use of FACET include aircraft self-separation for free flight; prediction of air-traffic-controller workload; decision support for direct routing; integration of spacecraft-launch operations into the U.S. national airspace system; and traffic- flow-management using rerouting, metering, and ground delays. Aircraft can be modeled as flying along either flight-plan routes or great-circle routes as they climb, cruise, and descend according to their individual performance models. The FACET software is modular and is written in the Java and C programming languages. The architecture of FACET strikes a balance between flexibility and fidelity; as a consequence, FACET can be used to model systemwide airspace operations over the contiguous U.S., involving as many as 10,000 aircraft, all on a single desktop or laptop computer running any of a variety of operating systems. Two notable applications of FACET include: (1) reroute conformance monitoring algorithms that have been implemented in one of the Federal Aviation Administration s nationally deployed, real-time, operational systems; and (2) the licensing and integration of FACET with the commercially available Flight Explorer, which is an Internet- based, real-time flight-tracking system.

14 CFR 1216.305 - Criteria for actions requiring environmental assessments.

Code of Federal Regulations, 2012 CFR

2012-01-01

... assessment are: (1) Specific spacecraft development and flight projects in space science. (2) Specific spacecraft development and flight projects in space and terrestrial applications. (3) Specific experimental... spacecraft development and flight projects. (2) R&D activities in space and terrestrial applications (e.g...

ISS Solar Array Management

NASA Technical Reports Server (NTRS)

Williams, James P.; Martin, Keith D.; Thomas, Justin R.; Caro, Samuel

2010-01-01

The International Space Station (ISS) Solar Array Management (SAM) software toolset provides the capabilities necessary to operate a spacecraft with complex solar array constraints. It monitors spacecraft telemetry and provides interpretations of solar array constraint data in an intuitive manner. The toolset provides extensive situational awareness to ensure mission success by analyzing power generation needs, array motion constraints, and structural loading situations. The software suite consists of several components including samCS (constraint set selector), samShadyTimers (array shadowing timers), samWin (visualization GUI), samLock (array motion constraint computation), and samJet (attitude control system configuration selector). It provides high availability and uptime for extended and continuous mission support. It is able to support two-degrees-of-freedom (DOF) array positioning and supports up to ten simultaneous constraints with intuitive 1D and 2D decision support visualizations of constraint data. Display synchronization is enabled across a networked control center and multiple methods for constraint data interpolation are supported. Use of this software toolset increases flight safety, reduces mission support effort, optimizes solar array operation for achieving mission goals, and has run for weeks at a time without issues. The SAM toolset is currently used in ISS real-time mission operations.

The Transition from Spacecraft Development Ot Flight Operation: Human Factor Considerations

NASA Technical Reports Server (NTRS)

Basilio, Ralph R.

2000-01-01

In the field of aeronautics and astronautics, a paradigm shift has been witnessed by those in academia, research and development, and private industry. Long development life cycles and the budgets to support such programs and projects has given way to aggressive task schedules and leaner resources to draw from all the while challenging assigned individuals to create and produce improved products of processes. however, this "faster, better, cheaper" concept cannot merely be applied to the design, development, and test of complex systems such as earth-orbiting of interplanetary robotic spacecraft. Full advantage is not possible without due consideration and application to mission operations planning and flight operations, Equally as important as the flight system, the mission operations system consisting of qualified personnel, ground hardware and software tools, and verified and validated operational processes, should also be regarded as a complex system requiring personnel to draw upon formal education, training, related experiences, and heuristic reasoning in engineering an effective and efficient system. Unquestionably, qualified personnel are the most important elements of a mission operations system. This paper examines the experiences of the Deep Space I Project, the first in a series of new technology in-flight validation missions sponsored by the United States National Aeronautics and Space Administration (NASA), specifically, in developing a subsystems analysis and technology validation team comprised of former spacecraft development personnel. Human factor considerations are investigated from initial concept/vision formulation; through operational process development; personnel test and training; to initial uplink product development and test support. Emphasis has been placed on challenges and applied or recommended solutions, so as to provide opportunities for future programs and projects to address and disposition potential issues and concerns as early as possible to reap the benefits associated with learning from other's past experiences.

Flight Mechanics/Estimation Theory Symposium, 1989

NASA Technical Reports Server (NTRS)

Stengle, Thomas (Editor)

1989-01-01

Numerous topics in flight mechanics and estimation were discussed. Satellite attitude control, quaternion estimation, orbit and attitude determination, spacecraft maneuvers, spacecraft navigation, gyroscope calibration, spacecraft rendevous, and atmospheric drag model calculations for spacecraft lifetime prediction are among the topics covered.

Quadrocopter Control Design and Flight Operation

NASA Technical Reports Server (NTRS)

Karwoski, Katherine

2011-01-01

A limiting factor in control system design and analysis for spacecraft is the inability to physically test new algorithms quickly and cheaply. Test flights of space vehicles are costly and take much preparation. As such, EV41 recently acquired a small research quadrocopter that has the ability to be a test bed for new control systems. This project focused on learning how to operate, fly, and maintain the quadrocopter, as well as developing and testing protocols for its use. In parallel to this effort, developing a model in Simulink facilitated the design and analysis of simple control systems for the quadrocopter. Software provided by the manufacturer enabled testing of the Simulink control system on the vehicle.

Assurance of COTS Boards for Space Flight. Part 1

NASA Technical Reports Server (NTRS)

Plante, Jeannette; Helmold, Norm; Eveland, Clay

1998-01-01

Space Flight hardware and software designers are increasingly turning to Commercial-Off-the-Shelf (COTS) products in hopes of meeting the demands imposed on them by projects with short development cycle times. The Technology Validation Assurance (TVA) team at NASA GSFC has embarked on applying a method for inserting COTS hardware into the Spartan 251 spacecraft. This method includes Procurement, Characterization, Ruggedization/Remediation and Verification Testing process steps which are intended to increase the uses confidence in the hardware's ability to function in the intended application for the required duration. As this method is refined with use, it has the potential for becoming a benchmark for industry-wide use of COTS in high reliability systems.

NASA Tech Briefs, October 2003

NASA Technical Reports Server (NTRS)

2003-01-01

Topics covered include: Cryogenic Temperature-Gradient Foam/Substrate Tensile Tester; Flight Test of an Intelligent Flight-Control System; Slat Heater Boxes for Thermal Vacuum Testing; System for Testing Thermal Insulation of Pipes; Electrical-Impedance-Based Ice-Thickness Gauges; Simulation System for Training in Laparoscopic Surgery; Flasher Powered by Photovoltaic Cells and Ultracapacitors; Improved Autoassociative Neural Networks; Toroidal-Core Microinductors Biased by Permanent Magnets; Using Correlated Photons to Suppress Background Noise; Atmospheric-Fade-Tolerant Tracking and Pointing in Wireless Optical Communication; Curved Focal-Plane Arrays Using Back-Illuminated High-Purity Photodetectors; Software for Displaying Data from Planetary Rovers; Software for Refining or Coarsening Computational Grids; Software for Diagnosis of Multiple Coordinated Spacecraft; Software Helps Retrieve Information Relevant to the User; Software for Simulating a Complex Robot; Software for Planning Scientific Activities on Mars; Software for Training in Pre-College Mathematics; Switching and Rectification in Carbon-Nanotube Junctions; Scandia-and-Yttria-Stabilized Zirconia for Thermal Barriers; Environmentally Safer, Less Toxic Fire-Extinguishing Agents; Multiaxial Temperature- and Time-Dependent Failure Model; Cloverleaf Vibratory Microgyroscope with Integrated Post; Single-Vector Calibration of Wind-Tunnel Force Balances; Microgyroscope with Vibrating Post as Rotation Transducer; Continuous Tuning and Calibration of Vibratory Gyroscopes; Compact, Pneumatically Actuated Filter Shuttle; Improved Bearingless Switched-Reluctance Motor; Fluorescent Quantum Dots for Biological Labeling; Growing Three-Dimensional Corneal Tissue in a Bioreactor; Scanning Tunneling Optical Resonance Microscopy; The Micro-Arcsecond Metrology Testbed; Detecting Moving Targets by Use of Soliton Resonances; and Finite-Element Methods for Real-Time Simulation of Surgery.

Deep Space 1 arrives at KSC and processing begins in the PHSF

NASA Technical Reports Server (NTRS)

1998-01-01

Wearing special protective suits, workers ready NASA's Deep Space 1 spacecraft for prelaunch processing in the Payload Hazardous Servicing Facility at KSC. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

Deep Space 1 arrives at KSC and processing begins in the PHSF

NASA Technical Reports Server (NTRS)

1998-01-01

Wearing special protective suits, workers look over NASA's Deep Space 1 spacecraft before prelaunch processing in the Payload Hazardous Servicing Facility at KSC. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

Deep Space 1 arrives at KSC and processing begins in the PHSF

NASA Technical Reports Server (NTRS)

1998-01-01

Wearing special protective suits, workers maneuver NASA's Deep Space 1 spacecraft into place for prelaunch processing in the Payload Hazardous Servicing Facility at KSC. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

Deep Space 1 arrives at KSC and processing begins in the PHSF

NASA Technical Reports Server (NTRS)

1998-01-01

Wearing special protective suits, workers move NASA's Deep Space 1 spacecraft into another room in the Payload Hazardous Servicing Facility for prelaunch processing . Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

KSC-98pc1053

NASA Image and Video Library

1998-09-11

The first stage of Boeing's Delta 7326 rocket, which will be used to launch the Deep Space 1 spacecraft, is lifted into place above the flame trench at Pad 17A at Cape Canaveral Air Station. Targeted for launch on Oct. 15, 1998, this first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1052

NASA Image and Video Library

1998-09-11

The first stage of Boeing's Delta 7326 rocket, which will be used to launch the Deep Space 1 spacecraft, is lifted into place above the surface of Pad 17A at Cape Canaveral Air Station. Targeted for launch on Oct. 15, 1998, this first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc936

NASA Image and Video Library

1998-08-17

KENNEDY SPACE CENTER, FLA. -- Wearing special protective suits, workers maneuver NASA’s Deep Space 1 spacecraft into place for prelaunch processing in the Payload Hazardous Servicing Facility at KSC. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA’s New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc937

NASA Image and Video Library

1998-08-17

KENNEDY SPACE CENTER, FLA. -- Wearing special protective suits, workers look over NASA’s Deep Space 1 spacecraft before prelaunch processing in the Payload Hazardous Servicing Facility at KSC. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA’s New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc932

NASA Image and Video Library

1998-08-17

KENNEDY SPACE CENTER, FLA. -- Wearing special protective suits, workers remove the protective covering from NASA’s Deep Space 1 spacecraft in the Payload Hazardous Servicing Facility at KSC to prepare it for prelaunch processing. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA’s New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc935

NASA Image and Video Library

1998-08-17

KENNEDY SPACE CENTER, FLA. -- Wearing special protective suits, workers move NASA’s Deep Space 1 spacecraft into another room in the Payload Hazardous Servicing Facility for prelaunch processing . Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA’s New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

TES: A modular systems approach to expert system development for real-time space applications

NASA Technical Reports Server (NTRS)

Cacace, Ralph; England, Brenda

1988-01-01

A major goal of the Space Station era is to reduce reliance on support from ground based experts. The development of software programs using expert systems technology is one means of reaching this goal without requiring crew members to become intimately familiar with the many complex spacecraft subsystems. Development of an expert systems program requires a validation of the software with actual flight hardware. By combining accurate hardware and software modelling techniques with a modular systems approach to expert systems development, the validation of these software programs can be successfully completed with minimum risk and effort. The TIMES Expert System (TES) is an application that monitors and evaluates real time data to perform fault detection and fault isolation tasks as they would otherwise be carried out by a knowledgeable designer. The development process and primary features of TES, a modular systems approach, and the lessons learned are discussed.

Advanced Software Techniques for Data Management Systems. Volume 2: Space Shuttle Flight Executive System: Functional Design

NASA Technical Reports Server (NTRS)

Pepe, J. T.

1972-01-01

A functional design of software executive system for the space shuttle avionics computer is presented. Three primary functions of the executive are emphasized in the design: task management, I/O management, and configuration management. The executive system organization is based on the applications software and configuration requirements established during the Phase B definition of the Space Shuttle program. Although the primary features of the executive system architecture were derived from Phase B requirements, it was specified for implementation with the IBM 4 Pi EP aerospace computer and is expected to be incorporated into a breadboard data management computer system at NASA Manned Spacecraft Center's Information system division. The executive system was structured for internal operation on the IBM 4 Pi EP system with its external configuration and applications software assumed to the characteristic of the centralized quad-redundant avionics systems defined in Phase B.

A Comparison of Learning Technologies for Teaching Spacecraft Software Development

ERIC Educational Resources Information Center

Straub, Jeremy

2014-01-01

The development of software for spacecraft represents a particular challenge and is, in many ways, a worst case scenario from a design perspective. Spacecraft software must be "bulletproof" and operate for extended periods of time without user intervention. If the software fails, it cannot be manually serviced. Software failure may…

Simple Sensitivity Analysis for Orion GNC

NASA Technical Reports Server (NTRS)

Pressburger, Tom; Hoelscher, Brian; Martin, Rodney; Sricharan, Kumar

2013-01-01

The performance of Orion flight software, especially its GNC software, is being analyzed by running Monte Carlo simulations of Orion spacecraft flights. The simulated performance is analyzed for conformance with flight requirements, expressed as performance constraints. Flight requirements include guidance (e.g. touchdown distance from target) and control (e.g., control saturation) as well as performance (e.g., heat load constraints). The Monte Carlo simulations disperse hundreds of simulation input variables, for everything from mass properties to date of launch.We describe in this paper a sensitivity analysis tool (Critical Factors Tool or CFT) developed to find the input variables or pairs of variables which by themselves significantly influence satisfaction of requirements or significantly affect key performance metrics (e.g., touchdown distance from target). Knowing these factors can inform robustness analysis, can inform where engineering resources are most needed, and could even affect operations. The contributions of this paper include the introduction of novel sensitivity measures, such as estimating success probability, and a technique for determining whether pairs of factors are interacting dependently or independently. The tool found that input variables such as moments, mass, thrust dispersions, and date of launch were found to be significant factors for success of various requirements. Examples are shown in this paper as well as a summary and physics discussion of EFT-1 driving factors that the tool found.

Micrometeoroid and Orbital Debris Threat Assessment: Mars Sample Return Earth Entry Vehicle

NASA Technical Reports Server (NTRS)

Christiansen, Eric L.; Hyde, James L.; Bjorkman, Michael D.; Hoffman, Kevin D.; Lear, Dana M.; Prior, Thomas G.

2011-01-01

This report provides results of a Micrometeoroid and Orbital Debris (MMOD) risk assessment of the Mars Sample Return Earth Entry Vehicle (MSR EEV). The assessment was performed using standard risk assessment methodology illustrated in Figure 1-1. Central to the process is the Bumper risk assessment code (Figure 1-2), which calculates the critical penetration risk based on geometry, shielding configurations and flight parameters. The assessment process begins by building a finite element model (FEM) of the spacecraft, which defines the size and shape of the spacecraft as well as the locations of the various shielding configurations. This model is built using the NX I-deas software package from Siemens PLM Software. The FEM is constructed using triangular and quadrilateral elements that define the outer shell of the spacecraft. Bumper-II uses the model file to determine the geometry of the spacecraft for the analysis. The next step of the process is to identify the ballistic limit characteristics for the various shield types. These ballistic limits define the critical size particle that will penetrate a shield at a given impact angle and impact velocity. When the finite element model is built, each individual element is assigned a property identifier (PID) to act as an index for its shielding properties. Using the ballistic limit equations (BLEs) built into the Bumper-II code, the shield characteristics are defined for each and every PID in the model. The final stage of the analysis is to determine the probability of no penetration (PNP) on the spacecraft. This is done using the micrometeoroid and orbital debris environment definitions that are built into the Bumper-II code. These engineering models take into account orbit inclination, altitude, attitude and analysis date in order to predict an impacting particle flux on the spacecraft. Using the geometry and shielding characteristics previously defined for the spacecraft and combining that information with the environment model calculations, the Bumper-II code calculates a probability of no penetration for the spacecraft.

What made Apollo a success?

NASA Technical Reports Server (NTRS)

1971-01-01

Spacecraft development, mission design planning, flight crew operations, and flight operations are considered. Spacecraft design principles and test activities are described. Determination of the best series of flights leading to a lunar landing at the earliest possible time, flight planning, techniques for establishing flight procedures and carrying out flight operations, and crew training and simulation activities are discussed.

Apollo experience report: Mission planning for Apollo entry

NASA Technical Reports Server (NTRS)

Graves, C. A.; Harpold, J. C.

1972-01-01

The problems encountered and the experience gained in the entry mission plans, flight software, trajectory-monitoring procedures, and backup trajectory-control techniques of the Apollo Program should provide a foundation upon which future spacecraft programs can be developed. Descriptions of these entry activities are presented. Also, to provide additional background information needed for discussion of the Apollo entry experience, descriptions of the entry targeting for the Apollo 11 mission and the postflight analysis of the Apollo 10 mission are presented.

Precise Image-Based Motion Estimation for Autonomous Small Body Exploration

NASA Technical Reports Server (NTRS)

Johnson, Andrew Edie; Matthies, Larry H.

2000-01-01

We have developed and tested a software algorithm that enables onboard autonomous motion estimation near small bodies using descent camera imagery and laser altimetry. Through simulation and testing, we have shown that visual feature tracking can decrease uncertainty in spacecraft motion to a level that makes landing on small, irregularly shaped, bodies feasible. Possible future work will include qualification of the algorithm as a flight experiment for the Deep Space 4/Champollion comet lander mission currently under study at the Jet Propulsion Laboratory.

Scientific Software

NASA Technical Reports Server (NTRS)

1995-01-01

The Interactive Data Language (IDL), developed by Research Systems, Inc., is a tool for scientists to investigate their data without having to write a custom program for each study. IDL is based on the Mariners Mars spectral Editor (MMED) developed for studies from NASA's Mars spacecraft flights. The company has also developed Environment for Visualizing Images (ENVI), an image processing system for easily analyzing remotely sensed data written in IDL. The Visible Human CD, another Research Systems product, is the first complete digital reference of photographic images for exploring human anatomy.

Photometer Performance Assessment in Kepler Science Data Processing

NASA Technical Reports Server (NTRS)

Li, Jie; Allen, Christopher; Bryson, Stephen T.; Caldwell, Douglas A.; Chandrasekaran, Hema; Clarke, Bruce D.; Gunter, Jay P.; Jenkins, Jon M.; Klaus, Todd C.; Quintana, Elisa V.;

Ground facility for information reception, processing, dissemination and scientific instruments management setup in the CORONAS-PHOTON space project

NASA Astrophysics Data System (ADS)

Buslov, A. S.; Kotov, Yu. D.; Yurov, V. N.; Bessonov, M. V.; Kalmykov, P. A.; Oreshnikov, E. M.; Alimov, A. M.; Tumanov, A. V.; Zhuchkova, E. A.

2011-06-01

This paper deals with the organizational structure of ground-based receiving, processing, and dissemination of scientific information created by the Astrophysics Institute of the Scientific Research Nuclear University, Moscow Engineering Physics Institute. Hardware structure and software features are described. The principles are given for forming sets of control commands for scientific equipment (SE) devices, and statistics data are presented on the operation of facility during flight tests of the spacecraft (SC) in the course of one year.

Gemini Program Mission Report for Gemini-Titan 1 (GT-1)

NASA Technical Reports Server (NTRS)

1964-01-01

The Gemini-Titan 1 (GT-1) space vehicle was comprised of the Gemini spacecraft and the Gemini launch vehicle. The Gemini launch vehicle is a two-stage modified Titan II ICBM. The major modifications are the addition of a malfunction detection system and a secondary flight controls system. The Gemini spacecraft, designed to carry a crew of two men on earth orbital and rendezvous missions, was unmanned for the flight reported herein (GT-1). There were no complete Gemini flight systems on board; however, the C-band transponder and telemetry transmitters were Gemini flight subsystems. Dummy equipment, having a mass and moment of inertia equal to flight system equipment, was installed in the spacecraft. The Spacecraft was instrumented to obtain data on spacecraft heating, structural loading, vibration, sound pressure levels, and temperature and pressure during the launch phase.

Flight and Integrated Vehicle Testing: Laying the Groundwork for the Next Generation of Space Exploration Launch Vehicles

NASA Technical Reports Server (NTRS)

Taylor, J. L.; Cockrell, C. E.

2009-01-01

Integrated vehicle testing will be critical to ensuring proper vehicle integration of the Ares I crew launch vehicle and Ares V cargo launch vehicle. The Ares Projects, based at Marshall Space Flight Center in Alabama, created the Flight and Integrated Test Office (FITO) as a separate team to ensure that testing is an integral part of the vehicle development process. As its name indicates, FITO is responsible for managing flight testing for the Ares vehicles. FITO personnel are well on the way toward assembling and flying the first flight test vehicle of Ares I, the Ares I-X. This suborbital development flight will evaluate the performance of Ares I from liftoff to first stage separation, testing flight control algorithms, vehicle roll control, separation and recovery systems, and ground operations. Ares I-X is now scheduled to fly in summer 2009. The follow-on flight, Ares I-Y, will test a full five-segment first stage booster and will include cryogenic propellants in the upper stage, an upper stage engine simulator, and an active launch abort system. The following flight, Orion 1, will be the first flight of an active upper stage and upper stage engine, as well as the first uncrewed flight of an Orion spacecraft into orbit. The Ares Projects are using an incremental buildup of flight capabilities prior to the first operational crewed flight of Ares I and the Orion crew exploration vehicle in 2015. In addition to flight testing, the FITO team will be responsible for conducting hardware, software, and ground vibration tests of the integrated launch vehicle. These efforts will include verifying hardware, software, and ground handling interfaces. Through flight and integrated testing, the Ares Projects will identify and mitigate risks early as the United States prepares to take its next giant leaps to the Moon and beyond.

Model-based software engineering for an optical navigation system for spacecraft

NASA Astrophysics Data System (ADS)

Franz, T.; Lüdtke, D.; Maibaum, O.; Gerndt, A.

2017-09-01

The project Autonomous Terrain-based Optical Navigation (ATON) at the German Aerospace Center (DLR) is developing an optical navigation system for future landing missions on celestial bodies such as the moon or asteroids. Image data obtained by optical sensors can be used for autonomous determination of the spacecraft's position and attitude. Camera-in-the-loop experiments in the Testbed for Robotic Optical Navigation (TRON) laboratory and flight campaigns with unmanned aerial vehicle (UAV) are performed to gather flight data for further development and to test the system in a closed-loop scenario. The software modules are executed in the C++ Tasking Framework that provides the means to concurrently run the modules in separated tasks, send messages between tasks, and schedule task execution based on events. Since the project is developed in collaboration with several institutes in different domains at DLR, clearly defined and well-documented interfaces are necessary. Preventing misconceptions caused by differences between various development philosophies and standards turned out to be challenging. After the first development cycles with manual Interface Control Documents (ICD) and manual implementation of the complex interactions between modules, we switched to a model-based approach. The ATON model covers a graphical description of the modules, their parameters and communication patterns. Type and consistency checks on this formal level help to reduce errors in the system. The model enables the generation of interfaces and unified data types as well as their documentation. Furthermore, the C++ code for the exchange of data between the modules and the scheduling of the software tasks is created automatically. With this approach, changing the data flow in the system or adding additional components (e.g., a second camera) have become trivial.

Model-based software engineering for an optical navigation system for spacecraft

NASA Astrophysics Data System (ADS)

Franz, T.; Lüdtke, D.; Maibaum, O.; Gerndt, A.

2018-06-01

The project Autonomous Terrain-based Optical Navigation (ATON) at the German Aerospace Center (DLR) is developing an optical navigation system for future landing missions on celestial bodies such as the moon or asteroids. Image data obtained by optical sensors can be used for autonomous determination of the spacecraft's position and attitude. Camera-in-the-loop experiments in the Testbed for Robotic Optical Navigation (TRON) laboratory and flight campaigns with unmanned aerial vehicle (UAV) are performed to gather flight data for further development and to test the system in a closed-loop scenario. The software modules are executed in the C++ Tasking Framework that provides the means to concurrently run the modules in separated tasks, send messages between tasks, and schedule task execution based on events. Since the project is developed in collaboration with several institutes in different domains at DLR, clearly defined and well-documented interfaces are necessary. Preventing misconceptions caused by differences between various development philosophies and standards turned out to be challenging. After the first development cycles with manual Interface Control Documents (ICD) and manual implementation of the complex interactions between modules, we switched to a model-based approach. The ATON model covers a graphical description of the modules, their parameters and communication patterns. Type and consistency checks on this formal level help to reduce errors in the system. The model enables the generation of interfaces and unified data types as well as their documentation. Furthermore, the C++ code for the exchange of data between the modules and the scheduling of the software tasks is created automatically. With this approach, changing the data flow in the system or adding additional components (e.g., a second camera) have become trivial.

Space Shuttle Ascent Flight Design Process: Evolution and Lessons Learned

NASA Technical Reports Server (NTRS)

Picka, Bret A.; Glenn, Christopher B.

2011-01-01

The Space Shuttle Ascent Flight Design team is responsible for defining a launch to orbit trajectory profile that satisfies all programmatic mission objectives and defines the ground and onboard reconfiguration requirements for this high-speed and demanding flight phase. This design, verification and reconfiguration process ensures that all applicable mission scenarios are enveloped within integrated vehicle and spacecraft certification constraints and criteria, and includes the design of the nominal ascent profile and trajectory profiles for both uphill and ground-to-ground aborts. The team also develops a wide array of associated training, avionics flight software verification, onboard crew and operations facility products. These key ground and onboard products provide the ultimate users and operators the necessary insight and situational awareness for trajectory dynamics, performance and event sequences, abort mode boundaries and moding, flight performance and impact predictions for launch vehicle stages for use in range safety, and flight software performance. These products also provide the necessary insight to or reconfiguration of communications and tracking systems, launch collision avoidance requirements, and day of launch crew targeting and onboard guidance, navigation and flight control updates that incorporate the final vehicle configuration and environment conditions for the mission. Over the course of the Space Shuttle Program, ascent trajectory design and mission planning has evolved in order to improve program flexibility and reduce cost, while maintaining outstanding data quality. Along the way, the team has implemented innovative solutions and technologies in order to overcome significant challenges. A number of these solutions may have applicability to future human spaceflight programs.

CASIS Fact Sheet: Hardware and Facilities

NASA Technical Reports Server (NTRS)

Solomon, Michael R.; Romero, Vergel

2016-01-01

Vencore is a proven information solutions, engineering, and analytics company that helps our customers solve their most complex challenges. For more than 40 years, we have designed, developed and delivered mission-critical solutions as our customers' trusted partner. The Engineering Services Contract, or ESC, provides engineering and design services to the NASA organizations engaged in development of new technologies at the Kennedy Space Center. Vencore is the ESC prime contractor, with teammates that include Stinger Ghaffarian Technologies, Sierra Lobo, Nelson Engineering, EASi, and Craig Technologies. The Vencore team designs and develops systems and equipment to be used for the processing of space launch vehicles, spacecraft, and payloads. We perform flight systems engineering for spaceflight hardware and software; develop technologies that serve NASA's mission requirements and operations needs for the future. Our Flight Payload Support (FPS) team at Kennedy Space Center (KSC) provides engineering, development, and certification services as well as payload integration and management services to NASA and commercial customers. Our main objective is to assist principal investigators (PIs) integrate their science experiments into payload hardware for research aboard the International Space Station (ISS), commercial spacecraft, suborbital vehicles, parabolic flight aircrafts, and ground-based studies. Vencore's FPS team is AS9100 certified and a recognized implementation partner for the Center for Advancement of Science in Space (CASIS

Nickel cadmium battery operations and performance

NASA Technical Reports Server (NTRS)

Rao, Gopalakrishna; Prettyman-Lukoschek, Jill; Calvin, Richard; Berry, Thomas; Bote, Robert; Toft, Mark

1994-01-01

The Earth Radiation Budget Satellite (ERBS), Compton Gamma Ray Observatory (CGRO), Upper Atmosphere Research Satellite (UARS), and Extreme Ultraviolet Explorer (EUVE) spacecraft are operated from NASA's Goddard Space Flight Center (GSFC) in Greenbelt, Maryland. On-board power subsystems for each satellite employ NASA Standard 50 Ampere-hour (Ah) nickel-cadmium batteries in a parallel configuration. To date, these batteries have exhibited degradation over periods from several months (anomalous behavior, UARS and CGRO (MPS-1); to little if any, EUVE) to several years (old age, normal behavior, ERBS). Since the onset of degraded performance, each mission's Flight Operations Team (FOT), under the direction of their cognizant GSFC Project Personnel and Space Power Application Branch's Engineers has closely monitored the battery performance and implemented several charge control schemes in an effort to extend battery life. Various software and hardware solutions have been developed to minimize battery overcharge. Each of the four sections of this paper covers a brief overview of each mission's operational battery management and its associated spacecraft battery performance. Also included are new operational procedures developed on-orbit that may be of special interest to future mission definition and development.

iPAS: AES Flight System Technology Maturation for Human Spaceflight

NASA Technical Reports Server (NTRS)

Othon, William L.

2014-01-01

In order to realize the vision of expanding human presence in space, NASA will develop new technologies that can enable future crewed spacecraft to go far beyond Earth orbit. These technologies must be matured to the point that future project managers can accept the risk of incorporating them safely and effectively within integrated spacecraft systems, to satisfy very challenging mission requirements. The technologies must also be applied and managed within an operational context that includes both on-board crew and mission support on Earth. The Advanced Exploration Systems (AES) Program is one part of the NASA strategy to identify and develop key capabilities for human spaceflight, and mature them for future use. To support this initiative, the Integrated Power Avionics and Software (iPAS) environment has been developed that allows engineers, crew, and flight operators to mature promising technologies into applicable capabilities, and to assess the value of these capabilities within a space mission context. This paper describes the development of the integration environment to support technology maturation and risk reduction, and offers examples of technology and mission demonstrations executed to date.

KSC-98pc1331

NASA Image and Video Library

1998-10-12

KENNEDY SPACE CENTER, FLA. -- On Launch Pad 17A at Cape Canaveral Air Station, Deep Space 1 is lowered in the white room for installation on a Boeing Delta 7326 rocket . The spacecraft is targeted for launch on Oct. 25. Deep Space 1 is the first flight in NASA's New Millennium Program, and is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

The Mercury-Redstone Program

NASA Technical Reports Server (NTRS)

Hammack, Jerome B.; Heberlig, Jack C.

1961-01-01

The Mercury-Redstone program is reviewed as to its intended mission and its main results. The progressive results of unmanned, animal, and manned flights of this over-all Project Mercury ballistic training program are presented. A technical description of the major spacecraft systems is presented with some analysis of flight performance. Performance of the spacecraft with and without pilot input is discussed. The influence of the astronaut as an operating link in the over-all system is presented, and relative difficulties of manned versus unmanned flight are briefly commented upon. The program provided information on man as an integral part of a space flight system, demonstrating that man can assume a primary role in space as he does in other realms of flight. The Mercury-Redstone program demonstrated that the Mercury spacecraft was capable of manned space flight, and succeeded in partially qualifying the spacecraft for orbital flight.

KSC-98pc1194

NASA Image and Video Library

1998-10-01

Workers at this clean room facility, Cape Canaveral Air Station, prepare to lift the protective can that covered Deep Space 1 during transportation from KSC. The spacecraft will undergo spin testing at the site. Deep Space 1, the first flight in NASA's New Millennium Program, is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non-chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. The spacecraft will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches

Autonomous Aerobraking Development Software: Phase One Performance Analysis at Mars, Venus, and Titan

NASA Technical Reports Server (NTRS)

Maddock, Robert W.; Bowes, Angela; Powell, Richard W.; Prince, Jill L. H.; Cianciolo, Alicia Dwyer

2012-01-01

When entering orbit about a planet or moon with an appreciable atmosphere, instead of using only the propulsion system to insert the spacecraft into its desired orbit, aerodynamic drag can be used after the initial orbit insertion to further decelerate the spacecraft. Several past NASA missions have used this aerobraking technique to reduce the fuel required to deliver a spacecraft into a desired orbit. Aerobraking was first demonstrated at Venus with Magellan in 1993 and then was used to achieve the science orbit of three Mars orbiters: Mars Global Surveyor in 1997, Mars Odyssey in 2001, and Mars Reconnaissance Orbiter in 2006. Although aerobraking itself reduces the propellant required to reach a final low period orbit, it does so at the expense of additional mission time to accommodate the aerobraking operations phase (typically 3-6 months), a large mission operations staff, and significant Deep Space Network (DSN) coverage. By automating ground based tasks and analyses associated with aerobraking and moving these onboard the spacecraft, a flight project could save millions of dollars in operations staffing and DSN costs (Ref. 1).

Error Analysis System for Spacecraft Navigation Using the Global Positioning System (GPS)

NASA Technical Reports Server (NTRS)

Truong, S. H.; Hart, R. C.; Hartman, K. R.; Tomcsik, T. L.; Searl, J. E.; Bernstein, A.

1997-01-01

The Flight Dynamics Division (FDD) at the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) is currently developing improved space-navigation filtering algorithms to use the Global Positioning System (GPS) for autonomous real-time onboard orbit determination. In connection with a GPS technology demonstration on the Small Satellite Technology Initiative (SSTI)/Lewis spacecraft, FDD analysts and programmers have teamed with the GSFC Guidance, Navigation, and Control Branch to develop the GPS Enhanced Orbit Determination Experiment (GEODE) system. The GEODE system consists of a Kalman filter operating as a navigation tool for estimating the position, velocity, and additional states required to accurately navigate the orbiting Lewis spacecraft by using astrodynamic modeling and GPS measurements from the receiver. A parallel effort at the FDD is the development of a GPS Error Analysis System (GEAS) that will be used to analyze and improve navigation filtering algorithms during development phases and during in-flight calibration. For GEAS, the Kalman filter theory is extended to estimate the errors in position, velocity, and other error states of interest. The estimation of errors in physical variables at regular intervals will allow the time, cause, and effect of navigation system weaknesses to be identified. In addition, by modeling a sufficient set of navigation system errors, a system failure that causes an observed error anomaly can be traced and accounted for. The GEAS software is formulated using Object Oriented Design (OOD) techniques implemented in the C++ programming language on a Sun SPARC workstation. The Phase 1 of this effort is the development of a basic system to be used to evaluate navigation algorithms implemented in the GEODE system. This paper presents the GEAS mathematical methodology, systems and operations concepts, and software design and implementation. Results from the use of the basic system to evaluate navigation algorithms implemented on GEODE are also discussed. In addition, recommendations for generalization of GEAS functions and for new techniques to optimize the accuracy and control of the GPS autonomous onboard navigation are presented.

Increasing Flight Software Reuse with OpenSatKit

NASA Technical Reports Server (NTRS)

McComas, David C.

2018-01-01

In January 2015 the NASA Goddard Space Flight Center (GSFC) released the Core Flight System (cFS) as open source under the NASA Open Source Agreement (NOSA) license. The cFS is based on flight software (FSW) developed for 12 spacecraft spanning nearly two decades of effort and it can provide about a third of the FSW functionality for a low-earth orbiting scientific spacecraft. The cFS is a FSW framework that is portable, configurable, and extendable using a product line deployment model. However, the components are maintained separately so the user must configure, integrate, and deploy them as a cohesive functional system. This can be very challenging especially for organizations such as universities building cubesats that have minimal experience developing FSW. Supporting universities was one of the primary motivators for releasing the cFS under NOSA. This paper describes the OpenSatKit that was developed to address the cFS deployment challenges and to serve as a cFS training platform for new users. It provides a fully functional out-of-the box software system that includes NASA's cFS, Ball Aerospace's command and control system COSMOS, and a NASA dynamic simulator called 42. The kit is freely available since all of the components have been released as open source. The kit runs on a Linux platform, includes 8 cFS applications, several kit-specific applications, and built in demos illustrating how to use key application features. It also includes the software necessary to port the cFS to a Raspberry Pi and instructions for configuring COSMOS to communicate with the target. All of the demos and test scripts can be rerun unchanged with the cFS running on the Raspberry Pi. The cFS uses a 3-tiered layered architecture including a platform abstraction layer, a Core Flight Executive (cFE) middle layer, and an application layer. Similar to smart phones, the cFS application layer is the key architectural feature for users to extend the FSW functionality to meet their mission-specific requirements. The platform abstraction layer and the cFE layers go a step further than smart phones by providing a platform-agnostic Application Programmer Interface (API) that allows applications to run unchanged on different platforms. OpenSatKit can serve two significant architectural roles that will further help the adoption of the cFS and help create a community of users that can share assets. First, the kit is being enhanced to automate the integration of applications with the goal of creating a virtual cFS "App Store".. Second, a platform certification test suite can be developed that would allow users to verify the port of the cFS to a new platform. This paper will describe the current state of these efforts and future plans.

Aquarius' Object-Oriented, Plug and Play Component-Based Flight Software

NASA Technical Reports Server (NTRS)

Murray, Alexander; Shahabuddin, Mohammad

2013-01-01

The Aquarius mission involves a combined radiometer and radar instrument in low-Earth orbit, providing monthly global maps of Sea Surface Salinity. Operating successfully in orbit since June, 2011, the spacecraft bus was furnished by the Argentine space agency, Comision Nacional de Actividades Espaciales (CONAE). The instrument, built jointly by NASA's Caltech/JPL and Goddard Space Flight Center, has been successfully producing expectation-exceeding data since it was powered on in August of 2011. In addition to the radiometer and scatterometer, the instrument contains an command & data-handling subsystem with a computer and flight software (FSW) that is responsible for managing the instrument, its operation, and its data. Aquarius' FSW is conceived and architected as a Component-based system, in which the running software consists of a set of Components, each playing a distinctive role in the subsystem, instantiated and connected together at runtime. Component architectures feature a well-defined set of interfaces between the Components, visible and analyzable at the architectural level (see [1]). As we will describe, this kind of an architecture offers significant advantages over more traditional FSW architectures, which often feature a monolithic runtime structure. Component-based software is enabled by Object-Oriented (OO) techniques and languages, the use of which again is not typical in space mission FSW. We will argue in this paper that the use of OO design methods and tools (especially the Unified Modeling Language), as well as the judicious usage of C++, are very well suited to FSW applications, and we will present Aquarius FSW, describing our methods, processes, and design, as a successful case in point.

TDRSS Onboard Navigation System (TONS) experiment for the Explorer Platform (EP)

NASA Astrophysics Data System (ADS)

Gramling, C. J.; Hornstein, R. S.; Long, A. C.; Samii, M. V.; Elrod, B. D.

A TDRSS Onboard Navigation System (TONS) is currently being developed by NASA to provide a high-accuracy autonomous spacecraft navigation capability for users of TDRSS and its successor, the Advanced TDRSS. A TONS experiment will be performed in conjunction with the Explorer Platform (EP)/EUV Explorer mission to flight-qualify TONS Block I. This paper presents an overview of TDRSS on-board navigation goals and plans and the technical objectives of the TONS experiment. The operations concept of the experiment is described, including the characteristics of the ultrastable oscillator, the Doppler extractor, the signal-acquisition process, the TONS ground-support system, and the navigation flight software. A description of the on-board navigation algorithms and the rationale for their selection is also presented.

Launch and Commissioning of the Deep Space Climate Observatory

NASA Technical Reports Server (NTRS)

Frey, Nicholas P.; Davis, Edward P.

2016-01-01

The Deep Space Climate Observatory (DSCOVR), formerly known as Triana, successfully launched on February 11th, 2015. To date, each of the five space-craft attitude control system (ACS) modes have been operating as expected and meeting all guidance, navigation, and control (GN&C) requirements, although since launch, several anomalies were encountered. While unplanned, these anomalies have proven to be invaluable in developing a deeper understanding of the ACS, and drove the design of three alterations to the ACS task of the flight software (FSW). An overview of the GN&C subsystem hardware, including re-furbishment, and ACS architecture are introduced, followed by a chronological discussion of key events, flight performance, as well as anomalies encountered by the GN&C team.

Enhancing the Cassini Mission Through FP Applications After Launch

NASA Technical Reports Server (NTRS)

Morgan, Paula S.

2016-01-01

Although rigorous pre-emptive measures are taken to preclude failures and anomalous conditions from occurring in JPL spacecraft missions prior to launch, unforeseeable problems can still surface after liftoff. In the case of the Cassini/Huygens Mission-to-Saturn spacecraft, several problems were observed post-launch: 1) immediately after takeoff, the collected engineering/science data stored on the Solid State Recorders (SSR) contained a significantly higher number of corrupted bits than was expected (considerably over spec) due to human error in the memory mapping of these devices, 2) numerous Solid State Power Switches (SSPS) sporadically tripped off throughout the mission due to cosmic ray bombardment from the unique space environment, and 3) false assumptions in the pressure regulator design in combination with missing heritage test data led to inaccurate design conclusions, causing the issuance of two waivers for the regulator to close properly (a potentially mission catastrophic single-point failure which occurred 24 days after launch) - amongst other problems. For Cassini, some of these anomalies led to arduous work-arounds or required continuous monitoring of telemetry variables by the ground-based Spacecraft Operations Flight Support (SOFS) team in order to detect and fix fault occurrences as they happened. Fortunately, sufficient funding and schedule margin allowed several Fault Protection (FP) solutions to be implemented into post-launch Flight Software (FSW) uploads to help resolve these issues autonomously, reducing SOFS ground support efforts while improving anomaly recovery time in order to preserve maximum science capture. This paper details the FP applications used to resolve the above issues as well as to optimize solutions for several other problems experienced by the Cassini spacecraft during its fight, in order to enhance the spacecraft's overall mission success throughout the 18 years of its 20 year expedition to and within the Saturnian system.

The first stage of Boeing's Delta 7326 arrives at Pad 17A, CCAS, in preparation for the Deep Space 1

NASA Technical Reports Server (NTRS)

1998-01-01

The first stage of Boeing's Delta 7326 rocket, which will be used to launch the Deep Space 1 spacecraft, arrives at Pad 17A at Cape Canaveral Air Station. Targeted for launch on Oct. 15, 1998, this first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

Deep Space 1 arrives at KSC and processing begins in the PHSF

NASA Technical Reports Server (NTRS)

1998-01-01

Wearing special protective suits, workers remove the protective covering from NASA's Deep Space 1 spacecraft in the Payload Hazardous Servicing Facility at KSC to prepare it for prelaunch processing. Targeted for launch on a Boeing Delta 7326 rocket on Oct. 15, 1998, the first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

Goddard Space Flight Center solar array missions, requirements and directions

NASA Technical Reports Server (NTRS)

Gaddy, Edward; Day, John

1994-01-01

The Goddard Space Flight Center (GSFC) develops and operates a wide variety of spacecraft for conducting NASA's communications, space science, and earth science missions. Some are 'in house' spacecraft for which the GSFC builds the spacecraft and performs all solar array design, analysis, integration, and test. Others are 'out of house' spacecraft for which an aerospace contractor builds the spacecraft and develops the solar array under direction from GSFC. The experience of developing flight solar arrays for numerous GSFC 'in house' and 'out of house' spacecraft has resulted in an understanding of solar array requirements for many different applications. This presentation will review those solar array requirements that are common to most GSFC spacecraft. Solar array technologies will be discussed that are currently under development and that could be useful to future GSFC spacecraft.

Collaboration Between NASA Centers of Excellence on Autonomous System Software Development

NASA Technical Reports Server (NTRS)

Goodrich, Charles H.; Larson, William E.; Delgado, H. (Technical Monitor)

2001-01-01

Software for space systems flight operations has its roots in the early days of the space program when computer systems were incapable of supporting highly complex and flexible control logic. Control systems relied on fast data acquisition and supervisory control from a roomful of systems engineers on the ground. Even though computer hardware and software has become many orders of magnitude more capable, space systems have largely adhered to this original paradigm In an effort to break this mold, Kennedy Space Center (KSC) has invested in the development of model-based diagnosis and control applications for ten years having broad experience in both ground and spacecraft systems and software. KSC has now partnered with Ames Research Center (ARC), NASA's Center of Excellence in Information Technology, to create a new paradigm for the control of dynamic space systems. ARC has developed model-based diagnosis and intelligent planning software that enables spacecraft to handle most routine problems automatically and allocate resources in a flexible way to realize mission objectives. ARC demonstrated the utility of onboard diagnosis and planning with an experiment aboard Deep Space I in 1999. This paper highlights the software control system collaboration between KSC and ARC. KSC has developed a Mars In-situ Resource Utilization testbed based on the Reverse Water Gas Shift (RWGS) reaction. This plant, built in KSC's Applied Chemistry Laboratory, is capable of producing the large amount of Oxygen that would be needed to support a Human Mars Mission. KSC and ARC are cooperating to develop an autonomous, fault-tolerant control system for RWGS to meet the need for autonomy on deep space missions. The paper will also describe how the new system software paradigm will be applied to Vehicle Health Monitoring, tested on the new X vehicles and integrated into future launch processing systems.

A Deep Space Orbit Determination Software: Overview and Event Prediction Capability

NASA Astrophysics Data System (ADS)

Kim, Youngkwang; Park, Sang-Young; Lee, Eunji; Kim, Minsik

2017-06-01

This paper presents an overview of deep space orbit determination software (DSODS), as well as validation and verification results on its event prediction capabilities. DSODS was developed in the MATLAB object-oriented programming environment to support the Korea Pathfinder Lunar Orbiter (KPLO) mission. DSODS has three major capabilities: celestial event prediction for spacecraft, orbit determination with deep space network (DSN) tracking data, and DSN tracking data simulation. To achieve its functionality requirements, DSODS consists of four modules: orbit propagation (OP), event prediction (EP), data simulation (DS), and orbit determination (OD) modules. This paper explains the highest-level data flows between modules in event prediction, orbit determination, and tracking data simulation processes. Furthermore, to address the event prediction capability of DSODS, this paper introduces OP and EP modules. The role of the OP module is to handle time and coordinate system conversions, to propagate spacecraft trajectories, and to handle the ephemerides of spacecraft and celestial bodies. Currently, the OP module utilizes the General Mission Analysis Tool (GMAT) as a third-party software component for highfidelity deep space propagation, as well as time and coordinate system conversions. The role of the EP module is to predict celestial events, including eclipses, and ground station visibilities, and this paper presents the functionality requirements of the EP module. The validation and verification results show that, for most cases, event prediction errors were less than 10 millisec when compared with flight proven mission analysis tools such as GMAT and Systems Tool Kit (STK). Thus, we conclude that DSODS is capable of predicting events for the KPLO in real mission applications.

A Hardware-in-the-Loop Testbed for Spacecraft Formation Flying Applications

NASA Technical Reports Server (NTRS)

Leitner, Jesse; Bauer, Frank H. (Technical Monitor)

2001-01-01

The Formation Flying Test Bed (FFTB) at NASA Goddard Space Flight Center (GSFC) is being developed as a modular, hybrid dynamic simulation facility employed for end-to-end guidance, navigation, and control (GN&C) analysis and design for formation flying clusters and constellations of satellites. The FFTB will support critical hardware and software technology development to enable current and future missions for NASA, other government agencies, and external customers for a wide range of missions, particularly those involving distributed spacecraft operations. The initial capabilities of the FFTB are based upon an integration of high fidelity hardware and software simulation, emulation, and test platforms developed at GSFC in recent years; including a high-fidelity GPS simulator which has been a fundamental component of the Guidance, Navigation, and Control Center's GPS Test Facility. The FFTB will be continuously evolving over the next several years from a too[ with initial capabilities in GPS navigation hardware/software- in-the- loop analysis and closed loop GPS-based orbit control algorithm assessment to one with cross-link communications and relative navigation analysis and simulation capability. Eventually the FFT13 will provide full capability to support all aspects of multi-sensor, absolute and relative position determination and control, in all (attitude and orbit) degrees of freedom, as well as information management for satellite clusters and constellations. In this paper we focus on the architecture for the FFT13 as a general GN&C analysis environment for the spacecraft formation flying community inside and outside of NASA GSFC and we briefly reference some current and future activities which will drive the requirements and development.

Rendezvous Integration Complexities of NASA Human Flight Vehicles

NASA Technical Reports Server (NTRS)

Brazzel, Jack P.; Goodman, John L.

2009-01-01

Propellant-optimal trajectories, relative sensors and navigation, and docking/capture mechanisms are rendezvous disciplines that receive much attention in the technical literature. However, other areas must be considered. These include absolute navigation, maneuver targeting, attitude control, power generation, software development and verification, redundancy management, thermal control, avionics integration, robotics, communications, lighting, human factors, crew timeline, procedure development, orbital debris risk mitigation, structures, plume impingement, logistics, and in some cases extravehicular activity. While current and future spaceflight programs will introduce new technologies and operations concepts, the complexity of integrating multiple systems on multiple spacecraft will remain. The systems integration task may become more difficult as increasingly complex software is used to meet current and future automation, autonomy, and robotic operation requirements.

Characterization of a Prototype Radio Frequency Space Environment Path Emulator for Evaluating Spacecraft Ranging Hardware

NASA Technical Reports Server (NTRS)

Mitchell, Jason W.; Baldwin, Philip J.; Kurichh, Rishi; Naasz, Bo J.; Luquette, Richard J.

2007-01-01

The Formation Flying Testbed (FFTB) at the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) provides a hardware-in-the-loop test environment for formation navigation and control. The facility is evolving as a modular, hybrid, dynamic simulation facility for end-to-end guidance, navigation and control (GN&C) design and analysis of formation flying spacecraft. The core capabilities of the FFTB, as a platform for testing critical hardware and software algorithms in-the-loop, have expanded to include S-band Radio Frequency (RF) modems for interspacecraft communication and ranging. To enable realistic simulations that require RF ranging sensors for relative navigation, a mechanism is needed to buffer the RF signals exchanged between spacecraft that accurately emulates the dynamic environment through which the RF signals travel, including the effects of the medium, moving platforms, and radiated power. The Path Emulator for Radio Frequency Signals (PERFS), currently under development at NASA GSFC, provides this capability. The function and performance of a prototype device are presented.

Streamlining Collaborative Planning in Spacecraft Mission Architectures

NASA Technical Reports Server (NTRS)

Misra, Dhariti; Bopf, Michel; Fishman, Mark; Jones, Jeremy; Kerbel, Uri; Pell, Vince

2000-01-01

During the past two decades, the planning and scheduling community has substantially increased the capability and efficiency of individual planning and scheduling systems. Relatively recently, research work to streamline collaboration between planning systems is gaining attention. Spacecraft missions stand to benefit substantially from this work as they require the coordination of multiple planning organizations and planning systems. Up to the present time this coordination has demanded a great deal of human intervention and/or extensive custom software development efforts. This problem will become acute with increased requirements for cross-mission plan coordination and multi -spacecraft mission planning. The Advanced Architectures and Automation Branch of NASA's Goddard Space Flight Center is taking innovative steps to define collaborative planning architectures, and to identify coordinated planning tools for Cross-Mission Campaigns. Prototypes are being developed to validate these architectures and assess the usefulness of the coordination tools by the planning community. This presentation will focus on one such planning coordination too], named Visual Observation Layout Tool (VOLT), which is currently being developed to streamline the coordination between astronomical missions

Deep Space 1 Using its Ion Engine (Artist's Concept)

NASA Technical Reports Server (NTRS)

2003-01-01

NASA's New Millennium Deep Space 1 spacecraft approaching the comet 19P/Borrelly. With its primary mission to serve as a technology demonstrator--testing ion propulsion and 11 other advanced technologies--successfully completed in September 1999, Deep Space 1 is now headed for a risky, exciting rendezvous with Comet Borrelly. NASA extended the mission, taking advantage of the ion propulsion and other systems to target the daring encounter with the comet in September 2001. Once a sci-fi dream, the ion propulsion engine has powered the spacecraft for over 12,000 hours. Another onboard experiment includes software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The first flight in NASA's New Millennium Program, Deep Space 1 was launched October 24, 1998 aboard a Boeing Delta 7326 rocket from Cape Canaveral Air Station, FL. Deep Space 1 successfully completed and exceeded its mission objectives in July 1999 and flew by a near-Earth asteroid, Braille (1992 KD), in September 1999.

A Technique for the Assessment of Flight Operability Characteristics of Human Rated Spacecraft

NASA Technical Reports Server (NTRS)

Crocker, Alan

2010-01-01

In support of new human rated spacecraft development programs, the Mission Operations Directorate at NASA Johnson Space Center has implemented a formal method for the assessment of spacecraft operability. This "Spacecraft Flight Operability Assessment Scale" defines six key themes of flight operability, with guiding principles and goals stated for each factor. A standardized rating technique provides feedback that is useful to the operations, design and program management communities. Applicability of this concept across the program structure and life cycle is addressed. Examples of operationally desirable and undesirable spacecraft design characteristics are provided, as is a sample of the assessment scale product.

Simple Sensitivity Analysis for Orion Guidance Navigation and Control

NASA Technical Reports Server (NTRS)

Pressburger, Tom; Hoelscher, Brian; Martin, Rodney; Sricharan, Kumar

2013-01-01

The performance of Orion flight software, especially its GNC software, is being analyzed by running Monte Carlo simulations of Orion spacecraft flights. The simulated performance is analyzed for conformance with flight requirements, expressed as performance constraints. Flight requirements include guidance (e.g. touchdown distance from target) and control (e.g., control saturation) as well as performance (e.g., heat load constraints). The Monte Carlo simulations disperse hundreds of simulation input variables, for everything from mass properties to date of launch. We describe in this paper a sensitivity analysis tool ("Critical Factors Tool" or CFT) developed to find the input variables or pairs of variables which by themselves significantly influence satisfaction of requirements or significantly affect key performance metrics (e.g., touchdown distance from target). Knowing these factors can inform robustness analysis, can inform where engineering resources are most needed, and could even affect operations. The contributions of this paper include the introduction of novel sensitivity measures, such as estimating success probability, and a technique for determining whether pairs of factors are interacting dependently or independently. The tool found that input variables such as moments, mass, thrust dispersions, and date of launch were found to be significant factors for success of various requirements. Examples are shown in this paper as well as a summary and physics discussion of EFT-1 driving factors that the tool found.

NASA Software Cost Estimation Model: An Analogy Based Estimation Model

NASA Technical Reports Server (NTRS)

Hihn, Jairus; Juster, Leora; Menzies, Tim; Mathew, George; Johnson, James

2015-01-01

The cost estimation of software development activities is increasingly critical for large scale integrated projects such as those at DOD and NASA especially as the software systems become larger and more complex. As an example MSL (Mars Scientific Laboratory) developed at the Jet Propulsion Laboratory launched with over 2 million lines of code making it the largest robotic spacecraft ever flown (Based on the size of the software). Software development activities are also notorious for their cost growth, with NASA flight software averaging over 50% cost growth. All across the agency, estimators and analysts are increasingly being tasked to develop reliable cost estimates in support of program planning and execution. While there has been extensive work on improving parametric methods there is very little focus on the use of models based on analogy and clustering algorithms. In this paper we summarize our findings on effort/cost model estimation and model development based on ten years of software effort estimation research using data mining and machine learning methods to develop estimation models based on analogy and clustering. The NASA Software Cost Model performance is evaluated by comparing it to COCOMO II, linear regression, and K-­ nearest neighbor prediction model performance on the same data set.

A Study of Learning Curve Impact on Three Identical Small Spacecraft

NASA Technical Reports Server (NTRS)

Chen, Guangming; McLennan, Douglas D.

2003-01-01

With an eye to the future strategic needs of NASA, the New Millennium Program is funding the Space Technology 5 (ST-5) project to address the future needs in the area of small satellites in constellation missions. The ST-5 project, being developed at Goddard Space Flight Center, involves the development and simultaneous launch of three small, 20-kilogram-class spacecraft. ST-5 is only a test drive and future NASA science missions may call for fleets of spacecraft containing tens of smart and capable satellites in an intelligent constellation. The objective of ST-5 project is to develop three such pioneering small spacecraft for flight validation of several critical new technologies. The ST-5 project team at Goddard Space Flight Center has completed the spacecraft design, is now building and testing the three flight units. The launch readiness date (LRD) is in December 2005. A critical part of ST-5 mission is to prove that it is possible to build these small but capable spacecraft with recurring cost low enough to make future NASA s multi- spacecraft constellation missions viable from a cost standpoint.

Leadership Development Program Final Project

NASA Technical Reports Server (NTRS)

Parrish, Teresa C.

2016-01-01

TOSC is NASA's prime contractor tasked to successfully assemble, test, and launch the EM1 spacecraft. TOSC success is highly dependent on design products from the other NASA Programs manufacturing and delivering the flight hardware; Space Launch System(SLS) and Multi-Purpose Crew Vehicle(MPCV). Design products directly feed into TOSC's: Procedures, Personnel training, Hardware assembly, Software development, Integrated vehicle test and checkout, Launch. TOSC senior management recognized a significant schedule risk as these products are still being developed by the other two (2) programs; SVE and ACE positions were created.

NASA Goddard Space Flight Center Robotic Processing System Program Automation Systems, volume 2

NASA Technical Reports Server (NTRS)

Dobbs, M. E.

1991-01-01

Topics related to robot operated materials processing in space (RoMPS) are presented in view graph form. Some of the areas covered include: (1) mission requirements; (2) automation management system; (3) Space Transportation System (STS) Hitchhicker Payload; (4) Spacecraft Command Language (SCL) scripts; (5) SCL software components; (6) RoMPS EasyLab Command & Variable summary for rack stations and annealer module; (7) support electronics assembly; (8) SCL uplink packet definition; (9) SC-4 EasyLab System Memory Map; (10) Servo Axis Control Logic Suppliers; and (11) annealing oven control subsystem.

Model Checking Verification and Validation at JPL and the NASA Fairmont IV and V Facility

NASA Technical Reports Server (NTRS)

Schneider, Frank; Easterbrook, Steve; Callahan, Jack; Montgomery, Todd

1999-01-01

We show how a technology transfer effort was carried out. The successful use of model checking on a pilot JPL flight project demonstrates the usefulness and the efficacy of the approach. The pilot project was used to model a complex spacecraft controller. Software design and implementation validation were carried out successfully. To suggest future applications we also show how the implementation validation step can be automated. The effort was followed by the formal introduction of the modeling technique as a part of the JPL Quality Assurance process.

UARS in-flight jitter study for EOS

NASA Technical Reports Server (NTRS)

Molnar, John; Garnek, Mike

1993-01-01

Response data collected from gyroscopes on board the Upper Atmosphere Research Satellite (UARS) provided a unique opportunity to analyze actual flight pointing jitter data. Flight modal frequencies and damping values are derived from the measured data using an Eigensystem Realization Algorithm (ERA). Flight frequencies at various solar array positions are compared to analytical predictions obtained with a Finite Element Model. The solar array modal frequencies change with position due to the modes acting about different spacecraft inertial axes. Higher order modes were difficult to identify due to the limited instrumentation. Future flight jitter studies on other spacecraft would be significantly aided by additional instrumentation. Spacecraft jitter due to continuous disturbance sources such as the 1.6 meter scanning microwave antenna, the solar array drive, and reaction wheels is presented. The solar array drive disturbance dominates the spacecraft response during normal operation.

The Software Design for the Wide-Field Infrared Explorer Attitude Control System

NASA Technical Reports Server (NTRS)

Anderson, Mark O.; Barnes, Kenneth C.; Melhorn, Charles M.; Phillips, Tom

1998-01-01

The Wide-Field Infrared Explorer (WIRE), currently scheduled for launch in September 1998, is the fifth of five spacecraft in the NASA/Goddard Small Explorer (SMEX) series. This paper presents the design of WIRE's Attitude Control System flight software (ACS FSW). WIRE is a momentum-biased, three-axis stabilized stellar pointer which provides high-accuracy pointing and autonomous acquisition for eight to ten stellar targets per orbit. WIRE's short mission life and limited cryogen supply motivate requirements for Sun and Earth avoidance constraints which are designed to prevent catastrophic instrument damage and to minimize the heat load on the cryostat. The FSW implements autonomous fault detection and handling (FDH) to enforce these instrument constraints and to perform several other checks which insure the safety of the spacecraft. The ACS FSW implements modules for sensor data processing, attitude determination, attitude control, guide star acquisition, actuator command generation, command/telemetry processing, and FDH. These software components are integrated with a hierarchical control mode managing module that dictates which software components are currently active. The lowest mode in the hierarchy is the 'safest' one, in the sense that it utilizes a minimal complement of sensors and actuators to keep the spacecraft in a stable configuration (power and pointing constraints are maintained). As higher modes in the hierarchy are achieved, the various software functions are activated by the mode manager, and an increasing level of attitude control accuracy is provided. If FDH detects a constraint violation or other anomaly, it triggers a safing transition to a lower control mode. The WIRE ACS FSW satisfies all target acquisition and pointing accuracy requirements, enforces all pointing constraints, provides the ground with a simple means for reconfiguring the system via table load, and meets all the demands of its real-time embedded environment (16 MHz Intel 80386 processor with 80387 coprocessor running under the VRTX operating system). The mode manager organizes and controls all the software modules used to accomplish these goals, and in particular, the FDH module is tightly coupled with the mode manager.

Spacecraft Design Thermal Control Subsystem

NASA Technical Reports Server (NTRS)

Miyake, Robert N.

2003-01-01

This slide presentation reviews the functions of the thermal control subsystem engineers in the design of spacecraft. The goal of the thermal control subsystem that will be used in a spacecraft is to maintain the temperature of all spacecraft components, subsystems, and all the flight systems within specified limits for all flight modes from launch to the end of the mission. For most thermal control subsystems the mass, power and control and sensing systems must be kept below 10% of the total flight system resources. This means that the thermal control engineer is involved in all other flight systems designs. The two concepts of thermal control, passive and active are reviewed and the use of thermal modeling tools are explained. The testing of the thermal control is also reviewed.

Autonomous Navigation With Ground Station One-Way Forward-Link Doppler Data

NASA Technical Reports Server (NTRS)

Horstkamp, G. M.; Niklewski, D. J.; Gramling, C. J.

1996-01-01

The National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) has spent several years developing operational onboard navigation systems (ONS's) to provide real time autonomous, highly accurate navigation products for spacecraft using NASA's space and ground communication systems. The highly successful Tracking and Data Relay Satellite (TDRSS) ONS (TONS) experiment on the Explorer Platform/Extreme Ultraviolet (EP/EUV) spacecraft, launched on June 7, 1992, flight demonstrated the ONS for high accuracy navigation using TDRSS forward link communication services. In late 1994, a similar ONS experiment was performed using EP/EUV flight hardware (the ultrastable oscillator and Doppler extractor card in one of the TDRSS transponders) and ground system software to demonstrate the feasibility of using an ONS with ground station forward link communication services. This paper provides a detailed evaluation of ground station-based ONS performance of data collected over a 20 day period. The ground station ONS (GONS) experiment results are used to project the expected performance of an operational system. The GONS processes Doppler data derived from scheduled ground station forward link services using a sequential estimation algorithm enhanced by a sophisticated process noise model to provide onboard orbit and frequency determination. Analysis of the GONS experiment performance indicates that real time onboard position accuracies of better than 125 meters (1 sigma) are achievable with two or more 5-minute contacts per day for the EP/EUV 525 kilometer altitude, 28.5 degree inclination orbit. GONS accuracy is shown to be a function of the fidelity of the onboard propagation model, the frequency/geometry of the tracking contacts, and the quality of the tracking measurements. GONS provides a viable option for using autonomous navigation to reduce operational costs for upcoming spacecraft missions with moderate position accuracy requirements.

Human Integration Design Processes (HIDP)

NASA Technical Reports Server (NTRS)

Boyer, Jennifer

2014-01-01

The purpose of the Human Integration Design Processes (HIDP) document is to provide human-systems integration design processes, including methodologies and best practices that NASA has used to meet human systems and human rating requirements for developing crewed spacecraft. HIDP content is framed around human-centered design methodologies and processes in support of human-system integration requirements and human rating. NASA-STD-3001, Space Flight Human-System Standard, is a two-volume set of National Aeronautics and Space Administration (NASA) Agency-level standards established by the Office of the Chief Health and Medical Officer, directed at minimizing health and performance risks for flight crews in human space flight programs. Volume 1 of NASA-STD-3001, Crew Health, sets standards for fitness for duty, space flight permissible exposure limits, permissible outcome limits, levels of medical care, medical diagnosis, intervention, treatment and care, and countermeasures. Volume 2 of NASASTD- 3001, Human Factors, Habitability, and Environmental Health, focuses on human physical and cognitive capabilities and limitations and defines standards for spacecraft (including orbiters, habitats, and suits), internal environments, facilities, payloads, and related equipment, hardware, and software with which the crew interfaces during space operations. The NASA Procedural Requirements (NPR) 8705.2B, Human-Rating Requirements for Space Systems, specifies the Agency's human-rating processes, procedures, and requirements. The HIDP was written to share NASA's knowledge of processes directed toward achieving human certification of a spacecraft through implementation of human-systems integration requirements. Although the HIDP speaks directly to implementation of NASA-STD-3001 and NPR 8705.2B requirements, the human-centered design, evaluation, and design processes described in this document can be applied to any set of human-systems requirements and are independent of reference missions. The HIDP is a reference document that is intended to be used during the development of crewed space systems and operations to guide human-systems development process activities.

Mobile Computing for Aerospace Applications

NASA Technical Reports Server (NTRS)

Alena, Richard; Swietek, Gregory E. (Technical Monitor)

1994-01-01

The use of commercial computer technology in specific aerospace mission applications can reduce the cost and project cycle time required for the development of special-purpose computer systems. Additionally, the pace of technological innovation in the commercial market has made new computer capabilities available for demonstrations and flight tests. Three areas of research and development being explored by the Portable Computer Technology Project at NASA Ames Research Center are the application of commercial client/server network computing solutions to crew support and payload operations, the analysis of requirements for portable computing devices, and testing of wireless data communication links as extensions to the wired network. This paper will present computer architectural solutions to portable workstation design including the use of standard interfaces, advanced flat-panel displays and network configurations incorporating both wired and wireless transmission media. It will describe the design tradeoffs used in selecting high-performance processors and memories, interfaces for communication and peripheral control, and high resolution displays. The packaging issues for safe and reliable operation aboard spacecraft and aircraft are presented. The current status of wireless data links for portable computers is discussed from a system design perspective. An end-to-end data flow model for payload science operations from the experiment flight rack to the principal investigator is analyzed using capabilities provided by the new generation of computer products. A future flight experiment on-board the Russian MIR space station will be described in detail including system configuration and function, the characteristics of the spacecraft operating environment, the flight qualification measures needed for safety review, and the specifications of the computing devices to be used in the experiment. The software architecture chosen shall be presented. An analysis of the performance characteristics of wireless data links in the spacecraft environment will be discussed. Network performance and operation will be modeled and preliminary test results presented. A crew support application will be demonstrated in conjunction with the network metrics experiment.

Initial Performance of the Aspect System on the Chandra Observatory: Post-Facto Aspect Reconstruction

NASA Technical Reports Server (NTRS)

Aldcroft, T.; Karovska, M.; Cresitello-Dittmar, M.; Cameron, R.

2000-01-01

The aspect system of the Chandra Observatory plays a key role in realizing the full potential of Chandra's x-ray optics and detectors. To achieve the highest spatial and spectral resolution (for grating observations), an accurate post-facto time history of the spacecraft attitude and internal alignment is needed. The CXC has developed a suite of tools which process sensor data from the aspect camera assembly and gyroscopes, and produce the spacecraft aspect solution. In this poster, the design of the aspect pipeline software is briefly described, followed by details of aspect system performance during the first eight months of flight. The two key metrics of aspect performance are: image reconstruction accuracy, which measures the x-ray image blurring introduced by aspect; and celestial location, which is the accuracy of detected source positions in absolute sky coordinates.

Anomaly Trends for Missions to Mars: Mars Global Surveyor and Mars Odyssey

NASA Technical Reports Server (NTRS)

Green, Nelson W.; Hoffman, Alan R.

2008-01-01

The long term flight operations of the Mars Global Surveyor and Mars Odyssey spacecraft give us an excellent chance to examine the operations of two long lived spacecraft in orbit around Mars during overlapping time periods. This study examined the anomalies for each mission maintained for NASA at the Jet Propulsion Laboratory. By examining the anomalies each mission encountered during their multiyear missions, trends were identified related to when anomalies occurred during each mission, the types of anomalies encountered, and corrective actions taken to mitigate the effects of the anomalies. As has been discovered in previous studies the numbers of anomalies directly correlate with mission activity and show a decreasing trend with elapsed mission time. Trend analysis also identified a heavy emphasis on software as the source or solution to anomalies for both missions.

The first stage of Boeing's Delta 7326 arrives at Pad 17A, CCAS, in preparation for the Deep Space 1

NASA Technical Reports Server (NTRS)

1998-01-01

The first stage of Boeing's Delta 7326 rocket, which will be used to launch the Deep Space 1 spacecraft, is lifted into place above the surface of Pad 17A at Cape Canaveral Air Station. Targeted for launch on Oct. 15, 1998, this first flight in NASA's New Millennium Program is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

TALARIS project update: Overview of flight testing and development of a prototype planetary surface exploration hopper

NASA Astrophysics Data System (ADS)

Rossi, Christopher; Cunio, Phillip M.; Alibay, Farah; Morrow, Joe; Nothnagel, Sarah L.; Steiner, Ted; Han, Christopher J.; Lanford, Ephraim; Hoffman, Jeffrey A.

2012-12-01

The TALARIS (Terrestrial Artificial Lunar And Reduced GravIty Simulator) project is intended to test GNC (Guidance, Navigation, and Control) algorithms on a prototype planetary surface exploration hopper in a dynamic environment with simulated reduced gravity. The vehicle is being developed by the Charles Stark Draper Laboratory and Massachusetts Institute of Technology in support of efforts in the Google Lunar X-Prize contest. This paper presents progress achieved since September 2010 in vehicle development and flight testing. Upgrades to the vehicle are described, including a redesign of the power train for the gravity-offset propulsion system and a redesign of key elements of the spacecraft emulator propulsion system. The integration of flight algorithms into modular flight software is also discussed. Results are reported for restricted degree of freedom (DOF) tests used to tune GNC algorithms on the path to a full 6-DOF hover-hop flight profile. These tests include 3-DOF tests on flat surfaces restricted to horizontal motion, and 2-DOF vertical tests restricted to vertical motion and 1-DOF attitude control. The results of tests leading up to full flight operations are described, as are lessons learned and future test plans.

Morpheus Vertical Test Bed Flight Testing

NASA Technical Reports Server (NTRS)

Hart, Jeremy; Devolites, Jennifer

2014-01-01

NASA's Morpheus Project has developed and tested a prototype planetary lander capable of vertical takeoff and landing, that is designed to serve as a testbed for advanced spacecraft technologies. The lander vehicle, propelled by a LOX/Methane engine and sized to carry a 500kg payload to the lunar surface, provides a platform for bringing technologies from the laboratory into an integrated flight system at relatively low cost. Morpheus onboard software is autonomous from ignition all the way through landing, and is designed to be capable of executing a variety of flight trajectories, with onboard fault checks and automatic contingency responses. The Morpheus 1.5A vehicle performed 26 integrated vehicle test flights including hot-fire tests, tethered tests, and two attempted freeflights between April 2011 and August 2012. The final flight of Morpheus 1.5A resulted in a loss of the vehicle. In September 2012, development began on the Morpheus 1.5B vehicle, which subsequently followed a similar test campaign culminating in free-flights at a simulated planetary landscape built at Kennedy Space Center's Shuttle Landing Facility. This paper describes the integrated test campaign, including successes and setbacks, and how the system design for handling faults and failures evolved over the course of the project.

Automated Attitude Sensor Calibration: Progress and Plans

NASA Technical Reports Server (NTRS)

Sedlak, Joseph; Hashmall, Joseph

2004-01-01

This paper describes ongoing work a NASA/Goddard Space Flight Center to improve the quality of spacecraft attitude sensor calibration and reduce costs by automating parts of the calibration process. The new calibration software can autonomously preview data quality over a given time span, select a subset of the data for processing, perform the requested calibration, and output a report. This level of automation is currently being implemented for two specific applications: inertial reference unit (IRU) calibration and sensor alignment calibration. The IRU calibration utility makes use of a sequential version of the Davenport algorithm. This utility has been successfully tested with simulated and actual flight data. The alignment calibration is still in the early testing stage. Both utilities will be incorporated into the institutional attitude ground support system.

Sierra Nevada Corporation's Dream Chaser Test Article Altitude T

NASA Image and Video Library

2017-08-30

Sierra Nevada Corporation’s Dream Chaser completed an important step toward orbital flight with a successful captive carry test at NASA’s Armstrong Flight Research Center in California, located on Edwards Air Force Base. A helicopter successfully carried a Dream Chaser test article, which has the same specifications as a flight-ready spacecraft, to the same altitude and flight conditions of an upcoming free flight test. The Dream Chaser is a lifting-body, winged spacecraft that will fly back to Earth in a manner similar to NASA’s space shuttles. The successful captive carry test clears the way for a free flight test of the spacecraft later this year in which the uncrewed Dream Chaser will be released to glide on its own and land.

Evolution of the Hubble Space Telescope Safing Systems

NASA Technical Reports Server (NTRS)

Pepe, Joyce; Myslinski, Michael

2006-01-01

The Hubble Space Telescope (HST) was launched on April 24 1990, with an expected lifespan of 15 years. Central to the spacecraft design was the concept of a series of on-orbit shuttle servicing missions permitting astronauts to replace failed equipment, update the scientific instruments and keep the HST at the forefront of astronomical discoveries. One key to the success of the Hubble mission has been the robust Safing systems designed to monitor the performance of the observatory and to react to keep the spacecraft safe in the event of equipment anomaly. The spacecraft Safing System consists of a range of software tests in the primary flight computer that evaluate the performance of mission critical hardware, safe modes that are activated when the primary control mode is deemed inadequate for protecting the vehicle, and special actions that the computer can take to autonomously reconfigure critical hardware. The HST Safing System was structured to autonomously detect electrical power system, data management system, and pointing control system malfunctions and to configure the vehicle to ensure safe operation without ground intervention for up to 72 hours. There is also a dedicated safe mode computer that constantly monitors a keep-alive signal from the primary computer. If this signal stops, the safe mode computer shuts down the primary computer and takes over control of the vehicle, putting it into a safe, low-power configuration. The HST Safing system has continued to evolve as equipment has aged, as new hardware has been installed on the vehicle, and as the operation modes have matured during the mission. Along with the continual refinement of the limits used in the safing tests, several new tests have been added to the monitoring system, and new safe modes have been added to the flight software. This paper will focus on the evolution of the HST Safing System and Safing tests, and the importance of this evolution to prolonging the science operations of the telescope.

Modeling to Improve the Risk Reduction Process for Command File Errors

NASA Technical Reports Server (NTRS)

Meshkat, Leila; Bryant, Larry; Waggoner, Bruce

2013-01-01

The Jet Propulsion Laboratory has learned that even innocuous errors in the spacecraft command process can have significantly detrimental effects on a space mission. Consequently, such Command File Errors (CFE), regardless of their effect on the spacecraft, are treated as significant events for which a root cause is identified and corrected. A CFE during space mission operations is often the symptom of imbalance or inadequacy within the system that encompasses the hardware and software used for command generation as well as the human experts and processes involved in this endeavor. As we move into an era of increased collaboration with other NASA centers and commercial partners, these systems become more and more complex. Consequently, the ability to thoroughly model and analyze CFEs formally in order to reduce the risk they pose is increasingly important. In this paper, we summarize the results of applying modeling techniques previously developed to the DAWN flight project. The original models were built with the input of subject matter experts from several flight projects. We have now customized these models to address specific questions for the DAWN flight project and formulating use cases to address their unique mission needs. The goal of this effort is to enhance the project's ability to meet commanding reliability requirements for operations and to assist them in managing their Command File Errors.

In flight estimations of Cassini spacecraft inertia tensor and thruster magnitude

NASA Technical Reports Server (NTRS)

Feldman, Antonette; Lee, Allan Y.

2006-01-01

This paper describes two methods used by the Cassini Attitude Control team to determine these key parameters and how flight telemetry was used to estimate them. The method for estimating the spacecraft inertia tensor exploits the conservation of angular momentum during spacecraft slews under reaction wheel control.

Generating Safety-Critical PLC Code From a High-Level Application Software Specification

NASA Technical Reports Server (NTRS)

2008-01-01

The benefits of automatic-application code generation are widely accepted within the software engineering community. These benefits include raised abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at Kennedy Space Center recognized the need for PLC code generation while developing the new ground checkout and launch processing system, called the Launch Control System (LCS). Engineers developed a process and a prototype software tool that automatically translates a high-level representation or specification of application software into ladder logic that executes on a PLC. All the computer hardware in the LCS is planned to be commercial off the shelf (COTS), including industrial controllers or PLCs that are connected to the sensors and end items out in the field. Most of the software in LCS is also planned to be COTS, with only small adapter software modules that must be developed in order to interface between the various COTS software products. A domain-specific language (DSL) is a programming language designed to perform tasks and to solve problems in a particular domain, such as ground processing of launch vehicles. The LCS engineers created a DSL for developing test sequences of ground checkout and launch operations of future launch vehicle and spacecraft elements, and they are developing a tabular specification format that uses the DSL keywords and functions familiar to the ground and flight system users. The tabular specification format, or tabular spec, allows most ground and flight system users to document how the application software is intended to function and requires little or no software programming knowledge or experience. A small sample from a prototype tabular spec application is shown.

WMAP C&DH Software

NASA Technical Reports Server (NTRS)

Cudmore, Alan; Leath, Tim; Ferrer, Art; Miller, Todd; Walters, Mark; Savadkin, Bruce; Wu, Ji-Wei; Slegel, Steve; Stagmer, Emory

2007-01-01

The command-and-data-handling (C&DH) software of the Wilkinson Microwave Anisotropy Probe (WMAP) spacecraft functions as the sole interface between (1) the spacecraft and its instrument subsystem and (2) ground operations equipment. This software includes a command-decoding and -distribution system, a telemetry/data-handling system, and a data-storage-and-playback system. This software performs onboard processing of attitude sensor data and generates commands for attitude-control actuators in a closed-loop fashion. It also processes stored commands and monitors health and safety functions for the spacecraft and its instrument subsystems. The basic functionality of this software is the same of that of the older C&DH software of the Rossi X-Ray Timing Explorer (RXTE) spacecraft, the main difference being the addition of the attitude-control functionality. Previously, the C&DH and attitude-control computations were performed by different processors because a single RXTE processor did not have enough processing power. The WMAP spacecraft includes a more-powerful processor capable of performing both computations.

Next Generation Remote Agent Planner

NASA Technical Reports Server (NTRS)

Jonsson, Ari K.; Muscettola, Nicola; Morris, Paul H.; Rajan, Kanna

1999-01-01

In May 1999, as part of a unique technology validation experiment onboard the Deep Space One spacecraft, the Remote Agent became the first complete autonomous spacecraft control architecture to run as flight software onboard an active spacecraft. As one of the three components of the architecture, the Remote Agent Planner had the task of laying out the course of action to be taken, which included activities such as turning, thrusting, data gathering, and communicating. Building on the successful approach developed for the Remote Agent Planner, the Next Generation Remote Agent Planner is a completely redesigned and reimplemented version of the planner. The new system provides all the key capabilities of the original planner, while adding functionality, improving performance and providing a modular and extendible implementation. The goal of this ongoing project is to develop a system that provides both a basis for future applications and a framework for further research in the area of autonomous planning for spacecraft. In this article, we present an introductory overview of the Next Generation Remote Agent Planner. We present a new and simplified definition of the planning problem, describe the basics of the planning process, lay out the new system design and examine the functionality of the core reasoning module.

Motion-Based System Identification and Fault Detection and Isolation Technologies for Thruster Controlled Spacecraft

NASA Technical Reports Server (NTRS)

Wilson, Edward; Sutter, David W.; Berkovitz, Dustin; Betts, Bradley J.; Kong, Edmund; delMundo, Rommel; Lages, Christopher R.; Mah, Robert W.; Papasin, Richard

2003-01-01

By analyzing the motions of a thruster-controlled spacecraft, it is possible to provide on-line (1) thruster fault detection and isolation (FDI), and (2) vehicle mass- and thruster-property identification (ID). Technologies developed recently at NASA Ames have significantly improved the speed and accuracy of these ID and FDI capabilities, making them feasible for application to a broad class of spacecraft. Since these technologies use existing sensors, the improved system robustness and performance that comes with the thruster fault tolerance and system ID can be achieved through a software-only implementation. This contrasts with the added cost, mass, and hardware complexity commonly required by FDI. Originally developed in partnership with NASA - Johnson Space Center to provide thruster FDI capability for the X-38 during re-entry, these technologies are most recently being applied to the MIT SPHERES experimental spacecraft to fly on the International Space Station in 2004. The model-based FDI uses a maximum-likelihood calculation at its core, while the ID is based upon recursive least squares estimation. Flight test results from the SPHERES implementation, as flown aboard the NASA KC-1 35A 0-g simulator aircraft in November 2003 are presented.

KSC-98pc1195

NASA Image and Video Library

1998-10-01

Workers at this clean room facility, Cape Canaveral Air Station, maneuver the protective can that covered Deep Space 1 during transportation from KSC away from the spacecraft. Deep Space 1 will undergo spin testing at the site. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non-chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. The spacecraft will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches

KSC-98pc1209

NASA Image and Video Library

1998-10-02

KENNEDY SPACE CENTER, FLA. -- KSC workers give a final check to Deep Space 1 before starting a spin test on the spacecraft at the Defense Satellite Communications System Processing Facility (DPF), Cape Canaveral Air Station. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non-chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. The spacecraft will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches

KSC-98pc1193

NASA Image and Video Library

1998-09-30

KENNEDY SPACE CENTER, FLA. -- KSC workers lower the "can" over Deep Space 1. The can will protect the spacecraft during transport to the Defense Satellite Communications System Processing Facility (DPF), Cape Canaveral Air Station, for testing. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non-chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. The spacecraft will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches

Deep Space 1 moves to CCAS for testing

NASA Technical Reports Server (NTRS)

1998-01-01

KSC workers lower the 'can' over Deep Space 1. The can will protect the spacecraft during transport to the Defense Satellite Communications System Processing Facility (DPF), Cape Canaveral Air Station, for testing. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non- chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. The spacecraft will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches.

Deep Space 1 is prepared for spin test at CCAS

NASA Technical Reports Server (NTRS)

1998-01-01

KSC workers give a final check to Deep Space 1 before starting a spin test on the spacecraft at the Defense Satellite Communications System Processing Facility (DPF), Cape Canaveral Air Station. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non-chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. The spacecraft will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches.

The Applications of NASA Mission Technologies to the Greening of Human Impact

NASA Technical Reports Server (NTRS)

Sims, Michael H.

2009-01-01

I will give an overview talk about flight software systems, robotics technologies and modeling for energy minimization as applied to vehicles and buildings infrastructures. A dominant issue in both design and operations of robotic spacecraft is the minimization of energy use. In the design and building of spacecraft increased power is acquired only at the cost of additional mass and volumes and ultimately cost. Consequently, interplanetary spacecrafts are designed to have the minimum essential power and those designs often incorporate careful timing of all power use. Operationally, the availability of power is the most influential constraint for the use of planetary surface robots, such as the Mars Exploration Rovers. The amount of driving done, the amount of science accomplished and indeed the survivability of the spacecraft itself is determined by the power available for use. For the Mars Exploration Rovers there are four tools which are used: (1) models of the rover and it s thermal and power use (2) predictive environmental models of power input and thermal environment (3) fine grained manipulation of power use (4) optimization modeling and planning tools. In this talk I will discuss possible applications of this methodology to minimizing power use on Earth, especially in buildings.

Apollo program flight summary report: Apollo missions AS-201 through Apollo 16, revision 11

NASA Technical Reports Server (NTRS)

Holcomb, J. K.

1972-01-01

A summary of the Apollo flights from AS-201 through Apollo 16 is presented. The following subjects are discussed for each flight: (1) mission primary objectives, (2) principle objectives of the launch vehicle and spacecraft, (3) secondary objectives of the launch vehicle and spacecraft, (4) unusual features of the mission, (5) general information on the spacecraft and launch vehicle, (6) space vehicle and pre-launch data, and (7) recovery data.

Space Flight Software Development Software for Intelligent System Health Management

NASA Technical Reports Server (NTRS)

Trevino, Luis C.; Crumbley, Tim

2004-01-01

The slide presentation examines the Marshall Space Flight Center Flight Software Branch, including software development projects, mission critical space flight software development, software technical insight, advanced software development technologies, and continuous improvement in the software development processes and methods.

Development of the GPM Observatory Thermal Vacuum Test Model

NASA Technical Reports Server (NTRS)

Yang, Kan; Peabody, Hume

2012-01-01

A software-based thermal modeling process was documented for generating the thermal panel settings necessary to simulate worst-case on-orbit flight environments in an observatory-level thermal vacuum test setup. The method for creating such a thermal model involved four major steps: (1) determining the major thermal zones for test as indicated by the major dissipating components on the spacecraft, then mapping the major heat flows between these components; (2) finding the flight equivalent sink temperatures for these test thermal zones; (3) determining the thermal test ground support equipment (GSE) design and initial thermal panel settings based on the equivalent sink temperatures; and (4) adjusting the panel settings in the test model to match heat flows and temperatures with the flight model. The observatory test thermal model developed from this process allows quick predictions of the performance of the thermal vacuum test design. In this work, the method described above was applied to the Global Precipitation Measurement (GPM) core observatory spacecraft, a joint project between NASA and the Japanese Aerospace Exploration Agency (JAXA) which is currently being integrated at NASA Goddard Space Flight Center for launch in Early 2014. From preliminary results, the thermal test model generated from this process shows that the heat flows and temperatures match fairly well with the flight thermal model, indicating that the test model can simulate fairly accurately the conditions on-orbit. However, further analysis is needed to determine the best test configuration possible to validate the GPM thermal design before the start of environmental testing later this year. Also, while this analysis method has been applied solely to GPM, it should be emphasized that the same process can be applied to any mission to develop an effective test setup and panel settings which accurately simulate on-orbit thermal environments.

Mars Pathfinder flight system integration and test.

NASA Astrophysics Data System (ADS)

Muirhead, B. K.

This paper describes the system integration and test experiences, problems and lessons learned during the assembly, test and launch operations (ATLO) phase of the Mars Pathfinder flight system scheduled to land on the surface of Mars on July 4, 1997. The Mars Pathfinder spacecraft consists of three spacecraft systems: cruise stage, entry vehicle and lander. The cruise stage carries the entry and lander vehicles to Mars and is jettisoned prior to entry. The entry vehicle, including aeroshell, parachute and deceleration rockets, protects the lander during the direct entry and reduces its velocity from 7.6 to 0 km/s in stages during the 5 min entry sequence. The lander's touchdown is softened by airbags which are retracted once stopped on the surface. The lander then uprights itself, opens up fully and begins surface operations including deploying its camera and rover. This paper overviews the system design and the results of the system integration and test activities, including the entry, descent and landing subsystem elements. System test experiences including science instruments, the microrover, Sojourner, and software are discussed. The final qualification of the entry, descent and landing subsystems during this period is also discussed.

ICESat-2: An overview of science objectives, status, data products and expected performance

NASA Astrophysics Data System (ADS)

Neumann, T.; Markus, T.; Anthony, M.

2016-12-01

NASA's Ice, Cloud, and land Elevation Satellite-2's (ICESat-2) mission objectives are to quantify polar ice sheet contributions to sea level change, quantify regional signatures of ice sheet changes to assess driving mechanisms, estimate sea ice thickness, and to enable measurements of canopy height as a basis for estimating large-scale biomass. With a scheduled launch date in late 2017 most of the flight hardware has been assembled, integrated and tested and algorithm implementation for its standard geophysical products is well underway. The spacecraft, built by Orbital ATK, is completed and is undergoing testing. ICESat-2's single instrument, the Advanced Topographic Laser Altimeter System (ATLAS), is built by NASA Goddard Space Flight Center and by the time of the Fall Meeting will be undergoing integration and testing with the spacecraft, becoming the ICESat-2 observatory. In parallel, high level geophysical data products and associated algorithms are in development using airborne laser altimeter data. This presentation will give an overview of the design of ICESat-2, of its hardware and software status, as well as examples of ICESat-2's coverage and what the data will look like.

Accommodation of practical constraints by a linear programming jet select. [for Space Shuttle

NASA Technical Reports Server (NTRS)

Bergmann, E.; Weiler, P.

1983-01-01

An experimental spacecraft control system will be incorporated into the Space Shuttle flight software and exercised during a forthcoming mission to evaluate its performance and handling qualities. The control system incorporates a 'phase space' control law to generate rate change requests and a linear programming jet select to compute jet firings. Posed as a linear programming problem, jet selection must represent the rate change request as a linear combination of jet acceleration vectors where the coefficients are the jet firing times, while minimizing the fuel expended in satisfying that request. This problem is solved in real time using a revised Simplex algorithm. In order to implement the jet selection algorithm in the Shuttle flight control computer, it was modified to accommodate certain practical features of the Shuttle such as limited computer throughput, lengthy firing times, and a large number of control jets. To the authors' knowledge, this is the first such application of linear programming. It was made possible by careful consideration of the jet selection problem in terms of the properties of linear programming and the Simplex algorithm. These modifications to the jet select algorithm may by useful for the design of reaction controlled spacecraft.

KSC-98pc1328

NASA Image and Video Library

1998-10-12

KENNEDY SPACE CENTER, FLA. -- Wrapped in an anti-static blanket for protection, Deep Space 1 is moved out of the Defense Satellite Communications Systems Processing Facility (DPF) at Cape Canaveral Air Station (CCAS) for its trip to Launch Pad 17A. The spacecraft will be launched aboard a Boeing Delta 7326 rocket on Oct. 25. Deep Space 1 is the first flight in NASA's New Millennium Program, and is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1329

NASA Image and Video Library

1998-10-12

KENNEDY SPACE CENTER, FLA. -- Wrapped in an anti-static blanket for protection, Deep Space 1 is lifted out of the transporter that carried it to Launch Pad 17A at Cape Canaveral Air Station. The spacecraft will be launched aboard a Boeing Delta 7326 rocket on Oct. 25. Deep Space 1 is the first flight in NASA's New Millennium Program, and is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1332

NASA Image and Video Library

1998-10-12

KENNEDY SPACE CENTER, FLA. -- On Launch Pad 17A at Cape Canaveral Air Station, Deep Space 1 is lowered toward the second stage of a Boeing Delta 7326 rocket. The adapter on the spacecraft can be seen surrounding the booster motor. Targeted for launch on Oct. 25, Deep Space 1 is the first flight in NASA's New Millennium Program, and is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1330

NASA Image and Video Library

1998-10-12

KENNEDY SPACE CENTER, FLA. -- Just before sunrise, on Launch Pad 17A at Cape Canaveral Air Station, Deep Space 1 is hoisted up the mobile service tower for installation on a Boeing Delta 7326 rocket . The spacecraft is targeted for launch on Oct. 25. Deep Space 1 is the first flight in NASA's New Millennium Program, and is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

Increasing Flight Software Reuse with OpenSatKit

NASA Technical Reports Server (NTRS)

McComas, David

2018-01-01

In January 2015 the NASA Goddard Space Flight Center (GSFC) released the Core Flight System (cFS) as open source under the NASA Open Source Agreement (NOSA) license. The cFS is based on flight software (FSW) developed for 12 spacecraft spanning nearly two decades of effort and it can provide about a third of the FSW functionality for a low-earth orbiting scientific spacecraft. The cFS is a FSW framework that is portable, configurable, and extendable using a product line deployment model. However, the components are maintained separately so the user must configure, integrate, and deploy them as a cohesive functional system. This can be very challenging especially for organizations such as universities building cubesats that have minimal experience developing FSW. Supporting universities was one of the primary motivators for releasing the cFS under NOSA. This paper describes the OpenSatKit that was developed to address the cFS deployment challenges and to serve as a cFS training platform for new users. It provides a fully functional out-of-the box software system that includes NASA's cFS, Ball Aerospaceâ€"TM"s command and control system COSMOS, and a NASA dynamic simulator called 42. The kit is freely available since all of the components have been released as open source. The kit runs on a Linux platform, includes 8 cFS applications, several kit-specific applications, and built in demos illustrating how to use key application features. It also includes the software necessary to port the cFS to a Raspberry Pi and instructions for configuring COSMOS to communicate with the target. All of the demos and test scripts can be rerun unchanged with the cFS running on the Raspberry Pi. The cFS uses a 3-tiered layered architecture including a platform abstraction layer, a Core Flight Executive (cFE) middle layer, and an application layer. Similar to smart phones, the cFS application layer is the key architectural feature for userâ€"TM"s to extend the FSW functionality to meet their mission-specific requirements. The platform abstraction layer and the cFE layers go a step further than smart phones by providing a platform-agnostic Application Programmer Interface (API) that allows applications to run unchanged on different platforms. OpenSatKit can serve two significant architectural roles that will further help the adoption of the cFS and help create a community of users that can share assets. First, the kit is being enhanced to automate the integration of applications with the goal of creating a virtual cFS 'App Store'. Second, a platform certification test suite can be developed that would allow users to verify the port of the cFS to a new platform. This paper will describe the current state of these efforts and future plans.

Summary of shuttle data processing and aerodynamic performance comparisons for the first 11 flights

NASA Technical Reports Server (NTRS)

Findlay, J. T.; Kelly, G. M.; Heck, M. L.; Mcconnell, J. G.

1984-01-01

NASA Space Shuttle aerodynamic and aerothermodynamic research is but one part of the most comprehensive end-to-end flight test program ever undertaken considering: the extensive pre-flight experimental data base development; the multitude of spacecraft and remote measurements taken during entry flight; the complexity of the Orbiter aerodynamic configuration; the variety of flight conditions available across the entire speed regime; and the efforts devoted to flight data reduction throughout the aerospace community. Shuttle entry flights provide a wealth of research quality data, in essence a veritable flying wind tunnel, for use by researchers to verify and improve the operational capability of the Orbiter and provide data for evaluations of experimental facilities as well as computational methods. This final report merely summarizes the major activities conducted by the AMA, Inc. under NASA Contract NAS1-16087 as part of that interesting research. Investigators desiring more detailed information can refer to the glossary of AMA publications attached herein as Appendix A. Section I provides background discussion of software and methodology development to enable Best Estimate Trajectory (BET) generation. Actual products generated are summarized in Section II as tables which completely describe the post-flight products available from the first three-year Shuttle flight history. Summary results are presented in Section III, with longitudinal performance comparisons included as Appendices for each of the flights.

LANDSAT-1 and LANDSAT-2 flight evaluation report, 23 July - 23 October 1976

NASA Technical Reports Server (NTRS)

1976-01-01

The LANDSAT-1 spacecraft was launched from the Western Test Range on 23 July 1972, at 18:08:06.508Z. The launch and orbital injection phase of the space flight was nominal, and deployment of the spacecraft followed predictions. Performance evaluation of the spacecraft is presented.

Apollo experience report: Manned thermal-vacuum testing of spacecraft

NASA Technical Reports Server (NTRS)

Mclane, J. C., Jr.

1974-01-01

Manned thermal-vacuum tests of the Apollo spacecraft presented many first-time problems in the areas of test philosophy, operational concepts, and program implementation. The rationale used to resolve these problems is explained and examined critically in view of actual experience. The series of 12 tests involving 1517 hours of chamber operating time resulted in the disclosure of numerous equipment and procedural deficiencies of significance to the flight mission. Test experience and results in view of subsequent flight experience confirmed that thermal-vacuum testing of integrated manned spacecraft provides a feasible, cost-effective, and safe technique with which to obtain maximum confidence in spacecraft flight worthiness early in the program.

A historical overview of the electrical power systems in the US manned and some US unmanned spacecraft

NASA Technical Reports Server (NTRS)

Maisel, J. E.

1984-01-01

A historical overview of electrical power systems used in the U.S. manned spacecraft and some of the U.S. unmanned spacecraft is presented in this investigation. A time frame of approximately 25 years, the period for 1959 to 1984, is covered in this report. Results indicate that the nominal bus voltage was 28 volts dc in most spacecraft and all other voltage levels were derived from this voltage through such techniques as voltage inversion or rectification, or a combination. Most spacecraft used solar arrays for the main source of power except for those spacecraft that had a relatively short flight duration, or deep spaceprobes that were designed for very long flight duration. Fuel cells were used on Gemini, Apollo, and Space Shuttle (short duration flights) while radioisotope thermoelectric generators were employed on the Pioneer, Jupiter/Saturn, Viking Lander, and Voyager spacecraft (long duration flights). The main dc bus voltage was unregulated on the manned spacecraft with voltage regulation provided at the user loads. A combination of regulated, semiregulated, and unregulated buses were used on the unmanned spacecraft depending on the type of load. For example, scientific instruments were usually connected to regulated buses while fans, relays, etc. were energized from an unregulated bus. Different forms of voltage regulation, such as shunt, buck/boot, and pulse-width modulated regulators, were used. This report includes a comprehensive bibliography on spacecraft electrical power systems for the space programs investigated.

Test/score/report: Simulation techniques for automating the test process

NASA Technical Reports Server (NTRS)

Hageman, Barbara H.; Sigman, Clayton B.; Koslosky, John T.

1994-01-01

A Test/Score/Report capability is currently being developed for the Transportable Payload Operations Control Center (TPOCC) Advanced Spacecraft Simulator (TASS) system which will automate testing of the Goddard Space Flight Center (GSFC) Payload Operations Control Center (POCC) and Mission Operations Center (MOC) software in three areas: telemetry decommutation, spacecraft command processing, and spacecraft memory load and dump processing. Automated computer control of the acceptance test process is one of the primary goals of a test team. With the proper simulation tools and user interface, the task of acceptance testing, regression testing, and repeatability of specific test procedures of a ground data system can be a simpler task. Ideally, the goal for complete automation would be to plug the operational deliverable into the simulator, press the start button, execute the test procedure, accumulate and analyze the data, score the results, and report the results to the test team along with a go/no recommendation to the test team. In practice, this may not be possible because of inadequate test tools, pressures of schedules, limited resources, etc. Most tests are accomplished using a certain degree of automation and test procedures that are labor intensive. This paper discusses some simulation techniques that can improve the automation of the test process. The TASS system tests the POCC/MOC software and provides a score based on the test results. The TASS system displays statistics on the success of the POCC/MOC system processing in each of the three areas as well as event messages pertaining to the Test/Score/Report processing. The TASS system also provides formatted reports documenting each step performed during the tests and the results of each step. A prototype of the Test/Score/Report capability is available and currently being used to test some POCC/MOC software deliveries. When this capability is fully operational it should greatly reduce the time necessary to test a POCC/MOC software delivery, as well as improve the quality of the test process.

SPHERES as Formation Flight Algorithm Development and Validation Testbed: Current Progress and Beyond

NASA Technical Reports Server (NTRS)

Kong, Edmund M.; Saenz-Otero, Alvar; Nolet, Simon; Berkovitz, Dustin S.; Miller, David W.; Sell, Steve W.

2004-01-01

The MIT-SSL SPHERES testbed provides a facility for the development of algorithms necessary for the success of Distributed Satellite Systems (DSS). The initial development contemplated formation flight and docking control algorithms; SPHERES now supports the study of metrology, control, autonomy, artificial intelligence, and communications algorithms and their effects on DSS projects. To support this wide range of topics, the SPHERES design contemplated the need to support multiple researchers, as echoed from both the hardware and software designs. The SPHERES operational plan further facilitates the development of algorithms by multiple researchers, while the operational locations incrementally increase the ability of the tests to operate in a representative environment. In this paper, an overview of the SPHERES testbed is first presented. The SPHERES testbed serves as a model of the design philosophies that allow for the various researches being carried out on such a facility. The implementation of these philosophies are further highlighted in the three different programs that are currently scheduled for testing onboard the International Space Station (ISS) and three that are proposed for a re-flight mission: Mass Property Identification, Autonomous Rendezvous and Docking, TPF Multiple Spacecraft Formation Flight in the first flight and Precision Optical Pointing, Tethered Formation Flight and Mars Orbit Sample Retrieval for the re-flight mission.

Advances in Autonomous Systems for Missions of Space Exploration

NASA Astrophysics Data System (ADS)

Gross, A. R.; Smith, B. D.; Briggs, G. A.; Hieronymus, J.; Clancy, D. J.

New missions of space exploration will require unprecedented levels of autonomy to successfully accomplish their objectives. Both inherent complexity and communication distances will preclude levels of human involvement common to current and previous space flight missions. With exponentially increasing capabilities of computer hardware and software, including networks and communication systems, a new balance of work is being developed between humans and machines. This new balance holds the promise of meeting the greatly increased space exploration requirements, along with dramatically reduced design, development, test, and operating costs. New information technologies, which take advantage of knowledge-based software, model-based reasoning, and high performance computer systems, will enable the development of a new generation of design and development tools, schedulers, and vehicle and system health monitoring and maintenance capabilities. Such tools will provide a degree of machine intelligence and associated autonomy that has previously been unavailable. These capabilities are critical to the future of space exploration, since the science and operational requirements specified by such missions, as well as the budgetary constraints that limit the ability to monitor and control these missions by a standing army of ground- based controllers. System autonomy capabilities have made great strides in recent years, for both ground and space flight applications. Autonomous systems have flown on advanced spacecraft, providing new levels of spacecraft capability and mission safety. Such systems operate by utilizing model-based reasoning that provides the capability to work from high-level mission goals, while deriving the detailed system commands internally, rather than having to have such commands transmitted from Earth. This enables missions of such complexity and communications distance as are not otherwise possible, as well as many more efficient and low cost applications. One notable example of such missions are those to explore for the existence of water on planets such as Mars and the moons of Jupiter. It is clear that water does not exist on the surfaces of such bodies, but may well be located at some considerable depth below the surface, thus requiring a subsurface drilling capability. Subsurface drilling on planetary surfaces will require a robust autonomous control and analysis system, currently a major challenge, but within conceivable reach of planned technology developments. This paper will focus on new and innovative software for remote, autonomous, space systems flight operations, including flight test results, lessons learned, and implications for the future. An additional focus will be on technologies for planetary exploration using autonomous systems and astronaut-assistance systems that employ new spoken language technology. Topics to be presented will include a description of key autonomous control concepts, illustrated by the Remote Agent program that commanded the Deep Space 1 spacecraft to new levels of system autonomy, recent advances in distributed autonomous system capabilities, and concepts for autonomous vehicle health management systems. A brief description of teaming spacecraft and rovers for complex exploration missions will also be provided. New software for autonomous science data acquisition for planetary exploration will also be described, as well as advanced systems for safe planetary landings. Current results of autonomous planetary drilling system research will be presented. A key thrust within NASA is to develop technologies that will leverage the capabilities of human astronauts during planetary surface explorations. One such technology is spoken dialogue interfaces, which would allow collaboration with semi-autonomous agents that are engaged in activities that are normally accomplished using language, e.g., astronauts in space suits interacting with groups of semi-autonomous rovers and other astronauts. This technology will be described and discussed in the context of future exploration missions and the major new capabilities enabled by such systems. Finally, plans and directions for the future of autonomous systems will be presented.

Applications of Advanced Nondestructive Measurement Techniques to Address Safety of Flight Issues on NASA Spacecraft

NASA Technical Reports Server (NTRS)

Prosser, Bill

2016-01-01

Advanced nondestructive measurement techniques are critical for ensuring the reliability and safety of NASA spacecraft. Techniques such as infrared thermography, THz imaging, X-ray computed tomography and backscatter X-ray are used to detect indications of damage in spacecraft components and structures. Additionally, sensor and measurement systems are integrated into spacecraft to provide structural health monitoring to detect damaging events that occur during flight such as debris impacts during launch and assent or from micrometeoroid and orbital debris, or excessive loading due to anomalous flight conditions. A number of examples will be provided of how these nondestructive measurement techniques have been applied to resolve safety critical inspection concerns for the Space Shuttle, International Space Station (ISS), and a variety of launch vehicles and unmanned spacecraft.

Autonomous Science Analysis with the New Millennium Program-Autonomous Sciencecraft Experiment

NASA Astrophysics Data System (ADS)

Doggett, T.; Davies, A. G.; Castano, R. A.; Baker, V. R.; Dohm, J. M.; Greeley, R.; Williams, K. K.; Chien, S.; Sherwood, R.

2002-12-01

The NASA New Millennium Program (NMP) is a testbed for new, high-risk technologies, including new software and hardware. The Autonomous Sciencecraft Experiment (ASE) will fly on the Air Force Research Laboratory TechSat-21 mission in 2006 is such a NMP mission, and is managed by the Jet Propulsion Laboratory, California Institute of Technology. TechSat-21 consists of three satellites, each equipped with X-band Synthetic Aperture Radar (SAR) that will occupy a 13-day repeat track Earth orbit. The main science objectives of ASE are to demonstrate that process-related change detection and feature identification can be conducted autonomously during space flight, leading to autonomous onboard retargeting of the spacecraft. This mission will observe transient geological and environmental processes using SAR. Examples of geologic processes that may be observed and investigated include active volcanism, the movement of sand dunes and transient features in desert environments, water flooding, and the formation and break-up of lake ice. Science software onboard the spacecraft will allow autonomous processing and formation of SAR images and extraction of scientific information. The subsequent analyses, performed on images formed onboard from the SAR data, will include feature identification using scalable feature "templates" for each target, change detection through comparison of current and archived images, and science discovery, a search for other features of interest in each image. This approach results in obtaining the same science return for a reduced amount of resource use (such as downlink) when compared to that from a mission operating without ASE technology. Redundant data is discarded. The science-driven goals of ASE will evolve during the ASE mission through onboard replanning software that can re-task satellite operations. If necessary, as a result of a discovery made autonomously by onboard science processing, existing observation sequences will be pre-empted to obtain data of potential high scientific content. Flight validation of this software will enable radically different missions with significant onboard decision-making and novel science concepts (onboard decision making and selective data return). This work has been carried out at the Jet Propulsion Laboratory-California Institute of Technology, under contract to NASA.

Prediction of Spacecraft Vibration using Acceleration and Force Envelopes

NASA Technical Reports Server (NTRS)

Gordon, Scott; Kaufman, Daniel; Kern, Dennis; Scharton, Terry

2009-01-01

The base forces in the GLAST X- and Z-axis sine vibration tests were similar to those derived using generic inputs (from users guide and handbook), but the base forces in the sine test were generally greater than the flight data. Basedrive analyses using envelopes of flight acceleration data provided more accurate predictions of the base force than generic inputs, and as expected, using envelopes of both the flight acceleration and force provided even more accurate predictions The GLAST spacecraft interface accelerations and forces measured during the MECO transient were relatively low in the 60 to 150 Hz regime. One may expect the flight forces measured at the base of various spacecraft to be more dependent on the mass, frequencies, etc. of the spacecraft than are the corresponding interface acceleration data, which may depend more on the launch vehicle configuration.

The Implementation of Satellite Control System Software Using Object Oriented Design

NASA Technical Reports Server (NTRS)

Anderson, Mark O.; Reid, Mark; Drury, Derek; Hansell, William; Phillips, Tom

1998-01-01

NASA established the Small Explorer (SMEX) program in 1988 to provide frequent opportunities for highly focused and relatively inexpensive space science missions that can be launched into low earth orbit by small expendable vehicles. The development schedule for each SMEX spacecraft was three years from start to launch. The SMEX program has produced five satellites; Solar Anomalous and Magnetospheric Particle Explorer (SAMPEX), Fast Auroral Snapshot Explorer (FAST), Submillimeter Wave Astronomy Satellite (SWAS), Transition Region and Coronal Explorer (TRACE) and Wide-Field Infrared Explorer (WIRE). SAMPEX and FAST are on-orbit, TRACE is scheduled to be launched in April of 1998, WIRE is scheduled to be launched in September of 1998, and SWAS is scheduled to be launched in January of 1999. In each of these missions, the Attitude Control System (ACS) software was written using a modular procedural design. Current program goals require complete spacecraft development within 18 months. This requirement has increased pressure to write reusable flight software. Object-Oriented Design (OOD) offers the constructs for developing an application that only needs modification for mission unique requirements. This paper describes the OOD that was used to develop the SMEX-Lite ACS software. The SMEX-Lite ACS is three-axis controlled, momentum stabilized, and is capable of performing sub-arc-minute pointing. The paper first describes the high level requirements which governed the architecture of the SMEX-Lite ACS software. Next, the context in which the software resides is explained. The paper describes the benefits of encapsulation, inheritance and polymorphism with respect to the implementation of an ACS software system. This paper will discuss the design of several software components that comprise the ACS software. Specifically, Object-Oriented designs are presented for sensor data processing, attitude control, attitude determination and failure detection. The paper addresses the benefits of the OOD versus a conventional procedural design. The final discussion in this paper will address the establishment of the ACS Foundation Class (AFC) Library. The AFC is a large software repository, requiring a minimal amount of code modifications to produce ACS software for future projects, saving production time and costs.

Lunar Atmosphere and Dust Environment Explorer Integration and Test

NASA Technical Reports Server (NTRS)

Wright, Michael R.; McCormick, John L.

2010-01-01

The Lunar Atmosphere and Dust Environment Explorer (LADEE) is a NASA collaborative flight project to explore the lunar exosphere. It is being developed through a unique partnership between NASA's Ames Research Center (ARC) and Goddard Space Flight Center (GSFC). Each center brings its own experience and flight systems heritage to the task of integrating and testing the LADEE subsystems, instruments, and spacecraft. As an "in-house" flight project being implemented at low-cost and moderate risk, LADEE relies on single-string subsystems and protoflight hardware to accomplish its mission. Integration and test (l&T) of the LADEE spacecraft with the instruments will be performed at GSFC, and includes assembly, integration, functional testing, and flight qualification and acceptance testing. Due to the nature of the LADEE mission, l&T requirements include strict contamination control measures and instrument calibration procedures. Environmental testing will include electromagnetic compatibility (EMC), vibro-acoustic testing, and thermal-balance/vacuum. Upon successful completion of spacecraft l&T, LADEE will be launched from NASA's Wallops Flight Facility. Launch of the LADEE spacecraft is currently scheduled for December 2012.

Global Precipitation Measurement Mission Launch and Commissioning

NASA Technical Reports Server (NTRS)

Davis, Nikesha; DeWeese, Keith; Vess, Melissa; O'Donnell, James R., Jr.; Welter, Gary

2015-01-01

During launch and early operation of the Global Precipitation Measurement (GPM) Mission, the Guidance, Navigation, and Control (GN&C) analysis team encountered four main on-orbit anomalies. These include: (1) unexpected shock from Solar Array deployment, (2) momentum buildup from the Magnetic Torquer Bars (MTBs) phasing errors, (3) transition into Safehold due to albedo induced Course Sun Sensor (CSS) anomaly, and (4) a flight software error that could cause a Safehold transition due to a Star Tracker occultation. This paper will discuss ways GN&C engineers identified the anomalies and tracked down the root causes. Flight data and GN&C on-board models will be shown to illustrate how each of these anomalies were investigated and mitigated before causing any harm to the spacecraft. On May 29, 2014, GPM was handed over to the Mission Flight Operations Team after a successful commissioning period. Currently, GPM is operating nominally on orbit, collecting meaningful scientific data that will significantly improve our understanding of the Earth's climate and water cycle.

Global Precipitation Measurement Mission Launch and Commissioning

NASA Technical Reports Server (NTRS)

Davis, Nikesha; Deweese, Keith; Vess, Missie; Welter, Gary; O'Donnell, James R., Jr.

2015-01-01

During launch and early operation of the Global Precipitation Measurement (GPM) Mission, the Guidance, Navigation and Control (GNC) analysis team encountered four main on orbit anomalies. These include: (1) unexpected shock from Solar Array deployment, (2) momentum buildup from the Magnetic Torquer Bars (MTBs) phasing errors, (3) transition into Safehold due to albedo-induced Course Sun Sensor (CSS) anomaly, and (4) a flight software error that could cause a Safehold transition due to a Star Tracker occultation. This paper will discuss ways GNC engineers identified and tracked down the root causes. Flight data and GNC on board models will be shown to illustrate how each of these anomalies were investigated and mitigated before causing any harm to the spacecraft. On May 29, 2014, GPM was handed over to the Mission Flight Operations Team after a successful commissioning period. Currently, GPM is operating nominally on orbit, collecting meaningful scientific data that will significantly improve our understanding of the Earth's climate and water cycle.

Spinoff 2013

NASA Technical Reports Server (NTRS)

2014-01-01

Topics covered include: Innovative Software Tools Measure Behavioral Alertness; Miniaturized, Portable Sensors Monitor Metabolic Health; Patient Simulators Train Emergency Caregivers; Solar Refrigerators Store Life-Saving Vaccines; Monitors Enable Medication Management in Patients' Homes; Handheld Diagnostic Device Delivers Quick Medical Readings; Experiments Result in Safer, Spin-Resistant Aircraft; Interfaces Visualize Data for Airline Safety, Efficiency; Data Mining Tools Make Flights Safer, More Efficient; NASA Standards Inform Comfortable Car Seats; Heat Shield Paves the Way for Commercial Space; Air Systems Provide Life Support to Miners; Coatings Preserve Metal, Stone, Tile, and Concrete; Robots Spur Software That Lends a Hand; Cloud-Based Data Sharing Connects Emergency Managers; Catalytic Converters Maintain Air Quality in Mines; NASA-Enhanced Water Bottles Filter Water on the Go; Brainwave Monitoring Software Improves Distracted Minds; Thermal Materials Protect Priceless, Personal Keepsakes; Home Air Purifiers Eradicate Harmful Pathogens; Thermal Materials Drive Professional Apparel Line; Radiant Barriers Save Energy in Buildings; Open Source Initiative Powers Real-Time Data Streams; Shuttle Engine Designs Revolutionize Solar Power; Procedure-Authoring Tool Improves Safety on Oil Rigs; Satellite Data Aid Monitoring of Nation's Forests; Mars Technologies Spawn Durable Wind Turbines; Programs Visualize Earth and Space for Interactive Education; Processor Units Reduce Satellite Construction Costs; Software Accelerates Computing Time for Complex Math; Simulation Tools Prevent Signal Interference on Spacecraft; Software Simplifies the Sharing of Numerical Models; Virtual Machine Language Controls Remote Devices; Micro-Accelerometers Monitor Equipment Health; Reactors Save Energy, Costs for Hydrogen Production; Cameras Monitor Spacecraft Integrity to Prevent Failures; Testing Devices Garner Data on Insulation Performance; Smart Sensors Gather Information for Machine Diagnostics; Oxygen Sensors Monitor Bioreactors and Ensure Health and Safety; Vision Algorithms Catch Defects in Screen Displays; and Deformable Mirrors Capture Exoplanet Data, Reflect Lasers.

Extraction of Modal Parameters from Spacecraft Flight Data

NASA Technical Reports Server (NTRS)

James, George H.; Cao, Timothy T.; Fogt, Vincent A.; Wilson, Robert L.; Bartkowicz, Theodore J.

2010-01-01

The modeled response of spacecraft systems must be validated using flight data as ground tests cannot adequately represent the flight. Tools from the field of operational modal analysis would typically be brought to bear on such structures. However, spacecraft systems have several complicated issues: 1. High amplitudes of loads; 2. Compressive loads on the vehicle in flight; 3. Lack of generous time-synchronized flight data; 4. Changing properties during the flight; and 5. Major vehicle changes due to staging. A particularly vexing parameter to extract is modal damping. Damping estimation has become a more critical issue as new mass-driven vehicle designs seek to use the highest damping value possible. The paper will focus on recent efforts to utilize spacecraft flight data to extract system parameters, with a special interest on modal damping. This work utilizes the analysis of correlation functions derived from a sliding window technique applied to the time record. Four different case studies are reported in the sequence that drove the authors understanding. The insights derived from these four exercises are preliminary conclusions for the general state-of-the-art, but may be of specific utility to similar problems approached with similar tools.

Innovative Educational Aerospace Research at the Northeast High School Space Research Center

NASA Technical Reports Server (NTRS)

Luyet, Audra; Matarazzo, Anthony; Folta, David

1997-01-01

Northeast High Magnet School of Philadelphia, Pennsylvania is a proud sponsor of the Space Research Center (SPARC). SPARC, a model program of the Medical, Engineering, and Aerospace Magnet school, provides talented students the capability to successfully exercise full simulations of NASA manned missions. These simulations included low-Earth Shuttle missions and Apollo lunar missions in the past, and will focus on a planetary mission to Mars this year. At the end of each scholastic year, a simulated mission, lasting between one and eight days, is performed involving 75 students as specialists in seven teams The groups are comprised of Flight Management, Spacecraft Communications (SatCom), Computer Networking, Spacecraft Design and Engineering, Electronics, Rocketry, Robotics, and Medical teams in either the mission operations center or onboard the spacecraft. Software development activities are also required in support of these simulations The objective of this paper is to present the accomplishments, technology innovations, interactions, and an overview of SPARC with an emphasis on how the program's educational activities parallel NASA mission support and how this education is preparing student for the space frontier.

Development of an automated electrical power subsystem testbed for large spacecraft

NASA Technical Reports Server (NTRS)

Hall, David K.; Lollar, Louis F.

1990-01-01

The NASA Marshall Space Flight Center (MSFC) has developed two autonomous electrical power system breadboards. The first breadboard, the autonomously managed power system (AMPS), is a two power channel system featuring energy generation and storage and 24-kW of switchable loads, all under computer control. The second breadboard, the space station module/power management and distribution (SSM/PMAD) testbed, is a two-bus 120-Vdc model of the Space Station power subsystem featuring smart switchgear and multiple knowledge-based control systems. NASA/MSFC is combining these two breadboards to form a complete autonomous source-to-load power system called the large autonomous spacecraft electrical power system (LASEPS). LASEPS is a high-power, intelligent, physical electrical power system testbed which can be used to derive and test new power system control techniques, new power switching components, and new energy storage elements in a more accurate and realistic fashion. LASEPS has the potential to be interfaced with other spacecraft subsystem breadboards in order to simulate an entire space vehicle. The two individual systems, the combined systems (hardware and software), and the current and future uses of LASEPS are described.

Navigation Operations for the Magnetospheric Multiscale Mission

NASA Technical Reports Server (NTRS)

Long, Anne; Farahmand, Mitra; Carpenter, Russell

2015-01-01

The Magnetospheric Multiscale (MMS) mission employs four identical spinning spacecraft flying in highly elliptical Earth orbits. These spacecraft will fly in a series of tetrahedral formations with separations of less than 10 km. MMS navigation operations use onboard navigation to satisfy the mission definitive orbit and time determination requirements and in addition to minimize operations cost and complexity. The onboard navigation subsystem consists of the Navigator GPS receiver with Goddard Enhanced Onboard Navigation System (GEONS) software, and an Ultra-Stable Oscillator. The four MMS spacecraft are operated from a single Mission Operations Center, which includes a Flight Dynamics Operations Area (FDOA) that supports MMS navigation operations, as well as maneuver planning, conjunction assessment and attitude ground operations. The System Manager component of the FDOA automates routine operations processes. The GEONS Ground Support System component of the FDOA provides the tools needed to support MMS navigation operations. This paper provides an overview of the MMS mission and associated navigation requirements and constraints and discusses MMS navigation operations and the associated MMS ground system components built to support navigation-related operations.

Deep Space 1 Using its Ion Engine Artist Concept

NASA Image and Video Library

2003-07-02

NASA's New Millennium Deep Space 1 spacecraft approaching the comet 19P/Borrelly. With its primary mission to serve as a technology demonstrator--testing ion propulsion and 11 other advanced technologies--successfully completed in September 1999, Deep Space 1 is now headed for a risky, exciting rendezvous with Comet Borrelly. NASA extended the mission, taking advantage of the ion propulsion and other systems to target the daring encounter with the comet in September 2001. Once a sci-fi dream, the ion propulsion engine has powered the spacecraft for over 12,000 hours. Another onboard experiment includes software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The first flight in NASA's New Millennium Program, Deep Space 1 was launched October 24, 1998 aboard a Boeing Delta 7326 rocket from Cape Canaveral Air Station, FL. Deep Space 1 successfully completed and exceeded its mission objectives in July 1999 and flew by a near-Earth asteroid, Braille (1992 KD), in September 1999. http://photojournal.jpl.nasa.gov/catalog/PIA04604

Expanding Hardware-in-the-Loop Formation Navigation and Control with Radio Frequency Crosslink Ranging

NASA Technical Reports Server (NTRS)

Mitchell, Jason W.; Barbee, Brent W.; Baldwin, Philip J.; Luquette, Richard J.

2007-01-01

The Formation Flying Testbed (FFTB) at the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) provides a hardware-in-the-loop test environment for formation navigation and control. The facility continues to evolve as a modular, hybrid, dynamic simulation facility for end-to-end guidance, navigation, and control (GN&C) design and analysis of formation flying spacecraft. The core capabilities of the FFTB, as a platform for testing critical hardware and software algorithms in-the-loop, are reviewed with a focus on recent improvements. With the most recent improvement, in support of Technology Readiness Level (TRL) 6 testing of the Inter-spacecraft Ranging and Alarm System (IRAS) for the Magnetospheric Multiscale (MMS) mission, the FFTB has significantly expanded its ability to perform realistic simulations that require Radio Frequency (RF) ranging sensors for relative navigation with the Path Emulator for RF Signals (PERFS). The PERFS, currently under development at NASA GSFC, modulates RF signals exchanged between spacecraft. The RF signals are modified to accurately reflect the dynamic environment through which they travel, including the effects of medium, moving platforms, and radiated power.

Spacecraft Data Simulator for the test of level zero processing systems

NASA Technical Reports Server (NTRS)

Shi, Jeff; Gordon, Julie; Mirchandani, Chandru; Nguyen, Diem

1994-01-01

The Microelectronic Systems Branch (MSB) at Goddard Space Flight Center (GSFC) has developed a Spacecraft Data Simulator (SDS) to support the development, test, and verification of prototype and production Level Zero Processing (LZP) systems. Based on a disk array system, the SDS is capable of generating large test data sets up to 5 Gigabytes and outputting serial test data at rates up to 80 Mbps. The SDS supports data formats including NASA Communication (Nascom) blocks, Consultative Committee for Space Data System (CCSDS) Version 1 & 2 frames and packets, and all the Advanced Orbiting Systems (AOS) services. The capability to simulate both sequential and non-sequential time-ordered downlink data streams with errors and gaps is crucial to test LZP systems. This paper describes the system architecture, hardware and software designs, and test data designs. Examples of test data designs are included to illustrate the application of the SDS.

Microcomputer spacecraft thermal analysis routines (MSTAR) Phase I: The user interface

DOE Office of Scientific and Technical Information (OSTI.GOV)

Teti, N.M.

1993-12-31

The Microcomputer Spacecraft Thermal Analysis Routines (MSTAR) software package is being developed for NASA/Goddard Space Flight Center by Swales and Associates, Inc. (S&AI). In December 1992, S&AI was awarded a phase I Small Business Inovative Research contract fronm NASA to develop a microcomputer based thermal analysis program to replace the current SSPTA and TRASYS programs. Phase I consists of a six month effort which will focus on developing geometric model generation and visualization capabilities using a graphical user interface (GUI). The information contained in this paper encompasses the work performed during the Phase I development cycle; with emphasis on themore » development of the graphical user interface (GUI). This includes both the theory behind and specific examples of how the MSTAR GUI was implemented. Furthermore, this report discusses new applications and enhancements which will improve the capabilities and commercialization of the MSTAR program.« less

Microcomputer spacecraft thermal analysis routines (MSTAR) Phase I: The user interface

NASA Technical Reports Server (NTRS)

Teti, Nicholas M.

1993-01-01

The Microcomputer Spacecraft Thermal Analysis Routines (MSTAR) software package is being developed for NASA/Goddard Space Flight Center by Swales and Associates, Inc. (S&AI). In December 1992, S&AI was awarded a phase I Small Business Inovative Research contract fronm NASA to develop a microcomputer based thermal analysis program to replace the current SSPTA and TRASYS programs. Phase I consists of a six month effort which will focus on developing geometric model generation and visualization capabilities using a graphical user interface (GUI). The information contained in this paper encompasses the work performed during the Phase I development cycle; with emphasis on the development of the graphical user interface (GUI). This includes both the theory behind and specific examples of how the MSTAR GUI was implemented. Furthermore, this report discusses new applications and enhancements which will improve the capabilities and commercialization of the MSTAR program.

Overview of Orion Crew Module and Launch Abort Vehicle Dynamic Stability

NASA Technical Reports Server (NTRS)

Owens, Donald B.; Aibicjpm. Vamessa V.

2011-01-01

With the retirement of the Space Shuttle, NASA is designing a new spacecraft, called Orion, to fly astronauts to low earth orbit and beyond. Characterization of the dynamic stability of the Orion spacecraft is important for the design of the spacecraft and trajectory construction. Dynamic stability affects the stability and control of the Orion Crew Module during re-entry, especially below Mach = 2.0 and including flight under the drogues. The Launch Abort Vehicle is affected by dynamic stability as well, especially during the re-orientation and heatshield forward segments of the flight. The dynamic stability was assessed using the forced oscillation technique, free-to-oscillate, ballistic range, and sub-scale free-flight tests. All of the test techniques demonstrated that in heatshield-forward flight the Crew Module and Launch Abort Vehicle are dynamically unstable in a significant portion of their flight trajectory. This paper will provide a brief overview of the Orion dynamic aero program and a high-level summary of the dynamic stability characteristics of the Orion spacecraft.

KSC-98pc1087

NASA Image and Video Library

1998-09-17

KENNEDY SPACE CENTER, FLA. -- Workers in the Payload Hazardous Servicing Facility prepare Deep Space 1 for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near-Earth asteroid, 1992 KD, has also been selected for a possible flyby

Deep Space 1 is prepared for launch

NASA Technical Reports Server (NTRS)

1998-01-01

Workers in the Payload Hazardous Servicing Facility prepare Deep Space 1 for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near- Earth asteroid, 1992 KD, has also been selected for a possible flyby.

ESOC - The satellite operation center of the European Space Agency

NASA Astrophysics Data System (ADS)

Dworak, H. P.

1980-04-01

The operation and individual functions of the European Space Operation Center (ESOC) that controls the flight of ESA satellites are presented. The main role of the ESOC is discussed and its division into three areas: telemetry, remote piloting, and tracking is outlined. Attention is given to the manipulation of experimental data collected on board the satellites as well as to the functions of the individual ground stations. A block diagram of the information flow to the Meteosat receiving station is presented along with the network outlay of data flow between the ground stations and the ESOC. Distribution of tasks between the ground operation manager, spacecraft operations manager, and flight dynamic software coordinator is discussed with reference to a mission team. A short description of the current missions including COS-B, GEOS-1 and 2, Meteosat, OTS, and ISEE-B is presented

Magellan attitude and articulation control subsystem closed loop testing

NASA Technical Reports Server (NTRS)

Olschansky, David G.

1987-01-01

In the spring of 1989, the Magellan spacecraft will embark on a two-year mission to map the surface of the planet Venus. Guiding it there will be the Attitude and Articulation Control Subsystem (AACS). To ensure reliable operations the AACS is being put through a rigorous test program at Martin Marietta Denver Aerospace. Before Magellan ever leaves the Space Shuttle bay from which it is to be launched, its components will have flown a simulated spaceflight in a ground-based lab. The primary objectives of the test program are to verify form, fit, and function of the AACS, particularly subsystem external interfaces and functional operation of the flight software. This paper discusses the Magellan Closed Loop Test Systems which makes realistic tests possible by simulating the dynamic and 'visual' flight environment for AACS components in the lab.

KSC-98pc1386

NASA Image and Video Library

1998-10-24

KENNEDY SPACE CENTER, FLA. -- Photographed at Launch Complex 17, Cape Canaveral Station, just after midnight on launch day, Boeing's Delta II rocket is bathed in light as it awaits its destiny, hurling NASA's Deep Space 1 into space. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century, including the ion propulsion engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-2013-3391

NASA Image and Video Library

2013-08-22

EDWARDS AFB, Calif. - ED13-0300-002 – An Erickson Air-Crane helicopter lifts Sierra Nevada Corporation's Dream Chaser flight vehicle during a captive-carry flight test. The test was a rehearsal for free flights at Edwards later this year. The spacecraft is under development in partnership with NASA's Commercial Crew Program. Although the spacecraft is designed for crew members, the vehicle will not have anyone onboard during the free flights. Photo credit: NASA/Carla Thomas

KSC-2013-3390

NASA Image and Video Library

2013-08-22

EDWARDS AFB, Calif. - ED13-0300-001 – An Erickson Air-Crane helicopter lifts Sierra Nevada Corporation's Dream Chaser flight vehicle during a captive-carry flight test. The test was a rehearsal for free flights at Edwards later this year. The spacecraft is under development in partnership with NASA's Commercial Crew Program. Although the spacecraft is designed for crew members, the vehicle will not have anyone onboard during the free flights. Photo credit: NASA/Carla Thomas

KSC-2013-3392

NASA Image and Video Library

2013-08-22

EDWARDS AFB, Calif. - ED13-0300-003 – An Erickson Air-Crane helicopter lifts Sierra Nevada Corporation's Dream Chaser flight vehicle during a captive-carry flight test. The test was a rehearsal for free flights at Edwards later this year. The spacecraft is under development in partnership with NASA's Commercial Crew Program. Although the spacecraft is designed for crew members, the vehicle will not have anyone onboard during the free flights. Photo credit: NASA/Carla Thomas

NASA Medical Response to Human Spacecraft Accidents

NASA Technical Reports Server (NTRS)

Patlach, Robert

2010-01-01

Manned space flight is risky business. Accidents have occurred and may occur in the future. NASA's manned space flight programs, with all their successes, have had three fatal accidents, one at the launch pad and two in flight. The Apollo fire and the Challenger and Columbia accidents resulted in a loss of seventeen crewmembers. Russia's manned space flight programs have had three fatal accidents, one ground-based and two in flight. These accidents resulted in the loss of five crewmembers. Additionally, manned spacecraft have encountered numerous close calls with potential for disaster. The NASA Johnson Space Center Flight Safety Office has documented more than 70 spacecraft incidents, many of which could have become serious accidents. At the Johnson Space Center (JSC), medical contingency personnel are assigned to a Mishap Investigation Team. The team deploys to the accident site to gather and preserve evidence for the Accident Investigation Board. The JSC Medical Operations Branch has developed a flight surgeon accident response training class to capture the lessons learned from the Columbia accident. This presentation will address the NASA Mishap Investigation Team's medical objectives, planned response, and potential issues that could arise subsequent to a manned spacecraft accident. Educational Objectives are to understand the medical objectives and issues confronting the Mishap Investigation Team medical personnel subsequent to a human space flight accident.

Spacecraft Design Thermal Control Subsystem

NASA Technical Reports Server (NTRS)

Miyake, Robert N.

2008-01-01

The Thermal Control Subsystem engineers task is to maintain the temperature of all spacecraft components, subsystems, and the total flight system within specified limits for all flight modes from launch to end-of-mission. In some cases, specific stability and gradient temperature limits will be imposed on flight system elements. The Thermal Control Subsystem of "normal" flight systems, the mass, power, control, and sensing systems mass and power requirements are below 10% of the total flight system resources. In general the thermal control subsystem engineer is involved in all other flight subsystem designs.

Use of Soft Computing Technologies for a Qualitative and Reliable Engine Control System for Propulsion Systems

NASA Technical Reports Server (NTRS)

Trevino, Luis; Brown, Terry; Crumbley, R. T. (Technical Monitor)

2001-01-01

The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to improve overall vehicle system safety, reliability, and rocket engine performance by development of a qualitative and reliable engine control system (QRECS). Specifically, this will be addressed by enhancing rocket engine control using SCT, innovative data mining tools, and sound software engineering practices used in Marshall's Flight Software Group (FSG). The principle goals for addressing the issue of quality are to improve software management, software development time, software maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control methodologies, but to provide alternative design choices for control, implementation, performance, and sustaining engineering, all relative to addressing the issue of reliability. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion (system level), software engineering for embedded flight software systems, and soft computing technologies (i.e., neural networks, fuzzy logic, data mining, and Bayesian belief networks); some of which are briefed in this paper. For this effort, the targeted demonstration rocket engine testbed is the MC-1 engine (formerly FASTRAC) which is simulated with hardware and software in the Marshall Avionics & Software Testbed (MAST) laboratory that currently resides at NASA's Marshall Space Flight Center, building 4476, and is managed by the Avionics Department. A brief plan of action for design, development, implementation, and testing a Phase One effort for QRECS is given, along with expected results. Phase One will focus on development of a Smart Start Engine Module and a Mainstage Engine Module for proper engine start and mainstage engine operations. The overall intent is to demonstrate that by employing soft computing technologies, the quality and reliability of the overall scheme to engine controller development is further improved and vehicle safety is further insured. The final product that this paper proposes is an approach to development of an alternative low cost engine controller that would be capable of performing in unique vision spacecraft vehicles requiring low cost advanced avionics architectures for autonomous operations from engine pre-start to engine shutdown.

Summary results of the first United States manned orbital space flight

NASA Technical Reports Server (NTRS)

Glenn, J. H. Jr

1963-01-01

This paper describes the principal findings of the first United States manned orbital space flight in light of the flight mission. Consideration is given to the coordinated tracking network, recovery forces and to the spacecraft and its several functional systems. These include mechanisms for heat protection, escape maneuvers, spacecraft control, power supply, communications, life support and landing. A few difficulties encountered in the flight and deviations from the planned sequence are described. Craft preparation, aeromedical studies, flight plan and particularly flight observations--including the color, light, horizon visibility by day and by night, cloud formations and sunrise and sunset effects are given in some detail. The general conclusion from the MA-6 flight is that man can adapt well to new conditions encountered in space flight and that man can contribute importantly to mission reliability and toward mission achievement through his capacities to control the spacecraft and its multiple systems contribute to decision making and adaptation of programming as well as to direct exploratory and experimental observations.

Tools Ensure Reliability of Critical Software

NASA Technical Reports Server (NTRS)

2012-01-01

In November 2006, after attempting to make a routine maneuver, NASA's Mars Global Surveyor (MGS) reported unexpected errors. The onboard software switched to backup resources, and a 2-day lapse in communication took place between the spacecraft and Earth. When a signal was finally received, it indicated that MGS had entered safe mode, a state of restricted activity in which the computer awaits instructions from Earth. After more than 9 years of successful operation gathering data and snapping pictures of Mars to characterize the planet's land and weather communication between MGS and Earth suddenly stopped. Months later, a report from NASA's internal review board found the spacecraft's battery failed due to an unfortunate sequence of events. Updates to the spacecraft's software, which had taken place months earlier, were written to the wrong memory address in the spacecraft's computer. In short, the mission ended because of a software defect. Over the last decade, spacecraft have become increasingly reliant on software to carry out mission operations. In fact, the next mission to Mars, the Mars Science Laboratory, will rely on more software than all earlier missions to Mars combined. According to Gerard Holzmann, manager at the Laboratory for Reliable Software (LaRS) at NASA's Jet Propulsion Laboratory (JPL), even the fault protection systems on a spacecraft are mostly software-based. For reasons like these, well-functioning software is critical for NASA. In the same year as the failure of MGS, Holzmann presented a new approach to critical software development to help reduce risk and provide consistency. He proposed The Power of 10: Rules for Developing Safety-Critical Code, which is a small set of rules that can easily be remembered, clearly relate to risk, and allow compliance to be verified. The reaction at JPL was positive, and developers in the private sector embraced Holzmann's ideas.

Internet Access to Spacecraft

NASA Technical Reports Server (NTRS)

Rash, James; Parise, Ron; Hogie, Keith; Criscuolo, Ed; Langston, Jim; Jackson, Chris; Price, Harold; Powers, Edward I. (Technical Monitor)

2000-01-01

The Operating Missions as Nodes on the Internet (OMNI) project at NASA's Goddard Space flight Center (GSFC), is demonstrating the use of standard Internet protocols for spacecraft communication systems. This year, demonstrations of Internet access to a flying spacecraft have been performed with the UoSAT-12 spacecraft owned and operated by Surrey Satellite Technology Ltd. (SSTL). Previously, demonstrations were performed using a ground satellite simulator and NASA's Tracking and Data Relay Satellite System (TDRSS). These activities are part of NASA's Space Operations Management Office (SOMO) Technology Program, The work is focused on defining the communication architecture for future NASA missions to support both NASA's "faster, better, cheaper" concept and to enable new types of collaborative science. The use of standard Internet communication technology for spacecraft simplifies design, supports initial integration and test across an IP based network, and enables direct communication between scientists and instruments as well as between different spacecraft, The most recent demonstrations consisted of uploading an Internet Protocol (IP) software stack to the UoSAT- 12 spacecraft, simple modifications to the SSTL ground station, and a series of tests to measure performance of various Internet applications. The spacecraft was reconfigured on orbit at very low cost. The total period between concept and the first tests was only 3 months. The tests included basic network connectivity (PING), automated clock synchronization (NTP), and reliable file transfers (FTP). Future tests are planned to include additional protocols such as Mobile IP, e-mail, and virtual private networks (VPN) to enable automated, operational spacecraft communication networks. The work performed and results of the initial phase of tests are summarized in this paper. This work is funded and directed by NASA/GSFC with technical leadership by CSC in arrangement with SSTL, and Vytek Wireless.

Automated constraint checking of spacecraft command sequences

NASA Astrophysics Data System (ADS)

Horvath, Joan C.; Alkalaj, Leon J.; Schneider, Karl M.; Spitale, Joseph M.; Le, Dang

1995-01-01

Robotic spacecraft are controlled by onboard sets of commands called "sequences." Determining that sequences will have the desired effect on the spacecraft can be expensive in terms of both labor and computer coding time, with different particular costs for different types of spacecraft. Specification languages and appropriate user interface to the languages can be used to make the most effective use of engineering validation time. This paper describes one specification and verification environment ("SAVE") designed for validating that command sequences have not violated any flight rules. This SAVE system was subsequently adapted for flight use on the TOPEX/Poseidon spacecraft. The relationship of this work to rule-based artificial intelligence and to other specification techniques is discussed, as well as the issues that arise in the transfer of technology from a research prototype to a full flight system.

Managing Complexity in Next Generation Robotic Spacecraft: From a Software Perspective

NASA Technical Reports Server (NTRS)

Reinholtz, Kirk

2008-01-01

This presentation highlights the challenges in the design of software to support robotic spacecraft. Robotic spacecraft offer a higher degree of autonomy, however currently more capabilities are required, primarily in the software, while providing the same or higher degree of reliability. The complexity of designing such an autonomous system is great, particularly while attempting to address the needs for increased capabilities and high reliability without increased needs for time or money. The efforts to develop programming models for the new hardware and the integration of software architecture are highlighted.

Gemini Program Mission Report: Gemini IV

NASA Technical Reports Server (NTRS)

1965-01-01

The second manned mission of the Gemini Program, Gemini IV, was launched from Complex 19 at Cape Kennedy, Florida, at 10:16 a.m. e.s.t. on June 3, 1965. The mission was successfully concluded on June 7, 1965, with the recovery of the spacecraft by the prime recovery ship, the aircraft carrier U.S.S. Wasp, at 27 deg 44' N. latitude, 74 deg 11' W. longitude at 2:28 p.m. e.s.t. This manned long-duration flight was accomplished 10 weeks after the three-orbit manned flight which qualified the Gemini spacecraft and systems for orbital flight. The spacecraft was manned by Astronaut James A. McDivitt, command pilot, and Astronaut Edward H. White II, pilot. The flight crew completed the 4-day mission in excellent physical condition, and demonstrated full control of the spacecraft and competent management of all aspects of the mission.

Using CCSDS Standards to Reduce Mission Costs

NASA Technical Reports Server (NTRS)

Wilmot, Jonathan

2017-01-01

NASA's open source Core Flight System (cFS) software framework has been using several Consultative Committee for Space Data Systems (CCSDS) standards since its inception. Recently developed CCSDS standards are now being applied by NASA, ESA and other organizations to streamline and automate aspects of mission development, test, and operations, speeding mission schedules and reducing mission costs. This paper will present the new CCSDS Spacecraft Onboard Interfaces Services (SOIS) Electronic Data Sheet (EDS) standards and show how they are being applied to data interfaces in the cFS software framework, tool chain, and ground systems across a range of missions at NASA. Although NASA is focusing on the cFS, it expected that these technologies are well suited for use in other system architectures and can lower costs for a wide range of both large and small satellites.

Titan/Centaur D-1TTC-5 Helios B flight data report

NASA Technical Reports Server (NTRS)

Adams, K. A.

1976-01-01

The fourth operational flight of the newest NASA unmanned launch vehicle is reported. The spacecraft was the Helios B, the second of two solar probes designed and built by the Federal Republic of Germany. The primary mission objective, to place the Helios spacecraft on a heliocentric orbit in the ecliptic plane with a perihelion distance of 0.29 AU, was successfully accomplished. After successful injection of the Helios spacecraft, a series of experiments were performed with the Centaur stage to demonstrate its operational capabilities. All objectives of the extended mission phase were successfully met. This report presents the analysis of the launch vehicle flight data for the primary mission phase of the TC-5 flight.

Definition and testing of the hydrologic component of the pilot land data system

NASA Technical Reports Server (NTRS)

Ragan, Robert M.; Sircar, Jayanta K.

1987-01-01

The specific aim was to develop within the Pilot Land Data System (PLDS) software design environment, an easily implementable and user friendly geometric correction procedure to readily enable the georeferencing of imagery data from the Advanced Very High Resolution Radiometer (AVHRR) onboard the NOAA series spacecraft. A software subsystem was developed within the guidelines set by the PLDS development environment utilizing NASA Goddard Space Flight Center (GSFC) Image Analysis Facility's (IAF's) Land Analysis Software (LAS) coding standards. The IAS current program development environment, the Transportable Applications Executive (TAE), operates under a VAX VMS operating system and was used as the user interface. A brief overview of the ICARUS algorithm that was implemented in the set of functions developed, is provided. The functional specifications decription is provided, and a list of the individual programs and directory names containing the source and executables installed in the IAF system are listed. A user guide is provided for the LAS system documentation format for the three functions developed.

Planned flight test of a mercury ion auxiliary propulsion system. 1: Objectives, systems descriptions, and mission operations

NASA Technical Reports Server (NTRS)

Power, J. C.

1978-01-01

A planned flight test of an 8 cm diameter, electron-bombardment mercury ion thruster system is described. The primary objective of the test is to flight qualify the 5 mN (1 mlb.) thruster system for auxiliary propulsion applications. A seven year north-south stationkeeping mission was selected as the basis for the flight test operating profile. The flight test, which will employ two thruster systems, will also generate thruster system space performance data, measure thruster-spacecraft interactions, and demonstrate thruster operation in a number of operating modes. The flight test is designated as SAMSO-601 and will be flown aboard the shuttle-launched Air Force space test program P80-1 satellite in 1981. The spacecraft will be 3- axis stabilized in its final 740 km circular orbit, which will have an inclination of approximately greater than 73 degrees. The spacecraft design lifetime is three years.

Flight Avionics Hardware Roadmap

NASA Technical Reports Server (NTRS)

Some, Raphael; Goforth, Monte; Chen, Yuan; Powell, Wes; Paulick, Paul; Vitalpur, Sharada; Buscher, Deborah; Wade, Ray; West, John; Redifer, Matt;

A Flight/Ground/Test Event Logging Facility

NASA Technical Reports Server (NTRS)

Dvorak, Daniel

1999-01-01

The onboard control software for spacecraft such as Mars Pathfinder and Cassini is composed of many subsystems including executive control, navigation, attitude control, imaging, data management, and telecommunications. The software in all of these subsystems needs to be instrumented for several purposes: to report required telemetry data, to report warning and error events, to verify internal behavior during system testing, and to provide ground operators with detailed data when investigating in-flight anomalies. Events can range in importance from purely informational events to major errors. It is desirable to provide a uniform mechanism for reporting such events and controlling their subsequent processing. Since radiation-hardened flight processors are several years behind the speed and memory of their commercial cousins, and since most subsystems require real-time control, and since downlink rates to earth can be very low from deep space, there are limits to how much of the data can be saved and transmitted. Some kinds of events are more important than others and should therefore be preferentially retained when memory is low. Some faults can cause an event to recur at a high rate, but this must not be allowed to consume the memory pool. Some event occurrences may be of low importance when reported but suddenly become more important when a subsequent error event gets reported. Some events may be so low-level that they need not be saved and reported unless specifically requested by ground operators.

AFRC2017-0124-015

NASA Image and Video Library

2017-05-20

Sierra Nevada Corporation's (SNC) Dream Chaser® spacecraft shown on the runway at NASA's Armstrong Flight Research Center on May 20 preparing for a tow-test. The spacecraft is undergoing ground tests leading up to a free flight test later this year.

Executable assertions and flight software

NASA Technical Reports Server (NTRS)

Mahmood, A.; Andrews, D. M.; Mccluskey, E. J.

1984-01-01

Executable assertions are used to test flight control software. The techniques used for testing flight software; however, are different from the techniques used to test other kinds of software. This is because of the redundant nature of flight software. An experimental setup for testing flight software using executable assertions is described. Techniques for writing and using executable assertions to test flight software are presented. The error detection capability of assertions is studied and many examples of assertions are given. The issues of placement and complexity of assertions and the language features to support efficient use of assertions are discussed.

Data catalog series for space science and applications flight missions. Volume 4A: Descriptions of meteorological and terrestrial applications spacecraft and investigations

NASA Technical Reports Server (NTRS)

Ng, C. Y. (Editor); Sheu, Y. T. P. (Editor)

1985-01-01

The National Space Science Data Center (NSSDC) provides data from and information about space science and applications flight investigations in support of additional studies beyond those performed as the principal part of any flight mission. The Earth-orbiting spacecraft for investigations of the earth and its atmosphere is discussed. Geodetic tracking data are included in this category. The principal subject areas presented are meteorology and earth resources survey, and the spacecraft selection is made according to those subjects. All experiments on board the spacecraft are described. No attempt is made to reference investigations that are related to the above disciplines, but that are described in other volumes of this series.

Rosetta enters hibernation

NASA Astrophysics Data System (ADS)

Ferri, Paolo; Accomazzo, Andrea; Hubault, Armelle; Lodiot, Sylvain; Pellon-Bailon, Jose-Luis; Porta, Roberto

2012-10-01

The International Rosetta Mission was launched on 2nd March 2004 on its 10 years journey to comet 67P/Churyumov-Gerasimenko. Rosetta will reach the comet in 2014, orbit it for about 1.5 years down to distances of a few kilometres and deliver the Lander Philae onto its surface. Following the fly-by of Asteroid (21-)Lutetia in 2010, Rosetta continued its travel towards the planned comet encounter in 2014. In this phase Rosetta became the solar-powered spacecraft that reached the largest Sun distances in history of spaceflight, up to an aphelion at 5.3 AU in October 2012. At distances above 4.5 AU the spacecraft's solar generator power is not sufficient to keep all spacecraft systems active. Therefore in June 2011 the spacecraft was spun up to provide gyroscopic stabilisation, and most of its on-board units, including those used for attitude control and communications, were switched off. Over this "hibernation" phase of about 2.5 years the spacecraft will keep a minimum of autonomy active to ensure maintenance of safe thermal conditions. After Lutetia fly-by, flight controllers had to tackle two anomalies that had significant impacts on the mission operations. A leak in the reaction control subsystem was confirmed and led to the re-definition of the operational strategy to perform the comet rendezvous manoeuvres planned for 2011 and 2014. Anomalous jumps detected in the estimated friction torque of two of the four reaction wheels used for attitude control forced the rapid adoption of measures to slow down the wheels degradation. This included in-flight re-lubrication activities and changes in the wheels operational speed regime. Once the troubleshooting of the two anomalies was completed, and the related operational scenarios were implemented, the first large (790 m/s) comet rendezvous manoeuvre was executed, split into several long burns in January and February 2011. The second burn was unexpectedly interrupted due to the anomalous behaviour of two thrusters, causing attitude off-pointing. Flight controllers modified the thrusters operation parameters in the on-board software and managed to re-start the sequence of burns and successfully complete the manoeuvre. After the manoeuvre, preparation for the critical spin-up and hibernation entry activities, planned for June 2011, began. This paper presents the activities carried out on Rosetta in the final year before hibernation entry. The major anomalies and the related troubleshooting and workaround solutions are detailed. Lessons learned from the operation of the first spacecraft operating with solar power at Jupiter-like distances from the Sun are presented and discussed.

Viking lander spacecraft battery

NASA Technical Reports Server (NTRS)

Newell, D. R.

1976-01-01

The Viking Lander was the first spacecraft to fly a sterilized nickel-cadmium battery on a mission to explore the surface of a planet. The significant results of the battery development program from its inception through the design, manufacture, and test of the flight batteries which were flown on the two Lander spacecraft are documented. The flight performance during the early phase of the mission is also presented.

IUS solid rocket motor contamination prediction methods

NASA Technical Reports Server (NTRS)

Mullen, C. R.; Kearnes, J. H.

1980-01-01

A series of computer codes were developed to predict solid rocket motor produced contamination to spacecraft sensitive surfaces. Subscale and flight test data have confirmed some of the analytical results. Application of the analysis tools to a typical spacecraft has provided early identification of potential spacecraft contamination problems and provided insight into their solution; e.g., flight plan modifications, plume or outgassing shields and/or contamination covers.

Viking Lander spacecraft battery. Final report

DOE Office of Scientific and Technical Information (OSTI.GOV)

Newell, D.R.

1976-09-01

The Viking Lander was the first spacecraft to fly a sterilized nickel--cadmium battery on a mission to explore the surface of a planet. The significant results of the battery development program from its inception through the design, manufacture, and test of the flight batteries which were flown on the two Lander spacecraft are documented. The flight performance during the early phase of the mission is also presented.

Network Monitor and Control of Disruption-Tolerant Networks

NASA Technical Reports Server (NTRS)

Torgerson, J. Leigh

2014-01-01

For nearly a decade, NASA and many researchers in the international community have been developing Internet-like protocols that allow for automated network operations in networks where the individual links between nodes are only sporadically connected. A family of Disruption-Tolerant Networking (DTN) protocols has been developed, and many are reaching CCSDS Blue Book status. A NASA version of DTN known as the Interplanetary Overlay Network (ION) has been flight-tested on the EPOXI spacecraft and ION is currently being tested on the International Space Station. Experience has shown that in order for a DTN service-provider to set up a large scale multi-node network, a number of network monitor and control technologies need to be fielded as well as the basic DTN protocols. The NASA DTN program is developing a standardized means of querying a DTN node to ascertain its operational status, known as the DTN Management Protocol (DTNMP), and the program has developed some prototypes of DTNMP software. While DTNMP is a necessary component, it is not sufficient to accomplish Network Monitor and Control of a DTN network. JPL is developing a suite of tools that provide for network visualization, performance monitoring and ION node control software. This suite of network monitor and control tools complements the GSFC and APL-developed DTN MP software, and the combined package can form the basis for flight operations using DTN.

NASA Tech Briefs, January 2014

NASA Technical Reports Server (NTRS)

2014-01-01

Topics include: Multi-Source Autonomous Response for Targeting and Monitoring of Volcanic Activity; Software Suite to Support In-Flight Characterization of Remote Sensing Systems; Visual Image Sensor Organ Replacement; Ultra-Wideband, Dual-Polarized, Beam-Steering P-Band Array Antenna; Centering a DDR Strobe in the Middle of a Data Packet; Using a Commercial Ethernet PHY Device in a Radiation Environment; Submerged AUV Charging Station; Habitat Demonstration Unit (HDU) Vertical Cylinder Habitat; Origami-Inspired Folding of Thick, Rigid Panels; A Novel Protocol for Decoating and Permeabilizing Bacterial Spores for Epifluorescent Microscopy; Method and Apparatus for Automated Isolation of Nucleic Acids from Small Cell Samples; Enabling Microliquid Chromatography by Microbead Packing of Microchannels; On-Command Force and Torque Impeding Devices (OC-FTID) Using ERF; Deployable Fresnel Rings; Transition-Edge Hot-Electron Microbolometers for Millimeter and Submillimeter Astrophysics; Spacecraft Trajectory Analysis and Mission Planning Simulation (STAMPS) Software; Cross Support Transfer Service (CSTS) Framework Library; Arbitrary Shape Deformation in CFD Design; Range Safety Flight Elevation Limit Calculation Software; Frequency-Modulated, Continuous-Wave Laser Ranging Using Photon-Counting Detectors; Calculation of Operations Efficiency Factors for Mars Surface Missions; GPU Lossless Hyperspectral Data Compression System; Robust, Optimal Subsonic Airfoil Shapes; Protograph-Based Raptor-Like Codes; Fuzzy Neuron: Method and Hardware Realization; Kalman Filter Input Processor for Boresight Calibration; Organizing Compression of Hyperspectral Imagery to Allow Efficient Parallel Decompression; and Temperature Dependences of Mechanisms Responsible for the Water-Vapor Continuum Absorption.

KSC-98pc1189

NASA Image and Video Library

1998-09-30

KENNEDY SPACE CENTER, FLA. -- Deep Space 1 rests on its work platform after being fitted with thermal insulation. The reflective insulation is designed to protect the spacecraft as this side faces the sun. At either side of the spacecraft are its solar wings, folded for launch. When fully extended, the wings measure 38.6 feet from tip to tip. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non-chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. Deep Space 1 will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches

Clementine mission

NASA Astrophysics Data System (ADS)

Rustan, Pedro L.

1995-01-01

The U.S. Department of Defense (DoD) and the National Aeronautics and Space Administration (NASA) started a cooperative program in 1992 to flight qualify recently developed lightweight technologies in a radiation stressed environment. The spacecraft, referred to as Clementine, was designed, built, and launched in less than a two year period. The spacecraft was launched into a high inclination orbit from Vandenburg Air Force Base in California on a Titan IIG launch vehicle in January 1994. The spacecraft was injected into a 420 by 3000 km orbit around the Moon and remained there for over two months. Unfortunately, after successfully completing the Lunar phase of the mission, a software malfunction prevented the accomplishment of the near-Earth asteroid (NEA) phase. Some of the technologies incorporated in the Clementine spacecraft include: a 370 gram, 7 watt star tracker camera; a 500 gram, 6 watt, UV/Vis camera; a 1600 gram, 30 watt Indium Antimonide focal plane array NIR camera; a 1650 gram, 30 watt, Mercury Cadmium Telluride LWIR camera; a LIDAR camera which consists of a Nd:YAG diode pumped laser for ranging and an intensified photocathode charge-coupled detector for imaging. The scientific results of the mission will be first analyzed by a NASA selected team, and then will be available to the entire community.

KSC-98pc1190

NASA Image and Video Library

1998-09-30

KENNEDY SPACE CENTER, FLA. -- Deep Space 1 rests on its work platform after being fitted with thermal insulation. The dark insulation is designed to protect the side of the spacecraft that faces away from the sun. At either side of the spacecraft are its solar wings, folded for launch. When fully extended, the wings measure 38.6 feet from tip to tip. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non-chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. Deep Space 1 will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches

Proposed data compression schemes for the Galileo S-band contingency mission

NASA Technical Reports Server (NTRS)

Cheung, Kar-Ming; Tong, Kevin

1993-01-01

The Galileo spacecraft is currently on its way to Jupiter and its moons. In April 1991, the high gain antenna (HGA) failed to deploy as commanded. In case the current efforts to deploy the HGA fails, communications during the Jupiter encounters will be through one of two low gain antenna (LGA) on an S-band (2.3 GHz) carrier. A lot of effort has been and will be conducted to attempt to open the HGA. Also various options for improving Galileo's telemetry downlink performance are being evaluated in the event that the HGA will not open at Jupiter arrival. Among all viable options the most promising and powerful one is to perform image and non-image data compression in software onboard the spacecraft. This involves in-flight re-programming of the existing flight software of Galileo's Command and Data Subsystem processors and Attitude and Articulation Control System (AACS) processor, which have very limited computational and memory resources. In this article we describe the proposed data compression algorithms and give their respective compression performance. The planned image compression algorithm is a 4 x 4 or an 8 x 8 multiplication-free integer cosine transform (ICT) scheme, which can be viewed as an integer approximation of the popular discrete cosine transform (DCT) scheme. The implementation complexity of the ICT schemes is much lower than the DCT-based schemes, yet the performances of the two algorithms are indistinguishable. The proposed non-image compression algorith is a Lempel-Ziv-Welch (LZW) variant, which is a lossless universal compression algorithm based on a dynamic dictionary lookup table. We developed a simple and efficient hashing function to perform the string search.

Saturn 5 Launch Vehicle Flight Evaluation Report, AS-510, Apollo 15 Mission

NASA Technical Reports Server (NTRS)

1971-01-01

A postflight analysis of the Apollo 15 flight is presented. The performance of the launch vehicle, spacecraft, and lunar roving vehicle are discussed. The objective of the evaluation is to acquire, reduce, analyze, and report on flight data to the extent required to assure future mission success and vehicle reliability. Actual flight problems are identified, their causes are determined, and recommendations are made for corrective actions. Summaries of launch operations and spacecraft performance are included. Significant events for all phases of the flight are tabulated.

Internet Technology on Spacecraft

NASA Technical Reports Server (NTRS)

Rash, James; Parise, Ron; Hogie, Keith; Criscuolo, Ed; Langston, Jim; Powers, Edward I. (Technical Monitor)

2000-01-01

The Operating Missions as Nodes on the Internet (OMNI) project has shown that Internet technology works in space missions through a demonstration using the UoSAT-12 spacecraft. An Internet Protocol (IP) stack was installed on the orbiting UoSAT-12 spacecraft and tests were run to demonstrate Internet connectivity and measure performance. This also forms the basis for demonstrating subsequent scenarios. This approach provides capabilities heretofore either too expensive or simply not feasible such as reconfiguration on orbit. The OMNI project recognized the need to reduce the risk perceived by mission managers and did this with a multi-phase strategy. In the initial phase, the concepts were implemented in a prototype system that includes space similar components communicating over the TDRS (space network) and the terrestrial Internet. The demonstration system includes a simulated spacecraft with sample instruments. Over 25 demonstrations have been given to mission and project managers, National Aeronautics and Space Administration (NASA), Department of Defense (DoD), contractor technologists and other decisions makers, This initial phase reached a high point with an OMNI demonstration given from a booth at the Johnson Space Center (JSC) Inspection Day 99 exhibition. The proof to mission managers is provided during this second phase with year 2000 accomplishments: testing the use of Internet technologies onboard an actual spacecraft. This was done with a series of tests performed using the UoSAT-12 spacecraft. This spacecraft was reconfigured on orbit at very low cost. The total period between concept and the first tests was only 6 months! On board software was modified to add an IP stack to support basic IP communications. Also added was support for ping, traceroute and network timing protocol (NTP) tests. These tests show that basic Internet functionality can be used onboard spacecraft. The performance of data was measured to show no degradation from current approaches. The cost to implement is much less than current approaches due to the availability of highly reliable and standard Internet tools. Use of standard Internet applications onboard reduces the risk of obsolescence inherent in custom protocols due to extremely wide use across all domains. These basic building blocks provide the framework for building onboard software to support direct user communication with payloads including payload control. Other benefits are payload to payload communication from dissimilar spacecraft, constellations of spacecraft, and reconfigurability on orbit. This work is funded through contract with the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC).

Deep Space 1 is prepared for transport to launch pad

NASA Technical Reports Server (NTRS)

1998-01-01

Wrapped in an anti-static blanket for protection, Deep Space 1 is moved out of the Defense Satellite Communications Systems Processing Facility (DPF) at Cape Canaveral Air Station (CCAS) for its trip to Launch Pad 17A. The spacecraft will be launched aboard a Boeing Delta 7326 rocket on Oct. 25. Deep Space 1 is the first flight in NASA's New Millennium Program, and is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

Deep Space 1 is prepared for transport to launch pad

NASA Technical Reports Server (NTRS)

1998-01-01

In the Defense Satellite Communications Systems Processing Facility (DPF), Cape Canaveral Air Station (CCAS), workers place an anti-static blanket over the lower portion of Deep Space 1, to protect the spacecraft during transport to the launch pad. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. Deep Space 1 will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, CCAS.

Deep Space 1 is prepared for transport to launch pad

NASA Technical Reports Server (NTRS)

1998-01-01

In the Defense Satellite Communications Systems Processing Facility (DPF), Cape Canaveral Air Station (CCAS), after covering the lower portion of Deep Space 1, workers adjust the anti-static blanket covering the upper portion. The blanket will protect the spacecraft during transport to the launch pad. Deep Space 1 is the first flight in NASA's New Millennium Program, and is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. Deep Space 1 will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, CCAS.

Deep Space 1 is prepared for transport to launch pad

NASA Technical Reports Server (NTRS)

1998-01-01

In the Defense Satellite Communications Systems Processing Facility (DPF), Cape Canaveral Air Station (CCAS), the lower part of Deep Space 1 is enclosed with the conical section leaves of the payload transportation container prior to its move to Launch Pad 17A. The spacecraft is targeted for launch Oct. 25 aboard a Boeing Delta 7326 rocket. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

KSC-98pc1316

NASA Image and Video Library

1998-10-10

KENNEDY SPACE CENTER, FLA. -- In the Defense Satellite Communications Systems Processing Facility (DPF), Cape Canaveral Air Station (CCAS), after covering the lower portion of Deep Space 1, workers adjust the anti-static blanket covering the upper portion. The blanket will protect the spacecraft during transport to the launch pad. Deep Space 1 is the first flight in NASA's New Millennium Program, and is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. Deep Space 1 will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, CCAS

KSC-98pc1315

NASA Image and Video Library

1998-10-10

KENNEDY SPACE CENTER, FLA. -- In the Defense Satellite Communications Systems Processing Facility (DPF), Cape Canaveral Air Station (CCAS), the lower part of Deep Space 1 is enclosed with the conical section leaves of the payload transportation container prior to its move to Launch Pad 17A. The spacecraft is targeted for launch Oct. 25 aboard a Boeing Delta 7326 rocket. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999

KSC-98pc1317

NASA Image and Video Library

1998-10-10

KENNEDY SPACE CENTER, FLA. -- In the Defense Satellite Communications Systems Processing Facility (DPF), Cape Canaveral Air Station (CCAS), workers place an anti-static blanket over the lower portion of Deep Space 1, to protect the spacecraft during transport to the launch pad. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century, including the engine. Propelled by the gas xenon, the engine is being flight-tested for future deep space and Earth-orbiting missions. Deceptively powerful, the ion drive emits only an eerie blue glow as ionized atoms of xenon are pushed out of the engine. While slow to pick up speed, over the long haul it can deliver 10 times as much thrust per pound of fuel as liquid or solid fuel rockets. Other onboard experiments include software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. Deep Space 1 will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, CCAS

Attitude Design for the LADEE Mission

NASA Technical Reports Server (NTRS)

Galal, Ken; Nickel, Craig; Sherman, Ryan

2015-01-01

The Lunar Atmosphere and Dust Environment Explorer (LADEE) satellite successfully completed its 148-day science investigation in a low-altitude, near-equatorial lunar orbit on April 18, 2014. The LADEE spacecraft was built, managed and operated by NASA's Ames Research Center (ARC). The Mission Operations Center (MOC) was located at Ames and was responsible for activity planning, command sequencing, trajectory and attitude design, orbit determination, and spacecraft operations. The Science Operations Center (SOC) was located at Goddard Space Flight Center and was responsible for science planning, data archiving and distribution. This paper details attitude design and operations support for the LADEE mission. LADEE's attitude design was shaped by a wide range of instrument pointing requirements that necessitated regular excursions from the baseline one revolution per orbit "Ram" attitude. Such attitude excursions were constrained by a number of flight rules levied to protect instruments from the Sun, avoid geometries that would result in simultaneous occlusion of LADEE's two star tracker heads, and maintain the spacecraft within its thermal and power operating limits. To satisfy LADEE's many attitude requirements and constraints, a set of rules and conventions was adopted to manage the complexity of this design challenge and facilitate the automation of ground software that generated pointing commands spanning multiple days of operations at a time. The resulting LADEE Flight Dynamics System (FDS) that was developed used Visual Basic scripts that generated instructions to AGI's Satellite Tool Kit (STK) in order to derive quaternion commands at regular intervals that satisfied LADEE's pointing requirements. These scripts relied heavily on the powerful "align and constrain" capability of STK's attitude module to construct LADEE's attitude profiles and the slews to get there. A description of the scripts and the attitude modeling they embodied is provided. One particular challenge analysts faced was in the design of LADEE maneuver attitudes. A flight rule requiring pre-maneuver verification of in-flight maneuver conditions by ground operators prior to burn execution resulted in the need to accommodate long periods in the maneuver attitude. This in turn complicated efforts to satisfy star tracker interference and communication constraints in lunar orbit. In response to this challenge, a graphical method was developed and used to survey candidate rotation angles about the thrust vector. This survey method is described and an example of its use on a particular LADEE maneuver is discussed. Finally, the software and methodology used to satisfy LADEE's attitude requirements are also discussed in the context of LADEE's overall activity planning effort. In particular, the way in which strategic schedules of instrument and engineering activities were translated into actual attitude profiles at the tactical level, then converted into precise quaternion commands to achieve those pointing goals is explained. In order to reduce the risk of time-consuming re-planning efforts, this process included the generation of long-term projections of constraint violation predictions for individual attitude profiles that could be used to establish keep-out time-frames for particular attitude profiles. The challenges experienced and overall efficacy of both the overall LADEE ground system and the attitude components of the Flight Dynamics System in meeting LADEE's varied pointing requirements are discussed.

Observation Scheduling System

NASA Technical Reports Server (NTRS)

Chien, Steve A.; Tran, Daniel Q.; Rabideau, Gregg R.; Schaffer, Steven R.

2011-01-01

Software has been designed to schedule remote sensing with the Earth Observing One spacecraft. The software attempts to satisfy as many observation requests as possible considering each against spacecraft operation constraints such as data volume, thermal, pointing maneuvers, and others. More complex constraints such as temperature are approximated to enable efficient reasoning while keeping the spacecraft within safe limits. Other constraints are checked using an external software library. For example, an attitude control library is used to determine the feasibility of maneuvering between pairs of observations. This innovation can deal with a wide range of spacecraft constraints and solve large scale scheduling problems like hundreds of observations and thousands of combinations of observation sequences.

Radioastron flight operations

NASA Technical Reports Server (NTRS)

Altunin, V. I.; Sukhanov, K. G.; Altunin, K. R.

1993-01-01

Radioastron is a space-based very-long-baseline interferometry (VLBI) mission to be operational in the mid-90's. The spacecraft and space radio telescope (SRT) will be designed, manufactured, and launched by the Russians. The United States is constructing a DSN subnet to be used in conjunction with a Russian subnet for Radioastron SRT science data acquisition, phase link, and spacecraft and science payload health monitoring. Command and control will be performed from a Russian tracking facility. In addition to the flight element, the network of ground radio telescopes which will be performing co-observations with the space telescope are essential to the mission. Observatories in 39 locations around the world are expected to participate in the mission. Some aspects of the mission that have helped shaped the flight operations concept are: separate radio channels will be provided for spacecraft operations and for phase link and science data acquisition; 80-90 percent of the spacecraft operational time will be spent in an autonomous mode; and, mission scheduling must take into account not only spacecraft and science payload constraints, but tracking station and ground observatory availability as well. This paper will describe the flight operations system design for translating the Radioastron science program into spacecraft executed events. Planning for in-orbit checkout and contingency response will also be discussed.

Satellite Ground Operations Automation: Lessons Learned and Future Approaches

NASA Technical Reports Server (NTRS)

Catena, John; Frank, Lou; Saylor, Rick; Weikel, Craig; Obenschain, Arthur F. (Technical Monitor)

2001-01-01

Reducing spacecraft ground system operations costs is a major goal in all missions. The Fast Auroral Snapshot (FAST) flight operations team at the NASA/Goddard Spacecraft Flight Center developed in-house scripts and procedures to automate monitoring of critical spacecraft functions. The initial staffing profile of 16x7 was reduced first to 8x5 and then to 'lights out'. Operations functions became an offline review of system performance and the generation of future science plans for subsequent upload to the spacecraft. Lessons learned will be applied to the challenging Triana mission, where 24x7 contact with the spacecraft will be necessary at all times.

Gemini-Titan 3 spacecraft in water after flight

NASA Technical Reports Server (NTRS)

1965-01-01

The Gemini-Titan 3 spacecraft is shown in the water after the March 23rd four hour and 53 minute flight. Two helicopters from the recovery ship, the U.S.S. Intrepid, hover over the scene for the pickup of the astronauts.

A gamma ray observatory ground attitude error analysis study using the generalized calibration system

NASA Technical Reports Server (NTRS)

Ketchum, E.

1988-01-01

The Goddard Space Flight Center (GSFC) Flight Dynamics Division (FDD) will be responsible for performing ground attitude determination for Gamma Ray Observatory (GRO) support. The study reported in this paper provides the FDD and the GRO project with ground attitude determination error information and illustrates several uses of the Generalized Calibration System (GCS). GCS, an institutional software tool in the FDD, automates the computation of the expected attitude determination uncertainty that a spacecraft will encounter during its mission. The GRO project is particularly interested in the uncertainty in the attitude determination using Sun sensors and a magnetometer when both star trackers are inoperable. In order to examine the expected attitude errors for GRO, a systematic approach was developed including various parametric studies. The approach identifies pertinent parameters and combines them to form a matrix of test runs in GCS. This matrix formed the basis for this study.

Failure rate analysis of Goddard Space Flight Center spacecraft performance during orbital life

NASA Technical Reports Server (NTRS)

Norris, H. P.; Timmins, A. R.

1976-01-01

Space life performance data on 57 Goddard Space Flight Center spacecraft are analyzed from the standpoint of determining an appropriate reliability model and the associated reliability parameters. Data from published NASA reports, which cover the space performance of GSFC spacecraft launched in the 1960-1970 decade, form the basis of the analyses. The results of the analyses show that the time distribution of 449 malfunctions, of which 248 were classified as failures (not necessarily catastrophic), follow a reliability growth pattern that can be described with either the Duane model or a Weibull distribution. The advantages of both mathematical models are used in order to: identify space failure rates, observe chronological trends, and compare failure rates with those experienced during the prelaunch environmental tests of the flight model spacecraft.

SCL: An off-the-shelf system for spacecraft control

NASA Astrophysics Data System (ADS)

Buckley, Brian; Vangaasbeck, James

1994-11-01

In this age of shrinking military, civil, and commercial space budgets, an off-the-shelf solution is needed to provide a multimission approach to spacecraft control. A standard operational interface which can be applied to multiple spacecraft allows a common approach to ground and space operations. A trend for many space programs has been to reduce operational staff by applying autonomy to the spacecraft and to the ground stations. The Spacecraft Command Language (SCL) system developed by Interface and Control Systems, Inc. (ICS) provides an off-the-shelf solution for spacecraft operations. The SCL system is designed to provide a hyper-scripting interface which remains standard from program to program. The spacecraft and ground station hardware specifics are isolated to provide the maximum amount of portability from system to system. Uplink and downlink interfaces are also isolated to allow the system to perform independent of the communications protocols chosen. The SCL system can be used for both the ground stations and the spacecraft, or as a value added package for existing ground station environments. The SCL system provides an expanded stored commanding capability as well as a rule-based expert system on-board. The expert system allows reactive control on-board the spacecraft for functions such as electrical power systems (EPS), thermal control, etc. which have traditionally been performed on the ground. The SCL rule and scripting capability share a common syntax allowing control of scripts from rules and rules from scripts. Rather than telemeter over sampled data to the ground, the SCL system maintains a database on-board which is available for interrogation by the scripts and rules. The SCL knowledge base is constructed on the ground and uploaded to the spacecraft. The SCL system follows an open-systems approach allowing other tasks to communicate with SCL on the ground and in space. The SCL system was used on the Clementine program (launched January 25, 1994) and is required to have bidirectional communications with the guidance, navigation, and control (GNC) algorithms which were written as another task. Sequencing of the spacecraft maneuvers are handled by SCL, but the low-level thruster pulse commands are handled by the GNC software. Attitude information is reported back as telemetry, allowing the SCL expert system to inference on the changing data. The Clementine SCL flight software was largely reused from another Naval Center for Space Technology (NCST) satellite program.

SCL: An off-the-shelf system for spacecraft control

NASA Technical Reports Server (NTRS)

Buckley, Brian; Vangaasbeck, James

1994-01-01

In this age of shrinking military, civil, and commercial space budgets, an off-the-shelf solution is needed to provide a multimission approach to spacecraft control. A standard operational interface which can be applied to multiple spacecraft allows a common approach to ground and space operations. A trend for many space programs has been to reduce operational staff by applying autonomy to the spacecraft and to the ground stations. The Spacecraft Command Language (SCL) system developed by Interface and Control Systems, Inc. (ICS) provides an off-the-shelf solution for spacecraft operations. The SCL system is designed to provide a hyper-scripting interface which remains standard from program to program. The spacecraft and ground station hardware specifics are isolated to provide the maximum amount of portability from system to system. Uplink and downlink interfaces are also isolated to allow the system to perform independent of the communications protocols chosen. The SCL system can be used for both the ground stations and the spacecraft, or as a value added package for existing ground station environments. The SCL system provides an expanded stored commanding capability as well as a rule-based expert system on-board. The expert system allows reactive control on-board the spacecraft for functions such as electrical power systems (EPS), thermal control, etc. which have traditionally been performed on the ground. The SCL rule and scripting capability share a common syntax allowing control of scripts from rules and rules from scripts. Rather than telemeter over sampled data to the ground, the SCL system maintains a database on-board which is available for interrogation by the scripts and rules. The SCL knowledge base is constructed on the ground and uploaded to the spacecraft. The SCL system follows an open-systems approach allowing other tasks to communicate with SCL on the ground and in space. The SCL system was used on the Clementine program (launched January 25, 1994) and is required to have bidirectional communications with the guidance, navigation, and control (GNC) algorithms which were written as another task. Sequencing of the spacecraft maneuvers are handled by SCL, but the low-level thruster pulse commands are handled by the GNC software. Attitude information is reported back as telemetry, allowing the SCL expert system to inference on the changing data. The Clementine SCL flight software was largely reused from another Naval Center for Space Technology (NCST) satellite program. This paper details the SCL architecture and how an off-the-shelf solution makes sense for multimission spacecraft programs. The Clementine mission will be used as a case study in the application of the SCL to a 'fast track' program. The benefits of such a system in a 'better, cheaper, faster' climate will be discussed.

Rapid Development of Orion Structural Test Systems

NASA Astrophysics Data System (ADS)

Baker, Dave

2012-07-01

NASA is currently validating the Orion spacecraft design for human space flight. Three systems developed by G Systems using hardware and software from National Instruments play an important role in the testing of the new Multi- purpose crew vehicle (MPCV). A custom pressurization and venting system enables engineers to apply pressure inside the test article for measuring strain. A custom data acquisition system synchronizes over 1,800 channels of analog data. This data, along with multiple video and audio streams and calculated data, can be viewed, saved, and replayed in real-time on multiple client stations. This paper presents design features and how the system works together in a distributed fashion.

Deep Space 1 is prepared for launch

NASA Technical Reports Server (NTRS)

1998-01-01

Workers in the Payload Hazardous Servicing Facility test equipment on Deep Space 1 to prepare it for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near-Earth asteroid, 1992 KD, has also been selected for a possible flyby.

Deep Space 1 is prepared for launch

NASA Technical Reports Server (NTRS)

1998-01-01

Workers in the Payload Hazardous Servicing Facility check equipment on Deep Space 1 to prepare it for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near-Earth asteroid, 1992 KD, has also been selected for a possible flyby.

AVID - A design system for technology studies of advanced transportation concepts. [Aerospace Vehicle Interactive Design

NASA Technical Reports Server (NTRS)

Wilhite, A. W.; Rehder, J. J.

1979-01-01

The basic AVID (Aerospace Vehicle Interactive Design) is a general system for conceptual and preliminary design currently being applied to a broad range of future space transportation and spacecraft vehicle concepts. AVID hardware includes a minicomputer allowing rapid designer interaction. AVID software includes (1) an executive program and communication data base which provide the automated capability to couple individual programs, either individually in an interactive mode or chained together in an automatic sequence mode; and (2) the individual technology and utility programs which provide analysis capability in areas such as graphics, aerodynamics, propulsion, flight performance, weights, sizing, and costs.

Large autonomous spacecraft electrical power system (LASEPS)

NASA Technical Reports Server (NTRS)

Dugal-Whitehead, Norma R.; Johnson, Yvette B.

1992-01-01

NASA - Marshall Space Flight Center is creating a large high voltage electrical power system testbed called LASEPS. This testbed is being developed to simulate an end-to-end power system from power generation and source to loads. When the system is completed it will have several power configurations, which will include several battery configurations. These configurations are: two 120 V batteries, one or two 150 V batteries, and one 250 to 270 V battery. This breadboard encompasses varying levels of autonomy from remote power converters to conventional software control to expert system control of the power system elements. In this paper, the construction and provisions of this breadboard are discussed.

Deep Space 1 is prepared for launch

NASA Technical Reports Server (NTRS)

1998-01-01

Workers in the Payload Hazardous Servicing Facility remove a solar panel from Deep Space 1 as part of the preparations for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near- Earth asteroid, 1992 KD, has also been selected for a possible flyby.

Deep Space 1 is prepared for launch

NASA Technical Reports Server (NTRS)

1998-01-01

Workers in the Payload Hazardous Servicing Facility check out Deep Space 1 to prepare it for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near-Earth asteroid, 1992 KD, has also been selected for a possible flyby.

Development of Autonomous Aerobraking (Phase 1)

NASA Technical Reports Server (NTRS)

Murri, Daniel G.; Powell, Richard W.; Prince, Jill L.

2012-01-01

The NASA Engineering and Safety Center received a request from Mr. Daniel Murri (NASA Technical Fellow for Flight Mechanics) to develop an autonomous aerobraking capability. An initial evaluation for all phases of this assessment was approved to proceed at the NESC Review Board meeting. The purpose of phase 1 of this study was to provide an assessment of the feasibility of autonomous aerobraking. During this phase, atmospheric, aerodynamic, and thermal models for a representative spacecraft were developed for both the onboard algorithm known as Autonomous Aerobraking Development Software, and a ground-based "truth" simulation developed for testing purposes. The results of the phase 1 assessment are included in this report.

KSC-98pc1088

NASA Image and Video Library

1998-09-17

KENNEDY SPACE CENTER, FLA. -- Workers in the Payload Hazardous Servicing Facility remove a solar panel from Deep Space 1 as part of the preparations for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near-Earth asteroid, 1992 KD, has also been selected for a possible flyby

KSC-98pc1090

NASA Image and Video Library

1998-09-17

KENNEDY SPACE CENTER, FLA. -- Workers in the Payload Hazardous Servicing Facility check equipment on Deep Space 1 to prepare it for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near-Earth asteroid, 1992 KD, has also been selected for a possible flyby

KSC-98pc1089

NASA Image and Video Library

1998-09-17

KENNEDY SPACE CENTER, FLA. -- Workers in the Payload Hazardous Servicing Facility check out Deep Space 1 to prepare it for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near-Earth asteroid, 1992 KD, has also been selected for a possible flyby

KSC-98pc1091

NASA Image and Video Library

1998-09-17

KENNEDY SPACE CENTER, FLA. -- Workers in the Payload Hazardous Servicing Facility test equipment on Deep Space 1 to prepare it for launch aboard a Boeing Delta 7326 rocket in October. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Most of its mission objectives will be completed within the first two months. A near-Earth asteroid, 1992 KD, has also been selected for a possible flyby

Nimbus/TOMS Science Data Operations Support

NASA Technical Reports Server (NTRS)

Childs, Jeff

1998-01-01

1. Participate in and provide analysis of laboratory and in-flight calibration of UV sensors used for space observations of backscattered UV radiation. 2. Provide support to the TOMS Science Operations Center, including generating instrument command lists and analysis of TOMS health and safety data. 3. Develop and maintain software and algorithms designed to capture and process raw spacecraft and instrument data, convert the instrument output into measured radiance and irradiances, and produce scientifically valid products. 4. Process the TOMS data into Level 1, Level 2, and Level 3 data products. 5. Provide analysis of the science data products in support of NASA GSFC Code 916's research.

Nimbus/TOMS Science Data Operations Support

NASA Technical Reports Server (NTRS)

1998-01-01

Projected goals include the following: (1) Participate in and provide analysis of laboratory and in-flight calibration of LTV sensors used for space observations of backscattered LTV radiation; (2) Provide support to the TOMS Science Operations Center, including generating instrument command lists and analysis of TOMS health and safety data; (3) Develop and maintain software and algorithms designed to capture and process raw spacecraft and instrument data, convert the instrument output into measured radiance and irradiances, and produce scientifically valid products; (4) Process the TOMS data into Level 1, Level 2, and Level 3 data products; (5) Provide analysis of the science data products in support of NASA GSFC Code 916's research.

Guidance and Navigation Software Architecture Design for the Autonomous Multi-Agent Physically Interacting Spacecraft (AMPHIS) Test Bed

DTIC Science & Technology

2006-12-01

NAVIGATION SOFTWARE ARCHITECTURE DESIGN FOR THE AUTONOMOUS MULTI-AGENT PHYSICALLY INTERACTING SPACECRAFT (AMPHIS) TEST BED by Blake D. Eikenberry...Engineer Degree 4. TITLE AND SUBTITLE Guidance and Navigation Software Architecture Design for the Autonomous Multi- Agent Physically Interacting...iii Approved for public release; distribution is unlimited GUIDANCE AND NAVIGATION SOFTWARE ARCHITECTURE DESIGN FOR THE AUTONOMOUS MULTI

Method of interplanetary trajectory optimization for the spacecraft with low thrust and swing-bys

NASA Astrophysics Data System (ADS)

Konstantinov, M. S.; Thein, M.

2017-07-01

The method developed to avoid the complexity of solving the multipoint boundary value problem while optimizing interplanetary trajectories of the spacecraft with electric propulsion and a sequence of swing-bys is presented in the paper. This method is based on the use of the preliminary problem solutions for the impulsive trajectories. The preliminary problem analyzed at the first stage of the study is formulated so that the analysis and optimization of a particular flight path is considered as the unconstrained minimum in the space of the selectable parameters. The existing methods can effectively solve this problem and make it possible to identify rational flight paths (the sequence of swing-bys) to receive the initial approximation for the main characteristics of the flight path (dates, values of the hyperbolic excess velocity, etc.). These characteristics can be used to optimize the trajectory of the spacecraft with electric propulsion. The special feature of the work is the introduction of the second (intermediate) stage of the research. At this stage some characteristics of the analyzed flight path (e.g. dates of swing-bys) are fixed and the problem is formulated so that the trajectory of the spacecraft with electric propulsion is optimized on selected sites of the flight path. The end-to-end optimization is carried out at the third (final) stage of the research. The distinctive feature of this stage is the analysis of the full set of optimal conditions for the considered flight path. The analysis of the characteristics of the optimal flight trajectories to Jupiter with Earth, Venus and Mars swing-bys for the spacecraft with electric propulsion are presented. The paper shows that the spacecraft weighing more than 7150 kg can be delivered into the vicinity of Jupiter along the trajectory with two Earth swing-bys by use of the space transportation system based on the "Angara A5" rocket launcher, the chemical upper stage "KVTK" and the electric propulsion system with input electrical power of 100 kW.

Evaluation of calibration accuracy of magnetometer sensors of Aist small spacecraft

NASA Astrophysics Data System (ADS)

Sedelnikov, A. V.; Filippov, A. S.; Gorozhakina, A. S.

2018-05-01

In the paper the technique of estimation of calibration accuracy of magnetometer gauges by the example of an Aist small spacecraft is stated. According to the measurement of the Earth's magnetic field in the orbital flight of a small spacecraft, the parameters of its rotational motion around the center of mass are estimated and primary information is generated for the magnetic actuators of the orbital motion control system. Therefore, calibration of the magnetometer sensors at the ground test stage is essential for the successful execution of the flight program. The technique can be used at the stages of ground and flight tests of magnetic field measuring instruments.

Planned flight test of a mercury ion auxiliary propulsion system. Part 2: Integration with host spacecraft

NASA Technical Reports Server (NTRS)

Knight, R. M.

1978-01-01

The objectives of the flight test and a description on how those objectives are in support of an overall program goal of attaining user application were described. The approach to accomplishment was presented as it applies to integrating the propulsion system with the host spacecraft. A number of known interface design considerations which affect the propulsion system and the spacecraft were discussed. Analogies were drawn comparing the relationship of the organizations involved with this flight test with those anticipated for future operational missions. The paper also expanded upon objectives, system description, mission operations, and measurement of plume effects.

Computer Software Configuration Item-Specific Flight Software Image Transfer Script Generator

NASA Technical Reports Server (NTRS)

Bolen, Kenny; Greenlaw, Ronald

2010-01-01

A K-shell UNIX script enables the International Space Station (ISS) Flight Control Team (FCT) operators in NASA s Mission Control Center (MCC) in Houston to transfer an entire or partial computer software configuration item (CSCI) from a flight software compact disk (CD) to the onboard Portable Computer System (PCS). The tool is designed to read the content stored on a flight software CD and generate individual CSCI transfer scripts that are capable of transferring the flight software content in a given subdirectory on the CD to the scratch directory on the PCS. The flight control team can then transfer the flight software from the PCS scratch directory to the Electronically Erasable Programmable Read Only Memory (EEPROM) of an ISS Multiplexer/ Demultiplexer (MDM) via the Indirect File Transfer capability. The individual CSCI scripts and the CSCI Specific Flight Software Image Transfer Script Generator (CFITSG), when executed a second time, will remove all components from their original execution. The tool will identify errors in the transfer process and create logs of the transferred software for the purposes of configuration management.

Magellan attitude control mission operations

NASA Technical Reports Server (NTRS)

Dukes, Eileen M.

1993-01-01

From the Martin Marietta Astronautics Group base in Denver, Colorado, spacecraft engineers have been operating the Magellan spacecraft for the past three and one half years, along with the Jet Propulsion Laboratory, for NASA. The spacecraft team in Denver is responsible for the health of the vehicle, from command generation to evaluation of engineering telemetry. Operation of the spacecraft's Attitude and Articulation Control Subsystem (AACS) has specifically posed several in-flight challenges. This system must provide accurate pointing of the spacecraft throughout each 3.2 hour orbit which typically consists of 5 - 9 discrete maneuvers. Preparation of bi-weekly command sequences, monitoring execution, and trending of subsystem performance is of paramount importance, but in-flight anomalies have also demanded the attention of AACS engineers. Anomalies are often very interesting and challenging aspects of a project, and the Magellan mission was no exception. From the first unsuccessful attempts to perform a starscan, to spacecraft safing events, much has been experienced to add to the `lessons learned' from this mission. Many of Magellan's in-flight experiences, anomalies, and their resolutions are highlighted in this paper.

Magellan attitude control mission operations

NASA Astrophysics Data System (ADS)

Dukes, Eileen M.

From the Martin Marietta Astronautics Group base in Denver, Colorado, spacecraft engineers have been operating the Magellan spacecraft for the past three and one half years, along with the Jet Propulsion Laboratory, for NASA. The spacecraft team in Denver is responsible for the health of the vehicle, from command generation to evaluation of engineering telemetry. Operation of the spacecraft's Attitude and Articulation Control Subsystem (AACS) has specifically posed several in-flight challenges. This system must provide accurate pointing of the spacecraft throughout each 3.2 hour orbit which typically consists of 5 - 9 discrete maneuvers. Preparation of bi-weekly command sequences, monitoring execution, and trending of subsystem performance is of paramount importance, but in-flight anomalies have also demanded the attention of AACS engineers. Anomalies are often very interesting and challenging aspects of a project, and the Magellan mission was no exception. From the first unsuccessful attempts to perform a starscan, to spacecraft safing events, much has been experienced to add to the `lessons learned' from this mission. Many of Magellan's in-flight experiences, anomalies, and their resolutions are highlighted in this paper.

Adaptive structures flight experiments

NASA Astrophysics Data System (ADS)

Martin, Maurice

The topics are presented in viewgraph form and include the following: adaptive structures flight experiments; enhanced resolution using active vibration suppression; Advanced Controls Technology Experiment (ACTEX); ACTEX program status; ACTEX-2; ACTEX-2 program status; modular control patch; STRV-1b Cryocooler Vibration Suppression Experiment; STRV-1b program status; Precision Optical Bench Experiment (PROBE); Clementine Spacecraft Configuration; TECHSAT all-composite spacecraft; Inexpensive Structures and Materials Flight Experiment (INFLEX); and INFLEX program status.

Adaptive Structures Flight Experiments

NASA Technical Reports Server (NTRS)

Martin, Maurice

1992-01-01

The topics are presented in viewgraph form and include the following: adaptive structures flight experiments; enhanced resolution using active vibration suppression; Advanced Controls Technology Experiment (ACTEX); ACTEX program status; ACTEX-2; ACTEX-2 program status; modular control patch; STRV-1b Cryocooler Vibration Suppression Experiment; STRV-1b program status; Precision Optical Bench Experiment (PROBE); Clementine Spacecraft Configuration; TECHSAT all-composite spacecraft; Inexpensive Structures and Materials Flight Experiment (INFLEX); and INFLEX program status.

Verification of the Microgravity Active Vibration Isolation System based on Parabolic Flight

NASA Astrophysics Data System (ADS)

Zhang, Yong-kang; Dong, Wen-bo; Liu, Wei; Li, Zong-feng; Lv, Shi-meng; Sang, Xiao-ru; Yang, Yang

2017-12-01

The Microgravity active vibration isolation system (MAIS) is a device to reduce on-orbit vibration and to provide a lower gravity level for certain scientific experiments. MAIS system is made up of a stator and a floater, the stator is fixed on the spacecraft, and the floater is suspended by electromagnetic force so as to reduce the vibration from the stator. The system has 3 position sensors, 3 accelerometers, 8 Lorentz actuators, signal processing circuits and a central controller embedded in the operating software and control algorithms. For the experiments on parabolic flights, a laptop is added to MAIS for monitoring and operation, and a power module is for electric power converting. The principle of MAIS is as follows: the system samples the vibration acceleration of the floater from accelerometers, measures the displacement between stator and floater from position sensitive detectors, and computes Lorentz force current for each actuator so as to eliminate the vibration of the scientific payload, and meanwhile to avoid crashing between the stator and the floater. This is a motion control technic in 6 degrees of freedom (6-DOF) and its function could only be verified in a microgravity environment. Thanks for DLR and Novespace, we get a chance to take the DLR 27th parabolic flight campaign to make experiments to verify the 6-DOF control technic. The experiment results validate that the 6-DOF motion control technique is effective, and vibration isolation performance perfectly matches what we expected based on theoretical analysis and simulation. The MAIS has been planned on Chinese manned spacecraft for many microgravity scientific experiments, and the verification on parabolic flights is very important for its following mission. Additionally, we also test some additional function by microgravity electromagnetic suspension, such as automatic catching and locking and working in fault mode. The parabolic flight produces much useful data for these experiments.

ACES: Space shuttle flight software analysis expert system

NASA Technical Reports Server (NTRS)

Satterwhite, R. Scott

1990-01-01

The Analysis Criteria Evaluation System (ACES) is a knowledge based expert system that automates the final certification of the Space Shuttle onboard flight software. Guidance, navigation and control of the Space Shuttle through all its flight phases are accomplished by a complex onboard flight software system. This software is reconfigured for each flight to allow thousands of mission-specific parameters to be introduced and must therefore be thoroughly certified prior to each flight. This certification is performed in ground simulations by executing the software in the flight computers. Flight trajectories from liftoff to landing, including abort scenarios, are simulated and the results are stored for analysis. The current methodology of performing this analysis is repetitive and requires many man-hours. The ultimate goals of ACES are to capture the knowledge of the current experts and improve the quality and reduce the manpower required to certify the Space Shuttle onboard flight software.

GSMS and space views: Advanced spacecraft monitoring tools

NASA Technical Reports Server (NTRS)

Carlton, Douglas; Vaules, David, Jr.; Mandl, Daniel

1993-01-01

The Graphical Spacecraft Monitoring System (GSMS) processes and translates real-time telemetry data from the Gamma Ray Observatory (GRO) spacecraft into high resolution 2-D and 3-D color displays showing the spacecraft's position relative to the Sun, Earth, Moon, and stars, its predicted orbit path, its attitude, instrument field of views, and other items of interest to the GRO Flight Operations Team (FOT). The GSMS development project is described and the approach being undertaken for implementing Space Views, the next version of GSMS, is presented. Space Views is an object-oriented graphical spacecraft monitoring system that will become a standard component of Goddard Space Flight Center's Transportable Payload Operations Control Center (TPOCC).

Flight-Proven Nano-Satellite Architecture for Hands-On Academic Training at the US Air Force Academy

NASA Astrophysics Data System (ADS)

Underwood, Craig I.; Sellers, Lt. Jerry, , Col.; Sweeting, Martin, , Sir

2002-01-01

This paper describes the use of "commercial-off-the-shelf" open-architecture satellite sub-systems, based on the flight- proven "SNAP" nanosatellite platform, to provide "hands-on" education and training at the United States Air Force Academy. The UK's first nanosatellite: SNAP-1, designed and built by Surrey Satellite Technology Ltd. (SSTL) and Surrey Space Centre staff - in less than a year - was launched in June 2000. The 6.5 kg spacecraft carries advanced, UK-developed, GPS navigation, computing, propulsion and attitude control technologies, which have been used to demonstrate orbital manoeuvring and full three-axis controlled body stabilisation. SNAP-1's primary payload is a machine vision system which has been used to image the in-orbit deployment of another SSTL-built spacecraft: Tsinghua-1. The highly successful, SNAP-1 mission has also demonstrated how the concept of using a standardised, modular nanosatellite bus can provide the core support units (power system, on-board data-handling and communications systems and standardised payload interface) for a practical nanosatellite to be constructed and flown in a remarkably short time-frame. Surrey's undergraduate and post-graduate students have made a major input to the SNAP concept over the last six years in the context of project work within the Space Centre. Currently, students at the USAF Academy are benefiting from this technology in the context of designing their own nanosatellite - FalconSAT-2. For the FalconSAT-2 project, the approach has been to focus on building up infrastructure, including design and development tools that can serve as a firm foundation to allow the satellite design to evolve steadily over the course of several missions. Specific to this new approach has been a major effort to bound the problem faced by the students. To do this, the program has leveraged the research carried out at the Surrey Space Centre, by "buying into" the SNAP architecture. Through this, the Academy program has achieved an "out of the box" solution for several critical subsystems; including power, communications and, most important, data handling. Using one set of SNAP hardware, the FalconSAT Avionics Simulation Testbed (FAST) was established in Fall 2000. FAST provides both a long-term facility for cadets to gain hands-on experience with spacecraft hardware and software, as well as overall program risk reduction by providing a facility for subsystem, software, and operational procedures development and testing. In addition, over the last two years, USAF cadets have been seconded to Surrey to help develop a MATLAB-based spacecraft simulator for SNAP, which itself is becoming a useful educational tool. While the use of the SNAP hardware has eased spacecraft design problem in many respects, considerable effort still remains in the areas of payload design and development, structures, attitude control, thermal control, solar panels, testing and operations -- more than enough to challenge even the most ambitious undergraduate students. This paper reviews our experience, both in the UK and in the US, in using a flight-proven nanosatellite in an educational context.

KSC-98pc1208

NASA Image and Video Library

1998-10-02

KENNEDY SPACE CENTER, FLA. -- KSC workers prepare Deep Space 1 for a spin test on the E6R Spin Balance Machine at the Defense Satellite Communications System Processing Facility (DPF), Cape Canaveral Air Station. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non-chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. The spacecraft will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches

Restoring Redundancy to the Wilkinson Microwave Anisotrophy Probe Propulsion System

NASA Technical Reports Server (NTRS)

O'Donnell, James R., Jr.; Davis, Gary T.; Ward, David K.

2004-01-01

The Wilkinson Microwave Anisotropy Probe is a follow-on to the Differential Microwave Radiometer instrument on the Cosmic Background Explorer. Attitude control system engineers discovered sixteen months before launch that configuration changes after the critical design review had resulted in a significant migration of the spacecraft's center of mass. As a result, the spacecraft no longer had a viable backup control mode in the event of a failure of the negative pitch-axis thruster. A tiger team was formed and identified potential solutions to this problem, such as adding thruster-plume shields to redirect thruster torque, adding or removing mass from the spacecraft, adding an additional thruster, moving thrusters, bending thruster nozzles or propellant tubing, or accepting the loss of redundancy. The project considered the impacts on mass, cost, fuel budget, and schedule for each solution, and decided to bend the propellant tubing of the two roll-control thrusters to allow the pair to be used for backup control in the negative pitch axis. This paper discusses the problem and the potential solutions, and documents the hardware and software changes and verification performed. Flight data are presented to show the on-orbit performance of the propulsion system and lessons learned are described.

Deep Space 1 is prepared for spin test at CCAS

NASA Technical Reports Server (NTRS)

1998-01-01

KSC workers prepare Deep Space 1 for a spin test on the E6R Spin Balance Machine at the Defense Satellite Communications System Processing Facility (DPF), Cape Canaveral Air Station. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include a solar-powered ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. The ion propulsion engine is the first non-chemical propulsion to be used as the primary means of propelling a spacecraft. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. The spacecraft will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches.

Enabling Higher Data Rates for Planetary Science Missions

NASA Astrophysics Data System (ADS)

Deutsch, L. J.; Townes, S. A.; Lazio, J.; Bell, D. J.; Chahat, N. E.; Kovalik, J. M.; Kuperman, I.; Sauder, J.; Liebrecht, P. E.

2017-12-01

The data rate from deep space spacecraft has increased by more than 10 orders of magnitude since the first lunar missions in the 1960s. The demand for increased data rates has stemmed from the increasing sophistication of the science questions being addressed and the concomitant increase in the complexity of the missions themselves (from fly-by to orbit to land and rove). Projections for the next few decades suggest the demand for data rates for deep space missions will continue to increase by approximately one order of magnitude every decade, driven by these same factors. Achieving higher data rates requires a partnership between the spacecraft and the ground system. We describe a series of technology developments for flight telecommunications systems, both at radio frequency (RF) and optical, to enable spacecraft to transmit and receive larger data volumes. These technology developments include deployable high gain antennas for small spacecraft, re-programmable software-defined radios, and optical communication packages designed for CubeSat form factors. The intent is that these developments would provide enhancements in capability for both spacecraft-Earth and spacecraft-spacecraft telecommunications. We also describe the future planning for NASA's Deep Space Network (DSN), which remains the prime conduit for data from all planetary science missions. Through a combination of new antennas and backends being installed over the next five years and incorporation of optical communications, the DSN aims to ensure that the historical improvements in data rates and volumes will continue for many decades. Part of this research was carried out at the Jet Propulsion Laboratory, California Institute of Technology, under a contract with the National Aeronautics and Space Administration.

In-flight calibration of the high-gain antenna pointing for the Mariner Venus-Mercury 1973 spacecraft

NASA Technical Reports Server (NTRS)

Hardman, J. M.; Havens, W. F.; Ohtakay, H.

1975-01-01

The methods used to in-flight calibrate the pointing direction of the Mariner Venus-Mercury 1973 spacecraft high gain antenna and the achieved antenna pointing accuracy are described. The overall pointing calibration was accomplished by performing calibration sequences at a number of points along the spacecraft trajectory. Each of these consisted of articulating the antenna about the expected spacecraft-earth vector to determine systematic pointing errors. The high gain antenna pointing system, the error model used in the calibration, and the calibration and pointing strategy and results are discussed.

Using computer graphics to enhance astronaut and systems safety

NASA Technical Reports Server (NTRS)

Brown, J. W.

1985-01-01

Computer graphics is being employed at the NASA Johnson Space Center as a tool to perform rapid, efficient and economical analyses for man-machine integration, flight operations development and systems engineering. The Operator Station Design System (OSDS), a computer-based facility featuring a highly flexible and versatile interactive software package, PLAID, is described. This unique evaluation tool, with its expanding data base of Space Shuttle elements, various payloads, experiments, crew equipment and man models, supports a multitude of technical evaluations, including spacecraft and workstation layout, definition of astronaut visual access, flight techniques development, cargo integration and crew training. As OSDS is being applied to the Space Shuttle, Orbiter payloads (including the European Space Agency's Spacelab) and future space vehicles and stations, astronaut and systems safety are being enhanced. Typical OSDS examples are presented. By performing physical and operational evaluations during early conceptual phases. supporting systems verification for flight readiness, and applying its capabilities to real-time mission support, the OSDS provides the wherewithal to satisfy a growing need of the current and future space programs for efficient, economical analyses.

Flight dynamics facility operational orbit determination support for the ocean topography experiment

NASA Technical Reports Server (NTRS)

Bolvin, D. T.; Schanzle, A. F.; Samii, M. V.; Doll, C. E.

1991-01-01

The Ocean Topography Experiment (TOPEX/POSEIDON) mission is designed to determine the topography of the Earth's sea surface across a 3 yr period, beginning with launch in June 1992. The Goddard Space Flight Center Dynamics Facility has the capability to operationally receive and process Tracking and Data Relay Satellite System (TDRSS) tracking data. Because these data will be used to support orbit determination (OD) aspects of the TOPEX mission, the Dynamics Facility was designated to perform TOPEX operational OD. The scientific data require stringent OD accuracy in navigating the TOPEX spacecraft. The OD accuracy requirements fall into two categories: (1) on orbit free flight; and (2) maneuver. The maneuver OD accuracy requirements are of two types; premaneuver planning and postmaneuver evaluation. Analysis using the Orbit Determination Error Analysis System (ODEAS) covariance software has shown that, during the first postlaunch mission phase of the TOPEX mission, some postmaneuver evaluation OD accuracy requirements cannot be met. ODEAS results also show that the most difficult requirements to meet are those that determine the change in the components of velocity for postmaneuver evaluation.

Operational Analysis of Time-Optimal Maneuvering for Imaging Spacecraft

DTIC Science & Technology

2013-03-01

imaging spacecraft. The analysis is facilitated through the use of AGI’s Systems Tool Kit ( STK ) software. An Analytic Hierarchy Process (AHP)-based...the Singapore-developed X-SAT imaging spacecraft. The analysis is facilitated through the use of AGI’s Systems Tool Kit ( STK ) software. An Analytic...89  B.  FUTURE WORK................................................................................. 90  APPENDIX A. STK DATA AND BENEFIT

NASA Computational Case Study: The Flight of Friendship 7

NASA Technical Reports Server (NTRS)

Simpson, David G.

2012-01-01

In this case study, we learn how to compute the position of an Earth-orbiting spacecraft as a function of time. As an exercise, we compute the position of John Glenn's Mercury spacecraft Friendship 7 as it orbited the Earth during the third flight of NASA's Mercury program.

Advanced transport operating system software upgrade: Flight management/flight controls software description

NASA Technical Reports Server (NTRS)

Clinedinst, Winston C.; Debure, Kelly R.; Dickson, Richard W.; Heaphy, William J.; Parks, Mark A.; Slominski, Christopher J.; Wolverton, David A.

1988-01-01

The Flight Management/Flight Controls (FM/FC) software for the Norden 2 (PDP-11/70M) computer installed on the NASA 737 aircraft is described. The software computes the navigation position estimates, guidance commands, those commands to be issued to the control surfaces to direct the aircraft in flight based on the modes selected on the Advanced Guidance Control System (AGSC) mode panel, and the flight path selected via the Navigation Control/Display Unit (NCDU).

14 CFR § 1214.111 - Rendezvous services.

Code of Federal Regulations, 2014 CFR

2014-01-01

... Earth of the orbiting spacecraft (or part thereof), including a spacecraft deployed earlier on the same Space Shuttle flight. (2) Exchange of a spacecraft (or part thereof) delivered to orbit on a particular... orbiting spacecraft to Earth. (3) Revisit of an orbiting spacecraft for purposes such as resupply, repair...

Parachute Testing for the NASA X-38 Crew Return Vehicle

NASA Technical Reports Server (NTRS)

Stein, Jenny M.

2005-01-01

NASA's X-38 program was an in-house technology demonstration program to develop a Crew Return Vehicle (CRV) for the International Space Station capable of returning seven crewmembers to Earth when the Space Shuttle was not present at the station. The program, managed out of NASA's Johnson Space Center, was started in 1995 and was cancelled in 2003. Eight flights with a prototype atmospheric vehicle were successfully flown at Edwards Air Force Base, demonstrating the feasibility of a parachute landing system for spacecraft. The intensive testing conducted by the program included testing of large ram-air parafoils. The flight test techniques, instrumentation, and simulation models developed during the parachute test program culminated in the successful demonstration of a guided parafoil system to land a 25,000 Ib spacecraft. The test program utilized parafoils of sizes ranging from 750 to 7500 p. The guidance, navigation, and control system (GN&C) consisted of winches, laser or radar altimeter, global positioning system (GPS), magnetic compass, barometric altimeter, flight computer, and modems for uplink commands and downlink data. The winches were used to steer the parafoil and to perform the dynamic flare maneuver for a soft landing. The laser or radar altimeter was used to initiate the flare. In the event of a GPS failure, the software navigated by dead reckoning using the compass and barometric altimeter data. The GN&C test beds included platforms dropped from cargo aircraft, atmospheric vehicles released from a 8-52, and a Buckeye powered parachute. This paper will describe the test program and significant results.

jsc2012e238681

NASA Image and Video Library

2012-11-28

At the Gagarin Cosmonaut Training Center in Star City, Russia, Expedition 34/35 Soyuz Commander Roman Romanenko studies a flight data file manual in front of a Soyuz spacecraft simulator Nov. 28, 2012 as he and his crewmates conducted the second of two days of flight qualification exams. Romanenko, NASA Flight Engineer Tom Marshburn and Flight Engineer Chris Hadfield of the Canadian Space Agency are scheduled to launch Dec. 19 from the Baikonur Cosmodrome in Kazakhstan on the Soyuz TMA-07M spacecraft, bound for a 5-month mission on the International Space Station. NASA/Stephanie Stoll

View of the approach of the new Soyuz Spacecraft taken during Expedition Three

NASA Image and Video Library

2001-10-23

ISS003-324-034 (23 October 2001) --- A Soyuz spacecraft approaches the International Space Station (ISS) carrying the Soyuz Taxi crew, Commander Victor Afanasyev, Flight Engineer Konstantin Kozeev and French Flight Engineer Claudie Haignere for an eight-day stay on the station. Afanasyev and Kozeev represent Rosaviakosmos, and Haignere represents ESA, carrying out a flight program for CNES, the French Space Agency, under a commercial contract with the Rosaviakosmos.

Results of solar electric thrust vector control system design, development and tests

NASA Technical Reports Server (NTRS)

Fleischer, G. E.

1973-01-01

Efforts to develop and test a thrust vector control system TVCS for a solar-energy-powered ion engine array are described. The results of solar electric propulsion system technology (SEPST) III real-time tests of present versions of TVCS hardware in combination with computer-simulated attitude dynamics of a solar electric multi-mission spacecraft (SEMMS) Phase A-type spacecraft configuration are summarized. Work on an improved solar electric TVCS, based on the use of a state estimator, is described. SEPST III tests of TVCS hardware have generally proved successful and dynamic response of the system is close to predictions. It appears that, if TVCS electronic hardware can be effectively replaced by control computer software, a significant advantage in control capability and flexibility can be gained in future developmental testing, with practical implications for flight systems as well. Finally, it is concluded from computer simulations that TVCS stabilization using rate estimation promises a substantial performance improvement over the present design.

Proximity operations considerations affecting spacecraft design

NASA Technical Reports Server (NTRS)

Staas, Steven K.

1991-01-01

Proximity operations can be defined as the maneuvering of two or more spacecraft within 1 nautical mile range, with relative velocity less than 10 feet per second. The passive vehicle is nontranslating and should provide for maintenance of the desired approach attitude. It must accommodate the active (translating) vehicle induced structural loads and performance characteristics (mating hardware tolerances), and support sensor compatibility (transponder, visual targets, etc.). The active vehicle must provide adequate sensor systems (relative state information, field-of-view, redundancy), flight control hardware (thruster sizing, minimal cross-coupling, performance margins, redundancy) and software (reconfigurable, attitude/rate modes, translation and rotation fine control authority) characteristic, and adequate non-propulsive consumables such as power. Operational concerns must be considered. These include the following: (1) the desired approach trajectory and relative orientation; (2) the active vehicle thruster plume effects (forces, torques, contamination) on the passive vehicle; and (3) procedures for contingencies such as loss of communications, sensor or propulsion failures, and target vehicle loss of control.

KSC-98pc1181

NASA Image and Video Library

1998-09-29

KENNEDY SPACE CENTER, FLA. -- In the Payload Hazardous Servicing Facility, Tom Shain, project manager on Deep Space 1, displays a CD containing 350,000 names of KSC workers that he will place in a pouch and insert inside the spacecraft. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but may also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999. Deep Space 1 will be launched aboard a Boeing Delta 7326 rocket from Launch Pad 17A, Cape Canaveral Air Station, in October. Delta II rockets are medium capacity expendable launch vehicles derived from the Delta family of rockets built and launched since 1960. Since then there have been more than 245 Delta launches

Managing Cassini Safe Mode Attitude at Saturn

NASA Technical Reports Server (NTRS)

Burk, Thomas A.

2010-01-01

The Cassini spacecraft was launched on October 15, 1997 and arrived at Saturn on June 30, 2004. It has performed detailed observations and remote sensing of Saturn, its rings, and its satellites since that time. In the event safe mode interrupts normal orbital operations, Cassini has flight software fault protection algorithms to detect, isolate, and recover to a thermally safe and commandable attitude and then wait for further instructions from the ground. But the Saturn environment is complex, and safety hazards change depending on where Cassini is in its orbital trajectory around Saturn. Selecting an appropriate safe mode attitude that insures safe operation in the Saturn environment, including keeping the star tracker field of view clear of bright bodies, while maintaining a quiescent, commandable attitude, is a significant challenge. This paper discusses the Cassini safe table management strategy and the key criteria that must be considered, especially during low altitude flybys of Titan, in deciding what spacecraft attitude should be used in the event of safe mode.

LANDSAT-2 launch and flight activation. Launch through orbit 50 and orbit adjust operation. [telemetry data processing

NASA Technical Reports Server (NTRS)

1975-01-01

The results of the analysis conducted on the telemetry data from the prelaunch, launch, and flight activation phases of LANDSAT-2 spacecraft are presented according to subsystems and interrelationships that exist between subsystems. Subsystem characteristics are included along with the flight evaluation results. Flight data are compared to baseline data established at the 20 C plateau during thermal vacuum testing of the spacecraft. Evaluation guidelines are derived from the specifications developed from the LANDSAT program objectives: (1) acquisition of multispectral images of the surface of the earth; and (2) use of the LANDSAT-2 receiving, frequency translating, and transmitting equipment as a relay system to gather data from fixed earth-based sensor platforms which are operated by individual investigators. Data are presented on the first 50 orbits of the spacecraft.

Telemetry Tracking and Control Through Commercial LEO Satellites

NASA Technical Reports Server (NTRS)

Streich, Ronald C.; Morgan, Dwayne R.; Bull, Barton B.; Grant, Charles E.; Powers, Edward I. (Technical Monitor)

2001-01-01

Personnel from the Goddard Space Flight Center Wallops Flight Facility (GSFC/WFF in Virginia have successfully tested commercial LEO communications satellites for sounding rocket, balloon and aircraft flight TT&C. The Flight Modern became a GSFC/WFF Advanced Range Technology Initiative (ARTI) in an effort to streamline TT&C capability to the user community at low cost. Ground tests of the Flight Modem verified duplex communications quality of service and measured transmission latencies. These tests were completed last year and results reported in the John Hopkins University (JHU) Applied Physics Laboratory (APL) 4th International Symposium on Reducing Spacecraft Costs for Ground Systems and Operations. The second phase of the Flight Modem baseline test program was a demonstration of the ruggedized version of the WFF Flight Modem flown on a sounding rocket launched it the Swedish rocket range (Esrangc) near Kiruna, Sweden, with results contained in this paper. Aircraft flight tests have been and continue to be conducted. Flights of opportunity are being actively pursued with other centers, ranges and users at universities. The WFF Flight Modem contains a CPS receiver to provide vehicle position for tracking and vehicle recovery. The system architecture, which integrates antennas, CPS receiver, commercial satellite packet data modem and a single board computer with custom software, is described. Small satellite use of the WFF Flight Modem is also being investigated, The Flight Modem provides an independent vehicle position source for Range Safety applications. The LEO communication system contains a coarse position location system, which is compared to GPS ace acy. This comparison allows users, to determine the need for a CPS receiver in addition to the satellite packet data modem for their application.

View of the nose of the Gemini 9 spacecraft taken from hatch of spacecraft

NASA Technical Reports Server (NTRS)

1966-01-01

Astronaut Eugene A. Cernan, pilot of the Gemini 9-A space flight, took this picture of the nose of the Gemini 9 spacecraft while standing in hatch of spacecraft. Area of earth below is the Pacific Ocean.

Apollo Program Summary Report: Synopsis of the Apollo Program Activities and Technology for Lunar Exploration

NASA Technical Reports Server (NTRS)

1975-01-01

Overall program activities and the technology developed to accomplish lunar exploration are discussed. A summary of the flights conducted over an 11-year period is presented along with specific aspects of the overall program, including lunar science, vehicle development and performance, lunar module development program, spacecraft development testing, flight crew summary, mission operations, biomedical data, spacecraft manufacturing and testing, launch site facilities, equipment, and prelaunch operations, and the lunar receiving laboratory. Appendixes provide data on each of the Apollo missions, mission type designations, spacecraft weights, records achieved by Apollo crewmen, vehicle histories, and a listing of anomalous hardware conditions noted during each flight beginning with Apollo 4.

The mission events graphic generator software: A small tool with big results

NASA Technical Reports Server (NTRS)

Lupisella, Mark; Leibee, Jack; Scaffidi, Charles

1993-01-01

Utilization of graphics has long been a useful methodology for many aspects of spacecraft operations. A personal computer based software tool that implements straight-forward graphics and greatly enhances spacecraft operations is presented. This unique software tool is the Mission Events Graphic Generator (MEGG) software which is used in support of the Hubble Space Telescope (HST) Project. MEGG reads the HST mission schedule and generates a graphical timeline.

Automation and Process Improvement Enables a Small Team to Operate a Low Thrust Mission in Orbit Around the Asteroid Vesta

NASA Technical Reports Server (NTRS)

Weise, Timothy M

2012-01-01

NASA's Dawn mission to the asteroid Vesta and dwarf planet Ceres launched September 27, 2007 and arrived at Vesta in July of 2011. This mission uses ion propulsion to achieve the necessary delta-V to reach and maneuver at Vesta and Ceres. This paper will show how the evolution of ground system automation and process improvement allowed a relatively small engineering team to transition from cruise operations to asteroid operations while maintaining robust processes. The cruise to Vesta phase lasted almost 4 years and consisted of activities that were built with software tools, but each tool was open loop and required engineers to review the output to ensure consistency. Additionally, this same time period was characterized by the evolution from manually retrieved and reviewed data products to automatically generated data products and data value checking. Furthermore, the team originally took about three to four weeks to design and build about four weeks of spacecraft activities, with spacecraft contacts only once a week. Operations around the asteroid Vesta increased the tempo dramatically by transitioning from one contact a week to three or four contacts a week, to fourteen contacts a week (every 12 hours). This was accompanied by a similar increase in activity complexity as well as very fast turn around activity design and build cycles. The design process became more automated and the tools became closed loop, allowing the team to build more activities without sacrificing rigor. Additionally, these activities were dependent on the results of flight system performance, so more automation was added to analyze the flight data and provide results in a timely fashion to feed the design cycle. All of this automation and process improvement enabled up the engineers to focus on other aspects of spacecraft operations, including spacecraft health monitoring and anomaly resolution.

LANDSAT-2 and LANDSAT-3 Flight evaluation report

NASA Technical Reports Server (NTRS)

Winchester, T. W.

1978-01-01

Flight performance analysis of LANDSAT 2 and LANDSAT 3 are presented for the period July 1978 to October 1978. Spacecraft operations and orbital parameters are summarized for each spacecraft. Data are provided on the performance and operation of the following subsystems onboard the spacecraft: power; attitude control; command/clock; telemetry; orbit adjust; magnetic moment compensating assembly; unified S band/premodulation processor; electrical interface; thermal narrowband tape recorders; wideband telemetry; attitude measurement sensor; wideband video tape recorders; return beam vidicon; multispectral scanner subsystem; and data collections.

Flights of a spacecraft with a solar sail out of ecliptic plane

NASA Astrophysics Data System (ADS)

Polyakhova, Elena; Starkov, Vladimir; Stepenko, Nikolai

2018-05-01

Solar sailing is an unique form of spacecraft (SC) propulsion that uses the free and limitless supply of photons from the Sun. The investigation of near-the-Sun space properties is of the great scientific interest. It can be realized by help of solar sailing. We present the numerical simulation of several closed modelled trajectories of a spacecraft with a controlled solar sail to reach out of ecliptic plane, to flight over the Sun north and south poles and return to the Earth.

International Symposium on Spacecraft Ground Control and Flight Dynamics, SCD1, Sao Jose dos Campos, Brazil, Feb. 7-11, 1994

NASA Astrophysics Data System (ADS)

Rozenfeld, Pawel; Kuga, Helio Koiti; Orlando, Valcir

An international symposium on spacecraft flight dynamics and ground control systems produced 85 papers in the areas of attitude determination and control, orbit control, satellite constellation strategies, stationkeeping, spacecraft maneuvering, orbit determination, astrodynamics, ground command and control systems, and mission operations. Several papers included discussions on the application of artificial intelligence, neural networks, expert systems, and ion propulsion. For individual titles, see A95-89098 through A95-89182.

Advanced Transport Operating System (ATOPS) Flight Management/Flight Controls (FM/FC) software description

NASA Technical Reports Server (NTRS)

Wolverton, David A.; Dickson, Richard W.; Clinedinst, Winston C.; Slominski, Christopher J.

1993-01-01

The flight software developed for the Flight Management/Flight Controls (FM/FC) MicroVAX computer used on the Transport Systems Research Vehicle for Advanced Transport Operating Systems (ATOPS) research is described. The FM/FC software computes navigation position estimates, guidance commands, and those commands issued to the control surfaces to direct the aircraft in flight. Various modes of flight are provided for, ranging from computer assisted manual modes to fully automatic modes including automatic landing. A high-level system overview as well as a description of each software module comprising the system is provided. Digital systems diagrams are included for each major flight control component and selected flight management functions.

Vacuum chamber translation/positioning mechanism and welding power supply controller

NASA Technical Reports Server (NTRS)

Smith, James E., Jr.; Cashon, John L.

1992-01-01

Welding in the vacuum of space represents an important and fundamental problem for space exploration. Repairs or connection of metal components on orbit or during travel to the moon or distant planets may be required. Cracks or holes in spacecraft skin or supporting structures external to the pressurized section will require some type of repair that must be permanently made to the skin or support by welding. The development of a translation/positioning system that will permit research into welding of metal samples in a small vacuum chamber located at Marshall Space Flight Center (MSFC) is addressed. The system and associated software was tested to the extent possible without the availability of the welder power supply or control computer that must be supplied by MSFC. Software has been developed for straight line welding. More extensive and varied translations are possible with simple alterations to the operating software to use the full capabilities of this three axes system. The source code 'VW.BAS' has been provided to serve as an example for further development of the vacuum welder translation system.

Evolution of Software-Only-Simulation at NASA IV and V

NASA Technical Reports Server (NTRS)

McCarty, Justin; Morris, Justin; Zemerick, Scott

2014-01-01

Software-Only-Simulations have been an emerging but quickly developing field of study throughout NASA. The NASA Independent Verification Validation (IVV) Independent Test Capability (ITC) team has been rapidly building a collection of simulators for a wide range of NASA missions. ITC specializes in full end-to-end simulations that enable developers, VV personnel, and operators to test-as-you-fly. In four years, the team has delivered a wide variety of spacecraft simulations that have ranged from low complexity science missions such as the Global Precipitation Management (GPM) satellite and the Deep Space Climate Observatory (DSCOVR), to the extremely complex missions such as the James Webb Space Telescope (JWST) and Space Launch System (SLS).This paper describes the evolution of ITCs technologies and processes that have been utilized to design, implement, and deploy end-to-end simulation environments for various NASA missions. A comparison of mission simulators are discussed with focus on technology and lessons learned in complexity, hardware modeling, and continuous integration. The paper also describes the methods for executing the missions unmodified flight software binaries (not cross-compiled) for verification and validation activities.

SPACECRAFT - MERCURY-ATLAS (MA)-9 - PRELAUNCH - ASTRONAUT COOPER - SIMULATED FLIGHT TESTS - CAPE

NASA Image and Video Library

1963-03-01

S63-03975 (1963) --- Astronaut L. Gordon Cooper Jr., prime pilot for the Mercury-Atlas 9 (MA-9) mission, is pictured prior to entering the Mercury spacecraft for a series of simulated flight tests. During these tests NASA doctors, engineers and technicians monitor Cooper's performance. Photo credit: NASA

Mercury Project

NASA Image and Video Library

1963-05-16

The recovery operation of the Faith 7 spacecraft after the completion of the 1-1/2 day orbital flight (MA-9 mission) with Astronaut Gordon Cooper. Navy frogmen attach the flotation collar to the spacecraft. The MA-9 mission was the last flight of the Mercury Project and launched on May 15, 1963 boosted by The Mercury-Atlas launch vehicle.

Global Precipitation Measurement (GPM) Safety Inhibit Timeline Tool

NASA Technical Reports Server (NTRS)

Dion, Shirley

2012-01-01

The Global Precipitation Measurement (GPM) Observatory is a joint mission under the partnership by National Aeronautics and Space Administration (NASA) and the Japan Aerospace Exploration Agency (JAXA), Japan. The NASA Goddard Space Flight Center (GSFC) has the lead management responsibility for NASA on GPM. The GPM program will measure precipitation on a global basis with sufficient quality, Earth coverage, and sampling to improve prediction of the Earth's climate, weather, and specific components of the global water cycle. As part of the development process, NASA built the spacecraft (built in-house at GSFC) and provided one instrument (GPM Microwave Imager (GMI) developed by Ball Aerospace) JAXA provided the launch vehicle (H2-A by MHI) and provided one instrument (Dual-Frequency Precipitation Radar (DPR) developed by NTSpace). Each instrument developer provided a safety assessment which was incorporated into the NASA GPM Safety Hazard Assessment. Inhibit design was reviewed for hazardous subsystems which included the High Gain Antenna System (HGAS) deployment, solar array deployment, transmitter turn on, propulsion system release, GMI deployment, and DPR radar turn on. The safety inhibits for these listed hazards are controlled by software. GPM developed a "pathfinder" approach for reviewing software that controls the electrical inhibits. This is one of the first GSFC in-house programs that extensively used software controls. The GPM safety team developed a methodology to document software safety as part of the standard hazard report. As part of this process a new tool "safety inhibit time line" was created for management of inhibits and their controls during spacecraft buildup and testing during 1& Tat GSFC and at the Range in Japan. In addition to understanding inhibits and controls during 1& T the tool allows the safety analyst to better communicate with others the changes in inhibit states with each phase of hardware and software testing. The tool was very useful for communicating compliance with safety requirements especially when working with a foreign partner.

Flight Force Measurements on a Spacecraft to Launch Vehicle Interface

NASA Astrophysics Data System (ADS)

Kaufman, Daniel S.; Gordon, Scott A.

2012-07-01

For several years we had wanted to measure interface forces between a launch vehicle and the Payload. Finally in July 2006 a proposal was made and funded to evaluate the use of flight force measurements (FFM) to improve the loads process of a Spacecraft in its design and test cycle. A NASA/Industry team was formed, the core Team consisted of 20 people. The proposal identified two questions that this assessment would attempt to address by obtaining the flight forces. These questions were: 1) Is flight correlation and reconstruction with acceleration methods sufficient? 2) How much can the loads and therefore the design and qualification be reduced by having force measurements? The objective was to predict the six interface driving forces between the Spacecraft and the Launch Vehicle throughout the boost phase. Then these forces would be compared with reconstructed loads analyses for evaluation in an attempt to answer them. The paper will present the development of a strain based force measurement system and also an acceleration method, actual flight results, post flight evaluations and lessons learned.

Ground correlation investigation of thruster spacecraft interactions to be measured on the IAPS flight test

NASA Technical Reports Server (NTRS)

Power, J. L.

1984-01-01

Preliminary ground correlation testing has been conducted with an 8 cm mercury ion thruster and diagnostic instrumentation replicating to a large extent the IAPS flight test hardware, configuration, and electrical grounding/isolation. Thruster efflux deposition retained at 25 C was measured and characterized. Thruster ion efflux was characterized with retarding potential analyzers. Thruster-generated plasma currents, the spacecraft common (SCC) potential, and ambient plasma properties were evaluated with a spacecraft potential probe (SPP). All the measured thruster/spacecraft interactions or their IAPS measurements depend critically on the SCC potential, which can be controlled by a neutralizer ground switch and by the SPP operation.

Temperature control of the Mariner class spacecraft - A seven mission summary.

NASA Technical Reports Server (NTRS)

Dumas, L. N.

1973-01-01

Mariner spacecraft have completed five missions of scientific investigation of the planets. Two additional missions are planned. A description of the thermal design of these seven spacecraft is given herein. The factors which have influenced the thermal design include the mission requirements and constraints, the flight environment, certain programmatic considerations and the experience gained as each mission is completed. These factors are reviewed and the impact of each on thermal design and developmental techniques is assessed. It is concluded that the flight success of these spacecraft indicates that adequate temperature control has been obtained, but that improvements in design data, hardware performance and analytical techniques are needed.

Flight test of carbon-phenolic on a spacecraft launched by the pacemaker vehicle system

NASA Technical Reports Server (NTRS)

Walton, T. E., Jr.; Witte, W. G.

1972-01-01

Carbon-phenolic material consisting of 50 percent carbon fibers and 50 percent phenolic resin was flight tested on a recoverable spacecraft launched by the Pacemaker vehicle system. The heat shield of the spacecraft was fabricated so that the carbon fibers in the ablator material had different orientations over several areas of the spacecraft. The environment in which the spacecraft was tested produced heating rates on the hemispherical nose up to 13.6 MW/sq m (1200 Btu/sq ft/sec) and stagnation-point pressures up to 1.27 MN/sq m (12.5 atm). The experimental results are presented. Due to high heating rates and possible spallation and mechanical char removal the greatest mass loss occurred in the nose region. Essentially uniform surface recession and char thickness were observed on the conical section of the spacecraft. A comparison of measured heating rates with computed turbulent and laminar heating rates, as well as measurements of sound-pressure fluctuations in the boundary layer obtained with acoustic sensors, indicated that the boundary layer underwent transition. The acoustic sensor provides an interesting new data form for the general study of boundary-layer transition for free-flight investigations.

Thermal Analysis and Correlation of the Mars Odyssey Spacecraft's Solar Array During Aerobraking Operations

NASA Technical Reports Server (NTRS)

Dec, John A.; Gasbarre, Joseph F.; George, Benjamin E.

2002-01-01

The Mars Odyssey spacecraft made use of multipass aerobraking to gradually reduce its orbit period from a highly elliptical insertion orbit to its final science orbit. Aerobraking operations provided an opportunity to apply advanced thermal analysis techniques to predict the temperature of the spacecraft's solar array for each drag pass. Odyssey telemetry data was used to correlate the thermal model. The thermal analysis was tightly coupled to the flight mechanics, aerodynamics, and atmospheric modeling efforts being performed during operations. Specifically, the thermal analysis predictions required a calculation of the spacecraft's velocity relative to the atmosphere, a prediction of the atmospheric density, and a prediction of the heat transfer coefficients due to aerodynamic heating. Temperature correlations were performed by comparing predicted temperatures of the thermocouples to the actual thermocouple readings from the spacecraft. Time histories of the spacecraft relative velocity, atmospheric density, and heat transfer coefficients, calculated using flight accelerometer and quaternion data, were used to calculate the aerodynamic heating. During aerobraking operations, the correlations were used to continually update the thermal model, thus increasing confidence in the predictions. This paper describes the thermal analysis that was performed and presents the correlations to the flight data.

Generic trending and analysis system

NASA Technical Reports Server (NTRS)

Keehan, Lori; Reese, Jay

1994-01-01

The Generic Trending and Analysis System (GTAS) is a generic spacecraft performance monitoring tool developed by NASA Code 511 and Loral Aerosys. It is designed to facilitate quick anomaly resolution and trend analysis. Traditionally, the job of off-line analysis has been performed using hardware and software systems developed for real-time spacecraft contacts; then, the systems were supplemented with a collection of tools developed by Flight Operations Team (FOT) members. Since the number of upcoming missions is increasing, NASA can no longer afford to operate in this manner. GTAS improves control center productivity and effectiveness because it provides a generic solution across multiple missions. Thus, GTAS eliminates the need for each individual mission to develop duplicate capabilities. It also allows for more sophisticated tools to be developed because it draws resources from several projects. In addition, the GTAS software system incorporates commercial off-the-shelf tools software (COTS) packages and reuses components of other NASA-developed systems wherever possible. GTAS has incorporated lessons learned from previous missions by involving the users early in the development process. GTAS users took a proactive role in requirements analysis, design, development, and testing. Because of user involvement, several special tools were designed and are now being developed. GTAS users expressed considerable interest in facilitating data collection for long term trending and analysis. As a result, GTAS provides easy access to large volumes of processed telemetry data directly in the control center. The GTAS archival and retrieval capabilities are supported by the integration of optical disk technology and a COTS relational database management system.

Safe and Secure Partitioning with Pikeos: Towards Integrated Modular Avionics in Space

NASA Astrophysics Data System (ADS)

Almeida, J.; Prochazka, M.

2009-05-01

This paper presents our approach to logical partitioning of spacecraft onboard software. We present PikeOS, a separation micro-kernel which applies the state-of-the- art techniques and widely recognised standards such as ARINC 653 and MILS in order to guarantee safety and security properties of partitions executing software with different criticality and confidentiality. We provide an overview of our approach, also used in the Securely Partitioning Spacecraft Computing Resources project, an ESA TRP contract, which shifts spacecraft onboard software development towards the Integrated Modular Avionics concept with relevance for dual-use military and civil missions.

Investigation of HZETRN 2010 as a Tool for Single Event Effect Qualification of Avionics Systems

NASA Technical Reports Server (NTRS)

Rojdev, Kristina; Koontz, Steve; Atwell, William; Boeder, Paul

2014-01-01

NASA's future missions are focused on long-duration deep space missions for human exploration which offers no options for a quick emergency return to Earth. The combination of long mission duration with no quick emergency return option leads to unprecedented spacecraft system safety and reliability requirements. It is important that spacecraft avionics systems for human deep space missions are not susceptible to Single Event Effect (SEE) failures caused by space radiation (primarily the continuous galactic cosmic ray background and the occasional solar particle event) interactions with electronic components and systems. SEE effects are typically managed during the design, development, and test (DD&T) phase of spacecraft development by using heritage hardware (if possible) and through extensive component level testing, followed by system level failure analysis tasks that are both time consuming and costly. The ultimate product of the SEE DD&T program is a prediction of spacecraft avionics reliability in the flight environment produced using various nuclear reaction and transport codes in combination with the component and subsystem level radiation test data. Previous work by Koontz, et al.1 utilized FLUKA, a Monte Carlo nuclear reaction and transport code, to calculate SEE and single event upset (SEU) rates. This code was then validated against in-flight data for a variety of spacecraft and space flight environments. However, FLUKA has a long run-time (on the order of days). CREME962, an easy to use deterministic code offering short run times, was also compared with FLUKA predictions and in-flight data. CREME96, though fast and easy to use, has not been updated in several years and underestimates secondary particle shower effects in spacecraft structural shielding mass. Thus, this paper will investigate the use of HZETRN 20103, a fast and easy to use deterministic transport code, similar to CREME96, that was developed at NASA Langley Research Center primarily for flight crew ionizing radiation dose assessments. HZETRN 2010 includes updates to address secondary particle shower effects more accurately, and might be used as another tool to verify spacecraft avionics system reliability in space flight SEE environments.

Approximate approach for optimization space flights with a low thrust on the basis of sufficient optimality conditions

NASA Astrophysics Data System (ADS)

Salmin, Vadim V.

2017-01-01

Flight mechanics with a low-thrust is a new chapter of mechanics of space flight, considered plurality of all problems trajectory optimization and movement control laws and the design parameters of spacecraft. Thus tasks associated with taking into account the additional factors in mathematical models of the motion of spacecraft becomes increasingly important, as well as additional restrictions on the possibilities of the thrust vector control. The complication of the mathematical models of controlled motion leads to difficulties in solving optimization problems. Author proposed methods of finding approximate optimal control and evaluating their optimality based on analytical solutions. These methods are based on the principle of extending the class of admissible states and controls and sufficient conditions for the absolute minimum. Developed procedures of the estimation enabling to determine how close to the optimal founded solution, and indicate ways to improve them. Authors describes procedures of estimate for approximately optimal control laws for space flight mechanics problems, in particular for optimization flight low-thrust between the circular non-coplanar orbits, optimization the control angle and trajectory movement of the spacecraft during interorbital flights, optimization flights with low-thrust between arbitrary elliptical orbits Earth satellites.

The development and flight test of a deployable precision landing system for spacecraft recovery

NASA Technical Reports Server (NTRS)

Sim, Alex G.; Murray, James E.; Neufeld, David C.; Reed, R. Dale

1993-01-01

A joint NASA Dryden Flight Research Facility and Johnson Space Center program was conducted to determine the feasibility of the autonomous recovery of a spacecraft using a ram-air parafoil system for the final stages of entry from space that included a precision landing. The feasibility of this system was studied using a flight model of a spacecraft in the generic shape of a flattened biconic which weighed approximately 150 lb and was flown under a commercially available, ram-air parachute. Key elements of the vehicle included the Global Positioning System guidance for navigation, flight control computer, ultrasonic sensing for terminal altitude, electronic compass, and onboard data recording. A flight test program was used to develop and refine the vehicle. This vehicle completed an autonomous flight from an altitude of 10,000 ft and a lateral offset of 1.7 miles which resulted in a precision flare and landing into the wind at a predetermined location. At times, the autonomous flight was conducted in the presence of winds approximately equal to vehicle airspeed. Several techniques for computing the winds postflight were evaluated. Future program objectives are also presented.

Mission operations and command assurance: Instilling quality into flight operations

NASA Technical Reports Server (NTRS)

Welz, Linda L.; Witkowski, Mona M.; Bruno, Kristin J.; Potts, Sherrill S.

1993-01-01

Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality in flight mission operations. From a system engineering view, MO&CA facilitates communication and problem-solving among flight teams and provides continuous process improvement to reduce the probability of radiating incorrect commands to a spacecraft. The MO&CA task has evolved from participating as a member of the spacecraft team to an independent team reporting directly to flight project management and providing system level assurance. JPL flight projects have benefited significantly from MO&CA's effort to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit from previous and ongoing flight experience.

Proximity Operations Nano-Satellite Flight Demonstration (PONSFD) Rendezvous Proximity Operations Design and Trade Studies

NASA Astrophysics Data System (ADS)

Griesbach, J.; Westphal, J. J.; Roscoe, C.; Hawes, D. R.; Carrico, J. P.

2013-09-01

The Proximity Operations Nano-Satellite Flight Demonstration (PONSFD) program is to demonstrate rendezvous proximity operations (RPO), formation flying, and docking with a pair of 3U CubeSats. The program is sponsored by NASA Ames via the Office of the Chief Technologist (OCT) in support of its Small Spacecraft Technology Program (SSTP). The goal of the mission is to demonstrate complex RPO and docking operations with a pair of low-cost 3U CubeSat satellites using passive navigation sensors. The program encompasses the entire system evolution including system design, acquisition, satellite construction, launch, mission operations, and final disposal. The satellite is scheduled for launch in Fall 2015 with a 1-year mission lifetime. This paper provides a brief mission overview but will then focus on the current design and driving trade study results for the RPO mission specific processor and relevant ground software. The current design involves multiple on-board processors, each specifically tasked with providing mission critical capabilities. These capabilities range from attitude determination and control to image processing. The RPO system processor is responsible for absolute and relative navigation, maneuver planning, attitude commanding, and abort monitoring for mission safety. A low power processor running a Linux operating system has been selected for implementation. Navigation is one of the RPO processor's key tasks. This entails processing data obtained from the on-board GPS unit as well as the on-board imaging sensors. To do this, Kalman filters will be hosted on the processor to ingest and process measurements for maintenance of position and velocity estimates with associated uncertainties. While each satellite carries a GPS unit, it will be used sparsely to conserve power. As such, absolute navigation will mainly consist of propagating past known states, and relative navigation will be considered to be of greater importance. For relative observations, each spacecraft hosts 3 electro-optical sensors dedicated to imaging the companion satellite. The image processor will analyze the images to obtain estimates for range, bearing, and pose, with associated rates and uncertainties. These observations will be fed to the RPO processor's relative Kalman filter to perform relative navigation updates. This paper includes estimates for expected navigation accuracies for both absolute and relative position and velocity. Another key task for the RPO processor is maneuver planning. This includes automation to plan maneuvers to achieve a desired formation configuration or trajectory (including docking), as well as automation to safely react to potentially dangerous situations. This will allow each spacecraft to autonomously plan fuel-efficient maneuvers to achieve a desired trajectory as well as compute adjustment maneuvers to correct for thrusting errors. This paper discusses results from a trade study that has been conducted to examine maneuver targeting algorithms required on-board the spacecraft. Ground software will also work in conjunction with the on-board software to validate and approve maneuvers as necessary.

Reactive Sequencing for Autonomous Navigation Evolving from Phoenix Entry, Descent, and Landing

NASA Technical Reports Server (NTRS)

Grasso, Christopher A.; Riedel, Joseph E.; Vaughan, Andrew T.

2010-01-01

Virtual Machine Language (VML) is an award-winning advanced procedural sequencing language in use on NASA deep-space missions since 1997, and was used for the successful entry, descent, and landing (EDL) of the Phoenix spacecraft onto the surface of Mars. Phoenix EDL utilized a state-oriented operations architecture which executed within the constraints of the existing VML 2.0 flight capability, compatible with the linear "land or die" nature of the mission. The intricacies of Phoenix EDL included the planned discarding of portions of the vehicle, the complex communications management for relay through on-orbit assets, the presence of temporally indeterminate physical events, and the need to rapidly catch up four days of sequencing should a reboot of the spacecraft flight computer occur shortly before atmospheric entry. These formidable operational challenges led to new techniques for packaging and coordinating reusable sequences called blocks using one-way synchronization via VML sequencing global variable events. The coordinated blocks acted as an ensemble to land the spacecraft, while individually managing various elements in as simple a fashion as possible. This paper outlines prototype VML 2.1 flight capabilities that have evolved from the one-way synchronization techniques in order to implement even more ambitious autonomous mission capabilities. Target missions for these new capabilities include autonomous touch-and-go sampling of cometary and asteroidal bodies, lunar landing of robotic missions, and ultimately landing of crewed lunar vehicles. Close proximity guidance, navigation, and control operations, on-orbit rendezvous, and descent and landing events featured in these missions require elaborate abort capability, manifesting highly non-linear scenarios that are so complex as to overtax traditional sequencing, or even the sort of one-way coordinated sequencing used during EDL. Foreseeing advanced command and control needs for small body and lunar landing guidance, navigation and control scenarios, work began three years ago on substantial upgrades to VML that are now being exercised in scenarios for lunar landing and comet/asteroid rendezvous. The advanced state-based approach includes coordinated state transition machines with distributed decision-making logic. These state machines are not merely sequences - they are reactive logic constructs capable of autonomous decision making within a well-defined domain. Combined with the JPL's AutoNav software used on Deep Space 1 and Deep Impact, the system allows spacecraft to autonomously navigate to an unmapped surface, soft-contact, and either land or ascend. The state machine architecture enabled by VML 2.1 has successfully performed sampling missions and lunar descent missions in a simulated environment, and is progressing toward flight capability. The authors are also investigating using the VML 2.1 flight director architecture to perform autonomous activities like rendezvous with a passive hypothetical Mars sample return capsule. The approach being pursued is similar to the touch-and-go sampling state machines, with the added complications associated with the search for, physical capture of, and securing of a separate spacecraft. Complications include optically finding and tracking the Orbiting Sample Capsule (OSC), keeping the OSC illuminated, making orbital adjustments, and physically capturing the OSC. Other applications could include autonomous science collection and fault compensation.

Rapid Diagnostics of Onboard Sequences

NASA Technical Reports Server (NTRS)

Starbird, Thomas W.; Morris, John R.; Shams, Khawaja S.; Maimone, Mark W.

2012-01-01

Keeping track of sequences onboard a spacecraft is challenging. When reviewing Event Verification Records (EVRs) of sequence executions on the Mars Exploration Rover (MER), operators often found themselves wondering which version of a named sequence the EVR corresponded to. The lack of this information drastically impacts the operators diagnostic capabilities as well as their situational awareness with respect to the commands the spacecraft has executed, since the EVRs do not provide argument values or explanatory comments. Having this information immediately available can be instrumental in diagnosing critical events and can significantly enhance the overall safety of the spacecraft. This software provides auditing capability that can eliminate that uncertainty while diagnosing critical conditions. Furthermore, the Restful interface provides a simple way for sequencing tools to automatically retrieve binary compiled sequence SCMFs (Space Command Message Files) on demand. It also enables developers to change the underlying database, while maintaining the same interface to the existing applications. The logging capabilities are also beneficial to operators when they are trying to recall how they solved a similar problem many days ago: this software enables automatic recovery of SCMF and RML (Robot Markup Language) sequence files directly from the command EVRs, eliminating the need for people to find and validate the corresponding sequences. To address the lack of auditing capability for sequences onboard a spacecraft during earlier missions, extensive logging support was added on the Mars Science Laboratory (MSL) sequencing server. This server is responsible for generating all MSL binary SCMFs from RML input sequences. The sequencing server logs every SCMF it generates into a MySQL database, as well as the high-level RML file and dictionary name inputs used to create the SCMF. The SCMF is then indexed by a hash value that is automatically included in all command EVRs by the onboard flight software. Second, both the binary SCMF result and the RML input file can be retrieved simply by specifying the hash to a Restful web interface. This interface enables command line tools as well as large sophisticated programs to download the SCMF and RMLs on-demand from the database, enabling a vast array of tools to be built on top of it. One such command line tool can retrieve and display RML files, or annotate a list of EVRs by interleaving them with the original sequence commands. This software has been integrated with the MSL sequencing pipeline where it will serve sequences useful in diagnostics, debugging, and situational awareness throughout the mission.

Writing executable assertions to test flight software

NASA Technical Reports Server (NTRS)

Mahmood, A.; Andrews, D. M.; Mccluskey, E. J.

1984-01-01

An executable assertion is a logical statement about the variables or a block of code. If there is no error during execution, the assertion statement results in a true value. Executable assertions can be used for dynamic testing of software. They can be employed for validation during the design phase, and exception and error detection during the operation phase. The present investigation is concerned with the problem of writing executable assertions, taking into account the use of assertions for testing flight software. They can be employed for validation during the design phase, and for exception handling and error detection during the operation phase The digital flight control system and the flight control software are discussed. The considered system provides autopilot and flight director modes of operation for automatic and manual control of the aircraft during all phases of flight. Attention is given to techniques for writing and using assertions to test flight software, an experimental setup to test flight software, and language features to support efficient use of assertions.

cFE/CFS (Core Flight Executive/Core Flight System)

NASA Technical Reports Server (NTRS)

Wildermann, Charles P.

2008-01-01

This viewgraph presentation describes in detail the requirements and goals of the Core Flight Executive (cFE) and the Core Flight System (CFS). The Core Flight Software System is a mission independent, platform-independent, Flight Software (FSW) environment integrating a reusable core flight executive (cFE). The CFS goals include: 1) Reduce time to deploy high quality flight software; 2) Reduce project schedule and cost uncertainty; 3) Directly facilitate formalized software reuse; 4) Enable collaboration across organizations; 5) Simplify sustaining engineering (AKA. FSW maintenance); 6) Scale from small instruments to System of Systems; 7) Platform for advanced concepts and prototyping; and 7) Common standards and tools across the branch and NASA wide.

26th Space Simulation Conference Proceedings. Environmental Testing: The Path Forward

NASA Technical Reports Server (NTRS)

Packard, Edward A.

2010-01-01

Topics covered include: A Multifunctional Space Environment Simulation Facility for Accelerated Spacecraft Materials Testing; Exposure of Spacecraft Surface Coatings in a Simulated GEO Radiation Environment; Gravity-Offloading System for Large-Displacement Ground Testing of Spacecraft Mechanisms; Microscopic Shutters Controlled by cRIO in Sounding Rocket; Application of a Physics-Based Stabilization Criterion to Flight System Thermal Testing; Upgrade of a Thermal Vacuum Chamber for 20 Kelvin Operations; A New Approach to Improve the Uniformity of Solar Simulator; A Perfect Space Simulation Storm; A Planetary Environmental Simulator/Test Facility; Collimation Mirror Segment Refurbishment inside ESA s Large Space; Space Simulation of the CBERS 3 and 4 Satellite Thermal Model in the New Brazilian 6x8m Thermal Vacuum Chamber; The Certification of Environmental Chambers for Testing Flight Hardware; Space Systems Environmental Test Facility Database (SSETFD), Website Development Status; Wallops Flight Facility: Current and Future Test Capabilities for Suborbital and Orbital Projects; Force Limited Vibration Testing of JWST NIRSpec Instrument Using Strain Gages; Investigation of Acoustic Field Uniformity in Direct Field Acoustic Testing; Recent Developments in Direct Field Acoustic Testing; Assembly, Integration and Test Centre in Malaysia: Integration between Building Construction Works and Equipment Installation; Complex Ground Support Equipment for Satellite Thermal Vacuum Test; Effect of Charging Electron Exposure on 1064nm Transmission through Bare Sapphire Optics and SiO2 over HfO2 AR-Coated Sapphire Optics; Environmental Testing Activities and Capabilities for Turkish Space Industry; Integrated Circuit Reliability Simulation in Space Environments; Micrometeoroid Impacts and Optical Scatter in Space Environment; Overcoming Unintended Consequences of Ambient Pressure Thermal Cycling Environmental Tests; Performance and Functionality Improvements to Next Generation Thermal Vacuum Control System; Robotic Lunar Lander Development Project: Three-Dimensional Dynamic Stability Testing and Analysis; Thermal Physical Properties of Thermal Coatings for Spacecraft in Wide Range of Environmental Conditions: Experimental and Theoretical Study; Molecular Contamination Generated in Thermal Vacuum Chambers; Preventing Cross Contamination of Hardware in Thermal Vacuum Chambers; Towards Validation of Particulate Transport Code; Updated Trends in Materials' Outgassing Technology; Electrical Power and Data Acquisition Setup for the CBER 3 and 4 Satellite TBT; Method of Obtaining High Resolution Intrinsic Wire Boom Damping Parameters for Multi-Body Dynamics Simulations; and Thermal Vacuum Testing with Scalable Software Developed In-House.

Benefits of Spacecraft Level Vibration Testing

NASA Technical Reports Server (NTRS)

Gordon, Scott; Kern, Dennis L.

2015-01-01

NASA-HDBK-7008 Spacecraft Level Dynamic Environments Testing discusses the approaches, benefits, dangers, and recommended practices for spacecraft level dynamic environments testing, including vibration testing. This paper discusses in additional detail the benefits and actual experiences of vibration testing spacecraft for NASA Goddard Space Flight Center (GSFC) and Jet Propulsion Laboratory (JPL) flight projects. JPL and GSFC have both similarities and differences in their spacecraft level vibration test approach: JPL uses a random vibration input and a frequency range usually starting at 5 Hz and extending to as high as 250 Hz. GSFC uses a sine sweep vibration input and a frequency range usually starting at 5 Hz and extending only to the limits of the coupled loads analysis (typically 50 to 60 Hz). However, both JPL and GSFC use force limiting to realistically notch spacecraft resonances and response (acceleration) limiting as necessary to protect spacecraft structure and hardware from exceeding design strength capabilities. Despite GSFC and JPL differences in spacecraft level vibration test approaches, both have uncovered a significant number of spacecraft design and workmanship anomalies in vibration tests. This paper will give an overview of JPL and GSFC spacecraft vibration testing approaches and provide a detailed description of spacecraft anomalies revealed.

Workstation-Based Avionics Simulator to Support Mars Science Laboratory Flight Software Development

NASA Technical Reports Server (NTRS)

Henriquez, David; Canham, Timothy; Chang, Johnny T.; McMahon, Elihu

2008-01-01

The Mars Science Laboratory developed the WorkStation TestSet (WSTS) to support flight software development. The WSTS is the non-real-time flight avionics simulator that is designed to be completely software-based and run on a workstation class Linux PC. This provides flight software developers with their own virtual avionics testbed and allows device-level and functional software testing when hardware testbeds are either not yet available or have limited availability. The WSTS has successfully off-loaded many flight software development activities from the project testbeds. At the writing of this paper, the WSTS has averaged an order of magnitude more usage than the project's hardware testbeds.

Disruption Tolerant Networking Flight Validation Experiment on NASA's EPOXI Mission

NASA Technical Reports Server (NTRS)

Wyatt, Jay; Burleigh, Scott; Jones, Ross; Torgerson, Leigh; Wissler, Steve

2009-01-01

In October and November of 2008, the Jet Propulsion Laboratory installed and tested essential elements of Delay/Disruption Tolerant Networking (DTN) technology on the Deep Impact spacecraft. This experiment, called Deep Impact Network Experiment (DINET), was performed in close cooperation with the EPOXI project which has responsibility for the spacecraft. During DINET some 300 images were transmitted from the JPL nodes to the spacecraft. Then they were automatically forwarded from the spacecraft back to the JPL nodes, exercising DTN's bundle origination, transmission, acquisition, dynamic route computation, congestion control, prioritization, custody transfer, and automatic retransmission procedures, both on the spacecraft and on the ground, over a period of 27 days. All transmitted bundles were successfully received, without corruption. The DINET experiment demonstrated DTN readiness for operational use in space missions. This activity was part of a larger NASA space DTN development program to mature DTN to flight readiness for a wide variety of mission types by the end of 2011. This paper describes the DTN protocols, the flight demo implementation, validation metrics which were created for the experiment, and validation results.

Standardization and program effect analysis (Study 2.4). Volume 2: Equipment commonality analysis. [cost savings of using flight-proven components in designing spacecraft

NASA Technical Reports Server (NTRS)

Shiokari, T.

1975-01-01

The feasibility and cost savings of using flight-proven components in designing spacecraft were investigated. The components analyzed were (1) large space telescope, (2) stratospheric aerosol and gas equipment, (3) mapping mission, (4) solar maximum mission, and (5) Tiros-N. It is concluded that flight-proven hardware can be used with not-too-extensive modification, and significant savings can be realized. The cost savings for each component are presented.

Deep Space 1 fairing arrives at pad 17A for launch

NASA Technical Reports Server (NTRS)

1998-01-01

The fairing for Deep Space 1 nears the top of the Mobile Service Tower before being attached to the Boeing Delta 7326 rocket that will launch on Oct. 15, 1998. The first flight in NASA's New Millennium Program, Deep Space 1 is designed to validate 12 new technologies for scientific space missions of the next century. Onboard experiments include an ion propulsion engine and software that tracks celestial bodies so the spacecraft can make its own navigation decisions without the intervention of ground controllers. Deep Space 1 will complete most of its mission objectives within the first two months, but will also do a flyby of a near-Earth asteroid, 1992 KD, in July 1999.

Smart SPHERES: A Telerobotic Free-Flyer for Intravehicular Activities in Space

NASA Technical Reports Server (NTRS)

Fong, Terrence; Micire, Mark J.; Morse, Ted; Park, Eric; Provencher, Chris; To, Vinh; Wheeler, D. W.; Mittman, David; Torres, R. Jay; Smith, Ernest

2013-01-01

Smart SPHERES is a prototype free-flying space robot based on the SPHERES platform. Smart SPHERES can be remotely operated by astronauts inside a spacecraft, or by mission controllers on the ground. We developed Smart SPHERES to perform a variety of intravehicular activities (IVA), such as operations inside the International Space Station (ISS). These IVA tasks include environmental monitoring surveys (radiation, sound levels, etc.), inventory, and mobile camera work. In this paper, we first discuss the motivation for free-flying space robots. We then describe the development of the Smart SPHERES prototype, including avionics, software, and data communications. Finally, we present results of initial flight tests on-board the ISS.