Thanks Bob.

73,
Frank
W4TG

On Fri, Jul 5, 2024 at 2:38 PM Bob Wilson, N6TV <n...@arrl.net> wrote:

> Once you learn how to fix this unwanted keying issue in Windows, there's
> little reason to ever use the default UNSAFE option of *CONFIG:PTT-KEY*
> (tap '1' to toggle between "USB SAFE" or "UNSAFE").  The K4 does not have
> any equivalent option because it is simply not needed.
>
> To prevent unwanted keying of your K3 or K4 about 6 or 7 times when using
> DTR or RTS to key the rig, just disable two COM port settings (Serial
> Enumeration and Modem Control at Startup) using Windows Device Manager.
> Just follow the instructions and screenshots in this short document, linked
> from my QRZ.COM page <https://www.qrz.com/db/N6TV>:
>
>    - How to prevent unexpected transmissions when using FTDI
>    USB-to-Serial adapters <https://bit.ly/FTDItip> (online Google Doc,
>    from post
>    
> <http://elecraft.85.s1.nabble.com/Preventing-unexpected-transmissions-when-using-FTDI-devices-tp7644324.html>
>  to
>    Elecraft Reflector, August 12th, 2018)
>
> This applies to the Elecraft K3S, or a K3 with the FTDI version of the
> Elecraft KUSB, or the Elecraft K4, or the CW / FSK / PTT keying circuits in
> my S-BOX-USB <https://bit.ly/S-BOX>.
>
> If using a legacy 9-pin serial port on a PC like COM1: for keying, a
> simple registry edit is required.  See pages 29 to 33 in this PowerPoint
> Presentation for the details, or contact me OFF LINE for help via TeamViewer
> QuickSupport <https://www.teamviewer.com/en-us/download/windows/> if you
> don't want to attempt this yourself:
>
>    - Everything You Need to Know About USB and Serial Interfaces
>    <https://bit.ly/USBserial2021>, updated for 2021, presented to Spokane
>    DX Association, Feb. 3rd, 2022
>       - Watch YouTube recording of this presentation here
>       <https://youtu.be/X1yLJ9mi0gY>.
>
> Note that moving a rig's USB cable to a new USB hub (internal or
> external), or using commercial "device driver updater" software (not
> recommended), or a major Windows update like upgrading from Windows 10 to
> Window 11, will usually reset these important driver options back to
> defaults, so if the keying problem returns, simply perform this procedure
> again.
>
> Then set CONFIG:PTT-KEY to UNSAFE and there will be no more hassles.
>
> 73,
> Bob, N6TV
>
>
> On Thu, Jul 4, 2024 at 5:42 PM W3FPR <w3fpr...@gmail.com> wrote:
>
>> Frank,
>>
>> Yes it should bring up RTS-DTR after the port is polled.
>> When running with Unsafe mode, pay attention to when the K3 is turned on
>> and when the computer is turned on.  At times, you may have to turn the
>> computer on after the K3, and an easy way to prevent the extraneous
>> keying is to either use TEST mode or simply turn VOX off during the
>> computer boot time.
>>
>> 73,
>> Don W3FPR
>>
>> On 7/4/2024 6:54 PM, Frank Stein wrote:
>> > Don,
>> > Bingo. That, in fact, was the problem.  Turning on "Unsafe" solves the
>> > problem.  I use cwtype which sends to the com port and doesn't poll
>> > the comm port.
>> > Assuming I was using a program like N1MM, which does read from the com
>> > port (for frequencies), do I just set the PTT-KEY to RTS-DTR and turn
>> > on USB-safe and the rig will automatically set up RTS-DTR after it
>> > receives a poll?
>> >
>> > Thanks for the help everyone.
>> >
>> > 73,
>> > Frank
>> >
>>
> ______________________________________________________________
>> 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 n...@arrl.net
>
>
______________________________________________________________
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 

Reply via email to