You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ICOM IC-910H doppler control semi-functional with current hamlib #367
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
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?
--vfo is the only way to run Icom rigs with gpredict -- without the vfos can swap like crazy.
Can you send me a debug log with the --vfo please?
Message ID: ***@***.***>
Are you using this branch?
https://github.com/KaComet/gpredict/tree/Hamlib_VFO
On Wednesday, September 18, 2024 at 03:03:59 PM CDT, Joshua ***@***.***> wrote:
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
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
Or csete's repo?
https://github.com/KaComet/gpredict.git
Most recent commit:
commit 91a4a3fb15e7eab0374d1bb7c859d386818b48eeAuthor: AsciiWolf ***@***.***>Date: Tue Jul 9 16:06:28 2024 +0200
Desktop fixes
On Wednesday, September 18, 2024 at 03:23:19 PM CDT, Michael Black ***@***.***> wrote:
Are you using this branch?
https://github.com/KaComet/gpredict/tree/Hamlib_VFO
On Wednesday, September 18, 2024 at 03:03:59 PM CDT, Joshua ***@***.***> wrote:
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
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
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
I assume you are compiling yourself?
Can you try the latest git version of hamlib?
Mike W9MDB
On Wednesday, September 18, 2024 at 03:43:54 PM CDT, Joshua ***@***.***> wrote:
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
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
Activity
mdblack98 commentedon Sep 18, 2024
dl3jop commentedon Sep 18, 2024
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 calledDiscarding the --vfo flag yields the
Command rejected by the rigerrors as in the logs abovemdblack98 commentedon Sep 18, 2024
dl3jop commentedon Sep 18, 2024
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 calledmdblack98 commentedon Sep 18, 2024
mdblack98 commentedon Sep 18, 2024
dl3jop commentedon Sep 18, 2024
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
mdblack98 commentedon Sep 22, 2024