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

FTdx101D \set_vfo \get_vfo not working #408

Closed
Ian-G3VPX opened this issue Oct 10, 2020 · 3 comments
Closed

FTdx101D \set_vfo \get_vfo not working #408

Ian-G3VPX opened this issue Oct 10, 2020 · 3 comments
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

Comments

@Ian-G3VPX
Copy link

FTdx101D VFO selection problem

\get_vfo

Main selected on rig:
v > result = Main scope decode VS; > VS0; = correct

Sub Selected on rig
v > result = VFOB scope decode: VS; > VS1; = correct *********

\set_vfo .... scope decode: no CAT command sent

V Main
set_vfo: error = Feature not impemented

V VFOA
set_vfo: error = Invalid parameter

V Sub
set_vfo: error = Feature not impemented

V VFOB
set_vfo: error = Invalid parameter

\set_vfo Sub
set_vfo: error = Feature not impemented

@mdblack98 mdblack98 added critical A problem for common operations with WSJT-X, GPredict, RigPi, etc. needs test Patches have been submitted but need testing to close issue bug labels Oct 10, 2020
@Ian-G3VPX
Copy link
Author

\set_vfo Main and \set_vfo Sub ( and \get_vfo )

  • working fine at rigctl command line
  • Not working in piWebCAT with rigctld - nothing on scope on Tx line
    I echoed the string (ie \set_vfo Main) from the PHP code line immediately
    before the socketwrte and it looks ok
    Is this possible?
    Ian G3VPX

@mdblack98
Copy link
Contributor

mdblack98 commented Oct 10, 2020 via email

@Ian-G3VPX
Copy link
Author

This is working fine now - (rig > piWebCAT and piWebCAT > rig)
... rigctl command line ok
... piWebCAT rigctld ok
(having to tmeporarily use: if(cat == 'Sub\n') ... need to tidy this up and remove '\n' for all returns
... most returns are numeric and parseInt ignores '\n' )

N0NB pushed a commit to N0NB/Hamlib that referenced this issue Nov 3, 2020
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
Projects
None yet
Development

No branches or pull requests

2 participants