[Elecraft] K3: USB port

[Joe Subich, W4TV]

Moving from RS-232 to USB for commands (CAT) is trivial - replace
the DB9 with one of the FTDI devices that is a USB to RS-232
converter built into the DB9 socket.  However, that does not get
you audio ...

To do audio, you would need not only the USB converter but a hub
and USB Audio CODEC (e.g. PCM8902 or similar).  Then Elecraft
would need to build controls for the USB CODEC (ADC/DAC) and do
all the other software support - further burdening the K3 CPU.

After all that, all you've done is move the USB soundcard, USB
to serial converter and USB hub into the K3 and added a whole new
level so support burden - providing operating system specific
drivers for each version of Windows (along with the cost of
signing drivers with Microsoft), specific drivers for each version
of OS-X, and specific drivers for each unique version of LINUX.
By the way ... depending on the USB Audio chip set (ADC/DAC) and
USB hub, you might find yourself needing specific drivers for each
chip (Audio, hub, control) *and* EEPROM to customize, control and
serialize each of those chip!

After all of that you have not provided any new capability for
the K3.  Other than adding at least $100 per unit in hardware,
development, and ongoing support costs the only thing this exercise
will accomplish is to relieve a relatively small number of users
of the need to purchase a KUSB and allow them to keep their sound-
card free for iTUNES.  For all the rest, you have increased the
cost of the K3, added an entirely new level of complexity to the
rig, and perhaps required that the user purchase new hardware to
use their rig with computer control.

73,

    ... Joe, W4TV

On 11/18/2010 7:31 PM, James Sarte (K2QI) wrote:
> Hello group,
>
> I know Wayne has mentioned several times in the past that they had
> considered all possibilities when it comes to PC interfaces for the K3,
> including USB.  In fact, he says the following on 16 June, 2009:
>
> "The KIO3's digital I/O module could be replaced with one that has USB
> rather than RS232 -- or better yet, both. We planned for this.
>
> The reason we went with RS232 initially is that many hams are still
> using PCs that have only RS232 ports. Those who prefer to use USB can
> use an inexpensive USB-to-RS232 adapter. There is no difference in I/O
> performance between the two methods. "
>
> Just wanted to revisit this topic and find out if anyone has heard anything
> more regarding a possible USB interface for the K3.  I know it's not for
> everyone, but for myself and perhaps others out there, the ability to carry
> all data, including audio on a single cable would be convenient.  Right now,
> I'm using a Keyspan USB to RS232 adapter for data, along with two separate
> stereo cables for audio.  I don't have any real complaints with that setup,
> but could be problematic when transferring the rig around from computer to
> computer.
>