SPEEDBIRD

VARA (TNC host client)#

SPEEDBIRD can drive a running VARA HF/FM instance (EA5HVK, closed and licensed) the same way Winlink Express, Pat and VarAC do: over VARA's documented TCP host interface. SPEEDBIRD does not contain or emulate the VARA modem. There are no waveform internals and nothing touches VARA's licensing. You need a licensed VARA, or another program that speaks the same host protocol, running somewhere on the network.

Code: src/speedbird/core/vara.py (VaraTnc, VaraService). Tests: tests/test_vara.py (fake TNC pair).

Ports and protocol#

SPEEDBIRD file convention#

A file goes out on the data port as \n#FILE <name> <size>\n followed by exactly <size> bytes. A receiving SPEEDBIRD turns that into a file in <state_dir>/vara/files. Any other peer sees it as text. All other data becomes a text message after a 0.8 s idle gap, or when the link drops.

Sending#

send connects to the peer if no link is up, writes to the data port, and waits until VARA reports BUFFER 0. It then emits sent with duration_s and bps. If SPEEDBIRD opened the link, it disconnects once nothing else is queued.

PTT#

VARA reports PTT ON/OFF. If VARA keys its own radio (VOX, CAT, or DIGIALL's in-process modems), leave ptt_handler unset. If SPEEDBIRD must key the radio, pass a ptt_handler(on: bool) that goes through the TX arbiter.

Config#

vara:
  endpoints:
    - {name: ic7300, host: 172.19.2.150, cmd_port: 8300, mycall: K4MFC-1}
    - {name: ic705,  host: 172.19.2.150, cmd_port: 8320}          # data_port defaults to 8321

Events are published on the bus as vara.<name> and use the same shapes as the SBP Console events (radio = endpoint name, plus transport: "vara"). They are logged to <state_dir>/vara/log.jsonl.