Updated to r8541

doc/user_guide/en/controls-functions-center.adoc

@@ -56,7 +56,8 @@ and reception in ISCAT, MSK144, and the fast JT9 modes.
 MSK144 and the fast JT9 submodes you can activate the spinner control
 *Tx CQ nnn* by checking the box to its right.  The program will then
 generate something like `CQ nnn K1ABC FN42` for your CQ message, where
-`nnn` is the kHz portion of your current operating frequency.  Your CQ
+`nnn` is the kHz portion of your current operating frequency,
+in the range 010 to 999.  Your CQ
 message *Tx6* will then be transmitted at the calling frequency
 selected in the *Tx CQ nnn* spinner control.  All other messages will
 be transmitted at your current operating frequency.  On reception,
@@ -67,7 +68,7 @@ specified response frequency.
 * Checkboxes at bottom center of the main window control special
 features for particular operating modes:
 
-** *Sh* enables shorthand messages in JT4, JT65, and MSK144 modes
+** *Sh* enables shorthand messages in JT4, JT65, QRA64 and MSK144 modes
 
 ** *Fast* enables fast JT9 submodes
 

doc/user_guide/en/controls-functions-main-window.adoc

@@ -1,9 +1,12 @@
 // Status=review
-The following buttons appear just under the decoded text windows on
+The following controls appear just under the decoded text windows on
 the main screen:
 
 //.Main UI 
-image::main-ui-controls.png[align="left",width=650,alt="Main UI Controls"]
+image::main-ui-controls.png[align="center",width=650,alt="Main UI Controls"]
+
+* When *CQ only* is checked, only messages from stations calling CQ will
+be displayed in the left text panel.
 
 * *Log QSO* raises a dialog window pre-filled with known information
 about a QSO you have nearly completed.  You can edit or add to this
@@ -62,3 +65,5 @@ Toggle the button a second time or click *Halt Tx* to terminate the
 *Tune* process.  Note that activating *Tune* interrupts a receive
 sequence and will prevent decoding during that sequence.
 
+* Uncheck the box *Menus* to make the top-of-window menus disappear,
+leaving more vertical space for decoded messages.

doc/user_guide/en/decoder_notes.adoc

@@ -1,9 +1,10 @@
 === AP Decoding
 
-The _WSJT-X_ decoders for QRA64 and FT8 include optional procedures
-that use naturally accumulating information during a minimal QSO.
-This _a priori_ (AP) information increases sensitivity of the decoder
-by up to 4 dB, at the cost of a slightly higher rate of false decodes.
+The _WSJT-X_ decoders for JT65, QRA64, and FT8 include optional
+procedures that use naturally accumulating information during a
+minimal QSO.  This _a priori_ (AP) information increases sensitivity
+of the decoder by up to 4 dB, at the cost of a slightly higher rate of
+false decodes.
 
 For example: when you decide to answer a CQ, you already know your own
 callsign and that of your potential QSO partner.  The software

doc/user_guide/en/faq.adoc

@@ -1,6 +1,6 @@
 ////
 Questions:
- Should be short one liners ending with ?::
+ Should be short one liners (in the .adoc file) ending with ?::
  If your question is too long for one line, consider multiple questions or rephrase
 
 Answers:
@@ -47,11 +47,11 @@ location for each instance of _WSJT-X_.
  wsjtx --rig-name=TS2000
  wsjtx --rig-name=FT847
 
-When setting up rig control through _OmniRig_, something goes wrong when I click *Test CAT*.  What can I do about it?::
+Rig control through _OmniRig_ seems to fail when I click *Test CAT*.  What can I do about it?::
 
-_OmniRig_ apparently has a bug that appears when you click *Test CAT*.
-Forget using *Test CAT* and just click *OK*.  _OmniRig_ then behaves
-normally.
+_Omni-Rig_ apparently has a bug that appears when you click *Test
+CAT*.  Forget using *Test CAT* and just click *OK*.  _Omni-Rig_ then
+behaves normally.
 
 I am using _WSJT-X_ with _Ham Radio Deluxe_.  All seems well until I start HRD Logbook or DM780 running in parallel; then CAT control becomes unreliable.::
 

doc/user_guide/en/install-mac.adoc

@@ -1,4 +1,4 @@
-// These instructions are up-to-date for WSJT-X v1.8
+// These instructions are up-to-date for WSJT-X v1.9
 
 *OS X 10.9* and later: Download the file {osx} to your desktop,
 double-click on it and consult its `ReadMe` file for important
@@ -6,13 +6,18 @@ installation notes.
 
 If you have already installed a previous version, you can retain it by
 changing its name in the *Applications* folder (say, from _WSJT-X_ to
-_WSJT-X_1.7_).  You can then proceed to the installation phase.
+_WSJT-X_1.8_).  You can then proceed to the installation phase.
 
 Take note also of the following:
 
 * Use the Mac's *Audio MIDI Setup* utility to configure your sound
 card for 48000 Hz, two-channel, 16-bit format.
 
+NOTE: If you are using macOS with an external audio device and find
+that Tx audio spontaneously switches to the motherboard sound device
+after a few transmissions, try setting the sample rate to 44100 Hz
+rather than the otherwise recommended 48000 Hz.
+
 * Use *System Preferences* to select an external time source to keep
 your system clock synchronized to UTC.
 

doc/user_guide/en/introduction.adoc

@@ -7,7 +7,7 @@ K1**JT**,`" while the suffix "`-X`" indicates that _WSJT-X_ started as
 an extended and experimental branch of the program
 _WSJT_.
 
-_WSJT-X_ Version 1.8 offers nine different protocols or modes: *FT8*,
+_WSJT-X_ Version 1.9 offers nine different protocols or modes: *FT8*,
 *JT4*, *JT9*, *JT65*, *QRA64*, *ISCAT*, *MSK144*, *WSPR*, and *Echo*.
 The first five are designed for making reliable QSOs under extreme
 weak-signal conditions. They use nearly identical message structure
@@ -62,3 +62,13 @@ tracking for EME QSOs and Echo testing.  The program runs equally well
 on Windows, Macintosh, and Linux systems, and installation packages
 are available for all three platforms.
 
+*Version Numbers:* _WSJT-X_ release numbers have major, minor, and
+patch numbers separated by periods: for example, _WSJT-X_ Version
+1.9.0.  Temporary "`beta`" release candidates are sometimes made in
+advance of a new general-availability release, in order to obtain user
+feedback.  For example, version 1.9.0-rc1, 1.9.0-rc2, etc., would
+be beta releases leading up to the final release of v1.9.0.
+Release candidates should be used _only_ during a short testing
+period. They carry an implied obligation to provide feedback to the
+program development group.  Candidate releases should not be used on
+the air after a full release with the same number has been made.

doc/user_guide/en/make-qso.adoc

@@ -41,7 +41,7 @@ are desirable.  Double-click the *Tx1* control under _Now_ or _Next_
 to toggle use of the Tx2 message rather than Tx1 to start a QSO.
 Similarly, double-click the *Tx4* control to toggle between sending
 `RRR` and `RR73` in that message.  The `RR73` message should be used
-only if you are reasonably confident that no repititions will be
+only if you are reasonably confident that no repetitions will be
 required.
 
 === Free-Text Messages
@@ -57,12 +57,14 @@ or rag-chewing.
 
 === Auto-Sequencing
 
-The slow modes JT4, JT9, JT65, and QRA64 allow nearly 10 seconds at
-the end of each one-minute receiving sequence -- enough time for you
-to inspect decoded messages and decide how to reply.  The 15-second
-T/R cycles of FT8 allow only about two seconds for this task, which is
-often not enough.  For this reason a basic auto-sequencing feature is
-offered. Check *Auto Seq* on the main window to enable this feature:
+The 15-second T/R cycles of FT8 allow only about two seconds to inspect 
+decoded messages and decide how to reply, which is often not enough.
+The slow modes JT4, JT9, JT65, and QRA64 allow nearly 10 seconds
+for this task, but operators may find that this is still insufficient
+when workload is high, especially on EME. For these  reasons a basic
+auto-sequencing feature is offered.
+
+Check *Auto Seq* on the main window to enable this feature:
 
 image::auto-seq.png[align="center",alt="AutoSeq"]
 

doc/user_guide/en/new_features.adoc

@@ -1,31 +1,32 @@
-=== New in Version 1.8
+=== New in Version 1.9
 
 For quick reference, here's a short list of features and capabilities
-added to _WSJT-X_ since Version 1.7.0:
+added to _WSJT-X_ since Version 1.8.0:
 
-- New mode *FT8* designed for fast QSOs
+- New *FT8 DXpedition Mode* to facilitate high QSO rates in pileup
+situations
 
-- New tool *FreqCal* for accurate frequency calibration of your radio
+- Decoding improvements for JT65 mode, including _a priori_ (AP)
+decoding when VHF/UHF/Microwave features are enabled
 
-- Improved decoding performance for JT65, QRA64, and MSK144
+- Optional Auto-Sequencing in JT4, JT9, and JT65 when VHF/UHF/Microwave features are enabled
 
-- *SWL* option for third-party decoding short-format MSK144 messages
+- Better suppression of low-confidence false decodes generated by AP
+decoding in FT8 mode
 
-- Experimental phase equalization for MSK144
-    
-- Options to minimize screen space used by *Main* and *Wide Graph*
-windows
-    
-- New set of suggested default frequencies specific to the three IARU
-regions
+- Improved decoding performance for WSPR mode, especially effective at LF and MF
 
-- Enhanced scheme for managing table of suggested default operating
-frequencies
+- Minor adjustments to auto-sequencing behavior
 
-- Improved CAT control for many radios, including those controlled
-through Commander or OmniRig
+- More flexible Doppler control features for EME
 
-- Bug fixes and minor tweaks to user interface
+- Improved waterfall sensitivity for very weak signals
+
+- Automatic real-time forwarding of logged information to _N1MM Logger+_
+
+- Expanded and improved UDP messages sent to companion programs
+
+- Bug fixes and other minor tweaks to user interface
 
 === Documentation Conventions
 

doc/user_guide/en/protocols.adoc

@@ -9,9 +9,11 @@ additional bit flags a message containing arbitrary alphanumeric text,
 up to 13 characters.  Special cases allow other information such as
 add-on callsign prefixes (e.g., ZA/K1ABC) or suffixes (e.g., K1ABC/P)
 to be encoded. The basic aim is to compress the most common messages
-used for minimally valid QSOs into a fixed 72-bit length.  Information
-payloads in FT8 include 3 additional bits (75 bits total), with
-definitions yet to be defined.
+used for minimally valid QSOs into a fixed 72-bit length.  The
+information payload in FT8 includes 3 additional bits (75 bits total).
+One of the added bits is used to flag special messages used by the
+DXpedition station in FT8 DXpedition Mode.  Uses for the remaining two
+bits are yet to be defined.
 
 A standard amateur callsign consists of a one- or two-character
 prefix, at least one of which must be a letter, followed by a digit
@@ -166,6 +168,51 @@ QRA64 presently offers no message averaging capability, though that
 feature may be added.  In early tests, many EME QSOs were made using
 submodes QRA64A-E on bands from 144 MHz to 24 GHz.  
 
+[[WSPR_PROTOCOL]]
+==== WSPR
+
+WSPR is designed for probing potential radio propagation paths using
+low power beacon-like transmissions. WSPR signals convey a callsign,
+Maidenhead grid locator, and power level using a compressed data
+format with strong forward error correction and narrow-band 4-FSK
+modulation. The protocol is effective at signal-to-noise ratios as low
+as –31 dB in a 2500 Hz bandwidth.
+
+WSPR messages can have one of three possible formats illustrated by
+the following examples:
+
+ - Type 1: K1ABC FN42 37
+ - Type 2: PJ4/K1ABC 37
+ - Type 3: <PJ4/K1ABC> FK52UD 37
+ 
+Type 1 messages contain a standard callsign, a 4-character Maidenhead
+grid locator, and power level in dBm. Type 2 messages omit the grid
+locator but include a compound callsign, while type 3 messages replace
+the callsign with a 15-bit hash code and include a 6-character locator
+as well as the power level. Lossless compression techniques squeeze
+all three message types into exactly 50 bits of user
+information. Standard callsigns require 28 bits and 4-character grid
+locators 15 bits.  In Type 1 messages, the remaining 7 bits convey the
+power level. In message types 2 and 3 these 7 bits convey power level
+along with an extension or re-definition of fields normally used for
+callsign and locator. Together, these compression techniques amount to
+“source encoding” the user message into the smallest possible number
+of bits.
+
+WSPR uses a convolutional code with constraint length K=32 and rate
+r=1/2. Convolution extends the 50 user bits into a total of (50 + K –
+1) × 2 = 162 one-bit symbols. Interleaving is applied to scramble the
+order of these symbols, thereby minimizing the effect of short bursts
+of errors in reception that might be caused by fading or interference.
+The data symbols are combined with an equal number of synchronizing
+symbols, a pseudo-random pattern of 0’s and 1’s.  The 2-bit
+combination for each symbol is the quantity that determines which of
+four possible tones to transmit in any particular symbol
+interval. Data information is taken as the most significant bit, sync
+information the least significant. Thus, on a 0 – 3 scale, the tone
+for a given symbol is twice the value (0 or 1) of the data bit, plus
+the sync bit.
+
 [[SLOW_SUMMARY]]
 ==== Summary
 

doc/user_guide/en/settings-advanced.adoc

@@ -31,12 +31,14 @@ IMPORTANT: For the health of your T/R relays and external
 preamplifier, we strongly recommend using a hardware sequencer and
 testing to make sure that sequencing is correct.
 
-- Check *FT8 and MSK144: NA VHF Contest Mode* to enable generation and
-auto-sequencing of messages using four-character grid locators in
-place of signal reports, as required for most North American VHF
-contests.
+- Check *x 2 Tone spacing* or *x 4 Tone spacing* to generate Tx audio
+with twice or four times the normal tone spacing.  This feature is
+intended for use with specialized LF/MF transmitters that divide
+generated frequencies by 2 or 4 as part of the transmission process.
+
+_FT8 DXpedition Mode_
+
+- Check *Fox* if you are a DXpedition station operating in FT8
+DXpedition Mode.  Check *Hound* if you wish to make QSOs with such a
+Fox.  Be sure to read the operating instructions for  {ft8_DXped}.
 
-- Check *x 2 Tone spacing* to generate Tx audio with twice the normal
-tone spacing.  This feature is intended for use with specialized LF/MF
-transmitters that divide the audio waveform by 2 before further
-processing.

doc/user_guide/en/settings-radio.adoc

@@ -11,7 +11,7 @@ your radio, select the *Radio* tab.
 
 - Alternatively, if you have configured your station for control by
 *DX Lab Suite Commander*, *Ham Radio Deluxe*, *Hamlib NET rigctl*, or
-*OmniRig*, you may select one of those program names from the *Rig*
+*Omni-Rig*, you may select one of those program names from the *Rig*
 list.  In these cases the entry field immediately under _CAT Control_
 will be relabeled as *Network Server*.  Leave this field blank to
 access the default instance of your control program, running on the
@@ -19,9 +19,9 @@ same computer. If the control program runs on a different computer
 and/or port, specify it here.  Hover the mouse pointer over the entry
 field to see the required formatting details.
 
-- Select *OmniRig Rig 1* or *OmniRig Rig 2* to connect to an _OmniRig_
-server running on the same computer.  Note that _OmniRig_ is available
-only under Windows.
+- Select *Omni-Rig Rig 1* or *Omni-Rig Rig 2* to connect to an
+_Omni-Rig_ server running on the same computer.  Note that _Omni-Rig_
+is available only under Windows.
 
 - Set *Poll Interval* to the desired interval for _WSJT-X_ to query
 your radio.  For most radios a small number (say, 1 – 3 s) is

doc/user_guide/en/settings-reporting.adoc

@@ -2,7 +2,9 @@
 [[FIG_CONFIG_RPT]]
 image::reporting.png[align="center",alt="Reporting Screen"]
 
-- _Logging_: Choose any desired options from this group.
+- _Logging_: Choose any desired options from this group.  Operators in
+a multi-operator station may wish to enter their home callsign as *Op
+Call*.
 
 - _Network Services_: Check *Enable PSK Reporter Spotting* to send
 reception reports to the {pskreporter} mapping facility.
@@ -13,3 +15,7 @@ updates from _WSJT-X_.  Cooperating applications like _JTAlert_ use
 this feature to obtain information about a running _WSJT-X_ instance.
 If you are using _JTAlert_, be sure to check the three boxes at lower
 right.
+
+- _N1MM Logger+ Broadcasts_: To send information on logged QSOs
+directly to _N1MM Logger+_, check the box and enter the IP address and
+port number for _N1MM_.

doc/user_guide/en/tutorial-example1.adoc

@@ -40,8 +40,8 @@ try clicking with the mouse on the decoded text lines and on the
 waterfall spectral display. You should be able to confirm the
 following behavior:
 
-- Double-click on either of the decoded lines highlighted in
-green. This action produces the following results:
+- Click or double-click on either of the decoded lines highlighted in
+green. These actions produce the following results:
 
 ** Callsign and locator of a station calling CQ are copied to the *DX
 Call* and *DX Grid* entry fields.
@@ -57,14 +57,16 @@ station.
 ** The *Gen Msg* ("`generated message`") radio button at bottom right 
 of the main window is selected.
 
-** If you had checked *Double-click on call sets Tx Enable* on the
-*Setup* menu, *Enable Tx* would be activated and a transmission would
-start automatically at the proper time.
+** *Double-click* does all of the above and also activates *Enable Tx*
+so that a transmission will start automatically at the proper time.
 
 ** You can modify the double-click behavior by holding down the
 *Shift* key to move only the Tx frequency or the *Ctrl* key to move
 both Rx and Tx frequencies.
 
+NOTE: You can prevent your Tx frequency from being changed by checking the
+box *Hold Tx Freq*.
+
 - Double-click on the decoded message `K1JT N5KDV EM41`, highlighted
 in red.  Results will be similar to those in the previous step. The Tx
 frequency (red marker) is not moved unless *Shift* or *Ctrl* is held
@@ -72,13 +74,6 @@ down.  Messages highlighted in red are usually in response to your own
 CQ or from a tail-ender, and you probably want your Tx frequency to
 stay where it was.
 
-NOTE: Double-clicking on decoded messages can be defaulted to simplex
-operation by checking *Double click on call sets Tx and Rx freqs* on
-the *Settings -> General* tab.
-
-NOTE: You can prevent your Tx frequency from being changed by checking the
-box *Lock Tx Freq*.
-
 - Click somewhere on the waterfall to set Rx frequency (green marker
 on waterfall scale).
 

doc/user_guide/en/tutorial-example3.adoc

@@ -45,16 +45,28 @@ when double-clicking.
 
 NOTE: To avoid QRM from competing callers, it is frequently desirable
 to answer a CQ on a different frequency from that of the CQing
-station.  Choose a Tx frequency that appears to be not in use.  The
-same is true when you tail-end another QSO.
+station.  The same is true when you tail-end another QSO.  Choose a Tx
+frequency that appears to be not in use.
 
-NOTE: The FT8 decoder can often copy several overlapping signals at
-nearly the same frequency.  Keyboard shortcuts *Shift+F11* and
-*Shift+F12* provide an easy way to move your Tx frequency down or up
-in 60 Hz steps.
+NOTE: Keyboard shortcuts *Shift+F11* and *Shift+F12* provide an easy
+way to move your Tx frequency down or up in 60 Hz steps.
 
 NOTE: Further helpful tips on FT8 operating procedures are available
 {ft8_tips}.  Thanks to ZL2IFB!
 
+.FT8 DXpedition Mode:
+
+- This special operating mode enables DXpeditions to make FT8 QSOs at
+very high rates.  Both stations must use _WSJT-X_ Version 1.9 or
+later.  Detailed operating instructions for {ft8_DXped} are available
+online.  Do not try to use DXpedition mode without reading these
+instructions carefully!
+
+IMPORTANT: FT8 DXpedition mode is suitable for use only by legitimate
+DXpeditions and those attempting to work them. Do not try to use
+DXpedition mode for normal FT8 operation.  Do not use it in the
+conventional FT8 subbands.  And especially, do not use the
+multi-signal capability unless you are a DXpedition.
+
 IMPORTANT: When finished with this Tutorial, don't forget to re-enter
 your own callsign as *My Call* on the *Settings | General* tab.

doc/user_guide/en/vhf-features.adoc

@@ -1,4 +1,4 @@
-_WSJT-X_ v1.8 suppports a number of features designed for use
+_WSJT-X_ v1.9 suppports a number of features designed for use
 on the VHF and higher bands.  These features include:
 
 - *FT8*, a mode designed for making fast QSOs with weak, fading
@@ -8,6 +8,8 @@ signals
 
 - *JT9* fast modes, useful for scatter propagation on VHF bands
 
+- *JT65*, widely used for EME on VHF and higher bands
+
 - *QRA64*, a mode for EME using a "`Q-ary Repeat Accumulate`" code,
 a low-density parity-check (LDPC) code using a 64-character symbol
 alphabet
@@ -24,6 +26,8 @@ propagation
 - *Doppler tracking*, which becomes increasingly important for EME
 on bands above 1.2 GHz.
 
+- Optional *Auto-Sequencing* in JT4, JT9, and JT65 as well as FT8 and QRA64.
+
 [[VHF_SETUP]]
 === VHF Setup
 
@@ -32,8 +36,8 @@ To activate the VHF-and-up features:
 - On the *Settings | General* tab check *Enable VHF/UHF/Microwave
 features* and *Single decode*.
 
-- For EME, check *Decode at t = 52 s* to allow for extra path delay on
-received signals.
+- For EME, check *Decode after EME delay* to allow for extra path
+delay on received signals.
 
 - If you will use automatic Doppler tracking and your radio accepts
 frequency-setting commands while transmitting, check *Allow Tx
@@ -77,13 +81,16 @@ becomes visible when you check *Doppler tracking*.
 
 image::Astronomical_data.png[align="center",alt="Astronomical data"]
 
-Three different types of Doppler tracking are provided:
+Five different types of Doppler tracking are provided:
 
 - Select *Full Doppler to DX Grid* if you know your QSO partner's locator
 and he/she will not be using any Doppler control.
 
-- Select *Receive only* to enable EME Doppler tracking of your receive
-frequency to a specific locator. Your Tx frequency will remain fixed.
+- Select *Own Echo* to enable EME Doppler tracking of your receive
+frequency to your own echo frequency. Your Tx frequency will remain fixed
+and is set to the Sked frequency.  This mode can be used when announcing 
+your CQ call on a specific frequency and listening on your own echo
+frequency.  It can also be used for echo testing with Echo mode.
 
 - Select *Constant frequency on Moon* to correct for your own one-way
 Doppler shift to or from the Moon.  If your QSO partner does the same
@@ -91,6 +98,25 @@ thing, both stations will have the required Doppler compensation.
 Moreover, anyone else using this option will hear both of you
 without the need for manual frequency changes.
 
+- Select *On Dx Echo* when your QSO partner is not using automated 
+Doppler tracking, and announces his/her transmit frequency and listening
+on their own echo frequency. When clicked, this Doppler method will 
+set your rig frequency on receive to correct for the mutual Doppler 
+shift.  On transmit, your rig frequency will be set so that your
+QSO partner will receive you on the same frequency as their own echo
+at the start of the QSO. As the QSO proceeds, your QSO partner will 
+receive you on this starting frequency so that they do not have to 
+retune their receiver as the Doppler changes.  Sked frequency in this 
+case is set to that announced by your QSO partner.
+
+- Select *Call DX* after tuning the radio manually to find a station,
+with the Doppler mode initally set to *None*. You may be tuning the band
+looking for random stations, or to a frequency where a station has been
+seen on an SDR display.  It is usually necessary to hold down the Ctrl key
+while tuning the radio. From the moment *Call DX* is pressed, your 
+transmit frequency is set so that your echo will fall on the same 
+frequency you (and the DX station) are listening. 
+
 - See <<ASTRODATA,Astronomical Data>> for details on the quantities
 displayed in this window.
 
@@ -142,8 +168,9 @@ shorthand messages for RO, RRR, and 73.  These messages are always
 enabled for reception; they will be automatically generated for
 transmission if you check the shorthand message box *Sh*.
 
-Be sure to check *Deep* on the *Decode* menu; you may optionally
-include *Enable averaging* and *Deep search*.
+*Deep* on the *Decode* menu will be automatically selected.  You may
+optionally include *Enable averaging*, *Enable Deep search*, and
+*Enable AP*.
 
 The following screen shot shows three transmissions from a 144 MHz EME
 QSO using submode JT65B and shorthand messages.  Take note of the