Browse Source
A strong frame's last pilot is an up-chirp. The detector and sync can lock onto it again within a symbol of the frame's end, the time shift showing as a large frequency offset; nothing follows, so the header fails and a "preamble found, header fail" was reported. Seen once in SDRangel at +17 dB (sync 55 chips before the end, offset -22.8 kHz) and reproduced from the recording at 150 kS/s: two such reports, syncs at -55 and +341 chips from the frame end. The existing check only dropped syncs more than M/2 before the end. A failed candidate whose sync starts before one symbol after the end of the frame just decoded is now a false alarm: not counted, not reported. Candidates there are still tried, so a real frame starting back to back is delivered as before. Decoded frames are identical on all captures; back-to-back frames (gap 0, SF9 and SF7 coherent, clean to -8 dB) decode 6/6 with old and new. make test and tools/check_c.py pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>master
1 changed files with 7 additions and 0 deletions
Loading…
Reference in new issue