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 253 records · Page 14

Training the Powered-Lift Evaluation Pilot

This poster describes a project to prepare pilots for a study assessing novel aircraft automation concepts for electric Vertical Takeoff and Landing (eVTOL) aircraft using NASA’s Vertical Motion Simulator (VMS). By exploring the operational and learning challenges related to transitioning between forward flight and vertical landing, we seek to establish baselines of pilot workload and aircraft handling qualities across varying atmospheric conditions and automation states. The simulated eVTOL design differentiates flight control allocations as a function of airspeed across four speed ranges as the vehicle transitions between fully thrust-borne lift and wing-borne lift. As speed increases, side stick controls command: translational ground speeds, vertical and lateral acceleration, vertical rate, vertical flight path angle, and bank angle. This novel approach to flight control allocation creates a significant learning challenge for pilots. Since initial eVTOL aircraft may have limitations on hover capabilities, automation and flight guidance cues also vary with airspeed to provide efficient landing profiles while still providing cues suitable for cruise flight. The NASA team prepared the study pilots to follow these flight guidance cues along curved Required Navigation Performance (RNP) approaches and along 6o and 12o glide paths to energy-efficient assistive-hover landing and goarounds. The pre-VMS preparation sought to prepare pilots from diverse levels of experience and background. To do this, NASA researchers designed and developed a fixed-based, large field-ofview simulator with terrain, structures, and air traffic. With one day of combined classroom learning and skill development in the fixedbase simulator, pilots were largely able to fly the simulated eVTOL in the VMS with sufficient mastery to provide handling quality assessments using the Cooper-Harper Handling Qualities Rating and workload assessments through the Bedford Workload Scale.

AAM↗

Volume serving and media management in a networked, distributed client/server environment

The E-Systems Modular Automated Storage System (EMASS) is a family of hierarchical mass storage systems providing complete storage/'file space' management. The EMASS volume server provides the flexibility to work with different clients (file servers), different platforms, and different archives with a 'mix and match' capability. The EMASS design considers all file management programs as clients of the volume server system. System storage capacities are tailored to customer needs ranging from small data centers to large central libraries serving multiple users simultaneously. All EMASS hardware is commercial off the shelf (COTS), selected to provide the performance and reliability needed in current and future mass storage solutions. All interfaces use standard commercial protocols and networks suitable to service multiple hosts. EMASS is designed to efficiently store and retrieve in excess of 10,000 terabytes of data. Current clients include CRAY's YMP Model E based Data Migration Facility (DMF), IBM's RS/6000 based Unitree, and CONVEX based EMASS File Server software. The VolSer software provides the capability to accept client or graphical user interface (GUI) commands from the operator's console and translate them to the commands needed to control any configured archive. The VolSer system offers advanced features to enhance media handling and particularly media mounting such as: automated media migration, preferred media placement, drive load leveling, registered MediaClass groupings, and drive pooling.

Herring, Ralph H.↗

Models of Human Information Requirements: "When Reasonable Aiding Systems Disagree"

Aircraft flight management and Air Traffic Control (ATC) automation are under development to maximize the economy of flight and to increase the capacity of the terminal area airspace while maintaining levels of flight safety equal to or better than current system performance. These goals are being realized by the introduction of flight management automation aiding and operations support systems on the flight deck and by new developments of ATC aiding systems that seek to optimize scheduling of aircraft while potentially reducing required separation and accounting for weather and wake vortex turbulence. Aiding systems on both the flight deck and the ground operate through algorithmic functions on models of the aircraft and of the airspace. These models may differ from each other as a result of variations in their models of the immediate environment. The resultant flight operations or ATC commands may differ in their response requirements (e.g. different preferred descent speeds or descent initiation points). The human operators in the system must then interact with the automation to reconcile differences and resolve conflicts. We have developed a model of human performance including cognitive functions (decision-making, rule-based reasoning, procedural interruption recovery and forgetting) that supports analysis of the information requirements for resolution of flight aiding and ATC conflicts. The model represents multiple individuals in the flight crew and in ATC. The model is supported in simulation on a Silicon Graphics' workstation using Allegro Lisp. Design guidelines for aviation automation aiding systems have been developed using the model's specification of information and team procedural requirements. Empirical data on flight deck operations from full-mission flight simulation are provided to support the model's predictions. The paper describes the model, its development and implementation, the simulation test of the model predictions, and the empirical validation process. The model and its supporting data provide a generalizable tool that is being expanded to include air/ground compatibility and ATC crew interactions in air traffic management.

Corker, Kevin↗

A prototype to automate the video subsystem routing for the video distribution subsystem of Space Station Freedom

The Video Distribution Subsystem (VDS) for Space Station Freedom provides onboard video communications. The VDS includes three major functions: external video switching; internal video switching; and sync and control generation. The Video Subsystem Routing (VSR) is a part of the VDS Manager Computer Software Configuration Item (VSM/CSCI). The VSM/CSCI is the software which controls and monitors the VDS equipment. VSR activates, terminates, and modifies video services in response to Tier-1 commands to connect video sources to video destinations. VSR selects connection paths based on availability of resources and updates the video routing lookup tables. This project involves investigating the current methodology to automate the Video Subsystem Routing and developing and testing a prototype as 'proof of concept' for designers.

Betz, Jessie M. Bethly↗

Launch processing system transition from development to operation

The Launch Processing System has been under development at Kennedy Space Center since 1973. A prototype system was developed and delivered to Marshall Space Flight Center for Solid Rocket Booster checkout in July 1976. The first production hardware arrived in late 1976. The System uses a distributed computer network for command and monitoring and is supported by a dual large scale computer system for 'off line' processing. A high level of automation is anticipated for Shuttle and Payload testing and launch operations to gain the advantages of short turnaround capability, repeatability of operations, and minimization of operations and maintenance (O&M) manpower. Learning how to efficiently apply the system is our current problem. We are searching for more effective ways to convey LPS system performance characteristics from the designer to a large number of users. Once we have done this, we can realize the advantages of LPS system design.

Paul, H. C.↗

Overview of the Telescience Testbed Program

The NASA's Telescience Testbed Program (TTP) conducted by the Ames Research Center is described with particular attention to the objectives, the approach used to achieve these objectives, and the expected benefits of the program. The goal of the TTP is to gain operational experience for the Space Station Freedom and the Earth Observing System programs, using ground testbeds, and to define the information and communication systems requirements for the development and operation of these programs. The results of TTP are expected to include the requirements for the remote coaching, command and control, monitoring and maintenance, payload design, and operations management. In addition, requirements for technologies such as workstations, software, video, automation, data management, and networking will be defined.

Rasmussen, Daryl N.↗

Interactive Spectral Analysis and Computation (ISAAC)

Isaac is a task in the NSO external package for IRAF. A descendant of a FORTRAN program written to analyze data from a Fourier transform spectrometer, the current implementation has been generalized sufficiently to make it useful for general spectral analysis and other one dimensional data analysis tasks. The user interface for Isaac is implemented as an interpreted mini-language containing a powerful, programmable vector calculator. Built-in commands provide much of the functionality needed to produce accurate line lists from input spectra. These built-in functions include automated spectral line finding, least squares fitting of Voigt profiles to spectral lines including equality constraints, various filters including an optimal filter construction tool, continuum fitting, and various I/O functions.

Lytle, D. M.↗

Emergency Response Fire-Imaging UAS Missions over the Southern California Wildfire Disaster

Objectives include: Demonstrate capabilities of UAS to overfly and collect sensor data on widespread fires throughout Western US. Demonstrate long-endurance mission capabilities (20-hours+). Image multiple fires (greater than 4 fires per mission), to showcase extendable mission configuration and ability to either linger over key fires or station over disparate regional fires. Demonstrate new UAV-compatible, autonomous sensor for improved thermal characterization of fires. Provide automated, on-board, terrain and geo-rectified sensor imagery over OTH satcom links to national fire personnel and Incident commanders. Deliver real-time imagery (within 10-minutes of acquisition). Demonstrate capabilities of OTS technologies (GoogleEarth) to serve and display mission-critical sensor data, coincident with other pertinent data elements to facilitate information processing (WX data, ground asset data, other satellite data, R/T video, flight track info, etc).

Cobleigh, Brent R.↗

NASA 2007 Western States Fire Missions (WSFM)

This viewgraph presentation describes the Western states Fire Missions (WSFM) that occurred in 2007. The objectives of this mission are: (1) Demonstrate capabilities of UAS to overfly and collect sensor data on widespread fires throughout Western US. (1) Demonstrate long-endurance mission capabilities (20-hours+). (2) Image multiple fires (greater than 4 fires per mission), to showcase extendable mission configuration and ability to either linger over key fires or station over disparate regional fires. (3) Demonstrate new UAV-compatible, autonomous sensor for improved thermal characterization of fires. (4) Provide automated, on-board, terrain and geo-rectified sensor imagery over OTH satcom links to national fire personnel and Incident commanders. (5) Deliver real-time imagery to (within 10-minutes of acquisition). (6) Demonstrate capabilities of OTS technologies (GoogleEarth) to serve and display mission-critical sensor data, coincident with other pertinent data elements to facilitate information processing (WX data, ground asset data, other satellite data, R/T video, flight track info, etc).

Buoni, Greg↗

Emergency Response Fire-Imaging UAS Missions over the Southern California Wildfire Disaster

Objectives include: Demonstrate capabilities of UAS to overfly and collect sensor data on widespread fires throughout Western US. Demonstrate long-endurance mission capabilities (20-hours+). Image multiple fires (greater than 4 fires per mission), to showcase extendable mission configuration and ability to either linger over key fires or station over disparate regional fires. Demonstrate new UAV-compatible, autonomous sensor for improved thermal characterization of fires. Provide automated, on-board, terrain and geo-rectified sensor imagery over OTH satcom links to national fire personnel and Incident commanders. Deliver real-time imagery (within 10-minutes of acquisition). Demonstrate capabilities of OTS technologies (GoogleEarth) to serve and display mission-critical sensor data, coincident with other pertinent data elements to facilitate information processing (WX data, ground asset data, other satellite data, R/T video, flight track info, etc).

DelFrate, John H.↗

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project

Over the past 5 years, the UAS integration into the NAS project has worked to reduce technical barriers to integration. A major focus of this work has been in support of RTCA SC-228. This committee has recently published the first UAS integration minimum performance standards (MOPS). This work has spanned detect and avoid (DAA) as well as command and control comm datalinks. I will discuss DAA efforts with focus on the human systems work. I will discuss how automation was discussed and addressed within this context. ICAO stood up a remotely piloted aircraft systems (RPAS) panel in 2014. They have developed an RPAS manual and are now working to revise existing annexes and standards and recommended practices. The Human In The System (HITS) has worked to infuse human factors guidelines into those documents. I will discuss that effort as well as how ICAO has defined and address autonomy. There is a great deal of interest in the control of multiple vehicles by a single operator. The UAS EXCOM Science and Research Panel (SARP) is holding a workshop on this topic in late June. I will discuss research performed on this topic when I worked for the Army and on-going work within the division and a NATO working group on Human-Autonomy Teaming.

Unmanned Aircraft Systems (UAS)↗

Ground Autonomy for an Aging Spacecraft

As it approaches the sixteenth of a 5 year prime mission, NASA's Solar Radiation and Climate Experiment (SORCE) mission continues to meet and exceed all science requirements while operating with severely degraded batteries. By 2013, the batteries had degraded such that the On Board Computer (OBC) could not be powered through eclipse. This prevents science data collection in eclipse and erases over 99% of all stored science and engineering telemetry. To mitigate these problems, the Flight Operations Team (FOT) at the Laboratory for Atmospheric and Space Physics (LASP) adopted a new operations scheme. "Daylight Only Operations" (DO-OP) transitions the spacecraft from safemode to science mode every orbit. This involved heavily automating the transition process using ground autonomy to improve spacecraft recovery time to 6 minutes - down from 3 orbits of manual commanding. While highly successful, this method of operations poses daily challenges that must be overcome using increasingly complex ground software.

Autonomous Operations↗

Simplifying operations with an uplink/downlink integration toolkit

