Report preparation
What happened?
No duplicate found after searching open issues for DAX, ALC, TX power, WSJT-X, and related transmit/audio terms. This appears to be a new report.
Bug Report
Excessive ALC on Slice D for WSJT-X digital modes (works correctly on B/C)
What happened
When using Slice D for WSJT-X digital modes (FT8/etc.), ALC levels are excessively high on all bands, even with identical WSJT-X power settings and the same radio TX power level that works correctly with Slice B or Slice C. The issue is reproducible and specific to Slice D in AetherSDR v26.5.2.1.
What I expected
ALC behavior should be consistent across Slices B, C and D for the same audio source/settings (WSJT-X output + AetherSDR TX gain/power). Slice D should not drive the radio into high ALC when the others do not.
Steps to reproduce
1.Connect AetherSDR to a FlexRadio (e.g., FLEX-8600).
2.Create/open multiple slices (at least up to D).
3.Configure WSJT-X to use Slice D (via CAT/TCI or equivalent).
4.Set the same TX power level in WSJT-X/radio as used successfully on Slice B or C.
5.Transmit (e.g., FT8) and observe ALC meter/gauge.
6.Repeat on Slice B or C for comparison.
Environment
- AetherSDR version: v26.5.2.1
- OS: Windows 11
- Radio: FLEX-8600, firmware 4.2.18
- Use case: Digital modes via WSJT-X over DAX
Suggested fix
Likely a per-slice difference in how TX audio gain, DAX-equivalent routing, or ALC-related parameters (e.g., mic gain, TX drive scaling, or slice-specific TX profile application) are applied in the audio engine or protocol commands for Slice D. Check SliceModel/TX handling for index-specific logic (slices are often 0-indexed internally, so D may be slice 3). Compare command sequences or status updates sent/received for different slice IDs during TX.
Labels: bug, audio, DAX, TX
AetherSDR version
V26.5.2.1
Radio model & firmware
FLEX-8600 4.2.18
Operating system
Windows
OS version and hardware
Windows 11
Report preparation
What happened?
No duplicate found after searching open issues for DAX, ALC, TX power, WSJT-X, and related transmit/audio terms. This appears to be a new report.
Bug Report
Excessive ALC on Slice D for WSJT-X digital modes (works correctly on B/C)
What happened
When using Slice D for WSJT-X digital modes (FT8/etc.), ALC levels are excessively high on all bands, even with identical WSJT-X power settings and the same radio TX power level that works correctly with Slice B or Slice C. The issue is reproducible and specific to Slice D in AetherSDR v26.5.2.1.
What I expected
ALC behavior should be consistent across Slices B, C and D for the same audio source/settings (WSJT-X output + AetherSDR TX gain/power). Slice D should not drive the radio into high ALC when the others do not.
Steps to reproduce
1.Connect AetherSDR to a FlexRadio (e.g., FLEX-8600).
2.Create/open multiple slices (at least up to D).
3.Configure WSJT-X to use Slice D (via CAT/TCI or equivalent).
4.Set the same TX power level in WSJT-X/radio as used successfully on Slice B or C.
5.Transmit (e.g., FT8) and observe ALC meter/gauge.
6.Repeat on Slice B or C for comparison.
Environment
Suggested fix
Likely a per-slice difference in how TX audio gain, DAX-equivalent routing, or ALC-related parameters (e.g., mic gain, TX drive scaling, or slice-specific TX profile application) are applied in the audio engine or protocol commands for Slice D. Check SliceModel/TX handling for index-specific logic (slices are often 0-indexed internally, so D may be slice 3). Compare command sequences or status updates sent/received for different slice IDs during TX.
Labels: bug, audio, DAX, TX
AetherSDR version
V26.5.2.1
Radio model & firmware
FLEX-8600 4.2.18
Operating system
Windows
OS version and hardware
Windows 11