Search NASA⌕ Search

SEARCH · Search NASA

Results for “COMMAND SYSTEM”

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 613 records · Page 34
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

Utilizing Testing Frameworks for Launch Control Systems Continuous Integration

Command and control software is an integral part of the launch procedure. The most important part of this type of software is its ability to communicate well with the user and relay information in a correctly formatted way such that the user can understand the data. There is a tool that aides the communication between the different parts of the system, and effectively, the user. This instrument is capable of taking several complex values and ensuring that they are correctly sorted into their distinctive message values and distributed properly among the different facets of the system. This tool will easily translate and publish the data inside of messages in the system to something that is readable and understandable. The tool also allows for transmission of the recorded data to the user, effectively ensuring the communication between different components of the system. As well as keeping track of messages and ensuring that the information contained within each of them reaches the correct location, this tool has the ability to keep track of its own statistics and determine how many messages passed in were erroneous and how many were successfully transmitted. It is able to check and see what the total message failure count is when an invalid message is given, as well as the number of different messages and their respective types passed into the tool. This tool is of great value to the new Space Launch System (SLS). As such, the tool must be thoroughly tested with test cases that, although improbable, are possible, where the tool may not function properly. Testing an interface this complex is necessary to ensure mission safety and create unlikely scenarios where the tool would work as intended, and stretch its limits to test that even under the most uncommon conditions it would still continue to function. This software will be an important part of the control system for the newest spacecraft which will fly deeper into space than humans have ever travelled. It will fly beyond the moon, into deep space to Mars and perhaps set the groundwork for a manned mission even further to create more opportunities for interplanetary and even interstellar travel by humans. This mission relies heavily on software and hardware to ensure the safety of the humans that will be on board and therefore must be checked, exhausting each and every different situation, such that there is not a doubt surrounding the well-being of the humans aboard the rocket. That is why testing is such an important part of the mission. It provides evidence that the systems aboard the rocket and on the launch pad are safe.

Unit Testing↗
NASA NTRS2006

Transforming Our SMEX Organization by Way of Innovation, Standardization, and Automation

NASA's Small Explorer (SMEX) Flight Operations Team (FOT) is currently tackling the challenge of supporting ground operations for several satellites that have surpassed their designed lifetime and have a dwindling budget. At Goddard Space Flight Center (GSFC), these missions are presently being reengineered into a fleet-oriented ground system. When complete, this ground system will provide command and control of four SMEX missions, and will demonstrate fleet automation and control concepts as a pathfinder for additional mission integrations. A goal of this reengineering effort is to demonstrate new ground-system technologies that show promise of supporting longer mission lifecycles and simplifying component integration. In pursuit of this goal, the SMEX organization has had to examine standardization, innovation, and automation. A core technology being demonstrated in this effort is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture focuses on providing standard interfaces for ground system applications to promote application interoperability. Building around commercial Message Oriented Middleware and providing a common messaging standard allows GMSEC to provide the capabilities necessary to support integration of new software components into existing missions and increase the level of interaction within the system. For SMS, GMSEC has become the technology platform to transform flight operations with the innovation and automation necessary to reduce operational costs. The automation technologies supported in SMEX are built upon capabilities provided by the GMSEC architecture that allows the FOT to further reduce the involvement of the console, operator. Initially, SMEX is automating only routine operations, such as safety and health monitoring, basic commanding, and system recovery. The operational concepts being developed here will reduce the need for staffed passes and are a necessity for future fleet management. As this project continues to evolve, additional innovations beyond GMSEC and automation have, and will continue to be developed. The team developed techniques for migrating ground systems of existing on-orbit assets. The tools necessary to monitor and control software failures were integrated and tailored for operational environments. All this was done with a focus of extending fleet operations to mission beyond SMU. The result of this work is the foundation for a broader fleet-capable ground system that will include several missions supported by the Space Science Mission Operations Project.

Madden, Maureen↗
NASA NTRS1987

A learning controller for nonrepetitive robotic operation

