OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

IW8PGT

[Mendicino(CS)-Italy]

 Login: GUEST





  
CX2SA  > SATDIG   19.04.17 01:50l 1243 Lines 32506 Bytes #999 (0) @ WW
BID : AMSATBB12108
Read: GUEST
Subj: AMSAT-BB-digest V12 108
Path: IW8PGT<CX2SA
Sent: 170418/2339Z @:CX2SA.SAL.URY.SOAM #:5330 [Salto] FBB7.00e $:AMSATBB12108
From: CX2SA@CX2SA.SAL.URY.SOAM
To  : SATDIG@WW

Today's Topics:

   1. FM Voice and Packet Satellites (Alan)
   2. Re: AO-73/FUNcube Mode switch (Patrick STODDARD (WD9EWK/VA7EWK))
   3. ISS Beaconator (Clayton Coleman)
   4. ISS Beaconator II (Clayton Coleman)
   5. Re: ISS Beaconator II (Dave Webb KB1PVH)
   6. Re: ISS Beaconator II (John Becker)
   7. Re: ISS Beaconator II (Dave Webb KB1PVH)
   8. Re: ISS Beaconator II (skristof@xxxxxxx.xxxx
   9. Re: ISS Beaconator II (Tucker McGuire)
  10. Re: ISS Beaconator II (Stephen  E. Belter)
  11. Presentation for Mesa Community College ARC,	last night
      (report) (Patrick STODDARD (WD9EWK/VA7EWK))
  12. Re: ISS Beaconator (Jeff)


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

Message: 1
Date: Tue, 18 Apr 2017 09:18:35 -0500
From: "Alan" <wa4sca@xxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] FM Voice and Packet Satellites
Message-ID: <000b01d2b84e$aad855b0$00890110$@xxxxx.xxx>

Back in the days when Pluto was still a planet, and I had hair, circa 1988,
there were two types of questions which were repeatedly asked of the
satellite builders:

1. Why do you keep making me build a new modem to copy data every time you
build a new satellite? Can't you just use a TNC? Why not fly a W0RLI packet
BBS?

2. Why can't you just build a flying FM repeater, so I can use my regular
equipment?

The techies who built satellites explained patiently both of these were
Really Bad Ideas; both are extremely poor choices from a technical
standpoint. They are single channel, and use one of the most inefficient
modulation schemes known to hams. We have spent the past 25+ years proving
the techies were right on both accounts. Consider the numerous detailed
discussions concerning problems with both over the past few days. Those
techies would be, and perhaps in some cases are, nodding knowingly at seeing
the validity of those objections being born out.

But the users have also been proven right. Satellite APRS manages to work
despite these limitations, and FM satellites are often in use AOS to LOS
with normally good cooperation. (Everybody is a newbie sometime.) The
ability to use rather simple equipment, easily understood, has won out over
technically "sweeter" solutions. Users have tacitly decided that the
limitations are a good tradeoff. The proof is the number of successful QSOs
and Dxpeditions reported. However, the limitations are inherent in the
chosen technology, and education, innovation, consensus, and courtesy can
only do so much.

Keep in mind there are other voice options in the form of linear satellites
now, and with only slightly greater complexity. You can chase DX, grids, and
rag chew at the same time without taking away resources from other users.

To borrow a phrase from AMSAT-NA's Official Curmudgeon,  Tom, K3IO, "But
wait, there's more!" Digital voice and data systems are being developed by
the current generation of techies which will make microwave systems, and the
resulting bandwidth, available to the everyone using digital signal
processing and eBay parts. As Phil Karn, KA9Q, puts it, any sufficiently
advanced modulation scheme is indistinguishable from noise. But with that
noise will come the ability to accommodate voice, TV, and data
simultaneously. For some, the tradeoff of greater complexity for almost
unbelievable capability will be worth it. For others, simplicity and
familiarity will win out. In both cases, that is in the best traditions of
amateur radio.

73s,

Alan
WA4SCA
Curmudgeon (jg)




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

Message: 2
Date: Tue, 18 Apr 2017 09:24:36 -0700
From: "Patrick STODDARD (WD9EWK/VA7EWK)" <amsat-bb@xxxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] AO-73/FUNcube Mode switch
Message-ID:
<CAN6TEUd4WnzyL6xnXpCGhesD_fqydPXJ7m_pnrp7WT-VWXg0cw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

?Jim,

Thanks to you and the FUNcube team for the extended period
of transponder time over the Easter holiday. It was nice to
have the transponder available for a demonstration last
night at a nearby college. Using my FT-817ND, SDRplay RSP1,
and an 8-inch Windows 10 tablet running HDSDR, I was able
to work two Mexican stations and a station in Las Vegas.
The crowd saw the tablet's screen, where the transponder
and the digital telemetry were easy to pick out of the
waterfall display.

73!




Patrick WD9EWK/VA7EWK
http://www.wd9ewk.net/
Twitter: @xxxxxx





On Tue, Apr 18, 2017 at 12:42 AM, Jim Heck G3WGM <jimlist@xxxx.xxx> wrote:

>
> Hi Folks,
>
>  This is to let you know that I have just switched AO-73/FUNcube back into
> autonomous mode, ie Educational mode when in sunlight, and amateur mode
> (low power beacon with transponder ON) when in eclipse.
>
>  This switch was done later than normal (normally done Sunday evenings
> UTC) due to the Easter Holidays.
>
> 73s Jim G3WGM and the FUNcube Team
>
>


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

Message: 3
Date: Tue, 18 Apr 2017 12:10:46 -0500
From: Clayton Coleman <kayakfishtx@xxxxx.xxx>
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] ISS Beaconator
Message-ID:
<CAPovOwdw7qM1m7mqDtck3LAmoGMU6T07H16xMRDB3E_zG7t5Eg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

These are actual packets decoded by my station between 16:31-16:33 UTC
today, April 18.

I could post more than two minutes but it doesn't paint a different picture.

Fortunately not everyone on the planet has their beacons set to go off
every 2-3 seconds.

73
Clayton
W5PFG


Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:23]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:25]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:28]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:30]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:32]
'g.7l #/]SP=



Fm RS0ISS To CQ <UI pid=F0 Len=36 >[11:31:35]
>ARISS - International Space Station



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:44]
'g.7l #/]SP=



Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[11:31:51]
=3726.20N/07742.21W-73' Via ISS w4tbd@xxxx.xxx FM17dk IGate WLNK-1



Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[11:32:07]
=3726.20N/07742.21W-73' Via ISS w4tbd@xxxx.xxx FM17dk IGate WLNK-1



Fm K9JKM To CQ Via RS0ISS* <UI pid=F0 Len=33 >[11:32:14]
=4211.29N/08827.08W-Greetings :-)



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:28]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:30]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:32]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:35]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:37]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:40]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:44]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:46]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:47]
'g.7l #/]SP=



Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[11:32:52]
=3726.20N/07742.21W-73' Via ISS w4tbd@xxxx.xxx FM17dk IGate WLNK-1



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:33:03]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:33:31]
'g.7l #/]SP=


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

Message: 4
Date: Tue, 18 Apr 2017 13:26:45 -0500
From: Clayton Coleman <kayakfishtx@xxxxx.xxx>
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] ISS Beaconator II
Message-ID:
<CAPovOwcMLtrUQTkFxNL7SG8JpsEYvFpY_DgU+Y3E+Mi+3Xuu4g@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

These are actual packets decoded by my station between 18:07-18:09 UTC
today, April 18.

At the rate these packets are being digipeated, I wonder just how fast
they are being transmitted. I suspect many packets are lost in
collisions and bad/partial decodes on the ISS.

Before anyone asks, this is not the same pass I posted previously.
This is the next pass. (timestamps are my local time.)

73
Clayton
W5PFG

Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:07:53]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:16]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:21]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:25]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:27]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:28]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:30]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:32]
'g.7l #/]SP=



Fm K1WY To TQTU7T Via RS0ISS*,RS0ISS <UI pid=F0 Len=22 >[13:08:38]
'dGRl -/]K1WY FN31ps



Fm N3FCX To APK102 Via RS0ISS* <UI pid=F0 Len=36 >[13:08:45]
:N2UFL    :HI SAM DE DAN VIA ISS{69


Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:48]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:51]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:56]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:57]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:59]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:01]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:02]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:04]
'g.7l #/]SP=



Fm KD8THX-6 To APWW10 Via RS0ISS* <UI pid=F0 Len=49 >[13:09:06]
=4245.95N/08607.96W-Hello from Holland, MI EN62ws



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:08]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:10]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:12]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:13]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:15]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:17]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:19]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:22]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:23]
'g.7l #/]SP=



Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[13:09:29]
=3726.20N/07742.21W-73' Via ISS w4tbd@xxxx.xxx FM17dk IGate WLNK-1



Fm KB3KBR-6 To APWW10 Via RS0ISS* <UI pid=F0 Len=37 >[13:09:32]
=4123.64N/07938.52WlAPRS-IS for Win32



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:34]
'g.7l #/]SP=



Fm K1WY To TQTU7T Via RS0ISS*,RS0ISS <UI pid=F0 Len=11 >[13:09:40]
'dGRl -/]



Fm RS0ISS To CQ <UI pid=F0 Len=36 >[13:09:42]
>ARISS - International Space Station



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:47]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:49]
'g.7l #/]SP=


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

Message: 5
Date: Tue, 18 Apr 2017 14:32:11 -0400
From: Dave Webb KB1PVH <kb1pvh@xxxxx.xxx>
To: AMSAT -BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ISS Beaconator II
Message-ID:
<CAEMY9FdeDPRkXHF5wZFAwom--JOJhPf3J3xo2372-RE=yQa1bA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

Good ol' N3FCX. I caught the same type of rapid fire beacons from him back
in January, I think it was. I emailed him with a copy of my RX log and
asked if he was having issues with his station and his response was
basically thanks for the email maybe I'll catch you on sometime. I guess he
hasn't changed anything.

Dave-KB1PVH


Sent from my Galaxy S7

On Apr 18, 2017 2:26 PM, "Clayton Coleman" <kayakfishtx@xxxxx.xxx> wrote:

> These are actual packets decoded by my station between 18:07-18:09 UTC
> today, April 18.
>
> At the rate these packets are being digipeated, I wonder just how fast
> they are being transmitted. I suspect many packets are lost in
> collisions and bad/partial decodes on the ISS.
>
> Before anyone asks, this is not the same pass I posted previously.
> This is the next pass. (timestamps are my local time.)
>
> 73
> Clayton
> W5PFG
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:07:53]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:16]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:21]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:25]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:27]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:28]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:30]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:32]
> 'g.7l #/]SP=
>
>
>
> Fm K1WY To TQTU7T Via RS0ISS*,RS0ISS <UI pid=F0 Len=22 >[13:08:38]
> 'dGRl -/]K1WY FN31ps
>
>
>
> Fm N3FCX To APK102 Via RS0ISS* <UI pid=F0 Len=36 >[13:08:45]
> :N2UFL    :HI SAM DE DAN VIA ISS{69
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:48]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:51]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:56]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:57]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:59]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:01]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:02]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:04]
> 'g.7l #/]SP=
>
>
>
> Fm KD8THX-6 To APWW10 Via RS0ISS* <UI pid=F0 Len=49 >[13:09:06]
> =4245.95N/08607.96W-Hello from Holland, MI EN62ws
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:08]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:10]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:12]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:13]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:15]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:17]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:19]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:22]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:23]
> 'g.7l #/]SP=
>
>
>
> Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[13:09:29]
> =3726.20N/07742.21W-73' Via ISS w4tbd@xxxx.xxx FM17dk IGate WLNK-1
>
>
>
> Fm KB3KBR-6 To APWW10 Via RS0ISS* <UI pid=F0 Len=37 >[13:09:32]
> =4123.64N/07938.52WlAPRS-IS for Win32
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:34]
> 'g.7l #/]SP=
>
>
>
> Fm K1WY To TQTU7T Via RS0ISS*,RS0ISS <UI pid=F0 Len=11 >[13:09:40]
> 'dGRl -/]
>
>
>
> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[13:09:42]
> >ARISS - International Space Station
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:47]
> 'g.7l #/]SP=
>
>
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:49]
> 'g.7l #/]SP=
> _______________________________________________
> 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: Tue, 18 Apr 2017 13:44:14 -0500
From: John Becker <w0jab@xxxxxxxxx.xxx>
To: Dave Webb KB1PVH <kb1pvh@xxxxx.xxx>, amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] ISS Beaconator II
Message-ID: <7e084fc5-a48e-cefa-f386-a405b6ba7cd3@xxxxxxxxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed



On 4/18/2017 1:32 PM, Dave Webb KB1PVH wrote:
> Good ol' N3FCX. I caught the same type of rapid fire beacons from him back
> in January, I think it was. I emailed him with a copy of my RX log and
> asked if he was having issues with his station and his response was
> basically thanks for the email maybe I'll catch you on sometime. I guess he
> hasn't changed anything.
>
And an EXTRA class to boot. you would think he would be trashing the
extra class band a bit also. Just got to love them "NO CODERS"

John


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

Message: 7
Date: Tue, 18 Apr 2017 14:59:25 -0400
From: Dave Webb KB1PVH <kb1pvh@xxxxx.xxx>
To: AMSAT -BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ISS Beaconator II
Message-ID:
<CAEMY9Fd7zbPLtGKzuBkiiPFq2v3n2MtmfMNFSPBhfCDiTnrw+A@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

John,

 I don't buy into the whole code vs. no code thing being a benchmark for
great operators because I've heard plenty of the "coders" operate pretty
poorly. Just check out AO-7 someday and watch it flip modes because the
superior "coders" blast it into Oblivion with QRO CW.

Dave-KB1PVH


Sent from my Galaxy S7

On Apr 18, 2017 2:44 PM, "John Becker" <w0jab@xxxxxxxxx.xxx> wrote:

>
>
> On 4/18/2017 1:32 PM, Dave Webb KB1PVH wrote:
>
>> Good ol' N3FCX. I caught the same type of rapid fire beacons from him back
>> in January, I think it was. I emailed him with a copy of my RX log and
>> asked if he was having issues with his station and his response was
>> basically thanks for the email maybe I'll catch you on sometime. I guess
>> he
>> hasn't changed anything.
>>
>> And an EXTRA class to boot. you would think he would be trashing the
> extra class band a bit also. Just got to love them "NO CODERS"
>
> John
>


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

Message: 8
Date: Tue, 18 Apr 2017 15:01:14 -0400
From: skristof@xxxxxxx.xxx
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ISS Beaconator II
Message-ID: <de01c863e9f013b5af6bfd335e8e0b8c@xxxxxxx.xxx>
Content-Type: text/plain; charset=US-ASCII

Just curious: If a person just let a preprogrammed CQ cycle run
endlessly on HF, wouldn't that be an enforceable offense under FCC regs?
Isn't this an equivalent situation?

How about a postcard from an ARRL Observer or the AMSAT equivalent (if
there is such a thing)?

Steve AI9IN

On 2017-04-18 14:26, Clayton Coleman wrote:

> These are actual packets decoded by my station between 18:07-18:09 UTC
> today, April 18.
>
> At the rate these packets are being digipeated, I wonder just how fast
> they are being transmitted. I suspect many packets are lost in
> collisions and bad/partial decodes on the ISS.
>
> Before anyone asks, this is not the same pass I posted previously.
> This is the next pass. (timestamps are my local time.)
>
> 73
> Clayton
> W5PFG
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:07:53]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:16]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:21]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:25]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:27]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:28]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:30]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:32]
> 'g.7l #/]SP=
>
> Fm K1WY To TQTU7T Via RS0ISS*,RS0ISS <UI pid=F0 Len=22 >[13:08:38]
> 'dGRl -/]K1WY FN31ps
>
> Fm N3FCX To APK102 Via RS0ISS* <UI pid=F0 Len=36 >[13:08:45]
> :N2UFL    :HI SAM DE DAN VIA ISS{69
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:48]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:51]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:56]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:57]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:08:59]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:01]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:02]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:04]
> 'g.7l #/]SP=
>
> Fm KD8THX-6 To APWW10 Via RS0ISS* <UI pid=F0 Len=49 >[13:09:06]
> =4245.95N/08607.96W-Hello from Holland, MI EN62ws
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:08]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:10]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:12]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:13]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:15]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:17]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:19]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:22]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:23]
> 'g.7l #/]SP=
>
> Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[13:09:29]
> =3726.20N/07742.21W-73' Via ISS w4tbd@xxxx.xxx FM17dk IGate WLNK-1
>
> Fm KB3KBR-6 To APWW10 Via RS0ISS* <UI pid=F0 Len=37 >[13:09:32]
> =4123.64N/07938.52WlAPRS-IS for Win32
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:34]
> 'g.7l #/]SP=
>
> Fm K1WY To TQTU7T Via RS0ISS*,RS0ISS <UI pid=F0 Len=11 >[13:09:40]
> 'dGRl -/]
>
> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[13:09:42]
>
>> ARISS - International Space Station
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:47]
> 'g.7l #/]SP=
>
> Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[13:09:49]
> 'g.7l #/]SP=
> _______________________________________________
> 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: Tue, 18 Apr 2017 15:02:34 -0400
From: Tucker McGuire <tucker@xxxxxxxxxxx.xxx>
To: Dave Webb KB1PVH <kb1pvh@xxxxx.xxx>
Cc: AMSAT -BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ISS Beaconator II
Message-ID:
<CA+gmQJR=esXtLuqiaMORiH+LZQB_Aykrd44UncKeTCAWORWqcA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

