Search NASA⌕ Search

SEARCH · Search NASA

Results for “launch software”

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 379 records · Page 21

Constellation Program Electrical Ground Support Equipment Research and Development

At the Kennedy Space Center, I engaged in the research and development of electrical ground support equipment for NASA's Constellation Program. Timing characteristics playa crucial role in ground support communications. Latency and jitter are two problems that must be understood so that communications are timely and consistent within the Kennedy Ground Control System (KGCS). I conducted latency and jitter tests using Alien-Bradley programmable logic controllers (PLCs) so that these two intrinsic network properties can be reduced. Time stamping and clock synchronization also play significant roles in launch processing and operations. Using RSLogix 5000 project files and Wireshark network protocol analyzing software, I verified master/slave PLC Ethernet module clock synchronization, master/slave IEEE 1588 communications, and time stamping capabilities. All of the timing and synchronization test results are useful in assessing the current KGCS operational level and determining improvements for the future.

McCoy, Keegan S.↗

Operational Analysis in the Launch Environment

The launch environment is a challenging regime to work due to changing system dynamics, changing environmental loading, joint compression loads that cannot be easily applied on the ground, and control effects. Operational testing is one of the few feasible approaches to capture system level dynamics since ground testing cannot reproduce all of these conditions easily. However, the most successful applications of Operational Modal Testing involve systems with good stationarity and long data acquisition times. This paper covers an ongoing effort to understand the launch environment and the utility of current operational modal tools. This work is expected to produce a collection of operational tools that can be applied to non-stationary launch environment, experience dealing with launch data, and an expanding database of flight parameters such as damping. This paper reports on recent efforts to build a software framework for the data processing utilizing existing and specialty tools; understand the limits of current tools; assess a wider variety of current tools; and expand the experience with additional datasets as well as to begin to address issues raised in earlier launch analysis studies.

James, George↗

Demystifying Kepler Data: A Primer for Systematic Artifact Mitigation

The Kepler spacecraft has collected data of high photometric precision and cadence almost continuously since operations began on 2009 May 2. Primarily designed to detect planetary transits and asteroseismological signals from solar-like stars, Kepler has provided high quality data for many areas of investigation. Unconditioned simple aperture time-series photometry are however affected by systematic structure. Examples of these systematics are differential velocity aberration, thermal gradients across the spacecraft, and pointing variations. While exhibiting some impact on Kepler's primary science, these systematics can critically handicap potentially ground-breaking scientific gains in other astrophysical areas, especially over long timescales greater than 10 days. As the data archive grows to provide light curves for 10(exp 5) stars of many years in length, Kepler will only fulfill its broad potential for stellar astrophysics if these systematics are understood and mitigated. Post-launch developments in the Kepler archive, data reduction pipeline and open source data analysis software have occurred to remove or reduce systematic artifacts. This paper provides a conceptual primer for users of the Kepler data archive to understand and recognize systematic artifacts within light curves and some methods for their removal. Specific examples of artifact mitigation are provided using data available within the archive. Through the methods defined here, the Kepler community will find a road map to maximizing the quality and employment of the Kepler legacy archive.

Kinemuchi, K.↗

Launch Vehicle Manual Steering with Adaptive Augmenting Control In-flight Evaluations Using a Piloted Aircraft

An adaptive augmenting control algorithm for the Space Launch System has been developed at the Marshall Space Flight Center as part of the launch vehicles baseline flight control system. A prototype version of the SLS flight control software was hosted on a piloted aircraft at the Armstrong Flight Research Center to demonstrate the adaptive controller on a full-scale realistic application in a relevant flight environment. Concerns regarding adverse interactions between the adaptive controller and a proposed manual steering mode were investigated by giving the pilot trajectory deviation cues and pitch rate command authority.

pilot ratings↗

Launch Vehicle Manual Steering with Adaptive Augmenting Control In-flight Evaluations of Adverse Interactions Using a Piloted Aircraft

An adaptive augmenting control algorithm for the Space Launch System has been developed at the Marshall Space Flight Center as part of the launch vehicles baseline flight control system. A prototype version of the SLS flight control software was hosted on a piloted aircraft at the Armstrong Flight Research Center to demonstrate the adaptive controller on a full-scale realistic application in a relevant flight environment. Concerns regarding adverse interactions between the adaptive controller and a proposed manual steering mode were investigated by giving the pilot trajectory deviation cues and pitch rate command authority. Two NASA research pilots flew a total of twenty five constant pitch-rate trajectories using a prototype manual steering mode with and without adaptive control.

manual steering mode↗

Survey of Verification and Validation Techniques for Small Satellite Software Development

The purpose of this paper is to provide an overview of the current trends and practices in small-satellite software verification and validation. This document is not intended to promote a specific software assurance method. Rather, it seeks to present an unbiased survey of software assurance methods used to verify and validate small satellite software and to make mention of the benefits and value of each approach. These methods include simulation and testing, verification and validation with model-based design, formal methods, and fault-tolerant software design with run-time monitoring. Although the literature reveals that simulation and testing has by far the longest legacy, model-based design methods are proving to be useful for software verification and validation. Some work in formal methods, though not widely used for any satellites, may offer new ways to improve small satellite software verification and validation. These methods need to be further advanced to deal with the state explosion problem and to make them more usable by small-satellite software engineers to be regularly applied to software verification. Last, it is explained how run-time monitoring, combined with fault-tolerant software design methods, provides an important means to detect and correct software errors that escape the verification process or those errors that are produced after launch through the effects of ionizing radiation.

Small Satellite Technology↗

CASIS Fact Sheet: Hardware and Facilities

Vencore is a proven information solutions, engineering, and analytics company that helps our customers solve their most complex challenges. For more than 40 years, we have designed, developed and delivered mission-critical solutions as our customers' trusted partner. The Engineering Services Contract, or ESC, provides engineering and design services to the NASA organizations engaged in development of new technologies at the Kennedy Space Center. Vencore is the ESC prime contractor, with teammates that include Stinger Ghaffarian Technologies, Sierra Lobo, Nelson Engineering, EASi, and Craig Technologies. The Vencore team designs and develops systems and equipment to be used for the processing of space launch vehicles, spacecraft, and payloads. We perform flight systems engineering for spaceflight hardware and software; develop technologies that serve NASA's mission requirements and operations needs for the future. Our Flight Payload Support (FPS) team at Kennedy Space Center (KSC) provides engineering, development, and certification services as well as payload integration and management services to NASA and commercial customers. Our main objective is to assist principal investigators (PIs) integrate their science experiments into payload hardware for research aboard the International Space Station (ISS), commercial spacecraft, suborbital vehicles, parabolic flight aircrafts, and ground-based studies. Vencore's FPS team is AS9100 certified and a recognized implementation partner for the Center for Advancement of Science in Space (CASIS

Solomon, Michael R.↗

Intelligent systems for KSC ground processing

The ground processing and launch of Shuttle vehicles and their payloads is the primary task of Kennedy Space Center. It is a process which is largely manual and contains little inherent automation. Business is conducted today much as it was during previous NASA programs such as Apollo. In light of new programs and decreasing budgets, NASA must find more cost effective ways in which to do business while retaining the quality and safety of activities. Advanced technologies including artificial intelligence could cut manpower and processing time. This paper is an overview of the research and development in Al technology at KSC with descriptions of the systems which have been implemented, as well as a few under development which are promising additions to ground processing software. Projects discussed cover many facets of ground processing activities, including computer sustaining engineering, subsystem monitor and diagnosis tools and launch team assistants. The deployed Al applications have proven an effectiveness which has helped to demonstrate the benefits of utilizing intelligent software in the ground processing task.

Heard, Astrid E.↗

Spaceport Command and Control System Automated Verification Software Development

