[RTTY] New

Thu Jan 12 17:40:25 PST 2012

He signed /KL7. Which in my opinion, is the ONLY to sign your call if you're 
a non KL7 in Alaska.  NOT /AL or /KL

73
Jim W7RY

--------------------------------------------------
From: "Larry" <lknain at nc.rr.com>
Sent: Thursday, January 12, 2012 5:35 PM
To: <rtty at contesting.com>
Subject: Re: [RTTY] New

> While N7ZYS may be legal from an FCC point of view it
> would violate rules for many contests as it does not indicate
> its actual (DXCC, DX) country whereas N7ZYS/KL (or /NL,
> /AL) would be OK. The /KL etc does not automatically mean
> that the requests for state would stop but may reduce the requests.
>
> 73, Larry  W6NWS
> ----- Original Message ----- 
> From: "Gary AL9A" <al9a at mtaonline.net>
> To: "Rtty" <rtty at contesting.com>
> Sent: Thursday, January 12, 2012 8:07 PM
> Subject: Re: [RTTY] New
>
>
>> Jim hit the nail on the head with the exchange from AK.  We send a serial
>> number in RRU, not a state abbreviation.  So if N7ZYS sends just his call
>> and then the required serial number because he is in AK I suspect he will
>> get many requests for ST? ST? as the call by itself doesn't indicate his
>> DX
>> location.  So he is legal, but faces the dilemma of being slowed down by
>> having to send the "/KL" appended to his call or by the requests to send
>> his
>> "ST?"  I don't know how long Neil will be operating from AK, but the best
>> solution might be to apply for a standard AK call or vanity call from the
>> FCC for the duration up here.
>>
>> Even with my AK call sign I got many requests for "ST?" or "WHAT IS YOUR
>> STATE" as if I were to dumb to know the rules.  From prior experience I
>> anticipated this and had some memories in my MKII loaded with various
>> replies.
>>
>> AK AK DX DX QSL?  (This may not be good enough as some will think AK 
>> means
>> Arkansas!)
>> ALASKA ALASKA QSL?
>> and for the stubborn
>> AK IS DX IN RU - TU QRZ AL9A
>>
>> 73,
>> Gary AL9A
>>
>>
>> ----- Original Message ----- 
>> From: "Jim W7RY" <jimw7ry at gmail.com>
>> To: "Al Kozakiewicz" <akozak at hourglass.com>; "Neilensign"
>> <neilensign at yahoo.com>; "Rtty" <rtty at contesting.com>
>> Sent: January 12, 2012 1:35 PM
>> Subject: Re: [RTTY] New
>>
>>
>>> Alaska sends a serial number not a state.  I for one liked the /kl7. 
>>> That
>>> way I knew he was in Alaska and expected a serial number instead of a
>>> state.
>>> Some of the new folks sent a serial number and a state. I just wish they
>>> would read the rules.
>>>
>>> 73
>>> Jim W7RY
>>>
>>>
>>>
>>> --------------------------------------------------
>>> From: "Al Kozakiewicz" <akozak at hourglass.com>
>>> Sent: Thursday, January 12, 2012 1:56 PM
>>> To: "Neilensign" <neilensign at yahoo.com>; "Rtty" <rtty at contesting.com>
>>> Subject: Re: [RTTY] New
>>>
>>>> In a sense it did take forever; nearly twice as long at any rate,
>>>>
>>>> Sending just your callsign twice (N7ZYS N7ZYS) takes 17 characters.
>>>> Adding the /KL7 takes 31:
>>>>
>>>> BAUDOT is a 5 bit code, which translates into 32 possible combinations.
>>>> Not enough for all the letters, numbers and a few symbols.  As a 
>>>> result,
>>>> the code requires a letters shift character to tell the decoder that 
>>>> the
>>>> characters following are to be decoded as letters and a figures shift 
>>>> to
>>>> signify that the characters following are to be decoded as numbers or
>>>> figures. Some common characters (like space and CR) are in both the
>>>> letters and figs table.  So, to send N7ZYS/KL7 once requires the
>>>> following
>>>> sequence:
>>>>
>>>> {LTRS}N{FIGS}7{LTRS}ZYS{FIGS}/{LTRS}KL{FIGS}7{SP}
>>>>
>>>> You can see that adding the /KL7 adds 7 or 8 characters to your
>>>> callsign,
>>>> depending on whether a letter follows or not. E.g. /KL7 599 takes 7,
>>>> while
>>>> /KL7 AK takes 8 since you need to shift back to letters before sending
>>>> 'AK'.
>>>>
>>>> I don't believe signing /portable is required by law if you are 
>>>> licensed
>>>> in the USA.  If you only run S&P, adding the extra suffix probably
>>>> doesn't
>>>> buy you much.  Adding it when running might attract interest in certain
>>>> contests.  Obviously you need to use the same callsign throughout the
>>>> contest. so you need to choose wisely.
>>>>
>>>> Al
>>>> AB2ZY
>>>>
>>>> ________________________________________
>>>> From: rtty-bounces at contesting.com [rtty-bounces at contesting.com] On
>>>> Behalf
>>>> Of Neilensign [neilensign at yahoo.com]
>>>> Sent: Thursday, January 12, 2012 4:22 PM
>>>> To: Rtty
>>>> Subject: [RTTY] New
>>>>
>>>> Hello all,
>>>>
>>>> This past contest was my first. I posted a dismal 107 contacts. I'll
>>>> devote more time next time.
>>>> I have a couple of questions....
>>>> My call is N7ZYS and I used N7ZYS/KL7. Seemed like it took forever to
>>>> send
>>>> my call 2 times. Since I'm in Alaska, what would be appropriate?
>>>> Also, I downloaded the N1MM macros for the contest. I trusted they were
>>>> ok
>>>> to use the way they are. Is this ok to do?
>>>> I'm learning a lot about what and what not to do on here. Thanks,
>>>>
>>>> Neil
>>>> N7ZYS
>>>>
>>>> Sent from Neil's iPhone
>>>>
>>>> _______________________________________________
>>>> RTTY mailing list
>>>> RTTY at contesting.com
>>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>> _______________________________________________
>>>> RTTY mailing list
>>>> RTTY at contesting.com
>>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>
>>> _______________________________________________
>>> RTTY mailing list
>>> RTTY at contesting.com
>>> http://lists.contesting.com/mailman/listinfo/rtty
>>
>> _______________________________________________
>> RTTY mailing list
>> RTTY at contesting.com
>> http://lists.contesting.com/mailman/listinfo/rtty
>>
>
>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty 