Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “REUSABLE SPACECRAFT”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

Automated Diagnosis and Control of Complex Systems

Livingstone2 is a reusable, artificial intelligence (AI) software system designed to assist spacecraft, life support systems, chemical plants, or other complex systems by operating with minimal human supervision, even in the face of hardware failures or unexpected events. The software diagnoses the current state of the spacecraft or other system, and recommends commands or repair actions that will allow the system to continue operation. Livingstone2 is an enhancement of the Livingstone diagnosis system that was flight-tested onboard the Deep Space One spacecraft in 1999. This version tracks multiple diagnostic hypotheses, rather than just a single hypothesis as in the previous version. It is also able to revise diagnostic decisions made in the past when additional observations become available. In such cases, Livingstone might arrive at an incorrect hypothesis. Re-architecting and re-implementing the system in C++ has increased performance. Usability has been improved by creating a set of development tools that is closely integrated with the Livingstone2 engine. In addition to the core diagnosis engine, Livingstone2 includes a compiler that translates diagnostic models written in a Java-like language into Livingstone2's language, and a broad set of graphical tools for model development.

Kurien, James↗
NASA NTRS1991

Facilities for animal research in space

The animal facilities used aboard or designed for various spacecraft research missions are described. Consideration is given to the configurations used in Cosmos-1514 (1983) and Cosmos-1887 (1987) missions; the reusable Biosatellite capsule flown three times by NASA between 1966 and 1969; the NASA's Lifesat spacecraft that is being currently designed; the Animal Enclosure Module flown on Shuttle missions in 1983 and 1984; the Research Animal Holding Facility developed for Shuttle-Spacelab missions; the Rhesus Research Facility developed for a Spacelab mission; and the Japanese Animal Holding Facility for the Space Station Freedom. Special attention is given to the designs of NASA's animal facilities developed for Space Station Freedom and the details of various subsystems of these facilities. The main characteristics of the rodent and the primate habitats provided by these various facilities are discussed.

Bonting, Sjoerd L.↗
NASA NTRS1983

Application of a space station to communications satellites

The economic benefits of a space station relative to communications satellites are discussed in terms of technology experiments, spacecraft checkout, repair, servicing, and refurbishment (RSR), and mating an OTV with satellites for boost to GEO. The zero gravity, vacuum conditions, and atmosphere free long ranges are environmental features that can be used for testing large, flexible antennas and laser communications devices. Some resistance might be encountered to checkout in LEO due to the substantial success of launches to GEO without LEO checkout. However, new generations of larger, more complex satellites may warrant the presence of a space station to verify performance of new spacecraft. One RSR positive aspect for a space station is as a storage site for propellant, as well as for reusable OTV booster engines. Also, the space station can serve as a base for manned or unmanned repair spacecraft which will travel to GEO to fix malfunctions in geostationary satellites.

Ramler, J. R.↗
NASA NTRS2003

The X-38 Spacecraft Fault-Tolerant Avionics System

In 1995 NASA began an experimental program to develop a reusable crew return vehicle (CRV) for the International Space Station. The purpose of the CRV was threefold: (i) to bring home an injured or ill crewmember; (ii) to bring home the entire crew if the Shuttle fleet was grounded; and (iii) to evacuate the crew in the case of an imminent Station threat (i.e., fire, decompression, etc). Built at the Johnson Space Center, were two approach and landing prototypes and one spacecraft demonstrator (called V201). A series of increasingly complex ground subsystem tests were completed, and eight successful high-altitude drop tests were achieved to prove the design concept. In this program, an unprecedented amount of commercial-off-the-shelf technology was utilized in this first crewed spacecraft NASA has built since the Shuttle program. Unfortunately, in 2002 the program was canceled due to changing Agency priorities. The vehicle was 80% complete and the program was shut down in such a manner as to preserve design, development, test and engineering data. This paper describes the X-38 V201 fault-tolerant avionics system. Based on Draper Laboratory's Byzantine-resilient fault-tolerant parallel processing system and their "network element" hardware, each flight computer exchanges information on a strict timescale to process input data, compare results, and issue voted vehicle output commands. Major accomplishments achieved in this development include: (i) a space qualified two-fault tolerant design using mostly COTS (hardware and operating system); (ii) a single event upset tolerant network element board, (iii) on-the-fly recovery of a failed processor; (iv) use of synched cache; (v) realignment of memory to bring back a failed channel; (vi) flight code automatically generated from the master measurement list; and (vii) built in-house by a team of civil servants and support contractors. This paper will present an overview of the avionics system and the hardware implementation, as well as the system software and vehicle command & telemetry functions. Potential improvements and lessons learned on this program are also discussed.

Kouba,Coy↗
NASA NTRS1981

Thermal vacuum testing of flexible radiator systems

Flexible fin radiators are being developed to meet spacecraft requirements of light weight, compact launch volume, modular growth, reusability, and the capability of an on-orbit deployment and retraction. Two prototype versions of deployable/retractable, flexible finspace radiators (soft and hard tube) were tested simultaneously under thermal vacuum conditions. A map of the heat rejection performance of each radiator panel under various environmental conditions is given. The soft tube radiator deployment system demonstrated minimal gas pressure and was capable of maintaining partial deployment; temperature control was achieved by varying the deployment length. The radiator could be recovered after an inadvertant freezing of the coolant in the Teflon tube. The hard tube radiator deployment mechanism performed adequately throughout the testing, but did exhibit some undesirable performance characteristics. The hard tube radiator pressure drop was higher than expected, but was not affected by the length of deployment. The radiator operated at less than full deployment, and the manifolds were found to have a significant effect on heat rejection. At low-load conditions, the hard tube radiator appeared to bypass its deployed area.

Rankin, G.↗
NASA NTRS1998

Just the Right Amount of Reinforcement

Lockheed Martin Skunk Works, is taking the next step towards economical low-Earth-orbit (LEO) operations with NASA's X-33 technology demonstrator, that uses composite tanks for liquid hydrogen (LH sub2) fuel storage and structural support, The X-33 is a 53% scale model of the VentureStar single-stage-to-orbit (SSTO) reusable launch vehicle(RLV) projected to orbit payloads at a rate, of $1,000 per pound beginning in 2004 In order to make VentureStar completely reusable and economical engineers are using composite materials throughout the spacecrafts structure. The first test of the design comes in 1999 on the X-33 technology demonstrator. Two of the primary structures that engineers will be evaluating are the carbon fiber/epoxy LH2 fuel tanks. The 29-ft long by 18-ft wide tanks, which fill two-thirds of the X-33's interior, serve a dual purpose carrying fuel and providing structural support to the walls of the spacecraft. Fiber placement makes it possible to build the fuel tanks, large, light and strong enough to satisfy X33's requirements. Lockheed Martin choose the fabrication technology to produce the eight sections of each tank because of fiber placement's ability to handle complex surfaces, speed and repeatability.

Walton, Greg↗
NASA NTRS2001

A Survey of Power Electronics Applications in Aerospace Technologies

The insertion of power electronics in aerospace technologies is becoming widespread. The application of semiconductor devices and electronic converters, as summarized in this paper, includes the International Space Station, satellite power system, and motor drives in 'more electric' technology applied to aircraft, starter/generators and reusable launch vehicles. Flywheels, servo systems embodying electromechanical actuation, and spacecraft on-board electric propulsion are discussed. Continued inroad by power electronics depends on resolving incompatibility of using variable frequency for 400 Hz-operated aircraft equipment. Dual-use electronic modules should reduce system development cost.

Kankam, M. David↗
NASA NTRS1998

Integration of the Remote Agent for the NASA Deep Space One Autonomy Experiment

