MESUR Pathfinder Mission Operations Concepts
Explore the source record for details and available documents.
Engineering topics
Publications and source records attributed to Dias, William C..
Explore the source record for details and available documents.
The Mars Pathfinder Project plans a December 1996 launch of a single spacecraft. After jettisoning a cruise stage, an entry body containing a lander and microrover will directly enter the Mars atmosphere and parachute to a hard landing near the sub-solar latitude of 15 degrees North in July 1997. Primary surface operations last for 30 days. Cost estimates for Pathfinder ground systems development and operations are not only lower in absolute dollars, but also are a lower percentage of total project costs than in past planetary missions. Operations teams will be smaller and fewer than typical flight projects. Operations scenarios have been developed early in the project and are being used to guide operations implementation and flight system design. Recovery of key engineering data from entry, descent, and landing is a top mission priority. These data will be recorded for playback after landing. Real-time tracking of a modified carrier signal through this phase can provide important insight into the spacecraft performance during entry, descent, and landing in the event recorded data is never recovered. Surface scenarios are dominated by microrover activity and lander imaging during 7 hours of the Mars day from 0700 to 1400 local solar time. Efficient uplink and downlink processes have been designed to command the lander and microrover each Mars day.
Explore the source record for details and available documents.
RISK D/C is prototype computer program assisting in attempts to do program risk modeling for Space Exploration Initiative (SEI) architectures proposed in Synthesis Group Report. Risk assessment performed with respect to risk events, probabilities, and severities of potential results. Enables ranking, with respect to effectiveness, of risk-mitigation strategies proposed for exploration program architecture. Allows for fact that risk assessment in early phases of planning subjective. Although specific to SEI in present form, also used as software framework for development of risk-assessment programs for other specific uses. Developed for Macintosh(TM) series computer. Requires HyperCard(TM) 2.0 or later, as well as 2 Mb of random-access memory and System 6.0.8 or later.
Missions are being proposed which involve landing a varying number (anywhere from one to 24) of small mobile spacecraft on Mars. Mission proposals include sample returns, in situ geochemistry and geology, and instrument deployment functions. This paper discusses changes needed in traditional space operations methods for support of rover operations. Relevant differences include more frequent commanding, higher risk acceptance, streamlined procedures, and reliance on additional spacecraft autonomy, advanced fault protection, and prenegotiated decisions. New methods are especially important for missions with several Mars rovers operating concurrently against time limits. This paper also discusses likely mission design limits imposed by operations constraints .
A NASA Risk Team has developed a method for the application of risk management to the definition of robotic mission requirements for the Space Exploration Initiative. These requirements encompass environmental information, infrastructural emplacement in advance, and either technology testing or system/subsystems demonstration. Attention is presently given to a method for step-by-step consideration and analysis of the risk component inherent in mission architecture, followed by a calculation of the subjective risk level. Mitigation strategies are then applied with the same rules, and a comparison is made.
Results of studies of robotic missions to the moon and Mars planned under the U.S. Space Exploration Initiative are summarized. First, an overall strategy for small robotic missions to accomplish the information gathering required by human missions is reviewed, and the principal robotic mission requirements are discussed. The discussion covers the following studies: the Lunar Observer, the Mars Environmental Survey mission, Mars Sample Return missions using microtechnology, and payloads.
A spectrum of concepts for planetary rovers and rover missions, is covered. Rovers studied range from tiny micro rovers to large and highly automated vehicles capable of traveling hundreds of kilometers and performing complex tasks. Rover concepts are addressed both for the Moon and Mars, including a Lunar/Mars common rover capable of supporting either program with relatively small modifications. Mission requirements considered include both Science and Human Exploration. Studies include a range of autonomy in rovers, from interactive teleoperated systems to those requiring and onboard System Executive making very high level decisions. Both high and low technology rover options are addressed. Subsystems are described for a representative selection of these rovers, including: Mobility, Sample Acquisition, Science, Vehicle Control, Thermal Control, Local Navigation, Computation and Communications. System descriptions of rover concepts include diagrams, technology levels, system characteristics, and performance measurement in terms of distance covered, samples collected, and area surveyed for specific representative missions. Rover development schedules and costs are addressed for Lunar and Mars exploration initiatives.
The goal is to suggest the scheduling and control functions necessary for accomplishing mission objectives of a fairly autonomous interplanetary mobile spacecraft, while maximizing reliability. Goals are to provide an extensible, reliable system conservative in its use of on-board resources, while getting full value from subsystem autonomy, and avoiding the lure of ground micromanagement. A functional layout consisting of four basic elements is proposed: GROUND and SYSTEM EXECUTIVE system functions and RESOURCE CONTROL and ACTIVITY MANAGER subsystem functions. The system executive includes six subfunctions: SYSTEM MANAGER, SYSTEM FAULT PROTECTION, PLANNER, SCHEDULE ADAPTER, EVENT MONITOR and RESOURCE MONITOR. The full configuration is needed for autonomous operation on Moon or Mars, whereas a reduced version without the planning, schedule adaption and event monitoring functions could be appropriate for lower-autonomy use on the Moon. An implementation concept is suggested which is conservative in use of system resources and consists of modules combined with a network communications fabric. A language concept termed a scheduling calculus for rapidly performing essential on-board schedule adaption functions is introduced.
Results of FY88 studies of a sample-collecting Mars rover are presented. A variety of rover concepts are discussed which include different technical approaches to rover functions. The performance of rovers with different levels of automation is described and compared to the science requirement for 20 to 40 km to be traversed on the Martian surface and for 100 rock and soil samples to be collected. The analysis shows that a considerable amount of automation in roving and sampling is required to meet this requirement. Additional performance evaluation shows that advanced RTG's producing 500 W and 350 WHr of battery storage are needed to supply the rover.
A frame-based expert scheduling system shell, PLAN-IT, is developed for spacecraft scheduling in the Request Integration Phase, using the Comet Rendezvous Asteroid Flyby (CRAF) mission as a development base. Basic, structured, and expert scheduling techniques are reviewed. Data elements such as activity representation and resource conflict representation are discussed. Resource constraints include minimum and maximum separation times between activities, percentage of time pointed at specific targets, and separation time between targeted intervals of a given activity. The different scheduling technique categories and the rationale for their selection are also considered.
A frame-based expert scheduling system shell, PLAN-IT, is developed for spacecraft scheduling in the Request Integration Phase, using the Comet Rendezvous Asteroid Flyby (CRAF) mission as a development base. Basic, structured, and expert scheduling techniques are reviewed. Data elements such as activity representation and resource conflict representation are discussed. Resource constraints include minimum and maximum separation times between activities, percentage of time pointed at specific targets, and separation time between targeted intervals of a given activity. The different scheduling technique categories and the rationale for their selection are also considered.