On 08/06/2016 02:36, Laurie, VK3AMA wrote:
I will be changing JTAlert to no longer display certain decodes,
specifically the QRZ style decodes, in Greenthat WSJT-X itself doesn't
highlight in green. This will help avoid the frequent reports I get of
WSJT-X not responding to a double-click in JTAlert.
Hi Laurie,
QRZ messages are one of the standard message forms and should be treated
as general calls. I am currently testing a change to WSJT-X to highlight
all QRZ messages in the CQ colour. Note that QRZ messages that are not
in the standard message form will be shown in the CQ colour but still
not be "double click-able", the reason for this is that WSJT-X expects
to find the callers callsign as the second word of the message and if
that second word is not a valid callsign then WSJT-X will not respond to
a double click. So the following forms will all be highlighted in the CQ
colour:
A message starting with the word "QRZ".
The following are not double click-able:
QRZ DX ...
QRZ EU ...
QRZ AS ...
and similar constructs.
Note that WSJT-X already responds to double clicks of correctly
formatted QRZ messages. I suggest that you should not filter double
click requests but if WSJT-X does not respond to a UDP reply request
then instead ask JTAlert users to try double clicking the same decode in
WSJT-X. If they feel that WSJT-X should have responded then an issue
report should be raised on WSJT-X.
Some background information:-
The only standard general call forms where the second word of the
message is *not* taken as the callers callsign are:
CQ DX <basic-callsign> [<grid>]
CQ DX <type-1-compond-callsign>
CQ NNN <basic-callsign> [<grid>]
CQ NNN <type-1-compound-callsign>
CQ NNN <type-2-compound-callsign> [<grid>]
where [...] is an optional part and NNN is a three digit number
(including leading zeros which are required) indicating a listen for
reply frequency. The NNN form is only relevant to VHF and up operating
where it is sometimes common to call on a well known calling frequency
but to carry out the QSO on another frequency.
The standard form QRZ messages are:
QRZ <basic-callsign> [<grid>}
QRZ <type-1-compound-callsign>
QRZ <type-2-compound-callsign> [<grid>]
There are another set of standard messages similar to the above but they
are not considered as general calls i.e. not highlighted:
DE <basic-callsign>
DE <type-1-compound-callsign>
DE <type-2-compound-callsign> [<grid>]
It has been proposed that the NNN style CQ messages may be used on HF to
encode continent specific general calls and indeed Beat HB9HQX has
unilaterally implemented a decoder change to map five specific NNN
values to "CQ NA", "CQ SA", "CQ EU", "CQ AS", and "CQ OC" (I am not sure
if there is a "CQ AN"). While this may be popular and a good idea, he
did not heed Joe's request to coordinate such a change in message
interpretation with other decoders.
Anyone may explore the the standard message forms by using the jt65code
or jt9code utilities which are shipped with WSJT-X. they are documented
in the WSJT-X User Guide -
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.6.0.html#UTIL
.
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
