Hi All,
Strange thing! I was working a DX station and my PC locked up, and kept sending my call sign. The only way to stop the RF was to turn the rig off. I let it sit for a minute or two, then turned it back on. The LCD screen flashed a ERR PTT. I disconnected the WinKeyer and plugged it back in and was able to work the station with the paddles, rather than N1MM+ Now, I can't get the K3s to connect to the PC (Win7 Pro 64bit). It shows as a unrecognized USB device in the Device Manager. I have shut everything down, PC, K3s, WinKeyer and removed power from all and let it sit for awhile. The PC starts fine, the K3s starts up fine (no ERR messages) and works well, the Winkeyer works fine. I know the K3s was communicating with the PC earlier, as I was using the K3 utility to set roofing filters I just installed in the sub receiver. Any suggestions on where to begin looking would be a great help. Thanks in advance. 73 de Jim - KE8G ______________________________________________________________ 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,
It sounds to me like your computer has corrupted driver files - maybe caused by some glitch in the computer or its power. Download and install the FTDI drivers. Then disconnect (not just power them down) the WinKeyer and all other other gear. See if you can connect using K3 Utility. If so, start adding back your other gear one at a time and see when it fails. If K3 Utility fails to connect, then an email to [hidden email] is in order. 73, Don W3FPR On 3/22/2019 8:15 PM, KE8G wrote: > Hi All, > Strange thing! I was working a DX station and my PC locked up, and kept > sending my call sign. The only way to stop the RF was to turn the rig > off. I let it sit for a minute or two, then turned it back on. The LCD > screen flashed a ERR PTT. I disconnected the WinKeyer and plugged it back > in and was able to work the station with the paddles, rather than N1MM+ > > Now, I can't get the K3s to connect to the PC (Win7 Pro 64bit). It shows > as a unrecognized USB device in the Device Manager. > > I have shut everything down, PC, K3s, WinKeyer and removed power from all > and let it sit for awhile. The PC starts fine, the K3s starts up fine (no > ERR messages) and works well, the Winkeyer works fine. > > I know the K3s was communicating with the PC earlier, as I was using the K3 > utility to set roofing filters I just installed in the sub receiver. 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 KE8G-2
Hi Jim,
even if you haven't changed any settings before I would check the COM Port settings like Baud rate etc. at the N1MM+ Check the settings at the K3S too. Next should be the connection from K3S to PC. If you have another cable. Give it a try If you boot the PC make sure the K3S is already ON 73 de Chris, DL2MDU Am 23.03.2019 um 01:15 schrieb KE8G: > Hi All, > Strange thing! I was working a DX station and my PC locked up, and kept > sending my call sign. The only way to stop the RF was to turn the rig > off. I let it sit for a minute or two, then turned it back on. The LCD > screen flashed a ERR PTT. I disconnected the WinKeyer and plugged it back > in and was able to work the station with the paddles, rather than N1MM+ > > Now, I can't get the K3s to connect to the PC (Win7 Pro 64bit). It shows > as a unrecognized USB device in the Device Manager. > > I have shut everything down, PC, K3s, WinKeyer and removed power from all > and let it sit for awhile. The PC starts fine, the K3s starts up fine (no > ERR messages) and works well, the Winkeyer works fine. > > I know the K3s was communicating with the PC earlier, as I was using the K3 > utility to set roofing filters I just installed in the sub receiver. > > Any suggestions on where to begin looking would be a great help. > > Thanks in advance. > 73 de Jim - KE8G > ______________________________________________________________ > 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
73 Chris, DL2MDU
|
In reply to this post by Don Wilhelm
Don,
Using the K3 Utility is good advice. Yesterday for some reason when I had updated WIN10, the one port changed numbers. And of all the ports I use for both K3's and all the programs and hardware, that was the only one that changed from 16 to 12. Go figure. Went into Device Manager and changed the port number back to what it was. Weird. 73, N2TK, Tony -----Original Message----- From: [hidden email] <[hidden email]> On Behalf Of Don Wilhelm Sent: Friday, March 22, 2019 11:05 PM To: KE8G <[hidden email]>; Elecraft <[hidden email]>; [hidden email] Subject: Re: [Elecraft-K3] [Elecraft] K3s won't connect to PC Jim, It sounds to me like your computer has corrupted driver files - maybe caused by some glitch in the computer or its power. Download and install the FTDI drivers. Then disconnect (not just power them down) the WinKeyer and all other other gear. See if you can connect using K3 Utility. If so, start adding back your other gear one at a time and see when it fails. If K3 Utility fails to connect, then an email to [hidden email] is in order. 73, Don W3FPR On 3/22/2019 8:15 PM, KE8G wrote: > Hi All, > Strange thing! I was working a DX station and my PC locked up, and > kept sending my call sign. The only way to stop the RF was to turn > the rig off. I let it sit for a minute or two, then turned it back > on. The LCD screen flashed a ERR PTT. I disconnected the WinKeyer > and plugged it back in and was able to work the station with the > paddles, rather than N1MM+ > > Now, I can't get the K3s to connect to the PC (Win7 Pro 64bit). It > shows as a unrecognized USB device in the Device Manager. > > I have shut everything down, PC, K3s, WinKeyer and removed power from > all and let it sit for awhile. The PC starts fine, the K3s starts up > fine (no ERR messages) and works well, the Winkeyer works fine. > > I know the K3s was communicating with the PC earlier, as I was using > the K3 utility to set roofing filters I just installed in the sub receiver. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#30596): https://groups.io/g/Elecraft-K3/message/30596 Mute This Topic: https://groups.io/mt/30723742/669041 Group Owner: [hidden email] Unsubscribe: https://groups.io/g/Elecraft-K3/leave/1872144/624467674/xyzzy [[hidden email]] -=-=-=-=-=-=-=-=-=-=-=- ______________________________________________________________ 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 |
Well, I have done all the suggested tests and configurations. The K3s USB
to PC connection is just not making it. The only COM ports showing up in the Device Manager are all accounted for and no new ones are present. I have tried different USB ports on the PC and different USB cables; all resulting in a message telling me the PC doesn't recognized the K3s as a USB device. I have removed the K3s USB to PC wire and am now using a KUSB via RS232 to the K3s and it is functioning perfectly. I have N1mm+ working & the Winkeyer working with this setup with no problems. I truly believe I'll be sending the K3s to Elecraft for repairs. I will call them on Monday. 73 de Jim - KE8G On Sat, Mar 23, 2019 at 12:37 PM <[hidden email]> wrote: > Don, > Using the K3 Utility is good advice. > Yesterday for some reason when I had updated WIN10, the one port changed > numbers. And of all the ports I use for both K3's and all the programs and > hardware, that was the only one that changed from 16 to 12. Go figure. Went > into Device Manager and changed the port number back to what it was. Weird. > 73, > N2TK, Tony > > -----Original Message----- > From: [hidden email] <[hidden email]> On Behalf Of Don > Wilhelm > Sent: Friday, March 22, 2019 11:05 PM > To: KE8G <[hidden email]>; Elecraft <[hidden email]>; > [hidden email] > Subject: Re: [Elecraft-K3] [Elecraft] K3s won't connect to PC > > Jim, > > It sounds to me like your computer has corrupted driver files - maybe > caused by some glitch in the computer or its power. > Download and install the FTDI drivers. > > Then disconnect (not just power them down) the WinKeyer and all other > other gear. See if you can connect using K3 Utility. If so, start adding > back your other gear one at a time and see when it fails. > > If K3 Utility fails to connect, then an email to [hidden email] is > in order. > > 73, > Don W3FPR > > On 3/22/2019 8:15 PM, KE8G wrote: > > Hi All, > > Strange thing! I was working a DX station and my PC locked up, and > > kept sending my call sign. The only way to stop the RF was to turn > > the rig off. I let it sit for a minute or two, then turned it back > > on. The LCD screen flashed a ERR PTT. I disconnected the WinKeyer > > and plugged it back in and was able to work the station with the > > paddles, rather than N1MM+ > > > > Now, I can't get the K3s to connect to the PC (Win7 Pro 64bit). It > > shows as a unrecognized USB device in the Device Manager. > > > > I have shut everything down, PC, K3s, WinKeyer and removed power from > > all and let it sit for awhile. The PC starts fine, the K3s starts up > > fine (no ERR messages) and works well, the Winkeyer works fine. > > > > I know the K3s was communicating with the PC earlier, as I was using > > the K3 utility to set roofing filters I just installed in the sub > receiver. > > -=-=-=-=-=-=-=-=-=-=-=- > Groups.io Links: You receive all messages sent to this group. > > View/Reply Online (#30596): https://groups.io/g/Elecraft-K3/message/30596 > Mute This Topic: https://groups.io/mt/30723742/669041 > Group Owner: [hidden email] > Unsubscribe: https://groups.io/g/Elecraft-K3/leave/1872144/624467674/xyzzy > [[hidden email]] > -=-=-=-=-=-=-=-=-=-=-=- > > > 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.
I presume that you have set the CONFIG:RS232 parameter to USB ? Page 18 of the K3S User Manual. There’s nothing in the replies (below) that seems to suggest doing this. 73, Alan. G4GNX From: KE8G Sent: Saturday, March 23, 2019 5:45 PM To: [hidden email] Cc: [hidden email] ; Elecraft Subject: Re: [Elecraft-K3] [Elecraft] K3s won't connect to PC Well, I have done all the suggested tests and configurations. The K3s USB to PC connection is just not making it. The only COM ports showing up in the Device Manager are all accounted for and no new ones are present. I have tried different USB ports on the PC and different USB cables; all resulting in a message telling me the PC doesn't recognized the K3s as a USB device. I have removed the K3s USB to PC wire and am now using a KUSB via RS232 to the K3s and it is functioning perfectly. I have N1mm+ working & the Winkeyer working with this setup with no problems. I truly believe I'll be sending the K3s to Elecraft for repairs. I will call them on Monday. 73 de Jim - KE8G On Sat, Mar 23, 2019 at 12:37 PM <[hidden email]> wrote: Don, Using the K3 Utility is good advice. Yesterday for some reason when I had updated WIN10, the one port changed numbers. And of all the ports I use for both K3's and all the programs and hardware, that was the only one that changed from 16 to 12. Go figure. Went into Device Manager and changed the port number back to what it was. Weird. 73, N2TK, Tony -----Original Message----- From: [hidden email] <[hidden email]> On Behalf Of Don Wilhelm Sent: Friday, March 22, 2019 11:05 PM To: KE8G <[hidden email]>; Elecraft <[hidden email]>; [hidden email] Subject: Re: [Elecraft-K3] [Elecraft] K3s won't connect to PC Jim, It sounds to me like your computer has corrupted driver files - maybe caused by some glitch in the computer or its power. Download and install the FTDI drivers. Then disconnect (not just power them down) the WinKeyer and all other other gear. See if you can connect using K3 Utility. If so, start adding back your other gear one at a time and see when it fails. If K3 Utility fails to connect, then an email to [hidden email] is in order. 73, Don W3FPR On 3/22/2019 8:15 PM, KE8G wrote: > Hi All, > Strange thing! I was working a DX station and my PC locked up, and > kept sending my call sign. The only way to stop the RF was to turn > the rig off. I let it sit for a minute or two, then turned it back > on. The LCD screen flashed a ERR PTT. I disconnected the WinKeyer > and plugged it back in and was able to work the station with the > paddles, rather than N1MM+ > > Now, I can't get the K3s to connect to the PC (Win7 Pro 64bit). It > shows as a unrecognized USB device in the Device Manager. > > I have shut everything down, PC, K3s, WinKeyer and removed power from > all and let it sit for awhile. The PC starts fine, the K3s starts up > fine (no ERR messages) and works well, the Winkeyer works fine. > > I know the K3s was communicating with the PC earlier, as I was using > the K3 utility to set roofing filters I just installed in the sub receiver. _._,_._,_ -------------------------------------------------------------------------------- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#30601) | Reply To Group | Reply To Sender | Mute This Topic | New Topic Your Subscription | Contact Group Owner | Unsubscribe [[hidden email]] _._,_._,_ ______________________________________________________________ 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 Elecraft mailing list
If it’s a K3S, be sure CONFIG:RS242 is set to USB if you are using the supplied USB cable.
Sent from my iPhone ...nr4c. bill > On Mar 23, 2019, at 12:33 PM, tony.kaz--- via Elecraft <[hidden email]> wrote: > > Don, > Using the K3 Utility is good advice. > Yesterday for some reason when I had updated WIN10, the one port changed numbers. And of all the ports I use for both K3's and all the programs and hardware, that was the only one that changed from 16 to 12. Go figure. Went into Device Manager and changed the port number back to what it was. Weird. > 73, > N2TK, Tony > > -----Original Message----- > From: [hidden email] <[hidden email]> On Behalf Of Don Wilhelm > Sent: Friday, March 22, 2019 11:05 PM > To: KE8G <[hidden email]>; Elecraft <[hidden email]>; [hidden email] > Subject: Re: [Elecraft-K3] [Elecraft] K3s won't connect to PC > > Jim, > > It sounds to me like your computer has corrupted driver files - maybe caused by some glitch in the computer or its power. > Download and install the FTDI drivers. > > Then disconnect (not just power them down) the WinKeyer and all other other gear. See if you can connect using K3 Utility. If so, start adding back your other gear one at a time and see when it fails. > > If K3 Utility fails to connect, then an email to [hidden email] is in order. > > 73, > Don W3FPR > >> On 3/22/2019 8:15 PM, KE8G wrote: >> Hi All, >> Strange thing! I was working a DX station and my PC locked up, and >> kept sending my call sign. The only way to stop the RF was to turn >> the rig off. I let it sit for a minute or two, then turned it back >> on. The LCD screen flashed a ERR PTT. I disconnected the WinKeyer >> and plugged it back in and was able to work the station with the >> paddles, rather than N1MM+ >> >> Now, I can't get the K3s to connect to the PC (Win7 Pro 64bit). It >> shows as a unrecognized USB device in the Device Manager. >> >> I have shut everything down, PC, K3s, WinKeyer and removed power from >> all and let it sit for awhile. The PC starts fine, the K3s starts up >> fine (no ERR messages) and works well, the Winkeyer works fine. >> ______________________________________________________________ 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 Elecraft mailing list
Checking communications capability with K3 Utility is always a good
first step when you have problems with communications with the K3/K3S (similar for KX3/KX2). If the Utility can communicate, then you should know to look to your computer applications and their setup information for the problem. If the Utility cannot connect, it is either a computer port assignment problem, a USB to serial adapter problem (including the adapter built into the K3S) or a K3/K3S problem. So depending on the results of the K3 Utility "Test Communications", you will know where to look for the problem. Often it is a computer problem such as Tony discovered. 73, Don W3FPR On 3/23/2019 12:33 PM, tony.kaz--- via Elecraft wrote: > Don, > Using the K3 Utility is good advice. > Yesterday for some reason when I had updated WIN10, the one port changed numbers. And of all the ports I use for both K3's and all the programs and hardware, that was the only one that changed from 16 to 12. Go figure. Went into Device Manager and changed the port number back to what it was. Weird. ______________________________________________________________ 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 |
I want to thank all who offered suggestions and information, it was a
pleasure to reach out for help and have so many folks willing to help! I contacted Elecraft yesterday and ran things past them. I was given a few suggestions, and decided to "pretend" it was a new set-up. I am not sure what was going on, but with the USB cable plugged into the same USB port on the same computer, when I turned the radio on, it went through a complete new set-up; including installing the drivers and audio CODECs. It even gave me the same COM port number. I am going to attribute it to divine intervention, as I did a lot of praying for it to be something simple! Things are working as normal, and a "boat load" of toroids are on the way!! Thanks again. 73 de Jim - KE8G On Sat, Mar 23, 2019 at 6:32 PM Don Wilhelm <[hidden email]> wrote: > Checking communications capability with K3 Utility is always a good > first step when you have problems with communications with the K3/K3S > (similar for KX3/KX2). > If the Utility can communicate, then you should know to look to your > computer applications and their setup information for the problem. > > If the Utility cannot connect, it is either a computer port assignment > problem, a USB to serial adapter problem (including the adapter built > into the K3S) or a K3/K3S problem. > > So depending on the results of the K3 Utility "Test Communications", you > will know where to look for the problem. Often it is a computer problem > such as Tony discovered. > > 73, > Don W3FPR > > On 3/23/2019 12:33 PM, tony.kaz--- via Elecraft wrote: > > Don, > > Using the K3 Utility is good advice. > > Yesterday for some reason when I had updated WIN10, the one port changed > numbers. And of all the ports I use for both K3's and all the programs and > hardware, that was the only one that changed from 16 to 12. Go figure. Went > into Device Manager and changed the port number back to what it was. Weird. > ______________________________________________________________ > 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 |
I have always loved self-healing electronics. By starting from scratch you removed the corruption issue. Way to go.
73, Bill K9YEQ https://wrj-tech.com/ -----Original Message----- From: [hidden email] <[hidden email]> On Behalf Of KE8G Sent: Tuesday, March 26, 2019 11:11 AM To: [hidden email] Cc: Elecraft <[hidden email]> Subject: Re: [Elecraft] [Elecraft-K3] K3s won't connect to PC I want to thank all who offered suggestions and information, it was a pleasure to reach out for help and have so many folks willing to help! I contacted Elecraft yesterday and ran things past them. I was given a few suggestions, and decided to "pretend" it was a new set-up. I am not sure what was going on, but with the USB cable plugged into the same USB port on the same computer, when I turned the radio on, it went through a complete new set-up; including installing the drivers and audio CODECs. It even gave me the same COM port number. I am going to attribute it to divine intervention, as I did a lot of praying for it to be something simple! Things are working as normal, and a "boat load" of toroids are on the way!! Thanks again. 73 de Jim - KE8G On Sat, Mar 23, 2019 at 6:32 PM Don Wilhelm <[hidden email]> wrote: > Checking communications capability with K3 Utility is always a good > first step when you have problems with communications with the K3/K3S > (similar for KX3/KX2). > If the Utility can communicate, then you should know to look to your > computer applications and their setup information for the problem. > > If the Utility cannot connect, it is either a computer port assignment > problem, a USB to serial adapter problem (including the adapter built > into the K3S) or a K3/K3S problem. > > So depending on the results of the K3 Utility "Test Communications", > you will know where to look for the problem. Often it is a computer > problem such as Tony discovered. > > 73, > Don W3FPR > > On 3/23/2019 12:33 PM, tony.kaz--- via Elecraft wrote: > > Don, > > Using the K3 Utility is good advice. > > Yesterday for some reason when I had updated WIN10, the one port > > changed > numbers. And of all the ports I use for both K3's and all the programs > and hardware, that was the only one that changed from 16 to 12. Go > figure. Went into Device Manager and changed the port number back to what it was. Weird. > ______________________________________________________________ > 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 |