Agree on all. When running in a contest I never go more than three
contacts without giving my call, but usually go at least two unless
conditions are dicey and I don't want anyone on the other end to have to
wait through a couple of contacts before deciding whether they want to
work me or not. I don't presume that they are using a spotting cluster.
When just chatting I always try to adhere to the ten minute rule, but I
can't remember the last time I ever heard about the FCC citing anyone
for going longer.
73,
Dave AB7E
On 10/21/2019 1:21 AM, Jim Brown wrote:
On 10/20/2019 2:44 PM, David Gilbert wrote:
As best I know, you don't need to ID every contact, and I suspect you
wouldn't even if moving around within a bandwidth as narrow as is
typical for FT8.
Far too much attention to identification is paid by those who don't
operate much, and/or aren't very good operators. In a typical contest
or DX QSO, one operator IDs when he calls CQ (or finishes a QSO), and
the caller calls by dropping his callsign (thus, an ID). The CQer IDs
with TU callsign or TU and someone else calls his/her. Whether TU or
TU callsign is up to the judgement of the CQing op, which is
appropriate boils down to making a lot of QSOs in a short time,
holding a frequency, and being courteous to potential callers. The FCC
minimum is an ID in 10 minutes of a series of transmssions. Courtesy
of a running station in a contest DEMANDS every 2-3 QSOs.
Too many IDs is slows down communications, and is a real PITA. In a
contest or DX QSO, re-sending your call when the running (DX) station
has it right is a LIDISM. When someone calls me in a contest or as a
DXpedition, all I want is their call, and I never want to hear it (or
mine) unless I've gotten their call WRONG. I know who they are both
from timing and their CW note.
73, Jim K9YC
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
