TO7GJ is perfectly acceptable as a standard callsign.
As described in the User Guide, the list of acceptable prefixes and
suffixes applies only to the case of a Type 1 add-on prefix or suffix,
which Lance will not be using.
-- Joe, K1JT
On 3/19/2022 2:29 PM, Lance Collister, W7GJ via wsjt-devel wrote:
Hi Rick,
Yes, I THINK I will be OK using the callsign of TO7GJ for both FT8 and
Q65-60A modes, but it sure will be interesting to hear definitively from
Joe as to whether I will suffer in any way by not having "TO" in the
list of official "Type 1" prefixes.
MNI TNX and VY 73, Lance
On 3/19/2022 18:15:29, K5GZR - Rick wrote:
Lance,
WSJT-X modes with 77-bit message payloads (FST4, FT4, FT8, MSK144, and
Q65) can handle QSOs between a standard and a compound/nonstandard call.
WSJT-X modes with 72-bit message payloads (JT4, JT9, JT65) have a much
more restrictive set of rules. The documentation has separate sections
for those two message payload lengths… I found it easy to get lost in
the discussion of the 72-bit payloads, which apply to modes you might
not be using.
Note that the comment about the table of prefixes and suffixes is
contained in the 72-bit section, not the 77-bit section.
So… I would suggest that if you have a Type 1 callsign and use the
modes with 77-bit message payloads, you should not have a problem
working stations with compound/nonstandard calls as long as they are
using a current version of WSJT-X, or some other software that is
‘compatible’.
As we all understand, the latest version of WSJT-X is compatible with
another copy of the latest version of WSJT-X…. HOWEVER… You, as the
dxpedition station, can’t guarantee compatibility with any other
software… and callers using other software are ‘on their own’.
Kinda ugly when you put it that way, but it is the same as saying ‘Our
SSB QSOs will use English’ and having stations expect you to be able
to understand Farsi, or Swahili, or French (LOL).
The ‘gotcha’ with 77-bit messages and compound/nonstandard callsigns
really only gets involved if the station with the compound/nonstandard
call is calling CQ.
In that case, the CQ message does not include the CQ caller’s grid.
However(!) with 77-bit messages and non-compound/standard callsigns
(like what Joe suggested, and what I think you will be using) CQ is
not a problem
The CQ message for a non-compound/standard callsign DOES include the
CQ caller’s grid.
It will be interesting to see the ‘official’ response from Joe.
73, Rick - K5GZR
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
