-
Notifications
You must be signed in to change notification settings - Fork 200
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
Regression from recent commit (set_level: Feature not available) #778
Labels
bug
critical
A problem for common operations with WSJT-X, GPredict, RigPi, etc.
needs test
Patches have been submitted but need testing to close issue
Milestone
Comments
cjritola
referenced
this issue
Aug 29, 2021
I can't reproduce this problem. Works fine here under Linux and Windows.
How are you getting error messages without using the verbose switches?
rigctl -vvv -m 1 set_level PREAMP 0
Opened rig model 1, 'Dummy'
Mike W9MDB
On Sunday, August 29, 2021, 06:06:42 AM CDT, Chuck Ritola ***@***.***> wrote:
rigctl -m 1 set_level PREAMP 0
set_level: error = Feature not available
read_string called, rxmax=1024
read_string(): RX 9 characters
rigctl_parse.c(3150):rigctl_set_level return(-11)
... issue arises in commit
d16fa49
Commenting parts of block starting at line 1000 in tests/rigctl_parse.c fixes it:
if (interactive)
{
rig_debug(RIG_DEBUG_TRACE, "%s: debug7\n", __func__);
//arg1[0] = fgetc(fin);
//arg1[1] = 0;
if (prompt /* && arg1[0] == 0x0a */)
{
I was pulling my hair out trying to get my new code to work when I realized rig_caps.set_level wasn't even getting called. XD
Looks like the parser was passing an empty string to rig_parse_level() in declare_proto_rig(set_level). I don't understand what is happening beyond that.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
How about this:
I think I got confused 7 hrs in. |
mdblack98
added
bug
critical
A problem for common operations with WSJT-X, GPredict, RigPi, etc.
labels
Aug 29, 2021
mdblack98
added a commit
that referenced
this issue
Aug 29, 2021
mdblack98
added
the
needs test
Patches have been submitted but need testing to close issue
label
Aug 29, 2021
Try again please...think I fixed it.
Mike W9MDB
On Sunday, August 29, 2021, 09:28:13 AM CDT, Chuck Ritola ***@***.***> wrote:
How about this:
***@***.***:~/Hamlib$ rigctld -m 1 &
[1] 20946
***@***.***:~/Hamlib$ rigctl -m 2 -r localhost set_level PREAMP 1
set_level: error = Feature not available
read_string called, rxmax=1024
read_string(): RX 9 characters
rigctl_parse.c(3150):rigctl_set_level return(-11)
I think I got confused 7 hrs in.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
That fixed it, thanks |
wutje
pushed a commit
to wutje/Hamlib
that referenced
this issue
Sep 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
critical
A problem for common operations with WSJT-X, GPredict, RigPi, etc.
needs test
Patches have been submitted but need testing to close issue
... issue arises in commit
d16fa49
Commenting parts of block starting at line 1000 in tests/rigctl_parse.c fixes it:
I was pulling my hair out trying to get my new code to work when I realized rig_caps.set_level wasn't even getting called. XD
Looks like the parser was passing an empty string to rig_parse_level() in declare_proto_rig(set_level). I don't understand what is happening beyond that.
The text was updated successfully, but these errors were encountered: