Hello,
I emailed BillG4WJS yesterday and explained why this happens. I have not heard
from him yet, so here is a copy of my message.
73 Alex VE3NEA
Hi Bill,
I released OmniRig 1.19 about a month ago, this version solves a few problems that I faced when I started to use WSJT-X with my
new
On 18/05/2019 14:04, Black Michael via wsjt-devel wrote:
If Alex sets the frequency or mode on the rig then either change the
internal state to reflect that or re-read the rig immediately.
Mike,
that's not how Omni-Rig works.
73
Bill
G4WJS.
I ran into a similar race condition in FLRig with set_mode and Dave fixed FLRig.
If Alex sets the frequency or mode on the rig then either change the internal
state to reflect that or re-read the rig immediately.
de Mike W9MDB
On Saturday, May 18, 2019, 7:59:43 AM CDT, Bill Somerville
I never got OmniRig to behave for me. I just tested 1.18 on my system and it
works just fine. Installed 1.19 and can't get it to behave at all.
I now use FLRig and have WSJT-X, Log4OM, FLDigi, a custom tuner utility, and
another project under development all talking to FLRig at the same time
On 18/05/2019 12:47, Mike wrote:
Now with the new 1.19, suppose the FT-450D is turned on and it's freq.
display reads 50.313.00. When I start WSJT-X using the new Omnirig it
changes the frequency to 50.313.05 on the radio display, and WSJT-X
shows it's 50.313 055. If I use WSJT-X to change
Well, that's not what he says and I have no idea, I'm just reporting the
issue. He said he'd be in touch with your developers. I just want to make
sure it's been seen. Thanks.
On Sat, May 18, 2019 at 7:27 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> If it works in
If it works in 1.16 and doesn't in 1.19 then it would seem to be OmniRig and
not WSJT-X. Alex must've broken it.
That frequency test has been in there for quite a while (a couple years
perhaps?) and nobody else has this problem. It would indicate OmniRig is
dropping the frequency change
