w4kek/WSJT-X
1
0
Fork 0
mirror of https://github.com/saitohirga/WSJT-X.git synced 2025-03-23 12:38:53 -04:00
Code Issues Packages Projects Releases Wiki Activity

Minor tweaks to Release Notes.

Browse Source 
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@7011 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
This commit is contained in:
Joe Taylor 2016-08-06 14:42:06 +00:00
parent 3d44ae89df
commit 3be4c5b438
1 changed files with 16 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
v1.7_Features.txt
View File

@ -32,29 +32,29 @@ your screen.
Standard MSK144 message frames are 72 ms long, compared to 117 ms for
JTMSK. The MSK144 waveform allows coherent demodulation, allowing up
to 3 dB better sensitivity. After QSO partners have exchanged
callsigns, MSK144 user can use even shorter messages, only 20 ms long.
As in all the fast modes in WSJT-X, the 20 ms or 72 ms messages are
callsigns, MSK144 can use even shorter messages, only 20 ms long. As
in all the fast modes in WSJT-X, the 20 ms or 72 ms messages are
repeated without gaps for the duration of a transmission cycle. For
most purposes we recommend a T/R cycle duration of 15 s, but 5 s and
10 s sequences are also supported.
MSK144 short ("Sh") messages are intended primarily for 144 MHz, where
most pings are short. These messages do not contain full callsigns;
instead, they contain a hash of the entire transmitted message along
with a report. They are not encrypted -- the report is sent in the
clear along with the hash. Short messages are fully decodable only by
the station to whom they are addressed, as part of an ongoing QSO,
because only then will the received hash match that calculated using
the known strings for "My Call" and "DX Call" and the received report,
RRR, or 73. If you are monitoring someone else's QSO, you will not be
able to decode its Sh messages.
Short ("Sh") messages in MSK144 are intended primarily for 144 MHz,
where most pings are short. These messages do not contain full
callsigns; instead, they contain a hash of the entire transmitted
message along with a report. They are not encrypted -- the report is
sent in the clear along with the hash. Short messages are fully
decodable only by the station to whom they are addressed, as part of
an ongoing QSO, because only then will the received hash match that
calculated using the known strings for "My Call" and "DX Call" and the
received report, RRR, or 73. If you are monitoring someone else's
QSO, you will not be able to decode its Sh messages.
An MSK144 signal occupies the full bandwidth of a typical SSB
transmitter, so transmissions are always centered at an offset of
1500Hz. For best results, selectable/adjustable Rx and Tx filters
should be set to provide the flattest possible response over at least
300 - 2700 Hz. The maximum permissible frequency offset between you
and your QSO partner is ± 200 Hz, and less is better.
and your QSO partner is 200 Hz, and less is better.
2. QRA64 is a intended for EME and other weak-signal use. Its
internal code was designed by Nico Palermo, IV3NWV, and implemented in
@ -100,7 +100,9 @@ Final Comments
Remember that you are using an Alpha Release. We will be grateful for
any and all reports from test users that may help us to further
improve WSJT-X. Send your reports to wsjtgroup@yahoogroups.com.
improve WSJT-X. The most helpful reports describe the problem clearly
and include a complete recipe to reproduce it. Send your reports to
wsjtgroup@yahoogroups.com.
Please be patient concerning responses from the development group.
Several of us will be on vacation or otherwise engaged during much of