ACE Weekly 09/15/2010 - 09/21/2010

All ACE spacecraft subsystems are performing nominally.

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

No maneuvers were completed this week.  The next attitude maneuver is
scheduled for Tuesday 09/28/2010.

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

DOY 260 (09/17/2010)   GND-203  Old ACE MOC String 3 Dismantled
String 3 in the old ACE MOC (Bldg 14 Rm W10F) has been turned off to be
dismantled.  There are 3 activities that have not yet transitioned to
the Multi-Mission Operations Center (MMOC).  1) Maneuver Planning (APU)
2)Attitude Determination (ADS) and  3)DSN CDR Download.  Maneuver
Planning and Attitude Determination are waiting for the final MTASS
release.  The network for DSN CDR to the MMOC has been fixed, but
additional problems are preventing successful CDR downloads.

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

Data Capture:  100%  DOY 255-262 2010

DOY 263 09/20/2010  DSN SPS/TTC Project Interface Test (PIT)
A third Tracking, Telemetry & Command (TTC) Project Interface Test (PIT)
was performed with DSS-27.  This was the second test with data flowing
through the TEST SLE TLM Provider at DSN.  At the low data-rate
(498bps), telemetry was delayed 5-10 seconds compared with the
operational pass on DSS-45.  The telemetry delay varied.  At the high
data-rate (87648bps), telemetry was duplicated in groups of ~2 seconds.
This occurred for both VC1 and VC2 and is a known problem.  Since the
TTC PIT was shadowing the normal pass on DSS-45, data forwarding and
data capture were not impacted.  Thanks to the SOHO mission for
freeing time on DSS-45 and DSS-27 for this PIT.
	
========================================================================
Anomalies:

DOY 258  09/15/2010  S-ACE-0530  G10-0047 ITOS tm_controller
ITOS was unable to process telemetry due to a "timeout reading from
tm_controller".  ITOS was restarted 5 minutes beginning of track.  This
problem occurs approximately once every 2 weeks.  The next release of
ITOS (8.6.0) is being tested.
IMPACT:  Manual intervention required.  5 minute delay in activities.

DOY 261  09/18/2010  S-ACE-0531  G10-0048 ITOS tm_controller
ITOS was unable to process telemetry due to a "timeout reading from
tm_controller".  ITOS was restarted 10 minutes beginning of track.  This
problem occurs approximately once every 2 weeks.  The next release of
ITOS (8.6.0) is being tested.
IMPACT:  Manual intervention required.  10 minute delay in activities.

DOY 263  09/20/2010  S-ACE-0532  G10-0049 ITOS tm_controller
ITOS was unable to process telemetry due to a "timeout reading from
tm_controller".  ITOS was restarted before beginning of track.  This
problem occurs approximately once every 2 weeks.  The next release of
ITOS (8.6.0) is being tested.
IMPACT:  Manual intervention required.  No delay in activities.