A practical learning control system is described which is applicable to complex robotic and telerobotic systems involving multiple feedback sensors and multiple command variables. In the controller, the learning algorithm is used to learn to reproduce the nonlinear relationship between the sensor outputs and the system command variables over particular regions of the system state space, rather than learning the actuator commands required to perform a specific task. The learned information is used to predict the command signals required to produce desired changes in the sensor outputs. The desired sensor output changes may result from automatic trajectory planning or may be derived from interactive input from a human operator. The learning controller requires no a priori knowledge of the relationships between the sensor outputs and the command variables. The algorithm is well suited for real time implementation, requiring only fixed point addition and logical operations. The results of learning experiments using a General Electric P-5 manipulator interfaced to a VAX-11/730 computer are presented. These experiments involved interactive operator control, via joysticks, of the position and orientation of an object in the field of view of a video camera mounted on the end of the robot arm.

Miller, W. T., III↗
NASA NTRS2014

Remote Software Application and Display Development

The era of the shuttle program has come to an end, but only to give rise to newer and more exciting projects. Now is the time of the Orion spacecraft, a work of art designed to exceed all previous endeavors of man. NASA is exiting the time of exploration and is entering a new period, a period of pioneering. With this new mission, many of NASAs organizations must undergo a great deal of change and development to support the Orion missions. The Spaceport Command and Control System (SCCS) is the new system that will provide NASA the ability to launch rockets into orbit and thus control Orion and other spacecraft as the goal of populating Mars becomes ever increasingly tangible. Since the previous control system, Launch Processing System (LPS), was primarily designed to launch the shuttles, SCCS was needed as Kennedy Space Center (KSC) reorganized to a multiuser spaceport for commercial flights, providing a more versatile control over rockets. Within SCCS, is the Launch Control System (LCS), which is the remote software behind the command and monitoring of flight and ground system hardware. This internship at KSC has involved two main components in LCS, including Remote Software Application and Display development. The display environment provides a graphical user interface for an operator to view and see if any cautions are raised, while the remote applications are the backbone that communicate with hardware, and then relay the data back to the displays. These elements go hand in hand as they provide monitoring and control over hardware and software alike from the safety of the Launch Control Center. The remote software applications are written in Application Control Language (ACL), which must undergo unit testing to ensure data integrity. This paper describes both the implementation and writing of unit tests in ACL code for remote software applications, as well as the building of remote displays to be used in the Launch Control Center (LCC).

ACL↗
NASA NTRS2014

Supporting Multiple Programs and Projects at NASA's Kennedy Space Center

With the conclusion of the shuttle program in 2011, the National Aeronautics and Space Administration (NASA) had found itself at a crossroads for finding transportation of United States astronauts and experiments to space. The agency would eventually hand off the taxiing of American astronauts to the International Space Station (ISS) that orbits in Low Earth Orbit (LEO) about 210 miles above the earth under the requirements of the Commercial Crew Program (CCP). By privatizing the round trip journey from Earth to the ISS, the space agency has been given the additional time to focus funding and resources to projects that operate beyond LEO; however, adding even more stress to the agency, the premature cancellation of the program that would succeed the Shuttle Program - The Constellation Program (CxP) -it would inevitably delay the goal to travel beyond LEO for a number of years. Enter the Space Launch System (SLS) and the Orion Multipurpose Crew Vehicle (MPCV). Currently, the SLS is under development at NASA's Marshall Spaceflight Center in Huntsville, Alabama, while the Orion Capsule, built by government contractor Lockheed Martin Corporation, has been assembled and is currently under testing at the Kennedy Space Center (KSC) in Florida. In its current vision, SLS will take Orion and its crew to an asteroid that had been captured in an earlier mission in lunar orbit. Additionally, this vehicle and its configuration is NASA's transportation to Mars. Engineers at the Kennedy Space Center are currently working to test the ground systems that will facilitate the launch of Orion and the SLS within its Ground Services Development and Operations (GSDO) Program. Firing Room 1 in the Launch Control Center (LCC) has been refurbished and outfitted to support the SLS Program. In addition, the Spaceport Command and Control System (SCCS) is the underlying control system for monitoring and launching manned launch vehicles. As NASA finds itself at a junction, so does all of its associated centers across the US. KSC has found itself at the blunt end of change as the entire center has transitioned from an operations mindset to a development mentality. The author of this paper has had the fortunate privilege and opportunity to be part of a transforming NASA during the fall months of 2014. The following is a high level account of projects that he had the chance to work on including the Spaceport Command and Control System, the Advanced Ground System and Maintenance Program Project, Customer Avionics Development & Analysis (CAIDA) Lab and Swamp Works.

