| |
CX2SA > SATDIG 06.07.16 21:25l 678 Lines 22220 Bytes #999 (0) @ WW
BID : AMSATBB11223
Read: GUEST
Subj: AMSAT-BB-digest V11 223
Path: IW8PGT<CX2SA
Sent: 160706/1917Z @:CX2SA.SAL.URY.SOAM #:48001 [Salto] FBB7.00e $:AMSATBB11223
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: W5PFG from DM77 today on FO-29 and SO-50 (Clayton Coleman)
2. Re: XW sats (Ted)
3. Re: XW sats (Patrick STODDARD (WD9EWK/VA7EWK))
4. Re: XW sats (AL7JK John)
5. Re: Band designators, Modes (RSoifer1@xxx.xxxx
6. Activating IN72 locator (afesan@xxxxx.xxxx
7. Re: Band designators, Modes (Peter Laws)
8. Re: Band designators, Modes (Paul Stoetzer)
9. Re: Band designators, Modes (Peter Laws)
10. Arduino GPS Corrected VFO - update (Gregory Beat)
11. Re: Band designators, Modes (skristof@xxxxxxx.xxxx
12. Re: Band designators, Modes (Paul Stoetzer)
13. Re: Band designators, Modes (Peter Laws)
14. Re: Band designators, Modes (skristof@xxxxxxx.xxxx
----------------------------------------------------------------------
Message: 1
Date: Tue, 5 Jul 2016 16:18:37 -0500
From: Clayton Coleman <kayakfishtx@xxxxx.xxx>
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] W5PFG from DM77 today on FO-29 and SO-50
Message-ID:
<CAPovOwfbOe-BJm8RAy6N_a=EUki7xnwa0s46LBPLauokrVL-OQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Thanks for N8HM for posting my DM77 operation announcement yesterday.
It was a very last-minute trip but went over very well. I made 25
contacts on FO-29 and 14 on SO-50. I attribute that number of
contacts to it being a U.S. Holiday (Independence Day.) Both
satellite passes were very orderly and it was nice to get a few new
stations in my log.
We had been in very mountainous terrain during the trip to the
destination grid. Fortunately DM77ab was just east of Antonito,
Colorado in a high valley. My GPS was reading an elevation of 7,864'
at my operating location. Using 4 elements on 70cm and 2 elements on
2m, I was able to work both satellites down to the horizon.
All of the contacts have been uploaded to Logbook of the World.
73
Clayton
W5PFG
------------------------------
Message: 2
Date: Tue, 5 Jul 2016 20:23:30 -0700
From: "Ted" <k7trkradio@xxxxxxx.xxx>
To: "'D. Craig Fox'" <DFox@xxxxxx.xxx>, "'Amsat'" <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] XW sats
Message-ID: <000d01d1d735$c5429a50$4fc7cef0$@xxxxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"
Hi Craig, do you know the current status of Lilacsat? It used to be on
MWFridays. Some say it is back...just wondering
Thanks, Ted
K7TRK
-----Original Message-----
From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of D. Craig Fox
Sent: Friday, July 01, 2016 7:06 PM
To: Amsat
Subject: [amsat-bb] XW sats
Wow so under used
Was on the last passes of XW2C and XW2F Very loud, very quiet - too bad Will
be on XW2A in one minute- high pass again for SoCal 73s Craig N6RSX
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available to all
interested persons worldwide without requiring membership. Opinions
expressed are solely those of the author, and do not reflect the official
views of AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 3
Date: Wed, 6 Jul 2016 03:28:41 +0000
From: "Patrick STODDARD (WD9EWK/VA7EWK)" <amsat-bb@xxxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] XW sats
Message-ID:
<CAN6TEUfDmWpuN=ysvokr1Lw0tGrwsDPaDKUenSHrJSMRVKzbaA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Ted,
There's no telling when it will be on. Some will post on here, or
on the AMSAT status page http://amsat.org/status/ whenever it is
on. The previous Monday/Wednesday/Friday "schedule" is only a
suggestion now. It has been on any day of the week, and sometimes
only for a few hours at a time. It was on during Field Day, and
helped those who gave it a listen during those passes.
73!
Patrick WD9EWK/VA7EWK
http://www.wd9ewk.net/
Twitter: @xxxxxx
On Wed, Jul 6, 2016 at 3:23 AM, Ted <k7trkradio@xxxxxxx.xxx> wrote:
> Hi Craig, do you know the current status of Lilacsat? It used to be on
> MWFridays. Some say it is back...just wondering
>
> Thanks, Ted
> K7TRK
>
>
------------------------------
Message: 4
Date: Wed, 6 Jul 2016 05:39:57 -0800
From: AL7JK John <al7jk.john@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] XW sats
Message-ID:
<CABy1QVkEJXctJgkyVw6JLGMJKyaCQ7a8KHvNh_BFw6cc4G7kmA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Howdy all. Surely a pattern will emerge, will setup some separate
receivers and patiently observe. There's not a lot of action on the
XW's up north here either, regardless I still put out a CQ on 'em
now and then.
Fuji-29 has been keeping me busy, stalking the JA's during
mutual passes using cw. Fun !
73 de AL7JK, John
BP51fh
On Tue, Jul 5, 2016 at 7:28 PM, Patrick STODDARD (WD9EWK/VA7EWK) <
amsat-bb@xxxxxx.xxx> wrote:
> Ted,
>
> There's no telling when it will be on. Some will post on here, or
> on the AMSAT status page http://amsat.org/status/ whenever it is
> on. The previous Monday/Wednesday/Friday "schedule" is only a
> suggestion now. It has been on any day of the week, and sometimes
> only for a few hours at a time. It was on during Field Day, and
> helped those who gave it a listen during those passes.
>
> 73!
>
>
>
>
>
> Patrick WD9EWK/VA7EWK
> http://www.wd9ewk.net/
> Twitter: @xxxxxx
>
>
>
>
> On Wed, Jul 6, 2016 at 3:23 AM, Ted <k7trkradio@xxxxxxx.xxx> wrote:
>
> > Hi Craig, do you know the current status of Lilacsat? It used to be on
> > MWFridays. Some say it is back...just wondering
> >
> > Thanks, Ted
> > K7TRK
> >
> >
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
> expressed
> are solely those of the author, and do not reflect the official views of
> AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 5
Date: Wed, 6 Jul 2016 11:21:47 -0400
From: RSoifer1@xxx.xxx
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Band designators, Modes
Message-ID: <101ee4.4f96605c.44ae7bfd@xxx.xxx>
Content-Type: text/plain; charset="US-ASCII"
Professionals in most fields love to use, and perpetuate, jargon instead of
plain language. I guess it makes them feel important
73 (er, that's jargon too),
Ray W2RS
------------------------------
Message: 6
Date: Wed, 6 Jul 2016 17:55:05 +0200
From: <afesan@xxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Activating IN72 locator
Message-ID: <F8AEBB82586042A29C8428D703A857C7@xxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
For those interested ..: Will activate IN72 grid on next friday, July 8th.
Will try to be active at most satellite passes as possible. FM&linear sats.
Even I will try AO7 (if we are lucky enough it be in ?B? mode active that
pass) looking only for USA stations. Cross fingers.
Will be present in FO-29, XW sats, SO-50,AO-85...Opertaion will begin at
0900-1000 UTC until 1900 UTC
73,s
Antonio (EA1IW)
------------------------------
Message: 7
Date: Wed, 6 Jul 2016 11:04:12 -0500
From: Peter Laws <plaws0@xxxxx.xxx>
To: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Band designators, Modes
Message-ID:
<CANVAiQ9ZKu95-zPpe3X4x6qOfpWcAxX+eGm=pTL++hks-tDibw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
On Mon, Jul 4, 2016 at 2:59 PM, Peter Laws <plaws0@xxxxx.xxx> wrote:
> I thought AMSAT was moving away from Modes A, B, J, etc, but they seem
> too entrenched and still appear in current pubs.
I don't much care which designators are used but I would like to see
AMSAT pick one and stick with it. If the organization wants to move
away from A/B/J/KT/whatever, and towards a combination of uplink and
downlink band letters, great, but then it needs to be a complete
break.
Or simply conclude that no one could handle the new style and just go
back to A/B/J/etc and come up with new single letters for the new
combinations.
Or are we *really* going to stick with "nickel and dime"? Mode C/X
sounds way better to me.
All that said, I keep finding more stuff for my table. I didn't
really realize that the "hole" in our 13 cm S band was taken up mostly
by the pay radio monopoly (who are on the ground as well as in the
sky). Lots of other services nipping at our heels, too.
Putting new satellites on C/X is a good idea on many levels.
--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!
------------------------------
Message: 8
Date: Wed, 6 Jul 2016 13:52:13 -0400
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: Peter Laws <plaws0@xxxxx.xxx>
Cc: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Band designators, Modes
Message-ID:
<CABzOSOpS094sKmxdrphdN+-D8Q=wrm-pgKGLuNSeyTT=6OxxNg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
AMSAT publications generally use the "new designators" developed prior
to the launch of AO-40, though sometimes with a parenthetical
reference to the old mode designation.
For example, from the website post regarding the selection of
RadFxSat-2 (Fox-1E) for a CSLI launch:
"The Fox-1E spacecraft bus will be built on the Fox-1 series but will
feature a linear V/U (Mode J) transponder ?upgrade? to replace the
standard FM repeater which Fox-1A through D have carried."
Several parts of the website (such as the frequency guide) also use a
less known custom with the second letter in lower case (to indicate
that the second letter is 'down').
Eventually I would hope we would move away from "five and dime" or
"nickel and dime" to using C/X in reference to 5 GHz uplinks and 10
GHz downlinks.
Regardless, I do think using letters to indicate uplink and downlink
is both meaningful and useful. I especially appreciate the history
behind the A, B, and J designations (A and B originating with AO-7's
two transponders and J originating with AO-8's JAMSAT built
transponder) and use those in general conversation with other
satellite ops since it's even easier than saying U/V or V/U. The
downside with U/V and V/U is it can get confused. For example, I know
that a well-known but poorly-informed purveyor of amateur satellite
information consistently confuses the two in his materials.
73,
Paul, N8HM
On Wed, Jul 6, 2016 at 12:04 PM, Peter Laws <plaws0@xxxxx.xxx> wrote:
> On Mon, Jul 4, 2016 at 2:59 PM, Peter Laws <plaws0@xxxxx.xxx> wrote:
>> I thought AMSAT was moving away from Modes A, B, J, etc, but they seem
>> too entrenched and still appear in current pubs.
>
> I don't much care which designators are used but I would like to see
> AMSAT pick one and stick with it. If the organization wants to move
> away from A/B/J/KT/whatever, and towards a combination of uplink and
> downlink band letters, great, but then it needs to be a complete
> break.
>
> Or simply conclude that no one could handle the new style and just go
> back to A/B/J/etc and come up with new single letters for the new
> combinations.
>
> Or are we *really* going to stick with "nickel and dime"? Mode C/X
> sounds way better to me.
>
> All that said, I keep finding more stuff for my table. I didn't
> really realize that the "hole" in our 13 cm S band was taken up mostly
> by the pay radio monopoly (who are on the ground as well as in the
> sky). Lots of other services nipping at our heels, too.
>
> Putting new satellites on C/X is a good idea on many levels.
>
>
>
> --
> Peter Laws | N5UWY | plaws plaws net | Travel by Train!
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
expressed
> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 9
Date: Wed, 6 Jul 2016 13:31:34 -0500
From: Peter Laws <plaws0@xxxxx.xxx>
To: Paul Stoetzer <n8hm@xxxx.xxx>
Cc: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Band designators, Modes
Message-ID:
<CANVAiQ_wjMVMbLuznMOsHfJyS6hf2h0vNC5bPoVoyvqu2XPuOQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
On Wed, Jul 6, 2016 at 12:52 PM, Paul Stoetzer <n8hm@xxxx.xxx> wrote:
>
> Several parts of the website (such as the frequency guide) also use a
> less known custom with the second letter in lower case (to indicate
> that the second letter is 'down').
>
> Eventually I would hope we would move away from "five and dime" or
> "nickel and dime" to using C/X in reference to 5 GHz uplinks and 10
> GHz downlinks.
Then let's start.
The actual designation has to be agreed upon first, though. Slash/no
slash? Case/no case? Pick one, stick with it. What was the original
decision anyway?
--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!
------------------------------
Message: 10
Date: Wed, 06 Jul 2016 12:40:10 -0500
From: Gregory Beat <w9gb@xxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Arduino GPS Corrected VFO - update
Message-ID: <2F36C6F2-2273-4CE7-A369-869FED3377E1@xxxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
May/June 2016 AMSAT Journal article
"An Arduino GPS Corrected VFO" by Gene Marcus, W3PM/GM4YRE
The Panasonic 12mm Rotary Encoder (EVE-GA1F1724M; DigiKey P10859-ND)
referenced in Figure 4, page 24
http://www.digikey.com/product-search/en?keywords=%20P10859-ND
has been discontinued by Panasonic in 2015.
http://media.digikey.com/pdf/PCNs/Panasonic/PDN.PG13.08.08.2014%20Discontinuat
ion%20of%20EVEG,%20EVEH,%20EVEK,%20EVEL.pdf
Direct Part Substitute (per DigiKey) is the Bourns 12mm rotary encoder
(PEC12R-4217F-N0024)
DigiKey PEC12R-4217F-N0024-ND
http://www.digikey.com/product-detail/en/bourns-inc/PEC12R-4217F-N0024/PEC12R-
4217F-N0024-ND/4699280
==
greg
w9gb
Sent from iPad Air
------------------------------
Message: 11
Date: Wed, 06 Jul 2016 14:52:28 -0400
From: skristof@xxxxxxx.xxx
To: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Band designators, Modes
Message-ID: <93119d24ad9c9bbdd5efefd634bebc81@xxxxxxx.xxx>
Content-Type: text/plain; charset=US-ASCII
What is the problem with just using the numbers? Why is using letters
better?
(Not being snippy here, maybe there is a good reason. If so, please
explain.)
Steve AI9IN
p.s. "We've always done it that way" is not really a good reason in and
of itself.
On 2016-07-06 14:31, Peter Laws wrote:
> On Wed, Jul 6, 2016 at 12:52 PM, Paul Stoetzer <n8hm@xxxx.xxx> wrote:
>
>> Several parts of the website (such as the frequency guide) also use a
>> less known custom with the second letter in lower case (to indicate
>> that the second letter is 'down').
>>
>> Eventually I would hope we would move away from "five and dime" or
>> "nickel and dime" to using C/X in reference to 5 GHz uplinks and 10
>> GHz downlinks.
>
> Then let's start.
>
> The actual designation has to be agreed upon first, though. Slash/no
> slash? Case/no case? Pick one, stick with it. What was the original
> decision anyway?
------------------------------
Message: 12
Date: Wed, 6 Jul 2016 15:02:30 -0400
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: Steve Kristoff <skristof@xxxxxxx.xxx>
Cc: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Band designators, Modes
Message-ID:
<CABzOSOp7sE1jimJTjLQYxCkHLzcB2HfT_qh-vtMv9J26VtLcMw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
It's a lot more characters to type - and especially to speak.
I'm not even sure why we are arguing about this. It takes
approximately 20 seconds to memorize a table of both the old and new
designations and the frequencies they represent. Just learn them and
move on.
There are a lot more complicated things that people have to learn to
be knowledgeable amateur radio and amateur satellite operators. A few
letters to represent frequencies isn't a big deal.
73,
Paul, N8HM
On Wed, Jul 6, 2016 at 2:52 PM, <skristof@xxxxxxx.xxx> wrote:
> What is the problem with just using the numbers? Why is using letters
> better?
>
> (Not being snippy here, maybe there is a good reason. If so, please
> explain.)
>
> Steve AI9IN
>
> p.s. "We've always done it that way" is not really a good reason in and
> of itself.
>
> On 2016-07-06 14:31, Peter Laws wrote:
>
>> On Wed, Jul 6, 2016 at 12:52 PM, Paul Stoetzer <n8hm@xxxx.xxx> wrote:
>>
>>> Several parts of the website (such as the frequency guide) also use a
>>> less known custom with the second letter in lower case (to indicate
>>> that the second letter is 'down').
>>>
>>> Eventually I would hope we would move away from "five and dime" or
>>> "nickel and dime" to using C/X in reference to 5 GHz uplinks and 10
>>> GHz downlinks.
>>
>> Then let's start.
>>
>> The actual designation has to be agreed upon first, though. Slash/no
>> slash? Case/no case? Pick one, stick with it. What was the original
>> decision anyway?
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
expressed
> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 13
Date: Wed, 6 Jul 2016 14:02:22 -0500
From: Peter Laws <plaws0@xxxxx.xxx>
To: skristof@xxxxxxx.xxx
Cc: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Band designators, Modes
Message-ID:
<CANVAiQ8h3qFMLQbD_BPqYELaGB1gBDvZWKYRa6xMX3z-01TC4A@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
On Wed, Jul 6, 2016 at 1:52 PM, <skristof@xxxxxxx.xxx> wrote:
> What is the problem with just using the numbers?
Which numbers? Wavelength or frequency?
There are at least three ways I see to describe a channel: frequency,
wavelength, IEEE/AMSAT band name. If precision is the goal, then it
probably needs to be frequency - but MHz or GHz? If you are talking a
passband, then it seems like wavelength or band name would be better.
Then there is also the old AMSAT mode describing both uplink and
downlink, so 4.
Again, it doesn't much matter which, but to prevent confusion, pick
one and stick with it.
--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!
------------------------------
Message: 14
Date: Wed, 06 Jul 2016 15:14:47 -0400
From: skristof@xxxxxxx.xxx
To: AMSAT-BB <AMSAT-BB@xxxxx.xxx>
Subject: Re: [amsat-bb] Band designators, Modes
Message-ID: <b1e2117186bd14db0c845fbf504df156@xxxxxxx.xxx>
Content-Type: text/plain; charset=US-ASCII
Asking a question is not arguing.
Your two paragraphs below contain no rational arguments for keeping the
letter based system.
Your argument is "We've always done it that way", so learn them and move
on. Sorry, that doesn't cut it.
If you're going to use letters, can't there at least be a rational
organizational scheme to the lettering system?
The current system looks like somebody just drew letters of a hat, then
threw darts at a board of frequencies to see what the letter should
represent.
The number based system would not be that hard. You decide on wavelength
or frequency and go from there.
If I'm going to operate on SO-50, I'm going 2 m up/70 cm down. Most
hams, whether they operate satellites are not, are likely to know what
that means. I don't have to memorize or look up mode F or whatever the
heck it is.
Steve AI9IN
On 2016-07-06 15:02, Paul Stoetzer wrote:
> It's a lot more characters to type - and especially to speak.
>
> I'm not even sure why we are arguing about this. It takes
> approximately 20 seconds to memorize a table of both the old and new
> designations and the frequencies they represent. Just learn them and
> move on.
>
> There are a lot more complicated things that people have to learn to
> be knowledgeable amateur radio and amateur satellite operators. A few
> letters to represent frequencies isn't a big deal.
>
> 73,
>
> Paul, N8HM
>
> On Wed, Jul 6, 2016 at 2:52 PM, <skristof@xxxxxxx.xxx> wrote: What is the
problem with just using the numbers? Why is using letters
> better?
>
> (Not being snippy here, maybe there is a good reason. If so, please
> explain.)
>
> Steve AI9IN
>
> p.s. "We've always done it that way" is not really a good reason in and
> of itself.
>
> On 2016-07-06 14:31, Peter Laws wrote:
>
> On Wed, Jul 6, 2016 at 12:52 PM, Paul Stoetzer <n8hm@xxxx.xxx> wrote:
>
> Several parts of the website (such as the frequency guide) also use a
> less known custom with the second letter in lower case (to indicate
> that the second letter is 'down').
>
> Eventually I would hope we would move away from "five and dime" or
> "nickel and dime" to using C/X in reference to 5 GHz uplinks and 10
> GHz downlinks.
> Then let's start.
>
> The actual designation has to be agreed upon first, though. Slash/no
> slash? Case/no case? Pick one, stick with it. What was the original
> decision anyway?
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership.
Opinions expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite
program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Subject: Digest Footer
_______________________________________________
Sent via amsat-bb@xxxxx.xxx.
AMSAT-NA makes this open forum available to all interested persons worldwide
without requiring membership. Opinions expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT member? Join now to support the amateur satellite program!
http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
End of AMSAT-BB Digest, Vol 11, Issue 223
*****************************************
Read previous mail | Read next mail
| |
