Here are the last two orbits for which we have telemetry prior to system
shutdown:
|
2003-12-26_01449 #40
overlapping colors override rather than mix |
2003-12-26_01448 #41
overlapping colors override rather than mix |
2003-11-26_01411 #78
overlapping colors override rather than mix |
2003-10-26_01372 #117
overlapping colors override rather than mix |
2003-09-26_01334 #155
overlapping colors override rather than mix |
2003-08-26_01295 #184
overlapping colors override rather than mix |
2003-07-26_01256 #219
overlapping colors override rather than mix |
Some people have speculated that the propusion failure in December of 2000 may have damaged the main battery. That could well be the case, but telemetry doesn't show much change after that event and i didn't see much fluctuation until the latter part of 2001, which seemed later to become stable again. It seems to have done that several times before our most recent event.
Run your own query
I've saved the plots of these telemetry signals based on what's available
1in the on-line archive, from launch to the end of January 2004, and you can
run your own query. If you want to look at the actual data, there is a link
to it next to the plots but be aware that the unzip'ed archive lives on my
laptop, and thus may not always be available to allow the decoded data to be
examine.
Please don't publish the resultant URLs, as the machine which generates
and stores these plots is not a public server.
This shows a sequence of plots by plot number, with #1 being the most recent
event when AO-40 shut down due to very low batteries. For example, here's a
query that
shows the ten most recent plots
(orbits) and another query which
shows 10 plots at 20 orbit intervals starting with plot #2.
2004/01-26_01487/a01487.tlm: MA 9 #1 0x1ED: 0x00->01 E-FLAGS Emergency status ON: Battery voltage low 0x1EE: 0x00->80 EXPFLAG -lo ON: Passbands 0x1EF: 0x00->10 EXPFLAG -hi ON: Heater 2004/01-26_01488/a01488.tlm: MA 8 #1 0x18B: 0x01->00 PSU Relay control OFF: main battery 0x1ED: 0x01->03 E-FLAGS Emergency status ON: Battery voltage very low 0x1EE: 0x80->ff EXPFLAG -lo ON: Laser ON: RF monitor ON: A CAM ON: B CAM ON: GPS ON: K Tx ON: X Tx 0x1EF: 0x10->1e EXPFLAG -hi ON: Rudak ON: Cedex control ON: Cedex power MA 32 #155 0x1ED: 0x03->00 E-FLAGS Emergency status OFF: Battery voltage low OFF: Battery voltage very low MA 42 #243 0x1ED: 0x00->02 E-FLAGS Emergency status ON: Battery voltage very lowHere's my interpretation of the status bits from the last few orbits before the power anomoly occured.
Early in Orbit 1487, the satellite detected a low voltage condition, and disabled the passbands and the fuel heater (not in use), setting the corresponding bits on EXPFLAG. Soon thereafter, the main battery seemed to return to normal, but the BCR current continued to fluctuate (as it had in recent passes). At about the same time in Orbit 1488, the satellite detected a very low voltage condition, and disabled all non-essential functions by setting all bits in EXPFLAG (to 0xFF). PSU Relay control was also cleared connecting both batteries to the +28V bus (as before, only the main battery was connected to the +28V power bus).
At that point, the voltage on both batteries appeared to rise to about 27V (where 30V is the maximum value typically seen) by MA=20, fluctuated between 26V and 27V until MA=39, dropped to about 25.5V and collapsed between MA=40.6 and MA=40.9, dropping about 18V. It appeared to sit there until MA=40.9, and at MA=42.6, dropped to about 14V, where it stayed until we apparently lost telemetry at about MA=45.
So it appears that during that orbit, voltages reported for the main battery, auxillary battery and the +28V bus were within a few tenth of a volt, so one might conclude that the auxillary battery was at least partially recharged during that cycle. However, it seems that if the controllers can manage to separate the batteries and one of them recharges enough to permit partial operation, if it can't stay above the "very low voltage" point, it may be hard to keep the two batteries separated.