OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

IW8PGT

[Mendicino(CS)-Italy]

 Login: GUEST





  
CX2SA  > SATDIG   16.01.18 15:00l 707 Lines 21637 Bytes #999 (0) @ WW
BID : AMSATBB1322
Read: GUEST
Subj: AMSAT-BB-digest V13 22
Path: IW8PGT<IZ3LSV<I0OJJ<N6RME<CX2SA
Sent: 180116/1252Z @:CX2SA.SAL.URY.SOAM #:32643 [Salto] FBB7.00e $:AMSATBB1322
From: CX2SA@CX2SA.SAL.URY.SOAM
To  : SATDIG@WW

Today's Topics:

   1. FW: NPR on Cubesats (Andy)
   2. FW: cubsat video (Andy)
   3. FW: cubesats (Andy)
   4. Unknown new satellite (Nico Janssen)
   5. Re: FOX-1D  Now AO-92 (Robert Switzer)
   6. Spid ras rotator issue (shakeel saad)
   7. Re: Spid ras rotator issue (Erich Eichmann)
   8. Re: Spid ras rotator issue (Zachary Leffke)
   9. Completion: Re:  Spid ras rotator issue (Erich Eichmann)
  10. Re: Spid ras rotator issue (Peter Green)
  11. Fox-1D L-band downshifter (Michael A. Foster)
  12. Re: Fox-1D L-band downshifter (Andrew Glasbrenner)
  13. AMSAT-OSCAR 92 identified (Nico Janssen)
  14. Re: AMSAT-OSCAR 92 identified (Ciprian Sufitchi)
  15. 488 US Grids Completed (Ronald Oldham)
  16. AMSAT-OSCAR 92 identified (ok2gz)


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

Message: 1
Date: Mon, 15 Jan 2018 00:35:55 -0600
From: "Andy" <w5acm@xxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] FW: NPR on Cubesats
Message-ID: <006101d38dcb$19388b90$4ba9a2b0$@xxxxxx.xxx>
Content-Type: text/plain;	charset="us-ascii"

For those that are not in the hobby.

Andy W5ACM



From: Heather MacAllister [mailto:heather@xxxxxxxxxxxxxxxxxx.xxxx
Sent: Sunday, January 14, 2018 11:41 AM
To: Andy MacAllister <w5acm@xxxxxx.xxx>
Subject:



https://www.space.com/38962-npr-planet-money-podcast-launches-cubesat.html



Heather

http://www.facebook.com/HeatherMacAllister

http://www.HeatherMacAllister.com





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

Message: 2
Date: Mon, 15 Jan 2018 00:38:12 -0600
From: "Andy" <w5acm@xxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] FW: cubsat video
Message-ID: <006601d38dcb$6b2f0f00$418d2d00$@xxxxxx.xxx>
Content-Type: text/plain;	charset="us-ascii"

More from PBS

De Andy W5ACM and Heather WB5RMA



From: Heather MacAllister [mailto:heather@xxxxxxxxxxxxxxxxxx.xxxx
Sent: Sunday, January 14, 2018 11:35 AM
To: Andy MacAllister <w5acm@xxxxxx.xxx>
Subject: cubsat video



http://www.pbs.org/video/sci-tech-central-scitech-central-1601-cubesat-revol
ution/



Heather

http://www.facebook.com/HeatherMacAllister

http://www.HeatherMacAllister.com





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

Message: 3
Date: Mon, 15 Jan 2018 00:40:10 -0600
From: "Andy" <w5acm@xxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] FW: cubesats
Message-ID: <006b01d38dcb$b14f7b50$13ee71f0$@xxxxxx.xxx>
Content-Type: text/plain;	charset="us-ascii"

And more from PBS de Andy W5ACM and Heather WB5RMA.



