RimuSDR for Linux — Now Available

Trucker

That's why it's nice to have choices. Without the Flex Radio API, AetherSDR, RimuSDR, and Markus version of SmartSDR would not exist. I believe that Flex Radio has kept SmartSDR simplified to allow 3rd party developers to create software for their radios. And it is a win for Flex Radio whether we use only SmartSDR or, one of the other interfaces available now. I don't see a problem with any of them. ( paid or for free)

James

WD5GWY

Doug - W3UB

Yep, choices are good!

Doug

TimW

The choices are good, and have a hidden benefit. I setup a Linux desktop machine just to try the Rimu client. I’ve had a ton of fun learning the Linux ecosystem. It’s been very educational, and this is from someone who had traditionally disliked Linux desktops. Windows 11 is turning into a real POS if you ask me.

Doug - W3UB

Yep, I’m never going to Win11. If you want to stick with Win10 you can subscribe to 0 patch. Or try Linux or OSX.

Doug

NV0E

RimuSDR v1.1.8 Release Announcement

RimuSDR v1.1.8 is now live, bringing two of the most requested integrations to the native Linux SDR client for FlexRadio: full FlexControl knob support and native Antenna Genius control. This update also includes performance boosts, workflow refinements, and a wide set of fixes across the suite.

Key Enhancements

• FlexControl Knob Fully supported with smooth, low latency hardware tuning.
• Antenna Genius Native control, including switching and configuration.
• Waterfall Performance Reduced CPU usage across all platforms.
• Audio Path Improvements RX buffer flush and Opus suppression during TX for cleaner transitions.
• Spot Levels Increased to 15 levels.
• MIDI Enhancements Better device detection, loopback filtering, new actions, UI refinements.
• SmartLink Login More reliable authentication flow.
• RimuDAX New statistics dialog and improved audio path.

Platform Updates

• Ubuntu 24.04 and 26.04 on aarch64 now fully supported for the entire RimuSDR suite (deb and AppImage).
• Fedora 44 now supported (rpm).
• Fedora 42 discontinued (EOL).

Fixes

• Panadapter Handling Multiple panadapter open issue resolved.
• Diversity Panel Gain and phase values now shown correctly.
• SmartLink Caching Caching behavior corrected.
• Waterfall Time Scale Drag regression resolved.
• Spectrum Fill Setting now saves properly.
• MIDI Detection Device detection fixed on Windows.
• Spot Overflow Overflow handling corrected.
• FM OPT and XVTR Settings now persist.
• FM Property Updates Slice flag and RX panel now update correctly.

TimW

Nice upgrade. Thanks for your efforts. Can’t wait to move the Flex Control device over from old PC.

TimW

Is there a trick to get the Flex Control working? The tty device seems to be detected okay in the configuration screen, however buttons and knob are unresponsive in the app. I might try rebooting. I did restart the app but no joy. Also, device is identified correctly in the USB section of the system information app as supplied by Mint.

Dan Trainor

So many nice new choices for applications on the client side. Both full featured SDR apps and also many new companions apps. The new ideas and creativity is impressive. And the platform support is great. Linux, Mac, iOS, Android, and Windows. Incredible. Development of some/most of these apps accelerated by AI assistance. We are entering a New Era of really really Smart client applications and new innovations. And, It has breathed new life into my 6000 series radios, for sure. I operate 95% of time Remote using my MacBook with external display. SmartSDR for Mac (Marcus) and now increasingly more use of AetherSDR for Mac. Although, I am now motivated to try Linux. So many new options and opportunities. Choices, It is a beautiful thing! Dan de WA1QZX.

NV0E

Hi Tim,

Let me know if rebooting helped, I haven't had any issues with the Flex Control. In fact, its been very robust and it just seems to work every time. Here are my settings, if that helps. The USB device name in Linux will likely vary.

NV0E

RimuSDR v1.1.9 Release Announcement

RimuSDR v1.1.9 is now live, delivering another highly requested integration: native Power Genius XL control directly inside the client.

Enhancements

• Power Genius XL control : Full native integration with a built‑in control panel for quick access and monitoring.
• Radio toast messages : New popup toast notifications for radio events, improving operator awareness without interrupting workflow.

TimW

I managed to get my Flex Control working by adding my user to the dialout group. When I get time I’ll go through the logs and see if a permissions error was journaled anywhere. A log off, log on was required.

NV0E

Oh, of course! In Linux, access to serial ports requires the user be in the dialout group. Its in the RimuCAT instructions, but I need to add it to the general instructions. Thanks Tim!

