Date: Wed, 2 Feb 94 04:30:40 PST
From: Ham-Space Mailing List and Newsgroup <ham-space@ucsd.edu>
Errors-To: Ham-Space-Errors@UCSD.Edu
Reply-To: Ham-Space@UCSD.Edu
Precedence: Bulk
Subject: Ham-Space Digest V94 #17
To: Ham-Space
Ham-Space Digest Wed, 2 Feb 94 Volume 94 : Issue 17
Today's Topics:
ARLK004 Keplerian data
Mods to 9600 for IC-970
Welcome to rec.radio.info!
Send Replies or notes for publication to: <Ham-Space@UCSD.Edu>
Send subscription requests to: <Ham-Space-REQUEST@UCSD.Edu>
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the Ham-Space Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/ham-space".
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: Mon, 31 Jan 1994 11:17:32 -0700
From: mvb.saic.com!unogate!news.service.uci.edu!usc!sol.ctr.columbia.edu!destroyer!nntp.cs.ubc.ca!alberta!ve6mgs!usenet@network.ucsd.edu
Subject: ARLK004 Keplerian data
To: ham-space@ucsd.edu
SB KEP @ ARL $ARLK004
ARLK004 Keplerian data
ZCZC SK71
QST de W1AW
Keplerian Bulletin 4 ARLK004
------------------------------
Date: 1 Feb 1994 09:30:01 GMT
From: mvb.saic.com!unogate!news.service.uci.edu!usc!howland.reston.ans.net!pipex!sunic!news.funet.fi!zippo.uwasa.fi!mkl@network.ucsd.edu
Subject: Mods to 9600 for IC-970
To: ham-space@ucsd.edu
I have tried to locate some documents on how to modify my IC-970
to do 9600 bps for satelite use. Could someone mail it, or tell,
me where I could ftp it from?
While I'm at it, has anyone interfaced Trackbox with IC-970? Do
you use the IC-970 serial interface to track dopler shift? If so
should I use RS-232 or TTL signals to talk with my rig?
--
Markus
------------------------------
Date: Sun, 30 Jan 1994 21:00:05 MST
From: destroyer!nntp.cs.ubc.ca!alberta!ve6mgs!rec-radio-info@uunet.uu.net
Subject: Welcome to rec.radio.info!
To: ham-space@ucsd.edu
Archive-name: radio/rec-radio-info/welcome
Last-modified: $Date: 1994/01/02 22:00 $
Version: $Revision: 1.06 $
*** Welcome to rec.radio.info! ***
Welcome to rec.radio.info, a group that aims to provide a noise-free source
of information and news for the entire rec.radio hierarchy.
Two introductory articles about rec.radio.info are posted to the group and
to news.answers every two weeks. You are now reading the first article, which
explains what rec.radio.info is, and answers some Frequently Asked Questions.
The second article is titled "Submission Guidelines", and you only need to
read it if you want to submit an article to rec.radio.info.
You can skip to the next section of this article by searching for the next
" -- " string. The sections available are:
- What is the purpose of rec.radio.info?
- Why are messages almost always cross posted to rec.radio.info?
- What is a 'follow-up', and what does 'moderated' mean?
- OK, so now I know what 'moderated' means. Tell me more.
- What type of material is considered inappropriate?
- I do not have access to news, how can I get the information posted to
rec.radio.info?
- Will the material appearing in rec.radio.info be archived somewhere?
- I have a regular posting with timely information, is there a way to
speed up it's delivery, or automate for more convenience?
-- What is the purpose of rec.radio.info?
The purpose or charter of rec.radio.info is to provide the Usenet community with
a resource for information, news, and facts about any and all things radio.
All the other rec.radio groups are intended for discussions and general chit
chat about radio. Rec.radio.info will contain informational, factual articles
only. Follow-ups are redirected to an appropriate other group, and further
discussion (if any) will not take place in rec.radio.info.
In order to ensure that rec.radio.info contains only appropriate articles, it
was decided to create the group as a moderated newsgroup.
-- Why are messages almost always cross posted to rec.radio.info?
It provides a "tag" for each article to be assembled into a filtered
presentation in rec.radio.info (even with cross-posting, only one message, with
a unique Message-ID, is propogated across the net). This tag also facilitates
a pre-existing method of dropping or cancelling the articles locally within the
discussion groups if you don't want to see them. This accommodates individuals
who want to separate the bulletins from the discussions, discussions from the
bulletins, as well as those who are adamant about not reading another
newsgroup and wanted to see everything all in one basket.
With the total size of Usenet (in number of newsgroups and total traffic)
doubling every year or so, this is no insignificant contribution to reducing
information noise and chaos. Making the discussion groups a catch-all, and
making extra newsgroups filters on that catch-all, is also the most realistic
way to implement such a scheme (It's not intuitively obvious what the charter,
contents, and general appropriate topics for each and every newsgroup are.
Seeing FAQ's and charter/intro postings in the home newsgroup is beneficial
for new readers).
By cross-posting one only is adding a few tens of bytes to each bulletin (to
specify the extra group on the Newsgroups line), but are adding the capability
for very powerful filtering features available on most news servers,
listservers and readers. Your local news guru could probably explain these
features in more detail.
In rn, for example, according to Leanne Phillips in her rn kill-file FAQ, add
a line of the form:
/Newsgroups:.*[ ,]rec\.radio\.info/h:j
either in ~/News/KILL (if you don't want to see rec.radio.info articles
anywhere) or ~/News/rec/radio/amateur/misc/KILL (if you don't want to see them
just in rec.radio.amateur.misc). The latter method means your kill file will
only be consulted during rec.radio.amateur.misc (and hence runs more
efficiently), and will probably work for most people.
In nn, according to Bill Wohler in his nn FAQ, add a line of the form:
rec.radio.info:!s/:^
in ~/.nn/kill (if you don't want to see rec.radio.info articles anywhere), or
put the following lines:
sequence
rec.radio.info
rec.radio.
at the end of ~/.nn/init in order to see all the rec.radio.info bulletins first,
then read the remaining rec.radio.* without the bulletins.
-- What is a 'follow-up', and what does 'moderated' mean?
If you are new to Usenet and are not familiar with the terminology, you might
want to read the general introductory articles found in the newsgroup
news.announce.newusers. Doing so will make your life on the net much easier,
and will probably save you from making silly beginner's mistakes.
If you think that at this moment you are reading an echo, a conference, or
a bulletin board, I'd also strongly suggest a trip over to
news.announce.newusers.
For the rest of this article, I will assume you have a basic knowledge of
Usenet terminology and mechanics.
A moderated group means that any article that needs to be posted to the group
has to be accepted by the moderator of the group. Since we need to ensure that
followups to an article (discussion) do not show up in the rec.radio.info
newsgroup, the `Followup-To:' header line contains a newsgroup that is
appropriate for disussions about the specific article.
-- OK, so now I know what 'moderated' means. Tell me more.
Rec.radio.info is a moderated newsgroup, which means that all articles
submitted to the group will have to be approved by the moderator first.
The current moderator of the group is Mark Salyzyn. Submissions to
rec.radio.info can be posted, or e-mailed to:
rec-radio-info@ve6mgs.ampr.ab.ca
Comments, criticisms, suggestions or questions about the group can be e-mailed
to:
rec-radio-request@ve6mgs.ampr.ab.ca
But before you do so, please be sure to check out the "Submission Guidelines"
article.
The influence of the moderator should be minimal and of an administrative
nature, consisting chiefly of weeding out obviously inappropriate articles,
while making sure correct headers etc. are used for the appropriate ones.
-- What type of material is considered inappropriate?
There are three broad categories of articles which will be rejected by the
moderator:
1) Requests for information: rec.radio.info is strictly a one-way street. I
receive information in my mailbox; I then post it to rec.radio.info.
Requests for specific information belong in the normal discussion newsgroups.
If your request gets answered, you might consider passing the answer on to
rec.radio.info, though. Especially if you can edit it into a informational,
rather than a discussion, format.
2) Obvious discussion articles, or articles that appear unsubstantiated.
3) Commercial stuff: a relatively unbiased test of a radio product would be
accepted, but any hint of for-profit might be reason for rejection. For three
reasons: This is not the purpose of the list, for-profit is a controversial
topic, and this list may be passed onto Amateur Packet Radio (where
for-profit is prohibited except under certain provisos).
rec.radio.swap (or possibly comp.newprod) may be more deserving of the
posting in any matter.
Similarly, copyrighted material generally cannot be used. If it's TRULY
worthwhile to the net, I would recommend obtaining permission from the
copyright holder. Please note the source, and if permission was given. I
reserve the right to make the final decision concerning appropriateness in
all situations. In most cases, a brief summary of, or pointer to, the
copyrighted information may be all I can allow.
-- I do not have access to news, how can I get the information posted to
rec.radio.info?
brian@UCSD.EDU (Brian Kantor) has kindly supplied a mail list server for
rec.radio.info. Non of the articles will be digested, due to their size, so
you will receive individual mailings for every article posted to the group.
Mail sent to radio-info@ucsd.edu will be forwarded to the moderator and
thus is an alias to rec-radio-info@ve6mgs.ampr.ab.ca
To subscribe and unsubscribe via the listserver; the format for that is
sub address radio-info
unsub address radio-info
where 'address' is your full mailing address. Send this request to
listserv@ucsd.edu
Note that the server will automatically delete any address that bounces mail.
If you leave the address portion blank, it will try to deduce your address
from the mail headers. This may not work if you are on bitnet, milnet or
some other non-Unix host, so it is recommended to put your return address
in any case. For example:
sub mymailbox@myhost.mydomain.mil radio-info
or
sub MEMEME01@DMBHST.bitnet radio-info
or something like that.
-- Will the material appearing in rec.radio.info be archived somewhere?
Yes. Still firming up details at the moment but here is a preliminary list:
- unbc.edu as maintained by Lyndon Nerenberg <lyndon@unbc.edu>
- nic.funet.fi maintained by Risto Kotalampi <rko@cs.tut.fi>
saved to /pub/dx/text/rec.radio.info currently stored as
numbered files.
Effectively this means that anything you post to rec.radio.info will be
permanently stored, so your work will not be lost.
-- I have a regular posting with timely information, is there a way to
speed up it's delivery, or automate for more convenience?
Yes, there is! It may take a bit of chatter with the moderator, but we are
willing to take responsible people and provide them the means of posting the
articles directly from their site. We will try everything we can as we fully
realize that DX (distant signal) and astronomical data can be somewhat
transitory. We are also willing to allow regular posters of information the
same courtesy, even if the information is not as time critical.
We refer to this as self-moderation, which is partly based on the model for
news.answer. This requires co-operation and good will to be beneficial to
the community in the rec.radio hierarchy.
I suggest reading the posting guidelines for more information. I am open to
suggestions.
I thank the following individuals for their input into this article:
rec.music.info moderator Leo Breebaart rec-music-info@cp.tn.tudelft.nl
rec.radio.broadcasting moderator Bill Pfeiffer wdp@gagme.chi.il.us
Paul W. Schleck, KD3FU pschleck@unomaha.edu
Ian Kluft, KD6EUI ikluft@uts.amdahl.com
--
Mark Salyzyn -- Moderator rec.radio.info
Submissions to: rec-radio-info@ve6mgs.ampr.ab.ca
Administrivia to: rec-radio-request@ve6mgs.ampr.ab.ca
* Requests for information do *not* belong in rec.radio.info *
------------------------------
Date: (null)
From: (null)
SB KEP ARL ARLK004
ARLK004 Keplerian data
Thanks to NASA, AMSAT and N3FKV for the following Keplerian data.
Decode 2-line elsets with the following key:
1 AAAAAU 00 0 0 BBBBB.BBBBBBBB .CCCCCCCC 00000-0 00000-0 0 DDDZ
2 AAAAA EEE.EEEE FFF.FFFF GGGGGGG HHH.HHHH III.IIII JJ.JJJJJJJJKKKKKZ
KEY: A-CATALOGNUM B-EPOCHTIME C-DECAY D-ELSETNUM E-INCLINATION F-RAAN
G-ECCENTRICITY H-ARGPERIGEE I-MNANOM J-MNMOTION K-ORBITNUM Z-CHECKSUM
AO-10
1 14129U 83058 B 94024.05103246 -.00000157 10000-3 0 2553
2 14129 27.1974 345.0665 6022479 148.8987 267.9531 2.05878528 51849
RS-10/11
1 18129U 87054 A 94024.51112470 0.00000029 15038-4 0 8568
2 18129 82.9229 75.0490 0013261 65.1117 295.1421 13.72330004330209
UO-11
1 14781U 84021 B 94027.58994195 0.00000271 53852-4 0 6609
2 14781 97.7910 48.8507 0012401 4.9153 355.2172 14.69129946529662
RS-12/13
1 21089U 91007 A 94027.69685878 0.00000029 14215-4 0 6585
2 21089 82.9228 115.6462 0029982 137.1573 223.1924 13.74033888149355
AO-13
1 19216U 88051 B 94026.63505797 -.00000145 10000-4 0 8695
2 19216 57.8701 271.4247 7210478 333.4771 3.3186 2.09723999 11545
UO-14
1 20437U 90005 B 94028.26890444 0.00000039 32348-4 0 9591
2 20437 98.5965 114.9087 0010274 241.9908 118.0234 14.29819295209591
AO-16
1 20439U 90005 D 94028.25987292 0.00000024 26533-4 0 7603
2 20439 98.6031 115.9878 0010541 243.2967 116.7135 14.29875009209606
DO-17
1 20440U 90005 E 94027.73801710 0.00000039 31945-4 0 7594
2 20440 98.6053 115.7511 0010665 243.9475 116.0601 14.30013086209547
WO-18
1 20441U 90005 F 94028.27066398 0.00000025 26890-4 0 7600
2 20441 98.6041 116.2877 0011227 243.0969 116.9065 14.29989493209624
LO-19
1 20442U 90005 G 94028.25813267 0.00000042 33233-4 0 7590
2 20442 98.6052 116.4988 0011536 242.1468 117.8543 14.30083361209632
FO-20
1 20480U 90013 C 94027.48250437 -.00000027 20863-4 0 6542
2 20480 99.0158 205.9942 0540414 298.3614 56.4001 12.83223665186087
AO-21
1 21087U 91006 A 94027.61611500 0.00000094 82657-4 0 4197
2 21087 82.9415 246.7308 0036510 114.1293 246.3688 13.74532330150278
UO-22
1 21575U 91050 B 94027.68364431 0.00000060 35027-4 0 4601
2 21575 98.4466 104.9350 0008122 355.6199 4.4915 14.36884969132908
KO-23
1 22077U 92052 B 94027.97690178 -.00000037 10000-3 0 3555
2 22077 66.0832 213.5449 0009026 322.7821 37.2574 12.86283816 68754
KO-25
1 22827U 93061 E 94024.68146431 0.00000048 37106-4 0 3190
2 22827 98.6652 101.8483 0008525 258.2169 101.8056 14.27809123 17216
IO-26
1 22826U 93061 D 94024.19945571 0.00000014 23681-4 0 2574
2 22826 98.6696 101.3894 0008709 274.0164 86.0022 14.27705052 17144
AO-27
1 22825U 93061 C 94024.20805866 0.00000024 27909-4 0 2564
2 22825 98.6679 101.3787 0008002 272.5619 87.4646 14.27602782 17142
PoSat
1 22829U 93061 G 94028.23890898 0.00000042 34883-4 0 2507
2 22829 98.6603 105.3994 0009389 246.0309 113.9887 14.27999663 17721
Arsene
1 22654U 93031 B 93361.28113215 -.00000051 10000-3 0 2117
2 22654 1.4185 112.4561 2935300 163.8590 194.2493 1.42195961 3311
STS-60
1 99960U 94034.56756353 0.00033606 55816-4 0 46
2 99960 57.0033 215.8607 0010675 264.1500 95.8328 15.72291901 23
Mir
1 16609U 86017 A 94027.71283080 0.00010322 13245-3 0 1150
2 16609 51.6150 171.3210 0004383 242.7692 117.2855 15.59769565454131
Keplerian bulletins are transmitted twice weekly from W1AW.
The next scheduled transmission of these data will be Tuesday,
February 1, 1994, at 2330z on Baudot and AMTOR.
NNNN
/EX
------------------------------
End of Ham-Space Digest V94 #17
******************************
******************************