Search NASA⌕ Search

SEARCH · Search NASA

Results for “command process”

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 955 records · Page 53

AFTI/F-111 airplane mission adaptive wing operational flight evaluation technique using uplinked pilot command cues

NASA and the USAF have conducted a program to investigate aircraft performance improvements utilizing a mission adaptive wing (MAW). The MAW was designed and developed for the AFTI/F-111 variable-sweep aircraft to provide a hydraulically driven, smooth, and continuous variable camber of the trailing and leading edges as a function of maneuvering requirements or of flight conditions. The remotely augmented vehicle facility (RAV) at the NASA DFRF, as utilized in the MAW investigations, is described. The RAV was a dedicated, ground based, general purpose facility capable of receiving a data stream downlinked from a test vehicle, processing this data stream in a digital computer, and transmitting processed data back to the test vehicle. It is shown that this method of flight testing provides a technique that can evaluate highly dynamic maneuvers.

Kempel, Robert W.↗

Constellation's Command, Control, Communications and Information (C3I) Architecture

Operations concepts are highly effective for: 1) Developing consensus; 2) Discovering stakeholder needs, goals, objectives; 3) Defining behavior of system components (especially emergent behaviors). An interoperability standard can provide an excellent lever to define the capabilities needed for system evolution. Two categories of architectures are needed in a program of this size are: 1) Generic - Needed for planning, design and construction standards; 2) Specific - Needed for detailed requirement allocations, interface specs. A wide variety of architectural views are needed to address stakeholder concerns, including: 1) Physical; 2) Information (structure, flow, evolution); 3) Processes (design, manufacturing, operations); 4) Performance; 5) Risk.

constellation↗

25 kW power module evolution study

This paper presents a study of evolutionary growth concepts for the 25 kW power module to augment STS mission support future capabilities. The study aimed to establish user payload requirements, define evolution methods for system initial operational capability, and formulate a development program and conceptual designs. The payload requirements analysis focused on material processing in space, public services, and solar terrestrial observations; evolutionary system concepts were evaluated to derive the power module and system support requirements, and four reference orbits were used to construct the nominal program scenario. The mission accomodations analysis evaluated the capability of the nominal program scenario and associated power module concepts to meet user needs. Finally, the recommended modular design consisting of electric power, attitude control, thermal control, and command and data handling is described, and it is concluded that the 25 kW power module is a logical first step to support the near term NASA sortie and free-flyer mission requirements.

Overall, J. W., Jr.↗

Science and Applications Space Platform (SASP) End-to-End Data System Study

The capability of present technology and the Tracking and Data Relay Satellite System (TDRSS) to accommodate Science and Applications Space Platforms (SASP) payload user's requirements, maximum service to the user through optimization of the SASP Onboard Command and Data Management System, and the ability and availability of new technology to accommodate the evolution of SASP payloads were assessed. Key technology items identified to accommodate payloads on a SASP were onboard storage devices, multiplexers, and onboard data processors. The primary driver is the limited access to TDRSS for single access channels due to sharing with all the low Earth orbit spacecraft plus shuttle. Advantages of onboard data processing include long term storage of processed data until TRDSS is accessible, thus reducing the loss of data, eliminating large data processing tasks at the ground stations, and providing a more timely access to the data.

Crawford, P. R.↗

The Global File System

The global file system (GFS) is a prototype design for a distributed file system in which cluster nodes physically share storage devices connected via a network-like fiber channel. Networks and network-attached storage devices have advanced to a level of performance and extensibility so that the previous disadvantages of shared disk architectures are no longer valid. This shared storage architecture attempts to exploit the sophistication of storage device technologies whereas a server architecture diminishes a device's role to that of a simple component. GFS distributes the file system responsibilities across processing nodes, storage across the devices, and file system resources across the entire storage pool. GFS caches data on the storage devices instead of the main memories of the machines. Consistency is established by using a locking mechanism maintained by the storage devices to facilitate atomic read-modify-write operations. The locking mechanism is being prototyped in the Silicon Graphics IRIX operating system and is accessed using standard Unix commands and modules.

Soltis, Steven R.↗

Impact to Space Shuttle Vehicle Trajectory on Day of Launch from change in Low Frequency Winds

The National Aeronautics and Space Administration's (NASA) Space Shuttle utilizes atmospheric winds on day of launch to develop throttle and steering commands to best optimize vehicle performance while keeping structural loading on the vehicle within limits. The steering commands and resultant trajectory are influenced by both the high and low frequency component of the wind. However, the low frequency component has a greater effect on the ascent design. Change in the low frequency wind content from the time of trajectory design until launch can induce excessive loading on the vehicle. Wind change limits have been derived to protect from launching in an environment where these temporal changes occur. Process of developing wind change limits are discussed followed by an observational study of temporal wind change in low frequency wind profiles at the NASA's Kennedy Space Center area are presented.

Decker, Ryan K.↗

The Deep Impact Network Experiment Operations Center

Delay/Disruption Tolerant Networking (DTN) promises solutions in solving space communications challenges arising from disconnections as orbiters lose line-of-sight with landers, long propagation delays over interplanetary links, and other phenomena. DTN has been identified as the basis for the future NASA space communications network backbone, and international standardization is progressing through both the Consultative Committee for Space Data Systems (CCSDS) and the Internet Engineering Task Force (IETF). JPL has developed an implementation of the DTN architecture, called the Interplanetary Overlay Network (ION). ION is specifically implemented for space use, including design for use in a real-time operating system environment and high processing efficiency. In order to raise the Technology Readiness Level of ION, the first deep space flight demonstration of DTN is underway, using the Deep Impact (DI) spacecraft. Called the Deep Impact Network (DINET), operations are planned for Fall 2008. An essential component of the DINET project is the Experiment Operations Center (EOC), which will generate and receive the test communications traffic as well as "out-of-DTN band" command and control of the DTN experiment, store DTN flight test information in a database, provide display systems for monitoring DTN operations status and statistics (e.g., bundle throughput), and support query and analyses of the data collected. This paper describes the DINET EOC and its value in the DTN flight experiment and potential for further DTN testing.

flight experiment↗

Best Practices Identified Through the Completion of UAS Flight Demonstrations

After several years of research into Detect and Avoid (DAA) and Command and Control (C2) systems for Unmanned Aircraft Systems (UAS), the National Aeronautics and Space Administration’s (NASA) UAS Integration into the National Airspace System project initiated a focused two-year effort along with the Federal Aviation Administration (FAA) and three industry partners to investigate remaining issues in the specification, test, certification and airspace integration to allow UAS operations in non-segregated airspace. The approach taken had the industry partners propose a flight demonstration approximating a commercial operation, while NASA helped, as needed, the partners through design and test phases and NASA observed interactions with the FAA. During this effort NASA collected best practices intended to be of value to similar UAS endeavors. These best practices can be divided into different sets, including practices that describe the relationship between business considerations to UAS design or describe several UAS development challenges. Another set includes best practices focused on navigating the UAS design and type certification processes. A third set includes best practices that relate to the design of the DAA system. Deploying DAA systems in this timeframe posed unique challenges. Commercial off-the-shelf DAA systems do not exist, necessitating custom development and, for two of the partners, the use of low-size, -weight, and -power (SWaP) sensors not completely specified for DAA. A fourth set of best practices relates to lost-link contingency planning. The final set of best practices relates to the design and testing of C2 systems and obtaining spectrum licenses. The UAS demonstrations were piloted remotely, and for all aspects of flight safety, a C2 system was required to communicate DAA and other UAS subsystem data to the remote pilot and to allow the pilot to issue commands to the vehicle. Throughout the course of this effort, the partners integrated prototype DAA and C2 systems into unmanned aircraft, tested those systems, and laid the groundwork for type certification programs that are expected to continue.

NASA↗

Center Director's Discretionary Fund 2005 Annual Report

The FY 2005 CDDF projects were selected from the following spaceport and range technology and science areas: fluid system technologies; spaceport structures and materials; command, control, and monitoring technologies; and biological sciences (including support for environmental stewardship). The FY 2005 CDDF research projects involved development of the following: a) Capacitance-based moisture sensors to optimize plant growth in reduced gravity; b) Commodity-free calibration methods; c) Application of atmospheric plasma glow discharge to alter the surface properties of polymers for improved electrostatic dissipation characteristics; d) A wipe-on, wipe-off chemical process to remove lead oxides found in paint; e) A robust metabolite profiling platform for better understanding the "law" of biological regulation; f) An explanation of the excavation processes that occur when a jet of gas impinges on a bed of sand; g) "Smart coatings" to detect and control corrosion at an early stage to prevent further corrosion h) A model that can produce a reliable diagnosis of the quality of a software product; i) The formulation of advanced materials to meet system safety needs to minimize electrostatic charges, flammability, and radiation exposure; j) A lab-based instrument that uses the electro-optic Pockels effect to make static electric fields visible; k) A passive volatile organic compound (VOC) cartridge to filter, identify, and quantify VOCs flowing into or emanating from plant flight experiments.

Nurge, Mark↗

Hypergolic Propellant Destruction Evaluation Cost Benefit Analysis

At space vehicle launch sites such as Vandenberg Air Force Base (VAFB), Cape Canaveral Air Force Station (CCAFS) and Kennedy Space Center (KSC), toxic vapors and hazardous liquid wastes result from the handling of commodities (hypergolic fuels and oxidizers), most notably from transfer operations where fuel and oxidizer are transferred from bulk storage tanks or transfer tankers to space launch vehicles. During commodity transfer at CCAFS and KSC, wet chemical scrubbers (typically containing four scrubbing towers) are used to neutralize fuel saturated vapors from vent systems on tanks and tanker trailers. For fuel vapors, a citric acid solution is used to scrub out most of the hydrazine. Operation of both the hypergolic fuel and oxidizer vapor scrubbers generates waste scrubber liquor. Currently, scrubber liquor from the fuel vapor scrubber is considered non-hazardous. The scrubber liquor is defined as spent citric acid scrubber solution; the solution contains complexed hydrazine I methylhydrazine and is used to neutralize nonspecification hypergolic fuel generated by CCAFS and KSC. This project is a collaborative effort between Air Force Space Command (AFSPC), Space and Missile Center (SMC), the CCAFS, and National Aeronautics and Space Administration (NASA) to evaluate microwave destruction technology for the treatment of non-specification hypergolic fuel generated at CCAFS and KSC. The project will capitalize on knowledge gained from microwave treatment work being accomplished by AFSPC and SMC at V AFB. This report focuses on the costs associated with the current non-specification hypergolic fuel neutralization process (Section 2.0) as well as the estimated costs of operating a mobile microwave unit to treat non-specification hypergolic fuel (Section 3.0), and compares the costs for each (Section 4.0).The purpose of this document is to assess the costs associated with waste hypergolic fuel. This document will report the costs associated with the current fuel neutralization process and also examine the costs of an alternative technology, microwave destruction of waste hypergolic fuel. The microwave destruction system is being designed as a mobile unit to treat non-specification hypergolic fuel at CCAFS and KSC.

Kessel, Kurt↗

Spaceport Command and Control System Software Development

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administration's (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This large system requires a large amount of intensive testing that will properly measure the capabilities of the system. Automating the test procedures would save the project money from human labor costs, as well as making the testing process more efficient. Therefore, the Exploration Systems Division (formerly the Electrical Engineering Division) at Kennedy Space Center (KSC) has recruited interns for the past two years to work alongside full-time engineers to develop these automated tests, as well as innovate upon the current automation process.

Glasser, Abraham↗

STS-99: Post Flight Presentation

Live footage shows the crewmembers of STS-99, Commander Kevin R. Kregel, Pilot Dominic L. Pudwill Gorie, and Mission Specialists Janet L. Kavandi, Janice E. Voss, Mamoru Mohri, and Gerhard P.J. Thiele, arriving at Kennedy Space Center (KSC) in the T-38 aircraft. Crewmembers are seen speaking to the welcoming crowd at KSC, suiting-up, walking out to the Astro-van, being strapped in the shuttle, and performing various activities while in orbit. Scenes include the astronaut training process, main engine ignition, liftoff, solid rocket booster separation, mast deployment and retraction, and the changing of the mapping tapes. Footage also includes the crewmembers sleeping, eating, exercising, dancing and having fun in zero gravity. The High Definition Television Camera (HDTV) picks up images from the Earth. These images includes Bolivia, Paraguay, Brazil, Bahamas, Mauritania, Saudi Arabia, Mount Fuji, Tokyo Bay, Southern Russia, the Black Sea, Equador, Northern Peru, the Mediterranean Sea, Malta, Sicily and Italy. The crewmembers of STS-99 each took a turn to narrate the scenes and events as they occur.

Source record↗

Lunar Dust and Lunar Simulant Activation, Monitoring, Solution and Cellular Toxicity Properties

During the Apollo missions, many undesirable situations were encountered that must be mitigated prior to returning humans to the moon. Lunar dust (that part of the lunar regolith less than 20 m in diameter) was found to produce several problems with astronaut s suits and helmets, mechanical seals and equipment, and could have conceivably produced harmful physiological effects for the astronauts. For instance, the abrasive nature of the dust was found to cause malfunctions of various joints and seals of the spacecraft and suits. Additionally, though efforts were made to exclude lunar dust from the cabin of the lunar module, a significant amount of material nonetheless found its way inside. With the loss of gravity correlated with ascent of the lunar module from the lunar surface to rendezvous with the command module, much of the major portions of the contaminating soil and dust began to float, irritating the astronaut s eyes and being inhaled into their lungs. Our goal has been to understand some of the properties of lunar dust that could lead to possible hazards for humans. Due to the lack of an atmosphere, there is nothing to protect the lunar soil from ultraviolet radiation, solar wind, and meteorite impacts. These processes could all serve to activate the soil, or produce reactive surface species. In order to understand the possible toxic effects of the reactive dust, it is necessary to reactivate the dust, as samples returned during the Apollo missions were exposed to the atmosphere of the Earth. We have used grinding and UV exposure to mimic some of the processes occurring on the Moon. The level of activation has been monitored using two methods: fluorescence spectroscopy and electron paramagnetic resonance spectroscopy (EPR). These techniques allow the monitoring of hydroxyl radical production in solution. We have found that grinding of lunar dust produces 2-3 times the concentration of hydroxyl radicals as lunar simulant and 10 times that of quartz. Exposure of the lunar dust to UV radiation under vacuum was also found to lead to hydroxyl radical production. After grinding, we have also monitored loss of reactivity of the dusts by exposing them to conditions of known humidity and temperature. From these tests, it was found that the reactivity half-life of lunar simulant is approximately 3 hours, while that of quartz is approximately 2 hours. Placing lunar dust in solution could lead to effects on mechanical and physiological systems, as well as other biological systems. For instance, while it is known that lunar dust is highly abrasive and caused a variety of problems with suits and equipment during Apollo, it is unknown as to how these properties might be affected in the presence of water or other liquids. It is possible that the dust may release minerals (e.g., metallic nanophase Fe) into solution that could speed corrosion or rust. Also, as lunar dust produces hydroxyl radicals (and possibly other reactive oxygen species) in solution, these radicals could also lead to the breakdown of suit or habitat materials. In the body (i.e., in lung solution), the effects could be two-fold. First, if the lunar dust dissolves, it may release an excess of elements (such as zero-valence metallic Fe) that are necessary for bodily functions but only in certain concentration ranges. For lunar dust, the presence of nanophase iron being released into the body is a concern. Secondly, the hydroxyl radicals or other reactive oxygen species produced by the dust in solution could conceivably interact with cells, leading to various problems. We have studied the dissolution of both ground and unground lunar simulant in buffer solutions of different pH. The concentration of a number of species was determined using mass spectrometry. These studies showed that lowering the pH of the solution causes a dramatic increase in the amount of each element released into solution and that grinding also produces higher concentrations. Finally, we have perfmed initial tests aimed at understanding the effects of lunar simulant on cellular systems. Alveolar epithelial cells were cultured and exposed to different concentrations of dust suspended in cell culture media. After predetermined amounts of time, the media was removed and the concentrations of important inflammatory cytokines (IL6, IL8, and TNF-alpha ) were measured. The results of these tests are being used to develop the correct protocols for tests to be performed using lunar dust samples.

Jeevarajan, A.S.↗

Program for Editing Spacecraft Command Sequences

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.

Gladden, Roy↗

Orbit Determination and Navigation Software Testing for the Mars Reconnaissance Orbiter

During the extended science phase of the Mars Reconnaissance Orbiter's lifecycle, the operational duties pertaining to navigation primarily involve orbit determination. The orbit determination process utilizes radiometric tracking data and is used for the prediction and reconstruction of MRO's trajectories. Predictions are done twice per week for ephemeris updates on-board the spacecraft and for planning purposes. Orbit Trim Maneuvers (OTM-s) are also designed using the predicted trajectory. Reconstructions, which incorporate a batch estimator, provide precise information about the spacecraft state to be synchronized with scientific measurements. These tasks were conducted regularly to validate the results obtained by the MRO Navigation Team. Additionally, the team is in the process of converting to newer versions of the navigation software and operating system. The capability to model multiple densities in the Martian atmosphere is also being implemented. However, testing outputs among these different configurations was necessary to ensure compliance to a satisfactory degree.

Deep Space Network↗

Simulation-to-Flight 1 (STF-1): Automating the Planning, Scheduling, Assessment and Data Processing/Reduction for a Small Satellite

