Upgrading to NereusSDR 2026.10.0

On this page
  1. Which machine runs what
  2. Before upgrading
  3. Installed package and startup
  4. Receivers and displays
  5. Core and remote sessions
  6. EQ/CFC, containers and meters
  7. DSP, modes and accessories
  8. Reliability retests and reports

Use this checklist when updating a station from 0.5.2. Start with the upgrade notes, then check the controls and connections you use. When reporting a problem, include the installed version, operating system, radio model and firmware, and whether you use a local or remote Core.

Which machine runs what

The Core owns the radio, station DSP, receiver allocation and transmit permissions. The GUI runs where the operator is, presenting spectra and state, playing received audio and sending controls/microphone audio. Local desktop mode runs both together; remote mode runs nereusd beside the radio and the GUI elsewhere, including the native iPhone/iPad app. The Core can run on a compatible SBC, including a Raspberry Pi inside an ANAN-G2. Development used a Raspberry Pi 4 and a Radxa Rock 5C with 2 GB RAM. Record your board and enabled DSP/receiver load when testing.

For remote access, the RV signalling service introduces the GUI and Core and provides a pairing mailbox. The Core authenticates the device. The session then uses a direct path, a TURN relay or the separate WebSocket relay. A Core reachable by LAN/VPN address can also be connected directly. See the Core/GUI and RV explanation.

For a fresh SBC, use the short Raspberry Pi OS Lite/Armbian Core install guide. Record the OS release and exact package along with the board when reporting your check.

Before upgrading

Keep a backup of your settings and microphone profiles before first launch. Close the console normally to save current edits. Let the new application migrate the existing settings; do not copy an older backup over newer edits. Update the Core and desktop together for the new controls and authority rules.

Installed package and startup

  1. Check the selected release's artifact list. Verify SHA256SUMS.txt.asc against SHA256SUMS.txt, then check the downloaded package's checksum. See README installation notes.
  2. Launch normally and confirm 2026.10.0 in About. Record startup errors, missing libraries or missing model assets. First-run FFTW wisdom can take time; later launches should use the cache.
  3. Confirm saved radio/Core targets, profiles and layout survived migration. Reopen after a normal Quit and check that your latest edits remain.

Receivers and displays

  1. Connect to your usual radio or Core. Add receivers within its stated capacity. Tune two receivers to different signals and change mode, filter, AGC and DSP separately. Confirm their audio and controls remain independent.
  2. Test shared-pan and separate-pan layouts. Select a different receiver, change the transmit receiver, float a pan and return it. Check receiver colours, identities and restored layout after restart. Give receivers different STEP values and verify each pan displays and wheel-tunes with its selected receiver's STEP after selection changes and reconnect. High-resolution trackpad gesture handling remains under review.
  3. Adjust TX spectrum/waterfall settings and verify they belong to the transmit display. Try the native 3D stacked spectrum/waterfall and change its history/view controls. Check resizing and CPU/GPU interaction geometry.
  4. Place, move and resize a tunable notch. Confirm persistence after restart. Record listening results separately from the visual notch indication.
  5. If your station supports Diversity, assign an eligible receiver and check its phase/gain controls, saved memories and refusal/pause explanations.

Core and remote sessions

  1. Check Core Settings: saved/manual targets, Core name, connection status, current audio path and device authority. Verify the displayed station matches the station you intended to join.
  2. Pair a second supported device if available. Give it its own receiver and check that ownership markers and transfer confirmations agree on both ends.
  3. During an ordinary disconnect/reconnect, check that stale replies do not change the new session's authority or controls. Record direct/relayed media status, drop/recovery behavior and any missing audio. On macOS, open the receiver preamp menu before reconnecting or changing the connected radio; confirm it refreshes to the radio's available choices without a crash and retains a supported selection. Also confirm spectra and waterfall rows continue updating after a handover and after closing/recreating a pan.
  4. Check per-receiver digital-app audio and the separate speaker/headphone mix. Record which compressed/lossless path actually ran. Use identical signal files and decoder settings for comparative decoder tests.

