Slices are coupled (cannot be moved independently of each other) with diversity reception

Open
#4,891 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp
Domain
desktop

Research direction

Reproduce the issue with a Flex 8600, two 2 m transverter receive paths, two panadapters, and diversity enabled on both slices. Start by tracing panadapter and slice handling around diversity reception and the FlexLib protocol; done means the slices remain independently tunable, or the unsupported limitation is made explicit.

Written by the indexing model from the issue text.

Description

bug GUI maintainer-review multi-pan
Report preparation
  • I used the AI-assisted bug report tool (Help → Support → File an Issue)
  • I have attached a support bundle or log file
What happened?

When operating 2 m SSB with two transverters, I use two receive paths so I can use diversity reception.

With two panadapters open, I can initially tune the slices independently. However, when I enable diversity reception on both panadapters, the slices begin following each other as though they have been coupled or linked.

Changing the frequency of the slice on one panadapter causes the slice on the other panadapter to move with it.

This prevents using two independently tuned panadapters while also using diversity reception.

What did you expect?

Each panadapter and its associated slice should remain independently tunable.

Enabling diversity for one receive setup should only associate the diversity resources needed for that slice. It should not cause a slice associated with another panadapter to become frequency-linked.

For example:

Panadapter 1 / Slice A can be tuned to one 2 m SSB frequency with diversity enabled.
Panadapter 2 / Slice B can be tuned to a different 2 m SSB frequency with diversity enabled.
Tuning Slice A should not move Slice B.
Tuning Slice B should not move Slice A.

If FlexRadio hardware or the FlexLib protocol does not support two completely independent diversity groups simultaneously, AetherSDR should make that limitation explicit rather than silently coupling the slices.

Steps to reproduce

Connect AetherSDR to a FlexRadio with two 2 m transverter receive paths available.
Open two panadapters.
Create/use a slice on each panadapter.
Verify that the two slices can initially be tuned independently.
Enable diversity reception on the first panadapter/slice.
Enable diversity reception on the second panadapter/slice.
Tune the VFO/slice on one panadapter.
Observe that the slice on the other panadapter follows the frequency change as though the two slices are coupled.
Disable diversity and observe that the slices can again operate independently.

AetherSDR version

26.8.2

Radio model & firmware

Flex 8600

Operating system

Windows

OS version and hardware

Windows 11

Dominant language
C++
Stars
221
Forks
117
Avg merge
2d 7h
Merged PRs (30d)
299

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aethersdr/AetherSDR

All issues in aethersdr/AetherSDR

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.