TCI problem, TX at max. 54%
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- desktop, networking
Research direction
Start by reproducing the issue in AetherSDR with WSJT-X using TCI for audio input and output, then compare the transmit path with DAX, which reaches full power. Trace the TCI tune and transmit flow; done means TCI transmission reaches the expected power instead of stopping at 54%.
Written by the indexing model from the issue text.
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?
TCI problem: AetherSDR connected to WSJT-X. Connection is via TCI als audio input and audio output via TCI.
When I press the tune button in WSJT-X (100% power): i get no power output or mlac 54%. When I press TUNE buttin in AetherSDR (slider set to 100% Tune power) I get max. 54% of power.
When I switch audio in/out to DAX, everything is working at 100%
Same when I transmit via the TCI cionnection, also then it is max. 54%.
This happens sincs v26.9.1.
What did you expect?
Power output must bne around 100%.
Steps to reproduce
- Open AetherSDR
- Choose a band
- Open WSJT-X (connected via TCI and audio in/out = TCI)
- Press Tune button
- Output power must be around 100%
- Output is max. 54%
AetherSDR version
26.9.1
Radio model & firmware
Flex 8600 v4.2.2
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
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.
More from aethersdr/AetherSDR
-
audio documentation good first issue maintainer-review
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
bug CW maintainer-review safety
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
docs(agents): family PRs must stay in the family tree (shared applet/pan/model edits stall review) Opendocumentation enhancement maintainer-review
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
-
bug good first issue GUI maintainer-review priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 86/100
All issues in aethersdr/AetherSDR
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·