This paper describes the integration of the Remote Agent (RA), a spacecraft autonomy system which is scheduled to control the Deep Space 1 spacecraft during a flight experiment in 1999. The RA is a reusable, model-based autonomy system that is quite different from software typically used to control an aerospace system. We describe the integration challenges we faced, how we addressed them, and the lessons learned. We focus on those aspects of integrating the RA that were either easier or more difficult than integrating a more traditional large software application because the RA is a model-based autonomous system. A number of characteristics of the RA made integration process easier. One example is the model-based nature of RA. Since the RA is model-based, most of its behavior is not hard coded into procedural program code. Instead, engineers specify high level models of the spacecraft's components from which the Remote Agent automatically derives correct system-wide behavior on the fly. This high level, modular, and declarative software description allowed some interfaces between RA components and between RA and the flight software to be automatically generated and tested for completeness against the Remote Agent's models. In addition, the Remote Agent's model-based diagnosis system automatically diagnoses when the RA models are not consistent with the behavior of the spacecraft. In flight, this feature is used to diagnose failures in the spacecraft hardware. During integration, it proved valuable in finding problems in the spacecraft simulator or flight software. In addition, when modifications are made to the spacecraft hardware or flight software, the RA models are easily changed because they only capture a description of the spacecraft. one does not have to maintain procedural code that implements the correct behavior for every expected situation. On the other hand, several features of the RA made it more difficult to integrate than typical flight software. For example, the definition of correct behavior is more difficult to specify for a system that is expected to reason about and flexibly react to its environment than for a traditional flight software system. Consequently, whenever a change is made to the RA it is more time consuming to determine if the resulting behavior is correct. We conclude the paper with a discussion of future work on the Remote Agent as well as recommendations to ease integration of similar autonomy projects.

Dorais, Gregory A.↗
NASA NTRS1988

A flexible telemetry processor for spacecraft testing

In the past, telemetry data systems in support of JPL flight projects were designed specifically for each mission. The Magellan System Test Data Processing Subsystem (STDPS) marks a departure from these past designs. For the first time, a reusable telemetry-processing subsystem has been designed that is flexible enough to meet the spacecraft-testing requirements of the present project, and can be easily changed for future projects as well. These changes are all accomplished through a user-friendly, menu-oriented interface. Extensive software reprogramming is no longer required.

Leng, Christopher↗
NASA NTRS2000

Remote Agent Experiment

Remote Agent (RA) is a model-based, reusable artificial intelligence (At) software system that enables goal-based spacecraft commanding and robust fault recovery. RA was flight validated during an experiment on board of DS1 between May 17th and May 21th, 1999.

Benard, Doug↗
NASA NTRS2002

Integrated System Test of an Airbreathing Rocket

This viewgraph presentation provides information on NASA's attempts to develop an air-breathing propulsion in an effort to make future space transportation safer, more reliable and significantly less expensive than today's missions. Spacecraft powered by air-breathing rocket engines would be completely reusable, able to take off and land at airport runways and ready to fly again within days. A radical new engine project is called the Integrated System Tests of an Air-breathing Rocket, or ISTAR.

Mack, Gregory↗
NASA NTRS1996

Development of an automated control center for the EUVE mission

The Automated Project Operations Control Center (APOCC) was developed to enable automated data acquisition, ground system management and spacecraft health and safety monitoring. The control center will be used for the Extreme Ultraviolet Explorer (EUVE) project to reduce operations staffing from three to one shift per day, while maintaining the science return and performing routine health and safety monitoring activities. The staff reduction is expected to yield a cost reduction of 250,000 dollars per year in comparison with a fully staffed, 24 hour/day operation. The APOCC infrastructure was designed to be reusable and extensible. Configurable data items are stored in data bases and spacecraft-specific information is stored in a health and safety monitoring knowledge base.

Penafiel, Catherine↗
NASA NTRS2010

Reactive Sequencing for Autonomous Navigation Evolving from Phoenix Entry, Descent, and Landing

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.

asteroid↗
NASA NTRS1993

Conceptual design of a two stage to orbit spacecraft

This project, undertaken through the Advanced Space Design Program, developed a 'Conceptual Design of a Two Stage To Orbit Spacecraft (TSTO).' The design developed utilizes a combination of air breathing and rocket propulsion systems and is fully reusable, with horizontal takeoff and landing capability. The orbiter is carried in an aerodynamically designed bay in the aft section of the booster vehicle to the staging altitude. This TSTO Spacecraft design meets the requirements of replacing the aging Space Shuttle system with a more easily maintained vehicle with more flexible mission capability.

Armiger, Scott C.↗
NASA NTRSDate not supplied

Rapid Spacecraft Payload Development: In-Orbit Demonstration of Flight Software Reuse, Scalability, and Dependability

