STATUS: DONE

Previous sequence 50520D will nominally be aborted at command [?]

MISSION SEQUENCE PLANNER REPORT

SEQUENCE DESCRIPTION

• Sol 6B Scenario

• Sequence 50620A (.pef file, viewable as text)
• Command-by-Command Description* (w/telemetry estimate)

• Roverview Traverse Graphic

• Vehicle Positions:

  No change in vehicle position expected during execution of 50620A.

• Pointing for IMP Images of Rover:

  Image Type	X (m)	Y (m)	Z (m)	Imaging Opportunity
  None

  
  

• Telemetry Volume Estimates

  • Sol 6 Downlink (by APID)
    Predicted telemetry volume generated between activation of sequence 50620A from nominal start to nominal abort [6245]

    SUMMARY BY TELEMETRY APID:

    APID	Name	Predicted #Pkts	Predicted #Mbits
    4	Health Status	21	0.04889
    5	Ops/Engr	12	0.00586
    6	Sequence Status	31	0.00755
    7	Error Reports	0	0.00000
    8	Science Imaging	0	0.00000
    9	Technology Imaging	0	0.00000
    10	Lander Imaging	0	0.00000
    12	APXS Results	0	0.00000
    23	Priority Ops/Engr.	0	0.00000
    24	Auto Imaging	0	0.00000
    25	Ops Imaging	0	0.00000
    29	Traverse Reporting	0	0.00000
    	TOTAL	64	0.06230

  • 50620A Full Sequence until Nominal Abort (by APID)
  • 50620A RAIF Comment List (comments appear as skipped commands in telemetry stream)

  • 50620A Full Sequence Summary for PLAN-IT

SEQUENCE IMPLEMENTATION REPORT

• SEQUENCE EXECUTION ISSUES:

• SEQUENCE PLAN ASSESSMENT:
  Recommendations for Downlink Assessment Team
  1. None
  Flight Rules Waived:
  1. None
  Macros Modified:
  1. None
  Incorporation of EAT Operational Constraints (this sequence)
  Operational Constraints (For next sequence)
  1. Set modem heating to 10 minutes
  2. Set modem reheating to 5 minutes
  3. Heat modem for 5 minutes prior to transmission of large messages (e.g., images) IF messages being transmitted prior to 14:00 LST.
  4. Perform Level 2 Health Checks every hour during the night to acquire night-time thermal profile.
  Operational Constraints (General)
  1. Read persistent state table at approximately 14:00 LST every Sol so that we get most recent state just prior to the end of the afternoon downlink.
  2. We MAY want to consider clear errors (except INVALID COMMAND flag) immediately before abSOLute wait commands to insure that the waits are not skipped and to maintain synchronization with lander activities.

  Incorporation of Operational Constraints
  1. All taken into consideration

SCIENCE/TECHNOLOGY OBJECTIVES REPORT

PRESS RELEASE