| |
CX2SA > SATDIG 03.10.16 15:44l 790 Lines 24752 Bytes #999 (0) @ WW
BID : AMSATBB11317
Read: GUEST
Subj: AMSAT-BB-digest V11 317
Path: IW8PGT<CX2SA
Sent: 161003/1342Z @:CX2SA.SAL.URY.SOAM #:54686 [Salto] FBB7.00e $:AMSATBB11317
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: QSO Protocol (Jeff Yanko)
2. Re: QSO Protocol (Jeff Yanko)
3. Re: QSO Protocol (Jim Walls)
4. Re: QSO Protocol (James Duffey)
5. Illumination Program (Joe)
6. Re: QSO Protocol (B J)
7. Off-topic But Related To Amateur Radio (B J)
8. Re: Illumination Program (Norm n3ykf)
9. Re: QSO Protocol (Graham Shirville)
10. Re: QSO Protocol (Scott Medbury)
11. QSO Protocol (Keith O'Brien)
12. Re: QSO Protocol (Simon Brown)
13. Re: QSO Protocol (Matthew Stevens)
14. QSO Protocol (Kevin M)
15. Re: QSO Protocol (Bruce)
----------------------------------------------------------------------
Message: 1
Date: Sun, 2 Oct 2016 15:11:03 -0700
From: Jeff Yanko <wb3jfs@xxx.xxx>
To: Paul Stoetzer <n8hm@xxxx.xxx>
Cc: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QSO Protocol
Message-ID: <7435a885-8596-db33-7c99-6532def175d1@xxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed
I would suspect that most people make QSO's via the birds to obtain
awards, certificates, etc. In a lot of cases, not all, grids are
required. That's why if you notice most QSL's printed up now have the
grid square listed along with possibly CQ and ITU zones. 10 years back,
I've never recalled a QSL with the grid square listed.
73,
Jeff WB3JFS
On 10/2/2016 2:51 PM, Paul Stoetzer wrote:
> Grid square isn't required. Time certainly isn't needed in any
> exchange (except for BARTG RTTY contest).
>
> 73,
>
> Paul, N8HM
>
> On Sunday, October 2, 2016, Jeff Yanko <wb3jfs@xxx.xxx
> <mailto:wb3jfs@xxx.xxx>> wrote:
>
> Callsign and grid square is all that is needed, plus the time,
> (UTC). Signal report on any birds isn't necessary.
>
> BTW, signal reports aren't needed for HF QSO under WAS or DXCC.
>
>
> 73,
>
> Jeff WB3JFS
>
>
> On 10/2/2016 1:37 PM, Joe wrote:
>
> What is the standard for a minimal contact of what must be
> exchanged for a valid QSO?
>
> Joe WB9SBD
>
>
> _______________________________________________
> 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
> <http://www.amsat.org/mailman/listinfo/amsat-bb>
>
------------------------------
Message: 2
Date: Sun, 2 Oct 2016 15:14:46 -0700
From: Jeff Yanko <wb3jfs@xxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] QSO Protocol
Message-ID: <fc85aab5-f961-785b-5d73-d23b093fe92f@xxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed
LOL! Plus the first born, just to be safe.
Jeff WB3JFS
On 10/2/2016 3:04 PM, Clayton W5PFG wrote:
> If you want to make a lot of friends, I would suggest providing your
> twelve digit grid square as part of the exchange. Make sure the other
> station repeats it back to you in its entirety. That way you know
> you're in the log and you had a clean QSO.
>
> 73
> Clayton
> W5PFG
>
> On 10/2/2016 15:45, Jim Jerzycke wrote:
>> Callsign and signal report?
>>
>>
>> Maybe name and grid square?
>>
>>
>> Jim KQ6EA
>>
>>
>> On 10/02/2016 08:37 PM, Joe wrote:
>>> What is the standard for a minimal contact of what must be exchanged
>>> for a valid QSO?
>>>
>>> Joe WB9SBD
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership.
> Opinions expressed
> are solely those of the author, and do not reflect the official views
> of AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 3
Date: Sun, 2 Oct 2016 16:04:44 -0700
From: Jim Walls <jim@xxxxx.xxx>
To: Amsat-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QSO Protocol
Message-ID: <46baadf3-9b25-b650-d2e1-ff9121cc526e@xxxxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 10/2/2016 15:11, Jeff Yanko wrote:
> I would suspect that most people make QSO's via the birds to obtain
> awards, certificates, etc. In a lot of cases, not all, grids are
> required. That's why if you notice most QSL's printed up now have the
> grid square listed along with possibly CQ and ITU zones. 10 years
> back, I've never recalled a QSL with the grid square listed.
This web page shows a revision date in 2000. Both cards with my current
call shows have the four digit grid square printed on the card.
Although I can't positively state it, I assume the "terrestrial" card
was printed shortly after I changed callsign in 1997.
http://members.dslextreme.com/users/k6ccc/QSL.html
--
73
-------------------------------------
Jim Walls - K6CCC
jim@xxxxx.xxx
Ofc: 818-548-4804
http://members.dslextreme.com/users/k6ccc/
AMSAT Member 32537 - WSWSS Member 395
------------------------------
Message: 4
Date: Sun, 2 Oct 2016 18:00:53 -0600
From: James Duffey <jamesduffey@xxxxxxx.xxx>
To: Joe <nss@xxx.xxx>
Cc: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QSO Protocol
Message-ID: <C6A234B4-7520-4E59-93F1-0A34E2FB8F3E@xxxxxxx.xxx>
Content-Type: text/plain; charset=windows-1252
Joe - Historically and traditionally, the minimum standard for VHF QSOes has
been:
Both stations send and copy both calls
Both stations exchange a meaningful piece of information
Both stations acknowledge receipt of the information.
So a minimal QSO would go like this:
KK6MC: CQ KK6MC
WB9BSD: WB9SBD
KK6MC: WB9SBD, DM65tc
KK6MC: roger, EN43XO
WB9BSD: roger
At this point the required minimum amount of information has been exchanged,
but there is some ambiguity as to whether or not KK6MC has received WB9SBD?s
rogers, so it is customary for KK6MC to send 73 to acknowledge the roger. So
the typical QSO goes:
KK6MC: CQ KK6MC
WB9BSD: WB9SBD
KK6MC: WB9SBD, DM65tc
KK6MC: roger, EN43XO
WB9BSD: roger
KK6MC: 73
Nothing says that satellite QSOes have to go this way, but it is a good
place to start. Everything is there and if you take something out, it starts
to make less sense. I hope that this helps. - Duffey KK6MC
On Oct 2, 2016, at 2:37 PM, Joe <nss@xxx.xxx> wrote:
> What is the standard for a minimal contact of what must be exchanged for a
valid QSO?
>
> Joe WB9SBD
> --
> Sig
> The Original Rolling Ball Clock
> Idle Tyme
> Idle-Tyme.com
> http://www.idle-tyme.com
> _______________________________________________
> 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
--
KK6MC
James Duffey
Cedar Crest NM
------------------------------
Message: 5
Date: Sun, 2 Oct 2016 19:08:55 -0500
From: Joe <nss@xxx.xxx>
To: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Illumination Program
Message-ID: <ba0aa1e4-d81f-048e-7111-b7aaa4571005@xxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed
The program that somone posted that tells us how well like AO-7 is being
illuminated.
I downloaded it. but cant get it to run. it complains about a missing
.OCX file.
Anyone have any help?
Joe WB9SBD
--
Sig
The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com
------------------------------
Message: 6
Date: Mon, 3 Oct 2016 00:12:27 +0000
From: B J <va6bmj@xxxxx.xxx>
To: Paul Stoetzer <n8hm@xxxx.xxx>
Cc: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QSO Protocol
Message-ID:
<CAP7QzkO0Qti=apTrr3zq4xwUT5JPb8P3k2mcSm9yZMg2i7UaCw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
On 10/2/16, Paul Stoetzer <n8hm@xxxx.xxx> wrote:
> Callsign + one additional piece of info (grid square, signal report,
> location, name, etc).
I've always understood that the minimum was that both stations give
their callsigns and grid squares.
I send out wallpaper whenever I contact a new station or grid square.
I haven't gone after any awards as such, but, maybe, the other station
does.
73s
Bernhard VA6BMJ @ DO33FL
------------------------------
Message: 7
Date: Mon, 3 Oct 2016 00:38:09 +0000
From: B J <va6bmj@xxxxx.xxx>
To: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Off-topic But Related To Amateur Radio
Message-ID:
<CAP7QzkP8exUHgfX9EbwJeHQ-GugZkvOw3aq8qygk3+G5f3WAdQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Turn an old drafting compass into a holder for a pair of multimeter probes:
http://hackaday.com/2016/10/02/multimeter-probe-goes-full-circle/
There have been lots of times when I'm checking a circuit or cable
that I've wished I could hold both probes with one hand and use the
other hand to, say, adjust my meter. What a clever idea!
73s
Bernhard VA6BMJ @ DO33FL
------------------------------
Message: 8
Date: Sun, 2 Oct 2016 21:11:26 -0400
From: Norm n3ykf <normanlizeth@xxxxx.xxx>
To: Joe <nss@xxx.xxx>
Cc: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Illumination Program
Message-ID:
<CAJUhCTM61BjWZfG0iPdMKPwPbn+sZgWoCQ5cP9TBd8aJX5eqfA@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Google the appropriate file name. Try and find a reputable download
site. Cross your fingers, download. scan and place correctly.
IIRC that file is difficult to find because it's (obsolete) IP.
Last time that trick wouldn't get Mike's code to run.
Good luck.
Norm n3ykf
On Sun, Oct 2, 2016 at 8:08 PM, Joe <nss@xxx.xxx> wrote:
> The program that somone posted that tells us how well like AO-7 is being
> illuminated.
>
> I downloaded it. but cant get it to run. it complains about a missing .OCX
> file.
>
> Anyone have any help?
>
> Joe WB9SBD
> --
> Sig
> The Original Rolling Ball Clock
> Idle Tyme
> Idle-Tyme.com
> http://www.idle-tyme.com
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
> expressed
> are solely those of the author, and do not reflect the official views of
> AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 9
Date: Mon, 3 Oct 2016 08:40:50 +0100
From: "Graham Shirville" <g.shirville@xxxxxxxxxx.xxx>
To: "AMSAT BB" <amsat-bb@xxxxx.xxx>, "Jeff Yanko" <wb3jfs@xxx.xxx>
Subject: Re: [amsat-bb] QSO Protocol
Message-ID: <0D864B1AAC834041ABA8B69FC1707DBC@xxxxxxx.xxxxx>
Content-Type: text/plain; charset="Windows-1252"
Hi Jeff,
For VHF in IARU Region 1 it is all here, currently encapsulated in 144 (!)
pages. The decisions and recommendations have been distilled as a result of
agreements reached in regional meetings held every 18 months for the past
?n? years. Download
I am not sure about awards but there are lots of contests which now have
online entry systems.
Of course generally only EME and satellite operations extend across Regional
?Borders? on these frequencies.
Happy reading
73
Graham
G3VZV
From: Jeff Yanko
Sent: Sunday, October 02, 2016 11:07 PM
To: Graham Shirville ; AMSAT BB
Subject: Re: [amsat-bb] QSO Protocol
Hi Graham,
That's the first I've heard of an IARU standard for a QSO, not saying there
isn't any. Interesting. Does the IARU issue awards in which you submit QSO
data to them to obtain?
73,
Jeff WB3JFS
On 10/2/2016 2:38 PM, Graham Shirville wrote:
Hi Jeff,
Here in IARU Region 1 we agreed a definition of a valid QSO sometime back
for VHF and above.
They are shown in this extract
http://www.southgatearc.org/news/may2007/qso_definition.htm
I suspect that such definitions have probably not yet been elaborated in
the other two IARU Regions
73
Graham
G3VZV
-----Original Message-----
From: Jeff Yanko
Sent: Sunday, October 02, 2016 10:31 PM
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] QSO Protocol
Callsign and grid square is all that is needed, plus the time, (UTC).
Signal report on any birds isn't necessary.
BTW, signal reports aren't needed for HF QSO under WAS or DXCC.
73,
Jeff WB3JFS
On 10/2/2016 1:37 PM, Joe wrote:
> What is the standard for a minimal contact of what must be exchanged
> for a valid QSO?
>
> Joe WB9SBD
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership. Opinions
expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 10
Date: Mon, 03 Oct 2016 07:20:56 -0500
From: Scott Medbury <smedbury@xxxxxxxxxx.xxx>
To: Jim Jerzycke <kq6ea@xxxxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] QSO Protocol
Message-ID: <20161003122457.56CB18D8E@xxxxxxxxxx.xxxxx.xxx>
Content-Type: text/plain; charset=utf-8
Typically for satellite name, grid, and sometimes SES Identifier or state
for rover's. Or body of water for maritime mobile.
Scott KD5FBA
Sent from my Verizon Wireless 4G LTE DROID
On Oct 2, 2016 3:45 PM, Jim Jerzycke <kq6ea@xxxxxxx.xxx> wrote:
>
> Callsign and signal report?
>
>
> Maybe name and grid square?
>
>
> Jim? KQ6EA
>
>
> On 10/02/2016 08:37 PM, Joe wrote:
> > What is the standard for a minimal contact of what must be exchanged
> > for a valid QSO?
> >
> > Joe WB9SBD
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
expressed
> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 11
Date: Mon, 3 Oct 2016 12:36:16 +0000 (UTC)
From: Keith O'Brien <n4zq@xxxxx.xxx>
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] QSO Protocol
Message-ID: <373638499.8532525.1475498176779@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
So these messages I see from time to time here on the AMSAT-BB that say "
Did anyone copythe call sign of the station I just worked "? are not valid
contacts, and shouldn't be countedfor anything but nice try, maybe next time.
Keith N4ZQ
------------------------------
Message: 12
Date: Mon, 3 Oct 2016 13:41:16 +0100
From: "Simon Brown" <simon@xxxxxxxxx.xxx>
To: "'Keith O'Brien via AMSAT-BB'" <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QSO Protocol
Message-ID: <002e01d21d73$6ed51ab0$4c7f5010$@xxxxxxxxx.xxx>
Content-Type: text/plain; charset="utf-8"
What is the station forgot the callsign in the heat of battle?
Myself I run a recording (SDR data IQ) so I can always replay the pass if
needed. My excuse is tinnitus and being easily confused...
Simon Brown, GK4ELI
http://sdr-radio.com
-----Original Message-----
From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Keith
O'Brien via AMSAT-BB
Sent: 03 October 2016 13:36
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] QSO Protocol
So these messages I see from time to time here on the AMSAT-BB that say "
Did anyone copythe call sign of the station I just worked " are not valid
contacts, and shouldn't be countedfor anything but nice try, maybe next time.
Keith N4ZQ
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership. Opinions
expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 13
Date: Mon, 3 Oct 2016 09:04:44 -0400
From: Matthew Stevens <matthew@xxxxxxxxx.xxx>
To: Simon Brown <simon@xxxxxxxxx.xxx>
Cc: Keith O'Brien via AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QSO Protocol
Message-ID: <FE6C261F-5D6C-4890-B4A5-97B26D24A599@xxxxxxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
My excuse is just being easily confused :D
Recordings have saved my QSOs more times than once.
- Matthew KK4FEM
Sent from my iPhone
> On Oct 3, 2016, at 08:41, Simon Brown <simon@xxxxxxxxx.xxx> wrote:
>
> What is the station forgot the callsign in the heat of battle?
>
> Myself I run a recording (SDR data IQ) so I can always replay the pass if
needed. My excuse is tinnitus and being easily confused...
>
> Simon Brown, GK4ELI
> http://sdr-radio.com
>
> -----Original Message-----
> From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Keith
O'Brien via AMSAT-BB
> Sent: 03 October 2016 13:36
> To: AMSAT-BB <amsat-bb@xxxxx.xxx>
> Subject: [amsat-bb] QSO Protocol
>
> So these messages I see from time to time here on the AMSAT-BB that say "
Did anyone copythe call sign of the station I just worked " are not valid
contacts, and shouldn't be countedfor anything but nice try, maybe next time.
> Keith N4ZQ
> _______________________________________________
> 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
>
> _______________________________________________
> 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: 14
Date: Mon, 3 Oct 2016 13:34:51 +0000 (UTC)
From: Kevin M <n4ufo@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] QSO Protocol
Message-ID: <1148292044.2796818.1475501691168@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
As far as valid QSOs for ARRL awards are concerned (DXCC/VUCC/WAS), they
simply state a 'contact' must be made. But no where do they ever define what
a contact consists of. They leave this definition up to the award applicant
and the stations that he/she contacts. When asked, I have always explained a
contact as, "I called you and you knew it was me, you answered and I knew it
was you..." In short, as long as we both understand that we 'contacted' each
other, then it's a contact.
My point is, there is no specified rule that says a grid square or any other
piece of information is exchanged. There is actually no rule that says the
CALLSIGN must be EXCHANGED. A contact exists when the two parties involved
in the communication agree that the contact happened... whether they
exchange a 'QSL' on air, via e-mail, LotW or by USPS mail, if both parties
agree that it took place... then it took place. The requirement for any
more, is to saddle the participants with a burden to overcome the
non-natural hindrances that can occur with high volume traffic over man made
devices... i.e. satellites. If EME or meteor scatter operators want to place
certain burdens upon themselves to ensure that their imaginations, tricks of
the senses, or natural phenomena did not insert a bit of faux communication
that did not actually take place, that is their perogative. BUT, why should
one penalize a station and say that a contact did not take place simply
because some guy with 50 w
atts and crap for a receiver decided to say, "Halllo! One, two, three,
haaaalo!" over top of Jeeves while he was uttering his grid square. Further,
since satellite passes are a time limited resource, why should we take away
precious airtime from others by forcing a repeat of a piece of information
that we likely already know, and at the very least can easily look up
online, etc.
Simply put... if I'm in a rare grid square working lots of stations on a
frenzied pass and I hear a voice I recognize saying his/her callsign while
obviously calling me, but someone keys on top of him in the middle of saying
his callsign, is it really necessary for me to say, "Who is the Hotel Mike?"
when I KNOW who it is? OR worse, stop to take the time to ask, 'What's your
grid again, Paul?' - Paul knew it was me, I knew it was Paul, I'm simply
going to say, "In the log, Paul," and call the next station.
Common sense and basic trust in personal integrity goes a long way towards
making life simpler and more enjoyable.... QSL?? 73!? N4UFO, EM95, over.
------------------------------
Message: 15
Date: Mon, 3 Oct 2016 08:40:16 -0500
From: Bruce <kk5do@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] QSO Protocol
Message-ID: <b30386d3-e4c9-0796-4a51-90fad3585c92@xxxxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed
i thought i would let this run a bit and see what transpired. i get
really annoyed when i hear someone in a rare grid (let's just take CY9C
for example) and people go back and forth with call and grid several times.
when i did a bit of traveling, my trick in maximizing my contacts was to
listen for a bit when i first heard the satellite and write down all the
calls i hear. if i wrote it down, i heard it, right? then i get on the
air and announce myself giving my call and grid and ask for people to
call me once. i put a check mark next to their call when they call back
(now, they heard my call or they would not have come back to me and i am
verifying their call again with my check mark).
then when there is a pause, i get back on the air and say xx1xx, xx2xx,
xx3xx, xx4xx, i have you any others? i write down the list i hear and go
back and say yy1yy, yy2yy, yy3yy, i have you. i only had to give my grid
once at the beginning and i really could care less what grid you are in,
i am not going to write it down nor repeat it back to you. i have no
interest in trying to earn vucc from a grid i work from once or twice.
if i recognize your voice, i even had your call down before i heard you
give it.
we made a two way contact because i copied your call, you copied mine
and we are all good. with this method, i can log about 10-20 stations in
a very short time. everyone gets in that wants to. with short satellite
passes, it is virtually impossible to do back and forth and back and
forth and then there is always the 'thanks for the contact, have fun'. i
know it is polite and you would like to do it but on satellite passes,
it is just not possible unless only a few get in and that is what i saw
on several of the CY9C passes on SO-50.
maybe it is not the best plan but it worked good for me and there were
many more sat operators on the air back in the ao-10/13 and ao-40 days
than now.
73...bruce
--
Bruce Paige, KK5DO
AMSAT Director Contests and Awards
AMSAT Board Member 2016-2018
AMSAT Board Alternate 2015-2016
ARRL Awards Field Checker (WAS, 5BWAS, VUCC), VE
Houston AMSAT Net - Wed 0100z on Echolink - Conference *AMSAT*
Also live streaming MP3 at http://www.amsatnet.com
Podcast at http://www.amsatnet.com/podcast.xml or iTunes
Latest satellite news on the ARRL Audio News
http://www.arrl.org
AMSAT on Twitter http://www.twitter.com/amsat
------------------------------
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 317
*****************************************
Read previous mail | Read next mail
| |
