Integrations and API

CAT4OM connects to existing amateur-radio applications through TCI and Hamlib/rigctld bridges, and exposes a native JSON WebSocket API for deeper station control, monitoring, and automation.

Connect CAT4OM to the rest of the station

CAT4OM is designed to work with more than its supplied desktop UI. Existing amateur-radio applications can connect through compatibility bridges, while custom software can use the native JSON WebSocket API for deeper control, management, and live state.

These integration paths can coexist within the same station. An operator can use CAT4OM UI for control, a logger for logging, a digital-mode client for operation, a dashboard for monitoring, and a custom integration for automation without giving every tool direct access to the radio.

Many operators already have a preferred mix of applications: Log4OM for logging, WSJT-X or JTDX for digital modes, monitoring tools for station status, and sometimes custom scripts or dashboards for automation.

CAT4OM is designed to fit into that ecosystem. TCI and Hamlib/rigctld bridges help existing applications connect without native CAT4OM support, while the native API gives more advanced clients a richer way to interact with the station.

TCI bridge

CAT4OM includes a TCI bridge for compatible logging, digital-mode, and station applications.

The bridge supports:

reading and setting frequency;
reading and setting mode;
reading and setting PTT;
VFO selection;
split control and related state;
TCI capability announcements;
transmit-safe control ownership;
RX/TX audio where configured.

Changes made through the bridge update the same station state used by native clients. This means the CAT4OM UI, Radio Follower, and other integrations can react to the same sequence of station changes.

For digital-mode workflows, the TCI bridge can carry both rig control and audio in one integration path. CAT4OM can route RX audio from the selected radio audio device to the TCI client and TX audio from the client back toward the selected transmit audio device.

Because bridge commands pass through CAT4OM, the UI and other clients remain aware of station changes. The digital-mode application is not hidden behind a separate direct radio connection; it participates in the same state and ownership model.

Hamlib / rigctld bridge

CAT4OM can expose a Net rigctl-compatible endpoint for applications that already support Hamlib network rig control.

The bridge can provide:

frequency control;
mode control;
PTT;
split;
VFO addressing;
Hamlib mode mapping;
antenna tuner operation where supported by the radio profile.

This gives operators a practical way to connect existing tools without requiring those tools to implement the native CAT4OM protocol.

Native JSON WebSocket API

The native API exposes the full CAT4OM model through structured WebSocket messages.

Through the Control channel, an integration can:

discover visible radios and initial state;
request or observe ownership;
read live radio state;
set supported radio controls;
set frequency, mode, PTT, VFO, split, RIT, and XIT where supported;
use tuner, CW, raw, and diagnostic operations where available;
receive state, ownership, and event pushes;
inspect supported modes, VFOs, and commands;
use audio streaming frames where supported.

Through the Management channel, an integration can:

inspect service, group, and radio status;
discover installed handbooks and available ports;
read and update configuration;
start or stop groups and radios;
test compatible connections;
adjust log level and inspect service health;
perform supported radio power operations;
discover audio devices and monitor audio levels;
monitor follower relationships and health.

Language-independent by design

The native interface uses JSON over standard WebSocket connections. Integrations are not limited to .NET or to CAT4OM assemblies; they can be written in any language with suitable WebSocket and JSON support.

This makes CAT4OM suitable for dashboards, remote panels, monitoring tools, automation scripts, station-specific integrations, and future applications that need deeper awareness than a legacy CAT bridge can provide.

Updates, messages, and optional statistics

CAT4OM includes product-information checks and version-aware system messages so operators can see relevant update information from the UI. Optional statistics can be enabled separately and may include station-level information such as callsign and country detection, with separate client/server reporting.

These features keep operational information visible without making statistics mandatory for normal use.

Connect existing applications through TCI or Hamlib/rigctld, or use the native WebSocket API for deeper station integration.