SEARCH · Engineering Papers

Results for “mission 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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 631 records · Page 35

All sources NASA NTRS DOE OSTI

NASA NTRS2007

NASA's SDR Standard: Space Telecommunications Radio System

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG s SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA s current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Reinhart, Richard C.↗

NASA NTRS2006

Space Telecommunications Radio Architecture (STRS): Technical Overview

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG s SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA's current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Reinhart, Richard C.↗

NASA NTRS2011

Software Certification - Coding, Code, and Coders

We describe a certification approach for software development that has been adopted at our organization. JPL develops robotic spacecraft for the exploration of the solar system. The flight software that controls these spacecraft is considered to be mission critical. We argue that the goal of a software certification process cannot be the development of "perfect" software, i.e., software that can be formally proven to be correct under all imaginable and unimaginable circumstances. More realistically, the goal is to guarantee a software development process that is conducted by knowledgeable engineers, who follow generally accepted procedures to control known risks, while meeting agreed upon standards of workmanship. We target three specific issues that must be addressed in such a certification procedure: the coding process, the code that is developed, and the skills of the coders. The coding process is driven by standards (e.g., a coding standard) and tools. The code is mechanically checked against the standard with the help of state-of-the-art static source code analyzers. The coders, finally, are certified in on-site training courses that include formal exams.

training↗

NASA NTRS2017

Environmental Control System Software & Hardware Development

ECS hardware: (1) Provides controlled purge to SLS Rocket and Orion spacecraft. (2) Provide mission-focused engineering products and services. ECS software: (1) NASA requires Compact Unique Identifiers (CUIs); fixed-length identifier used to identify information items. (2) CUI structure; composed of nine semantic fields that aid the user in recognizing its purpose.

student↗

NASA NTRS1974

Simulation verification techniques study. Subsystem simulation validation techniques

Techniques for validation of software modules which simulate spacecraft onboard systems are discussed. An overview of the simulation software hierarchy for a shuttle mission simulator is provided. A set of guidelines for the identification of subsystem/module performance parameters and critical performance parameters are presented. Various sources of reference data to serve as standards of performance for simulation validation are identified. Environment, crew station, vehicle configuration, and vehicle dynamics simulation software are briefly discussed from the point of view of their interfaces with subsystem simulation modules. A detailed presentation of results in the area of vehicle subsystems simulation modules is included. A list of references, conclusions and recommendations are also given.

Duncan, L. M.↗

NASA NTRS2010

Reinventing User Applications for Mission Control

In 2006, NASA Ames Research Center's (ARC) Intelligent Systems Division, and NASA Johnson Space Centers (JSC) Mission Operations Directorate (MOD) began a collaboration to move user applications for JSC's mission control center to a new software architecture, intended to replace the existing user applications being used for the Space Shuttle and the International Space Station. It must also carry NASA/JSC mission operations forward to the future, meeting the needs for NASA's exploration programs beyond low Earth orbit. Key requirements for the new architecture, called Mission Control Technologies (MCT) are that end users must be able to compose and build their own software displays without the need for programming, or direct support and approval from a platform services organization. Developers must be able to build MCT components using industry standard languages and tools. Each component of MCT must be interoperable with other components, regardless of what organization develops them. For platform service providers and MOD management, MCT must be cost effective, maintainable and evolvable. MCT software is built from components that are presented to users as composable user objects. A user object is an entity that represents a domain object such as a telemetry point, a command, a timeline, an activity, or a step in a procedure. User objects may be composed and reused, for example a telemetry point may be used in a traditional monitoring display, and that same telemetry user object may be composed into a procedure step. In either display, that same telemetry point may be shown in different views, such as a plot, an alpha numeric, or a meta-data view and those views may be changed live and in place. MCT presents users with a single unified user environment that contains all the objects required to perform applicable flight controller tasks, thus users do not have to use multiple applications, the traditional boundaries that exist between multiple heterogeneous applications disappear, leaving open the possibility of new operations concepts that are not constrained by the traditional applications paradigm.

Trimble, Jay Phillip↗

NASA NTRS1997

Mars Pathfinder Atmospheric Entry Navigation Operations

On July 4, 1997, after traveling close to 500 million km, the Pathfinder spacecraft successfully completed entry, descent, and landing, coming to rest on the surface of Mars just 27 km from its target point. In the present paper, the atmospheric entry and approach navigation activities required in support of this mission are discussed. In particular, the flight software parameter update and landing site prediction analyses performed by the Pathfinder operations navigation team are described. A suite of simulation tools developed during Pathfinder's design cycle, but extendible to Pathfinder operations, are also presented. Data regarding the accuracy of the primary parachute deployment algorithm is extracted from the Pathfinder flight data, demonstrating that this algorithm performed as predicted. The increased probability of mission success through the software parameter update process is discussed. This paper also demonstrates the importance of modeling atmospheric flight uncertainties in the estimation of an accurate landing site. With these atmospheric effects included, the final landed ellipse prediction differs from the post-flight determined landing site by less then 0.5 km in downtrack.

Braun, R. D.↗

NASA NTRS1993

The Advanced Technology Operations System: ATOS

Mission control systems supporting new space missions face ever-increasing requirements in terms of functionality, performance, reliability and efficiency. Modern data processing technology is providing the means to meet these requirements in new systems under development. During the past few years the European Space Operations Centre (ESOC) of the European Space Agency (ESA) has carried out a number of projects to demonstrate the feasibility of using advanced software technology, in particular, knowledge based systems, to support mission operations. A number of advances must be achieved before these techniques can be moved towards operational use in future missions, namely, integration of the applications into a single system framework and generalization of the applications so that they are mission independent. In order to achieve this goal, ESA initiated the Advanced Technology Operations System (ATOS) program, which will develop the infrastructure to support advanced software technology in mission operations, and provide applications modules to initially support: Mission Preparation, Mission Planning, Computer Assisted Operations, and Advanced Training. The first phase of the ATOS program is tasked with the goal of designing and prototyping the necessary system infrastructure to support the rest of the program. The major components of the ATOS architecture is presented. This architecture relies on the concept of a Mission Information Base (MIB) as the repository for all information and knowledge which will be used by the advanced application modules in future mission control systems. The MIB is being designed to exploit the latest in database and knowledge representation technology in an open and distributed system. In conclusion the technological and implementation challenges expected to be encountered, as well as the future plans and time scale of the project, are presented.

Kaufeler, J.-F.↗

NASA NTRS1991

Simulation models for autonomous rendezvous and capture

Autonomous rendezvous and capture (AR&C) is a critical space technology with significant application to a variety of missions. Martin Marietta Astronautics Group (MMAG) has been developing AR&C technical capability in support of several recent NASA contracts. The use of AR&C for the Mars Rover/Sample Return (MRSR) mission was studied through a contract with JSC. Incorporation of AR&C in the Space Transportation Vehicle (STV) lunar mission was studied through a contract with MSFC. The MMAG has also been developing AR&C simulation capability under independent research and development studies. Simulation development was driven by two goals: comprehensive software simulation of the autonomous rendezvous and capture mission from launch to final capture; and integration of the overall software and hardware simulation to support an AR&C flight demonstration. This presentation will highlight the AR&C software simulation tools and analyze results from their application to the STV lunar mission. Plans for an integrated software and hardware simulation will also be summarized.

Smith, Nick G.↗

NASA NTRS2003

Software for Tracking Costs of Mars Projects

The Mars Cost Tracking Model is a computer program that administers a system set up for tracking the costs of future NASA projects that pertain to Mars. Previously, no such tracking system existed, and documentation was written in a variety of formats and scattered in various places. It was difficult to justify costs or even track the history of costs of a spacecraft mission to Mars. The present software enables users to maintain all cost-model definitions, documentation, and justifications of cost estimates in one computer system that is accessible via the Internet. The software provides sign-off safeguards to ensure the reliability of information entered into the system. This system may eventually be used to track the costs of projects other than only those that pertain to Mars.

Wong, Alvin↗

NASA NTRS2001

Making Sense of Remotely Sensed Ultra-Spectral Infrared Data

NASA's Jet Propulsion Laboratory (JPL), Pasadena, California, Earth Observing System (EOS) programs, the Deep Space Network (DSN), and various Department of Defense (DOD) technology demonstration programs, combined their technical expertise to develop SEASCRAPE, a software program that obtains data when thermal infrared radiation passes through the Earth's atmosphere and reaches a sensor. Licensed by the California Institute of Technology (Caltech), SEASCRAPE automatically inverts complex infrared data and makes it possible to obtain estimates of the state of the atmosphere along the ray path. Former JPL staff members created a small entrepreneurial firm, Remote Sensing Analysis Systems, Inc., of Altadena, California, to commercialize the product. The founders believed that a commercial version of the software was needed for future U.S. government missions and the commercial monitoring of pollution. With the inversion capability of this software and remote sensing instrumentation, it is possible to monitor pollution sources from safe and secure distances on a noninterfering, noncooperative basis. The software, now know as SEASCRAPE_Plus, allows the user to determine the presence of pollution products, their location and their abundance along the ray path. The technology has been cleared by the Department of Commerce for export, and is currently used by numerous research and engineering organizations around the world.

Source record↗

NASA NTRS1991

Magellan mission planning and orbital operations

The goal of NASA's Magellan mission is to understand the geological and geophysical processes that have shaped the planet Venus. Through synthetic aperture radar, radiometric, altimetric, and gravity measurements, the scientific community hopes to improve its knowledge of the planet's topography and internal mass distribution. This paper provides an overview of the Magellan mission; describes the spacecraft sequence software design, development, and test; addresses the nominal operational flow of stored sequence design and generation; briefly describes the ground processing of engineering telemetry and imaging data; and then summarizes the Magellan operational experience with non-routine behavior of the spacecraft during the cruise and mapping portions of the prime mission.

Venus↗

NASA NTRS2004

The HiVy tool set

Our aim is to validate mission-specific components of spacecraft flight software designs that are specified using state-charts and translated automatically to the final flight code for the mission. We established an automatic translation tool set from state-charts to SPIN for the validation of such mission-specific components.

translation↗

NASA NTRS1985

FORTH as the basis for an integrated operations environment for a Space Shuttle scientific experiment

Over a period of three years, a FORTH-based system was developed by JPL for the operations of a major scientific instrument onboard the Space Shuttle. The software had to meet a very demanding operations environment where the interactiveness of the software was not merely desirable but essential to the success of the mission. Forth was chosen for its capability of integrating divergent software needs into an interactive package. The mission flown in October 1984 was beset with numerous hardware failures and challenged the capability of the system to its fullest.

Harris, Henry M.↗

NASA NTRS1989

Prototype software reuse environment at Goddard Space Flight Center

The Goddard Space Flight Center (GSFC) work is organized into four phases and includes participation by a contractor, CTA, Inc. The first phase was an automation study, which began with a comprehensive survey of software development automation technologies. Eight technical areas were analyzed for goals, current capabilities, and obstacles. The study documented current software development practice in GSFC Mission Operations and Data Systems Directorate, and presented short- and long-term recommendations that included focus on reuse and object-oriented development. The second phase, which has been completed, developed a prototype reuse environment with tools supporting object-oriented requirements analysis and design. This phase addressed the operational concept of software reuse, i.e., it attempted to understand how software can be reused. This environment has two semantic networks: object and keywords, and includes automated search, interactive browsing and a graphical display of database contents. Phase 3 was a domain analysis of Payload Operations Control Center (POCC) software. The goal in this phase was to create an initial repository of reusable components and techniques. Seven existing Operations Control Centers at GSFC were studied, but the domain analysis proved to be very slow. A lesson learned from this was that senior people who understand the environment and the functionality of the area are needed to perform successful domain analyses.

