fix(motor-antenna): don't inhibit TX on a band the antenna doesn't cover
The follow filter correctly leaves the antenna put on an un-ticked band, but the TX-inhibit loop ran independently: it gagged FlexRadio transmit whenever the antenna reported "moving" (a stray polled Moving flag, or a move finishing from the previous band), even on a band OpsLog was deliberately not managing. An operator working 15 m on another antenna had their FT8 cut mid-transmission by an "antenna moving" interlock. motorTXInhibitLoop now takes the covered-band set and forces moving=false when the current rig band isn't in it — un-ticking a band means hands off entirely: no tune AND no inhibit. Also correct the RCU-01 references to RCU-06 (the actual controller behind the short 11-byte status frame).
This commit is contained in:
@@ -509,7 +509,7 @@ func (c *Client) queryStatus() (*Status, error) {
|
||||
return nil, err
|
||||
}
|
||||
|
||||
// An older controller — seen behind an RS232-to-Ethernet bridge — answers with
|
||||
// An RCU-06 controller — seen behind an RS232-to-Ethernet bridge — answers with
|
||||
// an 11-byte status frame: the standard one WITHOUT the trailing FreqMax byte.
|
||||
// The packet checksum was already verified, so a short-but-valid frame is real,
|
||||
// not a fragment. Accept it and default the missing tail fields instead of
|
||||
|
||||
Reference in New Issue
Block a user