Advanced Ground System Maintenance↗
NASA NTRS2000

Selection of the Ground Segment for the Next Generation Space Telescope (NGST)

The Next Generation Space Telescope (NGST) is a large aperture space telescope designated to succeed the Hubble Space Telescope (HST). NGST will continue the recent breakthroughs of HST in our understanding of the earliest origins of stars, galaxies and the elements that are the foundations of Life. It is expected that the costs of NGST should be kept within a fraction of those for HST. The ground segment has a goal of reducing the cost of NGST in comparison to HST by 50% to 75%. To mitigate risks for NGST a flight demonstrator called Nexus is planned for 2005. Nexus is a smaller scale telescope, which plans to test the deployment and optical stability of the telescope, the "Wave Front Control" process, and the thermal performance of the sunshield. The Nexus Ground System will be developed by GSFC and STSci, and the NGST Ground System will be developed by STSci. The authors of this paper are engaged in a study to evaluate and recommend selection of a Command and Telemetry system for each of these Ground Systems. This paper focuses on the process of selecting the real-time Command and Telemetry system for NGST. We would like to use the conference as a sounding board as we make a selection.

Gal-Edd, Jonathan↗
NASA NTRS1986

AI challenges for spacecraft control programs

The application of AI technology to the spacecraft and experiment command and control systems environment is proposed. The disadvantages of the present methods for analyzing and resolving spacecraft experiment command and control problems are discussed. The potential capabilities and advantages of using AI for the spacecraft and experiment command and control systems are described.

Lightfoot, Patricia↗
NASA NTRS1986

A new meaning to 'flying the desk'

A unique advanced transport flight station design is described. The various systems and displays of the design are described, including: the configuration; switches; tailored logic/artificial intelligence; primary flight controllers; front panel displays; primary flight/navigation display; engine power/status, approach charts, and weather display; the Advisory, Caution, and Warning System/Cockpit Display of Traffic Information display; checklist/functional systems display; head-up display; voice command and response system; Flight Management Computer system; and integrated communications/navigation system. The application of the flight station to military research is briefly discussed.

Sexton, G. A.↗
NASA NTRS1988

Development of a C3 generic workstation: System overview

A command, control, and communications (C3) environment is described which will be applied to the evaluation of performance of aircrews, particularly in situations in which they are subjected to chemical defense protection drugs and antihistamines.

Strome, David R.↗
NASA NTRS2013

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 NTRS2012

International Space Station Payload Operations Integration Center (POIC) Overview

Objectives and Goals: Maintain and operate the POIC and support integrated Space Station command and control functions. Provide software and hardware systems to support ISS payloads and Shuttle for the POIF cadre, Payload Developers and International Partners. Provide design, development, independent verification &validation, configuration, operational product/system deliveries and maintenance of those systems for telemetry, commanding, database and planning. Provide Backup Control Center for MCC-H in case of shutdown. Provide certified personnel and systems to support 24x7 facility operations per ISS Program. Payloads CoFR Implementation Plan (SSP 52054) and MSFC Payload Operations CoFR Implementation Plan (POIF-1006).

Ijames, Gayleen N.↗
NASA NTRS1996

GOES-8 and -9 mission launch and operations support overview

