Today we had a heavy lightning storm pass through the area. All of my
antennas were disconnected, as were all the control cables, but the computer and my new K3 were still on. When I returned to the shack after the storm, everything appears to be working normally *except* that none of my software can communicate with the K3. The radio shows no error messages, and transmits and receives normally - just no communications. Alas, I have no other serial devices in the shack, and my backup computer does not have a serial port, so I can't test to determine whether it is the port on the computer or the KIO3. Is there any diagnostic that can be performed in the K3 to determine if in fact something's blown on the KIO3 board? -- 73, Pete N4ZR The World Contest Station Database, updated daily at www.conteststations.com The Reverse Beacon Network at http://reversebeacon.net, blog at reversebeacon.blogspot.com ______________________________________________________________ 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 |
On Sun, 06 Jun 2010 15:13:57 -0400, Pete Smith wrote:
>Is there any diagnostic that can be performed in the K3 to determine if >in fact something's blown on the KIO3 board? Pete, One of the things that lightning create errors in or modify digital memory. One thing I would try is going into the K3 menu and re-setting anything associated with digital comm, like bit rate, etc. Then do the same thing in your computer. If that solves the problem, there may be other errors lucking about. :) 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 |
In reply to this post by Pete Smith N4ZR
On 6/6/2010 12:13 PM, Pete Smith wrote:
> Alas, I have no other serial devices in the shack, and > my backup computer does not have a serial port, so I can't test to > determine whether it is the port on the computer or the KIO3. > > Is there any diagnostic that can be performed in the K3 to determine if > in fact something's blown on the KIO3 board? I am not sure, but you certainly can test the serial port con the computer. Just jump pins 2 and 3 of the connector (or cable) coming from the computer and activate any terminal program. Set it for no handshaking. If the port is working, you should see an echo of anything you type. -- Vic, K2VCO Fresno CA http://www.qsl.net/k2vco/ ______________________________________________________________ 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 |
In reply to this post by Pete Smith N4ZR
I assume you're restarted both the computer and the K3.
You need to eliminate either the computer or the K3 as the problem. Test the computer serial port by following these instructions. http://www.reliableracing.com/downloads/LoopBackTest.pdf If the port talks to itself the problem is with the K3. On 6/6/2010 2:13 PM, Pete Smith wrote: > Today we had a heavy lightning storm pass through the area. All of my > antennas were disconnected, as were all the control cables, but the > computer and my new K3 were still on. When I returned to the shack > after the storm, everything appears to be working normally *except* that > none of my software can communicate with the K3. The radio shows no > error messages, and transmits and receives normally - just no > communications. Alas, I have no other serial devices in the shack, and > my backup computer does not have a serial port, so I can't test to > determine whether it is the port on the computer or the KIO3. > > Is there any diagnostic that can be performed in the K3 to determine if > in fact something's blown on the KIO3 board? > > -- R. Kevin Stover ACØH ______________________________________________________________ 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 |
Thanks, Kevin. I assume (though the referenced test procedure doesn't
say it), that with pins 2 and 3 shorted to each other, each character you type on hyperterminal should be echoed on-screen twice, once locally and once by the loopback. If that's the case. then it may be that I just have a bad *computer* port, which would be good news indeed. 73, Pete N4ZR The World Contest Station Database, updated daily at www.conteststations.com The Reverse Beacon Network at http://reversebeacon.net, blog at reversebeacon.blogspot.com On 6/6/2010 4:51 PM, R. Kevin Stover wrote: > I assume you're restarted both the computer and the K3. > You need to eliminate either the computer or the K3 as the problem. > Test the computer serial port by following these instructions. > > http://www.reliableracing.com/downloads/LoopBackTest.pdf > > If the port talks to itself the problem is with the K3. > > On 6/6/2010 2:13 PM, Pete Smith wrote: >> Today we had a heavy lightning storm pass through the area. All of my >> antennas were disconnected, as were all the control cables, but the >> computer and my new K3 were still on. When I returned to the shack >> after the storm, everything appears to be working normally *except* that >> none of my software can communicate with the K3. The radio shows no >> error messages, and transmits and receives normally - just no >> communications. Alas, I have no other serial devices in the shack, and >> my backup computer does not have a serial port, so I can't test to >> determine whether it is the port on the computer or the KIO3. >> >> Is there any diagnostic that can be performed in the K3 to determine if >> in fact something's blown on the KIO3 board? >> > 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 |
Pete,
If you are using HyperTerminal (or most other terminal emulation programs), you can turn "local echo" on or off. When doing the kind of testing you're doing, I turn it OFF to avoid confusion. (1) In the New Connection - HyperTerminal screen, select File >> Properties. (2) In the New Connection Properties dialog box, click the Settings tab, then click the ASCII Setup... button. (3) In the ASCII Setup dialog box, make sure the "Echo typed characters locally" checkbox is UNCHECKED. (4) Click OK to commit the ASCII Setup settings. (4) Select the COM port you are going to test in the New Connection Properties dialog box and click OK to commit all settings for that port. Then the only thing that will appear on your screen as you type are the looped-back characters. Hope this helps -- Bill W5WVO -------------------------------------------------- From: "Pete Smith" <[hidden email]> Sent: Monday, June 07, 2010 4:17 AM To: "R. Kevin Stover" <[hidden email]> Cc: <[hidden email]> Subject: Re: [Elecraft] How to test serial communications? > Thanks, Kevin. I assume (though the referenced test procedure doesn't > say it), that with pins 2 and 3 shorted to each other, each character > you type on hyperterminal should be echoed on-screen twice, once locally > and once by the loopback. If that's the case. then it may be that I > just have a bad *computer* port, which would be good news indeed. > > 73, Pete N4ZR > > The World Contest Station Database, updated daily at > www.conteststations.com > The Reverse Beacon Network at http://reversebeacon.net, blog at > reversebeacon.blogspot.com > > > On 6/6/2010 4:51 PM, R. Kevin Stover wrote: >> I assume you're restarted both the computer and the K3. >> You need to eliminate either the computer or the K3 as the problem. >> Test the computer serial port by following these instructions. >> >> http://www.reliableracing.com/downloads/LoopBackTest.pdf >> >> If the port talks to itself the problem is with the K3. >> >> On 6/6/2010 2:13 PM, Pete Smith wrote: >>> Today we had a heavy lightning storm pass through the area. All of my >>> antennas were disconnected, as were all the control cables, but the >>> computer and my new K3 were still on. When I returned to the shack >>> after the storm, everything appears to be working normally *except* that >>> none of my software can communicate with the K3. The radio shows no >>> error messages, and transmits and receives normally - just no >>> communications. Alas, I have no other serial devices in the shack, and >>> my backup computer does not have a serial port, so I can't test to >>> determine whether it is the port on the computer or the KIO3. >>> >>> Is there any diagnostic that can be performed in the K3 to determine if >>> in fact something's blown on the KIO3 board? >>> >> > ______________________________________________________________ > 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 |
Sadly, doing this test with a brand new USB-to-serial cable, it works
fine. However, that cable to the K3 yields nothing, and there are some funky voltages on U1 on the KIO3. I'm afraid I may have blown the RS-232 transceivers on both the computer and K3 ends. Time for a changeout. 73, Pete N4ZR The World Contest Station Database, updated daily at www.conteststations.com The Reverse Beacon Network at http://reversebeacon.net, blog at reversebeacon.blogspot.com On 6/7/2010 9:34 AM, Bill VanAlstyne W5WVO wrote: > Pete, > > If you are using HyperTerminal (or most other terminal emulation programs), > you can turn "local echo" on or off. When doing the kind of testing you're > doing, I turn it OFF to avoid confusion. > > (1) In the New Connection - HyperTerminal screen, select File>> Properties. > > (2) In the New Connection Properties dialog box, click the Settings tab, > then click the ASCII Setup... button. > > (3) In the ASCII Setup dialog box, make sure the "Echo typed characters > locally" checkbox is UNCHECKED. > > (4) Click OK to commit the ASCII Setup settings. > > (4) Select the COM port you are going to test in the New Connection > Properties dialog box and click OK to commit all settings for that port. > > Then the only thing that will appear on your screen as you type are the > looped-back characters. > > Hope this helps -- > Bill W5WVO > > -------------------------------------------------- > From: "Pete Smith"<[hidden email]> > Sent: Monday, June 07, 2010 4:17 AM > To: "R. Kevin Stover"<[hidden email]> > Cc:<[hidden email]> > Subject: Re: [Elecraft] How to test serial communications? > > >> Thanks, Kevin. I assume (though the referenced test procedure doesn't >> say it), that with pins 2 and 3 shorted to each other, each character >> you type on hyperterminal should be echoed on-screen twice, once locally >> and once by the loopback. If that's the case. then it may be that I >> just have a bad *computer* port, which would be good news indeed. >> >> 73, Pete N4ZR >> >> The World Contest Station Database, updated daily at >> www.conteststations.com >> The Reverse Beacon Network at http://reversebeacon.net, blog at >> reversebeacon.blogspot.com >> >> >> On 6/6/2010 4:51 PM, R. Kevin Stover wrote: >> >>> I assume you're restarted both the computer and the K3. >>> You need to eliminate either the computer or the K3 as the problem. >>> Test the computer serial port by following these instructions. >>> >>> http://www.reliableracing.com/downloads/LoopBackTest.pdf >>> >>> If the port talks to itself the problem is with the K3. >>> >>> On 6/6/2010 2:13 PM, Pete Smith wrote: >>> >>>> Today we had a heavy lightning storm pass through the area. All of my >>>> antennas were disconnected, as were all the control cables, but the >>>> computer and my new K3 were still on. When I returned to the shack >>>> after the storm, everything appears to be working normally *except* that >>>> none of my software can communicate with the K3. The radio shows no >>>> error messages, and transmits and receives normally - just no >>>> communications. Alas, I have no other serial devices in the shack, and >>>> my backup computer does not have a serial port, so I can't test to >>>> determine whether it is the port on the computer or the KIO3. >>>> >>>> Is there any diagnostic that can be performed in the K3 to determine if >>>> in fact something's blown on the KIO3 board? >>>> >>>> >>> >> ______________________________________________________________ >> 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 |
Free forum by Nabble | Edit this page |