CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] [FCG] CQ WW Rules and SCP

To: "Cqtestk4xs@aol.com" <Cqtestk4xs@aol.com>
Subject: Re: [CQ-Contest] [FCG] CQ WW Rules and SCP
From: Maarten van Rossum <pd2r.maarten@gmail.com>
Date: Mon, 17 Jun 2013 20:00:41 +0200
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
No, that is perfectly legit. Your not using external data such as QRZ or a
DX cluster to verify callsigns, your just correcting a typo. Nothing wrong
with that.

As for the zone "problem" regarding U.S. stations Tony is talking about, I
don't see that as a problem at all. Log what you hear not what your logging
software suggests, it's that simple isn't it?

73, Maarten PD2R

Op maandag 17 juni 2013 schreef (Cqtestk4xs@aol.com) het volgende:

> So is going through your log AFTER THE CONTEST, looking for obvious  typos
> like KlABC instead of K1ABC or GOABC instead of G0ABC against the  rules?
>
> K4XS
>
>
> In a message dated 6/17/2013 3:36:01 P.M. Coordinated Universal Time,
> trogo@telegraphy.com <javascript:;> writes:
>
> If CP or  SCP logs the call incorrectly and I want to change it then I
> can't
> unless  I do it at that instant?  It seems a little ridiculous not to be
> able
> to change an
> incorrect exchange later so long as I'm using MY DATA and  correcting data
> that was received from another source.  To correct  based on data received
> from
> another source after the fact should  obviously not be permitted.   Many
> many
> US Stations are in zones  not coincidental with the default zone used in
> logging
> programs and  don't appear in CP and sometimes CP is wrong - people move.
> This is a  problem unique to stations in the USA and only if you're
> operating
> from a  DX location.
>
>
>
> Tony W4OI/HK4AR
> Licenses Previously  Held:
> N7BG, K5LMJ, W7HZF, WA6BOU, W6JPC, K4KES
> F7BK, VQ9AR, VP5AR,  9G5AR, TY5AR, CN2BG
> HK0/HK1AR, 5V7BG, TU/N7BG, OJ0/N7BG
> 5B4/N7BG,  ZC4/N7BG, ZF2AR, HB9/N7BG
> HK1AR and others
> Founding Member of VooDude  Contest Group
> Member of Florida Contest Group
> Member Central Arizona DX  Association since 1977
> Honorary Member Southern California DX Club  1968
> Referee WRTC 2000, 2002, 2006
> I've been to 103 DXCC Countries
> On  the air since 1957
> -----Original Message-----
> From: Tom Schaefer,  NY4I
> Sent: Monday, June 17, 2013 11:26 AM
> To: konecc@snet.net <javascript:;>
> Cc:  Group Group
> Subject: [FCG] CQ WW Rules and SCP
>
> Some might disagree  on this, but the text in the change is as follows:
>
> Correction of LOGGED  call signs by using any database, recordings, email
> or
> other methods of  confirming QSOs after the contest is not allowed. All
> logging must be  performed in real time (emphasis added).
>
> When you are working stations  and make use of SCP, the contact has not
> been
> LOGGED yet. I read the  change to prohibit after the fact changes. As SCP
> is
> used before the  contact is logged, I do not believe they prohibited SCP
> with
> this  change.
>
> Tom NY4I
> ny4i@arrl.net <javascript:;> (Blog: www.ny4i.com)
> Palm Harbor,  FL (Grid:  EL88pb)
>
>
>
>
>
> _______________________________________________
> FCG  mailing list
> Send mail - FCG@kkn.net <javascript:;>
> Change/edit subscription info -  http://www.kkn.net/mailman/listinfo/fcg
> FCG Web site -  www.floridacontestgroup.org
> Facebook -  http://tinyurl.com/4xw5jr7
> DXCluster - telnet to k4fcg.dyndns.org
>
> _______________________________________________
> FCG mailing  list
> Send mail - FCG@kkn.net <javascript:;>
> Change/edit subscription info -  http://www.kkn.net/mailman/listinfo/fcg
> FCG Web site -  www.floridacontestgroup.org
> Facebook -  http://tinyurl.com/4xw5jr7
> DXCluster - telnet to  k4fcg.dyndns.org
>
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com <javascript:;>
> http://lists.contesting.com/mailman/listinfo/cq-contest
>


-- 
73, Maarten PD2R
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

<Prev in Thread] Current Thread [Next in Thread>