Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “COMMAND CONTROL”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 955 records · Page 53

System for Contributing and Discovering Derived Mission and Science Data

A system was developed to provide a new mechanism for members of the mission community to create and contribute new science data to the rest of the community. Mission tools have allowed members of the mission community to share first order data (data that is created by the mission s process in command and control of the spacecraft or the data that is captured by the craft itself, like images, science results, etc.). However, second and higher order data (data that is created after the fact by scientists and other members of the mission) was previously not widely disseminated, nor did it make its way into the mission planning process.

Wallick, Michael N.↗

HERRO Mission to Mars Using Telerobotic Surface Exploration from Orbit

This paper presents a concept for a human mission to Mars orbit that features direct robotic exploration of the planet s surface via teleoperation from orbit. This mission is a good example of Human Exploration using Real-time Robotic Operations (HERRO), an exploration strategy that refrains from sending humans to the surfaces of planets with large gravity wells. HERRO avoids the need for complex and expensive man-rated lander/ascent vehicles and surface systems. Additionally, the humans are close enough to the surface to effectively eliminate the two-way communication latency that constrains typical robotic space missions, thus allowing real-time command and control of surface operations and experiments by the crew. Through use of state-of-the-art telecommunications and robotics, HERRO provides the cognitive and decision-making advantages of having humans at the site of study for only a fraction of the cost of conventional human surface missions. It is very similar to how oceanographers and oil companies use telerobotic submersibles to work in inaccessible areas of the ocean, and represents a more expedient, near-term step prior to landing humans on Mars and other large planetary bodies. Results suggest that a single HERRO mission with six crew members could achieve the same exploratory and scientific return as three conventional crewed missions to the Mars surface.

Oleson, Steven R.↗

Robotics On-Board Trainer (ROBoT)

ROBoT is an on-orbit version of the ground-based Dynamics Skills Trainer (DST) that astronauts use for training on a frequent basis. This software consists of two primary software groups. The first series of components is responsible for displaying the graphical scenes. The remaining components are responsible for simulating the Mobile Servicing System (MSS), the Japanese Experiment Module Remote Manipulator System (JEMRMS), and the H-II Transfer Vehicle (HTV) Free Flyer Robotics Operations. The MSS simulation software includes: Robotic Workstation (RWS) simulation, a simulation of the Space Station Remote Manipulator System (SSRMS), a simulation of the ISS Command and Control System (CCS), and a portion of the Portable Computer System (PCS) software necessary for MSS operations. These components all run under the CentOS4.5 Linux operating system. The JEMRMS simulation software includes real-time, HIL, dynamics, manipulator multi-body dynamics, and a moving object contact model with Tricks discrete time scheduling. The JEMRMS DST will be used as a functional proficiency and skills trainer for flight crews. The HTV Free Flyer Robotics Operations simulation software adds a functional simulation of HTV vehicle controllers, sensors, and data to the MSS simulation software. These components are intended to support HTV ISS visiting vehicle analysis and training. The scene generation software will use DOUG (Dynamic On-orbit Ubiquitous Graphics) to render the graphical scenes. DOUG runs on a laptop running the CentOS4.5 Linux operating system. DOUG is an Open GL-based 3D computer graphics rendering package. It uses pre-built three-dimensional models of on-orbit ISS and space shuttle systems elements, and provides realtime views of various station and shuttle configurations.

Johnson, Genevieve↗

NASA GRC UAS Project: Communications Modeling and Simulation Status

