Hi all,
FYI, I'm forwarding the message sent to the "Moon-Net" email list a few
minutes ago.
-- Joe, K1JT
-------- Original Message --------
Subject: [Moon-Net] HK0 as an add-on prefix
Date: Wed, 11 Nov 2015 16:21:11 -0500
From: Joe Taylor <[email protected]>
To: <[email protected]>
Dear EME Friends,
The DXpedition of Hermann (DL2NUD) and Joe (DL9MS) to San Andreas has
brought to light a flaw in the way a few add-on prefixes have been
encoded and decoded in WSJT and MAP65.
Until now the prefixes for DXCC entities San Andres & Providenci (HK0A)
and Malpelo Island (HK0M) have been encoded as distinct table entries. I
had thought this was the correct approach. It has been used in all
WSJT-related software for more than a decade, with no complaints. I
don't recall the exact details of my original research into the matter;
probably I took my cues from something like the list of prefixes posted
here: http://www.turkkonferans.org/amradprefixes.pdf. I did explicitly
asking for public input on the posted list of prefixes, but there was no
response.
The self-appointed QSO-validity police on Moon-Net have very kindly
pointed out that the assigned callsign for Hermann and Joe's DXpedition
is HK0/DL2NUD, not HK0A/DL2NUD.
Therefore, to avoid possible problems in making JT65 QSOs from San
Andreas, I have posted new versions of WSJT (version 10.0, r6074) and
MAP65 (version 2.5, r6077) on the WSJT home page:
http://physics.princeton.edu/pulsar/K1JT/index.html
The updated software will correctly handle messages using the compound
callsign HK0/DL2NUD.
With the new program versions you should operate as with any other
supported prefix: Hermann and Joe should enter HK0/DL2NUD as "My Call",
and other stations should enter HK0/DL2NUD as "To Radio" or "DX Call".
If Hermann and Joe do not have time to update their software, they
should enter HK0A/DL2NUD as "My Call"; it will be transmitted correctly
as HK0/DL2NUD, however. They would see messages from others displayed
as "HK0A/DL2NUD xxxxxx". They will know that the actual transmitted
message was "HK0/DL2NUD xxxxxx", and that the extra "A" is an artifact
of the software flaw.
Other operators using the old software will see messages containing
HK0/DL2NUD displayed as HK0A/DL2NUD. These operators, too, should
ignore the extra "A", knowing that it is merely an artifact of the
software flaw.
All those who upgrade their software will see the correct callsign,
HK0/DL2NUD.
QSOs made as described here with all software versions will be perfectly
valid.
Please note that there has been a large quantity of misinformation,
disinformation, and other low-SNR chatter posted on Moon-Net about this
question. Most of it should be ignored.
You might be interested to know that WSJT, MAP65, WSPR, and WSJT-X are
in regular use by more than 7000 hams around the world. Probably about
25% of these users are active on EME, meteor scatter, or other pursuits
at VHF and higher frequencies.
I hope all of you will remember that WSJT and its sister and derivative
programs are an all-volunteer effort. Members of the very active WSJT
development group have put thousands of hours into making these programs
useful to the ham radio community and enjoyable for so many to use.
-- 73, Joe, K1JT
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
