ACE Weekly 11/23/05 - 12/01/05 All ACE spacecraft subsystems are performing nominally. ============================================================================ Orbit/Attitude: No attitude maneuvers were completed this week. The next attitude maneuver is scheduled for Friday 12/02/05. ============================================================================ OCRs: DOY 335 (12/01/05) 1548-1556z SIS-034 Several Matrix detector strips were disabled recently but their firmware thresholds were not raised due to a limited number of available slots. This change will rearrange strips with raised firmware thresholds in order to optimize the performance of the instrument. ============================================================================ Ongoing Activities: Space Link Extension (SLE) - A successful Developer test in the TDF was performed on November 30. The first SLE delivery to the Library is expected December 14. The delivery to the FOT will not be until January. RIONet - String 3 is anticipated to move to the RIONet in January. The firewall in the TDF has not been completely configured and tested. The SA's would like the TDF configured with the firewall and RIONET before converting the MOC to the RIONET. ============================================================================ Extra Activities: DOY 333 (11/29/05) - The power supply on AC1WS3 was replaced and operations transitioned back to String 1 after the pass. Ref Anomaly G05-0144. ============================================================================ Anomalies: DOY 327 (11/23/05) G05-0144 AC1WS3 power supply dead After the pass the FOT noticed that AC1WS3 had died. Operations were manually moved to String 2 with String 3 as the backup for the holiday weekend. Operations remained on String 2 through Tuesday 11/29/05 (DOY 333). IMPACTS: ROBOTT would not have had a successful failover to String 2. The configuration files for the pass were not able to be copied from String 1 because AC1WS3 is the file server for the string. All the critical configurations were updated manually. Clock calibration was not done for two days. All data was captured during this time. DOY 331 (11/27/05) S05-0051 S3DPU_CONV_SEC_I Violated RH Limit S3DPU_CONV_SEC_I had 1 brief red high limit violation (RH >480 mA). The SSDIDLECTR was ~ 60. 2005-331 18:55:28 - 18:55:30 482.406mA Mark Popecki was notified. IMPACT: Unknown at this time. DOY 331 (11/27/05) G05-0145 DSS-16 Incorrect command mod index DSN monitor data indicated the station had an initial command mod index value of 0.43 dB. The value was changed to 1.81 dB. The nominal value is 1.69 dB. DR# N103221. IMPACT: The initial command was retransmitted 5 times before being accepted by the spacecraft. DOY 332 (11/28/05) G05-0146 Switch to Science Not Performed The FOT put the transition to science in a manual wait state in order for FDF to obtain their solution in ADC. The FOT never made the switch to go to science after FDF obtained their solution. IMPACT: Never transitioned to SCIENCE downlink format during the pass. All SCIENCE data was recovered from the SSR's. Weekly SWEPAM calibration was not executed until the next day. The final spacecraft state of health checks were not performed. DOY 332 (11/28/05) S05-0052 SSCPAM5V RH limit violation SSCPAM5V had 1 brief red high limit violation (RH >-4.5V). 2005-332 15:33:18 - 15:33:54 -4.490V Jim Raines notified. IMPACT: Awaiting instructions from Jim Raines. DOY 333 (11/29/05) S05-0053 SWICS limit violations SSCPAM5V had 3 brief red high limit violations (RH >-4.5V). 2005-333 22:09:39 - 22:10:03 -4.490V 2005-333 22:21:51 - 22:22:15 -4.490V 2005-333 22:33:16 - 22:33:40 -4.490V SSCGR20V had 2 brief yellow low limit violations (YL <= 17V). 2005-333 22:57:18 - 22:57:42 16.8 2005-333 23:57:09 - 22:57:45 16.9 Jim Raines notified. IMPACT: Awaiting instructions from Jim Raines. DOY 335 (12/01/05) G05-0147 DSS-27 - XMTR Problem Unable to command for 26 minutes due to transmitter problems at DSS-27. IMPACT: SSR redumps and final state of health checks were not performed. The redumps were done during the next support. All data recovered. DOY 335 (12/01/05) G05-0148 ROBOTT/C&C did not queue S_IDLE While waiting for G_END_DAY to complete, C&C decided to not execute s_idle instead of queuing the procedure to execute after G_END_DAY had completed. IMPACT: If the SSR is still in playback at EOT when the spacecraft switches to RTSW, the SSR will be stuck and will not transition to idle on its own. (Ref AR S05-0002 DOY 012). The SSR would be commanded to IDLE on the next support. DOY 335 (12/01/05) G05-0149 ROBOTT/C&C Froze After DSS-27 resolved the problem mentioned in Anomaly G05-0147, C&C froze for unknown reasons. IMPACT: There were only 2 minutes left in the pass so C&C was not rebooted. No pages were sent out stating that procedures had failed to complete. TPOCC was not terminated properly after the pass.