Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown remote command: ("\\get_powerstat") , when connecting from hamlib (rigctl) or wsjtx #1277

Closed
baryluk opened this issue Sep 12, 2023 · 4 comments · Fixed by #1334
Closed
Labels

Comments

@baryluk
Copy link

baryluk commented Sep 12, 2023

I am trying to setup gqrx with wsjtx, on Debian linux, both latest stable versions, and I am getting errors on connection, because it looks like hamlib (which wsjtx uses too) by default sends some commands on connection startup. This is \get_powerstat, but gqrx does not understand it.

user@debian:~$ rigctl --version
rigctl Hamlib 4.5.5 Apr 05 11:43:08Z 2023 SHA=6eecd3
user@debian:~$ dpkg -l gqrx-sdr | grep amd64
ii  gqrx-sdr       2.16-1       amd64        Software defined radio receiver
$ gqrx
...
Unknown remote command: ("\\get_powerstat")
strace rigctl --model=2  --rig-file=127.0.0.1:7356
...
...
socket(AF_INET, SOCK_STREAM, IPPROTO_TCP) = 5
connect(5, {sa_family=AF_INET, sin_port=htons(7356), sin_addr=inet_addr("127.0.0.1")}, 16) = 0
getsockname(5, {sa_family=AF_INET, sin_port=htons(57252), sin_addr=inet_addr("127.0.0.1")}, [16]) = 0
ioctl(5, FIONREAD, [0])                 = 0
write(5, "\\get_powerstat\n", 15)       = 15
pselect6(6, [5], NULL, [5], {tv_sec=10, tv_nsec=0}, NULL) = 1 (in [5], left {tv_sec=9, tv_nsec=988072431})
read(5, "R", 1)                         = 1
pselect6(6, [5], NULL, [5], {tv_sec=10, tv_nsec=0}, NULL) = 1 (in [5], left {tv_sec=9, tv_nsec=999998330})
read(5, "P", 1)                         = 1
pselect6(6, [5], NULL, [5], {tv_sec=10, tv_nsec=0}, NULL) = 1 (in [5], left {tv_sec=9, tv_nsec=999999050})
read(5, "R", 1)                         = 1
pselect6(6, [5], NULL, [5], {tv_sec=10, tv_nsec=0}, NULL) = 1 (in [5], left {tv_sec=9, tv_nsec=999999040})
read(5, "T", 1)                         = 1
pselect6(6, [5], NULL, [5], {tv_sec=10, tv_nsec=0}, NULL) = 1 (in [5], left {tv_sec=9, tv_nsec=999998970})
read(5, " ", 1)                         = 1
pselect6(6, [5], NULL, [5], {tv_sec=10, tv_nsec=0}, NULL) = 1 (in [5], left {tv_sec=9, tv_nsec=999999040})
read(5, "1", 1)                         = 1
pselect6(6, [5], NULL, [5], {tv_sec=10, tv_nsec=0}, NULL) = 1 (in [5], left {tv_sec=9, tv_nsec=999999120})
read(5, "\n", 1)                        = 1
close(3)                                = 0
close(4)                                = 0
write(2, "rig_open: error = 127.0.0.1:7356"..., 60rig_open: error = 127.0.0.1:7356 No such file or directory 
) = 60

RPRT 1, which indicates a failure.

@baryluk
Copy link
Author

baryluk commented Sep 12, 2023

This is somehow related, and worth reading on hamlib side: Hamlib/Hamlib#1266

@argilo
Copy link
Member

argilo commented Sep 13, 2023

Gqrx already has already implemented a number of commands that are only needed for hamlib compatibility, so I suppose it wouldn't hurt to add more.

On my system, I also see that \chk_vfo is sent and responded to with RPRT 1, but WSJT-X seems happy to carry on after that.

@argilo argilo added the bug label Sep 19, 2023
@kukabu
Copy link
Contributor

kukabu commented Oct 2, 2023

Gqrx has 'u/U DSP' commands and I think it's possible to add get_powerstat/set_powerstat as aliases.

@argilo
Copy link
Member

argilo commented Oct 2, 2023

The long command names for u and U are get_func and set_func respectively:

https://hamlib.sourceforge.net/html/rigctl.1.html

get_powerstat and set_powerstat have 0x88 and 0x87 as single-character forms.

yarda added a commit to yarda/gqrx that referenced this issue Feb 4, 2024
Fixes gqrx-sdr#1277

Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
jj1bdx pushed a commit to jj1bdx/gqrx that referenced this issue Feb 25, 2024
Fixes gqrx-sdr#1277

Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants