Skip to content

TCI: DRIVE and VOLUME commands have no effect when sent by client #1764

Description

@pvermote

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?

Hello,

I am controlling AetherSDR via TCI protocol from a Node.js server connected to a Stream Deck+, using a Flex 6600. AetherSDR reports TCI protocol version 1.5.

Aether version : v0.8.18

I am trying to control TX power (DRIVE), audio volume (VOLUME / RX_VOLUME) and Split mode remotely via TCI.

Observed behavior:

When I send the following commands from my TCI client, AetherSDR does not respond and the values do not change:

  • DRIVE:0,50; → no effect, power drops to 0 if previously set manually to another value
  • VOLUME:50; → no effect, no acknowledgement
  • RX_VOLUME:0,0,50; → no effect, AetherSDR replies with the old value
  • SPLIT_ENABLE:0,true; → no effect, no acknowledgement

However, when I read the current values:

  • RX_VOLUME:0,0; → AetherSDR correctly replies rx_volume:0,19;
  • DRIVE:0,27; → AetherSDR correctly sends current value at startup

Also, when I change TX power or volume manually in the AetherSDR GUI, nothing is broadcast to TCI clients — so I cannot even track the current value.

Expected behavior:

According to the TCI v2.0 documentation, DRIVE, VOLUME, RX_VOLUME and SPLIT_ENABLE are all bidirectional commands and should be settable by a TCI client.

Questions:

  1. Are DRIVE, VOLUME/RX_VOLUME and SPLIT_ENABLE currently implemented as writable commands in AetherSDR?
  2. If not, is there a planned fix or a workaround?
  3. Is there another TCI command to control TX power, audio volume and split mode?

Thank you for your help.

Best regards

What did you expect?

No response

Steps to reproduce

No response

Radio model & firmware

Flex 6600
FW : 4.1.539794
Aether v0.8.18

Linux distro & Qt version

Windows 11

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting-responseWaiting for reporter to provide additional informationenhancementImprovement to existing feature

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions