Upgrading to NereusSDR 2026.10.1

On this page
  1. Update the Core and the desktop together
  2. What changes on first launch
  3. Core installs on a Raspberry Pi, Rock or other SBC
  4. What to try
  5. Reporting

Use this note when updating a station from 2026.10.0. It lists what changes when you first launch, what to do on a Core, and a short list of things to try. If you are coming from 0.5.2, read the 2026.10.0 checklist first. When reporting a problem, include the installed version, operating system, radio model and firmware, and whether you use a local or remote Core.

Update the Core and the desktop together

The Core owns the radio, the station DSP and the accessories. The console runs where you operate. Update both. Rotor control, the CAT Control page on the phone and the Core speaker need a 2026.10.1 Core. An older Core grays them out with a reason such as "This Core does not control a rotor. Updating the Core may help.", and older Cores, desktops and phone apps still connect to each other. The phone shows the new Display pages only with a 2026.10.1 Core; with an older Core it keeps the earlier pages.

What changes on first launch

Keep a backup of your settings before the first launch, and close the console normally so the new version can migrate them once.

Core installs on a Raspberry Pi, Rock or other SBC

The Core runs as a service account with no groups of its own, so Linux sound cards and serial adapters each need a small systemd drop-in.

The SBC install guide has the details, including the sound card's own mixer and kernels that refuse real-time priority. Building the PulseAudio engine from source on Linux needs libpulse-dev.

What to try

Each item is a short check you can do in a few minutes. Note the result, including anything that surprised you.

  1. Rotor. Open File > Settings... > CAT & Network > Rotor, choose your controller (Yaesu GS-232A, serial port, Yaesu GS-232B, serial port, Hamlib rotctld, already running or Hamlib rotctld, started by the Core), set the end stop and travel, and select Save and connect. Open the Rotor applet, turn to a heading, stop it, and try a preset. Right-click a spot and choose Turn beam to the call. On the iPhone or iPad, open the Rotor page and confirm it shows the same heading. Release a held turn button and confirm the rotor stops.
  2. CAT. Open Tools > CAT Control... (or the CAT pages in File > Settings... > CAT & Network), assign a channel to a slice, enable one listener, and connect a logging or digital-mode program. Change frequency from the program and from NereusSDR and confirm both follow. Try the Hamlib rigctld port with a program that speaks it. On a headless Core, set CAT up from a connected desktop or from the phone's Tools tab. Confirm that a refused setting says why.
  3. Native audio. Check that the Driver lists show your system's audio system and that devices appear and disappear as you plug them in. With a Core, pick the Core speaker in Audio > Outputs and confirm the level and mute match the phone's Sound panel. Disconnect and reconnect your microphone and confirm transmit audio returns.
  4. Workspace look. Hide and show a container header with the eye button. Hold Shift (or press Ctrl+Shift+A) to arrange, dock a container on each edge, pop one out, pin it and return it. Save a workspace profile and switch to it with Containers > Manage Workspace Profiles…. Choose Reset Default Layout and confirm the S-Meter comes back.
  5. Receivers after a relaunch. Give two receivers different squelch, L/R pan, APF and AGC-T AUTO settings, close NereusSDR normally, open it again and confirm each receiver comes back as you left it and sounds the way it did.
  6. Hermes Lite 2 through a Pi Core. Key the radio from a window or the phone through a Core on a Raspberry Pi and hold it for half a minute. Confirm the radio stays keyed for the whole time.
  7. Rock real-time priority. After installing on a Rock and restarting it, log in over ssh and run cat /sys/fs/cgroup/cgroup.subtree_control. Confirm that cpu is not in the list, and that the Core's log has no "Raised thread priority was refused" line from after the restart.
  8. Two-tone and PureSignal. If you use PureSignal, run a two-tone test and a calibration at your new two-tone level and compare it with what you expect. Then check Show 2Tone measurements (Bench > IMD measurements), turn on DUP, run a brief two-tone test and read WORST IMD3 and WORST IMD5 on the rail's Inspect readout.
  9. RADE waveforms. In Containers > Edit Container, add Microphone waveform and Decoded speech waveform to a container whose Slice is the transmit slice and is in RADE-U or RADE-L. Speak while transmitting in RADE and confirm the microphone trace moves; receive a RADE signal and confirm the decoded speech trace moves. On a remote desktop, confirm an older Core shows a reason instead of a trace.

Reporting

Report expected behavior, actual behavior, a minimal reproduction, desktop and Core versions, platform, radio model and firmware, the connection path and a support bundle. Keep credentials and pairing tokens out of public reports. Bench results for physical serial ports, a physical rotor and logging programs on Windows and Linux are still open. Say which hardware and program you used.