NV0E

RimuSDR v1.1.10 - Release Announcement

RimuSDR v1.1.10 is now live. This update delivers two SmartSDR+‑aligned enhancements along with a focused set of reliability and workflow fixes.

RimuSDR can be found here: https://rimusystems.com/

Key Enhancements

• TX Passband - Adds the SmartSDR+ TX Passband feature, now fully implemented in RimuSDR.
• Filter Settings - If the radio has SmartSDR+, RimuSDR now honors the radio’s native filter settings. Otherwise, locally stored filter settings are used.

Fixes

• SmartLink Manager now correctly uses the new login dialog.
• RimuDAX now opens RX Streams properly when operating over SmartLink.
• Slice Flag Audio menu UI glitch resolved.
• Digital Offset added to the Slice DSP panel.
• Radio Discovery now falls back to serial number when no nickname is present.
• Slice Panel repositioning lag eliminated when dragging the slice tuning flag with panels open.
• RIT implementation corrected for proper visual behavior.
• RTTY Mark/Shift implementation fixed.
• Audio Settings no longer require pressing Apply button

NV0E

RimuSDR v1.1.11 — Release Announcement

v1.1.11 is now live. This is a packaging‑only maintenance release — all applications are unchanged from 1.1.10.
RimuSDR can be found here: Rimu Systems LLC — Native Linux SDR for FlexRadio.

Linux packages have been corrected to install and launch reliably on clean and minimal systems. Several issues were silent on typical desktops and only surfaced on minimal installs or newer distributions. Windows and AppImage builds were unaffected.

All packages are now validated by automated install‑and‑launch tests in clean Ubuntu 24.04, Ubuntu 26.04, and Fedora 43/44 environments before shipping.

Fixes

• RimuSDR — Qt Network Bundling
  Fixed startup crash on Fedora 44 (and other systems with Qt 6.11+) — Qt Network library is now bundled.
• RimuSDR — .deb ALSA Dependency
  Fixed .deb packages failing to start on minimal Debian/Ubuntu systems due to missing ALSA dependency.
• RimuDAX — Minimal System Dependencies
  Fixed launch failures on minimal Debian/Ubuntu systems — ALSA and libsecret dependencies now declared.
• RimuDAX — Fedora libxcb-cursor
  Fixed failure to start on minimal Fedora installs due to missing libxcb‑cursor.
• RimuCAT — .deb libsecret Dependency
  Fixed .deb packages failing to start on minimal Debian/Ubuntu systems due to missing libsecret dependency.

NV0E

RimuSDR v1.1.12 — Release Announcement

RimuSDR v1.1.12 is now live. This is a large release adding a lot of requested features and a significant number of stability fixes.

RimuSDR can be found here: RimuSDR - Native Linux SDR for FlexRadio

Enhancements

• Tuner Genius XL Support — RimuSDR now detects a TGXL on the network and exposes a full control panel when present.
• Wavelog / Cloudlog Integration — New RimuCAT port type enabling direct HTTP API integration. Live frequency/mode/power updates flow into the logbook, and click‑to‑tune commands return to the radio — no WaveLogGate or CloudlogCAT required.
• Waterfall History Scrolling — Operators can pause the waterfall and scroll backward through captured history.
• HamLib Protocol Support — New RimuCAT port type providing HamLib compatibility for third‑party apps lacking Flex‑style CAT support.
• MIDI Keyer Support — Added CW keying over MIDI; verified with CTR2 and HaliKey. Compatible with other MIDI keyers.
• Direct IP Radio Connection — Radios can now be connected via manually entered IP address for VPN/segmented network operation.
• Zoom to Band / Segment — Added missing zoom features to the panadapter.
• Application Log Governance — Log rotation + size limits prevent runaway growth under debug logging.

Fixes

