aethersdr / aethersdr/AetherSDR
Send TCI mode updates when changing bands...
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?
I am developing a TCI bridge between AetherSDR and external logging software such as Wavelog (https://github.com/wavelog/wavelog) to transfer the current frequency and operating mode...
When changing bands in AetherSDR, the TCI server updates the frequency correctly, but it does not send the current operating mode, the mode is only sent when the user manually changes it afterwards in AetherSDR
As a result, the bridge cannot keep Wavelog fully synchronized, because the frequency/band is updated correctly but the mode remains missing or incorrect after a band change...
What did you expect?
When changing bands, I expected AetherSDR to send the current operating mode through TCI together with the frequency/band update, so external applications like Wavelog remain synchronized with the radio state without requiring a manual mode change...
Steps to reproduce
TCI (Enabled)
AetherSDR version
26.7.2
Radio model & firmware
Flex 8400
Operating system
Windows
OS version and hardware
Windows 11 Profesional
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
The issue names no file or test; start at the TCI server's band-change handling and reproduce with TCI enabled while changing bands. Done means the current operating mode is sent through TCI together with the frequency/band update, without requiring a manual mode change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100