John, One question since you were using N1MM as well in the test. On the Modes tab in N1MM Config I checked "Always RTTY." Logging directly from WSJT-X/JTAlerts into the ARRLRTTY each Q hit the N1MM log fine. Each Q was logged as an FT8 Q. Unfortunately N1MM seems rather fussy as it gave all of the FT8 Q's zero points. Manually changing every Q from mode=FT8 to mode=RTTY solved the problem but that is obviously not a viable long term solution.
Probably an N1MMLogger+ issue but/and I am curios to know how you solved it. John K4SQC On Mon, Nov 19, 2018 at 10:32 PM John Zantek <j...@zantek.net> wrote: > Everything worked marvelously here, though I noticed the WSJT-X Contest > Log was recording local times. Moot for me since N1MM+ was doing the > primary logging/tracking mults/etc. Happy camper here; tnx so very much to > all the WSJT-X team. > > 73 John W7CD > > > > ARRLRTTY Summary Sheet > > Start Date : 2018-11-17 > > CallSign Used : W7CD > > Operator(s) : W7CD > > > > Operator Category : SINGLE-OP > > Assisted Category : ASSISTED > > Band : ALL > > Power : LOW > > Mode : DIGITAL > > Overlay Category : OVER-50 > > Default Exchange : WA > > Gridsquare : CN87PS > > ARRL Section : WWA > > Club/Team : Western Washington DX Club > > Software : N1MM Logger+ 1.0.7342.0 > > > > Band Mode QSOs Pts Sec DXC Pt/Q > > 7 FT8 42 42 20 4 1.0 > > Total Both 42 42 20 4 1.0 > > > > Score : 1,008 > > Rig : Flex 6400 w/SteppIR DB-18e > > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
