Search NASA⌕ Search

SEARCH · Search NASA

Results for “Ground Control Station Operator”

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

Tracking and data relay satellite system configuration and tradeoff study. Volume 3: TDRSS configuration and data summary, part 1

A reference handbook of configuration data and design information is presented. It treats the overall system definition, operations and control, and telecommunication service system including link budgets. A brief description of the user transceiver and ground station is presented. A final section includes a summary description of the TDR spacecraft and all the subsystems. The data presented are largely in tabular form for easy reference.

Source record↗

Notional Airspace Operations Demonstration Plan

The airspace operations demonstration (AOD) is intended to show that the Access 5 Step 1 functional requirements can be met. The demonstration will occur in two phases. The initial on-range phase will be carried out in restricted airspace to demonstrate the cooperative collision avoidance (CCA) functional requirements and to provide risk-reduction for the AOD by allowing the test team to rehearse some elements of the demonstration mission. The CCA system to be used in these flights is based on Automatic Dependent Surveillance-Broadcast (ADS-B) which is a commercially-available system by which airplanes constantly broadcast their current position and altitude to other aircraft and ground resources over a dedicated radio datalink. The final phase will occur in the national airspace (NAS) and will be the formal demonstration of the remainder of the proposed functional requirements. The general objectives of the AOD are as follows: (1) Demonstrate that the UAS can aviate in the NAS (2) Demonstrate that the UAS can navigate in the NAS (3) Demonstrate that the UAS can communicate with the NAS (4) Demonstrate that the UAS can perform selected collision avoidance functions in the NAS (5) Demonstrate that the UAS can evaluate and avoid weather conflicts in the NAS (6) Demonstrate that the UAS can provide adequate command and control in the NAS In addition to the stated objectives, there are a number of goals for the flight demonstration. The demo can be accomplished successfully without achieving these goals, but these goals are to be used as a guideline for preparing for the mission. The goals are: (1) Mission duration of at least 24 hours (2) Loiter over heavy traffic to evaluate the data block issue identified during the Access 5 Airspace Operations Simulations (3) Document the contingency management process and lessons learned (4) Document the coordination process for Ground Control Stations (GCS) handoff (5) Document lessons learned regarding the process of flying in the NAS Preliminary planning for a notional mission to achieve the objectives and goals has been prepared. The planning is intended to serve as a guide for detailed planning of the AOD.

Trongale, Nicholas A.↗

Implementation issues for a compact 6 degree of freedom force reflecting handcontroller with cueing of modes

Teleoperated control requires a master human interface device that can provide haptic input and output which reflect the responses of a slave robotic system. The effort reported in this paper addresses the design and prototyping of a six degree-of-freedom (DOF) Cartesian coordinate hand controller for this purpose. The device design recommended is an XYZ stage attached to a three-roll wrist which positions a flight-type handgrip. Six degrees of freedom are transduced and control brushless DC motor servo electronics similar in design to those used in computer controlled robotic manipulators. This general approach supports scaled force, velocity, and position feedback to aid an operator in achieving telepresence. The generality of the device and control system characteristics allow the use of inverse dynamics robotic control methodology to project slave robot system forces and inertias to the operator (in scaled form) and at the same time to reduce the apparent inertia of the robotic handcontroller itself. The current control design, which is not multiple fault tolerant, can be extended to make flight control or space use possible. The proposed handcontroller will have advantages in space-based applications where an operator must control several robot arms in a simultaneous and coordinated fashion. It will also have applications in intravehicular activities (within the Space Station) such as microgravity experiments in metallurgy and biological experiments that require isolation from the astronauts' environment. For ground applications, the handcontroller will be useful in underwater activities where the generality of the proposed handcontroller becomes an asset for operation of many different manipulator types. Also applications will emerge in the Military, Construction, and Maintenance/Manufacturing areas including ordnance handling, mine removal, NBC (Nuclear, Chemical, Biological) operations, control of vehicles, and operating strength and agility enhanced machines. Future avionics applications including advanced helicopter and aircraft control may also become important.

Jacobus, Heidi↗

Space Operations Training Concepts Benchmark Study (Training in a Continuous Operations Environment)