• Panadapter Visibility — Off‑screen manual frequency entry now repositions the panadapter correctly.
• Waterfall Sync — Waterfall no longer lags after external frequency changes.
• Slice Dragging Behavior — Panadapter no longer pans when the operator intends to drag a slice.
• Off‑Screen Slice Indicators — Clicking an off‑screen slice indicator restores the slice to view.
• External Tuning Handling — External frequency changes are no longer ignored after knob/keyboard tuning.
• DAX RX Gain — RX gain slider now works correctly under MultiFlex.
• Memory Handling Cleanup — Fixed issues across all three applications that left memory in use.
• RimuSDR SEGFAULT — Fixed unsafe multi‑thread variable access triggered when RimuCAT connects.
• Artix Linux AppImage Error — Removed indirect reference to a systemd library not present on Artix.
• MultiFlex API Fixes — Several API corrections to support MultiFlex.
• Thread Safety — Added mutex guards throughout the API layer.
• Windows Crash‑on‑Close — Fixed WASAPI initialize/uninitialize issues.
• WWV/GEN Band Buttons — Sent literal labels instead of numeric codes; now handled correctly.
• Manual Slice Frequency Entry — Now recenters the panadapter and shows off‑screen indicators.
• License Class Dropdown — Band‑privileges JSON now reliably staged.
• Audio Device Refresh — PulseAudioEngine’s refresh now works.
• CW Sidetone Latency Overhaul — Dedicated low‑latency stream with sample‑accurate keying; latency significantly reduced.
• Right‑Side Panel Flicker — Eliminated flicker caused by cached slice values during band changes.
• RimuDAX Audit Remediation — Fixed missing event handlers after reconnect, TX audio glitch, and stuck MOX silence path.
• RimuDAX Crash/Race Fixes — Closed use‑after‑free and lost‑wakeup bugs in RX/Mic/TX teardown.
• RimuCAT Audit Remediation — Fixed CommandQueue use‑after‑free, PTY corruption, CPU busy‑spin, shared‑pointer races, and a log filter bug hiding warnings.

Trevor Hopps

Thanks Simon, I've struggled through the years with my flex6500. I hated the idea of smartsdr being proprietary and having to run it on windows. You have just enabled me to be free of that last legacy. Installed it last night on cachyos (Appimage) with not a lot of hope to be honest given cachyos optimisations etc. This is a cachyos install on a virtual machine running on a small nuc in my homelab. I was very suprised at just how good it looked and worked straight out of the (we used to say box) downloads directory. No issues with audio (Cachyos uses pipewire) and no issues with the Dax cables to other applications. Happily paid for the license fee and will continue to follow as the roadmap develops. Thanks again. Trevor . VK8TH

NV0E

Hi Trevor,

Thank you for the kind words, and I am really glad to hear RimuSDR ran smoothly on your CachyOS setup, especially with all the VM and PipeWire layers in the mix.

I appreciate you supporting the project, and I am happy it helped you finally break free from the last bit of Windows in your Flex workflow.

You are always welcome to send any enhancement ideas or bug reports to support@rimusystems.com, they help shape the roadmap and keep things moving in the right direction.

Thanks again, and 73.
Simon

RKB

Good Afternoon,

I too have been able to say goodbye to Microsoft, as more software developers build quality products based on Linux.

I recently purchased my first Flex Radio after establishing that I could obtain and run it without compromise on Linux based software, it's certainly been an experience. Firstly a Radio with no knobs or buttons and software that is not full ads and hooks.

I have settled on Debian 14 for my operating system, RimuSDR, SDRLogger Plus and SDC Skimmer for my core software.

One of the reasons I decided on RimuSDR was that it was 'Paid Software', I believe that 'Paid Software' has a chance of rapid and sustained development due to the fact that the developer has that additional incentive of income, I guess time will tell.

The systems that I am using all fit together well, without a lot of hassles. Not being a 'Power' user one of the Linux issues I have had in the past has been the creation and use of Ports. RimuSDR has this covered well.

I discovered a very long time ago that most things are not better, they are just different which allows innovation and choice.

Looking forward to the future of our rapidly changing hobby.

RKB

Good Afternoon,

I am looking to either modify the Display Sub Band IARU Region 3 or create a Custom one. I read it can be done, however I need a starting point.

If you can assist me I will be most grateful.

NV0E

Hi Ron,

Thank you very much for your messages, and for purchasing RimuSDR. I’m really glad to hear you’ve had a smooth start on Debian. Welcome to the Linux side of FlexRadio operating. It’s great to see more operators discovering that Linux on the desktop is now mature and well supported with software.

I appreciate your comments about paid software. I share the same view: having a commercial model gives me the ability to keep development moving quickly and consistently. With the widespread use of AI tools in modern software development, and the very real cost of those tools, along with hosting and infrastructure, a paid model is simply the sensible way to offer software that can continue improving. In truth, the revenue mostly covers those costs and not much more, but it does make ongoing development viable.

Regarding the Display Sub‑Band for IARU Region 3: yes, you can create a custom one. I’ll add more instructions to the website with examples. Once you have a finished file, please send it to me and I’ll include it in the base package for the benefit of all VK operators.

NV0E

Hi Ron,

Here are instructions on customizing the sub-bands for a given region: Customizing sub-band privileges

