Hi!
Please consider UDP messages that follow ADIF 3.0.4 tag specification:
RST_RCVD
RST_SENT
These are ok now, just the rst either dB or 5xx format as leagacy rst
UDP string
GridSquare
This is also ok now. If contest message includes locator it should be
sent to companion program using leagacy locator UDP message
SRX
STX
Contest qso number sent and received , *NO other* message data, as new
UDP string
SRX_STRING
STX_STRING
Contest message information sent and received , *NOT including* serial
number or locator, as new UDP string
That way companion program can easily construct it's own database in way
what it wants.
--
Saku
OH1KH
Bill Somerville kirjoitti 3.12.2018 klo 1.37:
On 02/12/2018 21:19, Laurie, VK3AMA wrote:
On 3/12/2018 12:05 am, Bill Somerville wrote:
The WSJT-X UDP protocol logging message will have the contest
exchange fields added for the next release of WSJT-X and cooperating
applications will be able to extract the required information.
Bill,
Good to hear.
Please give some serious consideration to adding additional UDP
status data. Currently, there is no way to know what operating mode
(not TX mode) WSJT-X is currently using, Fox, Hound or which Contest
enabled. It would be very helpful if the UDP protocol provided a
field within the Status packet for these modes of operation.
de Laurie VK3AMA
Hi Laurie,
I am not really certain that knowing which mode WSJT-X is in will
necessarily help a great deal. Part of the point of the new FT8 77-bit
messages is that WSJT-X does not need to know which type it is set to
to decode any message. the messages contain all the information with
exception of the ones with a hash code where some information is
recalled from prior decodes. OTOH it is likely that each mode of
operation will be separated by time or frequency or both so I suppose
there is some value but there is no guarantee that when in one of the
contest modes it will only decode messages deigned for that contest mode.
Anyway, I have made the changes. Here is the diff of the
NetworkMessage.hpp file:
$ git diff wsjtx-2.0.0-rc5 -- NetworkMessage.hpp
diff --git a/NetworkMessage.hpp b/NetworkMessage.hpp
index ffd0ff288..a4d9ba0d5 100644
--- a/NetworkMessage.hpp
+++ b/NetworkMessage.hpp
@@ -124,6 +124,7 @@
* Tx Watchdog bool
* Sub-mode utf8
* Fast mode bool
+ * Special operation mode quint8
*
* WSJT-X sends this status message when various internal state
* changes to allow the server to track the relevant state of each
@@ -142,10 +143,22 @@
* At the start and end of decoding,
* When the Rx DF changes,
* When the Tx DF changes,
- * When the DE call or grid changes (currently when settings are
exited),
+ * When settings are exited,
* When the DX call or grid changes,
* When the Tx watchdog is set or reset.
*
+ * The Special operation mode is an enumeration that indicates the
+ * setting selected in the WSJT-X "Settings->Advanced->Special
+ * operating activity" panel. The values are as follows:
+ *
+ * 0 -> NONE
+ * 1 -> NA VHF
+ * 2 -> EU VHF
+ * 3 -> FIELD DAY
+ * 4 -> RTTY RU
+ * 5 -> FOX
+ * 6 -> HOUND
+ *
*
* Decode Out 2 quint32
* Id (unique key) utf8
@@ -240,6 +253,8 @@
* Operator call utf8
* My call utf8
* My grid utf8
+ * Exchange sent utf8
+ * Exchange received utf8
*
* The QSO logged message is sent to the server(s) when the
* WSJT-X user accepts the "Log QSO" dialog by clicking the "OK"
I will send you a preview Windows installer direct.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
