8000 Add support for VFO mode in Rigctrl. Gpredict will now try to enable … by KaComet · Pull Request #318 · csete/gpredict · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add support for VFO mode in Rigctrl. Gpredict will now try to enable … #318

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add support for VFO mode in Rigctrl. Gpredict will now try to enable … #318

wants to merge 1 commit into from

Conversation

KaComet
Copy link
Contributor
@KaComet KaComet commented Nov 28, 2022 •
edited
Loading

…and use VFO mode, usually set via the --vfo command line flag in Rigctrl, when connecting to a radio. If VFO mode could not be enabled, the old style of commanding the radio is used.

Why is this needed:

@mdblack98 has indicated that Gpredict should move to default to VFO mode.

Changes that impact the users

  • Users will now have to define the VFOs for the manual and auto modes, just like users of the full-duplex mode.

Testing:

All radio modes (full duplex, RX only, ect) were tested on an FT-736R, IC-9700, FT-991A. Additionally, I have been using this version of Gpredict for my personal use for approximately 1 week. I have not encountered any issues. Rigctrl version: rigctl Hamlib 4.6~git Mon Nov 28 22:45:08 2022 +0000 SHA=e2570d

Testing results:

FT-991A:

  • All modes working as intended. Testing with VFO mode forcefully disabled resulted in all modes working as intended. Testing with the half-duplex mode required some workarounds because the radio does not support switching bands while transmitting.

IC-9700:

  • All modes working as intended. Testing with VFO mode forcefully disabled resulted in all modes working as intended. Testing with the half-duplex mode required some workarounds because the radio does not support switching bands while transmitting.

FT-736R:

  • All modes working as intended. Testing with VFO mode forcefully disabled resulted in all modes working as intended. Testing with the half-duplex mode required some workarounds because the radio does not support switching bands while transmitting.

Additional relevant testing data will be provided on request.

@KaComet
Add support for VFO mode in Rigctrl. Gpredict will now try to enable …
3183702 
…and use VFO mode, usally set via the --vfo command line flag in Rigctrl, when connecting to a radio. If VFO mode could not be enabled, the old style of commanding the radio is used.
@mdblack98
Copy link
Contributor

Try the latest hamlib from the master repo. I put a patch in for the 736 that should set VFOB correctly.
https://github.com/Hamlib/Hamlib

@KaComet
Copy link
Contributor Author
KaComet commented Nov 29, 2022 •
edited
Loading

@mdblack98, latest Hamlib commit resolved issues with the FT-736R. Testing results have been updated. I appreciate your assistance. Hamlib version: rigctl Hamlib 4.6~git Mon Nov 28 22:45:08 2022 +0000 SHA=e2570d

@csete
Copy link
Owner
csete commented Dec 24, 2023

Hi @KaKomet

Thanks for the improvement and sorry for the late followup. I wanted to merge this but there are now some conflicts that I am unsure about how to resolve. Could you see if you can resolve them?

Thanks
Alex

@mdblack98
Copy link
Contributor

What conflicts?

@csete
Copy link
Owner
csete commented Dec 24, 2023

Sorry, I forgot that only I can see the merge conflict info.

I have tried to resolve the conflicts and pushed the code to the hamlibvfo branch. If it looks okay, I can merge it these changes manually.

@KaComet
Copy link
Contributor Author
KaComet commented Dec 24, 2023

@csete, thanks for taking a look. For reference, this PR is my implementation of mdblack's suggestion that GPredict should prefer to use VFO mode in Hamlib. You can find the original discussion regarding the use of VFO mode under #287 . While mdblack originally made #316 to implement VFO mode. Unfortunately, I found that this PR did not correctly implement VFO mode and broke compatibility with all of the radios I tested it with. After some testing, the discussion of which can be found in the comments under #316, I submitted this P 968F R with code that implements VFO mode.

I have tested this code of multiple radios and modes. Currently, I use this PR's changes for my everyday satellite endeavors. I even used these changes during this year's ARRL field day. You can see my testing data in the original PR comment.

I can take a look over the next few days and verify that the rig control loop works correctly under the resolved branch. I'll keep you updated with my results.

@df7cb
Copy link
df7cb commented Mar 1, 2025

Hi, I'm trying to get started with LEO sats, and getting gpredict to connect to my IC-9700 has been a bit bumpy.

This PR (merging with current master is trivial) works best so far, but there are still problems:

  • the radio is initially switched into SAT mode. In that mode, the rig only supports VFO A, and trying to set VFO B is rejected. The "Engage" button pops out again immediately. Both with and without this PR I can force it to work by manually unselecting SAT mode (Menu->Satellite).
  • the currently selected VFO is flickering from Main to Sub every second (or whatever other interval "Cycle" is selected). This looks annoying and (worse) breaks tuning with the VFO knob because while Sub is selected, the wrong VFO is moved.
  • I am running rigctld --vfo, if that still makes a difference.

Is anyone working on this? Any other branch that works better?

(There is also the question which version/branch of gpredict I should upload to Debian.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@KaComet @mdblack98 @csete @df7cb
0