Locked Re: Kenwood TS-2000 serial CAT control malfunction

Jan Kappert <pa0ply@...>

Hi Dave,
Thanks for this information, it is very helpfull.
During my investigation I found that ptt keying with one comport to the ts2k did work but it was not possible to use the acc2 audio input.
This was caused by th fact that the ts2k command set through rs232 only have one command, which actually blocks the audio from the acc connector.
Hardware wise one can access this 2 possibilities using the backpanel connector of the ts2k but not through the rs232 port.
I solved this problem using a different comport for the pttswitching of the radio.

Br and thanks agn.

Op di, jan. 21, 2020 om 20:59 schreef Dave_G0WBX via Groups.Io


Kenwood TS-2000 serial CAT control malfunction
From: Jan Kappert
Date: Mon, 20 Jan 2020 14:13:00 PST


Yes you will need an additional port for PTT, which is due to the limited commandset of the TS. Using one port would have been much easier, but due to the commandset issue not possible.

Br. Jan PAoPLY

Sorry Jan, but no, you do NOT need an extra COM port to do what is wanted.

Use the SAME COM port's DTR line to key the ACC2 PTT pin9 (PKS) via a small NPN transistor, "in the usual way".  Yes, you may have to build something, but it's really simple.

See  https://www.qsl.net/sv1hao/Schematic1.htm  for one opto-isolated way.

I just use a NPN transistor (2N2222 or 2N3903 2N3904, or BC108 etc) with the port DTR line going to the base via a 4k7 resistor, with an anti-parallel diode between Base and Emitter (Diode Cathode to the Transistor Base.)   After all, you've got the serial port ground common now, between Rig and PC.

The Emitter & Diode Anode goes to the radio's ground, the Collector goes to the ACC port Pin 9.

The Kenwood TS-2000 manual doesn't state the RX voltage, or TX current that pin uses, but if it's like my TS-870s, it's well within the capability of any of those transistors.

(If you switch a relay, you'll need some protection for the transistor, from the back EMF from the relay coil when going from TX to RX.)

In WSJTX's RADIO settings, either...

Use WSJTx's implementation of Hamlib, but select DTR under PTT Method.

You could also use Flrig between WSJTx/Hamlib, and the radio, as that can also use DTR PTT, and supports the TS-2000.  It then gives you more control of the rig from the PC, filter settings and so on.

I can describe how to do that too, either here, or if you PM me.

But it is perfectly possible to control many Kenwood (and possibly other) HF radios, that "Need" Hardware PTT (so as to route the sound-card audio to the TX modulator) with just one single COM port, and a little ingenuity.  Isn't that what were supposed to be able to do?

The only downside, is that when the PC boots, it may key the radio.  But the Kenwoods have a nice menu item to disable any transmission.  Menu item 27 on my TS-870, item 54 in the TS-2000.

Or just make sure the radio is powered down when the PC boots, but is powered up, before you run (FlRig if used, and then) WSJTx.

And for those afflicted with Windows, there are ways to prevent the COM port "wandering" about by itself (COM1 changing to COM3 after next boot, and so on.)

This works on all Windows I've tried, Win2k on.


I don't have Windows in the shack now, but it could perhaps work on Win10 too, I don't have access to a Win10 box to try.

Under Linux, we have the ability to create and use "Udev Rules".  But that's beyond the scope of this list.   However, good tutorials & instructions can be found using your favorite search engine, or for the real head bangers, at a command line type    man udev   and enter.

These are what I have defined.  (Running Mint 19.3)

# This lives in /lib/udev/rules.d on Mint 19.x it can be in other places, in other distro's!

#FT-736r via FTDI                                                                                                                                                                                                                          
SUBSYSTEM=="tty", ATTRS{serial}=="A50285BI", SYMLINK+="ttyFT736"

#TM-V71 via FTDI
SUBSYSTEM=="tty", ATTRS{serial}=="AK06ML2R", SYMLINK+="ttyTMV71"

#PCR1000 via genuine Prolific
SUBSYSTEM=="tty", ATTRS{devpath}=="1.3.1", SYMLINK+="ttyPCR1K"

#Thunderbolt via genuine Prolific
SUBSYSTEM=="tty", ATTRS{devpath}=="1.3.2", SYMLINK+="ttyTBOLT"

#TS-870s via genuine Prolific
SUBSYSTEM=="tty", ATTRS{devpath}=="1.3.3", SYMLINK+="ttyTS870"

#TNC-220 via genuine Prolific
SUBSYSTEM=="tty", ATTRS{devpath}=="1.3.4", SYMLINK+="ttyTNC220"

#GPS-puck via fake Prolific
SUBSYSTEM=="tty", ATTRS{devpath}=="2-1.6:1.0", SYMLINK+="ttyGPS"

The use of {serial} is preferred, and the major reason to use genuine FTDI USB/Serial adapters, as they have Unique serial numbers.   Else, you have to use the "Path" to the device, and that will change if you plug something into a different USB socket!

All the above reliably come back as the symlink, irrespective of how the OS enumerated them at boot/load time.

Within WSJTx (or FlRig) the HF radio's serial port is specified as   /dev/ttyTS870   for example, under Linux.

73 All.

Dave G0WBX, a TS-870s owner/user.  One serial port ONLY used between PC and Radio.  Job done.

Created on and sent from a Unix like PC running and using free and open source software:

Join main@WSJTX.groups.io to automatically receive all group messages.