SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Small Satellite Technology Initiative (SSTI) Lewis Spacecraft Program is evaluated. Spacecraft integration, test, launch, and spacecraft bus are discussed. Payloads and technology demonstrations are presented. Mission data management system and ground segment are also addressed.
The Telecommand Data Routing and Channel Services defined by the Consultative Committee for Space Data Systems (CCSDS) are flexible enough to support a myriad of commanding models. Because the standard is so broad, the traditional approach has been to implement only the portion of the standard needed by the particular spacecraft being tested/operated. Tasked with providing Telecommand Services for an entire class of spacecraft, where each spacecraft may choose any valid CCSDS commanding model, NASA Code 584 designed a common architecture capable of handling the full CCSDS protocol. The solution uses another CCSDS standard - the Standard Formatted Data Unit (SFDU) as the interface to the Telecommand Services. SFDUs provide a consistent way of labelling data objects, as well as allowing data objects to encapsulate other data objects. The resulting interface is: - Flexible: The full Data Routing and Channel Services are available via a single interface. The client (i.e. the command source) may enter commands at any layer within the protocol stack, specify any of the data aggregation or segmentation methods, and dynamically set any configuration parameter defined in the standard. - Object-oriented: Each object specifies both the data and the actions to be performed with the data. An object may contain other objects. - Expandable: New capabilities are added by defining new objects. Objects pass thru the protocol layers until they reach the applicable layer. The resulting design is: - Modular: The logic for each protocol layer is contained in a separate Application Program Interface (API). The objects used for the external interface are also used for communication between layers. - Distributable: The design can be split along any layer boundary for distribution across multiple machines. The objects ensure data consistency across platforms. This paper describes the SFDU-based interface and the resulting protocol implementation. The implementation is currently used by NASA (National Aeronautics and Space Administration) for integration & test of the microwave Anisotropy Probe (MAP) and Earth observer-I (EO-l) spacecraft. It will be used for post-launch operations of these spacecraft as well as the Imager for Magnetopause to Aurora Global Exploration (IMAGE) spacecraft.
This paper discusses the development and performance of the X-33 Aerospike Engine RealTime Model. This model was developed for the purposes of control law development, six degree-of-freedom trajectory analysis, vehicle system integration testing, and hardware-in-the loop controller verification. The Real-Time Model uses time-step marching solution of non-linear differential equations representing the physical processes involved in the operation of a liquid propellant rocket engine, albeit in a simplified form. These processes include heat transfer, fluid dynamics, combustion, and turbomachine performance. Two engine models are typically employed in order to accurately model maneuvering and the powerpack-out condition where the power section of one engine is used to supply propellants to both engines if one engine malfunctions. The X-33 Real-Time Model is compared to actual hot fire test data and is been found to be in good agreement.
Soybeans have been baselined to be grown in a habitat (Advanced Life Support Systems Integration Test Bed, ALSSITB) intended for evaluating advanced life support systems developed for long duration missions to the Moon or Mars. The ALSSITB is being constructed at NASA-Johnson Space Center and is composed of 5 chambers (4.6 m x 11.3 m each) and an airlock joined by an interconnecting tunnel (3.7 m x 19.2 m). Processed soy products such as soy milk and soy bread are planned to be incorporated into a nutritionally sound, plant-based food system. Since all consumables will be recycled and reused, volatile compounds evolved during the manufacturing of these food products need to be quantified to assess their impact on this closed loop system. Soy milk was made in a prototype machine and bread in a commercial bread baking machine. These machines were each placed in a tightly closed chamber and, at the completion of the process, air volatiles were identified and quantified by GC/MS. For soy milk, ethanol, acetaldehyde, methanol, hexanal, propanal and acetone and for soybread, acetaldehyde, ethanol, N-propanol and ethyl acetate were detected in significant quantities. The crew members will spend an average of 180 days in the ALSSITB and it was estimated that 138 batches of soy milk will be processed in the tunnel and 130 loaves of soybread would be baked in the habitat chamber during their stay. The aforementioned volatiles would surpass the 180 day Spacecraft Maximum Allowable Concentrations (SMACs) if no means of scrubbing are adapted which would lead to toxic levels of these compounds. Therefore, sufficient means for eliminating the contribution of volatiles evolved from food processing and preparation equipment needs to be provided in the ALSSITB.
This manuscript describes the Sensor Web Adaptive Resource Manager (SWARM) project. The primary focus of the project is on the design and prototyping of middleware for managing computing and network resources in a way that enables the information systems of satellite constellations to provide realtime performance within dynamic environments. The middleware has been prototyped, and it has been evaluated by employing it to manage a pool of distributed resources for the ITOS (Integrated Test and Operations System) satellite command and control software system. The design of the middleware is discussed and a summary of the evaluation effort is provided.
This paper describes the requirements, design, integration, test, performance, and lessons learned of NASA's Microwave Anisotropy Probe (MAP) propulsion subsystem. MAP was launched on a Delta-II launch vehicle from NASA's Kennedy Space Center on June 30, 2001. Due to instrument thermal stability requirements, the Earth-Sun L2 Lagrange point was selected for the mission orbit. The L2 trajectory incorporated phasing loops and a lunar gravity assist. The propulsion subsystem's requirements are to manage momentum, perform maneuvers during the phasing loops to set up the lunar swingby, and perform stationkeeping at L2 for 2 years. MAP's propulsion subsystem uses 8 thrusters which are located and oriented to provide attitude control and momentum management about all axes, and delta-V in any direction without exposing the instrument to the sun. The propellant tank holds 72 kg of hydrazine, which is expelled by unregulated blowdown pressurization. Thermal management is complex because no heater cycling is allowed at L2. Several technical challenges presented themselves during I and T, such as in-situ weld repairs and in-situ bending of thruster tubes to accommodate late changes in the observatory CG. On-orbit performance has been nominal, and all phasing loop, mid-course correction, and stationkeeping maneuvers have been successfully performed to date.
Goddard Space Flight Center (GSFC) Wallops Flight Facility (WFF) manages NASA's Shuttle Small Payloads Project (SSPP). The SSPP designs, develops, tests, integrates and flies a group of small payload carrier systems for the space shuttle. These carriers - the Hitchhiker, Getaway Specials (GAS), and Space Experiment Module (SEM) - support payloads supplied by NASA, other U.S. government agencies, universities, high schools, domestic commercial customers, and foreign nationals and governments. These carriers can support payloads that range in size between 50 lbs. (23 kg) and 4,000 lbs. (2,270 kg).
The objective of this paper is to provide future ISS scientists and/or engineers with an overview of the coordination process for the preparation and implementation of the pre-launch checkout and transition activities as observed from the Marshall Control Flight Center (MSFC) Payload Operations Integration Center perspective. This includes 4 major phases: (1) Verification and validation of the new command and telemetry databases that are needed for new payload experiments and new onboard formats; (2) Integration testing of the new ground control software and hardware; (3) Final internal and external pre-launch checkouts with cadre and experiment teams; (4) Performance of the actual synchronized transition between MSFC, Johnson Space Center (JSC), and ISS onboard configuration to new onboard software, ground software, and databases.
An On-line Technology Information System (OTIS) is currently being developed for the Advanced Life Support (ALS) Program. This paper describes the preliminary development of OTIS, which is a system designed to provide centralized collection and organization of technology information. The lack of thorough, reliable and easily understood technology information is a major obstacle in effective assessment of technology development progress, trade studies, metric calculations, and technology selection for integrated testing. OTIS will provide a formalized, well-organized protocol to communicate thorough, accurate, current and relevant technology information between the hands-on technology developer and the ALS Community. The need for this type of information transfer system within the Solid Waste Management (SWM) element was recently identified and addressed. A SWM Technology Information Form (TIF) was developed specifically for collecting detailed technology information in the area of SWM. In the TIF, information is requested from SWM technology developers, based upon the Technology Readiness Level (TRL). Basic information is requested for low-TRL technologies, and more detailed information is requested as the TRL of the technology increases. A comparable form is also being developed for the wastewater processing element. In the future, similar forms will also be developed for the ALS elements of air revitalization, food processing, biomass production and thermal control. These ALS element-specific forms will be implemented in OTIS via a web-accessible interface,with the data stored in an object-oriented relational database (created in MySQLTM) located on a secure server at NASA Ames Research Center. With OTIS, ALS element leads and managers will be able to carry out informed research and development investment, thereby promoting technology through the TRL scale. OTIS will also allow analysts to make accurate evaluations of technology options. Additionally, the range and specificity of information solicited will help educate technology developers of programmatic needs.
Contents include the following: Advanced life support. System integration, modeling, and analysis. Progressive capabilities. Water processing. Air revitalization systems. Why advanced CO2 removal technology? Solid waste resource recovery systems: lyophilization. ISRU technologies for Mars life support. Atmospheric resources of Mars. N2 consumable/make-up for Mars life. Integrated test beds. Monitoring and controlling the environment. Ground-based commercial technology. Optimizing size vs capability. Water recovery systems. Flight verification topics.
We consider the effect of gravitational perturbations from Jupiter on the dynamics of asteroids, when Jupiter is itself perturbed by Saturn. The presence of Saturn introduces a number of additional frequencies into Jupiters orbit. These frequencies in turn produce chaos in narrow regions on either side of the chaotic zones associated with the mean motion resonances between the asteroids and Jupiter. The resonant arguments of these three-body resonances contain the longitudes of Jupiter and the asteroid together with either the secular frequency 9-6, or the longitude of Saturn. Resonances involving the longitude of Saturn are analogs of the Laplace resonance in the Jovian satellite system. We show that many three-body resonances involving the longitude of Saturn are chaotic. We give simple expressions for the width of the chaotic region and the associated Lyapunov time. In some cases the chaos can produce a diffusive growth in the 4 eccentricity of the asteroid that leads to ejection of the asteroid on times shorter than the age of the solar system. We give simple estimates for the diffusion time. Finally, we present the results of numerical integrations testing the theory.
Viewgraphs on Advanced Life Support (ALS) Systems are presented. The topics include: 1) Fundamental Need for Advanced Life Support; 2) ALS organization; 3) Requirements and Rationale; 4) Past Integrated tests; 5) The need for improvements in life support systems; 6) ALS approach to meet exploration goals; 7) ALS Projects showing promise to meet exploration goals; and 9) GRC involvement in ALS.
Virtual Flight - RITE (Rapid Integration Test Environment) is a NASA program devoted to the development of rapid prototyping technology for the design of aerospace vehicles. In the fourth simulation entry in this series of projects, a Crew Transfer Vehicle concept design developed at NASA-Ames Research Center was simulated. This concept vehicle, known as CTV8, is a delta-wing design with sharp leading edges to improve the hypersonic lift-to-drag ratio (L/D). Control surfaces included ailerons and elevators on the trailing edge of the wing, a rudder on the trailing edge of the vertical tail, and upper and lower body flaps (on the aft upper and lower edges of the fuselage) for speed control.
The Kepler mission will launch in 2007 and determine the distribution of earth-size planets (0.5 to 10 earth masses) in the habitable zones (HZs) of solar-like stars. The mission will monitor > 100,000 dwarf stars simultaneously for at least 4 years. Precision differential photometry will be used to detect the periodic signals of transiting planets. Kepler will also support asteroseismology by measuring the pressure-mode (p-mode) oscillations of selected stars. Key mission elements include a spacecraft bus and 0.95 meter, wide-field, CCD-based photometer injected into an earth-trailing heliocentric orbit by a 3-stage Delta II launch vehicle as well as a distributed Ground Segment and Follow-up Observing Program. The project is currently preparing for Preliminary Design Review (October 2004) and is proceeding with detailed design and procurement of long-lead components. In order to meet the unprecedented photometric precision requirement and to ensure a statistically significant result, the Kepler mission involves technical challenges in the areas of photometric noise and systematic error reduction, stability, and false-positive rejection. Programmatic and logistical challenges include the collaborative design, modeling, integration, test, and operation of a geographically and functionally distributed project. A very rigorous systems engineering program has evolved to address these challenges. This paper provides an overview of the Kepler systems engineering program, including some examples of our processes and techniques in areas such as requirements synthesis, validation & verification, system robustness design, and end-to-end performance modeling.
A new timing system has been developed for the NASA Deep Space Network (DSN) and is currently in the final stages of integration, testing and implementation in all three DSN sites. The DSN is a distributed antenna network for deep space communication, whose facilities are continuously engaged in spacecraft tracking, Very Long Baseline Interferometry (VLBI) or Radio Astronomy activities. Its primary components consist of three Deep Space Communication Centers (DSCC) separated nearly equidistant around the Earth in California, USA; Spain; and Australia. Within each DSCC, synchronized, low jitter timing signals must be distributed to many users over distances of up to 30 kilometers. The design criteria for the timing system required state of the art stability and jitter performance, but also extremely high operability and reliability. This paper describes some of the key features and recent system performance data as measured both in the laboratory and the operational DSN.
Desert "RATS" (Research and Technology Studies) is a combined, multi-discipline group of inter-NASA center scientists and engineers, net-working and collaborating with representatives of industry and academia, for the purpose of conducting planetary surface exploration-focused remote field exercises. These integrated testing exercises conducted under representative analog Lunar and Mars surface terrain conditions, provide NASA the capability to validate experimental prototype hardware and software systems as well as to evaluate and develop mission operational techniques in order to identify and establish technical requirements and identify potential technology "gaps" applicable for future planetary human exploration. The 2007 D-RATS field campaign test activities were initiated based on the major themes and objectives of a notional 5-year plan developed for conducting relative analog test activities in support of the engineering evaluation and assessment of various system architectural requirements, conceptual prototype support equipment and selected technologies necessary for the establishment of a lunar outpost. Specifically, the major objectives included measuring task efficiency during robot, human, and human-robot interactive tasks associated with lunar outpost site surveying and reconnaissance activities and deployment of a representative solar panel power and distribution system. In addition, technology demonstrations were conducted with a new Lithium-ion battery and autonomous software to coordinate multiple robot activities. Secondary objectives were evaluating airlock concept mockups and prototype removable space suit over-garment elements for dust mitigation, and upgrades to the prototype extravehicular activities (EVA) communication and information system. Dry run test activities, prior to testing at a designated remote field site location, were initially conducted at the Johnson Space Center (JSC) Remote Field Demonstration Test Site. This is a multi-acre external test site located at JSC and has detailed representative terrain features simulating both Lunar and Mars surface characteristics. Both the local JSC and remote field test sites have terrain conditions that are representative and characteristic of both the Moon and Mars, such as strewn rock and volcanic ash fields, craters, rolling plains, hills, gullies, slopes, and outcrops. The D-RATS 2007 field campaign, representing the completion of its tenth year of analog testing, was conducted at the large Cinder Lake volcanic ash bed area adjacent to Flagstaff, Arizona.
Virtual Satellite (VirtualSat) is a computer program that creates an environment that facilitates the development, verification, and validation of flight software for a single spacecraft or for multiple spacecraft flying in formation. In this environment, enhanced functionality and autonomy of navigation, guidance, and control systems of a spacecraft are provided by a virtual satellite that is, a computational model that simulates the dynamic behavior of the spacecraft. Within this environment, it is possible to execute any associated software, the development of which could benefit from knowledge of, and possible interaction (typically, exchange of data) with, the virtual satellite. Examples of associated software include programs for simulating spacecraft power and thermal- management systems. This environment is independent of the flight hardware that will eventually host the flight software, making it possible to develop the software simultaneously with, or even before, the hardware is delivered. Optionally, by use of interfaces included in VirtualSat, hardware can be used instead of simulated. The flight software, coded in the C or C++ programming language, is compilable and loadable into VirtualSat without any special modifications. Thus, VirtualSat can serve as a relatively inexpensive software test-bed for development test, integration, and post-launch maintenance of spacecraft flight software.
This annual report describes work to integrate a set of tools to support early model-based analysis of failures and hazards due to system-software interactions. The tools perform and assist analysts in the following tasks: 1) extract model parts from text for architecture and safety/hazard models; 2) combine the parts with library information to develop the models for visualization and analysis; 3) perform graph analysis and simulation to identify and evaluate possible paths from hazard sources to vulnerable entities and functions, in nominal and anomalous system-software configurations and scenarios; and 4) identify resulting candidate scenarios for software integration testing. There has been significant technical progress in model extraction from Orion program text sources, architecture model derivation (components and connections) and documentation of extraction sources. Models have been derived from Internal Interface Requirements Documents (IIRDs) and FMEA documents. Linguistic text processing is used to extract model parts and relationships, and the Aerospace Ontology also aids automated model development from the extracted information. Visualizations of these models assist analysts in requirements overview and in checking consistency and completeness.