Re: [Hamlib-developer] Hamlib new version fails on YAESU FT-100 VFO handling

[Marco C. <PY...@ou...>]

*WRONG!
*
The issue is till present also in the new Hamlib!

I need to manually switch off  the split operation in my FT-100, then 
click again on the new band, otherwise VFOB keeps using the previous band!

I use mode Rig in my WSJTX Radio Settings.

Very dumb issue which was not present on the older Hamlib!

Sorry for the wrong announcement!

Regards!

Marco, PY1ZRJ

Il 13/10/25 08:19, Marco Calistri ha scritto:
> Hello!
>
> Updating to
>
> *rigctld Hamlib 4.7~git 2025-10-10T14:52:54Z SHA=23710cf2d 64-bit*
>
> Has resolved the issue I spoken about in my previous message.
>
> So far, so good!
>
> Thanks,
>
>
> ---
> *73 de Marco, PY1ZRJ (former IK5BCU)*
> **
>
>
>
> Il 30/09/25 11:57, Marco Calistri ha scritto:
>> Hello,
>>
>> Hope someone of the Hamlib group being sneaking here.
>>
>> So far my rigctld command to drive my YAESU FT-100 CAT port has 
>> worked flawlessly:
>>
>> /usr/local/bin/rigctld -m 1021 -r /dev/FT-100_USB1 -t 4532 -s 4800 
>> *--vfo* &
>>
>> This by using older Hamlib version:
>> rigctld --version: rigctld Hamlib 4.6~git 2023-07-20T21:59:57Z 
>> SHA=aacf06 64-bit
>>
>> Now, using the new Hamlib version:
>>
>> rigctld --version: rigctld Hamlib 4.7~git 2025-09-27T16:16:32Z 
>> SHA=0d122f6b1 64-bit
>>
>> One of the VFO stays on previous frequency when I switch band.
>>
>> For example: I start working on 10 meters band then VFOA tunes on 
>> 28.074 and VFOB tunes on the same frequency minus or plus the audio 
>> shift.
>>
>> When I switch band, for example to 17 meters, VFOA sets on 18.100, 
>> whereas VFOB stays on 28.074!
>>
>> This is a really annoying behavior!
>>
>> I tried also without adding the *--vfo* parameter at rigctld without 
>> success and obtaining a worst and slower switching from TX to RX.
>>
>> Thanks for any inputs you could provide.
>>
>> Marco, PY1ZRJ
>> ---
>> *73 de Marco, PY1ZRJ (former IK5BCU)*
>> **
>
>


---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**