w4kek/WSJT-X
1
0
Fork 0
mirror of https://github.com/saitohirga/WSJT-X.git synced 2024-11-21 19:55:20 -05:00
Code Issues Packages Projects Releases Wiki Activity

First cut at replacing QRA64 with Q65 throughout the User Guide.

Browse Source
This commit is contained in:
Joe Taylor 2021-03-04 11:37:00 -05:00
parent 10c8fe5353
commit 3db1b27c06
7 changed files with 109 additions and 132 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/common/license.adoc
View File

@ -27,9 +27,10 @@ our work under terms of the GNU General Public License must display
the following copyright notice prominently:
*The algorithms, source code, look-and-feel of _{prog}_ and related
programs, and protocol specifications for the modes FSK441, FT4, FT8,
JT4, JT6M, JT9, JT65, JTMS, QRA64, ISCAT, and MSK144 are Copyright (C)
2001-2020 by one or more of the following authors: Joseph Taylor,
K1JT; Bill Somerville, G4WJS; Steven Franke, K9AN; Nico Palermo,
IV3NWV; Greg Beam, KI7MT; Michael Black, W9MDB; Edson Pereira, PY2SDR;
Philip Karn, KA9Q; and other members of the WSJT Development Group.*
programs, and protocol specifications for the modes FSK441, FST4,
FST4W, FT4, FT8, JT4, JT6M, JT9, JT44, JT65, JTMS, Q65, QRA64, ISCAT,
and MSK144 are Copyright (C) 2001-2021 by one or more of the following
authors: Joseph Taylor, K1JT; Bill Somerville, G4WJS; Steven Franke,
K9AN; Nico Palermo, IV3NWV; Greg Beam, KI7MT; Michael Black, W9MDB;
Edson Pereira, PY2SDR; Philip Karn, KA9Q; and other members of the
WSJT Development Group.*

5
doc/user_guide/en/controls-functions-center.adoc
View File

@ -60,7 +60,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, QRA64 and MSK144 modes
** *Sh* enables shorthand messages in JT4, JT65, Q65, and MSK144 modes
** *Fast* enables fast JT9 submodes
@ -69,4 +69,5 @@ features for particular operating modes:
** *Call 1st* enables automatic response to the first decoded
responder to your CQ
** *Tx6* toggles between two types of shorthand messages in JT4 mode
** *Tx6* toggles between two types of shorthand messages in JT4 and
Q65 modes

35
doc/user_guide/en/decoder_notes.adoc
View File

@ -2,12 +2,12 @@
=== AP Decoding
The _WSJT-X_ decoders for FST4, FT4, FT8, JT65, and QRA64 include
The _WSJT-X_ decoders for FST4, FT4, FT8, JT65, and Q65 include
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. AP is optional in FT8, JT65, and QRA64, but is always
enabled for FT4 and FST4 when decode depth is Normal or Deep.
false decodes. AP is optional in FT8 and JT65, but is always enabled
for Q65 and for FT4 and FST4 when decode depth is Normal or Deep.
For example: when you decide to answer a CQ, you already know your own
callsign and that of your potential QSO partner. The software
@ -132,25 +132,16 @@ End of line information::
`d` - Deep Search algorithm +
`f` - Franke-Taylor or Fano algorithm +
`N` - Number of Rx intervals or frames averaged +
`P` - Number indicating type of AP information (Table 1, above) +
`P` - Number indicating type of AP information (Table 1 or Table 6) +
Table 6 below shows the meaning of the return codes R in QRA64 mode.
[[QRA64_AP_INFO_TABLE]]
.QRA64 AP return codes
[width="35%",cols="h10,<m20",frame=topbot,options="header"]
[[Q65_AP_INFO_TABLE]]
.Q65 end-of-line codes
[width="45%",cols="h10,<m20",frame=topbot,options="header"]
|===============================================
|rc | Message components
|0 | ? &#160; &#160; ? &#160; &#160; ?
|1 | CQ &#160; &#160; ? &#160; &#160; ?
|2 | CQ &#160; &#160; ?
|3 | MyCall &#160; &#160; ? &#160; &#160; ?
|4 | MyCall &#160; &#160; ?
|5 | MyCall DxCall &#160; &#160; ?
|6 | ? &#160; &#160; DxCall &#160; &#160; ?
|7 | ? &#160; &#160; DxCall
|8 | MyCall DxCall DxGrid
|9 | CQ DxCall &#160; &#160; ?
|10 | CQ DxCall
|11 | CQ DxCall DxGrid
| | Message components
|q0 | ? &#160; &#160; ? &#160; &#160; ?
|q1 | CQ &#160; &#160; ? &#160; &#160; ?
|q2 | MyCall &#160; &#160; ? &#160; &#160; ?
|q3 | MyCall DxCall &#160; &#160; ?
|q4 | MyCall DxCall &#160; &#160; [<blank> \| RRR \| RR73 \| 73]
|===============================================

