[WT-support] Problem with CAT of the Yaesu FTX-1 (works partially)

[Bob Wilson, N6TV]

After studying the FTX-1 CAT manual, the reason Win-Test can't display the
VFO frequency problem is now clear:  Yaesu has (once again) created a major
compatibility headache, by changing the format of the data returned in
response to a critical CAT command (IF;)

In this case, Win-Test is polling the Yaesu rigs with an "IF;" command to
get the VFO frequency.  But instead of the VFO A frequency being found at
byte 6, where it is located in every other current Yaesu rig, the VFO
frequency is now found at byte 8.

This change means the FTX-1 is going to be incompatible with lots of
existing software.  Devices that track the rig's frequency using IF;
commands such as SteppIR Controllers, and linear amplifiers from ACOM, SPE,
and Yaesu, could also have problems.

I've just created a new OmniRig .ini file that should allow Win-Test (and
other software) to work with the FTX-1, but I have no way to test it, so I
would really appreciate it if you or anyone else with an FTX-1 could try it.

   1. Download, extract, and and install OmniRig from
   http://dxatlas.com/OmniRig/Files/OmniRig.zip
   2. Download the following file:  https://www.kkn.net/~n6tv/FTX1ini.zip
   3. Extract the FTX-1.ini file from the FTX1ini.zip file, and copy the
   .ini file to C:\Program Files (x86)\Afreet\OmniRig\Rigs\  (Administrator
   privileges required)
   4. Start the OmniRig configuration program, set Radio Type to FTX-1,
   COM4:, 38400, 8, None, 1, Low, Low, Poll 400 ms, Timeout 1000 ms (baud rate
   much match Yaesu CAT-1 Baud Rate)
   5. Click OK and start Win-Test
   6. Type SETUP [Enter] in the Win-Test logging window
   7. Do not mark any COM port as Radio 1 (no check marks on COM4)
   8. At the bottom, Set Radio 1 to OmniRig
   9. Click OK

If the test works OK, I will send the FTX-1.ini file to VE3NEA for
distribution in his RigIni.zip file.  Later perhaps Laurent will be able to
add FTX-1 support so you won't need to use OmniRig.

73,
Bob, N6TV


On Sat, Dec 13, 2025 at 5:58 PM Bob Wilson, N6TV <n6tv at arrl.net> wrote:

> Change Yaesu FTX-1 Menu OPERATION SETTING > GENERAL > CAT1 TIMEOUT TIMER
> to 3000 ms (default 10 ms will not work).
>
> Try changing Win-Test Radio type FT-dx101.  Make sure Radio Poll is
> enabled in Win-Test SETUP.  38400 baud.  Do not leave RTS=Handshake, RS-232
> handshake is not supported by this rig.  Set DTR=CW, RTS=CW if you like, or
> set both th Always OFF.  Or you can use CW SETTING > MODE CW > PC KEYING >
> DTR if you set DTR=CW.
>
> Most of the LUA scripts should work OK.
>
> Be sure you are using the "Enhanced" COM Port listed in Windows Device
> Manager, not the "Standard" COM port (USB cable creates two ports).
>
> 73,
> Bob, N6TV
>
>
> On Sat, Dec 13, 2025 at 12:19 PM IZ4MJP Franco <franco at iz4mjp.com> wrote:
>
>> Today I was configuring a Yaesu FTX-1 Optima purchased from a club I'm a
>> member of.
>> The CAT works correctly with DXLab, QARTest, WSJTX, MSHV, MixW, etc., but
>> with WinTest partially works.
>>
>> To get it to "work partially" I had to select an FT-991 from the
>> drop-down menu, as neither the FTX-1 nor the 710 were present.
>> Once connected, the CAT allows me to change bands using the - key
>> combination, but the frequency indicator does NOT follow the radio's VFO.
>>
>> In the Band Map of Radio 1, I can click on a spot, the radio tunes to the
>> correct frequency, and the display also indicates it correctly.
>>
>> If I move the VFO, however, nothing happens.
>> The installed version is 4.57 (but I also tried 4.58 dev).
>>
>> Among other tests, I changed both the RS-232 port speed and the radio
>> model (FT-5000, FT 891, etc.), but the result was the same.
>>
>> Has anyone else encountered the same problem?
>>
>> I'm also wondering if the LUA script "YaesuScripts.zip" developed by N6TV
>> can be installed to manage the FTX-1's internal DVK or CW transmission.
>>
>> Thanks for any suggestions.
>>
>> 73, IZ4MJP Franco
>>
>>
>>
>> --
>> support mailing list
>> support at win-test.com
>> https://lists.win-test.com/cgi-bin/mailman/listinfo/support
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.win-test.com/pipermail/support/attachments/20251215/687fdfcc/attachment.htm>