Re: Elecraft Digest, Vol 91, Issue 4

[I7SWX]

>________________________________
>Da: "[hidden email]" <[hidden email]>
>A: [hidden email]
>Inviato: Giovedì 3 Novembre 2011 17:00
>Oggetto: Elecraft Digest, Vol 91, Issue 4
>
>Send Elecraft mailing list submissions to
>    [hidden email]
>
>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
>    [hidden email]
>
>You can reach the person managing the list at
>    [hidden email]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Elecraft digest..."
>
>
>Today's Topics:
>
>   1. Re: USB interface (David Ferrington, M0XDF)
>   2. Re: Laptop Serial Port Card for K3 (Jim Brown)
>   3. Re: Silly question about DVK3 (Julius Fazekas n2wn)
>   4. Re: P3 - What am I observing? (Rose)
>   5. k3 Strange Problem (Joe Ford)
>   6. FS:  W2 REDUCED (Phil LaMarche)
>   7. Re: Orion I for K3 (Fred Atchley)
>   8. USB Adapters and RF (Lee Buller)
>   9. K3 DVK vs N1MM difficulties (Ralph Parker)
>  10. Re: USB Adapters and RF (Ian White GM3SEK)
>  11. Re: USB Adapters and RF (Lee Buller)
>  12. Re: K3: COM1 and COM3 question (Mike)
>  13. Re: Silly question about DVK3 (iain macdonnell - N6ML)
>  14. Re: USB Adapters and RF (Joe Subich, W4TV)
>  15. Re: USB Adapters and RF (Joe Subich, W4TV)
>  16. Re: K3: COM1 and COM3 question (Jim Dunstan)
>  17. Re: K3 Strange Problem (Guy Olinger K2AV)
>  18. Re: K3: COM1 and COM3 question (Don Wilhelm)
>  19. Re: K3: COM1 and COM3 question (David Gilbert)
>  20. Re: K3: COM1 and COM3 question (David Windisch)
>  21. Re: K3: COM1 and COM3 question (Greg)
>  22. Re: K3: COM1 and COM3 question (Jim Dunstan)
>  23. Re: K3: COM1 and COM3 question (Don Wilhelm)
>  24. Re: K3: COM1 and COM3 question (Ron D'Eau Claire)
>  25. Elecraft FS XG2 Sig Gen (Gilbert Cross)
>  26. Re: K3 Strange Problem (Joe Ford)
>  27. Re: K3 Strange Problem (W0MU Mike Fatchett)
>  28. K3 and MT63: XMIT Non-Copy (Dan Sherwood)
>  29. Remote control of a K3? (tomb18)
>  30. Re: K3 and MT63: XMIT Non-Copy (Don Wilhelm)
>  31. 160M event (Gary VK4FD)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Wed, 2 Nov 2011 16:09:52 +0000
>From: "David Ferrington, M0XDF" <[hidden email]>
>Subject: Re: [Elecraft] USB interface
>To: Ian White GM3SEK <[hidden email]>
>Cc: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>Good point Ian
>73 de M0XDF
>--
>Facts do not cease to exist because they are ignored.
>-Aldous Huxley, novelist (1894-1963)
>
>On 2 Nov 2011, at 13:51, Ian White GM3SEK wrote:
>
>> David Ferrington, M0XDF wrote:
>>> Pity the won't ship the the UK ROSH compliance I guess.
>>
>> Why do you want to ship an FTDI-based USB adapter from the USA? They are
>> available from local vendors in every major country, and they're all
>> functionally identical because they use the same FTDI chip.
>>
>> Google for: ftdi usb adapter site:uk
>>
>> FTDI is a relatively small company, still privately owned and still
>> based here in Scotland, that has become a world leader by specializing
>> in just one thing... but doing it better than anyone else.
>>
>> (Does that sound familiar?)
>>
>>
>> --
>>
>> 73 from Ian GM3SEK
>> http://www.ifwtech.co.uk/g3sek
>> ______________________________________________________________
>> 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: 2
>Date: Wed, 02 Nov 2011 09:34:48 -0700
>From: Jim Brown <[hidden email]>
>Subject: Re: [Elecraft] Laptop Serial Port Card for K3
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>On 11/2/2011 7:53 AM, edward mccann wrote:
>> Prices of new PCMCIA cards seem to run from $20 to $100 on Amazon and elsewhere. Has anyone had experience with this matter and can recommend a specific card that has worked for you without glitches?
>
>Back in 2004, I bought a 2-port PCMCIA card made by Quatech, which has
>since been on a lot of Field Days, CA QSO Party county expeditions, and
>even a DX trip. It contains two real hardware serial ports and a
>pluggable dongle.  I've since bought two more for additional laptops. 
>They are not cheap, Quatech is a US company, based in OH, I think.  I've
>observed no RFI issues, and they work with signal returns connected to
>DB9 connector shells.  .
>
>In recent years, I've heard good things about Edgeport products.  They
>were not cheap until they went bankrupt a year or two ago.
>
>73, Jim K9YC
>
>
>------------------------------
>
>Message: 3
>Date: Wed, 2 Nov 2011 09:49:11 -0700 (PDT)
>From: Julius Fazekas n2wn <[hidden email]>
>Subject: Re: [Elecraft] Silly question about DVK3
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>Hi Olli,
>
>Both of your methods work, thanks...
>
>Still am unable to get the ESC key to stop a message, even after trying
>different settings, but placing a "-" on a function key seems to do the
>trick.
>
>73,
>Julius
>n2wn
>
>-----
>Julius Fazekas
>N2WN
>
>Tennessee Contest Group
>http://www.k4ro.net/tcg/index.html
>
>Tennessee QSO Party
>http://www.tnqp.org/
>
>Elecraft K2        #4455
>Elecraft K3/100 #366
>Elecraft K3/100
>--
>View this message in context: http://elecraft.365791.n2.nabble.com/Silly-question-about-DVK3-tp6948894p6956013.html
>Sent from the Elecraft mailing list archive at Nabble.com.
>
>
>------------------------------
>
>Message: 4
>Date: Wed, 2 Nov 2011 17:02:34 +0000
>From: Rose <[hidden email]>
>Subject: Re: [Elecraft] P3 - What am I observing?
>To: Phil Westover <[hidden email]>,    Elecraft Reflector
>    <[hidden email]>
>Message-ID:
>    <CAK+fsRWpmq3j3hHFW5ah66q2Srms01DJ6Bh2F2j0j77BN5=[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1
>
>Hi Phil,
>
>You may be seeing "hum" or other "noise" on his carrier.
>
>You'll likely see the same sort of display when observing
>WWV's signal when they're transmitting their tone/s.
>
>Tune around the bands a bit and I think you'll see the double
>"spikes" on quite a number of signals, regardless of mode.
>
>Ignore the "Rose" header ... I'm using her computer for this
>reply.
>
>73! Ken - K0PP
>[hidden email]
>
>
>> Here's my question:  What are the two "spikes" that I see about 500 Hz to
>> each side of 28.130, approximately 25-30 dB down from the center's peak
>> level (-125 to -130 dB)?  These spikes are above my observed floor about
>> 20-25 dB.
>>
>> It's a beautiful thing; I simply am not sure what I'm seeing.  One thing I
>> am sure of, when you all respond with the answer, I'll bop myself in the
>> head for not thinking about it!
>
>
>------------------------------
>
>Message: 5
>Date: Wed, 2 Nov 2011 10:15:02 -0700 (PDT)
>From: Joe Ford <[hidden email]>
>Subject: [Elecraft] k3 Strange Problem
>To: Elecraft <[hidden email]>
>Message-ID:
>    <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>Guy and Don made the right call. Thanks, I was off on a tangent and not the right one for sure.
>
>I have another 88' foot long dipole which we use for our CW station at Field Day. So I strung it up in a temporary location and bypassed the other dipole as a test. No more HIGH SWR message. It tunes right to 1:1. So now I have to lower the problem dipole and give it a thorough checkout. If I don't see something right away I can jusdt string up the FD dipole to get going again.
>
>
>Thanks, Guy, Don and others for pushing me down the right road.
>
>73,
>Joe
>k4nvj
>
>
>------------------------------
>
>Message: 6
>Date: Wed, 02 Nov 2011 13:28:23 -0400
>From: "Phil LaMarche" <[hidden email]>
>Subject: [Elecraft] FS:  W2 REDUCED
>To: <[hidden email]>
>Message-ID: <04ec01cc9984$d2b51f80$781f5e80$@verizon.net>
>Content-Type: text/plain;    charset="US-ASCII"
>
>I have a like new W2 with the 200 and 2000 watt couplers/cables.  Also the
>serial cable.
>
>
>
>$210.00 Shipped and insured.
>
>
>
>Phil W9DVM
>
>
>
>Philip LaMarche
>
>
>
>LaMarche Enterprises, Inc
>
>
>
><mailto:[hidden email]> [hidden email]
>
><http://www.lamarcheenterprises.com/> www.LaMarcheEnterprises.com 
>
>
>
>727-944-3226
>
>727-937-8834 Fax
>
>727-510-5038 Cell
>
>  <http://www.w9dvm.com/> www.w9dvm.com
>
>K3 # 1605
>
>KPA500 # 029
>
>P3 #1480
>
>
>
>CCA 98-00827
>
>CRA 1701
>
>W9DVM
>
>
>
>
>
>
>
>------------------------------
>
>Message: 7
>Date: Wed, 2 Nov 2011 10:45:56 -0700
>From: "Fred Atchley" <[hidden email]>
>Subject: Re: [Elecraft] Orion I for K3
>To: <[hidden email]>
>Message-ID: <A7D13084C5A64434BB2246977508BFB7@eagle>
>Content-Type: text/plain;    charset="us-ascii"
>
>Caveat Emptor .FWIW: I had an Orion, years back. It was a very good rig. But
>it was announced that the manufacturer of its signal processor was changing
>dies which could affect availability and future maintainability of the Orion
>I. I made a decision then to "upgrade" to the OMNI VII, because of the OMNI
>lineage. Boy was I disappointed with the pseudo roofing filter when that rig
>was employed in the CQP (as compared to the Orion I.) So, in less than a
>year I turned to the K3. The K3 was a massive improvement for detecting weak
>signals and separating strong signals.
>
>Another consideration is the upgrade path for Orion I vs. the K3. The P3 is
>a game changer. I don't know how I lived without it. OTOH the spectrum
>display on the Orion I was useless to me. Then there is the KPA500 which,
>like the P3, integrates all its functions seamlessly with the K3.
>
>As a Ten Tec owner I tried the Ten Tec blog for a limited time. I quit
>because of the elitist flaming.
>
>I'll stick with Elecraft, thank you. 73, Fred
>
>
>
>
>
>------------------------------
>
>Message: 8
>Date: Wed, 2 Nov 2011 11:34:50 -0700 (PDT)
>From: Lee Buller <[hidden email]>
>Subject: [Elecraft] USB Adapters and RF
>To: Elecraft Reflector <[hidden email]>
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>
>I run legal limit on some contests.  I seem to burn up USB to Serial devices.  I
>am grounded properly.  I am suspect of these things in high RF fields. 
>But...what is a guy gonna do when RS232 Serial ports are totally discontinued. 
>Turn down or turn off the amp.  Hmmmmmm!
>
>Lee - K0WA
>
>
>In our day and age it seems that Common Sense is in short supply.  If you don't
>have any Common Sense - get some Common Sense and use it.  If you can't find any
>Common Sense, ask for help from somebody who has some Common Sense.  Is Common
>Sense divine?
>
>Common Sense is the image of the Creator expressing revealed truth in my mind.
>-  John W. (Kansas)
>
>Never interfere with anything that isn't bothering you.
>
>------------------------------
>
>Message: 9
>Date: Wed, 02 Nov 2011 12:10:43 -0700
>From: Ralph Parker <[hidden email]>
>Subject: [Elecraft] K3 DVK vs N1MM difficulties
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; CHARSET=US-ASCII
>
>Hi Gang:
>In the recent CQ WW SSB, I used N1MM 11.10.3 to key the KDVR3 via a
>microHAM CW Keyer, using the N1MM macros provided by N6ML. It worked, but
>with every second CQ (press of <F1>, or <ENTER> via ESM), N1MM popped up a
>window complaining about a missing .WAV file, which had to be closed before
>any further action was possible. The workaround was to close the window and
>keep going - a royal PITA.
>
>I have done this before, with a previous version of N1MM, and I don't
>remember this problem. Perhaps I should ask for help on the N1MM reflector,
>but I'm not a member (yet).
>
>Any help/hints/suggestions greatfully received.
>
>Ralph, VE7XF
>
>
>
>------------------------------
>
>Message: 10
>Date: Wed, 2 Nov 2011 19:18:56 +0000
>From: Ian White GM3SEK <[hidden email]>
>Subject: Re: [Elecraft] USB Adapters and RF
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain;charset=us-ascii;format=flowed
>
>Lee Buller wrote:
>>
>>I run legal limit on some contests.  I seem to burn up USB to Serial
>>devices.  I am grounded properly.  I am suspect of these things in high
>>RF fields. But...what is a guy gonna do when RS232 Serial ports are
>>totally discontinued. Turn down or turn off the amp.  Hmmmmmm!
>>
>
>Look very carefully at that statement "I am grounded properly"; because
>the evidence suggests otherwise. More specifically, it suggests that the
>ground terminals for various parts of your shack are not correctly
>bonded together. Another very common source of RF in the shack is a bad
>shield connection inside a PL259.
>
>A few minutes applying a clamp-on RF current meter to various connecting
>cables could tell you a great deal.
>
>
>--
>
>73 from Ian GM3SEK
>http://www.ifwtech.co.uk/g3sek
>
>
>------------------------------
>
>Message: 11
>Date: Wed, 2 Nov 2011 12:27:37 -0700 (PDT)
>From: Lee Buller <[hidden email]>
>Subject: Re: [Elecraft] USB Adapters and RF
>To: Elecraft Reflector <[hidden email]>
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>
>Very interesting....
>
>Maybe I should have said..."I think I am grounded properly!"  I will have to
>check this out. 
>
>
>Lee
>K0WA
>
>
>
>
>
>
>________________________________
>From: Ian White GM3SEK <[hidden email]>
>To: [hidden email]
>Sent: Wed, November 2, 2011 2:18:56 PM
>Subject: Re: [Elecraft] USB Adapters and RF
>
>Lee Buller wrote:
>>
>>I run legal limit on some contests.  I seem to burn up USB to Serial
>>devices.  I am grounded properly.  I am suspect of these things in high
>>RF fields. But...what is a guy gonna do when RS232 Serial ports are
>>totally discontinued. Turn down or turn off the amp.  Hmmmmmm!
>>
>
>Look very carefully at that statement "I am grounded properly"; because
>the evidence suggests otherwise. More specifically, it suggests that the
>ground terminals for various parts of your shack are not correctly
>bonded together. Another very common source of RF in the shack is a bad
>shield connection inside a PL259.
>
>A few minutes applying a clamp-on RF current meter to various connecting
>cables could tell you a great deal.
>
>
>--
>
>73 from Ian GM3SEK
>http://www.ifwtech.co.uk/g3sek
>______________________________________________________________
>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: 12
>Date: Wed, 02 Nov 2011 15:37:02 -0400
>From: Mike <[hidden email]>
>Subject: Re: [Elecraft] K3: COM1 and COM3 question
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>I'm not sure what the question is. The com port number only matters to the computer,
>not the radio. The radio has no knowledge of com port numbers.
>
>73, Mike NF4L
>
>On 11/2/2011 10:49 AM, David Windisch wrote:
>> Hi, all concerned:
>>
>> Operationally, all has been well with 2 K3s and P3s in the station over the
>> last several years.
>> Been thru  multiple successful firmware upgrades, yearly recals, and so on,
>> with no external adapters or port-sharing software being used, simply the K3
>> and P3 utilities, dummy loads, and XG2 for the usual housekeeping.
>>
>> I've long ignored that one K3 has always communicated thru COM1 to its
>> computer and the other thru COM3 to its computer.
>>
>> Afaik they ain't broke; anybody have an explanation, please?
>>
>> Brgds,
>> Dave Windisch, N3HE
>>
>>
>>
>>
>> --
>> View this message in context: http://elecraft.365791.n2.nabble.com/K3-COM1-and-COM3-question-tp6955511p6955511.html
>> Sent from the Elecraft mailing list archive at Nabble.com.
>> ______________________________________________________________
>> 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: 13
>Date: Wed, 2 Nov 2011 19:39:51 +0000
>From: iain macdonnell - N6ML <[hidden email]>
>Subject: Re: [Elecraft] Silly question about DVK3
>To: Julius Fazekas n2wn <[hidden email]>
>Cc: [hidden email]
>Message-ID:
>    <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1
>
>Unfortunately they changed N1MM Logger such that it no longer
>generates an "RX;" command when Escape is pressed, even when "PTT via
>radio command" is enabled. You can program one of the F-keys to send
>the "RX;" command instead.... at least for now - hopefully we can come
>up with a solution to make the Escape key work again, as that's the
>most intuitive method, IMO...
>
>    ~iain / N6ML
>
>
>On Wed, Nov 2, 2011 at 4:49 PM, Julius Fazekas n2wn
><[hidden email]> wrote:
>> Hi Olli,
>>
>> Both of your methods work, thanks...
>>
>> Still am unable to get the ESC key to stop a message, even after trying
>> different settings, but placing a "-" on a function key seems to do the
>> trick.
>>
>> 73,
>> Julius
>> n2wn
>>
>> -----
>> Julius Fazekas
>> N2WN
>>
>> Tennessee Contest Group
>> http://www.k4ro.net/tcg/index.html
>>
>> Tennessee QSO Party
>> http://www.tnqp.org/
>>
>> Elecraft K2 ? ? ? ?#4455
>> Elecraft K3/100 #366
>> Elecraft K3/100
>> --
>> View this message in context: http://elecraft.365791.n2.nabble.com/Silly-question-about-DVK3-tp6948894p6956013.html
>> Sent from the Elecraft mailing list archive at Nabble.com.
>> ______________________________________________________________
>> 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: 14
>Date: Wed, 02 Nov 2011 15:59:44 -0400
>From: "Joe Subich, W4TV" <[hidden email]>
>Subject: Re: [Elecraft] USB Adapters and RF
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>
>> I run legal limit on some contests. I seem to burn up USB to Serial
>> devices. I am grounded properly. I am suspect of these things in high
>> RF fields.
>
>It is odd that I just answered this same question in a different form
>on the N1MM Logger list ...
>
>> *Any time* one feeds an unbalanced antenna with coax and does not have
>> a current "balun" with a high choking impedance, the coax will act
>> like a random length "radial" or half of the driven element.  When that
>> "radial" is an odd multiple of 1/4 wave long, the "end" of the radial
>> will be at a high RF voltage.  Old timers will recognize this at the
>> "hot mic" (RF bites the lips!) scenario.  When the RF voltage is high
>> enough, it can upset electronics ... a 5V P-P voltage at the USB port
>> of a computer/peripheral can "cancel" the 5V (or 3.3V in some systems)
>> USB power and shut down the port.  RF voltages higher than 5V P-P can
>> result in *reverse bias* permanently damage some components.
>
>Bottom line, be *absolutely sure* to use choking impedance common mode
>chokes, properly installed, at the appropriate places in your antenna
>system.  Proper points are at the antenna feed point and at the "entry
>window" to the building (outboard of the point at which the cable
>shields are grounded so the choke is working against a low impedance).
>
>If you can't do that, only purchase interface products that include a
>proper over voltage suppressor on the USB power line (to clamp any
>voltage to 0/+5.5V).  Before anyone asks - I do not know which low
>cost USB to serial converters include voltage suppressors.
>
>73,
>
>    ... Joe, W4TV
>
>
>On 11/2/2011 2:34 PM, Lee Buller wrote:
>>
>> I run legal limit on some contests.  I seem to burn up USB to Serial devices.  I
>> am grounded properly.  I am suspect of these things in high RF fields.
>> But...what is a guy gonna do when RS232 Serial ports are totally discontinued.
>> Turn down or turn off the amp.  Hmmmmmm!
>>
>> Lee - K0WA
>>
>>
>>   In our day and age it seems that Common Sense is in short supply.  If you don't
>> have any Common Sense - get some Common Sense and use it.  If you can't find any
>> Common Sense, ask for help from somebody who has some Common Sense.  Is Common
>> Sense divine?
>>
>> Common Sense is the image of the Creator expressing revealed truth in my mind.
>> -  John W. (Kansas)
>>
>> Never interfere with anything that isn't bothering you.
>> ______________________________________________________________
>> 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: 15
>Date: Wed, 02 Nov 2011 16:29:03 -0400
>From: "Joe Subich, W4TV" <[hidden email]>
>Subject: Re: [Elecraft] USB Adapters and RF
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>I see my cut/paste from the other reply left out some important
>information.  The following is edited to add the missing references.
>
>*Any time* one feeds an unbalanced antenna with coax and does not have
>a current "balun" with a high choking impedance, the coax will act
>like a random length "radial" or half of the driven element. When that
>"radial" is an odd multiple of 1/4 wave long, the "end" of the radial
>will be at a high RF voltage. Old timers will recognize this at the
>"hot mic" (RF bites the lips!) scenario. When the RF voltage is high
>enough, it can upset electronics ... a 5V P-P voltage at the USB port
>of a computer/peripheral can "cancel" the 5V (or 3.3V in some systems)
>USB power and shut down the port. RF voltages higher than 5V P-P can
>result in *reverse bias* and permanently damage some components.
>
>There are two good tutorials on common mode chokes on-line - one by
>K9YC: http://www.audiosystemsgroup.com/RFI-Ham.pdf and one by W1HIS:
>http://www.yccc.org/Articles/W1HIS/CommonModeChokesW1HIS2006Apr06.pdf
>I strongly recommend studying both.
>
>Bottom line, be *absolutely sure* to use high choking impedance common
>mode chokes, properly installed, at the appropriate places in your
>antenna system. Proper points are at the antenna feed point and at
>the "entry window" to the building (outboard of the point at which the
>cable shields are grounded so the choke is working against a low impedance).
>
>If you can't do that, only purchase interface products that include a
>proper over voltage suppressor on the USB power line (to clamp any
>voltage to 0/+5.5V). Before anyone asks - I do not know which low
>cost USB to serial converters include voltage suppressors.
>
>73,
>
>    ... Joe, W4TV
>
>
>On 11/2/2011 3:59 PM, Joe Subich, W4TV wrote:
>>
>>
>>> I run legal limit on some contests. I seem to burn up USB to Serial
>>> devices. I am grounded properly. I am suspect of these things in high
>>> RF fields.
>>
>> It is odd that I just answered this same question in a different form
>> on the N1MM Logger list ...
>>
>>> *Any time* one feeds an unbalanced antenna with coax and does not have
>>> a current "balun" with a high choking impedance, the coax will act
>>> like a random length "radial" or half of the driven element.  When that
>>> "radial" is an odd multiple of 1/4 wave long, the "end" of the radial
>>> will be at a high RF voltage.  Old timers will recognize this at the
>>> "hot mic" (RF bites the lips!) scenario.  When the RF voltage is high
>>> enough, it can upset electronics ... a 5V P-P voltage at the USB port
>>> of a computer/peripheral can "cancel" the 5V (or 3.3V in some systems)
>>> USB power and shut down the port.  RF voltages higher than 5V P-P can
>>> result in *reverse bias* permanently damage some components.
>>
>> Bottom line, be *absolutely sure* to use choking impedance common mode
>> chokes, properly installed, at the appropriate places in your antenna
>> system.  Proper points are at the antenna feed point and at the "entry
>> window" to the building (outboard of the point at which the cable
>> shields are grounded so the choke is working against a low impedance).
>>
>> If you can't do that, only purchase interface products that include a
>> proper over voltage suppressor on the USB power line (to clamp any
>> voltage to 0/+5.5V).  Before anyone asks - I do not know which low
>> cost USB to serial converters include voltage suppressors.
>>
>> 73,
>>
>>      ... Joe, W4TV
>>
>>
>> On 11/2/2011 2:34 PM, Lee Buller wrote:
>>>
>>> I run legal limit on some contests.  I seem to burn up USB to Serial devices.  I
>>> am grounded properly.  I am suspect of these things in high RF fields.
>>> But...what is a guy gonna do when RS232 Serial ports are totally discontinued.
>>> Turn down or turn off the amp.  Hmmmmmm!
>>>
>>> Lee - K0WA
>>>
>>>
>>>    In our day and age it seems that Common Sense is in short supply.  If you don't
>>> have any Common Sense - get some Common Sense and use it.  If you can't find any
>>> Common Sense, ask for help from somebody who has some Common Sense.  Is Common
>>> Sense divine?
>>>
>>> Common Sense is the image of the Creator expressing revealed truth in my mind.
>>> -  John W. (Kansas)
>>>
>>> Never interfere with anything that isn't bothering you.
>>> ______________________________________________________________
>>> 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
>>
>
>
>------------------------------
>
>Message: 16
>Date: Wed, 02 Nov 2011 15:30:41 -0500
>From: Jim Dunstan <[hidden email]>
>Subject: Re: [Elecraft] K3: COM1 and COM3 question
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset="us-ascii"; format=flowed
>
>At 07:49 AM 11/2/2011 -0700, you wrote:
>
>>I've long ignored that one K3 has always communicated thru COM1 to its
>>computer and the other thru COM3 to its computer.
>>
>>Afaik they ain't broke; anybody have an explanation, please?
>>
>>Brgds,
>>Dave Windisch, N3HE
>
>Hi
>
>No problem, and not unusual.  The computer OS assigns the COM number to
>devices,
>in this case the Serial Ports, and assures they operate without conflict
>with any other device in/attached to the computer.
>
>Generally the serial port is often but not always set as COM1.  If you
>attach a device to the serial port and it works right
>away ... then they are both set to the same COM number.  If the COM numbers
>are not the same they will not communicate
>and you will have to change the number either at the computer or the
>device/program.
>
>Communications between computer and device using COM1 to COM1 is the same
>as COM3 to COM3.  Now if you swap
>computers/radios in your shack you will also have to change the COM# on the
>radios (best place to make the change).
>
>Jim, VE3CI
>
>
>
>
>
>------------------------------
>
>Message: 17
>Date: Wed, 2 Nov 2011 16:49:13 -0400
>From: Guy Olinger K2AV <[hidden email]>
>Subject: Re: [Elecraft] K3 Strange Problem
>To: Joe Ford <[hidden email]>
>Cc: Elecraft <[hidden email]>
>Message-ID:
>    <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1
>
>On Tue, Nov 1, 2011 at 9:24 PM, Joe Ford <[hidden email]> wrote:
>
>... I'll take down the ant and inspect it.But it works fine on all the other
>> bands. Tunes with no problems all other bands. The KAT100 tunes but the KAT3
>> doesn't?
>
>Tuning all bands using a single antenna is always dicey
>somewhere.Success is NOT guaranteed, but fortunate.  You are often
>operating at the fringe of a tuner's range on one band or another.
>The KAT 100 and KAT3 are not the same tuners, have different coils,
>different tradeoffs, and different firmware to drive it.  Though the
>ranges are approximately the same, give the two units an impedance at
>the far fringe, and one or the other may not be able tune it properly.
>
>Change any of the coax lengths after the tuner, INCLUDING THOSE INSIDE
>THE K3, by switching, exchange, or whatever, and what just barely got
>tuned the last time by the same tuner may not now tune.
>
>Though this may not be your problem at all, a friend of mine was
>having troubles of this mysterious sort. Eventually he discovered that
>he had not soldered either the braid OR the center conductor on a
>PL259.  It worked for YEARS before it finally started getting
>intermittent.
>
>Another ham had a balun that was gradually going bad and overheating,
>apparently shorting some turns and causing mysterious changes in SWR.
>He discovered that because during a QRO contest it caught fire and
>completely shorted out.  Actually his wife discovered it looking out
>the window at the tower out in the field, and came and told him his
>tower was on fire.
>
>The way to validate and check out one of these compromise antennas, is
>to run it when it is brand new and working spiffy.  SWEEP the MFJ
>CONTINUOUSLY from the bottom of the lowest band to the top of the
>highest band.  Note the actual resonances you find along the way.
>Write down those frequencies, the R at those resonant frequencies, and
>the 2:1 SWR points above and below all of those resonances. Entirely
>possible that all of the resonances are outside the ham bands.  Keep
>these figures as a reference.  When you have trouble, repeat the
>measurements.  IF there is trouble in the antenna, those readings will
>change.  If the coax gets waterlogged, the 2:1 SWR points will broaden
>out significantly and the R values at resonance will likely change.
>If something gets broken the resonances will all move on you.
>
>If you have an AIM 4170 as your analyzer, just sweep it from 0.5 to 30
>MHz and save the file.  You can then import it and have an onscreen
>compare between the old and new readings.
>
>73, Guy.
>
>
>------------------------------
>
>Message: 18
>Date: Wed, 02 Nov 2011 17:38:32 -0400
>From: Don Wilhelm <[hidden email]>
>Subject: Re: [Elecraft] K3: COM1 and COM3 question
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Jim,
>
>Sorry to disagree, but there is no way to set the COM Port on either the
>K3 nor the P3.
>Setting the baud rate - yes, but the computer (or the computer
>application software) determines which COM port is to be assigned to a
>particular connector or cable.
>
>73,
>Don W3FPR
>
>On 11/2/2011 4:30 PM, Jim Dunstan wrote:
>> Generally the serial port is often but not always set as COM1. If you
>> attach a device to the serial port and it works right away ... then
>> they are both set to the same COM number. If the COM numbers are not
>> the same they will not communicate and you will have to change the
>> number either at the computer or the device/program. Communications
>> between computer and device using COM1 to COM1 is the same as COM3 to
>> COM3. Now if you swap computers/radios in your shack you will also
>> have to change the COM# on the radios (best place to make the change).
>> Jim, VE3CI
>
>
>------------------------------
>
>Message: 19
>Date: Wed, 02 Nov 2011 14:59:14 -0700
>From: David Gilbert <[hidden email]>
>Subject: Re: [Elecraft] K3: COM1 and COM3 question
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>That is simply not true.  The K3 has no idea what COM port on the
>computer it is talking to.  Please describe how you change the COM port
>designation on the K3.
>
>Dave   AB7E
>
>
>On 11/2/2011 1:30 PM, Jim Dunstan wrote:
>
>Hi
>
>No problem, and not unusual.  The computer OS assigns the COM number to
>devices,
>in this case the Serial Ports, and assures they operate without conflict
>with any other device in/attached to the computer.
>
>Generally the serial port is often but not always set as COM1.  If you
>attach a device to the serial port and it works right
>away ... then they are both set to the same COM number.  If the COM numbers
>are not the same they will not communicate
>and you will have to change the number either at the computer or the
>device/program.
>
>Communications between computer and device using COM1 to COM1 is the same
>as COM3 to COM3.  Now if you swap
>computers/radios in your shack you will also have to change the COM# on the
>radios (best place to make the change).
>
>Jim, VE3CI
>
>
>
>
>------------------------------
>
>Message: 20
>Date: Wed, 2 Nov 2011 15:10:13 -0700 (PDT)
>From: David Windisch <[hidden email]>
>Subject: Re: [Elecraft] K3: COM1 and COM3 question
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>Hi, all concerned:
>A gent who shall remain anonymous provided an explanation directly.
>The Windows DEVICE MANAGER can be used to assign port numbers up to 256 to
>the physical hardware COM adapters.
>Tks and brgds to all who replied.
>Dave Windisch, N3HE
>
>
>--
>View this message in context: http://elecraft.365791.n2.nabble.com/K3-COM1-and-COM3-question-tp6955511p6957155.html
>Sent from the Elecraft mailing list archive at Nabble.com.
>
>
>------------------------------
>
>Message: 21
>Date: Wed, 2 Nov 2011 15:13:13 -0700
>From: Greg <[hidden email]>
>Subject: Re: [Elecraft] K3: COM1 and COM3 question
>To: David Gilbert <[hidden email]>
>Cc: [hidden email]
>Message-ID:
>    <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1
>
>I suspect he means going into device manager and changing the COM port
>designation for the port the radio is connected to.  That's the only thing
>that makes sense to me at least.
>
>73
>Greg
>
>
>
>On Wed, Nov 2, 2011 at 2:59 PM, David Gilbert <[hidden email]>wrote:
>
>>
>> That is simply not true.  The K3 has no idea what COM port on the
>> computer it is talking to.  Please describe how you change the COM port
>> designation on the K3.
>>
>> Dave   AB7E
>>
>>
>> On 11/2/2011 1:30 PM, Jim Dunstan wrote:
>>
>>  Hi
>>
>> No problem, and not unusual.  The computer OS assigns the COM number to
>> devices,
>> in this case the Serial Ports, and assures they operate without conflict
>> with any other device in/attached to the computer.
>>
>> Generally the serial port is often but not always set as COM1.  If you
>> attach a device to the serial port and it works right
>> away ... then they are both set to the same COM number.  If the COM numbers
>> are not the same they will not communicate
>> and you will have to change the number either at the computer or the
>> device/program.
>>
>> Communications between computer and device using COM1 to COM1 is the same
>> as COM3 to COM3.  Now if you swap
>> computers/radios in your shack you will also have to change the COM# on the
>> radios (best place to make the change).
>>
>> Jim, VE3CI
>>
>>
>> ______________________________________________________________
>> 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: 22
>Date: Wed, 02 Nov 2011 17:25:43 -0500
>From: Jim Dunstan <[hidden email]>
>Subject: Re: [Elecraft] K3: COM1 and COM3 question
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset="us-ascii"; format=flowed
>
>At 05:38 PM 11/2/2011 -0400, you wrote:
>>Jim,
>>
>>Sorry to disagree, but there is no way to set the COM Port on either the
>>K3 nor the P3.
>>Setting the baud rate - yes, but the computer (or the computer
>>application software) determines which COM port is to be assigned to a
>>particular connector or cable.
>>
>>73,
>>Don W3FPR
>
>I am sure you are correct.  I don't own a K3.  But the original post
>mentioned two K3 operating positions each
>controlled by separate computers.  One computer uses Com1 on the RS232 port
>and the other uses Com3.
>
>There was no question ... but a request for an explanation.
>
>Perhaps you can provide the explanation.
>
>Thanks
>
>Jim, VE3CI
>
>
>
>
>------------------------------
>
>Message: 23
>Date: Wed, 02 Nov 2011 18:55:25 -0400
>From: Don Wilhelm <[hidden email]>
>Subject: Re: [Elecraft] K3: COM1 and COM3 question
>To: Jim Dunstan <[hidden email]>
>Cc: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Jim,
>
>Let me try an explanation as simple as I can put it.
>
>The COM port numbers are set at the computer end.  First the OS assigns
>port numbers to the physical COM ports that are present on that computer.
>
>You connect a cable and a terminal device (the K3 or P3 or several of
>them) each to a physical port on that computer - you have to know which
>connector on the computer corresponds to COM1 through COM nnn - normally
>a computer with one true serial port will have COM1 on that connector -
>for those with multiple true serial ports, you have to know which number
>corresponds with each port - that information is normally silkscreened
>on the motherboard.  For add-on cards, consult the card instructions.
>With USB adapters, you can usually find the relationship in Device
>Manager - the numbers are usually higher.  If you don't know which
>adapter is which, unplug it and see which port numbers go away, then
>plug it back in and see which numbers appear.
>
>After you know which port numbers are assigned to which serial
>connector, then you can go to the software application and tell it to
>talk to a particular device over a particular COM port (the one you have
>cabled to your device).  Some applications will scan through the
>available ports to try to find what it thinks is a valid open port with
>the desired device connected (and powered on) at the other end of the
>cable.  The software application will seize the port and makes it busy
>to all other applications.  The operating system passes whatever flows
>on that port over to the application.
>
>The terminal device does not know which computer port it is connected to
>- it sees data coming in over the TXD signal line and responds on the
>RXD signal line - the computer and application sorts out which device it
>is talking to.
>
>73,
>Don W3FPR
>
>On 11/2/2011 6:25 PM, Jim Dunstan wrote:
>> At 05:38 PM 11/2/2011 -0400, you wrote:
>>> Jim,
>>>
>>> Sorry to disagree, but there is no way to set the COM Port on either the
>>> K3 nor the P3.
>>> Setting the baud rate - yes, but the computer (or the computer
>>> application software) determines which COM port is to be assigned to a
>>> particular connector or cable.
>>>
>>> 73,
>>> Don W3FPR
>> I am sure you are correct.  I don't own a K3.  But the original post
>> mentioned two K3 operating positions each
>> controlled by separate computers.  One computer uses Com1 on the RS232 port
>> and the other uses Com3.
>>
>> There was no question ... but a request for an explanation.
>>
>> Perhaps you can provide the explanation.
>>
>> Thanks
>>
>> Jim, VE3CI
>>
>>
>> ______________________________________________________________
>> 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: 24
>Date: Wed, 2 Nov 2011 16:07:34 -0700
>From: "Ron D'Eau Claire" <[hidden email]>
>Subject: Re: [Elecraft] K3: COM1 and COM3 question
>To: <[hidden email]>
>Message-ID: <000001cc99b4$352b87b0$9f829710$@biz>
>Content-Type: text/plain;    charset="us-ascii"
>
>Is, perhaps, someone being confused because they see that they must select
>the com port associated with the radio in the program at the computer (just
>as it is in the Elecraft Utility programs), they think that it is at the
>radio that selection is being made - just as they enter frequency and other
>data at the computer that changes things at the radio?
>
>Whew  - that was a sentence ...
>
>Ron AC7AC
>
>
>
>-----Original Message-----
>At 05:38 PM 11/2/2011 -0400, you wrote:
>>Jim,
>>
>>Sorry to disagree, but there is no way to set the COM Port on either the
>>K3 nor the P3.
>>Setting the baud rate - yes, but the computer (or the computer
>>application software) determines which COM port is to be assigned to a
>>particular connector or cable.
>>
>>73,
>>Don W3FPR
>
>I am sure you are correct.  I don't own a K3.  But the original post
>mentioned two K3 operating positions each
>controlled by separate computers.  One computer uses Com1 on the RS232 port
>and the other uses Com3.
>
>There was no question ... but a request for an explanation.
>
>Perhaps you can provide the explanation.
>
>Thanks
>
>Jim, VE3CI
>
>
>______________________________________________________________
>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: 25
>Date: Wed, 02 Nov 2011 19:48:23 -0400
>From: Gilbert Cross <[hidden email]>
>Subject: [Elecraft] Elecraft FS XG2 Sig Gen
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>         Sig Gen is mounted in an Altoids tin. Asking $50.00. I ship in CONUS. Please reply off list...
>
>             Thank you    Gil   K8EAG
>
>
>------------------------------
>
>Message: 26
>Date: Wed, 2 Nov 2011 17:55:00 -0700 (PDT)
>From: Joe Ford <[hidden email]>
>Subject: Re: [Elecraft] K3 Strange Problem
>To: Guy Olinger K2AV <[hidden email]>
>Cc: Elecraft <[hidden email]>
>Message-ID:
>    <[hidden email]>
>Content-Type: text/plain; charset=iso-8859-1
>
>Guy,
>
>Thanks for the tips. My coax jumpers are some I bought from a company I don't remember exactly which one. It was one that I saw recommended somewhere. Unfortunately the PL259s are crimped on but they seem to work okay. Just to be sure, when I was troubleshooting the problem I replaced the jumper with no change. I can't remember if I traded with the K2. I might have. I need to change the coax anyway because I need them to be a little longer. If I can find someone who sells good quality with soldered PL259s I'll probably order them, otherwise I'll just make my on.
>
>I lowered the dipole, looked it over but didn't see anything except the ends a rusting a little where they are tied to the insulators. Unfortunately it doesn't hang free and clear. I have lots of trees. I tried to reroute it where it would be more in the clear. Then I put it back up and it performs the same. I guess the next step is to replace it with the other dipole that tested okay. When I did the test I just hung the dipole between 2 trees. I did not hang it where the problem dipole is so it was not a 100% valid test. I'll try switching the 2 and see what happens. At least the test confirmed the switch and balun are okay.
>
>
>Thanks for the suggestion about recording the swr across the antenna bandwidth when it is new. I can plot a little graph and save it for future use. Even for my beam which is not new it will be a good thing to have.
>
>
>Joe
>k4nvj
>
>
>
>________________________________
>From: Guy Olinger K2AV <[hidden email]>
>To: Joe Ford <[hidden email]>
>Cc: Elecraft <[hidden email]>; "[hidden email]" <[hidden email]>
>Sent: Wednesday, November 2, 2011 3:49 PM
>Subject: Re: K3 Strange Problem
>
>On Tue, Nov 1, 2011 at 9:24 PM, Joe Ford <[hidden email]> wrote:
>
>... I'll take down the ant and inspect it.But it works fine on all the other
>> bands. Tunes with no problems all other bands. The KAT100 tunes but the KAT3
>> doesn't?
>
>Tuning all bands using a single antenna is always dicey
>somewhere.Success is NOT guaranteed, but fortunate.? You are often
>operating at the fringe of a tuner's range on one band or another.
>The KAT 100 and KAT3 are not the same tuners, have different coils,
>different tradeoffs, and different firmware to drive it.? Though the
>ranges are approximately the same, give the two units an impedance at
>the far fringe, and one or the other may not be able tune it properly.
>
>Change any of the coax lengths after the tuner, INCLUDING THOSE INSIDE
>THE K3, by switching, exchange, or whatever, and what just barely got
>tuned the last time by the same tuner may not now tune.
>
>Though this may not be your problem at all, a friend of mine was
>having troubles of this mysterious sort. Eventually he discovered that
>he had not soldered either the braid OR the center conductor on a
>PL259.? It worked for YEARS before it finally started getting
>intermittent.
>
>Another ham had a balun that was gradually going bad and overheating,
>apparently shorting some turns and causing mysterious changes in SWR.
>He discovered that because during a QRO contest it caught fire and
>completely shorted out.? Actually his wife discovered it looking out
>the window at the tower out in the field, and came and told him his
>tower was on fire.
>
>The way to validate and check out one of these compromise antennas, is
>to run it when it is brand new and working spiffy.? SWEEP the MFJ
>CONTINUOUSLY from the bottom of the lowest band to the top of the
>highest band.? Note the actual resonances you find along the way.
>Write down those frequencies, the R at those resonant frequencies, and
>the 2:1 SWR points above and below all of those resonances. Entirely
>possible that all of the resonances are outside the ham bands.? Keep
>these figures as a reference.? When you have trouble, repeat the
>measurements.? IF there is trouble in the antenna, those readings will
>change.? If the coax gets waterlogged, the 2:1 SWR points will broaden
>out significantly and the R values at resonance will likely change.
>If something gets broken the resonances will all move on you.
>
>If you have an AIM 4170 as your analyzer, just sweep it from 0.5 to 30
>MHz and save the file.? You can then import it and have an onscreen
>compare between the old and new readings.
>
>73, Guy.
>
>------------------------------
>
>Message: 27
>Date: Wed, 02 Nov 2011 19:12:39 -0600
>From: W0MU Mike Fatchett <[hidden email]>
>Subject: Re: [Elecraft] K3 Strange Problem
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>There is nothing wrong with crimped connectors if done properly.  Is
>this an antenna that was working fine and then stopped on one band with
>absolutely no changed in the shack or coax etc? What band is out of
>whack...I apologize for missing most of this thread.
>
>Mike W0MU
>
>J6M CQ WW DX CW Contest 2011
>J6/W0MU November 21 - December 1 2011
>W0MU-1 CC Cluster w0mu.net
>
>
>On 11/2/2011 6:55 PM, Joe Ford wrote:
>> Guy,
>>
>> Thanks for the tips. My coax jumpers are some I bought from a company I don't remember exactly which one. It was one that I saw recommended somewhere. Unfortunately the PL259s are crimped on but they seem to work okay. Just to be sure, when I was troubleshooting the problem I replaced the jumper with no change. I can't remember if I traded with the K2. I might have. I need to change the coax anyway because I need them to be a little longer. If I can find someone who sells good quality with soldered PL259s I'll probably order them, otherwise I'll just make my on.
>>
>> I lowered the dipole, looked it over but didn't see anything except the ends a rusting a little where they are tied to the insulators. Unfortunately it doesn't hang free and clear. I have lots of trees. I tried to reroute it where it would be more in the clear. Then I put it back up and it performs the same. I guess the next step is to replace it with the other dipole that tested okay. When I did the test I just hung the dipole between 2 trees. I did not hang it where the problem dipole is so it was not a 100% valid test. I'll try switching the 2 and see what happens. At least the test confirmed the switch and balun are okay.
>>
>>
>> Thanks for the suggestion about recording the swr across the antenna bandwidth when it is new. I can plot a little graph and save it for future use. Even for my beam which is not new it will be a good thing to have.
>>
>>
>> Joe
>> k4nvj
>>
>>
>>
>> ________________________________
>> From: Guy Olinger K2AV<[hidden email]>
>> To: Joe Ford<[hidden email]>
>> Cc: Elecraft<[hidden email]>; "[hidden email]"<[hidden email]>
>> Sent: Wednesday, November 2, 2011 3:49 PM
>> Subject: Re: K3 Strange Problem
>>
>> On Tue, Nov 1, 2011 at 9:24 PM, Joe Ford<[hidden email]>  wrote:
>>
>> ... I'll take down the ant and inspect it.But it works fine on all the other
>>> bands. Tunes with no problems all other bands. The KAT100 tunes but the KAT3
>>> doesn't?
>> Tuning all bands using a single antenna is always dicey
>> somewhere.Success is NOT guaranteed, but fortunate.  You are often
>> operating at the fringe of a tuner's range on one band or another.
>> The KAT 100 and KAT3 are not the same tuners, have different coils,
>> different tradeoffs, and different firmware to drive it.  Though the
>> ranges are approximately the same, give the two units an impedance at
>> the far fringe, and one or the other may not be able tune it properly.
>>
>> Change any of the coax lengths after the tuner, INCLUDING THOSE INSIDE
>> THE K3, by switching, exchange, or whatever, and what just barely got
>> tuned the last time by the same tuner may not now tune.
>>
>> Though this may not be your problem at all, a friend of mine was
>> having troubles of this mysterious sort. Eventually he discovered that
>> he had not soldered either the braid OR the center conductor on a
>> PL259.  It worked for YEARS before it finally started getting
>> intermittent.
>>
>> Another ham had a balun that was gradually going bad and overheating,
>> apparently shorting some turns and causing mysterious changes in SWR.
>> He discovered that because during a QRO contest it caught fire and
>> completely shorted out.  Actually his wife discovered it looking out
>> the window at the tower out in the field, and came and told him his
>> tower was on fire.
>>
>> The way to validate and check out one of these compromise antennas, is
>> to run it when it is brand new and working spiffy.  SWEEP the MFJ
>> CONTINUOUSLY from the bottom of the lowest band to the top of the
>> highest band.  Note the actual resonances you find along the way.
>> Write down those frequencies, the R at those resonant frequencies, and
>> the 2:1 SWR points above and below all of those resonances. Entirely
>> possible that all of the resonances are outside the ham bands.  Keep
>> these figures as a reference.  When you have trouble, repeat the
>> measurements.  IF there is trouble in the antenna, those readings will
>> change.  If the coax gets waterlogged, the 2:1 SWR points will broaden
>> out significantly and the R values at resonance will likely change.
>> If something gets broken the resonances will all move on you.
>>
>> If you have an AIM 4170 as your analyzer, just sweep it from 0.5 to 30
>> MHz and save the file.  You can then import it and have an onscreen
>> compare between the old and new readings.
>>
>> 73, Guy.
>> ______________________________________________________________
>> 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: 28
>Date: Wed, 02 Nov 2011 19:26:46 -0700
>From: Dan Sherwood <[hidden email]>
>Subject: [Elecraft] K3 and MT63: XMIT Non-Copy
>To: <[hidden email]>
>Message-ID: <CAD749F6.354F%[hidden email]>
>Content-Type: text/plain;    charset="ISO-8859-1"
>
>I am trying to get my K3 to properly transmit in the MT63 digital mode, (1K,
>max interleave), on a USAF MARS net.  Frequency just above 4 MHZ.  The KBPF3
>module is installed.  I was running MIXW2.2, using the same installation and
>settings that used to run perfectly on my TS-940S.  Our net is standardized
>so everyone runs USB with the MT63 1K channel centered exactly 1 KHZ above
>dial frequency.  I use the line input/output on the K3.  In USB mode I set
>computer sound card output in s/w so that with power out set to 100W, and
>line-in level at 10, the rig produces 50W and absolutely no ALC.
>Compression was backed down to zero.  Using TX TEST and headphones, the
>transmit audio sounds clean and distortion free.  Transmit EQ settings are
>factory default.
>
>Comments from net members are the audio sounds clean, and well centered on
>frequency, (+ 3HZ within tolerance).  With live transmit, monitoring the
>signal has no evidence of distortion.  The problem is the print is
>double-spaced, with long strings of blanks, and all characters are lower
>case.  Also much garble not evident on the TS-940S.  I realize the guys
>recommend using DATA mode, but this net mixed voice and data ? kind of tough
>to be switching back and forth.
>
>My copy on receive is as good as ever, just transmit.  I?m thinking there?s
>some kind of DSP issue going on here, even though compression is at 0.
>
>Any ideas?
>
>Thanks
>
>Dan Sherwood
>AFA9LV / WA6PZK
>
>
>
>------------------------------
>
>Message: 29
>Date: Wed, 2 Nov 2011 19:47:32 -0700 (PDT)
>From: tomb18 <[hidden email]>
>Subject: [Elecraft] Remote control of a K3?
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>Hi,
>Has anyone set up their K3 to be used remotely with HRD?  Does it work well
>with a laptops speakers and mike?
>What type of cables do I need for the connection of the sound card (I
>presume it is mono in)?  Or is it stereo cables?
>
>Thanks for any help1
>
>
>--
>View this message in context: http://elecraft.365791.n2.nabble.com/Remote-control-of-a-K3-tp6957747p6957747.html
>Sent from the Elecraft mailing list archive at Nabble.com.
>
>
>------------------------------
>
>Message: 30
>Date: Thu, 03 Nov 2011 00:34:07 -0400
>From: Don Wilhelm <[hidden email]>
>Subject: Re: [Elecraft] K3 and MT63: XMIT Non-Copy
>To: [hidden email]
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Dan,
>
>I think your statement about ALC=0 is the key..  With the K3, increase
>the audio drive until ALC= 4 bars (with the 5th bar flickering) for
>normal audio drive.  With that done, the K3 will propery transmit at the
>level set on the Power knob.  The onset of ALC in the K3 is at the the
>5th bar on the ALC meter - so you did not have sufficient audio drive.
>
>It should make no difference between DATA A and SSB mode - except that
>in DATA A mode, the Compression is automatically set to zero.  Since you
>said you had compression set to zero, SSB mode should work just fine.
>
>73,
>Don W3FPR
>
>On 11/2/2011 10:26 PM, Dan Sherwood wrote:
>> I am trying to get my K3 to properly transmit in the MT63 digital mode, (1K,
>> max interleave), on a USAF MARS net.  Frequency just above 4 MHZ.  The KBPF3
>> module is installed.  I was running MIXW2.2, using the same installation and
>> settings that used to run perfectly on my TS-940S.  Our net is standardized
>> so everyone runs USB with the MT63 1K channel centered exactly 1 KHZ above
>> dial frequency.  I use the line input/output on the K3.  In USB mode I set
>> computer sound card output in s/w so that with power out set to 100W, and
>> line-in level at 10, the rig produces 50W and absolutely no ALC.
>> Compression was backed down to zero.  Using TX TEST and headphones, the
>> transmit audio sounds clean and distortion free.  Transmit EQ settings are
>> factory default.
>>
>> Comments from net members are the audio sounds clean, and well centered on
>> frequency, (+ 3HZ within tolerance).  With live transmit, monitoring the
>> signal has no evidence of distortion.  The problem is the print is
>> double-spaced, with long strings of blanks, and all characters are lower
>> case.  Also much garble not evident on the TS-940S.  I realize the guys
>> recommend using DATA mode, but this net mixed voice and data ? kind of tough
>> to be switching back and forth.
>>
>> My copy on receive is as good as ever, just transmit.  I?m thinking there?s
>> some kind of DSP issue going on here, even though compression is at 0.
>>
>
>
>------------------------------
>
>Message: 31
>Date: Thu, 3 Nov 2011 21:41:51 +1000
>From: Gary VK4FD <[hidden email]>
>Subject: [Elecraft] 160M event
>To: "Elecraft" <[hidden email]>
>Message-ID: <BE7D277A03864949AA38996E72865592@vk4fd>
>Content-Type: text/plain;    charset="iso-8859-1"
>
>Hi Y'all,
>
>We will be active as VK4XQA from Uramo (pronounced You-Ra-Mo) in Far North Queensland on November 19/20/21 on 160M and 80M DX window (3.776-3.800)
>
>The site is a brand new AM broadcast antenna which has yet to be placed into commercial service.
>
>We will be running a full K-Line.
>
>Please listen out for us. A 'special' one off QSL card will be available for this event.
>
>73
>
>Gary
>
>
>VK4FD - Motorhome Mobile
>Elecraft Equipment
>K3 #679, KPA-500 #018
>Living the dream!!!
>
>
>------------------------------
>
>_______________________________________________
>Elecraft mailing list
>Post to: [hidden email]
>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 91, Issue 4
>***************************************
>
>
>

______________________________________________________________
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