Page 1 of 1

[SOLVED] V 2.12.0 not put frecuency in log from CAT with HAMLIB

Posted: 01 Apr 2021, 21:10
by lu4hne
Download the latest version and now it allows you to see the 2 vfo but when registering a contact it does not copy the frequency in the log
frecuencia 2.11.png
frecuencia 2.11.png (18.19 KiB) Viewed 3189 times
In version 2.12 it correctly shows both vfo but it does not copy the value in the contact, even when saving it does not copy the value either.
disable
frecuencia 2.12.png
frecuencia 2.12.png (23.48 KiB) Viewed 3189 times
My Rig is FT-890

this option new "VFO mode" parameter no make change if enable or disable

Re: V 2.12.0 not put frecuency in log from CAT with HAMLIB

Posted: 01 Apr 2021, 23:33
by KI5IO
OM,

Have you tried the same routines while using OmniRig for CAT control?

That would provide additional trouble shooting details.

Re: V 2.12.0 not put frecuency in log from CAT with HAMLIB

Posted: 02 Apr 2021, 20:41
by lu4hne
Thanks for answering, unfortunately with omnirig my yaesu ft-890 does not work, only with hamlib I have been able to use CAT

Re: V 2.12.0 not put frecuency in log from CAT with HAMLIB

Posted: 02 Apr 2021, 21:41
by KI5IO
lu4hne wrote: 02 Apr 2021, 20:41 Thanks for answering, unfortunately with omnirig my yaesu ft-890 does not work, only with hamlib I have been able to use CAT
Max,

I seem to recall that other OMs have expressed similar and were able to get OmniRig working using a different FT 'ini' file, but don't recall which one. Doing some searches here on the forum might provide those prior threads.

FWIW - we're also currently testing a new Hamlib version that should address the frequency issue. Can't give you a date for that release, but may not be a very long wait.

Re: V 2.12.0 not put frecuency in log from CAT with HAMLIB

Posted: 02 Apr 2021, 22:00
by lu4hne
Thanks Nolan for your answer, I will keep trying with an omnirig configuration while correcting hamlib, I prefer it

Re: [SOLVED] V 2.12.0 not put frecuency in log from CAT with HAMLIB

Posted: 06 May 2021, 20:58
by lu4hne
Solved in version 2.13.
Thanks