For as long as we have walked the Earth, humans have always been explorers. We have visited our nearest celestial body and sent Voyager 1 beyond our solar system1 out into interstellar space. Now it is finally time for us to step beyond our home and onto another planet. The Spaceport Command and Control System (SCCS) is being developed along with the Space Launch System (SLS) to take us on a journey further than ever attempted. Within SCCS are separate subsystems and system level software, each of which have to be tested and verified. Testing is a long and tedious process, so automating it will be much more efficient and also helps to remove the possibility of human error from mission operations. I was part of a team of interns and full-time engineers who automated tests for the requirements on SCCS, and with that was able to help verify that the software systems are performing as expected.

Automation↗

An overview of software design languages

The nature and use of design languages and associated processors that are used in software development are reviewed with reference to development work on the Galileo spacecraft project, a Jupiter orbiter scheduled for launch in 1984. The major design steps are identified (functional design, architectural design, detailed design, coding, and testing), and the purpose, functions and the range of applications of design languages are examined. Then the general character of any design language is analyzed in terms of syntax and semantics. Finally, the differences and similarities between design languages are illustrated by examining two specific design languages: Software Design and Documentation language and Problem Statement Language/Problem Statement Analyzer.

Callender, E. D.↗

Ground System Milestones: 20 Years of Earth Observing Satellite Mission Operations

Aqua, Aura, and Terra are Earth observing satellites that serve in the Earth Observing System (EOS). Terra, the flagship mission of the EOS, was launched in 1998. Aqua was launched in 2002 and Aura was launched in 2004. Each spacecraft was designed for a 6 year lifespan. Currently, each spacecraft meets all mission and science requirements. As technology advances, the onboard hardware and software remain the same, however, our ground system progresses. In the past twenty years, many changes have taken place. Our goal is to describe the life of the ground system from launch, to present day, and touch on our future plans. The focus of our presentation will be how EOS has and continues to modernize our ground system for the future. We would like to share our experiences and give insight into the operational challenges of a 20 year old ground system. Our hope is for future mission operators and those maintaining potential age defying satellites to use our past experiences and lessons learned for future operational concepts.

Barrett, Grant↗

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.↗

Linking Satellites Via Earth "Hot Spots" and the Internet to Form Ad Hoc Constellations

As more assets are placed in orbit, opportunities emerge to combine various sets of satellites in temporary constellations to perform collaborative image collections. Often, new operations concepts for a satellite or set of satellites emerge after launch. To the degree with which new space assets can be inexpensively and rapidly integrated into temporary or "ad hoc" constellations, will determine whether these new ideas will be implemented or not. On the Earth Observing 1 (EO-1) satellite, a New Millennium Program mission, a number of experiments were conducted and are being conducted to demonstrate various aspects of an architecture that, when taken as a whole, will enable progressive mission autonomy. In particular, the target architecture will use adaptive ground antenna arrays to form, as close as possible, the equivalent of wireless access points for low earth orbiting satellites. Coupled with various ground and flight software and the Internet. the architecture enables progressive mission autonomy. Thus, new collaborative sensing techniques can be implemented post-launch. This paper will outline the overall operations concept and highlight details of both the research effort being conducted in <he area of adaptive antenna arrays and some of the related successful autonomy software that has been implemented using EO-1 and other operational satellites. Keywords: collaborative remote sensing smart antennas, adaptive antenna arrays, sensor webs. ad hoc constellations, mission autonomy and

Mandl, Dan↗

Shuttle avionics and the goal language including the impact of error detection and redundancy management

The relationship is examined between the space shuttle onboard avionics and the ground test computer language GOAL when used in the onboard computers. The study is aimed at providing system analysis support to the feasibility analysis of a GOAL to HAL translator, where HAL is the language used to program the onboard computers for flight. The subject is dealt with in three aspects. First, the system configuration at checkout, the general checkout and launch sequences, and the inventory of subsystems are described. Secondly, the hierarchic organization of onboard software and different ways of introducing GOAL-derived software onboard are described. Also the flow of commands and test data during checkout is diagrammed. Finally, possible impact of error detection and redundancy management on the GOAL language is discussed.

Flanders, J. H.↗

An application of the Multi-Purpose System Simulation /MPSS/ model to the Monitor and Control Display System /MACDS/ at the National Aeronautics and Space Administration /NASA/ Goddard Space Flight Center /GSFC/

