Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+QRPers\s+\-\-\-\s+Please\s+QRQ\s*$/: 21 ]

Total 21 documents matching your query.

1. [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "K0HB " <k-zero-hb@earthlink.net>
Date: Mon, 7 Nov 2005 19:40:17 -00
While Danny may shoot me for saying it, it's great to see so many QRPers in contesting. But it seems that many of them feel they need to send slooooooow and use "words twice" procedure to get their m
/archives//html/CQ-Contest/2005-11/msg00275.html (8,077 bytes)

2. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Bob Naumann - W5OV" <w5ov@w5ov.com>
Date: Mon, 07 Nov 2005 14:40:13 -0600
that Q, because after the second try you're going to get a quick "R TU" from me and I'll do an <alt-W> and move on. << What type of logic leads you to tell the QRP (or other difficult to copy) statio
/archives//html/CQ-Contest/2005-11/msg00278.html (7,652 bytes)

3. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Barry " <w2up@mindspring.com>
Date: Mon, 07 Nov 2005 20:42:17 -0000
Another note for QRPers, and anyone else, for that matter. Please follow instructions. If I say "NR ONLY" don't repeat the whole exchange. If I ask for "suffix only" don't give me your enitre call ag
/archives//html/CQ-Contest/2005-11/msg00279.html (9,524 bytes)

4. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: Pete Smith <n4zr@contesting.com>
Date: Mon, 07 Nov 2005 15:38:29 -0500
I have been pleasantly surprised, over the last 10 years or so, to see such rapid improvement in the average quality of QRP ops. A decade ago, a lot of them seemed to be using their left feet, or a b
/archives//html/CQ-Contest/2005-11/msg00280.html (9,124 bytes)

5. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Tom McAlee" <tom@klient.com>
Date: Mon, 7 Nov 2005 16:46:26 -0500
I agree with all of the recommendations. Many times this weekend the QRPers slowed down when I asked for a repeat, as if the reason I couldn't copy it was because they were sending too fast. Nope...
/archives//html/CQ-Contest/2005-11/msg00281.html (8,378 bytes)

6. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: mwdink@eskimo.com
Date: Mon, 7 Nov 2005 14:48:02 -0800 (PST)
But it's really cool when they fade out sending your call, they rise up out of the noise for the number and Prec, fade for their call, then rise up once more for the Check and Section.... :>) It happ
/archives//html/CQ-Contest/2005-11/msg00284.html (7,199 bytes)

7. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "N7MAL" <N7MAL@CITLINK.NET>
Date: Mon, 7 Nov 2005 23:25:49 -0000
I am even more impressed at the quality of some of the QRP signals. Several were over S-9 and one in Colorado was even 20 over 9. Those QRP guys have been doing a lot of antenna work and have really
/archives//html/CQ-Contest/2005-11/msg00286.html (10,779 bytes)

8. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: John Laney <k4bai@worldnet.att.net>
Date: Mon, 07 Nov 2005 18:27:00 -0500
In my opinion Hans, you should tell the QRPer that you didn't copy his exchange, so there is no QSO at this time. Maybe he will call later and you will get the exchange then. You no doubt want him to
/archives//html/CQ-Contest/2005-11/msg00287.html (8,130 bytes)

9. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Dale Putnam" <daleputnam@hotmail.com>
Date: Mon, 07 Nov 2005 17:18:32 -0700
And with the correct procedures, fills are minimal. Ask for what is needed... quickly. And send it once... let the rx station request what ... and only what he needs. I got real exasperated with the
/archives//html/CQ-Contest/2005-11/msg00288.html (11,259 bytes)

10. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Warren C. Stankiewicz" <nf1j@earthlink.net>
Date: Mon, 7 Nov 2005 16:48:44 -0800
What's interesting to me is that there were a lot of people this past weekend who wouldn't hear me when I sent at 30, but *did* hear me when I slowed down to 26. In fact, it got to the point where I'
/archives//html/CQ-Contest/2005-11/msg00290.html (9,063 bytes)

11. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Steve Murphy" <murphys@comcast.net>
Date: Mon, 7 Nov 2005 20:35:34 -0500
I don't normally get involved in these discussions, but I have to ask... Am I really your QSO #160? :-) Just kidding. 73- Steve N8NM _______________________________________________ CQ-Contest mailing
/archives//html/CQ-Contest/2005-11/msg00293.html (8,174 bytes)

12. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: K6VVA - Contester <dx35@hilding.com>
Date: Mon, 07 Nov 2005 21:25:13 -0800
Well put, John...essentially the good old "Golden Rule". Amen & Amen. Over 10% of my SS QSOs were with "Q" stations, and 75% of those were "brain beaters" in trying to copy them way down in the crud.
/archives//html/CQ-Contest/2005-11/msg00302.html (10,102 bytes)

13. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: Doug Smith W9WI <w9wi@earthlink.net>
Date: 07 Nov 2005 23:35:23 -0600
On a number of occasions I got the impression the request "NR?" meant "NR ES PREC?"... that the op on the other end was surprised (and disappointed) that I replied with "156" instead of "156 Q". Like
/archives//html/CQ-Contest/2005-11/msg00303.html (9,235 bytes)

14. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: Jim Smith <jimsmith@shaw.ca>
Date: Tue, 08 Nov 2005 02:57:07 -0800
Hi Warren, It's not necessarily a matter of deliberately "not hearing". While I can usually copy contest stuff at a bit over 30 under good conditions, if I'm very tired I can't. The beginning of SS o
/archives//html/CQ-Contest/2005-11/msg00304.html (9,855 bytes)

15. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Date: Tue, 08 Nov 2005 07:27:13 -0500
I got at least one station asking "P ?" I assume this is because Writelog labels the Precedence field as "P" so that's what guys ask for. "PR ?" was much more understandable. 73 - Jim AD1C p.s. no, I
/archives//html/CQ-Contest/2005-11/msg00307.html (9,517 bytes)

16. [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: DL8MBS <prickler.schneider@t-online.de>
Date: Tue, 08 Nov 2005 13:33:00 +0100
de dl8mbs/mostly qrp Hello Hans et al, from my experience qrq isn&acute;t generally better. In the qsb-case qrq is favourable as well as on a not too crowded 80 or 20m-band with a good signal strengt
/archives//html/CQ-Contest/2005-11/msg00309.html (10,237 bytes)

17. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Kyle Chavis" <wa4pgm@kinex.net>
Date: Tue, 8 Nov 2005 07:42:40 -0500
That's the wrong way to look at it Hans, you certainly wouldn't want a station to remove you after being told "R TU". Contesting is about working the strong and weak in the time allowed, it shouldn't
/archives//html/CQ-Contest/2005-11/msg00310.html (10,708 bytes)

18. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Lee Hiers" <aa4ga@contesting.com>
Date: Tue, 08 Nov 2005 08:09:21 -0500
Over the years I've figured out that is often the case, and almost always send the fill as NR & PREC...I've even programmed a message memory that way. 73 de Lee -- Lee Hiers, AA4GA Cornelia, Georgia
/archives//html/CQ-Contest/2005-11/msg00316.html (9,423 bytes)

19. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Joe Brown" <joe.brown@gordmans.com>
Date: Tue, 8 Nov 2005 11:52:36 -0600
Agree with Lee. If you miss the number, there is a good chance you also missed the PREC, and PREC is always the worst thing to ask for a fill on. Half the time the other station thinks you meant CK a
/archives//html/CQ-Contest/2005-11/msg00329.html (9,804 bytes)

20. Re: [CQ-Contest] QRPers --- Please QRQ (score: 1)
Author: "Mario" <s56a@bit.si>
Date: Wed, 9 Nov 2005 01:34:46 +0100
Yes, it is because of all the QRO signals nearby. QRP signal must be above the composite noise. Just preparing second VXO TX and 3L20 for another try on 1988 EU record. I need 600 DX so please liste
/archives//html/CQ-Contest/2005-11/msg00339.html (8,444 bytes)


This search system is powered by Namazu