Skip to content

Port types

A port is one endpoint RimuCAT exposes to other software. Each port has a protocol - the language it speaks - and a transport - how software reaches it.

Create as many ports as you need. They all run at the same time, and each one is configured from the same Add Port dialog.

Port type Transports Slices
CAT Virtual serial, hardware serial, TCP, UDP One
Hamlib rigctld TCP, virtual serial One, or two in dual VFO mode
PTT Virtual serial, hardware serial One
Winkeyer Virtual serial, TCP None
OTRSP Virtual serial, TCP Two
N1MM+ spots UDP None
USB passthrough Virtual serial, hardware serial None
Wavelog / Cloudlog HTTP API None

What each one is for

CAT
Kenwood-dialect CAT control for logging and digital-mode software - frequency, mode, PTT, S-meter, and filters.
Hamlib rigctld
The Hamlib rigctld network dialect, for software configured as Hamlib NET rigctl rather than a Kenwood rig.
PTT
Transmit keying on its own port, driven by the RTS or DTR line rather than by CAT commands.
Winkeyer
CW keying from contest loggers that drive a WinKey keyer, such as N1MM+ and Win-Test. Keying goes to the radio's CW engine.
OTRSP
SO2R antenna and audio switching between two slices, for contest loggers that speak the Open Two Radio Switching Protocol.
N1MM+ spots
Receives N1MM+ bandmap spots and places them on the panadapter in RimuSDR.
USB passthrough
Relays raw bytes between a serial port on your computer and a FlexRadio USB cable, so software on the PC reaches hardware attached to the radio.
Wavelog / Cloudlog
Pushes live frequency, mode, and power into your Wavelog or Cloudlog logbook over its HTTP API, and accepts click-to-tune back.