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 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
NASA NTRS1975

Error Analysis of the Shuttle Orbital Maneuvering System P-V-T Propellant Gaging Module. Mission Planning, Mission Analysis and Software Formulation

An investigation of the shuttle orbital maneuvering system (OMS) pressure-volume-temperature (P-V-T) propellant gaging module has revealed that the gaging errors due to the combined effects of random instrumentation measurement errors, propellant loading uncertainties, and simplifying assumptions in the software are non-linear over the range of the usable propellant quantity gage (0-100%), with the largest error being at the zero point. When the OMS propellant tanks in the orbiter vehicle pods are filled to contain 100% of the maximum usable propellant, the gaging error at the zero point was determined to be 9.5% for the fuel and 9.5% for the oxidizer. When the OMS propellant tanks initially contain 50% of the maximum usable propellant, the largest gaging error is still 9.5% for the fuel and 9.5% for the oxidizer.

Duhon, D. D.↗
NASA NTRS1977

Space shuttle engineering and operations support. ALT separation reference trajectories for tailcone on orbiter forward and aft CG configurations. Mission planning, mission analysis and software formulation

A preflight analysis of the ALT separation reference trajectories for the tailcone on, forward, and aft cg orbiter configurations is documented. The ALT separation reference trajectories encompass the time from physical separation of the orbiter from the carrier to orbiter attainment of the maximum ALT interface airspeed. The trajectories include post separation roll maneuvers by both vehicles and are generated using the final preflight data base. The trajectories so generated satisfy all known separation design criteria and violate no known constraints. The requirement for this analysis is given along with the specifications, assumptions, and analytical approach used to generate the separation trajectories. The results of the analytical approach are evaluated, and conclusions and recommendations are summarized.

Glenn, G. M.↗
NASA NTRS1977

Smoothing of orbital tracking data: Mission planning, mission analysis and software formulation

The problem created by the presence of wild or outlying data points among orbital tracking data, is addressed. Consideration is given to the effects of such outliers on the orbit determination process, and methods for minimizing or even eliminating these effects are proposed. Some preliminary efforts implementing these new methods are described, and the results thus far obtained are summarized. Based on these ideas and results, recommendations are made for future investigation.

Vedder, J. D.↗
NASA NTRS1978

Remote manipulator system flexibility analysis program: Mission planning, mission analysis, and software formulation

A computer program is described for calculating the flexibility coefficients as arm design changes are made for the remote manipulator system. The coefficients obtained are required as input for a second program which reduces the number of payload deployment and retrieval system simulation runs required to simulate the various remote manipulator system maneuvers. The second program calculates end effector flexibility and joint flexibility terms for the torque model of each joint for any arbitrary configurations. The listing of both programs is included in the appendix.

Kumar, L.↗
NASA NTRS1979

Modifications to give HOPE/MDC 2.0 the capability to solve for or consider vent forces: Mission planning, mission analysis, and software formulation

The modifications are described as necessary to give the Houston Operations Predictor/Estimator (HOPE) program the capability to solve for or consider vent forces for orbit determination. The model implemented in solving for vent forces is described along with the integrator problems encountered. A summary derivation of the mathematical principles applicable to solve/consider methodology is provided.

Zyla, L. V.↗
NASA NTRS1989

Trajectory optimization software for planetary mission design

The development history and characteristics of the interactive trajectory-optimization programs MOSES (D'Amario et al., 1981) and PLATO (D'Amario et al., 1982) are briefly reviewed, with an emphasis on their application to the Galileo mission. The requirements imposed by a mission involving flybys of several planetary satellites or planets are discussed; the formulation of the parameter-optimization problem is outlined; and particular attention is given to the use of multiconic methods to model the gravitational attraction of Jupiter in MOSES. Diagrams and tables of numerical data are included.

D'Amario, Louis A.↗
NASA NTRS1993

Mission-Clock-Display Software Tool

Displays including images of alarm clocks illustrate temporal statuses of multiple events. MCLK is customizable clock-display computer program with Motif user interface. Used to keep track of such multiple "milestone" events as those occurring during countdowns in spacecraft launches, and alerts user when event time reached. In addition, program displays time from several time zones. Real time measured in Coordinated Universal Time. Written in C language.

Aguilera, Christine↗
NASA NTRS1993

Expert diagnostics system as a part of analysis software for power mission operations

The operation of interplanetary spacecraft at JPL has become an increasingly complex activity. This complexity is due to advanced spacecraft designs and ambitious mission objectives which lead to operations requirements that are more demanding than those of any previous mission. For this reason, several productivity enhancement measures are underway at JPL within mission operations, particularly in the spacecraft analysis area. These measures aimed at spacecraft analysis include: the development of a multi-mission, multi-subsystem operations environment; the introduction of automated tools into this environment; and the development of an expert diagnostics system. This paper discusses an effort to integrate the above mentioned productivity enhancement measures. A prototype was developed that integrates an expert diagnostics system into a multi-mission, multi-subsystem operations environment using the Galileo Power / Pyro Subsystem as a testbed. This prototype will be discussed in addition to background information associated with it.

Harris, Jennifer A.↗
NASA NTRS1994

Benefits of advanced software techniques for mission planning systems

