Added NewMode.txt -FT4 per Dave's instructions. Upgraded to JTAlert v2.13.4. Still no communication between WSJT-X v2.10-rc5 & JTAlert 2.13.4. I can bring up unique callsign in JTAlert pop-up but

Just another data point - FT4 with Commander and TS-590S working ok here. Config is rig split, mode none, with CAT keying. Expected transmit times were observed and my data logger shows expected

Thanks Rich. I was indeed using "Rig." I changed it to "Fake It" and I am now seeing a full TX cycle. I do wonder why such a significant delay when using Rig, but that is another discussion. I

Hi Rich, in general that is not the case. For some rigs it is true. I did not think the IC-7300 was one of those so I suspect some non-fatal configuration setting is at play. Maybe some throughput

In WSJT-X, if you have "Split Operation" set to "Rig", try changing it to "Fake It". The RX-to-TX transition with the "Rig" setting seems to be very slow when using another program (like Commander) as

FT4 with Commander working fine here Andy K3UK

I'm sure I have a configuration error in Commander that has just shown itself through testing FT4. I am configured as WSJT-X -> Commander -> IC-7300 CAT. I have been using this configuration for

+ AA6YQ comments below

More progress made here. Thanks. Continuing from the last update, those mis-placed SpotCollector.exe app files (see last note) have now been moved back into the SpotCollector Folder where they

Thank you, Dave. And thank you, Mike. This is helpful,and quite educational, especially the lengthy background explanations. I have now pruned all but the main unnumbered .exe and two of the more

On Tue, Apr 30, 2019 at 01:03 PM, Dave AA6YQ wrote: + A selector can only display "legal values". Ok, I get it now, thanks. 73, Andy, k3wyc

+ AA6YQ comments below + The QSO panel at the top of the "Log QSOs" tab of DXKeeper's Main window can be used for both logging new QSOs and for displaying the contents of logged QSOs. Since the Log

They do offer an FT8 endorsement of the main digital WAS award. So it an assumption, but seemingly likely they would add an endorsement for FT4 in the future. While not for a "for band" award, it is

On Tue, Apr 30, 2019 at 11:52 AM, Dave AA6YQ wrote: + The QSO panel at the top of the "Log QSOs" tab of DXKeeper's Main window can be used for both logging new QSOs and for displaying the contents of

+ AA6YQ comments below Dave, Does the exact mode match really matter since there is no new modes being recognized for individual bands by LOTW? When FT8 was introduced I spoke to ARRL as t when it

Dave, Does the exact mode match really matter since there is no new modes being recognized for individual bands by LOTW? When FT8 was introduced I spoke to ARRL as t when it would be added to the list

+ AA6YQ comments below EXCESS DXKEEPER FILES. Screen Shots and Notes below I'd be interested to know what others have done in the way of pruning some of the unnecessary files in

These files are a result of the upgrade process of the applications in DX Lab Suite. Which is detailed here. http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion You definitely do not need to

+ AA6YQ comments below The experimental WSJT-X version appears to work as designed. It's helpmate, JTAlert, can't decode these new transmissions but it does serve as a stable transfer medium for

EXCESS DXKEEPER FILES. Screen Shots and Notes below I'd be interested to know what others have done in the way of pruning some of the unnecessary files in C:/DXLab/DXKeeper. In line of