BLIND-HAMS Archives

For blind ham radio operators

BLIND-HAMS@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Buddy Brannan <[log in to unmask]>
Reply To:
For blind ham radio operators <[log in to unmask]>
Date:
Sun, 31 Jan 2016 19:58:23 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
AGN = Again
TU = Thank you

Probably "73" and "QRZ?" would be good to know, as would "5NN", because everyone's a 5NN. Screw all the other numbers. Wanna piss off a contester? Give him a 437 signal report. Sure, nobody has a tone any less thann a N these days, but if you're going to give an inaccurate signal report anyway, you may as well have some fun with it. 

--
Buddy Brannan, KB5ELV - Erie, PA
Phone: 814-860-3194 
Mobile: 814-431-0962
Email: [log in to unmask]




> On Jan 31, 2016, at 7:08 PM, Scott Gillen <[log in to unmask]> wrote:
> 
> I was reading another list the other day and they were talking=20
> about high-speed code.  One guy said the DX vocabulary is very small and rea=
> sonably easy to learn at high-speed.=20
> 
> This is what he claimed you needed to know
> 
> CQ, AGN, ?, UP, TU, and your own call sign.
> 
> My question for you CW DXers is, do you agree? =20
> And what does AGN and TU stand for?
> 
> 73
> Scott
> N0HOK / ZL1CHM
> Auckland New Zealand
> 
> Sent from my iPhone=

ATOM RSS1 RSS2