Skip to content

INVALID CHANNEL is cryptic #509

@jmkristian

Description

@jmkristian

If I configure two devices, like this:

ADEVICE plughw:CARD=Digirig,DEV=0
ACHANNELS 1
ADEVICE1 plughw:CARD=DRA,DEV=0

... the second AGW port is described to AGW clients as INVALID CHANNEL. An AGW 'X' request to this port elicits this response:
{port:1, dataKind:"X", callFrom:"W6JMK", data:"00"}
Which suggests that Direwolf rejected the call sign. Direwolf's log output is not much more informative:
ERROR - Request to transmit on invalid radio channel 1.

I would prefer that invalid channels are not visible to AGW clients, or at least the log message says something about this port relating to the right channel of the first device (not a channel of the second device).

I used Direwolf built from source tag 1.7 commit de293a1 on Ubuntu 22.04.3 on an x86_64 laptop.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions