ACE Weekly 12/15/2006 - 12/21/2006

All ACE spacecraft subsystems are performing nominally.

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

	Type        Attitude
	Date        12/21/2006
	DOY         355 2006
	Thrusters   2R 4R- 4R+
	Duration    8:38 min
	Start       16:11:03z
	Stop        16:19:41z
	StartHGA    -2.94 deg
	StopHGA      6.28 deg
	Firing      44 pulses
	FinalSCMass 1393.824lbs

The next attitude maneuver is scheduled for Thursday, 12/28/2006.

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

DOY 349 (12/15/2006)  1945-1947z  CRIS-011
The Image Intensifier was powered on after being automatically safeguarded
during the previous week's solar activity (DOY 341 14:00:28z).  This OCR was
last executed on 09/12/2005.


The following 4 S3DPU OCRs reload the patches after the S3DPU latchup on DOY
347 2006 10:08:40z.

DOY 354 (12/20/2006)  1537-1552z  S3D-004
Patch 4x (sections A, B and C) to extend the SWIMS Deadtime.

DOY 354 (12/20/2006)  1553z  S3D-003
Patch 2 for the SWICS PHA identifier.  This changes the scheme used by S3DPU
to identify which of three solid state detectors was triggered by an ion and
in which classification range it falls.

DOY 354 (12/20/2006)  1555-1613z  S3D-002
Patch 3.1.3.B (sections A, B and C) to extend SWICS deadtime (time DPU does
not analyze PHA Data) for the period when Stepping voltage changes from
lowest value to highest value.

DOY 354 (12/20/2006)  1615-1636z  S3D-005
Patch 5 allows SEPICA to be in Engineering Mode without affecting SWICS and
SWIMS.


DOY 354 (12/20/2006)  GND-177
SSH was installed on string 3 workstations.  This will allow the FOT to
monitor the data flow from the new GMUG fanout on the Restricted IONet.


OCR SEP-110 has been rescheduled to start on Wednesday 01/03/2007 (DOY
003) in conjunction with the attitude maneuver scheduled for Thursday
01/04/2006 (DOY 004).  Sepica will be power-cycled to try to induce a gas
valve to open.

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

Due to DSS-27 being red on DOY 350 & DOY 351, along with limited available
DSN time, resulted in a 1.8 hour loss of playback data (2006-350-18:28:42
to  2006-350-20:16:45).  Data capture for the week is 98.93%.

DSN's available time has been limited.  No pass was scheduled for DOY 353.
An SSR failover occurred on DOY 354 at 14:27:40z.  No attitude report was
generated for DOY 353 and no clock calibration report for DOY 353 and DOY
354.  January 2007, fortunately, does have a pass for each day.

RIONET - Testing of String 3 continues.  String 2 is tentatively scheduled
to be switched to RIONet in January 2007.

Space Link Extension (SLE) - ACE SLE version 2.1 was delivered to the
Library on April 28, 2006.  Installation in the ACE MOC will not occur until
after the MOC is converted to the RIONET.

The ULEIS shutter has opened up after the solar flares dissipated.
	348-20:16:32	from   1% open to   6% open
	349-02:53:19	from   6% open to  25% open
	349-14:01:03	from  25% open to 100% open

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

DOY 350 (12/16/2006) S-ACE-0130 (G06-0120) - D27 Red
Saturday morning (3:30am), Ops Chief notified FOT that DSS-27 was unable to
support the ACE pass.  An APC (Antenna Pointing Controller) Card had failed.
The FOT requested a short 2-hour pass with DSS-46 from the limited time
available.  Since the pass was later than the original support, the FOT did
not need to come to the MOC to download the new DSN schedule.  DR#G107305
IMPACT:  Additional DSN support needed to be scheduled.  SSR playback was
still not completed.  7.5 hours of plbk data would be redumped in the first
50 minutes of the following support.


DOY 351 (12/17/2006) S-ACE-0133 (G06-0121) - D27 Red
Sunday morning (3:30am), Ops Chief notified FOT that DSS-27 was unable to
support the ACE pass.  The FOT requested a short 2-hour pass with DSS-54
from the limited time available.  The FOT needed to immediately come to the
MOC to download the new DSN schedule so that the ground software could take
the support.  Problems with the DSN schedule delayed activities by 20
minutes, leaving only 1 hour 40 minutes for the support.
IMPACT:  Additional DSN support needed to be scheduled.  Due to the short
time available, the redump was not able to be completed before the SSRs were
swapped.  1.8 hours of playback data was lost (DOY 350 18:28:42-20:16:45z).


DOY 351 (12/17/2006) S-ACE-0134 (G06-0122) - ROBOTT Frozen
The ROBOTT ground software froze at the end of the DSS-54 support.
IMPACT:  Ground software cleanup (g_acedown, offline, etc) performed
manually.


DOY 352 (12/18/2006) S-ACE-0129 (G06-0123) - 2 instances of ROBOTT/C&C
An additional support was scheduled with DSS-46 on Monday.  This was done to
catch up on SSR playback since no pass was scheduled for Tuesday.  ROBOTT
froze after the first support.  RTMON rebooted all software, but did not
kill the original instance of C&C.  This resulted in 2 command control
systems running procedures.  FOT killed both instances of C&C and restarted
a single instance before the pass started.
IMPACT:  The 2 instances of C&C were executing duplicate procedures.  If
this had continued during the support, the spacecraft would not have been
commanded correctly.


DOY 354 (12/20/2006) S-ACE-0132 (G06-0124) - Bitbucket error/No redumps
TPOCC occasionally generates bitbucket errors when executing UNIX
directives.  When this occurs, TPOCC pauses the procedure ('wait') and the
UNIX directives completes.  When ROBOTT/C&C is monitoring TPOCC, C&C gives a
'go' when it sees the wait statement.  A bit bucket error occurred while
calculating the redumps for the day.  The procedure was continued before the
dumplist was generated and no redumps were performed.
IMPACT:  Minimal.  Redumps were performed on the following day.


DOY 350 (12/16/2006) S-ACE-0135 (S06-0015) - S3DPU_I Red High Limit
S3DPU current (S3DPU_I) briefly violated the red high limit (RH > 145mA).
	2006-350-23:04:10 - 23:04:26  149.744-151.318mA
The last S3DPU_I red high limit violation was DOY 139 2006 (05/19/2006).
S3DPU_I daily maximums increased from 125-150mA to 135-170mA starting around
DOY 180 2005.  Mark Popecki has been notified.
IMPACT:  Only 2 consecutive values out of limits


DOY 352 (12/18/2006) S-ACE-0131 (S06-0014) - S3DPU_I Red High Limit
S3DPU current (S3DPU_I) briefly violated the red high limit (RH > 145mA).
	2006-352-19:42:33 - 19:42:34  147.392-153.664mA
Mark Popecki has been notified.
IMPACT:  Only 2 consecutive values out of limits