Feature request: Internal ATU memory indexed by Antenna Genius antenna selection

SM6KZW

When an Antenna Genius is connected behind a FlexRadio antenna port (Port A or B on 6000/8000Aurora), the internal ATU stores tuning solutions per radio port only. It has no awareness of which AG antenna is currently selected behind that port. The result is that ATU memory becomes unreliable as soon as multiple antennas with different impedance characteristics share the same radio port through AG. With MEM enabled, the radio will recall the wrong solution. With MEM disabled, the ATU stays on the last loaded solution and the operator has to manually retune on every antenna change.

The mechanism to fix this already exists in the ecosystem:

• AG publishes its selected antenna slot (1 to 8) over the SmartSDR API
• SmartSDR already consumes this API for automatic band-based antenna selection through AG
• Tuner Genius XL uses the same data and stores 20 tuning memories per band, per AG antenna slot, when paired with AG (20 x 12 x 9 = 2160 stored solutions per the published spec)

What the internal ATU does today: index memory by (radio port, band, frequency).
What it could do: index memory by (radio port, AG antenna slot, band, frequency).

The radio already knows everything it needs. The AG antenna slot is published on the LAN. The internal ATU firmware would need to subscribe to AG state, expand its memory index, and store more solutions. No hardware change required, and TGXL has already demonstrated that the data flow works.

This would benefit any operator running AG without TGXL, which is a real configuration for stations that do not need 2 kW tuning. The Aurora AU-510/AU-520 ship with a 500W internal ATU integrated into the product specifically to reduce the need for external boxes, which makes this gap more visible on Aurora than on the legacy 6000 series.

I understand TGXL is the current path for this use case and that there may be valid reasons (firmware priorities, validation effort, memory footprint) for keeping the integration where it is. But the architecture supports it cleanly, and closing this gap would meaningfully improve the experience for AG users who do not also run TGXL.