ACE Weekly 09/25/2012 - 10/01/2012

All ACE spacecraft subsystems are performing as expected.

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

No maneuvers were completed this week.  The next attitude maneuver is
scheduled for Monday 10/08/2012.

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

None

========================================================================
Activities:

Data Capture:  100%  DOY 267-274 2012

On 9/25/2012 (DOY 269), a DSN Project Interface Test (PIT) for software
upgrades to DSN's Uplink Tracking and Command Subsystem (UPL v10.5) and
Downlink Telemetry and Tracking (DTT v11.1) was completed.  No problems
were found from the MOC, but DSN reported issues with conscan.  Note,
conscan configuration was part of the test even though ACE does not use
conscan because of solar interference.  Also, no FOT review was done of
DSN Monitor data or 0161 header information.  The FOT used to review
this data (before 2004) which had helped to uncover problems in previous
DSN tests.

On 10/1/2012 (DOY 275), a WS1 Engineering Test was performed with all
regular pass activities.  There was a realtime (vc1) telemetry stop at
1439z and an hourly disconnect/reconnect of the playback (vc2)
connection.  All other activities were successful.  Another test is
scheduled for Friday 10/5/2012 (DOY 279) to see if these issues recur.

WS1 resolved the LEO-T timestamp problem where the header occasionally
read 1/1/2012 0000z.  The millisecond problem was with the MMOC software
and has been fixed.  The WS1 ground receipt time is within milliseconds
of DSN's ground receipt time and no problems are expected using either
for ACE clock calibration.


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

DOY 275  10/01/2012  S-ACE-0624  G11-0051  MUS CMD unable to BIND
The MMOC SLE (MUS) cmd process (ace-d24-cmd) generated the error "Cannot
send a BIND because of the following Anite error condition:
ace-d24-cmd's F-CLTU provider object could not thread off an Operations
server because".  This error last occurred on 8/13/2012.  MUS CMD was
restarted and no further problems occurred.
IMPACT:  Manual intervention required.  Activities delayed 12 minutes.