Search NASA⌕ Search

SEARCH · Search NASA

Results for “Mars architecture”

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 NTRS1990

A control architecture for a Mars walking vehicle

A design framework for a Mars Rover, intended for missions where a high degree of autonomy is dictated, is presented. The framework provides a logical computing architecture for rover mobility and local navigation subsystem design by defining a set of functional modules and interfaces to facilitate software and hardware specification. The similarities and dissimilarities between the present approach and related architectures for autonomous navigation and robotic control are discussed. An approach is presented for specifying actions to be taken by the mobility and local navigation subsystems of the rover.

Spiessbach, Andrew J.↗
NASA NTRS2005

The Mars Reconnaissance Orbiter mission operations: architecture and approach

The Mars Reconnaissance Orbiter (MRO) was launched on August 12, 2005 by an Atlas V launch vehicle from Cape Canaveral Air Force Station. MRO will carry a rich set of science instruments to Mars and provide global, regional survey, and targeted observations. In addition, a set of engineering instruments providing optical navigation, Ka band telecommunication and UHF relay services to future Mars missions are part of the MRO payload.

MRO↗
NASA NTRS2006

The Mars Reconnaissance Orbiter Mission Operations: Architecture and Approach

The Mars Reconnaissance Orbiter (MRO) was launched on August 12, 2005 by an Atlas V launch vehicle from Cape Canaveral Air Force Station. MRO will carry a rich set of science instruments to Mars and provide global, regional survey, and targeted observations. In addition, a set of engineering instruments providing optical navigation, Ka band telecommunication and UHF relay services to future Mars missions are part of the MRO payload. During the mission, the MRO operations teams are presented with two major challenges - unprecedented high data rate and data volumes, and complex science planning and resource sharing. MRO has the capability to communicate with earth at a maximum of six Megabits per second (> 50 times any previous Mars missions). With the current Deep Space Network (DSN) contact schedule of 19 eight-hour tracks per week, the baseline mission plan is for MRO to return 34 Terabits of raw science data during the two year primary science phase. Each of the science instruments has its unique requirements for global mapping, regional survey, and targeted observations. Some instruments prefer nadir-only observations, while others require off-nadir observations (especially for stereo viewing). The requirements from these Mars viewing instruments presented a significant challenge for the operations team to design the complex science planning and resource sharing/allocation process. This paper describes what MRO project is implementing to solve these challenges.

Mars Reconnaissance Orbiter (MRO)↗
NASA NTRS2005

Designing and Implementing a Distributed System Architecture for the Mars Rover Mission Planning Software (Maestro)

Distributed systems allow scientists from around the world to plan missions concurrently, while being updated on the revisions of their colleagues in real time. However, permitting multiple clients to simultaneously modify a single data repository can quickly lead to data corruption or inconsistent states between users. Since our message broker, the Java Message Service, does not ensure that messages will be received in the order they were published, we must implement our own numbering scheme to guarantee that changes to mission plans are performed in the correct sequence. Furthermore, distributed architectures must ensure that as new users connect to the system, they synchronize with the database without missing any messages or falling into an inconsistent state. Robust systems must also guarantee that all clients will remain synchronized with the database even in the case of multiple client failure, which can occur at any time due to lost network connections or a user's own system instability. The final design for the distributed system behind the Mars rover mission planning software fulfills all of these requirements and upon completion will be deployed to MER at the end of 2005 as well as Phoenix (2007) and MSL (2009).

Goldgof, Gregory M.↗
NASA NTRS2002

NASA Exploration Team (NExT) In-Space Transportation Overview

This presentation provides an overview of NASA Exploration Team's (NEXT) vision of in-space transportation in the future. Hurdles facing in-space transportation include affordable power sources, crew health and safety, optimized robotic and human operations and space systems performance. Topics covered include: exploration of Earth's neighborhood, Earth's neighborhood architecture and elements, Mars mission trajectory options, delta-v variations, Mars mission duration options, Mars mission architecture, nuclear electric propulsion advantages and miscellaneous technology needs.

Bret G Drake↗
NASA NTRS2001

Navigation architecture for future Mars missions

Developing cost efficient individual flight projects that perform both orbital and surface exploraton will likely require intelligent infrastructure elements for critical functions such as navigation.

Mars navigation↗
NASA NTRS2003

A Distributed Data Architecture for 2001 Mars Odyssey Data Distribution

Newer instruments and communications techniques have given scientists unprecedented amounts of data, more than can be feasibly distributed through traditional methods such as mailed CD-ROM's. Leveraging the web makes sense since it enables scientists to request specific data and retrieve products as soon as they're available. Yet defining the middleware system to support such an application has remained just out of reach, until Odyssey. For the first time ever, data from all Odyssey mission instruments were made available through a single system immediately upon delivery to the Planetary Data System (PDS). The Object Oriented Data Technology (OODT) software made such an application possible.

distributed↗