The increasing complexity of modern spacecraft, and the stringent requirement for maximizing their mission return, call for a new generation of Mission Planning Systems (MPS). In this paper, we discuss the requirements for the Space Mission Planning and the benefits which can be expected from Artificial Intelligence techniques through examples of applications developed by Matra Marconi Space.

Gasquet, A.↗
NASA NTRS2011

Project Report: Automatic Sequence Processor Software Analysis

The Mission Planning and Sequencing (MPS) element of Multi-Mission Ground System and Services (MGSS) provides space missions with multi-purpose software to plan spacecraft activities, sequence spacecraft commands, and then integrate these products and execute them on spacecraft. Jet Propulsion Laboratory (JPL) is currently is flying many missions. The processes for building, integrating, and testing the multi-mission uplink software need to be improved to meet the needs of the missions and the operations teams that command the spacecraft. The Multi-Mission Sequencing Team is responsible for collecting and processing the observations, experiments and engineering activities that are to be performed on a selected spacecraft. The collection of these activities is called a sequence and ultimately a sequence becomes a sequence of spacecraft commands. The operations teams check the sequence to make sure that no constraints are violated. The workflow process involves sending a program start command, which activates the Automatic Sequence Processor (ASP). The ASP is currently a file-based system that is comprised of scripts written in perl, c-shell and awk. Once this start process is complete, the system checks for errors and aborts if there are any; otherwise the system converts the commands to binary, and then sends the resultant information to be radiated to the spacecraft.

sequencing↗
NASA NTRS1993

Commonality of flight control systems for support of European telecommunications missions

This paper is concerned with the presentation of mission-independent software systems that provide a common software platform to ground data systems for mission operations. The objectives of such common software platforms are to reduce the cost of the development of mission-dedicated software systems and to increase the level of reliability of the ground data systems for mission operations. In accordance with this objective, the Multi-Satellite Support System (MSSS) was developed at the European Space Operations Center (ESOC). Between 1975 and 1992, the MSSS provided support to 16 European Space Agency (ESA) missions, among them very demanding science missions such as GEOS, EXOSAT, and Giotto. The successful support of these missions proved the validity of the MSSS concept with its extended mission-independent platform. This paper describes the MSSS concept and focuses on the wide use of MSSS as a flight control system for geosynchronous telecommunications satellites. Reference is made to more than 15 telecommunications missions that are operated from Western Europe using flight control systems with an underlying MSSS concept, demonstrating the benefits of a commonly used software platform. Finally, the paper outlines the design of the new generation of flight control systems, which is being developed at ESOC for this decade, following a period of more than 15 years of MSSS support.

Debatin, Kurt↗
NASA NTRS1984

Mission planning and operations of a Space Shuttle payload experiment: SIR-A

In November 1981 the first scientific payload was carried on board the second flight of the Space Shuttle. The principal instrument on that flight was a synthetic aperture radar. This paper is concerned with the operational concepts developed to achieve the objective of terrestrial geologic mapping by radar from earth orbit for this mission. Computer software was developed as an aid to mission design prior to the mission and as a replanning tool used during the mission: The first step in the development of software for future missions where such tools will become indispensable to meet the apparently contradictory objectives of complex observations and low cost.

Harris, H. M.↗
NASA NTRS2018

Ground Software Technologies – Embracing Change: Mission Drivers and Technology Opportunities to Enable Long Lived Missions

Mission lifecycles have proven to extend well beyond their original design. The benefits to this are countless but introduce challenges in today’s rapidly changing ground infrastructure and software technologies used to enable mission success. What remains constant is the risk posture missions maintain when accepting change and the use of new technologies. Larger missions are ready for change in early lifecycle development but near launch and especially in operations, few continue to evolve beyond what is set in place in phase C. This paper will discuss how the Advance Multi-Mission Operations System (AMMOS) intends to address, three driving missions concerns: Maintaining functionality (hardware/software) for decades, rapidly responding to security vulnerabilities in software, and finally the ability to quickly evolve infrastructure and software changes. These driving concerns are briefly described below: 1. Maintaining functionality (hardware/software) for decades. Hardware updates considerably faster than 10 years ago. Expectations that a system can remain in place for more than 10 years is no longer valid. Expecting to find hardware replacements for a system older than 5 years will increasingly become more and more challenging. How than do missions plan for hardware changes for long lived missions? Principle Objective: Provide abstraction by virtualizing and containerizing software abstract away any hardware dependencies and package up the application lightweight units. 2. Rapidly responding to security vulnerabilities in software. Cost is often the main impediment and largely driven by the revalidation and testing of system that undergo change. In todays, environment security updates are a major diver demanding systems remain up to date. How then do missions accept these changes and avoid large testing efforts? Principle Objective: Help reduce the cost of re-testing by automation of testing, deployment, and compartmentalizing change. 3. Ability to quickly evolve infrastructure and software changes. Responding quickly to change is similar to the second concern in this paper regarding security vulnerabilities. In this case, it address broader concerns of updating software and infrastructure on a more realistic timeline. How do missions stay up to date with the most recent versions of software and allowing for improved functionality? Principle Objective: Use continuous integration techniques at the system level to ensure rapid turnaround. This paper explores each of these concerns in more detail. It focuses the AMMOS’s current plans, challenges and current roadmap.

Giovannoni, Brian J.↗