mirror of
https://github.com/saitohirga/WSJT-X.git
synced 2024-10-31 15:47:10 -04:00
Fix many typos in User Guide. Thanks to Frode, LA6VQ, for reporting most of these!
This commit is contained in:
parent
7dfe51ab8e
commit
e00f44d0f3
@ -28,7 +28,7 @@ decoded text or a signal in the waterfall.
|
||||
|
||||
* For modes lacking a multi-decode feature, or when *Enable
|
||||
VHF/UHF/Microwave features* has been checked on the *Settings ->
|
||||
General* tab, the *F Tol* control sets a frequency toilerance range
|
||||
General* tab, the *F Tol* control sets a frequency tolerance range
|
||||
over which decoding will be attempted, centered on the Rx frequency.
|
||||
|
||||
* The *Report* control lets you change a signal report that has been
|
||||
|
@ -30,7 +30,7 @@ Pressing *Enter* on a modified message #5 automatically adds that
|
||||
message to the stored macros.
|
||||
|
||||
* In some circumstances it may be desirable to make your QSOs as
|
||||
shiort as possible. To configure the program to start contacts with
|
||||
short as possible. To configure the program to start contacts with
|
||||
message #2, disable message #1 by double-clicking on its round
|
||||
radio-button or rectangular *Tx 1* button. Similarly, to send RR73
|
||||
rather than RRR for message #4, double-click on one of its buttons.
|
||||
|
@ -17,7 +17,7 @@ displayed exactly as it will be decoded by receiving stations. The
|
||||
second label (as shown above) will be absent if you are using the
|
||||
*Default* setting on the *Configurations* menu. A progress bar shows
|
||||
the elapsed fraction of a Tx or Rx sequence. Finally, if the Watchdog
|
||||
(WD) timer was enabled on the *settings | General* tab, a label in the
|
||||
(WD) timer was enabled on the *Settings | General* tab, a label in the
|
||||
lower right-hand corner displays the number of minutes remaining
|
||||
before timeout.
|
||||
|
||||
|
@ -53,7 +53,7 @@ You need to install suitable _OpenSSL_ libraries - see <<OPENSSL,Instructions to
|
||||
|
||||
I occasionally get Rig Control Errors if I adjust my Icom rig's VFO. What's wrong?::
|
||||
|
||||
By default most Icom transceivers have *CI-V Tranceive Mode" enabled,
|
||||
By default, most Icom transceivers have *CI-V Tranceive Mode" enabled,
|
||||
this will cause unsolicited CAT traffic from the rig that disrupts CAT
|
||||
control by a PC. Disable this option in the rig's menu.
|
||||
|
||||
|
Binary file not shown.
Before Width: | Height: | Size: 7.4 KiB After Width: | Height: | Size: 7.6 KiB |
@ -70,7 +70,7 @@ TIP: If you cannot install the _OpenSSL_ libraries or do not have an
|
||||
To ensure that this will be so when running under recent versions of
|
||||
Windows, open the system's *Sound* control panel and select in turn
|
||||
the *Recording* and *Playback* tabs. Click on *Properties*, then
|
||||
*Advanced*, and select *16 bit, 48000 Hz (DVD Quality)*. Switch of
|
||||
*Advanced*, and select *16 bit, 48000 Hz (DVD Quality)*. Switch off
|
||||
all audio enhancement features for these devices.
|
||||
|
||||
* You can uninstall _WSJT-X_ by clicking its *Uninstall* link in the
|
||||
|
@ -20,7 +20,7 @@ signal report, R plus a signal report, or the final acknowledgements
|
||||
RRR or 73. These messages are compressed and encoded in a highly
|
||||
efficient and reliable way. In uncompressed form (as displayed
|
||||
on-screen) they may contain as many as 22 characters. Some operators
|
||||
prefer ro send RR73 rather than RRR. This is workable because RR73 is
|
||||
prefer to send RR73 rather than RRR. This is workable because RR73 is
|
||||
encoded as a valid grid locator, one unlikely ever to be occupied by
|
||||
an amateur station.
|
||||
|
||||
@ -81,7 +81,7 @@ fully automated QSOs.
|
||||
|
||||
=== Contest Messages
|
||||
|
||||
The new FT8 and MSK144 protocols support special messages optimized
|
||||
The new FT4, FT8, and MSK144 protocols support special messages optimized
|
||||
for *NA VHF* and *EU VHF* contests. FT8 also supports messages for
|
||||
*ARRL Field Day* and the *ARRL RTTY Roundup*. The decoders recognize
|
||||
and decode these messages at any time. Configure the program to
|
||||
|
@ -36,7 +36,7 @@ in other parts of the world.
|
||||
frequencies, check *Execute frequency calibration cycle* on the
|
||||
*Tools* menu. _WSJT-X_ will spend 30 seconds at each
|
||||
frequency. Initially no measurement data is saved to the `fmt.all`
|
||||
file although it is displayed on screen, this allows you to check you
|
||||
file although it is displayed on screen, this allows you to check your
|
||||
current calibration parameters.
|
||||
|
||||
- During the calibration procedure, the radio's USB dial frequency is
|
||||
@ -44,11 +44,11 @@ offset 1500 Hz below each *FreqCal* entry in the default frequencies
|
||||
list. As shown in the screen shot below, detected signal carriers
|
||||
therefore appear at about 1500 Hz in the _WSJT-X_ waterfall.
|
||||
|
||||
- To start a measurement session check the *Measure* option and let
|
||||
- To start a measurement session, check the *Measure* option and let
|
||||
the calibration cycle run for at least one complete sequence. Note
|
||||
that, while measuring, any existing calibration parameters are
|
||||
automatically disabled so you may have to increase the *FTol* range if
|
||||
your rig is off freqeuncy by more than a few Hertz in order to capture
|
||||
your rig is off frequency by more than a few Hertz in order to capture
|
||||
valid measurements.
|
||||
|
||||
image::FreqCal.png[align="left",alt="FreqCal"]
|
||||
|
@ -17,7 +17,7 @@ In this manual the following icons call attention to particular types
|
||||
of information:
|
||||
|
||||
NOTE: *Notes* containing information that may be of interest to
|
||||
particuar classes of users.
|
||||
particular classes of users.
|
||||
|
||||
TIP: *Tips* on program features or capabilities that might otherwise be
|
||||
overlooked.
|
||||
|
@ -52,9 +52,10 @@ were the callsigns `E9AA` through `E9ZZ`. Upon reception they are
|
||||
converted back to the form `CQ AA` through `CQ ZZ`, for display to the
|
||||
user.
|
||||
|
||||
The new FT8 and MSK144 protocols use a different lossless compression
|
||||
algorithm with features to generate and recognize the special messages
|
||||
used for contesting and the like. (More to come, here ...)
|
||||
The new FT4, FT8, and MSK144 protocols use a different lossless
|
||||
compression algorithm with features to generate and recognize the
|
||||
special messages used for contesting and the like. (More to come,
|
||||
here ...)
|
||||
|
||||
To be useful on channels with low signal-to-noise ratio, this kind of
|
||||
lossless message compression requires use of a strong forward error
|
||||
@ -224,7 +225,7 @@ the sync bit.
|
||||
[[SLOW_SUMMARY]]
|
||||
==== Summary
|
||||
|
||||
Table 2 provides a brief summary parameters for the slow modes in
|
||||
Table 7 provides a brief summary parameters for the slow modes in
|
||||
_WSJT-X_. Parameters K and r specify the constraint length and rate
|
||||
of the convolutional codes; n and k specify the sizes of the
|
||||
(equivalent) block codes; Q is the alphabet size for the
|
||||
@ -250,7 +251,7 @@ which the probability of decoding is 50% or higher.
|
||||
|
||||
Submodes of JT4, JT9, JT65, and QRA64 offer wider tone spacings for
|
||||
circumstances that may require them, such significant Doppler spread.
|
||||
Table 3 summarizes the tone spacings, bandwidths, and approximate
|
||||
Table 8 summarizes the tone spacings, bandwidths, and approximate
|
||||
threshold sensitivities of the various submodes when spreading is
|
||||
comparable to tone spacing.
|
||||
|
||||
@ -335,7 +336,7 @@ The JT9 slow modes all use keying rate 12000/6912 = 1.736 baud. By contrast, wi
|
||||
the *Fast* setting submodes JT9E-H adjust the keying rate to match the
|
||||
increased tone spacings. Message durations are therefore much
|
||||
shorter, and they are sent repeatedly throughout each Tx sequence.
|
||||
For details see Table 4, below.
|
||||
For details see Table 9, below.
|
||||
|
||||
==== MSK144
|
||||
|
||||
|
@ -38,7 +38,7 @@ 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.
|
||||
|
||||
_Special Operating Activity: Generation of FT8 and MSk144 messages_
|
||||
_Special Operating Activity: Generation of FT8 and MSK144 messages_
|
||||
|
||||
- Check this box and select the type of activity to enable
|
||||
auto-generation of special message formats for contesting and
|
||||
|
@ -37,11 +37,11 @@ TIP: The _WSJT-X_ ADIF file records must contain the "CALL" field.
|
||||
|
||||
Stations who are known to have uploaded their logs to the ARRL LoTW
|
||||
QSL matching service can be highlighted. The data used to determine
|
||||
this is available on line.
|
||||
this is available online.
|
||||
|
||||
* *Fetch Now* will download a fresh dataset from the *Users CSV file
|
||||
URL*. The LoTW team normally update this data weekly.
|
||||
|
||||
* Adjust *Age of of last upload less than* to set the period within
|
||||
* Adjust *Age of last upload less than* to set the period within
|
||||
which a station must have uploaded their log to LoTW to trigger
|
||||
highlighting.
|
||||
|
@ -3,7 +3,7 @@
|
||||
[[FIG_BAND_SETTINGS]]
|
||||
image::settings-frequencies.png[align="center",alt="Frequency Screen"]
|
||||
|
||||
_Working Frequencies_: By default the *Working Frequencies* table
|
||||
_Working Frequencies_: By default, the *Working Frequencies* table
|
||||
contains a list of frequencies conventionally used for modes FT8, JT4,
|
||||
JT9, JT65, MSK144, WSPR, and Echo. Conventions may change with time
|
||||
or by user preference; you can modify the frequency table as desired.
|
||||
|
@ -42,7 +42,7 @@ NOTE: _Omni-Rig_ is available only under Windows.
|
||||
|
||||
NOTE: A special value of *USB* is available for custom USB devices
|
||||
like those used by some SDR kits. This is not the same a virtual
|
||||
serial port provided by USB connected transcivers and CAT
|
||||
serial port provided by USB connected transceivers and CAT
|
||||
interfaces, for those use the COM or serial port name that
|
||||
refers to them.
|
||||
|
||||
@ -69,7 +69,7 @@ NOTE: CAT interfaces that require handshaking will be non-responsive
|
||||
|
||||
NOTE: When using a proxy application for rig control, *CAT* is usually
|
||||
the correct option for _PTT Method_ assuming the proxy
|
||||
application is capable of keying your transceiver idependently.
|
||||
application is capable of keying your transceiver independently.
|
||||
|
||||
* _Transmit Audio Source_: some radios permit you to choose the
|
||||
connector that will accept Tx audio. If this choice is enabled,
|
||||
|
@ -28,7 +28,7 @@ When this file was recorded KF4RWA was finishing a QSO with K1JT.
|
||||
Since the green marker was placed at his audio frequency, 1224 Hz, his
|
||||
message `K1JT KF4RWA 73` is decoded first and appears in the *Rx
|
||||
Frequency* window. The *Band Activity* window shows this message plus
|
||||
all decodes at other frequencies. By default lines containing `CQ`
|
||||
all decodes at other frequencies. By default, lines containing `CQ`
|
||||
are highlighted in green, and lines with *My Call* (in this case K1JT)
|
||||
in red.
|
||||
|
||||
|
@ -39,7 +39,7 @@ things just described and also invokes the decoder in a small range
|
||||
around the Rx frequency. To decode a particular signal, double-click
|
||||
near the left edge of its waterfall trace.
|
||||
|
||||
- Now double-click on any of the the lines of decoded text in the Band
|
||||
- Now double-click on any of the lines of decoded text in the Band
|
||||
Activity window. Any line will show the same behavior, setting
|
||||
Rx frequency to that of the selected message and leaving Tx frequency
|
||||
unchanged. To change both Rx and Tx frequencies, hold *Ctrl* down
|
||||
|
@ -37,7 +37,7 @@ follow your frequency selections.
|
||||
- Do the same thing with the *Ctrl* key held down. Now the both colored
|
||||
markers and both spinner controls will follow your selections.
|
||||
|
||||
- Now double-click on any of the the lines of decoded text in the Band
|
||||
- Now double-click on any of the lines of decoded text in the Band
|
||||
Activity window. Any line will show similar behavior, setting
|
||||
Rx frequency to that of the selected message and leaving Tx frequency
|
||||
unchanged. To change both Rx and Tx frequencies, hold *Ctrl* down
|
||||
|
@ -1,4 +1,4 @@
|
||||
_WSJT-X_ v{VERSION_MAJOR}.{VERSION_MINOR} suppports a number of
|
||||
_WSJT-X_ v{VERSION_MAJOR}.{VERSION_MINOR} supports a number of
|
||||
features designed for use on the VHF and higher bands. These features
|
||||
include:
|
||||
|
||||
@ -111,7 +111,7 @@ 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
|
||||
with the Doppler mode initially 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
|
||||
@ -221,7 +221,7 @@ to indicate to the other station that you are ready to receive messages.
|
||||
|
||||
TIP: QRA64 is different from JT65 in that the decoder attempts to find
|
||||
and decode only a single signal in the receiver passband. If many
|
||||
signals are present you may be able to decode them by double-clicking
|
||||
signals are present, you may be able to decode them by double-clicking
|
||||
on the lowest tone of each one in the waterfall.
|
||||
|
||||
TIP: G3WDG has prepared a more detailed tutorial on using {QRA64_EME}.
|
||||
@ -236,11 +236,11 @@ error-correction facility.
|
||||
|
||||
=== MSK144
|
||||
|
||||
Meteor-scatter QSOs can be made any time on the VHF bands at distances
|
||||
Meteor scatter QSOs can be made any time on the VHF bands at distances
|
||||
up to about 2100 km (1300 miles). Completing a QSO takes longer in
|
||||
the evening than in the morning, longer at higher frequencies, and
|
||||
longer at distances close to the upper limit. But with patience, 100
|
||||
Watts or more, and a single yagi it can usually be done. The
|
||||
W or more, and a single yagi it can usually be done. The
|
||||
following screen shot shows two 15-second reception intervals
|
||||
containing MSK144 signals from three different stations.
|
||||
|
||||
@ -271,7 +271,7 @@ image::Rx_pct_MSK144.png[align="center",alt="MSK144 Percent CPU"]
|
||||
|
||||
- The displayed number (here 17%) indicates the fraction of available
|
||||
time being used for execution of the MSK144 real-time decoder. If
|
||||
this number is well below 100% you may increase the decoding depth
|
||||
this number is well below 100%, you may increase the decoding depth
|
||||
from *Fast* to *Normal* or *Deep*, and increase *F Tol* from 100 to
|
||||
200 Hz.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user