Aqua Daily Report May 9, 2002 1130 GMT – May 10, 2002 1130 GMT
The following activities were completed:
- The Master Command Load (MCL) for day 130 was loaded at 1908z and activated at 0000z.
- The daily spacecraft ephemeris table was loaded at 2040z.
- The FMU/SSR Reconfiguration SCSs were loaded at 2206z.
- Successfully transitioned from Earth Point Mode to Fine Point Mode (FPM) at 1836z. The spacecraft is currently maintaining FPM within the Aqua science tolerances. Activities included:
- Enabled Attitude Propagation with the IRU.
- Activated Star Trackers.
- Uplinked Attitude Quaternion.
- Initialized Star Identification.
- Enabled Fault Management related to Fine Point Mode.
- The Ultra Stable Oscillator (USO) Frequency Adjust to GIRD and GIIS occurred at 2127z. The adjustment was performed to calibrate the on-board clocks. To minimize clock adjusts this will not be scheduled for more than once per week.
- Performed AIRS Memory Dump at 0616z.
- The Direct Broadcast Control SCSs were uploaded at 0314z.
- Loaded and dumped the Delta-V Maneuver SCSs at 0935z in preparation for the Delta-V demo Yaw burn on May 10.
The following activities are scheduled for the next 24 hours:
- Uplink and activate the Master Command Load (MCL) for day 131.
- Uplink daily spacecraft ephemeris with continuity check.
- Activities related to the Delta-V demonstration maneuver include:
- Open Isovalve
- Turn ON Cat Bed Heater
- Demonstration of Yaw Maneuver to Offset Attitude
- Zero Duration Burn
- Yaw Maneuver to Nominal Attitude
- Turn OFF Cat Bed Heaters
- Re-enable FPM Fault management
- Load and Dump Delta-V Maneuver SCSs for demo burn
- X-Band Communication Subsystem Activation
- First planned X-Band SSR Playback, containing State-of-Health Data
- Partition SSR for Science Data
- Route Science Data to SSR only
- Enable CERES Instrument Science Transactions
- First Dump of SSR with Science Partitioning
Aqua Spacecraft Status:
- Spacecraft State is currently Standby.
- GNC Mode is Fine Point Mode, HiFi Ephemeris.
Aqua Instrument Status:
- AIRS is in Decontaminate state, Quiet bus is ON, Noisy bus is ON, Cryocooler is OFF, Scan mirror rotating is OFF and earth shield is CLOSED.
- AMSR-E is in Modified Sleep mode, rotating at 4 RPM.
- AMSU A1 is in Survival mode and the antenna is in the TARGET position.
- AMSU A2 is in Survival mode and the antenna is in the TARGET position.
- CERES Aft is in Safe mode and the covers are CLOSED.
- CERES Fore is in Safe mode and the covers are CLOSED.
- HSB is in Survival mode and the antenna is in the TARGET position.
- MODIS is in Standby mode, Nadir Door is Unlatched and CLOSED, Solar Diffuser Door is Unlatched and CLOSED, and the Space View Door is Unlatched and CLOSED.
Activities Deferred:
Spacecraft transition to Fine Point Mode (FPM) which was originally delayed, was successfully completed on May 9th.
- Delta-V demonstration Yaw Maneuver is scheduled for Friday, May 10.
- Remaining activation activities impacted by the FPM delay will be rescheduled.
Anomalies:
- The ground system has experienced 2 anomalous passes on SGS, 1 occurred on May 6, and 1 occurred on May 7 where data were missing in S-Band playbacks.
- (Correction to status reported on May 9) SSR data were replayed in subsequent passes to ensure no data loss. Later analysis of the original playback proved that no SSR data were lost in the original playback.
- EOC Mission Operations Systems (EMOS) personnel and CSOC personnel have concluded that the actual playback data were good, and only idle frames at the beginning of the pass are affected. The FOT did not anticipate the affects of the low power levels of the RF signal at the horizon (manifested as Reed-Solomon corrupted CADUs) because all pre-launch testing was done with the RF signal at a constant power level. The phenomenon is seen only at the Norway stations because of the Norwegian antennas position on the plateau, they can see the true horizon (zero degrees elevation). The stations are operating within normal parameters.
- There is an apparent misalignment of approximately 0.2 degrees between Star Tracker Assembly (STA) 1 and STA2.
- Most probable causes are:
- Measurement or mathematical error in generation of original alignment matrices.
- Rotation about STA1 boresight axis.
- Rotation about STA2 Y-axis.
- Actions underway:
- For probable cause (i) a comprehensive review of measurements, calibrations, and calculations is being performed by independent alignment experts at TRW Space Park
- For probable causes (ii) and (iii) discussion has been initiated with instrument teams in case geolocation assistance is needed to distinguish between (ii) and (iii).
- Most probable causes are:
- Commands dropped for AIRS (May 6 and 7) and MODIS (May 7) (formerly referred to as Code Word Errors).
- Caused by AGS and SGS transmitting with incorrect polarization. Ground stations have been reconfigured and communications are nominal.
- Command Telemetry Controller (CTC) received incomplete transfer frames from Transponder Interface Electronics (TIE) (formerly CLCW errors not associated with commands). This anomaly has not affected the ability to command the spacecraft and it has been safe at all times. There have been a total of 13 occurrences.
- Most probable cause is rogue codeblocks processed by TIE and sent to CTC in the absence of, or as a result of, anomalous commanding. Potential sources of these rogue codeblocks are:
- Inadvertent reception of another spacecrafts CCSDS uplink.
- TIE processing random data bits produced by transponder when no signal is present.
- Anomalous uplink near AOS.
- Actions underway for probable causes (i) through (iii).
- Patch loaded to telemeter codeblock data. Awaiting event recurrence and fault data processing.
- Organizing and analyzing all existing telemetry data.
- Analyzing flight software functions.
- Analyzing transponder/TIE design/operation.
- Reviewing ground network pre-contact operations.
- Correlating event times with proximity of other spacecraft using CCSDS.
- Most probable cause is rogue codeblocks processed by TIE and sent to CTC in the absence of, or as a result of, anomalous commanding. Potential sources of these rogue codeblocks are: