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 451 records · Page 25
All sourcesNASA NTRSDOE OSTI
NASA NTRS2017

Launch Control System Software Development System Automation Testing

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administration's (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This system requires high quality testing that will measure and test the capabilities of the system. For the past two years, the Exploration and Operations Division at Kennedy Space Center (KSC) has assigned a group including interns and full-time engineers to develop automated tests to save the project time and money. The team worked on automating the testing process for the SCCS GUI that would use streamed simulated data from the testing servers to produce data, plots, statuses, etc. to the GUI. The software used to develop automated tests included an automated testing framework and an automation library. The automated testing framework has a tabular-style syntax, which means the functionality of a line of code must have the appropriate number of tabs for the line to function as intended. The header section contains either paths to custom resources or the names of libraries being used. The automation library contains functionality to automate anything that appears on a desired screen with the use of image recognition software to detect and control GUI components. The data section contains any data values strictly created for the current testing file. The body section holds the tests that are being run. The function section can include any number of functions that may be used by the current testing file or any other file that resources it. The resources and body section are required for all test files; the data and function sections can be left empty if the data values and functions being used are from a resourced library or another file. To help equip the automation team with better tools, the Project Lead of the Automated Testing Team, Jason Kapusta, assigned the task to install and train an optical character recognition (OCR) tool to Brandon Echols, a fellow intern, and I. The purpose of the OCR tool is to analyze an image and find the coordinates of any group of text. Some issues that arose while installing the OCR tool included the absence of certain libraries needed to train the tool and an outdated software version. We eventually resolved the issues and successfully installed the OCR tool. Training the tool required many images and different fonts and sizes, but in the end the tool learned to accurately decipher the text in the images and their coordinates. The OCR tool produced a file that contained significant metadata for each section of text, but only the text and coordinates of the text was required for our purpose. The team made a script to parse the information we wanted from the OCR file to a different file that would be used by automation functions within the automated framework. Since a majority of development and testing for the automated test cases for the GUI in question has been done using live simulated data on the workstations at the Launch Control Center (LCC), a large amount of progress has been made. As of this writing, about 60% of all of automated testing has been implemented. Additionally, the OCR tool will help make our automated tests more robust due to the tool's text recognition being highly scalable to different text fonts and text sizes. Soon we will have the whole test system automated, allowing for more full-time engineers working on development projects.

Automation↗
NASA NTRS2022

An Overview of the Current State of the Art on Small Spacecraft Avionics Systems

Small spacecraft command and data handling and flight software systems, technologies, and capabilities are continuously evolving, enabling new opportunities for developing and deploying next-generation small spacecraft avionics. When small spacecraft were first introduced, their primary purpose was to observe and send information back to Earth. As awareness and utility expands, there is a need to improve the overall capability of collecting data in a specific mission environment. Small spacecraft currently perform a wide variety of science in low-Earth orbit and are emerging as candidates for more formidable beyond low-Earth orbit missions. This paper will expand on the technological evolution of avionics systems, their requirements to meet the need for modern, complex small spacecraft missions, and the updated avionics architecture composition. The authors will also inform the readers on the current state-of-the-art in SmallSat avionics and connect decentralized avionics architecture to non-aerospace applications and its underlying role in the movement to “digitally managed everything”.

B. Yost↗
NASA NTRS1978

A nonlinear trajectory command generator for a digital flight-control system

Operational application of the command generator (CG) was examined in detail in a simulation of a flight control system with the augmentor wing jet STOL research aircraft. The basic repertoire of single axis maneuvers and operational constraints are discussed, and the system behavior is tested on a rigorous STOL approach path and as affected by various approximations in the CG synthesis and types of disturbances found in the operational environment. The simulation results indicate that a satisfactory nonlinear system with general maneuvering capabilities throughout the flight envelope was developed which satisfies the basic design objectives while maintaining a practicable degree of simplicity.

Cicolani, L. S.↗
NASA NTRS1985

Development of an expert system prototype for determining software functional requirements for command management activities at NASA Goddard

The development of an expert system prototype for determining software functional requirements for NASA Goddard's Command Management System (CMS) is described. The role of the CMS is to transform general requests into specific spacecraft commands with command execution conditions. The CMS is part of the NASA Data System which entails the downlink of science and engineering data from NASA near-earth satellites to the user, and the uplink of command and control data to the spacecraft. Subjects covered include: the problem environment of determining CMS software functional requirements; the expert system approach for handling CMS requirements development; validation and evaluation procedures for the expert system.

Liebowitz, J.↗
NASA NTRS1986

The emergence of Zipf's law - Spontaneous encoding optimization by users of a command language

The distribution of commands issued by experienced users of a computer operating system allowing command customization tends to conform to Zipf's law. This result documents the emergence of a statistical property of natural language as users master an artificial language. Analysis of Zipf's law by Mandelbrot and Cherry shows that its emergence in the computer interaction of experienced users may be interpreted as evidence that these users optimize their encoding of commands. Accordingly, the extent to which users of a command language exhibit Zipf's law can provide a metric of the naturalness and efficiency with which that language is used.

Ellis, S. R.↗
NASA NTRS1986

Development of an expert system prototype for determining software functional requirements for command management activities at NASA Goddard

The development of an expert system prototype for software functional requirement determination for NASA Goddard's Command Management System, as part of its process of transforming general requests into specific near-earth satellite commands, is described. The present knowledge base was formulated through interactions with domain experts, and was then linked to the existing Knowledge Engineering Systems (KES) expert system application generator. Steps in the knowledge-base development include problem-oriented attribute hierarchy development, knowledge management approach determination, and knowledge base encoding. The KES Parser and Inspector, in addition to backcasting and analogical mapping, were used to validate the expert system-derived requirements for one of the major functions of a spacecraft, the solar Maximum Mission. Knowledge refinement, evaluation, and implementation procedures of the expert system were then accomplished.

Liebowitz, J.↗
NASA NTRS1987

Emergency Control for a Circulation-Control Helicopter Rotor

Digital system gives pilot partial command when primary system fails. Emergency system provides digital control of rigid circulation-control rotor for experimental X-wing aircraft. In addition to centering collective-pitch control, new command provides limited roll control via collective pitch and gyroscopic decoupling in pitch and aerodynamic decoupling.

Fischer, William C.↗
NASA NTRS1984

The 1984 ASEE-NASA summer faculty fellowship program (aeronautics and research)

The 1984 NASA-ASEE Faculty Fellowship Program (SFFP) is reported. The report includes: (1) a list of participants; (2) abstracts of research projects; (3) seminar schedule; (4) evaluation questionnaire; and (5) agenda of visitation by faculty programs committee. Topics discussed include: effects of multiple scattering on laser beam propagation; information management; computer techniques; guidelines for writing user documentation; 30 graphics software; high energy electron and antiproton cosmic rays; high resolution Fourier transform infrared spectrum; average monthly annual zonal and global albedos; laser backscattering from ocean surface; image processing systems; geomorphological mapping; low redshift quasars; application of artificial intelligence to command management systems.

Dah-Nien, F.↗
NASA NTRS1985

The Galileo scan platform pointing control system - A modern control theoretic viewpoint

The current Galileo scan platform pointing control system (SPPCS) is described, and ways in which modern control concepts could serve to enhance it are considered. Of particular interest are: the multi-variable design model and overall control system architecture, command input filtering, feedback compensator and command input design, stability robustness constraint for both continuous time control systems and for sampled data control systems, and digital implementation of the control system. The proposed approach leads to the design of a system that is similar to current Galileo SPPCS configuration, but promises to be more systematic.

Sevaston, G. E.↗
NASA NTRS2004

Proposed Development of NASA Glenn Research Center's Aeronautical Network Research Simulator

Accurate knowledge and understanding of data link traffic loads that will have an impact on the underlying communications infrastructure within the National Airspace System (NAS) is of paramount importance for planning, development and fielding of future airborne and ground-based communications systems. Attempting to better understand this impact, NASA Glenn Research Center (GRC), through its contractor Computer Networks & Software, Inc. (CNS, Inc.), has developed an emulation and test facility known as the Virtual Aircraft and Controller (VAC) to study data link interactions and the capacity of the NAS to support Controller Pilot Data Link Communications (CPDLC) traffic. The drawback of the current VAC test bed is that it does not allow the test personnel and researchers to present a real world RF environment to a complex airborne or ground system. Fortunately, the United States Air Force and Navy Avionics Test Commands, through its contractor ViaSat, Inc., have developed the Joint Communications Simulator (JCS) to provide communications band test and simulation capability for the RF spectrum through 18 GHz including Communications, Navigation, and Identification and Surveillance functions. In this paper, we are proposing the development of a new and robust test bed that will leverage on the existing NASA GRC's VAC and the Air Force and Navy Commands JCS systems capabilities and functionalities. The proposed NASA Glenn Research Center's Aeronautical Networks Research Simulator (ANRS) will combine current Air Traffic Control applications and physical RF stimulation into an integrated system capable of emulating data transmission behaviors including propagation delay, physical protocol delay, transmission failure and channel interference. The ANRS will provide a simulation/stimulation tool and test bed environment that allow the researcher to predict the performance of various aeronautical network protocol standards and their associated waveforms under varying density conditions. The system allows the user to define human-interactive and scripted aircraft and controller models of various standards, such as (but not limited to) Very High Frequency Digital Link (VDL) of various modes.

Nguyen, Thanh C.↗
NASA NTRS1962

NIMBUS COMMAND SUBSYSTEM

All satellites have one common requirement, known as the command facility. This is usually a real-time direct RF link from a ground transmitter through the satellite receiver and decoder to a relay or controlled circuit. The more sophisticated research and operational satellites require a command facility which will permit storing of commands to activate systems at predetermined future times when the satellite is beyond the range of the command ground station. These satellites require an accurate clock and a source of precision frequencies. In the Nimbus spacecraft, all these functions are performed by an integrated command and clock subsystem, which includes the command clock and clock-receiver modules in the spacecraft, plus the associated command ground station. This paper will describe the functions and features of these various equipment's.

GROUND SUPPORT SYSTEM↗
NASA NTRS1988

Solutions to time variant problems of real-time expert systems

Real-time expert systems for monitoring and control are driven by input data which changes with time. One of the subtle problems of this field is the propagation of time variant problems from rule to rule. This propagation problem is even complicated under a multiprogramming environment where the expert system may issue test commands to the system to get data and to access time consuming devices to retrieve data for concurrent reasoning. Two approaches are used to handle the flood of input data. Snapshots can be taken to freeze the system from time to time. The expert system treats the system as a stationary one and traces changes by comparing consecutive snapshots. In the other approach, when an input is available, the rules associated with it are evaluated. For both approaches, if the premise condition of a fired rule is changed to being false, the downstream rules should be deactivated. If the status change is due to disappearance of a transient problem, actions taken by the fired downstream rules which are no longer true may need to be undone. If a downstream rule is being evaluated, it should not be fired. Three mechanisms for solving this problem are discussed: tracing, backward checking, and censor setting. In the forward tracing mechanism, when the premise conditions of a fired rule become false, the premise conditions of downstream rules which have been fired or are being evaluated due to the firing of that rule are reevaluated. A tree with its root at the rule being deactivated is traversed. In the backward checking mechanism, when a rule is being fired, the expert system checks back on the premise conditions of the upstream rules that result in evaluation of the rule to see whether it should be fired. The root of the tree being traversed is the rule being fired. In the censor setting mechanism, when a rule is to be evaluated, a censor is constructed based on the premise conditions of the upstream rules and the censor is evaluated just before the rule is fired. Unlike the backward checking mechanism, this one does not search the upstream rules. This paper explores the details of implementation of the three mechanisms.

Yeh, Show-Way↗
NASA NTRS1991

Collision avoidance for CTV: Requirements and capabilities

Cargo transfer vehicle (CTV) operations near Space Station Freedom will require positive collision avoidance maneuver (CAM) capability to preclude any change of collision, even in the event of CTV failures. The requirements for CAM are discussed, and the CAM design approach and design of the Orbiting Maneuvering Vehicle (OMV) are reviewed; this design met requirements for OMV operation near the Space Station, provided a redundant collision avoidance maneuver capability. Significant portions of the OMV CAM design should be applicable to CTV. The key features of the OMV design are summarized and related to the CTV mission design to that of OMV's. CAM is a defined sequence of events executed by the CTV to place the vehicle in a safe position relative to a target such as the Space Station. CAM can be performed through software commands to the propulsion system, or through commands pre-stored in hardware. Various techniques for triggering CAM are considered, and the risks associated with CAM enable and execution in phases are considered. OMV CAM design features both hardware and software CAM capability, with analyses conducted to assess the ability to meet the collision-free requirement during all phases of the mission.

Nosek, Thomas P.↗
NASA NTRS2000

Ground Data System Risk Mitigation Techniques for Faster, Better, Cheaper Missions

With the advent of faster, cheaper, and better missions, NASA Projects acknowledged that a higher level of risk was inherent and accepted with this approach. It was incumbent however upon each component of the Project whether spacecraft, payload, launch vehicle, or ground data system to ensure that the mission would nevertheless be an unqualified success. The Small Explorer (SMEX) program's ground data system (GDS) team developed risk mitigation techniques to achieve these goals starting in 1989. These techniques have evolved through the SMEX series of missions and are practiced today under the Triana program. These techniques are: (1) Mission Team Organization--empowerment of a closeknit ground data system team comprising system engineering, software engineering, testing, and flight operations personnel; (2) Common Spacecraft Test and Operational Control System--utilization of the pre-launch spacecraft integration system as the post-launch ground data system on-orbit command and control system; (3) Utilization of operations personnel in pre-launch testing--making the flight operations team an integrated member of the spacecraft testing activities at the beginning of the spacecraft fabrication phase; (4) Consolidated Test Team--combined system, mission readiness and operations testing to optimize test opportunities with the ground system and spacecraft; and (5). Reuse of Spacecraft, Systems and People--reuse of people, software and on-orbit spacecraft throughout the SMEX mission series. The SMEX ground system development approach for faster, cheaper, better missions has been very successful. This paper will discuss these risk management techniques in the areas of ground data system design, implementation, test, and operational readiness.

Catena, John J.↗
NASA NTRS2004

Open-systems architecture of a standardized command interface chip-set for switching and control of a spacecraft power bus

The Jet Propulsion Laboratory (JPL) has developed a command interface chip-set that primarily consists of two mixed-signal ASICs'; the Command Interface ASIC (CIA) and Analog Interface ASIC (AIA). The Open-systems architecture employed during the design of this chip-set enables its use as both an intelligent gateway between the system's flight computer and the control, actuation, and activation of the spacecraft's loads, valves, and pyrotechnics respectfully as well as the regulator of the spacecraft power bus. Furthermore, the architecture is highly adaptable and employed fault-tolerant design methods enabling a host of other mission uses including reliable remote data collection. The objective of this design is to both provide a needed flight component that meets the stringent environmental requirements of current deep space missions and to add a new element to a growing library that can be used as a standard building block for future missions to the outer planets.

flight computers↗