2
doc/user_guide/en/introduction.adoc
View File

@ -15,7 +15,7 @@ first seven are designed for making reliable QSOs under weak-signal
conditions. They use nearly identical message structure and source
encoding. JT65 was designed for EME ("`moonbounce`") on VHF and
higher bands and is mostly used for that purpose today. Q65 replaces
an earlier mode, QRA64; it is particularly effective for tropospheric
an earlier mode, QRA64. Q65 is particularly effective for tropospheric
scatter, rain scatter, ionospheric scatter, TEP, and EME on VHF and
higher bands, as well as other types of fast-fading signals. JT9 was
originally designed for the HF and lower bands. Its submode JT9A is 1

66
doc/user_guide/en/protocols.adoc
View File

@ -169,25 +169,25 @@ same as that of the sync tone used in long messages, and the frequency
separation is 110250/4096 = 26.92 Hz multiplied by n for JT65A, with n
= 2, 3, 4 used to convey the messages RO, RRR, and 73, respectively.
[[QRA64_PROTOCOL]]
==== QRA64
[[Q65_PROTOCOL]]
==== Q65
QRA64 is intended for EME and other extreme weak-signal applications.
Its internal code was designed by IV3NWV. The protocol uses a (63,12)
**Q**-ary **R**epeat **A**ccumulate code that is inherently better
than the Reed Solomon (63,12) code used in JT65, yielding a 1.3 dB
advantage. A new synchronizing scheme is based on three 7 x 7 Costas
arrays. This change yields another 1.9 dB advantage.
Q65 is intended for scatter, EME, and other extreme weak-signal
applications. Forward error correction (FEC) uses a specially
designed (65,15) block code with six-bit symbols. Two symbols are
“punctured” from the code, yielding an effective (63,13) code with a
payload of k = 13 information symbols conveyed by n = 63 channel
symbols. The punctured symbols consist of a 12-bit CRC computed from
the 13 information symbols. The CRC is used to reduce the
false-decode rate to a very low value. A 22-symbol pseudo-random
sequence spread throughout a transmission is sent as “tone 0” and used
for synchronization. The total number of channel symbols in a Q65
transmission is thus 63 + 22 = 85.
In most respects the current implementation of QRA64 is operationally
similar to JT65. QRA64 does not use two-tone shorthand messages, and
it makes no use of a callsign database. Rather, additional
sensitivity is gained by making use of already known information as a
QSO progresses -- for example, when reports are being exchanged and
you have already decoded both callsigns in a previous transmission.
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.
For each T/R sequence length, submodes A - E have tone spacings and
occupied bandwidths 1, 2, 4, 8, and 16 times those specified in the
above table. Full submode designations include a number for sequence
length and a letter for tone spacing, as in Q65-15A, Q65-120C, etc.
[[WSPR_PROTOCOL]]
==== WSPR
@ -277,8 +277,12 @@ which the probability of decoding is 50% or higher.
|FT8 |LDPC |(174,91)| 8| 8-GFSK| 6.25 | 50.0 | 0.27| 12.6 | -21
|JT4A |K=32, r=1/2|(206,72)| 2| 4-FSK| 4.375| 17.5 | 0.50| 47.1 | -23
|JT9A |K=32, r=1/2|(206,72)| 8| 9-FSK| 1.736| 15.6 | 0.19| 49.0 | -26
|JT65A |Reed Solomon|(63,12) |64|65-FSK| 2.692| 177.6 | 0.50| 46.8 | -25
|QRA64A|Q-ary Repeat Accumulate|(63,12) |64|64-FSK|1.736|111.1|0.25|48.4| -26
|JT65A |RS|(63,12) |64|65-FSK| 2.692| 177.6 | 0.50| 46.8 | -25
|Q65-15A |QRA|(63,13) |64|65-FSK|6.667|433|0.26| 12.8| -22.2
|Q65-30A |QRA|(63,13) |64|65-FSK|3.333|217|0.26| 25.5| -24.8
|Q65-60A |QRA|(63,13) |64|65-FSK|1.667|108|0.26| 51.0| -27.6
|Q65-120A|QRA|(63,13) |64|65-FSK|0.750| 49|0.26|113.3| -30.8
|Q65-300A|QRA|(63,13) |64|65-FSK|0.289| 19|0.26|293.8| -33.8
| WSPR |K=32, r=1/2|(162,50)| 2| 4-FSK| 1.465| 5.9 | 0.50|110.6 | -31
|FST4W-120 |LDPC | (240,74)| 4| 4-GFSK| 1.46 | 5.9 | 0.25| 109.3 | -32.8
|FST4W-300 |LDPC | (240,74)| 4| 4-GFSK| 0.558 | 2.2 | 0.25| 286.7 | -36.8
@ -286,14 +290,18 @@ which the probability of decoding is 50% or higher.
|FST4W-1800 |LDPC | (240,74)| 4| 4-GFSK| 0.089 | 0.36 | 0.25| 1792.0| -44.8
|===============================================================================
Submodes of JT4, JT9, JT65, and QRA64 offer wider tone spacings for
LDPC = Low Density Parity Check
RS = Reed Solomon
QRA = Q-ary Repeat Accumulate
Submodes of JT4, JT9, and JT65 offer wider tone spacings for
circumstances that may require them, such as significant Doppler spread.
Table 8 summarizes the tone spacings, bandwidths, and approximate
threshold sensitivities of the various submodes when spreading is
comparable to tone spacing.
[[SLOW_SUBMODES]]
.Parameters of Slow Submodes with Selectable Tone Spacings
.Parameters of Slow Submodes JT4, JT9, and JT65 with Selectable Tone Spacings
[width="50%",cols="h,3*^",frame=topbot,options="header"]
|=====================================
|Mode |Tone Spacing |BW (Hz)|S/N (dB)
@ -315,11 +323,17 @@ comparable to tone spacing.
|JT65A |2.692| 177.6 |-25
|JT65B |5.383| 352.6 |-25
|JT65C |10.767| 702.5 |-25
|QRA64A|1.736| 111.1 |-26
|QRA64B|3.472| 220.5 |-25
|QRA64C|6.944| 439.2 |-24
|QRA64D|13.889| 876.7 |-23
|QRA64E|27.778|1751.7 |-22
|=====================================
.Parameters of Q65 Submodes
[width="100%",cols="h,5*^",frame=topbot,options="header"]
|=====================================
|T/R Period (s) |A Spacing Width (Hz)|B Spacing Width (Hz)|C Spacing Width (Hz)|D Spacing Width (Hz)|E Spacing Width (Hz)
|15|6.67 &#160; &#160; 4.33|13.33 &#160; &#160; 867|26.67 &#160; &#160; 1733|N/A|N/A
|30|3.33 &#160; &#160; 217|6.67 &#160; &#160; 433|13.33 &#160; &#160; 867| 26.67 &#160; &#160; 1733| N/A
|60|1.67 &#160; &#160; 108|3.33 &#160; &#160; 217|6.67 &#160; &#160; 433|13.33 &#160; &#160; 867|26.67 &#160; &#160; 1733
|120|0.75 &#160; &#160; 49|1.50 &#160; &#160; 98|3.00 &#160; &#160; 195|6.00 &#160; &#160; 390| 12.00 &#160; &#160; 780
|300|0.29 &#160; &#160; 19|0.58 &#160; &#160; 38|1.16 &#160; &#160; 75|2.31 &#160; &#160; 150|4.63 &#160; &#160; 301
|=====================================
[[FAST_MODES]]

