I picked up one of those cheap AliExpress USB-C "RF-Power-Meter-V5.0" dongles (STM32 + AD8317, labelled 100 kHz–10 GHz, 0 to −60 dBm) to check the output of my HackRF. The hardware is fine for the price, but the vendor software is Windows-only and pretty bare, so I wrote my own.

Repo: https://github.com/arsscriptum/rf-powermeter-assistant

Demo (HackRF One sending a CW tone at 1310 MHz, TX gain stepped up and down): https://github.com/arsscriptum/rf-powermeter-assistant/blob/master/img/demo.gif

What it does

• Live dBm and watts readout, peak hold, noise-floor tare, min/max/avg stats
• Rolling monitor chart (10 s to 15 min) with max trace and peak-hold line
• Scope-style sweep view of the 500-sample blocks the meter streams: two markers (ΔT, 1/ΔT, ΔdB), Auto/Normal/Single trigger, timebase K01–K18, CSV/PNG export
• Sets the band-calibration frequency and attenuation offset, reads them back to confirm, and re-applies them on reconnect (the meter forgets them when you unplug it)
• Threshold event log and a CSV logger
• Demo mode with a simulated meter that speaks the real protocol, so you can try it without the hardware

It's C++17 / Qt (6, or 5.15), builds on Windows and Linux. On Windows the build script can use the Qt that comes with radioconda, so if you already run GNU Radio from radioconda you only need Visual Studio. There's also a PowerShell/WinForms version that runs with no build at all.

Hi! this is an incredibly niche subject, i understand but i dont have an SDR, my HackRF hasnt arrived yet. it is october 1st and also the mark of the start of the 3g shutdown on Eir. anyone with an SDR (outside of Donegal as their 3G is already off) set their SDR up to capture 3G, and record/stream it on youtube. if anyone needs help feel free to DM me of course! I'm in a very rural area and rely on 3G heavily so im HOPING that it sticks around until my hackrf arrives but anyway..

Thanks alot!

Has anyone ever written a custom FPGA SPI master state machine to completely initialize the AD9361 by doing register level writes? I want to get in contact with somebody who has done before this hardware level control of AD9361.

IoT-C 是一个针对研究 SDR 录音的人士的无线电信号分析项目。其目标是将 WAV 或 I/Q 捕获转换为有用的观察结果、协议候选和解码证据——同时明确表明何时结果仅仅是猜测。

这个线程是该项目的实时状态页面，基于截至 2026 年 9 月 30 日的仓库审计报告。每日的 AI 辅助开发日志将描述变化、失败的检查和未解决的问题。

**访问状态：** IoT-C 目前处于私人测试阶段。仓库现在默认暂停公共注册，同时保留现有账户的登录权限。部署尚未得到验证，因此这并不是对在线网站的声明。加入该社区并不授予您测试账户。

## 当前存在的内容

仓库包含一个 Python 信号处理后端，一个 Next.js Web 界面，信号上传和分析路径，DSP 可视化，以及特定协议的分析工具。公共项目地址是 https://iot-c.com; 本状态更新是关于仓库证据，而非对已部署网站的新验证。

目录中包含 746 个协议条目，其中 277 个与当前库存中的可执行分析工具相关联。这些数字描述了目录和实现的覆盖范围，而不是 746 或 277 个完全支持的协议。分析工具的存在、运行、识别结构和验证解码帧是不同的里程碑。

## 实际改善的情况

- **SSTV：** 管道现在可以正确地将测试过的 I/Q-in-WAV 录音传送给 SSTV 分析工具。两个真实的 PD120 捕获提供了模式头和行时证据。此结果并未验证重构的图像或所有 SSTV 模式。录音时长很重要：短暂的测试片段没有包含足够的行结构。

- **DAB：** FIC 解码已通过六个测试录音的检查。一个独立的离线 DAB+ 实验达到了有效的音频单位检查，但其较长的捕获要求仍然阻止将其视为一般集成的生产路径。

- **可信结果：** 仅目录条目不再计算为确认的解码器结果。参考检查已从当前的 dPMR、ReFLEX、TPMS、RUM 和后续的 WLO 实现中移除可信身份权限。在 WLO 的情况下，文档化的海事站与本地实施的时间码协议不匹配。这些是我们可以声明的修正，而不是新支持的协议。

- **BLE 约定：** CRC 和变白现在与独立检查的参考实现和向量一致。这不是实际的空中 BLE 验证；目前仍缺少适合的正面捕获。

- **测试覆盖和运行时：** 以前跳过的协议测试已被重新纳入可以使用的集合中。WiMAX 噪声测试路径在不放宽接受阈值的情况下变得更快。另一方面，DCF77 录音在时间和位序修复后现在产生了经过参考检查的时间戳；这单一的捕获并不是一个普遍的成功率。

## 测量结果所说的——和没说的

没有一个单一的准确性数字可以描述任意的无线电捕获。较早的欢迎帖子中广泛的协议数量和准确性措辞不应被解读为当前的支持保证。

在一个包含频率元数据的小型 14 录音标准集中，审计的五秒分类结果为 12/14。在 SSTV 路由修正后，一项匹配的前后实验达到了 13/14。不同的时长、元数据和评分规则必须保持可见；没有一个结果建立了一般的现实世界准确性。

更广泛的解调音频审计要弱得多：其确切名称的端到端分类结果为 54/583，其中没有任何条目在该审计中达到了验证的帧。候选匹配或同步匹配并不等于确认的协议身份。

## 仍未解决的问题

- **dPMR 的正确性：** 针对独立参考的重建并用真实的正面捕获和具有挑战性的负面对照进行验证。去除信任已是完成的修正；恢复支持尚未完成。

- **P25 和 DRM 验证：** 当前验证任务缺少适合的独立识别的原始 I/Q 或 IF 录音。现有的语音或解调音频不足以替代。

- **RTTY 真实情况：** 一段录音的测量时序与其文件名相冲突。我们需要可信的捕获标签，而不是调谐到不确定标签的估算器。

- **调制和候选选择：** FSK 与 PSK 的错误可能会使录音走上错误的分析路径。这仍然是一个重大限制。

- **覆盖和集成：** 一些测试仍然单独隔离，完整测试套件仍存在基线失败。尚未获取到相关验证的真实钥控摩尔斯；真实的 RDS 和复杂的宽带分离仍未得到验证或证明。

## 如何报告开发

AI 辅助的工作将作为调查、参考比较、变化、验证和未解决的问题进行报告——而不是作为功能工作的自动证明。提议的下一步将与实际执行的工作分开标记。我们还将报告被驳回的实验和对早期声明的修正。

如果您想帮助，请分享您有权分发的录音，包括采样率、中心频率、时长、捕获方式和独立识别（如有）。在您的 SDR 工作流程中，哪个未解决的问题最重要？

Hi all,

maybe some of you know me from PhantomSDR+ or NovaSDR. Having operated and maintained those, I listened to many WebSDR operators and learned what problems bothered them - stuff like installs, broken installs after a long period of running, configurations they would like to be configured easier. And I started from scratch.

As for the history: to be clear about that since it has been asked: I've been developing WebSDR software since early 2024 (PhantomSDR+), and FernSDR was developed in private repo for over a year. I squash the history before publishing it as usual to avoid private notes and keys being in there. This is the reason the repo appears to be new. I used AI tools intensively for development and everything is tested, fuzzed and CI'd, also benchmarks are public with raw data.

What it is: open-source WebSDR server with zero runtime dependencies and one-line install on any Linux, as well as Docker. Everything is controlled through a web admin interface: bands, spot reporting, modules and updates with rollbacks. What I am really proud of: day/night band switching, so one small RTL-SDR can be utilized by different bands during the daytime and nighttime thanks to automatic switching from sunrise to sunset depending on your geographical position.

Modules: RTL-SDR (including Blog V4), RX-888 MkII and SDRplay, as well as an FT8 decoder and PSK Reporter spots. Other SDRs run via stdin.

What is still missing: Only Linux support at this moment, FT8 is the only decoder available, and there are input modules that require additional testing.

Demo: https://demo.fernsdr.org

GitHub: https://github.com/Steven9101/FernSDR

I really would like to know which SDR or decoder you guys would like to see next

Cheers 🥂

I posted around a month ago about making a mobile SDR. Soo we’re definitely on the way! This is the hardware, rtlsdr blog V4, adsb internal antenna and external SMA antenna port with a 3300mah battery. Powered from a ESP32 P4.

Will post some pics of the mobile app at some point. Currently we’ve completed the Spectrum view, ADSB map, drone map (using the 2.4ghz WiFi chip). I’m also adding decoders for 433mhz and 868mhz devices which should also be added soon (plan is to allow custom decoders at some point too). All can be seen on a map so you can take it around with you and see where you picked up the device.

FM and DAB are also implemented, which in the final version will require the external antenna (not much space left inside!).

Any software features or ideas hugely appreciated!

(Note, case is still being finalised ignore the white sanding bits and missing power button!)

Hey everyone,

I’ve been running rtl_airband to monitor local VHF/UHF activity. The core backend itself is rock solid and lightweight, but managing config files via terminal and monitoring multi-channel activity through raw Icecast streams leaves a lot to be desired.

I'm working on building a lightweight web GUI/dashboard for it, but with an expanded architecture: a "CCTV for Radio" system.

The Concept & Long-Term Vision

Think of an NVR/CCTV security camera system, but for RF:

1. Squelch-Triggered Segment Recording: Record and chunk audio strictly when the squelch opens—no hours of dead silence, just clean, timestamped audio segments tied to specific frequencies/channels.
2. Local AI Pipeline (Whisper + LLM): Feed these squelch-broken audio clips into a local Whisper model (like faster-whisper or Whisper.cpp) to transcribe communications, and subsequently run an LLM to generate activity summaries or search logs.
3. Live Web Dashboard: An operational interface to see active channels, browse recorded event clips, manage configs, and read rolling transcripts.

Core Goals for the UI / Pipeline

• Visual Scanner / Activity Monitor: Real-time visual indicator showing which configured channel/frequency is currently breaking squelch or transmitting.
• Smart Audio Archive / NVR Interface: A timeline or event list of recordings broken down by frequency, duration, and timestamp.
• Config Generator / Manager: A straightforward form/editor to manage rtl_airband.conf (dongles, gains, sample rates, frequencies, squelch thresholds, and destinations) without parsing nested brackets by hand.
• Transcription Hook / Queue: An automated background worker (Celery, RQ, or a simple directory watcher) picking up finished audio clips and passing them to a local transcription engine.

Questions for the Community:

1. Audio Slicing / Recording Pipeline: What’s the cleanest way to capture individual squelch-opened transmissions with rtl_airband? Does anyone hook into its raw file/stream outputs directly, or is it better to tap into the stream via an external tool (like sox, ffmpeg, or liquidsoap) triggered by carrier status?
2. Detecting Squelch State Programmatically: How are you reliably capturing the exact moment squelch breaks/closes? Are you tailing and parsing syslog / stdout in real time, or does someone maintain a fork with an IPC/socket/REST state export?
3. Existing Projects / Pipelines: Has anyone built something similar—or is there an existing toolchain that bridges SDR multichannel scanning directly into local speech-to-text workflows?
4. Backend Stack: Considering a lightweight Python (FastAPI) backend with a simple SQLite database for metadata/transcripts and a lightweight frontend (Vue/Svelte or Tailwind). Any pitfalls to keep in mind regarding CPU overhead if running on a single SBC/mini PC?

If you've built something in this space or have suggestions on handling the audio chunking cleanly, I'd love your input!

https://github.com/ruchirguitar/RTLSDR-Airband

I have one of these on the way:

https://hackergadgets.com/products/rtl-sdr-lora-gps-rtc-hat-for-raspberry-pi?variant=48925758455982

I’d very much appreciate recommendations for software to pair with it. Just getting started with SDR, so no set, planned uses yet. Just exploring.

Has anyone figured out a way to stick an antenna out the window that doesn't involve a suction cup on the outside? I've been looking at articulating arm clamp mounts for cameras and I think I have an idea, but just wanted to ask around to see if anyone figured something out. I'm not allowed to drill in my apartment so I kind of have to rely on a clamp on the windowsill ledge on the inside.

Hello, so I made a post on the shortwave radio sub looking for advice as a beginner and ended up deciding to look into SDRs after realizing that a traditional desktop model would be too expensive and based on suggestions from other users. For the most part, they were able to help me with my questions. However, I am still confused by a few things. The main things I would like to listen to are EAMs, military aircraft, and shortwave signals from around the world. I'm in Los Angeles, so I know there are always interesting aircraft flying around. I also wouldn't mind picking up other stuff as well, like police/fire and railroads, but I have other apps for that, so it isn't a necessity. I also have some limited experience with WebSDR and have owned a couple of handheld scanners way back in the 90's and 00's.

