rpitx/ft8_lib
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Updated with focus on FT8 v2 (v1 is gone pretty much)

Browse source
This commit is contained in:
Karlis Goba 2018-12-22 15:35:10 +02:00
parent 6eaf85f86c
commit 4e5bd7ce69
1 changed files with 9 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
README.md
View file

@ -4,31 +4,30 @@ A C++ implementation of FT8 protocol, mostly intended for experimental use on mi
The encoding process is relatively light on resources, and an Arduino should be perfectly capable of running this code.
The intent of this library is to foster experimentation with e.g. automated beacons. FT8 already supports free-text messages and the upcoming new version will support raw telemetry data (71 bits).
The intent of this library is to foster experimentation with e.g. automated beacons. For example, FT8 supports free-text messages and raw telemetry data (71 bits).
Work is in progress (possibly taking forever) to explore decoding options. On a fast 32-bit microcontroller decoding might be possible, perhaps with some tradeoffs.
# What works
So far only encoding is implemented. It should support the basic set of FT8 version 1 (75-bit) messages:
Currently the basic message set of the revised FT8 protocol with 77-bit payload (introduced since WSJT-X version 2.0) is supported:
* CQ {call} {grid}, e.g. CQ CA0LL GG77
* CQ {xy} {call} {grid}, e.g. CQ JA CA0LL GG77
* {call} {call} {report}, e.g. CA0LL OT7ER R-07
* {call} {call} 73/RRR/RR73, e.g. OT7ER CA0LL 73
* Free-text messages (up to 13 characters from a limited alphabet)
I am working on the revised FT8 protocol with 77-bit payload (introduced since WSJT-X version 2.0), and currently the library supports the basic message set:
* CQ {call} {grid}, e.g. CQ CA0LL GG77
* CQ {xy} {call} {grid}, e.g. CQ JA CA0LL GG77
* {call} {call} {report}, e.g. CA0LL OT7ER R-07
* {call} {call} 73/RRR/RR73, e.g. OT7ER CA0LL 73
So far only encoding is implemented. There is historical code that supports the same set of FT8 version 1 (75-bit) messages plus free-text messages.
# What doesn't
I'm currently working on these features:
* Encoding free-text messages (up to 13 characters from a limited alphabet)
* Encoding telemetry data
* Decoding
These features are low on my priority list:
* Encoding contest mode messages
* Encoding extended range signal reports (<-30dB or >=0dB S/N)
* Encoding compound callsigns with country prefixes and mode suffixes
* Decoding (working on it)
# What to do with it