Search NASA⌕ Search

SEARCH · Search NASA

Results for “automated command”

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 217 records · Page 12

Automated Sequence Generation Process and Software

"Automated sequence generation" (autogen) signifies both a process and software used to automatically generate sequences of commands to operate various spacecraft. The autogen software comprises the autogen script plus the Activity Plan Generator (APGEN) program. APGEN can be used for planning missions and command sequences.

Gladden, Roy↗

Trends in the automation of planetary spacecraft

The automation of planetary spacecraft at the Jet Propulsion Laboratory (JPL) is discussed. Factors affecting the development of spacecraft automation, such as predictable and repetitive functions and narrow time-window, are analyzed. The volume of command data transmitted to the spacecraft is considered, together with an examination of 'autonomy' (executing functions without outside control) in relation to the ground command activity needed during the mission. The role of the spacecraft's growing computational power in increasing vehicle autonomy is noted.

Bird, T. H.↗

Computational fluid dynamics analysis of space shuttle main propulsion feed line 17-inch disconnect valves

A steady incompressible three-dimensional (3-D) viscous flow analysis was conducted for the Space Shuttle Main Propulsion External Tank (ET)/Orbiter (ORB) propellant feed line quick separable 17-inch disconnect flapper valves for liquid oxygen (LO2) and liquid hydrogen (LH2). The main objectives of the analysis were to predict and correlate the hydrodynamic stability of the flappers and pressure drop with available water test data. Computational Fluid Dynamics (CFD) computer codes were procured at no cost from the public domain, and were modified and extended to carry out the disconnect flow analysis. The grid generator codes SVTGD3D and INGRID were obtained. NASA Ames Research Center supplied the flow solution code INS3D, and the color graphics code PLOT3D. A driver routine was developed to automate the grid generation process. Components such as pipes, elbows, and flappers can be generated with simple commands, and flapper angles can be varied easily. The flow solver INS3D code was modified to treat interior flappers, and other interfacing routines were developed, which include a turbulence model, a force/moment routine, a time-step routine, and initial and boundary conditions. In particular, an under-relaxation scheme was implemented to enhance the solution stability. Major physical assumptions and simplifications made in the analysis include the neglect of linkages, slightly reduced flapper diameter, and smooth solid surfaces. A grid size of 54 x 21 x 25 was employed for both the LO2 and LH2 units. Mixing length theory applied to turbulent shear flow in pipes formed the basis for the simple turbulence model. Results of the analysis are presented for LO2 and LH2 disconnects.

Kandula, Max↗

Autobalancing and FDIR for a space-based centrifuge prototype

This report summarizes centrifuge-related work performed at the Smart Systems Research Laboratory at NASA Ames Research Center's Computational Sciences Division from 1995 through 2003. The goal is to develop an automated system that will sense an imbalance (both static and dynamic3) in a centrifuge and issue control commands to drive counterweights to eliminate the effects of the imbalance. This autobalancing development began when the ISS centrifuge design was not yet finalized, and was designed to work with the SSRL Centrifuge laboratory prototype, constructed in 1993-1995. Significant differences between that prototype and the current International Space Station (ISS) Centrifuge design are that: the spin axis for the SSRL Centrifuge prototype can translate freely in x and y, but not wobble, whereas the ISS centrifuge spin axis has 3 translational and two rotational degrees of freedom, supported by a vibration 34. The imbalance sensors are strained gauges both in the rotor and the stator, measuring the imbalance forces, whereas the ISS centrifuge uses eddy current displacement sensors to measure the displacements resulting from imbalance. High fidelity autobalancing and FDIR systems (for both counterweights and strain gauges) are developed and tested in MATLAB simulation, for the SSRL Centrifuge configuration. Hardware implementation of the autobalancing technology was begun in 1996, but was terminated due to lack of funding. The project lay dormant until 2001-2002 when the FDIR capability was added.

Wilson, Edward↗

Plan Execution Interchange Language (PLEXIL)

Plan execution is a cornerstone of spacecraft operations, irrespective of whether the plans to be executed are generated on board the spacecraft or on the ground. Plan execution frameworks vary greatly, due to both different capabilities of the execution systems, and relations to associated decision-making frameworks. The latter dependency has made the reuse of execution and planning frameworks more difficult, and has all but precluded information sharing between different execution and decision-making systems. As a step in the direction of addressing some of these issues, a general plan execution language, called the Plan Execution Interchange Language (PLEXIL), is being developed. PLEXIL is capable of expressing concepts used by many high-level automated planners and hence provides an interface to multiple planners. PLEXIL includes a domain description that specifies command types, expansions, constraints, etc., as well as feedback to the higher-level decision-making capabilities. This document describes the grammar and semantics of PLEXIL. It includes a graphical depiction of this grammar and illustrative rover scenarios. It also outlines ongoing work on implementing a universal execution system, based on PLEXIL, using state-of-the-art rover functional interfaces and planners as test cases.

Estlin, Tara↗

Extraction and Analysis of Display Data

The Display Audit Suite is an integrated package of software tools that partly automates the detection of Portable Computer System (PCS) Display errors. [PCS is a lap top computer used onboard the International Space Station (ISS).] The need for automation stems from the large quantity of PCS displays (6,000+, with 1,000,000+ lines of command and telemetry data). The Display Audit Suite includes data-extraction tools, automatic error detection tools, and database tools for generating analysis spread sheets. These spread sheets allow engineers to more easily identify many different kinds of possible errors. The Suite supports over 40 independent analyses, 16 NASA Tech Briefs, November 2008 and complements formal testing by being comprehensive (all displays can be checked) and by revealing errors that are difficult to detect via test. In addition, the Suite can be run early in the development cycle to find and correct errors in advance of testing.

Land, Chris↗

Software for Better Documentation of Other Software

The Literate Programming Extraction Engine is a Practical Extraction and Reporting Language- (PERL-)based computer program that facilitates and simplifies the implementation of a concept of self-documented literate programming in a fashion tailored to the typical needs of scientists. The advantage for the programmer is that documentation and source code are written side-by-side in the same file, reducing the likelihood that the documentation will be inconsistent with the code and improving the verification that the code performs its intended functions. The advantage for the user is the knowledge that the documentation matches the software because they come from the same file. This program unifies the documentation process for a variety of programming languages, including C, C++, and several versions of FORTRAN. This program can process the documentation in any markup language, and incorporates the LaTeX typesetting software. The program includes sample Makefile scripts for automating both the code-compilation (when appropriate) and documentation-generation processes into a single command-line statement. Also included are macro instructions for the Emacs display-editor software, making it easy for a programmer to toggle between editing in a code or a documentation mode.

Pinedo, John↗

Airborne Trajectory Management (ABTM): A Blueprint for Greater Autonomy in Air Traffic Management

The aviation users of the National Airspace System (NAS) - the airlines, General Aviation (GA), the military and, most recently, operators of Unmanned Aircraft Systems (UAS) - are constrained in their operations by the design of the current paradigm for air traffic control (ATC). Some of these constraints include ATC preferred routes, departure fix restrictions and airspace ground delay programs. As a result, most flights cannot operate on their most efficient business trajectories and a great many flights are delayed even getting into the air, which imposes a significant challenge to maintaining efficient flight and network operations. Rather than accepting ever more sophisticated scheduling solutions to accommodate the existing constraints in the airspace, a series of increasingly capable airborne technologies, integrated with planned improvements in the ground system through the Federal Aviation Administration (FAA) Next Generation Air Traffic Management System (NextGen) programs, could produce much greater operational flexibility for flight path optimization by the aviation system users. These capabilities, described in research coming out of NASA's Aeronautics Research Mission Directorate, can maintain or improve operational safety while taking advantage of air and ground NextGen technologies in novel ways. The underlying premise is that the nation's physical airspace is still abundant and underused, and that the delays and inefficient flight operations resulting from artificial structure in airspace use and procedural constraints on those operations may not be necessary for safe and efficient flight. This article is not an indictment of today's NAS or the people who run it. Indeed, it is an exceptional achievement that Air Traffic Management (ATM) - the complex human/machine conglomeration of communications, navigation and surveillance equipment and the rules and procedures for controlling traffic in the airspace - has both the capacity and enables the degree of efficiency in air travel that it does. But it is also true that sixty years of the "radar religion" (i.e., reliance on radar-based command and control) has produced several generations of ATM system operators and researchers who believe that introducing automation within the existing functional structure of ATM is the only way to "modernize" the system. Even NextGen, which began as a proposal for "transformational" change in the way ATC is performed, has morphed over the last decade and a half to become just the inclusion of Global Positioning System (GPS) for navigation, Automatic Dependent Surveillance Broadcast (ADS-B) for surveillance, and Data Communications (Data Comm) for communications, while still operating in rigidly structured airspace with human controllers being responsible for separation and traffic flow management (TFM) within defined sectors of airspace, using the same horizontal separation standards that have been in use since raw primary radar was introduced in the 1950s. No system as massive as the current NAS ATM can be replaced with a better system while simultaneously meeting the transportation and other aviation needs of the nation. A new generation of more flexible operations must emerge and yet coexist in harmony with the current operation (i.e., share the same airspace without segregation), thereby enabling a long-term transformation to take place in the way increasing numbers of flights are handled. Market forces will be the ultimate driver of this transformation, and investment realities mandate that real benefits must accrue to the first operators to adopt these new capabilities. In fact, the kinds of missions envisioned in the emerging world of UAS operations, unachievable under conventional ATM, demand that this transformation take place. Airborne Trajectory Management (ABTM) is proposed as a series of transformational steps leading to vastly increased flexibility in flight operations and capacity in the airspace to accommodate many varied airspace uses while improving safety. As will be described, ABTM enables the gradual emergence of a new paradigm for user-based trajectory management in ATM that brings tangible benefits to equipped operators at every step while leveraging the air and ground investments of NextGen. There are five steps in this ABTM transformation.1 NASA has extensively studied the first and last of these steps, and a roadmap of increasing capabilities and benefits is proposed for bridging between these operational concepts.

Cotton, William B.↗

Assessing Customer Experience and Business Models around Price-to-Device Communication and Smart Control Pathways in CalFlexHub

California is facing three major challenges in electrical grid operation: renewable overgeneration, steep evening ramping, and growing peak demand. The state has identified dynamic retail price response as a key strategy evidenced by CPUC’s Dynamic Rates proceeding and CEC’s Load Management Standards. Furthermore, the CEC launched a $16M “California Load Flexibility Research and Deployment Hub (CalFlexHub)” administered by Berkeley Lab to accelerate price-response flexible load technologies in buildings and EV charging. There are more than 16 laboratory and field demonstration projects in CalFlexHub, each demonstrating innovative automated price-response technologies. CalFlexHub tests various pathways through which hourly price signals and triggered control commands are communicated to load-flexible devices such as smart thermostats, heat pumps, water heaters, and EVs. We identified seven unique communication and control pathways, which involve combinations of third-party cloud, device OEM’s cloud, building central gateway, and local controller in between the price server and the load-flexible devices. It is important for utilities and policy makers to understand the long-term implications of each pathway in designing future programs and creating related policies and mandates for market transformation. We propose an evaluation framework including the following aspects: ● Functionality: connectivity and uptime, resilience, and optimization; ● Customer experience: simplicity in setup, troubleshooting support, continuity, customer choice, first cost, and ongoing cost; ● Business model and scalability: advance interoperability, holistic solution, bridge unique gap, customer base, and value streams and pricing structures. In this paper, we identify emerging business models associated with each communication pathway and discuss their positive features and challenges from the above aspects.

Liu, Jingjing↗

Mission planning for space based satellite surveillance experiments with the MSX