The integration of Unmanned Aircraft Systems (UAS) in the National Airspace represents new operational concepts required in civil aviation. These new concepts are evolving as the nation moves toward the Next Generation Air Transportation System (NextGen) under the leadership of the Joint Planning and Development Office (JPDO), and through ongoing work by the Federal Aviation Administration (FAA). The desire and ability to fly UAS in the National Air Space (NAS) in the near term has increased dramatically, and this multi-agency effort to develop and implement a national plan to successfully address the challenges of UAS access to the NAS in a safe and timely manner is well underway. As part of the effort to integrate UAS in the National Airspace, NASA Glenn Research Center is currently involved with providing research into Communications systems and Communication system operations in order to assist with developing requirements for this implementation. In order to provide data and information regarding communication systems performance that will be necessary, NASA GRC is tasked with developing and executing plans for simulations of candidate future UAS command and control communications, in line with architectures and communications technologies being developed and/or proposed by NASA and relevant aviation organizations (in particular, RTCA SC-203). The simulations and related analyses will provide insight into the ability of proposed communications technologies and system architectures to enable safe operation of UAS, meeting UAS in the NAS project goals (including performance requirements, scalability, and interoperability), and ultimately leading to a determination of the ability of NextGen communication systems to accommodate UAS. This presentation, compiled by the NASA GRC team, will provide a view of the overall planned simulation effort and objectives, a description of the simulation concept and status of the design and development that has occurred to date.

Kubat, Greg↗

NASA Activity Update for the 2013 Unmanned Vehicle Systems International (UVSI) Yearbook

This year s report offers a high level perspective on some of the UAS related activities in which NASA is involved, both internal and external to the agency. Internally, NASA issued UAS operational policy on certification of NASA UAS and aircrew. A team of NASA UAS experts and operators analyzed all current procedures and best practices to design the policy. An update to the agencies Aircraft Operations Management Manual incorporated a new chapter to address UAS planning, preflight operations, flight operations, flight crew requirements, airworthiness and flight safety reviews. NASA UAS are classified into three categories based on weight and airspeed. Aircrews, including observers, are classified by how they interface with the UAS, and the policy defines qualifications, training, and currency. The NASA flight readiness approval process identifies risks and mitigations in order to reduce the likelihood and/or consequence of the risk to an acceptable level. The UAS operations process incorporates all aspects of airworthiness, flight standards and range safety exactly the same processes used for NASA manned aircraft operations. NASA has two internal organizations that routinely operate UAS. The Science Mission Directorate utilizes UAS as part of its Airborne Science Program and is the most frequent operator of NASA UAS in both national and international airspace. The Aeronautics Research Mission Directorate conducts UAS flight operations in addition to conducting research important to the UAS community. This past year the Science Mission Directorate supported the Hurricane and Severe Storm Sentimental (HS3) Mission with two NASA Global Hawk platforms. HS3 is a five-year mission specifically targeted to investigate the processes that underlie hurricane formation. During the 2012 portion of this mission the Global Hawk overflew hurricanes Leslie and Nadine in the Atlantic Ocean completing 6 flights and accumulating more than 148 flight hours. Another multi-year mission was initiated last year when the Sensor Integrated Environmental Remote Research Aircraft (SIERRA) UAS began surveying faults in California s Surprise Valley. A team of scientists and engineers from the United States Geological Survey (USGS), NASA Ames Research Center, Central Washington University, and Carnegie Mellon University will measure magnetic fields using ground surveys and the SIERRA to map the geophysics below the surface of Surprise Valley. The data collected will be used to generate 3D maps of the geophysical data of the area. The Aeronautics Mission Directorate continues its collaboration with Boeing to conduct UAS flight operations of the X-48C, a modified version of the X-48B originally built by Cranfield Aerospace, United Kingdom. The Aeronautics Mission Directorate utilizes vehicles of this size for a wide variety of research studies. Most of these operations are conducted within restricted airspace. The Aeronautics Research Mission Directorate also sponsors the UAS in the National Airspace System (NAS) Project, which is working in close cooperation with the Federal Aviation Administration (FAA) to address critical challenges associated with routine UAS operations in civil airspace. The project is focused on separation assurance and collision avoidance systems and algorithms, command and control for non-military operations including spectrum allocation requirements, human system interaction issues, and safety and certification topics.

Bauer, Jeffrey E.↗

Integrated Ground Operations Demonstration for Responsive Space Access