The NASA/USAF Benchmark Space Operations Training Concepts Study will perform a comparative analysis of the space operations training programs utilized by the United States Air Force Space Command with those utilized by the National Aeronautics and Space Administration. The concentration of the study will be focused on Ground Controller/Flight Controller Training for the International Space Station Payload Program. The duration of the study is expected to be five months with report completion by 30 June 2002. The U.S. Air Force Space Command was chosen as the most likely candidate for this benchmark study because their experience in payload operations controller training and user interfaces compares favorably with the Payload Operations Integration Center's training and user interfaces. These similarities can be seen in the dynamics of missions/payloads, controller on-console requirements, and currency/proficiency challenges to name a few. It is expected that the report will look at the respective programs and investigate goals of each training program, unique training challenges posed by space operations ground controller environments, processes of setting up controller training programs, phases of controller training, methods of controller training, techniques to evaluate adequacy of controller knowledge and the training received, and approaches to training administration. The report will provide recommendations to the respective agencies based on the findings. Attached is a preliminary outline of the study. Following selection of participants and an approval to proceed, initial contact will be made with U.S. Air Force Space Command Directorate of Training to discuss steps to accomplish the study.

Johnston, Alan E.↗

Jet Propulsion Laboratory/Kennedy Space Center telerobotic inspection and manipulation demonstration

The goal of this effort is to demonstrate telerobotic inspection and mainpulation of space shuttle payloads in the presence of substantial communications time delays between the operator station and the robotic work space. The processing of space shuttle payloads provides a variety of tasks which are typical of both space shuttle ground operations and Space Station in-flight operations, and communications time delays are inevitable in space operations where the operator station will be light-seconds away from the telerobot. With this demonstration we hope to show the efficacy and safety of robotic technology for ground and space operations. Our approach is to develop an experimental telerobotic system with the remote sensing, actuation and reflex portions located at KSC in Florida, while the operator control station will be located at Jet Propulsion Laboratory (JPL) in California. The JPL portion of the system includes a high-level operator interface, intelligent spatial planning and machine vision, while the KSC portion includes the robot arm, end effectors, cameras and proximity sensors, and the necessary control and communications computers and software. The communications between JPL and KSC are over a limited-bandwidth network channel (19200 baud) with unpredictable and unrepeatable time delays. In FY89 we integrated a basic version of the robotic, communications, and computer hardware, and we developed the software to perform an operator-supervised inspection of a PAM-D satellite upper stage rocket motor and its shuttle support cradle. The demonstration, though severely limited by the bulk of the available computer arm, showed the potential of telerobotics for inspection tasks. In the future, we plan to develop additional capabilities which will allow manipulation tasks to be performed, including removal of dust covers and lens caps, insertion of connectors and batteries, and installation of payload objects.

Wilcox, Brian↗

Robotic Technology Development at Ames: The Intelligent Robotics Group and Surface Telerobotics

Future human missions to the Moon, Mars, and other destinations offer many new opportunities for exploration. But, astronaut time will always be limited and some work will not be feasible for humans to do manually. Robots, however, can complement human explorers, performing work autonomously or under remote supervision from Earth. Since 2004, the Intelligent Robotics Group has been working to make human-robot interaction efficient and effective for space exploration. A central focus of our research has been to develop and field test robots that benefit human exploration. Our approach is inspired by lessons learned from the Mars Exploration Rovers, as well as human spaceflight programs, including Apollo, the Space Shuttle, and the International Space Station. We conduct applied research in computer vision, geospatial data systems, human-robot interaction, planetary mapping and robot software. In planning for future exploration missions, architecture and study teams have made numerous assumptions about how crew can be telepresent on a planetary surface by remotely operating surface robots from space (i.e. from a flight vehicle or deep space habitat). These assumptions include estimates of technology maturity, existing technology gaps, and likely operational and functional risks. These assumptions, however, are not grounded by actual experimental data. Moreover, no crew-controlled surface telerobotic system has yet been fully tested, or rigorously validated, through flight testing. During Summer 2013, we conducted a series of tests to examine how astronauts in the International Space Station (ISS) can remotely operate a planetary rover across short time delays. The tests simulated portions of a proposed human-robotic Lunar Waypoint mission, in which astronauts in lunar orbit remotely operate a planetary rover on the lunar Farside to deploy a radio telescope array. We used these tests to obtain baseline-engineering data.

robotics↗

Use of Semi-Autonomous Tools for ISS Commanding and Monitoring

