ESP32 software-defined radio experiments have moved beyond listening to an early demonstration of transmission and reception. Hackaday reports that developer marble released transmit-capable firmware and demonstrated communication between an ESP32-S3 and an ESP32-C6 using a radio mode called Hellschreiber.
The starting point was access to raw radio samples. The report describes two apparently simultaneous hacks that exposed those samples from the 2.4 GHz radios inside many ESP32 variants, turning them into listen-only software-defined radio, or SDR, platforms. That distinction explains what the newer firmware adds: the earlier work exposed received samples, while marble’s firmware can also transmit.
From observing signals to creating them
Why is that exciting? A receiver lets an experimenter observe signals and work out how to decode them. Adding transmission closes the loop: developers can generate a waveform, send it to another device and test whether their receiver recovers the message. It turns a listening experiment into a platform for trying out communication techniques.
The project repository describes the mechanism as I/Q capture from the receiver and I/Q playback through the transmit digital-to-analog converter. I/Q samples are paired numbers that represent a signal’s amplitude and phase. Working at that level gives software control over the waveform, rather than merely handing a Wi-Fi packet to the chip’s normal networking software. The Zephyr-based project builds on and extends the ESPARGOS esp-sdr work.
That is what makes the Hellschreiber link impressive: it uses an integrated Wi-Fi radio to carry a signal outside the Wi-Fi specification. Hellschreiber conveys text as a pattern of dots, rather like transmitting a tiny printed image. The achievement is not a faster Wi-Fi connection; it is showing that the hardware can be repurposed to communicate in a different way.
The reported reception in gqrx also matters beyond the demonstration. The repository includes a SoapySDR module for gqrx and GNU Radio, connecting the experiment to established SDR software. That offers a route to inspecting signals and developing signal-processing experiments with familiar tools, rather than building every part of the workflow from scratch. For education and wireless prototyping, the attraction is exploring those ideas on ESP32 hardware a developer may already have.
What it could mean for other wireless technology
There are important limits. The project explicitly warns that it is not intended or qualified for production use. Its SDR initialization takes over the radio brought up by the Wi-Fi driver, and the documentation says not to scan, connect or start an access point while using it. This is therefore not simply an extra radio feature running alongside normal Wi-Fi, nor has the demonstration established it as a replacement for a dedicated, broadly tunable SDR.
ZigBee is a separate prospect, not another demonstrated feature. Hackaday says marble was working on 802.15.4 modulation and suggests that ZigBee communication might follow. The distinction is between a working example and a development goal: the Hellschreiber demonstration shows transmission and reception, while the reported 802.15.4 work remains unfinished.
IEEE 802.15.4 supplies the lower-level wireless foundation used by ZigBee and Thread. Experimenting with its modulation could help developers investigate how those signals are generated and received. But producing a compatible waveform is not the same as implementing a complete ZigBee device: packet handling, network formation, security and application behavior would still need to work together.
Nor would this be the first route to ZigBee on the ESP32 family: the ESP32-C6 already has native 802.15.4 support. The broader promise of the SDR approach is flexibility for experimentation—not replacing a supported protocol stack with a hack. Its significance is that a radio normally used through fixed networking interfaces is becoming accessible as a more programmable component.