ICOM IC-910H doppler control semi-functional with current hamlib
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 22/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- c
- 领域
- desktop-dev
调研方向
Start with the radio setup notes in doc/notes/ic-910.txt and the rig-control path that talks to rigctld (hamlib model 3044). The open question is whether VFO_A/VFO_B should map to Main/Sub in satellite mode, which needs a rig and hardware to reproduce. Done means the downlink and uplink tracking stay locked without the rejected-command spam, which can't be confirmed without an IC-910H attached.
由索引模型根据 Issue 内容生成。
描述
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:
- 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
- 主要语言
- C
- 星标
- 1.2k
- 派生
- 305
- 平均合并
- 8 小时 48 分钟
- 30 天内合并 PR
- 3
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
csete/gpredict 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1 小时以内 新手友好度 60/100
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 3/5 1-2 天 新手友好度 55/100
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
bug Component component: net
难度 2/5 1-3 小时 新手友好度 78/100
RT-Thread/rt-thread#11913 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
contiki-ng/contiki-ng#3289 ·
维护者通常 3 天内回复
-
area:docs help wanted type:enhancement
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
semantic-reasoning/wirelog#2229 ·
维护者通常 1 天内回复