On 07/01/2019 15:10, Bob VanFossen wrote:
Thanks, Bill.
I missed the checkbox on the Broadcast! Just added it and re-logged
a contact and it populated N1MM correctly.
I had planned to run both FT8 and RTTY in the contest, but after the
log failure with N1MM, I abandoned the RTTY part.
Thanks again for the quick response. Looking forward to FD and FT8.
Bob, K4DJG
Hi Bob,
with that configuration you must either not run JTAlert or change the
UDP port it uses to relay WSJT-X UDP traffic to N1MM Logger+ because
without doing so you will get duplicate log entries for FT8 QSOs in N1MM
Logger+. BTW the reason JTAlert was not logging correctly was that you
were not using the latest version.
IMHO the current best solution for using FT8 *and* RTTY in an ARRL RTTY
Roundup style contest is to use just WSJT-X and N1MM Logger+. The new
WSJT-X decodes window in N1MM allows you to see both dupes and
multipliers calculated from the cumulative RTTY and FT8 log in N1MM.
Usage is still a bit clunky when switching modes as only one application
can control your rig since N1MM doesn't support any of the rig sharing
options that WSJT-X uses. There are documented (by others) some
workarounds for certain rigs etc., otherwise you can disable CAT in the
application that is not currently using the rig.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
