Re: K3 RTTY issues with N1MM+
toggle quoted messageShow quoted text
wonder if the other computer – on AFSK had VOX on
or which route the PTT was wired with different test rigs
for K3, you might resolve using the “Comm PTT” on Ports setup page
Not my favorite but worth testing (That’s a writelog screen – assume N1MM has similar)
PI4C, PI4CO and PI4COM are all found in the recent RBN link given on web page
Recall doing repeat as was copying different callsigns with and without “M”
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Ronald PA3EWP
Sent: Saturday, October 03, 2020 4:35 AM
Subject: [Elecraft-K3] K3 RTTY issues with N1MM+
During the RTTY contest last weekend we noticed a problem that our transmitted text was abrupted.
A lot of times our call was transmitted as PI4C or PI4CO instead of PI4COM.
We used the latest version of N1MM+, MMTTY, Microkeyer MK2 and a Elecraft K3.
N1MM was configured as SO2V.
If I looked at the digital interface window the text was transmitted, at the end the software disabled the PTT of the radio.
But the radio was still busy transmitting the text, the FSK led was still flashing, but the software disabled the PTT.
I try to find what was happening or was changed, but I couldn’t find any solution for it.
So we changed it to AFSK and all worked fine again.
If I started MMTTY without N1MM it worked fine.
I checked it at after the contest and I come to the following conclusion:
The same computer setup with another K3 radio, other Microkeyer interface => same results.
Same computer setup with TS990, no problem
Other computer setup with the same K3, same problem.
I asked a friend to test his K3 and he has the same issue.
I hope someone has a solution for it, I am sure it must be something simple, but I can’t find it.
Contestgroup Oude Maas
30th anniversary callsign: PI30COM