Rimu Systems LLC
Buy Now Download Trial
Support

Support & Community

Get help with RimuSDR installation, configuration, and troubleshooting.

Support channels · Email · Documentation · FAQ

Community Forums

Connect with other FlexRadio users to ask questions, share tips, and get help with RimuSDR.

FlexRadio Community Forum

Official FlexRadio community discussion board.

  • Ask questions about RimuSDR for Linux
  • Share your experience with other users
  • Follow the dedicated RimuSDR for Linux thread

FlexRadio SmartSDR Group

Active groups.io mailing list for SmartSDR users.

  • Community-driven support and discussion
  • Tips and configuration advice from experienced operators
  • Announcements and user-to-user help

How to Reach Us

We're here to help with technical questions, installation issues, and product guidance.

Email Support

Direct technical assistance for RimuSDR users.

Before Contacting Support

Information to have ready for faster assistance.

  • Your operating system and version (Linux distribution or Windows release)
  • RimuSDR version number
  • FlexRadio model and firmware version
  • Description of the issue and steps to reproduce
  • Any error messages or log entries

License Help

Quick answers for the most common license and activation issues.

Lost License Code
If you've lost your license code email, contact support@rimusystems.com with your callsign and purchase information to retrieve it.
Moving to a New Computer
Deactivate first via Help → Deactivate License, then activate on the new machine. See Transferring Your License.
Activation Problems
Connection errors, rejected codes, and callsign issues are covered in the activation troubleshooting guide. If you're still stuck, email support.

Collecting Diagnostic Information

When you report a problem, send the application log, the System Info text, and any crash files. These three items resolve most problems quickly.

Step 1: Record a detailed log

RimuSDR sets the log level to CRITICAL when it is installed. At that level the log records almost nothing. Set the level to DEBUG before you make the problem occur.

  • 1. Start RimuSDR.
  • 2. Select Settings → Display...
  • 3. Select the Logging tab.
  • 4. Make sure that Log to file is selected.
  • 5. Set Log Level to DEBUG (show all).
  • 6. Click OK. The new level starts immediately. A restart is not necessary.
  • 7. Do the steps that cause the problem.
  • 8. Attach the log file to your report. The file locations are below.
  • 9. Set Log Level back to CRITICAL (critical only) when you are finished. DEBUG writes a large quantity of data.

The Logging tab also shows the Log file and Settings file paths for your computer. This is the fastest way to find them.

Step 2: Collect the System Info text
  • 1. Select Help → System Info...
  • 2. Click Copy to Clipboard.
  • 3. Paste the text into your email or your issue report.

System Info records the RimuSDR version, the API layer version, the Qt version, the installation type, the operating system, the CPU and memory, the graphics and screen data, the audio configuration, and the connected radio clients.

Step 3: Attach the files - Linux
  • Application log ~/.local/state/rimu-systems/rimusdr/rimusdr.log
  • Previous logs RimuSDR keeps two older logs in the same folder: rimusdr.log.1 and rimusdr.log.2. Each log file has a limit of 5 MB. Attach these files also if the problem did not occur in the current session.
  • Crash report ~/.local/state/rimu-systems/rimusdr/crash/rimusdr_crash_<timestamp>.txt
  • RimuDAX and RimuCAT logs ~/.local/state/rimu-systems/rimudax/rimudax.log
    ~/.local/state/rimu-systems/rimucat/rimucat.log
    Attach these files if the problem is related to audio streaming or to CAT control.
  • Settings file ~/.config/rimu-systems/rimusdr/settings.json
    Send this file only when support asks for it. It holds your RimuSDR preferences: window layout, audio device selections, station name, and any Antenna Genius device codes.
  • Collect all logs in one archive tar -czf rimusdr-diagnostics.tar.gz -C ~ .local/state/rimu-systems
    The archive contains the logs and the crash reports for RimuSDR, RimuDAX and RimuCAT. It does not contain your settings or your license data.
Step 3: Attach the files - Windows
  • Application log %AppData%\rimu-systems\rimusdr\rimusdr.log
    The full path is C:\Users\<your user name>\AppData\Roaming\rimu-systems\rimusdr\. To open the folder, press Win+R, type %AppData%\rimu-systems\rimusdr, then press Enter.
  • Previous logs RimuSDR keeps two older logs in the same folder: rimusdr.log.1 and rimusdr.log.2. Each log file has a limit of 5 MB. Attach these files also if the problem did not occur in the current session.
  • Crash report %UserProfile%\Documents\rimusdr_CrashDumps\rimusdr_crash_<timestamp>.txt
    Attach this file first. It is a text file, and it contains the error and the stack trace.
  • Crash memory dump %UserProfile%\Documents\rimusdr_CrashDumps\rimusdr_crash_<timestamp>.dmp
    This file is a full memory dump, and it can be very large. Compress it, then ask support before you send it.
  • If Windows offers to open a debugger %LocalAppData%\CrashDumps\RimuSDR.exe.<number>.dmp
    Some failures stop RimuSDR before it can write the two files above. Windows shows its own dialog instead of the RimuSDR crash message, and Windows records the dump. Attach the newest file in that folder. It is a few megabytes rather than a full memory dump, so you can send it without asking first.
  • If you cannot find the crash folder The crash message shows the two file paths. Write them down before you close the message. If your Documents folder syncs to OneDrive, look in %UserProfile%\OneDrive\Documents\rimusdr_CrashDumps instead.
  • Settings file %LocalAppData%\rimu-systems\rimusdr\sdr_config.json
    Send this file only when support asks for it. It holds your RimuSDR preferences: window layout, audio device selections, station name, and any Antenna Genius device codes.

RimuDAX and RimuCAT are Linux components. Windows computers do not have their logs.

Where to send the information

Frequently Asked Questions

Common questions about RimuSDR installation, compatibility, and usage.

Licensing & Purchase

How much does RimuSDR cost?

RimuSDR is a $49.00 one-time purchase that includes the integrated RimuDAX and RimuCAT components and all version 1.x updates. See the pricing page for full license terms.

Is there a free trial?

Yes. Every download includes a trial mode so you can evaluate RimuSDR with your own radio. Trial mode is limited to 80m receive-only with transmit disabled. Download the trial.

How many computers can I install RimuSDR on?

Your license allows up to 10 active installations on computers you own or control. To move to a new computer, deactivate first via Help → Deactivate License. See the activation guide.

I lost my license code. How do I get it back?

Contact support@rimusystems.com with your callsign and purchase information and we'll retrieve it for you.

What is the refund policy?

Purchases are covered by our refund policy. We recommend trying the free trial with your radio before buying.

Installation & Compatibility

Which Linux distributions are supported?

RimuSDR is tested on Ubuntu 24.04+, Debian 13, Linux Mint 22+, Fedora 43/44, and Raspberry Pi 4B/5. RPM packages are available for Fedora and Rocky Linux, and AppImage builds are available for other distributions.

Which FlexRadio models work with RimuSDR?

RimuSDR supports FlexRadio 6000, 8000, and Aurora series radios.

Can I run RimuSDR on Raspberry Pi?

Yes, RimuSDR has been tested on Raspberry Pi 4B and Pi 5 running 64-bit ARM Linux. Note: current builds require glibc 2.38+, so Raspberry Pi OS Bookworm users may see a GLIBC_2.38 not found error - a Bookworm‑compatible build is coming soon.

What are the system requirements?

A modern GPU is recommended for optimal panadapter performance. See the installation guide for detailed requirements.

Features & Usage

Does RimuSDR include DAX and CAT?

Yes, RimuSDR includes the integrated RimuDAX and RimuCAT components as part of a single suite.

Can I use RimuSDR with WSJT-X?

Yes, the integrated RimuDAX component provides audio routing for WSJT-X and other digital mode applications. See our WSJT-X setup guide.

Does RimuSDR support SmartLink?

Yes, RimuSDR includes full SmartLink support for remote radio access and credential management.

How many panadapters can I use?

RimuSDR supports up to 8 panadapters and 8 slices, depending on your radio's capabilities.

MIDI CW paddle keying isn't as smooth on Windows as it is on Linux - why?

When you use a MIDI paddle and let RimuSDR generate the sidetone, Windows adds more fixed audio delay than Linux (roughly 27 ms versus about 7 ms). Because you judge paddle-release timing by listening to the sidetone, that extra delay makes precise iambic timing harder and can occasionally insert an extra dit or dah in a character. This is a limitation of the Windows shared-mode audio system, not something specific to RimuSDR - other CW applications are affected the same way on Windows. For the tightest CW paddle timing we recommend running RimuSDR on Linux or a Raspberry Pi. This does not affect straight-key input or computer-generated CW; it only affects paddle timing judged by ear against the sidetone.

About Rimu Systems LLC

Rimu Systems LLC develops native Linux software for amateur radio operators. The name Rimu, pronounced REE-moo, comes from the Rimu tree of New Zealand, chosen both as a nod to the founder's origins and as a symbol of strong, clean, long‑lasting design.

Additional Resources

More ways to learn about RimuSDR and stay informed.

Product Information
Visit the RimuSDR details page to learn about features, capabilities, and the integrated suite components.
Release Updates
See the release notes for the changes, fixes, and improvements in each RimuSDR release.
Setup Guides
Review our WSJT-X integration guide and other documentation to prepare for installation and configuration.
×