mirror of
https://github.com/saitohirga/WSJT-X.git
synced 2024-12-18 08:55:53 -05:00
c197d216b3
These documentation source files are not the one true version, just a copy for testing purposes. DO NOT EDIT THESE FILES. To use this on Windows you will need a working asciidoc installation and the path to it must be included in your CMAKE_PREFIX_PATH (probably via a local CMake tool chain file). At the time of writing the official asciidoc package does not work on Windows. The latest development master does however work, it can be downloaded as a snapshot ZIP archive from here: https://github.com/asciidoc/asciidoc/archive/master.zip git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@5316 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
117 lines
4.8 KiB
Plaintext
117 lines
4.8 KiB
Plaintext
// Status=review
|
||
.Wide Graph Settings:
|
||
|
||
- Set *Bins/Pixel* = 7
|
||
- Adjust the width of the Wide Graph window so that the upper
|
||
frequency limit is approximately 4000 Hz.
|
||
|
||
.Main Window:
|
||
- Select *JT9+JT65* on the *Mode* menu.
|
||
- Toggle the *Tx mode* button to read *Tx JT65*, and set the Tx and Rx
|
||
frequencies to 1718 Hz.
|
||
- Double-click on *Erase* to clear both text windows.
|
||
|
||
.Open a Wave File:
|
||
|
||
- Select *File | Open* and navigate to +...\save\samples\130610_2343.wav+.
|
||
The waterfall should look like this:
|
||
|
||
//.130610_2343.wav Decode
|
||
[[X14]]
|
||
image::images/130610_2343-wav-80.png[align="left",alt="Wide Graph Decode 130610_2343"]
|
||
|
||
TIP: Notice the [blue]*BLUE* marker on the waterfall scale, here
|
||
set at 2500 Hz. Its position is set by the spinner control *JT65 nnnn
|
||
JT9*, where nnnn is a frequency in Hz. In *JT9+JT65* mode the program
|
||
will automatically decode JT65 signals below this frequency and JT9
|
||
signals above it.
|
||
|
||
JT9 signals appear in the *Cumulative* spectrum as nearly
|
||
rectangular shapes about 16 Hz wide. Although there is no clearly
|
||
visible sync tone like the one at the low-frequency edge of JT65
|
||
signals, by convention the nominal frequency of a JT9 signal is taken
|
||
to be that of its lowest tone, at the left edge of its spectrum.
|
||
|
||
This sample file contains 17 decodable signals — nine in JT65 mode
|
||
(flagged with the character # in the decoded text windows), and eight
|
||
in JT9 mode (flagged with @). The *Band Activity* window should
|
||
contain these decodes (you may need to scroll back in the window to
|
||
see them all):
|
||
|
||
// ... Figure here showing the text windows ?
|
||
[[FigDecodes]]
|
||
image::images/decodes.png[align="center"]
|
||
|
||
Since the Tx mode was set to *Tx JT65*, signals in that mode were
|
||
decoded first. If you had selected *Tx JT9*, JT9 signals would have
|
||
been decoded first.
|
||
|
||
- Confirm that mouse-click behavior is similar to that described
|
||
<<TUT_EX1,earlier>>, in Example 1. The program automatically determines
|
||
the mode of each JT9 or JT65 signal.
|
||
|
||
TIP: When you double-click on a signal in the waterfall it will be
|
||
properly decoded even if on the ``wrong'' side of the *JT65 nnnn JT9*
|
||
marker. The Tx mode automatically switches to that of the decoded
|
||
signal and the Rx and Tx frequency markers on the waterfall scale
|
||
resize themselves accordingly. When selecting a JT65 signal, click on
|
||
the sync tone at its left edge.
|
||
|
||
- Double-click on the waterfall near 815 Hz: a JT65 message
|
||
originating from W7VP will be decoded and appear in the *Rx Frequency*
|
||
window.
|
||
|
||
[width="70%",cols="3,^3,^3,^4,^4,30",options="header"]
|
||
|=================================
|
||
|UTC|dB|DT|Freq|Mode|Message
|
||
|+2343+|+-7+|+0.3+|+815+|+#+|+KK4DSD W7VP -16+
|
||
|=================================
|
||
|
||
- Double-click on the waterfall at 3196 Hz. The program will decode a
|
||
JT9 message from IZ0MIT:
|
||
|
||
[width="70%",cols="3,^3,^3,^4,^4,30",options="header"]
|
||
|=====================================
|
||
|UTC|dB|DT|Freq|Mode|Message
|
||
|+2343+|+-7+|+0.3+|+3196+|+@+|+WB8QPG IZ0MIT -11+
|
||
|=====================================
|
||
|
||
- Scroll back in the *Band Activity* window and double-click on the
|
||
message +CQ DL7ACA JO40+. The program will set *Tx mode* to JT65 and Tx
|
||
and Rx frequencies to that of DL7ACA, 975 Hz. If you had checked
|
||
*Double-click on call sets Tx Enable* on the *Setup* menu, the program
|
||
would configure itself to start a QSO with DL7ACA.
|
||
|
||
- Double-click on the decoded JT65 message +CQ TA4A KM37+. The program
|
||
will set Tx mode to JT9 and the Rx and Tx frequencies to 3567 Hz. The
|
||
program is now configured properly for a JT9 QSO with TA4A.
|
||
|
||
.Reopen the First Sample File:
|
||
- Select *File | Open* and navigate to +...\save\samples\130418_1742.wav+.
|
||
|
||
Taking full advantage of the wide-band, dual-mode capability of
|
||
_WSJT-X_ requires a receiver bandwidth of at least 4 kHz. These
|
||
data were recorded with a much narrower Rx bandwidth, roughly 200 to
|
||
2600 Hz. If you have no Rx filter wider than about 2.7 kHz, you will
|
||
be using data like this. For best viewing, adjust *Bins/Pixel* and the
|
||
width of the Wide Graph so that only the active part of the spectrum
|
||
shows, say 0 to 2600 Hz. Re-open the example file after any change of
|
||
*Bins/Pixel* or Wide Graph width, to refresh the waterfall.
|
||
|
||
The signals in this file are all JT9 signals. To decode them
|
||
automatically in *JT9+JT65* mode you’ll need to move the *JT65 nnnn JT9*
|
||
delimiter down to 1000 Hz or less.
|
||
|
||
.Start, Zero, and Gain
|
||
|
||
Now is a good time to experiment with the *Start*, *Zero*, and *Gain*
|
||
parameters. *Start* determines the frequency displayed at the left
|
||
side of the waterfall scale. *Zero* sets the baseline level for
|
||
colors, and *Gain* sets the sensitivity for color changes. For the
|
||
receiver setup of this file good values are close to *Zero*=0,
|
||
*Gain*=0. Re-open the wave file after each change, to see the new
|
||
results.
|
||
|
||
IMPORTANT: When finished with this Tutorial, don’t forget to re-enter
|
||
your own callsign as *My Call* on the *Settings | General* tab.
|