Engineering Papers⌕ Search

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.

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

At least 469 records · Page 26

Mission planning for the Lidar in Space Technology Experiment

Developing a mission planning system for a Space Shuttle mission is a complex procedure. Several months of preparation are required to develop a plan that optimizes science return during the short operations time frame. Further complicating the scenario is the necessity to schedule around crew activities and other payloads which share Orbiter resources. SpaceTec, Inc. developed the mission planning system for the Lidar In Space Technology Experiment, or LITE, which flew on Space Shuttle mission STS-64 in September of 1994. SpaceTec used a combination of off-th-shelf and in-house developed software to analyze various mission scenarios both premission and real-time during the flight. From this analysis, SpaceTec developed a comprehensive mission plan that met the mission objectives.

Redifer, Matthew E.↗

Challenges of Developing New Classes of NASA Self-Managing Mission

NASA is proposing increasingly complex missions that will require a high degree of autonomy and autonomicity. These missions pose hereto unforeseen problems and raise issues that have not been well-addressed by the community. Assuring success of such missions will require new software development techniques and tools. This paper discusses some of the challenges that NASA and the rest of the software development community are facing in developing these ever-increasingly complex systems. We give an overview of a proposed NASA mission as well as techniques and tools that are being developed to address autonomic management and the complexity issues inherent in these missions.

Hinchey, M. G.↗

Architecture for Verifiable Software

Verifiable MDS Architecture (VMA) is a software architecture that facilitates the construction of highly verifiable flight software for NASA s Mission Data System (MDS), especially for smaller missions subject to cost constraints. More specifically, the purpose served by VMA is to facilitate aggressive verification and validation of flight software while imposing a minimum of constraints on overall functionality. VMA exploits the state-based architecture of the MDS and partitions verification issues into elements susceptible to independent verification and validation, in such a manner that scaling issues are minimized, so that relatively large software systems can be aggressively verified in a cost-effective manner.

Reinholtz, William↗

Multi-Mission Simulation and Visualization for Real-Time Telemetry Display, Playback and EDL Event Reconstruction

he Jet Propulsion Laboratory's Entry, Descent and Landing (EDL) Reconstruction Task has developed a software system that provides mission operations personnel and analysts with a real time telemetry-based live display, playback and post-EDL reconstruction capability that leverages the existing high-fidelity, physics-based simulation framework and modern game engine-derived 3D visualization system developed in the JPL Dynamics and Real Time Simulation (DARTS) Lab. Developed as a multi-mission solution, the EDL Telemetry Visualization (ETV) system has been used for a variety of projects including NASA's Mars Science Laboratory (MSL), NASA'S Low Density Supersonic Decelerator (LDSD) and JPL's MoonRise Lunar sample return proposal.

Entry, Descent and Landing (EDL) Reconstruction↗

Assessment Environment for Complex Systems Software Guide

This Software Guide (SG) describes the software developed to test the Assessment Environment for Complex Systems (AECS) by the West Virginia High Technology Consortium (WVHTC) Foundation's Mission Systems Group (MSG) for the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD). This software is referred to as the AECS Test Project throughout the remainder of this document. AECS provides a framework for developing, simulating, testing, and analyzing modern avionics systems within an Integrated Modular Avionics (IMA) architecture. The purpose of the AECS Test Project is twofold. First, it provides a means to test the AECS hardware and system developed by MSG. Second, it provides an example project upon which future AECS research may be based. This Software Guide fully describes building, installing, and executing the AECS Test Project as well as its architecture and design. The design of the AECS hardware is described in the AECS Hardware Guide. Instructions on how to configure, build and use the AECS are described in the User's Guide. Sample AECS software, developed by the WVHTC Foundation, is presented in the AECS Software Guide. The AECS Hardware Guide, AECS User's Guide, and AECS Software Guide are authored by MSG. The requirements set forth for AECS are presented in the Statement of Work for the Assessment Environment for Complex Systems authored by NASA Dryden Flight Research Center (DFRC). The intended audience for this document includes software engineers, hardware engineers, project managers, and quality assurance personnel from WVHTC Foundation (the suppliers of the software), NASA (the customer), and future researchers (users of the software). Readers are assumed to have general knowledge in the field of real-time, embedded computer software development.

