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

rigctld dummy failure #504

Closed
mdblack98 opened this issue Jan 11, 2021 · 0 comments
Closed

rigctld dummy failure #504

mdblack98 opened this issue Jan 11, 2021 · 0 comments
Labels
bug critical A problem for common operations with WSJT-X, GPredict, RigPi, etc.

Comments

@mdblack98
Copy link
Contributor

a recent hamlib update killed my workflow.

To strip it down, I opened two windows, and the
commands are

rigctld -vvv

in the first window and

rigctl -m 2 -vvvv

in the second one. Used to work until few days ago but not after my last pull.

output window 1 (all OK)

[MacChef:Ham/@@MacSoftware/hamlib] chwu% rigctld -vvv
Recommend using --vfo switch for rigctld if client supports it
rigctl and netrigctl will automatically detect vfo mode
Opened rig model 1, ‚Dummy'

output window 2 (no longer working):

[MacChef:] chwu% rigctl -m 2 -vvvv
rigctl Hamlib 4.1
git
Last commit was Sun Jan 10 20:39:39 2021 +0000 SHA=4571dc
Report bugs to hamlib-developer@lists.sourceforge.net

rig_init called
initrigs4_dummy: _init called
rig_register called
rig_register: rig_register (1)
rig_register called
rig_register: rig_register (2)
rig_register called
rig_register: rig_register (4)
rig_register called
rig_register: rig_register (5)
rig_register called
rig_register: rig_register (6)
rig_init: rig does not have rx_range!!
Unknown rig num 2, or initialization error.
Please check with --list option.

until two days ago, the output from window 2 was
(and this is OK)

[MacChef:] chwu% rigctl -m 2 -vvvv
rigctl Hamlib 4.1
git
Last commit was Mon Dec 07 04:54:47 2020 +0000 SHA=15958c
Report bugs to hamlib-developer@lists.sourceforge.net

rig_init called
initrigs4_dummy: _init called
rig_register called
rig_register: rig_register (1)
rig_register called
rig_register: rig_register (2)
rig_register called
rig_register: rig_register (4)
rig_register called
rig_register: rig_register (5)
rig_register called
rig_register: rig_register (6)
rig_open called
port_open called
network_open called
network_open version 1.0
network_open: hoststr=127.0.0.1, portstr=4532
netrigctl_open called
netrigctl_transaction: called len=9
network_flush called
write_block called
netrigctl_open: vfo_mode=0
netrigctl_transaction: called len=12
network_flush called
write_block called
rig_get_vfo called
netrigctl_get_vfo called
netrigctl_transaction: called len=2
network_flush called
write_block called
rig_parse_vfo called
Opened rig model 2, 'NET rigctl'
Backend version: 20200503.0, Status: Stable

@mdblack98 mdblack98 added bug critical A problem for common operations with WSJT-X, GPredict, RigPi, etc. labels Jan 11, 2021
@mdblack98 mdblack98 added this to the 4.1 milestone Jan 11, 2021
mdblack98 added a commit that referenced this issue Jan 11, 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.
Projects
None yet
Development

No branches or pull requests

1 participant