Two new environment variables to control special testing behaviour:
* WSJT_TX_BOTH - set to "1" to force transmission on both periods.
* WSJT_REVERSE_DOPPLER - set to "1" to transpose Tx and Rx Doppler
corrections. Use this to test Doppler tracking on a terrestrial
link.
Two new environment variables to control special testing behaviour:
* WSJT_TX_BOTH - set to "1" to force transmission on both periods.
* WSJT_REVERSE_DOPPLER - set to "1" to transpose Tx and Rx Doppler
corrections. Use this to test Doppler tracking on a terrestrial
link.
The UDP Example reference applications now work correctly with WSJT-X
instances with duplicate --rig-name= command line arguments so long as
duplicate instances are run on unique hosts.
Default selection is the loop-back interface. Users who require
interoperation between WSJT-X instances cooperating applications
running on different hosts should select a suitable network interface
and carefully choose a multicast group address, and TTL, that has
minimal scope covering the necessary network(s). Using 224.0.0.1 is a
reasonable strategy if all hosts are on the same
subnet. Administratively scoped multicast group addresses like those
within 239.255.0.0/16 can cover larger boundaries, but care must be
taken if the local subnet has access to a multicast enabled router.
The IPv4 broadcast address (255.255.255.255) may be used as an
alternative to multicast UDP, but note that WSJT-X will only send
broadcast UDP datagrams on the loop-back interface, so all recipient
applications must be running on the same host system.
The reference UDP Message protocol applications are being extended to
be configurable with a list of interfaces to join a multicast group
address on. By default they will only join on the loop-back interface,
which is also recommended for any applications designed to take part
in the WSJT-X UDP Message Protocol. This allows full user control of
the scope of multicast group membership with a very conservative
default mode that will work with all interoperating applications
running on the same host system.
Use the -X command option to set single decode mode and to set the NB
level.
-X 256*(n+3)+s
Where s=32 selects single decode mode, and 'n' is the equivalent NB
setting as used in the WSJT-X UI. Default for both is zero in FST4(W)
mode if no -X option is passed. E.g. -X 544 selects single decode with
NB=-1 (256*(-1+3)+32).
Use the -X command option to set single decode mode and to set the NB
level.
-X 256*(n+3)+s
Where s=32 selects single decode mode, and 'n' is the equivalent NB
setting as used in the WSJT-X UI. Default for both is zero in FST4(W)
mode if no -X option is passed. E.g. -X 544 selects single decode with
NB=-1 (256*(-1+3)+32).
The sent/received 'mode' parameter posted to WSPRnet.org has been
amended as follows:
WSPR-2: "2"
FST4W-120: "3"
FST4W-300: "5"
FST4W-900: "16"
FST4W-1800: "30"
this change is designed to maintain backwards compatibility with older
versions of WSJT-X and other software like WSPR-X which already post
these values:
WSPR-2: "2"
WSPR-15: "15"
It is expected that the WSPRnet.org server side will be updated in
sync with a WSJT-X v2.3.0 RC2 (or GA) release to account for this
change.
The sent/received 'mode' parameter posted to WSPRnet.org has been
amended as follows:
WSPR-2: "2"
FST4W-120: "3"
FST4W-300: "5"
FST4W-900: "16"
FST4W-1800: "30"
this change is designed to maintain backwards compatibility with older
versions of WSJT-X and other software like WSPR-X which already post
these values:
WSPR-2: "2"
WSPR-15: "15"
It is expected that the WSPRnet.org server side will be updated in
sync with a WSJT-X v2.3.0 RC2 (or GA) release to account for this
change.
