http://elecraft.85.s1.nabble.com/K3-and-N1MM-Logger-Configuration-Rosetta-Stone-tp2489303p2493281.html
Thanks Andy. I tried different delay settings but they did not solve the problem. But I do now have a Microham MKII I need
to install that I am sure will solve any related issues. On the otherhand....simply not setting up PTT in MM fixed the
problem too. This also may have been related to using MM with a Parallels interface on a 3.0G iMac.
>Greg,
> I noticed the same problem sending CW to the K3 using my own software,
>CQPWIN, and a Winkeyer when using the Winkeyer to assert PTT. The cure was
>adding even a small amount of Winkey keying delay (as little as 10 msec did
>the trick). So if N1MM allows you to do that, you might investigate it.
>Also, using the Winkeyer does allow one to avoid having another line for
>PTT. And with modern laptops there is an advantage that you can use it
>directly attached to a USB port without any serial port converters needed
>(the Winkey software generates a virtual serial port that the computer
>uses).
> 73, Andy, ae6y
>----- Original Message -----
>From: "Jim Brown"
[hidden email]>
>To: "Elecraft List"
[hidden email]>
>Sent: Tuesday, March 17, 2009 11:36 AM
>Subject: Re: [Elecraft] K3 and N1MM Logger Configuration Rosetta Stone
>
>
>> On Tue, 17 Mar 2009 09:55:22 -0400, Greg - AB7R wrote:
>>
>>>Hi Jim. I've notice something like timing problems or part of
>> the
>>>first character being chopped when CW AND PTT are set at the same
>>>time. If I only set either DTR or RTS to key CW and no PTT
>> action
>>>it keys perfectly.
>>
>> Thanks, Greg. Good information. The sub-programs within N1MM and
>> other logging software that sends CW is one of the weakest parts
>> of those programs, and it doesn't take much to degrade the CW. In
>> general, the faster the machine and the more memory it has
>> available, the better the CW works. The computer in my shack is a
>> five year old, 1.1 GHz Thinkpad (T22) with 512MB, and it has never
>> had a problem with CW, even with a lot of other stuff running at
>> the same time.
>>
>> Another point. As code for the K3 evolves, the guys who write the
>> radio control elements of logging software are pedaling as fast as
>> they can to keep up. There are also some differences in the way
>> the K3 does things as compared to other radios, and the guys who
>> are writing the code for the loggers aren't always aware of them.
>> As a result, there ARE some flakinesses in that part of the
>> software. All of this is gradually being worked out, as Wayne and
>> Lyle implement more features that we ask for and tweak the way
>> things operate.
>>
>> One example. One thing I LOVE about the K3 is that "normal" puts
>> CW on the same sideband on all bands, whereas most radios use LSB
>> on 40M and below, USB above 40M.
>>
>> 73,
>>
>> Jim K9YC
>>
>>
>> ______________________________________________________________
>> Elecraft mailing list
>> Home:
http://mailman.qth.net/mailman/listinfo/elecraft>> Help:
http://mailman.qth.net/mmfaq.htm>> Post:
[hidden email]','','','')">
[hidden email]
>>
>> This list hosted by:
http://www.qsl.net>> Please help support this email list:
http://www.qsl.net/donate.html
>
>______________________________________________________________
>Elecraft mailing list
>Home:
http://mailman.qth.net/mailman/listinfo/elecraft>Help:
http://mailman.qth.net/mmfaq.htm>Post:
[hidden email]','','','')">
[hidden email]
>
>This list hosted by:
http://www.qsl.net>Please help support this email list:
http://www.qsl.net/donate.html