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 631 records · Page 35

Automated Diagnosis and Control of Complex Systems

Livingstone2 is a reusable, artificial intelligence (AI) software system designed to assist spacecraft, life support systems, chemical plants, or other complex systems by operating with minimal human supervision, even in the face of hardware failures or unexpected events. The software diagnoses the current state of the spacecraft or other system, and recommends commands or repair actions that will allow the system to continue operation. Livingstone2 is an enhancement of the Livingstone diagnosis system that was flight-tested onboard the Deep Space One spacecraft in 1999. This version tracks multiple diagnostic hypotheses, rather than just a single hypothesis as in the previous version. It is also able to revise diagnostic decisions made in the past when additional observations become available. In such cases, Livingstone might arrive at an incorrect hypothesis. Re-architecting and re-implementing the system in C++ has increased performance. Usability has been improved by creating a set of development tools that is closely integrated with the Livingstone2 engine. In addition to the core diagnosis engine, Livingstone2 includes a compiler that translates diagnostic models written in a Java-like language into Livingstone2's language, and a broad set of graphical tools for model development.

Kurien, James↗

Personnel Data Analysis and Retrieval of Phase 1 Move To LC-39 Area

As a technology major from Jackson State University (JSU) I was called in as a summer intern at Kennedy Space Center (KSC) to work in the NASA Engineering, Control and Data Systems (NE-C) Division supporting the Spaceport Command and Control System (SCCS) at the Space Station Processing Facility (SSPF). I was given a two-part project; the first consisted of lending support relocating SCCS Computer Equipment and Project Personnel to the Launch Control Center (LCC). This task involved me using a Microsoft Office data processing tool to assist with the analysis and information management of logistics worth millions of dollars. With the assistance of two other interns, I was responsible for collecting data on equipment used, on a daily basis, by over 200 KSC employees. The many network servers, enterprise switches, desktop computers, and fiber optics had to be handled in an equally prompt and precise manner in order to ensure a minimal amount of equipment down time; which is critical in ensuring a properly secured networking environment. The second part of my project was to assist KSC in developing a more cost effective way of maintaining and taking full advantage of the functionality of some new kiosk units. Since KSC currently has no expert on the servicing and maintenance of the units, I, as a computer technology major, was given the opportunity to assess the hardware and software of the machines. The goal was to learn to establish a secure and remote environment for the kiosks; a goal highly valuing convenience by preserving valuable man-hours saved by not having to travel to each individual kiosk location. In addition, I was to leave a clear and precise plan for future users and administrators of the devices to follow.

Davis, Derrick D.↗

U.S. Coast Guard Boat Recovery Simulation at the NASA Ames Vertical Motion Simulator

The U.S. Coast Guard routinely uses the Over-The-Horizon (OTH-IV), a cutter deployed, rigid-hulled inflatable boat for rescue and law enforcement operations. The term "cutter" refers to a Coast Guard vessel 65 feet in length or greater with accommodations for crew to live aboard and the ability to deploy smaller boats including the OTH-IV. A deployment method employed by some cutter class vessels is a davit crane system and specialized hook mechanism to connect the smaller boat. The launch and recovery operation requires several crewmembers, where one is tasked with releasing and connecting the hook to the small boat. Manipulating the hook can pose a risk to the crewmember depending on sea conditions combined with fatigue level or task expertise. Equipment and crewmembers are tested extensively due to the inherent risk of the task, but the sea conditions cannot be controlled. To address the sea condition variable, the U.S. Coast Guard and NASA leveraged the Vertical Motion Simulator (VMS) as a platform to test new equipment or train crewmembers in varying sea conditions. With 6 degrees of freedom and a vertical displacement of +/- 22ft, the VMS is capable of simulating conditions up to sea-state 5. The proof of concept experiment took place in September 2018 and demonstrated that the VMS can accurately simulate varying sea-states, collect performance data, and design a reliable and safe system for participants. The U.S. Coast Guard provided boat displacement data from the Large Amplitude Motion Program (LAMP). The program generates multi-directional waves with a cosine squared spreading function which produced a time history response of displacement data (surge, sway, heave, roll, pitch, yaw) of the OTH-IV's center of gravity (C.G). The displacement data was differentiated into acceleration evaluated at the crewmember's position at the front (bow) of the boat. Those accelerations were transformed to the VMS coordinate system and used as command inputs to the motion system's washout filters. The VMS uses Interchangeable Cabs (ICab) to perform flight simulations on a variety of aircraft or spacecraft configurations. An ICab typically contains seats, restraints, pilot controls, instrument panel, and out-the-window projectors all enclosed in a familiar cockpit configuration. To replicate the launch and recovery of a small boat, all the conventional features of a flight simulator and canopy were removed to be replaced with a to-scale OTH-IV bow mockup. The bow section was constructed from aluminum, and a connection point known as the davit ring. Additionally, a hook replica was suspended by a cable from the ceiling as if it were hanging from a davit crane aboard a cutter vessel. The last step was providing an auxiliary control to close the distance between suspended hook and the davit ring on the bow mockup. Without control the boat would simulate the wave motion, but with no guarantee that the crewmember will be in reach of the hook. Since the wave motion was repeatable, an additional acceleration command sent to the washout filters to move the simulator in the surge, sway, and heave directions, independently. The commands were rate limited such that the additional movement was not detectable with respect to the wave motion. The results showed that for each wave profile, a unique set of acceleration commands provided opportunities for crewmembers to gain control of the hook and connect it to the davit ring.

Riccobono, Nicholas S.↗

Support for User Interfaces for Distributed Systems

An extensible Java(TradeMark) software framework supports the construction and operation of graphical user interfaces (GUIs) for distributed computing systems typified by ground control systems that send commands to, and receive telemetric data from, spacecraft. Heretofore, such GUIs have been custom built for each new system at considerable expense. In contrast, the present framework affords generic capabilities that can be shared by different distributed systems. Dynamic class loading, reflection, and other run-time capabilities of the Java language and JavaBeans component architecture enable the creation of a GUI for each new distributed computing system with a minimum of custom effort. By use of this framework, GUI components in control panels and menus can send commands to a particular distributed system with a minimum of system-specific code. The framework receives, decodes, processes, and displays telemetry data; custom telemetry data handling can be added for a particular system. The framework supports saving and later restoration of users configurations of control panels and telemetry displays with a minimum of effort in writing system-specific code. GUIs constructed within this framework can be deployed in any operating system with a Java run-time environment, without recompilation or code changes.

Eychaner, Glenn↗

Reaction control system helium pressure regulator filter failure

The failure analysis of the command module reaction control system helium pressure regulators revealed that the filter element end caps were bulged by the helium pressure surge during activation. Some end caps may bulge and also some wire separation may occur during command module reaction control system activations; however, system performance should not be affected. The reaction control system design is acceptable and no change in hardware, system, or activation procedures is required.

Source record↗

OMV: A simplified mathematical model of the orbital maneuvering vehicle

A model of the orbital maneuvering vehicle (OMV) is presented which contains several simplications. A set of hand controller signals may be used to control the motion of the OMV. Model verification is carried out using a sequence of tests. The dynamic variables generated by the model are compared, whenever possible, with the corresponding analytical variables. The results of the tests show conclusively that the present model is behaving correctly. Further, this model interfaces properly with the state vector transformation module (SVX) developed previously. Correct command sentence sequences are generated by the OMV and and SVX system, and these command sequences can be used to drive the flat floor simulation system at MSFC.

Teoh, W.↗

Framework for Development of Object-Oriented Software

The Real-Time Control (RTC) Application Framework is a high-level software framework written in C++ that supports the rapid design and implementation of object-oriented application programs. This framework provides built-in functionality that solves common software development problems within distributed client-server, multi-threaded, and embedded programming environments. When using the RTC Framework to develop software for a specific domain, designers and implementers can focus entirely on the details of the domain-specific software rather than on creating custom solutions, utilities, and frameworks for the complexities of the programming environment. The RTC Framework was originally developed as part of a Space Shuttle Launch Processing System (LPS) replacement project called Checkout and Launch Control System (CLCS). As a result of the framework s development, CLCS software development time was reduced by 66 percent. The framework is generic enough for developing applications outside of the launch-processing system domain. Other applicable high-level domains include command and control systems and simulation/ training systems.

Perez-Poveda, Gus↗

Increasing Flight Software Reuse with OpenSatKit

