[Elecraft] K3 - interfacing to N1MM Contest Logging software

[Don Wilhelm]

Barry,

I believe you are correct in your "if it ain't broke, don't fix it" 
stance.  Keep on keeping on!

However there are two things to be aware of in case of trouble down the 
road.
1).Usually, USB to serial adapters work better at high speeds than low - 
that is counterintuitive, but true.
2).For asynchronous RS232 protocol, the number of stop bits stated is a 
minimum number.  With a properly functioning device at both ends, 
increasing the number of stop bits should do nothing.  The state of the 
'stop bit' is the same as the idle state - that means when 
communication  pauses, the result is electrically the same as a large 
number of stop bits.

I believe your ESC key 'problem' may be a matter of definition.  Keying 
via DTR is not  "keying via the radio communications port" by my 
definitions.   I would interpret that statement in the K1MM 
documentation to mean keying by a technique similar to the K2/K3 "KY 
command" (which uses the TXD/RXD communication lines).  Yes, the DTR 
signal is a part of the RS-232 interface, but is is a signalling 
(control) line and not a "communications" line - TXD and RXD are the 
'communications' lines.  Others can tell you if my interpretation is 
correct in light of the K1MM implementation (I don't know that answer), 
but I know the terminology I used is correct for RS-232 communications.

73,
Don W3FPR

Barry Pfeil wrote:
> After a bit of frustration with poor documentation, I've got my laptop connected to my new K3 using the Elecraft KUSB USB to Serial Adapter.  I was pleased to find a "K3" option in the N1MM Configurer but I have a few questions.
>
> ESCape key - In the configurer, N1MM says that "ESC will not interrupt CW keying via the radio communications port".  But I'm using the DTR line on the single RS232 interface for keying and ESC seems to instantly stop any "F" key-initiated sending.  Am I missing something?
>
> Stop bits - I apologize for my naivete on this, but N1MM sets the stop bits at 2 while also noting that Elecraft recommends 1 stop bit.  Anybody know why?  Should I change it to 1 stop bit?  It works fine as is (2 stop bits) so I'm basically in the "if it ain't broke, don't fix it" mode.
>
> Speed - N1MM sets the speed at 4800 baud and also notes that "Elecraft recommends 4800-38,400 baud".  The Elecraft KUSB adapter set itself initially at 9600 baud.  Any insights here?  Again, I'm in "don't fix it..." mode
>   
>