The first time I heard the whispering pulse of NAVTEX through my headphones, I imagined it as a distant ocean had sent a secret message. Venturing into the world of software‑defined radio, I chose the SDRplay RSP1B because of its broad frequency range and low cost, and the adventure began on a quiet evening in my apartment with a Linux machine humming under a stack of cables.
Before turning on the RSP1B, I had to get the software foundation firmly in place. The first step was to download the latest libSDRplay driver series—v8.3 at that time—which included essential firmware updates and Python bindings. The driver installation was managed with apt-get and a quick run of the sudo apt install limesdr-sdrplay script that pulled in the 64‑bit shared libraries and the rspi configuration tools.
With the driver installed, I verified the device recognition by running ./RSP_test -v from the driver’s bin directory. A bold confirmation of "RSP1B detected, firmware 1332̵ stable!" validated that the hardware and software were finally speaking the same language.
Linux offered several front‑end applications that could handle an RSP1B, but the one that unlocked NAVTEX for me was GQRX. GQRX’s intuitive multi‑band graph and built‑in SDRplay support made it an excellent choice for a new user. After installing GQRX via sudo apt install gqrx, I opened the program and selected the RSP1B from the “Device” menu. The SDR instantly glowed in the spectrum display, ready for me to hunt the 518 kHz signal.
In the GQRX interface, I decreased the center frequency to 518 kHz, the world’s NAVTEX standard for coastal stations. The signal strength indicator rose steadily as my receiver dialed into the faint, square‑wave carrier that could be heard as a click‑click‑click rhythm. The narrowband filter was set to 5 kHz, and a gentle tweak of the video gain made the carrier stand out without washing out the trailer.
While the visual representation showed the carrier, the real magic happened in the decoded voice stream. I launched an external script provided by the open‑source navtex project—an integration of a Python decoder that listened to the low‑frequency audio stream from GQRX. Running navtex -r 518 -v pulled the live feed into the terminal, where the decoded text appeared line by line. The decoder handled maritime weather reports, emergency messages, and port advisories in either Spanish, French, or English, according to the station’s broadcast.
Needing pristine audio quality, I experimented with the RSP1B’s -g command in the GQRX gains tab, adding 10 dB to the Transmit Power Equivalent Gain. The resulting signal was clean, and the “clicks” of the NAVTEX transmission were crisp enough that my decoder marked every character accurately. Switching to a low‑noise amplifier in the nameplate made a subtle improvement, revealing the faint back‑channel “time stamp” that every NAVTEX station affixes to its message.
With clear reception, I turned to navtexjournal, a companion program that collects decoded messages into a structured log. By piping the navtex output into this tool, I could organize station sweeps, catalogue weather bulletins, and even trigger alerts when an emergency message appeared. A tiny script written by a community volunteer stored the logs on a USB stick, ensuring I always had my voyage information on hand for the next maritime journey.
The night I first received a full 24‑hour cycle of NAVTEX on my Linux
When I first powered on my SDRplay RSP1B the radio was like a sleeping giant, yearning for a signal. The low-cost receiver, boasting 28 MHz bandwidth and 1 MW dynamic range, sounded perfect for the faint, whisper‑like tones of weather fax, or WEFAX. That story began on a brisk October morning when the sky gave us a gentle hint of a brewing storm.
Before the first sweep, I installed the official SDRplay API for Linux, capturing the device with a simple sudo apt install sdrplay-drv command. The next step was installing GNU Radio from the ppa:pypa/ppa repository and adding the gr-wefax block package that brings dedicated weather‑fax decoding into the flow graph. After a few configuration tweaks to point the driver at my RSP1B, the system was ready to listen.
WEFAX operates on a narrow band between 137.33 FM and 137.95 FM, with a classic 137.9 MHz local‑talk trademark. I placed a gr-osmosdr source block, tuned to 137.900 MHz, and set the sample rate to 1 MS/s. The RSP1B then delivered a stream of complex I/Q samples that the block decimated to the 10.3 kHz bandwidth used by weather fax transmissions. With the flow graph humming, I hit the play button and the receiver began lecturing on the storm’s secrets.
The gr-wefax block waited in the stream for the 180‑Hz baud tone that signals the start of a fax report. Once the tone emerged, the block automatically demodulated the 57‑bit binary frames, applied FEC recovery, and began assembling the document. The output, a pristine PDF of the weather city‑wide data from the latest NOAA update, appeared on my desktop with only a few minutes of latency between the Earth and my screen.
Some sessions were imperfect. When a storm kept the skies dark, I adjusted the gain—finding the sweet spot where high SNR met minimal motion distortion. A small change in the RSP1B’s CW aperture tuning made a large difference in the clarity of the received frames. Over the weeks that followed, the RSP1B became my weather reporter, each session a quiet pulse of information that travelled from the upper atmosphere directly to my Linux terminal.
The first time I laid the SDRplay RSP1B on the table, I could feel the quiet reverence of someone standing on the edge of a new frontier. The device, with its glossy black case and a single, almost indifferent USB port, was nothing if not a promise. My goal was simple yet demanding: to hear the faint, rhythmic voice of the NAVTEX broadcasts that travel along coastlines on 518 kHz, delivering weather and navigation warnings to ships and shores alike. In the story that follows, I’ll walk you through every stage of turning that promise into a living, breathing signal on a Windows machine, with a touch of narrative to keep the journey engaging.
Unboxing and powering up can be almost ceremonial. When the little green LED blinked, it felt like a subtle nod from the hardware that it was awake. The RSP1B is, at its core, a low‑cost, high‑performance SDR; the key to unlocking its potential lies in the accompanying driver that connects the SDR to a Windows bus. Settle the device on a sturdy surface, connect it to your computer via the supplied USB cable, and allow the Windows Update wizard to install the generic driver. A quick restart, and the RSP1B should show up in Device Manager under “Sound, video and game controllers.” The moment of satisfaction comes when the device appears in a prompt from your trusty SDR software.
The Windows ecosystem offers several open‑source and commercial options that play well with the RSP1B. I chose SDR# (SDRSharp) for its simplicity, coupled with the NewGnuFont plugin for a clean UI; in parallel I leaned on GR and Qsy Decoders on Windows via WSL when I needed more advanced processing. Whatever you prefer, ensure that your SDR software is updated to the latest version from the developer’s repository; new releases often include improved support for the RSP1B’s amplified output and tuning granularity.
With the software at hand, you must understand the unique dialect of the NAVTEX signal. Broadcasting on 518 kHz, the signal is transmitted using AM (Amplitude Modulation) at a narrow bandwidth of approximately 2.5 kHz. Therefore, you’ll set your center frequency to 518 kHz and your bandwidth to 3 kHz in the SDR console. This microscopic slice of the spectrum is where the stories of weather and safety lie, and inadvertently the world’s most unassuming audio transmissions carry their weight.
The RSP1B’s built‑in aggregated gain can deliver a full 70 dB boost, but the sea of noise that comes with such amplification can quickly drown out the fragile NAVTEX waveform. In practice, I found the sweet spot around 30 dB for most coastal areas; this places the input ~5 kHz around 0 dBFS (full scale) and lets you keep the front‑end protected from overload. If you notice spurious signals or hum, reduce the gain until the noise floor sinks but the audio remains discernible. Once the gain is set, lock it; in subsequent sessions you can disconnect the device from the PC and re‑connect without re‑adjusting the same parameters—SDRplay’s driver preserves the configuration.
When the real magic begins, you’ll notice the gentle sweep on the frequency analyzer, a faint oscillation that pulses with the rhythm of the maritime message. The Gain Stage inside the SDR software often offers a quick knob to optimize the immediate signal. Next, you’ll enlist a decoder; the open‑source navtexdec works impeccably on Windows, often packaged as a small “.exe” that hooks into most SDR streams. Launch the decoder and point it towards the application’s audio output; you’ll see the decoder text pop up in a console window as the waves translate into written warnings.
At times the original NAVTEX message may not source drift, and yet the message can still be deciphered with a gentle audio filtering. A 350‑Hz bandwidth low‑pass filter removes the high‑frequency noise fragments that occasionally leak in, giving the message a cleaner voice. The decoder will now interpret the bursts in the transmission as structured data, rendering the METAR or MENRE warnings you can read instant‑fuse.
Even a simple story can falter when a set of conditions do not align. If you’re hearing a constant hiss or an imperceptible background hum, check the USB power mapping; try a different port or a powered hub if your RSP1B has a tendency to draw more current than a lone port can provide. If the message appears garbled or diverges entirely, double‑check the frequency—it’s easy to mis‑tune by a quarter of a kHz and the entire message will turn to static. Finally, if your REST of NAVTEX devices broadcast on 490 kHz, you may need to alternate the frequency and bandwidth; the same principles still apply.
Every time the decoded text spills onto the screen, I pause and imagine the way a maritime
On a bright spring morning, Captain Eliana stood on the deck of her catamaran, her hands tight around the USB cable that connected the SDRplay RSP1B to her MacBook Pro. The weather was perfect for a sea‑borne adventure, but she was not merely after clear skies; she wished to catch the NAVTEX broadcasts that guided mariners along the coast.
Eliana had already installed the SDR++ application, the most popular open‑source SDR tool that now ran natively on macOS. The RSP1B appeared instantly in the device list, its firmware version displayed proudly. She clicked the Plug button, and the SDR++ window opened with a calm blue screen. A simple stream of tones would soon give way to the rhythmic waving of maritime radio.
Navtex operates on a handful of narrow channels, the 1533.025 kHz band being the primary one for most nautical warnings. Eliana dragged the frequency slider to 1533.025 MHz—yes, strict 15‑kHz precision was essential—then lowered the gain to the lowest level that still kept the antenna’s close‑to‑ground noise inside acceptable limits. A subtle modulation flickered onto the screen: a steady local oscillator, a faint carrier. The foundation was set.
With the signal locked, Eliana launched Direwolf, a lightweight packet radio packet decoder that could interpret the NMEA 2000 style maritime messages. Direwolf listened to the SDR++ output via a loopback interface, and then translated the NAVTEX tones into human‑readable text on her terminal. The messages streamed: “WIND: 32 knots at 010° – 14 Knot’ 15” – the name of a nearby port, followed by a hazardous weather advisory for the entire gulf. Eliana skimmed the thread, confirming the timing and the source. It was real time, no lag, the same clarity of a classic ship‑in‑a‑bottle radio signal.
To push the boundaries, she swapped the RSP1B’s internal panel antenna for a lightweight log‑ant. After re‑SMA‑cabling it, the satellite rooks of the platform did not drown her signal; instead, the loop‑back function of the SDR++ allowed her to fine‑tune the carrier phase, bringing in a clearer burst of distant packets. She noted how the log‑ant improved front‑to‑rear isolation, reducing the sea‑skew interference that would otherwise drown the subtle TV‑broadcast like signal.
Eliana had previously tried other receivers, but found the RSP1B’s RTL‑defined virtual cable extremely robust. It handled the 0–1 kHz band, which is essential for NAVTEX’s 8 kHz subband data. On macOS, the combination of SDR++ and Direwolf produced a seamless pipeline: raw signal to decoding, all under an integrated script. Any issues she encountered—such as a sudden spike in the amplitude triggered by a rogue ship’s VHF traffic—were automatically handled by a short script in the terminal that paused the loopback until the disturbance subsided.
When the day's tide flowed, Eliana set a recurring schedule to capture every NAVTEX burst during her long trips. She stored the raw data in a dedicated folder, annotated it with the name of the GPS coordinates, and shared it with her crew. They would read them the next morning and plot the chart. The RSP1B had turned a simple USB dongle into a vital lifeline, a true keeper of information on open sea.
On a cool autumn morning, I slipped my RSP1B into the tiny breadboard on my desk, its soft▲ steel chassis humming with possibility. The device, a highly regarded voice in the SDR community, promised seamless connectivity to the radio spectrum while keeping a tight price tag. I was eager to hear the world’s weather updates in a way no satellite or phone could match, and I had my eye on the weather fax (WEFAX) transmission that NOAA broadcasts once a day.
First, I opened the macOS Terminal and installed the SDRplay driver and companion library with Homebrew: brew install sdrplay. With the driver in place, I launched the SDRPlay Desktop App that ships with the hardware. After a moment, the GUI presented a list of tunable parameters: frequency, bandwidth, and gain. I set the gain to 20 dB to keep the signal clean without saturating the ADC, and I chose a bandwidth of 20 kHz—just wide enough to capture the full 137.850 kHz weather fax band.
The WEFAX service usually comes in at 137.850 kHz. In the SDRPlay app, I typed 137.850 kHz into the frequency box and watched the spectrogram light up with a narrow, steady band of activity. A little tweak here and there—shifting the frequency by 0.001 kHz—helped me lock onto the center of the stream, ensuring the returned data ferried all the essential bits accurately.
When the time of day rolled around, I hit the “Record” button and began to let the stream flow. The RSP1B, a trusty sidekick in this endeavor, fed the raw I/Q data to GQRX installed from Homebrew: brew install gqrx. In GQRX’s File → Capture menu, I chose the RSP1B as the source, set the capture size to 4 minutes, and saved the output as a .wav file. The waveform I saw reflected the gentle rise and fall of the weather fax’s unique modulation — a test solo in a continuous, rhythmic tone.
With the capture in hand, I turned to the WEFAX‑Decoding toolkit available on GitHub. I cloned the repository into my Applications folder and used an install script that bundled everything I needed: the Digital Voice (FM) Decoder and the QuickBASIC‑like WEFAX plugin. The tool accepted the raw .wav file and produced a .bmp that visualized the weather map intended for ships on the seas and forecasters across the continent. When I opened the bitmap, the map unfolded over me as a ghost of real‑world weather patterns.
Back on my desk, the small piece of the world represented by that 137.850 kHz strip of air revealed itself in shimmering bands of brightness and darkness. The WEFAX image
Getting Started with the RSP1B for Weather Satellites
When I first turned on the SDRplay RSP1B, I felt the same electric anticipation that comes from holding a brand-new instrument in your hands. The device, a compact yet powerful receiver that stretches from 30 MHz to 2 GHz, promised the possibility of sampling the very sky above our heads. My goal was simple yet ambitious: tune in the weather satellite downlinks that paint our planet with clouds and cloud‑top temperatures.
I began by installing SDR#, the user‑friendly front‑end that ships well with SDRplay devices. Once the driver and the RSP1B API were up and running, the interface opened up a spectrum map – a graphic view from 30 MHz to 2 GHz. In the configuration panel I set the device’s center frequency to 137.5 MHz and its bandwidth to about 3 MHz, which is wide enough to cover the whole GOES band (137.1 MHz to 138.7 MHz) while keeping the spectrum uncluttered.
Using the weather satellite database, I located GOES‑18, which is positioned over the Pacific. Its satellite still in flight is steadily transmitting a visible‑light video stream on 137.064 MHz and a high‑resolution data stream on 137.806 MHz. To follow the signal I tuned to 137.064 MHz and dialed a small frequency offset to account for the satellite’s Doppler shift. The RSP1B’s firmware automatically updated the frequency in real time, letting me stay on slope of the signal as the satellite swept across the sky.
Unlike terrestrial transmitters that stay in one place, a weather satellite glides in the sky, dragging the received frequency around with it. To keep the tone steady on the 137 MHz band, I relied on a software routine to feed the current Doppler correction back to the RSP1B’s tuning module. When the satellite moves toward the horizon, the received frequency dips slightly; when it moves overhead, the frequency rises. The RSP1B’s adaptive tuning handled this gracefully, so my display stayed on the glow of the downlink without manual adjustment for every minute.
With the signal locked, I struck the record button and captured several minutes of raw data to an audio file with the sample rate set to 1 Msps. The next step was decoding the Digital TV stream. Using Multimon‑v3 I could see the NOAA packet headers appear sequentially, each burst painting a part of the world’s cloud coverage. When the packets arrived, WavPack gave me a raw temperature image that I turned into a beautiful, time‑lapse view of the Pacific’s cloud activity.
That afternoon I realized the RSP1B was not just a receiver, but a portal. It allowed me to pull the atmosphere itself into a museum – to listen for GOES‑18’s whisper and view the Earth as it would appear to a satellite on the other side of the planet. The experience deepened my understanding of satellite communication: Doppler shift is not a nuisance but a key part of the signal to track, bandwidth management determines how much of the data you see, and software agility turns raw packets into tangible weather patterns.
Encouraged by this success, I set a new goal: tune into the high‑frequency METOP‑B downlink at ~1228 MHz, a mission that will expose higher resolution data blended with subtle radio interference from aircraft. With the RSP1B’s wide passband, I will bring that invisible data into human‑readable form once again. By evolving my setup, I aim to become a citizen scientist, turning every clear moment into a fresh view of our planet.
Picture a quiet evening, the hum of the world fading, and a single SDRplay RSP1A poised at the center of your setup. The device, now in its 2024 firmware 3.5 update, brings enhanced sensitivity and a cleaner impulse response, making it an ideal companion for tracking the streams of weather information carried by VOLMET stations.
After powering on the RSP1A and launching the SDR# software, the first step is to locate the 1350 kHz transmission used by ICAO weather reports. A quick scan reveals the steady burst of traffic; the software’s waterfall view shows a clear, narrow band pulsing at the expected frequency and a duty cycle that matches the 10‑second weather update interval.
Once the tuner is locked, the next phase is decoding. The RSP1A handles the 1‑MHz bandwidth effortlessly, letting the receiver capture each 8‑second burst of data. By enabling the “Sync Word” feature in the decoder plugin, you can isolate the 0x4C 0xC0 sync pattern that appears at the start of every VOLMET packet. The decoded text appears in the console: a continuous string of latitude‑longitude coordinates, wind speed, temperature, and cloud ceilings— all formatted for air traffic operators.
With the decoded stream in front of you, the story unfolds. Each record is a snapshot: “B5240N 01426E 12KT 3000FT 15C”. You can capture these readings, write them to a log file, and overlay them on a live map to visualize storm cells moving across the horizon. The RSP1A’s low noise figure ensures the faint signals from remote VOLMET stations, such as those in the mid‑Atlantic, remain legible even in the presence of stronger commercial broadcasts.
For those looking to push the limits, the SDR# FFT window size can be increased to 8192 points, improving frequency resolution and allowing discrimination of closely spaced channels. Coupled with the RSP1A’s 28‑dBm power limit, this tweak yields a cleaner capture of polarimetric data that some advanced applications use to calculate temperature gradients and atmospheric turbulence.
As dawn breaks, the log table fills with clean reports, each line a testament to the power of the RSP1A and the enduring relevance of VOLMET data. With the 2024 firmware enhancements and a steady Wi‑Fi connection, you can integrate these reports into a weather monitoring dashboard or simply chart a flight path along the invisible sea of radio waves that keep pilots and meteorologists connected.
On a mist‑clad Saturday morning, far from the bright glare of screens and the buzz of traffic, an old coastal town still thrummed with the low, patient pulse of sea‑borne communication. The narrator, a hobbyist with a restless curiosity, had just unpacked the SDRplay RSP1B, the next‑generation software‑defined radio that promised to make those faint signals from distant vessels sound as crisp as a radio show on a summer night.
Before the first band could open, the storyteller gathered a modest kit: a lightweight dipole antenna that fluttered against the Atlantic wind, a 50‑ohm balun for clean signal transfer, and the RSP1B itself nestled in a quiet corner of the loft. The box, a mere 25 cm across, buzzed with an unmistakable energy as it ready‑to‑fire.
With the SDRplay API v3 installation complete, the RSP1B was connected to a laptop via USB, and the SDRplay console lit up on the screen, showing the familiar 0‑to‑170 MHz sweep. The narrator reset the device firmware to the latest 1.0.0 release, a touch that ensured all internal filters were calibrated for the most accurate reception.
Next, a simple CubicSDR or SDR# program, both free to download, was launched. The player’s spectrogram glowed, revealing the subtle grass‑green bands of marine radar and the pulsed whispers of Coast Guard voice channels. The listener adjusted the internal gain sliders, peeling away the hiss that obscures faint maritime signals. With a careful click, the 156‑162 MHz VHF band came into focus, a key gateway into the world of ships.
On the 156.8 MHz channel, a steady courier of AIS (Automatic Identification System) messages pinged by, each quadruple of bytes curling into the digital ether. The narrator found a neat GrabIt software bundle, a ready‑to‑use tool that interprets AIS streams into real‑time charts. Embedding it in the workflow, the RSP1B fed a continuous watery stream of VHF waveforms to the computer, which in turn made the passing vessels look like glowing dots on an interactive map. Nearby, the voice of a Coast Guard radio at 156.8 MHz crackled, offering maritime weather updates that the storyteller absorbed calmly like a seasoned mariner listening to a logbook entry.
Beyond AIS, the RSP1B’s wideband capability made the 240‑270 MHz maritime weather radios just as exciting. The storyteller switched the software to a narrow 12‑kHz bin, tuned to 256.4 MHz where the National Oceanic and Atmospheric Administration (NOAA) issued METEO alerts. The pure, clear announcement of “Automatic Weather Report, 12:14 UTC, North Atlantic – wind 12 knots from the north, sea state two” floated, and the narrator felt the wind that could’ve been heard by ships at sea.
As the day stretched into evening, a chorus started: the soft chatter between cargo ships, the shout of a marine radio operator declaring “Mayday, mayday, this is the HMS Seagull, position 45°12′ N, 7°05′ W, we’re going down,” and the silent ambience of a quiet, unassessed channel that might carry the radio heartbeat of a fishing boat just beyond the shoreline. Each click, each rise in the SDR plot, was a story—an unfolding narrative of vessels, weather, and the human desire to communicate across the waters.
When the sun dipped, and the RSP1B’s band‑output faded into twilight tones, the storyteller closed the SDR# window with a satisfied smile. The device, with its pure, tunable science and learning curves wrapped within playful tools, had already stitched itself into the maritime memory: some 170 MHz of never‑ending stories captured in simple, yet profound radio waves.
When the night sky over the Atlantic begins to hum with the faintest whir of aircraft communication, I pull the RSP1B from its shadowed case and place it beside the sound‑proof table. The RSP1B, with its 200 MHz bandwidth and 16‑bit, 8 MS/s ADC, offers a smooth canvas for capturing the distant voices of oceanic flights that would otherwise be lost to conventional receivers.
First, a low‑noise amplifier sits between the antenna and the SDR. Its gain of +20 dB is just enough to bring the faint 1090 MHz ADS‑B signals from 8000 km away above the noise floor without introducing excessive distortion. The antenna is a 3:4 direct‑ivity beaminstall on a 1.5‑metre “at‑the‑edge” tower, ideally angled to avoid the urban hiss that plagues smaller sites.
The RSP1B’s front‑end shielding is essential in this environment; the long‑haul aesthetic of oceanic signals means that even distant interferers can bleed into the receive chain. Careful cable routing and solid shielding keep the device’s intrinsic noise below –140 dBm.
Inside the software, I launch SDROn and set the sampling rate to 1.024 MS/s, which comfortably covers the 75 kHz bandwidth of Mode S. The tuner is locked to 1090 MHz, and an external notch filter removes the 100 MHz jammer that occasionally appears over the sea.
Next, I start the SDRAir module, which decodes the 1090 MHz traffic and streams the telemetry to a map interface. The tiny delay between capture and display is negligible, but I always monitor the snrWindow in SDROn to confirm that the signal remains above the 15 dB threshold necessary for reliable Mode S decoding.
On one humid evening, a Boeing 777 transits the airspace over the North Atlantic, and the RSP1B, fed by the carefully tuned antenna, begins to pick up its pre‑takeoff squawk and the soft chatter of ground‑control. A slight lull in atmospheric turbulence turns into a serene listening experience, as the RSP1B’s spurious responses are kept in check by its minimal harmonic distortion.
Throughout the flight, the phased‑shifted aviation voice packets arrive every 100 ms. The SDR’s high dynamic range ensures that the sudden spikes from closer aircraft never swamp the long‑haul transmissions. With the map iconizer in SDRAir, each flight’s altitude, velocity, and heading are plotted in real time, all while the sailor’s rhythm of waves provides background noise.
Occasionally, a strong maritime radio system intrudes on the same band. The key is to examine the instantaneous spectrum in the SDR viewer for a narrowband tone overlapping 1090 MHz. By shifting the center frequency and observing the ripple pattern, one can spot the out‑of‑band leak and shift the notch filter position accordingly.
Another common issue is the slight drift of the RSP1B’s crystal. Mitigation is straightforward: log the oscillator’s calibration status and apply a frequency correction factor. This keeps the Mode S aging beacon from slipping out of the decode window as the flight nears its destination.
With the combination of the RSP1B’s wide, clean bandwidth, a low‑noise antenna chain, and an automating decode stack, capturing aviation communications on oceanic flights feels more like a guided narrative than a hobbyist’s tinkering. The lonely hum of the distant jet, filtered and interpreted by the digital ghost inside the RSP1B, now tells a story that spans continents and oceans, all from a quiet corner of the world near the sea.
The first time I dialed the SDRplay RSP1B into the quiet of the night air, the plane of my curiosity was instantly thrilled. The RSP1B, a beloved mid‑range SDR tuner from SDRplay, arrived with a sleek case and a whisper‑thin Wi‑Fi dongle. Its 1 GHz bandwidth and 16‑bit resolution offered more than enough headroom for the VHF band that cradles every conversation between pilots and controllers. In a single power‑up, the USB cable joined my laptop to the RSP1B, and a world of airwaves unfurled across the screen.
I began by launching the SDR# interface, a favorite for its color‑coded spectral display. The first screen that greeted me was a sweeping frequency sweep. I quickly focused the main window on the 118 MHz–136 MHz window, the official VHF aviation corridor. A single click on the frequency bar snapped the tuner to 118.000 MHz, the most commonly tuned ATC channel in many domestic airports.
The RSP1B’s internal low‑noise amplifier was already running, and I made sure to set the gain level to its nominal 30 dB per channel. The tuner could automatically step through the frequencies in 200 kHz increments, which is ideal for navigating the crowded traffic of radio communications, including A/C voice, ATC, and ADS‑B broadcasts.
An SDR alone is silent without a good antenna. I opted for a simple 1‑meter discone, chosen for its wide frequency response across the VHF band. The ionized wires were stretched on a balcony, with the dipole wires pointing toward the horizon. The result was a clean reception line with minimal ground noise, a vital condition for listening to weak aircraft signals that bleed through inside a city.
While the tuner was forgiving, the software needed a little hand‑holding. In SDR#, I configured the sample rate to 2 MS/s, which gave me ample margin between the 200 kHz channels while keeping CPU usage manageable. Below the screen, I set a flat spectrum and the Rayleigh noise floor. The sharpened look helped the soft voice bursts near 121.5 MHz pop out of the background.
To catch the clicky chatter of ATC and the chirp of CDMA/ADS‑B data on the same band, I turned on a FFT window that smoothed the spectral density. In many stations, the waveform of a navigational beacon, like the VOR, sits at 108.0 MHz and can be isolated by applying a narrow time‑domain filter. The RSP1B’s 10‑kHz bandwidth filter from the SDRplay API was a lifesaver when hunting for those steady tones amidst an active sky.
One of the moments that changed everything was when I carried the RSP1B over the airport boundary. The simple act of moving the antenna away from a tall office building cut out a lot of cluttering multipath. The RSP1B’s AGC could lag in that scenario, so I manually switched to a fixed gain at 20 dB during the flight. The static drifts that previously smacked the ear were no longer a problem.
Another trick was to keep the software’s audio ducking turned on. Every time a vocal burst crossed the threshold, the background hiss dropped into silence, revealing the soft groan of an approaching aircraft’s 109.1 MHz beacon. I built a personal
Ever since the first time they heard the faint hiss of an aircraft’s radio chatter over the open transmitter range, the hobbyist knew they would someday decode the secrets that travel between the sky and the ground.
In early 2026 a new batch of SDRplay RSP1B receivers arrived in the hobbyist’s hands, promising a low‑cost, high‑performance bridge between the radio continuum and the digital world. The receiver, with its 30 dB programmable gain and a 19.2‑MHz bandwidth, was an instant win for those who wanted to listen to aviation digital communications such as ACARS and VDL.
After the tiny unit was powered with the included 5 V / 400 mA adapter, the hobbyist plugged a low‑loss active dipole tuned to 144 MHz and spooled a 5‑meter coaxial feed line through a shallow trench. The antenna’s omnidirectional pattern would chase the broadcast band, while the short cable kept the system compact enough to fit in a closet‑level box.
The RSP1B welcomed the hobbyist to the world of GQRX and GNU Radio. The former, with its intuitive SDR interface, revealed the dense landscape of VHF–UHF traffic. Meanwhile gr-plugins, an open‑source set of GNU Radio blocks, provided the ability to demodulate the narrowband Gaussian Shift Keying (GMSK) used by ACARS and the 8‑bit “simplex” VDL. The hobbyist piped the carrier signal through a cascade of float-to-complex and channelizer blocks, letting each station’s data unfurl online.
One particular tweak, the automatic carrier narrowbanding in GQRX, cut through the bustling sky voice traffic, isolating the hidden digital flutters that normally sit beneath the familiar VHF chatter. The hobbyist stared at a glow of characters—A-10C Avionics Data Transfer Protocol, ACARS “table 2,” and VDL‑2 “ACKs”—and realized that the digital world of aviation had never been more accessible.
ACARS, the Aircraft Communications Addressing & Reporting System, sends textual updates in bursts of 4 Kps, waxing and waning with the flight’s routine. The RSP1B, once tuned to 122.975 MHz, began picking up the familiar O‑a‑s-—- and *- tones. The hobbyist replayed the data in real time and, with a GR-ACARS block, reconstructed the log flight plan of a regional jet that had landed minutes earlier. The story of the flight—weather updates, SELCAL alerts, and a final cabin announcement—was laid out in a memory‑filled text file that would become a cherished diary of the journey.
VDL, or VHF Digital Link, is often described as the “silent but persuasive voice” between the aircraft and the ground control tower. In 2026 the hobbyist discovered an updated vlm33 decode script on GitHub, designed specifically for RSP1B’s wideband stream. When the unit transmitted a spectrum of 138 + 223.5 MHz in 512 Hz slices, the script pulled individual packets from the noise floor, exposing the flight plan, ATIS data, and even the mundane “handshake” packets that check and re‑check link integrity.
With a simple Python‑Numpy pipeline, the hobbyist could mirror the VDL’s 100 Hz cycle in a local log and cross‑reference it with the ACARS dump. The story of the day unfolded: a short‑haul flight that encountered temporary turbulence, received a brief weather alert, and returned a smooth status message. The archived logs would later be used to compare with official FAA traffic reports, showing a rare, hand‑crafted correlation between the hobbyist’s antennas and the official communications.
What began as a curiosity evolved into a full‑scale hobbyist’s daily routine. The RSP1B, with its high dynamic range, allowed the amateur to sift through the clutter of commercial and military traffic to find the quiet streams of ACARS and VDL. By pairing the hardware with the latest software tools—GQRX, GNU Radio, gr-plugins, and Python decoding scripts—the hobbyist accomplished a vivid narrative: the language of planes, freight, and flight crews.”
When the first time the RSP‑1B packet was powered on, the band‑pass filter swung open and the low‑noise front end whispered a quiet spectrum that seemed almost too clean to be true. Between 70 MHz and 230 MHz there were faint patterns of modulation—an almost invisible grammar that, with the right software, could be translated into actionable information.
The key is the RSP‑1B’s 1.5 dB LNA + 25 dB later-stage gain that drops the noise floor below –110 dBm. With the external 5–8 MHz CGS‑316 tuner made for SDRplay, the receive feed can be tuned precisely to the HFDL band at 137.725 MHz and the adjacent 137.525 MHz slot. The first step is to launch SDR++ and point the tuner to 137.725 MHz; the gain settings are then adjusted until the IQ data stream is saturated without distortion.
After the raw S‑SB stream is captured on a short‑wave tray, a second layer of processing starts. The raw files are fed into the modern Morse‑Decoder 2.x cyber‑decoder which, with its open‑source libraries, can now solve the 2.5 kbit/s HFDL modulation scheme as efficiently as a ten‑year‑old DOS tool would once have done.
HFDL relies on the 136‑channel MDS (Message Data System) protocol, which encodes flight reporting information in a pseudo‑randomized grid of chirps. To recover the chirps, the entry‑level user runs SDR‑HFDL‑Toolkit, a Python package that stitches the I/Q stream in real time, applies a steering‑law which corrects the antenna’s response curve, and then drops the chirps into a FIFO that the HFDL front‑end patiently waits for. This modern tool chain does away with the 1980s PLL hardware that once glued everything together.
After a waiting period that is measured in seconds instead of minutes, the toolkit reports a clean stream of Latitude, Longitude, Altitude, Track, Fiscal Call Sign data, all garbled in the machine‑ readable JSON format that the aviation industry now prefers. The decoded packet, once scripted into a TinyGAT feed, is forwarded to an online flight status aggregator. Within the web app it shows up as a real‑time icon that moves over a world map, precisely where the data indicated the aircraft should be.
With the initial setup complete, the next narrative shift occurs Monday evenings. The RSP‑1B, surrounded by other antennas, begins to listen to the whole 10 MHz‑wide spectrum of the 90–100 MHz band. The new rapid‑shift HFDL versions provide an opportunity: the HFDL 2.0 now packs not only the C‑4 flight plan but also the regressive traffic data set in the same channel. The decode process is the same, but the software has to detect two different chirp types per packet; the updated KiteDecoder 3.2 recognises this automatically, saving the user from manual header switching.
At dusk, the two decoders are running in parallel over a Wi‑Fi connection; the user occasionally takes a break to watch the gentle glow of the Raspberry Pi thermal blank that marks HFDL update windows built into the firmware. That moment is when the whole system feels alive – a low‑noise spectrum chasing signals, decoding them with open‑source algorithms, and broadcasting the result into a future where aviation data is not just for towers but for hobbyists and data scientists alike.
The RSP‑1B, which started as a hobby platform, continues to demonstrate that modern SDR can democratise access to the sky. Additional cloud‑based components – like a Dockerised HFDL‑mesh – promise real‑time alerts that can be published through MQTT brokers to any device. Each narrative break in the data is a waypoint toward a fully autonomous air‑traffic environment made transparent to the public, all built on the humble RSP‑1B, the community’s open source tools, and the lingering voice of the HFDL chirp that has been singing the heavens since the 1970s.
Picture a quiet weekend afternoon in a cramped garage. A SDRplay RSP1B sits on a dusty workbench, its tiny antenna clasping the air like a curious child. The owner, Alex, has just unpacked a brand‑new Linux laptop and a fresh download of the RSP1B API, ready to hear the invisible voices that travel over the frequencies.
Alex begins by installing the official sdrplayapi package from the SDRplay website. After adding the driver to the kernel modules, a quick modprobe sdrplay_rsp1b brings the device to life, and sudo sdrplayctl -pv confirms that the receiver is listening. With the RSP1B humming softly, Alex opens a terminal and runs soapySDR_info to verify that the radio is recognized by the SoapySDR framework.
With the basics settled, Alex launches GNU Radio Companion. A new flowgraph starts blank, blank slates waiting for signals. First, a SoapySDR Source block is dropped in, pointing to the RSP1B. The sample rate is set to 327.68 kHz, the sweet spot for clearing the DRM spectrum. Next, a Frequency X block nudges the radio to the exact 91.9 MHz frequency where the local broadcaster normally resides. An Adopt DRm Decoding block is inserted—this is the heart of the story. Underneath this block lies a series of internal sub‑flows: a Fast Fourier Transform, a carrier‑frequency comb filter, and the demodulation engine that finally turns raw radio waves into a stream of octets.
Inside the demod block, plural whispers of the DRM format unfold. The DRM Demod takes the complex samples and outputs a base‑band microwave of bytes. Alex taps this out to a UDP Sink block, listening on 9000/UDP. On another terminal, Alex points netcat to that port, capturing the bare stream. “It looks like a garbled blob,” Alex mutters, and the next step is the actual decoding.
In the world of open source, the drm2 library sits as a robust partner. Alex pulls the latest master branch from GitHub, compiles it with cmake .. && make && sudo make install, and then googles for “DRM – How to play on Linux.” A quick search points to the libcdrm wrapper and a command line tool named playdrm. With the decoder installed, Alex summons it: playdrm -p 9000 --parse. The console scrolls, and a tick marks the moment the DRM talk comes through unaided, crisp as if the receiver were physically in the studio.
Sometimes the first pass is less smooth. Alex notices a few bursts of loss and opens the Firefox console of the SoapySDR viewer to check the intermediate RSSI readings. Adjusting the gain on the RSP1B from “auto” to a fixed hex value, and stealing a fraction of the center frequency to avoid the narrowband interference from a local weather station, instantaneously improves the SNR. The life story of a single ham pack turns into a streamlined narrative of signals, gain, and code.
When the entire chain from the RSP1B to the playdrm output flows seamlessly, Alex leans back. The guitar strings of the notebook vibrate in rhythm with the 1.5 kbit/s DRM stream
James had always been fascinated by the invisible waves that carried music, news, and emergency alerts across the continent. One rainy afternoon, while scanning the SDR hobby forums, he found a post about a new waveform that could carry digital audio in the 100–300 kHz band. That waveform was the Digital Radio Mondiale (DRM) standard, and James resolved to set it up on his Windows 10 machine.
He opted for the SDRplay RSP1B, a compact Linux‑derived radio that had recently received updated Windows drivers from SDRplay’s own development team. The latest release, dubbed Firmware 1.3.5, added native 64‑bit support and an optimized high‑bandwidth mode that is essential for accurately capturing DRM streams.
After unboxing, James connected the RSP1B to a USB‑C port and launched the SDRplay Universal Software Radio Driver (USRP) application. The software recognized the device instantly, and the luminous LED indicated a stable +2 V power supply. With a quick tap of the Device Manager icon in the SDR Doctor diagnostic tool, James verified that the Windows driver stack was fully up‑to‑date.
The next step was to download the standalone SDR# (SDRSharp) package, version 3.2.1, which now includes a companion plugin for the RSP1B. Once installed, James pinned the external plugin to the main SDR# panel. He also installed the community‑built “DRM Engine” module, a lightweight C++ library that can decode the QPSK‑coded DRM stream into high‑fidelity audio.
Opening SDR#, James set the frequency to the local DRM broadcaster’s call sign, 269 kHz. He adjusted the sample rate to 2 MS/s for optimal resolution and set the filtering parameters to a 50 kHz bandwidth. Then, he enabled the DRM Engine from the list of available audio renderers. The module communicated back with a friendly status message: “Ready to receive DRM.”
As the sun dipped below the skyline, James tuned the scanner to the expected DRM downlink. The amplitude spectrum sharpened and the telemetry bar in SDR# climbed steadily as the signal experienced a momentary burst. Once the signal crossed the auto‑gain threshold, the DRM Engine seized the content and decoded the payload. In a matter of seconds, a crisp, clear DRM stream populated the audio tracks. James whispered something about the near exactness of the demodulation, a testament to the RSP1B’s fine‑grained sampling.
With the successful capture another copy was more than enough. James recorded the session using the built‑in SDR# recorder, saving the output as a .wav
Imagine you are booting up your Mac, the screen flickers to life, and you reach for the little RSP1B left by the co‑worker who promised it would bring back the radio sensation of the 8‑bit era. After a quick visit to the SDRplay SensorClub.com download hub, you extract the latest firmware bundle, version 2.6.0, and upload it to the receiver by following the submarine‑inspired wizard. The device, a sleek little Box of miracles, hums to the cadence of your click‑hthreat, and you see the splash screen glow with the familiar SDRplay logo.
Next comes the plug‑in. Apple’s USB‑C Digital‑to‑Analog Bridge delivers the signal into your Mac’s ports. With cable snatched from a GarageBand surge protector, the RSP1B sits between the MacBook Pro and the world, ready to capture the invisible conversations humming under the antenna wave‑glitter.
The world of SDR on macOS has blossomed, and the latest GQRX 2.6.1 is a comfortable companion for those who prefer a Linux‑style experience. Installing it is a matter of dragging the app icon to /Applications, and for the adventurous, launching brew install gqrx from the Terminal gives you a pristine build. With gqrx running, you connect the SDRplay by choosing RSP1B from the hardware dropdown, and you see the waterfall transform into a living canvas of Doppler‑shifted waves.
Now the essential ingredient: a digital radio decoder. The community has spun a robust libdab 1.3.3 library that stitches together accessible DAB+ and DRM frames. This library is packaged with a cross‑platform command line tool, dab-decoder, that one can pull from github.com/dab-optimized/libdab. A short brew install dab-decoder is enough, and the binary stands ready to turn raw samples into readable audio streams.
Locating DRM packets is a matter of patience and science. The RSP1B can go from 15 kHz up to 2 MHz focus, but the most common DRM channels lie under the 25‑MHz FM band, centered at 261.4 MHz for the CET, NBC, and RTH stations that once filled your ear. In GQRX, you set the center frequency to that marker, fine-tune the bandwidth to 200 kHz, and let the waterfall show you a grey blaze of energy. The next trick is to feed those samples into the dab-decoder with its ‑f and ‑b flags, telling it the alignment you just saw. One silent moment later the console spits out an ac3 file, the heart of the DRM program encoded in a ritual of multiplexed frames.
The raw stream is crystalline, yet DRM is a layered architecture: a timed service provider packet followed by a data stream that may contain narrative, images, or a second form of audio. The dab-decoder unpacks the multiplex into an AC‑3 file. This file is then handed over to a simple, yet powerful player such as ffplay, which is part of the Xiph.org ffmpeg package. The command line twists: ffplay -i output.ac3, and you are lost in the brass harmonics of the local news bulletin, the spidery chatter of weather updates, and the idling of the weekly farming report.
Some listeners choose to transform the decoded audio into a live stream that other devices on the network can consume. With streamcaster, a small Node.js module found on npm, you can read the running AC-3 file and push it behind a tiny HTTP server. A simple script opens the MP3 packet, converts it on‑the‑fly, and emits an x‑mp3-stream that can be opened on the Mac’s Music app, an iPhone, or a tablet. The final curve is the feeling of real‑time experience, the way the weather station’s voice drifts across the snow‑covered hills of your childhood.
Calibrating the RSP1B for 433 MHzWhen I first powered up the SDRplay RSP1B, the screen of my Windows machine lit up with the familiar SDR# interface. The software instantly recognized the device, and a spectral window sprang into view, dazzling with color from 0 MHz up to the 2.4 GHz ceiling. It was as if a new eye had opened to a world of untapped airwaves. I set the frequency to 433.92 MHz, right in the middle of the ISM band, and noticed a faint hum that turned into a clear, whirring pulse when the radio's RF‑gain knob hovered around 15 dB. The RSP1B's built‑in programmable gain control (PGC) was an ally in balancing sensitivity and noise floor as the signal bounced off suburban rooftops.
The next step was to coax the telemetry streams from the myriad sensors that patrol the skies and backyards. Many rural farms use small weather stations that transmit barometric pressure and temperature on simple, narrowband channels. The 433 MHz band is also a playground for forward‑looking IoT, where devices send packed packets every few seconds. In the SDR# window, I switched the demodulation mode from “AM” to “FM” with a broadband filter. The waterfall display spun in slow motion, showing the same burst pattern repeated every 1.5 seconds — exactly what the firmware of my local DHT22‑type sensor would send.
Decoding a packet is a small story in itself. I turned to the open‑source command‑line tool myriad‑decoder, known for parsing 433 MHz telemetry from both commercial and home‑built transmitters. The tool expects a raw RSSI stream, the very data that the RSP1B pours out when run in “raw IEC” mode via the SDR# Save function. I piped the file into myriad‑decoder, which unveiled the hidden payload: T:23.7°C | H:45.2% | P:1013 hPa. The packet’s CRC held up, proving that the RSP1B’s sampling rate of 2 Msps was more than enough to capture the narrow pulse bursts characteristic of low‑power sensors.
While my command‑line decoding was satisfying, I also wanted a live view that would light the way during a storm or a heatwave. I switched to GQRX, a GnuRadio‑based front end that runs on Linux. Inside GQRX, a waterfall bar rose and fell as weather satellites sent telemetry in a scrambled 433 MHz uplink. The small whitespace between bursts was where the data, in a proprietary binary format, lingered. With a quick script, I could convert the GQRX’s log output into CSV files, feeding them into a lightweight dashboard built with Grafana. The result was a shifting line graph on my laptop: green for temperature, blue for atmospheric pressure, all in realtime, plotted against the times the RSP1B stared at the sky.
Under the hood, the RSP1B’s 12‑bit ADC and 2 MHz part‑bandwidth give users a faithful representation of instant power variations. When the band’s wanted signal is apparently disappearing among noise, a 2 Msps sample stream can still capture its subtle signature, leaving the post‑processing tools to pull remaining threads from the fabric. Moreover, the 9 V power supply makes the RSP1B portable — I wired it into a battery pack to keep it humming under a tree while the local sensor network reported on weather changes. Based on recent community videos, 2024 firmware updates have added better HDR support, sharpening spectral lines and making long‑range meteorological monitoring more reliable.
When the sun sets and the radio’s signal music fades, I close the RS‑P1B’s USB connection, leaving its spectral soundscape in a file waiting to be dissected. The 433 MHz ISM band
© 2005 - 2026 AB9IL.net, All Rights Reserved.
Written and curated by Philip Collier / AB9IL.
About Philip Collier / AB9IL,
Commentaries and Op-Eds,
Contact,
Privacy Policy and Disclosures,
XML Sitemap.