Yes, that's what is says, and the FCC has continually interpreted
"communication" very broadly. Broadly enough that in the past they have
several times informally said that they weren't going to require it
every contact.
Thousands of contesters have for decades made several contacts between
identifications and the FCC doesn't care in the least.
Dave AB7E
On 10/20/2019 3:06 PM, David Beauchesne wrote:
You do need to ID with every contact. See Part 97.119 (a) “Each
amateur station, except a space station or telecommand station, must
transmit its assigned call sign on its transmitting channel at the end
of each communication…”
AK2L
*From:*David Gilbert <xda...@cis-broadband.com>
*Sent:* Sunday, October 20, 2019 14:44
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] Suggestion: CW ID callsign
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. So why not simply use the freeform 13-character TX5
message to periodically ID? I've played around with it a bit and it
will even accept a few non-alphanumeric symbols like -, ?, and +. It
certainly will accept four character suffixes ... even four characters
after a "/". It shouldn't even matter whether any other amateur
station realizes that it was you who sent it.
I've seen several FT8 stations with long callsigns using TX5 to
periodically identify their grid when it won't fit within the normal
message exchange.
What don't I understand?
73,
Dave AB7E
On 10/20/2019 12:48 PM, David A. Behar wrote:
Hi friends, I am writing to share an idea...
WSJT callsign encoding generally accommodates most amateur radio
callsigns, but some callsigns -- e.g., some special-event
callsigns, and callsigns which might use a _four character
suffix_ as provided at ITU RR19-7 §30
<http://life.itu.int/radioclub/rr/art19.pdf#page=7> -- can't be
accommodated by the coding scheme. There has been plenty of
previous discussion about that, and I think no more is necessary.
WSPR-X provides for the user's specification of a single callsign;
that callsign is used for encoding into messages, and also for use
in optional CW Morse identification.
I think it would be nice if a user could optionally specify a
free-form CW identification callsign which is not subject to the
restrictions of the callsign encoding scheme. This would enable
stations to comply with regulatory station identification
requirements in cases of callsigns which are not accommodated by
the callsign coding scheme.
David/ K7DB
_______________________________________________
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