The Midcourse Space Experiment is a BMDO-sponsored scientific satellite set for launch within the year. The satellite will collect phenomenology data on missile targets, plumes, earth limb backgrounds and deep space backgrounds in the LWIR, visible and ultra-violet spectral bands. It will also conduct functional demonstrations for space-based space surveillance. The Space-Based Visible sensor, built by Lincoln Laboratory, Massachusetts Institute of Technology, is the primary sensor on board the MSX for demonstration of space surveillance. The SBV Processing, Operations and Control Center (SPOCC) is the mission planning and commanding center for all space surveillance experiments using the SBV and other MSX instruments. The guiding principle in the SPOCC Mission Planning System was that all routine functions be automated. Manual analyst input should be minimal. Major concepts are: (I) A high level language, called SLED, for user interface to the system; (2) A group of independent software processes which would generally be run in a pipe-line mode for experiment commanding but can be run independently for analyst assessment; (3) An integrated experiment cost computation function that permits assessment of the feasibility of the experiment. This paper will report on the design, implementation and testing of the Mission Planning System.

Sridharan, R.↗

ACDC (Automated Campbell Diagram Code) [SWR-26-042]

This application provides a web-based graphical user interface to generating Campbell Diagrams and visualizing mode shapes for OpenFAST turbine models. Determining the aeroelastic stability and dynamic characteristics of wind turbines is a critical step in turbine design and analysis. Historically, extracting natural frequencies and mode shapes from OpenFAST—the industry-standard whole-turbine simulation code—has been a fragmented and tedious process. It required manual model configuration, command-line linearization execution, and complex post-processing via proprietary scripts to handle rotating-frame dynamics. To address these workflow bottlenecks, we present the Automated Campbell Diagram Code (ACDC), an open-source graphical software tool developed by the National Laboratory of the Rockies (NLR) under the DOE-funded Distributed Wind Aeroelastic Modeling (dWAM) project. ACDC streamlines the end-to-end linearization and stability analysis workflow into a single, intuitive cross-platform application. The software guides users through OpenFAST model configuration, definition of operating points, and the automated execution of steady-state trim and linearization simulations. Under the hood, ACDC automates the complex mathematical post-processing steps required for rotating systems, including Multi-Blade Coordinate (MBC) transformations, eigenanalysis, and advanced modal tracking utilizing the Modal Assurance Criterion (MAC) and spectral clustering. Finally, ACDC processes these results to automatically generate Campbell diagrams and features a robust 3D visualization engine to animate full-system mode shapes. By eliminating the reliance on external post-processing environments and manual data manipulation, ACDC significantly accelerates dynamic analysis and lowers the barrier to entry for wind energy researchers and engineers.

Summerville, Brent [National Laboratory of the Roc↗

Gesture-Controlled Interfaces for Self-Service Machines

Gesture-controlled interfaces are software- driven systems that facilitate device control by translating visual hand and body signals into commands. Such interfaces could be especially attractive for controlling self-service machines (SSMs) for example, public information kiosks, ticket dispensers, gasoline pumps, and automated teller machines (see figure). A gesture-controlled interface would include a vision subsystem comprising one or more charge-coupled-device video cameras (at least two would be needed to acquire three-dimensional images of gestures). The output of the vision system would be processed by a pure software gesture-recognition subsystem. Then a translator subsystem would convert a sequence of recognized gestures into commands for the SSM to be controlled; these could include, for example, a command to display requested information, change control settings, or actuate a ticket- or cash-dispensing mechanism. Depending on the design and operational requirements of the SSM to be controlled, the gesture-controlled interface could be designed to respond to specific static gestures, dynamic gestures, or both. Static and dynamic gestures can include stationary or moving hand signals, arm poses or motions, and/or whole-body postures or motions. Static gestures would be recognized on the basis of their shapes; dynamic gestures would be recognized on the basis of both their shapes and their motions. Because dynamic gestures include temporal as well as spatial content, this gesture- controlled interface can extract more information from dynamic than it can from static gestures.

Cohen, Charles J.↗

Flight Test Evaluation of Autonomous Descending-Decelerating Precision Point-in-Space Approach to the Ground

New forms of highly automated Advanced Air Mobility (AAM) aircraft, such as electric vertical take-off and landing (eVTOL) vehicles, could transform transportation, cargo delivery, and a variety of public services. The National Aeronautics and Space Administration (NASA) conducted a series of flight demonstrations in collaboration with the Defense Advanced Research Projects Agency (DARPA) and Sikorsky Aircraft (a Lockheed Martin company) to progressively evaluate autonomous technologies. The autoland flight test research is a first in series for investigating the world’s first procedural descending-decelerating automated landing with vertical guidance Instrument Flight Procedures (IFP). The Sikorsky Optionally Piloted Vehicle (OPV) experimental UH-60 Black Hawk was used to evaluate a flight path’s four-dimensional trajectory (4DT) management into primitive commands and then follow those commands to a Point-in-Space (PinS) landing to the ground. All flight procedures were manually flown to the ground at 12 degrees with a 20-knot tail wind to ensure flight safety before automation was engaged. New and novel high precision approach procedures could pave the way for all future VTOL operations.

David Zahn↗

Automated testing of low-orbiting satellites

This paper describes the hardware, software, and test procedures implemented at a ground station for the automated testing of a polar-orbiting satellite in a low orbit. The satellite passes during the testing were characterized by short visibility times of no more than 18 min and by high rates of change of the link parameters as seen by the ground station. The advantages of automated testing became apparent for these dynamic conditions. Under computer control throughout the pass, programmable test instruments were commanded and data was collected and stored. Data reduction was performed after the pass.

Barbiere, D.↗

Preliminary Results Obtained in Integrated Safety Analysis of NASA Aviation Safety Program Technologies

This is a listing of recent unclassified RTO technical publications for January 1, 2005 through March 31, 2005 processed by the NASA Center for AeroSpace Center available on the NASA Aeronautics and Space Database. Contents include 1) Electronic Information Management; 2) Decision Support to Combined Joint Task Force and Component Commanders; 3) RTO Technical Publications : A Quarterly Listing (December 2004); 4) The Role of Humans in Intelligent and Automated Systems.