As space mission design trends towards shared, multi-mission platforms and high-performance onboard computing architectures, the number of spacecraft launched into operation is also steadily rising. Through ridesharing, spacecraft miniaturization, and other cost-reduction measures, the barriers to space are lowering, resulting in compounded growth in the amount of flight software being deployed. To meet the needs of both the growing quantity and evolving nature of spacecraft, flight software design must accordingly adapt to support more efficient development, solutions to computational resource-sharing, and software reusability. This paper focuses on a software payload demonstrating several core technologies that improve the state-of-the-art in these identified areas. Launched into low-earth orbit in January 2022, our software payload was conceived, designed, and delivered in a span of merely two months. It was developed on top of the NASA core Flight System (cFS) framework and the Distributed Spacecraft Autonomy (DSA) Comm cFS application, which translates cFS software bus messages across a Data Distribution Service (DDS) network. The flight software, packaged in Linux container images, was deployed as one of 18 flight applications managed through the Unibap SpaceCloud Framework. The applications were run on a Unibap iX5-102 radiation-tolerant payload computer, hosted on the D-Orbit SCV-004 spacecraft as part of an ESA-sponsored in-orbit technology test. Our payload, referred to as the DSA D-Orbit software, demonstrates the reusability of the DSA Comm app in a substantially different context and purpose as its original mission. Comm’s original design goal was to reliably distribute messages between spacecraft swarms of arbitrary size and dynamic network topology. However, we leverage this same functionality to introduce redundancy and opportunistic parallel data processing in the context of a representative onboard image processing workload. This adaptive mission architecture was enabled in part by the SpaceCloud Framework’s use of container virtualization as the payload integration interface. By using a base container image with common high-level language runtimes and libraries, we were able to rapidly design, develop, and validate our image processing application without many of the technological barriers common to flight software development. We present details the goals, approach, results, and lessons learned through this technology demonstration experiment and contextualize those observations against present and future challenges in spacecraft software development.

computer programming↗
NASA NTRS1991

Space Flyer Unit (SFU)

The DSN (Deep Space Network) mission support requirements for the Space Flyer Unit (SFU) are summarized. The SFU is an unmanned, reusable, and retrievable free-flying platform for multipurpose use. The SFU spacecraft will carry seven individual experiments to be completed during its mission period. The mission objectives are outlined and the DSN support requirements are defined through the presentation of tables and narratives describing the spacecraft flight profile; DSN support coverage; frequency assignments; support parameters for telemetry, command and support systems; and tracking support responsibility.

Ninomiya, T.↗
NASA NTRS1998

The Implementation of Satellite Control System Software Using Object Oriented Design

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.

Anderson, Mark O.↗
NASA NTRS2005

Reusable Hybrid Propellant Modules for Outer-Space Transport

A report summarizes the concept of reusable hybrid propellant modules (HPMs), which would be used in outer space for long-term cryogenic storage of liquefied spacecraft-propellant gases, including for example, oxygen and hydrogen for combustion-based chemical rocket engines and xenon for electric thrusters. The HPM concept would provide the fundamental building block for an efficient, reusable in-space transportation system for both crewed and uncrewed missions. Each HPM would be equipped to implement an advanced zero-boil-off method of managing cryogenic fluids, and would include a fluid-transfer interface comprising standardized fittings that would be compatible with fittings on all supply facilities and on spacecraft to be supplied. The HPM, combined with a chemical or electric orbital transfer spacecraft, would provide an integrated propulsion system. HPMs would supply chemical propellant for time-critical transfers such as crewed missions, and utilize the more efficient electric-propulsion transfer vehicles to transport filled HPMs to the destinations and to return empty HPMs back to near-Earth orbits or other intermediate locations for replenishment and reuse. The HPM prepositioned using electric propulsion would provide the chemical propellant for the crew s return trip in a much more efficient manner than a chemical-only approach. The propellants to fill the HPMs would be delivered from the Earth or other initial supply locations to the intermediate locations by use of automated, compatible spacecraft designed specifically for that purpose. Additionally, multiple HPMs could be aggregated and positioned in orbits and on planets, moons, and asteroids to supply fluids to orbiting and interplanetary spacecraft.

Mazanek, Daniel D.↗