Let us know if you need help, or have any other suggestions.

All the best.

KD0RC

Very cool Simon! The write-up looks great.

g4ivv

For any UK users of RimuSDR, I have published a first draft of a UK sub-bands file on GitHub here:

https://github.com/g4ivv/rimusdr-uk-subbands

I think I've got it OK, let me know if you spot any mistakes.

Jonathan G4IVV

RKB

Good Morning,

I am having an issue Docking the CWX.

When I select CWS it pops up here, dragging it does not sort it out.

If someone can point me in the right direction so I can find what I am doing wrong I will be grateful

KD0RC

Hi Ron, In the Windows version, I see the pop-out and pop-in arrows. It looks like a bug in whichever version that you are using. If Simon doesn't see this post on his own, I will let him know this evening. Which operating system are you using?

NV0E

Thanks Len and Ron. I've replicated this. Working on a workaround and a fix right now.

NV0E

Hi Jonathan,

I think there is an issue with your UK 80m range. I'll send you an email with the details.

NV0E

Hi Ron,

The fix is merged and will be in the next release which is due to be published this week sometime. Meanwhile, here is how to get the CWX panel back, and what is actually going on.

What is happening

RimuSDR remembers two separate things about the CWX panel: whether it is shown, and whether it is floating (undocked) or docked to the left edge of the main window. Those are stored in your settings file and reapplied at startup.

On startup the app read the saved "floating" setting, decided the panel was already floating, and skipped the step that actually moves the panel into the floating window. So the window opened - correct title, correct size, correct position - with the panel still sitting in the docked area, which is hidden while the panel is meant to be floating. The result is an empty window.

That also explains why there is no way out from inside the app: the dock/undock button lives on the panel itself, and the panel is the thing that never made it into the window.

Nothing is lost or corrupted. The only thing wrong is where the panel is being displayed, and one setting controls that.

The workaround: flip one setting back to docked

Step 1 - close RimuSDR completely.

This matters. RimuSDR writes its settings file when it exits, so if you edit the file while the app is running, your edit is overwritten the moment you quit. Make sure the app is fully closed before you start.

Step 2 - open your settings file in a text editor.

• Linux (including the .deb and AppImage builds):
  ~/.config/rimu-systems/rimusdr/settings.json
• Raspberry Pi: same as Linux, above.
• Windows:
  %LOCALAPPDATA%\rimu-systems\rimusdr\sdr_config.json
  Paste that into the Explorer address bar (including the % signs) and press Enter - Windows expands it to your own user folder.

Step 3 - find the CWX section.

Search the file for "cwx". You are looking for a block that reads roughly like this:

"ui": {
  "cwx": {
    "isOpen": true,
    "popout": { "height": 460, "width": 326, "x": 200, "y": 200 },
    "poppedOut": true,
    "showPanel": true
  }
}

Step 4 - change "poppedOut": true to "poppedOut": false.

Change only that one word. Leave the commas, quotes and braces exactly as they are - the file is JSON, and a stray character will stop it loading. Save the file.

If you would rather not hand-edit JSON, on Linux this single command does the same thing (with RimuSDR closed):

python3 -c "
import json, pathlib
p = pathlib.Path.home()/'.config/rimu-systems/rimusdr/settings.json'
d = json.loads(p.read_text()); d['ui']['cwx']['poppedOut'] = False
p.write_text(json.dumps(d, indent=2))"

Step 5 - start RimuSDR and connect to your radio.

Click CWX in the status bar. The panel now opens docked to the left of the panadapter, with all of its controls present.

Until the fixed build arrives

You can still undock CWX and use it floating for the rest of that session. The one thing to avoid is closing the app while CWX is left floating - that saves the floating setting again, and the next start reproduces the empty window (and needs the same edit to recover). Dock the panel before you quit and you will not hit it again.

Once you are on the fixed build, none of this applies: leave CWX floating when you close the app and it comes back floating, fully populated, exactly where you left it.

One more thing

The DVK panel shares the same undock mechanism and had the same flaw, so it could have behaved this way too. It is fixed in the same change. If you have hit it there, the same workaround applies - the setting is "poppedOut" inside the "dvk" section of the same file.

TimW

Simon, your technical writing is fantastic. I’ve spent more years than I care to think about in IT, so feel quite qualified to provide a compliment.

g4ivv

Hi Simon,

I think there is an issue with your UK 80m range. I'll send you an email with the details.

Many thanks for spotting that, I've pushed the update to my GitHub,

73 Jonathan