2015-05-27 23:50:08 +00:00
|
|
|
// Status=review
|
|
|
|
|
[[FIG_CONFIG_RPT]]
|
2015-11-21 02:34:20 +00:00
|
|
|
image::reporting.png[align="center",alt="Reporting Screen"]
|
2015-05-27 23:50:08 +00:00
|
|
|
|
2018-02-12 16:27:15 +00:00
|
|
|
- _Logging_: Choose any desired options from this group. Operators in
|
|
|
|
|
a multi-operator station may wish to enter their home callsign as *Op
|
|
|
|
|
Call*.
|
2015-05-27 23:50:08 +00:00
|
|
|
|
2015-11-11 13:49:20 +00:00
|
|
|
- _Network Services_: Check *Enable PSK Reporter Spotting* to send
|
|
|
|
|
reception reports to the {pskreporter} mapping facility.
|
2015-05-27 23:50:08 +00:00
|
|
|
|
|
|
|
|
- _UDP Server_: This group of options controls the network name or
|
2019-08-06 10:15:45 -04:00
|
|
|
address and port number used to exchange information with a third
|
|
|
|
|
party application that interoperates with _WSJT-X_. Exchanged
|
|
|
|
|
information includes decoded messages, general program status, QSOs
|
|
|
|
|
logged, highlighting of callsigns in the _WSJT-X_ band activity
|
|
|
|
|
window, and limited facilities to initiate QSOs in response to CQ or
|
|
|
|
|
QRZ messages. Full details of the protocol can be found in comments
|
|
|
|
|
at the top of this file in our source code repository:
|
2020-05-10 18:18:44 +01:00
|
|
|
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/Network/NetworkMessage.hpp
|
2018-02-12 16:27:15 +00:00
|
|
|
|
2021-02-10 20:27:10 +00:00
|
|
|
NOTE: The *Outgoing interfaces* and *Multicast TTL* fields are only
|
|
|
|
|
present when a multicast group IP address has been entered in
|
|
|
|
|
the *UDP Server* field.
|
|
|
|
|
|
2019-08-06 10:15:45 -04:00
|
|
|
Programs like _JTAlert_ use the _UDP Server_ feature to obtain
|
2020-05-10 18:18:44 +01:00
|
|
|
information about running _WSJT-X_ instances. If you are using
|
|
|
|
|
_JTAlert_ to control _WSJT-X_, be sure to check the
|
|
|
|
|
*Accept UDP requests* box.
|
