Data Controller Report Template

FLIGHT
SOL 1 END-OF-DAY DOWNLINK STATUS REPORT

Last updated: 5 July 1997, 02:30 pm PST, Data Controllers: Allen R. Sirota and Henry W. Stone

Summary Report
Retransmit Requests
Sequence Planning Recommendations & Constraints
Sequence Execution Status
Telemetry Volume
Traverse Hazards (Detected)
Subsystem Reports
Telemetry Processing Anomalies
Press Release

SUMMARY REPORT

Wakeup:

The rover woke up at 06:59:13 LTST via lander relay as expected.
Wakeup Health Check
- All A/D readings corrupted. Received associated suite of error messages indicating the A/D readings out of bounds.
- Suspect 12V converter boot problem identical to that previously experienced on the SIM vehicle.
- Battery usage counters will be off. Will have to compensate manually.
Subsequent auto health check indicates vehicle is healthy with the exception of the X accelerometer which indicates an accelerometer current anomoly (very low current). Internal temperatures about 15 degrees above predict (at 0C +/- 5C.
Lander landed on base petal and bounced 3 time with impacts of 18.7 g, 9.1 g, and 11.5 g, respectively.
Rover petal airbag retraction successful.
Lander orientation: Azimuth: +142 deg, Tilt: +2.45 deg
Rover petal orientation via Lander data (Left-Hand Rule):
- Pitch: -1.3 deg
- Roll: +2.0 deg

Sequence 50110W:

Sequence queued on schedule
Received first commanded Health Check, Cmd 1034 (Lvl 3) during Pass 1.
- A/D channel read problem cleared as expected.
- Rover Orientation via rover Accelerometers
  - Pitch: -1.2 deg
  - Roll: +2.40 deg
  - Essentially identical with lander estimate of rover petal pitch & roll.
- Error reported on X Accelerometer (low current reading).
  - X accelerometer failure count incremented to "3" (2 failures).
  - Despite accel current reading anomoly, accelerometer data consistent with being on Mars.
  - Believe that accels are functioning properly.
  - Subsequent auto health checks (level 2) should not cause failure count to increase since previous readings within accel sensor limits.
- Telecom performance looks great at this point in time!
  - LMFE Link Performance: 98%
  - Rover Link Performance: 90%
- Thermal
  - External Temps: ~ -50C (Nominal ... close to predicts)
  - Internal Temps: 0C +/- 5C (~ 15C above predicts)
- Power
  - All S/S elements nominal
  - Estimate Tau=0.5 (same as lander estimate)
Received a (31) command acknowledges later in the day (see below for more details)
The (31) packets finally retransmitted and received during Pass 4.
Data ended at cmd_seq_num 1034 (set parameter command just prior to going into first APXS hold comm subsequence).

Pass 2:

DID NOT receive any rover data.
Lander channels indicated that (31) APID 5 packets were sent during Pass 2.
Transfer frames apparently lost during start of Pass 2 due to a HGA signal lock timing problem with the DSN. Believe that these transfer frames contained the (31) APID 5 packets.
Requested for retransmit for Pass 3.
Ramp pre-deploy pan received. Airbag material seen on corner of rear ramp preventing its deployment. Deployment of front ramp also in question due to location of airbag material.
Stereo measurements indicate that surface of rover petal between 40-50 cm aabove surface.

Airbag Retraction:

Airbag retraction sequence built to further retract airbags. Petal lifted to approximately 40 deg, airbags retracted, petal returned to original position, new airbag assessment image taken.
Sequence uplinked prior to Pass 3.

Pass 3:

Retransmit sequence was not validated in time and was not sent to lander prior to start of Pass 3.
Again DID NOT receive any rover data.
Lander downlink channels indicate that no additional packets received from rover. Doesn't make sense. Rover should have transmitted more APID 4, 5, & 12 packets.
LMRE Link Performance GREATLY reduced. Down to ~24%. No explanation.
Received ramp deploy images S0009 and S0010 revealed that air bag re-retraction successful for front ramp, questionable for rear ramp. Modified S0010 sequence.

Pass 4:

Retransmit sequence finally sent to lander prior to start of downlink pass.
LMRE Modem was power cycled prior to start of Pass. Power cycling would automatically reinitialize LMRE UART. Action taken on hypothesis that UART in funny state and unable to properly complete rover comm sessions.
Received all (31) APID 5 packets previously lost.
Lander downlink channels still indicate that lander has not received any more packets from rover. LMRE power cycling apparently had not effect.
LMRE Link Performance continues to be poor ... ~20%. No rover data to access Rover Link Performance.

Sequences 50130 & 50140:

Decided very late to release the front ramp and the rover and to queue sequences 50130 and 50140 ... in the blind.
Attempted to perform an additional downlink pass prior to earth set but were to late.
Did not receive confirmation of receipt of S0020 by lander. Subsequent analysis seems to indicate that it mostly likely was not sent in time.

Rover/Lander Comm problem documented under Telecom S/S detailed report.

RETRANSMIT REQUESTS

NONE

SEQUENCE PLANNING RECOMENDATIONS

MODIFY with Nominal Sequence Plan

Operational Constraints (For next sequence)

Send SHORT sequence morning of Sol2 prior to sunrise with at least the following commands:
- Abort
- Clear Errors
- Read Mem (Persistent state table)
- Set Param (Disable Hold Comm)
Flush rover sequences prior to sunrise.

Operational Constraints (General)

None

SEQUENCE EXECUTION STATUS & VEHICLE STATE

SEQUENCE EXECUTION STATUS:

Execution:	Nominal
State:	Executing
Wakeup:	Solar Power, 97/185-06:59:17 LTST
Crit Errors:	0E01, due to A/D/12V Conv init problem.
Cmds Skipped:	None
Telem Anomalies:	None ... excluding rover/lander comm problem
Last Command:	1037, Set Parameter

Most likely executing runout of sequence 50110W assuming that late transmisson of S0022 did not make it to the lander.

VEHICLE STATE:

(AS OF COMMAND: 1034, Health Check SCET: 7/4/97 21:21:14.623, MLST: 07:21:58 )


Mission Phase:	Pre-Release
Mode:	Running
Config:	Unreleased, Stowed
Power:	Nominal
Device Status:	All devices GOOD except X accel
Temp (Internal):	15 deg above predict
Temp (External:	Nominal
Temp:(Modem):	Nominal

   Parameter    Initial    Final    Parameter     Initial  Final
----------------------------------------------------------------
X Position (m)    0.000    0.000   LBogey (deg)    ??.??  +38.56
Y Position (m)    0.900    0.900   RBogey (deg)    ??.??  +38.40
Heading  (deg)    0.0      0.0     Diff   (deg)    ??.??  -40.72

Pitch    (deg)    ?.??     -2.4   (+ Pitch -> Front down)
Roll     (deg)    ?.??     +1.2   (+ Roll  -> Roll to Starboard)

ADM Pos  (deg)    ?.??   -29.44

LFS      (deg)     ?.?      -0.6     RFS    (deg)    ?.?    0.6
LRS      (deg)     ?.?      +1.9     RRS    (deg)    ?.?   -1.3
----------------------------------------------------------------

BATTERY STATE/USAGE

              Total           Battery Remaining (Amp*hrs)
Category    Allocation      Initial    Final    *Predicted
--------------------------------------------------------------
Operations      10            10         ?	   ?
Science         10            10         ?	   ?
Technology      10            10         ?	   ?
Reserve          6             6         ?	   ?
--------------------------------------------------------------
Total           36            36         ?         ?

* at completion of current sequence assuming nominal execution
** anomalous value due to previously noted A/D initialization problem.  Affected all subsequent battery usage calculations.

ADM Bumper Solar
UL UR B RB LB LR RR RF LF
Mask ? ? ? ? ? ? ? ? ?
State 0 0 1 0 0 0 0 0 0

	ADM	Bumper	Solar
UL	UR	B	RB	LB	LR	RR	RF	LF
Mask	?	?	?	?	?	?	?	?	?
State	0	0	1	0	0	0	0	0	0

ERROR FLAGS
Skip GenFail InvalidCmd WEB_Hot NoPwr NonTrav DevNA DevFail Timeout
Mask ? ? ? ? ? ? ? ? ?
State 0 0 0 0 0 0 0 0 0

	ERROR FLAGS
Skip	GenFail	InvalidCmd	WEB_Hot	NoPwr	NonTrav	DevNA	DevFail	Timeout
Mask	?	?	?	?	?	?	?	?	?
State	0	0	0	0	0	0	0	0	0

SUBSYSTEM STATUS:

S/S	Status	Comments
C&N	Off-Nominal	Accel Cur low, CCD Cur High
MTM	Nominal	None
Power	Off-Nominal	Due to 12V converter problem
Telecom	Off-Nominal	Rover/Lander Comm failing

TRAVERSE HAZARDS (DETECTED)

NONE

TELEMETRY VOLUME

APID	Name	Predicted #Pkts	Actual #Pkts	Predicted #Mbits	Actual #Mbits
		Predicted #Pkts	Actual #Pkts	Predicted #Mbits	Actual #Mbits
4	Health/Status		18		0.04235
5	Ops/Engr (Low)		134		0.04731
6	Seq Status		4		0.00192
7	Error Rep		1		0.00320
8	Image (Sci)		55		0.75525
9	Image (Tech)		0		0.00000
10	Image (Land)		119		1.81090
12	APXS Results		6		0.05136
23	Ops/Engr (High)		0		0.00000
24	Image (Auto)		0		0.00000
25	Image (Ops)		90		1.22136
29	Traverse		4		0.03486
29	TOTAL		431		3.96850

*All data downlink on Sol INCLUDING retransmitted data.

SUBSYSTEM REPORTS

NAVIGATION PERFORMANCE:

C&N subsystem components essentially all performing as expected.

Accelerometer current very low (4.7 mA). Sensor readings, however, appear to be nominal and consistent with petal orientation.
CCD current higher than expected. Suspect 12 Volt converter problem (i.e., it may have a "soft" output.
No constraints to impose upon sequence planning at this point in time.

THERMAL PERFORMANCE:

Thermal subsystem components all performing as expected.

Rover internal temps ~ 15C above predicts. Nothing to be terribly concerned about. Will monitor carefully ... if we get any more useful data.
Y-pin heater commanded on at EOD (confirmed).
No constraints to impose upon sequence planning

COMMUNICATIONS PERFORMANCE:

Telecom subsystem components initially performing just fine ... then performance degraded severly. The following is a summary of the possible causes of the problem as discussed during a midnight team meeting.

Hold-Com Scenario
- Garbled Frames
- All ?
- Not Probable
LMRE low power latchup
- UART .vs. LMRE
- Both seem to be fine (Glen Reeves)
- Will turn on diagnostics packets with real-time command tomorrow
Part Failure ... LMRE Regulator?
HGA Config & Freq shift
- Must have both conditions
- Crystal problem
- Physical config of HGA (scattering creating/moving null)
- Standup and deploy of antennae may fix problem ... if we unstow.
- Performance changed (degraded) as day went on.
Lander S/W ... Glen Reeves sees no evidence of this.
LMRE CTS didn't go active error
- has happened often in ORTs
- expected
High Bus Voltage
- 35 V on lander
- Ron Banes says NO
Rover/Lander UART crystal drift
Rover CPU crystal problem
- Highly unlikely (Henry Stone).
- Was a crystal startup problem.
- Never started ok and then went bad!

MOBILITY PERFORMANCE:

Mobility subsystem components all performing as expected.

Images indicate rover physically healthy (i.e., no visible damage to solar panel, etc).
No constraints to impose upon sequence planning.

POWER PERFORMANCE:

Power subsystem components all performing as expected with possible exception of 12 volt converter

Accels and CCD's powered by 12 volt converter. Their current draws are not consistent with predicts or cruise health check data.
No explanation at present for anamolous behavior of 12 V converter
Battery usage data will have to monitored manually due to initial A/D readings all being "FF".
No constraints to impose upon sequence planning at this point in time.

TELEMETRY PROCESSING ANOMALIES

LabView Version 4.0 not configured properly. SubVi menu has (2) MAE vi's and a number of SubVi's are dimmed (i.e., no selectable). "Current" pointer set to Version 3.0

PRESS RELEASE

To Be Completed

Web Page Authors: Henry W. Stone and Allen.R.Sirota

All information on this site, including text and images describing the Rover is copyright © 1997, Jet Propulsion Laboratory, California Institute of Technology and the National Aeronautics and Space Administration.

FLIGHT SOL 1 END-OF-DAY DOWNLINK STATUS REPORT

FLIGHT
SOL 1 END-OF-DAY DOWNLINK STATUS REPORT