Integrated Ground Operations Demonstration Units (IGODU) project developed to mature, integrate and demonstrate advancements in cryogenics, system health management and command and control technologies. Two Distinct Testing Environments: a) GODU Integrated Refrigeration and Storage - GODU LH2; b) GODU Autonomous Control - GODU LO2. Scope: I. GODU LH2: a) Investigate alternative storage and distribution architecture for future cryogenic propellant operations. b) Demonstrate advanced cryogenic propellant handling operations (liquefaction, storage and distribution) of normal boiling point and sub-cooled cryogenic propellants. II. GODU L02: a) Develop and demonstrate advanced control and health management technologies and techniques to autonomously control cryogenic propellant servicing operations. b) Investigate modern COTS hardware and control systems in an effort to reduce the "standing army" of engineers associated with maintaining and operating ground systems through the use of health management and autonomous control technologies. Goals: a) Raise Technology Readiness Levels (TRL) and Integration Readiness Levels (IRL) of several key technology development areas. b) Reduce operations lifecycle costs of future test programs and launch complexes. c) Demonstrate technologies for future exploration beyond low earth orbit. d) Serve as test environments for extraterrestrial surface operations.

Johnson, Robert G.↗

Developing a Model Component

The Spaceport Command and Control System (SCCS) Simulation Computer Software Configuration Item (CSCI) is responsible for providing simulations to support test and verification of SCCS hardware and software. The Universal Coolant Transporter System (UCTS) was a Space Shuttle Orbiter support piece of the Ground Servicing Equipment (GSE). The initial purpose of the UCTS was to provide two support services to the Space Shuttle Orbiter immediately after landing at the Shuttle Landing Facility. The UCTS is designed with the capability of servicing future space vehicles; including all Space Station Requirements necessary for the MPLM Modules. The Simulation uses GSE Models to stand in for the actual systems to support testing of SCCS systems during their development. As an intern at Kennedy Space Center (KSC), my assignment was to develop a model component for the UCTS. I was given a fluid component (dryer) to model in Simulink. I completed training for UNIX and Simulink. The dryer is a Catch All replaceable core type filter-dryer. The filter-dryer provides maximum protection for the thermostatic expansion valve and solenoid valve from dirt that may be in the system. The filter-dryer also protects the valves from freezing up. I researched fluid dynamics to understand the function of my component. The filter-dryer was modeled by determining affects it has on the pressure and velocity of the system. I used Bernoulli's Equation to calculate the pressure and velocity differential through the dryer. I created my filter-dryer model in Simulink and wrote the test script to test the component. I completed component testing and captured test data. The finalized model was sent for peer review for any improvements. I participated in Simulation meetings and was involved in the subsystem design process and team collaborations. I gained valuable work experience and insight into a career path as an engineer.

Fields, Christina M.↗

Developing a Model Component

The Spaceport Command and Control System (SCCS) Simulation Computer Software Configuration Item (CSCI) is,. responsible for providing simulations to support test and verification of SCCS hardware and software. The Universal Coolant Transporter System (UCTS) is a Space Shuttle Orbiter support piece of the Ground Servicing Equipment (GSE). The purpose of the UCTS is to provide two support services to the Space Shuttle Orbiter immediately after landing at the Shuttle Landing Facility. The Simulation uses GSE Models to stand in for the actual systems to support testing of SCCS systems s:luring their development. As an intern at KSC, my assignment was to develop a model component for the UCTS. I was given a fluid component (drier) to model in Matlab. The drier was a Catch All replaceable core type filter-drier. The filter-drier provides maximum protection for the thermostatic expansion valve and solenoid valve from dirt that may be in the system. The filter-drier also protects the valves from freezing up. I researched fluid dynamics to understand the function of my component. I completed training for UNIX and Simulink to help aid in my assignment. The filter-drier was modeled by determining affects it has on the pressure, velocity and temperature of the system. I used Bernoulli's Equation to calculate the pressure and velocity differential through the dryer. I created my model filter-drier in Simulink and wrote the test script to test the component. I completed component testing and captured test data. The finalized model was sent for peer review for any improvements.

Fields, Christina M.↗

Creating and Testing Simulation Software

