With RFix
- Place emitters and a receiver on the RF map.
- Connect signals, interference, and ITU-R or Sionna paths.
- Inspect the IQ and export labels, SigMF, and the source project.
Desktop Startup
Loading interface...
Preparing the renderer process.
RFix vs GNU Radio
RFix keeps visual design, maps, ITU-R and Sionna propagation, interference, IQ analysis, labels, SigMF, instruments, batch APIs, and MCP in one repeatable project. GNU Radio offers powerful real-time SDR and custom DSP flowgraphs, but a comparable scenario-to-dataset workflow requires more blocks, scripts, and integration.
RFix advantage: The shortest path from a mapped RF scenario to a traceable IQ dataset.
Choose GNU Radio mainly for: Real-time SDR hardware, custom DSP, and open flowgraphs.
Why choose RFix
RFix removes the integration work between scenario design, propagation, IQ analysis, datasets, and automation.
You want maps, terrain, propagation, interference, labels, analysis, and exports produced from one repeatable project.
You need dataset variants generated over an API or MCP without maintaining a custom flowgraph pipeline.
You want measured and synthetic IQ, recording metadata, and scenario configuration to remain traceable together.
Workflow advantage
| Capability | RFix | GNU Radio |
|---|---|---|
| Product scope | Build repeatable RF scenarios from signal design through analysis and export. | Build real-time DSP and SDR flowgraphs for software or connected radio hardware.[1] |
| Block library | 94+ fully included visual signal nodes in one packaged workspace. | 554 documented blocks, mostly low-level DSP and flowgraph building blocks, plus extensions.[7] |
| Visual authoring | Drag-and-drop RF blocks, projects, and map placement share one model. | Visual flowgraph editor, but RF systems still require detailed wiring, parameters, and often custom Python/C++.[2] |
| Maps & terrain | Map-authored emitters, receivers, motion, terrain, and height-aware geometry. | No built-in RF map or terrain authoring layer; flowgraphs focus on signal processing.[2] |
| Propagation & interference | ITU-R models, Sionna terrain paths, and composable interference scenarios. | Flexible channel blocks; terrain-aware standards workflows require custom assembly.[1] |
| IQ import & analysis | Integrated spectrogram and time-domain analysis for measured or generated IQ. | Excellent QT GUI time, frequency, waterfall, and constellation sinks.[3] |
| Labels & deliverables | Traceable labels, raw IQ, SigMF pairs, and portable source projects. | Stream tags and file/SigMF sinks; dataset labels and packaging are user-defined.[4][5] |
| Automation & AI agents | Batch APIs and native MCP tools generate, inspect, validate, and export RF projects. | No native MCP-based RF project workflow; automation and extensions use Python or C++.[1] |
| SDR hardware | Built-in desktop SDR discovery, transmit, and receive through SoapySDR, bladeRF, and USRP paths. | Broad live SDR hardware integration for real-time transmit and receive chains.[6] |
| VSG & signal analyzers | Paired VSG/analyzer sessions, waveform playback, measurements, IQ capture, diagnostics, and SCPI are built in. | Lab-instrument control generally requires custom blocks, drivers, or external SCPI tooling.[6] |
| Licensing | Commercial platform with free and licensed capabilities. | Open source and free.[1] |
Concrete workflow
Specialist exception
Choose GNU Radio primarily when one of these specialist requirements matters more than an integrated scenario-to-IQ workflow:
RFix is the faster route from mapped scenario to traceable IQ dataset because maps, propagation, interference, analysis, exports, APIs, and MCP already share one project. Choose GNU Radio mainly for open-ended real-time SDR and custom DSP flowgraphs.
The fastest way to compare is on your data. We can generate a sample labeled dataset from a scenario like yours so you can judge the fit directly.
Explore RFix
Verification
Published ยท Last reviewed