On 10/05/2020 15:56, Steve Wilson via groups.io wrote:

I know that N3FJP can be interfaced to WSJT-X via JTAlert, but I'd like to toss out my vote for a direct interface. :-)

73!

Steve  K6WW

Hi Steve,

the WSJT-X development team is small and focused on weak signal communications modes, we have no wish to implement and support numerous different interfaces to the plethora of QSO logging applications. That would be an unnecessary drain on our resources, particularly where those applications do not run on all the platforms that WSJT-X is supported on. Instead we provide a documented protocol that other applications can interoperate with, that protocol provides more than just logged QSO details, it also provides near real-time information of decodes printed, and the status of the WSJT-X user interface. It also provides messages for external applications to initiate QSOs, highlight text in the WSJT-X Band Activity window, and change some user interface controls in WSJT-X. The protocol, when implemented properly, also allows multiple applications to interoperate with any number of WSJT-X instances, all running concurrently.

Where the authors of logging, or other third party applications, do not have the inclination or resources to implement the WSJT-X UDP Message Protocol then there is space for other developers to implement bridging applications to fill that gap. An excellent example of that, although not the only one, is the JTAlert application by Laurie, VK3AMA. So that begs the question: what is wrong with the use of JTAlert to bridge between WSJT-X and AC Log, and have you asked Laurie if such deficiencies can be addressed within JTAlert?

73
Bill
G4WJS.