Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!floyd!harpo!seismo!hao!hplabs!hpda!fortune!dsd!dna
From: dna@dsd.UUCP
Newsgroups: net.ham-radio
Subject: A clue in the Uosat 11 mystery!
Message-ID: <273@dsd.UUCP>
Date: Sun, 4-Mar-84 05:43:58 EST
Article-I.D.: dsd.273
Posted: Sun Mar  4 05:43:58 1984
Date-Received: Tue, 6-Mar-84 04:04:01 EST
Lines: 337


  TO: HM              
FROM: PK
SENT: 03 MAR 84 06:13:34  
READ: 03 MAR 84 14:46:42  

I've been posting comments on UO-11 on the telemail AMSAT bb.
Rather than repeat the whole thing here, I'll summarize the situation as
I know it.

The last reported UO-11 frames are from Graham Radcliff in Australia.
The last frame he sent me on Telemail was at about 23:15 UTC; this is
about 45 minutes before the no-show at KA9Q.  The path of the satellite
between these two times took it over Antarctica and up the Atlantic
Ocean.  There was visibility in most of eastern South America, Falkland
and Ascension Islands.  In particular, Falkland's pass included the start
of the half-hour eclipse which occurs on each orbit.  Anybody know
anyone down there?

I've written a telemetry decoding program in "C" for anyone who wants
it. Harold has a copy and he's bringing it up on his system.  From my
examination of Graham's frames, nothing really looks suspicious.
Rather than post it here (the decoded version of his frames is 116K!),
I'll give a summary.

Temperatures were running cool, but not exceptionally so for a
spacecraft, but remember it had been in sunlight for a while and was
about to enter eclipse in about 20 minutes.

The battery was sitting at a stable +6 C, the battery voltage at a
little over +14 with little fluctuations, and all the solar arrays were
producing power (but not at the same time, of course).
The battery charge/discharge current was fluctuating rapidly,
sometimes going slightly negative but usually running at a few hundred
mA positive.  The spacecraft was obviously spinning fairly fast as
indicated by the rapidly changing solar array and battery currents.

Regulated voltages looked reasonable.  From a phone conversation with
Harold, none of the various currents seemed out of line.  The warmest
temperature reading was, of course, the 2m beacon: +16.6C.  It was putting
out about 650 mw of RF.

Facet temperatures were cool, ranging from -5C to 0C, except the -Y facet
with a consistent warm reading of +12.8C.

The mode bits were as expected, 1802 computer, nav mag and 2m beacon
about the only things turned on. The navigation magnetometer seemed to
be producing numbers. No activity was seen on any of the command
receivers (but they were drawing supply current).  The computer was on,
but not commanding the spacecraft.  The command watchdog timer was
enabled; according to Harold, this timer runs for about 20 days and
turns off the beacons if no command is heard from the ground in this
time.

I'm stumped.

Phil

  TO: HM              
FROM: PK
SENT: 03 MAR 84 13:48:41  
READ: 03 MAR 84 14:48:18  

Tom (with copy to everyone),
Here's the predicted AOS times for my next pass as derived from all of
the UO-11 element sets on hand:

prelim: 14:13:21.7
MH: 14:12:45.1
Nasa 1: 14:15:52.5
Nasa 2: 14:15:53.6
Nasa 3: 14:14:02.5

In particular, that last one (Nasa set #3) looks suspicious.  Without a
beacon to track, we could very easily be looking at the wrong object.

Phil

  TO: HM              
FROM: PK
SENT: 03 MAR 84 13:52:00  
READ: 03 MAR 84 14:48:40  

Larry,
I'm having pretty good luck in decoding those frames you sent me. So
far, I can't find a clue - except I'm wondering about the state of
the battery charge/discharge line.  I can't figure out if it's
functioning properly or not, as I see wild excursions.  I tend
to discount these because the battery voltage is reasonably stable,
varying as you would expect due to eclipses and s/c loading.  Can you
tell me from which parts of orbits these frames are from?

Phil

P.S. If you want any decoded frames, just yell. They're large,
though.

  TO: HM
FROM: TC
SENT: 03 MAR 84 16:13:58
READ: 03 MAR 84 21:31:05

In addition to Phil's analysis of Graham's data, I asked Bob Diersing
to try decoding it. Bob has sent me a LARGE text file of the decoded
data which agrees with Phil's analysis. If anybody want to see all or
part, I have it captured here on disk.
Tom

  TO: HM
FROM: HP
SENT: 03 MAR 84 17:17:14
READ: 03 MAR 84 21:31:26

Saturday morning news

Just got off the phone with Roger Peal.  Last nite they found an error in the
software which was loaded into the 1802 computer that caused the beacon
to stay on only 1/10 the time they thought, thus the second pass had
an 8 minute beacon instead of 80, and the third pass had an hour beacon
instead of 10 hours.  Thus there is now a good reason for hearing it
in VK but not in the US.  It would have gone off in the south Atlantic.

(Phil, can you compute where it would have gone off?  Assume the program
was loaded 2/3 of the way thru the last UK pass.)

This doesn't explain why the beacon won't come back on.  A possible
explaination follows.  The was a problem with the two meter beacon that
caused it to be intermittent.  One of the osc. stages would occasionally
not lock up fast, and the beacon would draw more power than the power
module would allow it to.  This limited the current it could get and it
never locked up.  The fixed at VAFB was to increase the current limit for
the beacon.  The problem never re-occurred.  One theory says that when
the s/c got colder, it drew more current during the start up time, and
has locked up again.  By the way, all tlm reviewed shows a healthy s/c
that is not too cold for normal operation.

Assuming the 2 meter beacon is locked up, it may be putting out enuff
hash to block the two and 70 cm receivers.  It may be possible to hear
this hash with enuff gain on the ground.  Can someone with a big
array point it the right place with a spectrum analyiser and look
for dopplering noise?

Roger promises to put a more complete status summary on TM soon, there
TM link in the UK has been down for several hours.

Keep listening.

Harold.

Posted: Sat  Mar  3, 1984   7:24 PM GMT              Msg: AGIE-1731-2616
From:   MSWEETING
To:     AMSAT
Subj:   Oscar-11 status

Sorry for the ominous silence from UoS - our Telemail PSS link
has been down for the past day or so.  Thanks for the
telemetry and phone calls received since launch.

We have discovered a problem in the program which was run on
the Oscar-11 computer on orbits 2 & 3, causing them both to
turn the 2m beacon off in an eighth of the time intended.
No-one commented that the previous report from us saying that
the 2m beacon was on for 80 minutes on orbit 2 was incorrect.
So on orbit 2, telemetry was transmitted for 10 minutes from
shortly before LOS at Surrey, and on orbit 3 for 75 minutes
from 22:30:20 until 23:45:20 - just short of the east coast of
the USA.

Since we have now a positive reason why the beacon went off
late Thursday evening (GMT), our worst fears of a catastrophic
failure look less likely. Discussions at Surrey and very
recently with Harold, NK6K, suggest that a more plausible
explanation is that the 2m beacon, when cold after being off
for 7 hours, failed to oscillate properly on power-on.  An
effect similar to this was seen during the first cold cycle of
Thermal Vacuum testing, however the problem was later tracked
down and rectified.  The cause was a large current surge on
power-up causing the power distribution to foldback
sufficiently to prevent full power-up.

Discussion of the remedy for this scenario is still in
progress, so any suggestions would be gratefully received.
Use of the 1.2GHz uplink is a possibility, since the 70cm
uplink shares an antenna with 2m. Harold is already looking at
whether the non-nominal signals can be received from the 2m
beacon using large antenna arrays in the L.A. area.

Roger

Posted: Sat  Mar  3, 1984   8:04 PM GMT              Msg: QGIE-1731-2652
From:   VRIP
To:     HPRICE,MSWEETING
CC:     AMSAT
Subj:   UO-11 Report of W4DAQ

I have just debriefed W4DAQ on his observation of this morning.
Here are the salient facts as he reported them to me a few moments ago.

His QTH is Demoplis, Alabama.
Using NASA element set #2 he had predicted AOS of 3 Mar 1418 UTC; actual
 AOS 1423 @ 120 az.  Actual LOS at 180 az at 1436 UTC.

Signals heard on 145.825 characterized as very weak;  2 THEN D8 = D8 + F9

         ****** SHOULD BE ******

     900 IF MONTH > 2 THEN D8 = D8 + F9

This one will surely appear on the nets and the fix is simple enough
that it can be communicated.  I will check to see if this problem
exists in other versions of the program and advise.

73, Bob

Posted: Sat  Mar  3, 1984   1:23 PM PST              Msg: BGIE-1731-2757
From:   VRIP
To:     MSWEETING,HPRICE
CC:     AMSAT
Subj:   Big Ears To the Rescue
Dave Olean, K1WHS, will be listening for UO-11 on its expected passes
tonite beginning abt 23:xx UTC.  Will advise.

Posted: Sat  Mar  3, 1984   1:25 PM PST              Msg: EGIE-1731-2760
From:   VRIP
To:     MSWEETING,HPRICE
CC:     AMSAT
Subj:   K1WHS
It occurs that a few may not recall that K1WHS's EME array is one of the
most sensitive in amateur hands.  I thought I'd mention it.  73.

Posted: Sat  Mar  3, 1984   5:54 PM PST              Msg: IGIE-1731-2964
From:   VRIP
To:     AMSAT
Subj:   UO-11 (Non) Reception Report
K1WHS, KA9Q and WA2LQQ negative report for 23:40 (3 Mar) and 01:20 (4 Mar)
orbits.  If K1WHS's 26dBd array couldn't pick it up, chances are very
slim there was anything going on with any spectral density at all!  Dave
can hear the static from a crickets legs rubbing tohgether at 10,000 km
(it is alleged!)   Sri but nothing stirring here. 73 de Dave, Phil, Rip