The Operations Engineering Lab (OEL) at JPL has developed a simple, generic toolkit to integrate the uplink/downlink processes, (often called closing the loop), in JPL's Multimission Ground Data System. This toolkit provides capabilities for integrating telemetry verification points with predicted spacecraft commands and ground events in the Mission Sequence Of Events (SOE) document. In the JPL ground data system, the uplink processing functions and the downlink processing functions are separate subsystems that are not well integrated because of the nature of planetary missions with large one-way light times for spacecraft-to-ground communication. Our new closed-loop monitoring tool allows an analyst or mission controller to view and save uplink commands and ground events with their corresponding downlinked telemetry values regardless of the delay in downlink telemetry and without requiring real-time intervention by the user. An SOE document is a time-ordered list of all the planned ground and spacecraft events, including all commands, sequence loads, ground events, significant mission activities, spacecraft status, and resource allocations. The SOE document is generated by expansion and integration of spacecraft sequence files, ground station allocations, navigation files, and other ground event files. This SOE generation process has been automated within the OEL and includes a graphical, object-oriented SOE editor and real-time viewing tool running under X/Motif. The SOE toolkit was used as the framework for the integrated implementation. The SOE is used by flight engineers to coordinate their operations tasks, serving as a predict data set in ground operations and mission control. The closed-loop SOE toolkit allows simple, automated integration of predicted uplink events with correlated telemetry points in a single SOE document for on-screen viewing and archiving. It automatically interfaces with existing real-time or non real-time sources of information, to display actual values from the telemetry data stream. This toolkit was designed to greatly simplify the user's ability to access and view telemetry data, and also provide a means to view this data in the context of the commands and ground events that are used to interpret it. A closed-loop system can prove especially useful in small missions with limited resources requiring automated monitoring tools. This paper will discuss the toolkit implementation, including design trade-offs and future plans for enhancing the automated capabilities.

Murphy, Susan C.↗

America in Space: The First Decade - NASA Spacecraft

It is ten years since the National Aeronautics and Space Administration was created to explore space and to continue the American efforts that had already begun with the launch of Explorer 1 on January 31, 1958. Many changes have occurred since that tumbling, 31 -pound cylinder went into an Earth orbit. "NASA Spacecraft" represents one of the broad avenues selected by NASA as an approach to its objective of making widely known the progress that has taken place in its program of space exploration. This report is a vivid illustration of the changes that have occurred and the complexities that have developed. Here one finds descriptions of the present family of spacecraft some small, some large; some spinoriented, some accurately attitude-controlled; some manned, some automated; some in low orbits, some in trajectories to the Moon and the planets; some free in space until they expire, others commanded to return to the Earth or to land on the Moon

Source record↗

Ikhana UAS Overview

Ikhana demonstrates capabilities of UAS to overfly and collect sensor data on widespread fires throughout Western US and also demonstrate long-endurance mission capabilities (20-hours+). Ikhana images multiple fires (greater than 4 fires per mission), to showcase extendable mission configuration and ability to either linger over key fires or station over disparate regional fires. Ikhana also demonstrates new UAV-compatible, autonomous sensor for improved thermal characterization of fires. Also it provides automated, on-board, terrain and geo-rectified sensor imagery over the horizon SATCOM links to national fire personnel and Incident commanders.

UAS in the NAS↗

ICEG2D (v2.0) - An Integrated Software Package for Automated Prediction of Flow Fields for Single-Element Airfoils With Ice Accretion

An integrated geometry/grid/simulation software package, ICEG2D, is being developed to automate computational fluid dynamics (CFD) simulations for single- and multi-element airfoils with ice accretions. The current version, ICEG213 (v2.0), was designed to automatically perform four primary functions: (1) generate a grid-ready surface definition based on the geometrical characteristics of the iced airfoil surface, (2) generate high-quality structured and generalized grids starting from a defined surface definition, (3) generate the input and restart files needed to run the structured grid CFD solver NPARC or the generalized grid CFD solver HYBFL2D, and (4) using the flow solutions, generate solution-adaptive grids. ICEG2D (v2.0) can be operated in either a batch mode using a script file or in an interactive mode by entering directives from a command line within a Unix shell. This report summarizes activities completed in the first two years of a three-year research and development program to address automation issues related to CFD simulations for airfoils with ice accretions. As well as describing the technology employed in the software, this document serves as a users manual providing installation and operating instructions. An evaluation of the software is also presented.

Thompson David S.↗

A software architecture for automating operations processes

The Operations Engineering Lab (OEL) at JPL has developed a software architecture based on an integrated toolkit approach for simplifying and automating mission operations tasks. The toolkit approach is based on building adaptable, reusable graphical tools that are integrated through a combination of libraries, scripts, and system-level user interface shells. The graphical interface shells are designed to integrate and visually guide a user through the complex steps in an operations process. They provide a user with an integrated system-level picture of an overall process, defining the required inputs and possible output through interactive on-screen graphics. The OEL has developed the software for building these process-oriented graphical user interface (GUI) shells. The OEL Shell development system (OEL Shell) is an extension of JPL's Widget Creation Library (WCL). The OEL Shell system can be used to easily build user interfaces for running complex processes, applications with extensive command-line interfaces, and tool-integration tasks. The interface shells display a logical process flow using arrows and box graphics. They also allow a user to select which output products are desired and which input sources are needed, eliminating the need to know which program and its associated command-line parameters must be executed in each case. The shells have also proved valuable for use as operations training tools because of the OEL Shell hypertext help environment. The OEL toolkit approach is guided by several principles, including the use of ASCII text file interfaces with a multimission format, Perl scripts for mission-specific adaptation code, and programs that include a simple command-line interface for batch mode processing. Projects can adapt the interface shells by simple changes to the resources configuration file. This approach has allowed the development of sophisticated, automated software systems that are easy, cheap, and fast to build. This paper will discuss our toolkit approach and the OEL Shell interface builder in the context of a real operations process example. The paper will discuss the design and implementation of a Ulysses toolkit for generating the mission sequence of events. The Sequence of Events Generation (SEG) system provides an adaptable multimission toolkit for producing a time-ordered listing and timeline display of spacecraft commands, state changes, and required ground activities.

Miller, Kevin J.↗

Autonomous Formation Flying from Ground to Flight

The cost of on-orbit operations remains a significant and increasingly visible concern in the support of satellite missions. Headway has been made in automating some ground operations; however, increased mission complexity and more precise orbital constraints have compelled continuing human involvement in mission design and maneuver planning operations. AI Solutions, Inc. in cooperation with the National Aeronautics and Space Administration's (NASA) Goddard Space Flight Center (GSFC) has tackled these more complex problems through the development of AutoCon as a tool for an automated solution. NASA is using AutoCon to automate the maneuver planning for the Earth Orbiter-1 (EO-1) mission. AutoCon was developed originally as a ground system tool. The EO-1 mission will be using a scaled version of AutoCon on-board the EO-1 satellite to command orbit adjustment maneuvers. The flight version of AutoCon plans maneuvers based on formation flying algorithms developed by GSFC, JPL, and other industry partners. In its fully autonomous mode, an AutoCon planned maneuver will be executed on-board the satellite without intervention from the ground. This paper describes how AutoCon automates maneuver planning for the formation flying constraints of the EO-1 mission. AutoCon was modified in a number of ways to automate the maneuver planning on-board the satellite. This paper describes how the interface and functionality of AutoCon were modified to support the on-board system. A significant component of this modification was the implementation of a data smoother, based on a Kalman filter, that ensures that the spacecraft states estimated by an on-board GPS receiver are as accurate as possible for maneuver planning. This paper also presents the methodology use to scale the AutoCon functionality to fit and execute on the flight hardware. This paper also presents the modes built that allow the incremental phasing in of autonomy. New technologies for autonomous operations are usually received with significant, and probably appropriate trepidation. A number of safeguards have been designed in both AutoCon and the interfacing systems to alleviate the potential of mission-impacting anomalies from the on-board autonomous system. This paper describes the error checking, input data integrity validation and limits set on maneuvers in AutoCon and the on-board system.

Chapman, Keith B.↗