ⓘ Callsign lookups are in real time via the FCC database.
Vanity callsign availability is refreshed daily at 6:00 AM CST.
The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cmvia PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHzDXSpotterInfo
Recent spots—
Select a band above to load spots
Ready — select a band to fetch live spots
Raspberry Pi 4 WSPR beacon drifting on Si5351 - GPS sync working but frequency unstable
Built a multi-band WSPR beacon using RPi 4, Adafruit Si5351 breakout, and u-blox NEO-6M GPS module. GPS sync is solid, timing is perfect, but I'm seeing significant frequency drift on all bands - roughly 15-20 Hz over a 2-minute transmission cycle.
Currently running the VK3HN Arduino sketch ported to Python with JT65encode library. The Si5351 is running at default 25MHz reference with no TCXO upgrade.
Beacon transmits properly and gets decoded
Frequency starts on-target then drifts high
Temperature doesn't seem to correlate with drift pattern
Has anyone successfully compensated for Si5351 drift in software, or is a TCXO upgrade the only real solution for stable WSPR?
Built a multi-band WSPR beacon using RPi 4, Adafruit Si5351 breakout, and u-blox NEO-6M GPS module. GPS sync is solid, timing is perfect, but I'm seeing significant frequency drift on all bands - roughly 15-20 Hz over a 2-minute transmission cycle.
Currently running the VK3HN Arduino sketch ported to Python with JT65encode library. The Si5351 is running at default 25MHz reference with no TCXO upgrade.
Has anyone successfully compensated for Si5351 drift in software, or is a TCXO upgrade the only real solution for stable WSPR?
Link to comment
https://www.hamradiobase.com/forums/topic/260-raspberry-pi-4-wspr-beacon-drifting-on-si5351-gps-sync-working-but-frequency-unstable/Share on other sites