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

Stray dummy_get_channel called in rigerror #526

Closed
df7cb opened this issue Feb 4, 2021 · 3 comments
Closed

Stray dummy_get_channel called in rigerror #526

df7cb opened this issue Feb 4, 2021 · 3 comments

Comments

@df7cb
Copy link
Contributor

df7cb commented Feb 4, 2021

Seen in 4.1 and git head, looks like a leftover from debugging:

perl /usr/share/doc/libhamlib-perl/examples/perltest.pl
get_conf:		path = "/dev/Rig", retry = 50
freq:			14266000
get_mode:		FM
width:			15000
get_vfo:		VFOA
Backend copyright:	LGPL
Model:			Dummy
Manufacturer:		Hamlib
Backend version:	20200606.0
get_info:		Nothing much (dummy)
VOX delay:		0
VOX delay:		5
get_channel status:	0 = Command completed successfully
dummy_get_channel called                             <--------------- there
VFO:			VFOA, 14266000
Attenuators:		10 20 30 0 0 0 0 0

(On 4.1, there's a huge amount of bogus whitespace around it, but that's fixed in head.)

@mdblack98 mdblack98 added this to the 4.2 milestone Feb 4, 2021
@mdblack98
Copy link
Contributor

Not a leftover -- new rig_error return contains the last debug message now -- may soon contain the last two messages.
So I'll modify perltest.pl to allow for the new format.

@df7cb
Copy link
Contributor Author

df7cb commented Feb 4, 2021

Thanks for the feedback!
But, how is that supposed to be useful? If some program like wsjtx gets a rig error and tells me in the popup window "whatever_get_channel called", does that help me with fixing the problem?

@mdblack98
Copy link
Contributor

It doesn't help you -- it helps those of us who can fix the problem.
I'm still working on gettting more useful messages -- it's a work in progress.

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

2 participants