I think it is a good idea to check for open spectrum more frequently in F&H, esp as all the calling stations are in a narrower passband than for typical ops.... /K1BZ

Bill, Good point. I guess I was in the habit of looking at the colors of WSJT before I installed JTAlert. I just turned off the WSJT internal highlighting so the colors in JTAert alert

Tony, you can substitute the WSJT-X ADIF log file with one of your choice, but as I said, you will not necessarily get the same results as WSJT-X does not tale account of

Bill, Thanks for the info. Is it possible to update the WSJT's log file with the same ADIF file I used to update JTAlert? N2TK, Tony

On 23/11/2020 04:22, Reino Talarmo wrote: Hi Tom, Mark, and Reino, with an all digital Tx audio chain not using one of the WSJT-X split modes may be OK but I would agree with

YES! last update removed all of my sounds systems and driver and disabled the desk top speaker. Took all day to get everything reinstalled and working with the right driver down loads. Thanks MS for

With a Flex you don't need to use Fake It or Split. Both on RX and TX you can open your filter width and TX band width really wide. I run my Flex with a TX band width of 8k, When using DIGU mode

make sure your tqsl program is up to date Dave Garber VE3WEJ / VE3IE

Tom, If 'Fake it' is working use it. The User Guide in 4.2. Radio recommends: Either method will result in a cleaner transmitted signal, by keeping the Tx audio always in the range 1500 to 2000 Hz so

Looks like I got DXKeeper working with jralert. But now when I try to upload a qso to Lotw it rejects FT8 modes. Need to figure out to correct that problem

+ AA6YQ comments below Have been trying to figure out if I can connect DX Keeper, WSJT-x and my 991A together. Do I have to have the Commander running, since it is being very difficult to connect to

Hi Hank, Yes, "normal" - one of those very annoying "features" of wsjt-x; supposedly to "prevent it from becoming an automatic QSO machine". 73 - John - N7GHZ

Normal operation for Fox/Hound... It’s in the manual. Bill WB6JJJ

Have my transmit watchdog set for 10 minutes, and it normally works that way just fine. Tonight I was calling 7Q7RU who was using fox/hound, but watchdog was cutting me off after only 2 minute

Hi Tony, WSJT-X works only with its own ADIF log file. It has no knowledge or concept of a confirmed QSO. It only deals in worked or not worked. Because of that you should be seeing less highlighting

I am using both JTAlert and WSJT-X vers 2.2.2. With JTAlert I have the following checked My call in message Wanted DXCC Wanted CQ Zone. No issues with JTAlert. I get the correct colors when DX called

Has anyone noted S and P does not enable tx when used in the latest versions (rc1 and rc2) in v2.3.0? Works fine in 2.2.2 for me. I know it is primarily for contesting in FT4, but I use it with FT4,

Mike and Neil, this is rather biased advice. Although JTAlert is a great companion to WSJT-X, it is not necessarily the only way to log WSJT-X QSOs in DXKeeper. I would recommend getting Commander

To use DXKeeper with WSJT-X for logging, you need an intermediate bridge program. You can use JT-Alert (which has very good DXKeeper integration), GridTracker, or SpotCollector from the

Have been trying to figure out if I can connect DX Keeper, WSJT-x and my 991A together. Do I have to have the Commander running, since it is being very difficult to connect to the radio and I am about