Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “command and 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

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↗

Manchester Coding Option for SpaceWire: Providing Choices for System Level Design

This paper proposes an optional coding scheme for SpaceWire in lieu of the current Data Strobe scheme for three reasons. First reason is to provide a straightforward method for electrical isolation of the interface; secondly to provide ability to reduce the mass and bend radius of the SpaceWire cable; and thirdly to provide a means for a common physical layer over which multiple spacecraft onboard data link protocols could operate for a wide range of data rates. The intent is to accomplish these goals without significant change to existing SpaceWire design investments. The ability to optionally use Manchester coding in place of the current Data Strobe coding provides the ability to DC balanced the signal transitions unlike the SpaceWire Data Strobe coding; and therefore the ability to isolate the electrical interface without concern. Additionally, because the Manchester code has the clock and data encoded on the same signal, the number of wires of the existing SpaceWire cable could be optionally reduced by 50. This reduction could be an important consideration for many users of SpaceWire as indicated by the already existing effort underway by the SpaceWire working group to reduce the cable mass and bend radius by elimination of shields. However, reducing the signal count by half would provide even greater gains. It is proposed to restrict the data rate for the optional Manchester coding to a fixed data rate of 10 Megabits per second (Mbps) in order to make the necessary changes simple and still able to run in current radiation tolerant Field Programmable Gate Arrays (FPGAs). Even with this constraint, 10 Mbps will meet many applications where SpaceWire is used. These include command and control applications and many instruments applications with have moderate data rate. For most NASA flight implementations, SpaceWire designs are in rad-tolerant FPGAs, and the desire to preserve the heritage design investment is important for cost and risk considerations. The Manchester coding option can be accommodated in existing designs with only changes to the FPGA.

Electrical Isolation↗

Firing Room Remote Application Software Development

The Engineering and Technology Directorate (NE) at National Aeronautics and Space Administration (NASA) Kennedy Space Center (KSC) is designing a new command and control system for the checkout and launch of Space Launch System (SLS) and future rockets. The purposes of the semester long internship as a remote application software developer include the design, development, integration, and verification of the software and hardware in the firing rooms, in particular with the Mobile Launcher (ML) Launch Accessories subsystem. In addition, a Conversion Fusion project was created to show specific approved checkout and launch engineering data for public-friendly display purposes.

Pathways↗

OSIRIS-REx, Returning the Asteroid Sample

This paper addresses the technical aspects of the sample return system for the upcoming Origins, Spectral Interpretation, Resource Identification, and Security-Regolith Explorer (OSIRIS-REx) asteroid sample return mission. The overall mission design and current implementation are presented as an overview to establish a context for the technical description of the reentry and landing segment of the mission.The prime objective of the OSIRIS-REx mission is to sample a primitive, carbonaceous asteroid and to return that sample to Earth in pristine condition for detailed laboratory analysis. Targeting the near-Earth asteroid Bennu, the mission launches in September 2016 with an Earth reentry date of September 24, 2023.OSIRIS-REx will thoroughly characterize asteroid Bennu providing knowledge of the nature of near-Earth asteroids that is fundamental to understanding planet formation and the origin of life. The return to Earth of pristine samples with known geologic context will enable precise analyses that cannot be duplicated by spacecraft-based instruments, revolutionizing our understanding of the early Solar System. Bennu is both the most accessible carbonaceous asteroid and one of the most potentially Earth-hazardous asteroids known. Study of Bennu addresses multiple NASA objectives to understand the origin of the Solar System and the origin of life and will provide a greater understanding of both the hazards and resources in near-Earth space, serving as a precursor to future human missions to asteroids.This paper focuses on the technical aspects of the Sample Return Capsule (SRC) design and concept of operations, including trajectory design and reentry retrieval. Highlights of the mission are included below.The OSIRIS-REx spacecraft provides the essential functions for an asteroid characterization and sample return mission: attitude control propulsion power thermal control telecommunications command and data handling structural support to ensure successful rendezvous with Bennu characterization of Bennus properties delivery of the sampler to the surface, and return of the spacecraft to the vicinity of the Earth sample collection, performed by the Touch-and-Go Sample Acquisition Mechanism (TAGSAM), to acquire a regolith sample from the surface Earth re-entry and SRC recovery. Following sample collection, OSIRIS-REx drifts away from Bennu until the Asteroid Departure Maneuver is commanded on March 4, 2021, sending OSIRIS-REx on a ballistic return cruise to Earth. No additional large deterministic maneuvers are required to return the SRC to Earth. During the cruise, tracking and trajectory correction maneuvers (TCMs) are performed as necessary to precisely target the entry corridor. As OSIRIS-REx approaches Earth, the reentry plans are reviewed starting about a year before arrival, and preparations begin. The spacecraft is targeted away from the Earth until 7 days before entry. The final two trajectory correction maneuvers bring the spacecraft on target toward the Utah Test and Training Range (UTTR), with sufficient time for contingency resolution. The SRC releases 4 hours prior to atmospheric entry interface and, using the Stardust capsule heritage design, employs a traditional drogue and main parachute descent system for a soft touchdown.

reentry↗

NASA GRC UAS Project - Communications Modeling and Simulation Development 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 Modeling and Simulation team, will provide an update to this ongoing effort at NASA GRC as follow-up to the overview of the planned simulation effort presented at ICNS in 2013. The objective of presentation will be to describe the progress made in developing both a NAS-Wide simulation architecture application and the detailed radiocomm system models for this research, and will present interim data and information compiled in the process of developing these simulation capabilities to date.

Modeling and Simulation↗

Command Process Modeling & Risk Analysis

Commanding Errors may be caused by a variety of root causes. It's important to understand the relative significance of each of these causes for making institutional investment decisions. One of these causes is the lack of standardized processes and procedures for command and control. We mitigate this problem by building periodic tables and models corresponding to key functions within it. These models include simulation analysis and probabilistic risk assessment models.

functional analysis↗

Integrated Test and Evaluation Flight Test 3 Flight Test Plan

The desire and ability to fly Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) is of increasing urgency. The application of unmanned aircraft to perform national security, defense, scientific, and emergency management are driving the critical need for less restrictive access by UAS to the NAS. UAS represent a new capability that will provide a variety of services in the government (public) and commercial (civil) aviation sectors. The growth of this potential industry has not yet been realized due to the lack of a common understanding of what is required to safely operate UAS in the NAS. NASA's UAS Integration into the NAS Project is conducting research in the areas of Separation Assurance/Sense and Avoid Interoperability, Human Systems Integration (HSI), and Communication to support reducing the barriers of UAS access to the NAS. This research is broken into two research themes namely, UAS Integration and Test Infrastructure. UAS Integration focuses on airspace integration procedures and performance standards to enable UAS integration in the air transportation system, covering Sense and Avoid (SAA) performance standards, command and control performance standards, and human systems integration. The focus of Test Infrastructure is to enable development and validation of airspace integration procedures and performance standards, including the integrated test and evaluation. In support of the integrated test and evaluation efforts, the Project will develop an adaptable, scalable, and schedulable relevant test environment capable of evaluating concepts and technologies for unmanned aircraft systems to safely operate in the NAS. To accomplish this task, the Project will conduct a series of Human-in-the-Loop and Flight Test activities that integrate key concepts, technologies and/or procedures in a relevant air traffic environment. Each of the integrated events will build on the technical achievements, fidelity and complexity of the previous tests and technical simulations, resulting in research findings that support the development of regulations governing the access of UAS into the NAS.

Unmanned↗

The Deep Impact Network Experiment Operations Center

Delay/Disruption Tolerant Networking (DTN) promises solutions in solving space communications challenges arising from disconnections as orbiters lose line-of-sight with landers, long propagation delays over interplanetary links, and other phenomena. DTN has been identified as the basis for the future NASA space communications network backbone, and international standardization is progressing through both the Consultative Committee for Space Data Systems (CCSDS) and the Internet Engineering Task Force (IETF). JPL has developed an implementation of the DTN architecture, called the Interplanetary Overlay Network (ION). ION is specifically implemented for space use, including design for use in a real-time operating system environment and high processing efficiency. In order to raise the Technology Readiness Level of ION, the first deep space flight demonstration of DTN is underway, using the Deep Impact (DI) spacecraft. Called the Deep Impact Network (DINET), operations are planned for Fall 2008. An essential component of the DINET project is the Experiment Operations Center (EOC), which will generate and receive the test communications traffic as well as "out-of-DTN band" command and control of the DTN experiment, store DTN flight test information in a database, provide display systems for monitoring DTN operations status and statistics (e.g., bundle throughput), and support query and analyses of the data collected. This paper describes the DINET EOC and its value in the DTN flight experiment and potential for further DTN testing.

flight experiment↗