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.
Inertial Upper Stage (IUS) and DoD Communication Interface Unit (CIU) communication system design, hardware specifications, and interfaces were evaluated to determine their compatibility with the Orbiter payload communication and data handling equipment and the Orbiter network communication equipment.
National Space Development Agency of Japan (NASDA) is developing the Japanese Experiment Module (JEM), as its contribution to the International Space Station. The JEM consists of the pressurized module (PM), the exposed facility (EF), the experiment logistics module pressurized section (ELM-PS), the experiment logistics module exposed section (ELM-ES) and the Remote Manipulator System (RMS). The JEMRMS services for the JEM EF, which is a space experiment platform, consists of the Main Arm (MA), the Small Fine Arm (SFA) and the RMS console. The MA handles the JEM EF payloads, the SFA and the JEM element, such as ELM-ES.
The Mission Analysis Division of the Systems Analysis and Integration Laboratory at the Marshall Space Flight Center is developing a system of programs to handle all aspects of scheduling payload operations for Space Station. The Expert Scheduling Program (ESP2) is the heart of this system. The task of payload operations scheduling can be simply stated as positioning the payload activities in a mission so that they collect their desired data without interfering with other activities or violating mission constraints. ESP2 is an advanced version of the Experiment Scheduling Program (ESP) which was developed by the Mission Integration Branch beginning in 1979 to schedule Spacelab payload activities. The automatic scheduler in ESP2 is an expert system that embodies the rules that expert planners would use to schedule payload operations by hand. This scheduler uses depth-first searching, backtracking, and forward chaining techniques to place an activity so that constraints (such as crew, resources, and orbit opportunities) are not violated. It has an explanation facility to show why an activity was or was not scheduled at a certain time. The ESP2 user can also place the activities in the schedule manually. The program offers graphical assistance to the user and will advise when constraints are being violated. ESP2 also has an option to identify conflict introduced into an existing schedule by changes to payload requirements, mission constraints, and orbit opportunities.
The Photon Sieve (PS) team at NASA Langley Research Center (LaRC) began receiving support for the development and characterization of PS devices through the NASA Internal Research & Development Program (IRAD) in 2015. The project involves ascertaining the imaging characteristics of various PS devices. These devices hold the potential to significantly reduce mission costs and improve imaging quality by replacing traditional reflector telescopes. The photon sieve essentially acts as a lens to diffract light to a concentrated point on the focal plane like a Fresnel Zone Plate (FZP). PS’s have the potential to focus light to a very small spot which is not limited by the width of the outermost zone as for the FZP and offers a promising solution for high resolution imaging. In the fields of astronomy, remote sensing, and other applications that require imaging of distant objects both on the ground and in the sky, it is often necessary to perform post-process filtering in order to separate noise signals that arise from multiple scattering events near the collection optic. The PS exhibits a novel filtering technique that rejects the unwanted noise without the need for time consuming post processing of the images. This project leverages key Langley resources to design, manufacture, and characterize a series of photon sieve specimens. After a prototype was developed and characterized in the Langley ISO5 optical cleanroom and laboratory, outside testing was conducted via the capture of images of the moon by using a telescopic setup. This next goal of the project is to design and develop a telescope and image capture system as a drone-based instrument payload. The vehicle utilized for the initial demonstration was a NASA hive model 1200 XE-8 research Unmanned Aerial Vehicle (UAV), capable of handling a 20-pound maximum payload with a 25-minute flight time. This NASA Technical Memorandum (NASA-TM) introduces preliminary results obtained using a PS-based imaging system on the UAV. The next version of the telescope structure will be designed around diffractive optical components and commercially available camera electronics to create a lightweight payload.
Astronaut Deployed Services Bus and Payload Solution
NASA's New Millenium Program (NMP) has identified a variety of revolutionary technologies that will support orders of magnitude improvements in the capabilities of spacecraft missions. This program's Autonomy team has focused on science and engineering automation technologies. In doing so, it has established a clear development roadmap specifying the experiments and demonstrations required to mature these technologies. The primary developmental thrusts of this roadmap are in the areas of remote agents, PI/operator interface, planning/scheduling fault management, and smart execution architectures. Phases 1 and 2 of the ASSET Project (previously known as the WebSat project) have focused on establishing World Wide Web-based commanding and telemetry services as an advanced means of interfacing a spacecraft system with the PI and operators. Current automated capabilities include Web-based command submission, limited contact scheduling, command list generation and transfer to the ground station, spacecraft support for demonstrations experiments, data transfer from the ground station back to the ASSET system, data archiving, and Web-based telemetry distribution. Phase 2 was finished in December 1996. During January-December 1997 work was commenced on Phase 3 of the ASSET Project. Phase 3 is the subject of this report. This phase permitted SSDL and its project partners to expand the ASSET system in a variety of ways. These added capabilities included the advancement of ground station capabilities, the adaptation of spacecraft on-board software, and the expansion of capabilities of the ASSET management algorithms. Specific goals of Phase 3 were: (1) Extend Web-based goal-level commanding for both the payload PI and the spacecraft engineer; (2) Support prioritized handling of multiple PIs as well as associated payload experimenters; (3) Expand the number and types of experiments supported by the ASSET system and its associated spacecraft; (4) Implement more advanced resource management, modeling and fault management capabilities that integrate the space and ground segments of the space system hardware; (5) Implement a beacon monitoring test; (6) Implement an experimental blackboard controller for space system management; (7) Further define typical ground station developments required for Internet-based remote control and for full system automation of the PI-to-spacecraft link. Each of those goals is examined in the next section. Significant sections of this report were also published as a conference paper.
Potential problems associated with interfacing payload elements with orbiter communications and data handling elements are identified. Elements include Ku-band signal processor (KuSP), payload signal processor (PSP), payload interrogator (PI), payload data interleaver (PDI) and payload recorder (PR).
A description is provided of the capabilities offered by the Spacelab design for doing research in space. The Spacelab flight vehicle consists of two basic elements including the habitable pressurized compartments and the unpressurized equipment mounting platforms. Spacelab services to payloads are considered, taking into account payload mass, electrical power and energy, heat rejection for Spacelab and payload, aspects of Spacelab data handling, and the extended flight capability. Attention is also given to the Spacelab structure, crew station and habitability, the electrical power distribution subsystem, the command and data management subsystem, the experiment computer operating system, the environmental control subsystem, the experiment vent assembly, the common payload support equipment, the instrument pointing subsystem, and details concerning the utilization of Spacelab.
In order to reduce the cost of landing small payloads on Mars, a new technology is being developed: the Small High Impact Energy Landing Device concept (SHIELD). The purpose of SHIELD is to provide a low-cost option to deliver up to 6 kg of science payload to the surface of Mars. SHIELD could be launched as a hosted payload, rideshare on an EELV secondary payload adapter (ESPA), or launching from a dedicated small launch vehicle using a kick stage. The SHIELD concept can achieve low-cost access to Mars by taking advantage of a low ballistic coefficient design to decelerate safely instead of using the typically required parachutes and/or propulsion to decelerate and stabilize itself during entry, decent, and landing (EDL). Current finite element simulations suggest that SHIELD would experience an impact acceleration pulse ranging from 1000 to 2000 g’s with a duration of 8 milliseconds. The SHIELD concept payload subsystem includes a “ruggedized” small warm electronics box (WEB). The WEB houses the telecommunications, command and data handling, thermal control, electrical power, and payload subsystems while maintaining an internal operating temperature ranging between -20° to 20° C. The system is designed to survive the Martian night by utilizing electric heaters powered with solar cells during the day and secondary batteries. The WEB is designed to be impact resistant capable of surviving an impact acceleration pulse equal to or less than 2000 g’s.
In order to reduce the cost of landing small payloads on Mars, a new technology is being developed: the Small High Impact Energy Landing Device concept (SHIELD). The purpose of SHIELD is to provide a low-cost option to deliver up to 6 kg of science payload to the surface of Mars. SHIELD could be launched as a hosted payload, rideshare on as a secondary payload adapter, or launching from a dedicated small launch vehicle using a kick stage to get to Mars. In order to enable delivery of low cost, SHIELD uses a large diameter deployed drag surface (> 2 m diameter) and low entry mass (< 50 kg) to achieve a very low ballistic coefficient (< 10 kg/m^2): this low ballistic coefficient results in low terminal velocity (< 70 m/sec) without requiring a parachute. Upon impacting the Martian surface at terminal velocity, SHIELD uses a mechanism to decelerate the payload to rest in a robust and predictable manner that limits acceleration of the payload to < 2000 g with a duration less than 8 milliseconds. The SHIELD concept payload subsystem includes a “ruggedized” small warm electronics box (WEB). The WEB houses the telecommunications, command and data handling, thermal control, electrical power, and payload subsystems while maintaining an internal operating temperature ranging between -20° to 20° C. The system is designed to survive the Martian night by utilizing electric heaters powered in a highly insulated box that is powered solar cells and secondary batteries. The WEB is designed to be impact resistant, capable of surviving an impact acceleration pulse equal to or less than 2000 g’s.
Ground systems operations at the National Aeronautics and Space Administration's (NASA) Payload Operations and Integration Function (POIF) is increasing, via the High Operations Tempo (HOT) initiative, its ability to support more science activities with a fourth crew member on the International Space Station (ISS). The Flight Control Team's need to support this increased crew presence mandated the need for a series of software tools to better handle the increasing pace of payload science operations. The overall need was clear from the outset, but the full scope and user experience for each tool, were not as well understood, so establishing a fixed set of initial requirements was not feasible. An Agile Software Development (ASD) paradigm takes advantage of uncertainty, and plans for it, so it was deemed the most appropriate approach to create room for exploring novel concepts, and to mount a rapid and flexible response to inevitiably changing requirements. It facilitated the need for unprecedented collaboration between the Product Team (i.e. users from the Flight Control Team) and the Development Team (i.e. POIC systems engineers, developers, testers). This is a process shift in the development, test, and release of software from one that is prescriptive to one that is adaptive, which is necessary for these tools to have longevity. The application of ASD to the product development lifecycle permitted the timely incorporation of customer feedback, and, allowed for continuous quality improvements. This resulted in a suite of tools that are efficient, user-friendly, and enable POIF ground systems to support the increasing pace of payload science operations. ASD is not as much a set of prescriptive processes as it is a shift in mindset; one that moves from planning against change, to planning for change, thereby iteratively growing software towards user-defined value.
The University of Colorado's first Get Away Special was conceived by a dozen science and engineering students in the spring of 1984. Since that time, the project has grown to include over 100 undergraduate and graduate students who have 'provided the experimental objectives, design, construction, integration, testing and management of the payload. Faculty and staff of the university and its affiliated laboratories as well as engineers from local industries have provided many useful suggestions at all stages of development. The principal motivation for developing this payload is to provide university students with the opportunity to participate in space science and engineering beginning at the ground level. At the same time, they are contributing their results from new science and technological discoveries to several disciplines. There are four separate experiments integrated into the /'single payload of G-285 which are supported by internal payload !power, thermal environment control, command land data handling [ facilities and structural subsystems. The four experiments contained in this payload are: a single spectrometer performing i two experiments- one to study night time shuttle glow phenomena in the ultraviolet and the other to observe NO2 concentrations over / equatorial latitudes in the day; a fluids management experiment ' using centrifugation for particle/liquid/vapor separation; and an experiment using Phycomyces fungi to study the gravireceptor mechanism theory. The experiments are supported by a microprocessor, data storage devices, power and thermal control subsystems. All these are located within a sealed aluminum container. The container, a refitted sounding rocket casing, has a top and bottom which bolt to the main body of the rocket section. The top section holds a five inch diameter quartz window through which light enters the spectrometer. A rotating mirror assembly and one of two battery boxes are mounted on the outside of the top section below the interface plane of the MDA. A second battery box is attached to the bottom section of the sealed container. All payload items except the battery boxes and mirror assembly are located inside the sealed rocket section to insure containment and to prevent outgassing of materials. The container will be sealed prior to launch and purged with one atmosphere of argon.
This report attempts to indicate the current status of Space Shuttle cargo handling analysis. It is intended for use by the various organizations operating in support of the Space Shuttle effort who are investigating problems not necessarily affected by the frequent configuration and approach changes imposed on the primary task team and contractor personnel. The various studies have been analyzed and the results interwoven with the results of in-house efforts. The problems involved in orbital docking, payload extraction and transfer, cargo handling, and special-purpose missions are discussed and some tentative conclusions and recommendations are presented. This report has been reviewed and approved for release by the MSFC Shuttle Task Team. However, no statements made herein should be interpreted as position statements with respect to the Space Shuttle, the direction of future efforts, or intended methods of operation. This document reflects the view of the author, following analysis of the data available, and should not be construed as an official recommendation.
The paper examines communications and data handling services that the Space Shuttle will provide for payloads and discusses mission and data processing capabilities. Uses of these capabilities are considered, and the Orbiter data processing system is described. Functional scientific data interfaces for attached payloads and functional system status data interfaces for attached payloads are indicated.
Lunar robotic functions include: 1. Transport of crew and payloads on the surface of the moon; 2. Offloading payloads from a lunar lander; 3. Handling the deployment of surface systems; with 4. Human commanding of these functions from inside a lunar vehicle, habitat, or extravehicular (space walk), with Earth-based supervision. The systems that will perform these functions may not look like robots from science fiction. In fact, robotic functions may be automated trucks, cranes and winches. Use of this equipment prior to the crew s arrival or in the potentially long periods without crews on the surface, will require that these systems be computer controlled machines. The public release of NASA's Exploration plans at the 2nd Space Exploration Conference (Houston, December 2006) included a lunar outpost with as many as four unique mobility chassis designs. The sequence of lander offloading tasks involved as many as ten payloads, each with a unique set of geometry, mass and interface requirements. This plan was refined during a second phase study concluded in August 2007. Among the many improvements to the exploration plan were a reduction in the number of unique mobility chassis designs and a reduction in unique payload specifications. As the lunar surface system payloads have matured, so have the mobility and offloading functional requirements. While the architecture work continues, the community can expect to see functional requirements in the areas of surface mobility, surface handling, and human-systems interaction as follows: Surface Mobility 1. Transport crew on the lunar surface, accelerating construction tasks, expanding the crew s sphere of influence for scientific exploration, and providing a rapid return to an ascent module in an emergency. The crew transport can be with an un-pressurized rover, a small pressurized rover, or a larger mobile habitat. 2. Transport Extra-Vehicular Activity (EVA) equipment and construction payloads. 3. Transport habitats and power modules over long distances, pre-positioning them for the arrival of crew on a subsequent lander. Surface Handling 1. Offload surface system payloads from the lander, breaking launch restraints and power/data connections. Payloads may be offloaded to a wheeled vehicle for transport. 2. Deploy payloads from a wheeled vehicle at a field site, placing the payloads in their final use site on the ground or mating them with existing surface systems. 3. Support regolith collection, site preparation, berm construction, or other civil engineering tasks using tools and implements attached to rovers. Human-Systems Interaction 1. Provide a safe command and control interface for suited EVA to ride on and drive the vehicles, making sure that the systems are also safe for working near dismounted crew. 2. Provide an effective control system for IV crew to tele-operate vehicles, cranes and other equipment from inside the surface habitats with evolving independence from Earth. .. Provide a supervisory system that allows machines to be commanded from the ground, working across the Earth-Lunar time delays on the order of 5-10 seconds (round trip) to support operations when crew are not resident on the surface. Technology Development Needs 1. Surface vehicles that can dock, align and mate with outpost equipment such as landers, habitats and fluid/power interfaces. 2. Long life motors, drive trains, seals, motor electronics, sensors, processors, cable harnesses, and dash board displays. 3. Active suspension control, localization, high speed obstacle avoidance, and safety systems for operating near dismounted crew. 4. High specific energy and specific power batteries that are safe, rechargeable, and long lived.
The Automated Space System Experimental Testbed (ASSET) system is a simple yet comprehensive real-world operations network being developed. Phase 3 of the ASSET Project was January-December 1997 and is the subject of this report. This phase permitted SSDL and its project partners to expand the ASSET system in a variety of ways. These added capabilities included the advancement of ground station capabilities, the adaptation of spacecraft on-board software, and the expansion of capabilities of the ASSET management algorithms. Specific goals of Phase 3 were: (1) Extend Web-based goal-level commanding for both the payload PI and the spacecraft engineer. (2) Support prioritized handling of multiple (PIs) Principle Investigators as well as associated payload experimenters. (3) Expand the number and types of experiments supported by the ASSET system and its associated spacecraft. (4) Implement more advanced resource management, modeling and fault management capabilities that integrate the space and ground segments of the space system hardware. (5) Implement a beacon monitoring test. (6) Implement an experimental blackboard controller for space system management. (7) Further define typical ground station developments required for Internet-based remote control and for full system automation of the PI-to-spacecraft link. Each of those goals are examined. Significant sections of this report were also published as a conference paper. Several publications produced in support of this grant are included as attachments. Titles include: 1) Experimental Initiatives in Space System Operations; 2) The ASSET Client Interface: Balancing High Level Specification with Low Level Control; 3) Specifying Spacecraft Operations At The Product/Service Level; 4) The Design of a Highly Configurable, Reusable Operating System for Testbed Satellites; 5) Automated Health Operations For The Sapphire Spacecraft; 6) Engineering Data Summaries for Space Missions; and 7) Experiments In Automated Health Assessment And Notification For The Sapphire Microsatellite.
This paper summarizes a study of small orbital transfer vehicles to place payloads in orbits with altitudes above those of the standard Shuttle operations. The overall objective of the study is to examine the role of the small orbital transfer vehicle (SOTV) in Shuttle operations and to identify typical propulsion concepts for accomplishing the mission. Consideration is given to existing and planned systems and upper stages, along with new propulsion stages. The new propulsion concept development examines tandem and clustered solids, controlled solids, monopropellant and bipropellant liquids, and staged solid/liquid combinations. The paper presents considerations of the mission requirements, tradeoffs of the various configurations, and candidate selections. For the selected candidate concepts the performance, support equipment, operational considerations and program costs were determined. The results show that a new modular liquid stage system is cost effective in handling the majority of the payloads considered. The remainder of the payloads can be accomodated by existing systems.
In-Situ instruments are an integral part of mission designs for exploration of planetary surfaces. A technology gap exists today between sample acquisition and sample analysis tools. Integrated science payload packages need an integrated sample handling system.