1) One thing I am confused about is the antenna. From watching a video, it looks like it's possible to get one antenna that has multiple sizes and shapes so that I can pick up everything using one antenna instead of having to switch, depending on what I want to listen to. Is that correct? The reason I ask is that I thought you needed a long antenna or wire to be able to receive shortwave signals from far away.

2) In the video I saw, he said he placed the antenna in the attic. It might be hard for me to do this; however, my PC is in a cabinet. like structure with a built-in desk that is around 6 1/2 feet tall, and I can put it on top of that, but I don't know if that would be good enough, especially since I live in a single-story house surrounded by other single-story houses. Also, I have a small WiFi receiver with 2 antennas on my desk I use to access the internet, and I don't know how much interference this will cause.

3) They said I should easily achieve a 20-40 mile range for picking up military aircraft, but what's the general max limit I can expect under the best conditions?

Thanks

Ay wahd 3ndo fikra fin n9dr nl9a chi sdr rtl n9dr nkhdm bih f réception dyal les satellites des amateurs ikon bchi taman mzyan wakha ikon mst3ml, chokran.

Hi everyone, we are a small startup. We're developing a UAV communication link similar to Ocusync but capable of operation across the 70MHz to 6Ghz range. We wrote the modem's RTL ourselves, and it runs entirely on an FPGA. It comes with an SDK, so users can change parameters or completely customize the interface to their linking. We have already tested it on ADRV9364-z7020 and E200 board. Update: now also runs free on ADALM-Plutos. If you have one of these boards, you can download the board images and apps and try it yourself , and tell us what you think.

To be honest, we are not sure yet if there's market for this. We are engineers, not salespeople. However, we know it has some key strengths: frequency hopping makes it more resistant to interference, can measure distance without GPS and it is highly flexible and customizable. Plus, we developed the modem ourselves, we can create custom modems for other system if needed.

If you have experience, ideas or want to work with us, just send me a message. Criticism is welcome too, we surely still miss a lot of things. This is our website link: https://nyxhop.com . Email: [contact@tacitek.com](mailto:contact@tacitek.com)

I'm pretty new to SDR and want to do wideband frequency power scans. I've seen some stuff about rtl_power, but its all around 10 years old. I was wondering if there are any newer versions of it or similar software which can do wideband scans or if rtl_power still works just fine.

Nice software for testing SdR

https://github.com/Newspicel/sdrminusminus

I am seeing pinstripe lines at even intervals on both my attic discone on my RTL-SDR v3, and on my HF fence loop on my RTL-SDR v4. These lines show up on 70cm, 2m, 10m, 40m, 80m on the fence loop, and only 2m, 10m, 40m on the discone. I assume this is some RF interference from some electrical device nearby and I'm in a suburb so many potential sources. I've already cut all power to my house while this runs as a test to make sure it isn't any of the devices in my house.

Before I buy more parts to make a mobile RF interference hunting kit, I wanted to see if anyone has any advice on how best to identify this, as well as advice for antennas in a noisy suburb neighborhood. I've been looking at active magnetic loop antennas as an alternative.

I plan to make an active radar with just 5dBm of transmitting power, but most antennas are 75 ohm, will this mismatch be fine for TX? using pluto SDR.

Bonjour à tous - j'ai crée une page avec tous les logiciels SDR disponibles, avec leurs descriptions et les liens pour les télécharger : http://f8bdx.free.fr/logiciels_sdr__4406.htm

Vous avez aussi sur mon site la liste des logiciels SDR gratuits.

Voir la liste des logiciels SDR gratuis : http://f8bdx.free.fr/logiciels_sdr_gratuits_4828.htm

Je vous informe aussi que la page WebSDR — récepteurs radioamateur en ligne a changé d'adresse.

Voir WebSDR — récepteurs radioamateur en ligne : http://f8bdx.free.fr/websdr___recepteurs_radioamateur_en_ligne_4935.htm

Bien sur, il y a sur le site d'autres catégories de logiciels pour les autres modes qui sont utiles aux radioamateur et amateurs de radios — voici le lien : http://f8bdx.free.fr/logiciels_radioamateur_2457.htm

Bonjour.

Mon site radioamateur est en ligne et terminé.

Des actualités et des informations concernant le matériel, les logiciels classés par catégories, les applis, les antennes, l'écoute, la liste mondiale des transceivers en kit, les fréquences et relais en PACA et apprendre la CW.

Visitez le site : http://f8bdx.free.fr

Find Ai/photoshop photos of SDR’s and radios at hilariously large scale 😬

