Hi Dave, Ok, I just assumed wsjtx & js8call were using a later version. I guess it's it a different fork, or customized, one that has OmniRig listed as "rigs" in it. Perhaps pictures will help. wsjtx

I’ve not used “rig” split mode for a while. I’ll look to see if the problem is still there. Phil GM3ZZA Sent from Mail for Windows 10

What version of WSJT-X are you running? I'm running 2.3.0-rc2 and VFOB follow VFOA when doing band changes on WSJT-X. Mike W9MDB

The latest hamlib snapshot is: hamlib-4.1~git-bfdce275-20201120.tar.gz fldigi version 4.1.16.03 is linked to this version of hamlib

Thanks! :-) Only today I realized I haven't updated fldigi for some time and now it has a tree structure in configuration. In the new version (4.1.16 I think) it is much easier to find these

hamlib 4~ on github is a moving target. I consider it the tertiary transceiver control for fldigi. I update the source for building the Windows exe about once a month or when

Hi and thanks very much for the detailed response. I've been asking these questions about fldigi primarily because my radio is getting "PTT" activated without explanation. This was occurring every

OmniRig is not in hamlib...it's in WSJT-X as an add-on to the hamlib rigs as is HRD. I will be trying to add to hamlib though.l What should work is using FLRig -- FLDigi talks to it -- Hamlib talks

Howdy David, I have the same problem when running any program with OmniRig while running flrig, or fldigi with RigCat, with both connected to a VPSE virtual serial port tee. Frequency jumps around

Icom's lack of VFO addressing and even finding out the active VFO are the bane of my existence. Most every other rig in the universe can at least find out the active VFO. Most can set VFOB without

I’ve looked in the IC-7300 CAT Command list and there is no immediately obvious way to read VFO-B frequency without selecting VFO-B. 73 Phil GM3ZZA. Sent from Mail for Windows 10

I’ve seen the problem with WSJT-X/Flrig/IC-7300 with WSJT-X using rig mode for “split”. If I change bands VFO-B in the rig on the previous band, whereas flrig and WSJT-X move to the new band. I

Good suggestion. David, W1HKJ fldigi developer On 11/20/20 1:41 AM, ok4rm wrote:

Hello, configuring fldigi was a frustrating experience for me at times. What I found especially annoying was the impossibility the change confirmation behavior in "waterfall-only" mode launched by

Hello, Rich, found the file. Surprisingly, there is only one instance (in C:\Users\{myusername}). This config file is effective for standalone run of fldigi. What happens in N1MM logger+ seems to be a

BTW, if the log state is saved on shutdown, anyway, why not make "no confirm" the default? Another idea: although I am not familiar with the whole set of XML-RPC commands, I think *if* there is

On Thu, Nov 19, 2020 at 09:37 PM, ve3ki wrote: https://n1mmwp.hamdocs.com/manual-operating/digital-modes/#fldigi-initial-configurationThank you very much, Rich. I consider N1MM logger a little bit

I apologize, it's really frustrating... Jindra

Recently I used FLDIGI in conjunction with N3FJP for the WAE RTTY contest. I selected Generic contest and all worked fine. However, when I went to write the Cabrillo file, I noticed that many of the

Dave, This is normal behavior as Flrig reads the radio’s parameters to save them and restore them as you exit. It will do it every time. 73, Cliff, AE5ZA