After picking up the sBitx v3 from HF Signals at the recent LARC8 event in Hyderabad, I’ve spent considerable time exploring it—not just on-air, but under the hood. This is not merely another HF transceiver competing with commercial brands. The sBitx v3 is something fundamentally different: a Linux-powered SDR platform that happens to be a radio.
For many Indian hams who grew up building, modifying, and dreaming over Ashhar Farhan VU3ESE‘s legendary Bitx designs, the sBitx feels like the natural and ultimate evolution of that legacy. It carries the same experimental DNA, just updated for the Raspberry Pi era. Linux SDR

sBitx v3 Architecture: Not Just a Radio, but a Computer with RF
At its core, the sBitx v3 is a Raspberry Pi 4 running Linux, tightly integrated with an HF RF deck. This architectural choice defines everything—both its strengths and its frustrations.
You are not dealing with fixed firmware inside a sealed black box. Instead, you’re interacting with:
- A full Linux operating system
- SDR signal processing done in software
- Open-source control logic
- Real hardware that you can actually probe, modify, and repair
This immediately sets expectations: the sBitx is not an appliance, and it doesn’t pretend to be one. It’s a platform for experimentation, learning, and genuine radio craft.
The All-in-One Experience: Surprisingly Liberating
The most phenomenal aspect of the sBitx v3 is how self-contained it is. I’ve been using the built-in FT8 engine for several contacts, and when it works, it feels almost magical—no laptop, no audio cables, no CAT interface boxes. Just power, antenna, and you’re on the air.
That said, the internal logging can be intermittent, which becomes frustrating during pile-ups or rapid QSOs. Losing a contact entry after successfully decoding is never fun.

Enter JTDX: The Power of Linux Flexibility
To work around this, I installed JTDX directly on the radio itself. This is where the Linux foundation really shines. Once installed, the sBitx becomes a fully self-contained digital station. For portable or mobile operation, not carrying a laptop is a massive relief.
The same flexibility extends to other applications. Want WSJT-X instead? No problem. Prefer Fldigi for RTTY or PSK31? Install it. The radio becomes whatever you need it to be.
Physical Design: Built for the Field
The built-in speaker deserves special mention. Audio quality is surprisingly rich and clean, far better than expected for a compact SDR rig. Combined with the large touchscreen, digital waterfalls look excellent, making extended operating sessions comfortable.
The metal enclosure feels rugged and field-ready. For POTA or portable operations, it inspires confidence. The size and weight hit that sweet spot—portable enough to carry, substantial enough to feel serious.
Remote Operation: The Couch-Shack Revolution
One area where the sBitx v3 genuinely outshines many big-brand radios is remote operation. Using RealVNC, I regularly operate the radio from:
- An iPad while relaxing on the couch
- A MacBook from another room
- Any browser-enabled device on my network
The radio can sit quietly in the shack while I operate comfortably wherever I please. The web interface and VNC access are both stable and responsive, making remote operation feel natural rather than hacked together.
For late-night FT8 sessions or casual band scanning, this capability transforms how you interact with your station. No need to be tethered to the desk. No complicated remote software licensing. Just connect and operate.

