(tr)uSDX vs QMX+ 160–6m: Two Very Different Paths to “Small, Capable QRP”

If you’ve been shopping the “pocket QRP” universe lately, you’ve probably noticed a theme: a lot of capability is now available in surprisingly small, affordable radios. Two of the most discussed options are the (tr)uSDX and the QRP Labs QMX+ 160–6m multi-mode transceiver.

They overlap in intent—portable, low-power HF operation—but their design philosophy is very different. The (tr)uSDX emphasizes ultra-compact, efficient, minimalist hardware with broad mode support. The QMX+ emphasizes integration and computer-friendly operation, especially for digital modes, via a built-in USB sound interface and CAT control. QRP Labs+1


At-a-glance comparison

Category(tr)uSDXQMX+ 160–6m multi-mode
Bands (typical / default)Marketed as 5-band, commonly 80/60/40/30/20m by default; other band/filter setups exist12 bands, 160m–6m DL2MAN+2QRP Labs+2
ModesSSB (LSB/USB), CW, AM, FM DL2MAN+1CW, Digi, SSB (multi-mode) QRP Labs+1
Output power (headline)QRP (varies by build/supply; commonly discussed as a few watts class)~5W class (documentation/marketing headline) QRP Labs+1
Digital modes workflowOften workable, but usually requires a more “DIY” approach (software/adapter approaches exist) GitHubDesigned for digi: built-in 24-bit 48 ksps USB sound card + CAT control QRP Labs+1
Form factor & intent“Pocket format” focus; onboard mic/speaker and minimalist field usability highlighted DL2MAN+1Compact kit with strong PC integration; optional internal GPS module mentioned QRP Labs
EcosystemMultiple firmware branches and community variants GitHub+1Single-vendor documentation + kit ecosystem from QRP Labs QRP Labs+1

Design philosophy: “portable radio” vs “portable station”

(tr)uSDX: radio-first minimalism

The (tr)uSDX identity is tied to being a pocket transceiver with a very small footprint and simple field usability features (onboard mic, small speaker, OLED UI, and a basic “get on the air” mindset). DL2MAN

Where it shines:

  • Fast setup for casual portable SSB/CW work.
  • A UI/mode set that includes AM and FM in addition to the usual SSB/CW expectations in this class. DL2MAN+1

QMX+: station-in-a-box integration

The QMX+ is positioned as an embedded-SDR, computer-friendly transceiver. The big differentiator is the integrated USB audio interface (24-bit/48 ksps) and CAT control, plus the option for an internal GPS module. QRP Labs+1

Where it shines:

  • A highly streamlined path to FT8/FT4/JS8Call and other soundcard modes without external audio interfaces.
  • Band coverage that’s hard to match for the size/cost: 160m through 6m. QRP Labs+1

Bands: this is usually the deciding factor

If you want maximum band coverage from one small radio, QMX+ is clearly oriented that way: 12 bands from 160–6m. QRP Labs+1

The (tr)uSDX, by contrast, is widely characterized as a 5-band radio by default, commonly shipping/assembled around 80/60/40/30/20m (with alternate filter configurations possible depending on variant/build). DL2MAN

Practical takeaway

  • If your portable operating is mostly 40/20 (and maybe 30/17/15/10) you may not miss 160 or 6.
  • If you want a single small rig that meaningfully covers top band experimentation, NVIS options, and 6m openings, QMX+ is built for that. QRP Labs+1

Modes and operating style

Voice modes

  • (tr)uSDX explicitly supports LSB/USB, CW, AM, FM. That AM/FM inclusion is unusual in the tiny-QRP SSB/CW category and can be a nice flexibility win depending on your goals. DL2MAN+1
  • QMX+ markets itself as multi-mode CW, Digi, SSB—less about “everything,” more about the modes most people use on HF/6 for QRP contacts and computer modes. QRP Labs+1

Digital modes (where QMX+ pulls ahead on convenience)

This is the QMX+ home-field advantage: integrated USB sound and CAT control reduce the “portable mess” to essentially: laptop + USB cable + radio + battery. QRP Labs+1

The (tr)uSDX can be used for digital with additional effort and tooling; there are community projects/scripts designed to pass audio over its USB serial interface, but it’s not the same “native soundcard radio” experience as QMX+. GitHub

If your primary operating is WSJT-X/FT8, QMX+ will generally feel like the more purpose-built instrument. QRP Labs+1


Firmware, community, and “what you’re really buying”

With the (tr)uSDX ecosystem, you’re also “buying into” a broader set of variants and firmware branches—for better (innovation, customization) and sometimes for worse (version fragmentation, differing behaviors by hardware revision). GitHub+1

QMX+ is more of a single-vendor, document-driven kit product—you build and operate it in the QRP Labs ecosystem, with structured manuals and revision-specific docs. QRP Labs+1


Recommendations by operator profile

Choose QMX+ 160–6m if…

  • You operate digital modes frequently and want the cleanest laptop workflow (USB sound + CAT). QRP Labs+1
  • You want one small radio that covers 160–6m for experimentation and band agility. QRP Labs+1
  • You prefer a more standardized kit/documentation ecosystem. QRP Labs+1

Choose (tr)uSDX if…

  • You want a pocket-first field radio that’s straightforward for SSB/CW and includes AM/FM flexibility. DL2MAN+1
  • Your operating focus is primarily in the classic portable HF bands and you don’t need 160/6 in this form factor. DL2MAN
  • You enjoy a more tinker-friendly ecosystem with multiple firmware/community paths. GitHub+1

Bottom line

  • The (tr)uSDX is best described as a radio you can throw in a pocket and use in a broadly self-contained way—especially if your portable priorities are voice + CW and you appreciate AM/FM availability. DL2MAN+1
  • The QMX+ 160–6m is best described as a portable station core—a compact transceiver explicitly designed to make digital + CAT operation easy while providing exceptional band coverage in its size and price class. QRP Labs+1

If you tell me how you operate most (POTA SSB? CW? FT8 from a laptop/tablet? battery voltage you standardize on?), I can tailor a “which one fits your go-kit” recommendation and include a suggested accessory list (power, cabling, audio, logging) matched to your workflow.

Leave a Reply

Your email address will not be published. Required fields are marked *