tests↗

An Integrated Approach To Payload System Simulation

This paper describes a payload system simulation implemented at JPL as part of a comprehensive mission simulation facility. The flight software function includes communication with other process modules, instrument control, and data management. The payload system simulation software consists of: a camera subsystem, a virtual world, and a mission visualization toolset.

dynamics model photometric model geological model ↗

Science Benefits of Onboard Spacecraft Navigation

Primitive bodies (asteroids and comets), which have remained relatively unaltered since their formation, are important targets for scientific missions that seek to understand the evolution of the solar system. Often the first step is to fly by these bodies with robotic spacecraft. The key to maximizing data returns from these flybys is to determine the spacecraft trajectory relative to the target body-in short, navigate the spacecraft- with sufficient accuracy so that the target is guaranteed to be in the instruments' field of view. The most powerful navigation data in these scenarios are images taken by the spacecraft of the target against a known star field (onboard astrometry). Traditionally, the relative trajectory of the spacecraft must be estimated hours to days in advance using images collected by the spacecraft. This is because of (1)!the long round-trip light times between the spacecraft and the Earth and (2)!the time needed to downlink and process navigation data on the ground, make decisions based on the result, and build and uplink instrument pointing sequences from the results. The light time and processing time compromise navigation accuracy considerably, because there is not enough time to use more accurate data collected closer to the target-such data are more accurate because the angular capability of the onboard astrometry is essentially constant as the distance to the target decreases, resulting in better "plane-of- sky" knowledge of the target. Excellent examples of these timing limitations are high-speed comet encounters. Comets are difficult to observe up close; their orbits often limit scientists to brief, rapid flybys, and their coma further restricts viewers from seeing the nucleus in any detail, unless they can view the nucleus at close range. Comet nuclei details are typically discernable for much shorter durations than the roundtrip light time to Earth, so robotic spacecraft must be able to perform onboard navigation. This onboard navigation can be accomplished through a self- contained system that by eliminating light time restrictions dramatically improves the relative trajectory knowledge and control and subsequently increases the amount of quality data collected. Flybys are one-time events, so the system's underlying algorithms and software must be extremely robust. The autonomous software must also be able to cope with the unknown size, shape, and orientation of the previously unseen comet nucleus. Furthermore, algorithms must be reliable in the presence of imperfections and/or damage to onboard cameras accrued after many years of deep-space operations. The AutoNav operational flight software packages, developed by scientists at the Jet Propulsion Laboratory (JPL) under contract with NASA, meet all these requirements. They have been directly responsible for the successful encounters on all of NASA's close-up comet-imaging missions (see Figure !1). AutoNav is the only system to date that has autonomously tracked comet nuclei during encounters and performed autonomous interplanetary navigation. AutoNav has enabled five cometary flyby missions (Table!1) residing on four NASA spacecraft provided by three different spacecraft builders. Using this software, missions were able to process a combined total of nearly 1000 images previously unseen by humans. By eliminating the need to navigate spacecraft from Earth, the accuracy gained by AutoNav during flybys compared to ground-based navigation is about 1!order of magnitude in targeting and 2!orders of magnitude in time of flight. These benefits ensure that pointing errors do not compromise data gathered during flybys. In addition, these benefits can be applied to flybys of other solar system objects, flybys at much slower relative velocities, mosaic imaging campaigns, and other proximity activities (e.g., orbiting, hovering, and descent/ascent).

Autonomy↗

Study to define logic associated with CMGS to maneuver and stabilize an orbiting spacecraft

A study was conducted to define the logic associated with the control moment gyroscopes to maneuver and stabilize an orbiting spacecraft. The study objectives are as follows: (1) to define mission requirements and feasible attitudes for a shuttle-like vehicle that will meet mission objectives, (2) to determine the control moment gyroscope (CMG) and system configurations that will best meet overall mission requirements, (3) to define all of the software required to manage and control the selected CMG systems, and (4) to verify by computer simulation the adequacy of the selected CMG system and specified software package in meeting the overall mission requirements.

Source record↗

NASA SpaceWire Status

