|
I was using the K3 today. The VOX kept cycling to transmit and back
with no voice input. Sounded like an easy problem to fix. Just touch up the antivox. Nope. Listening in the monitor, there is a rushing sound with clicking (like fans in the background or something with a superimposed woodpecker). Clearly that spurious noise is what was tripping the vox off/on. Next removing the mike plug, the rushing sound was still there. With no mike input where is it coming from? Unlikely to be RFI since it is there at 1 watt. Setting the mike gain to zero and compression doesn't fix it. Compression level does substantial increase or decrease it. Any suggestions? 73 de Brian/K3KO ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2247 / Virus Database: 3658/6449 - Release Date: 12/25/13 ______________________________________________________________ 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 |
|
Any sound card input?
73, Mike NF4L On Dec 25, 2013, at 12:28 PM, Brian Alsop <[hidden email]> wrote: > I was using the K3 today. The VOX kept cycling to transmit and back with no voice input. > > Sounded like an easy problem to fix. Just touch up the antivox. > > Nope. > > Listening in the monitor, there is a rushing sound with clicking (like fans in the background or something with a superimposed woodpecker). > Clearly that spurious noise is what was tripping the vox off/on. > > Next removing the mike plug, the rushing sound was still there. > > With no mike input where is it coming from? Unlikely to be RFI since it is there at 1 watt. > > Setting the mike gain to zero and compression doesn't fix it. Compression level does substantial increase or decrease it. > > Any suggestions? > > 73 de Brian/K3KO > > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2247 / Virus Database: 3658/6449 - Release Date: 12/25/13 > > ______________________________________________________________ > 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 |
|
In reply to this post by alsopb
Have you got anything connected to the line in socket ?
John G4ZTR -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Brian Alsop Sent: 25 December 2013 17:29 To: 'Elecraft Reflector' Subject: [Elecraft] Weird K3 SSB problems I was using the K3 today. The VOX kept cycling to transmit and back with no voice input. Sounded like an easy problem to fix. Just touch up the antivox. Nope. Listening in the monitor, there is a rushing sound with clicking (like fans in the background or something with a superimposed woodpecker). Clearly that spurious noise is what was tripping the vox off/on. Next removing the mike plug, the rushing sound was still there. With no mike input where is it coming from? Unlikely to be RFI since it is there at 1 watt. Setting the mike gain to zero and compression doesn't fix it. Compression level does substantial increase or decrease it. Any suggestions? 73 de Brian/K3KO ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2247 / Virus Database: 3658/6449 - Release Date: 12/25/13 ______________________________________________________________ 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 |
|
In reply to this post by alsopb
Thanks to tips from several people of the list this problem was solved.
It turns out that a scope showed there was a 300 mv audio signal on line in. Line in was not selected and I don't understand how it got to the mic input. Bleed through? I normally use line in for PSK in the data A mode. Never the less, I had shot myself if the foot. The SDR RX/Rocky connected to the K3 normally has its audio sent to a sound card with no speaker/earphones connected. Today I listened to it a bit on a different sound card. Resetting the sound card choice, I'd sent it to the SC used for PSK transmit tones. 73 de Brian/K3KO On 12/25/2013 17:28, Brian Alsop wrote: > I was using the K3 today. The VOX kept cycling to transmit and back > with no voice input. > > Sounded like an easy problem to fix. Just touch up the antivox. > > Nope. > > Listening in the monitor, there is a rushing sound with clicking (like > fans in the background or something with a superimposed woodpecker). > Clearly that spurious noise is what was tripping the vox off/on. > > Next removing the mike plug, the rushing sound was still there. > > With no mike input where is it coming from? Unlikely to be RFI since it > is there at 1 watt. > > Setting the mike gain to zero and compression doesn't fix it. > Compression level does substantial increase or decrease it. > > Any suggestions? > > 73 de Brian/K3KO > > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2247 / Virus Database: 3658/6449 - Release Date: 12/25/13 > > ______________________________________________________________ > 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 > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2247 / Virus Database: 3658/6449 - Release Date: 12/25/13 > > ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2247 / Virus Database: 3658/6449 - Release Date: 12/25/13 ______________________________________________________________ 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 |
|
Please ignore this. I found a 300 mv SDR audio signal on line in.
I don't understand how it got into the mic input-- it's only selected that way for DATA A. I thought the mike/line in inputs were isolated from one another. Guess not. Removing the line-in signal solved the problem. 73 de Brian/K3KO -------- Original Message -------- Subject: Weird K3 SSB problems fixed Date: Wed, 25 Dec 2013 19:27:10 +0000 From: Brian Alsop <[hidden email]> To: [hidden email] Thanks to tips from several people of the list this problem was solved. It turns out that a scope showed there was a 300 mv audio signal on line in. Line in was not selected and I don't understand how it got to the mic input. Bleed through? I normally use line in for PSK in the data A mode. Never the less, I had shot myself if the foot. The SDR RX/Rocky connected to the K3 normally has its audio sent to a sound card with no speaker/earphones connected. Today I listened to it a bit on a different sound card. Resetting the sound card choice, I'd sent it to the SC used for PSK transmit tones. 73 de Brian/K3KO On 12/25/2013 17:28, Brian Alsop wrote: > I was using the K3 today. The VOX kept cycling to transmit and back > with no voice input. > > Sounded like an easy problem to fix. Just touch up the antivox. > > Nope. > > Listening in the monitor, there is a rushing sound with clicking (like > fans in the background or something with a superimposed woodpecker). > Clearly that spurious noise is what was tripping the vox off/on. > > Next removing the mike plug, the rushing sound was still there. > > With no mike input where is it coming from? Unlikely to be RFI since it > is there at 1 watt. > > Setting the mike gain to zero and compression doesn't fix it. > Compression level does substantial increase or decrease it. > > Any suggestions? > > 73 de Brian/K3KO > > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2247 / Virus Database: 3658/6449 - Release Date: 12/25/13 > > ______________________________________________________________ > 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 > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2247 / Virus Database: 3658/6449 - Release Date: 12/25/13 > > ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2247 / Virus Database: 3658/6449 - Release Date: 12/25/13 ______________________________________________________________ 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 |
|
Brian,
Check in SSB mode to see if MIC + LINE has been inadvertently turned on. 73, Don W3FPR On 12/25/2013 2:30 PM, Brian Alsop wrote: > Please ignore this. I found a 300 mv SDR audio signal on line in. > > I don't understand how it got into the mic input-- it's only selected > that way for DATA A. I thought the mike/line in inputs were isolated > from one another. > > Guess not. Removing the line-in signal solved the problem. ______________________________________________________________ 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 |
