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.

SourceResearch connectionFrom yearThrough year

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

At least 1,045 records · Page 58

All sources NASA NTRS DOE OSTI

NASA NTRS2013

Conducting Research on the International Space Station Using the EXPRESS Rack Facilities

Eight "Expedite the Processing of Experiments to Space Station" (EXPRESS) Rack facilities are located within the International Space Station (ISS) laboratories to provide standard resources and interfaces for the simultaneous and independent operation of multiple experiments within each rack. Each EXPRESS Rack provides eight Middeck Locker Equivalent locations and two drawer locations for powered experiment equipment, also referred to as sub-rack payloads. Payload developers may provide their own structure to occupy the equivalent volume of one, two, or four lockers as a single unit. Resources provided for each location include power (28 Vdc, 0-500 W), command and data handling (Ethernet, RS-422, 5 Vdc discrete, +/- 5 Vdc analog), video (NTSC/RS 170A), and air cooling (0-200 W). Each rack also provides water cooling (500 W) for two locations, one vacuum exhaust interface, and one gaseous nitrogen interface. Standard interfacing cables and hoses are provided on-orbit. One laptop computer is provided with each rack to control the rack and to accommodate payload application software. Four of the racks are equipped with the Active Rack Isolation System to reduce vibration between the ISS and the rack. EXPRESS Racks are operated by the Payload Operations Integration Center at Marshall Space Flight Center and the sub-rack experiments are operated remotely by the investigating organization. Payload Integration Managers serve as a focal to assist organizations developing payloads for an EXPRESS Rack. NASA provides EXPRESS Rack simulator software for payload developers to checkout payload command and data handling at the development site before integrating the payload with the EXPRESS Functional Checkout Unit for an end-to-end test before flight. EXPRESS Racks began supporting investigations onboard ISS on April 24, 2001 and will continue through the life of the ISS.

Thompson, Sean W.↗

NASA NTRS2016

Conducting Research on the International Space Station using the EXPRESS Rack Facilities

Eight "Expedite the Processing of Experiments to Space Station" (EXPRESS) Rack facilities are located within the International Space Station (ISS) laboratories to provide standard resources and interfaces for the simultaneous and independent operation of multiple experiments within each rack. Each EXPRESS Rack provides eight Middeck Locker Equivalent locations and two drawer locations for powered experiment equipment, also referred to as sub-rack payloads. Payload developers may provide their own structure to occupy the equivalent volume of one, two, or four lockers as a single unit. Resources provided for each location include power (28 Vdc, 0-500 W), command and data handling (Ethernet, RS-422, 5 Vdc discrete, +/- 5 Vdc analog), video (NTSC/RS 170A), and air cooling (0-200 W). Each rack also provides water cooling for two locations (500W ea.), one vacuum exhaust interface, and one gaseous nitrogen interface. Standard interfacing cables and hoses are provided on-orbit. One laptop computer is provided with each rack to control the rack and to accommodate payload application software. Four of the racks are equipped with the Active Rack Isolation System to reduce vibration between the ISS and the rack. EXPRESS Racks are operated by the Payload Operations Integration Center at Marshall Space Flight Center and the sub-rack experiments are operated remotely by the investigating organization. Payload Integration Managers serve as a focal to assist organizations developing payloads for an EXPRESS Rack. NASA provides EXPRESS Rack simulator software for payload developers to checkout payload command and data handling at the development site before integrating the payload with the EXPRESS Functional Checkout Unit for an end-to-end test before flight. EXPRESS Racks began supporting investigations onboard ISS on April 24, 2001 and will continue through the life of the ISS.

Thompson, Sean W.↗

DOE OSTI2024

Command of three-dimensional solitary waves via photopatterning

Multidimensional solitons are prevalent in numerous research fields. In orientationally ordered soft matter system, three-dimensional director solitons exemplify the localized distortion of molecular orientation. However, their precise manipulation remains challenging due to unpredictable and uncontrolled generation. Here, we utilize preimposed programmable photopatterning in nematics to control the kinetics of director solitons. This enables both unidirectional and bidirectional generation at specific locations and times, confinement within micron-scaled patterns of diverse shapes, and directed propagation along predefined trajectories. A focused dynamical model provides insight into the origins of these solitons and aligns closely with experimental observations, underscoring the pivotal role of anchoring conditions in soliton manipulation. Our findings pave the way for diverse fundamental research avenues and promising applications, including microcargo transportation and optical information processing.