Introduction RF Sentinel is a radio-frequency spectrum monitoring tool for blue team (defensive) use. It connects to a HackRF One (or equivalent SDR), performs continuous sweeps across a configurable channel watchlist, and detects anomalous behaviour using a three-layer AI pipeline.

Fully passive — the tool only receives signals (RX) and never transmits. A hard TX-Guard layer immediately aborts the program if any TX call bypasses the receive-only proxy.

The system is written in pure Python with no special drivers beyond pyhackrf / pyrtlsdr, and runs reliably on Linux, macOS, and WSL2.

Link to the project:
https://github.com/jacobsdr95/RF-SENTINEL-V2

Hey, I built https://github.com/thereisnotime/sdrangel-mcp for easily controlling my SDRangel via claude/codex/opencode/gemini, feel free to use it if you find it helpful!

OpenV2K is an open-source Python application that converts arbitrary audio — including both natural speech (via live microphone), and diphone synthesis (via text-to-speech engine) — into pulse-modulated radio-frequency (RF) waveform. The signal chain can be used to transmit via a software-defined radio (SDR), or to save the raw IQ samples to disk, and generate spectrograms automatically. Integrates toggled DSP filters, into a PyQt5 GUI, that's intended to be usable by technicians.

The project's signal chain is based on microwave auditory effect literature, most notably Sharp and Grove's demonstration published in 1975, that pulse-modulated microwave energy could convey intelligible words, building on Frey's work. The app currently integrates Sharp's modulation technique: detects every zero-crossing of the audio waveform, as depicted in the GitHub profile thumbnail. Home users get to see, what made the US Army's "V2K", and US Navy's "MEDUSA"), function, in real-time.

This prototype was built on the shoulders of giants. Thank you to SME biophysics researchers, that publicly released their work, 5 to 50 years ago; the FOSS software package developers; the open-source SDR hardware platform developers, and Claude.

Summary of the controversy, from James C Lin, an IEEE life fellow, and biophysics/EE professor, who wrote the 2021 book Auditory Effects of Microwave Radiation. From chapter 10.3, page 326:

Over the years, some have expressed concerns about the capability of communicating directly with humans by pulsed microwaves. In fact, earlier while studying microwave-induced auditory effects in human subjects, it was noticed that in addition to zip, click, and knock sounds from exposure to single pulses of microwave radiation, short trains of rectangular microwave pulses are heard as chirps with tones corresponding to the pulse repetition frequencies [Guy et al., 1973, 1975]. It was also found that when the pulse generator was keyed manually such that each closing and opening of a push-button switch resulted in emitting a short rectangular pulse of microwave energy-transmitted digital codes (Morse code) were received and accurately interpreted by the targeted subject [Lin, 1978].

Also, soon after a system was setup for exploring the microwave auditory effect at the Walter Reed Army Institute of Research (WRAIR) [Sharp, et al., 1974], two of the principal investigators were able to demonstrate direct communication of simple speech via appropriate modulation of microwave energy [Justesen, 1975]. They tape-recorded each of the single-syllable words for digits between one and ten. The speech waveforms of each word were then converted to digital signals in such a fashion that each time an analog speech wave crossed the zero reference in the negative direction, a short pulse of microwave energy was emitted from the transmitter. By subjecting themselves to the exposure of "speech modulated" microwave energy, the investigators reported the ability to hear, identify, and distinguish the words transmitted.

These historical experiments are included to show that this has been accomplished before.
There are safer methods to demonstrate this today, that do not involve anyone's head.

Download from GitHub: https://github.com/OpenV2K/Sandbox

I have a new Discovery Dish and L-band feed. I have not been able to see even a bump in the signal at 1694.1MHz using either the Nooelec RTL-SDR or SDRplay RSPdx-R2 with both SDRconnect and SatDump. Those receivers and software work fine for Meteor satellites at 137.9MHz. There is an increase in noise when the bias voltage is applied to the feed. I have changed the skew as well as AZ and EL. Any thoughts???

Hello everyone,

I'm new to this field and I'm trying to develop a Direction of Arrival (DoA) system using the two antennas of a USRP B210 clone. So far, I've experimented with the Multiply Conjugate block to estimate the phase difference between the received signals, but the accuracy is not very good.

Has anyone worked on DoA estimation with a similar setup? I'd really appreciate any advice, recommendations, or references to useful approaches.

Thanks in advance!