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

KX3 responds to v with VFOA after setting VFOB. #563

Closed
mdblack98 opened this issue Feb 25, 2021 · 3 comments
Closed

KX3 responds to v with VFOA after setting VFOB. #563

mdblack98 opened this issue Feb 25, 2021 · 3 comments
Labels
bug critical A problem for common operations with WSJT-X, GPredict, RigPi, etc. holding Issues being held for other solutions beyond our control needs test Patches have been submitted but need testing to close issue RigPi Issues affecting RigPi operations

Comments

@mdblack98
Copy link
Contributor

Rig command: V VFOB
rigctl_parse: cmd=V(56)
rigctl_parse: cmd==0x56
rigctl_parse: vfo_opt=0
rigctl_parse: debug1
rigctl_parse: debug3
rigctl_parse: debug4 arg1=
rigctl_parse: debug5
rigctl_parse: debug10
rigctl_parse: vfo_opt=0
rig_parse_vfo called
rig.c(2285):rig_set_vfo entered
rig_set_vfo called vfo=VFOB
vfo_fixup: vfo=VFOB
vfo_fixup: final vfo=VFOB
k3_set_vfo called
kenwood_transaction called
kenwood_transaction: cache invalidated
kenwood_transaction: cmdstr = SWT11
rig_flush: called for serial device
serial.c(628):serial_flush entered
tcflush
serial.c(660):serial_flush return
write_block called
write_block(): TX 6 bytes
0000 53 57 54 31 31 3b SWT11;
write_block called
write_block(): TX 3 bytes
0000 49 44 3b ID;
read_string called, rxmax=35
read_string(): RX 6 characters
0000 49 44 30 31 37 3b ID017;
kenwood_transaction: read_string(len=6)='ID017;'
kenwood_transaction: No data expected, checking ID; in ID017;
kenwood_transaction: returning RIG_OK, retval=0
kenwood_transaction: returning retval=0
kenwood.c(557):kenwood_transaction return
rig_set_vfo: rig->state.current_vfo=VFOB
kenwood_get_freq called
kenwood_safe_transaction called
kenwood_transaction called
kenwood_transaction: cmdstr = FB
rig_flush: called for serial device
serial.c(628):serial_flush entered
tcflush
serial.c(660):serial_flush return
write_block called
write_block(): TX 3 bytes
0000 46 42 3b FB;
read_string called, rxmax=51
read_string(): RX 14 characters
0000 46 42 30 30 30 32 38 30 33 39 32 36 38 3b FB00028039268;
kenwood_transaction: read_string(len=14)='FB00028039268;'
kenwood_transaction: returning RIG_OK, retval=0
kenwood_transaction: returning retval=0
kenwood.c(557):kenwood_transaction return
kenwood.c(627):kenwood_safe_transaction return
kenwood.c(1677):kenwood_get_freq return
rig_set_vfo: retcode from rig_get_freq = Command completed successfully
kenwood.c(1677):kenwood_get_freq return
rig_set_vfo: retcode from rig_get_freq = Command completed successfully
kenwood.c(1677):kenwood_get_freq return
kenwood.c(1677):kenwood_get_freq return
elapsed_ms: start = 1614275484,719085442
elapsed_ms: elapsed_msecs=10000
elapsed_ms: start = 0,0
elapsed_ms: elapsed_msecs=10000
rig_set_vfo: return 0, vfo=VFOB
rig.c(2361):rig_set_vfo return
rigctl_parse: vfo_opt=0
rigctl_parse: retcode=0
rigctl_parse: called, interactive=1

Rig command: rigctl_parse: cmd==0x0a

rigctl_parse: cmd==0x0a
? for help, q to quit.

Rig command: rigctl_parse: called, interactive=1

Rig command: v
rigctl_parse: cmd=v(76)
rigctl_parse: cmd==0x76
rigctl_parse: vfo_opt=0
rigctl_parse: debug1
rigctl_parse: debug5
rigctl_parse: debug10
rigctl_parse: vfo_opt=0
rig.c(2386):rig_get_vfo entered
elapsed_ms: start = 1614275480,862083014
elapsed_ms: elapsed_msecs=26653
rig_get_vfo: cache check age=26653ms
rig_get_vfo: cache miss age=26653ms
kenwood_get_vfo_if called
kenwood_get_if called
kenwood.c(998):kenwood_get_if return
kenwood_safe_transaction called
kenwood_transaction called
kenwood_transaction: cmdstr = IF
rig_flush: called for serial device
serial.c(628):serial_flush entered
tcflush
serial.c(660):serial_flush return
write_block called
write_block(): TX 3 bytes
0000 49 46 3b IF;
read_string called, rxmax=128
read_string(): RX 38 characters
0000 49 46 30 30 30 32 38 30 33 39 31 35 30 20 20 20 IF00028039150
0010 20 20 2b 30 31 36 30 30 30 20 30 30 30 32 30 30 +016000 000200
0020 30 30 30 31 20 3b 0001 ;
kenwood_transaction: read_string(len=38)='IF00028039150 +016000 0002000001 ;'
kenwood_transaction: returning RIG_OK, retval=0
elapsed_ms: start = 0,0
elapsed_ms: after gettime, start = 1614275507,563120745
kenwood_transaction: returning retval=0
kenwood.c(557):kenwood_transaction return
kenwood.c(627):kenwood_safe_transaction return
kenwood_get_vfo_if: priv->tx_vfo=VFOA
kenwood.c(1464):kenwood_get_vfo_if return
elapsed_ms: start = 0,0
elapsed_ms: after gettime, start = 1614275507,563303038
rig.c(2436):rig_get_vfo return
VFO: VFOA
rigctl_parse: vfo_opt=0
rigctl_parse: retcode=0
rigctl_parse: called, interactive=1

@mdblack98 mdblack98 added this to the 4.2 milestone Feb 25, 2021
@mdblack98 mdblack98 added bug RigPi Issues affecting RigPi operations critical A problem for common operations with WSJT-X, GPredict, RigPi, etc. labels Feb 25, 2021
mdblack98 added a commit that referenced this issue Feb 26, 2021
mdblack98 added a commit that referenced this issue Feb 27, 2021
KX4 set_vfo may not work
#563
@mdblack98 mdblack98 added the needs test Patches have been submitted but need testing to close issue label Feb 27, 2021
mdblack98 added a commit that referenced this issue Feb 27, 2021
mdblack98 added a commit that referenced this issue Mar 1, 2021
k3.c fix set_mode for VFOB
k3.c remove passband limit checks and just let the rig do it's thing
#563
mdblack98 added a commit that referenced this issue Mar 1, 2021
mdblack98 added a commit that referenced this issue Mar 1, 2021
@mdblack98
Copy link
Contributor Author

Elecraft rigs seem function with the exception of rig_set_mode on the K4.
It seems the is doing band selection operations after a set_mode and misses the bandwidth request -- or rather overrides the bandwidth request from hamlib with the bandstack value. Bandstack is by band and mode.
So holding this issue open until Elecraft fixes the problem.

@mdblack98 mdblack98 added the holding Issues being held for other solutions beyond our control label Mar 2, 2021
mdblack98 added a commit that referenced this issue Mar 3, 2021
@mdblack98
Copy link
Contributor Author

Elecraft rigs have no real concept of A/B being active -- the vfos are directly addressable so all we do is emulate the VFO selection to make rigctl happy.

Still holding this open for firmware fix for the K4 on the bandstack overriding the frequency set request.

@mdblack98
Copy link
Contributor Author

Closed -- K4 firmware as of 2021-03-12 has this problem fixed.
Tested with Dick Dievendorf

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. holding Issues being held for other solutions beyond our control needs test Patches have been submitted but need testing to close issue RigPi Issues affecting RigPi operations
Projects
None yet
Development

No branches or pull requests

1 participant