From 848ce68ec527b25b019a4404281a6e86e739666d Mon Sep 17 00:00:00 2001 From: rouggy Date: Tue, 25 Aug 2026 23:18:11 +0200 Subject: [PATCH] feat(tci): key the radio ourselves and push a tone, to see what it wants MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A first real transmission settled one question and raised a better one. With the receive stream open and six seconds of transmit, the radio sent 282 frames of receive audio and NOTHING else: no chrono, no transmit audio. So the chrono the documentation describes is not offered to a client that merely happens to be connected while the operator keys the microphone, and waiting for it to appear is waiting for nothing. The reading that fits is that the radio asks for audio when the transmission is the CLIENT'S and takes the microphone when it is the operator's — which makes the experiment obvious. Key it from here, push a 1 kHz tone, and watch. Chrono frames appearing gives their size and cadence by measurement instead of by guesswork; no chrono but a tone on the meter is just as useful, because then the pacing is optional and the voice keyer can push frames at the rate the stream already runs at. A tone rather than silence so the answer shows on the power meter and not only in the log. It transmits, so: an explicit button inside a warning box, five seconds, capped at ten, and every path out unkeys — including the panic that has not happened yet and a socket that dies mid-tone. A transmitter left keyed by a defect is the one fault here that would reach somebody else's band. Writes are now serialised too. send() held the lock only long enough to read the connection, which was enough while every command came from the poll loop; a stream of audio frames from a second goroutine is not, and gorilla panics on a concurrent write rather than failing quietly. --- app_tci_audio.go | 27 ++++ frontend/src/components/SettingsModal.tsx | 20 ++- frontend/src/lib/i18n.tsx | 4 +- frontend/wailsjs/go/main/App.d.ts | 2 + frontend/wailsjs/go/main/App.js | 4 + internal/cat/tci.go | 7 + internal/cat/tci_tx_probe.go | 171 ++++++++++++++++++++++ 7 files changed, 232 insertions(+), 3 deletions(-) create mode 100644 internal/cat/tci_tx_probe.go diff --git a/app_tci_audio.go b/app_tci_audio.go index be2b283..c65ea1a 100644 --- a/app_tci_audio.go +++ b/app_tci_audio.go @@ -51,3 +51,30 @@ func (a *App) GetTCIAudioStatus() cat.TCIAudioStatus { st, _ := a.cat.TCIAudioState() return st } + +// ProbeTCITransmit keys the radio and pushes a tone over TCI, to find out +// whether the transmit half of the stream works at all. +// +// A first real transmission proved that the radio sends nothing extra while the +// OPERATOR keys it — 282 receive frames and no chrono over six seconds — so the +// only way forward is to key it from here and watch. Everything interesting +// lands in the log; see internal/cat/tci_tx_probe.go for what the two possible +// answers mean. +// +// THIS TRANSMITS. The button that calls it says so, and the radio must be on a +// dummy load. +func (a *App) ProbeTCITransmit(seconds int) error { + if a.cat == nil { + return fmt.Errorf("CAT not initialized") + } + return a.cat.TCIAudioDo(func(t cat.TCIAudioController) error { + p, ok := t.(interface { + ProbeTXStream(seconds int, toneHz float64) error + }) + if !ok { + return fmt.Errorf("this CAT backend is not a TCI radio") + } + applog.Printf("tci: TX PROBE requested (%d s) — the radio should be on a dummy load", seconds) + return p.ProbeTXStream(seconds, 1000) + }) +} diff --git a/frontend/src/components/SettingsModal.tsx b/frontend/src/components/SettingsModal.tsx index 3e8ff26..db1ae37 100644 --- a/frontend/src/components/SettingsModal.tsx +++ b/frontend/src/components/SettingsModal.tsx @@ -58,7 +58,7 @@ import { GetFolderSync, SaveFolderSync, PickFolderSyncFolder, GetFolderSyncStatus, SyncFolderNow, GetRelayAuto, SaveRelayAuto, GetStationDevices, GetAwardDefs, GetTrackedAwards, SaveTrackedAwards, - GetBandOpenSettings, SaveBandOpenSettings, GetGridScopeSettings, SaveGridScopeSettings, GetPSKReporterStatus, GetChaseNewGrids, SetChaseNewGrids, GetChaseNew, SetChaseNew, GetGridCacheStatus, GetLinkedAmps, SetLinkedAmps, GetSpotTTLMinutes, SetSpotTTLMinutes, GetSpotMax, SetSpotMax, StartTCIAudio, StopTCIAudio, GetTCIAudioStatus, RecordTCIAudio, GetTCIRecordAudio, SetTCIRecordAudio, + GetBandOpenSettings, SaveBandOpenSettings, GetGridScopeSettings, SaveGridScopeSettings, GetPSKReporterStatus, GetChaseNewGrids, SetChaseNewGrids, GetChaseNew, SetChaseNew, GetGridCacheStatus, GetLinkedAmps, SetLinkedAmps, GetSpotTTLMinutes, SetSpotTTLMinutes, GetSpotMax, SetSpotMax, StartTCIAudio, StopTCIAudio, GetTCIAudioStatus, RecordTCIAudio, GetTCIRecordAudio, SetTCIRecordAudio, ProbeTCITransmit, } from '../../wailsjs/go/main/App'; import type { profile as profileModels } from '../../wailsjs/go/models'; import type { LookupSettingsForm, StationSettingsForm, ListsSettingsForm, ModePresetForm } from '@/types'; @@ -1948,6 +1948,7 @@ export function SettingsModal({ onClose, onSaved, initialSection, onMainPaneChan // done for nothing. const [tciAudio, setTciAudio] = useState({ running: false, sample_rate: 0, frames: 0, peak_db: -99 }); const [tciRecBusy, setTciRecBusy] = useState(false); + const [tciTXBusy, setTciTXBusy] = useState(false); // Whether the QSO recorder takes its audio from the radio's own stream. const [tciRec, setTciRec] = useState(false); useEffect(() => { GetTCIRecordAudio().then((v: boolean) => setTciRec(!!v)).catch(() => {}); }, []); @@ -6601,6 +6602,23 @@ export function SettingsModal({ onClose, onSaved, initialSection, onMainPaneChan {!!tciRecPath && {tciRecPath}} )} + {/* The transmit experiment. It KEYS THE RADIO, which is why it is + worded as a warning and not as another test button: a first pass + on real hardware showed the radio sends nothing extra while the + operator keys it by hand, so the only way to learn what it wants + is to key it from here and push a tone. */} +
+ +

{t('aud.tciTXWarn')}

+
{!!tciAudio.last_err &&

{tciAudio.last_err}

}