[Elecraft] K3 and N1MM Logger

[Guy Olinger K2AV]

First of all, if you can talk to your K3 via your PC using the
utility, the problem is NOT in the K3.  Are you using the same
computer to run the K3 utility as you are when running N1MM with the
K3?

Is there anything else on the RS232 line besides the PC and MM.  If
so, disconnect it.

Is there any other program that looks at the same com port.  If so
shut it down.  Does that program have a boot-up driver that runs all
the time, then stop it.  Try again.

I'd guess half of K3 owners are on 4.03, and it has been out for quite
a while.  If there was an endemic RS232 problem it would have been
howled out of existence a while ago.

I note that you are setting memory locations. I think that is a real
risk with Win 7 (I have Win 7 pro, using 4.03, a REAL serial port on a
PCI-X serial card using one of three extra video slots that will never
be used otherwise, and I let the OS configure memory locations and
IRQ's (I don't understand your comment about Win 7 not supporting
"real" serial ports -- that's simply not true, it's running here.)  I
have the hardware drivers for the serial card set up to claim COM1 and
COM2.  These are on board and operational at boot up, not when
something is plugged in, which will always be a problem for USB
configure at USB plug-in-time.

73, Guy.

On Tue, Aug 3, 2010 at 2:32 PM, Tommy Alderman <aldermant at windstream.net> wrote:
> Thanks Jim, but that is NOT the problem. I have had both the serial port and
> K3's RS232 set to both 19200 b and also 38400 b and get the same results.
>
> I initially had the problem because my serial port was set to 19200 b and my
> K3's RS232 was set for the default of 4800 b. After I changed RS232 to 19200
> b, the K3 and N1MM communicated excellent. AFTER updating the K3 firmware to
> 4.03, again, the K3 and N1MM would not communicate.
>
> I am in the process of reverting the K3 firmware back to 3.xx.
>
> Thanks Jim and 73,
>
> Tom - W4BQF
>
>
> -----Original Message-----
> From: elecraft-bounces at mailman.qth.net
> [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Jim Brown
> Sent: Tuesday, August 03, 2010 2:16 PM
> To: elecraft at mailman.qth.net
> Subject: Re: [Elecraft] K3 and N1MM Logger
>
> On Tue, 3 Aug 2010 12:28:54 -0400, Tommy Alderman wrote:
>
>> It was working just fine right after I reset the
>>RS242 to the correct (19200 b) baud rate; then I updated to the beta 4.03
>>firmware and now it does not talk to N1MM again.
>
> That's the problem. You must set BOTH the K3 and N1MM to the SAME baud rate.
>
> Changing it is what made it spit up. Like Guy, I use 38,400. Slower speeds
> also work.
>
> 73, Jim K9YC
>
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> 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: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>