Signal Visor opens a recording from 433, 868 or 315 MHz and reads it: where the transmissions are, how long the pulses last, what the modulation is, which protocol it matches and what its fields say. When nothing matches – the usual case with an unknown sensor – it lays the frames out side by side so you can find the structure yourself.
Signal Visor grew out of the ook_sniffer project.
What it reads
.sub RAW filesWindows 10/11, 64-bit · works offline, on files from any receiver · no account, no telemetry
One of the demo recordings that ship with the program, generated rather than recorded: the carrier in the spectrum, the pulse train under it, the protocol it reads as, and the pulse lengths that show a 1 : 3 width code before any decoder runs. Click or tap the picture for the full-size window.
The point of recognising a device is to hand it to something else: an
rtl_433 flex decoder line, ESPHome raw or
rc_switch YAML, an RCSwitch protocol entry for Arduino, a
Flipper Zero .sub to replay, a CSV of every pulse, and PNGs of
the plots for documentation.
Every protocol is a small JSON file with a schema, not code: timing, coding, frame layout, fields and a checksum. Your own definitions go in your own folder and override the built-in ones, so a fix needs no new release. The Protocol workspace edits them with a live preview against the open recording.
A decoder that is sure of itself is easy to write and easy to be wrong with. A short frame without a checksum cannot be told from noise, and a reading that is internally consistent can still be wrong end to end – this program found exactly that in one of its own protocols, and only a second, independent reading of the same signal settled it.
So Signal Visor shows its working. Every candidate carries a confidence and a sentence saying what it is made of. A definition is draft until a real recording has verified it, and a draft is ranked accordingly. Where a figure is an estimate rather than a measurement, it says so.
.cu8, .cs8, .cs16, .cf32,
.iq, .complex, .sigmf-data.sub RAW – pulse timings, no amplitudeWhat it deliberately does not do
It does not transmit, and it does not help with rolling codes. Opening a car or an alarm is not an engineering problem this tool is interested in; reading your own sensor is.
Audio measurements through an audio interface: THD+N, IMD, response, noise, crosstalk, wow and flutter – both channels at once.
Technical reports from measurement data: charts and tables from CSV, equations and diagrams, export to PDF, DOCX or HTML.
Frequency response, phase and distortion measured with a bench oscilloscope and function generator over LAN.
Logging bench instruments over LAN, USB or serial (SCPI): live values and plots, recorded to CSV.
Have a .sub from a Flipper or an IQ file from an RTL-SDR? That is all it takes to
start – no radio has to be connected.