aethersdr / aethersdr/AetherSDR
split mode slice A, issues when you came back on Slice B
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 221
- Forks
- 117
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 299
Description
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?
Example:
Two open slices: Slice A and Slice B.
Slice A in CW 14MHz, Slice B in CW 21MHz. Close Slice B with the X and go to Slice A, opening Split mode. After you've finished split operations, close the split and switch to Slice B. Clicking on any frequency of 21MHz doesn't open the VFO, but changes the frequency of Slice A from 14MHz to 21MHz.
What did you expect?
No response
Steps to reproduce
flex 6400
2 slice open
AetherSDR version
0.9.1
Radio model & firmware
flex 6400 v.4.1.5
Operating system
Windows
OS version and hardware
windows 10 pro
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce this on a FLEX 6400 with two open slices using AetherSDR 0.9.1, following the Slice A/Slice B and Split mode sequence; inspect the attached support log for related state changes. Done means selecting a frequency on Slice B after closing Split mode changes Slice B's VFO rather than Slice A's.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100