ACE Weekly 11/04/05 - 11/10/05

All ACE spacecraft subsystems are performing nominally.

A new Real-Time Engineer, Himanshu Patel, joined the ACE FOT on
11/07/05 to replace a member that left the team. 

=======================================================================
=====
Orbit/Attitude:

        Type         Attitude     
        Date         11/10/05     
        DOY          314 2005     
        Thrusters    2R 4R+ 4R-   
        Duration     9:20 min     
        Start Time   13:46:18z    
        Stop Time    13:55:38z    
        Firing       48 pulses    

The next attitude maneuver is scheduled for Tuesday 11/22/05.

=======================================================================
=====
OCRs:

DOY 313 (11/09/05)  1626-1641z  SIS-033
Leakage currents on HV side of Matrix detector M1B have been steadily
increasing, resulting in higher noise on detector strips. By turning
off 3 noisy strips and raising the M12B bias voltage from 2.8 to 3.3V
we will explore the effects of slightly higher bias voltage on the
leakage current and the counting rates of this detector. If the results
are positive we will leave the higher bias voltage in place.

CRIS-012 is scheduled for execution on Friday 11/11/05 to dump the
content of the CRIS error counters.

=======================================================================
=====
Ongoing Activities:

Space Link Extension (SLE) - ACE SLE development has been become a top
priority.  The next DTF-21/Developer test is targeted for mid-November
and will verify TDF firewall configuration.  The next software test
including the long duration test with DTF-21 is targeted for November
30.  The target date for the developer's MOC system test is in the
first week of December followed by a delivery in the second week.  

RIONet - String 3 is anticipated to move to the RIONet by the end of
month.

=======================================================================
=====
Extra Activities:

DOY 313 (11/09/05) - MOC Contingency Exercise
The Sys Admins disconnected the String 3 Front End and WS3 drives and
connected external drives for the MOC contingency.  The ACE FOT was
tasked to send a /no_op command to the spacecraft utilizing a minimum
configuration that was installed on string 3 using external drives.
After successfully sending the /no_op command the SAs dismantled the
drives and the FOT sent another /no_op command (successfully) after
returning to the nominal configuration.  The contingency exercise was
successful in the ACE MOC.
As a result of the Contingency Exercise, the number of commands sent to
the spacecraft did not equal the number of echoes since two commands
were sent from the alternate string.  

=======================================================================
=====
Anomalies:

DOY 310 (11/06/05)  G05-0138  ROBOTT Killed Procedure Prematurely
The procedure S_OPS_PLBK_COMPLETE started immediately after
ULEIS_MOTOR_ERROR completed.  However, results checking for ULEIS
hadn't completed before starting the next procedure.  ROBOTT
erroneously killed the procedure S_OPS_PLBK_COMPLETE when the results
checking for ULEIS finished.
05-310-21:44:06.6    1069 Procedure ULEIS_MOTOR_ERROR completed.

05-310-21:44:09.4    1070 Procedure S_OPS_PLBK_COMPLETE started.

05-310-21:46:37.9    1005 Op In (genie:gensaa) killp all

05-310-21:46:37.9    1021 Killed procedure "S_OPS_PLBK_COMPLETE".

On Day 05311, the FOT confirmed there were no redumps needed.
DR CDSID 21122 was opened on 12/08/04 to document this existing
problem.  Also reference CDSID# 0021270.

DOY 311 (11/07/05)  G04-0125  Data Server Connection lost (appended)
FOT received page: "Data Server Connection Lost - Too Late for
FAILOVER. 15 minutes to EOT Sys-ac1ws3
It is still unknown why this message occurs in ROBOTT after the pass is
completed.  DR CDSID 21091 was opened in November 2004 for this
problem.

DOY 313 (11/09/05)  G05-0139  G_ACEUP Executed Twice
The FOT received notification from that G_ACEUP executed twice.  From
the log files, the FOT was unable to come to a conclusion why this
happened.  The C&C log files were sent to the ROBOTT developers for
further analysis.  
IMPACT: C&C rebooted for unknown reasons