Listen to FT8: fifteen seconds of everybody at once
A new section, alongside the aircraft, the weather sensors and APRS. FT8 is the odd one out among the things this program listens to, and the reason is worth stating because it shapes everything below. Every station on the band transmits in the same quarter-minute slots, on the same dial frequency, fifty hertz wide each, stacked across three kilohertz of audio. One receiver parked on one frequency therefore hears the whole band's worth of stations at once -- and hears most of them well below the noise, because half of what is sent is error-correcting code. That is the entire trick: a rate of about one half buys a mode that decodes twenty-odd decibels under what an operator can hear. A receiver that took the loudest tone of each symbol and hoped would decode almost nothing, which is why the tone detector reports how confident it is bit by bit rather than what it thinks it heard. Written from first principles except for two tables. The checksum, the belief propagation over the sparse graph, the Costas sync search, the waterfall, the soft-bit metric, and the seventy-seven bits that hold two callsigns and a grid square are all here. The generator and the parity-check matrix are not: they cannot be derived, being the code itself rather than consequences of anything, so they are taken from ft8_lib under its MIT licence with the attribution it asks for, and said so in the readme, the manual and the file. No decoding logic came with them. That the two agree -- and they are not derivable from one another, the generator's parity half running to fifty-odd bits a row against the sparse matrix's six or seven -- is a test rather than an assumption. Tested against the air, not against itself. Eleven off-air recordings with published decodes: ninety-seven of a hundred and fifty messages, no false decodes, timing within a hundredth of a second, frequency within a hertz, signal reports within half a decibel on average. The third not decoded are the weakest in each slot; a mature decoder subtracts what it has decoded and looks again in the remainder, and does ordered-statistics decoding where belief propagation fails, and neither is built here. What is here decodes nothing that other receivers did not also hear, which is the property that matters in a log. Ten whole codewords lifted off the air are in the tests as a permanent fixture, so the recordings can go missing and the regression cannot. Three things that looked like bugs and were not, and three that were. The half-second timing discrepancy was the convention: a transmission is 12.64 seconds in a slot of fifteen and everybody starts half a second in, so lateness is reported against that. Synthetic signals at known offsets proved the clock self-consistent before anything was changed. The signal reports were twenty-one decibels optimistic because those recordings have a receiver passband above three kilohertz, putting a whole-band median twelve to sixteen decibels below the real noise floor -- so noise is now measured beside the signal, and in the tone that was actually sent rather than the loudest of eight, the largest of eight noisy numbers being well above their mean even with no signal at all. And the test transmitter was thirteen decibels pessimistic, scaling its noise into a fifty-hertz reference instead of the sampled bandwidth, which made the decoder look deaf when it was the test signal that had been quietly attenuated. The real bug the simulator caught was a one-block timestamp error: samples were dated a block earlier than they were taken, which slid every slot slice a second late and cut the first half-second -- three symbols, part of the opening Costas array -- off every transmission on the band. One decode a slot became six. Reachable both ways, as everything here is. Twenty-one options, every one of them a command-line flag and a line in the menu, both built from one table so they cannot disagree -- and a test that says so, since an option in no group would be settable from the command line and invisible in the menu. The band list says which channels a plain dongle can reach and which need an upconverter, because almost all the activity is on shortwave and finding that out by listening to silence for ten minutes is the wrong way to learn it. The default is two metres, which a plain dongle can hear. --grid turns decodes into geography: every CQ says where it is, so each gets a distance and a bearing and the furthest is named. --adif writes the log in the form every amateur logging program imports, marked as heard rather than worked, because nothing here transmits and an ADIF that let a logging program treat these as contacts would put claims into somebody's log that they cannot make. One bug shipped and found by being used rather than by being tested: the line that opens the receiver called a function this program has never had. Every test reached it through the simulator, which takes the other branch, so the one line that matters to somebody with an aerial was the one line never run. There is now a check that every name these modules import actually exists -- it names the missing one rather than failing somewhere downstream -- and two that say a receiver which cannot be opened is reported rather than raised, and that nothing claims to be listening before there is one. It had been announcing the frequency first, so a dongle that would not open read as listening that had gone wrong. Ninety-six new tests. Full suite 2781 passed. Built as 2026-09-21_04. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016PsWPTweCT6pwxKngvVxcg
This commit is contained in:
parent
e203b3e581
commit
93120b80a6
14 changed files with 4247 additions and 3 deletions
|
|
@ -77,6 +77,13 @@ def aprs_section() -> list[str]:
|
|||
return options_section(ap)
|
||||
|
||||
|
||||
def ft8_section() -> list[str]:
|
||||
"""Every FT8 option, from the same table again."""
|
||||
from bandsaunter import ft8
|
||||
|
||||
return options_section(ft8)
|
||||
|
||||
|
||||
def options_section(air) -> list[str]:
|
||||
"""One section's options, written out from the table the program uses.
|
||||
|
||||
|
|
@ -1792,6 +1799,58 @@ Every option the APRS side takes, in the four groups the menu shows them in.
|
|||
Each is a flag here and a line in the menu, and both come from one table in
|
||||
the program, so they cannot disagree.
|
||||
.APRS_OPTIONS_HERE
|
||||
.SH FT8
|
||||
Fifteen seconds of everybody at once. Every station on the band transmits in
|
||||
the same quarter-minute slots, on the same dial frequency, fifty hertz wide
|
||||
each, stacked across three kilohertz of audio \[em] so one receiver parked on
|
||||
one frequency hears the whole band's worth of stations at the same time, and
|
||||
hears most of them well below the noise.
|
||||
.PP
|
||||
Half of what is transmitted is error-correcting code, and that is the trick:
|
||||
it is what buys a mode that decodes twenty-odd decibels under what an operator
|
||||
can hear. A receiver that took the loudest tone of each symbol and hoped would
|
||||
decode almost nothing, which is why the tone detector reports how confident it
|
||||
is bit by bit rather than what it thinks it heard.
|
||||
.SS What it needs
|
||||
The clock has to be right to a second or two. The slots are quarter-minutes of
|
||||
UTC and every station on earth agrees about which one it is. A receiver a
|
||||
second out still decodes; one a slot out hears every transmission split across
|
||||
two captures and decodes none of them. This is the one failure that looks
|
||||
exactly like a dead band, so the display and the report both say so when
|
||||
nothing arrives.
|
||||
.PP
|
||||
Almost all the activity is on shortwave, which a plain receiver of this kind
|
||||
cannot reach. The default is therefore the two-metre channel at 144.174 MHz,
|
||||
which it can. All thirteen channels are in the list and the shortwave ones
|
||||
work through an upconverter or a receiver in direct sampling mode; the menu
|
||||
says which is which rather than leaving somebody to find out by listening to
|
||||
silence.
|
||||
.SS What comes out
|
||||
.BI \-\-grid " SQUARE"
|
||||
is what turns decodes into geography: every station calling CQ says where it
|
||||
is, so with your own square filled in each gets a distance and a bearing and
|
||||
the furthest heard is named. Three tables afterwards \[em] stations heard,
|
||||
calling CQ, and who was working whom.
|
||||
.PP
|
||||
.B \-\-adif
|
||||
writes the log again in the form every amateur logging program imports,
|
||||
marked as heard rather than worked. Nothing here transmits, so nothing here is
|
||||
a contact, and an ADIF that let a logging program treat these as worked would
|
||||
put claims into somebody's log that they cannot make.
|
||||
.SS How well it works
|
||||
Checked against eleven off-air recordings with published decodes, which is the
|
||||
only honest way to test a decoder: an encoder tested against its own decoder
|
||||
agrees with it about anything they are both wrong about. Ninety-seven of a
|
||||
hundred and fifty messages, with no false decodes; timing within a hundredth
|
||||
of a second, frequency within a hertz, signal reports within half a decibel on
|
||||
average. The third not decoded are the weakest in each slot: a mature decoder
|
||||
subtracts what it has decoded and looks again in the remainder, which is not
|
||||
built here.
|
||||
.SH FT8 OPTIONS
|
||||
Every option the FT8 side takes, in the five groups the menu shows them in.
|
||||
Each is a flag here and a line in the menu, and both come from one table in
|
||||
the program, so they cannot disagree.
|
||||
.FT8_OPTIONS_HERE
|
||||
.SH FILES
|
||||
.TP
|
||||
.I ~/.config/bandsaunter/config.yaml
|
||||
|
|
@ -1924,6 +1983,16 @@ terms, in
|
|||
or at
|
||||
.UR https://www.gnu.org/licenses/
|
||||
.UE .
|
||||
.PP
|
||||
One file is not original work.
|
||||
.I ft8tables.py
|
||||
holds the two fixed tables that define the FT8 error-correcting code, taken
|
||||
from ft8_lib (https://github.com/kgoba/ft8_lib), MIT licensed, copyright 2018
|
||||
K\[u0101]rlis Goba, which took them in turn from WSJT\-X. They are reproduced
|
||||
under the MIT terms and that file carries the attribution they ask for. They
|
||||
are there because they cannot be derived: everything else about FT8 here is
|
||||
worked out from first principles, but those two tables are the code itself,
|
||||
chosen once by its designers and published. No decoding logic was taken.
|
||||
.SH BUGS
|
||||
The DVB-T television driver claims these dongles on sight. If the receiver
|
||||
cannot be opened, that is almost always why: the package blacklists the
|
||||
|
|
@ -1944,6 +2013,7 @@ def main() -> int:
|
|||
text = text.replace(".WEATHER_OPTIONS_HERE",
|
||||
"\n".join(weather_section()))
|
||||
text = text.replace(".APRS_OPTIONS_HERE", "\n".join(aprs_section()))
|
||||
text = text.replace(".FT8_OPTIONS_HERE", "\n".join(ft8_section()))
|
||||
text = text.replace("\n\n", "\n") # troff dislikes blank lines
|
||||
target = Path(sys.argv[1] if len(sys.argv) > 1
|
||||
else Path(__file__).parent / "bandsaunter.1")
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue