| |
CX2SA > SATDIG 21.04.16 19:09l 924 Lines 32886 Bytes #999 (0) @ WW
BID : AMSATBB11129
Read: GUEST
Subj: AMSAT-BB-digest V11 129
Path: IW8PGT<HB9CSR<IK2XDE<DB0RES<DB0OVN<DB0GOS<ON0AR<OZ5BBS<CX2SA
Sent: 160421/1700Z @:CX2SA.SAL.URY.SOAM #:42522 [Salto] FBB7.00e $:AMSATBB11129
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: ISS Beacons (Richard Tejera)
2. Upcoming ARISS Contact Schedule as of 2016-04-21 05:30 UTC
(AJ9N@xxx.xxxx
3. Re: ISS Unattended Beacon Theory (UBT) - PROVE ME WRONG!
(Robert McGwier)
4. Re: ISS Unattended Beacon Theory (UBT) - PROVE ME WRONG!
(Robert Bruninga)
5. Need help decoding EO-79 packets. (Jeff A. Boyd)
6. Re: ISS Unattended Beacon Theory (UBT) - PROVE ME WRONG!
(Robert McGwier)
7. Re: Need help decoding EO-79 packets. (Mike Rupprecht)
8. Re: Need help decoding EO-79 packets. (PE0SAT | Amateur Radio)
9. Re: ISS Unattended Beacon Theory (UBT) - PROVE ME WRONG!
(Stefan Wagener)
----------------------------------------------------------------------
Message: 1
Date: Wed, 20 Apr 2016 20:41:33 -0700
From: Richard Tejera <Saguaroastro@xxx.xxx>
To: "amsat-bb@xxxxxx.xxxx <amsat-bb@xxxxxx.xxx>, 'AMSAT'
<amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ISS Beacons
Message-ID: <vt42d7t21bix3plcc8oiysfi.1461210093254@xxxxx.xxxxxxx.xxx>
Content-Type: text/plain; charset=utf-8
It does, or do have most of the info already stored in the user phrases
What I was looking for was sending the message to ALL.
I would them in the message text past the appropriate user phrase (F key
-->x, where x is the user phrase.
There is a good pass tomorrow about 1130 mst/2830 UT. I'll take an early
lunch and see if anyone answers. I'll be in DM43
73
Rick Tejera K7TEJ
Saguaro Astronomy Club
www.SaguaroAstro.org
Thunderbird Amateur Radio Club
www.w7tbc.org
On April 20, 2016, at 20:27, "Patrick STODDARD (WD9EWK/VA7EWK)"
<amsat-bb@xxxxxx.xxx> wrote:
Rick,
On my TH-D72A, there are a couple of options for sending a CQ call. First,
a few settings need for the HT to be heard through the ISS or NO-84
packet digipeater...
Status Text: I use message number 1 with TX rate 1/1, and I use "WD9EWK
and VA7EWK" as the text. The TX rate determines how often this text is
transmitted, and 1/1 means everytime your HT transmits your location, this
text will also go out with that. You could use something like "CQ de
K7TEJ" or something like that to draw attention to yourself. Since I use
my HT on both the spaceborne digipeaters and the terrestrial APRS network,
I don't normally want to have a CQ call in that text field. Sometimes I
will replace the "and VA7EWK" with other text if I am at a hamfest or on
a trip, or I'll turn it into something like "WD9EWK and VA7EWK - 2016 World
Tour". :-)
You can store up to 5 different status text messages, and then
select different messages for different situations. You could
have a CQ call in one, another message with something like your
e-mail address or the repeater you're listening to in another,
etc. I just use the first status text message, and change it as
needed.
TX Beacon: Method is Auto, Initial Interval is 1 minute.
Packet Path: Type is Others, PATH is ARISS - this will work for the ISS
and NO-84 when its 145.825 MHz digipeater is on, and then you can change
the Type value to New-N when you are using the HT on the terrestrial APRS
network instead of a spaceborne digipeater.
You can either rely on the HT to beacon at that interval you set in the
TX Beacon value, or you can press F followed by BCON (the 6 key) to send
a beacon on demand. Or press BCON to remove BCON from the display, and then
press BCON again to reenable the HT's beacon.
An alternative to using the Status Text and TX Beacon to make your CQ calls
would be to use an APRS message sent to ALL, and then type in a CQ call
like "CQ de K7TEJ". You could just put something like "K7TEJ looking for a
call", hoping a live operator in the footprint will pick up on something
different coming from the digipeater. APRS messages are normally sent out
once a minute over a 5-minute period, or you can go into the MSG (press the
4 key) menu and force an APRS message to be retransmitted on demand. This
might be useful, if you see your HT transmit but don't see something like
"My Message" or "My Message via ... " to indicate your HT heard the message
being retransmitted by the spaceborne digipeater.
I don't worry about an explicit CQ call when I work these digipeaters. I
transmit my location and status text to show up on the digipeater, and then
try to send APRS messages to other call signs I see on my HT's screen. I
updated the instructions I have on my QRZ.com page on how I work the ISS
and NO-84 digipeaters, asking stations to contact me via APRS messages when
they see WD9EWK-9. Otherwise, freeform text sent from another station isn't
shown or stored on the HT - just the call sign.
Hope that helps. 73!
Patrick WD9EWK/VA7EWK
http://www.wd9ewk.net/
Twitter: @xxxxxx
On Wed, Apr 20, 2016 at 11:58 PM, Rick Tejera <saguaroastro@xxx.xxx> wrote:
> Patrick,
>
> When sending a CQ message, What call sign would you send to? I get how to
> respond with user phrases or position comments, but how do you get that
> first CQ out to whoever is listening?
>
> Rick Tejera (K7TEJ)
_______________________________________________
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: 2
Date: Thu, 21 Apr 2016 01:33:46 -0400
From: AJ9N@xxx.xxx
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Upcoming ARISS Contact Schedule as of 2016-04-21
05:30 UTC
Message-ID: <3c4bb.6c2a9aa5.4449c03a@xxx.xxx>
Content-Type: text/plain; charset="UTF-8"
Upcoming ARISS Contact Schedule as of 2016-04-21 05:30 UTC
Quick list of scheduled contacts and events:
STEM Trajectory Initiative with Albuquerque Public Schools, Albuquerque
New Mexico, direct via NM5HD
The ISS callsign is presently scheduled to be NA1SS
The scheduled astronaut is Jeff Williams KD5TVQ
Contact is a go for: Fri 2016-04-22 17:32:37 UTC 83 deg
Saratov, Russia, direct via TBD (***)
The ISS callsign is presently scheduled to be RS?ISS (***)
The scheduled astronaut is Yuri Malenchenko RK3DUP (***)
Contact is a go for: Sat 2016-04-23 09:06 UTC (***)
Wellesley House School, Broadstairs, Kent, UK, direct via GB1WHS
The ISS callsign is presently scheduled to be GB1SS
The scheduled astronaut is Timothy Peake KG5BVI
Contact is a go for: Sat 2016-04-23 12:10:50 UTC 62 deg
Watch for HamTV coverage
St. Petersburg, Russia, direct via TBD (***)
The ISS callsign is presently scheduled to be RS?ISS (***)
The scheduled astronaut is TBD (***)
Contact is a go for: Sat 2016-04-23 10:41 UTC (***)
Republic of Chuvashia, direct via TBD (***)
The ISS callsign is presently scheduled to be RS?ISS (***)
The scheduled astronaut is Yuri Malenchenko RK3DUP (***)
Contact is a go for Sun 2016-04-23 09:50 UTC (***)
The Derby High School, Bury, UK, direct via GB1DHS
The ISS callsign is presently scheduled to be GB1SS
The scheduled astronaut is Timothy Peake KG5BVI
Contact is a go for: Mon 2016-04-25 12:02:27 UTC 49 deg
Istituto Comprensivo Statale ?Diego Valeri?, Campolongo Maggiore, Italy,
direct via IZ3YRA
The ISS callsign is presently scheduled to be OR4ISS
The scheduled astronaut is Tim Kopra KE5UDN
Contact is a go for: Fri 2016-04-29 08:34:08 UTC 64 deg (***)
****************************************************************************
**
The next window to submit a proposal for an upcoming contact is now
closed. The window was open from 2016-02-15 to 2016-04-15 and would be for
contacts between 2017-01-01 and 2017-06-30.
Check out the ARISS website http://www.ariss.org/ or the ARRL website
http://www.arrl.org/hosting-an-ariss-contact for full details of future
proposal windows.
****************************************************************************
**
The next window to submit a proposal for an upcoming contact is now open.
The window is open from 2016-02-15 to 2016-04-15 and would be for contacts
between 2017-01-01 and 2017-06-30.
Check out the ARISS website http://www.ariss.org/ or the ARRL website
http://www.arrl.org/hosting-an-ariss-contact for full details.
****************************************************************************
**
ARISS is always glad to receive listener reports for the above contacts.
ARISS thanks everyone in advance for their assistance. Feel free to send
your reports to aj9n@xxxxx.xxx or aj9n@xxx.xxx.
****************************************************************************
***
All ARISS contacts are made via the Ericsson radio unless otherwise noted.
****************************************************************************
***
Several of you have sent me emails asking about the RAC ARISS website and
not being able to get in. That has now been changed to
http://www.ariss.org/
Note that there are links to other ARISS websites from this site.
****************************************************************************
Looking for something new to do? How about receiving DATV from the ISS?
If interested, then please go to the ARISS-EU website for complete
details. Look for the buttons indicating Ham Video.
http://www.ariss-eu.org/
If you need some assistance, ARISS mentor Kerry N6IZW, might be able to
provide some insight. Contact Kerry at kbanke@xxxxxxxxx.xxx
****************************************************************************
ARISS congratulations the following mentors who have now mentored over 100
schools:
Gaston ON4WF with 121
Satoshi 7M3TJZ with 117
Francesco IK?WGF with 116
****************************************************************************
The webpages listed below were all reviewed for accuracy. Out of date
webpages were removed and new ones have been added. If there are
additional
ARISS websites I need to know about, please let me know.
Note, all times are approximate. It is recommended that you do your own
orbital prediction or start listening about 10 minutes before the listed
time.
All dates and times listed follow International Standard ISO 8061 date
and
time format YYYY-MM-DD HH:MM:SS
The complete schedule page has been updated as of 2016-04-21 05:30 UTC.
(***)
Here you will find a listing of all scheduled school contacts, and
questions, other ISS related websites, IRLP and Echolink websites, and
instructions for any contact that may be streamed live.
http://www.amsat.org/amsat/ariss/news/arissnews.rtf
Total number of ARISS ISS to earth school events is 1045.
Each school counts as 1 event.
Total number of ARISS ISS to earth school contacts is 1010.
Each contact may have multiple schools sharing the same time slot.
Total number of ARISS supported terrestrial contacts is 47.
A complete year by year breakdown of the contacts may be found in the
file.
http://www.amsat.org/amsat/ariss/news/arissnews.rtf
Please feel free to contact me if more detailed statistics are needed.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The following US states and entities have never had an ARISS contact:
Arkansas, Delaware, Rhode Island, South Dakota,
Wyoming, American Samoa, Guam, Northern Marianas Islands, and the Virgin
Islands.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
QSL information may be found at:
http://www.ariss.org/qsl-cards.html
ISS callsigns: DP?ISS, IR?ISS, NA1SS, OR4ISS, RS?ISS
****************************************************************************
The successful school list has been updated as of 2016-04-18 19:00 UTC.
http://www.amsat.org/amsat/ariss/news/Successful_ARISS_schools.rtf
Frequency chart for packet, voice, and crossband repeater modes showing
Doppler correction as of 2005-07-29 04:00 UTC
http://www.amsat.org/amsat/ariss/news/ISS_frequencies_and_Doppler_correction
.rtf
Listing of ARISS related magazine articles as of 2006-07-10 03:30 UTC.
http://www.amsat.org/amsat/ariss/news/ARISS_magazine_articles.rtf
Check out the Zoho reports of the ARISS contacts
https://reports.zoho.com/ZDBDataSheetView.cc?DBID=412218000000020415
****************************************************************************
Exp. 46 on orbit
Tim Kopra KE5UDN
Timothy Peake KG5BVI
Yuri Malenchenko RK3DUP
Exp. 47 on orbit
Jeff Williams KD5TVQ
Oleg Skripochka RN3FU
Aleksey Ovchinin
****************************************************************************
73,
Charlie Sufana AJ9N
One of the ARISS operation team mentors
------------------------------
Message: 3
Date: Thu, 21 Apr 2016 02:58:41 -0400
From: Robert McGwier <rwmcgwier@xxxxx.xxx>
To: skristof@xxxxxxx.xxx
Cc: amsat bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ISS Unattended Beacon Theory (UBT) - PROVE ME
WRONG!
Message-ID:
<CA+K5gzcr7+TDeFedtuvQxETYD4RgWy-b9MqN7LrLA_Pn8Qnz+g@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
We should turn off digipeating of UI frames. One bit flip and it ends.
The ISS can beacon but this activity will end.
Bob
On Tue, Apr 19, 2016 at 12:52 PM, <skristof@xxxxxxx.xxx> wrote:
>
>
> A short exchange of name, QTH (Grid Square &/or state), then a QSL to
> acknowledge. Kind of like JT65 except faster than growing grass.
>
> I use UISS software. That program has macros (like many other programs)
> that can be set up with all the info, then sent with the push of a
> button. It can be done if you're paying attention and catch the breaks
> between beacons.
>
> Steve AI9IN
>
> p.s. No spam from JT65 fans, please. I play with it myself. Catch you on
> 7.076 some evening!
>
> On 2016-04-19 12:25, John Becker wrote:
>
> > can you even have a QSO for all the beacons?
> >
> > _______________________________________________
> > 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
> [1]
>
>
> Links:
> ------
> [1] http://www.amsat.org/mailman/listinfo/amsat-bb
> _______________________________________________
> 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
>
--
Bob McGwier
Founder, Federated Wireless, Inc
Founder and Technical Advisor, HawkEye 360, Inc
Research Professor Virginia Tech
Dir. Research: The Ted and Karyn Hume Center for National Security and
Technology
Senior Member IEEE, Facebook: N4HYBob, ARS: N4HY
Faculty Advisor Virginia Tech Amateur Radio Assn. (K4KDJ)
Director of AMSAT
------------------------------
Message: 4
Date: Thu, 21 Apr 2016 09:09:36 -0400
From: Robert Bruninga <bruninga@xxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] ISS Unattended Beacon Theory (UBT) - PROVE ME
WRONG!
Message-ID: <2e5a8d2aa2442660413c43b69e55bc23@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Do you mean turn it into another BLEEPsat of our own making?..
-----Original Message-----
> Subject: ISS Unattended Beacon Theory (UBT) - PROVE ME WRONG!
>
> We should turn off digipeating of UI frames. One bit flip and it ends.
> The ISS can beacon but this activity will end.
> Bob
On Tue, Apr 19, 2016 at 12:52 PM, <skristof@xxxxxxx.xxx> wrote:
> A short exchange of name, QTH (Grid Square &/or state), then a QSL to
> acknowledge. Kind of like JT65 except faster than growing grass.
> I use... macros that can be set up with all the info, then sent with the
> push of a button. It can be done if you're paying attention and catch
> the breaks between beacons.
> Steve AI9IN
------------------------------
Message: 5
Date: Fri, 22 Apr 2016 00:18:02 +0900
From: "Jeff A. Boyd" <the2belo@xxx.xxxxxxx.xx.xx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Need help decoding EO-79 packets.
Message-ID: <20160422001802.FBCF.63087B45@xxx.xxxxxxx.xx.xx>
Content-Type: text/plain; charset="US-ASCII"
I have been trying for weeks to set up a system to decode telemetry packets
from
EO-79 (QB50P1) without success. As I am new at dealing with data from
satellites
that is not already handled by a dedicated program such as FUNCube Dashboard,
which handles Doppler tracking and packet decoding all by itself, I'm still
kind
of lost as to how all the required components are supposed to come together.
If I can figure out EO-79, goes my thinking, then I can go on to tackling
other
BPSK 1200 baud birds such as the XW-2 constellation. I will list what I'm
doing
below; if someone can please give me a sanity check it would be greatly
appreciated.
- Receiver: FUNCube Dongle Pro+, SDR# outputting to a virtual audio cable.
- SATPC32 tracking EO-79, correcting for Doppler, and controlling SDR#.
- AGW Packet Engine set up with "Sound Card" TNC (the other end of the virtual
audio cable), dual port, 1200 baud for each channel.
- AGW Online KISS set up to connect to the Packet Engine. WINSock remote port
8000.
- Soundmodem by UZ7HO on the same port 8000 and listening to SDR#, which
is set for USB, 4kHz bandwidth. SATPC32 is keeping the packet traces in the
center of the 4kHz passband, and I can see the traces appearing in the
waterfall
in Soundmodem. The modems in Soundmodem (2 channels) are set for BPSK 1200
baud, and the reticules match up exactly with the traces I can see in the
waterfall.
And Soundmodem refuses to decode a single #$%&ing thing. There is an
occasional
"<NON AX.25 FRAME>" that shows up in the list, and Online KISS will show a
bunch
of garbage, but this mostly occurs when there is nothing in the waterfall at
all.
Several sites have said that I'm to connect something to something else using
virtual serial ports, but none of them have really given me a straight
answer as
to where to connect what to what.
What am I doing wrong here? Any advice would be ridiculously appreciated.
73
--
J. Boyd, JR2TTS/NI3B
the2belo@xxx.xxxxxxx.xx.xx
http://www.flickr.com/photos/the2belo/
http://www.qrz.com/db/JR2TTS
Twitter: @xxxxxxxx
------------------------------
Message: 6
Date: Thu, 21 Apr 2016 12:11:09 -0400
From: Robert McGwier <rwmcgwier@xxxxx.xxx>
To: Robert Bruninga <bruninga@xxxx.xxx>
Cc: amsat bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ISS Unattended Beacon Theory (UBT) - PROVE ME
WRONG!
Message-ID:
<CA+K5gzexCNusiAoGouWAQ3pGHZs2RBobwa5uG5pueDQ6JuAfOA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
That is what it is now Bob. It is people on the ground doing the bleeping
and they are using it as a pseudo bent pipe transponder doing demod/remod
constantly unattended. is that how it was intended to be used?
Tell me how to stop this behavior without turning off UI? Or maybe you
feel this is not a real impediment to comms. The originator of this thread
seems to feel it is.
73s
Bob
On Thu, Apr 21, 2016 at 9:09 AM, Robert Bruninga <bruninga@xxxx.xxx> wrote:
> Do you mean turn it into another BLEEPsat of our own making?..
>
> -----Original Message-----
> > Subject: ISS Unattended Beacon Theory (UBT) - PROVE ME WRONG!
> >
> > We should turn off digipeating of UI frames. One bit flip and it ends.
> > The ISS can beacon but this activity will end.
> > Bob
>
> On Tue, Apr 19, 2016 at 12:52 PM, <skristof@xxxxxxx.xxx> wrote:
>
> > A short exchange of name, QTH (Grid Square &/or state), then a QSL to
> > acknowledge. Kind of like JT65 except faster than growing grass.
> > I use... macros that can be set up with all the info, then sent with the
>
> > push of a button. It can be done if you're paying attention and catch
> > the breaks between beacons.
> > Steve AI9IN
> _______________________________________________
> 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
>
--
Bob McGwier
Founder, Federated Wireless, Inc
Founder and Technical Advisor, HawkEye 360, Inc
Research Professor Virginia Tech
Dir. Research: The Ted and Karyn Hume Center for National Security and
Technology
Senior Member IEEE, Facebook: N4HYBob, ARS: N4HY
Faculty Advisor Virginia Tech Amateur Radio Assn. (K4KDJ)
Director of AMSAT
------------------------------
Message: 7
Date: Thu, 21 Apr 2016 18:33:09 +0200
From: "Mike Rupprecht" <mail@xxxxxxxxxxxxxx.xx>
To: <the2belo@xxx.xxxxxxx.xx.xx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Need help decoding EO-79 packets.
Message-ID: <001601d19beb$7de2cb10$79a86130$@xx>
Content-Type: text/plain; charset="iso-8859-1"
Hi Jeff,
if you use soundmodem by UZ7HO you don't need AGW Packet Engine.
Firstly start soundmodem software, then AGW Online KISS OR use the QB50p1
Online decoder.
If it's connected you should see a green light.
If you successfully decode a packet you should see something like this in
soundmodem:
2: <NON-AX25 frame Len=125> [18:29:19R]
2: <NON-AX25 frame Len=125> [18:29:29R]
2: <NON-AX25 frame Len=125> [18:29:39R]
2: <NON-AX25 frame Len=125> [18:29:49R]
73 Mike
DK3WN
-----Urspr?ngliche Nachricht-----
Von: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx Im Auftrag von Jeff A.
Boyd
Gesendet: 21 April 2016 17:18
An: amsat-bb@xxxxx.xxx
Betreff: [amsat-bb] Need help decoding EO-79 packets.
I have been trying for weeks to set up a system to decode telemetry packets
from
EO-79 (QB50P1) without success. As I am new at dealing with data from
satellites that is not already handled by a dedicated program such as
FUNCube Dashboard, which handles Doppler tracking and packet decoding all by
itself, I'm still kind of lost as to how all the required components are
supposed to come together.
If I can figure out EO-79, goes my thinking, then I can go on to tackling
other BPSK 1200 baud birds such as the XW-2 constellation. I will list what
I'm doing below; if someone can please give me a sanity check it would be
greatly appreciated.
- Receiver: FUNCube Dongle Pro+, SDR# outputting to a virtual audio cable.
- SATPC32 tracking EO-79, correcting for Doppler, and controlling SDR#.
- AGW Packet Engine set up with "Sound Card" TNC (the other end of the
virtual audio cable), dual port, 1200 baud for each channel.
- AGW Online KISS set up to connect to the Packet Engine. WINSock remote
port 8000.
- Soundmodem by UZ7HO on the same port 8000 and listening to SDR#, which is
set for USB, 4kHz bandwidth. SATPC32 is keeping the packet traces in the
center of the 4kHz passband, and I can see the traces appearing in the
waterfall in Soundmodem. The modems in Soundmodem (2 channels) are set for
BPSK 1200 baud, and the reticules match up exactly with the traces I can see
in the waterfall.
And Soundmodem refuses to decode a single #$%&ing thing. There is an
occasional "<NON AX.25 FRAME>" that shows up in the list, and Online KISS
will show a bunch of garbage, but this mostly occurs when there is nothing
in the waterfall at all.
Several sites have said that I'm to connect something to something else
using virtual serial ports, but none of them have really given me a straight
answer as to where to connect what to what.
What am I doing wrong here? Any advice would be ridiculously appreciated.
73
--
J. Boyd, JR2TTS/NI3B
the2belo@xxx.xxxxxxx.xx.xx
http://www.flickr.com/photos/the2belo/
http://www.qrz.com/db/JR2TTS
Twitter: @xxxxxxxx
_______________________________________________
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: Thu, 21 Apr 2016 18:56:15 +0200
From: PE0SAT | Amateur Radio <pe0sat@xxxxx.xx>
To: <the2belo@xxx.xxxxxxx.xx.xx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Need help decoding EO-79 packets.
Message-ID: <25c976c9f51d877bc6bf2ebfcfb3f463@xxxxx.xx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Jeff,
Here some extra info that might help:
Use BPSK AX.25 mode when decoding QB50p1, make sure non-AX25 filter is
not selected.
You can try to replay the file at:
http://janvgils.home.xs4all.nl/download/QB50px/
to see if things are working. There three different signals in the
file.
QB50p1 1200bps and 2400 bps
DO-64 (Delfi-C3) with 1200bps
They can both be decoded with UZ7HO and AGW Online Kiss.
Maybe the block diagram on the following page will also help in
understanding how
things can be connected.
http://www.pe0sat.vgnet.nl/decoding/block-diagram/
73 Jan - PE0SAT
On 21-04-2016 18:33, Mike Rupprecht wrote:
> Hi Jeff,
>
> if you use soundmodem by UZ7HO you don't need AGW Packet Engine.
>
> Firstly start soundmodem software, then AGW Online KISS OR use the
> QB50p1
> Online decoder.
> If it's connected you should see a green light.
>
> If you successfully decode a packet you should see something like this
> in
> soundmodem:
>
> 2: <NON-AX25 frame Len=125> [18:29:19R]
> 2: <NON-AX25 frame Len=125> [18:29:29R]
> 2: <NON-AX25 frame Len=125> [18:29:39R]
> 2: <NON-AX25 frame Len=125> [18:29:49R]
>
> 73 Mike
> DK3WN
>
> -----Urspr?ngliche Nachricht-----
> Von: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx Im Auftrag von Jeff
> A.
> Boyd
> Gesendet: 21 April 2016 17:18
> An: amsat-bb@xxxxx.xxx
> Betreff: [amsat-bb] Need help decoding EO-79 packets.
>
> I have been trying for weeks to set up a system to decode telemetry
> packets
> from
> EO-79 (QB50P1) without success. As I am new at dealing with data from
> satellites that is not already handled by a dedicated program such as
> FUNCube Dashboard, which handles Doppler tracking and packet decoding
> all by
> itself, I'm still kind of lost as to how all the required components
> are
> supposed to come together.
>
> If I can figure out EO-79, goes my thinking, then I can go on to
> tackling
> other BPSK 1200 baud birds such as the XW-2 constellation. I will list
> what
> I'm doing below; if someone can please give me a sanity check it would
> be
> greatly appreciated.
>
> - Receiver: FUNCube Dongle Pro+, SDR# outputting to a virtual audio
> cable.
> - SATPC32 tracking EO-79, correcting for Doppler, and controlling
> SDR#.
> - AGW Packet Engine set up with "Sound Card" TNC (the other end of the
> virtual audio cable), dual port, 1200 baud for each channel.
> - AGW Online KISS set up to connect to the Packet Engine. WINSock
> remote
> port 8000.
> - Soundmodem by UZ7HO on the same port 8000 and listening to SDR#,
> which is
> set for USB, 4kHz bandwidth. SATPC32 is keeping the packet traces in
> the
> center of the 4kHz passband, and I can see the traces appearing in the
> waterfall in Soundmodem. The modems in Soundmodem (2 channels) are set
> for
> BPSK 1200 baud, and the reticules match up exactly with the traces I
> can see
> in the waterfall.
>
> And Soundmodem refuses to decode a single #$%&ing thing. There is an
> occasional "<NON AX.25 FRAME>" that shows up in the list, and Online
> KISS
> will show a bunch of garbage, but this mostly occurs when there is
> nothing
> in the waterfall at all.
>
> Several sites have said that I'm to connect something to something
> else
> using virtual serial ports, but none of them have really given me a
> straight
> answer as to where to connect what to what.
>
> What am I doing wrong here? Any advice would be ridiculously
> appreciated.
>
> 73
>
> --
> J. Boyd, JR2TTS/NI3B
> the2belo@xxx.xxxxxxx.xx.xx
> http://www.flickr.com/photos/the2belo/
> http://www.qrz.com/db/JR2TTS
> Twitter: @xxxxxxxx
--
With regards PE0SAT
Internet web-page http://www.pe0sat.vgnet.nl/
DK3WN SatBlog http://www.dk3wn.info/p/
irc://chat.freenode.net #Cubesat
------------------------------
Message: 9
Date: Thu, 21 Apr 2016 19:58:43 +0300
From: Stefan Wagener <wageners@xxxxx.xxx>
To: Robert McGwier <rwmcgwier@xxxxx.xxx>
Cc: amsat bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ISS Unattended Beacon Theory (UBT) - PROVE ME
WRONG!
Message-ID:
<CAKu8kHAc=nQaNo=N_ZMW8s5yuOeNV1DQMQCovBWtHgokPb-Rgw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
....now, at the end of the day, unattended use does no harm (other then
annoying a few folks) as long as there are others using it for a quick QSO.
If no one is available to "talk" it is not a problem for those that decide
to run unattended stations. It is a perception problem by those that expect
that on every ISS pass lots of folks just wait for quick preprogrammed or
live UISS messages and "QSOs". At least the unattended stations keep the
system in use because not to many other folks do. So lets increase the
numbers of operators, have AMSAT or someone create an award or something.
Blaming and shaming unattended use does not solve the lack of interest!
....and *no*, I do not run any unattended station and *yes*, i make the
occasional QSO since I like it.
My 2 cents,
Stefan, VE4NSA
On Thu, Apr 21, 2016 at 7:11 PM, Robert McGwier <rwmcgwier@xxxxx.xxx> wrote:
> That is what it is now Bob. It is people on the ground doing the bleeping
> and they are using it as a pseudo bent pipe transponder doing demod/remod
> constantly unattended. is that how it was intended to be used?
>
> Tell me how to stop this behavior without turning off UI? Or maybe you
> feel this is not a real impediment to comms. The originator of this thread
> seems to feel it is.
>
> 73s
> Bob
>
>
> On Thu, Apr 21, 2016 at 9:09 AM, Robert Bruninga <bruninga@xxxx.xxx>
> wrote:
>
> > Do you mean turn it into another BLEEPsat of our own making?..
> >
> > -----Original Message-----
> > > Subject: ISS Unattended Beacon Theory (UBT) - PROVE ME WRONG!
> > >
> > > We should turn off digipeating of UI frames. One bit flip and it ends.
> > > The ISS can beacon but this activity will end.
> > > Bob
> >
> > On Tue, Apr 19, 2016 at 12:52 PM, <skristof@xxxxxxx.xxx> wrote:
> >
> > > A short exchange of name, QTH (Grid Square &/or state), then a QSL to
> > > acknowledge. Kind of like JT65 except faster than growing grass.
> > > I use... macros that can be set up with all the info, then sent with
> the
> >
> > > push of a button. It can be done if you're paying attention and catch
> > > the breaks between beacons.
> > > Steve AI9IN
> > _______________________________________________
> > 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
> >
>
>
>
> --
> Bob McGwier
> Founder, Federated Wireless, Inc
> Founder and Technical Advisor, HawkEye 360, Inc
> Research Professor Virginia Tech
> Dir. Research: The Ted and Karyn Hume Center for National Security and
> Technology
> Senior Member IEEE, Facebook: N4HYBob, ARS: N4HY
> Faculty Advisor Virginia Tech Amateur Radio Assn. (K4KDJ)
> Director of AMSAT
> _______________________________________________
> 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 129
*****************************************
Read previous mail | Read next mail
| |
