For some time I have been using WSJT -X 1.3 in conjuction with JTAlert -X 2.4 and DXKeeper very successfully.
I have now installed WSJT-X 1.6 and cannot find a way to get JTAlert and DXKeeper to play nicely with this latest version.
JTAlert-X 2.4 will start WSJT-X 1.6 and DXKeeper as before, but does not capture anything from WSJT-X 1.6 . I must be doing something wrong but no amount of head scratching can find the answer.
Stations being logged by WSJT-X 1.6 are not being "seen " by JTAlert-X. I had thought that JTAlert-X 2.4 was the latest and that JTAlert 2.6.27 is for JT65-HF, but will check it out.
On 01/01/2016 12:56, stephen_qrp@... [WSJTX] wrote:
Stations being logged by WSJT-X 1.6 are not being "seen " by JTAlert-X.
Hi Stephen,
one cause for that is having one of the cooperating applications (WSJT-X or DXKeeper) installed in "C:\Program FIles" or "C:\Program Files (x86)" or having one of the applications running with Administrator privileges.
On 01/01/2016 15:40, stephen_qrp@... [WSJTX] wrote:
Installing JTAlert 2.6.27 solved the problem.
Hi Stephen,
glad to here that, thanks for the update.
With that version you can enable the UDP messaging in WSJT-X in "Settings->Reporting" and JTAlert will use it. That also allows replies to CQ calls and QRZ calls by double clicking the alert itself in JTAlert.
