Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+Cut\s+number\s+advice\s*$/: 24 ]

Total 24 documents matching your query.

1. [CQ-Contest] Cut number advice (score: 1)
Author: "AD5VJ Bob" <rtnmi@sbcglobal.net>
Date: Sun, 4 Nov 2007 13:32:47 -0600
I just went through many hours of ss not understanding why I was getting so many repeats. Since my logging applications lets me decide whether to use all cut numbers or just the T for 0 I decided to
/archives//html/CQ-Contest/2007-11/msg00131.html (6,940 bytes)

2. Re: [CQ-Contest] Cut number advice (score: 1)
Author: KI9A@aol.com
Date: Sun, 4 Nov 2007 17:59:15 EST
I personally HATE cut numbers. I can copy at 30wpm while talking on the phone, but cuts kill me. If everyone used them, fine. But, if you send them to me, be prepared to repeat. Well, other than 5NN
/archives//html/CQ-Contest/2007-11/msg00132.html (7,290 bytes)

3. Re: [CQ-Contest] Cut number advice (score: 1)
Author: John Geiger <n5ten@yahoo.com>
Date: Sun, 4 Nov 2007 19:15:25 -0800 (PST)
Hi BOb, I set up the keyer in my FT920 to use T for 0 but kept getting repeats on the NR today. I guess that most people weren't expecting to hear a T at the beginning of a number. I changed it back
/archives//html/CQ-Contest/2007-11/msg00134.html (9,162 bytes)

4. Re: [CQ-Contest] Cut number advice (score: 1)
Author: Jeff Stai <jds@twistedoak.com>
Date: Sun, 04 Nov 2007 22:37:01 -0800
Good advice. They only confuse the new people and the casual operators. And we need them. thanks! - jeff wk6i -- Jeff Stai jds@twistedoak.com Twisted Oak Winery http://www.twistedoak.com/ Winery Blog
/archives//html/CQ-Contest/2007-11/msg00139.html (8,129 bytes)

5. Re: [CQ-Contest] Cut number advice (score: 1)
Author: "Gerry Hull" <gerry.hull@gmail.com>
Date: Mon, 5 Nov 2007 09:09:18 -0500
I used NN VT instead of 99 VT. I got asked for a lot of fills. I found this strange... N for 9 is VERY common. If I sent NN as the fill, they get it immediately. ... then there are the other guys who
/archives//html/CQ-Contest/2007-11/msg00145.html (10,423 bytes)

6. Re: [CQ-Contest] Cut number advice (score: 1)
Author: "Jeffrey Embry" <jeffrey.embry@gmail.com>
Date: Mon, 5 Nov 2007 09:05:59 -0500
Personally...I don't care for cut-numbers in any contest. In my opinion...if the exchange as specified in the rules calls for a number then send a number...not a T or N or whatever. -- Jeff Embry, K3
/archives//html/CQ-Contest/2007-11/msg00148.html (8,197 bytes)

7. Re: [CQ-Contest] Cut number advice (score: 1)
Author: Tom Hammond <n0ss@embarqmail.com>
Date: Mon, 05 Nov 2007 09:12:55 -0600
Hi Gerry: Well..... maybe not... at least one leading zero is NOT always a waste... It's certainly not a waste if you start in the middle of the contest, sending "1" and you get repeatedly asked for
/archives//html/CQ-Contest/2007-11/msg00149.html (8,670 bytes)

8. Re: [CQ-Contest] Cut number advice (score: 1)
Author: "Don Cassel" <ve3xd@rogers.com>
Date: Mon, 5 Nov 2007 10:32:15 -0500
I think much of the problem with cut numbers is one of expectations. One expects to hear a cut number for a leading zero in the serial number especially early in the game but I know that NN for year
/archives//html/CQ-Contest/2007-11/msg00154.html (12,374 bytes)

9. Re: [CQ-Contest] Cut number advice (score: 1)
Author: J F <phriendly1@yahoo.com>
Date: Mon, 5 Nov 2007 07:46:10 -0800 (PST)
I sent cut numbers in the original exchange, but only T for Zeros... I really don't like N for anything other than a signal report. If asked for a repeat, I sent full the full number. Worked every ti
/archives//html/CQ-Contest/2007-11/msg00156.html (10,220 bytes)

10. Re: [CQ-Contest] Cut number advice (score: 1)
Author: John Geiger <n5ten@yahoo.com>
Date: Mon, 5 Nov 2007 07:34:40 -0800 (PST)
NN did cause me to pause for a minute when I got his exchange, but I did figure it out without a repeat. I am not used to hearing cut numbers in the check either. I think that O almost works better a
/archives//html/CQ-Contest/2007-11/msg00158.html (13,791 bytes)

11. Re: [CQ-Contest] Cut number advice (score: 1)
Author: John Geiger <n5ten@yahoo.com>
Date: Mon, 5 Nov 2007 07:30:58 -0800 (PST)
Hi Jeff, That is what I said when the discussion came up before. What is the purpose of saying the check is the last 2 digits of the year first licensed, if they don't intend on enforcing it? Why not
/archives//html/CQ-Contest/2007-11/msg00159.html (11,572 bytes)

12. Re: [CQ-Contest] Cut number advice (score: 1)
Author: "K0HB " <k-zero-hb@earthlink.net>
Date: Mon, 5 Nov 2007 15:44:37 -0000
though. WriteLog (for one) allows you to specify the length (in 'n' digits) of the serial number, and pads the number with the required number of leading zeroes. For example if you specify 'n'=3, th
/archives//html/CQ-Contest/2007-11/msg00162.html (9,010 bytes)

13. Re: [CQ-Contest] Cut number advice (score: 1)
Author: "Gerry Hull" <gerry@yccc.org>
Date: Mon, 5 Nov 2007 10:34:54 -0500
Hi Tom, I guess you are right. Simpy Sending NR before the number eliminates that problem. Most people do send the NR. -- <img src = "http://www.customsoftware.tv/w1vesig.gif" border=0 </img> _______
/archives//html/CQ-Contest/2007-11/msg00163.html (10,375 bytes)

14. Re: [CQ-Contest] Cut number advice (score: 1)
Author: Jimk8mr@aol.com
Date: Mon, 5 Nov 2007 11:21:44 EST
I used NN VT instead of 99 VT. I got asked for a lot of fills. I found this strange... N for 9 is VERY common. If I sent NN as the fill, they get it immediately. Unlike the NN in 5NN, the SS check ac
/archives//html/CQ-Contest/2007-11/msg00171.html (9,310 bytes)

15. Re: [CQ-Contest] Cut number advice (score: 1)
Author: "Gerry Hull" <gerry.hull@gmail.com>
Date: Mon, 5 Nov 2007 11:29:08 -0500
I thought I'd try it out for one contest... I'd say 60 out of 900+ QSOs asked for a fill... about 7%. That's more than I want, so I'll send the full numbers next time. I did notice a distinct pause a
/archives//html/CQ-Contest/2007-11/msg00172.html (10,266 bytes)

16. Re: [CQ-Contest] Cut number advice (score: 1)
Author: "Dave Hachadorian" <K6LL@ARRL.net>
Date: Mon, 5 Nov 2007 15:56:15 -0000
In SS CW, somebody sent me 3AA, and I was supposed to figure out that it meant 31A! This is in a contest where logging accuracy is critical. Other than 5NN, cut numbers are nuts. Another bad idea is
/archives//html/CQ-Contest/2007-11/msg00174.html (9,214 bytes)

17. Re: [CQ-Contest] Cut number advice (score: 1)
Author: "Steve Harrisonusa" <k0xp@dandy.net>
Date: Mon, 5 Nov 2007 12:03:36 -0500 (EST)
I was one of those who got "bit" by your "NN". The problem was that you were too weak to actually hear the "NN"; and also, I just didn't expect anyone to be using cut numbers in the SS exchange; nev
/archives//html/CQ-Contest/2007-11/msg00175.html (10,123 bytes)

18. Re: [CQ-Contest] Cut number advice (score: 1)
Author: kd4d@comcast.net
Date: Mon, 05 Nov 2007 17:18:16 +0000
I had someone send me "48TU", which I interpreted as 48 and then "Why is this guy saying thanks?" I ended up missing the check as well, That, at least, was an unfortunate combination. So, especially
/archives//html/CQ-Contest/2007-11/msg00177.html (11,300 bytes)

19. Re: [CQ-Contest] Cut number advice (score: 1)
Author: Steve London <n2icarrl@gmail.com>
Date: Mon, 05 Nov 2007 10:54:22 -0700
I hate to disagree with my good friend Tom, but.... The issue with giving out #1-#9 goes away very quickly...on the 10th QSO ! Receiving a leading zero on a serial number always takes me by surprise.
/archives//html/CQ-Contest/2007-11/msg00180.html (9,624 bytes)

20. Re: [CQ-Contest] Cut number advice (score: 1)
Author: John Geiger <n5ten@yahoo.com>
Date: Mon, 5 Nov 2007 09:59:29 -0800 (PST)
3AA could also be 311, meaning they had no prec. 73s John AA5JG http://lists.contesting.com/mailman/listinfo/cq-contest __________________________________________________ Do You Yahoo!? Tired of spam
/archives//html/CQ-Contest/2007-11/msg00182.html (10,431 bytes)


This search system is powered by Namazu