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 883 records · Page 49
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Ethernet for Space Flight Applications

NASA's Goddard Space Flight Center (GSFC) is adapting current data networking technologies to fly on future spaceflight missions. The benefits of using commercially based networking standards and protocols have been widely discussed and are expected to include reduction in overall mission cost, shortened integration and test (I&T) schedules, increased operations flexibility, and hardware and software upgradeability/scalability with developments ongoing in the commercial world. The networking effort is a comprehensive one encompassing missions ranging from small University Explorer (UNEX) class spacecraft to large observatories such as the Next Generation Space Telescope (NGST). Mission aspects such as flight hardware and software, ground station hardware and software, operations, RF communications, and security (physical and electronic) are all being addressed to ensure a complete end-to-end system solution. One of the current networking development efforts at GSFC is the SpaceLAN (Spacecraft Local Area Network) project, development of a space-qualifiable Ethernet network. To this end we have purchased an IEEE 802.3-compatible 10/100/1000 Media Access Control (MAC) layer Intellectual Property (IP) core and are designing a network node interface (NNI) and associated network components such as a switch. These systems will ultimately allow the replacement of the typical MIL-STD-1553/1773 and custom interfaces that inhabit most spacecraft. In this paper we will describe our current Ethernet NNI development along with a novel new space qualified physical layer that will be used in place of the standard interfaces. We will outline our plans for development of space qualified network components that will allow future spacecraft to operate in significant radiation environments while using a single onboard network for reliable commanding and data transfer. There will be a brief discussion of some issues surrounding system implications of a flight Ethernet. Finally, we will show an onboard network architecture for a proposed new mission using Ethernet for science data transport.

Webb, Evan↗
NASA NTRS2005

MSAP Hardware Verification: Testing Multi-Mission System Architecture Platform Hardware Using Simulation and Bench Test Equipment

The Multi-Mission System Architecture Platform (MSAP) project aims to develop a system of hardware and software that will provide the core functionality necessary in many JPL missions and can be tailored to accommodate mission-specific requirements. The MSAP flight hardware is being developed in the Verilog hardware description language, allowing developers to simulate their design before releasing it to a field programmable gate array (FPGA). FPGAs can be updated in a matter of minutes, drastically reducing the time and expense required to produce traditional application-specific integrated circuits. Bench test equipment connected to the FPGAs can then probe and run Tcl scripts on the hardware. The Verilog and Tcl code can be reused or modified with each design. These steps are effective in confirming that the design operates according specifications.

Crossin, Kent R.↗
NASA NTRS2013

Space Data Systems Applications in the iPAS Pathfinder Laboratory

The iPAS is an integrated hardware/software test and evaluation environment, in support of current and future spacecraft development The iPAS has two main elements. A common avionics, hardware, and software architecture that can be applied over various missions. A common testbed framework that supports integrated hardware/software testing for a variety of applications. The iPAS includes the following (non-flight qualified) components: Core Flight Software (from GSFC). Commercially available Proton and S950 Flight Computer boards. Power and propulsion systems based on representative flight hardware. A realistic flight deck based on the Multi-Purpose Crew Vehicle (MPCV), including realistic flight controls and displays. A Space Data System based on CCSDS protocols.

Rich, Tom↗
NASA NTRS1996

SEDSAT 1 Technologies

The original goals of this project were to support the development of SEDSAT 1 for a tethered launch in July of 1997. This specifically required: (1) Monitoring development progress against a comprehensive delivery plan; (2) Incremental development and release of CDS and SEASIS software; (3) Supporting the integration of version 1.0 SEASIS software that will allow minimal autonomous operation without a software reload. These algorithms would include image quality evaluation, attitude determination, and autonomous earth imaging; and (4) Developing software requirements and design for ground segment software, concentrating on command and data download capability; and interface to external development efforts for a more comprehensive software suite to be used after the initial mission. Because of an unfavorable space shuttle safety review of the SEDS-3 tether deployer, and cost and schedule problems in upgrading the deployer, the mission was changed to an independent launch of SEDSAT. The original plan was to do a tether-less deployment from the space shuttle. Since this would have resulted in an unacceptable orbital lifetime, the mission was changed again to a tethered launch from a Delta II in June 1998. As a result of Marshall Space Flight Center's redirection of the SEDS-3 mission away from a tether launch, the whole question of a tether endmass had to be reconsidered. The net result of these multiple changes was twofold. First, we completed work needed to define some aspects of ground software on SEDSAT 1 that would remain constant no matter the launch mode. Second, we developed a set of concepts for using SEDSAT 1 technology to support alternative endmass missions on SEDS-3. Both of these are included.

Maier, Mark W.↗
NASA NTRS1996

Flight Dynamics Mission Support and Quality Assurance Process

This paper summarizes the method of the Computer Sciences Corporation Flight Dynamics Operation (FDO) quality assurance approach to support the National Aeronautics and Space Administration Goddard Space Flight Center Flight Dynamics Support Branch. Historically, a strong need has existed for developing systematic quality assurance using methods that account for the unique nature and environment of satellite Flight Dynamics mission support. Over the past few years FDO has developed and implemented proactive quality assurance processes applied to each of the six phases of the Flight Dynamics mission support life cycle: systems and operations concept, system requirements and specifications, software development support, operations planing and training, launch support, and on-orbit mission operations. Rather than performing quality assurance as a final step after work is completed, quality assurance has been built in as work progresses in the form of process assurance. Process assurance activities occur throughout the Flight Dynamics mission support life cycle. The FDO Product Assurance Office developed process checklists for prephase process reviews, mission team orientations, in-progress reviews, and end-of-phase audits. This paper will outline the evolving history of FDO quality assurance approaches, discuss the tailoring of Computer Science Corporations's process assurance cycle procedures, describe some of the quality assurance approaches that have been or are being developed, and present some of the successful results.

Oh, InHwan↗
NASA NTRS1996

Co-Investigator Participation in the Mars-94 Mission Studies of the Mars-Solar Wind Interaction: Topside Sounder and Magnetometer

The purpose of this investigation has been to provide United States co-investigator support toward the preparation of the Topside Ionospheric Sounder and Magnetometer experiments on the Russian Mars-96 (previously Mars-94) mission. The main role has been to assist in the preparation of software tools for the optimum design of the investigation and the evaluation of mission operational plans and orbits.

Luhmann, Janet G.↗
NASA NTRSDate not supplied

Designing Autonomy into Interfaces for Long-Duration Missions

As NASA develops technologies for long-duration crewed missions, we must understand how communication between ground control teams and astronauts differs from the current dynamic to adapt new concepts for long-duration mission operations. Today, ground control teams support astronauts with immediate availability to answer questions, resolve issues, and manage activities. In the near future, however, extended communication delays during long-duration missions will require astronauts to become more autonomous. As many of the responsibilities shift from the ground control teams to the astronauts on-board, the concept of operations must also change from how it functions today. With increased astronaut autonomy, software tools must be developed that enable efficient completion of mission tasks without increased mental workload. Designing software tools to facilitate crew autonomy requires development teams to know which data will enhance quick decision making while providing necessary context for situational awareness of systems being managed on-board. NASA's Autonomous Systems and Operations (ASO) team is presently developing a software interface tool, EXPRESS (EXpedite the PRocessing of Experiments for Space Station) 2.5 to enable a long-duration crew to schedule activities for and operate autonomous systems. This paper describes details of the integrated human factors approach that drove the design of the elements of the software tool, including self-managed scheduling, constraint-driven planning, autonomous system fault recovery, and recommended troubleshooting actions. Additionally, this paper will chronicle ASO modifications of the user interface after the team's first flight demonstration, how it was based on lessons learned during software development, as well as from crew feedback in order to develop the current version which will be demonstrated on ISS in 2021. In the upcoming ISS demonstration, the astronaut crew will be given scenarios for scheduling and operating autonomous system activities, including off-nominal scenarios and autonomous system recoveries. The demonstration of the EXPRESS 2.5 tool is a step towards improved levels of autonomy as our new journeys take us farther into space.

autonomy↗
NASA NTRS2011

The Traverse Planning Process for the Drats 2010 Analog Field Simulations

Traverse planning concentrates on optimizing the science return within the overall objectives of planetary surface missions or their analog field simulations. Such simulations were conducted in the San Francisco Volcanic Field, northern Arizona, from Aug. 26 to Sept 17, 2010 and involved some 200 individuals in the field, with some 40 geoscientists composing the science team. The purpose of these Desert Research and Technology Studies (DRATS) is to exercise and evaluate developmental hardware, software and operational concepts in a mission-like, fully-integrated, setting under the direction of an onsite Mobile Mission Control Center(MMCC). DRATS 2010 focused on the simultaneous operation of 2 rovers, a historic first. Each vehicle was manned by an astronaut-commander and an experienced field geologist. Having 2 rovers and crews in the field mandated substantially more complex science and mission control operations compared to the single rover DRATS tests of 2008 and 2009, or the Apollo lunar missions. For instance, the science support function was distributed over 2 "back rooms", one for each rover, with both "tactical" teams operating independently and simultaneously during the actual traverses. Synthesis and integration of the daily findings and forward planning for the next day(s) was accomplished overnight by yet another "strategic" science team.

Horz, Friedrich↗
DOE OSTI2024

A Survey of Open Source Software Repositories in the U.S. Department of Energy’s National Laboratories

There are 17 national laboratory systems in the United States operating under the auspices of the U.S. Department of Energy (DOE). These government labs employ tens of thousands of people engaging in research software engineering activities across a variety of missions. To support this work, many open source projects are maintained. Further, many of these projects have broad utility to the computing community at large and domain scientists in a variety of fields. However, the complexity and decentralized nature of the laboratory system has resulted in a situation where no one entity even knows about all the open source software projects in this ecosystem, let alone crude metrics of their health. In this article, we do the first external inventory of open source software repositories with a nexus to DOE labs. We posit that a project’s need for sustainability support can be determined by comparing measures of active use to measures of active maintenance.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS2012

Ascent/Descent Software

The Ascent/Descent Software Suite has been used to support a variety of NASA Shuttle Program mission planning and analysis activities, such as range safety, on the Integrated Planning System (IPS) platform. The Ascent/Descent Software Suite, containing Ascent Flight Design (ASC)/Descent Flight Design (DESC) Configuration items (Cis), lifecycle documents, and data files used for shuttle ascent and entry modeling analysis and mission design, resides on IPS/Linux workstations. A list of tools in Navigation (NAV)/Prop Software Suite represents tool versions established during or after the IPS Equipment Rehost-3 project.

Brown, Charles↗
NASA NTRS2017

Technology and Tool Development to Support Safety and Mission Assurance

The Assurance Case approach is being adopted in a number of safety-mission-critical application domains in the U.S., e.g., medical devices, defense aviation, automotive systems, and, lately, civil aviation. This paradigm refocuses traditional, process-based approaches to assurance on demonstrating explicitly stated assurance goals, emphasizing the use of structured rationale, and concrete product-based evidence as the means for providing justified confidence that systems and software are fit for purpose in safely achieving mission objectives. NASA has also been embracing assurance cases through the concepts of Risk Informed Safety Cases (RISCs), as documented in the NASA System Safety Handbook, and Objective Hierarchies (OHs) as put forth by the Agency's Office of Safety and Mission Assurance (OSMA). This talk will give an overview of the work being performed by the SGT team located at NASA Ames Research Center, in developing technologies and tools to engineer and apply assurance cases in customer projects pertaining to aviation safety. We elaborate how our Assurance Case Automation Toolset (AdvoCATE) has not only extended the state-of-the-art in assurance case research, but also demonstrated its practical utility. We have successfully developed safety assurance cases for a number of Unmanned Aircraft Systems (UAS) operations, which underwent, and passed, scrutiny both by the aviation regulator, i.e., the FAA, as well as the applicable NASA boards for airworthiness and flight safety, flight readiness, and mission readiness. We discuss our efforts in expanding AdvoCATE capabilities to support RISCs and OHs under a project recently funded by OSMA under its Software Assurance Research Program. Finally, we speculate on the applicability of our innovations beyond aviation safety to such endeavors as robotic, and human spaceflight.

Mission Assuranc↗
NASA NTRS2019

Data Preservation: Final Step in the Life Cycle of a Mission

Many NASA Earth Observing System (EOS) have either already reached the end of their active life or are nearing it. Preservmissionsation of data products is a fairly well defined task for the NASA EOS Data Centers or DAACs.The Goddard Earth Sciences Data and Information Services Center (GES-DISC) has implemented a repository system, which is capable of long-term archive of documentation artifacts and other associated digital content. The existing GES-DISC Repository System is based on Fedora Commons, an open-source repository management software, for cost savings and flexibility.The first mission to utilize the GES-DISC Repository System was the High Resolution Dynamics Limb Sounder (HIRDLS) on the Aura spacecraft. Since then, the GES DISC has gathered documentation from the UARS and TOMS into the Repository. The Microwave Limb Sounder (MLS) team has begun delivering some early pre-launch documents to the GES-DISC Repository System as well. Other missions in planning or progress include AIRS, OMI, SORCE, SNPP Sounder, and TRMM.

Johnson, J.↗
NASA NTRS2003

Navigation Flight Test Results from the Low Power Transceiver Communications and Navigation Demonstration on Shuttle (CANDOS) Experiment

This paper presents the Global Positioning System (GPS) navigation results from the Communications and Navigation Demonstration on Shuttle (CANDOS) experiment flown on STS-107. This experiment was the initial flight of a Low Power Transceiver (LPT) that featured high capacity space- space and space-ground communications and GPS- based navigation capabilities. The LPT also hosted the GPS Enhanced Orbit Determination Experiment (GEODE) orbit determination software. All CANDOS test data were recovered during the mission using LPT communications links via the Tracking and Data Relay Satellite System (TDRSS). An overview of the LPT s navigation software and the GPS experiment timeline is presented, along with comparisons of test results to the NASA Johnson Space Center (JSC) real-time ground navigation vectors and Best Estimate of Trajectory (BET).

Haas, Lin↗
NASA NTRS2003

Software Supports Distributed Operations via the Internet

Multi-mission Encrypted Communication System (MECS) is a computer program that enables authorized, geographically dispersed users to gain secure access to a common set of data files via the Internet. MECS is compatible with legacy application programs and a variety of operating systems. The MECS architecture is centered around maintaining consistent replicas of data files cached on remote computers. MECS monitors these files and, whenever one is changed, the changed file is committed to a master database as soon as network connectivity makes it possible to do so. MECS provides subscriptions for remote users to automatically receive new data as they are generated. Remote users can be producers as well as consumers of data. Whereas a prior program that provides some of the same services treats disconnection of a user from the network of users as an error from which recovery must be effected, MECS treats disconnection as a nominal state of the network: This leads to a different design that is more efficient for serving many users, each of whom typically connects and disconnects frequently and wants only a small fraction of the data at any given time.

Norris, Jeffrey↗
NASA NTRS2015

Towards an Open, Distributed Software Architecture for UxS Operations

To address the growing need to evaluate, test, and certify an ever expanding ecosystem of UxS platforms in preparation of cultural integration, NASA Langley Research Center's Autonomy Incubator (AI) has taken on the challenge of developing a software framework in which UxS platforms developed by third parties can be integrated into a single system which provides evaluation and testing, mission planning and operation, and out-of-the-box autonomy and data fusion capabilities. This software framework, named AEON (Autonomous Entity Operations Network), has two main goals. The first goal is the development of a cross-platform, extensible, onboard software system that provides autonomy at the mission execution and course-planning level, a highly configurable data fusion framework sensitive to the platform's available sensor hardware, and plug-and-play compatibility with a wide array of computer systems, sensors, software, and controls hardware. The second goal is the development of a ground control system that acts as a test-bed for integration of the proposed heterogeneous fleet, and allows for complex mission planning, tracking, and debugging capabilities. The ground control system should also be highly extensible and allow plug-and-play interoperability with third party software systems. In order to achieve these goals, this paper proposes an open, distributed software architecture which utilizes at its core the Data Distribution Service (DDS) standards, established by the Object Management Group (OMG), for inter-process communication and data flow. The design decisions proposed herein leverage the advantages of existing robotics software architectures and the DDS standards to develop software that is scalable, high-performance, fault tolerant, modular, and readily interoperable with external platforms and software.

Cross, Charles D.↗
NASA NTRS1991

A planning language for activity scheduling

Mission planning and scheduling of spacecraft operations are becoming more complex at NASA. Described here are a mission planning process; a robust, flexible planning language for spacecraft and payload operations; and a software scheduling system that generates schedules based on planning language inputs. The mission planning process often involves many people and organizations. Consequently, a planning language is needed to facilitate communication, to provide a standard interface, and to represent flexible requirements. The software scheduling system interprets the planning language and uses the resource, time duration, constraint, and alternative plan flexibilities to resolve scheduling conflicts.

Zoch, David R.↗
NASA NTRS1975

Atmosphere explorer /AE-C/ adaptive mission design and trajectory performance

The preflight mission design and in-flight execution are presented to illustrate the actual utilization of the adaptive nature of this mission. Spacecraft systems (propulsion, attitude, accelerometer) and software (maneuver program) features which contribute to the adaptive trajectory flexibility are discussed. Descriptions of procedures used to handle low perigee maneuver operations (to 130 km), for achieving ground track control and orbit phasing, for making a transition from elliptical to circular orbits, and for circular orbit restoration and maintenance are presented in detail. The 85 maneuvers made during the first 17 months of the mission are summarized.

Barbieri, R. W.↗