From: Heather MacAllister [mailto:heather@xxxxxxxxxxxxxxxxxx.xxxx
Sent: Sunday, January 14, 2018 11:31 AM
To: Andy MacAllister <w5acm@xxxxxx.xxx>
Subject: cubesats



https://www.pbs.org/newshour/science/these-tiny-satellites-equipped-with-ion
-thrusters-could-change-how-we-explore-space



Heather

http://www.facebook.com/HeatherMacAllister

http://www.HeatherMacAllister.com





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

Message: 4
Date: Mon, 15 Jan 2018 12:33:59 +0100
From: Nico Janssen <hamsat@xxxxxx.xx>
To: amsat-bb@xxxxx.xxxx Ray Hoad <ray.hoad@xxxxxxxx.xxx>
Subject: [amsat-bb] Unknown new satellite
Message-ID: <721f417f-7913-bab5-48c3-5be97a2d3bb0@xxxxxx.xx>
Content-Type: text/plain; charset=utf-8; format=flowed

All,

A new unknown satellite has appeared which has a downlink near
435.085 MHz with 1200 bps FSK AX.25 telemetry. Detailed doppler
measurements show that this satellite is object 43116, 2018-004F.
Probably this is INS 1C, which was launched together with AO 92.
To be confirmed.

73,
Nico PA0DLO




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

Message: 5
Date: Mon, 15 Jan 2018 15:38:20 +0000 (UTC)
From: Robert Switzer <rs2atmink@xxxxx.xxx>
To: amsat-bb@xxxxx.xxxx alex weimer <ingejack@xxx.xxx>
Subject: Re: [amsat-bb] FOX-1D  Now AO-92
Message-ID: <1924204793.3466161.1516030700328@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

where does it show up in satpc32?
when I click on satellites, I see a list of files:
 amateur.txtcubesat.txtgeo.txtintelsat.txtnasa.txtnoaa.txtOrbsmanual.eleweathe
r.txt
so far, I only see 99934 in nasa.txt
Rob KA2CZU



    On Saturday, January 13, 2018, 4:01:48 PM EST, alex weimer
<ingejack@xxx.xxx> wrote:

 FOX-1D has now been officially changed to AO-92? ? Change shown in SATPC32
already? 73? JACK? KC7MG
_______________________________________________
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: 6
Date: Mon, 15 Jan 2018 17:49:04 +0000 (UTC)
From: shakeel saad <shakeelj2k@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Spid ras rotator issue
Message-ID:
<D3A01489B241618E.89b1e485-a2e4-4929-b9e9-a8cc8686e2f3@xxxx.xxxxxxx.xxx>

Content-Type: text/plain; charset=us-ascii

Hi


I have spid ras azimuth elevation rotator. I have set up Satpc32 for yaesu
232 mode to connect with rotator. My Satpc32 is sending azimuth and
elevation to comport. But rotator is not moving. Please tell how do I know
my rotator is installed correctly. I have setup mode of rotator to ps. But
how to confirm or check rotator is installed correctly. The rotator is
moving with moving its supplied mouse.




Any help


Shakeel




Get Outlook for Android





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

Message: 7
Date: Mon, 15 Jan 2018 19:20:36 +0100
From: Erich Eichmann <erich.eichmann@xxxxxxxx.xx>
To: shakeel saad <shakeelj2k@xxxxx.xxx>, AMSAT-BB@xxxxx.xxx
Subject: Re: [amsat-bb] Spid ras rotator issue
Message-ID: <aee0fb7f-caa6-d370-e880-aac5bb8eac37@xxxxxxxx.xx>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi,
did you also choose Yaesu mode in the controller setup and did you
specify COM port and baud rate in the ServerSDX setup window?
SatPC32 supports also the Rot2 mode of the AlfaSpid rotors which is
supported by all AlfaSpid models.? To test it? choose? item 'AlfaSpid'
from the ist of supportd controllers (menu 'Rotor Setup'), click the
upper 'Store' button and restart SatPC32.? Then specify the COM port in
the ServerSpid setup window. The baudrate is fix 600.

73, Erich, DK1TB


Am 15.01.2018 um 18:49 schrieb shakeel saad via AMSAT-BB:
> Hi
>
>
> I have spid ras azimuth elevation rotator. I have set up Satpc32 for yaesu
232 mode to connect with rotator. My Satpc32 is sending azimuth and
elevation to comport. But rotator is not moving. Please tell how do I know
my rotator is installed correctly. I have setup mode of rotator to ps. But
how to confirm or check rotator is installed correctly. The rotator is
moving with moving its supplied mouse.
>
>
>
>
> Any help
>
>
> Shakeel
>
>
>
>
> Get Outlook for Android
>
>
>
> _______________________________________________
> 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: 8
Date: Mon, 15 Jan 2018 13:29:57 -0500 (EST)
From: Zachary Leffke <zleffke@xx.xxx>
To: shakeel saad <shakeelj2k@xxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Spid ras rotator issue
Message-ID:
<2071678870.178432.1516040997006.JavaMail.zimbra@xxxx.xx.xxx>
Content-Type: text/plain; charset=utf-8

Hi Shakeel,
I have a bit of experience with the Alfa Spid systems, so hopefully this
might help.  First question is what type of controller are you using?  We
use the MD-01s at Virginia Tech (MD-02s would be behave the same), but I
believe there is another controller option for these types of rotators (not
sure if they have the same config settings in the other model, also not sure
what the model designation is).

I can say for sure that the protocol for communicating with a RAS (alfa
spid) rotator and a yaesu rotator are completely different.  I personally
don't use SatPC32, so I'm not sure if there is an option in there for
changing it to one of the spid protocols.  We have our MD-01s configured to
communicate using the spid 'Rot2Prog' interface.  So if you see anything
like that in the SatPC32 options, try using that instead of yaesu.

Alternatively, I *think* the MD-01s have a protocol config for emulating
Yaesu systems.  If you hunt through the manuals/settings on the rotator
controller there may be an option for selecting yaesu.  I'm not 100% sure,
but it is possible that even if the option is in the controller for Yaesu,
depending on your model and firmware version it might still not work (even
though the option is in there, it might be for 'future use').  This is not
something I've personally tested since we got the Rot2Prog interface
working, but might be worth trying if SatPC32 doesn't have the configs for
spid systems.

There is also an 'MD-01' option in the MD-01 rotator controller that exposes
more advanced options to the control program......in my experience this is
spotty and 'beta' firmware, and personally i don't trust it (though we
interface with custom software, so the problems there could easily be
entirely my fault in our SW).


Finally, at least for MD-01s, there is a configuration option that needs to
be set to 'activate' the comm port setting.  We actually use the Ethernet
module in our systems, but you might want to make sure that the equivalent
setting for the serial port is 'enabled' on your controller.  In that same
vein make sure you have the right port settings in there as well (baud rate,
stop bits, etc.)


And last bit of advice (and I don't mean this to be snarky, as referenced in
the other thread about linux mailing lists) is carefully read the manuals
and make sure you have the correct manuals for all the settings I mentioned
above.  I bring this up from personal experience because I *didn't*
carefully read the manual and wasted a bunch of time because I didn't have
the right settings on the controller.  Also, I bring this up because the
manuals from Spid are a bit difficult to read through and sometimes not
totally clear.  Further compounding the problem is that there are a few
organizations involved with these systems and they each have their own
manuals (I'm still not sure who does what between Alfa Spid in Canada and
Spid Elektronik in Poland and I think theres one more group somewhere else).
 The manuals can be found here:  http://www.alfaradio.ca/downloads/ (pretty
accurate and I believe current) and also here if you have an MD-01/02
(careful, this link is a direct download of
  the pdf):
https://www.haystack.mit.edu/edu/undergrad/srt/pdf%20files/MD-01%20en.pdf.

Summary:  I recommend using the Rot2Prog protocol on the controller (tried
and true, been in use for a long time, so most 'beta' issues have been
sorted).  Then, if possible, I'd try to see if SatPC32 has a controller
option for 'spid' or 'rot2prog' or something along those lines instead of
yaesu.  Finally, I believe there is a windows based client application that
can be used to interface with the controller (at least there is for the
MD-01s).  I'd recommend using that first with the controller to sort out all
the settings and make sure it is working over the com port first, then try
to switch over to using SatPC32 (I think the windows client can also act as
a DDE client, so maybe it can be used in conjunction with SatPC32 over a DDE
link).

For me there were lots of config testing and changes, sort of one at a time,
until all the stars aligned and it started working.

Good luck! Hopefully this is helpful.  Let us know if you have more questions.

-Zach, KJ4QLP