19
doc/user_guide/en/utilities.adoc
View File

@ -89,25 +89,6 @@ You will discover that every possible JT65 message differs from every
other possible JT65 message in at least 52 of the 63
information-carrying channel symbols.
Here's an example using the QRA64 mode:
C:\WSJTX\bin qra64code "KA1ABC WB9XYZ EN37"
Message Decoded Err? Type
--------------------------------------------------------------------------
1 KA1ABC WB9XYZ EN37 KA1ABC WB9XYZ EN37 1: Std Msg
Packed message, 6-bit symbols 34 16 49 32 51 26 31 40 41 22 0 41
Information-carrying channel symbols
34 16 49 32 51 26 31 40 41 22 0 41 16 46 14 24 58 45 22 45 38 54 7 23 2 49 32 50 20 33
55 51 7 31 31 46 41 25 55 14 62 33 29 24 2 49 4 38 15 21 1 41 56 56 16 44 17 30 46 36
23 23 41
Channel symbols including sync
20 50 60 0 40 10 30 34 16 49 32 51 26 31 40 41 22 0 41 16 46 14 24 58 45 22 45 38 54 7
23 2 49 32 50 20 33 55 51 20 50 60 0 40 10 30 7 31 31 46 41 25 55 14 62 33 29 24 2 49
4 38 15 21 1 41 56 56 16 44 17 30 46 36 23 23 41 20 50 60 0 40 10 30
Execution of any of these utility programs with "-t" as the only
command-line argument produces examples of all supported message
types. For example, using `jt65code -t`:

