HI Dave, I felt the same way as you about the activity of some hams. I’m now mostly all the time CW. The operator are more like the old days and its more fun with the key. There’s really not much to talk about after 50 years of hamming, i received my ticket in 1964. Was so, so different back then, but there still are lots of cw op’s. The only thing I don’t like about whats happening to our great hobby , i send QSL cards and don’t get many returns. Just not the same anymore. Its a joy to receive a card and make a friend, you remember the old days. vincent, wb2pdw 73 > On Feb 15, 2016, at 3:49 PM, elecraft-requ...@mailman.qth.net wrote: > > Send Elecraft mailing list submissions to > elecraft@mailman.qth.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.qth.net/mailman/listinfo/elecraft > or, via email, send a message with subject or body 'help' to > elecraft-requ...@mailman.qth.net > > You can reach the person managing the list at > elecraft-ow...@mailman.qth.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Elecraft digest..." > > > Today's Topics: > > 1. Re: 75m (David Gilbert) > 2. Re: 75m (Richard Fjeld) > 3. Re: Microham Microkeyer II, RFI in mike with my K3 > (bernhard.ho...@bmw.de) > 4. Re: Microham Microkeyer II, RFI in mike with my K3 (Jim Brown) > 5. Re: K3 KIO3B - FSK - stereo (Ian White) > 6. Re: K3 KIO3B - FSK - stereo (Don Wilhelm) > 7. Re: setting up a kx3, when I get one. (Jerry Moore) > 8. Re: Microham Microkeyer II, RFI in mike with my K3 > (Joe Subich, W4TV) > 9. Re: K1 Low Power on 20M band once ATU is installed... > (Don Wilhelm) > 10. Re: CQ WPX RTTY Contest (David Kuechenmeister) > 11. Re: abject buffoonery (w7aqk) > 12. Re: K3 KIO3B - FSK - stereo (Richard Ferch) > 13. Re: K3 KIO3B - FSK - stereo (Ian White) > 14. Re: CQ WPX RTTY Contest (Rick Prather) > 15. Re: abject buffoonery (Eric Swartz - WA6HHQ, Elecraft) > 16. Re: 75m (Eric Swartz - WA6HHQ, Elecraft) > 17. Microham Microkeyer II, RFI in mike with my K3 (Guy Olinger K2AV) > 18. Re: PX3 /Keyboard QSO count repeat (Paul Saffren N6HZ) > 19. Re: P3 TX MON question (Paul Saffren N6HZ) > 20. (no subject) (Jeff) > 21. New Purchase Sanity Check (Michael Greb) > 22. KX3 pedestrian mobile? (John Fritze) > 23. Wanted: K2 Nifty Guide (EricJ) > 24. Re: (no subject) (Don Wilhelm) > 25. Re: New Purchase Sanity Check (Bob N3MNT) > 26. Re: PX3 /Keyboard QSO count repeat (Bob N3MNT) > 27. Re: KX3 pedestrian mobile? (Steve) > 28. Re: New Purchase Sanity Check (Don Wilhelm) > 29. Re: Wanted: K2 Nifty Guide (Don Wilhelm) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 14 Feb 2016 22:24:52 -0700 > From: David Gilbert <xda...@cis-broadband.com> > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] 75m > Message-ID: <56c16124.1080...@cis-broadband.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > I will have been a ham for 50 years next year, and I believe I can say > with some authority that the average operator of today is no worse than > the ones I came across back then. Our hobby is not free of whackos any > more than general society is, and if anything we had to suffer more of > them 50 years ago when ham radio was actually a somewhat mainstream > communication medium. > > I don't think ham radio has changed as much as you might have. > > Dave AB7E > > > > On 2/14/2016 4:09 PM, Tom Fitzgerald via Elecraft wrote: >> "I'm dismayed by much of what I hear on 75. I think one of the best behaved >> bands is 17." Bob >> >> Many of the same colorful characters on 75m make regular appearances on 40m >> & 20m as well. Fact is, IMO of course, I hear the "stuff" on every band & >> the local repeaters. The hobby just isn't what it use to be anymore mostly >> because the operators today aren't the operators of yesteryear. Anyone wanna >> buy an exquisite station with very low hours that's rarely in use these >> days???? I've lost all interest in the hobby. View it on my QRZ'd page & >> email me if interested. >> >> 73, >> kd0bcf >> >> "We are just an advanced breed of monkeys on a minor planet of a >> very average star. But we can understand the Universe. That makes us >> something very special." -Stephen Hawking. >> >> "Do not lose time on daily trivialities. Do not dwell on petty detail. For >> all of these things melt away and drift apart within the obscure traffic of >> time. Live well and live broadly. You are alive and living now. Now is the >> envy of all of the dead." -Emily clone circa 2242 >> >> >> >> >> ______________________________________________________________ >> 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 >> Message delivered to xda...@cis-broadband.com >> > > > > ------------------------------ > > Message: 2 > Date: Mon, 15 Feb 2016 00:01:33 -0600 > From: Richard Fjeld <rpfj...@outlook.com> > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] 75m > Message-ID: <blu436-smtp87a5782c3b45e1bf4b8366bf...@phx.gbl> > Content-Type: text/plain; charset="windows-1252"; format=flowed > > It doesn't help that the FCC is not monitoring the bands like they used > to do. > > Dick, n0ce > > On 2/14/2016 11:24 PM, David Gilbert wrote: >> >> I will have been a ham for 50 years next year, and I believe I can say >> with some authority that the average operator of today is no worse >> than the ones I came across back then. Our hobby is not free of >> whackos any more than general society is, and if anything we had to >> suffer more of them 50 years ago when ham radio was actually a >> somewhat mainstream communication medium. >> >> I don't think ham radio has changed as much as you might have. >> >> Dave AB7E >> > > > > ------------------------------ > > Message: 3 > Date: Mon, 15 Feb 2016 07:20:35 +0000 > From: <bernhard.ho...@bmw.de> > To: <li...@subich.com>, <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] Microham Microkeyer II, RFI in mike with my K3 > Message-ID: <67E5CDC47D8B374AAE23787EF65563F2458FBF@smucm55b> > Content-Type: text/plain; charset="utf-8" > > Dear all, > > just an update..the Microham Microkeyer II has definitely a problem with RF! > I replaced the Microkeyer with a homebrew USB and soundcard interface (Built > in 2008) and made new cable distribution box..And the problems are gone. > > I have S-NO 280 on the microkeyer..hope the newer ones are better. But > definitely not my kind of solution for that cost! > > 73s > Bernie > DL5RDP > > -----Urspr?ngliche Nachricht----- > Von: Joe Subich, W4TV [mailto:li...@subich.com] > Gesendet: Freitag, 12. Februar 2016 14:15 > An: elecraft@mailman.qth.net > Betreff: Re: [Elecraft] Microham Microkeyer II, RFI in mike with my K3 > > >> As I recall, I used pin 7 for the mic ground and pin 8 for the PTT >> ground. In a brief test it worked ok into a dummy load. Is this not >> correct? > > That is correct although with the K3/K3S since the Elecraft mic RFI > change it should not matter (both pin 7 and pin 8 are connected to > the "ground" foil on the front panel circuit board). > > Early K3 front panels included an RF choke in the mic *and* PTT returns > which made the "pin 1 problem" much worse. With the RF choke removed > (bypassed) the issue is significantly reduced but there may still be a > problem if the overall station installation has any "RF on the coax." > > 73, > > ... Joe, W4TV > > > On 2/12/2016 7:59 AM, j...@kk9a.com wrote: >> This week I wired rewired my MicroHAM Micro2R cables for K3S's. As I >> recall, I used pin 7 for the mic ground and pin 8 for the PTT ground. In a >> brief test it worked ok into a dummy load. Is this not correct? >> >> John KK9A >> > > > ------------------------------ > > Message: 4 > Date: Mon, 15 Feb 2016 00:07:14 -0800 > From: Jim Brown <j...@audiosystemsgroup.com> > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] Microham Microkeyer II, RFI in mike with my K3 > Message-ID: <56c18732.2070...@audiosystemsgroup.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > On Sun,2/14/2016 11:20 PM, bernhard.ho...@bmw.de wrote: >> just an update..the Microham Microkeyer II has definitely a problem with RF! > > Without diving into the details, I helped W6OAT chase down RFI issues in > his station. He had a MicroHam box with an "interface" to the radio that > was a jumble of wires. Virtually NO attention had been paid to the > fundamental concept of a transmission line in the interface between it > and the radio. While that is acceptable at baseband (audio), it is > monumentally foolish when RF is present (i.e. an antenna on the roof). > > Current flows in loops, whether at DC or at RF, and the loops form both > antennas and magnetic loops whose coupling is proportional to the loop > area. In the near field, magnetic coupling dominates, so the loop area > can be a VERY big deal. EVERY signal path between devices must be > treated as a transmission line of RFI is a potential issue. That means > EVERY signal path should be a twisted pair or a coaxial pair, so that > the path forms a transmission line. Any interface that does not do this > is an invitation to RFI if the antenna is close enough, or if the power > is high enough, or both. > > This is NOT an indictment of Microham -- at a CQP expedition a few years > ago, a team member showed up with an interface betweeen is radio and his > amp to key the amp that was an RCA to RCA cable with a single wire, no > shield. Chassis to chassis was depended on for the return. That works > fine at DC to key the amp, but the resulting current loop area gives > that circuit VERY STRONG coupling to an RF field, both as a magnetic > circuit and as an antenna. > > Noted RFI guru Henry Ott talks about understanding where ALL the current > flows, which is revealed by "the hidden schematic lurking behind the > ground symbol" that causes most issues with RFI and crosstalk. > > 73, Jim K9YC > > > ------------------------------ > > Message: 5 > Date: Mon, 15 Feb 2016 11:42:32 -0000 > From: "Ian White" <gm3...@ifwtech.co.uk> > To: "'Richard Ferch'" <ve3...@storm.ca>, <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] K3 KIO3B - FSK - stereo > Message-ID: <005301d167e5$fab96200$f02c2600$@co.uk> > Content-Type: text/plain; charset="us-ascii" > > VE3KI wrote: >> >> Also, make sure that the USB Audio Codec is not selected as the Default >> Device or the Default Communications Device - these should both be set >> to the motherboard sound card in your PC. > > Please could you explain the reasons for that? > > Thanks for the QSO at the weekend (with GM3W). > > > 73 from Ian GM3SEK > > >> -----Original Message----- >> From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of >> Richard Ferch >> Sent: 12 February 2016 21:54 >> To: elecraft@mailman.qth.net >> Subject: Re: [Elecraft] K3 KIO3B - FSK - stereo >> >> Here is something to check: >> >> Right-click the speaker icon in the Task Bar and select Recording >> devices. In the Sound window select the USB Audio Codec and click on >> Properties. In the Properties window click on the Advanced tab and > check >> the Default Format. If it is set to 1 channel, ... change it to 2 >> channel, ... . >> >> Also, make sure that the USB Audio Codec is not selected as the Default >> Device or the Default Communications Device - these should both be set >> to the motherboard sound card in your PC. >> >> You should see main RX audio in the left channel. If the subRX is off, >> you might see a bit of leakage from the left channel in the right >> channel, but if the subRX is on you should only see subRX audio. When >> you are transmitting, if your Monitor level is non-zero you should see >> the transmitted signal in both channels. >> >> 73, >> Rich VE3KI >> >> >> N2TK wrote: >> >>> Trying to setup the CODEC on the KIO3B. Is it stereo that it will > allow me >>> to do what I am presently doing for two channels? >>> >>> When I select Microphone (4-USB Audio CODEC) for both MMTTY's, I get >> the >>> same signal on both MMTTY's. The second receiver has no impact. >> >> ______________________________________________________________ >> 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 >> Message delivered to gm3...@ifwtech.co.uk > > > > ------------------------------ > > Message: 6 > Date: Mon, 15 Feb 2016 06:58:12 -0500 > From: Don Wilhelm <w3...@embarqmail.com> > To: Ian White <gm3...@ifwtech.co.uk>, 'Richard Ferch' > <ve3...@storm.ca>, elecraft@mailman.qth.net > Subject: Re: [Elecraft] K3 KIO3B - FSK - stereo > Message-ID: <56c1bd54.9090...@embarqmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Ian, > > The operating system plays its sounds through the default soundcard. > You really don't want to transmit those sounds on the air. > > 73, > Don W3FPR > > On 2/15/2016 6:42 AM, Ian White wrote: >> VE3KI wrote: >>> Also, make sure that the USB Audio Codec is not selected as the Default >>> Device or the Default Communications Device - these should both be set >>> to the motherboard sound card in your PC. >> Please could you explain the reasons for that? >> >> > > > > ------------------------------ > > Message: 7 > Date: Mon, 15 Feb 2016 07:25:32 -0500 > From: "Jerry Moore" <je...@carolinaheli.com> > To: "'a45wg'" <t...@sy-edm.com>, "'Paul Artman'" <kg7...@yahoo.com> > Cc: <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] setting up a kx3, when I get one. > Message-ID: <009901d167eb$f8af0450$ea0d0cf0$@carolinaheli.com> > Content-Type: text/plain; charset="UTF-8" > > The Raspberry Pi runs < 1A at +5vdc and does logging/digital with FLDIGI. > I've not played with the small touch screens available but there's anything > from 2" up to 10" screens. I don?t run portable yet so my screen is an old > 12" flat cpu screen. I'm considering a 7" touch screen but I've not found any > good SHIELDED water proof enclosures for the pi+Screen. I just ordered the Pi > 2 and a metal case. We'll see what develops. > > Jerry Moore > CDXA, INDEXA, SKCC, Fists > AE4PB, K3S - S.N. 010324 > http://www.qrz.com/db/AE4PB > An Amateur is - Considerate, Loyal, Progressive, Friendly, Balanced, and > Patriotic. > > -----Original Message----- > From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of a45wg > Sent: Sunday, February 14, 2016 11:48 PM > To: Paul Artman > Cc: elecraft@mailman.qth.net > Subject: Re: [Elecraft] setting up a kx3, when I get one. > > The RasberryPI - will work to the KX3. I have used mine on and off for some > development stuff. > > Portable will be an issue - unless you have a very small screen for logging > (I personally use a school notebook - and just retype when I get home). What > ever your choice - Raspberry/Phablet/Notebook/Laptop/Road-Warrior battery > life will be your governing issue. It seems pointless to me to drag a 14V > power source just to power a laptop (school notebook requires even less > wattage the the KX3) - use those stored Watts to radiate a signal. > > The KX3 - will do digital modes very well - so even /P you do not need a > computer (I would not suggest you try and do contests without one mind you) - > you just need to be able to send Morse (it is amazing to hear the PSK/RTTY > being generated). > > You could do some large Macro?s (using the KX3 Utility) and not bother with > most of the CW - but you will always need to say the other parties call-sign > etc. And soon you will want to join the fun of CW operating (which the KX3 > does amazingly well also) > > Whatever you choose the KX3 - is a great rig?. and so similar to the K3-S it > makes switching between them almost seamless. > > Good > > > >> On 14 Feb 2016, at 13:14, Paul Artman via Elecraft >> <elecraft@mailman.qth.net> wrote: >> >> Planning. On a kx3, when I get the $. I am wandering if I can get by with a >> raspberry pi, and my kindle tablet, or will need a laptop. I want to do >> dxing, and some digital. Portable setup stuf. >> >> Sent from Yahoo Mail on Android >> ______________________________________________________________ >> 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 Message delivered to >> a4...@sy-edm.com > > ______________________________________________________________ > 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 Message > delivered to je...@carolinaheli.com > > > > ------------------------------ > > Message: 8 > Date: Mon, 15 Feb 2016 08:24:52 -0500 > From: "Joe Subich, W4TV" <li...@subich.com> > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] Microham Microkeyer II, RFI in mike with my K3 > Message-ID: <56c1d1a4.2010...@subich.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > >> just an update..the Microham Microkeyer II has definitely a problem >> with RF! > > microKEYER II does not have a problem with RF. You must have an > exceptional problem with common mode RF on your feedline(s) and > that would impact *any* interface in the mic line. > >> I replaced the Microkeyer with a homebrew USB and soundcard >> interface (Built in 2008) and made new cable distribution box..And >> the problems are gone. > > Unless your homebrew interface includes mic handling circuits with > a wide range preamp, your test in meaningless. Any change in cable > length can make significant differences in RFI as it moves the high > voltage point. > > 73, > > ... Joe, W4TV > > > On 2/15/2016 2:20 AM, bernhard.ho...@bmw.de wrote: >> Dear all, >> >> just an update..the Microham Microkeyer II has definitely a problem with RF! >> I replaced the Microkeyer with a homebrew USB and soundcard >> interface (Built in 2008) and made new cable distribution box..And >> the problemsare gone. >> >> I have S-NO 280 on the microkeyer..hope the newer ones are better. But >> definitely not my kind of solution for that cost! >> >> 73s >> Bernie >> DL5RDP >> >> -----Urspr?ngliche Nachricht----- >> Von: Joe Subich, W4TV [mailto:li...@subich.com] >> Gesendet: Freitag, 12. Februar 2016 14:15 >> An: elecraft@mailman.qth.net >> Betreff: Re: [Elecraft] Microham Microkeyer II, RFI in mike with my K3 >> >> >>> As I recall, I used pin 7 for the mic ground and pin 8 for the PTT >>> ground. In a brief test it worked ok into a dummy load. Is this not >>> correct? >> >> That is correct although with the K3/K3S since the Elecraft mic RFI >> change it should not matter (both pin 7 and pin 8 are connected to >> the "ground" foil on the front panel circuit board). >> >> Early K3 front panels included an RF choke in the mic *and* PTT returns >> which made the "pin 1 problem" much worse. With the RF choke removed >> (bypassed) the issue is significantly reduced but there may still be a >> problem if the overall station installation has any "RF on the coax." >> >> 73, >> >> ... Joe, W4TV >> >> >> On 2/12/2016 7:59 AM, j...@kk9a.com wrote: >>> This week I wired rewired my MicroHAM Micro2R cables for K3S's. As I >>> recall, I used pin 7 for the mic ground and pin 8 for the PTT ground. In a >>> brief test it worked ok into a dummy load. Is this not correct? >>> >>> John KK9A >>> >> > > > ------------------------------ > > Message: 9 > Date: Mon, 15 Feb 2016 08:39:47 -0500 > From: Don Wilhelm <w3...@embarqmail.com> > To: n2...@aol.com, elecraft@mailman.qth.net > Subject: Re: [Elecraft] K1 Low Power on 20M band once ATU is > installed... > Message-ID: <56c1d523.5090...@embarqmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Michael, > > Did you change the jumper next to the BNC jack when you installed the > KAT1? If you failed to do that, the K1 would show a low power even > though it was actually developing full power output. > Make sure the ATU menu is set to CAL P. > > If you are measuring power output with an external wattmeter, then check > the soldering of the KAT1 toroid leads. You should not see any enamel > on the solder side of the board and you should see a bit of tinned lead > above the board. > > 73, > Don W3FPR > > On 2/13/2016 11:11 PM, Michael via Elecraft wrote: >> I just built a new K1 and had some problems with the output power. To make >> a long story short I >> ended up having to lower the values of R5 and R11... This brought the >> power levels up on >> the 40 M band from 1.5 to 6.5 Watts and on the 20 M band from 0.5 to 5.5 >> Watts. >> >> Figured all was well now until I installed the new ATU.... >> >> For some reason my output power on the 20M band into a 50 Ohm dummy load >> is >> only around 0.7 Watts now with the ATU installed. If I remove it - it >> goes back up to normal! >> >> Any ideas? >> >> Thanks, >> >> Michael >> n2zdb >> ______________________________________________________________ >> 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 >> Message delivered to w3...@embarqmail.com >> > > > > ------------------------------ > > Message: 10 > Date: Mon, 15 Feb 2016 13:57:06 +0000 (UTC) > From: David Kuechenmeister <n...@bellsouth.net> > To: Elecraft Discussion List <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] CQ WPX RTTY Contest > Message-ID: > <707610153.4093147.1455544626963.javamail.ya...@mail.yahoo.com> > Content-Type: text/plain; charset=UTF-8 > > I ran my K3 with the K3IOB upgrade card installed. I also have a P3 and set > it to a 10 KHz span. Before, when I used the line out as an input to Fldigi, > it seemed like there was a little more tolerance in how I tuned in on the > space signal. Now, I notice that the K3 decodes text when I get reasonably > close to the space signal, but Fldigi still needs a little more finagling to > get it decoding at all.? > I may be back to using the Xonar sound card and cables unless I can establish > a more consistent tuning procedure on the RTTY signals. > vy 73,Dave N4KD > > > > On Monday, February 15, 2016 12:22 AM, Rick Prather <rprat...@mac.com> wrote: > > > I used RUMlogNG for WPX and it worked very well. > > My set up though is a bit different than your's I think. > > I use the K3 set to FSK D? and cocoaModem as a back up.? I tune the signals > using my P3 set to about 15 Khz span and tune to the Right (space) signal. > The only repeats I needed to give didn't surprise me since I am running > only 100W to a wire. > > I found that cocoaModem was slightly better at decoding but most of my > decodeing and therefore grabbing call signs, etc. was from the RUMlogNG > display with cocoaModem used mostly as an occasional backup. > > Interestingly enough, I found a few situations, especially on weak and/or > fluttery signals, where the K3 did a much better job of decoding than > cocoaModem. > > I also spent some time running FLDIGI on the side but found it was not > nearly as good as cocoaModem or the K3 in decoding. > > Rick > K6LE > > > > > ------------------------------ > > Message: 11 > Date: Mon, 15 Feb 2016 07:34:38 -0700 > From: "w7aqk" <w7...@cox.net> > To: "Elecraft Reflector" <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] abject buffoonery > Message-ID: <697986CFD6CB41398D02227A9BA2C6A2@LAPTOPEPVQLR1I> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > Hi All, > > This is a major reason why I have almost totally abdicated usage of SSB, and > stick to CW, which is my preferred mode anyway. There I can participate in > relatively nonsense free and enjoyable rag chews with others. About the > only time we get substantial craziness on that mode is when there is some > sort of DXpedition going on. > > For the most part, I don't think that, for the most part, these clowns (I > actually have a much stronger, more profane term for them!) can even copy > CW. So, it's not much "fun" for them to jam conversations they can't even > understand. I also think that alcohol has a great deal to do with what you > hear on 75 meters. Sometimes it is completely obvious! > > I don't know about the rest of you, but I would be willing to pay a > significant additional fee, and every year if necessary, if FCC could then > do serious enforcement on the bands. I know right now they don't have any > real staff to do it. You wouldn't even need a particularly high percentage > of successful enforcement situations to generate substantially beneficial > results. Just having a real threat that such actions might be successfully > captured could be enough to put "the fear of God" into a significant number > of perpetrators. Right now, there is little, if any, risk of being caught. > So, it is like having speed limits, but no enforcement whatsoever! > > A lot of people say "just ignore" the incidents. I tend to agree with that, > since confrontation only excites the perpetrator--particularly if alcohol is > involved!!!! You can't argue or reason with a drunk! I do think recordings > could be helpful, and if you have the capability, a little "DFing" might add > some useful info if there was any place such info could be collected for > further analysis. > > I think every ham radio club in the country should take this issue > seriously. Not only should members "pledge" to avoid such conduct, they > should also agree to be actively involved in identifying it. It's hard to > believe that a number of these perpetrators aren't close enough to someone > else that they couldn't be better identified. We need to take some > responsibility ourselves for trying to reduce such infractions. That > doesn't mean direct confrontation, but serious information could be useful > to authorities. > > Just my thoughts. > > Dave W7AQK > > > > ------------------------------ > > Message: 12 > Date: Mon, 15 Feb 2016 09:42:40 -0500 > From: Richard Ferch <ve3...@storm.ca> > To: "elecraft@mailman.qth.net" <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] K3 KIO3B - FSK - stereo > Message-ID: <56c1e3e0.4060...@storm.ca> > Content-Type: text/plain; charset=utf-8; format=flowed > > Most media players use the default device. In addition to Windows > sounds, you wouldn't want sound clips from your Internet browser playing > through the radio codec, to pick an example. > > Another reason might be that if the K3S or K3+KIO3B is turned off or > disconnected from the computer, the device would disappear and Windows > would change the default to some other (possibly unpredictable) device. > > There may be yet another reason: I believe that in recent versions of > Windows, when a device is selected as the default device, Windows > routinely disables other inputs on that sound card or codec. If, for > example, the microphone input were selected as the default device, I > believe that the line input on that same card would be disabled. I don't > know whether the KIO3B codec has multiple inputs, so I don't know > whether this actually applies to it. > > 73, > Rich VE3KI > > > W3FPR wrote: > >> Ian, >> >> The operating system plays its sounds through the default soundcard. >> You really don't want to transmit those sounds on the air. >> >> 73, >> Don W3FPR >> >> On 2/15/2016 6:42 AM, Ian White wrote: >>> VE3KI wrote: >>>> Also, make sure that the USB Audio Codec is not selected as the Default >>>> Device or the Default Communications Device - these should both be set >>>> to the motherboard sound card in your PC. >>> Please could you explain the reasons for that? >>> >>> > > > > ------------------------------ > > Message: 13 > Date: Mon, 15 Feb 2016 16:09:19 -0000 > From: "Ian White" <gm3...@ifwtech.co.uk> > To: <elecraft@mailman.qth.net> > Cc: "'Richard Ferch'" <ve3...@storm.ca>, "'Don Wilhelm'" > <w3...@embarqmail.com> > Subject: Re: [Elecraft] K3 KIO3B - FSK - stereo > Message-ID: <009b01d1680b$3f491c60$bddb5520$@co.uk> > Content-Type: text/plain; charset="us-ascii" > > Many thanks to Don and to Rich. I was aware of the first reason but > hadn't been clear about the other two. > > 73 from Ian GM3SEK > > >> -----Original Message----- >> From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of >> Richard Ferch >> Sent: 15 February 2016 14:43 >> To: elecraft@mailman.qth.net >> Subject: Re: [Elecraft] K3 KIO3B - FSK - stereo >> >> Most media players use the default device. In addition to Windows >> sounds, you wouldn't want sound clips from your Internet browser > playing >> through the radio codec, to pick an example. >> >> Another reason might be that if the K3S or K3+KIO3B is turned off or >> disconnected from the computer, the device would disappear and Windows >> would change the default to some other (possibly unpredictable) device. >> >> There may be yet another reason: I believe that in recent versions of >> Windows, when a device is selected as the default device, Windows >> routinely disables other inputs on that sound card or codec. If, for >> example, the microphone input were selected as the default device, I >> believe that the line input on that same card would be disabled. I > don't >> know whether the KIO3B codec has multiple inputs, so I don't know >> whether this actually applies to it. >> >> 73, >> Rich VE3KI >> >> >> W3FPR wrote: >> >>> Ian, >>> >>> The operating system plays its sounds through the default soundcard. >>> You really don't want to transmit those sounds on the air. >>> >>> 73, >>> Don W3FPR >>> >>> On 2/15/2016 6:42 AM, Ian White wrote: >>>> VE3KI wrote: >>>>> Also, make sure that the USB Audio Codec is not selected as the > Default >>>>> Device or the Default Communications Device - these should both be > set >>>>> to the motherboard sound card in your PC. >>>> Please could you explain the reasons for that? >>>> >>>> >> >> ______________________________________________________________ >> 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 >> Message delivered to gm3...@ifwtech.co.uk > > > > ------------------------------ > > Message: 14 > Date: Mon, 15 Feb 2016 08:40:20 -0800 > From: Rick Prather <rprat...@mac.com> > Cc: Elecraft Discussion List <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] CQ WPX RTTY Contest > Message-ID: > <CAAEtO3=f-pcfjdyau4ympnc3dt3yra+npw7kggg22prwfed...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I forgot to mention that I also will set the tuning bars in cocoaModem as > close to 1275/1445 (my preferred tones) as I can and often use the XY > tuning indicator in CCM. > > BTW, CCM also has the benefit of being able to use both VFO's and tuning > for the next call while I wait for the "NR?'s and AGN?'s" to be finished > on the main receiver. That way is I have a secondary station tuned in on > the SUB I can do a quick A/B switch to work the next one. > > Rick > K6LE > > On Mon, Feb 15, 2016 at 5:57 AM, David Kuechenmeister <n...@bellsouth.net> > wrote: > >> I ran my K3 with the K3IOB upgrade card installed. I also have a P3 and >> set it to a 10 KHz span. Before, when I used the line out as an input to >> Fldigi, it seemed like there was a little more tolerance in how I tuned in >> on the space signal. Now, I notice that the K3 decodes text when I get >> reasonably close to the space signal, but Fldigi still needs a little more >> finagling to get it decoding at all. >> I may be back to using the Xonar sound card and cables unless I can >> establish a more consistent tuning procedure on the RTTY signals. >> vy 73,Dave N4KD >> >> >> >> On Monday, February 15, 2016 12:22 AM, Rick Prather <rprat...@mac.com> >> wrote: >> >> >> I used RUMlogNG for WPX and it worked very well. >> >> My set up though is a bit different than your's I think. >> >> I use the K3 set to FSK D and cocoaModem as a back up. I tune the signals >> using my P3 set to about 15 Khz span and tune to the Right (space) signal. >> The only repeats I needed to give didn't surprise me since I am running >> only 100W to a wire. >> >> I found that cocoaModem was slightly better at decoding but most of my >> decodeing and therefore grabbing call signs, etc. was from the RUMlogNG >> display with cocoaModem used mostly as an occasional backup. >> >> Interestingly enough, I found a few situations, especially on weak and/or >> fluttery signals, where the K3 did a much better job of decoding than >> cocoaModem. >> >> I also spent some time running FLDIGI on the side but found it was not >> nearly as good as cocoaModem or the K3 in decoding. >> >> Rick >> K6LE >> >> >> >> ______________________________________________________________ >> 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 >> Message delivered to rick.prat...@gmail.com >> > > > ------------------------------ > > Message: 15 > Date: Mon, 15 Feb 2016 08:51:46 -0800 > From: "Eric Swartz - WA6HHQ, Elecraft" <e...@elecraft.com> > To: w7aqk <w7...@cox.net>, Elecraft Reflector > <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] abject buffoonery > Message-ID: <56c20222.20...@elecraft.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Folks - We're drifting a bit far OT from our usual focus. As this is a > repeating > topic in many other forums,it is best covered there or in private emails. > > Let's end this thread at this time to reduce list email overload for our > readers. > > 73, > > Eric > /elecraft.com/ > > On 2/15/2016 6:34 AM, w7aqk wrote: >> Hi All, >> >> This is a major reason why I have almost totally abdicated usage of SSB, and >> stick to CW, which is my preferred mode anyway. There I can participate in >> relatively nonsense free and enjoyable rag chews with others. About the >> only >> time we get substantial craziness on that mode is when there is some sort of >> DXpedition going on. >> >> For the most part, I don't think that, for the most part, these clowns (I >> actually have a much stronger, more profane term for them!) can even copy >> CW. >> So, it's not much "fun" for them to jam conversations they can't even >> understand. I also think that alcohol has a great deal to do with what you >> hear on 75 meters. Sometimes it is completely obvious! >> >> I don't know about the rest of you, but I would be willing to pay a >> significant additional fee, and every year if necessary, if FCC could then >> do >> serious enforcement on the bands. I know right now they don't have any real >> staff to do it. You wouldn't even need a particularly high percentage of >> successful enforcement situations to generate substantially beneficial >> results. Just having a real threat that such actions might be successfully >> captured could be enough to put "the fear of God" into a significant number >> of >> perpetrators. Right now, there is little, if any, risk of being caught. So, >> it is like having speed limits, but no enforcement whatsoever! >> >> A lot of people say "just ignore" the incidents. I tend to agree with that, >> since confrontation only excites the perpetrator--particularly if alcohol is >> involved!!!! You can't argue or reason with a drunk! I do think recordings >> could be helpful, and if you have the capability, a little "DFing" might add >> some useful info if there was any place such info could be collected for >> further analysis. >> >> I think every ham radio club in the country should take this issue >> seriously. >> Not only should members "pledge" to avoid such conduct, they should also >> agree >> to be actively involved in identifying it. It's hard to believe that a >> number >> of these perpetrators aren't close enough to someone else that they couldn't >> be better identified. We need to take some responsibility ourselves for >> trying to reduce such infractions. That doesn't mean direct confrontation, >> but >> serious information could be useful to authorities. >> >> Just my thoughts. >> >> Dave W7AQK >> >> ______________________________________________________________ >> 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 >> Message delivered to eric.swa...@elecraft.com >> > > > > ------------------------------ > > Message: 16 > Date: Mon, 15 Feb 2016 08:53:15 -0800 > From: "Eric Swartz - WA6HHQ, Elecraft" <e...@elecraft.com> > To: Richard Fjeld <rpfj...@outlook.com>, elecraft@mailman.qth.net > Subject: Re: [Elecraft] 75m > Message-ID: <56c2027b.2000...@elecraft.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Ad noted in my prior post (covering the other subject line for this thread), > this OT thread is now closed in the interest of reducing list email overload > for > our readers. > > 73, > > Eric > /elecraft.com/ > > On 2/14/2016 10:01 PM, Richard Fjeld wrote: >> It doesn't help that the FCC is not monitoring the bands like they used to >> do. >> >> Dick, n0ce >> >> On 2/14/2016 11:24 PM, David Gilbert wrote: >>> >>> I will have been a ham for 50 years next year, and I believe I can say with >>> some authority that the average operator of today is no worse than the ones >>> I >>> came across back then. Our hobby is not free of whackos any more than >>> general society is, and if anything we had to suffer more of them 50 years >>> ago when ham radio was actually a somewhat mainstream communication medium. >>> >>> I don't think ham radio has changed as much as you might have. >>> >>> Dave AB7E >>> >> >> ______________________________________________________________ >> 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 >> Message delivered to eric.swa...@elecraft.com >> > > > > ------------------------------ > > Message: 17 > Date: Mon, 15 Feb 2016 12:15:06 -0500 > From: Guy Olinger K2AV <k2av....@gmail.com> > To: "bernhard.ho...@bmw.de" <bernhard.ho...@bmw.de>, Elecraft > Reflector <elecraft@mailman.qth.net> > Subject: [Elecraft] Microham Microkeyer II, RFI in mike with my K3 > Message-ID: > <canckpc2+dgvsuf-n4ly_0qe4phi2yrp-37ubfqjpgj44kd3...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi Bernie, > > If you are running QRO over your roof, your RFI proofing needs to be > perfect. Your situation is only exceeded in nastiness by being next door to > a 50 kW AM station and maybe not then. Your induced common mode RF > voltages on conductors can be double and triple the desired signal voltages > on the cables and ridiculously more than microphone voltages. > > One CAN get lucky and get by, but if one does it's only by dumb blind luck > and any change to cable routing or position and count of station equipment > can disable or polute electronic functions. > > If you succumb to the temptation to attribute the changes to the last thing > changed or moved, you will be sent down the rabbit hole to join company > with Alice and the Mad Hatter where nothing makes sense any more. This can > include complaints to manufacturers straight from Wonderland requiring > apologies afterward. Been there, done that. Know whereof I speak. > > It is quite probable that replacing the box changed cable specifics. Any > connection that is not a tenth of an ohm or less needs to be replaced or > repaired. I have no idea where you got 2 ohms as a satisfactory connection > resistance. Maybe the USB signal itself will tolerate that under > otherwise non-stressed circumstances but it's far away out of bounds for > RFI proofing. > > In your case, QRO on the roof, you need to take maximum anti-RF measures on > **ALL** conductors in the shack. Otherwise just changing orientation of > cables may remove or incite RFI, or worse makes RFI intermittent leading to > suspicions of poltergeist. > > I have finally gotten to the point where all retail audio cables need to be > replaced with soldered coax or shielded pairs with WOVEN shields. > ESPECIALLY audio cables terminated in RCA plugs which typically have the > cheapest shields known to man. No retail manufacturer is testing them for > RFI susceptibility in rooftop QRO conditions. > > There is a good selection of shielded pair and coax cable with Teflon > dielectric/insulation and woven shields easily soldered to *quality* RCA > plugs or other connectors without melting the wire. > > I know that QRO on the roof is all that's available for many folks. Just > understand that's the very stiffest possible demand on all RFI proofing > issues. No cheapies, no short cuts, no omissions allowed in the protocol. > > 73, Guy K2AV > > On Monday, February 15, 2016, <bernhard.ho...@bmw.de > <javascript:_e(%7B%7D,'cvml','bernhard.ho...@bmw.de');>> wrote: > >> Dear all, >> >> just an update..the Microham Microkeyer II has definitely a problem with >> RF! >> I replaced the Microkeyer with a homebrew USB and soundcard interface >> (Built in 2008) and made new cable distribution box..And the problems are >> gone. >> >> I have S-NO 280 on the microkeyer..hope the newer ones are better. But >> definitely not my kind of solution for that cost! >> >> 73s >> Bernie >> DL5RDP >> >> -----Urspr?ngliche Nachricht----- >> Von: Joe Subich, W4TV [mailto:li...@subich.com] >> Gesendet: Freitag, 12. Februar 2016 14:15 >> An: elecraft@mailman.qth.net >> Betreff: Re: [Elecraft] Microham Microkeyer II, RFI in mike with my K3 >> >> >>> As I recall, I used pin 7 for the mic ground and pin 8 for the PTT >>> ground. In a brief test it worked ok into a dummy load. Is this not >>> correct? >> >> That is correct although with the K3/K3S since the Elecraft mic RFI >> change it should not matter (both pin 7 and pin 8 are connected to >> the "ground" foil on the front panel circuit board). >> >> Early K3 front panels included an RF choke in the mic *and* PTT returns >> which made the "pin 1 problem" much worse. With the RF choke removed >> (bypassed) the issue is significantly reduced but there may still be a >> problem if the overall station installation has any "RF on the coax." >> >> 73, >> >> ... Joe, W4TV >> >> >> On 2/12/2016 7:59 AM, j...@kk9a.com wrote: >>> This week I wired rewired my MicroHAM Micro2R cables for K3S's. As I >>> recall, I used pin 7 for the mic ground and pin 8 for the PTT ground. In >> a >>> brief test it worked ok into a dummy load. Is this not correct? >>> >>> John KK9A >>> >> >> ______________________________________________________________ >> 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 >> Message delivered to k2av....@gmail.com > > > > -- > Sent via Gmail Mobile on my iPhone > > > ------------------------------ > > Message: 18 > Date: Mon, 15 Feb 2016 10:16:01 -0700 (MST) > From: Paul Saffren N6HZ <pa...@elecraft.com> > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] PX3 /Keyboard QSO count repeat > Message-ID: <1455556561902-7614120.p...@n2.nabble.com> > Content-Type: text/plain; charset=us-ascii > > Hi Bob, > > Starting in version 1.39 (currently available) you can put as many \c as you > want to, the number only increments once per message. In other words, the > counter value only advances once per invocation of the text message. > > > Kind regards, > > Paul > > > > -- > View this message in context: > http://elecraft.365791.n2.nabble.com/PX3-Keyboard-QSO-count-repeat-tp7614088p7614120.html > Sent from the Elecraft mailing list archive at Nabble.com. > > > ------------------------------ > > Message: 19 > Date: Mon, 15 Feb 2016 10:23:05 -0700 (MST) > From: Paul Saffren N6HZ <pa...@elecraft.com> > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] P3 TX MON question > Message-ID: <1455556985618-7614122.p...@n2.nabble.com> > Content-Type: text/plain; charset=us-ascii > > Hi Barry, > > The P3TXMON can configured to trigger by sensing the forward RF power at the > coupler. For K3 users, the P3TXMON uses internal communication with the > K3(S) . > > Kind regards, > > Paul > > > > -- > View this message in context: > http://elecraft.365791.n2.nabble.com/P3-TX-MON-question-tp7614053p7614122.html > Sent from the Elecraft mailing list archive at Nabble.com. > > > ------------------------------ > > Message: 20 > Date: Mon, 15 Feb 2016 13:17:19 -0500 > From: "Jeff" <w...@charter.net> > To: <Elecraft@mailman.qth.net> > Subject: [Elecraft] (no subject) > Message-ID: <FF7D24C51807438BA71ED9C7C55D2177@w7jwHP> > Content-Type: text/plain; charset="iso-8859-1" > > Can someone please help me understand if I am doing this correctly? I want to > RX in diversity and run split more than 10 KHz.? > > I have my main RX on 1.8245, then press split button and set the B VFO to > 1.835. Then I turn on the 2nd RX in diversity, press b-set and use the B VFO > to move it to 1.8245, narrow the filter to 400 Hz. then press b-set agn. Now > I lock the VFOs so they track. SUB and SPLIT indicators are on. Am I still > TXing on 1.835 and if so how do I know that if VFO B shows the second RX QRG? > > > Tnx es 73 Jeff W7JW > > ------------------------------ > > Message: 21 > Date: Mon, 15 Feb 2016 13:28:05 -0500 > From: Michael Greb <mich...@thegrebs.com> > To: elecraft <elecraft@mailman.qth.net> > Subject: [Elecraft] New Purchase Sanity Check > Message-ID: > <caa+max00nc4pynqkv0qcbtnkz7qe8zpysgawzlb5+5zhlek...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Ready to pull the trigger on a KX3 + PX3 + KXPA100. > > I plan on the internal tuner for the KXPA100 but I'd like the option of > working without it. If the KX3 internal tuner is installed but the KXPA100 > with internal ATU is connected will the KX3 correctly bypass its internal > tuner causing the tuner functions to operate on the KXPA100's tuner? > > Thanks > > -- > Mike Greb > 562-MIKEGRB > http://michael.thegrebs.com > > > ------------------------------ > > Message: 22 > Date: Mon, 15 Feb 2016 13:48:02 -0500 > From: John Fritze <fritzej...@gmail.com> > To: "elecraft@mailman.qth.net" <elecraft@mailman.qth.net> > Subject: [Elecraft] KX3 pedestrian mobile? > Message-ID: > <CAC2wZkZy_McoA7ntkQEo7PmbX66y9Y=xmr7wcekcxs2jaxp...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Anyone using the KX3 pedestrian mobile with the radio in front of you? > What are you holding it in? Any pictures are appreciated. Feel free to > contact direct. > > -- > John Fritze Jr > K2QY > k...@arrl.net > ACACES president 2014 > ARES ENY DEC Northern District > Hudson Div. Asst. Director > Twitter: @k2qy > 401 261 4996 (cell) > > > ------------------------------ > > Message: 23 > Date: Mon, 15 Feb 2016 10:52:43 -0800 > From: EricJ <eric_c...@hotmail.com> > To: Elecraft@mailman.qth.net > Subject: [Elecraft] Wanted: K2 Nifty Guide > Message-ID: <blu436-smtp113dc514206e8d06897e40c8e...@phx.gbl> > Content-Type: text/plain; charset="utf-8"; format=flowed > > The K2 Nifty Guide is out of print. > > Anyone have one left over from upgrading to K3? > > Please contact off the list. > > Eric > KE6US > eric_c...@hotmail.com > > > ------------------------------ > > Message: 24 > Date: Mon, 15 Feb 2016 13:56:05 -0500 > From: Don Wilhelm <w3...@embarqmail.com> > To: Jeff <w...@arrl.net>, Elecraft@mailman.qth.net > Subject: Re: [Elecraft] (no subject) > Message-ID: <56c21f45.5010...@embarqmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Jeff, > > I am not sure you want Diversity. I would suggest you turn the SUB on > (not Diversity) by tapping the SUB button (HOLD will get you into > Diversity). > > With the SUB on, tune to your receive frequency with the VFO A knob. > Then tap A > B twice to transfer the frequency, mode, etc to VFO B > Then tune with the VFO B knob to your proposed transmit frequency. > Now turn on SPLIT. Note the arrow in the display next to the TX label > to the right side now points to VFO B. That arrow points to the > frequency where you will transmit. > You will hear the main receiver in your left ear, and the right ear will > hear what is on your transmit frequency. > > If you want to use Diversity, the K3 will behave more like a single > receiver, but if using 2 antennas (one on the main and the other on the > sub), you may be able to hear better through QSB. In diversity, both > the main and the sub are controlled by the VFO A knob. > If you are in diversity and want to go split, tap the A>B button twice > and then go to SPLIT. > Move VFO B to your desired transmit frequency. > You will not be able to hear on your transmit frequency unless you hold > the REV button - while holding that button you will hear the TX > frequency (but not your RX frequency). > > I hope that helps. > > 73, > Don W3FPR > > On 2/15/2016 1:17 PM, Jeff wrote: >> Can someone please help me understand if I am doing this correctly? I want >> to RX in diversity and run split more than 10 KHz.? >> >> I have my main RX on 1.8245, then press split button and set the B VFO to >> 1.835. Then I turn on the 2nd RX in diversity, press b-set and use the B >> VFO to move it to 1.8245, narrow the filter to 400 Hz. then press b-set agn. >> Now I lock the VFOs so they track. SUB and SPLIT indicators are on. Am I >> still TXing on 1.835 and if so how do I know that if VFO B shows the second >> RX QRG? >> >> Tnx es 73 Jeff W7JW >> > > > > ------------------------------ > > Message: 25 > Date: Mon, 15 Feb 2016 11:58:41 -0700 (MST) > From: Bob N3MNT <b...@hogbytes.com> > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] New Purchase Sanity Check > Message-ID: <1455562721323-7614128.p...@n2.nabble.com> > Content-Type: text/plain; charset=us-ascii > > When the KXPA100 is on and power over 10-12 watts the internal tuner in the > KX3 is bypassed and the tuner in the amp is operational. If the > > > > -- > View this message in context: > http://elecraft.365791.n2.nabble.com/New-Purchase-Sanity-Check-tp7614124p7614128.html > Sent from the Elecraft mailing list archive at Nabble.com. > > > ------------------------------ > > Message: 26 > Date: Mon, 15 Feb 2016 12:01:42 -0700 (MST) > From: Bob N3MNT <b...@hogbytes.com> > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] PX3 /Keyboard QSO count repeat > Message-ID: <1455562902884-7614129.p...@n2.nabble.com> > Content-Type: text/plain; charset=us-ascii > > Thank You as always for fast accurate response. That is what I was looking > for. PX3 was fun to use in RTTY test this weekend. > > > > -- > View this message in context: > http://elecraft.365791.n2.nabble.com/PX3-Keyboard-QSO-count-repeat-tp7614088p7614129.html > Sent from the Elecraft mailing list archive at Nabble.com. > > > ------------------------------ > > Message: 27 > Date: Mon, 15 Feb 2016 14:13:16 -0500 > From: Steve <lawr...@woh.rr.com> > To: John Fritze <fritzej...@gmail.com> > Cc: "elecraft@mailman.qth.net" <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] KX3 pedestrian mobile? > Message-ID: <a8107cd4-6339-4875-bf8d-449f26fce...@woh.rr.com> > Content-Type: text/plain; charset=utf-8 > > John, > I don?t have photos, but liked this idea for carrying the KX3 on the chest: > - Purchase a set of end plates for the KX3. There are several sources. > - Use the slots in the end plates for a place to attach a strap to hang the > KX3 either around the neck or suspended from your pack?s shoulder straps > > 73, > Steve > aa8af > >> On Feb 15, 2016, at 1:48 PM, John Fritze <fritzej...@gmail.com> wrote: >> >> Anyone using the KX3 pedestrian mobile with the radio in front of you? >> What are you holding it in? Any pictures are appreciated. Feel free to >> contact direct. > > > > ------------------------------ > > Message: 28 > Date: Mon, 15 Feb 2016 15:44:51 -0500 > From: Don Wilhelm <w3...@embarqmail.com> > To: Michael Greb <mich...@thegrebs.com>, elecraft > <elecraft@mailman.qth.net> > Subject: Re: [Elecraft] New Purchase Sanity Check > Message-ID: <56c238c3.10...@embarqmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Mike, > > Yes, that is the way it works - and it is automatic. > > 73, > Don W3FPR > > On 2/15/2016 1:28 PM, Michael Greb wrote: >> Ready to pull the trigger on a KX3 + PX3 + KXPA100. >> >> I plan on the internal tuner for the KXPA100 but I'd like the option of >> working without it. If the KX3 internal tuner is installed but the KXPA100 >> with internal ATU is connected will the KX3 correctly bypass its internal >> tuner causing the tuner functions to operate on the KXPA100's tuner? >> >> Thanks >> > > > > ------------------------------ > > Message: 29 > Date: Mon, 15 Feb 2016 15:49:17 -0500 > From: Don Wilhelm <w3...@embarqmail.com> > To: EricJ <eric_c...@hotmail.com>, Elecraft@mailman.qth.net > Subject: Re: [Elecraft] Wanted: K2 Nifty Guide > Message-ID: <56c239cd.4060...@embarqmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Eric and anyone else interested, > > I don't have a Nifty Guide, but as an alternative, you may want to > download the K2 Quick Reference from my website www.w3fpr.com. > Look near the bottom of the opening page. > > 73, > Don W3FPR > > On 2/15/2016 1:52 PM, EricJ wrote: >> The K2 Nifty Guide is out of print. >> >> Anyone have one left over from upgrading to K3? >> > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Elecraft mailing list > Post to: Elecraft@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/elecraft > You must be a subscriber to post. > Elecraft web page: http://www.elecraft.com > > ------------------------------ > > End of Elecraft Digest, Vol 142, Issue 30 > *****************************************
______________________________________________________________ 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 Message delivered to arch...@mail-archive.com
