Skip to main content
Archived

This project has been archived by its maintainers, and is no longer receiving any updates.

PyFT8m

An FT8 Receiver, FT8 Transmitter, and GUI, written in three single & short Python files. The Receiver and Transmitter can be run standalone.

Capture2

Features

As of version 1.0.0, the key features are:

  • Written entirely in Python
  • Implements LDPC and OSD decoding
  • Demonstrated by a Tkinter GUI
  • Receiver and Transmitter can be used standalone
  • Internal connections are via UDP (so e.g. alternative Receivers / Transmitters could be easily swapped in)
  • Rx and Tx of standard messages with optional /P and /R
  • Tx uses GFSK waveform as defined in FT8 standard
  • RX of nonstandard calls plus hashed calls
  • Launches quickly (~2 seconds on my old Dell Optiplex 790)
  • Finds sound cards by keywords so follows them if e.g. Windows moves them ...
  • Logs QSOs to user-specified ADIF file
  • Uploads spots to pskreporter
  • Controls rigs via Hamlib's rigctl.exe, which doesn't hog the rig's COM port
  • Click on the spectrum display to set Tx frequency

Design philosophy

This isn't meant to do anything 'better' than applications like WSJT-x and MSHV, but it illustrates what can be done in a very few lines of Python, and it is written to be free of bloat. Currently, the code comprises:

  • Receiver ~ 300 lines, including LDPC and OSD decoding
  • Transmitter ~ 300 lines
  • Tkinter GUI ~ 500 lines

That's an FT8 transmitter / receiver application in about 1100 lines of Python. The Receiver and Transmitter are implemented in single Python files (apart from common use of a small UDP class) and communicate with the GUI only via UDP. The point of doing this is to keep the interfaces here minimal, so that in theory it's easy to swap out either transmitter, receiver, or GUI and replace it with something written in any other language, subject to meeting / adapting the UDP commands reference below.

Installation and use

To use it as a 'turnkey' transceiver, just install the project via pip:

pip install PyFT8m

... and then run the tk_gui either in a Python environment or by using the command:

pyft8mgui

You might have to open a new command window after pip install so that the command 'pyft8mgui' is recognised. I haven't written too much of a step by step quide here, as the project is really intended for people who want to poke around and maybe modify the code. But hopefully even if you're new to Python or coding, you can have a look and work out how it's done.

To control a rig's PTT and frequency, you'll need a copy of Hamlib's rigctl.exe.

Hacking it

The transmitter and receiver may be run independently from the GUI, as they communicate only via UDP (see below). For example, to run the receiver from Python,

from PyFT8m import Receiver
rx = Receiver(output_type = 'print', input_keywords = 'Mic, CODEC')

Or of course copy the receiver.py file, add this line at the bottom (minus the import), and hack away.

UDP messages

The following shows the main points of the way that the UDP messages are constructed - please see the code for the absolute reference.

  1. All UDP messages apart from those sent to pskreporter.info or the waterfall data sent from the receiver to the GUI, are Python dictionaries serialised with JSON and encoded to bytes.
  2. All dictionaries start with a key called 'mtype' meaning 'messsage type'. The main ones are 'decode' (indicating that the dictionary contains various entries from a decoded message), 'shutdown', 'waterfall', 'rollover', 'test_info', 'set_tx_Hz', 'generate_tx_audio', 'send_tx_audio', 'stop_tx_audio'.

As the project grows, I might write a more formal spec for these messages.

Acknowledgements

This project implements a decoder for the FT8 digital mode. FT8 was developed by Joe Taylor, K1JT, Steve Franke, K9AN, and others as part of the WSJT-X project. Protocol details are based on information publicly described by the WSJT-X authors and in related open documentation.

Some constants and tables (e.g. Costas synchronization sequence, LDPC structure, message packing scheme) are derived from the publicly available WSJT-X source code and FT8 protocol descriptions. Original WSJT-X source is © the WSJT Development Group and distributed under the GNU General Public License v3 (GPL-3.0), hence the use of GPL-3.0 in this repository.

Metadata

Release files for PyFT8m 1.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for PyFT8m 1.1.1
File Size Uploaded Provenance Actions
pyft8m-1.1.1.tar.gz 42.2 kB Without provenance Details for pyft8m-1.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for PyFT8m 1.1.1
File Interpreter ABI Platform Actions
pyft8m-1.1.1-py3-none-any.whl Python 3 none any Details for pyft8m-1.1.1-py3-none-any.whl

Total release size: 83.3 kB

Release files / pyft8m-1.1.1.tar.gz

Download URL pyft8m-1.1.1.tar.gz
Size 42.2 kB
Tags Source
SHA-256 checksum
How to use checksums
daace97db252b8877a0c38ee1076c5aba336383697f72330cdf2525361d3a12d
BLAKE2b-256 checksum
How to use checksums
f22c61d84e66b12d40f17fbed2bb995768af0a7e269d3a533dcb8d6d748c25b2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.14

Release files / pyft8m-1.1.1-py3-none-any.whl

Download URL pyft8m-1.1.1-py3-none-any.whl
Size 41.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
92213b228496ec776d364a0d15fddfc25ce9b47dff31281f8e4172793303dea6
BLAKE2b-256 checksum
How to use checksums
aa1ed3a008a22c37da60d3c0d00ff59217c8ea3e12278d805e57e9e6eb1667e8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.14

Security for PyFT8m 1.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page