Date: Sun, 14 Nov 93 11:41:04 PST
From: Info-Hams Mailing List and Newsgroup <info-hams@ucsd.edu>
Errors-To: Info-Hams-Errors@UCSD.Edu
Reply-To: Info-Hams@UCSD.Edu
Precedence: Bulk
Subject: Info-Hams Digest V93 #1345
To: Info-Hams


Info-Hams Digest            Sun, 14 Nov 93       Volume 93 : Issue 1345

Today's Topics:
                        Amateur Radio Newslin
                              DSP units
                    Message failed to FORUM.VA.GOV
                Mobile Transceiver Installation Guide?
                  SAREX Keps & Update 10/28 (3 msgs)
                          What do I do now/

Send Replies or notes for publication to: <Info-Hams@UCSD.Edu>
Send subscription requests to: <Info-Hams-REQUEST@UCSD.Edu>
Problems you can't solve otherwise to brian@ucsd.edu.

Archives of past issues of the Info-Hams Digest are available 
(by FTP only) from UCSD.Edu in directory "mailarchives/info-hams".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 14 Nov 93 02:05:00 GMT
From: library.ucla.edu!agate!doc.ic.ac.uk!uknet!ernie.almac.co.uk!almac!martin.briscoe@network.ucsd.edu
Subject: Amateur Radio Newslin
To: info-hams@ucsd.edu

-> Mike; On this side of the pond we write our dates as Month/Day/Year.
-> It's just as confusing to me when I read newsletter posts written in
-> Europe.

I suppose that we should count ourselves lucky that they don't write the 
time as MM:SS:HH, following the same logic as MM/DD/YY then it should be.



* RM 1.2 00964 * Martin Briscoe - Inverness-shire - Scotland

------------------------------

Date: Sat, 13 Nov 1993 23:09:20 GMT
From: library.ucla.edu!europa.eng.gtefsd.com!gatech!asuvax!ennews!anasaz!john@network.ucsd.edu
Subject: DSP units
To: info-hams@ucsd.edu

kenman@iastate.edu (Kenneth D Anderson) writes:


>Could someone please enlighten me on DSP units such as JPS, Datong, and
>Timeware(?) sell?  How well do these puppies work?

I have a Timewave DSP-9 on my TS-430 and I think it works VERY WELL. Nice
widget - inexpensive also.
-- 
DISCLAIMER: These views are mine alone, and do not reflect my employer's!
John Moore 7525 Clearwater Pkwy, Scottsdale, AZ 85253  USA  (602-951-9326)
john@anasazi.com   Amateur call:NJ7E  Civil Air Patrol:Thunderbird 381
- - Don't forget the thought which by it's very nature cannot be remembered!- -
- - - - - - Storm Chasers Do It in All Kinds of Weather! - - - - - -

------------------------------

Date: 14 Nov 93 18:59:58 GMT
From: news-mail-gateway@ucsd.edu
Subject: Message failed to FORUM.VA.GOV
To: info-hams@ucsd.edu

Your message 'Info-Hams Digest V93 #1344' was not accepted by FORUM.VA.GOV.
The error message was '7'.

------------------------------

Date: 14 Nov 93 16:24:57 GMT
From: olivea!news.bu.edu!noc.near.net!news.delphi.com!BIX.com!arog@ames.arpa
Subject: Mobile Transceiver Installation Guide?
To: info-hams@ucsd.edu

While the question asked related to rfi to auto computer equipment,
I figure that there is one other point to be made...

When connecting to the 12 volt system of a car, its *real*good*
pratice to get as close to the battery as possible. Generaly,
I,ve done this by using a Burndy clamp to make the splice on
the cable as it comes from the battery. "Split bolt" type 
clamps also work and bith should be in stock at electrical 
contactor or their suppy houses. These ar used for high current
applications in industrial applications and elsewhere.

alan

------------------------------

Date: 14 Nov 93 16:37:34 GMT
From: news-mail-gateway@ucsd.edu
Subject: SAREX Keps & Update 10/28
To: info-hams@ucsd.edu

R:931114/1843Z @:VK1KCM.ACT.AUS.OC [Canberra, ACT] $:29047_W7OEK
R:931112/1442Z @:VK4DGQ.QLD.AUS.OC [Brisbane] #:39039  $:29047_W7OEK
R:931112/0503z 39129@KE7KD.#NONEV.NV.USA.NOAM [RENO, NV.]
R:931107/0432z 11312@N7KXI.UT.USA.NA
R:931107/0111z 17783@KG7FC.UT.USA.NA [DATA HUB UT]
R:931104/1920z 10535@N7MLR.UT.USA.NA
R:931104/1123z 52019@N0LEU.#NWCO.CO.USA.NOAM
R:931103/1739z 59375@KT0H.#NECO.CO.USA [DATA HUB CO]
R:931103/1716Z @:W0RA.#SECO.CO.USA.NA [YODER] FBB5.14d #:82723
R:931103/1302Z @:W7GCI.WA.USA.NA [Tacoma] #:35682 Z:98499 FBB5.15
R:931103/1212Z @:WA7BHH.WA.USA.NA [Tacoma] #:13575 Z:98465 FBB5.15
R:931103/1132 6215@WB7QEU.WA.USA.NA
R:931103/1016 7983@WA7SJN.WA.USA.NA
R:931103/1003 1121@W0RLI.OR.USA.NOAM
R:931103/0545 37550@N7DXT.#EUGEN.OR.USA.NA
R:931103/0454 49935@WB7VMS.#MURPH.OR.USA.NOAM

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 29047 ; Wed, 03 Nov 93 01:09:32 GMT
Date: Wed, 03 Nov 93 01:09:40 UTC
Message-Id: <29041_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 29041 ; Tue, 02 Nov 93 21:42:27 GMT
Date: Tue, 02 Nov 93 21:42:59 UTC
Message-Id: <28985_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28985 ; Tue, 02 Nov 93 20:47:06 GMT
Date: Tue, 02 Nov 93 20:47:48 UTC
Message-Id: <28973_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28973 ; Tue, 02 Nov 93 19:58:01 GMT
Date: Tue, 02 Nov 93 19:58:49 UTC
Message-Id: <28968_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 i9; Tu,2v 93 18:43:20 GMT
Date: Tue, 02 Nov 93 18:44:09 UTC
Message-Id: <28942_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28942 ; Tue, 02 Nov 93 17:43:53 GMT
Date: Tue, 02 Nov 93 17:44:47 UTC
Message-Id: <28937_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28937 ; Tue, 02 Nov 93 15:43:49 GMT
Date: Tue, 02 Nov 93 15:44:50 UTC
Message-Id: <28936_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28936 ; Tue, 02 Nov 93 14:43:54 GMT
Date: Tue, 02 Nov 93 14:44:51 UTC
Message-Id: <28935_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28935 ; Tue, 02 Nov 93 13:43:53 GMT
Date: Tue, 02 Nov 93 13:44:50 UTC
Message-Id: <28933_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28933 ; Tue, 02 Nov 93 12:42:37 GMT
Date: Tue, 02 Nov 93 12:43:53 UTC
Message-Id: <28932_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28932 ; Tue, 02 Nov 93 12:09:45 GMT
X-Forwarded-To: W7OEK
Date: 28 Oct 93 19:00:00 UTC
Message-Id: <931028050312@w7oek.bbs>
From: abfhb@wa8ure.#swmi.mi.usa.na
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

R:931102/0810z 28885@W7OEK.OR.USA.NA
R:931102/0121 49595@WB7VMS.#MURPH.OR.USA.NOAM
R:931101/1449 37097@N7DXT.#EUGEN.OR.USA.NA
R:931101/0530 4700@KB7DBD.OR.USA.NA
R:931101/1218 9138@KB7KBT.OR.USA.NA
R:931101/1152 6500@KA7AGH.OR.USA.NA
R:931101/1156 23351@W0RLI.OR.USA.NA
R:931101/1128 7291@WA7SJN.WA.USA.NA
R:931101/0025 12848@WA7BHH.WA.USA.NA
R:931101/0000 35118@W7GCI.WA.USA.NA
R:931030/1514 47346@N8GTC.#CIN.IN.USA.NOAM
R:931030/0718 29215@W9OJ.IN.USA.NA
R:931030/0652 22073@N5CEC.IN.USA.NA
R:931030/0540 21727@KK9G.#CEIN.IN.USA.NA
R:931030/0537 35453@N5AAA.#CEIN.IN.USA.NA
R:931029/1256 26400@KD9LP.#NCIN.IN.USA.NA
R:931029/0636 15967@NU9H.#NWIN.IN.USA.NA
R:931028/1900 36038@WA8URE.#SWMI.MI.USA.NA

SB SAREX @ AMSAT $STS-58.025
SAREX Keps & Update: 10/28

Thursday 10/28/93 @ 08:00 UTC

The last school group contact was completed yesterday.  The Portsmouth HS 
in Portsmouth, New Hampshire had a telebridge contact using stations in 
California (Ralph Warner, N6MNN) and Texas (Bob Douglas, W5GEL).  The 
students asked 5 questions during this bridge contact.

Hams across the U.S. and around the world continue to work the Shuttle 
Columbia on both voice and packet.  Moreover, the completion of school 
group contacts has cleared several school backup passes for possible 
general QSO opportunities.  While the SAREX Working Group cannot fully 
guarantee availability, there is a high probability that the STS-58 crew 
will be ready to take general calls over the continental U.S. on these 
passes.  Two of these "scheduled" passes remain.  These include orbit 
178 at MET 11 days 1 hour 42 minutes (10/29 at 16:35 UTC) and orbit 192 
at MET 11 days 22 hours and 29 minutes (10/30 at 13:22 UTC).  Please note 
that the astronauts operated voice during yesterday's "scheduled" pass 
which occurred on 10/27 at 14:59 UTC (Orbit 145).  Also note that hams on 
the ground heard or worked the Shuttle Columbia crew on several other orbits 
yesterday.

Element set GSFC-031, generated by Ron Parise, WA4SIR, is the official SAREX 
set for today.  Please note that there is only a six second difference 
between element set GSFC-025 (released two days ago) and element set GSFC-
031.

 STS-58
 1 22869U 93065A   93300.17699070 0.00133671  99048-5  24183-3 0   318
 2 22869  39.0252  71.9896 0012817  34.2105 325.9529 16.00500857  1383

 Satellite: STS-58
 Catalog number: 22869
 Epoch time:      93300.17699070         (27 OCT 93   04:14:51.** UTC)
 Element set:     GSFC-031
 Inclination:       39.0252 deg
 RA of node:        71.9896 deg          Space Shuttle Flight STS-58
 Eccentricity:    0.0012817                  Keplerian Elements
 Arg of perigee:    34.2105 deg
 Mean anomaly:     325.9529 deg
 Mean motion:   16.00500857 rev/day      Semi-major Axis: 6651.1630 Km
 Decay rate:       0.13E-02 rev/day*2    Apogee  Alt:        281.30 Km
 Epoch rev:             138              Perigee Alt:        264.25 Km


 NOTE - This element set is based on NORAD element set # 031.
        The spacecraft has been propagated to the next ascending
        node, and the orbit number has been adjusted to bring it
        into agreement with the NASA numbering convention.

Submitted by Frank H. Bauer, KA3HDO for the SAREX Working Group

------------------------------

Date: 14 Nov 93 16:55:07 GMT
From: news-mail-gateway@ucsd.edu
Subject: SAREX Keps & Update 10/28
To: info-hams@ucsd.edu

R:931114/1846Z @:VK1KCM.ACT.AUS.OC [Canberra, ACT] $:29050_W7OEK
R:931112/1444Z @:VK4DGQ.QLD.AUS.OC [Brisbane] #:39041  $:29050_W7OEK
R:931112/0459z 39127@KE7KD.#NONEV.NV.USA.NOAM [RENO, NV.]
R:931107/0451z 11314@N7KXI.UT.USA.NA
R:931106/0721z 17716@KG7FC.UT.USA.NA [DATA HUB UT]
R:931104/2120z 10537@N7MLR.UT.USA.NA
R:931104/1305z 52021@N0LEU.#NWCO.CO.USA.NOAM
R:931103/1735z 59374@KT0H.#NECO.CO.USA [DATA HUB CO]
R:931103/1708Z @:W0RA.#SECO.CO.USA.NA [YODER] FBB5.14d #:82722
R:931103/1257Z @:W7GCI.WA.USA.NA [Tacoma] #:35681 Z:98499 FBB5.15
R:931103/1205Z @:WA7BHH.WA.USA.NA [Tacoma] #:13574 Z:98465 FBB5.15
R:931103/1123 6214@WB7QEU.WA.USA.NA
R:931103/1009 7982@WA7SJN.WA.USA.NA
R:931103/0959 1118@W0RLI.OR.USA.NOAM
R:931103/0516 37547@N7DXT.#EUGEN.OR.USA.NA
R:931103/0445 49934@WB7VMS.#MURPH.OR.USA.NOAM

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 29050 ; Wed, 03 Nov 93 02:01:26 GMT
Date: Wed, 03 Nov 93 02:01:50 UTC
Message-Id: <29047_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 29047 ; Wed, 03 Nov 93 01:09:32 GMT
Date: Wed, 03 Nov 93 01:09:40 UTC
Message-Id: <29041_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 29041 ; Tue, 02 Nov 93 21:42:27 GMT
Date: Tue, 02 Nov 93 21:42:59 UTC
Message-Id: <28985_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28985 ; Tue, 02 Nov 93 20:47:06 GMT
Date: Tue, 02 Nov 93 20:47:48 UTC
Message-Id: <28973_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28973 ; Tue, 02 Nov 93 19:58:01 GMT
Date: Tue, 02 Nov 93 19:58:49 UTC
Message-Id: <28968_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28968 ; Tue, 02 Nov 93 18:43:20 GMT
Date: Tue, 02 Nov 93 18:44:09 UTC
Message-Id: <28942_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28942 ; Tue, 02ov 93 17:43:53 GMT
Date: Tue, 02 Nov 93 17:44:47 UTC
Message-Id: <28937_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG b iy W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28937 ; Tue, 02 Nov 93 15:43:49 GMT
Date: Tue, 02 Nov 93 15:44:50 UTC
Message-Id: <28936_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28936 ; Tue, 02 Nov 93 14:43:54 GMT
Date: Tue, 02 Nov 93 14:44:51 UTC
Message-Id: <28935_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28935 ; Tue, 02 Nov 93 13:43:53 GMT
Date: Tue, 02 Nov 93 13:44:50 UTC
Message-Id: <28933_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28933 ; Tue, 02 Nov 93 12:42:37 GMT
Date: Tue, 02 Nov 93 12:43:53 UTC
Message-Id: <28932_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28932 ; Tue, 02 Nov 93 12:09:45 GMT
X-Forwarded-To: W7OEK
Date: 28 Oct 93 19:00:00 UTC
Message-Id: <931028050312@w7oek.bbs>
From: abfhb@wa8ure.#swmi.mi.usa.na
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

R:931102/0810z 28885@W7OEK.OR.USA.NA
R:931102/0121 49595@WB7VMS.#MURPH.OR.USA.NOAM
R:931101/1449 37097@N7DXT.#EUGEN.OR.USA.NA
R:931101/0530 4700@KB7DBD.OR.USA.NA
R:931101/1218 9138@KB7KBT.OR.USA.NA
R:931101/1152 6500@KA7AGH.OR.USA.NA
R:931101/1156 23351@W0RLI.OR.USA.NA
R:931101/1128 7291@WA7SJN.WA.USA.NA
R:931101/0025 12848@WA7BHH.WA.USA.NA
R:931101/0000 35118@W7GCI.WA.USA.NA
R:931030/1514 47346@N8GTC.#CIN.IN.USA.NOAM
R:931030/0718 29215@W9OJ.IN.USA.NA
R:931030/0652 22073@N5CEC.IN.USA.NA
R:931030/0540 21727@KK9G.#CEIN.IN.USA.NA
R:931030/0537 35453@N5AAA.#CEIN.IN.USA.NA
R:931029/1256 26400@KD9LP.#NCIN.IN.USA.NA
R:931029/0636 15967@NU9H.#NWIN.IN.USA.NA
R:931028/1900 36038@WA8URE.#SWMI.MI.USA.NA

