FLIGHT SOL 2 Final Scenario

Final FLIGHT Scenario
Sol 2 scenario, 7/5/97

Assumptions:

Nominal landing
If sequences uplinked on SOL 1 (50130 and 50140) were activated, considered unlikely, the rover may have unstowed.
Rover-lander communications anomaly in effect:
- Several possible scenarios for the observed communications problem have been considered:
  - Rover hold_comm parameter is set to prevent communications (unlikely)
  - LMRE modem is in low power latchup state (unlikely, since power cycling had no effect, and some communications seems to be taking place)
  - Part failure (possible, but likely not recoverable)
  - HGA configuration and frequency drift in modems has made link marginal in rover's current location and configuration (possible, would probably require rover standup or antenna deployment to correct)
  - Lander software configuration problem is impacting communications/telemetry handling (no evidence yet to support this)
  - LMRE CTS is failing to go active (has occurred in ORT's, possible)
  - High bus voltage condition (no causal relationship)
  - Rover CPU crystal problem (unlikely)
  - Rover/lander UART crystal drift

Rover Activities:

Solar wakeup of rover
Send short sequence (50210T) to reset hold_comm parameter on rover, and determine if a short uplink can be accepted by the rover.
Follow this sequence with a more extensive conservative runout sequence (50220T)
If communications is reestablished, perform an APXS retraction and rover unstow.
If rover unstow is completed nominally, plan and uplink a ramp egress sequence.

Last Updated: 7/5/97