![]() |
|
Clementine
| |||||||||||
If you would like to receive further information on SETAS, or have suggestions on what information you would like to see accessible through this archive, please fill out the SETAS request form. Responsible Parties: Page Content: William H. Kinard Page Construction: Thomas H. See |
|
Meteoroid & DebrisA First Look at the Clementine Interstage Adapter Satellite Orbital Meteoroid and Debris Counter (OMDC) ResultsJohn P. Oliver, Senior Research Scientist, Institute for Space Science and Technology, 1810 NW 6th Street, Gainesville FL 32609
Abstract
Introduction
The Clementine mission to map the moon and then observe an asteroid (Ref 2) provided an opportunity to gather new data on the microparticle meteoroid and debris environment. The Clementine Interstage boosted the main spacecraft into an elliptical orbit around the Earth, and then separated to become the Interstage Adaptor Satellite (ISAS; Ref 3). The orbit of the ISAS had an inclination of 66 degrees, an eccentricity of 0.90, and a period of 52 hours. The initial apogee was 133,370 km and the initial perigee was 6736 km. This highly eccentric orbit meant that the ISAS spent less than one hour in LEO each orbit. Thus most of the exposure was to a relatively debris-free environment. The Orbital Meteoroid and Debris Counter‡ experiment was carried on the ISAS.
The OMDC Experiment
Each group of 16 sensors was connected to an accumulating counter which registered a count upon an impact on any one of the sensors in the group. The total bias current drawn by all 48 sensors was monitored to allow an indication of the overall health of the sensors. A typical sensor was expected to have a leakage current of approximately one microampere. A series resistor limited the short circuit current drawn by a single sensor to about 20 microamperes.
Data Stream Format and Downlinks
ISAS data downlinks were possible near the time of perigee passage (approximately every 52 hours) when the spacecraft was within 20,000 kms of a ground station. The planned procedure was to transmit a "TX-on" signal when the spacecraft came within range. The spacecraft was programmed to transmit its entire data buffer upon that ground command, and then to erase the buffer. Unfortunately, ground-based RF interference with the spacecraft telemetry receiver caused the spacecraft systems to transmit the data buffer and then erase it at every perigee, whether the ground station was in a position to receive the data or not. As a result, buffered data were successfully received and stored at the ground station for only about forty percent of the ISAS active data taking period.§
Observations
The sensor leakage current started at about 75 microamps (µa), slowly declining to just less than 60 ua over the first three weeks.** This decrease is likely due to the outgassing and curing of insulation and potting compounds used on the sensor wiring. The plateau value of about 58 µa is consistent with the expected leakage for an array of 48 sensors. These data indicate that it is unlikely that more than one sensor was short circuited and non-functional at OMDC turn on time although is possible that as many as two sensors were short circuited at that time. The small rise in sensor leakage current at the very end of the flight may be due to the relatively high number of impacts recorded at this time, or to a change in the sensor temperature. There are no direct sensor temperature measurements available. As may be seen in Figure 6, the solar array temperature reached relatively high values at this time. The readings of the three OMDC counters are given in Table 1 for each data record. These are the "time tagged" readings for which the ISAS position could be determined. The ISAS radial distance, angle from perigee, and hours after perigee tabulated were calculated from orbital elements provided by the Naval Research Lab (Refs 6, 7). The column labeled "Accumulated" lists the contents of the three counters at the time of the record. The column labeled "New Counts" gives the change in counter value. Recall that no record was stored unless at least one counter recorded a count. The first record was recorded less than five seconds after the ISAS data acquisition system startup. These five counts represent counter turn-on transients and (possibly) impacts that occurred during the week in low Earth orbit before the bias was applied to the sensors. These counts should be disregarded in the analysis of OMDC data. There are five other records in Table 1 that show more than one new count. Each of these occurs after spurious downloads had cleared the data buffer. There are no cases where more than one count can be assumed to have occurred in a single five second interval. The orbit of the ISAS is shown in Figure 3 with the location of most of the time tagged records marked by orbit number. The counter readings are plotted in Figure 4 as a function of time. All of the time tagged records during the first 60 days occurred within ten degrees following apogee, however only one-third of the early impacts were time tagged. The time tagged records during the last 20 days were distributed over much of the orbit although no time tagged counts were recorded in LEO (altitude less than 2000 km). The data appear to be divided into two distinct segments which have significantly different counting rates. During the first 76 days a total of 22 impacts were recorded giving an average counting rate of 0.28 impacts per day. During the last 19 days a total of 53 impacts were recorded giving an average counting rate of 2.8 impacts per day. The data are summarized in Table 2.
Table 2 OMDC Counting Statistics
Total Tagged Rate
First 5 seconds 5 - -
First 76 days 22 8 .28
Last 19 days 53 45 2.8
Total 80 53 .79
During the early period the counts increased linearly with no discrete events. This may represent the random background. The later period appears to be comprised of two discrete events with an intervening quiescent period. The random background component may well have continued through this period.
ISAS Dynamical Behavior
One approach to inferring the ISAS dynamical behavior that appears to yield some useful information is the analysis of the Solar Array temperature. Once each hour data from a variety of temperature sensors was stored in the DAS data buffer for transmission at the next downlink. One of these sensors was installed in close contact with the ISAS external skin, on the exterior of the spacecraft about mid-way between top and bottom of the cylindrical body. It was covered by approximately 15 mils of blanketing. This sensor was intended to monitor the temperatures encountered by the solar cells. The data from Solar Array (SA) temperature sensor are plotted for the entire 95 day ISAS flight in Figure 5. Selected samples are plotted at an expanded scale in the upper portion of this figure while the entire data set is plotted at the bottom. Several points can be made about these data.
It seems probable that the ISAS was rotating rapidly relative to the one-per-hour temperature sampling rate during the early part of the mission since it appears unlikely that the Solar Array temperature sensor remained at a constant angle to the sun during this entire period. The oscillations during the last two orbits may well represent the actual rotation rate during this period. The apparent rotation period varied between 12 and 24 hours. Less probably, the oscillation rate could represent a "beat period" against the temperature sampling rate. The data scattered in a band between orbits 166 and 174 is characteristic of "under-sampled" data. The spacecraft appears to have been rotating slowly enough that the skin temperature was varying with time, but enough faster than the temperature sampling rate to yield under-sampling. The data of Table 1 indicate that the counts were relatively evenly distributed among the three counter channels during the early part of the mission. During the last part, however, counts were clearly not uniformly distributed. There were almost no counts recorded by counter number 1. There is some apparent tendency of counters 2 and 3 to alternate active periods. The Solar Array temperature and the OMDC new count activity during the last five orbits are shown in Figure 6. The counts on counters 2 and 3 appear "clumped" to some extent but there does not seem to be a clear correlation with the Solar Array temperature (and thus the inferred rotation).
Fluxes
Acknowledgments
References
§ Note: no counts were lost, only time tags. ** Note that the "banding" of values visible in the figure is due to problems with the analog-to-digital converter in the ISAS data acquisition system but the interpretation of the data is not significantly affected.
|
|||||||||||