The Multi-Purpose System Simulator (MPSS) model was used to investigate the current and projected performance of the Monitor and Control Display System (MACDS) at the Goddard Space Flight Center in processing and displaying launch data adequately. MACDS consists of two interconnected mini-computers with associated terminal input and display output equipment and a disk-stored data base. Three configurations of MACDS were evaluated via MPSS and their performances ascertained. First, the current version of MACDS was found inadequate to handle projected launch data loads because of unacceptable data backlogging. Second, the current MACDS hardware with enhanced software was capable of handling two times the anticipated data loads. Third, an up-graded hardware ensemble combined with the enhanced software was capable of handling four times the anticipated data loads.

Mill, F. W.↗

Reduction and scientific analysis of data from the charge-energy-mass (CHEM) spectrometer on the AMPTE/CCE spacecraft

The Charge-Energy-Mass (CHEM) spectrometer instrument on the AMPTE/Charge Composition Explorer (CCE) spacecraft is designed to measure the mass and charge-state abundance of magnetospheric and magnetosheath ions between 0.3 and 315 keV/e, an energy range that includes the bulk of the ring current and the dynamically important portion of the plasma sheet population. Continuing research is being conducted using the AMPTE mission data set, and in particular, that of the CHEM spectrometer which has operated flawlessly since launch and still provides excellent quality data. The requirted routine data processing and reduction, and software develpment continues to be performed. Scientific analysis of composition data in a number of magnetospheric regions including the ring current region, near-earth plasma sheet and subsolar magnetosheath continues to be undertaken. Correlative studies using data from the sister instrument SULEICA, which determines the mass and charge states of ions in the energy range of approximately 10 to 250 keV/e on the IRM, as well as other data from the CCE and IRM spacecraft, particularly in the upstream region and plasma sheet have also been undertaken.

Gloeckler, G.↗

Evolutionary space station fluids management strategies

Results are summarized for an 11-month study to define fluid storage and handling strategies and requirements for various specific mission case studies and their associated design impacts on the Space Station. There are a variety of fluid users which require a variety of fluids and use rates. Also, the cryogenic propellants required for NASA's STV, Planetary, and Code Z missions are enormous. The storage methods must accommodate fluids ranging from a high pressure gas or supercritical state fluid to a sub-cooled liquid (and superfluid helium). These requirements begin in the year 1994, reach a maximum of nearly 1800 metric tons in the year 2004, and trail off to the year 2018, as currently planned. It is conceivable that the cryogenic propellant needs for the STV and/or Lunar mission models will be met by LTCSF LH2/LO2 tanksets attached to the SS truss structure. Concepts and corresponding transfer and delivery operations have been presented for STV propellant provisioning from the SS. A growth orbit maneuvering vehicle (OMV) and associated servicing capability will be required to move tanksets from delivery launch vehicles to the SS or co-orbiting platforms. Also, appropriate changes to the software used for OMV operation are necessary to allow for the combined operation of the growth OMV. To support fluid management activities at the Space Station for the experimental payloads and propellant provisioning, there must be truss structure space allocated for fluid carriers and propellant tanksets, and substantial beam strengthening may be required. The Station must have two Mobile Remote Manipulator Systems (MRMS) and the growth OMV propellant handling operations for the STV at the SS. Propellant needs for the Planetary Initiatives and Code Z mission models will most likely be provided by co-orbiting propellant platform(s). Space Station impacts for Code Z mission fluid management activities will be minimal.

Source record↗

Architecture for Survivable Systems Processing (ASSP). Technology benefits for Open System Interconnects

The Architecture for Survivable Systems Processing (ASSP) program is a two phase program whose objective is the derivation, specification, development and validation of an open system architecture capable of supporting advanced processing needs of space, ground, and launch vehicle operations. The output of the first phase is a set of hardware and software standards and specifications defining this architecture at three levels. The second phase will validate these standards and develop the technology necessary to achieve strategic hardness, packaging density, throughput requirements, and interoperability/interchangeability.

Wood, Richard J.↗