As the International Space Station (ISS) has moved into a utilization phase, operations have shifted to become more ground-based with fewer mission control personnel monitoring and commanding multiple ISS systems. This shift to fewer people monitoring more systems has prompted use of semi-autonomous console tools in the ISS Mission Control Center (MCC) to help flight controllers command and monitor the ISS. These console tools perform routine operational procedures while keeping the human operator "in the loop" to monitor and intervene when off-nominal events arise. Two such tools, the Pre-positioned Load (PPL) Loader and Automatic Operators Recorder Manager (AutoORM), are used by the ISS Communications RF Onboard Networks Utilization Specialist (CRONUS) flight control position. CRONUS is responsible for simultaneously commanding and monitoring the ISS Command & Data Handling (C&DH) and Communications and Tracking (C&T) systems. PPL Loader is used to uplink small pieces of frequently changed software data tables, called PPLs, to ISS computers to support different ISS operations. In order to uplink a PPL, a data load command must be built that contains multiple user-input fields. Next, a multiple step commanding and verification procedure must be performed to enable an onboard computer for software uplink, uplink the PPL, verify the PPL has incorporated correctly, and disable the computer for software uplink. PPL Loader provides different levels of automation in both building and uplinking these commands. In its manual mode, PPL Loader automatically builds the PPL data load commands but allows the flight controller to verify and save the commands for future uplink. In its auto mode, PPL Loader automatically builds the PPL data load commands for flight controller verification, but automatically performs the PPL uplink procedure by sending commands and performing verification checks while notifying CRONUS of procedure step completion. If an off-nominal condition occurs during procedure execution, PPL Loader notifies CRONUS through popup messages, allowing CRONUS to examine the situation and choose an option of how PPL loader should proceed with the procedure. The use of PPL Loader to perform frequent, routine PPL uplinks offloads CRONUS to better monitor two ISS systems. It also reduces procedure performance time and decreases risk of command errors. AutoORM identifies ISS communication outage periods and builds commands to lock, playback, and unlock ISS Operations Recorder files. Operation Recorder files are circular buffer files of continually recorded ISS telemetry data. Sections of these files can be locked from further writing, be played back to capture telemetry data that occurred during an ISS loss of signal (LOS) period, and then be unlocked for future recording use. Downlinked Operation Recorder files are used by mission support teams for data analysis, especially if failures occur during LOS. The commands to lock, playback, and unlock Operations Recorder files are encompassed in three different operational procedures and contain multiple user-input fields. AutoORM provides different levels of automation for building and uplinking the commands to lock, playback, and unlock Operations Recorder files. In its automatic mode, AutoORM automatically detects ISS LOS periods, then generates and uplinks the commands to lock, playback, and unlock Operations Recorder files when MCC regains signal with ISS. AutoORM also features semi-autonomous and manual modes which integrate CRONUS more into the command verification and uplink process. AutoORMs ability to automatically detect ISS LOS periods and build the necessary commands to preserve, playback, and release recorded telemetry data greatly offloads CRONUS to perform more high-level cognitive tasks, such as mission planning and anomaly troubleshooting. Additionally, since Operations Recorder commands contain numerical time input fields which are tedious for a human to manually build, AutoORM's ability to automatically build commands reduces operational command errors. PPL Loader and AutoORM demonstrate principles of semi-autonomous operational tools that will benefit future space mission operations. Both tools employ different levels of automation to perform simple and routine procedures, thereby offloading human operators to perform higher-level cognitive tasks. Because both tools provide procedure execution status and highlight off-nominal indications, the flight controller is able to intervene during procedure execution if needed. Semi-autonomous tools and systems that can perform routine procedures, yet keep human operators informed of execution, will be essential in future long-duration missions where the onboard crew will be solely responsible for spacecraft monitoring and control.

Brzezinski, Amy S.↗

NASA ground communications

As part of the Communications Requirements and Constraints, NASA's two major Ground Data Networks were briefly described. The NASA Communication Network, called NASCOM, is the worldwide operational telecommunications system which interconnects as the tracking and telemetry acquisition sites, launch areas, mission and project control centers, data capture facilities, and network control centers in support of space flight. For the Space Station era, NASCOM plans are set for higher data rate service utilizing data packet switched technology. Increased use of fiber optics is expected in a much more diverse network topology. The second major ground network, the Program Support Communications Network (PSCN), interconnects all NASA Centers and NASA contractor locations for intercenter non-operation communications. The primary functions are to transport voice, video, data and facsimile information for intercenter coordination, and to provide user access to space science and applications data bases. For the Space Station era, PSCN plans address the significant increase in forecast requirements for science data distribution and access to the Numerical Aerodynamics Simulator, and increased use of the Video Teleconference System.

Roeder, John↗

