chore(tci): log the transmit meters as they arrive, or fail to
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.
This commit is contained in:
@@ -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
|
// it. What the radio actually announces after the command settles whether
|
||||||
// this is our reading or its doing, and no amount of reasoning will.
|
// this is our reading or its doing, and no amount of reasoning will.
|
||||||
switch name {
|
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)
|
debugLog.Printf("TCI: %s:%s", name, args)
|
||||||
}
|
}
|
||||||
switch name {
|
switch name {
|
||||||
|
|||||||
Reference in New Issue
Block a user