r/sdr

▲ 21 r/sdr

The new LITEMALADSP MLITE 880 is Amazing!

If you're someone already used to programming SDR Radios the way you like to hear them, you're in for a treat with this one! MalahitTeam has perfected NR and equalization of sound for Shortwave Listeners like Ive never even heard it from the DSP2. This radio is closer to what I imagine the DSP3 being, except at leas than half the price! If you hear alot of radio buffs raving about this one, it's because they're right! This is Top Notch! I've given you a good listen! Listen! If you're going to buy one, buy it direct from Elecevolve! Don't bother with Banggood like some of us did early on! You can get it for $40 cheaper direct! And Download the Firmware and flash it on to the radio! It adds all of the other features that make it even better! I just wished they'd put a shut off timer on it! My only gripe! Otherwise, you're going to love this one!

u/FlakyPrinciple8907 — 4 days ago
▲ 8 r/sdr+1 crossposts

I have a 1 metre V dipole antenna and I’m looking to receive images from a satellite, does anyone know an easy satellite to start with?

reddit.com
u/treemasta99100 — 5 days ago
▲ 1 r/sdr+1 crossposts

Why am I getting a lower quality copy of broadcasts at there frequencies around the broadcast?

For example, I can hear a radio station at 98.2 MHz but then I hear that same station at varying qualities across multiple frequencies up to 99.6 MHz

reddit.com
u/treemasta99100 — 5 days ago
▲ 9 r/sdr

Real-time SDR Spectrum & Waterfall Analyzer with Deterministic Replay and Python Bindings – New Open-Source Tool

Hey r/sdr,

I just open-sourced a tool I've been building because I kept running into the same frustration: analysis results that differ between GUI, scripts, and automated tests.

Meet sdr-signal-analyzer — a deterministic SDR analysis backend focused on reproducible signal inspection.

Key highlights:

  • Same C++ core powers the CLI, GUI, and Python bindings → consistent results everywhere, no more “works in the GUI but not in my script” issues.
  • Deterministic replay from committed SigMF IQ fixtures — perfect for testing, CI/CD pipelines, and sharing reproducible experiments.
  • Simulator-first workflow (no hardware needed to get started) + optional live sources (rtl_tcp already verified in CI, UHD/SoapySDR support in progress).
  • Peak detection, RF feature extraction, JSONL export, peak-hold, waterfall & spectrum view.
  • The GUI is already quite usable and includes recent improvements like peak-hold reset.

It's still early-stage (0 stars, actively developed), but the replay determinism is fully verified in the repo (see docs/proof.md and the committed test fixtures).

Quick install (Ubuntu/Debian example):

Bash

sudo apt install -y cmake g++ libegl1 libxcb-cursor0 libxkbcommon-x11-0 ninja-build python3-dev
python -m pip install ".[gui]"

Then try:

  • sdr-signal-analyzer-demo
  • or sdr-analyzer-cli --source simulator --frames 20

Links:

I’d love honest feedback, bug reports, feature ideas, or contributions — especially from people who care about automation, reproducible RF measurements, or building test pipelines.

Does anyone else miss reliable determinism when switching between tools like Inspectrum, GQRX, or SDRangel?

u/Wonderful-Gap7420 — 4 days ago
▲ 26 r/sdr+2 crossposts

VertexSDR - open source WebSDR-compatible server (clean-room rewrite in C)

https://preview.redd.it/zb4k8344xlvg1.png?width=1891&format=png&auto=webp&s=3841e118c311ecbac7c34505ea7a94c9bddb3c61

Hey,

I’ve been getting less active in the WebSDR scene lately, but this is something I’ve been working on for a few years and wanted to finally release.

The original WebSDR by PA3FWM has been closed source for over 10 years. It’s still widely used, but because of that, people mostly end up patching around it instead of actually building on it.

I wanted to make a proper open alternative that keeps compatibility but is fully independent.

VertexSDR is a WebSDR-compatible server written from scratch in C.

Since the original is closed source, this is a clean-room style rewrite. No code was taken from it, no reverse engineering copy paste. The goal was to match behavior and features so existing setups can migrate easily, while having a fully open codebase going forward.

It uses the official WebSDR frontend, so the UI and workflow are exactly what people are used to.

This took a few years to get to this point.

My goal is and was always working with the community and bringing value.

What you get:

  • Same WebSDR experience in the browser (official frontend)
  • AM, SSB, CW, FM including synchronous AM
  • RTL-SDR via rtl_tcp
  • ALSA, TCP SDR relay, and stdin input
  • Not limited to 8-bit, works with higher resolution IQ
  • FFTW CPU backend and optional Vulkan or VkFFT GPU backend
  • Multi-band with config reload
  • IQ balance correction, noise blanker, per-frequency EQ
  • Logbook and chat
  • Registers to websdr.org and sdr-list.xyz

What’s improved:

  • Fully open source (LGPL)
  • Clean codebase, no legacy patches
  • Fixes issues like raw IP address leaking
  • Adds sync AM, bandplan support, and flexible input (stdin, etc)
  • Not tied to a specific SDR or format
  • Meant to be extended instead of everyone maintaining their own private versions

Quick start (Debian/Ubuntu):

sudo apt install build-essential libfftw3-dev libpng-dev libasound2-dev libssl-dev xxd
make
edit websdr.cfg
./vertexsdr

Open http://localhost:8901

RTL-SDR example:

rtl_tcp -a 127.0.0.1 -p 1234 -f 10100000 -s 2048000 -g 30

In websdr.cfg:

!rtlsdr 127.0.0.1:1234

stdin example:

