Re: K3 intermittently forgets to transmit even though FT8 has gone into TX mode
Although I have not had the specific problem that started this thread I have been having continuing problems with WSJT-X and N1MM playing together with my SO2R K3 setup. Many times when I switch bands or modes I have to exit N1MM and kill an orphan copy of WSJT-X with the Task Manager. Usually this is proceeded by the failure of N1MM to communicate with the K3 that I changed bands or modes on from N1MM. N1MM by itself works flawlessly without a WSJT-X window open. If I just use two WSJT-X windows and only use N1MM as the logger it works also. Mix WSJT-X and another mode and it goes in the dumper. Maybe this is the way it’s designed by necessity. I thought it worked before with mixed modes but maybe not.
From: Rick Ellison
Sent: Thursday, October 10, 2019 10:50 AM
Subject: Re: [N1MM+] K3 intermittently forgets to transmit even though FT8 has gone into TX mode
Are you using the latest version?? There were some recent changes made to the way the TCP connections is done and I had a couple of K3 users testing it out to make sure it corrected their issues of the radio dropping out. I have nothing but good things from them saying the radio connection is rock solid with their K3 setup. I’m hoping one of them will chime in here and tell you what their settings are so you can get thru this issue. I don’t own a K3 so I relied on what they were telling me.
73 Rick N2AMG
N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of
B. Smith via Groups.Io
N1MM uses DXCommander in name only, so, although this suggestion may help, it can't be done.