|
Does anyone have a full functional test procedure to verify my K3S is fully operational? I had a local lightning strike came in through ground that apparently damaged a USB hub, Raspberry PI, Keyboard, Mouse... I suspect the K3s may be damaged as well (especially the USB). I'm looking for a full test process so I can find all of the damage first time around rather than hunt/peck. The K3S powers and appears to rx/tx, Thanks in advance Jerry Moore, AE4PB ______________________________________________________________ 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] |
|
Further testing has proven to be interesting.
Final assessment. 1 USB hub damaged All other gear is fully functional. It's more likely that the hub failed at an earlier date and was only discovered on me testing post storm. This is the most logical as everything has been disconnected for weeks due to inactivity. Jer -----Original Message----- From: Jerry Moore [mailto:[hidden email]] Sent: Friday, July 22, 2016 1:34 PM To: '[hidden email]' Subject: [K3S] Test Procedure Does anyone have a full functional test procedure to verify my K3S is fully operational? I had a local lightning strike came in through ground that apparently damaged a USB hub, Raspberry PI, Keyboard, Mouse... I suspect the K3s may be damaged as well (especially the USB). I'm looking for a full test process so I can find all of the damage first time around rather than hunt/peck. The K3S powers and appears to rx/tx, Thanks in advance Jerry Moore, AE4PB ______________________________________________________________ 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] |
|
Glad that's all that was toasted, Jerry!
Did I miss where the "complete test procedure" was posted? That's a diag tree I'd like ot have. 73, ______________________ Clay Autery, KY5G MONTAC Enterprises (318) 518-1389 On 7/24/2016 2:39 PM, Jerry Moore wrote: > Further testing has proven to be interesting. > Final assessment. > 1 USB hub damaged > > All other gear is fully functional. It's more likely that the hub failed at > an earlier date and was only discovered on me testing post storm. This is > the most logical as everything has been disconnected for weeks due to > inactivity. > Jer > > -----Original Message----- > From: Jerry Moore [mailto:[hidden email]] > Sent: Friday, July 22, 2016 1:34 PM > To: '[hidden email]' > Subject: [K3S] Test Procedure > > > > Does anyone have a full functional test procedure to verify my K3S is fully > operational? > > I had a local lightning strike came in through ground that apparently > damaged a USB hub, Raspberry PI, Keyboard, Mouse... I suspect the K3s may be > damaged as well (especially the USB). > I'm looking for a full test process so I can find all of the damage first > time around rather than hunt/peck. > > The K3S powers and appears to rx/tx, > Thanks in advance > Jerry Moore, AE4PB > > ______________________________________________________________ > 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] ______________________________________________________________ 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] |
|
Not yet received to date
Sent from my iPad > On Jul 24, 2016, at 4:16 PM, Clay Autery <[hidden email]> wrote: > > Glad that's all that was toasted, Jerry! > > Did I miss where the "complete test procedure" was posted? That's a > diag tree I'd like ot have. > > 73, > > ______________________ > Clay Autery, KY5G > MONTAC Enterprises > (318) 518-1389 > >> On 7/24/2016 2:39 PM, Jerry Moore wrote: >> Further testing has proven to be interesting. >> Final assessment. >> 1 USB hub damaged >> >> All other gear is fully functional. It's more likely that the hub failed at >> an earlier date and was only discovered on me testing post storm. This is >> the most logical as everything has been disconnected for weeks due to >> inactivity. >> Jer >> >> -----Original Message----- >> From: Jerry Moore [mailto:[hidden email]] >> Sent: Friday, July 22, 2016 1:34 PM >> To: '[hidden email]' >> Subject: [K3S] Test Procedure >> >> >> >> Does anyone have a full functional test procedure to verify my K3S is fully >> operational? >> >> I had a local lightning strike came in through ground that apparently >> damaged a USB hub, Raspberry PI, Keyboard, Mouse... I suspect the K3s may be >> damaged as well (especially the USB). >> I'm looking for a full test process so I can find all of the damage first >> time around rather than hunt/peck. >> >> The K3S powers and appears to rx/tx, >> Thanks in advance >> Jerry Moore, AE4PB >> >> ______________________________________________________________ >> 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] > > ______________________________________________________________ > 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] ______________________________________________________________ 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] |
|
You probably won't.
The K3 or K3S is put in a test fixture and run for 24 hours before being shipped after assembly, repair and/or upgrades. I just talked to Elecraft in the last week about one of my K3s I had in for upgrades and was told it would ship a day after being put in a test fixture and going through a 24 hour burn in. I take that to mean there is some sort of computer/microprocessor automation that runs various tests on the K3 over a 24 hour period. So there is probably no complete overall K3 test we as users can perform other than what is in the K3 utility and/or specific tests for a specific problem as directed to users by Elecraft support. There may be someone (support, Wayne or Eric) who knows more than I that can confirm or deny my assumption. Even if we as users had such a procedure, how many users would have the test equipment necessary to perform such tests? Plus running the risk that the user(s) could mess up the works. Mark Musick, WB9CIF -----Original Message----- From: Elecraft [mailto:[hidden email]] On Behalf Of Jerry Sent: Sunday, July 24, 2016 10:10 PM To: Clay Autery <[hidden email]> Cc: [hidden email] Subject: Re: [Elecraft] [K3S] Test Procedure Not yet received to date Sent from my iPad > On Jul 24, 2016, at 4:16 PM, Clay Autery <[hidden email]> wrote: > > Glad that's all that was toasted, Jerry! > > Did I miss where the "complete test procedure" was posted? That's a > diag tree I'd like ot have. > > 73, > > ______________________ > Clay Autery, KY5G > MONTAC Enterprises > (318) 518-1389 > >> On 7/24/2016 2:39 PM, Jerry Moore wrote: >> Further testing has proven to be interesting. >> Final assessment. >> 1 USB hub damaged >> >> All other gear is fully functional. It's more likely that the hub >> failed at an earlier date and was only discovered on me testing post >> storm. This is the most logical as everything has been disconnected >> for weeks due to inactivity. >> Jer >> >> -----Original Message----- >> From: Jerry Moore [mailto:[hidden email]] >> Sent: Friday, July 22, 2016 1:34 PM >> To: '[hidden email]' >> Subject: [K3S] Test Procedure >> >> >> >> Does anyone have a full functional test procedure to verify my K3S is >> fully operational? >> >> I had a local lightning strike came in through ground that apparently >> damaged a USB hub, Raspberry PI, Keyboard, Mouse... I suspect the K3s >> may be damaged as well (especially the USB). >> I'm looking for a full test process so I can find all of the damage >> first time around rather than hunt/peck. >> >> The K3S powers and appears to rx/tx, >> Thanks in advance >> Jerry Moore, AE4PB >> >> ______________________________________________________________ >> 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] > > ______________________________________________________________ > 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] ______________________________________________________________ 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] ______________________________________________________________ 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] |
|
The lack of a full functional test is more likely due to it not being
profitable AND being overkill. Generally if it works then it just works. I'm still thinking it through, however, the process doesn't require complex test gear as it's a functional testing of all features/modules of the radio. The build/calibration process is a bare bones, single band/mode setup. I'll run back through the manuals and if I don't find something then I'll create one. The objective is to give a quantitative value for the current operation go/no-go that can be recorded and used to detect when system degradation has occurred. Jer -----Original Message----- From: Mark E. Musick [mailto:[hidden email]] Sent: Sunday, July 24, 2016 7:38 PM To: 'Jerry'; 'Clay Autery' Cc: [hidden email] Subject: RE: [Elecraft] [K3S] Test Procedure You probably won't. The K3 or K3S is put in a test fixture and run for 24 hours before being shipped after assembly, repair and/or upgrades. I just talked to Elecraft in the last week about one of my K3s I had in for upgrades and was told it would ship a day after being put in a test fixture and going through a 24 hour burn in. I take that to mean there is some sort of computer/microprocessor automation that runs various tests on the K3 over a 24 hour period. So there is probably no complete overall K3 test we as users can perform other than what is in the K3 utility and/or specific tests for a specific problem as directed to users by Elecraft support. There may be someone (support, Wayne or Eric) who knows more than I that can confirm or deny my assumption. Even if we as users had such a procedure, how many users would have the test equipment necessary to perform such tests? Plus running the risk that the user(s) could mess up the works. Mark Musick, WB9CIF -----Original Message----- From: Elecraft [mailto:[hidden email]] On Behalf Of Jerry Sent: Sunday, July 24, 2016 10:10 PM To: Clay Autery <[hidden email]> Cc: [hidden email] Subject: Re: [Elecraft] [K3S] Test Procedure Not yet received to date Sent from my iPad > On Jul 24, 2016, at 4:16 PM, Clay Autery <[hidden email]> wrote: > > Glad that's all that was toasted, Jerry! > > Did I miss where the "complete test procedure" was posted? That's a > diag tree I'd like ot have. > > 73, > > ______________________ > Clay Autery, KY5G > MONTAC Enterprises > (318) 518-1389 > >> On 7/24/2016 2:39 PM, Jerry Moore wrote: >> Further testing has proven to be interesting. >> Final assessment. >> 1 USB hub damaged >> >> All other gear is fully functional. It's more likely that the hub >> failed at an earlier date and was only discovered on me testing post >> storm. This is the most logical as everything has been disconnected >> for weeks due to inactivity. >> Jer >> >> -----Original Message----- >> From: Jerry Moore [mailto:[hidden email]] >> Sent: Friday, July 22, 2016 1:34 PM >> To: '[hidden email]' >> Subject: [K3S] Test Procedure >> >> >> >> Does anyone have a full functional test procedure to verify my K3S is >> fully operational? >> >> I had a local lightning strike came in through ground that apparently >> damaged a USB hub, Raspberry PI, Keyboard, Mouse... I suspect the K3s >> may be damaged as well (especially the USB). >> I'm looking for a full test process so I can find all of the damage >> first time around rather than hunt/peck. >> >> The K3S powers and appears to rx/tx, >> Thanks in advance >> Jerry Moore, AE4PB >> >> ______________________________________________________________ >> 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] > > ______________________________________________________________ > 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] ______________________________________________________________ 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] ______________________________________________________________ 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] |
|
In reply to this post by markmusick
Mark,
I think you are correct, no "standard" test procedure is possible because it would not account for all installed options, filter assignments, and other configurable aspects of the K3/K3S. I would however suggest that one could use a procedure similar to what I use for a K2. It is best if you have a dummy load and can observe the TX waveforms on an oscilloscope connected across that dummy load with a 10X probe. How well you can do the tests will depend on the equipment you have available. Testing into an antenna can produce ambiguous results - use a dummy load even if you have to borrow one. An external wattmeter with trusted calibration is also useful. Proposed procedure --- 1) Go through all the calibration items listed in the manual. 2) Check the status of each option installed and do a functional check to assure that each of those options is working. 3) Check the computer connection capability - does it connect with K3 Uility? 4) Check the filter assignments using K3 Utility. 5) Check the CW output waveform on the 'scope. 6) Check the SSB output waveform. Does it change with Mic Gain and Compression. 7) Check data mode operation if you had been set up for that capability. 8) Check FM capability if your K3 is equipped with the 13kHz filter. 9) Check AM capability if your K3 has the 6kHz or 13kHz filter. 10) if you have the KAT3, check that it tunes properly into a dummy load on all bands. 10a) if you have 2 50 ohm dummy loads, connect them in parallel and assure that the KAT3 will tune into the resultant 25 ohm dummy load. 11) Check receive function on all bands. A signal generator like the XG3 is a big help with this evaluation. Check at low signal levels. 12) Check the KRX3 receive in the same manner as the main reciever. Note, you can best observe the RX characteristics using an audio spectrum analyzer (Spectrogram or Spectrum Lab or others) running on your computer - feed the headphone output (or rear panel phones or speaker) to the soundcard input. The main RX is the left channel and the KRX3 is the right channel. If you do not have an audio spectrum analyzer, you can download a good copy of Spectrogram from my website www.w3fpr.com - look near the bottom of the opening page for links to a copy internal to my website (it has been scrubbed by several anti-virus programs and has come up clean - contrary to several copies of Spectrogram found 'in the wild' on the internet). 73, Don W3FPR On 7/24/2016 7:38 PM, Mark E. Musick wrote: > You probably won't. > The K3 or K3S is put in a test fixture and run for 24 hours before being > shipped after assembly, repair and/or upgrades. > I just talked to Elecraft in the last week about one of my K3s I had in for > upgrades and was told it would ship a day after being put in a test fixture > and going through a 24 hour burn in. > I take that to mean there is some sort of computer/microprocessor automation > that runs various tests on the K3 over a 24 hour period. > So there is probably no complete overall K3 test we as users can perform > other than what is in the K3 utility and/or specific tests for a specific > problem as directed to users by Elecraft support. > There may be someone (support, Wayne or Eric) who knows more than I that can > confirm or deny my assumption. > Even if we as users had such a procedure, how many users would have the test > equipment necessary to perform such tests? Plus running the risk that the > user(s) could mess up the works. > ______________________________________________________________ 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] |
|
I think Don should write that up and post it on his site.
On 7/24/2016 8:37 PM, Don Wilhelm wrote: > Mark, > > I think you are correct, no "standard" test procedure is possible > because it would not account for all installed options, filter > assignments, and other configurable aspects of the K3/K3S. > > I would however suggest that one could use a procedure similar to what > I use for a K2. > It is best if you have a dummy load and can observe the TX waveforms > on an oscilloscope connected across that dummy load with a 10X probe. > How well you can do the tests will depend on the equipment you have > available. > Testing into an antenna can produce ambiguous results - use a dummy > load even if you have to borrow one. An external wattmeter with > trusted calibration is also useful. > > Proposed procedure --- > 1) Go through all the calibration items listed in the manual. > 2) Check the status of each option installed and do a functional check > to assure that each of those options is working. > 3) Check the computer connection capability - does it connect with K3 > Uility? > 4) Check the filter assignments using K3 Utility. > 5) Check the CW output waveform on the 'scope. > 6) Check the SSB output waveform. Does it change with Mic Gain and > Compression. > 7) Check data mode operation if you had been set up for that capability. > 8) Check FM capability if your K3 is equipped with the 13kHz filter. > 9) Check AM capability if your K3 has the 6kHz or 13kHz filter. > 10) if you have the KAT3, check that it tunes properly into a dummy > load on all bands. > 10a) if you have 2 50 ohm dummy loads, connect them in parallel and > assure that the KAT3 will tune into the resultant 25 ohm dummy load. > 11) Check receive function on all bands. A signal generator like the > XG3 is a big help with this evaluation. Check at low signal levels. > 12) Check the KRX3 receive in the same manner as the main reciever. > > Note, you can best observe the RX characteristics using an audio > spectrum analyzer (Spectrogram or Spectrum Lab or others) running on > your computer - feed the headphone output (or rear panel phones or > speaker) to the soundcard input. The main RX is the left channel and > the KRX3 is the right channel. > If you do not have an audio spectrum analyzer, you can download a good > copy of Spectrogram from my website www.w3fpr.com - look near the > bottom of the opening page for links to a copy internal to my website > (it has been scrubbed by several anti-virus programs and has come up > clean - contrary to several copies of Spectrogram found 'in the wild' > on the internet). > > 73, > Don W3FPR > -- R. Kevin Stover AC0H ARRL FISTS #11993 SKCC #215 NAQCC #3441 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ______________________________________________________________ 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] |
| Free forum by Nabble | Edit this page |
