RimuSDR 1.1.18 : Waveform Manager and spot display updates
14 enhancements and 17 fixes across RimuSDR, RimuDAX and RimuCAT.
Version 1.1.18
Known issue
- RimuSDR does not start on some older processors - On Linux PCs with an older processor, mainly Intel Core 2 and older AMD processors from before about 2009, RimuSDR 1.1.18 does not start. In a terminal it shows "Incompatible processor. This Qt build requires the following features: sse4.2 popcnt". Qt 6.12, which RimuSDR now uses, needs these two processor features. RimuDAX and RimuCAT are not affected. To check your processor, run
grep -o -w popcnt /proc/cpuinfoin a terminal: if it prints nothing, your processor is affected. Until the fix is released, use RimuSDR 1.1.17, which has step-by-step instructions for going back. The next release will run on both older and newer processors.
Enhancements
RimuSDR
- Waveform Manager - A new File > Waveforms... menu item opens the Waveform Manager. It lists the waveforms installed on the radio, such as FreeDV, and installs, uninstalls and restarts them. On radios that run container waveforms, such as the FLEX-8000 series and Aurora, it also installs container waveforms and shows and edits each one's environment variables. Install is not available over SmartLink. A restart keeps a container's existing variables unless you enter new ones, so to clear them all, uninstall the waveform and install it again with the box empty.
- Spot indicator lines - A new Show Lines setting in Spots Settings > General > Display joins each spot's label to a dot on the peak of its signal, or to a ring on the noise floor when nothing is heard, with a dotted line and a notch down to the frequency scale. The lines take the spot's color and fade with its age unless Fade With Age is off. Show Lines is off by default, so the panadapter looks as before until you turn it on. Thanks to Bill, K3CDY, for the suggestion.
- Spot text on the sideband - A new Justify Text on Sideband setting in Spots Settings > Layout puts a USB spot's callsign just right of its frequency and an LSB spot's just left of it, so the label lies over the voice signal. The spot's line stays on the frequency, and spots in other modes stay centered. It is off by default. Thanks to Mark, N6MTS, for the suggestion.
- Clear All Spots - A new Clear All Spots... item in the spot menu, the collapsed-spot menu and at the bottom left of Spots Settings removes every spot from the radio after a Yes/No confirmation. This also removes the spots of other programs and other stations, and a station that is spotted again can return. The Spot Manager now follows the radio too: a spot that leaves the radio by Remove Spot, by expiry or by another client's clear loses its row. A row that a filter keeps off the radio stays, labeled "Not on the radio", so loosening the filter still sends the spot. Thanks to John, G4IRN, for the suggestion.
- Spot Manager flags - The Flag column in the Spot Manager was blank for 94 DXCC entities. It now shows the entity's own flag where one is available, for example England, Scotland, Wales, Cape Verde and the Canary Islands, and otherwise the parent country's flag, for example Hawaii and Alaska, Madeira and Corsica. Northern Ireland shows the UK flag. Nine entities stay blank because they have no flag to show or no clear parent country: UN HQ, ITU HQ, Peter 1 Island, the South Shetland and South Orkney Islands, Market Reef, the Sovereign Military Order of Malta, the Spratly Islands and Scarborough Reef.
- Updated country data - RimuSDR now includes Big CTY of 23 October 2026, which the spot table uses for each spot's entity, continent and CQ zone.
- Qt 6.12 and supported systems - RimuSDR now uses Qt 6.12 on every platform, and the Raspberry Pi package now includes its own copy of Qt. RimuDAX and RimuCAT stay on their current Qt. There are no longer Rocky 9 RPMs of RimuSDR, RimuDAX or RimuCAT. The Rocky 10 RPMs stay.
- Installer launch checkbox - The RimuSDR Windows installer now finishes with its Launch RimuSDR checkbox unchecked, so clicking Finish no longer starts RimuSDR unless you check the box. Thanks to Ron, NI0F, for the suggestion.
- Connect details in the log - RimuSDR now writes what the radio reports at connect to its log at the default level: free slices and panadapters, each slice and panadapter that arrives, the first transmit status, and a summary 5 seconds after connecting. This is to help diagnose reports of a connection with no panadapter and RF Power and Tune Pwr at 0. It does not fix that fault.
RimuDAX
- TCI panel clients and transmit - The TCI panel has new Clients and TX Streams sections. Clients lists each TCI connection with its port, what it uses (receive audio on a DAX channel, IQ, or control only) and a KEYED tag on the one that is transmitting. In TCI mode, the TX button, gain and meter move from the strip above the panels into TX Streams. That section also shows which program holds the key, its slice and DAX channel, and a warning when a keyed program has no DAX TX stream or its audio is being dropped.
- Station name in the status line - The status line now names the bound station, for example "HOME-NUC bound and ready", so you can see which station RimuDAX is bound to and that a change of station worked. Thanks to John, G4IRN, for the suggestion.
- Installer launch checkbox - The RimuDAX Windows installer now finishes with its Launch RimuDAX checkbox unchecked, so clicking Finish no longer starts RimuDAX unless you check the box. Thanks to Ron, NI0F, for the suggestion.
RimuCAT
- Station name in the status line - The status line now names the bound station, for example "HOME-NUC bound and ready". It used to read the same before and after a change of station, which made a change that had worked look as if nothing had happened. Thanks to John, G4IRN, for the suggestion.
- Installer launch checkbox - The RimuCAT Windows installer now finishes with its Launch RimuCAT checkbox unchecked, so clicking Finish no longer starts RimuCAT unless you check the box. Thanks to Ron, NI0F, for the suggestion.
Fixes
RimuSDR
- MSVCP140.dll missing on Windows - The RimuSDR Windows installer did not include the Microsoft Visual C++ runtime, so on a PC without it Windows reported that MSVCP140.dll was missing and the install failed. The installer now includes the runtime, so you no longer need to install it separately. Thanks to Ron, VK4JE, for the report.
- Wayland with RPM packages - The RimuSDR RPM packages left out Qt libraries that its native Wayland support needs, so on a Wayland session RimuSDR fell back to X11 with no message. The RPM packages now include them. If you use an RPM on Wayland, RimuSDR may now run as a native Wayland application for the first time, so please report anything that looks different.
- MON and the CW sidetone - RimuSDR turned on MON, the CW sidetone and the monitor levels by itself on every CWX send or macro, and turned on MON when you switched on the CW sidetone control. When two multiFLEX stations use the same mic profile, this also turned on MON at the other station. These settings now change only when you change them. If you relied on RimuSDR to turn them on, you may need to turn them on once. With the CW sidetone off, you do not hear a CWX send at your PC.
- MON when the radio says unavailable - The MON button and the sideband monitor level stayed enabled whatever the radio reported. Both are now disabled while the radio reports that MON is not available, and they follow later reports. A disabled MON button still shows the radio's MON state, and the MIDI actions for MON and its level are refused in this state. The CW monitor level is not affected.
- Saving CW profiles - The CW tab of the Profile Manager had no Save button, so you could create a CW profile but not update an existing one. The tab now has Save, which updates the selected profile with the current settings. Thanks to Jonathan, G4IVV, for the report.
- Firmware version over direct IP - On a connection with no discovery packet, such as a direct IP connection, RimuSDR did not learn the radio's firmware version, and System Info showed v0.0.0.0. The PTT Override button could then stay disabled and say that it needs firmware 4.3, and the mic meter could show the wrong source when the override is off. RimuSDR now takes the version from the radio's own reply after connect, and both controls update when it arrives.
- Radio Setup GPS tab - The GPS tab showed the GPS Install and Uninstall controls and an empty status line on every radio. The tab now follows the radio model, as in SmartSDR: the FLEX-8000 series, Aurora and other newer radios show no install controls and say whether GPS or GNSS is installed, the other FLEX-6000 radios keep the install controls, and the FLEX-6300 has no GPS tab. The status line now shows only the radio's GPS state, not the result of an Install or Uninstall click.
- DSP Controls without SmartSDR+ - On a radio without the SmartSDR+ license, the DSP Controls window said "Advanced needs SmartSDR+" on every page, even where the whole algorithm was locked or nothing was locked, and locked value boxes looked editable. A locked algorithm (NRL, NRF, NRS, RNN, ANFL, ANFT) now says "Needs SmartSDR+" beside its disabled On/Off button, and is dimmed in the list with the same reason in its tooltip. NR and ANF show "Advanced needs SmartSDR+" under a rule that separates Level from the advanced settings, and disabled controls in this window are dimmed. Reset and Reset All stay disabled without the license, as before.
- Windows installer links - The publisher, support and updates links in the RimuSDR Windows installer pointed to a website page that did not exist. They now point to rimusystems.com.
RimuDAX
- TCI transmit with no audio - When a TCI program closed its connection and opened a new one a moment later, for example when DXLog resets its interfaces, RimuDAX could be left with no DAX TX stream. The next key then put the radio into transmit with no audio. RimuDAX now requests a new TX stream whenever a connected TCI program still needs one. Thanks to John, G4IRN, for the report.
- TCI key with no audio from a second RimuDAX - When the radio was using another client's DAX TX stream, for example a RimuDAX left running on a second computer, a TCI key put the radio into transmit with no audio. RimuDAX now refuses a TCI key in this state and stops one already running, and the TCI panel warns as soon as the state begins. A tune, or a key that does not use TCI audio, still goes out. Thanks to John, G4IRN, for the report.
- Station choice at startup - With two stations on the radio, RimuDAX could connect to whichever was announced first, even when the saved station was also running, and then save that station as the new choice. TX audio then went out through the wrong station. RimuDAX now connects by itself only to the saved station, and the saved station changes only when you choose another. If the saved station is not running, RimuDAX shows it as Offline and connects when it starts. If there is no saved station, RimuDAX connects to nothing until you choose one from the list, so a first run takes one more click than before. Thanks to John, G4IRN, for the report.
- TCI split in SO2R - With two TCI programs on two slices, for example DXLog in SO2R, moving TX to one program's slice made the other program show split, with VFO B on the other radio's slice. A VFO B change from that program could then retune the other radio's slice. A slice that has a DAX channel is now never another program's VFO B. Split shows only while TX is on a slice with no DAX channel on the same panadapter, such as the copy that RimuSDR's SPLIT button makes. Thanks to John, G4IRN, for the report.
- TCI VFO B after a band change - After a VFO A change on a slice where a TCI program had set VFO B, RimuDAX did not send VFO B again, so a program that waits for it, such as WSJT-X Improved after a band change, waited up to 2 seconds. RimuDAX now sends VFO B after every VFO A change.
- Log level setting - The log level setting did not work: INFO messages were written at every level, and the INFO level left out warnings and errors. Each level now writes its own messages and every more serious one. The default level changes from CRITICAL to INFO, as in RimuSDR and RimuCAT. A level you set by hand is kept.
RimuCAT
- Station choice at startup - With two stations on the radio, RimuCAT could connect to whichever was announced first, even when the saved station was also running, and then save that station as the new choice. RimuCAT now connects by itself only to the saved station, and the saved station changes only when you choose another. If the saved station is not running, RimuCAT shows it as Offline and connects when it starts. If there is no saved station, RimuCAT connects to nothing until you choose one from the list, so a first run takes one more click than before. While it waits, a slice on another station does not reach a CAT port. Thanks to John, G4IRN, for the report.
- Windows installer links - The publisher, support and updates links in the RimuCAT Windows installer pointed to a website page that did not exist. They now point to rimusystems.com.