mirror of
https://github.com/saitohirga/WSJT-X.git
synced 2024-09-28 16:16:48 -04:00
40 lines
1.5 KiB
Plaintext
40 lines
1.5 KiB
Plaintext
|
To Do for FT8++
|
||
|
---------------
|
||
|
|
||
|
The following list is for informtion and general guidance. Everything
|
||
|
is subject to revision!
|
||
|
|
||
|
1. Nomenclature and parameters for message types
|
||
|
- Old-style = classic 72-bit JT-style source-encoding
|
||
|
FT8: (174,87) code: 72-bit info, i3bit, CRC12, itype=1 sync
|
||
|
MSK144: (128,80) code: 72-bit info, CRC8
|
||
|
- New-style
|
||
|
FT8: (174,91) code: 74+3+14, sync uses itype=2
|
||
|
MSK144: (128,90) code: 74+3+13
|
||
|
|
||
|
2. (K1JT) For backward compatibility (good for, say, 6 months only?),
|
||
|
by default we'll generate old-style messages where possible, new-style
|
||
|
messages where they are needed. We'll decode both old and new types.
|
||
|
|
||
|
3. (K1JT -- DONE) Two new checkboxes on Advanced tab to enable 77-bit
|
||
|
messages:
|
||
|
- "Always generate new-style (77-bit) messages."
|
||
|
- "Decode only 77-bit messages
|
||
|
|
||
|
4. (K9AN) New-style messages can be as long as 37 characters. We'll
|
||
|
need to allow for that in a number of places.
|
||
|
|
||
|
5. (K9AN) Subroutine genft8() will need to parse the message to be
|
||
|
transmitted, determine the effective message type i3 and possibly
|
||
|
subtype, n3. It will then generate itone, calling genft8_174_91(() if
|
||
|
needed.
|
||
|
|
||
|
6. (K1JT) Code to generate the user-readable messages for each
|
||
|
specialized type of operating, e.g., NA VHF contest, EU VHF contest,
|
||
|
ARRL Field Day, ARRL RTTY Roundup, use of goofy calls.
|
||
|
|
||
|
7. (??) Code to do the necessary auto-sequencing for each specialized
|
||
|
type of operating.
|
||
|
|
||
|
8. (??) What's needed for MSK144 with LDPC(128,90) ?
|