rx_sdr -f 10100000 -s 2048000 -g 30 - | ./vertexsdr

Current state:

It works and people are running it, but it’s still beta. Needs more testing across hardware and different setups.

The goal is to give the community a real open base instead of everyone running slightly different patched versions.

Binary release for x86 is available. More to come.

Links:

If you try it, feedback and bug reports are very helpful right now.

If you find it useful and want to support development, you can star the repo on GitHub or donate, both links are on the project page.

reddit.com
u/magicint1337 — 7 days ago
🔥 Hot ▲ 55 r/sdr+1 crossposts

Open-source distributed SIGINT system — SDR signal detection + triangulation overlaid on ATAK in real time

https://preview.redd.it/hos0nhl0kkvg1.png?width=1198&format=png&auto=webp&s=4f72d47672ff19625bcdc26ef9e87f8b45abae9b

Been working (mostly vibe coding, not going to lie) on this for a while and figured this community would appreciate it. It's a distributed SDR-based signal detection and triangulation system that streams everything to ATAK as CoT.

What it does:

  • Detects radio emissions across 30+ signal types: PMR446, FRS, Marine VHF, TETRA, P25, keyfobs, TPMS, GSM/LTE, ADS-B, AIS, POCSAG pagers, BLE (including AirTag/Find My tracking), WiFi probe requests, drone RemoteID, LoRa/Meshtastic, ISM-band devices, and more
  • Distributed sensor nodes report RSSI from known GPS positions, 3+ nodes triangulate emitter locations via multilateration
  • Streams detections to ATAK as CoT markers in real time, aircraft, vessels, drones, vehicles, RF emitters all show up on the map with appropriate icons
  • Generates RF activity heatmaps as KML overlays for ATAK
  • Tracks device movement trails as CoT polylines
  • Cross-signal device correlation (finds clusters of devices that always appear together)
  • Voice interception with Whisper speech-to-text on PMR/FRS/Marine channels
  • Modulation classification (FM, OOK, FSK, PSK, QAM, OFDM, no ML/GPU needed)

How it works:

  • Central server (pelican case) with wideband SDRs continuously scans all bands
  • Lightweight sensor nodes (~$80 each: RTL-SDR Blog V4 + GPS + Raspberry Pi zero) distributed across the area (stations or in operators backpacks)
  • Short-burst signals (keyfobs, TPMS, pagers): nodes scan autonomously, triangulation via post-hoc correlation
  • Long signals (voice, GSM): central detects and tasks nodes to tune and measure RSSI
  • Everything logs to per-session SQLite databases, so you can do post-hoc analysis too

Web dashboard, shows live detections with category tabs (Voice, Drones, Aircraft, Vessels, Devices, Cellular...), a Leaflet map, device tracking, correlation analysis, and audio playback with transcripts for voice intercepts. Can also run standalone against historical .db files.

There are still some missing features, like the server to node coms (planned over Meshtastic), hopefully I will be able to implement it as soon as the rest of the hardware arrives.

Hardware:

  • Multiple RTL-SDR Blog V4 (~$30) for most RF
  • Alfa USB WiFi adapter for monitor-mode WiFi/drone detection and BT
  • HackRF One for wideband, TX tests and further plans
  • GPS module
  • Server runs on Raspberry Pi 5
  • Nodes are planned to run on Raspberry Pi zero
  • Power hubs

Stack: Python, no cloud dependencies, everything runs locally. TAK server integration via client certificates.

Code is on GitHub. Happy to answer questions or hear ideas.

https://github.com/arall/sigint

reddit.com
u/mk394 — 7 days ago
▲ 21 r/sdr+1 crossposts

Another experiment [Integrive-100 MIMO SDR] : How far can we push it?

Hi everyone,

Following up on my previous demo, my team and I decided to take the Integrive-100 out for a real-world stress test. I wanted to see how our architecture handles a challenging Non-Line-of-Sight (NLOS) environment in an urban setting.

The Setup:
Distance: 207m (Straight-line distance)
Environment: Dense urban with buildings (NLOS)
Placement: Transmitter on a building rooftop / Receiver at ground level.
Frequency: 915 MHz
Bandwidth: 5 MHz
Modulation: QPSK
FEC: Reed-Solomon (Code Rate: 0.8)
Tx Power: 18.5 dBm

The Results:
Measured SNR: 17 ~ 19 dB
Packet Error Rate (PER): 0.13% (0.0013) No retransmissions
Throughput: 5.5 Mbps

The high SNR margin suggests our RF front-end and signal processing are operating efficiently, leaving significant headroom for more challenging environments or longer distances. At 5.5 Mbps (69% efficiency including slot-based MAC overhead), the link provides enough capacity to support stable, real-time video or audio streaming. Our focus remains on fixing the 'hardware plumbing' so that your algorithms can reach their maximum theoretical potential.

How many of you are also taking your setups out of the lab?
I’d love to compare notes with anyone else doing field work!

[previous post-1] https://www.reddit.com/r/sdr/comments/1rl9zlg/i_got_tired_of_fighting_os_jitter_and_hostpc/

[previous post-2] https://www.reddit.com/r/sdr/comments/1s8l5uz/followup_experiments_on_dualsdr_video_transmission/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

[demo video] https://youtu.be/o-cW08NGJvM?si=G9dUO6K7Hp9IsnIq

u/Life-Luck-3788 — 7 days ago
▲ 2 r/sdr

Rds Blocks

How can i run the rds blocks in vs code claude says i only can on Linux i'm using windows so the rds is not giving me clear output

reddit.com
u/FishermanCharming575 — 4 days ago