SB SAREX @ AMSAT $STS-58.025
SAREX Keps & Update: 10/28

Thursday 10/28/93 @ 08:00 UTC

The last school group contact was completed yesterday.  The Portsmouth HS 
in Portsmouth, New Hampshire had a telebridge contact using stations in 
California (Ralph Warner, N6MNN) and Texas (Bob Douglas, W5GEL).  The 
students asked 5 questions during this bridge contact.

Hams across the U.S. and around the world continue to work the Shuttle 
Columbia on both voice and packet.  Moreover, the completion of school 
group contacts has cleared several school backup passes for possible 
general QSO opportunities.  While the SAREX Working Group cannot fully 
guarantee availability, there is a high probability that the STS-58 crew 
will be ready to take general calls over the continental U.S. on these 
passes.  Two of these "scheduled" passes remain.  These include orbit 
178 at MET 11 days 1 hour 42 minutes (10/29 at 16:35 UTC) and orbit 192 
at MET 11 days 22 hours and 29 minutes (10/30 at 13:22 UTC).  Please note 
that the astronauts operated voice during yesterday's "scheduled" pass 
which occurred on 10/27 at 14:59 UTC (Orbit 145).  Also note that hams on 
the ground heard or worked the Shuttle Columbia crew on several other orbits 
yesterday.

Element set GSFC-031, generated by Ron Parise, WA4SIR, is the official SAREX 
set for today.  Please note that there is only a six second difference 
between element set GSFC-025 (released two days ago) and element set GSFC-
031.

 STS-58
 1 22869U 93065A   93300.17699070 0.00133671  99048-5  24183-3 0   318
 2 22869  39.0252  71.9896 0012817  34.2105 325.9529 16.00500857  1383

 Satellite: STS-58
 Catalog number: 22869
 Epoch time:      93300.17699070         (27 OCT 93   04:14:51.** UTC)
 Element set:     GSFC-031
 Inclination:       39.0252 deg
 RA of node:        71.9896 deg          Space Shuttle Flight STS-58
 Eccentricity:    0.0012817                  Keplerian Elements
 Arg of perigee:    34.2105 deg
 Mean anomaly:     325.9529 deg
 Mean motion:   16.00500857 rev/day      Semi-major Axis: 6651.1630 Km
 Decay rate:       0.13E-02 rev/day*2    Apogee  Alt:        281.30 Km
 Epoch rev:             138              Perigee Alt:        264.25 Km


 NOTE - This element set is based on NORAD element set # 031.
        The spacecraft has been propagated to the next ascending
        node, and the orbit number has been adjusted to bring it
        into agreement with the NASA numbering convention.

Submitted by Frank H. Bauer, KA3HDO for the SAREX Working Group

------------------------------

Date: 14 Nov 93 16:44:53 GMT
From: news-mail-gateway@ucsd.edu
Subject: SAREX Keps & Update 10/28
To: info-hams@ucsd.edu

R:931114/1845Z @:VK1KCM.ACT.AUS.OC [Canberra, ACT] $:29062_W7OEK
R:931112/1443Z @:VK4DGQ.QLD.AUS.OC [Brisbane] #:39040  $:29062_W7OEK
R:931112/0502z 39128@KE7KD.#NONEV.NV.USA.NOAM [RENO, NV.]
R:931107/0442z 11313@N7KXI.UT.USA.NA
R:931107/0111z 17782@KG7FC.UT.USA.NA [DATA HUB UT]
R:931104/2117z 10536@N7MLR.UT.USA.NA
R:931104/1309z 52022@N0LEU.#NWCO.CO.USA.NOAM
R:931103/1733z 59373@KT0H.#NECO.CO.USA [DATA HUB CO]
R:931103/1654Z @:W0RA.#SECO.CO.USA.NA [YODER] FBB5.14d #:82721
R:931103/1252Z @:W7GCI.WA.USA.NA [Tacoma] #:35679 Z:98499 FBB5.15
R:931103/1158Z @:WA7BHH.WA.USA.NA [Tacoma] #:13572 Z:98465 FBB5.15
R:931103/1116 6213@WB7QEU.WA.USA.NA
R:931103/1007 7981@WA7SJN.WA.USA.NA
R:931103/0953 1114@W0RLI.OR.USA.NOAM
R:931103/0511 37545@N7DXT.#EUGEN.OR.USA.NA
R:931103/0435 49933@WB7VMS.#MURPH.OR.USA.NOAM

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 29062 ; Wed, 03 Nov 93 02:45:25 GMT
Date: Wed, 03 Nov 93 02:46:01 UTC
Message-Id: <29050_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 29050 ; Wed, 03 Nov 93 02:01:26 GMT
Date: Wed, 03 Nov 93 02:01:50 UTC
Message-Id: <29047_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 29047 ; Wed, 03 Nov 93 01:09:32 GMT
Date: Wed, 03 Nov 93 01:09:40 UTC
Message-Id: <29041_w7oek@w7oek.bbs>
From: abfhb%w7ok@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 29041 ; Tue, 02 Nov 93 21:42:27 GMT
Date: Tue, 02 Nov 93 21:42:59 UTC
Message-Id: <28985_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28985 ; Tue, 02 Nov 93 20:47:06 GMT
Date: Tue, 02 Nov 93 20:47:48 UTC
Message-Id: <28973_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28973 ; Tue, 02 Nov 93 19:58:01 GMT
Date: Tue, 02 Nov 93 19:58:49 UTC
Message-Id: <28968_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28968 ; Tue, 02 Nov 93 18:43:20 GMT
Date: Tue, 02 Nov 93 18:44:09 UTC
Message-Id: <28942_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28942 ; Tue, 02 Nov 93 17:43:53 GMT
Date: Tue, 02 Nov 93 17:44:47 UTC
Message-Id: <28937_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28937 ; Tue, 02 Nov 93 15:43:49 GMT
Date: Tue, 02 Nov 93 15:44:50 UTC
Message-Id: <28936_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28936 ; Tue, 02 Nov 93 14:43:54 GMT
Date: Tue, 02 Nov 93 14:44:51 UTC
Message-Id: <28935_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28935 ; Tue, 02 Nov 93 13:43:53 GMT
Date: Tue, 02 Nov 93 13:44:50 UTC
Message-Id: <28933_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28933 ; Tue, 02 Nov 93 12:42:37 GMT
Date: Tue, 02 Nov 93 12:43:53 UTC
Message-Id: <28932_w7oek@w7oek.bbs>
From: abfhb%w7oek@wd4eck.ampr.org
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

Received: from WD4ECK.AMPR.ORG by W7OEK.AMPR.ORG with SMTP originator <ABFHB%W7OEK@WD4ECK.AMPR.ORG>
 id 28932 ; Tue, 02 Nov 93 12:09:45 GMT
X-Forwarded-To: W7OEK
Date: 28 Oct 93 19:00:00 UTC
Message-Id: <931028050312@w7oek.bbs>
From: abfhb@wa8ure.#swmi.mi.usa.na
To: ans@amsat.org
Subject: SAREX Keps & Update 10/28
X-BBS-Msg-Type: B

R:931102/0810z 28885@W7OEK.OR.USA.NA
R:931102/0121 49595@WB7VMS.#MURPH.OR.USA.NOAM
R:931101/1449 37097@N7DXT.#EUGEN.OR.USA.NA
R:931101/0530 4700@KB7DBD.OR.USA.NA
R:931101/1218 9138@KB7KBT.OR.USA.NA
R:931101/1152 6500@KA7AGH.OR.USA.NA
R:931101/1156 23351@W0RLI.OR.USA.NA
R:931101/1128 7291@WA7SJN.WA.USA.NA
R:931101/0025 12848@WA7BHH.WA.USA.NA
R:931101/0000 35118@W7GCI.WA.USA.NA
R:931030/1514 47346@N8GTC.#CIN.IN.USA.NOAM
R:931030/0718 29215@W9OJ.IN.USA.NA
R:931030/0652 22073@N5CEC.IN.USA.NA
R:931030/0540 21727@KK9G.#CEIN.IN.USA.NA
R:931030/0537 35453@N5AAA.#CEIN.IN.USA.NA
R:931029/1256 26400@KD9LP.#NCIN.IN.USA.NA
R:931029/0636 15967@NU9H.#NWIN.IN.USA.NA
R:931028/1900 36038@WA8URE.#SWMI.MI.USA.NA

SB SAREX @ AMSAT $STS-58.025
SAREX Keps & Update: 10/28

Thursday 10/28/93 @ 08:00 UTC

The last school group contact was completed yesterday.  The Portsmouth HS 
in Portsmouth, New Hampshire had a telebridge contact using stations in 
California (Ralph Warner, N6MNN) and Texas (Bob Douglas, W5GEL).  The 
students asked 5 questions during this bridge contact.

Hams across the U.S. and around the world continue to work the Shuttle 
Columbia on both voice and packet.  Moreover, the completion of school 
group contacts has cleared several school backup passes for possible 
general QSO opportunities.  While the SAREX Working Group cannot fully 
guarantee availability, there is a high probability that the STS-58 crew 
will be ready to take general calls over the continental U.S. on these 
passes.  Two of these "scheduled" passes remain.  These include orbit 
178 at MET 11 days 1 hour 42 minutes (10/29 at 16:35 UTC) and orbit 192 
at MET 11 days 22 hours and 29 minutes (10/30 at 13:22 UTC).  Please note 
that the astronauts operated voice during yesterday's "scheduled" pass 
which occurred on 10/27 at 14:59 UTC (Orbit 145).  Also note that hams on 
the ground heard or worked the Shuttle Columbia crew on several other orbits 
yesterday.

Element set GSFC-031, generated by Ron Parise, WA4SIR, is the official SAREX 
set for today.  Please note that there is only a six second difference 
between element set GSFC-025 (released two days ago) and element set GSFC-
031.

 STS-58
 1 22869U 93065A   93300.17699070 0.00133671  99048-5  24183-3 0   318
 2 22869  39.0252  71.9896 0012817  34.2105 325.9529 16.00500857  1383

 Satellite: STS-58
 Catalog number: 22869
 Epoch time:      93300.17699070         (27 OCT 93   04:14:51.** UTC)
 Element set:     GSFC-031
 Inclination:       39.0252 deg
 RA of node:        71.9896 deg          Space Shuttle Flight STS-58
 Eccentricity:    0.0012817                  Keplerian Elements
 Arg of perigee:    34.2105 deg
 Mean anomaly:     325.9529 deg
 Mean motion:   16.00500857 rev/day      Semi-major Axis: 6651.1630 Km
 Decay rate:       0.13E-02 rev/day*2    Apogee  Alt:        281.30 Km
 Epoch rev:             138              Perigee Alt:        264.25 Km


 NOTE - This element set is based on NORAD element set # 031.
        The spacecraft has been propagated to the next ascending
        node, and the orbit number has been adjusted to bring it
        into agreement with the NASA numbering convention.

Submitted by Frank H. Bauer, KA3HDO for the SAREX Working Group

------------------------------

Date: 14 Nov 93 17:59:43 GMT
From: pacbell.com!amdahl!JUTS!arl00@ames.arpa
Subject: What do I do now/
To: info-hams@ucsd.edu

In article <2c46b1$hl4@crcnis1.unl.edu> mcduffie@unlinfo.unl.edu (Gary McDuffie Sr) writes:
>drenze@icaen.uiowa.edu (Douglas J Renze) writes:
>
>> The manual doesn't give me any help, and I don't seem to be able to
>>find anything which tells me just how to tweak everything and get on the air!!!
>
>>Any help?
>
>>Peace es 73,
>
>>Doug N0YVW
>
>Now, if that doesn't say something about the current licensing 
>situation, nothing will.
>
>Gary

Gary,
I would suggest you consider turning your ticket in and hanging out on
CB for the next ten years, where attitudes such as yours constitute
acceptable behavior.

Cut the kid some slack, bud, and look up the concept of "Elmering" in
the books on your shelves. Even doing nothing more than suggesting
that Doug pick up a copy of the '94 ARRL Handbook and do some reading
is vastly preferable to your boorish comment.

I suggest pounder apology is in order

------------------------------

End of Info-Hams Digest V93 #1345
******************************
******************************