[upl-image-preview uuid=0442c3af-768d-4177-870d-5c7d8752202c url=https://storage.hamcq.cn/2024-12-29/1735475027-431746-image.png alt={TEXT?}] 如上图设备：icom705 连接软件：Icom Remote Utility 问题发生情况：在打开JTDX软件正常通联时，使用大波轮改变频率，或改变电台设置时，100%触发以上图片情况，另有概率触发以下情况[upl-image-preview uuid=9ff77c20-cef4-4ae3-986e-97991c71fcec url=https://storage.hamcq.cn/2024-12-29/1735475205-277746-image.png alt={TEXT?}] 设备使用FT8通联时，设置在VFO模式，（非memo及call模式）求助各位705用户，如何解决以上问题

个人认为是频率变化导致驻波变化结论是：磁环多加一些在控制线和馈线上

@"BH3XZT"#p47954 705是这样的就是容易被打掉usb

对了我需要补充一下，为了避免USB连接的不稳定（被打断）我的ic705与电脑连接的方式为：WIFI（使用Icom Remote Utility实现的）

@"BH3XZT"#p48611 但仍然出现了上述问题

有没有多试几个版本的JTDX或者换WSJT-X看看如何？没准是Hamlib.dll的版本问题。

或者试试把里面有两个需要hamlib的选项禁用

电台要接地线！我接了再也没有过，没接前隔几天就这样。

疑似找到问题的解决方案了[upl-image-preview uuid=03ec997e-9cf8-406a-a196-cd6780e63f15 url=https://storage.hamcq.cn/2025-06-17/1750180265-65486-image.png alt={TEXT?}] 经过尝试，好像不报错了

Have you all experienced this situation when using FT8?

BH3XZT

As shown in the above figure.
Equipment: icom705
Connection software: Icom Remote Utility
Problem occurrence: When using a large wheel to change frequencies or modify radio settings while the JTDX software is normally connected, the following images are triggered 100% of the time, and there is also a probability of triggering the following situations:
When using FT8 communication, set the device to VFO mode (not memo or call mode).
Help from all 705 users: How to solve the above problems?

ba4qdi

BH3XZT 705 works like this: it's easily disrupted by USB.

BI4OAE

Personally, I believe that changes in frequency are responsible for the observed variations in standing waves.
The conclusion is that more magnetic rings should be added to the control line and feed lines.

BH3XZT

By the way, I need to add that in order to avoid USB connection instability (disconnections), my IC-705 is connected to the computer via Wi-Fi (using the Icom Remote Utility).

BH3XZT

BH3XZT However, the aforementioned issues still persisted.

Liridice

Have you tried using different versions of JTDX or switching to WSJT-X to see if that resolves the issue? It might be a problem with the Hamlib.dll version.

BG8LOK

Alternatively, try disabling the two options that require hamlib.

BH3XZT

It appears we have found a potential solution to the problem.
After trying, it seems like there are no more errors.

闽ICP备2021006864号-7

闽公网安备35020602002794号互联网举报中心

用户协议隐私政策社区规范积分规则中继规则转载须知
更新日志联系我们常见问题友情链接运营报告赞助

浩奇科技（厦门）有限公司

是无线电，把我们联系在一起