On December 16, 2019, a 3-U CubeSat named STF-1 launched as West Virginia's first spacecraft. This event marked the culmination of a run-up to launch involving the production of the spacecraft, creation/configuration of command and control infrastructure, and the evolution of its co-creation, the NASA Operational Simulator for Small Satellites (NOS3). This event also marked the beginning of a new phase: operations. While plans, procedures, and infrastructure were already in place or started for operations, many lessons were learned during the operations phase, especially during early operations (first month/commissioning phase). Additional plans, procedures, and infrastructure, especially related to communication planning and automated data processing, were created and developed to fill needs for the operation of the STF-1 mission.This paper and presentation will overview the STF-1 operations team's solutions to addressing the many needs of operating a low-earth orbiting CubeSat mission with a single ground antenna that is shared and scheduled with several other missions. The STF-1 operations team deployed a combination of virtualization technologies, ground station technology solutions, collaboration software, custom planning software solutions, and existing ground antenna scheduling solutions to create an effective and efficient CubeSat operations environment. The end-solution satisfied the operations stakeholders, which include NASA, its industry partner TMC Technologies, and four independent professor-student teams at West Virginia University.

CubeSat↗

STF-1 Ground Operations - Automating the Planning, Scheduling, Assessment and Data Processing/Reduction for a Small Satellite

On December 16, 2018, a 3-U CubeSat named STF-1 launched as West Virginia's first spacecraft. This event marked the culmination of a run-up to launch involving the production of the spacecraft, creation/configuration of command and control infrastructure, and the evolution of its co-creation, the NASA Operational Simulator for Small Satellites (NOS3). This event also marked the beginning of a new phase: operations. While plans, procedures, and infrastructure were already in place or started for operations, many lessons were learned during the operations phase, especially during early operations (first month/commissioning phase). Additional plans, procedures, and infrastructure, especially related to communication planning and automated data processing, were created and developed to fill needs for the operation of the STF-1 mission.This paper and presentation will overview the STF-1 operations team's solutions to addressing the many needs of operating a low-earth orbiting CubeSat mission with a single ground antenna that is shared and scheduled with several other missions. The STF-1 operations team deployed a combination of virtualization technologies, ground station technology solutions, collaboration software, custom planning software solutions, and existing ground antenna scheduling solutions to create an effective and efficient CubeSat operations environment. The end-solution satisfied the operations stakeholders, which include NASA, its industry partner TMC2 Technologies, and four independent professor-student teams at West Virginia University.

Suder, Mark↗

The Development of the Ares I-X Flight Test

The National Aeronautics and Space Administration (NASA) Constellation Program (CxP) has identified a series of tests to provide insight into the design and development of the Ares I Crew Launch Vehicle (CLV) and the Orion Crew Exploration Vehicle (CEV). Ares I-X was created as the first suborbital development flight test to help meet CxP objectives. The Ares I-X flight vehicle is an early operational model of Ares, with specific emphasis on Ares I and ground operation characteristics necessary to meet Ares I-X flight test objectives. Ares I-X will encompass the design and construction of an entire system that includes the Flight Test Vehicle (FTV) and associated operations. The FTV will be a test model based on the Ares I design. Select design features will be incorporated in the FTV design to emulate the operation of the CLV in order to meet the flight test objectives. The operations infrastructure and processes will be customized for Ares I-X, while still providing data to inform the developers of the launch processing system for Ares/Orion. The FTV is comprised of multiple elements and components that will be developed at different locations. The components will be delivered to the launch/assembly site, Kennedy Space Center (KSC), for assembly of the elements and components into an integrated, flight-ready, launch vehicle. The FTV will fly a prescribed trajectory in order to obtain the necessary data to meet the objectives. Ares I-X will not be commanded or controlled from the ground during flight, but the FTV will be equipped with telemetry systems, a data recording capability and a flight termination system (FTS). The in-flight part of the test includes a trajectory to simulate maximum dynamic pressure during flight and perform a stage separation representative of the CLV. The in-flight test also includes separation of the Upper Stage Simulator (USS) from the First Stage and recovery of the First Stage. The data retrieved from the flight test will be analyzed and used in the design and development of the Ares I vehicle. This paper will discuss the challenges in developing a new launch vehicle in a very short timeframe. The duration from formal Authority to Proceed to launch is 32 months with launch scheduled for April, 2009. The discussion will include changes to organizational structure, system engineering approaches, and early lessons learned for a fast tracked and highly visible project.

Ess, Robert H.↗