Source record↗

Mission Operations Planning and Scheduling System (MOPSS)

MOPSS is a generic framework that can be configured on the fly to support a wide range of planning and scheduling applications. It is currently used to support seven missions at Goddard Space Flight Center (GSFC) in roles that include science planning, mission planning, and real-time control. Prior to MOPSS, each spacecraft project built its own planning and scheduling capability to plan satellite activities and communications and to create the commands to be uplinked to the spacecraft. This approach required creating a data repository for storing planning and scheduling information, building user interfaces to display data, generating needed scheduling algorithms, and implementing customized external interfaces. Complex scheduling problems that involved reacting to multiple variable situations were analyzed manually. Operators then used the results to add commands to the schedule. Each architecture was unique to specific satellite requirements. MOPSS is an expert system that automates mission operations and frees the flight operations team to concentrate on critical activities. It is easily reconfigured by the flight operations team as the mission evolves. The heart of the system is a custom object-oriented data layer mapped onto an Oracle relational database. The combination of these two technologies allows a user or system engineer to capture any type of scheduling or planning data in the system's generic data storage via a GUI.

Wood, Terri↗

Target Trailing With Safe Navigation for Maritime Autonomous Surface Vehicles

This software implements a motion-planning module for a maritime autonomous surface vehicle (ASV). The module trails a given target while also avoiding static and dynamic surface hazards. When surface hazards are other moving boats, the motion planner must apply International Regulations for Avoiding Collisions at Sea (COLREGS). A key subset of these rules has been implemented in the software. In case contact with the target is lost, the software can receive and follow a "reacquisition route," provided by a complementary system, until the target is reacquired. The programmatic intention is that the trailed target is a submarine, although any mobile naval platform could serve as the target. The algorithmic approach to combining motion with a (possibly moving) goal location, while avoiding local hazards, may be applicable to robotic rovers, automated landing systems, and autonomous airships. The software operates in JPL s CARACaS (Control Architecture for Robotic Agent Command and Sensing) software architecture and relies on other modules for environmental perception data and information on the predicted detectability of the target, as well as the low-level interface to the boat controls.

Wolf, Michael↗

Toward an Autonomous Feature-based Pointing System for Planetary Missions

Although the analytical groundwork for understanding two-dimensional object images and various aspects of computer vision has been laid, we have not yet applied these concepts to automating the process of obtaining science images during space exploration missions. Our current approach in specifying pointing-command sequences relies heavily on target predicts, based on predicted target and spacecraft ephemerides, that propagate the target position as a function of time during pointing operations.

Computer↗