I agree with Dave on this one. I strongly dislike using the whole "no code"
extra class card as a determining factor for an operator's skills.

Cheers & 73,
Tucker
W4FS
(A "no code extra" that knows code)

On Tue, Apr 18, 2017 at 2:59 PM, Dave Webb KB1PVH <kb1pvh@xxxxx.xxx> wrote:

> John,
>
>  I don't buy into the whole code vs. no code thing being a benchmark for
> great operators because I've heard plenty of the "coders" operate pretty
> poorly. Just check out AO-7 someday and watch it flip modes because the
> superior "coders" blast it into Oblivion with QRO CW.
>
> Dave-KB1PVH
>
>
> Sent from my Galaxy S7
>
> On Apr 18, 2017 2:44 PM, "John Becker" <w0jab@xxxxxxxxx.xxx> wrote:
>
> >
> >
> > On 4/18/2017 1:32 PM, Dave Webb KB1PVH wrote:
> >
> >> Good ol' N3FCX. I caught the same type of rapid fire beacons from him
> back
> >> in January, I think it was. I emailed him with a copy of my RX log and
> >> asked if he was having issues with his station and his response was
> >> basically thanks for the email maybe I'll catch you on sometime. I guess
> >> he
> >> hasn't changed anything.
> >>
> >> And an EXTRA class to boot. you would think he would be trashing the
> > extra class band a bit also. Just got to love them "NO CODERS"
> >
> > John
> >
> _______________________________________________
> 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: Tue, 18 Apr 2017 19:36:37 +0000
From: "Stephen  E. Belter" <seb@xxxxxx.xxx>
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] ISS Beaconator II
Message-ID: <D51BDDB1.8A912%seb@xxxxxx.xxx>
Content-Type: text/plain; charset="utf-8"

According to QRZ, N3FCX is Daniel Vernot and he has a General class
license, not an Extra Class.

QRZ also has an e-mail address for him if you?d like to politely
communicate that he?s jamming the ISS and making it difficult for others
to use the packet system on the ISS.

73, Steve N9IP
--
Steve Belter, seb@xxxxxx.xxx


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

Message: 11
Date: Tue, 18 Apr 2017 13:44:00 -0700
From: "Patrick STODDARD (WD9EWK/VA7EWK)" <amsat-bb@xxxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Presentation for Mesa Community College ARC,	last
night (report)
Message-ID:
<CAN6TEUc7d7kvhvLa1T26pouWYxT5ORFxrc5D2tLRKYWVCeyS+g@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

?Hi!

Last night's presentation and demonstrations for the Mesa Community College
Amateur Radio Club (KM7CC) in Mesa, Arizona, was a great way to spend an
evening. Along with the presentation, satellite pass timing allowed for two
demonstrations, using the ISS and AO-73.

When I drove to the college, I arrived just in time for an eastern ISS pass
around 0120 UTC - 40 minutes before the start of the meeting. I was able to
make a couple of QSOs using my TH-D74A and Elk antenna, and ensure the HT
was ready for a possible demonstration later in the evening. I had planned
on using either AO-73 or EO-88 for a demonstration after the meeting around
0350-0430 UTC, but the meeting agenda had a break around 0300 UTC - just in
time for a western ISS pass.

Unlike many radio clubs, the presentations at the KM7CC club are done first.
Knowing a break was scheduled, and that the ISS was passing by around that
time, I made sure the presentation fit within the schedule. Then everyone
went outside for the ISS pass. We weren't able to see the ISS, but I wasn't
the only one reading the packet traffic on that pass. One of the attendees
had a brand new TH-D72A and Arrow Yagi, and I helped him set it up to copy
the packet traffic on 145.825 MHz. The two of us had crowds watching the
radios and listening to the packet traffic, and others were using their
mobile phones to see this happening on the ariss.net web site. I was able
to work two of the 3 stations I saw on the pass - thanks to KK6OTJ and
AD5MT in southern California for the quick exchanges.

