Let's take a look at the telecom experiments we want to perform while on Mars...

Basically, experiments with the rover telecommunications system are limited to evaluation of the health and performance data of the rover at different surface locations. The radios do not output received signal power or AGC (Automatic Gain Control) voltage telemetry values so no direct measurements of ground conductivity or permittivity can be made. We may have to wait for the 2001 Mars mission to get that data and perform radio science experiments. But we can determine telecom hardware and system performance as a function of location, time and temperature. Toward the end of the extended mission we may attempt to navigate the rover beyond the 10 meter radius limit imposed for the primary mission. Beyond 10 meters the telecom system should perform well, but will become more and more sensitive to changes in terrain and rock sizes. Also, beyond 10 meters the IMP camera, which is used to help the rover drivers and sequence planners in developing the test sequences, will not provide very good narrow angle shots of the rover and surrounding terrain, so driving the microrover will be more challenging.

That is the extent of the radio science we can do with this telecommunications subsystem, which was designed to be simple and reliable. Next time we put a microrover on Mars hopefully we'll have much more radio hardware engineering telemetry that will allow us to perform complex telecom experiments and radio science.

Rover Mission Operations...

Rover mission operations is performed at JPL in the Space Flight Operations Facility (SFOF building 230). The Rover Engineering Analysis Team (EAT) is comprised of a group of engineers whos job it is to analyze the rover engineering data as it's received during downlinks. The downlinks happen two or more times during a Martian sol while earth is still within view of the lander HGA (High Gain Antenna). Most of the engineers involved in mission operations are those who actually designed, built and tested the rover flight hardware. They were the logical choice for mission operations support since they know the most about the hardware. The different sub-systems represented are Power, Mobility, Control & Navigation, Data Control, Rover Coordination and of course Telecommunications. Analysis of the engineering data is done as soon as it is received, primarily to look for validation of the rover sequence of operations along with any problems we may have encountered. If there are any operational problems they are carefully assessed by the proper sub-system person(s) and an advisement is given on a solution to the data controller and to the Rover test coordinator. At the end of each downlink analysis session a verbal 'GO' or 'NO-GO' is given to the data controller. A 'GO' means to proceed as planned, a 'NO-GO' means that we may not proceed until the problem is resolved. Finally at the end of that day's sequence of rover operations, a written report is created by the data controller and delivered to the Project test conductor and presented to the press. Additionally each rover sub-system creates a written report summarizing that day's activities and analysis.

Below are some images of the Rover Engineering team members and various work areas...