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

NET rigctl reports wrong Antenna set/get caps #1466

Closed
PianetaRadio opened this issue Dec 29, 2023 · 1 comment
Closed

NET rigctl reports wrong Antenna set/get caps #1466

PianetaRadio opened this issue Dec 29, 2023 · 1 comment
Labels
bug fixed Issue has been fixed
Milestone

Comments

@PianetaRadio
Copy link
Contributor

I have Yaesu FT-991, it has only one antenna selection and the newcat correctly reports no antenna selection capabilities.
But if I connect it via rigctld this cap is wrongly reported, for example this is the ouput of rigctl connected to rigctld connected to Yaesu FT-991

`rigctl -m 2
Rig command: /dump_caps

Rig command: \dump_caps
Caps dump for model: 2
Model name: NET rigctl
Mfg name: Hamlib
Hamlib version: Hamlib 4.6~git 2023-12-27T04:46:38Z SHA=da478d 32-bit

...

Can get Ant: Y
Can set Ant: Y
`

@PianetaRadio
Copy link
Contributor Author

This cause delay in my GUI when get_ant is wrongly called

2023-12-29T21:10:32.297535+0100: 2:rig.c(6151):rig_get_ant entered 2023-12-29T21:10:32.297535+0100: netrigctl_get_ant called 2023-12-29T21:10:32.297535+0100: netrigctl_transaction: called len=7 2023-12-29T21:10:32.297535+0100: network_flush called 2023-12-29T21:10:52.308564+0100: 2:rig.c(6179):rig_get_ant returning(-5) Communication timed out

@mdblack98 mdblack98 added this to the 4.6 milestone Dec 29, 2023
@mdblack98 mdblack98 added the bug label Dec 29, 2023
@mdblack98 mdblack98 added the fixed Issue has been fixed label Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fixed Issue has been fixed
Projects
None yet
Development

No branches or pull requests

2 participants