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

Add rigctl command A/B/C to get A/B freq/mode/width #530

Closed
mdblack98 opened this issue Feb 7, 2021 · 1 comment
Closed

Add rigctl command A/B/C to get A/B freq/mode/width #530

mdblack98 opened this issue Feb 7, 2021 · 1 comment

Comments

@mdblack98
Copy link
Contributor

mdblack98 commented Feb 7, 2021

Add new command \get_vfo_info to rigctl/rigcltd to get VFOA freq/mode/width and VFOB freq/mode/width....or Main/Sub too.
This would replace using "f" for those apps that need to get both VFOA and VFOB frequencies like Log4OM.
freq/mode/width return could be extended to return more info if needed.

@mdblack98 mdblack98 added this to the 4.2 milestone Feb 7, 2021
mdblack98 added a commit that referenced this issue Feb 7, 2021
…th by vfo in one call

Overcomes limitation of f command where vfo swapping is needed if not in --vfo mode
rig_get_vfo_info function added
Log4OM should be able to get VFOB frequency on most rigs
#530
@mdblack98 mdblack98 reopened this Feb 10, 2021
@mdblack98
Copy link
Contributor Author

get_vfo_info works with readline support -- so it seems parsing of arguments for \ commands is incomplete.

Rig command: \get_vfo_info
VFO: VFOA
VFO: 145000000
Freq: FM
Mode: 15000

But not without readline support
Rig command: \get_vfo_info VFOA
VFO: 0
Freq:
Mode: 0
get_vfo_info: error = Invalid parameter
rigctl_parse: vfo_opt=0

@mdblack98 mdblack98 added the bug label Feb 10, 2021
mdblack98 added a commit that referenced this issue Feb 10, 2021
Should allow Log4OM to query VFOB/Sub freq now
Another fix to argumenet prompting with rigctl/rigctld
#530
mdblack98 added a commit that referenced this issue Feb 10, 2021
Should allow Log4OM to query VFOB/Sub freq now
Another fix to argumenet prompting with rigctl/rigctld
Add 2nd line of return for rigerror -- we well gradually be improving error info
#530
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant