I agree that the transistor is likely not an issue. However, Lyle did write: "About a year ago we changed the transistor used in this oscillator to a higher-gain device because a small number of KIO3 modules had marginal negative voltage."
Unless I'm mistaken, it seems to me that holding the K3 blameless and suggesting that it's something else, is not necessarily a definitive answer. Believe it or not, the KIO3 could actually be defective. I know that this is heresy in this forum, but nothing's perfect :-) - On Fri, 1/8/10, Mike <n...@nf4l.com> wrote: From: Mike <n...@nf4l.com> Subject: Re: [Elecraft] K3 not communicating with PC To: Cc: elecraft@mailman.qth.net, "Roger Dallimore" <mw0...@rgdw.fsnet.co.uk> Date: Friday, January 8, 2010, 6:41 PM I agree also. Try a different device on the cable, like a digital camera, or an iPOD, or a GPS, or...... 73, Mike NF4L Don Wilhelm wrote: > Roger, > > I do not believe the transistors on the IO board should be very high on > the suspect list. It is rare to find a component failure unless it has > been subjected to some unusual stress - component degradation in 3 years > or less is highly unlikely, 20 to 40 years, maybe, but not 3. > May I suggest that the KUSB itself would have the highest probability of > failure, and your tests so far have not done anything to check it (other > than the checks from the computer device manager). The adapter could > have something as subtle as a broken wire in the cable. > Can you try another adapter, or better yet, try using a computer with a > real serial port. > > 73, > Don W3FPR > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html