Re: [wsjt-devel] v2.8.0 improved with OmniRig

[Uwe, D. <dg...@gm...>]

Hi Andy,

I have just systematically tested it again. My FT-991 runs with v2.8.0 
perfectly with OmniRig. Both with Mode=None and with Mode=USB as well as 
with Mode=Data/Pkt. And all these variants with both Split Operation Rig 
and Fake it. Not a single issue! Just like with the previous 2.7.1-devel 
versions.

This means that your OmniRig issue must be related specifically to your 
rig or to your setup in general.

But you know that you can easily edit any OmniRig driver yourself, don't 
you? I would advise you to do this next. The drivers are at C:\Program 
Files (x86)\Afreet\OmniRig\Rigs. See what commands are in there and 
adjust them if necessary so that you get what your rig needs. With my 
very slow Malachite SDR receiver, I also got it to work with OmniRig 
that way. I had used it until Mike W9MDB wrote a Hamlib driver for the 
Malachite SDR RX and we both optimized it together so that it worked 
even better than with OmniRig in the end.

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB


Am 19.04.2025 um 18:20 schrieb Andy Durbin via wsjt-devel:
> "2.8.0 improved, when used with OnmiRig, does not control rig 
> frequency when Mode = None.  It does control rig frequency when Mode = 
> USB."
>
> A bit more experimenting with 2.8.0. showed MODE=USB was a necessary 
> but not sufficient condition.  Rig control only seemed to work if 
> Split operation was changed too.
>
> E.g.
>
> Start with Mode None, Split Rig - frequency control inop
> Set Mode USB - frequency control inop
> Set Split Fake it - Rig RX VFO responds. TX VFO unchanged
> Set Split Rig - Frequency control ok
> Set Mode none - Frequency control inop
> Set Mode USB - Frequency control inop
> Set Split none - Rig RX VFO responds. TX VFO unchanged
> Set Split Rig - frequency control ok
>
> This is only part of the problem.  The fact that the WSJT-X dial 
> frequency does change means the WSJT-X frequency display is not always 
> rig dial frequency but is sometimes the commanded dial frequency.
>
> Shouldn't WSJT-X dial frequency always be the frequency reported by 
> the rig and have some alert if rig frequency is not equal to commanded 
> frequency?
>
> 73,
> Andy, k3wyc
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel