Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Dupes\s+how\s+to\s+handle\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Dupes\s+how\s+to\s+handle\s*$/: 48 ]

Total 48 documents matching your query.

1. [RTTY] Dupes how to handle (score: 1): Author: trevor dunne <trevor_dunne@yahoo.com>; Date: Sun, 12 Feb 2012 16:02:13 +0000 (GMT); Whats the correct procedure to handle dupe in any contest but mainly WPX RTTY I have a few QSO's that I thought were good but the other station called me again and when I said QSO B4, I wasn't in the; /archives//html/RTTY/2012-02/msg00127.html (7,657 bytes)
2. Re: [RTTY] Dupes how to handle (score: 1): Author: David Levine <david@levinecentral.com>; Date: Sun, 12 Feb 2012 11:28:59 -0500; Just log them and move on to the next contact. Whatever serial you have and the one you received from the other station is what you need to log. Don't delete anything and don't worry about the # beyo; /archives//html/RTTY/2012-02/msg00128.html (8,441 bytes)
3. Re: [RTTY] Dupes how to handle (score: 1): Author: Robert Chudek - K0RC <k0rc@citlink.net>; Date: Sun, 12 Feb 2012 10:29:52 -0600; Hello Trevor... Here's the guidelines to follow: Never delete any QSO from your log. If a station calls you a second time, rework him. You might miscopied someone elses call sign. It's faster to rewo; /archives//html/RTTY/2012-02/msg00129.html (8,313 bytes)
4. Re: [RTTY] Dupes how to handle (score: 1): Author: "Ed Muns" <ed@w0yk.com>; Date: Sun, 12 Feb 2012 17:36:58 -0400; Please, PLEASE, do not ever remove any QSOs from your log! Especially dupes are no consequence in the log. It is all sorted out in log checking. If you remove a QSO that is in another log, then that; /archives//html/RTTY/2012-02/msg00130.html (8,427 bytes)
5. Re: [RTTY] Dupes how to handle (score: 1): Author: trevor dunne <trevor_dunne@yahoo.com>; Date: Mon, 13 Feb 2012 00:13:32 +0000 (GMT); Thanks for all the replies, I guess I should have asked before the contest but I don't think I had that many logging problems ( I hope) Thanks Trevor EI2GLB ________________________________ From: E; /archives//html/RTTY/2012-02/msg00131.html (9,641 bytes)
6. Re: [RTTY] Dupes how to handle (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Sun, 12 Feb 2012 22:27:18 -0800; ORIGINAL MESSAGE: REPLY: When a dupe calls you, the best approach is to completely ignore the fact he is a dupe and work him normally. Don't delete the previous QSO, don't try to alter serial numbers; /archives//html/RTTY/2012-02/msg00144.html (8,521 bytes)
7. Re: [RTTY] Dupes how to handle (score: 1): Author: "James C. Hall, MD" <heartdoc@nwtcc.com>; Date: Mon, 13 Feb 2012 14:58:33 -0600; This is really hard to take sometimes. I had a dupe rate of 1.7% - in this day and age of computer logging, this seems WAY too high. There was one K4 who was about to get on my last nerve who was a d; /archives//html/RTTY/2012-02/msg00155.html (10,311 bytes)
8. Re: [RTTY] Dupes how to handle (score: 1): Author: "Gary AL9A" <al9a@mtaonline.net>; Date: Mon, 13 Feb 2012 12:16:08 -0900; I had one fellow work me and give me his number 2. Within fifteen minutes he was back and called multiple times. Despite my telling him he was a DUPE he persisted in calling over and over. Out of fru; /archives//html/RTTY/2012-02/msg00156.html (9,419 bytes)
9. Re: [RTTY] Dupes how to handle (score: 1): Author: "K3RWN" <rwnewbould@comcast.net>; Date: Mon, 13 Feb 2012 16:26:06 -0500; I agree just work the dupes again. Something may have been wrong with the copy on either end the first time and if not it is quicker to just work them. I had a dupe during the first 6 Qs of the test; /archives//html/RTTY/2012-02/msg00157.html (8,036 bytes)
10. Re: [RTTY] Dupes how to handle (score: 1): Author: Jeff Stai <wk6i.jeff@gmail.com>; Date: Mon, 13 Feb 2012 13:31:51 -0800; I had a large number of dupes this time. It finally sank in that I was using a call for WPX that had never been used in a RTTY contest. Being an unfamiliar call I suspect it was getting miscopied. Th; /archives//html/RTTY/2012-02/msg00158.html (12,171 bytes)
11. Re: [RTTY] Dupes how to handle (score: 1): Author: "Alejandro V. XE1EE" <xe1ee@telmexmail.com>; Date: Mon, 13 Feb 2012 16:33:42 -0600; Hello Trevor Well, I have a macro who checks the call against the current contest log, if it is a dupe sends Call QSO B4 XE1EE QRZ, if not just sends the serial number and I keep going, I never work; /archives//html/RTTY/2012-02/msg00160.html (9,950 bytes)
12. Re: [RTTY] Dupes how to handle (score: 1): Author: Robert Chudek - K0RC <k0rc@citlink.net>; Date: Mon, 13 Feb 2012 17:01:28 -0600; "I never work dupes." What is your logic behind this? What happens if the fellow who calls you the second time lost his log from the first day? You will get a NIL and penalty when log checking is don; /archives//html/RTTY/2012-02/msg00161.html (12,269 bytes)
13. Re: [RTTY] Dupes how to handle (score: 1): Author: trevor dunne <trevor_dunne@yahoo.com>; Date: Mon, 13 Feb 2012 23:08:08 +0000 (GMT); Sorry I missed you Alejandro, I had some very big pile ups on 15m, It made me feel like a DX station at times. I struggle to get a decode when there is lots of stations calling, I guess everyone does; /archives//html/RTTY/2012-02/msg00162.html (12,151 bytes)
14. Re: [RTTY] Dupes how to handle (score: 1): Author: "Alejandro V. XE1EE" <xe1ee@telmexmail.com>; Date: Mon, 13 Feb 2012 17:23:19 -0600; Well, my logic is to avoid dupes on my log, however it's a good point what you state about the guy loosing his log. So you think is better to work dupes instead of ignore them?.. will the penalties w; /archives//html/RTTY/2012-02/msg00163.html (14,205 bytes)
15. Re: [RTTY] Dupes how to handle (score: 1): Author: "Alejandro V. XE1EE" <xe1ee@telmexmail.com>; Date: Mon, 13 Feb 2012 17:29:37 -0600; Yes i saw your pileup and it was huge, there was another EI station calling also and don't know why he had less clients. FSK is better than AFSK, still you can use autotune function of you're running; /archives//html/RTTY/2012-02/msg00164.html (14,534 bytes)
16. Re: [RTTY] Dupes how to handle (score: 1): Author: "James C. Hall, MD" <heartdoc@nwtcc.com>; Date: Mon, 13 Feb 2012 17:33:28 -0600; Alejandro: I had 31 in my log !! I don't think you'll have a problem. :) BTW, thanks for the Q's. 73, Jamie WB4YDL Well, my logic is to avoid dupes on my log, however it's a good point what you state; /archives//html/RTTY/2012-02/msg00165.html (15,091 bytes)
17. Re: [RTTY] Dupes how to handle (score: 1): Author: "Larry" <lknain@nc.rr.com>; Date: Mon, 13 Feb 2012 18:37:11 -0500; Some of this duplicate QSO stuff is not limited to contests. I heard several occasions during the recent HK0NA expedition, for example, where the same stations were worked more than three times in le; /archives//html/RTTY/2012-02/msg00166.html (12,189 bytes)
18. Re: [RTTY] Dupes how to handle (score: 1): Author: trevor dunne <trevor_dunne@yahoo.com>; Date: Mon, 13 Feb 2012 23:43:22 +0000 (GMT); I will have a look at Writelog, I use Ham radio deluxe for my day to day logging but that soon is to be a commerical sw at a cost so I want to try the other options available to me. I used to use l; /archives//html/RTTY/2012-02/msg00167.html (15,775 bytes)
19. Re: [RTTY] Dupes how to handle (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Mon, 13 Feb 2012 15:53:20 -0800; ORIGINAL MESSAGE: REPLY: For what it's worth - when I call someone and I see he is stacking the calls, I'm gone. I do not want to wait in line. I figure anyone who stacks calls is a serious contester; /archives//html/RTTY/2012-02/msg00169.html (8,656 bytes)
20. Re: [RTTY] Dupes how to handle (score: 1): Author: Bill Turner <dezrat1242@yahoo.com>; Date: Mon, 13 Feb 2012 16:00:31 -0800; ORIGINAL MESSAGE: REPLY: This is usually caused by the misuse of AFC by the calling station. The calling station has AFC on while tuning across the band and when he comes close to you, the AFC reache; /archives//html/RTTY/2012-02/msg00170.html (8,996 bytes)

Current List: 1 - 20
Page: [1] [2] [3]