Truszkowski, Walt↗

NASA NTRS2019

CHANGO: A Software Tool for Boost Stage Guidance of the Space Launch System Exploration Mission 1

The Day of Launch Initiation Load Update (DOLILU) System is the means by which the Space Launch System (SLS) Vehicle trajectory is designed, verified, and uploaded on the Day of Launch (DOL) in order to ensure a safe flight. Launch vehicles are designed to fly down a narrow angle of attack and sideslip angle corridor in order to keep them within structural load limits. The angle of attack and sideslip angle response to the launch vehicle experiences can vary significantly based upon the winds experienced on the DOL. SLS Boost Stage flight employs an open-loop guidance scheme through Solid Rocket Booster (SRB) separation. In the SLS open-loop scheme, the vehicle will fly a prescribed set of attitudes as a function of the change in altitude since launch. This set of reference attitude values and corresponding altitude reference independent values are designed with ground software using winds measured on the DOL with the goal of minimizing angle of attack and sideslip angle, thereby minimizing related ascent integrated vehicle structural loads. The table of Boost Stage attitude commands as a function of altitude gained since launch is called the chi table. A software tool called CHANGO (Chi Angle Optimizer) designs the Boost Stage chi table which is uploaded to the vehicle’s flight computer and used during ascent by the flight software (FSW). The wind and atmospheric conditions are measured prior to launch and pre-processed to become input to the CHANGO software along with a set of parameters developed in advance of the DOL. CHANGO’s target set consists of the heading and altitude rate at SRB separation determined well before launch by the Program to Optimize Simulated Trajectories (POST). CHANGO consists of a simplified three degree-of-freedom (3-DOF) simulation representing the SLS launch configuration. In general, the launch azimuth is strongly correlated with the heading at SRB separation, and the initial pitchover rate is strongly correlated with the altitude rate at SRB separation. CHANGO uses an adaptation of Powell’s method to vary the initial pitchover rate and launch azimuth to solve a 2-dimentional minimization problem. CHANGO’s trajectory simulation is phase-based, with flight events separating the phases. Each flight phase has different attitude alignment logic. CHANGO’s 3-DOF simulation starts when the vehicle’s thrust-to-weight ratio equals one, and ends at a pre-calculated SRB separation time.

Ahmad, Naeem↗

NASA NTRS2014

Preparing GMAT for Operational Maneuver Planning of the Advanced Composition Explorer (ACE)

The General Mission Analysis Tool (GMAT) is an open-source space mission design, analysis and trajectory optimization tool. GMAT is developed by a team of NASA, private industry, public and private contributors. GMAT is designed to model, optimize and estimate spacecraft trajectories in flight regimes ranging from low Earth orbit to lunar applications, interplanetary trajectories and other deep space missions. GMAT has also been flight qualified to support operational maneuver planning for the Advanced Composition Explorer (ACE) mission. ACE was launched in August, 1997 and is orbiting the Sun-Earth L1 libration point. The primary science objective of ACE is to study the composition of both the solar wind and the galactic cosmic rays. Operational orbit determination, maneuver operations and product generation for ACE are conducted by NASA Goddard Space Flight Center (GSFC) Flight Dynamics Facility (FDF). This paper discusses the entire engineering lifecycle and major operational certification milestones that GMAT successfully completed to obtain operational certification for the ACE mission. Operational certification milestones such as gathering of the requirements for ACE operational maneuver planning, gap analysis, test plans and procedures development, system design, pre-shadow operations, training to FDF ACE maneuver planners, shadow operations, Test Readiness Review (TRR) and finally Operational Readiness Review (ORR) are discussed. These efforts have demonstrated that GMAT is flight quality software ready to support ACE mission operations in the FDF.

Trajectory analysis↗

NASA NTRS2019

Preparing General Mission Analysis Tool for Operational Maneuver Planning of the Advanced Composition Explorer Mission

mission design↗