Hi Laurie,
See my previous message in this thread, some more comments in line below.
On 08/06/2016 06:41, Laurie, VK3AMA wrote:
What is the position on the following 2 decodes shown in Green in WSJT-X?
>Pass: CQ DX VK3AMA
>Fail: CQ EU VK3AMA
The first responds to the UDP reply command, while the second doesn't
despite it being colored as a CQ (which it is).
The first is a standard form JT65/JT9 message, the second is a free text
message. In the first case WSJT-X will check that he third word is a
valid callsign and respond appropriately. The second message will get
highlighted in the CQ colour but as it is a free text message, it is up
to the user to formulate a suitable reply. This may seem somewhat
ambiguous but WSJT-X does not purport to understand the meaning of
arbitrary free text messages beyond a few basic assumptions like those
that start with CQ or QRZ are general calls or those that contain the
word 73 are sign off messages.
Will WSJT-X be extended to support the non-DX 2 characters? A simple
regex pattern would easily match and 2 alpha characters with a leading
and training space following the CQ.
Maybe, but it is not as simple as you suggest. The proposal was to
overload the meaning of some existing messages to be used as continent
specific CQ calls, this requires that both the message encoder and the
message decoder understand this usage and that all software decoding
messages map the correct result. What you suggest assumes that such
messages are free text messages but that would not work as the 13
character limitation would be impractical for users with long callsigns
and/or those that wish to send grid information in their general calls.
I believe the proposal is to use E9 calls to indicate continent specific
and state specific (or any other two or three alphabetic character
indicator) where "E9AA-E9ZZ ..." and "E9AAA-E9ZZZ ..." would be taken as
"CQ AA-ZZ ..." and "CQ AAA-ZZZ ..." respectively. So the message "CQ EU
VK3AMA QF22" would be encoded as "E9EU VK3AMA QF22". Note that E9 calls
are probably never going to be issued but are valid callsigns as far as
the JT65 and JT9 protocols are concerned so they may be utilized for
this proposal with some certainty that it will not break down in future
when some licensing authority starts issuing unusual callsigns.
Just to complicate things an intermediate proposal to use the callsign
CQ9DX to indicate "CQ DX ..." is understood by WSJT-X at the moment.
I see the second style of decode quite frequently on the Bands where a
Station is doing a Destination Style CQ, whether it is for a specific
Continent or US State.
You will only see such messages when they have been encoded as free text
messages by those with callsigns short enough to fit the message into 13
characters. You may also see messages like "CQ 000 VK3AMA QF22" which
are meant to be interpreted as "CQ DX VK3AMA QF22" and messages like
"E9MT VK3AMA QF22" which is intended to be decoded as "CQ MT VK3AMA QF22".
As you may gather this is all a bit of a mess. The E9 calls proposal is
by far the best and most flexible option IMHO and I believe Joe K1JT
favours that too as it has the minimum impact for the gain available.
All we need is time to get it done in a coordinated fashion across the
board.
73
Bill
G4WJS.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
