Elecraft › [K3]

K3 and N1MM Logger

Classic

List

Threaded

8 messages Options

Chester Alderman

K3 and N1MM Logger

I just received a new factory wired K3 (s/n 4521) and I can not get the
K3/Logger to talk to each other. At this point I think the problem with the
K3 (and it's user!) but I am not sure.
Prior to setting up my K3, I had been using an IC-7700, keying with COM1 and
interfacing with COM3, so I know those ports were working. I have a home
brew keying circuit that works with various other programs, so I have no
need to key the K3 through its serial port.
What I have done is moved my keying circuit (it works fine with the K3) to
the K3 and moved my COM3 serial cable to the K3. In Logger Config, I changed
from the IC-7700 to K3, I used the recommended configuration for the K3,
i.e., 19600/N/8/1 and I have DTR and RTS set to 'Always OFF'. The CW/PTT
Port Adr is set for 3E8.
I have tried numerous other settings, N1MM recognizes it is connected to a
K3, but I get no frequency readout.
Sure would appreciate some constructive suggestions or some working
configuration settings!
Tom - W4BQF

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Mike Reublin

Re: K3 and N1MM Logger

Congrats, Tom.

Do you have the K3 baud rate set to match? CONFIG:RS232? I have N/8/2 for the other
parms.

Can you connect to the K3 using the K3 utility?

I'm a bit confused if you're having trouble with keying also, or just with the
freq/mode stuff.

73, Mike

On 8/3/2010 8:05 AM, Tommy Alderman wrote:

> I just received a new factory wired K3 (s/n 4521) and I can not get the
> K3/Logger to talk to each other. At this point I think the problem with the
> K3 (and it's user!) but I am not sure.
> Prior to setting up my K3, I had been using an IC-7700, keying with COM1 and
> interfacing with COM3, so I know those ports were working. I have a home
> brew keying circuit that works with various other programs, so I have no
> need to key the K3 through its serial port.
> What I have done is moved my keying circuit (it works fine with the K3) to
> the K3 and moved my COM3 serial cable to the K3. In Logger Config, I changed
> from the IC-7700 to K3, I used the recommended configuration for the K3,
> i.e., 19600/N/8/1 and I have DTR and RTS set to 'Always OFF'. The CW/PTT
> Port Adr is set for 3E8.
> I have tried numerous other settings, N1MM recognizes it is connected to a
> K3, but I get no frequency readout.
> Sure would appreciate some constructive suggestions or some working
> configuration settings!
> Tom - W4BQF
>
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html

Chester Alderman

Re: K3 and N1MM Logger

No Mike, the only problem I'm having is with the frequency and mode
information into N1MM. 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.

Right after updating to the beta firmware, I tested the CW QRQ and found it
to really be excellent. I went from 50 wpm up to 100 wpm in 10 wpm
increments and the keying is just excellent. The characters are perfectly
formed up to 100 wpm, but around 95 or so wpm, something like an AGC hang
occurred. But they have done a really good job with this.

Now if I can just solve the K3/N1MM communications problem I'll be all
set..hihi.

Tom - W4BQF

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Mike
Sent: Tuesday, August 03, 2010 9:52 AM
To: [hidden email]
Subject: Re: [Elecraft] K3 and N1MM Logger

Congrats, Tom.

Do you have the K3 baud rate set to match? CONFIG:RS232? I have N/8/2 for
the other
parms.

Can you connect to the K3 using the K3 utility?

I'm a bit confused if you're having trouble with keying also, or just with
the
freq/mode stuff.

73, Mike

On 8/3/2010 8:05 AM, Tommy Alderman wrote:
> I just received a new factory wired K3 (s/n 4521) and I can not get the
> K3/Logger to talk to each other. At this point I think the problem with
the
> K3 (and it's user!) but I am not sure.
> Prior to setting up my K3, I had been using an IC-7700, keying with COM1
and
> interfacing with COM3, so I know those ports were working. I have a home
> brew keying circuit that works with various other programs, so I have no
> need to key the K3 through its serial port.
> What I have done is moved my keying circuit (it works fine with the K3) to
> the K3 and moved my COM3 serial cable to the K3. In Logger Config, I
changed

> from the IC-7700 to K3, I used the recommended configuration for the K3,
> i.e., 19600/N/8/1 and I have DTR and RTS set to 'Always OFF'. The CW/PTT
> Port Adr is set for 3E8.
> I have tried numerous other settings, N1MM recognizes it is connected to a
> K3, but I get no frequency readout.
> Sure would appreciate some constructive suggestions or some working
> configuration settings!
> Tom - W4BQF
>
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[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: mailto:[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: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Bob Naumann W5OV

Re: K3 and N1MM Logger

You probably blew away the RS232 settings in the radio when you changed to
beta firmware.

Check it again.

> No Mike, the only problem I'm having is with the frequency and mode
> information into N1MM. 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.
>
> Right after updating to the beta firmware, I tested the CW QRQ and found
> it
> to really be excellent. I went from 50 wpm up to 100 wpm in 10 wpm
> increments and the keying is just excellent. The characters are perfectly
> formed up to 100 wpm, but around 95 or so wpm, something like an AGC hang
> occurred. But they have done a really good job with this.
>
> Now if I can just solve the K3/N1MM communications problem I'll be all
> set..hihi.
>
> Tom - W4BQF
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Mike
> Sent: Tuesday, August 03, 2010 9:52 AM
> To: [hidden email]
> Subject: Re: [Elecraft] K3 and N1MM Logger
>
> Congrats, Tom.
>
> Do you have the K3 baud rate set to match? CONFIG:RS232? I have N/8/2 for
> the other
> parms.
>
> Can you connect to the K3 using the K3 utility?
>
> I'm a bit confused if you're having trouble with keying also, or just with
> the
> freq/mode stuff.
>
> 73, Mike
>
> On 8/3/2010 8:05 AM, Tommy Alderman wrote:
>> I just received a new factory wired K3 (s/n 4521) and I can not get the
>> K3/Logger to talk to each other. At this point I think the problem with
> the
>> K3 (and it's user!) but I am not sure.
>> Prior to setting up my K3, I had been using an IC-7700, keying with COM1
> and
>> interfacing with COM3, so I know those ports were working. I have a home
>> brew keying circuit that works with various other programs, so I have no
>> need to key the K3 through its serial port.
>> What I have done is moved my keying circuit (it works fine with the K3)
>> to
>> the K3 and moved my COM3 serial cable to the K3. In Logger Config, I
> changed
>> from the IC-7700 to K3, I used the recommended configuration for the K3,
>> i.e., 19600/N/8/1 and I have DTR and RTS set to 'Always OFF'. The CW/PTT
>> Port Adr is set for 3E8.
>> I have tried numerous other settings, N1MM recognizes it is connected to
>> a
>> K3, but I get no frequency readout.
>> Sure would appreciate some constructive suggestions or some working
>> configuration settings!
>> Tom - W4BQF
>>
>>
>>
>> ______________________________________________________________
>> Elecraft mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/elecraft
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:[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: mailto:[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: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>

Guy, K2AV

Re: K3 and N1MM Logger

Bring up the K3 utility on your K3.

Note the settings being used by the utility. Use those for ALL
communications with the K3 over the serial port. I always use 38400.
Is there some advantage to using less?

Are you using a serial port on the computer or are you using a
serial/USB converter?

73, Guy.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Jim Brown-10

Re: K3 and N1MM Logger

In reply to this post by Chester Alderman

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:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Chester Alderman

Re: K3 and N1MM Logger

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: [hidden email]
[mailto:[hidden email]] On Behalf Of Jim Brown
Sent: Tuesday, August 03, 2010 2:16 PM
To: [hidden email]
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:[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: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Guy, K2AV

Re: K3 and N1MM Logger

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 <[hidden email]> 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: [hidden email]
> [mailto:[hidden email]] On Behalf Of Jim Brown
> Sent: Tuesday, August 03, 2010 2:16 PM
> To: [hidden email]
> 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:[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: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>