The goal of this project is to learn about the software development process, specifically the process to test and fix components of the software. The paper will cover the techniques of testing code, and the benefits of using one style of testing over another. It will also discuss the overall software design and development lifecycle, and how code testing plays an integral role in it. Coding is notorious for always needing to be debugged due to coding errors or faulty program design. Writing tests either before or during program creation that cover all aspects of the code provide a relatively easy way to locate and fix errors, which will in turn decrease the necessity to fix a program after it is released for common use. The backdrop for this paper is the Spaceport Command and Control System (SCCS) Simulation Computer Software Configuration Item (CSCI), a project whose goal is to simulate a launch using simulated models of the ground systems and the connections between them and the control room. The simulations will be used for training and to ensure that all possible outcomes and complications are prepared for before the actual launch day. The code being tested is the Programmable Logic Controller Interface (PLCIF) code, the component responsible for transferring the information from the models to the model Programmable Logic Controllers (PLCs), basic computers that are used for very simple tasks.

Heinich, Christina M.↗

NASA World Wind: Infrastructure for Spatial Data

The world has great need for analysis of Earth observation data, be it climate change, carbon monitoring, disaster response, national defense or simply local resource management. To best provide for spatial and time-dependent information analysis, the world benefits from an open standards and open source infrastructure for spatial data. In the spirit of NASA's motto "for the benefit of all" NASA invites the world community to collaboratively advance this core technology. The World Wind infrastructure for spatial data both unites and challenges the world for innovative solutions analyzing spatial data while also allowing absolute command and control over any respective information exchange medium.

Hogan, Patrick↗

Design and Development of Functionally Operative and Visually Appealing Remote Firing Room Displays

This internship provided an opportunity for an intern to work with NASA's Ground Support Equipment (GSE) for the Spaceport Command and Control System (SCCS) at Kennedy Space Center as a remote display developer, under NASA mentor Kurt Leucht. The main focus was on creating remote displays for the hypergolic and high pressure helium subsystem team to help control the filling of the respective tanks. As a remote display developer for the GSE hypergolic and high pressure helium subsystem team the intern was responsible for creating and testing graphical remote displays to be used in the Launch Control Center (LCC) on the Firing Room's computer monitors. To become more familiar with the subsystem, the individual attended multiple project meetings and acquired their specific requirements regarding what needed to be included in the remote displays. After receiving the requirements, the next step was to create a display that had both visual appeal and logical order using the Display Editor, on the Virtual Machine (VM). In doing so, all Compact Unique Identifiers (CUI), which are associated with specific components within the subsystem, will need to be included in each respective display for the system to run properly. Then, once the display was created it needed to be tested to ensure that the display runs as intended by using the Test Driver, also found on the VM. This Test Driver is a specific application that checks to make sure all the CUIs in the display are running properly and returning the correct form of information. After creating and locally testing the display it will need to go through further testing and evaluation before deemed suitable for actual use. By the end of the semester long experience at NASA's Kennedy Space Center, the individual should have gained great knowledge and experience in various areas of display development and testing. They were able to demonstrate this new knowledge obtained by creating multiple successful remote displays that will one day be used by the hypergolic and high pressure helium subsystem team in one of the LCC's firing rooms to fill the new Orion spacecraft.

Ground Support Systems↗

System Administrator for LCS Development Sets

The Spaceport Command and Control System Project is creating a Checkout and Control System that will eventually launch the next generation of vehicles from Kennedy Space Center. KSC has a large set of Development and Operational equipment already deployed in several facilities, including the Launch Control Center, which requires support. The position of System Administrator will complete tasks across multiple platforms (Linux/Windows), many of them virtual. The Hardware Branch of the Control and Data Systems Division at the Kennedy Space Center uses system administrators for a variety of tasks. The position of system administrator comes with many responsibilities which include maintaining computer systems, repair or set up hardware, install software, create backups and recover drive images are a sample of jobs which one must complete. Other duties may include working with clients in person or over the phone and resolving their computer system needs. Training is a major part of learning how an organization functions and operates. Taking that into consideration, NASA is no exception. Training on how to better protect the NASA computer infrastructure will be a topic to learn, followed by NASA work polices. Attending meetings and discussing progress will be expected. A system administrator will have an account with root access. Root access gives a user full access to a computer system and or network. System admins can remove critical system files and recover files using a tape backup. Problem solving will be an important skill to develop in order to complete the many tasks.

