Hi Bill, I didn't think that could be the case since I have JTAlert set up to log to ACLog. And it logged those test QSOs correctly to ACLog. However, JTAlert has a thing called Last QSO API that is always on and does log to the same (by default) port N1MM was looking for. So that's why the QSOs were being logged twice. So, I can change port numbers or not use the WSJTX logging feature. Thank you for pointing this out! 73, Carey, WB4HXE
On Tue, Dec 18, 2018 at 10:23 PM Bill Somerville <[email protected]> wrote: > On 19/12/2018 03:14, Carey Fisher wrote: > > I think I've set everything up correctly. Any ideas why this is happening? > > Hi Carey, > > you probably have JTAlert running and have its option to relay logged QSOs > to NiMM Logger+ enabled as well as that in WSJT-X. The route directly from > WSJT-X is recommended as I believe the route via JTAlert may not transfer > the required contest exchange details. This last point may not be correct > any more as the UDP messages from WSJT-X that JTAlert uses have been > recently updated along with changes in JTAlert to interpret them. I suggest > you experiment but whichever route you choose you must only have one > enabled. > > 73 > Bill > G4WJS. > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- Carey Fisher [email protected]
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