----- Original Message -----
From: "shakeel saad via AMSAT-BB" <amsat-bb@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Sent: Monday, January 15, 2018 12:49:04 PM
Subject: [amsat-bb] Spid ras rotator issue

Hi


I have spid ras azimuth elevation rotator. I have set up Satpc32 for yaesu
232 mode to connect with rotator. My Satpc32 is sending azimuth and
elevation to comport. But rotator is not moving. Please tell how do I know
my rotator is installed correctly. I have setup mode of rotator to ps. But
how to confirm or check rotator is installed correctly. The rotator is
moving with moving its supplied mouse.




Any help


Shakeel




Get Outlook for Android



_______________________________________________
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: Mon, 15 Jan 2018 20:26:45 +0100
From: Erich Eichmann <erich.eichmann@xxxxxxxx.xx>
To: shakeel saad <shakeelj2k@xxxxx.xxx>, AMSAT-BB@xxxxx.xxx
Subject: [amsat-bb] Completion: Re:  Spid ras rotator issue
Message-ID: <bc9db2cd-c3be-7243-2595-ab564afec22b@xxxxxxxx.xx>
Content-Type: text/plain; charset=utf-8; format=flowed

SatPC32 supports also the AlfaSpiid MD1, MD2 mode.
73s, Erich, DK1TB

Am 15.01.2018 um 18:49 schrieb shakeel saad via AMSAT-BB:
> Hi
>
>
> I have spid ras azimuth elevation rotator. I have set up Satpc32 for yaesu
232 mode to connect with rotator. My Satpc32 is sending azimuth and
elevation to comport. But rotator is not moving. Please tell how do I know
my rotator is installed correctly. I have setup mode of rotator to ps. But
how to confirm or check rotator is installed correctly. The rotator is
moving with moving its supplied mouse.
>
>
>
>
> Any help
>
>
> Shakeel
>
>
>
>
> Get Outlook for Android
>
>
>
> _______________________________________________
> 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: 10
Date: Mon, 15 Jan 2018 17:56:14 +0000
From: Peter Green <peteragreen@xx.xxx>
To: AMSAT-BB@xxxxx.xxx
Subject: Re: [amsat-bb] Spid ras rotator issue
Message-ID: <23D152DC-009F-45A7-9500-6D19755B1882@xx.xxx>
Content-Type: text/plain; charset=us-ascii

I think you need to select  PS-4 for Yaesu


> On 15 Jan 2018, at 17:49, shakeel saad via AMSAT-BB <amsat-bb@xxxxx.xxx>
wrote:
>
> Hi
>
>
> I have spid ras azimuth elevation rotator. I have set up Satpc32 for yaesu
232 mode to connect with rotator. My Satpc32 is sending azimuth and
elevation to comport. But rotator is not moving. Please tell how do I know
my rotator is installed correctly. I have setup mode of rotator to ps. But
how to confirm or check rotator is installed correctly. The rotator is
moving with moving its supplied mouse.
>
>
>
>
> Any help
>
>
> Shakeel
>
>
>
>
> Get Outlook for Android
>
>
>
> _______________________________________________
> 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: 11
Date: Mon, 15 Jan 2018 16:23:27 -0500
From: "Michael A. Foster" <akx2@xxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Fox-1D L-band downshifter
Message-ID: <BC2CF6F608304A8A88B0C1CB167F5875@xxxxxxxxx>
Content-Type: text/plain;	charset="utf-8"

Hello all, Does anybody know how the L-band downshifter experiment is
switched to utilize an uplink
of 1267.350mhz? Thanks, Michael ? n8iup



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

Message: 12
Date: Mon, 15 Jan 2018 17:11:21 -0500
From: "Andrew Glasbrenner" <glasbrenner@xxxxxxxxxx.xxx>
To: "'Michael A. Foster'" <akx2@xxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Fox-1D L-band downshifter
Message-ID: <03f201d38e4d$c66721f0$533565d0$@xxxxxxxxxx.xxx>
Content-Type: text/plain;	charset="utf-8"

By command station only.

73, Drew KO4MA

-----Original Message-----
From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Michael A.
Foster
Sent: Monday, January 15, 2018 4:23 PM
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Fox-1D L-band downshifter

Hello all, Does anybody know how the L-band downshifter experiment is
switched to utilize an uplink of 1267.350mhz? Thanks, Michael ? n8iup

_______________________________________________
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: Mon, 15 Jan 2018 23:24:23 +0100
From: Nico Janssen <hamsat@xxxxxx.xx>
To: amsat-bb@xxxxx.xxxx Ray Hoad <ray.hoad@xxxxxxxx.xxx>,
wa4sca@xxxxx.xxx
Subject: [amsat-bb] AMSAT-OSCAR 92 identified
Message-ID: <fb47e07a-dafc-a1bb-e94e-02ad5361dcd5@xxxxxx.xx>
Content-Type: text/plain; charset=utf-8; format=flowed

All,

Detailed doppler measurements show that AMSAT-OSCAR 92 (AO 92),
earlier called FOX 1D, is object 43137, 2018-004AC.

73,
Nico PA0DLO




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

Message: 14
Date: Mon, 15 Jan 2018 19:15:21 -0500
From: "Ciprian Sufitchi" <ciprian@xxxxxxxx.xxx>
To: "'Nico Janssen'" <hamsat@xxxxxx.xx>, <amsat-bb@xxxxx.xxx>,	"'Ray
Hoad'" <ray.hoad@xxxxxxxx.xxx>, <wa4sca@xxxxx.xxx>
Subject: Re: [amsat-bb] AMSAT-OSCAR 92 identified
Message-ID: <000001d38e5f$19837800$4c8a6800$@xxxxxxxx.xxx>
Content-Type: text/plain;	charset="us-ascii"

The id on website n2yo.com has changed to 43137 (2018-004AC).
http://www.n2yo.com/satellite/?s=43137

73s de Chip N2YO

-----Original Message-----
From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Nico Janssen
Sent: Monday, January 15, 2018 5:24 PM
To: amsat-bb@xxxxx.xxxx Ray Hoad <ray.hoad@xxxxxxxx.xxx>; wa4sca@xxxxx.xxx
Subject: [amsat-bb] AMSAT-OSCAR 92 identified

All,

Detailed doppler measurements show that AMSAT-OSCAR 92 (AO 92), earlier
called FOX 1D, is object 43137, 2018-004AC.

73,
Nico PA0DLO


_______________________________________________
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: 15
Date: Tue, 16 Jan 2018 06:31:34 +0000 (UTC)
From: Ronald Oldham <rgoldham@xxxxxxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] 488 US Grids Completed
Message-ID: <1181990089.1587849.1516084294126@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8


On Sunday I was able to log the last grid I needed to complete the 488 US
grids . I would like to publicly thank Doug - N6UA for going out of his way
to help me get DN23 in my log. Without the efforts of many portable
satellite operators like Doug it would not be possible to achieve this
accomplishment.? In reviewing my log I would like to acknowledge the help of
the following "top ten" portable operators and provide the number grids that
I received because of their efforts
1 ND9M 332 K8YSE 273 AC0RA 234 W5PFG 205 WC7V 126 WD9EWK 117 KA6SIP 108 NJ7H
? 89 AA5CK 710 KB5WIA 610 KB0RZD 6
Many thanks to all of the operators that helped me throughout the years.
73,
Ron - N8RO



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

Message: 16
Date: Tue, 16 Jan 2018 09:13:00 +0100
From: ok2gz <ok2gz@xxxxxx.xx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] AMSAT-OSCAR 92 identified
Message-ID: <6556fb84-2efb-0e1f-7959-105c663fc65e@xxxxxx.xx>
Content-Type: text/plain; charset=utf-8; format=flowed

How to get TLE data with Norad ID 43137 ?

Thanks to Nico PA0DLO for identifying AO-92. He did the same job in case
of AO-91.
When we know the Norad ID 43137, where I can find these TLE data?
Automatic update of GPredict the data did not reach, they are not on the
celestrak-web page tle-new also...
Can anybody help me and others too?

73
 ??? jarda ok2gz

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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

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 13, Issue 22
****************************************


Read previous mail | Read next mail


 11.05.2024 07:28:17lGo back Go up