101
doc/user_guide/en/vhf-features.adoc
View File

@ -11,13 +11,11 @@ higher bands. These features include:
- *JT65*, widely used for EME on VHF and higher bands
- *Q65*, for propagation modes including tropospheric scatter, rain
scatter, ionospheric scatter, TEP, and EME
- *Q65*, for ionospheric scatter, tropospheric scatter, rain scatter,
TEP, and EME
- *MSK144*, for meteor scatter
- *ISCAT*, for aircraft scatter and other types of scatter propagation
- *Echo* mode, for detecting and measuring your own lunar echoes
- *Doppler tracking*, which becomes increasingly important for EME
@ -177,49 +175,31 @@ image::JT65B.png[align="center",alt="JT65B"]
=== Q65
Q65 is designed for propagation paths that produce signals exhibiting fast
fading, including tropospheric scatter, rain scatter, ionospheric scatter,
trans-equatorial propagation (TEP), and EME.
Q65 is designed for propagation paths that produce fast fading
signals: tropospheric scatter, rain scatter, ionospheric scatter,
trans-equatorial propagation (TEP), EME, and the like. The following
screen shot shows an example with submode Q65-30A on a 6-meter
ionospheric scatter path of about 1100 km.
EME on VHF and higher bands; its
operation is generally similar to JT4 and JT65. The following screen
shot shows an example of a QRA64C transmission from DL7YC recorded at
G3WDG over the EME path at 24 GHz. Doppler spread on the path was 78
Hz, so although the signal is reasonably strong its tones are
broadened enough to make them hard to see on the waterfall. The
triangular red marker below the frequency scale shows that the decoder
has achieved synchronization with a signal at approximately 967 Hz.
image::Q65_6m_ionoscatter.png[align="center",alt="Q65"]
image::Q65_6m_ionoscatter.png[align="center",alt="QRA64"]
The QRA64 decoder makes no use of a callsign database. Instead, it
The Q65 decoder makes no use of a callsign database. Instead, it
takes advantage of _a priori_ (AP) information such as one's own
callsign and the encoded form of message word `CQ`. In normal usage,
as a QSO progresses the available AP information increases to include
the callsign of the station being worked and perhaps also his/her
4-digit grid locator. The decoder always begins by attempting to
decode the full message using no AP information. If this attempt
fails, additional attempts are made using available AP information to
provide initial hypotheses about the message content. At the end of
each iteration the decoder computes the extrinsic probability of the
most likely value for each of the message's 12 six-bit information
symbols. A decode is declared only when the total probability for all
12 symbols has converged to an unambiguous value very close to 1.
callsign and the message word `CQ`. In normal usage, as a QSO
progresses the available AP information increases to include the
callsign of the station being worked and perhaps also his/her 4-digit
grid locator. The decoder takes advantage of whatever AP information
is available.
For EME QSOs some operators use short-form QRA64 messages consisting
of a single tone. To activate automatic generation of these messages,
check the box labeled *Sh*. This also enables the generation of a
single tone at 1000Hz by selecting Tx6, to assist in finding signals
initially, as the QRA64 tones are often not visible on the waterfall.
The box labeled *Tx6* switches the Tx6 message from 1000Hz to 1250Hz
to indicate to the other station that you are ready to receive messages.
For Q65 EME QSOs, particularly on the micriowave bands, some operators
use short-form messages consisting of a single tone. To activate
automatic generation of these messages, check the box labeled *Sh*.
This also enables the generation of a single tone at 1000Hz by
selecting Tx6, to assist in finding signals initially. The box
labeled *Tx6* switches the Tx6 message from 1000Hz to 1250Hz to
indicate to the other station that you are ready to receive messages.
TIP: QRA64 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 on the lowest tone of each one in the
waterfall.
TIP: G3WDG has prepared a more detailed tutorial on using {QRA64_EME}.
// TIP: G3WDG has prepared a more detailed tutorial on using {QRA64_EME}.
=== MSK144
@ -332,21 +312,28 @@ image::echo_144.png[align="center",alt="Echo 144 MHz"]
=== Tips for EME
Current conventions dictate that digital EME is usually done with
JT65A on the 50 MHz band, JT65B on 144 and 432 MHz, and JT65C on 1296
MHz. On higher microwave bands typical choices are JT65C or one of
Until the advent of Q65, digital EME has mostly been done using JT65A
on the 50 MHz band, JT65B on 144 and 432 MHz, and JT65C on 1296 MHz.
On higher microwave bands typical choices have been JT65C or one of
the wider QRA64 or JT4 submodes, depending on the expected amount of
Doppler spread. JT4 and JT65 offer message *Averaging* -- the
summation of subsequent transmissions that convey the same message --
to enable decodes at signal-to-noise ratios several dB below the
threshold for single transmissions. These modes also allow *Deep
Search* decoding, in which the decoder hypothesizes messages
containing known or previously decoded callsigns and tests them for
reliability using a correlation algorithm. Finally, JT65 and QRA64
offer _a priori_ (AP) decoding, which takes advantage of naturally
accumulating information during a QSO. The following tutorial aims to
familiarize you with these program features, all of which are of
special interest for EME and other extreme weak-signal conditions.
Doppler spread. We now recommend a suitable submodes of Q65 for EME
on all bands: for example, Q65-60A on 50 and 144 MHz, -60B on
432 MHz, -60C on 1296 MHz, and -60D on 10 GHz.
JT4, JT65, and Q65 offer *Message Averaging* -- the summation of
subsequent transmissions that convey the same message -- to enable
decodes at signal-to-noise ratios several dB below the threshold for
single transmissions. JT4 and JT65 also allow *Deep Search* decoding,
in which the decoder hypothesizes messages containing known or
previously decoded callsigns and tests them for reliability using a
correlation algorithm. JT65 and Q65 offer _a priori_ (AP)
decoding, which takes advantage of naturally accumulating information
during a QSO.
////
The following tutorial aims to familiarize you with
these program features, all of which are of special interest for EME
and other extreme weak-signal conditions.
As a starting point, configure _WSJT-X_ as follows:
@ -434,3 +421,5 @@ You might wish to experiment with other combinations of entries for
options of the *Decode* menu on and off. For best sensitivity, most
users will want to use *Deep* decoding with *Enable averaging*,
*Enable deep search*, and *Enable AP* all turned on.
////