The meeting went for about 25 minutes after the break for the ISS pass.
This meant the AO-73 pass just before 0400 UTC was available for one more
satellite demonstration. Since I mentioned my portable all-mode satellite
station during the presentation, including an SDRplay receiver and Windows
10 tablet running HDSDR, I used that setup out for the AO-73 pass. Not many
were on that pass, but I think I worked everyone else I saw and heard.
Tony XE1H in Guadalajara started things off. Tony also operates using a
club call sign, XE1TD. A contact was made with that call sign, too. A
couple of minutes later, Brad W5SAT in Las Vegas showed up for the third
and final contact for me on that pass.

With the Windows 10 tablet and HDSDR, I used the waterfall display to
show where the digital telemetry was, along with seeing the width of
the transponder. This was a great practical demonstration of using SDR
in ham radio, something that was discussed by the club during the
meeting.

Thanks to Charlie NJ7V and the KM7CC club for the opportunity to visit the
club, give a presentation, and have two demonstrations last night. And I
still have two more presentations later this week...

73!




Patrick WD9EWK/VA7EWK
http://www.wd9ewk.net/
Twitter: @xxxxxx


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

Message: 12
Date: Tue, 18 Apr 2017 19:38:03 -0400
From: "Jeff" <kb2m@xxxxxxx.xxx>
To: "Clayton Coleman" <kayakfishtx@xxxxx.xxx>, "AMSAT-BB"
<amsat-bb@xxxxx.xxx>
Cc: dan_n3fcx@xxxxx.xxx
Subject: Re: [amsat-bb] ISS Beaconator
Message-ID: <F3EEBC703053427B87C6BE4AE0B63E58@xxxxxxx>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original

All this is demonstrating is that N3FCX is watching the ARISS site to see
himself/or if his message has made it to the internet. If he doesn't see he
got in, he is simply trying again.  Does anyone really think he is an
unattended station transmitting every 3 seconds??? All this is showing is
that there is a need for better  ISS IGATES. This whole thing is really
getting ridiculous...

73 Jeff kb2m

-----Original Message-----
From: Clayton Coleman
Sent: Tuesday, April 18, 2017 1:10 PM
To: AMSAT-BB
Subject: [amsat-bb] ISS Beaconator

These are actual packets decoded by my station between 16:31-16:33 UTC
today, April 18.

I could post more than two minutes but it doesn't paint a different picture.

Fortunately not everyone on the planet has their beacons set to go off
every 2-3 seconds.

73
Clayton
W5PFG


Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:23]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:25]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:28]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:30]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:32]
'g.7l #/]SP=



Fm RS0ISS To CQ <UI pid=F0 Len=36 >[11:31:35]
>ARISS - International Space Station



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:31:44]
'g.7l #/]SP=



Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[11:31:51]
=3726.20N/07742.21W-73' Via ISS w4tbd@xxxx.xxx FM17dk IGate WLNK-1



Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[11:32:07]
=3726.20N/07742.21W-73' Via ISS w4tbd@xxxx.xxx FM17dk IGate WLNK-1



Fm K9JKM To CQ Via RS0ISS* <UI pid=F0 Len=33 >[11:32:14]
=4211.29N/08827.08W-Greetings :-)



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:28]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:30]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:32]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:35]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:37]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:40]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:44]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:46]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:32:47]
'g.7l #/]SP=



Fm W4TBD-6 To CQ Via RS0ISS*,SGATE,WIDE2-1 <UI pid=F0 Len=66 >[11:32:52]
=3726.20N/07742.21W-73' Via ISS w4tbd@xxxx.xxx FM17dk IGate WLNK-1



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:33:03]
'g.7l #/]SP=



Fm N3FCX To DJFT2R Via RS0ISS* <UI pid=F0 Len=14 >[11:33:31]
'g.7l #/]SP=
_______________________________________________
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


---
This email has been checked for viruses by AVG.
http://www.avg.com



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

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 12, Issue 108
*****************************************


Read previous mail | Read next mail


 12.05.2024 04:22:55lGo back Go up