It was a quiet afternoon in the university lab, the air humming with the low buzz of a computer fan. A lone researcher, Maya, unfolded a new piece of equipment—a ADALM‑Pluto Revision D SDR—that had arrived days before, its body a sleek, matte gray with a small tag marked “Pluto-D.” She had read through the latest release notes, which highlighted upgraded silicon that offered tighter loopback latency and improved PPK calibration, and she felt the anticipation of trying something different, something that could open up the radio spectrum for her experiments.
Loading the Toolchain
After a quick boot, Maya launched the updated ADI XDSs2 hub on her workstation. The toolchain now supported a new integration with LabVIEW 2024 and a clean API for spectral sweep functions. She cycled through the RF front‑end test benches, confirming that the downward‑tuning pinout and the MIMO‑capable antenna array had been correctly configured. The Revision D’s flexible PLLs allowed her to lock onto any target frequency across the 0.9–6 GHz band, but the real draw was the robust low‑noise SMA connector on the daughterboard, which reduced loss by an extra 0.5 dB compared to earlier releases.
Why Chirp Spread Spectrum?
When Maya turned on the software she heard the familiar “chirp” tone that slowly sweeps upward—a signal called a Chirp Spread Spectrum (CSS) waveform. In the narrative of radio communication, CSS is not just a trick of audio; it is a foundational technique for Low Power Wide Area Networks (LPWANs). What makes CSS so advantageous is its ability to *simultaneously* spread the power of a narrowband signal over a wide band while preserving its spectral density. This widens the signal’s resilience to both multipath distortion and interference, which is especially critical in urban canyons where buildings bounce signals or in rural environments where the radio backhaul can be sparse.
Furthermore, Maya read how CSS enables very long, low‑rate data frames—perfect for IoT devices that need to transmit tiny packets over 10 + kilometers without drawing much power. By increasing the Spreading Factor—the ratio of the number of chips to the number of bits—CSS pushes the signal into a quasi‑orthogonal space. This means that multiple devices can share the same frequency channel without colliding, a property that is at the heart of LoRa™ technology, which was originally developed by the same team that now runs the ADALM‑Pluto.
An Experiment in Space
Armed with the new Revision D device, Maya set up a two‑node test. The first node—a Pluto housed inside a weatherproof box—added a CSS packet every minute, broadcasting its stable GPS timestamp. The second node, a nearby laptop with an SDR dongle, captured the chirp waveform and decoded the packet. By varying the Spreading Factor from 7 to 12, Maya observed that the packet error rate fell dramatically as the factor increased, even in the presence of a strong TV uplink that the lab’s antenna system picked up as extreme interference. The low‑noise floor of the Revision D’s ADC allowed the receiver to recover the signal at an SNR of less than 2 dB, a performance rarely achieved with older hardware.
Beyond the Lab
When she later presented her findings at the university’s radio‑technology symposium, the audience buzzed with excitement. The ADALM‑Pluto Revision D had not just been a chip upgrade; it had opened a window into real‑world CSIT—Channel State Information at Transmitter—within the flexibility of a software‑defined platform. For projects that demand ultra‑low power consumption over wide coverage, CSS remains the gold standard, and the new Revision D made probing it as simple as writing a few lines of code.
In that moment, Maya looked at the graceful sweep of the chirp in her spectracope and realized that the future of wireless IoT wasn’t just about faster data; it was about *lasting* connectivity for everything from freeway traffic lights to little sensors buried beneath the earth—an era that had just become a little more reachable, thanks to the humble, yet powerful, ADALM‑Pluto Revision D and its steadfast CSS pulse.
The Dawn of a New SDR
In the quiet corner of a university lab, a researcher named Mara brushed dust from an old ADALM‑Pluto Rev D board. The board’s glossy case seemed almost unremarkable—just another piece of hardware lamented for years in an online forum fed by DIY enthusiasts. Yet beneath that unassuming shell lies a transformative platform: a 300 MHz to 3.8 GHz transceiver coupled with a Zynq‑7000 that marries a familiar ARM Cortex‑A9 to a powerful programmable logic fabric.
When Mara powered the board up, the familiar green LEDs flickered alive, and the lab quieted. She listened to the soft hum of the LDOs and thought of the world of radio waves that stretched beyond the walls, waiting to be captured.
Exploring the Frequency Landscape
LoRa, a long‑range, low‑power wireless protocol, has woven itself into a growing tapestry of IoT applications. By operating primarily around 868 MHz in Europe and 915 MHz in the United States, it occupies a utopian hundred–kilometer airspace that customarily belongs to amateur bands or cellular systems. The pluto’s coverage up to 3.9 GHz positions it squarely within safe reach of any LoRa deployment.
What sets the Revision D apart is its enhanced dynamic range—a new, robust antenna tuner and recalibrated receiver front‑end that boosts the signal‑to‑noise ratio. The board’s 12‑bit ADC now samples faint bursts with greater precision, resolving the delicate chirps that LoRa packets carry.
A Tale of LoRa Signals
Mara’s goal is simple: capture a LoRa packet transmitted from a garden sensor that records soil humidity. The traffic is sporadic, burying itself in a canyon of industrial chatter. But with the pluto’s sensitivity improving from –115 dBm to –130 dBm over recent firmware, Mara knows her chances rise significantly.
She has already written Python scripts harnessing the pyrtlsdr library that stream raw I/Q samples. By locking the center frequency to 868.1 MHz and expanding a 2.5 MHz slice, she opens a window wide enough to catch every LoRa burst.
Tuning Into the Void
First, she adjusts the DAB gain to 35 dB, then hovers over a glass of cold water to practice setting the antenna tuner to a nominal 50 Ω point at the target frequency. The software’s real‑time waterfall confirms an eye‑opening sweep: a low‑amplitude chirp gracefully moving across the spectrum.
With the pluto’s Fast Fourier Transform view, Mara detects the unique interleaving of chirps—each over 125 kHz, each a Libra of linear frequency modulation, echoing through the hallway. She notes that the antenna’s reactive compensation
The First Encounter
When Alex first unplugged the ADALM‑Pluto Revision D from its package, the familiar buzz of the USB port promised more than just a soldered plug. He had just walked into the lab of a former radio engineer, whose desk was a patchwork of antennas, a wall‑mounted oscilloscope, and a whiteboard filled with equations. Alex’s mission was clear: listen to the silent dance of bits that shivered through the 915 MHz band.
Preparing the Playground
After confirming the device was recognized by the operating system, Alex opened GQRX, the Graphical Radio Quest explorer. The Pluto’s internal tuner, an IP3101A, gleamed in the software catalog, welcoming a LoRa frequency sweep. He set the center frequency to 915 MHz and the bandwidth to 1 MHz, a sweet spot that captured both the beacon and the quiet chatter of low‑power packets. The software’s waterfall plot started painting bars and clouds, a digital currency of energy drifting across time.
Chirps on the Horizon
LoRa’s signature was not a module of harmonics but a long chirp, a frequency–swept burst that traveled from 920 MHz to 925 MHz and back. Alex turned the Pluto’s fine‑tune knob, which shifted the tuner in 10 Hz steps, until the waterfall highlighted a steady, golden‑grad “heart‑beat.” He had found the first packet. Using GQRX’s spectral binning, Alex captured this burst and threaded it through a Cayenne LoRa decoder script. The script peeled back the CRC, demultiplexed the output, and revealed a string of hex digits that encoded a sensor’s ID.
Porting the Vision to GNU Radio
To validate and extend his findings, Alex turned to GNU Radio Companion. He stacked a small block chain: Pluto SDR source → demodulate chirp → burst splitter → packet demodulator → decode helper. The plug‑and‑play nature of the Playground’s workflow allowed him to tweak the spread factor from 7 to 12 on the fly, observing how the chirp’s slope flattened with higher SF, a direct relationship to payload length and range. The SDR’s board‑level USB2.0 IO was a bottleneck for the maximal sample rate, but at 1 Msps the SDR comfortably rendered the full 1 MHz LoRa spectrum.
Quieting the Noise
When the band was crowded, Alex added a narrowband notch filter block in the pipeline. By carving out a 10 kHz slice around a stubborn RFID reader, the Pluto’s antenna driver shrugged off the interference. The droplet of interference vanished from the waterfall, and the LoRa chirps rose again. Alex noted that RFSeek could be used to programmatically apply these notches if the board was embedded in a broader sensor‑network.
Walking Through 867 MHz
Transitioning to the European 867 MHz band required a half‑step re‑calibration. Alex adjusted the Pluto’s PLL to lock onto 867 MHz, tuning the I/Q path by the same 10 Hz finetune. The LoRa chirp, now slightly lower in frequency, remained unmistakable. Remnants of the 915 band—such as two neighboring slots—loomed nearby. In the flowchart of the GQRX interface, Alex colored the 868 MHz channel red, the 869 MHz channel green, and the orphaned 868.7 MHz pirate band a faint blue. The whole alive scene proved that the Pluto’s tuner handled both spectrums with equal aplomb.
Story in the Signal
With each packet decoded, Alex felt as if the SDR were tapping the patient pulse of an unseen world. Bots on farms, passengers on scooters, home‑automation points—all sliding across two bands, whispering data in chirps that seemed almost musical. As the sweeping spectrum filled his monitor, the entire narrative—an electric euphony of bits—unfolded like a secret language waiting to be read by anyone willing to listen. The ADALM‑Pluto Revision D had finally become, in Alex’s story, not merely a device but a bridge to a silent network that danced just beyond the human ear at 867 and 915 MHz.
Setting the Stage
In late 2024, the world of low‑power wide‑area networking hit a new milestone when the Analog Devices ADALM‑Pluto Revision D debuted with upgraded firmware that bolstered its UHF performance. My friends in the research lab had been listening in on LoRa foot traffic in the city’s downtown district, hoping to map out the sprawling mesh of IoT sensors that now spanned the entire skyline. The challenge was clear: to capture those faint digital whispers below 1 GHz with enough fidelity that could tease out their hidden addressing schemes.
Reinvented Radio Architecture
The Revision D overhaul introduced a dedicated 433‑MHz front end, a smoother RF switch, and a finer‑grained gain‑control chain. These tweaks meant the Pluto could now lock onto the lower LoRa bands (433 MHz and 915 MHz) without sacrificing sensitivity. I plugged the SDR into a quiet laptop, loaded ZTB3-ZOO on the remote side to bind MyriadBoard with the new firmware, and set the sample rate to 10 Msps to guarantee a clean spectral slice.
Antenna‑Driven Sensitivity
What if you pair that upgraded SDR with the right directional antenna? The band of interest—UHF LoRa—sits just out of reach for the usual omni‑directional dipoles. I fell back on a 2.4‑GHz Horn trimmed for 900 MHz operation, wired through a low‑loss 0.5 dB SMA patch. The antenna’s cardioid shape sliced the urban canyon’s multipath reflections, letting me pick up a single LoRa beacon several hundred meters away. Later, I swapped in a carefully calibrated Yagi array with four elements, optimized for 923.2 MHz. The narrow beamwidth from that made the SDR focus its gaze on a solitary street‑level sensor, reducing interference from neighboring cells and thus improving the demodulation success rate.
Signal Capture and Logging
With the directional antenna locked on, the Pluto streamed raw IQ data to the laptop, where a Python script streamed it to a Matlab workspace over a USB–1.1 pipe. The bash command pluto_export -f 923.2e6 -r 10e6 -s 1M -o lora.raw saved the packet burst for offline analysis. In the tiny suburban canyons of the campus, the LoRa packet burst turned into a clean tone that later seemed to reveal a hunk of data I had been hunting for.
Decoding the LoRa Silence
Using the LoRa Stack v2.0 decode library, I parsed the chirp spread spectrum and extracted the 8‑byte payload. The first word revealed the device ID—1234ABCD—while the second carried a timestamp that matched the local GPS clock. Importantly, the directional bias from the Yagi had reduced adjacent‑channel bleed, letting me recover packets that in earlier trials were lost in noise.
Field Lessons and Future Work
What unfolded in those subtle minutes of capturing LoRa in UHF reminds us that the newest SDR hardware is only as powerful as the antenna choice that accompanies it. In 2025, the ADALM‑Pluto continuous updates will likely add a programmable passband for 868 MHz, but until then, a modest directional element remains the secret weapon for probing LoRa networks. And with the growing interest in private IoT networks, those directional beams will help engineers aggressively guard against unintended eavesdropping, ensuring that low‑power bursts stay exactly where they’re meant to be—on the air, pretty much invisibly threaded across the city’s fabric.
The Quest for Distant LoRa Signals
Every night, when the city lights dimmed to a quiet hum, Alex turned his setup to the horizon, waiting for that faint whisper of a LoRa packet that had to travel long distances through a silvery night. The ADALM‑Pluto Revision D sat on the bench, its clouds of capacitors and tiny solder joints looking almost like a spaceship docked next to a radio tower.
Meet the Analog Devices Altair
During a July 2023 firmware update, Analog Devices published a patch that tweaked the Pluto’s internal firmware, giving Revision D a slight boost in freq‑accurate hopping. The new firmware allows the demodulator to notch out narrow‑band interference with a larger bandwidth,
On a crisp mornings, a quiet experiment unfolded in a small accessories shop that had become a playground for curious engineers. The focal point was an ADALM‑Pluto Revision D, humming softly beside a rack of vinyl cutting tools and an ancient desk lamp that cast a nostalgic glow. The air was scented with solder and the faint sound of a coffee machine. Inside the shop, a new project had taken life: listening to the quiet chatter of the LoRa network that pulsed through the city streets.
First Encounter
Natalie, a seasoned signal‑processing hobbyist, remembered the whispered excitement that went into pointing the Pluto toward the sky. She wanted to capture a burst of LoRa data that ranged just over 27 MHz, far below the usual 2.4 GHz bands. The Revision D board would need some tweaks, and she knew just the right notes to play.
She began with the minimal software bundle supplied by Analog Devices, but soon she found she needed a more elaborate toolkit. Forty‑five minutes later, the GNU Radio companion glowed on her screen, displaying a vast canvas of blocks ready to be connected. It was that day that gr-lora whispered its name in the background code, promising to turn raw radio samples into something human.
Calibrating the Pluto
She started by updating the firmware to the latest STM32F4‑LM4F, rev. D version. After a quick re‑boot, the PLL was locked at a precise 27.000 MHz. The Pluto’s IF filter bandwidth was then set to 800 kHz, a sweet spot that would allow the LoRa carrier to travel while dodging the jagged spikes of out‑of‑band interference.
Next came the calibration curve, a process she approached with the same care she had when tuning a vintage piano. Natalie recorded a continuous sinusoid raw from a laboratory signal generator, then plotted the spectrum to find the center frequency drift. By adjusting the Pluto’s tuning offset in steps of one kilohertz, she realigned the carrier to precisely 27.000 MHz, with an accuracy that surprised even the board.
The GNU Radio Flow
Sitting at her desk, Natalie opened GNU Radio and built the first block. The PlutoSDR source fed raw I/Q samples into a FreqXlating FIR Filter that shifted the 27 MHz baseband down to DC, simplifying the demodulation process. No resampling was required, thanks to the LoRa symbols’ generous bandwidth of 125 kHz.
She then added gr‑lora’s lora‑receiver block, a marvel of open‑source ingenuity. Setting the spreading factor to SF 7 and the code rate to CR 4/5 matched the city‑wide LoRaWAN configuration. The block’s internal low‑pass filter clipped the odd harmonics that might otherwise interfere with the delicate chirp signals used in LoRa transmissions.
On the far right of the flow, Natalie placed a QT GUI sinks block, providing a live waterfall view that split the network into real‑time stories. The demodulated packets arrived as bursts of text, each packet’s payload appearing instantly on the screen. The gr‑lora symbol extraction was flawless; each packet hit the sink in a quiet cascade, showing the time stamps, sequence numbers, and the raw payload.
Demodulating LoRa
To deepen the story, Natalie captured a packet from a nearby weather station that lasted roughly 30 ms. She examined the raw chirp waveform and worked out in detail the rise and fall of the series of frequency hops. Each chirp, in that raw form, carried several hundred symbols: a fact that never ceased to amaze her.
Using Python scripts, she parsed the raw payload, converting the fields into a clear sentence: “Temperature: 18.3 °C, Humidity: 54 %.” The river of data that once floated from a distant sensor now flowed into her local dashboard, all thanks to the gr‑lora block and the careful tuning of the Pluto.
Wrapping Up
As twilight deepened, Natalie's setup sat quiet, silent throughout the night, continuing to listen for more LoRa chatter. The ADALM‑Pluto Revision D became a quiet guardian, and gr‑lora the translator of its silent signals. She would constantly refine her flow, sometimes tweaking the low‑pass filter to shave off that stubborn impulse, or occasionally advancing the PLL offset when a new firmware update arrived.
When she spoke with her peers, she described the tale of how a modest SDR board, entwined with an insightful open‑source block, turned countless beeps in the air into a living archive of the city’s wireless whispers. It was a story born in a workshop, carried through code, and sung in the chirps of LoRa, forever preserving the dialogue between devices that would otherwise remain unheard.
Setting the Stage
When the morning light brushed the bay windows, Emma settled her laptop beside the ADALM‑Pluto Revision D, a compact and affordable software defined radio that had quietly taken the community by storm. She had spent the weekend poring over the latest forum posts, discovering that the latest firmware update for the Pluto now offered better input attenuation and a new calibration routine that made the device even more precise in the sub‑gigahertz band.
Getting the Pluto to Talk to SDRangel
Emma began by launching SDRangel, her favourite SDR front‑end. In the Hardware Input pane she selected the ADALM‑Pluto from the list of available devices. The UI showed the new 12‑bit ADC interface and the updated gain settings, confirming that the firmware upgrade had been successful. The tone on her screen was reassuring: “Device detected. Ready for streaming.” She let the program clock the Pluto’s local oscillator and, after a quick calibrate, got the live waterfall looking like a steady sea of colors.
Choosing the Right Mode for LoRa
LoRa, the low‑power, wide‑area network technology, behaves like a whisper in the spectrum—tiny, but full of information. In the case of her project, Emma wanted to capture and decode the chatter of a village weather station. She dragged and dropped the LoRa demodulator block into the SDRangel processing chain and set the carrier frequency to 868 MHz, the standard European band. The demodulator’s key settings were the spreading factor and the bandwidth; Emma chose a spreading factor of 12 to match the station’s configuration and a bandwidth of 125 kHz, the minimum required for clarity.
Introducing ChirpChat into the Flow
With the demodulator configured, Emma turned her attention to ChirpChat, the open‑source LoRa packet decoder that now supported the SDRangel plugin. She installed the latest ChirpChat‑SDRangel‑plugin from the GitHub release page, right after the big announcement of the 3.2.0 update. That release added a new visualizer for packet timing and improved symbol decoding for the newest EU 600‑kHz band. The plugin appeared in SDRangel’s External Plugins list immediately—her fruitfully updated toolbox was growing more powerful.
The First Capture
Emma pressed Start Stream and watched the waterfall pulse with the station’s bursts. The LoRa demodulator slice of the chain translated the chirps into a sequence of symbols, which ChirpChat then parsed into human‑readable packets. The plugin’s packet list filled up almost instantly, each line revealing a timestamp, payload, and ACK status. She let the system run for ten minutes, watching the debug log show “Packet received – payload: 0x3E5F” and “Signal‑to‑Noise Ratio: +17 dB.”
Fine‑Tuning and Playback
After confirming that the packets were legitimate, Emma decided it was time to replay them. In ChirpChat she accessed the drag‑drop interface, dragged the captured packet to the replay window, and clicked the green button. The output signal was fed back to the SDRangel transmitter module, configured to the same 868 MHz band. After applying a 30‑dB attenuation to avoid clipping, the local transmitter started sending the re‑encoded chirps into the air. The village airwaves answered in kind, and Emma approved the message with a delighted smile.
What Made This Experience Unique
The combination of the ADALM‑Pluto’s low cost and the proven flexibility of SDRangel, enhanced by the brand‑new ChirpChat plugin, made Lily’s weekend both productive and exciting. The real magic came from how smoothly the Pluto’s firmware update unlocked new performance, and how the latest plugin updated to the real‑time needs of LoRa enthusiasts everywhere. The story shows that even a simple SDR can become a window into the internet of things, and that the community’s collaborative spirit keeps buzzing just as strongly as the signals she captures.
The Journey Begins
A quiet weekday afternoon found me hunched over my desk, the ADALM‑Pluto Revision D perched like a silver beetle beside my laptop. The newest revision, released earlier this year, brought a minor firmware tweak that now allows cleaner reception in the 800‑1000 MHz band—just the sweet spot for many LoRa devices in urban environments. The mission was simple yet grand: listen to a sea of LoRa chatter and feed those whispers into a Reticulum mesh network running Meshchat.
Capturing LoRa Waves
First came the setup. I updated the adalm_pluto drivers and flashed the latest firmware via pluto-bootloader. With the device humming, I launched GnuRadio Companion and built a monolithic flowgraph: the Pluto Source at 915 MHz, time‑offset via a GPSDO, a channel‑reduction filter, followed by a LoRa Demodulator block from the gr‑lora repository. The demodulator output a burst‑by‑burst stream of symbols which I piped into a Python script through a TCP socket. This script decoded the LoRa payloads into plain text, while also tagging each frame with its timestamp and RSSI.
Bringing Signals into the Mesh
Next step: the mesh. I installed the current Reticulum stack from the official repository and set up the reticulum.conf file to use satellite‑relay KISS nodes, which are perfect for low‑latency communication. Inside the Python demodulation script, I wrapped the decoded messages in a Reticulum Payload object, specifying a destination nickname that matched the busy mesh node I’d previously configured. The data were then sent across the mesh with a low‑priority queuing policy to keep the network from choking on the swarms of LoRa packets.
Meshchat in Action
With the payloads now dancing through the mesh, it was time to let Meshchat take the reins. After installing the latest meshchat package via pip install meshchat, I launched the client and logged onto the same nickname I’d used in the Reticulum script. The client, in its gentle chat interface, began showing the incoming LoRa messages as markdown‑styled chat bubbles. A few minutes later, a user in a remote ham‑radio shack typed back a report: “Got the LoRa storm the other night—our antenna caught a burst from the university testbed. The node relayed it here in no time.”
Throughout the night, I tuned the Pluto’s local oscillator to hunt for sidebands and experimented with channel‑width adjustments inside GnuRadio. Every tweak translated into more reliable demodulation, and consequently, cleaner messages inside the mesh. The glow of the terminal echoed the glow of the Pacific horizon, where the LoRa waves carried whispers of rural communities and the mesh carried them to the heart of a sprawling urban network.
Closing the Loop
At dawn, the story closed with the conclusion that the intersection of a low‑cost SDR, an open‑source mesh stack, and a lightweight chat client can truly democratize signal processing. The ADALM‑Pluto Revision D kept the LoRa signals in a clean, readable packet; the Python script bridged the physical layer to the logical mesh; and Meshchat turned raw data into a conversation that anyone could read. It’s a narrative that proves once again that with the right tools, the universe’s faintest whispers can become the next sentence in our collective dialogue.
Setting the Stage
It began on a quiet Saturday afternoon, the kind of day that invites experimentation. In a corner of the home lab, a rugged ADALM‑Pluto Revision D sat on a wooden shelf, its silicon heart beating quietly as it waited for the first command. The Revision D had a new firmware release in mid‑2023 that added a LoRa mode to its already versatile radio engine, and the lab’s RnodeInterface library had just dropped version 0.14, ready to bridge the hardware to the world of sub‑Ghz communication.
From Firmware to LoRa
After updating the Pluto’s firmware via SoapyPlutoSDR, I opened the terminal and launched the RnodeInterface command line tool. Signatures of the newly added LoRa parameters were visible: lora_frequency, lora_spreading_factor, and lora_bandwidth. Setting the device to 915 MHz, a spreading factor of 12, and a bandwidth of 125 kHz, I wrote a quick Python script to freeze the radio into this mode. In the console output, a green checkmark appeared, confirming the Pluto had moved into LoRa land.
Connecting with RnodeInterface
With the radio locked, the next step was to tame the interface. The RnodeInterface library uses a simple serial protocol that the Pluto’s GPIO pins expose through a Raspberry Pi acting as a bridge. I connected the Pi’s UART to the Pluto’s aux serial pins, ran rnode‑iface‑config --baud 115200, and watched the serial handshakes dot the screen. The library’s Python wrapper, rnode, offered a clean API: rnode.set("lora_tx_power", 18) to crank the output to 18 dBm; rnode.listen() to start a passive receiver; rnode.send("Hello, Pluto!") to transmit. Each call returned a timestamped acknowledgment, and the responses were parsed by a small JSON wrapper that the script printed to the console.
Reticulum Meshchat Comes Alive
Once the Pluto could talk LoRa, I felt the breeze of possibility drift through the lab. I wanted a way to gossip across the mesh without choking the network with broadcast storms. Reticulum Meshchat, the light‑weight messaging layer built on the Reticulum Protocol, fit the bill. I cloned the corporift/reticulum repository, patched it to accept LoRa packets from the RnodeInterface, and launched the background service on the same Raspberry Pi.
Configuration was modest. In the reticulum.conf file I set interface = rnode and range = 2 to limit hops, then executed reticulum‑start. The service wrote log entries every few seconds: rx lora 923.968MHz 20kbps LoRaRx 08:15:23 77#NodeA# Hello!. It was clear that the machine was now receiving LoRa packets, decoding them through the Rnode wrapper, and injecting them into the Reticulum network stack.
Two‑Way Communications
From the viewpoint of the lab, the success of the loopback felt like dusk turning into dawn. I opened a second terminal on a second Pi, running the same Reticulum Meshchat service, but with node_id = NodeB
© 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.