The new series of geosynchronous operational environmental satellite (GOES) missions, GOES-8 and GOES-9, provide greater instrument coverage flexibility and greater resolution than previous GOES spinners. This added flexibility and the three-axis stabilized operating mode results in control system of increased complexity: almost 5000 real-time commands are sent daily to the satellites compared to 200 commands per day for GOES-7. These advanced technologies present new challenges to the NASA operations support personnel. In order to prepare for launching, post-launch tests and in-orbit operations, a mission planning scheme was developed in order to assure the flight system command and the systems' health monitoring. The mission operations approaches are reviewed together with the associated philosophies and the operation tools developed to assist the personnel in performing complex routine and special operation tasks.

McCuistion, D.↗
NASA NTRS1977

NASA standard communications and data handling subsystem

The paper gives a functional description and discusses hardware implementation for the Communication and Data Handling (C&DH) subsystem of the Multimission Modular Spacecraft. The C&DH subsystem: (1) provides the command and telemetry link between the spacecraft and the terrestrial system, (2) distributes commands to and collects telemetry from all spacecraft systems via a duplex serial multiplex data bus and remote interface units, and (3) contains onboard computation capability. The C&DH is a single 4 x 4 x 1-1/2 foot module; the stuffed module weighs 270 lbs including 60 lbs of mission unique weight. The hardware is versatile and cost effective, and its modular structure permits repair, refurbishment, and even modification/updating in space

Robinson, D. L.↗
NASA NTRS2008

James Webb Space Telescope - Applying Lessons Learned to I&T

The James Webb Space Telescope (JWST) is part of a new generation of spacecraft acquiring large data volumes from remote regions in space. To support a mission such as the JWST, it is imperative that lessons learned from the development of previous missions such as the Hubble Space Telescope and the Earth Observing System mission set be applied throughout the development and operational lifecycles. One example of a key lesson that should be applied is that core components, such as the command and telemetry system and the project database, should be developed early, used throughout development and testing, and evolved into the operational system. The purpose of applying lessons learned is to reap benefits in programmatic or technical parameters such as risk reduction, end product quality, cost efficiency, and schedule optimization. In the cited example, the early development and use of the operational command and telemetry system as well as the establishment of the intended operational database will allow these components to be used by the developers of various spacecraft components such that development, testing, and operations will all use the same core components. This will reduce risk through the elimination of transitions between development and operational components and improve end product quality by extending the verification of those components through continual use. This paper will discuss key lessons learned that have been or are being applied to the JWST Ground Segment integration and test program.

Johns, Alan↗
NASA NTRS1971

Communication system modeling

This report presents the results of work on communications systems modeling and covers three different areas of modeling. The first of these deals with the modeling of signals in communication systems in the frequency domain and the calculation of spectra for various modulations. These techniques are applied in determining the frequency spectra produced by a unified carrier system, the down-link portion of the Command and Communications System (CCS). The second modeling area covers the modeling of portions of a communication system on a block basis. A detailed analysis and modeling effort based on control theory is presented along with its application to modeling of the automatic frequency control system of an FM transmitter. A third topic discussed is a method for approximate modeling of stiff systems using state variable techniques.

Holland, L. D.↗
NASA NTRS1989

Knowledge based and interactive control for the Superfluid Helium On-orbit Transfer Project

NASA's Superfluid Helium On-Orbit Transfer (SHOOT) project is a Shuttle-based experiment designed to acquire data on the properties of superfluid helium in micro-gravity. Aft Flight Deck Computer Software for the SHOOT experiment is comprised of several monitoring programs which give the astronaut crew visibility into SHOOT systems and a rule based system which will provide process control, diagnosis and error recovery for a helium transfer without ground intervention. Given present Shuttle manifests, this software will become the first expert system to be used in space. The SHOOT Command and Monitoring System (CMS) software will provide a near real time highly interactive interface for the SHOOT principal investigator to control the experiment and to analyze and display its telemetry. The CMS software is targeted for all phases of the SHOOT project: hardware development, pre-flight pad servicing, in-flight operations, and post-flight data analysis.

Castellano, Timothy P.↗