SEARCH · Search NASA
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.
This presentation focuses on the design of antennas for the Mars Exploration Rovers (MER). Specific topics covered include: MER spacecraft architecture, the evolution of an antenna system, MER cruise stage antennas, antenna stacks, the heat-shield/back shell antenna, and lander and rover antennas. Additionally, the mission's science objectives are reviewed.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
For planetary lander missions, the most challenging phase of the spacecraft to ground communications is during the entry, descent, and landing (EDL). As each 2003 Mars Exploration Rover (MER) enters the Martian atmosphere, it slows dramatically. The extreme acceleration and jerk cause extreme Doppler dynamics on the X-band signal received on Earth. When the vehicle slows sufficiently, the parachute is deployed, causing almost a step in deceleration. After parachute deployment, the lander is lowered beneath the parachute on a bridle. The swinging motion of the lander imparts high Doppler dynamics on the signal and causes the received signal strength to vary widely, due to changing antenna pointing angles. All this time, the vehicle transmits important health and status information that is especially critical if the landing is not successful. Even using the largest Deep Space Network antennas, the weak signal and high dynamics render it impossible to conduct reliable phase coherent communications. Therefore, a specialized form of frequency-shift-keying will be used. This paper describes the EDL scenario, the signal conditions, the methods used to detect and frequency-track the carrier and to detect the data modulation, and the resulting performance estimates.
The twin Mars Exploration Rovers, Spirit and Opportunity, were launched on June 10, 2003, and July 8, 2003, from Cape Canaveral, Florida. Spirit and Opportunity were targeted for landings at Gusev Crater (arrival on January 4, 2004) and Meridiani Planum (arrival on January 25, 2004). The primary navigation challenge was to deliver each spacecraft to the desired atmospheric entry interface point with sufficient accuracy such that each lander would touch down within a specified landing ellipse (about 70 km x 5 km) determined to be safe for landing and also judged to be scientifically interesting. In order to achieve landing within the target ellipse, precise control of the inertial entry flight path angle (FPA) at atmospheric entry was required. The maximum allowable errors in FPA following TCM-5 (trajectory correction maneuver #5) at Entry (E) -2 days were +/-0.12 deg(3 sigma) for Spirit and +/-0.14 deg(3 sigma) for Opportunity. Achieving these entry delivery accuracies necessitated significant improvements to the interplanetary navigation system used for MER. These improvements included new processes and software for orbit determination, propulsive maneuver design, and entry, descent, and landing (EDL) trajectory simulation. The actual achieved atmospheric entry accuracies for Spirit and Opportunity significantly exceeded the requirements. At the navigation data cutoff for the TCM-5 final design, the orbit determination FPA knowledge error was 0.028 deg(3 sigma) for Spirit and 0.035 deg(3 sigma) for Opportunity. Because of exceptionally accurate navigation performance, TCM-5 (E - 2 days) and TCM-6 (E - 4 hours) were canceled for both Spirit and Opportunity. The actual landing locations (determined from in-situ Doppler tracking between the MER rovers and the Mars Odyssey orbiter) differed from the target landing points by 10.1 km (downtrack) for Spirit and 24.6 km (downtrack) for Opportunity. The majority of the landing position offsets for both landers was primarily caused by variations in atmosphere and spacecraft aerodynamic modeling from what was predicted. The amount of the landing position offset caused by navigation-only errors was only 3.3 km (uptrack) for Spirit and 9.7 km (downtrack) for Opportunity.
The twin Mars Exploration Rovers, Spirit and Opportunity, were launched on June 10, 2003(dagger), and July 8, 2003, from Cape Canaveral, Florida. Spirit and Opportunity were targeted for landings at Gusev Crater (arrival on January 4, 2004) and Meridiani Planum (arrival on January 25, 2004). The primary navigation challenge was to deliver each spacecraft to the desired atmospheric entry interface point with sufficient accuracy such that each lander would touch down within a specified landing ellipse (about 70 km x 5 km) determined to be safe for landing and also judged to be scientifically interesting. In order to achieve landing within the target ellipse, precise control of the inertial entry flight path angle (FPA) at atmospheric entry was required. The maximum allowable errors in FPA following TCM-5 (trajectory correction maneuver #5) at Entry (E) - 2 days were +/-0.12(deg) (3(sigma)) for Spirit and +/-0.14(deg) (3(sigma)) for Opportunity. Achieving these entry delivery accuracies necessitated significant improvements to the interplanetary avigation system used for MER. These improvements included new processes and software for orbit determination, propulsive maneuver design, and entry, descent, and landing (EDL) trajectory simulation. The actual achieved atmospheric entry accuracies for Spirit and Opportunity significantly exceeded the requirements. At the navigation data cutoff for the TCM-5 final design, the orbit determination FPA knowledge error was +/-0.028(deg) (3(sigma) ) for Spirit and +/-0.035(deg) (3(sigma)) for Opportunity. Because of exceptionally accurate navigation performance, TCM-5 (E - 2 days) and TCM-6 (E - 4 hours) were canceled for both Spirit and Opportunity. The actual landing locations (determined from in-situ Doppler tracking between the MER rovers and the Mars Odyssey orbiter) differed from the target landing points by 10.1 km (downtrack) for Spirit and 24.6 km (downtrack) for Opportunity. The majority of the landing position offsets for both landers was primarily caused by variations in atmosphere and spacecraft aerodynamic modeling from what was predicted. The amount of the landing position offset caused by navigation-only errors was only 3.3 km (uptrack) for Spirit and 9.7 km (downtrack) for Opportunity.
NASA relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft launched that does not have a computer on board that will provide command and control services. There have been recent incidents where software has played a role in high-profile mission failures and hazardous incidents. For example, the Mars Orbiter, Mars Polar Lander, the DART (Demonstration of Autonomous Rendezvous Technology), and MER (Mars Exploration Rover) Spirit anomalies were all caused or contributed to by software. The Mission Control Centers for the Shuttle, ISS, and unmanned programs are highly dependant on software for data displays, analysis, and mission planning. Despite this growing dependence on software control and monitoring, there has been little to no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Meanwhile, academia and private industry have been stepping forward with procedures and standards for safety critical systems and software, for example Dr. Nancy Leveson's book Safeware: System Safety and Computers. The NASA Software Safety Standard, originally published in 1997, was widely ignored due to its complexity and poor organization. It also focused on concepts rather than definite procedural requirements organized around a software project lifecycle. Led by NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard has recently undergone a significant update. This new standard provides the procedures and guidelines for evaluating a project for safety criticality and then lays out the minimum project lifecycle requirements to assure the software is created, operated, and maintained in the safest possible manner. This update of the standard clearly delineates the minimum set of software safety requirements for a project without detailing the implementation for those requirements. This allows the projects leeway to meet these requirements in many forms that best suit a particular project's needs and safety risk. In other words, it tells the project what to do, not how to do it. This update also incorporated advances in the state of the practice of software safety from academia and private industry. It addresses some of the more common issues now facing software developers in the NASA environment such as the use of Commercial-Off-the-Shelf Software (COTS), Modified OTS (MOTS), Government OTS (GOTS), and reused software. A team from across NASA developed the update and it has had both NASA-wide internal reviews by software engineering, quality, safety, and project management. It has also had expert external review. This presentation and paper will discuss the new NASA Software Safety Standard, its organization, and key features. It will start with a brief discussion of some NASA mission failures and incidents that had software as one of their root causes. It will then give a brief overview of the NASA Software Safety Process. This will include an overview of the key personnel responsibilities and functions that must be performed for safety-critical software.
The Maestro Science Activity Planner is a computer program that assists human users in planning operations of the Mars Explorer Rover (MER) mission and visualizing scientific data returned from the MER rovers. Relative to its predecessors, this program is more powerful and easier to use. This program is built on the Java Eclipse open-source platform around a Web-browser-based user-interface paradigm to provide an intuitive user interface to Mars rovers and landers. This program affords a combination of advanced display and simulation capabilities. For example, a map view of terrain can be generated from images acquired by the High Resolution Imaging Science Explorer instrument aboard the Mars Reconnaissance Orbiter spacecraft and overlaid with images from a navigation camera (more precisely, a stereoscopic pair of cameras) aboard a rover, and an interactive, annotated rover traverse path can be incorporated into the overlay. It is also possible to construct an overhead perspective mosaic image of terrain from navigation-camera images. This program can be adapted to similar use on other outer-space missions and is potentially adaptable to numerous terrestrial applications involving analysis of data, operations of robots, and planning of such operations for acquisition of scientific data.
Localization of the two Mars Exploration Rovers involved three independent approaches to place the landers with respect to the surface of Mars and to refine the location of those points on the surface with the Mars control net: 1) Track the spacecraft through entry, descent, and landing, then refine the final roll stop position by radio tracking and comparison to images taken during descent; 2) Locate features on the horizon imaged by the two rovers and compare them to the MOC and THEMIS VIS images, and the DIMES images on the two MER landers; and 3) 'Check' and refine locations by acquisition of MOC 1.5 meter and 50 cm/pixel images.
Current developments in immersive environments for mission planning include several tools which make up a system for performing and rehearsing missions. This system, known as the Rover Sequencing and Visualization Program (RSVP), includes tools for planning long range sorties for highly autonomous rovers, tools for planning operations with robotic arms, and advanced tools for visualizing telemetry from remote spacecraft and landers. One of the keys to successful planning of rover activities is knowing what the rover has accomplished to date and understanding the current rover state. RSVP builds on the lessons learned and the heritage of the Mars Pathfinder mission This paper will discuss the tools and methodologies present in the RSVP suite for examining rover state, reviewing previous activities, visually comparing telemetered results to rehearsed results, and reviewing science and engineering imagery. In addition we will present how this tool suite was used on the Mars Exploration Rovers (MER) project to explore the surface of Mars.
The Phoenix Lander, a NASA Discovery mission which lands on Mars in the spring of 2008, will rely entirely on UHF relay links between it and Mars orbiting assets, (Odyssey and Mars Reconnaissance Orbiter (MRO)), to communicate with the Earth. As with the Mars Exploration Rover (MER) relay system, non directional antennas will be used to provide roughly emispherical coverage of the Martian sky. Phoenix lander deck object pattern interference and obscuration are significant, and needed to be quantified to answer system level design and operations questions. This paper describes the measurement campaign carried out at the SPAWAR (Space and Naval Warfare Research) Systems Center San Diego (SSC-SD) hemispherical antenna range, using a Phoenix deck mockup and engineering model antennas. One goal of the measurements was to evaluate two analysis tools, the time domain CST, and the moment method WIPL-D software packages. These would subsequently be used to provide pattern analysis for configurations that would be difficult and expensive to model and test on Earth.
The Mars Reconnaissance Orbiter (MRO) continues its dual-mode mission of scientific exploration and programmatic support. Now in its 13th year of flight (and its 12th year in its low-altitude, sun-synchronous orbit around Mars), the spacecraft continues in its normal flight mode and its science instruments continue to acquire a treasure trove of data which is being used to study the Martian environment (surface, sub-surface, and atmosphere). To date (July 2018), more than 333 TB of scientific data have been returned to Earth. Building onto the 2017 IAC paper: “The Mars Reconnaissance Orbiter Mission: Continuing a Record of Exploration from Mars Orbit,” [1] this paper provides a 2018 status update on the MRO Mission. A signature event since the 2017 writing is the onset and evolution of a planet-encircling dust event (PEDE), the first such event since 2007. Additional recent science highlights for MRO include the discovery of mid-latitude ice cliffs, polar cap characterization, daily global mapping of the 2018 PEDE dust activity and the atmospheric thermal response, further characterization of the tantalizing recurring slope lineae (RSL), and continued detection of surface changes. Programmatically, UHF relay support for the Mars Science Laboratory (MSL) rover Curiosity and the Mars Exploration Rover (MER) rover Opportunity continues at a pace that provides the engineers and scientists operating those surface vehicles timely information to support their mission planning and science analysis. Most of the landing site characterization requests for the NASA Mars 2020 rover and the ESA ExoMars Rover/Surface Platform (RSP) missions have been completed, with final acquisitions delayed due to the obscuring dust haze from the current PEDE. In parallel, the flight team has faced new engineering challenges as the spacecraft has aged. The team has developed and is implementing actions that are aimed at stretching spacecraft battery life. A new all-stellar capability using the spacecraft’s star trackers now allows for normal spacecraft operations without IMUs. In addition to its current relay duties, MRO will be synchronized to provide critical communications support for the InSight Entry, Descent, and Landing (EDL) event on November 26, 2018, and will be readied to support InSight’s critical commissioning phase with UHF relay support and environmental characterization. A new split-pass relay capability has been developed which will allow MRO to relay with two surface vehicles in “close proximity” on the same overflight, i.e. the InSight lander and the Curiosity rover. Extended for another year of operations by NASA, this paper will highlight recent scientific progress and describe actions that will extend MRO’s life well into the 2020’s as a key element of the Mars Exploration Program.
MER SPICE Interface is a software module for use in conjunction with the Mars Exploration Rover (MER) mission and the SPICE software system of the Navigation and Ancillary Information Facility (NAIF) at NASA's Jet Propulsion Laboratory. (SPICE is used to acquire, record, and disseminate engineering, navigational, and other ancillary data describing circumstances under which data were acquired by spaceborne scientific instruments.) Given a Spacecraft Clock value, MER SPICE Interface extracts MER-specific data from SPICE kernels (essentially, raw data files) and calculates values for Planet Day Number, Local Solar Longitude, Local Solar Elevation, Local Solar Azimuth, and Local Solar Time (UTC). MER SPICE Interface was adapted from a subroutine, denoted m98SpiceIF written by Payam Zamani, that was intended to calculate SPICE values for the Mars Polar Lander. The main difference between MER SPICE Interface and m98SpiceIf is that MER SPICE Interface does not explicitly call CHRONOS, a time-conversion program that is part of a library of utility subprograms within SPICE. Instead, MER SPICE Interface mimics some portions of the CHRONOS code, the advantage being that it executes much faster and can efficiently be called from a pipeline of events in a parallel processing environment.
The Planetary Image Geometry (PIG) library is a multi-mission library used for projecting images (EDRs, or Experiment Data Records) and managing their geometry for in-situ missions. A collection of models describes cameras and their articulation, allowing application programs such as mosaickers, terrain generators, and pointing correction tools to be written in a multi-mission manner, without any knowledge of parameters specific to the supported missions. Camera model objects allow transformation of image coordinates to and from view vectors in XYZ space. Pointing models, specific to each mission, describe how to orient the camera models based on telemetry or other information. Surface models describe the surface in general terms. Coordinate system objects manage the various coordinate systems involved in most missions. File objects manage access to metadata (labels, including telemetry information) in the input EDRs and RDRs (Reduced Data Records). Label models manage metadata information in output files. Site objects keep track of different locations where the spacecraft might be at a given time. Radiometry models allow correction of radiometry for an image. Mission objects contain basic mission parameters. Pointing adjustment ("nav") files allow pointing to be corrected. The object-oriented structure (C++) makes it easy to subclass just the pieces of the library that are truly mission-specific. Typically, this involves just the pointing model and coordinate systems, and parts of the file model. Once the library was developed (initially for Mars Polar Lander, MPL), adding new missions ranged from two days to a few months, resulting in significant cost savings as compared to rewriting all the application programs for each mission. Currently supported missions include Mars Pathfinder (MPF), MPL, Mars Exploration Rover (MER), Phoenix, and Mars Science Lab (MSL). Applications based on this library create the majority of operational image RDRs for those missions. A Java wrapper around the library allows parts of it to be used from Java code (via a native JNI interface). Future conversions of all or part of the library to Java are contemplated.
This paper describes technology to support a new paradigm of space science campaigns. These campaigns enable opportunistic science observations to be autonomously coordinated between multiple spacecraft. Coordinated spacecraft can consist of multiple orbiters, landers, rovers, or other in-situ vehicles (such as an aerobot). In this paradigm, opportunistic science detections can be cued by any of these assets where additional spacecraft are requested to take further observations characterizing the identified event or surface feature. Such coordination will enable a number of science campaigns not possible with present spacecraft technology. Examples from Mars include enabling rapid data collection from multiple craft on dynamic events such as new Mars dark slope streaks, dust-devils or trace gases. Technology to support the identification of opportunistic science events and/or the re-tasking of a spacecraft to take new measurements of the event is already in place on several individual missions such as the Mars Exploration Rover (MER) Mission and the Earth Observing One (EO1) Mission. This technology includes onboard data analysis techniques as well as capabilities for planning and scheduling. This paper describes how these techniques can be cue and coordinate multiple spacecraft in observing the same science event from their different vantage points.
Humans have been fascinated with the idea of exploring Mars since the very beginning of the space age. Largely due to the belief that life may have at one time existed in some form, surface exploration has been the ultimate ambition of this exploration. Unfortunately engineers and scientists discovered early on that landing a spacecraft on the surface of Mars was to become one of the most difficult and treacherous challenges of robotic space exploration. At arrival to Mars, a spacecraft will be traveling at velocities between 4 and 7 km/s. 100% of this kinetic energy (KE) must be safely removed for a lander to deliver its payload to the surface. Fortunately Mars has an atmosphere substantial enough to allow the combination of a high drag heatshield and a parachute to remove 99% and 0.98% respectively of this kinetic energy. Unfortunately the atmosphere is not substantial enough to bring a lander to a safe touchdown. This means that an additional landing system is required to remove the remaining kinetic energy. On all previous successful missions the landing system has consisted of 2 major elements, a propulsion subsystem to remove an additional 0.002% (approx.50 - 100 m/s ) of the original KE and a final dedicated touchdown system. The first generation Mars landers used legs to accomplish touchdown. The second generation of Mars lander touchdown systems used airbags to mitigate the last few meters per second of residual velocity. NASA is currently developing a third generation landing system in an effort to reduce cost, mass and risk while simultaneously increasing performance as measured by payload fraction to the surface and accessible terrain roughness.
Following the successful landings of both Mars Exploration Rover (MER) vehicles at Gusev Crater and Meridiani Planum, respectively, their Athena suite of instruments is being used to study the geologic history of these two very different landing sites on Mars that had been selected on the basis of showing different types of evidence for aqueous processes in the planet s past. Utilizing the on-board instruments as well as the rovers mobility system, a wide range of physical properties investigations is carried out as well - the subject of this abstract - that provide additional information on the geology and processes at the sites. Results of the mission in general as well as of the physical properties studies thus far greatly exceed expectations in that observations and measurements by both vehicles show a rich variety in materials and processes: the Gusev site in the vicinity of the lander is remarkably flat and generally devoid of large rocks along traverses up to the time of this writing (approx.Sol 50) and suggestive of a deflated surface with generally only thin veneers of bright dust while exhibiting evidence of a widespread occurrence of a crust from cemented fines that has been observed to fail in the form of blocky clods when disturbed by vehicle rolling action; numerous small and shallow depressions - presumably created by impacts - are observed at the site which are infilled with bright, fine-grained material that likewise appears indurated and which was studied by a trenching experiment; small ripple bedforms are scattered across the site and were characterized in terms of particle size distributions. At the Meridiani site, studies so far - up to approx.Sol 33 - have focussed on soils and the rock outcrop encountered within the approx.20 m diameter crater that the spacecraft came to rest in: from a physical properties point of view, a mantle of dark, well-sorted, apparently basaltic sand with small to moderate cohesion has been of interest - and has been studied by a trenching experiment - as well as a fine-grained unit underlying the mantle at least locally within the crater. Rock grindings were accomplished successfully at both sites at the time of this writing, suggesting different strengths of the two targets (the basaltic rock nicknamed Adirondack at Gusev and the Meridiani rock outcrop) in addition to enabling compositional measurements below the original rock surfaces.