I am finally getting around to setting my KX3 Up for FT-8 and have watched several YouTube videos on setting up the KX3 and read Don Wilhelm’s excellent paper on setting up Elecraft radios for digital modes (Tnx, Don).
My hang up is the radio settings tab in WSJT-X: baud rate, data bits, stop bits, PTT, etc. Any help would be appreciated! Tnx & 73, Cary, K4TM H3cary at GMail dot Com Sent from Clovelly Cottage II, home of amateur radio station K4TM and the most creative Sue Cary, in the foothills of the beautiful Blue Ridge mountains of Virginia. ______________________________________________________________ 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] |
My current wsjt-x settings on my mac for my kx3 are:
38400,8,1,hw cat.data/pkt, rig On Wed, Aug 26, 2020 at 12:50 PM Hunsdon Cary III <[hidden email]> wrote: > I am finally getting around to setting my KX3 Up for FT-8 and have watched > several YouTube videos on setting up the KX3 and read Don Wilhelm’s > excellent paper on setting up Elecraft radios for digital modes (Tnx, Don). > > My hang up is the radio settings tab in WSJT-X: baud rate, data bits, > stop bits, PTT, etc. Any help would be appreciated! > Tnx & 73, > Cary, K4TM > H3cary at GMail dot Com > > Sent from Clovelly Cottage II, home of amateur radio station K4TM and the > most creative Sue Cary, in the foothills of the beautiful Blue Ridge > mountains of Virginia. > ______________________________________________________________ > 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] -- Scott Small ______________________________________________________________ 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 Hunsdon Cary III
I've had good luck setting up my KX3 for FT-8., but it took awhile. I
used several good sources which I'm sure other will point you to. But here's my current issue: I'm regularly getting FT-8 QSOs on 40m, 20m, and 10 m with no problems. The other night I decided to try 17m. My Windoze computer replied "USB device not recognized." HUH? I been using the KX3USB and a cheap sound card in a very simple set up. Any ideas why the PC reacts this way to 17m? I seem to be transmitting and receiving fine on 17m. Does it matter? david KC1DNY KX3 #08651 On 8/26/2020 3:49 PM, Hunsdon Cary III wrote: > I am finally getting around to setting my KX3 Up for FT-8 and have watched several YouTube videos on setting up the KX3 and read Don Wilhelm’s excellent paper on setting up Elecraft radios for digital modes (Tnx, Don). > > My hang up is the radio settings tab in WSJT-X: baud rate, data bits, stop bits, PTT, etc. Any help would be appreciated! > Tnx & 73, > Cary, K4TM > H3cary at GMail dot Com > > Sent from Clovelly Cottage II, home of amateur radio station K4TM and the most creative Sue Cary, in the foothills of the beautiful Blue Ridge mountains of Virginia. > ______________________________________________________________ > 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] |
David,
It is a mystery why the computer reports that message only on 17 meters. There should be no band dependency for the USB connection. 73, Don W3FPR On 8/26/2020 7:02 PM, David Haines wrote: > I've had good luck setting up my KX3 for FT-8., but it took awhile. I > used several good sources which I'm sure other will point you to. But > here's my current issue: > > I'm regularly getting FT-8 QSOs on 40m, 20m, and 10 m with no problems. > The other night I decided to try 17m. My Windoze computer replied "USB > device not recognized." HUH? > ______________________________________________________________ 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] |
Here are more details:
All seems to be working fine on 160m-10m except for 17m, so KX3 VFO is at 18.100 for the rest of this discussion. Without WSJT-X running, ATU finds a 1.1 match and TUNE button on KX3 works as expected. With WSJT-X running, using the WSJT-X TUNE button causes the following: 1. KXPA100 power LED's light from left to right _twice_, in synchronization with a musical ringing that rises in frequency, then settle down quietly to about 100W. 2. Around the same time Windows reports "USB device not recognized" and the mouse cursor disappears. At this point different things can happen: Maybe the cursor comes back and I can stop the TUNE at WSJT-X. Maybe it doesn't and I have to shut off the KX3 with XMIT button. Sometimes the PC freezes and needs a hard reset. 3. The KXPA100 fault table lists no faults. Anybody seen anything like this? david, KC1DNY, KX3 #08651 On 8/26/2020 7:59 PM, Don Wilhelm wrote: > David, > > It is a mystery why the computer reports that message only on 17 > meters. There should be no band dependency for the USB connection. > > 73, > Don W3FPR > > On 8/26/2020 7:02 PM, David Haines wrote: >> I've had good luck setting up my KX3 for FT-8., but it took awhile. I >> used several good sources which I'm sure other will point you to. But >> here's my current issue: >> >> I'm regularly getting FT-8 QSOs on 40m, 20m, and 10 m with no >> problems. The other night I decided to try 17m. My Windoze computer >> replied "USB device not recognized." HUH? >> 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] |
Sounds like you have RF getting in somewhere. Given that the PC sometimes loses it’s mind, I’d look there first. Do you have ferrites on the various connections going to the PC?
Grant NQ5T > On Aug 27, 2020, at 12:41 PM, David Haines <[hidden email]> wrote: > > Here are more details: > > All seems to be working fine on 160m-10m except for 17m, so KX3 VFO is at 18.100 for the rest of this discussion. > > Without WSJT-X running, ATU finds a 1.1 match and TUNE button on KX3 works as expected. > > With WSJT-X running, using the WSJT-X TUNE button causes the following: > > 1. KXPA100 power LED's light from left to right _twice_, in synchronization with a musical ringing that rises in frequency, then settle down quietly to about 100W. > > 2. Around the same time Windows reports "USB device not recognized" and the mouse cursor disappears. At this point different things can happen: Maybe the cursor comes back and I can stop the TUNE at WSJT-X. Maybe it doesn't and I have to shut off the KX3 with XMIT button. Sometimes the PC freezes and needs a hard reset. > > 3. The KXPA100 fault table lists no faults. > > Anybody seen anything like this? > > david, KC1DNY, KX3 #08651 > > ______________________________________________________________ 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 David Haines
David,
As someone else suggested, it sounds a lot like RF feedback on 17m. Try operating into a dummy load to see if the same thing happens - if not, get out the ferrites. 73, Don W3FPR On 8/27/2020 12:41 PM, David Haines wrote: > > Here are more details: > > All seems to be working fine on 160m-10m except for 17m, so KX3 VFO is > at 18.100 for the rest of this discussion. > > Without WSJT-X running, ATU finds a 1.1 match and TUNE button on KX3 > works as expected. > > With WSJT-X running, using the WSJT-X TUNE button causes the following: > > 1. KXPA100 power LED's light from left to right _twice_, in > synchronization with a musical ringing that rises in frequency, then > settle down quietly to about 100W. > > 2. Around the same time Windows reports "USB device not recognized" > and the mouse cursor disappears. At this point different things can > happen: Maybe the cursor comes back and I can stop the TUNE at > WSJT-X. Maybe it doesn't and I have to shut off the KX3 with XMIT > button. Sometimes the PC freezes and needs a hard reset. > > ______________________________________________________________ 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] |
Agreed. If you have a bad enough match, and it isn't choked, you can
certainly get enough RF in the shack to cause havoc. I have some bands I can't use my trackpad *inside my laptop* during full-power ft8 transmit, because I haven't set up proper antennas for that band. Scott AD6YT On Thu, Aug 27, 2020 at 10:21 AM Don Wilhelm <[hidden email]> wrote: > David, > > As someone else suggested, it sounds a lot like RF feedback on 17m. > Try operating into a dummy load to see if the same thing happens - if > not, get out the ferrites. > > 73, > Don W3FPR > > On 8/27/2020 12:41 PM, David Haines wrote: > > > > Here are more details: > > > > All seems to be working fine on 160m-10m except for 17m, so KX3 VFO is > > at 18.100 for the rest of this discussion. > > > > Without WSJT-X running, ATU finds a 1.1 match and TUNE button on KX3 > > works as expected. > > > > With WSJT-X running, using the WSJT-X TUNE button causes the following: > > > > 1. KXPA100 power LED's light from left to right _twice_, in > > synchronization with a musical ringing that rises in frequency, then > > settle down quietly to about 100W. > > > > 2. Around the same time Windows reports "USB device not recognized" > > and the mouse cursor disappears. At this point different things can > > happen: Maybe the cursor comes back and I can stop the TUNE at > > WSJT-X. Maybe it doesn't and I have to shut off the KX3 with XMIT > > button. Sometimes the PC freezes and needs a hard reset. > > > > > > ______________________________________________________________ > 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] -- Scott Small ______________________________________________________________ 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 Don Wilhelm
Don:
Problem goes away when I reduce to 20W, the maximum for my dummy load. I just put ferrites on mouse wires, keyboard wires, and sound wires and nothing changed. I guess I could add more, but ... . Maybe my best solution is to go to wireless mouse and keyboard. I intentionally used wired because my cybersecurity son is against wireless... . Still doesn't explain the funny noise from the KXP100, does it? david KC1DNY On 8/27/2020 1:20 PM, Don Wilhelm wrote: > David, > > As someone else suggested, it sounds a lot like RF feedback on 17m. > Try operating into a dummy load to see if the same thing happens - if > not, get out the ferrites. > > 73, > Don W3FPR > > On 8/27/2020 12:41 PM, David Haines wrote: >> >> Here are more details: >> >> All seems to be working fine on 160m-10m except for 17m, so KX3 VFO >> is at 18.100 for the rest of this discussion. >> >> Without WSJT-X running, ATU finds a 1.1 match and TUNE button on KX3 >> works as expected. >> >> With WSJT-X running, using the WSJT-X TUNE button causes the following: >> >> 1. KXPA100 power LED's light from left to right _twice_, in >> synchronization with a musical ringing that rises in frequency, then >> settle down quietly to about 100W. >> >> 2. Around the same time Windows reports "USB device not recognized" >> and the mouse cursor disappears. At this point different things can >> happen: Maybe the cursor comes back and I can stop the TUNE at >> WSJT-X. Maybe it doesn't and I have to shut off the KX3 with XMIT >> button. Sometimes the PC freezes and needs a hard reset. >> >> > ______________________________________________________________ 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] |
Sometimes, a line or cable is just the right fraction of a specific wavelength to act as an efficient antenna, and RF will find it's way in.
With the digimodes your soundcard is involved, so if you're getting a 'funny noise', that's where I'd look - 73 and good DX de Mike, K6MKF, NCDXC Secretary > -----Original Message----- > From: [hidden email] <[hidden email]> > On Behalf Of David Haines > Sent: Thursday, August 27, 2020 10:32 > To: [hidden email]; [hidden email] > Subject: Re: [Elecraft] KX3 radio settings for WSJT-X > > Don: > > Problem goes away when I reduce to 20W, the maximum for my dummy load. > I just put ferrites on mouse wires, keyboard wires, and sound wires and nothing > changed. I guess I could add more, but ... . > Maybe my best solution is to go to wireless mouse and keyboard. I intentionally > used wired because my cybersecurity son is against wireless... . > > Still doesn't explain the funny noise from the KXP100, does it? > > david KC1DNY > > On 8/27/2020 1:20 PM, Don Wilhelm wrote: > > David, > > > > As someone else suggested, it sounds a lot like RF feedback on 17m. > > Try operating into a dummy load to see if the same thing happens - if > > not, get out the ferrites. > > > > 73, > > Don W3FPR > > > > On 8/27/2020 12:41 PM, David Haines wrote: > >> > >> Here are more details: > >> > >> All seems to be working fine on 160m-10m except for 17m, so KX3 VFO > >> is at 18.100 for the rest of this discussion. > >> > >> Without WSJT-X running, ATU finds a 1.1 match and TUNE button on KX3 > >> works as expected. > >> > >> With WSJT-X running, using the WSJT-X TUNE button causes the following: > >> > >> 1. KXPA100 power LED's light from left to right _twice_, in > >> synchronization with a musical ringing that rises in frequency, then > >> settle down quietly to about 100W. > >> > >> 2. Around the same time Windows reports "USB device not recognized" > >> and the mouse cursor disappears. At this point different things can > >> happen: Maybe the cursor comes back and I can stop the TUNE at > >> WSJT-X. Maybe it doesn't and I have to shut off the KX3 with XMIT > >> button. Sometimes the PC freezes and needs a hard reset. > >> > >> > > > > ______________________________________________________________ > 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] |
On 8/27/2020 10:39 AM, Mike Flowers wrote:
> Sometimes, a line or cable is just the right fraction of a specific wavelength to act as an efficient antenna, and RF will find it's way in. These issues are often prevented simply by practicing the proper bonding within the station, providing a counterpoise for any end-fed antennas (verticals, random wires), and using an effective ferrite choke at all antenna feedpoints. The feedpoint is where the feedline connects to the antenna (up in the air, or at the end of the end-fed wire). Without this choke, your feedline, and everything it is connected to, including stuff in your shack and AC wiring, is carrying antenna current. Note that non-resonant antennas, especially those fed with 2-wire line, cannot be effectively choked. Effective chokes you can build are here. http://k9yc.com/2018Cookbook.pdf Do NOT be a sucker for commercially made chokes, including those from Balun Designs, Palomar, and most other ham vendors. They won't blow up, mainly because they aren't doing anything useful. 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 Message delivered to [hidden email] |
In reply to this post by David Haines
I suspect we should both be working on improving our antennas/matching
rather than adding more chokes inside the shack (didn't work for me either). Scott AD6YT On Thu, Aug 27, 2020 at 10:34 AM David Haines <[hidden email]> wrote: > Don: > > Problem goes away when I reduce to 20W, the maximum for my dummy load. > I just put ferrites on mouse wires, keyboard wires, and sound wires and > nothing changed. I guess I could add more, but ... . > Maybe my best solution is to go to wireless mouse and keyboard. I > intentionally used wired because my cybersecurity son is against > wireless... . > > Still doesn't explain the funny noise from the KXP100, does it? > > david KC1DNY > > On 8/27/2020 1:20 PM, Don Wilhelm wrote: > > David, > > > > As someone else suggested, it sounds a lot like RF feedback on 17m. > > Try operating into a dummy load to see if the same thing happens - if > > not, get out the ferrites. > > > > 73, > > Don W3FPR > > > > On 8/27/2020 12:41 PM, David Haines wrote: > >> > >> Here are more details: > >> > >> All seems to be working fine on 160m-10m except for 17m, so KX3 VFO > >> is at 18.100 for the rest of this discussion. > >> > >> Without WSJT-X running, ATU finds a 1.1 match and TUNE button on KX3 > >> works as expected. > >> > >> With WSJT-X running, using the WSJT-X TUNE button causes the following: > >> > >> 1. KXPA100 power LED's light from left to right _twice_, in > >> synchronization with a musical ringing that rises in frequency, then > >> settle down quietly to about 100W. > >> > >> 2. Around the same time Windows reports "USB device not recognized" > >> and the mouse cursor disappears. At this point different things can > >> happen: Maybe the cursor comes back and I can stop the TUNE at > >> WSJT-X. Maybe it doesn't and I have to shut off the KX3 with XMIT > >> button. Sometimes the PC freezes and needs a hard reset. > >> > >> > > > > ______________________________________________________________ > 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] -- Scott Small ______________________________________________________________ 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 Jim Brown-10
On 8/27/2020 11:01 AM, Jim Brown wrote:
> These issues are often prevented simply by practicing the proper bonding > within the station, I failed to provide this link to slides for talks I've done at Pacificon, Visalia, and to several local clubs. http://k9yc.com/GroundingAndAudio.pdf This material is also well covered in N0AX's excellent ARRL book on the topic, to which I contributed. 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 Message delivered to [hidden email] |
In reply to this post by Tox
On 8/27/2020 11:01 AM, Tox wrote:
> I suspect we should both be working on improving our antennas/matching > rather than adding more chokes inside the shack (didn't work for me either). YES! 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 Message delivered to [hidden email] |
And thanks for your tips - I did try to improve ground bonding, but it
still floats differently because I haven't gone far enough, and since chokes on my feedline are at the amp end, instead of the untuned iintentional radiator 30' above me.....I shouldn't be surprised :) Scott On Thu, Aug 27, 2020 at 11:15 AM Jim Brown <[hidden email]> wrote: > On 8/27/2020 11:01 AM, Tox wrote: > > I suspect we should both be working on improving our antennas/matching > > rather than adding more chokes inside the shack (didn't work for me > either). > > YES! > > 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 > Message delivered to [hidden email] > -- Scott Small ______________________________________________________________ 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 David Haines
That is clearly a case of RFI; the USB connection is 'sensitive' at that
frequency range. Your clue is: " then settle down quietly to about 100W. 2. Around the same time Windows reports "USB device not recognized" and the mouse cursor disappears. " If it doesn't happen at low wattage but does at higher is your hint; you're getting RF back into the shack, which is never a good thing. Presuming that ALL your equipment is properly bonded AND grounded (not the same thing), adding some ferrite to the cabling (begin with the USB cable) would be a good place to start. If you are not completely bonded and grounded, start there first (it can also lower the noise floor so you can hear better too). 73, Rick NK7I On 8/27/2020 9:41 AM, David Haines wrote: > Here are more details: > > All seems to be working fine on 160m-10m except for 17m, so KX3 VFO is > at 18.100 for the rest of this discussion. > > Without WSJT-X running, ATU finds a 1.1 match and TUNE button on KX3 > works as expected. > > With WSJT-X running, using the WSJT-X TUNE button causes the following: > > 1. KXPA100 power LED's light from left to right _twice_, in > synchronization with a musical ringing that rises in frequency, then > settle down quietly to about 100W. > > 2. Around the same time Windows reports "USB device not recognized" > and the mouse cursor disappears. At this point different things can > happen: Maybe the cursor comes back and I can stop the TUNE at > WSJT-X. Maybe it doesn't and I have to shut off the KX3 with XMIT > button. Sometimes the PC freezes and needs a hard reset. > > 3. The KXPA100 fault table lists no faults. > > Anybody seen anything like this? > > david, KC1DNY, KX3 #08651 > > > On 8/26/2020 7:59 PM, Don Wilhelm wrote: >> David, >> >> It is a mystery why the computer reports that message only on 17 >> meters. There should be no band dependency for the USB connection. >> >> 73, >> Don W3FPR >> >> On 8/26/2020 7:02 PM, David Haines wrote: >>> I've had good luck setting up my KX3 for FT-8., but it took awhile. >>> I used several good sources which I'm sure other will point you to. >>> But here's my current issue: >>> >>> I'm regularly getting FT-8 QSOs on 40m, 20m, and 10 m with no >>> problems. The other night I decided to try 17m. My Windoze computer >>> replied "USB device not recognized." HUH? >>> > ______________________________________________________________ > 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 k6mkf
I checked carefully and the "funny noise" is definitely from the
KXPA100. It's unlike the relays switching to find a match, but more like a ringing, increasing in frequency. Just twice. However I'm now convinced that my problem is RFI, thanks to all for the great advice. Oh, and all my equipment is carefully bonded, EXCEPT the darned PC. OK, I'll do that next. david KC1DNY On 8/27/2020 1:39 PM, Mike Flowers wrote: > Sometimes, a line or cable is just the right fraction of a specific wavelength to act as an efficient antenna, and RF will find it's way in. > > With the digimodes your soundcard is involved, so if you're getting a 'funny noise', that's where I'd look > > - 73 and good DX de Mike, K6MKF, NCDXC Secretary > >> -----Original Message----- >> From: [hidden email] <[hidden email]> >> On Behalf Of David Haines >> Sent: Thursday, August 27, 2020 10:32 >> To: [hidden email]; [hidden email] >> Subject: Re: [Elecraft] KX3 radio settings for WSJT-X >> >> Don: >> >> Problem goes away when I reduce to 20W, the maximum for my dummy load. >> I just put ferrites on mouse wires, keyboard wires, and sound wires and nothing >> changed. I guess I could add more, but ... . >> Maybe my best solution is to go to wireless mouse and keyboard. I intentionally >> used wired because my cybersecurity son is against wireless... . >> >> Still doesn't explain the funny noise from the KXP100, does it? >> >> david KC1DNY >> >> On 8/27/2020 1:20 PM, Don Wilhelm wrote: >>> David, >>> >>> As someone else suggested, it sounds a lot like RF feedback on 17m. >>> Try operating into a dummy load to see if the same thing happens - if >>> not, get out the ferrites. >>> >>> 73, >>> Don W3FPR >>> >>> On 8/27/2020 12:41 PM, David Haines wrote: >>>> Here are more details: >>>> >>>> All seems to be working fine on 160m-10m except for 17m, so KX3 VFO >>>> is at 18.100 for the rest of this discussion. >>>> >>>> Without WSJT-X running, ATU finds a 1.1 match and TUNE button on KX3 >>>> works as expected. >>>> >>>> With WSJT-X running, using the WSJT-X TUNE button causes the following: >>>> >>>> 1. KXPA100 power LED's light from left to right _twice_, in >>>> synchronization with a musical ringing that rises in frequency, then >>>> settle down quietly to about 100W. >>>> >>>> 2. Around the same time Windows reports "USB device not recognized" >>>> and the mouse cursor disappears. At this point different things can >>>> happen: Maybe the cursor comes back and I can stop the TUNE at >>>> WSJT-X. Maybe it doesn't and I have to shut off the KX3 with XMIT >>>> button. Sometimes the PC freezes and needs a hard reset. >>>> >>>> >> ______________________________________________________________ >> 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] |
Free forum by Nabble | Edit this page |