A Surprising Comparison: sBitx V3 vs IC-705
Interestingly, I often find myself preferring the sBitx over my Icom IC-705. Both radios are nearly the same size, but the sBitx offers:
- More flexible filter shaping
- Deeper RX parameter control
- A more experimental, adjustable signal chain
- The ability to run any Linux software you can compile
The IC-705 feels like a polished appliance—refined, predictable, and closed. The sBitx feels like a lab instrument you can reshape to your liking. Different tools for different mindsets.
If you want to push a button and know exactly what will happen, the IC-705 wins. If you want to understand why it happens and change the outcome, the sBitx wins.
The Technical Reality: Strengths and Pain Points
What the sBitx v3 Does Exceptionally Well
1. Open Source Everything
The entire software stack is fully open, and development is ongoing. Volunteer developers regularly push updates, improvements, and bug fixes. Check the GitHub repository, and you’ll find commits from just days ago. This is a living project, not a frozen product.
2. Deep Customization
If you don’t like how something behaves, you can literally change it. Filters, UI behavior, DSP parameters—everything is accessible if you’re willing to dig into the code. The radio becomes an extension of your technical curiosity.
3. Excellent Filter Control
The adjustable bandwidth filters are a joy to use. Whether conditions are crowded or noisy, you can tailor the receive audio precisely to your taste. Narrow it down for a weak DX station, or open it up for natural SSB audio.
4. Solid Physical Build
The metal enclosure feels rugged and field-ready. The front panel controls are responsive. The connectors are properly mounted. This isn’t a delicate lab prototype—it’s field-deployable hardware.
5. Price-to-Capability Ratio
At roughly one-third the cost of comparable commercial SDR rigs, the sBitx delivers remarkable value—especially when you factor in the built-in touchscreen, speaker, and Linux computer.
Where the Frustrations Begin
1. Power Output on Higher Bands
While the radio performs well on lower HF bands, output power drops noticeably on 10m and 12m, often struggling to exceed 8–10 watts. For contest operation or chasing weak DX on these bands, this is a real limitation.
Some users report better results after careful tuning and alignment, but out-of-the-box performance varies. If you primarily operate on 20m and below, this won’t affect you much.
2. User Interface Quirks
The touchscreen UI can feel clunky. Menu navigation sometimes requires multiple presses, and touchscreen calibration can drift over time. It works—but it doesn’t always feel refined.
The good news? Because it’s open source, UI improvements are actively being developed. The bad news? You’re beta testing in real-time.
3. No Reverse Polarity Protection
This is a serious concern. One accidental power connection mistake can permanently damage the board. I strongly recommend adding external reverse polarity protection—either a physical diode solution or a properly rated fuse setup. This isn’t a beginner-friendly oversight. It requires real caution.
4. Missing Convenience Features
There is:
- No internal antenna tuner (external required)
- No internal battery (though the 12V input makes portable power simple)
- Band coverage limited to 80m–10m (no 160m or 6m)
These aren’t deal-breakers, but they do mean additional accessories for field operation. A good external ATU becomes essential.
5. Documentation Gaps
Because the project evolved through the DE version, V1, V2, and now V3, documentation is fragmented. Old forum posts reference outdated procedures. GitHub wikis contain remnants of earlier designs.
For newcomers unfamiliar with Linux or SDR concepts, this learning curve can be steep. However, the active community on the Facebook group and forums is generally helpful and responsive.
Receiver Performance: Where It Truly Shines
One aspect that deserves deeper attention is the receiver performance. The SDR architecture, combined with thoughtful software implementation, delivers:
- Excellent dynamic range for handling strong signals
- Low noise floor that pulls weak stations out of the mud
- Flexible AGC settings that adapt to different operating modes
- Sharp, configurable filters that eliminate adjacent interference
Compared to older hybrid or analog rigs, the sBitx receiver feels modern and capable. Yes, big-dollar commercial transceivers still have the edge in extreme cases, but for everyday HF operation, the sBitx holds its own remarkably well.
Is the sBitx v3 an “Appliance Radio”?
Absolutely not—and that’s the point.
If you expect a Kenwood, Yaesu, or Icom experience at one-third the cost, you will be disappointed. The sBitx is not designed for that audience.
Post-purchase support relies heavily on:
- Community forums
- The active Facebook group
- Fellow experimenters
- Your own technical abilities
There is no traditional “send it to the service center” comfort. However, if you are the kind of ham who:
- Enjoys holding a soldering iron
- Is comfortable at the Linux command line
- Likes understanding how things actually work
- Values true ownership over convenience
Then the sBitx offers something rare: genuine ownership. You can repair it, modify it, and improve it yourself—something almost impossible with modern commercial rigs locked behind encrypted firmware and proprietary protocols.
Who Should (and Shouldn’t) Buy the sBitx v3?
You’ll Love This Radio If:
- You grew up with Bitx designs and want the modern evolution
- You’re comfortable with Linux and basic troubleshooting
- You value hackability over plug-and-play convenience
- You enjoy experimenting with DSP and signal processing
- You want a truly portable digital station without a laptop
- You appreciate active, ongoing development
Look Elsewhere If:
- You want polished, appliance-like reliability
- You expect factory support and warranty repairs
- You need consistent power output across all bands
- You’re uncomfortable with occasional software bugs
- You prefer closed systems that “just work” out of the box
sBitx v3: A Rough Diamond Worth Polishing
The sBitx v3 is not perfect, and honestly, that’s part of its charm. It is a hackable, experimental SDR that brings back the joy of learning, breaking, fixing, and improving.
Ashhar Farhan (VU3ESE) continues to provide software updates freely, and the hardware platform keeps evolving. Watching the GitHub commits roll in, seeing community members solve problems and share solutions—it feels like amateur radio used to be. It feels like radio craft.
This radio rewards curiosity. It punishes carelessness. And it absolutely refuses to be boring.
If you work me on FT8 from a park, chances are I’ll be using this radio. It may be a rough diamond, but for an Indian ham who loves to tinker, experiment, and truly understand their station, there is simply nothing else like it on the market today.
The sBitx v3 isn’t trying to be the best radio. It’s trying to be the most honest one. And in that mission, it succeeds brilliantly.
Credits and Acknowledgments
It is necessary to clarify and give proper credit to the individuals involved in the ongoing development of sBITX. Although the original idea and initial direction of the project were started by Farhan, the current status and continued relevance of sBITX are the result of the hard work of a much larger community of individuals.
A large part of the software development, maintenance, improvements, bug fixes, and feature additions have been done by the sBITX volunteer development team, coordinated through the GitHub repository found at https://github.com/drexjj/sbitx. The individuals listed on this page, including the project maintainer and several community developers, have all contributed thousands of hours of work to the development of the platform.
The purpose of this article is to give credit to the individuals who started the project and to the large number of individuals who have contributed to the ongoing development of sBITX into the capable, modern, and interesting Linux-based SDR platform that it is today.
73 and happy hacking!
Have you built or operated an sBitx? Share your experiences in the comments below. What modifications have you made? What’s your favorite feature?
Related Posts

Your article praises several features but attributes them solely to Farhan without any mention of the substantial work done by me and the volunteer development team.
The contributors listed on my GitHub, including myself, have collectively invested thousands more hours into the project than Farhan has, especially since he largely stepped away from the software and stopped actively maintaining or developing it.
You might want to edit your article to give credit where credit is due.
refer article again