Updates to User Guide.

git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8481 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
This commit is contained in:
Joe Taylor 2018-02-08 19:37:21 +00:00
parent 5b70c7dcff
commit ac01a6289f
7 changed files with 39 additions and 15 deletions

View File

@ -68,7 +68,7 @@ d). Edit lines as needed. Keeping them in alphabetic order help see dupes.
:fmt_k5cm: http://www.k5cm.com/[FMT Event Info]
:fmt_wspr: http://www.physics.princeton.edu/pulsar/K1JT/FMT_User.pdf[Accurate Frequency Measurements with your WSPR Setup]
:ft8_tips: http://www.physics.princeton.edu/pulsar/K1JT/FT8_Operating_Tips.pdf[here]
:ft8_DXped: http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf[here]
:ft8_DXped: http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf[FT8 DXpedition Mode]
:gnu_gpl: http://www.gnu.org/licenses/gpl-3.0.txt[GNU General Public License]
:homepage: http://physics.princeton.edu/pulsar/K1JT/[WSJT Home Page]
:hrd: http://www.hrdsoftwarellc.com/[Ham Radio Deluxe]

View File

@ -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,8 +47,7 @@ location for each instance of _WSJT-X_.
wsjtx --rig-name=TS2000
wsjtx --rig-name=FT847
When setting up rig control through _Omni-Rig_, 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?::
_Omni-Rig_ apparently has a bug that appears when you click *Test
CAT*. Forget using *Test CAT* and just click *OK*. _Omni-Rig_ then

Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

After

Width:  |  Height:  |  Size: 83 KiB

View File

@ -13,6 +13,11 @@ 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.

View File

@ -3,7 +3,8 @@
For quick reference, here's a short list of features and capabilities
added to _WSJT-X_ since Version 1.8.0:
- New *FT8 DXpedition Mode* to facilitate high-rate QSOs in a pileup
- New *FT8 DXpedition Mode* to facilitate high QSO rates in pileup
situations
- Decoding improvements for JT65 mode, including _a priori_ (AP)
decoding when VHF/UHF/Microwave features are enabled
@ -15,15 +16,15 @@ decoding in FT8 mode
- Minor adjustments to auto-sequencing behavior
- Improved Doppler control features for EME
- More flexible Doppler control features for EME
- Improved waterfall sensitivity for very weak signals
- Automatic real-time forwarding of logged information to _N1MM Logger+_
- Expanded and improved UDP messages for companion programs
- Expanded and improved UDP messages sent to companion programs
- Bug fixes and minor tweaks to user interface
- Bug fixes and other minor tweaks to user interface
=== Documentation Conventions

View File

@ -58,9 +58,15 @@ NOTE: Further helpful tips on FT8 operating procedures are available
- 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 can be found {ft8_DXped}.
Do not try to use DXpedition mode without reading these instructions
carefully!
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.

View File

@ -77,20 +77,33 @@ 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
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* ...
- 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.