From 130c4e72e05b55f2a174273f5003edd66e2a5faa Mon Sep 17 00:00:00 2001 From: rouggy Date: Wed, 26 Aug 2026 21:28:09 +0200 Subject: [PATCH] chore(tci): log the transmit meters as they arrive, or fail to MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The log shows 'tx_power;' going out four times a second during a tune and nothing coming back — but that proves less than it looks: a reply that arrived and failed to parse leaves exactly the same trace as one that never came. Both are now visible. --- internal/cat/tci_panel.go | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/internal/cat/tci_panel.go b/internal/cat/tci_panel.go index 7e3afb6..d4f064c 100644 --- a/internal/cat/tci_panel.go +++ b/internal/cat/tci_panel.go @@ -111,7 +111,12 @@ func (t *TCI) handlePanel(name string, get func(int) string, args string) bool { // it. What the radio actually announces after the command settles whether // this is our reading or its doing, and no amount of reasoning will. switch name { - case "mute", "sql_enable", "sql_level": + case "mute", "sql_enable", "sql_level", "tx_power", "tx_swr", "tune": + // Logged on arrival so an ANSWER can be told from a silence. The + // transmit meters are asked for four times a second while keyed and the + // log showed only the asking, which proves nothing on its own: a reply + // that arrived and failed to parse looks exactly like one that never + // came. debugLog.Printf("TCI: %s:%s", name, args) } switch name {