K3 stopped communicating with N3FJP log program and Elecraft Utility

[Tom & Barb Valosin]

Hello all - I am at a loss. First off - I am definitely not a computer
X-pert, just a program user. (Not an Expert in anything - X is
mathematical coefficient for the unknown and a spurt is a drip under
pressure. Therefore, I am NOT an expert. Well, it was funny when the
high school math teacher said it back in 8th grade>)

I purchased a previously loved K3, S/N 4734 from Rich, W2EG in Sept
2016. He upgraded to the "latest and greatest" version of the K3. Before
he would allow me to actually pay for the rig he wanted to be sure all
was up to snuff so he sent it to factory to get a top to bottom check
out by Keith, WE6R. Keith made some upgrades and pronounced it "meets or
exceeds all specifications". Nice thing here - Rich did not add the cost
into my purchase price. (If he ever says he has something for sale -
fear not!).

The K3 worked great, communicated with rig control from the N3FJP
logging program via Windows 10. Connected via the RS-232 connector on
the rig. The Elecraft utility also worked well. Now (about 3 months ago)
it started acting up. Lost a month trying to get it to work while on VK2
holiday for a month. Now been back at it. The rig performs well with the
exception of the communication issue. I have tried new interconnecting
cables, run the interface to log on every combination of Com Ports,
Rates, Parity, Start and Stop, Power, Polling rate and so forth. Because
my son, VK2KDP is more computer savvy than I am, and the fact he has his
station doing as it should and has helped other VKs get set up, I turned
him loose through screen-share. No joy!

Suggestion please, or should I just pack it up to the factory?

Tom, WB2KLD / VK2RSG

______________________________________________________________
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
Message delivered to [hidden email]

[Don Wilhelm]

Tom,

Are you operating with a real RS-232 port, or a USB to serial adapter?
Don't forget that the serial port or adapter could be part of the
problem - also suspect the cable to the K3 RS232 connector.
Do you also have the P3 in the RS-232 loop?  If so, remove it and
connect the PC directly to the K3.

What I am asking you to do is strip things down to the most basic
configuration and then try again.  We very often look to the rig for
problems when it could be something external.

Can I assume this is a K3 with an RS-232 connection and not a K3S or an
upgraded K3 with the USB connection?  My comments address the RS-232
connection.

Check the RS232 baud rate in the menu and set it at 38400 if it is
currently anything else.  FACT, some USB to serial adapters do not like
to work at slow baud rates, no matter how non-intuitive that might be.

Forget N3JFP software or any other software application other than K3
Utility.

Start K3 Utility and open the PORTs tab.
Put the COM port number you are using into the port box on that page
(specifying the COM port is much better than letting it auto-detect
which can have false positives.

If you are using a USB to serial port adapter and are not certain of the
COM port number, go to the PC's Device Manager and open PORTS.  If the
associated COM port is not obvious, unplug it and see which one goes
away - then plug it in again and observe which port is associated with
the USB to serial adapter.

After telling K3 Utility which COM port to use, click on Test
Communications.  If it is able to connect with the K3, there is no K3
problem, look at the setup stuff in your software application for the
problem solution.

If it actually is a COM port failure, it may have to take a trip to
Watsonville.  Or you may want to upgrade to the KIO3B with the built-in
USB to serial adapter and the internal USB soundcard.

73,
Don W3FPR





On 12/2/2018 4:11 PM, Tom & Barb Valosin wrote:

>
> I purchased a previously loved K3, S/N 4734 from Rich, W2EG in Sept
> 2016. He upgraded to the "latest and greatest" version of the K3. Before
> he would allow me to actually pay for the rig he wanted to be sure all
> was up to snuff so he sent it to factory to get a top to bottom check
> out by Keith, WE6R. Keith made some upgrades and pronounced it "meets or
> exceeds all specifications". Nice thing here - Rich did not add the cost
> into my purchase price. (If he ever says he has something for sale -
> fear not!).
>
> The K3 worked great, communicated with rig control from the N3FJP
> logging program via Windows 10. Connected via the RS-232 connector on
> the rig. The Elecraft utility also worked well. Now (about 3 months ago)
> it started acting up. Lost a month trying to get it to work while on VK2
> holiday for a month. Now been back at it. The rig performs well with the
> exception of the communication issue. I have tried new interconnecting
> cables, run the interface to log on every combination of Com Ports,
> Rates, Parity, Start and Stop, Power, Polling rate and so forth. Because
> my son, VK2KDP is more computer savvy than I am, and the fact he has his
> station doing as it should and has helped other VKs get set up, I turned
> him loose through screen-share. No joy!
>
> Suggestion please, or should I just pack it up to the factory?
>

______________________________________________________________
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
Message delivered to [hidden email]