I noticed on the ARRL lists of dxcc it lists KL7 as DXCC. Thats the
one I saw in the booklet they sell. I sign mine as du1/n6hpx and
occassionally kh2/n6hpx and from what I have seen its listed as DXCC.
Just curious if this is true or not
Larry, du1/n6hpx
marine mobile off japan
On 1/13/12, rtty-request@contesting.com <rtty-request@contesting.com> wrote:
> Send RTTY mailing list submissions to
> rtty@contesting.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.contesting.com/mailman/listinfo/rtty
> or, via email, send a message with subject or body 'help' to
> rtty-request@contesting.com
>
> You can reach the person managing the list at
> rtty-owner@contesting.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of RTTY digest..."
>
>
> Today's Topics:
>
> 1. Re: New (Gary AL9A)
> 2. Re: New (Larry)
> 3. Re: New (Jim W7RY)
> 4. RU Thanks from K3MJW (K3RWN)
> 5. Re: New (Gary AL9A)
> 6. Re. RTTY RU Exchange Complaints (Jack West)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 12 Jan 2012 16:07:53 -0900
> From: "Gary AL9A" <al9a@mtaonline.net>
> Subject: Re: [RTTY] New
> To: "Rtty" <rtty@contesting.com>
> Message-ID: <8988B6EE309C4D1AB83AC62A998D0CBB@AL9APC>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
> 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@gmail.com>
> To: "Al Kozakiewicz" <akozak@hourglass.com>; "Neilensign"
> <neilensign@yahoo.com>; "Rtty" <rtty@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@hourglass.com>
>> Sent: Thursday, January 12, 2012 1:56 PM
>> To: "Neilensign" <neilensign@yahoo.com>; "Rtty" <rtty@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@contesting.com [rtty-bounces@contesting.com] On Behalf
>>> Of Neilensign [neilensign@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@contesting.com
>>> http://lists.contesting.com/mailman/listinfo/rtty
>>> _______________________________________________
>>> RTTY mailing list
>>> RTTY@contesting.com
>>> http://lists.contesting.com/mailman/listinfo/rtty
>>
>> _______________________________________________
>> RTTY mailing list
>> RTTY@contesting.com
>> http://lists.contesting.com/mailman/listinfo/rtty
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 12 Jan 2012 20:35:08 -0500
> From: "Larry" <lknain@nc.rr.com>
> Subject: Re: [RTTY] New
> To: <rtty@contesting.com>
> Message-ID: <FB7BE6643F834D969BE49D6F617152F6@LarryKnainPC>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
> 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@mtaonline.net>
> To: "Rtty" <rtty@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@gmail.com>
>> To: "Al Kozakiewicz" <akozak@hourglass.com>; "Neilensign"
>> <neilensign@yahoo.com>; "Rtty" <rtty@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@hourglass.com>
>>> Sent: Thursday, January 12, 2012 1:56 PM
>>> To: "Neilensign" <neilensign@yahoo.com>; "Rtty" <rtty@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@contesting.com [rtty-bounces@contesting.com] On
>>>> Behalf
>>>> Of Neilensign [neilensign@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@contesting.com
>>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>> _______________________________________________
>>>> RTTY mailing list
>>>> RTTY@contesting.com
>>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>
>>> _______________________________________________
>>> RTTY mailing list
>>> RTTY@contesting.com
>>> http://lists.contesting.com/mailman/listinfo/rtty
>>
>> _______________________________________________
>> RTTY mailing list
>> RTTY@contesting.com
>> http://lists.contesting.com/mailman/listinfo/rtty
>>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 12 Jan 2012 17:40:25 -0800
> From: "Jim W7RY" <jimw7ry@gmail.com>
> Subject: Re: [RTTY] New
> To: "Larry" <w6nws@arrl.net>, <rtty@contesting.com>
> Message-ID: <98A64CB18AB7411C80F1D71832131D55@Laptop>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
> 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@nc.rr.com>
> Sent: Thursday, January 12, 2012 5:35 PM
> To: <rtty@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@mtaonline.net>
>> To: "Rtty" <rtty@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@gmail.com>
>>> To: "Al Kozakiewicz" <akozak@hourglass.com>; "Neilensign"
>>> <neilensign@yahoo.com>; "Rtty" <rtty@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@hourglass.com>
>>>> Sent: Thursday, January 12, 2012 1:56 PM
>>>> To: "Neilensign" <neilensign@yahoo.com>; "Rtty" <rtty@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@contesting.com [rtty-bounces@contesting.com] On
>>>>> Behalf
>>>>> Of Neilensign [neilensign@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@contesting.com
>>>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>>> _______________________________________________
>>>>> RTTY mailing list
>>>>> RTTY@contesting.com
>>>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>>
>>>> _______________________________________________
>>>> RTTY mailing list
>>>> RTTY@contesting.com
>>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>
>>> _______________________________________________
>>> RTTY mailing list
>>> RTTY@contesting.com
>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>
>>
>>
>> _______________________________________________
>> RTTY mailing list
>> RTTY@contesting.com
>> http://lists.contesting.com/mailman/listinfo/rtty
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 12 Jan 2012 21:22:41 -0500
> From: "K3RWN" <rwnewbould@comcast.net>
> Subject: [RTTY] RU Thanks from K3MJW
> To: "'RTTY'" <rtty@contesting.com>
> Message-ID: <21366889D329464DA7D3620252319D6F@RADIOROOM2>
> Content-Type: text/plain; charset="us-ascii"
>
> A big thanks to all from the M/S team at K3MJW. Thanks to all who worked us
> during the RU. We had a great time, great food, and turned in one of best
> efforts in the RU from the clubhouse.
>
>
>
> We did have some problems with RF getting into our internet connection and
> causing a disconnect from the cluster. This was a new issue and we were
> able to resolve it last night with some ferrite, too bad I did have some
> with me on the weekend. All of the other equipment including WL worked
> flawlessly.
>
>
>
> We had a fabulous run on 80m peaking out over 90 Qs per hour for two
> straight hours.
>
>
>
> It was great to see many familiar calls.
>
>
>
> Once again thanks to all
>
>
>
> We are already looking forward to next year
>
>
>
> K3RWN, K3RMB, WC3O, KB3EYY, AB3LS, and K3FH.
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 12 Jan 2012 17:39:26 -0900
> From: "Gary AL9A" <al9a@mtaonline.net>
> Subject: Re: [RTTY] New
> To: <rtty@contesting.com>
> Message-ID: <313BDC1463924D2F817561BB299540CC@AL9APC>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
>
> Not meaning to be nit picky here, but KL7 no more identifies AK than AL, KL,
> NL or WL. The number is immaterial, it can be any digit from 0 - 9.
> Traditionally a 7 was used because AK is in the Northwestern block of states
> covered by the 7th call district. The key designator in AK call signs is
> the "L", not the preceding letter and not the following number. The state
> is not subdivided into regions by number as is done for a country, so any
> number following the "L" does nothing to clarify the location. It does
> however slow down the exchange.
>
> 73,
> Gary AL9A
>
> ----- Original Message -----
> From: "Jim W7RY" <jimw7ry@gmail.com>
> To: "Larry" <w6nws@arrl.net>; <rtty@contesting.com>
> Sent: January 12, 2012 4:40 PM
> Subject: Re: [RTTY] New
>
>
>> 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
>>
>>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 12 Jan 2012 18:49:14 -0800
> From: "Jack West" <w7ldxp@embarqmail.com>
> Subject: [RTTY] Re. RTTY RU Exchange Complaints
> To: "RTTY GROUP" <rtty@contesting.com>
> Message-ID: <012601ccd19d$f0721220$0202a8c0@hamradio>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi All,
>
> One station sent MY CALL (three times) de HIS CALL (three times) RST 599
> (three times)
> and his STATE only (ONCE!) and I had to ask for a repeat.
>
> Talk about PRIORITIES!
>
> 73 de
> Jack / W7LD / "Lucky Dog"
>
>
> ------------------------------
>
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
>
> End of RTTY Digest, Vol 109, Issue 20
> *************************************
>
--
Member:ARRL, PARL
========================
monitoring shortwave,Ham Radio and scanners
========================
du1/n6hpx Cavite Philippines
Grid:pk04
also:VQ9LF,DU3/N6HPX
========================
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|