Virtualizing in Linux↗

Advancing Autonomous Operations for Deep Space Vehicles

Starting in Jan 2012, the Advanced Exploration Systems (AES) Autonomous Mission Operations (AMO) Project began to investigate the ability to create and execute "single button" crew initiated autonomous activities [1]. NASA Marshall Space Flight Center (MSFC) designed and built a fluid transfer hardware test-bed to use as a sub-system target for the investigations of intelligent procedures that would command and control a fluid transfer test-bed, would perform self-monitoring during fluid transfers, detect anomalies and faults, isolate the fault and recover the procedures function that was being executed, all without operator intervention. In addition to the development of intelligent procedures, the team is also exploring various methods for autonomous activity execution where a planned timeline of activities are executed autonomously and also the initial analysis of crew procedure development. This paper will detail the development of intelligent procedures for the NASA MSFC Autonomous Fluid Transfer System (AFTS) as well as the autonomous plan execution capabilities being investigated. Manned deep space missions, with extreme communication delays with Earth based assets, presents significant challenges for what the on-board procedure content will encompass as well as the planned execution of the procedures.

Haddock, Angie T.↗

An Information NEXUS: The NASA Global Hawk Link Module

The Link Module described in this paper was first developed for the NASA Global Hawk Pacific Mission (GloPAC), four flights of 30 hour duration, supporting the Aura Validation Experiment (AVE). Its second use was during the Genesis and Rapid Intensification Processes (GRIP) experiment, a NASA Earth Science field experiment to better understand how tropical storms form and develop into major hurricanes. In these missions, the Link module negotiated all communication over the high bandwidth Ku satellite link, archived al the science data from onboard experiments in a spatially enable database, routed command and control of the instruments from the Global Hawk Operations Center, and retransmitted select data sets directly to experimenters control and analysis systems. The availability of aggregated information from collections of sensors, and remote control capabilities, in real-time, is revolutionizing the way Airborne Science is being conducted. Also described is the next generation Link Module now being designed and tested to support the NASA Earth Venture missions, the Hurricane and Severe Storm Sentinel (HS3) mission, and Airborne Tropical Tropopause Experiment (ATTREX) mission. Advanced data fusion technologies being developed will further advance the Scientific productivity, flexibility and robustness of these systems. Historically, the Link module evolved from the instrument and communication interface controller used by NASA's Pathfinder and Pathfinder plus solar powered UAS's in the late 1990's. It later was expanded for use in the AIRDAS four channel scanner flown on the NASA Altus UAS, and then again to a module in the AMS twelve channel multispectral scanner flying on the NASA (Predator-b) Ikhana UAS. The current system is the next step in the evolution, a multi board system packaged in a Curtiss Wright MIL-spec, flight qualified enclosure.

Remote Sensing↗

Micro Cathode Arc Thruster for PhoneSat: Development and Potential Applications

NASA Ames Research Center and the George Washington University are developing an electric propulsion subsystem that will be integrated into the PhoneSat bus. Experimental tests have shown a reliable performance by firing three different thrusters at various frequencies in vacuum conditions. The interface consists of a microcontroller that sends a trigger pulse to the Pulsed Plasma Unit that is responsible for the thruster operation. A Smartphone is utilized as the main user interface for the selection of commands that control the entire system. The propellant, which is the cathode itself, is a solid cylinder made of Titanium. This simplicity in the design avoids miniaturization and manufacturing problems. The characteristics of this thruster allow an array of μCATs to perform attitude control and orbital correction maneuvers that will open the door for the implementation of an extensive collection of new mission concepts and space applications for CubeSats. NASA Ames is currently working on the integration of the system to fit the thrusters and the PPU inside a 1.5U CubeSat together with the PhoneSat bus. This satellite is intended to be deployed from the ISS in 2015 and test the functionality of the thrusters by spinning the satellite around its long axis and measure the rotational speed with the phone gyros. This test flight will raise the TRL of the propulsion system from 5 to 7 and will be a first test for further CubeSats with propulsion systems, a key subsystem for long duration or interplanetary small satellite missions.

CUBESAT↗

A Class of Selenocentric Retrograde Orbits With Innovative Applications to Human Lunar Operations

Selenocentric distant retrograde orbits with radii from approx. 12,500 km to approx. 25,000 km are assessed for stability and for suitability as crewed command and control infrastructure locations in support of telerobotic lunar surface operations and interplanetary human transport. Such orbits enable consistent transits to and from Earth at virtually any time if they are coplanar with the Moon's geocentric orbit. They possess multiple attributes and applications distinct from NASA's proposed destination orbit for a redirected asteroid about 70,000 km from the Moon.

Moon↗

Unit Testing and Remote Display Development

The Kennedy Space Center is currently undergoing an extremely interesting transitional phase. The final Space Shuttle mission, STS-135, was completed in July of 2011. NASA is now approaching a new era of space exploration. The development of the Orion Multi- Purpose Crew Vehicle (MPCV) and the Space Launch System (SLS) launch vehicle that will launch the Orion are currently in progress. An important part of this transition involves replacing the Launch Processing System (LPS) which was previously used to process and launch Space Shuttles and their associated hardware. NASA is creating the Spaceport Command and Control System (SCCS) to replace the LPS. The SCCS will be much simpler to maintain and improve during the lifetime of the spaceflight program that it will support. The Launch Control System (LCS) is a portion of the SCCS that will be responsible for launching the rockets and spacecraft. The Integrated Launch Operations Applications (ILOA) group of SCCS is responsible for creating displays and scripts, both remote and local, that will be used to monitor and control hardware and systems needed to launch a spacecraft. It is crucial that the software contained within be thoroughly tested to ensure that it functions as intended. Unit tests must be written in Application Control Language (ACL), the scripting language used by LCS. These unit tests must ensure complete code coverage to safely guarantee there are no bugs or any kind of issue with the software.

LCS↗

Development and Testing of Functionally Operative and Visually Appealing Remote Firing Room Displays and Applications

This internship provided an opportunity for an intern to work with NASA's Ground Support Equipment (GSE) for the Spaceport Command and Control System (SCCS) at Kennedy Space Center as a remote display developer, under NASA technical mentor Kurt Leucht. The main focus was on creating remote displays and applications for the hypergolic and high pressure helium subsystem team to help control the filling of the respective tanks. As a remote display and application developer for the GSE hypergolic and high pressure helium subsystem team the intern was responsible for creating and testing graphical remote displays and applications to be used in the Launch Control Center (LCC) on the Firing Room's computers. To become more familiar with the subsystem, the individual attended multiple project meetings and acquired their specific requirements regarding what needed to be included in the software. After receiving the requirements for the displays, the next step was to create displays that had both visual appeal and logical order using the Display Editor, on the Virtual Machine (VM). In doing so, all Compact Unique Identifiers (CUI), which are associated with specific components within the subsystem, were need to be included in each respective display for the system to run properly. Then, once the display was created it was to be tested to ensure that the display runs as intended by using the Test Driver, also found on the VM. This Test Driver is a specific application that checks to make sure all the CUIs in the display are running properly and returning the correct form of information. After creating and locally testing the display it needed to go through further testing and evaluation before deemed suitable for actual use. For the remote applications the intern was responsible for creating a project that focused on channelizing each component included in each display. The core of the application code was created by setting up spreadsheets and having an auto test generator, generate the complete code structure. This application code was then loaded and ran on a testing environment set to ensure the code runs as anticipated. By the end of the semester-long experience at NASA's Kennedy Space Center, the individual should have gained great knowledge and experience in various areas of both display and application development and testing. They were able to demonstrate this new knowledge obtained by creating multiple successful remote displays that will one day be used by the hypergolic and high pressure helium subsystem team in the LCC's firing rooms to service the new Orion spacecraft. The completed display channelization application will be used to receive verification from NASA quality engineers.

Display Devices↗