[WT-support] Icom IC-9700 under Linux/Wine

Bob Wilson, N6TV n6tv at arrl.net
Wed Mar 18 04:09:06 CET 2026


I would also put VFO B of the 9700 on the SAME BAND (it may be on some UHF
band?) Win-Test may struggle to display that properly.

73,
Bob, N6TV


On Tue, Mar 17, 2026 at 3:06 PM Bob Wilson, N6TV <n6tv at arrl.net> wrote:

> On Tue, Mar 17, 2026 at 2:19 PM Jens Wagner <jens.wagner767 at gmail.com>
> wrote:
>
>> we do not use Omnirig. We are using the native Win-Test implementation.
>> And in addition to Ralf I must consider that the problem occures on Windows
>> too.
>>
>
> My point was that any *other* program, not Win-Test could have set the
> CI-V Transceive OFF at some point, long ago, which will cause problems.
>
> Win-Test usually tracks all Icom rigs VERY well with polling DISABLED, but
> chances are there are one or more Icom menu settings still set to the
> IC-9700 factory defaults, so that could be the only thing you have to check
> to fix everything.
>
> Please check all of the following items in the IC-9700 menu:
>
> SET > Connectors > CI-V:
>
> CI-V Baud Rate:  19200 (do NOT use the factory default, AUTO)
> CI-V Address:  A2h
> CI-V Transceive:  ON
> CI-V USB Port: Unlink from [REMOTE]
> CI-V USB Baud Rate:  19200 (to NOT use the factory default, AUTO)
> CI-V USB Echo Back:  ON (do NOT use the factory default, OFF)
>
> The problem seems to belong to the CAT handling in the 9700.
>>
>
> I don't think so.  The same common code is used by Win-Test for almost
> every Icom rig.  The only thing that changes is the CI-V Address plus a few
> settings to read VFO B.  The IC-705 is much newer than the IC-9700 so
> perhaps AUTO mode works better there?  There's no reason to use it instead
> of specifying the specific matching baud rate.
>
> 73,
> Bob, N6TFV
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.win-test.com/pipermail/support/attachments/20260317/75db5e0e/attachment.htm>


More information about the support mailing list