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

FT-857D RX frequency increments for satellites with identical RX and TX frequencies

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
15/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
c, linux
领域
desktop-dev

调研方向

The report points to the transponder file ~/.config/Gpredict/trsp/53106.trsp (its DOWN_LOW and UP_LOW values for the same frequency) and the rig file with Type=4, LO and LO_UP, which the rig-control code reads when Engage is pressed. Start in the gpredict source where the rig is updated during tracking, and check how it handles the Hamlib rigctld connection on localhost:4533. Done means downlink and uplink keep their own frequencies after Engage, which needs an FT-857D or a rigctld simulator to verify.

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

描述

This may be related to #294 . I am trying to use gpredict for greencube. To define both the uplink and downlink frequencies, I added the following section to ~/.config/Gpredict/trsp/53106.trsp:

[Mode U GMSK FULL DUPLEX]
DOWN_LOW=435310000
UP_LOW=435310000
MODE=FSK AX.100 Mode 5
BAUD=1200

I defined a rig for this as "FT817/857/897 (auto)" with PTT Status set to "Read PTT". Its .rig file is as follows:

[Radio]
Host=localhost
Port=4533
LO=0
LO_UP=0
Type=4
PTT=1
SIGNAL_AOS=false
SIGNAL_LOS=false

My problem is when I start tracking the satellite and click "Engage", at first everything is normal; both the Downlink and Uplink radio frequencies get updated regularly:
Screenshot from 2023-03-13 18-01-38

After about 7-8 seconds, both the Downlink and Uplink radio frequencies get set to the same (Uplink) frequency and my Downlink frequency automatically shifts up. From this point onwards, my Downlink radio frequency tracks the Uplink radio frequency.
Screenshot from 2023-03-13 18-01-43

Fedora 37, gpredict 2.2.1, hamlib-4.5.4.

主要语言
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 摘要。