The native iPhone/iPad app is a full operating console for the same Core, with touch receiver controls, live display/audio and microphone/PTT uplink. Its validation and delivery are tracked independently of desktop packages.

IPv6 and CGNAT checks

When available, test from an IPv6 or mobile/CGNAT network as well as the station LAN. Record the client network, whether each end has usable IPv4/IPv6, the selected direct/TURN/WebSocket path, and actual audio/display recovery. Test reconnection after changing between Wi-Fi and cellular networks. A working LAN session alone does not close cellular, firewall, IPv6-only or prolonged mobile-session acceptance.

See the IPv6/CGNAT explanation. CGNAT can prevent incoming IPv4 connections despite a home-router forwarding rule; usable IPv6 and outbound relay paths address different parts of that reachability problem. Test the path that actually runs rather than assuming a provider or an IPv6 address guarantees a direct connection.

EQ/CFC, containers and meters

  1. Open TX EQ. Edit Graphic and Parametric modes and confirm each keeps its own values. Try drag handles, exact entry, width/Q and undo/redo. Hide and reopen the editor; confirm history is retained.
  2. Request a 5/10/18-band change. Check the pending notice and Apply N bands. Cancel retains the old curve; Apply resets to the requested count; Undo restores the prior curve. See the EQ/CFC guide.
  3. In CFC, check the aligned compression/post-EQ plots, shared frequencies, independent gains/Q and measured compression bars. Save/reload a microphone profile. The configured response graph is not a measurement of the whole audio chain.
  4. Move an applet and a complete meter object by their grips/menu, reorder them, float a container and return it to its remembered home. Reopen an editor after moving its parent applet.
  5. Preview a container change, Cancel, then repeat and Apply. Check portable export/import with a copy of your layout, including customized legacy objects and external MMIO bindings.
  6. Check composite meters in receive/transmit states available to your normal station operation. Unavailable sources should be reported as unavailable. On the ANAN face, check scale labels at ordinary sizes and readout font growth. Visible idle pointers should park dim without a measured value; switching receive/transmit groups must clear stale values and history. Compare any RF/calibration readings against the documented hardware matrix.
  7. Create an editable Canvas with a meter and a supported control. Move and resize through grips, numeric fields and keyboard handles; check layers, locking, scrolling and Apply/Cancel. Restore an imported layout and confirm saved positions survive until explicitly edited.
  8. Resize a Bar and another complete meter face at your display scale. Titles, scale labels, units and readings should fit their own regions. Check that preview controls remain inert and live controls retain their ordinary capability and authority rules. On macOS, switch the selected container in Settings with a pending draft edit and confirm it survives without a crash.

DSP, modes and accessories

Test the NNR Models manager, selection and pending Apply behavior with your station's assets. Check per-receiver tuning and unavailable-model explanations. Test PureSignal settings/status and correction-file handling against the WDSP 2.10 operator notes and verification matrix. Record software checks separately from listening/RF measurements.

AM/SAM/DSB modulation monitoring, RADE end-of-over callsigns, microphone input options, radio speaker/headphone mixing and PGXL/TGXL/RF2K-S behavior depend on your station capabilities. Follow their feature-specific verification steps and record the exact hardware, operating mode and result. Previously open accessory, on-air and sustained SBC rows remain pending until evidence closes them.

Reliability retests and reports

The release includes fixes for live receiver reconfiguration stopping TX mic pumping (#331), DEXP threshold persistence (#332), repeated HL2 TUNE power (#333), anti-VOX state replay (#334), stale-session keying callbacks (#335) and spectrum paint/mouse geometry (#336). Retest the original triggering sequence when your station matches it. The broader reports #235, #299 and #300 still need their requested retests; these narrower fixes do not close them by assumption.

Report expected behavior, actual behavior, minimal reproduction, desktop/Core versions, platform, radio model/firmware, connection path and relevant support bundle. Keep credentials and pairing tokens out of public reports.

CW transmit, FM pre-emphasis, CAT/rigctld, legacy skin import and WAV/IQ recording are not delivered by this release. Remaining disabled actions and hardware acceptance are tracked in their feature documents.