In January 2015 the NASA Goddard Space Flight Center (GSFC) released the Core Flight System (cFS) as open source under the NASA Open Source Agreement (NOSA) license. The cFS is based on flight software (FSW) developed for 12 spacecraft spanning nearly two decades of effort and it can provide about a third of the FSW functionality for a low-earth orbiting scientific spacecraft. The cFS is a FSW framework that is portable, configurable, and extendable using a product line deployment model. However, the components are maintained separately so the user must configure, integrate, and deploy them as a cohesive functional system. This can be very challenging especially for organizations such as universities building cubesats that have minimal experience developing FSW. Supporting universities was one of the primary motivators for releasing the cFS under NOSA. This paper describes the OpenSatKit that was developed to address the cFS deployment challenges and to serve as a cFS training platform for new users. It provides a fully functional out-of-the box software system that includes NASA's cFS, Ball Aerospace's command and control system COSMOS, and a NASA dynamic simulator called 42. The kit is freely available since all of the components have been released as open source. The kit runs on a Linux platform, includes 8 cFS applications, several kit-specific applications, and built in demos illustrating how to use key application features. It also includes the software necessary to port the cFS to a Raspberry Pi and instructions for configuring COSMOS to communicate with the target. All of the demos and test scripts can be rerun unchanged with the cFS running on the Raspberry Pi. The cFS uses a 3-tiered layered architecture including a platform abstraction layer, a Core Flight Executive (cFE) middle layer, and an application layer. Similar to smart phones, the cFS application layer is the key architectural feature for users to extend the FSW functionality to meet their mission-specific requirements. The platform abstraction layer and the cFE layers go a step further than smart phones by providing a platform-agnostic Application Programmer Interface (API) that allows applications to run unchanged on different platforms. OpenSatKit can serve two significant architectural roles that will further help the adoption of the cFS and help create a community of users that can share assets. First, the kit is being enhanced to automate the integration of applications with the goal of creating a virtual cFS "App Store".. Second, a platform certification test suite can be developed that would allow users to verify the port of the cFS to a new platform. This paper will describe the current state of these efforts and future plans.

Computer Programming and Software↗

Mission-centric cyber security assessment of critical systems

We present a novel model-based, mission-centric approach to perform cyber security assessments for evaluating the impact of low-level cyber events on high-level mission objectives.We demonstrate the benefits of our approach using a system model and attack trees specific to the command-and-control system of a spacecraft. Specifically, we demonstrate how our approach enables a decision-maker to assess the security posture of the system, identify necessary mitigations and prioritize their deployment.

Tan, Kymie↗

A Work Station For Control Of Changing Systems

Touch screen and microcomputer enable flexible control of complicated systems. Computer work station equipped to produce graphical displays used as command panel and status indicator for command-and-control system. Operator uses images of control buttons displayed on touch screen to send prestored commands. Use of prestored library of commands reduces incidence of errors. If necessary, operator uses conventional keyboard to enter commands in real time to handle unforeseeable situations.

Mandl, Daniel J.↗

Spacelab's interface to payload experiments

The Spacelab Payload Standard Modular Electronics (SPSME) program has been designed to provide a standardized set of space-qualified low-power electronic modules from which an experimenter may economically implement a command and data management system. SPSME is based on the Computer Automated Measurement and Control (CAMAC) interface standards. To the system of CAMAC, SPSME adds Spacelab interface modules, a flight qualified system crate, and an efficient light-weight power supply to produce a system compatible with the Spacelab environments, the Spacelab Command and Data Management System interface, and any experiment.

Golemon, W. F.↗

SCL: An off-the-shelf system for spacecraft control

In this age of shrinking military, civil, and commercial space budgets, an off-the-shelf solution is needed to provide a multimission approach to spacecraft control. A standard operational interface which can be applied to multiple spacecraft allows a common approach to ground and space operations. A trend for many space programs has been to reduce operational staff by applying autonomy to the spacecraft and to the ground stations. The Spacecraft Command Language (SCL) system developed by Interface and Control Systems, Inc. (ICS) provides an off-the-shelf solution for spacecraft operations. The SCL system is designed to provide a hyper-scripting interface which remains standard from program to program. The spacecraft and ground station hardware specifics are isolated to provide the maximum amount of portability from system to system. Uplink and downlink interfaces are also isolated to allow the system to perform independent of the communications protocols chosen. The SCL system can be used for both the ground stations and the spacecraft, or as a value added package for existing ground station environments. The SCL system provides an expanded stored commanding capability as well as a rule-based expert system on-board. The expert system allows reactive control on-board the spacecraft for functions such as electrical power systems (EPS), thermal control, etc. which have traditionally been performed on the ground. The SCL rule and scripting capability share a common syntax allowing control of scripts from rules and rules from scripts. Rather than telemeter over sampled data to the ground, the SCL system maintains a database on-board which is available for interrogation by the scripts and rules. The SCL knowledge base is constructed on the ground and uploaded to the spacecraft. The SCL system follows an open-systems approach allowing other tasks to communicate with SCL on the ground and in space. The SCL system was used on the Clementine program (launched January 25, 1994) and is required to have bidirectional communications with the guidance, navigation, and control (GNC) algorithms which were written as another task. Sequencing of the spacecraft maneuvers are handled by SCL, but the low-level thruster pulse commands are handled by the GNC software. Attitude information is reported back as telemetry, allowing the SCL expert system to inference on the changing data. The Clementine SCL flight software was largely reused from another Naval Center for Space Technology (NCST) satellite program. This paper details the SCL architecture and how an off-the-shelf solution makes sense for multimission spacecraft programs. The Clementine mission will be used as a case study in the application of the SCL to a 'fast track' program. The benefits of such a system in a 'better, cheaper, faster' climate will be discussed.

Buckley, Brian↗

A transportable system for management and exchange of programs and other text

A system is presented for exchanging information on tape, that allows information about the data to be included with the data. The system is designed for portability, but requires a few simple machine dependent modules. These modules are available for a variety of machines, and a bootstrapping procedure is provided. The system allows content selected reading of the tape, and a simple text editing facility is provided. Although the system recognizes 30 commands, information may be extracted from the tape by using as few as three commands. In addition to its use for information exchange, the system is expected to find use in maintaining large libraries of text.

Snyder, W. V.↗

[A Handling Qualities Metric for Damaged Aircraft]

In recent flight tests of F-15 Intelligent Flight Control System (IFCS), software simulated aircraft control surface failures were inserted to evaluate the IFCS adaptive systems. The failure commanded the left stabilator to a fixed position. The adaptive system uses a neural network that is designed to change control law gains, in the event of damage (real or simulated), that allows the aircraft to fly as it had before the damage. The performance of the adaptive system was assessed in terms of its ability to re-establish good onboard model tracking and its ability to decouple roll and pitch response.

Cogan, Bruce↗

Increasing Flight Software Reuse with OpenSatKit

In January 2015 the NASA Goddard Space Flight Center (GSFC) released the Core Flight System (cFS) as open source under the NASA Open Source Agreement (NOSA) license. The cFS is based on flight software (FSW) developed for 12 spacecraft spanning nearly two decades of effort and it can provide about a third of the FSW functionality for a low-earth orbiting scientific spacecraft. The cFS is a FSW framework that is portable, configurable, and extendable using a product line deployment model. However, the components are maintained separately so the user must configure, integrate, and deploy them as a cohesive functional system. This can be very challenging especially for organizations such as universities building cubesats that have minimal experience developing FSW. Supporting universities was one of the primary motivators for releasing the cFS under NOSA. This paper describes the OpenSatKit that was developed to address the cFS deployment challenges and to serve as a cFS training platform for new users. It provides a fully functional out-of-the box software system that includes NASA's cFS, Ball Aerospaceâ€"TM"s command and control system COSMOS, and a NASA dynamic simulator called 42. The kit is freely available since all of the components have been released as open source. The kit runs on a Linux platform, includes 8 cFS applications, several kit-specific applications, and built in demos illustrating how to use key application features. It also includes the software necessary to port the cFS to a Raspberry Pi and instructions for configuring COSMOS to communicate with the target. All of the demos and test scripts can be rerun unchanged with the cFS running on the Raspberry Pi. The cFS uses a 3-tiered layered architecture including a platform abstraction layer, a Core Flight Executive (cFE) middle layer, and an application layer. Similar to smart phones, the cFS application layer is the key architectural feature for userâ€"TM"s to extend the FSW functionality to meet their mission-specific requirements. The platform abstraction layer and the cFE layers go a step further than smart phones by providing a platform-agnostic Application Programmer Interface (API) that allows applications to run unchanged on different platforms. OpenSatKit can serve two significant architectural roles that will further help the adoption of the cFS and help create a community of users that can share assets. First, the kit is being enhanced to automate the integration of applications with the goal of creating a virtual cFS 'App Store'. Second, a platform certification test suite can be developed that would allow users to verify the port of the cFS to a new platform. This paper will describe the current state of these efforts and future plans.

McComas, David↗

Apollo 15 mission report. Supplement 2: Service propulsion system final flight evaluation

The command and service module 112 service propulsion system performance for the Apollo 15 mission was evaluated and found to be satisfactory. The following items were considered: (1) the steady-state performance as determined from analysis of the third and eight burns; (2) techniques, problems, and assumptions; (3) flight analysis results as compared to the preflight predicted performance; (4) the propellant utilization and gaging system operation; (5) the pressurization system performance; (6) transient data; and (7) revision of estimated propellant consumption.

Smith, R. J.↗