[Elecraft] Preventing unexpected transmissions when using FTDI devices

[Jack Brindle]

Bob;

This is a Windows-only issue that dates back to their use of serial mice. It is not  problem on the Mac, which has no reason to toggle the serial port control signals on startup.

73!
Jack, W6FB


> On Aug 12, 2018, at 3:50 PM, Bob Wilson, N6TV <n6tv at arrl.net> wrote:
> 
> Elecraft K3 MCU version 5.33 added the new "USB SAFE" option as a default
> (CONFIG:PTT-KEY, Tap '1'), which prevents unexpected transmissions when you
> restart Windows or reconnect an FTDI adapter.
> 
> This works fine when controlling a K3 or K3S via USB, but it doesn't help
> when using an FTDI USB-to-Serial adapter for CW / FSK / PTT keying on a
> separate serial port.
> 
> I've published a 2-page document online, with screen shots, describing
> step-by-step how to use the Windows Device Manager to correct the default
> "Serial Enumerator" and "Modem Control" options set by the FTDI drivers,
> options which Windows unfortunately enables every time you connect a new
> FTDI adapter.  Every FTDI port must be independently configured at least
> once.
> 
> The short link to the online document is here:
> 
> https://bit.ly/FTDItip
> 
> 
> These FTDI settings are also recommended when using the S-BOX-USB
> <https://bit.ly/S-BOX> with a K3 or K3S, especially when used with the
> RemoteHams "Use RTS as Power" option.
> 
> If anyone on this list uses a MAC or Linux box with an FTDI adapter or FTDI
> KUSB cable, and the macOS offers the equivalent device options, please send
> me the screen shots (.PNG format preferred), and I'll add them to the
> document.
> 
> Thank you!
> 
> 73,
> Bob, N6TV
> https://bit.ly/S-BOX
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at 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 jackbrindle at me.com