Hi Marko If you want to be sure that the Hamlib developers are informed, it may be best to contact them directly.
Contact information for them is given in WSJT-X's Help menu 'How to deal with rig control errors' 73 Charlie DL3WDG On Mon, 29 Sept 2025 at 23:17, Marco Calistri via wsjt-devel < [email protected]> wrote: > 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) * > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