Three projects are developing SpaceWire upper layer protocols: JWST, LRO, GOES-R. JWST protocol development was complete before Protocol ID field was introduced to the standard. Commanding is done by using CCD5 packets tunneled through SpaceWire. Science Data packet is optimized for implementation specific requirements. Lunar Reconnaissance Orbiter (LRD) investigated using the SnP Rmap protocol but chose to use CCSDS tunneled through SpaceWire. GOES-R is using CCDS tunneled through SpaceWire with project developed Reliable Delivery protocol. Reliable Delivery protocol may be used to replace MIL-STD-1553 for other mission. CCDS is the native format for the software bus for many NASA GSFC missions and therefore it is a natural packet format to tunnel through SpaceWire.

Rakow, Glenn Parker↗

Graphical Planning Of Spacecraft Missions

Mission Planning Graphical Tool (MPGT) computer program provides analysts with graphical representations of spacecraft and environmental data used in planning missions. Designed to be generic software tool configured to analyze any specified Earth-orbiting spacecraft mission. Data presented as series of overlays on top of two-dimensional or three-dimensional projection of Earth. Includes spacecraft-orbit tracks, ground-station-antenna masks, solar and lunar ephemerides, and coverage by Tracking Data and Relay Satellite System (TDRSS). From graphical representations, analyst determines such spacecraft-related constraints as communication coverage, infringement upon zones of interference, availability of sunlight, and visibility of targets to instruments.

Jeletic, J. F.↗

Service Provider Agnostic Adaptive Coding and Modulation System Design

Commercial service providers (CSPs) are increasingly used to provide communications services to near-Earth science and exploration missions. CSPs commonly utilize modems that are designed to implement adaptive coding and modulation (ACM) in unique ways with modems from the same vendor. However, some missions cannot fly a matching vendor modem, either because the vendor only designs modems for terrestrial use, or the mission needs to fly a software defined radio. We present an ACM system design that allows missions to implement ACM on DVB-S2 compliant CSP links without needing to fly a modem from the same vendor the CSP uses. We implement and test our design in an emulated communications testbed. These tests demonstrate that our ACM system design can successfully adapt to link quality changes up to 6.12 dB/second.

Adaptive coding and modulation↗

Service Provider Agnostic Adaptive Coding and Modulation System Design

Commercial service providers (CSPs) are increasingly used to provide communications services to near-Earth science and exploration missions. CSPs commonly utilize modems that are designed to implement adaptive coding and modulation (ACM) in unique ways with modems from the same vendor. However, some missions cannot fly a matching vendor modem, either because the vendor only designs modems for terrestrial use, or the mission needs to fly a software defined radio. We present an ACM system design that allows missions to implement ACM on DVB-S2 compliant CSP links without needing to fly a modem from the same vendor the CSP uses. We implement and test our design in an emulated communications testbed. These tests demonstrate that our ACM system design can successfully adapt to link quality changes up to 6.12 dB/second.

Adaptive coding and modulation↗

Optimal guidance with obstacle avoidance for nap-of-the-earth flight

The development of automatic guidance is discussed for helicopter Nap-of-the-Earth (NOE) and near-NOE flight. It deals with algorithm refinements relating to automated real-time flight path planning and to mission planning. With regard to path planning, it relates rotorcraft trajectory characteristics to the NOE computation scheme and addresses real-time computing issues and both ride quality issues and pilot-vehicle interfaces. The automated mission planning algorithm refinements include route optimization, automatic waypoint generation, interactive applications, and provisions for integrating the results into the real-time path planning software. A microcomputer based mission planning workstation was developed and is described. Further, the application of Defense Mapping Agency (DMA) digital terrain to both the mission planning workstation and to automatic guidance is both discussed and illustrated.

Pekelsma, Nicholas J.↗

Re-Engineering JPL's Mission Planning Ground System Architecture for Cost Efficient Operations in the 21st Century

Work carried out to re-engineer the mission analysis segment of JPL's mission planning ground system architecture is reported on. The aim is to transform the existing software tools, originally developed for specific missions on different support environments, into an integrated, general purpose, multi-mission tool set. The issues considered are: the development of a partnership between software developers and users; the definition of key mission analysis functions; the development of a consensus based architecture; the move towards evolutionary change instead of revolutionary replacement; software reusability, and the minimization of future maintenance costs. The current status and aims of new developments are discussed and specific examples of cost savings and improved productivity are presented.

Fordyce, Jess↗

Failure Assessment

Three questions to which software developers want accurate, precise answers are "How can the software system fail?", "mat bad things will happen if the software fails?t', and "How many failures will the software experience?". Numerous techniques have been devised to answer these questions; three of the best known are: 1) Software Fault Tree Analysis (SFTA) 2) Software Failure Modes, Effects, and Criticality Analysis (SFMECA 3) Software Fault/Failure Modeling. SFTA and SFMECA have been successfully used to analyze the flight software for a number of robotic planetary exploration missions, including Galileo, Cassini, and Deep Space 1. Given the increasing interest in reusing software components from mission to mission, one of us has developed techniques for reusing the corresponding portions of the SFTA and SFMECA, reducing the effort required to conduct these analyses. SFTA has also been shown to be effective in analyzing the security aspects of software systems; intrusion mechanisms and effects can easily be modeled using these techniques. The Bi- Directional Safety Analysis (BDSA) method combines a forward search (similar to SFMECA) from potential failure modes to their effects, with a backward search (similar to SFTA) from feasible hazards to the contributing causes of each hazard. BDSA offers an efficient way to identify latent failures. Recent work has extended BDSA to product-line applications such as flight-instrumentation displays and developed tool support for the reuse of the failure-analysis artifacts within a product line. BDSA has also been streamlined to support those projects having tight cost and/or schedule constraints for their failure analysis efforts. We discuss lessons learned from practice, describe available tools, and identi@ some future directions for the topic. A substantial amount of research has been devoted to estimating the number of failures that a software system will experience during test and operations, as well as the number of faults that have been inserted into that system during its development. One of us has found that the amount of structural change to a system during its development is strongly related to the number of faults inserted into it. Using techniques requiring no additional effort on the part of the development organization, the required measurements of structural evolution can be easily obtained from a development effort's configuration management system and readily transformed into an estimate of fault content. So far, structure-fault relationships have been identified for source code; current work seeks to examine artifacts available earlier in the lifecycle to determine if similar relationships between structure and fault content can be found. In particular, relationships between requirements change requests and the number of faults inserted into the implemented system would provide a significant improvement in our ability to control software quality during the early development phases.

fault tree↗

A Multi-mission Event-Driven Component-Based System for Support of Flight Software Development, ATLO, and Operations first used by the Mars Science Laboratory (MSL) Project

This viewgraph presentation reviews the architectural description of the Mission Data Processing and Control System (MPCS). MPCS is an event-driven, multi-mission ground data processing components providing uplink, downlink, and data management capabilities which will support the Mars Science Laboratory (MSL) project as its first target mission. MPCS is designed with these factors (1) Enabling plug and play architecture (2) MPCS has strong inheritance from GDS components that have been developed for other Flight Projects (MER, MRO, DAWN, MSAP), and are currently being used in operations and ATLO, and (3) MPCS components are Java-based, platform independent, and are designed to consume and produce XML-formatted data

Mission Data Processing and Control System (MPCS)↗

Life Cycle Cost Growth Study for the Discovery and New Frontiers Program Office

The D&NF Program Office LCC Management Study provides a detailed look at the drivers underlying cost overruns and schedule delays for five D&NF missions. While none of the findings are new, the study underlines the importance of continued emphasis on sound project management techniques: a clean project management structure with a clear definition of roles and responsibilities across the various partners in a project, an understanding of institutional standards and procedures and any differences among the partners, and the critical need for a comprehensive IMS that can be used easily and routinely to identify potential threats to the critical path. The study also highlights the continuing need for realistic estimates of the total LCC. Sufficient time and resources must be allocated early in a project to ensure that the appropriate trade studies and analyses are performed across all aspects of a mission: spacecraft, ground system, operations concept, and fault management, to ensure that proposed and confirmed costs truly reflect the resource requirements over the entire mission life cycle. These studies need to include a realistic review of the assumptions underlying the use of new technologies, the integration of heritage and new hardware and software into the total mission environment, and any development and test savings based on heritage technology and lessons learned. Finally, the LCC Management Study stresses the need to listen to, carefully consider, and take positive action regarding the issues raised during reviews by the expert review teams.

Barley, Bryan↗

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↗