Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Please allow time or angle overshoot for AOS/LOS rigctl signaling in radio control

未关闭
#284 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
c
领域
desktop

调研方向

The AOS and LOS signalling decisions are in src/gtk-rig-ctrl.c, where the issue points to the hardcoded 0.0 degree elevation checks near lines 2314 and 2331. Read how those checks feed the rig control signals, then decide whether the overshoot should be a time margin or an angle, since the issue leaves that open. Done means a user-configurable overshoot exists, the default behaviour is unchanged, and the signals fire earlier and later by the chosen amount. No test is named in the payload, so verify by running a pass with rigctl signalling enabled.

由索引模型根据 Issue 内容生成。

描述

I have clear horizon and it seems I have up to 30 seconds of quite a good signal reception before AOS and after LOS is signaled for ISS passes. This adds nearly one minute to the window which could be utilized for nearly half ARISS SSTV PD120 image reception which is worth the effort.

Please add an option allowing time (or maybe angle) overshoot when using AOS/LOS rigctl signaling for automatic recording.

It seems currently 0.0 degree elevation is hardcoded for AOS:
https://github.com/csete/gpredict/blob/master/src/gtk-rig-ctrl.c#L2314
and LOS:
https://github.com/csete/gpredict/blob/master/src/gtk-rig-ctrl.c#L2331

主要语言
C
星标
1.2k
派生
305
平均合并
8 小时 48 分钟
30 天内合并 PR
3

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

csete/gpredict 的其他 Issue

查看 csete/gpredict 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。