ICOM IC-910H doppler control semi-functional with current hamlib · Issue #367 · csete/gpredict · GitHub
Skip to content

ICOM IC-910H doppler control semi-functional with current hamlib #367

Open

Description

@dl3jop

Hey,

I've seen multiple issues, some closed, some still open, with conflicting issues regarding doppler control on the IC-910.
I did some tests and wanted to share the current state (and if i find ideas how to fix it) :

Issue:

  • Doppler control with gpredict/hamlib/ic910 not working
  • only downlink is corrected, rigctld shows rejected command errors
  • if the VFO knob on the radio is turned, the frequency jumps back and forth a couple of kHz
  • disengages after some seconds

Steps to reproduce:

  • rigctld Hamlib 4.6~git 2024-08-19T14:01:05Z SHA=137231 64-bit
  • gpredict 2.2.1
  • radio setup as per https://github.com/csete/gpredict/blob/master/doc/notes/ic-910.txt:
    grafik
  • rigctld commands:
    • rigctld -m 3044 --serial-speed=19200 -r /dev/ttyUSB0 -vvvvv
    • adding --vfo has no apparent effect
    • adding --twiddle_timeout=2s decreases the frequency jumps a little but sometimes jumps still occur
  • IC-910 in satellite mode
  • Result:
    • gpredict sets inital downlink frequency, and tracks it for some seconds, than disengages

The rigctld log is spammed with rejected commands: https://pastebin.com/asNU0FjC
The logs show errors when addressing VFO_A/B but in this mode I think it should be Main/Sub?

I also tried this branch with no success

Did anyone get it to work lately?
All the best,
Joshua

Activity

  1. mdblack98 commented on Sep 18, 2024

    @mdblack98
    Contributor
  2. dl3jop commented on Sep 18, 2024

    @dl3jop
    Author

    Hey Michael,
    thanks for coming back so quickly, I compiled it with your version with the new backend but the error still persists:

    Using --vfo the rigctl gets unresponsive trying to retreive the VFO:
    Backend version: 20240831.2, Status: Stable main: Using IPV4 main: rigctld listening on port 4532 Connection opened from 127.0.0.1:60392 mutex_rigctld: client lock engaged mutex_rigctld: client lock disengaged mutex_rigctld: client lock engaged mutex_rigctld: client lock disengaged handle_socket: doing rigctl_parse vfo_mode=1, secure=0 rigctl_parse: called, interactive=1 rigctl_parse: cmd=S(53) handle=9 rig_parse_vfo called

    Discarding the --vfo flag yields the Command rejected by the rig errors as in the logs above

  3. mdblack98 commented on Sep 18, 2024

    @mdblack98
    Contributor
  4. dl3jop commented on Sep 18, 2024

    @dl3jop
    Author

    Ah, thanks for the information about the --vfo flag.

    Here's the log: https://pastebin.com/DvC3bS6p

    After engaging control in gpredict it just freezes at rig_parse_vfo called

  5. mdblack98 commented on Sep 18, 2024

    @mdblack98
    Contributor
  6. mdblack98 commented on Sep 18, 2024

    @mdblack98
    Contributor
  7. dl3jop commented on Sep 18, 2024

    @dl3jop
    Author

    Using the master branch it freezes on the same position: https://pastebin.com/dxfw3zPZ

    Using the hamlib_VFO branch, it tracks and corrects downlink but the uplink is unchanged and not written to the radio. When spinning the radios VFO dial it crashes after some seconds:
    vfo_branch.log

  8. mdblack98 commented on Sep 22, 2024

    @mdblack98
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions