SmartSDR backend: PTT-on intermittently fails with “another slice has PTT control” (Hamlib 4.7.2)
维护者通常 5 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by locating the SmartSDR backend’s PTT handling and the code that reports “another slice has PTT control”; the issue does not name source files or tests. Compare the slice and PTT state handling on successful and failed T 1 requests, using the attached rigctld debug log as a starting point. Done means repeated PTT-on and PTT-off commands targeting the same slice behave consistently without the reported rejection.
由索引模型根据 Issue 内容生成。
描述
Environment
- Hamlib version: 4.7.2 (build 2026-06-21, SHA
40f63488f) - Rig model: FlexRadio SmartSDR Slice A (model 23005)
- Connection:
rigctldconnected to the radio at192.168.197.161:4992 - rigctld listening on port
4532
Problem
PTT-on commands (T 1) behave inconsistently. Some succeed, but others fail with RPRT -12 and the debug message:
smartsdr_set_ptt: abort PTT on slice ?, another slice has PTT control
The subsequent PTT-off command (T 0) succeeds.
Log evidence
On successful PTT-on, the backend sends commands including:
dax audio set 1 tx=1slice set 0 tx=1xmit 1
and returns RPRT 0.
On a failed PTT-on request, the backend returns RPRT -12 (“Target VFO unaccessible”) before sending xmit 1 to the radio. The following T 0 command succeeds.
Expected behavior
Repeated PTT-on / PTT-off commands should behave consistently, without intermittent rejection by the SmartSDR backend when targeting the same slice.
Actual behavior
PTT-on sometimes succeeds and sometimes fails with the backend reporting that another slice has PTT control.
Attachments
Full rigctld debug log available.
Could this be caused by incorrect slice/PTT state tracking in the SmartSDR backend, or by the backend detecting PTT ownership on another slice incorrectly?
. . .
Cheers Uli, DF4IAH.
- 主要语言
- C
- 星标
- 851
- 派生
- 308
- 平均合并
- 3 天 20 小时
- 30 天内合并 PR
- 8
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Hamlib/Hamlib 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 5 天内回复
-
Enhancement
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 5 天内回复
-
难度 2/5 1-3 小时 新手友好度 90/100
维护者通常 5 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 5 天内回复
-
难度 4/5 1-2 天 新手友好度 57/100
维护者通常 5 天内回复
相似的 Issue
-
category:port-update
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 2 天内回复
-
emerge failure MARK mark-unstable media-kit
难度 2/5 1-3 小时 新手友好度 82/100
macaroni-os/mark-issues#834 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
NVIDIA/open-gpu-kernel-modules#1479 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 1/5 1 小时以内 新手友好度 93/100
webarkit/WebARKitLib#107 ·
维护者通常 1 天内回复