| |
CX2SA > SATDIG 18.09.19 02:24z 1002 Lines 35864 Bytes #999 (0) @ WW
BID : AMSATBB14353
Read: GUEST
Subj: AMSAT-BB-digest V14 353
Path: HB9ON<IW2OHX<IQ2LB<IZ3LSV<I0OJJ<I0OJJ<N6RME<CX2SA
Sent: 190918/0215Z @:CX2SA.SAL.URY.SOAM #:14310 [Salto] FBB7.00e $:AMSATBB14353
>From cx2sa%cx2sa.sal.ury.soam@i0ojj.ampr.org Wed Sep 18 04:17:43 2019
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0k.3b2) with SMTP
id AA27034 ; Wed, 18 Sep 2019 04:17:43 +0200
Message-Id: <AMSATBB14353@xfbb.bbs>
>From: cx2sa@cx2sa.sal.ury.soam
X-JNOS-User-Port: Telnet (xfbb @ 44.134.32.240) -> Sending message
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: How to tame gr-satellites? (John Zaruba)
2. Re: How to tame gr-satellites? (Edson W. R. Pereira)
3. Taurus-1 FM/Codec2 Voice Repeater Active (Scott)
4. Re: How to tame gr-satellites? (Daniel Est?vez)
5. Re: How to tame gr-satellites? (Hans BX2ABT)
6. Hackaday article on the Lunar Gateway. (Hans BX2ABT)
7. Upcoming ARISS contact with Boys and Girls Club, Ft. Meade,
MD (n4csitwo@?????????.????
8. Upcoming ARISS contact with Boys and Girls Club, Ft. Meade,
MD - CORRECTED RELEASE (n4csitwo@?????????.????
----------------------------------------------------------------------
Message: 1
Date: Tue, 17 Sep 2019 09:18:46 -0400
From: John Zaruba <aa2bn@???????.???>
To: amsat-bb@?????.???
Subject: Re: [amsat-bb] How to tame gr-satellites?
Message-ID: <F43A0FB7-510C-404B-84E8-41E4A24C4141@???????.???>
Content-Type: text/plain; charset=utf-8
I completely agree with Hans? point, but to put it more succinctly:
Don?t give me a fish, teach me how to fish.
It would be excellent to have a series of YouTube videos ( or a series of
Journal articles)to follow to learn the ins-and-outs of gr-satellites.
73,
John K2ZA
Sent from my iPhone
------------------------------
Message: 2
Date: Tue, 17 Sep 2019 11:09:55 -0300
From: "Edson W. R. Pereira" <ewpereira@?????.???>
To: amsat-bb@?????.???
Subject: Re: [amsat-bb] How to tame gr-satellites?
Message-ID:
<CALNQy4-==63MPK-5AqghLkH4cZusY9mgKt=oVNaoa6Wf5=UvKQ@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Hi John and Hans,
I agree with all said and also share the frustration. Gnuradio is a huge
framework. It is a like a lego and the only way to make sense of things is
to understand how to use the blocks -- and this may require understanding
the guts of some of the blocks. Unfortunately gnuradio's documentation is
no so good from the point of view of an user. It expects the user to be
familiar with SDR and DSP. Many of the blocks have controls that can only
be understood after reading about their functions in a DSP book -- and that
on itself is not an easy endeavor.
Daniel?s gr-satellites is a remarkable piece of work and talent. I agree
with Daniel that his time is better used to develop and polish the modules.
I think what if could have more people using gr-satellites, we as users
could develop some howtos. Perhaps a discussion group dedicated to
gr-satellites could help. What do you think?
73, Edson PY2SDR
On Tue, Sep 17, 2019 at 10:20 AM John Zaruba via AMSAT-BB <
amsat-bb@?????.???> wrote:
> I completely agree with Hans? point, but to put it more succinctly:
>
> Don?t give me a fish, teach me how to fish.
>
> It would be excellent to have a series of YouTube videos ( or a series of
> Journal articles)to follow to learn the ins-and-outs of gr-satellites.
>
> 73,
>
> John K2ZA
>
> Sent from my iPhone
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: https://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 3
Date: Tue, 17 Sep 2019 13:55:24 -0400
From: Scott <scott23192@?????.???>
To: amsat-bb@?????.???
Subject: [amsat-bb] Taurus-1 FM/Codec2 Voice Repeater Active
Message-ID:
<CAJCSnOZwarxcu9_VM32oX-WJBcR90-GtUqB7T5Ai2aanebS=cQ@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
The FM / Codec2 voice repeater on Taurus-1 went "live" today (17-Sept-2019)
with 2 passes available to stations on the U.S. East Coast.
W2RTV posted a video of the entire pass as seen from his station at
https://www.youtube.com/watch?v=ge9mSscTZYg
The spacecraft is clearly spinning at a high rate; my receive audio wasn't
nearly as good as Rocco's, but he's got a vastly superior antenna setup, so
that never hurts.
The repeater's uplink is normal FM on 145.820 MHz w/ a 67 Hz CTCSS tone.
High power is definitely not needed but adjusting for uplink doppler can
help extend your range.
The downlink is a Codec2 digital stream at 9600 BPSK which you receive as
USB on 435.840 MHz. That gets you in the ballpark, anyway. Once downlink
packets are observed, center your 15k-wide USB window on the packets and
doppler track from there.
The digital voice stream (as well as telemetry) decodes with a flowgraph in
GNU Radio. The original telemetry decoder for Taurus-1 was produced by
EA4GPZ and is located at https://github.com/daniestevez/gr-satellites
Several of us have added to Dani's flowgraph to provide audio output now
that the repeater is active. That hybrid flowgraph can be found at:
https://www.qsl.net/k/k4kdr//grc/taurus1-k4kdr-telem+audio-v1.grc
Note that both the original decoder from Dani as well as the hybrid
voice/telemetry flowgraph expect UDP audio input such as from GQRX.
Here is a Tweet I posted after my first contact on the repeater today with
a screen shot which pretty clearly shows how the spacecraft is spinning:
https://twitter.com/scott23192/status/1174001658419994624
This repeater seems to work extremely well and should be way better if the
spin rate reduces over time. Hope to hear more people on!
-Scott, K4KDR
------------------------------
Message: 4
Date: Wed, 18 Sep 2019 01:15:59 +0200
From: Daniel Est?vez <daniel@????????.???>
To: Hans BX2ABT <hans.bx2abt@???.?????.???>, amsat-bb@?????.???
Subject: Re: [amsat-bb] How to tame gr-satellites?
Message-ID: <6a8ec4ad-9703-834b-b7ba-b2baa68fd87f@????????.???>
Content-Type: text/plain; charset=utf-8
Hi Hans,
I'm taking your email as constructive criticism, so I'll discuss on
ideas about how to improve the documentation or procedures rather than
on how many people use GNU Radio or gr-satellites and whether this is
satisfactory.
One problem is that some things that might seem so obvious when you are
really involved with some software/framework are not obvious at all for
newcomers. With these things, many times a few extra sentences in the
documentation can help a lot. And usually the best advice comes from
newcomers: the pitfalls they found and how to help others avoid them.
This said, answers to particular points below.
El 17/9/19 a las 8:58, Hans BX2ABT escribi?:
> On the gr-satellites github page it says you need to fulfill some
> dependency requirements before compiling gr-satellites.
>
> [quote]
>
> * Phil Karn's KA9Q |libfec|. A fork that builds in modern linux
> systems can be found here <https://github.com/daniestevez/libfec>.
> * construct <https://construct.readthedocs.io/en/latest/>, at least
> version 2.9.
> * requests <https://pypi.org/project/requests/2.7.0/>.
> * swig <http://www.swig.org/>
>
> [/unquote]
>
> The above is very ambiguous. It indicates "why" but not "how".
>
> 1) Do I have to compile and install all this myself, or can they be
> found in my distro's repositories?
>
> 2) Are they all installed with ./configure, make, make install or are
> there other methods?
>
> The answers are (I think, but not sure):
>
> 1) You do have to compile and install the first three, but you can use
> swig from you distro's repository.
>
> 2) libfec is compiled with ./configure, make, make install. Construct
> and requests can be found in distro's repositories but are probably
> older versions and they are called (on Debian systems) python-construct
> and python requests. So the best way to go is to install by using pip.
The problem with this is that it depends a lot on what particular
distribution or setup you are using. Maybe your distribution ships a
recent version of GNU Radio and you installed that. Maybe you compiled
it from source. Maybe swig came as a dependency as you installed GNU
Radio. Maybe not and you need to install it explicitly. Maybe your
distribution has packaged recent enough versions of construct or
requests. Maybe not and you are better off using pip. Or maybe you
Python installation is based on Anaconda, so you install all Python
packages using conda. Or maybe you used PyBOMBs to install GNU Radio and
gr-satellites instead of your distributions' package manager. Or maybe
you are using Arch, which has an AUR package for gr-satellites.
Certainly it is hard (especially for a single person) to give precise
instructions covering all these use cases.
However, I see a couple possible solutions:
1) Identify the case that typically should work for most people. This is
more or less what you said: install GNU Radio, SWIG and requests through
your package's manager, install construct through pip, install libfec
from source, and install gr-satellites from source.
I think this would be the recommended steps in Ubuntu 19.04, which seems
the most popular distribution, and is also what I'm doing on Gentoo.
2) Try to get help from the community to describe precise installation
steps for different distributions and/or setups. Actually Github
supports Wiki pages for the repositories. I'm not currently using this
feature, but perhaps it could be useful to open up an "Installation"
wiki page where people can detail installation steps for different distros.
I think option 2) might be more desirable, but I'm not sure if I could
get enough people to engage and maintain good quality and up to date
instructions (this is important as new distros get released).
Option 1) might be much easier to set up and could be accomplished by
adding an "Installation of dependencies" section to the README.
I agree that having some installation instructions that you can simply
copy & paste onto the command line can save time and effort even to very
experienced people.
> Another example. I've got GNU Radio and gr-satellites installed and I
> figured out where the .grc files were hiding. I open one and am greeted
> with loads of red because of missing blocks. There is also another
> warning that says "Port is not connected". I've been reading and
> searching the web for two hours already, but still haven't got a clue
> about the "why" and certainly not about "how" to proceed now. I don't
> mind trouble shooting, but then I need at least some hints to get
> started. Right now I haven't.
This might be because you haven't installed the hierarchical flowgraphs.
It is described in the README. Ideally I would like this step to run
automatically from CMake, but I haven't been able to find how.
Therefore, it needs to be run manually. Maybe with the updated CMake
infrastructure in GNU Radio 3.8 it will be easier to do this automatically.
If you have indeed installed the hierarchical flowgraphs and are getting
missing blocks, please detail which blocks are missing.
> Third example: last year I did have a working GNURadio/gr-satellites
> setup with pyBOMBS (before that broke). I did see some telemetry rolling
> down a terminal window, but the last block in every flow graph is always
> this SatNogs Telemetry Forwarder. Tried to figure out if it was actually
> forwarding, where it ended up, where I could see my forwarded data.
> Couldn't figure it out, couldn't find any documentation or examples, so
> I gave up.
There is also either a telemetry parser block or a debug message block
as last block (in parallel with the telemetry forwarder) which is in
charge of printing the telemetry values that appear in the terminal window.
Regarding the SatNOGS telemetry forwarder, this is documented in the
README, in a section called "Submitting telemetry to SatNOGS", which I
think already answers some of your questions.
As you'll see, you need to specify your callsign and location to submit
telemetry to SatNOGS, so unless you did set these, then the forwarder
was simply doing nothing.
The questions that occur to me that are not explicitly treated in the
documentation are:
* How do I know if this is working? It happens that the forwarder will
print nothing when a frame is submitted correctly. However, if there is
some error, the forwarder will print an error message. I figured out
this was the most useful approach, as it would be too verbose to print
out a message anytime that a packet is submitted successfully. However,
as this design choice is not obvious, perhaps a sentence should be added
to the documentation.
* Where do the frames end up in SatNOGS DB. Of course the answer is that
you need to got to SatNOGS DB webpage, select the particular satellite,
scroll to the bottom, and there you have some links to download the
frames in the database (which in my experience might or might not work
depending on how much data you request). However, I think that this
functionality should be documented from SatNOGS side rather than from
the gr-satellites side. Somehow, in the 2Submitting telemetry to
SatNOGS" section of the README it is assumed that you know what SatNOGS
DB is.
So to wrap up:
It is possible to create a Wiki page on Github were people can
contribute with documentation to help others (installation instructions,
setup descriptions, interfacing with other software). I can set this up.
Would be people interested in contributing?
Regarding the README, I'm open for pull requests with improvements or
with concreted ideas about how to improve it.
73,
Dani.
------------------------------
Message: 5
Date: Wed, 18 Sep 2019 08:44:59 +0800
From: Hans BX2ABT <hans.bx2abt@???.?????.???>
To: Daniel Est?vez <daniel@????????.???>, amsat-bb@?????.???
Subject: Re: [amsat-bb] How to tame gr-satellites?
Message-ID: <ee673db7-ebd4-195f-db91-cb39e2bad881@???.?????.???>
Content-Type: text/plain; charset=utf-8; format=flowed
Hello Daniel,
Thanks for taking my writing in stride and you are right: being deeply
involved in something might narrow one's vision, especially compared to
people not in the know. But from your reaction I am confident we're
getting ahead in making gr-satellites even more accessible.
Your suggestion for a Wiki on GitHub is a good one and I will certainly
be a contributor. I am not sure if this Wiki will need an administrator
or moderator, but if it does then I'm willing to help out there, too, if
no better candidate is available.
As for the README, I'm not very familiar with GitHub and how to create a
pull request, but I'll look into it tonight. As you can tell from my
previous post I do have some ideas on how to improve it.
I'll leave it at that for now. 73 de Hans
On 09/18/2019 07:15 AM, Daniel Est?vez wrote:
> Hi Hans,
>
> I'm taking your email as constructive criticism, so I'll discuss on
> ideas about how to improve the documentation or procedures rather than
> on how many people use GNU Radio or gr-satellites and whether this is
> satisfactory.
>
> One problem is that some things that might seem so obvious when you are
> really involved with some software/framework are not obvious at all for
> newcomers. With these things, many times a few extra sentences in the
> documentation can help a lot. And usually the best advice comes from
> newcomers: the pitfalls they found and how to help others avoid them.
>
> This said, answers to particular points below.
>
> El 17/9/19 a las 8:58, Hans BX2ABT escribi?:
>
>> On the gr-satellites github page it says you need to fulfill some
>> dependency requirements before compiling gr-satellites.
>>
>> [quote]
>>
>> * Phil Karn's KA9Q |libfec|. A fork that builds in modern linux
>> systems can be found here <https://github.com/daniestevez/libfec>.
>> * construct <https://construct.readthedocs.io/en/latest/>, at least
>> version 2.9.
>> * requests <https://pypi.org/project/requests/2.7.0/>.
>> * swig <http://www.swig.org/>
>>
>> [/unquote]
>>
>> The above is very ambiguous. It indicates "why" but not "how".
>>
>> 1) Do I have to compile and install all this myself, or can they be
>> found in my distro's repositories?
>>
>> 2) Are they all installed with ./configure, make, make install or are
>> there other methods?
>>
>> The answers are (I think, but not sure):
>>
>> 1) You do have to compile and install the first three, but you can use
>> swig from you distro's repository.
>>
>> 2) libfec is compiled with ./configure, make, make install. Construct
>> and requests can be found in distro's repositories but are probably
>> older versions and they are called (on Debian systems) python-construct
>> and python requests. So the best way to go is to install by using pip.
> The problem with this is that it depends a lot on what particular
> distribution or setup you are using. Maybe your distribution ships a
> recent version of GNU Radio and you installed that. Maybe you compiled
> it from source. Maybe swig came as a dependency as you installed GNU
> Radio. Maybe not and you need to install it explicitly. Maybe your
> distribution has packaged recent enough versions of construct or
> requests. Maybe not and you are better off using pip. Or maybe you
> Python installation is based on Anaconda, so you install all Python
> packages using conda. Or maybe you used PyBOMBs to install GNU Radio and
> gr-satellites instead of your distributions' package manager. Or maybe
> you are using Arch, which has an AUR package for gr-satellites.
>
> Certainly it is hard (especially for a single person) to give precise
> instructions covering all these use cases.
>
> However, I see a couple possible solutions:
>
> 1) Identify the case that typically should work for most people. This is
> more or less what you said: install GNU Radio, SWIG and requests through
> your package's manager, install construct through pip, install libfec
> from source, and install gr-satellites from source.
>
> I think this would be the recommended steps in Ubuntu 19.04, which seems
> the most popular distribution, and is also what I'm doing on Gentoo.
>
> 2) Try to get help from the community to describe precise installation
> steps for different distributions and/or setups. Actually Github
> supports Wiki pages for the repositories. I'm not currently using this
> feature, but perhaps it could be useful to open up an "Installation"
> wiki page where people can detail installation steps for different distros.
>
> I think option 2) might be more desirable, but I'm not sure if I could
> get enough people to engage and maintain good quality and up to date
> instructions (this is important as new distros get released).
>
> Option 1) might be much easier to set up and could be accomplished by
> adding an "Installation of dependencies" section to the README.
>
> I agree that having some installation instructions that you can simply
> copy & paste onto the command line can save time and effort even to very
> experienced people.
>
>> Another example. I've got GNU Radio and gr-satellites installed and I
>> figured out where the .grc files were hiding. I open one and am greeted
>> with loads of red because of missing blocks. There is also another
>> warning that says "Port is not connected". I've been reading and
>> searching the web for two hours already, but still haven't got a clue
>> about the "why" and certainly not about "how" to proceed now. I don't
>> mind trouble shooting, but then I need at least some hints to get
>> started. Right now I haven't.
> This might be because you haven't installed the hierarchical flowgraphs.
> It is described in the README. Ideally I would like this step to run
> automatically from CMake, but I haven't been able to find how.
> Therefore, it needs to be run manually. Maybe with the updated CMake
> infrastructure in GNU Radio 3.8 it will be easier to do this automatically.
>
> If you have indeed installed the hierarchical flowgraphs and are getting
> missing blocks, please detail which blocks are missing.
>
>> Third example: last year I did have a working GNURadio/gr-satellites
>> setup with pyBOMBS (before that broke). I did see some telemetry rolling
>> down a terminal window, but the last block in every flow graph is always
>> this SatNogs Telemetry Forwarder. Tried to figure out if it was actually
>> forwarding, where it ended up, where I could see my forwarded data.
>> Couldn't figure it out, couldn't find any documentation or examples, so
>> I gave up.
> There is also either a telemetry parser block or a debug message block
> as last block (in parallel with the telemetry forwarder) which is in
> charge of printing the telemetry values that appear in the terminal window.
>
> Regarding the SatNOGS telemetry forwarder, this is documented in the
> README, in a section called "Submitting telemetry to SatNOGS", which I
> think already answers some of your questions.
>
> As you'll see, you need to specify your callsign and location to submit
> telemetry to SatNOGS, so unless you did set these, then the forwarder
> was simply doing nothing.
>
> The questions that occur to me that are not explicitly treated in the
> documentation are:
>
> * How do I know if this is working? It happens that the forwarder will
> print nothing when a frame is submitted correctly. However, if there is
> some error, the forwarder will print an error message. I figured out
> this was the most useful approach, as it would be too verbose to print
> out a message anytime that a packet is submitted successfully. However,
> as this design choice is not obvious, perhaps a sentence should be added
> to the documentation.
>
> * Where do the frames end up in SatNOGS DB. Of course the answer is that
> you need to got to SatNOGS DB webpage, select the particular satellite,
> scroll to the bottom, and there you have some links to download the
> frames in the database (which in my experience might or might not work
> depending on how much data you request). However, I think that this
> functionality should be documented from SatNOGS side rather than from
> the gr-satellites side. Somehow, in the 2Submitting telemetry to
> SatNOGS" section of the README it is assumed that you know what SatNOGS
> DB is.
>
>
> So to wrap up:
>
> It is possible to create a Wiki page on Github were people can
> contribute with documentation to help others (installation instructions,
> setup descriptions, interfacing with other software). I can set this up.
> Would be people interested in contributing?
>
> Regarding the README, I'm open for pull requests with improvements or
> with concreted ideas about how to improve it.
>
> 73,
>
> Dani.
>
>
>
------------------------------
Message: 6
Date: Wed, 18 Sep 2019 08:47:54 +0800
From: Hans BX2ABT <hans.bx2abt@???.?????.???>
To: AMSAT <amsat-bb@?????.???>
Subject: [amsat-bb] Hackaday article on the Lunar Gateway.
Message-ID: <d5e95854-3f41-1f80-6352-d9af05f9583f@???.?????.???>
Content-Type: text/plain; charset=utf-8; format=flowed
Saw an article on Hackaday.com about hams and the Lunar Gateway. Might
be an interesting, even though it's not very in-dept.
https://hackaday.com/2019/09/16/hams-in-space-gearing-up-for-the-lunar-gateway
/
73 de Hans
------------------------------
Message: 7
Date: Tue, 17 Sep 2019 21:54:42 -0400
From: <n4csitwo@?????????.???>
To: <amsat-bb@?????.???>, <ariss-press@?????.???>
Subject: [amsat-bb] Upcoming ARISS contact with Boys and Girls Club,
Ft. Meade, MD
Message-ID: <A27A56105D9F4431AC92712093D82B5B@???>
Content-Type: text/plain; charset="iso-8859-1"
An International Space Station school contact has been planned with
participants at Boys and Girls Club, Ft. Meade, MD on 18 Sept. The event is
scheduled to begin at approximately 19:58 UTC. It is recommended that you
start listening approximately 10 minutes before this time. The duration of
the contact is approximately 9 minutes and 30 seconds. The contact will be a
telebridge between NA1SS and VK4KHZ. The contact should be audible over
portions of Australia and adjacent areas. Interested parties are invited to
listen in on the 145.80 MHz downlink. The contact is expected to be
conducted in English.
Story:
The Fort Meade, Maryland Middle School / Teen (MST) Program provides an
after-school and summer camp program for youth ages 11 to 18 (grades 6 -
12). The program has 174 enrolled members and 50 - 60 youth attend on any
given day. Half of the youth that attend are from military families, and
most of the other half have parents who work in DoD in some capacity. The
MST Program encourages middle school and high school teenagers to be the
best that they can be by challenging them through various means. It
provides a safe and supervised environment for youth engagement. Youth are
provided internet access, snacks, homework help, game systems, a basketball
court, music equipment, pool table, and ping-pong table.
Through a generous grant from Raytheon through the Boys and Girls Clubs of
America (BGCA), the program recently constructed a state of the art STEM
center known as the Center of Innovation (COI), which incorporates training
for MST Program staff, STEM events throughout the year, and a newly
remodeled room with new STEM equipment for pushing the envelope in STEM
experiences. Youth are now offered activities such as CAD, 3D printing and
carving, and building circuits, to name a few. With the implementation of
the COI, engineers and technologists of Raytheon, as well as government
agencies such as DISA and NSA, consistently volunteer their time to offer
STEM activities to youth. The program welcomes volunteers and the broader
perspective that they bring.
Participants will ask as many of the following questions as time allows:
1. Do you have any customs for greeting arriving astronauts?
2. Do you feel trapped by not being able to go outside whenever you want?
3. Can you see the whole earth from up there?
4. How does it feel to sleep in space?
5. Is the experience of being on the ISS worth being gone for so long?
6. How old do you have to be to go into space?
7. What are your roles?
8. What is your favorite type of work on the ISS?
9. What is the most interesting experiment you're doing on the ISS?
10. What kinds of things do you build with your 3D printers?
11. When you return to earth, do you feel completely different?
12. What do you eat, and how do you store your food?
13. What is your favorite space food?
14. Can you all participate in space walks?
15. Do you feel lost or disoriented when space-walking?
16. As a team, how do you resolve your differences?
17. What's the view like up there?
18. What happens when you get sick?
19. How long have you been up there?
20. Are you ready to come back home?
21. What do you do when you're onboard?
22. What do you do for fun?
23. How do you solve your problems when they arise?
24. What is it like to live and work in space?
PLEASE CHECK THE FOLLOWING FOR MORE INFORMATION ON ARISS UPDATES:
Visit ARISS on Facebook. We can be found at Amateur Radio on the
International Space Station (ARISS).
To receive our Twitter updates, follow @????????????
Next planned event(s):
1. School in Bulgaria, direct via TBD
The ISS callsign is presently scheduled to be RS?ISS
The scheduled astronaut is TBD
Contact is go for Tue 2019-09-24 16:10 UTC
2. UAE school #1 with Space Flight participant, direct via TBD
The ISS callsign is presently scheduled to be RS?ISS
The scheduled astronaut is TBD
Contact is go for Fri 2019-09-27 12:10 UTC
3. UAE school #2 with Space Flight participant, direct via TBD
The ISS callsign is presently scheduled to be RS?ISS
The scheduled astronaut is TBD
Contact is go for Sat 2019-09-28 11:20 UTC
4. UAE school #3 with Space Flight participant, direct via TBD
The ISS callsign is presently scheduled to be RS?ISS
The scheduled astronaut is TBD
Contact is go for Tue 2019-10-01 TBD UTC
About ARISS
Amateur Radio on the International Space Station (ARISS) is a cooperative
venture of international amateur radio societies and the space agencies that
support the International Space Station (ISS). In the United States,
sponsors are the Radio Amateur Satellite Corporation (AMSAT), the American
Radio Relay League (ARRL), the ISS National Lab and National Aeronautics and
Space Administration (NASA). The primary goal of ARISS is to promote
exploration of science, technology, engineering, and mathematics (STEM)
topics by organizing scheduled contacts via amateur radio between crew
members aboard the ISS and students in classrooms or public forms. Before
and during these radio contacts, students, educators, parents, and
communities learn about space, space technologies, and amateur radio. For
more information, see www.ariss.org.
Thank you & 73,
David - AA4KN
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------
Message: 8
Date: Tue, 17 Sep 2019 22:04:40 -0400
From: <n4csitwo@?????????.???>
To: <amsat-bb@?????.???>, <ariss-press@?????.???>
Subject: [amsat-bb] Upcoming ARISS contact with Boys and Girls Club,
Ft. Meade, MD - CORRECTED RELEASE
Message-ID: <98A4F232F7114CA7A272AA1AB283703D@???>
Content-Type: text/plain; charset="iso-8859-1"
PLEASE NOTE THAT THIS RELEASE REPLACES THE INITIAL FT. MEADE, MD. CONTACT
RELEASE SENT AT 01:57 UTC ON 9-18-2019. THE CONTACT DATE ON THE INITIAL
RELEASE WAS INCORRECT.
An International Space Station school contact has been planned with
participants at Boys and Girls Club, Ft. Meade, MD on 20 Sept. The event is
scheduled to begin at approximately 19:58 UTC. It is recommended that you
start listening approximately 10 minutes before this time. The duration of
the contact is approximately 9 minutes and 30 seconds. The contact will be a
telebridge between NA1SS and VK4KHZ. The contact should be audible over
portions of Australia and adjacent areas. Interested parties are invited to
listen in on the 145.80 MHz downlink. The contact is expected to be
conducted in English.
Story:
The Fort Meade, Maryland Middle School / Teen (MST) Program provides an
after-school and summer camp program for youth ages 11 to 18 (grades 6 -
12). The program has 174 enrolled members and 50 - 60 youth attend on any
given day. Half of the youth that attend are from military families, and
most of the other half have parents who work in DoD in some capacity. The
MST Program encourages middle school and high school teenagers to be the
best that they can be by challenging them through various means. It
provides a safe and supervised environment for youth engagement. Youth are
provided internet access, snacks, homework help, game systems, a basketball
court, music equipment, pool table, and ping-pong table.
Through a generous grant from Raytheon through the Boys and Girls Clubs of
America (BGCA), the program recently constructed a state of the art STEM
center known as the Center of Innovation (COI), which incorporates training
for MST Program staff, STEM events throughout the year, and a newly
remodeled room with new STEM equipment for pushing the envelope in STEM
experiences. Youth are now offered activities such as CAD, 3D printing and
carving, and building circuits, to name a few. With the implementation of
the COI, engineers and technologists of Raytheon, as well as government
agencies such as DISA and NSA, consistently volunteer their time to offer
STEM activities to youth. The program welcomes volunteers and the broader
perspective that they bring.
Participants will ask as many of the following questions as time allows:
1. Do you have any customs for greeting arriving astronauts?
2. Do you feel trapped by not being able to go outside whenever you want?
3. Can you see the whole earth from up there?
4. How does it feel to sleep in space?
5. Is the experience of being on the ISS worth being gone for so long?
6. How old do you have to be to go into space?
7. What are your roles?
8. What is your favorite type of work on the ISS?
9. What is the most interesting experiment you're doing on the ISS?
10. What kinds of things do you build with your 3D printers?
11. When you return to earth, do you feel completely different?
12. What do you eat, and how do you store your food?
13. What is your favorite space food?
14. Can you all participate in space walks?
15. Do you feel lost or disoriented when space-walking?
16. As a team, how do you resolve your differences?
17. What's the view like up there?
18. What happens when you get sick?
19. How long have you been up there?
20. Are you ready to come back home?
21. What do you do when you're onboard?
22. What do you do for fun?
23. How do you solve your problems when they arise?
24. What is it like to live and work in space?
PLEASE CHECK THE FOLLOWING FOR MORE INFORMATION ON ARISS UPDATES:
Visit ARISS on Facebook. We can be found at Amateur Radio on the
International Space Station (ARISS).
To receive our Twitter updates, follow @????????????
Next planned event(s):
1. School in Bulgaria, direct via TBD
The ISS callsign is presently scheduled to be RS?ISS
The scheduled astronaut is TBD
Contact is go for Tue 2019-09-24 16:10 UTC
2. UAE school #1 with Space Flight participant, direct via TBD
The ISS callsign is presently scheduled to be RS?ISS
The scheduled astronaut is TBD
Contact is go for Fri 2019-09-27 12:10 UTC
3. UAE school #2 with Space Flight participant, direct via TBD
The ISS callsign is presently scheduled to be RS?ISS
The scheduled astronaut is TBD
Contact is go for Sat 2019-09-28 11:20 UTC
4. UAE school #3 with Space Flight participant, direct via TBD
The ISS callsign is presently scheduled to be RS?ISS
The scheduled astronaut is TBD
Contact is go for Tue 2019-10-01 TBD UTC
About ARISS
Amateur Radio on the International Space Station (ARISS) is a cooperative
venture of international amateur radio societies and the space agencies that
support the International Space Station (ISS). In the United States,
sponsors are the Radio Amateur Satellite Corporation (AMSAT), the American
Radio Relay League (ARRL), the ISS National Lab and National Aeronautics and
Space Administration (NASA). The primary goal of ARISS is to promote
exploration of science, technology, engineering, and mathematics (STEM)
topics by organizing scheduled contacts via amateur radio between crew
members aboard the ISS and students in classrooms or public forms. Before
and during these radio contacts, students, educators, parents, and
communities learn about space, space technologies, and amateur radio. For
more information, see www.ariss.org.
Thank you & 73,
David - AA4KN
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------
Subject: Digest Footer
_______________________________________________
Sent via amsat-bb@?????.???.
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!
https://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
End of AMSAT-BB Digest, Vol 14, Issue 353
*****************************************
Read previous mail | Read next mail
| |
