Report preparation
What happened?
What happened
When clicking a DXCluster spot that is tagged as SSB mode in the spot
tooltip, AetherSDR tunes the radio to the correct frequency but incorrectly
switches the slice mode to CW instead of SSB (USB or LSB).
This is reproducible in v0.8.19 on macOS Tahoe 26.4.1.
As seen in the attached screenshots:
- The spot tooltip shows:
F5MUX 7.1600 MHz · SSB · DXCluster · Spotted 2026-04-22 06:24:54 UTC
- After clicking the spot, the VFO lands on 7.160.000 — correct
- But the mode tab strip highlights CW instead of USB/LSB
Environment
- AetherSDR version: v0.8.19
- OS: macOS Tahoe 26.4.1
- Radio: FlexRadio FLEX-8600, firmware v4.15
- Spot source: DXCluster (via N2ESP spotter, as shown in tooltip)
Suggested fix
The spot click handler (likely in SpectrumWidget or wherever spot markers
emit a tune signal) should map the spot's mode string to a FlexRadio slice
mode before issuing the slice set command:
"SSB" on freq < 10 MHz → "LSB"
"SSB" on freq >= 10 MHz → "USB"
"CW" → "CW" (or "CWL"/"CWU" depending on band)
"RTTY" → "DIGL"
"" (no mode) → leave current mode unchanged
The relevant command would be:
slice set 0 mode=LSB
If the spot mode string is empty or unrecognised, the slice mode should not
be changed at all.
It is also worth checking whether the spot click code is accidentally passing
a raw DXCluster mode string (e.g. "SSB") directly to the radio as a mode
value — the radio does not accept "SSB" as a valid mode token and may be
silently falling back to CW or its last-set mode.
Labels
bug, GUI, spectrum, protocol
What did you expect?
When clicking a spot tagged as SSB mode:
- The radio should tune to the spotted frequency ✓
- The slice mode should be set to USB (for frequencies above 10 MHz) or
LSB (for frequencies below 10 MHz, e.g. 7 MHz) — not CW
- If the spot has no mode or an ambiguous mode, the current slice mode should
be preserved (no forced mode change)
Steps to reproduce
- Connect AetherSDR v0.8.19 to a FlexRadio (FLEX-8600, fw v1.4.0.0)
- Enable DX Cluster spots (SpotSettingsDialog → connect to a DXCluster)
- Wait for an SSB spot to appear on the panadapter (spot tag shows
SSB)
- Click the spot marker on the panadapter / spectrum overlay
- Observe: radio tunes correctly but slice mode switches to CW
AetherSDR version
v0.8.19
Radio model & firmware
FlexRadio FLEX-8600, firmware v4.1.5
Operating system
macOS
OS version and hardware
macOS Tahoe 26.4.1, Apple Silicon M4Pro
Report preparation
What happened?
What happened
When clicking a DXCluster spot that is tagged as SSB mode in the spot
tooltip, AetherSDR tunes the radio to the correct frequency but incorrectly
switches the slice mode to CW instead of SSB (USB or LSB).
This is reproducible in v0.8.19 on macOS Tahoe 26.4.1.
As seen in the attached screenshots:
F5MUX 7.1600 MHz · SSB · DXCluster · Spotted 2026-04-22 06:24:54 UTCEnvironment
Suggested fix
The spot click handler (likely in
SpectrumWidgetor wherever spot markersemit a tune signal) should map the spot's mode string to a FlexRadio slice
mode before issuing the
slice setcommand:"SSB" on freq < 10 MHz → "LSB"
"SSB" on freq >= 10 MHz → "USB"
"CW" → "CW" (or "CWL"/"CWU" depending on band)
"RTTY" → "DIGL"
"" (no mode) → leave current mode unchanged
The relevant command would be:
slice set 0 mode=LSB
If the spot mode string is empty or unrecognised, the slice mode should not
be changed at all.
It is also worth checking whether the spot click code is accidentally passing
a raw DXCluster mode string (e.g.
"SSB") directly to the radio as a modevalue — the radio does not accept
"SSB"as a valid mode token and may besilently falling back to
CWor its last-set mode.Labels
bug, GUI, spectrum, protocol
What did you expect?
When clicking a spot tagged as
SSBmode:LSB (for frequencies below 10 MHz, e.g. 7 MHz) — not CW
be preserved (no forced mode change)
Steps to reproduce
SSB)AetherSDR version
v0.8.19
Radio model & firmware
FlexRadio FLEX-8600, firmware v4.1.5
Operating system
macOS
OS version and hardware
macOS Tahoe 26.4.1, Apple Silicon M4Pro