On 07/06/2016 00:36, Laurie VK3AMA wrote:
I have been working with a user experiencing a failure of WSJT-X to
initiate a CQ response after receiving a UDP Reply Command (4) packet
from JTAlert.
From what I can see, not all CQ decodes are supported by Reply
Command. CQ messages that appear to have been created by using a
free-text message appear to be ignored.
An example of CQ messages that are not working...
* CQ W7BBQ DX
* CQ DEL KW0RH
* CQ K1RI OC AS
Is there a standard CQ message structure that is only supported by the
UDP Reply Command?
HI Laurie,
reply messages are filtered for acceptability but those should all pass.
The requirements are that the message contains the word CQ or the word
QRZ, other than that the other fields of the UDP reply message must
exactly match the original decode message. The only exception is a
trivial edge case where WSJT-X can print -0.0 for the DT, in that case
0.0 is an allowed synonym since the float argument cannot reasonably be
expected to be between -0.05 and zero (that being the reason that WSJT-X
prints -0.0 as the Fortran print routine rounds like that).
I am not in a position to do a test at the moment but when I get a
chance I will try with message_aggregator and see if I can reproduce
this issue.
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
