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

FTDX3000 ptt still on #906

Closed
mdblack98 opened this issue Dec 27, 2021 · 0 comments
Closed

FTDX3000 ptt still on #906

mdblack98 opened this issue Dec 27, 2021 · 0 comments
Labels
bug critical A problem for common operations with WSJT-X, GPredict, RigPi, etc. JTDX Bugs affecting JTDX operations WSJTX Bugs affecting WSTJ-X operations

Comments

@mdblack98
Copy link
Contributor

[RIGCTRL][2021-12-26 00:28:59.392481][00:46:55.682797][warning] newcat_set_freq: ptt still on...retry#3
[RIGCTRL][2021-12-26 00:28:59.535992][00:46:55.826331][warning] newcat_set_freq: ptt still on...retry#2
[RIGCTRL][2021-12-26 00:28:59.677373][00:46:55.967671][warning] newcat_set_freq: ptt still on...retry#1
[RIGCTRL][2021-12-26 00:28:59.817436][00:46:56.107748][warning] newcat_set_freq: ptt still on...retry#0
[RIGCTRL][2021-12-26 00:28:59.929317][00:46:56.219564][error] error: Target VFO unaccessible
newcat.c(1677):newcat_get_ptt return(0)
newcat_set_freq: ptt still on...retry#0
rig.c(1936):rig_set_freq return(12)
[SYSLOG][2021-12-26 00:28:59.933320][00:46:56.224093][error] handle_transceiver_failure: reason: Hamlib error: Target VFO unaccessible
newcat.c(1677):newcat_get_ptt return(0)
newcat_set_freq: ptt still on...retry#0
rig.c(1936):rig_set_freq return(12) while setting frequency

@mdblack98 mdblack98 added bug critical A problem for common operations with WSJT-X, GPredict, RigPi, etc. WSJTX Bugs affecting WSTJ-X operations JTDX Bugs affecting JTDX operations labels Dec 27, 2021
mdblack98 added a commit that referenced this issue Dec 27, 2021
This will covers rigs that cannot set freq while transmitting like the FTDX3000 and FTDX5000
#906
mdblack98 added a commit that referenced this issue Dec 27, 2021
VS1;VS; was answering VS0 instead of VS1 even though VFO did change to VFOB
#906
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. JTDX Bugs affecting JTDX operations WSJTX Bugs affecting WSTJ-X operations
Projects
None yet
Development

No branches or pull requests

1 participant