Science & Technology - Other Topics↗

NASA NTRS1999

Signal processing related to the vestibulo-ocular reflex during combined angular rotation and linear translation of the head

The contributions of vestibular nerve afferents and central vestibular pathways to the angular (AVOR) and linear (LVOR) vestibulo-ocular reflex were studied in squirrel monkeys during fixation of near and far targets. Irregular vestibular afferents did not appear to be necessary for the LVOR, since when they were selectively silenced with galvanic currents the LVOR was essentially unaffected during both far- and near-target viewing. The linear translation signals generated by secondary AVOR neurons in the vestibular nuclei were, on average, in phase with head velocity, inversely related to viewing distance, and were nearly as strong as AVOR-related signals. We suggest that spatial-temporal transformation of linear head translation signals to angular eye velocity commands is accomplished primarily by the addition of viewing distance multiplied, centrally integrated, otolith regular afferent signals to angular VOR pathways.

NASA Discipline Neuroscience↗

NASA NTRS1991

Earth Radiation Budget Satellite (ERBS): Emergency support

The primary purpose of the Earth Radiation Budget Satellite (ERBS) project is to study the Earth's atmospheric processes and their relationship to the Earth's climate. Following deployment from the Space Shuttle, the satellite was maneuvered into a circular orbit of 610 km x 610 km x 57 degrees, with a period of 99.6 minutes. The Deep Space Network (DSN) will support the ERBS during emergency situations in the event that the standard Tracking and Data Relay Satellite System (TDRSS) to White Sands data link is inoperative. Emergency support will be provided by the DSN's 26-meter antenna subnetwork. Information is given in tabular form for DSN network support, frequency assignments, telemetry, and command.

Williamson, J.↗

NASA NTRS1991

Model reference adaptive control of flexible robots in the presence of sudden load changes

Direct command generator tracker based model reference adaptive control (MRAC) algorithms are applied to the dynamics for a flexible-joint arm in the presence of sudden load changes. Because of the need to satisfy a positive real condition, such MRAC procedures are designed so that a feedforward augmented output follows the reference model output, thus, resulting in an ultimately bounded rather than zero output error. Thus, modifications are suggested and tested that: (1) incorporate feedforward into the reference model's output as well as the plant's output, and (2) incorporate a derivative term into only the process feedforward loop. The results of these simulations give a response with zero steady state model following error, and thus encourage further use of MRAC for more complex flexibile robotic systems.

Steinvorth, Rodrigo↗

NASA NTRS2017

Spaceport Command and Control System Automated Testing

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administrations (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This large system requires high quality testing that will properly measure the capabilities of the system. Automating the test procedures would save the project time and money. Therefore, 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.

LCS↗

NASA NTRS2017

Spaceport Command and Control System Automation Testing

Testing↗

NASA NTRSDate not supplied

NASA's Moon to Mars Autonomous Habitat Status

NASA is developing a strategy for sending humans to the Mars vicinity, known broadly as the Moon to Mars (M2M) Campaign. A critical part of this campaign is the development of in-space and surface habitation systems capable of substantially extending human presence beyond Low Earth Orbit (LEO). Mars missions feature an in-space transit habitat capable of supporting crews of four on ~850-1200-day missions, including transit to and from Mars and time in Mars orbit. Surface and transit habitats are complex elements which must keep crewmembers healthy and productive in deep-space environments with limited resources, long rescue times in contingency situations, and communication delays; all within constrained mass, volume, and power budgets. These habitats provide crew both living and workspace as well as most of the resources needed to support crew life. For deep space habitats, automation needs to be employed due to latency and for significant amounts of time when the habitats are uncrewed. Automation of systems is possible in space applications, but there are limitations. Outside of the Earth’s (or any) magnetosphere, radiation environments are harsh to both the physical hardware and the software components. Radiation (charged particles and ionizing electromagnetic waves) degrades and damages the hardware and causes single event upsets (SEUs) in software. If the hardware is damaged, data can be lost, or control actions not made. For software, SEUs cause algorithms to result in different solutions, or incorrect commands to be sent out. This means that algorithms and hardware used for deep space systems are different than what is used on Earth. Radiation-tolerant hardware is generations behind the current state-of-the-art hardware. Recent NASA missions, such as James Webb Space Telescope, continue to rely on older technologies such as the RAD750 processor, and the most advanced processors are still single core and less than 1.5 GHz. There have been attempts to use higher performance processors, but these often take multiple mitigation steps to handle the radiation environments, which limits the processing power and/or throughput. Current techniques for radiation mitigation have been redundancies, voting, physical separation of hardware, encasing materials, under-clocking hardware, and more. Some radiation mitigation techniques do provide benefits such as having a redundant system to improve the probability that a system will be available when needed. Autonomous software systems will have fewer interactions with humans on deep space missions and therefore need to be able to handle more off-nominal conditions. Microgravity also complicates the autonomous aspects of the mission because autonomous systems are usually built from known deterministic states, but microgravity causes physical objects to shift and move changing the location an autonomous system placed the object. Not only does the software need to be reliable and deterministic, losing resources due to a software error is not only costly but detrimental to reputation. The combination of having lower performance hardware and having to be able to verify and deterministically run software and an ever-changing environment makes deep space autonomous systems more complicated. Multiple gaps have been identified including verification of autonomous software algorithms (including artificial intelligence and machine learning), higher performance processors (graphics and general purpose), high speed networks (onboard and transmissions), memory, power distribution, data security, and variations from these. These gaps need to be closed for more advanced systems to be deployed and reduce the size, weight, and power impacts on the habitats.

Scott B. Tashakkor↗

NASA NTRS2002

Systems Architecture for Fully Autonomous Space Missions

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

Esper, Jamie↗

NASA NTRS2007

Flight Dynamics Performances of the MetOp A Satellite during the First Months of Operations

The 19th of October 2006 at 16:28 UTC the first MetOp satellite (MetOp A) was successfully launched from the Baykonur cosmodrome by a Soyuz/Fregat launcher. After only three days of LEOP operations, performed by ESOC, the satellite was handed over to EUMETSAT, who is since then taking care of all satellite operations. MetOp A is the first European operational satellite for meteorology flying in a Low Earth Orbit (LEO), all previous satellites operated by EUMETSAT, belonging to the METEOSAT family, being located in the Geo-stationary orbit. To ensure safe operations for a LEO satellite accurate and continuous commanding from ground of the on-board AOCS is required. That makes the operational transition at the end of the LEOP quite challenging, as the continuity of the Flight Dynamics operations is to be maintained. That means that the main functions of the Flight Dynamics have to be fully validated on-flight during the LEOP, before taking over the operational responsibility on the spacecraft, and continuously monitored during the entire mission. Due to the nature of a meteorological operational mission, very stringent requirements in terms of overall service availability (99 % of the collected data), timeliness of processing of the observation data (3 hours after sensing) and accuracy of the geo-location of the meteorological products (1 km) are to be fulfilled. That translates in tight requirements imposed to the Flight Dynamics facility (FDF) in terms of accuracy, timeliness and availability of the generated orbit and clock solutions; a detailed monitoring of the quality of these products is thus mandatory. Besides, being the accuracy of the image geo-location strongly related with the pointing performance of the platform and with the on-board timing stability, monitoring from ground of the behaviour of the on-board sensors and clock is needed. This paper presents an overview of the Flight Dynamics operations performed during the different phases of the MetOp A mission up to routine. The activities performed to validate all the Flight Dynamics functions, characterize the behaviour of the satellite and monitor the performances of the Flight Dynamics facility will be highlighted. The MetOp Flight Dynamics Operations team is led by Anders Meier Soerensen and composed by Pier Luigi Righetti, Francisco Sancho, Antimo Damiano and David Lazaro. The team is supported by Hilda Meixner, responsible for all Flight Dynamics validation activities.

Righetti, Pier Luigi↗

NASA NTRS1992

Assured crew return vehicle post landing configuration design and test

The 1991-1992 senior Mechanical and Aerospace Engineering Design class continued work on the post landing configurations for the Assured Crew Return Vehicle (ACRV) and the Emergency Egress Couch (EEC). The ACRV will be permanently docked to Space Station Freedom fulfilling NASA's commitment of Assured Crew Return Capability in the event of an accident or illness aboard Space Station Freedom. The EEC provides medical support and a transportation surface for an incapacitated crew member. The objective of the projects was to give the ACRV Project Office data to feed into their feasibility studies. Four design teams were given the task of developing models with dynamically and geometrically scaled characteristics. Groups one and two combined efforts to design a one-fifth scale model for the Apollo Command Module derivative, an on-board flotation system, and a lift attachment point system. This model was designed to test the feasibility of a rigid flotation and stabilization system and to determine the dynamics associated with lifting the vehicle during retrieval. However, due to priorities, it was not built. Group three designed a one-fifth scale model of the Johnson Space Center (JSC) benchmark configuration, the Station Crew Return Alternative Module (SCRAM) with a lift attachment point system. This model helped to determine the flotation and lifting characteristics of the SCRAM configuration. Group four designed a full scale EEC with changeable geometric and geometric and dynamic characteristics. This model provided data on the geometric characteristics of the EEC and on the placement of the CG and moment of inertia. It also gave the helicopter rescue personnel direct input to the feasibility study. Section 1 describes in detail the design of a one-fifth scale model of the Apollo Command Module Derivative (ACMD) ACRV. The objective of the ACMD Configuration Model Team was to use geometric and dynamic constraints to design a one-fifth scale working model of the Apollo Command Module Derivative (ACMD) configuration with a Lift Attachment Point (LAP) System. This model was required to incorporate a rigidly mounted flotation system and the egress system designed the previous academic year. The LAP system was to be used to determine the dynamic effects of locating the lifting points at different locations on the vehicle. The team was then to build and test the model; however, due to priorities, this did not occur. To better simulate the ACMD after a water landing, the nose cone section was removed and the deck area exposed. The areas researched during the design process were construction, center of gravity and moment of inertia, and lift attachment points.

Source record↗

NASA NTRS1999

Landsat-7 Simulation and Testing Environments

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

Holmes, E.↗

NASA NTRS1993

Mission Operations and Command Assurance: Automating an Operations TQM Task

Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality into mission operations. The mission operations environment is inherently risky because each decision made is potentially mission critical. The flight operations environment generally requires operators to make rapid critical decisions and solve problems based on limited information, while closely following standard procedures. MO&CA's primary goal is to help improve the operational reliability and reduce risk of projects during flight. To achieve this goal, automation of the MO&CA task is required. MO&CA specifically embodies the TQM principle of continuous process improvement (CPI) in which processes are continually examined and analyzed for opportunities for improvement. The second way in which MO&CA implements CPI on JPL projects is on new projects or upgrades to existing projects.

mission↗

NASA NTRS1994

Evolving software reengineering technology for the emerging innovative-competitive era

This paper reports on a multi-tool commercial/military environment combining software Domain Analysis techniques with Reusable Software and Reengineering of Legacy Software. It is based on the development of a military version for the Department of Defense (DOD). The integrated tools in the military version are: Software Specification Assistant (SSA) and Software Reengineering Environment (SRE), developed by Computer Command and Control Company (CCCC) for Naval Surface Warfare Center (NSWC) and Joint Logistics Commanders (JLC), and the Advanced Research Project Agency (ARPA) STARS Software Engineering Environment (SEE) developed by Boeing for NAVAIR PMA 205. The paper describes transitioning these integrated tools to commercial use. There is a critical need for the transition for the following reasons: First, to date, 70 percent of programmers' time is applied to software maintenance. The work of these users has not been facilitated by existing tools. The addition of Software Reengineering will also facilitate software maintenance and upgrading. In fact, the integrated tools will support the entire software life cycle. Second, the integrated tools are essential to Business Process Reengineering, which seeks radical process innovations to achieve breakthrough results. Done well, process reengineering delivers extraordinary gains in process speed, productivity and profitability. Most importantly, it discovers new opportunities for products and services in collaboration with other organizations. Legacy computer software must be changed rapidly to support innovative business processes. The integrated tools will provide commercial organizations important competitive advantages. This, in turn, will increase employment by creating new business opportunities. Third, the integrated system will produce much higher quality software than use of the tools separately. The reason for this is that producing or upgrading software requires keen understanding of extremely complex applications which is facilitated by the integrated tools. The radical savings in the time and cost associated with software, due to use of CASE tools that support combined Reuse of Software and Reengineering of Legacy Code, will add an important impetus to improving the automation of enterprises. This will be reflected in continuing operations, as well as in innovating new business processes. The proposed multi-tool software development is based on state of the art technology, which will be further advanced through the use of open systems for adding new tools and experience in their use.

Hwang, Phillip Q.↗

NASA NTRS2003

STS-107 Flight Day 6 Highlights

This video shows the activities of the STS-107 crew on flight day 6 of the Columbia orbiter's final mission. The crew members include: Rick Husband, Commander; William McCool, Pilot; Kalpana Chawla, David Brown, Michael Anderson, Laurel Clark; Mission Specialists; Ilan Ramon, Payload Specialist. The primary activities of flight day 6 are spaceborne experiments, and a conversation between Israeli Prime Minister Ariel Sharon, accompanied by the Israeli Minister of Education, and Israeli astronaut Ilan Ramon. Both the Israelis and their interpreter are audible on the tape. The video also features a bioreactor used to grow cancer cells in microgravity, and footage taken by the Mediterranean Israeli Dust Experiment (MEIDEX) of sprites, lightning in the lower ionosphere. Mission Specialist Anderson is shown working on the Laminar Soot Processes (LSP-2) experiment. Pilot McCool answers two questions from the public, and a view of Panama is shown.

Source record↗

NASA NTRS2010

Analyzing Distributed Functions in an Integrated Hazard Analysis

Large scale integration of today's aerospace systems is achievable through the use of distributed systems. Validating the safety of distributed systems is significantly more difficult as compared to centralized systems because of the complexity of the interactions between simultaneously active components. Integrated hazard analysis (IHA), a process used to identify unacceptable risks and to provide a means of controlling them, can be applied to either centralized or distributed systems. IHA, though, must be tailored to fit the particular system being analyzed. Distributed systems, for instance, must be analyzed for hazards in terms of the functions that rely on them. This paper will describe systems-oriented IHA techniques (as opposed to traditional failure-event or reliability techniques) that should be employed for distributed systems in aerospace environments. Special considerations will be addressed when dealing with specific distributed systems such as active thermal control, electrical power, command and data handling, and software systems (including the interaction with fault management systems). Because of the significance of second-order effects in large scale distributed systems, the paper will also describe how to analyze secondary functions to secondary functions through the use of channelization.

Morris, A. Terry↗

NASA NTRS2007

Tracking and Data Relay Satellite (TDRS) Orbit Estimation Using an Extended Kalman Filter

Alternatives to the Tracking and Data Relay Satellite (TDRS) orbit estimation procedure were studied to develop a technique that both produces more reliable results and is more amenable to automation than the prior procedure. The Earth Observing System (EOS) Terra mission has TDRS ephemeris prediction 3(sigma) requirements of 75 meters in position and 5.5 millimeters per second in velocity over a 1.5-day prediction span. Meeting these requirements sometimes required reruns of the prior orbit determination (OD) process, with manual editing of tracking data to get an acceptable solution. After a study of the available alternatives, the Flight Dynamics Facility (FDF) began using the Real-Time Orbit Determination (RTOD(Registered TradeMark)) Kalman filter program for operational support of TDRSs in February 2007. This extended Kalman filter (EKF) is used for daily support, including within hours after most thrusting, to estimate the spacecraft position, velocity, and solar radiation coefficient of reflectivity (C(sub R)). The tracking data used are from the Bilateration Ranging Transponder System (BRTS), selected TDRS System (TDRSS) User satellite tracking data, and Telemetry, Tracking, and Command (TT&C) data. Degraded filter results right after maneuvers and some momentum unloads provided incentive for a hybrid OD technique. The results of combining EKF strengths with the Goddard Trajectory Determination System (GTDS) Differential Correction (DC) program batch-least-squares solutions, as recommended in a 2005 paper on the chain-bias technique, are also presented.

Ward, Douglas T.↗