Tracking and Data Relay Satellite System configuration and tradeoff study. Volume 2: Delta 2914 launched TDRSS, Configuration 2. Part 2: Final Report, 22 August 1972 - 1 April 1973

Configuration data and design information for a Delta 2914 launched configuration with greatly enhanced telecommunication service over the Part I Delta 2914 configuration is contained. The overall system definition, operations and control, and telecommunication service system, including link budgets are discussed. A brief description of the user transceiver and ground station is presented. A final section includes a summary description of the TDR spacecraft and all the subsystems. The data presented are largely in tabular form.

Source record↗

Tracking and Data Relay Satellite System configuration and tradeoff study. Volume 4: Space shuttle launched TDRSS. Part 2: Final Report, 22 August 1972 - 1 April 1973

Configuration data and design information for the space shuttle launched configuration is presented. The overall system definition, operations and control, and telecommunication service system including link budgets are discussed. A brief description of the user transceiver and ground station is presented. A final section includes a summary description of the TDR spacecraft and all the subsystems. The data presented are largely in tabular form.

Source record↗

The 727 approach energy management system avionics specification (preliminary)

Hardware and software requirements for an Approach Energy Management System (AEMS) consisting of an airborne digital computer and cockpit displays are presented. The displays provide the pilot with a visual indication of when to manually operate the gear, flaps, and throttles during a delayed flap approach so as to reduce approach time, fuel consumption, and community noise. The AEMS is an independent system that does not interact with other navigation or control systems, and is compatible with manually flown or autopilot coupled approaches. Operational use of the AEMS requires a DME ground station colocated with the flight path reference.

Jackson, D. O.↗

Telecommunications and data acquisition systems support for the Viking 1975 mission to Mars, volume 5

The support provided by the Deep Space Network to the Viking Project from 1 June 1978 to 30 April 1980 is described. The project was supported by the worldwide network of Deep Space Stations with 26- and 64-meter-diameter antennas, together with a ground communications system, for the transmission of commands, telemetry, radio metric data, and operational instructions between the stations and the network operation control center in Pasadena, California. Assistance was substantially less than in the previous phases of the Viking Project in order to provide adequate support to the Pioneer and Voyager Projects.

Larkin, W. E.↗

Ground data system for Space Flyer Unit (SFU)

The Space Flyer Unit (SFU) is an unmanned, multi-purpose, retrievable and reusable space platform. The first mission of SFU (SFU-1) will be launched by NASDA's H-2 launch vehicle in early 1995 and retrieved by NASA's Space Shuttle after several months in orbit. Two Japanese ground stations, several ground stations belonging to NASA, and a ground station in Chile will be used for tracking of SFU-1. The control center of SFU-1 is the Sagamihara Operations Center (SOC) of ISAS located in Sagamihara, Japan. This paper describes the tracking and data acquisition network for SFU-1, the configuration and design policy of the SFU operations control system, and data processing schemes used for mission operations of SFU.

Yamada, Takahiro↗

Autonomous Power Control

Intelligent autonomous control of a spacecraft is an enabling technology that must be developed for deep space human exploration. NASA's current long term human space platform, the International Space Station which is in Low Earth Orbit, is in almost continuous communication with ground based mission control. This allows near realtime operation of all the vehicle core systems, including power, from the ground. As the focus shifts from Low Earth Orbit to deep space, challenges associated with communication time-lag and bandwidth limitations beyond geosynchronous orbit do not permit this type of ground based operation. These communication limitations motivate autonomous vehicle operations, including the vehicle subsystems such as power. This presentation will describe the ongoing development of an Autonomous Power Control (APC) system that can be used for a deep space exploration spacecraft. This work extends previous work on developing an autonomous power control which includes developing a control architecture for deep space vehicles, the use of software agents, and constructing a control simulation lab for demonstrating this capability. This presentation will begin with a discussion of the representative future power architectures that will be required for deep space exploration vehicles. The presentation then will describe how the power controller will integrate with the vehicle followed with a discussion of the autonomous power controller. Next it will describe the test setup used to evaluate the performance of the system and lastly show some of the test results. To develop the type of controller envisioned, it will be necessary to employ a detailed real-time simulation to evaluate its performance and ultimately verify its functionality.

Csank, Jeffrey↗

Spheres: from Ground Development to ISS Operations

SPHERES (Synchronized Position Hold Engage and Reorient Experimental Satellites) is an internal International Space Station (ISS) Facility that supports multiple investigations for the development of multi-spacecraft and robotic control algorithms. The SPHERES National Lab Facility aboard ISS is managed and operated by NASA Ames Research Center (ARC) at Moffett Field California. The SPHERES Facility on ISS consists of three self-contained eight-inch diameter free-floating satellites which perform the various flight algorithms and serve as a platform to support the integration of experimental hardware. SPHERES has served to mature the adaptability of control algorithms of future formation flight missions in microgravity (6 DOF (Degrees of Freedom) / long duration microgravity), demonstrate key close-proximity formation flight and rendezvous and docking maneuvers, understand fault diagnosis and recovery, improve the field of human telerobotic operation and control, and lessons learned on ISS have significant impact on ground robotics, mapping, localization, and sensing in three-dimensions - among several other areas of study.

SPHERES↗

Space flight operations

Under contract to the National Aeronautics and Space Administration, the Jet Propulsion Laboratory (JPL) of the California Institute of Technology manages and operates the ground facilities required to support unmanned spacecraft in missions to the moon, the planets, and beyond. A worldwide network of tracking stations, known as the Deep Space Network (DSN), was established to communicate with spacecraft. The Mission Control and Computing Center at JPL houses the mission control personnel and the computer facilities that command and control spacecraft in flight. Communications between the MCCC and the tracking stations, as well as communications among the stations, are the responsibility of the DSN Ground Communications Facility, which connects all parts of the ground system with telephone, teletype, and high-speed data lines. The operation of the ground system is outlined, and the various missions which were successfully supported are described.

Source record↗

Small Unmanned Aircraft Systems Integration into the National Airspace System Visual-Line-of-Sight Human-in-the-Loop Experiment

As part of the Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) project, research on integrating small UAS (sUAS) into the NAS was underway by a human-systems integration (HSI) team at the NASA Langley Research Center. Minimal to no research has been conducted on the safe, effective, and efficient manner in which to integrate these aircraft into the NAS. sUAS are defined as aircraft weighing 55 pounds or less. The objective of this human system integration team was to build a UAS Ground Control Station (GCS) and to develop a research test-bed and database that provides data, proof of concept, and human factors guidelines for GCS operations in the NAS. The objectives of this experiment were to evaluate the effectiveness and safety of flying sUAS in Class D and Class G airspace utilizing manual control inputs and voice radio communications between the pilot, mission control, and air traffic control. The design of the experiment included three sets of GCS display configurations, in addition to a hand-held control unit. The three different display configurations were VLOS, VLOS + Primary Flight Display (PFD), and VLOS + PFD + Moving Map (Map). Test subject pilots had better situation awareness of their vehicle position, altitude, airspeed, location over the ground, and mission track using the Map display configuration. This configuration allowed the pilots to complete the mission objectives with less workload, at the expense of having better situation awareness of other aircraft. The subjects were better able to see other aircraft when using the VLOS display configuration. However, their mission performance, as well as their ability to aviate and navigate, was reduced compared to runs that included the PFD and Map displays.

Trujillo, Anna C.↗

Automatic Weather Station (AWS) Lidar

An autonomous, low-power atmospheric lidar instrument is being developed at NASA Goddard Space Flight Center. This compact, portable lidar will operate continuously in a temperature controlled enclosure, charge its own batteries through a combination of a small rugged wind generator and solar panels, and transmit its data from remote locations to ground stations via satellite. A network of these instruments will be established by co-locating them at remote Automatic Weather Station (AWS) sites in Antarctica under the auspices of the National Science Foundation (NSF). The NSF Office of Polar Programs provides support to place the weather stations in remote areas of Antarctica in support of meteorological research and operations. The AWS meteorological data will directly benefit the analysis of the lidar data while a network of ground based atmospheric lidar will provide knowledge regarding the temporal evolution and spatial extent of Type la polar stratospheric clouds (PSC). These clouds play a crucial role in the annual austral springtime destruction of stratospheric ozone over Antarctica, i.e. the ozone hole. In addition, the lidar will monitor and record the general atmospheric conditions (transmission and backscatter) of the overlying atmosphere which will benefit the Geoscience Laser Altimeter System (GLAS). Prototype lidar instruments have been deployed to the Amundsen-Scott South Pole Station (1995-96, 2000) and to an Automated Geophysical Observatory site (AGO 1) in January 1999. We report on data acquired with these instruments, instrument performance, and anticipated performance of the AWS Lidar.

Rall, Jonathan A.R.↗